Develop Bugs

Retail Rom and IMEI lost

Is there any risk of lose the IMEI while flashing a retail ROM instead of a carrier-brand one?

Only one way to find out is to try it.. If it does, I'm sure if reflash a branded one, you would get it back..

Try skipping the modem firmware i.e NOH-HLOS , fsg , erase modemst1 and modemst2. And flash boot , recovery and system_sparsechunks. I have not personally tried this (bcoz already on retail rom) but may work as reported in Moto Z2 Play forum
Sent from my Moto Z2 Force using XDA Labs

YESSSS
Only if you downgrade with flashall.
Use this instead:
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit

Z2 with no OS. Need help to get it back

Hello everbody,
Here is my story of how I managed it to have to OS on my Z2 Force (XT1789-6 with 6gb). I wanted to have lineagos on my smartphone and installed it before on my smartphone therefore I thought it would be easy.
1. I visited the official page and followed there instruction until the twrp instruction
HTML:
https://wiki.lineageos.org/devices/nash/install
. I did an oem unlock and installed twrp temporally (fastboot boot twrp-3.2.3-1-nash.img) and did a full backup.
2. I was reading on this forum that I need Oreo on my phone to install lineage, therefore I tried to update it. All attempts to update it failed. I was able to download updates to my phone and it started to install but it always failed.
3. I tried to flash the fitting Oreo Version on my phone (XT1789—06) OPXS27.109-49-5 from
HTML:
https://forum.xda-developers.com/z2-force/development/factory-image-moto-z2-force-nash-retail-t3699306
with the sequence in #5 but it would only flash the bootloader and fails for the rest (erase works).
I flashed no gpt.bin!
*(fastboot flash bootloader bootloader.img) -> only when needed!
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash system_b system_b.img_sparsechunk.3
fastboot flash oem oem.img
fastboot erase cache
fastboot erase carrier
fastboot erase ddr
fastboot reboot
Click to expand...
Click to collapse
Fastboot menu now showed a modified Version
4. Since the official website does not tell about having Oreo on you smartphone I wanted to give it a try and proceeded with their instruction. I wiped the system and tried to install lineage with help of TWRP with resulted in Error 255.
5. I tried to Recover with TWRP but it told me that no partition is selected. Fastboot menu shows that there is no partition a/b.
I tried to flash Nougat from the same source like Oreo which works for bootloader (and gpt.bin) and fails for the rest
xxx>fastboot flash modem NON-HLOS.bin
Sending 'modem__a' (97411 KB) OKAY [ 2.684s]
Writing 'modem__a' (bootloader) Invalid partitio
n name modem__a
FAILED (remote failure)
Finished. Total time: 2.700s
6. No it shows me in fastboot that I have an unmodified oem locked phone. On start up it tells me that I have a corrupted phone and instead of the yellow unlocked bootloader warning its red. Its starts over and over again until I start fastboot.
Can you suggest me how I can get back to stock or to lineage?

b.bew said:
Hello everbody,
Here is my story of how I managed it to have to OS on my Z2 Force (XT1789-6 with 6gb). I wanted to have lineagos on my smartphone and installed it before on my smartphone therefore I thought it would be easy.
1. I visited the official page and followed there instruction until the twrp instruction
HTML:
https://wiki.lineageos.org/devices/nash/install
. I did an oem unlock and installed twrp temporally (fastboot boot twrp-3.2.3-1-nash.img) and did a full backup.
2. I was reading on this forum that I need Oreo on my phone to install lineage, therefore I tried to update it. All attempts to update it failed. I was able to download updates to my phone and it started to install but it always failed.
3. I tried to flash the fitting Oreo Version on my phone (XT1789—06) OPXS27.109-49-5 from
HTML:
https://forum.xda-developers.com/z2-force/development/factory-image-moto-z2-force-nash-retail-t3699306
with the sequence in #5 but it would only flash the bootloader and fails for the rest (erase works).
Fastboot menu now showed a modified Version
4. Since the official website does not tell about having Oreo on you smartphone I wanted to give it a try and proceeded with their instruction. I wiped the system and tried to install lineage with help of TWRP with resulted in Error 255.
5. I tried to Recover with TWRP but it told me that no partition is selected. Fastboot menu shows that there is no partition a/b.
I tried to flash Nougat from the same source like Oreo which works for bootloader (and gpt.bin) and fails for the rest
xxx>fastboot flash modem NON-HLOS.bin
Sending 'modem__a' (97411 KB) OKAY [ 2.684s]
Writing 'modem__a' (bootloader) Invalid partitio
n name modem__a
FAILED (remote failure)
Finished. Total time: 2.700s
6. No it shows me in fastboot that I have an unmodified oem locked phone. On start up it tells me that I have a corrupted phone and instead of the yellow unlocked bootloader warning its red. Its starts over and over again until I start fastboot.
Can you suggest me how I can get back to stock or to lineage?
Click to expand...
Click to collapse
Try this commands:
fastboot --set-active=_a
pause
fastboot reboot bootloader
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader_a bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash bluetooth_a BTFM.bin
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash oem_a oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot oem fb_mode_clear
fastboot -w
fastboot --set-active=_b
fastboot reboot bootloader
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader_b bootloader.img
fastboot flash modem_b NON-HLOS.bin
fastboot flash fsg_b fsg.mbn
fastboot flash bluetooth_b BTFM.bin
fastboot flash dsp_b adspso.bin
fastboot flash logo_b logo.bin
fastboot flash boot_b boot.img
fastboot flash system_b system.img_sparsechunk.0
fastboot flash system_b system.img_sparsechunk.1
fastboot flash system_b system.img_sparsechunk.2
fastboot flash system_b system.img_sparsechunk.3
fastboot flash system_b system.img_sparsechunk.4
fastboot flash system_b system.img_sparsechunk.5
fastboot flash oem_b oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
fastboot -w
fastboot --set-active=_a
fastboot reboot bootloader

