DUB-LX1 - bootloop after UPDATE.APP

[mahcin]

--------- 2020-07-03 22:36:42 ---------
SigmaKey 2.36.01 Qcom: Write firmware
^ Android Sooner Single ADB Interface, Version 0.5, Name: MSM8953, Serial number: 4FF6R19Bxxxxxxxxx
(ADB) Writing flash...UPDATE.APP
Firmware: DUB-L22 8.2.0.100(C432)
Wrong selection of firmware files can damage the phone.
Are you sure you want to proceed? [YES]
Version: System 8.2.0.036(06J8)
Preparing...This Android security patch level is not supported.
Please wait for future updates.
--------- 2020-07-03 22:45:42 ---------
SigmaKey 2.36.01 Qcom: Write firmware
^ Android Sooner Single ADB Interface, Version 0.5, Name: MSM8953, Serial number: 9e5e6820
(ADB) Writing flash...UPDATE.APP
Firmware: DUB-L22 8.2.0.100(C432)
Wrong selection of firmware files can damage the phone.
Are you sure you want to proceed? [YES]
Version: DUB-AL00-BD 1.0.0.54(log)
Writing flash partition...Partition table doesn't exist

Writing flash rpm...OK
Writing flash tz...OK
Writing flash sbl1...OK
Writing flash apdp...OK
Writing flash msadp...OK
Writing flash keymaster...OK
Writing flash devcfg...OK
Writing flash aboot...OK
Writing flash modem...OK
Writing flash kernel...OK
Writing flash ramdisk...OK
Writing flash recovery_ramdisk...OK
Writing flash recovery_vendor...OK
Writing flash preas.0...Partition table doesn't exist

Writing flash preas.1...partition table doesn't exist
Writing flash preavs.0...Partition table doesn't exist

Writing flash prets.0...Partition table doesn't exist

Writing flash pretvs.0...Partition table doesn't exist

Writing flash erecovery_kernel...OK
Writing flash erecovery_ramdisk...OK
Writing flash erecovery_vendor...OK
Writing flash system.0...OK
Writing flash system.1...OK
Writing flash system.2...OK
Writing flash system.3...OK
Writing flash cache.0...OK
Writing flash odm.0...OK
Writing flash vendor.0...OK
Writing flash product.0...OK
Writing flash userdata.0...OK
Writing flash...Done
Restarting phone...OK

Same file works absolutely fine from SD card/phone works fine every time when flashed via SD, everytime bootloop when flashed via sigma. Can You fix it please? I would be easier and faster to flash via key.

[mahcin]

I think all because Sigma is not supporting these partitions:
P53: preas (006DE000, 001D8000) 944 MB
P54: preavs (008B6000, 00010000) 32 MB
P55: prets (008C6000, 00062000) 196 MB
P56: pretvs (00928000, 00008000) 16 MB

these partitions are in latest software versions of DUB-LX1.

[rebainoor]

your mobile is DUB-LX1 or DUB-LX2 ?

[kikas112]

board soft write over test point, u write in adb

[mahcin]

DUB-LX1

I have no problem with flash .APP by SD card at all, successful flash, phone working, but I'm doing research how do it with Sigma, would be nice to do it.

I have tried with TP, Factory Mode, Fastboot... all methods over last 3 days, I had 100% final repair only by SD flash or by some other tools, but when flashing with sigma (.APP files) - phone always in bootloop. Same files used for SD method and no problems at all.

my phone hardware is from december 2019. C10 cust with original 8.2.0.147 software and latest security version.
57 partitions in it (when fully working)
GPT was on position 00
so last partition is 57th really not 56th

P53: preas (006DE000, 001D8000) 944 MB
P54: preavs (008B6000, 00010000) 32 MB
P55: prets (008C6000, 00062000) 196 MB
P56: pretvs (00928000, 00008000) 16 MB

I have passed it back to customer, fully working, but flashed with other tool, would be nice to make full repair with sigma, however I would be not able successful repair without sigma. Sigma made perfect IMEI/oeminfo details repair. Brilliant tool for repair, unfortunately not good for full flash repair.

Please don't understand me wrong, brilliant tool for repair, I wouldn't be able do IMEI/oeminfo repair without sigma, but I wasn't able do successful flash with sigma. Phone was taken now by customer, but I hope that some time in the future flash option will be improved for latest SW/HW

I have flashed version: 8.2.0.160
Phone boot OK when SD method.
Phone in bootloop when same .APP flashed by sigma (fastboot/TP)

[kikas112]

Just flash in upgrade mode, works good

Wysłane z mojego moto g(6) play przy użyciu Tapatalka

[rebainoor]

team will test and fix this issus in future update

[mahcin]

Originally Posted by kikas112

Just flash in upgrade mode, works good

Please understand that I was doing research as above explained, maybe if someone has not fully software damaged phone, some modes like "upgrade mode" will do fine, unfortunately when software is totally damaged it doesn't work correctly. I just found that there are two versions of software, let say NEW and OLD:
if I modify ramdisk from older software, for root purposes and load it to NEW versions like 80.2.0.160 I will end up in bootloop, from NEW it won't work in older versions... so I can see similar problem in flashing by sigma. Maybe if someone has older DUB-LX1 then everything works perfect regarding flashing.

Please understand that DUB-LX1 is in production from beginning of 2018 (maybe end of 2017?) My board/factory software is from end of 2019.

They could change something on factory production which we're not yet aware here, this is not very popular phone, usually sold as unlocked so not many people need really flash it. I hope that this post will help to get it sorted.

In deep files of this unit I could see "DUB-L21" for OTA purposes, but on the phone box and in the menu originally it says DUB-LX1

[mahcin]

btw as far as I know partition table is taken from files or phone, partition table is not dictated by flashing software, in this case sigma. It could be dictated by flasher IF flasher would now for which addresses ask phone exactly. (This is just my theory about it, I may be wrong, just theory)

btw2:
In SigmaKey 2.36.00 I couldn't flash .APP for this unit at all (wrong partition table error), so in this SigmaKey 2.36.01 I could flash, so a little bit more Sigma team and this platform of LX1 will be whole compatible :-)

Thanks

Unfortunately I'll be able test it again when again I get same phone.