Wow thanks. Worked out perfectly.

So many thanks, this helped me from a hard brick

Help 0 imei no wifi no cellular signal

I have the xt1789-04 I updated it to android 9.0 without flashing the modems everything worked fine then did flash all to Oreo and the fhlashed pixel experience ROM witch got me into bootloop so I flash Oreo again and now I have now WiFi no data no imei and I tried flashing twrp but it won’t let me keeps on appearing an error message

I had similar issue and I tried following file and it helped me. below code will erase everything on your phone so proceed with caution.
if you are on fastboot mode, try flashing stock oreo with bothslotflashall.bat file(below code). If you dont have mfastboot, please edit below code with "fastboot" command.
fastboot erase all
mfastboot oem fb_mode_set
mfastboot getvar max-sparse-size
mfastboot flash partition gpt.bin
mfastboot flash bootloader_a bootloader.img
mfastboot flash bootloader_b bootloader.img
mfastboot flash modem_a NON-HLOS.bin
mfastboot flash fsg_a fsg.mbn
mfastboot flash modem_b NON-HLOS.bin
mfastboot flash fsg_b fsg.mbn
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash bluetooth_a BTFM.bin
mfastboot flash dsp_a adspso.bin
mfastboot flash logo_a logo.bin
mfastboot flash boot_a boot.img
mfastboot flash system_a system.img_sparsechunk.0
mfastboot flash system_a system.img_sparsechunk.1
mfastboot flash system_a system.img_sparsechunk.2
mfastboot flash system_a system.img_sparsechunk.3
mfastboot flash system_a system.img_sparsechunk.4
mfastboot flash system_a system.img_sparsechunk.5
mfastboot flash oem_a oem.img
mfastboot flash bluetooth_b BTFM.bin
mfastboot flash dsp_b adspso.bin
mfastboot flash logo_b logo.bin
mfastboot flash boot_b boot.img
mfastboot flash system_b system.img_sparsechunk.0
mfastboot flash system_b system.img_sparsechunk.1
mfastboot flash system_b system.img_sparsechunk.2
mfastboot flash system_b system.img_sparsechunk.3
mfastboot flash system_b system.img_sparsechunk.4
mfastboot flash system_b system.img_sparsechunk.5
mfastboot flash oem_b oem.img
mfastboot erase carrier
mfastboot erase ddr
mfastboot oem fb_mode_clear
mfastboot -w
mfastboot --set-active=other
mfastboot reboot-bootloader
Click to expand...
Click to collapse

Will try it when I get home and will let you know for now thank you

latadswapnil said:
I had similar issue and I tried following file and it helped me. below code will erase everything on your phone so proceed with caution.
if you are on fastboot mode, try flashing stock oreo with bothslotflashall.bat file(below code). If you dont have mfastboot, please edit below code with "fastboot" command.
Click to expand...
Click to collapse
Any risk to run "fastboot erase all"
My baseband "Not Found".
Sent from my LG-LS997 using Tapatalk

cgigate said:
Any risk to run "fastboot erase all"
My baseband "Not Found".
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
erase all will erase all the partitions, I have done this on my XT1789-04 several times and never faced any issue.
But be sure that you have a stock rom to flash.

latadswapnil said:
erase all will erase all the partitions, I have done this on my XT1789-04 several times and never faced any issue.
But be sure that you have a stock rom to flash.
Click to expand...
Click to collapse
Actually. the "erase all" does very little things, I wish it can erase the modem_a and modem_b partitions.
>fastboot erase all
erasing 'all'...
(bootloader) erasing ddr ...
(bootloader) erasing carrier ...
(bootloader) erasing modemst1 ...
(bootloader) erasing modemst2 ...
(bootloader) erasing fsc ...
(bootloader) erasing userdata ...
(bootloader) erasing fsg_a ...
(bootloader) erasing fsg_b ...
OKAY [ 0.829s]
finished. total time: 0.830s

cgigate said:
Actually. the "erase all" does very little things, I wish it can erase the modem_a and modem_b partitions.
>fastboot erase all
erasing 'all'...
(bootloader) erasing ddr ...
(bootloader) erasing carrier ...
(bootloader) erasing modemst1 ...
(bootloader) erasing modemst2 ...
(bootloader) erasing fsc ...
(bootloader) erasing userdata ...
(bootloader) erasing fsg_a ...
(bootloader) erasing fsg_b ...
OKAY [ 0.829s]
finished. total time: 0.830s
Click to expand...
Click to collapse
Yeah it doesn't, I dont understand why cant we able to format these system partitions, I thought of blankflashing older bootloader and install older stock rom but my phone doesnt go in EDL mode.

latadswapnil said:
Yeah it doesn't, I dont understand why cant we able to format these system partitions, I thought of blankflashing older bootloader and install older stock rom but my phone doesnt go in EDL mode.
Click to expand...
Click to collapse
Actually, it is very easy to get in EDL mode.

cgigate said:
Actually, it is very easy to get in EDL mode.
Click to expand...
Click to collapse
I tried all the methods available online such as "adl reboot edl" or from twrp nothing works. Phone just reboots normally , once or twice screen went blank but then again system didnt detect the phone and phone rebooted again normally in 30 seconds automatically.
I tried USB 2.0, 3.0, USB C but nothing is working.

latadswapnil said:
I tried all the methods available online such as "adl reboot edl" or from twrp nothing works. Phone just reboots normally , once or twice screen went blank but then again system didnt detect the phone and phone rebooted again normally in 30 seconds automatically.
I tried USB 2.0, 3.0, USB C but nothing is working.
Click to expand...
Click to collapse
"adb reboot edl" works well to get in EDL mode from TWRP.
there is a timing issue
All you needs is to run "flashblanl.bat" in another CMD windows, then immediately issue ""adb reboot edl" command in a CMD windows under twrp,
but my blankflashing can flash, you can see the progress and logs, but it eventually failed, I may need to make another blank flash single image file

gave it a try and it didnt let me flash this is what appeared
quote: C:\Users\gustavo\Downloads\TMO Moto Z2 Force 27.1.5 flashall\TMO Moto Z2 Force 27.1.5 flashall>fastboot erase all
(bootloader) partition-ty: not found
erasing 'all'...
(bootloader) Invalid partition name allrtition-ty
FAILED (remote failure)
finished. total time: 0.023s

i was able to flash the comands but still imei unavailable and no cellular signal and no wifi

Moto Z2 Play Start Up Failed

Moto Z2 Play was running Andorid 9.0 29.133.30 I was trying to downgrade to Android 8 by using fastboot but it kept on failing, to make sure it didn't mess with anything else I flashed the Android 9 ROM on via fastboot and all the fastboot commands were successful but now it ONLY booting into fastboot saying "Error: Failed to pass validation. backup to fastboot"
Any help?
Here's the commands used.
Spoiler: Code
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
Right after I posted this thread I found my solution... The script I yoinked from the Android 8 ROM was missing one sparsechunk, got it working again now.
Will never do that again.

TechnoRush said:
Right after I posted this thread I found my solution... The script I yoinked from the Android 8 ROM was missing one sparsechunk, got it working again now.
Will never do that again.
Click to expand...
Click to collapse
I recommend creating your own .bat file from the flash_file.xml
Use a batch file for easier flashing
Online FlashFile Converter

[MOTO G5] boot loop - ADSP error

Hi there, thanks in advance for the help.
The issue
I have a Moto G5 XT1675 (Bootloader unlocked), which recently has started rebooting on it's own.
First it was sporadic, now it almost never reaches the end of the boot animation.
What I've tried to fix it
Tried a factory reset from TWRP -> no difference
Tried a "full wipe" (system+data+cache+dalvik) and reflashing stock ("XT1675_CEDRIC_TIMIT_8.1.0_OPPS28.85-13-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml") -> again no difference, phone still reboots at random times during sturtup animation or in rare cases soon after the welcome screen appears
Commands used to reflash stock ROM:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Additional data
Got the logs from `/sys/fs/pstore/` using ADB after one of the reboots. Logs seem to hint to an issue with ADSP.
Full logs in attachment.
console-ramoops
Code:
[ 26.247802,6] Fatal error on adsp!
[ 26.247835,6] adsp subsystem failure reason: DALSysLogEvent.c:172:DALLOG Device [0x2000145] Type [F06426FA] Log [F065DFDB].
[ 26.247856,6] Kernel panic - not syncing: Subsystem adsp crashed during SSR!
[ 26.247868,6] CPU: 6 PID: 350 Comm: kworker/u16:5 Not tainted 3.18.71-perf-g6fc7aba #1
[ 26.247900,6] [<c010e00c>] (unwind_backtrace) from [<c010aa70>] (show_stack+0x10/0x14)
[ 26.247916,6] [<c010aa70>] (show_stack) from [<c0d01eb4>] (dump_stack+0x78/0x98)
[ 26.247932,6] [<c0d01eb4>] (dump_stack) from [<c0cfe60c>] (panic+0x11c/0x39c)
[ 26.247949,6] [<c0cfe60c>] (panic) from [<c04da848>] (subsystem_restart_dev+0x13c/0x1e4)
[ 26.247966,6] [<c04da848>] (subsystem_restart_dev) from [<c04d2ff4>] (subsys_err_fatal_intr_handler+0x54/0x64)
What is ADSP? Is this an hardware issue? Any chance to fix it? Thanks!