Related
I tried to flash a downgrade image to my moto e 2nd gen. Now Im stuck in bootloader and a warning message for unlocked bootloder. Ive tried to flash logo.bin, and other images aswell with no luck. It keeps asking me to install a valid signed images, I don't know where to find these images. Please help!
You need to do exactly what it's asking you to do - flash valid signed images. Which model do you have (XT152x)? Which region are you in? Which version were you downgrading from?
Just so you know, downgrading the stock ROM is very highly discouraged as it can cause bricking in certain circumstances. In particular, never try to downgrade the stock ROM when the bootloader is locked. You can try flashing back the upgraded images and seeing if your phone accepts them. Be aware that the signed images must match your model number and region.
squid2 said:
You need to do exactly what it's asking you to do - flash valid signed images. Which model do you have (XT152x)? Which region are you in? Which version were you downgrading from?
Just so you know, downgrading the stock ROM is very highly discouraged as it can cause bricking in certain circumstances. In particular, never try to downgrade the stock ROM when the bootloader is locked. You can try flashing back the upgraded images and seeing if your phone accepts them. Be aware that the signed images must match your model number and region.
Click to expand...
Click to collapse
Thanks for reply.
I don't have these images, where to get them? My model is xt1524reteuall, I'm in europe/sweden and I downgraded from stock Lollipop 5.0.2
I did unlock the bootloader via motorolas site.
pemhak said:
Thanks for reply.
I don't have these images, where to get them? My model is xt1524reteuall, I'm in europe/sweden and I downgraded from stock Lollipop 5.0.2
I did unlock the bootloader via motorolas site.
Click to expand...
Click to collapse
Hmm, so you went from a newer 5.0.2 build to an old 5.0.2 build? What were you downgrading to?
Go to this folder: https://mega.nz/#F!rMIhDLgR!oq5Cz_XbgZLEEysmqoYtcA
Navigate to Surnia ->5.0.2
Look for the file XT1524_RETEUALL_MOTOE2... (it's near the middle of the list)
Download and try flashing everything it in using fastboot.
squid2 said:
You need to do exactly what it's asking you to do - flash valid signed images. Which model do you have (XT152x)? Which region are you in? Which version were you downgrading from?
Just so you know, downgrading the stock ROM is very highly discouraged as it can cause bricking in certain circumstances. In particular, never try to downgrade the stock ROM when the bootloader is locked. You can try flashing back the upgraded images and seeing if your phone accepts them. Be aware that the signed images must match your model number and region.
Click to expand...
Click to collapse
Thanks for reply.
I don't have these images, where to get them? My model is xt1524reteuall, I'm in europe/sweden and I downgraded from stock Lollipop 5.0.2
I did unlock the bootloader via motorolas site.
I got my device back!! I did succeed to flash it with this rom "surnia_stock_5.0.2.zip" with TWRP. I did not have the patience to wait at the Motorola logo when booting, I have to wait 2-3 min and 2-3 min for services to start. for the device to boot. But now it doesn't register any sim card when at desktop?!?
squid2 said:
Hmm, so you went from a newer 5.0.2 build to an old 5.0.2 build? What were you downgrading to?
Go to this folder:
Navigate to Surnia ->5.0.2
Look for the file XT1524_RETEUALL_MOTOE2... (it's near the middle of the list)
Download and try flashing everything it in using fastboot.
Click to expand...
Click to collapse
I was downgrading to kitkat 4.4.4 due to poor battery in lollipop 5.0.2. I'm downloading a xt1524reteuall rom right now but ir is going slowly.
pemhak said:
I was downgrading to kitkat 4.4.4 due to poor battery in lollipop 5.0.2. I'm downloading a xt1524reteuall rom right now but ir is going slowly.
Click to expand...
Click to collapse
Oh, you must have flashed something really wrong then. There are no 4.4.4 ROMs for this device. You would have flashed something totally incompatible and highly risky if you flashed 4.4.4 from somewhere. That may have wrecked your modem software too. Download and flash the proper XT1524-specific software with the correct modem. If you are unhappy with the performance of the stock ROM, you can flash scritch007's CM12.1.
squid2 said:
Oh, you must have flashed something really wrong then. There are no 4.4.4 ROMs for this device. You would have flashed something totally incompatible and highly risky if you flashed 4.4.4 from somewhere. That may have wrecked your modem software too. Download and flash the proper XT1524-specific software with the correct modem. If you are unhappy with the performance of the stock ROM, you can flash scritch007's CM12.1.
Click to expand...
Click to collapse
Ok, thanks. I will wait for download to complete and flash that image.
pemhak said:
Ok, thanks. I will wait for download to complete and flash that image.
Click to expand...
Click to collapse
Hi! Did you solve your problem? I'm kind of stuck on same problem and with no working solution yet.
EDIT: I tried the @squid2 with no success. Maybe I will send the phone to waranty....
Noeljunior said:
Hi! Did you solve your problem? I'm kind of stuck on same problem and with no working solution yet.
EDIT: I tried the @squid2 with no success. Maybe I will send the phone to waranty....
Click to expand...
Click to collapse
I did solve the problem with these steps.
1. Find and download the files for your region.
2. Unzip files to a folder with fastboot and adb.
3. Create stock.bat with these commands and run stock.bat within the same folder as above files.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
fastboot reboot
(4. I needed to reunlock my Moto E 2nd Gen at Motorolas site, because i did relock it.)
5. Get into bootloader menu and flash this TWRP image (i can email it to you) within the same folder and flash it with fastboot.
6. Restart phone. Wait 2-3 minutes so it boots into android.
7. Hope I made it clear enough to follow the instructions, if you got questions please reply and I try to answer them. Sorry for my poor english.
pemhak said:
I did solve the problem with these steps.
1. Find and download the files for your region.
2. Unzip files to a folder with fastboot and adb.
3. Create stock.bat with these commands and run stock.bat within the same folder as above files.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
fastboot reboot
(4. I needed to reunlock my Moto E 2nd Gen at Motorolas site, because i did relock it.)
5. Get into bootloader menu and flash this TWRP image (i can email it to you) within the same folder and flash it with fastboot.
6. Restart phone. Wait 2-3 minutes so it boots into android.
7. Hope I made it clear enough to follow the instructions, if you got questions please reply and I try to answer them. Sorry for my poor english.
Click to expand...
Click to collapse
And I'm back with my Moto E! Thank you! I wasn't doing some of those commands and with all those commands it works! Thank you!
After so many failed attempts I found the way to get my phone a brick. Thanks to the rom "XT1625_ATHENE_AMAZON_MPJ24.139-64_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip".
The method only require simple:
- Tool ADB: http://www.mediafire.com/file/9m1dopcvpmm6zif/adb-setup-1.4.3.exe
- Fastboot+abds: http://www.mediafire.com/file/48gtedd1hlodozz/Herramientas+ADB.rar
- Drivers motorola: http://www.mediafire.com/file/90xvah7a3p4l2m4/MotorolaDeviceManager_2.4.5.exe
- Rom moto g4 amazon prime: https://goo.gl/dK7u4X
- RSDLite6.2.4.zip: http://rootjunkysdl.com/files/Moto G 4th Gen XT1625/Remove Amazon Bloat Ads/RSDLite6.2.4.zip
After having the essential tools unpack the ROM our "moto g4 amazon".
- Install the drivers phone and ads.
- After you've done this step opens RSD lite.
- Having your phone in bootloader as it is important because running fastboot command.
- Locate the place where you unzipped the rom.
- Select the file "xml" flashfile.xml
- After you have selected the "flashfile.xml" file make sure your phone is connected and that your computer recognizes it.
- Click Start.
If you want to run the fastboot command would these
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img_sparsechunk.0
fastboot flash oem oem.img_sparsechunk.1
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
I hope it will help save many a 'moto g4 "to be a brick.
AnderGuzmanD said:
After so many failed attempts I found the way to get my phone a brick. Thanks to the rom "XT1625_ATHENE_AMAZON_MPJ24.139-64_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip".
The method only require simple:
- Tool ADB: http://www.mediafire.com/file/9m1dopcvpmm6zif/adb-setup-1.4.3.exe
- Fastboot+abds: http://www.mediafire.com/file/48gtedd1hlodozz/Herramientas+ADB.rar
- Drivers motorola: http://www.mediafire.com/file/90xvah7a3p4l2m4/MotorolaDeviceManager_2.4.5.exe
- Rom moto g4 amazon prime: http://www.filefactory.com/file/sks...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
- RSDLite6.2.4.zip: http://rootjunkysdl.com/files/Moto G 4th Gen XT1625/Remove Amazon Bloat Ads/RSDLite6.2.4.zip
After having the essential tools unpack the ROM our "moto g4 amazon".
- Install the drivers phone and ads.
- After you've done this step opens RSD lite.
- Having your phone in bootloader as it is important because running fastboot command.
- Locate the place where you unzipped the rom.
- Select the file "xml" flashfile.xml
- After you have selected the "flashfile.xml" file make sure your phone is connected and that your computer recognizes it.
- Click Start.
If you want to run the fastboot command would these
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img_sparsechunk.0
fastboot flash oem oem.img_sparsechunk.1
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
I hope it will help save many a 'moto g4 "to be a brick.
Click to expand...
Click to collapse
wanted to know if this work for my device
its been bricked and am anew moto user
this the screen appeared
no factory reset or wipe works
herakikoly said:
wanted to know if this work for my device
its been bricked and am anew moto user
this the screen appeared
no factory reset or wipe works
Click to expand...
Click to collapse
this is the screen
AnderGuzmanD said:
After so many failed attempts I found the way to get my phone a brick. Thanks to the rom "XT1625_ATHENE_AMAZON_MPJ24.139-64_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip".
- Rom moto g4 amazon prime: http://www.filefactory.com/file/sks...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I hope it will help save many a 'moto g4 "to be a brick.
Click to expand...
Click to collapse
Do you have another link to that Rom? FileFactory keeps telling me they are overloaded and it won't let me DL. Side note, I've already tried the 139-64_65 file from https://androidfilehost.com/?w=files&flid=72578 and no luck. Still get stuck at Recovery saying "we have attempted a detect to flash." I'm hoping your ROM link is slight different, because the one I found has oem.img as one file, not two sparsechunks. I'm pretty sure I have a real brick.
brockwitting said:
Do you have another link to that Rom? FileFactory keeps telling me they are overloaded and it won't let me DL. Side note, I've already tried the 139-64_65 file from https://androidfilehost.com/?w=files&flid=72578 and no luck. Still get stuck at Recovery saying "we have attempted a detect to flash." I'm hoping your ROM link is slight different, because the one I found has oem.img as one file, not two sparsechunks. I'm pretty sure I have a real brick.
Click to expand...
Click to collapse
good afternoon friend this afternoon I'll upload to another server to his comodida permitame few hours. regards
herakikoly said:
this is the screen
Click to expand...
Click to collapse
if friend exactly there. regards
FYI, this WORKS. Even though I found like 4 different versions of this ROM and none worked, yours did. Thanks a ton!!!!!
brockwitting said:
FYI, this WORKS. Even though I found like 4 different versions of this ROM and none worked, yours did. Thanks a ton!!!!!
Click to expand...
Click to collapse
It was thanks to a forum user who shared a comment on the file name but did not expect that I could repair it even was it sent for review
AnderGuzmanD said:
It was thanks to a forum user who shared a comment on the file name but did not expect that I could repair it even was it sent for review
Click to expand...
Click to collapse
I did not work,
Please your help with the link to download
regards
brockwitting said:
FYI, this WORKS. Even though I found like 4 different versions of this ROM and none worked, yours did. Thanks a ton!!!!!
Click to expand...
Click to collapse
the order was a pleasure friend was like trying until you get the corresponding ROM to return to life the phone
AnderGuzmanD said:
the order was a pleasure friend was like trying until you get the corresponding ROM to return to life the phone
Click to expand...
Click to collapse
AnderGuzmanD,
help me up the rom you downloaded since the original link does not work
regards
frankml01 said:
AnderGuzmanD,
help me up the rom you downloaded since the original link does not work
regards
Click to expand...
Click to collapse
Good evening friend by tomorrow I upload the link to my account because mega still is rising and modify the one corrupted
Come on, man... First off, you posted this in the wrong subforum. Second, you took my instructions without crediting me (my original post). Third, I already created a post about this (here) and gave full credit to my sources.
beano311 said:
Come on, man... First off, you posted this in the wrong subforum. Second, you took my instructions without crediting me (my original post). Third, I already created a post about this (here) and gave full credit to my sources.
Click to expand...
Click to collapse
And MUCH THAT YOU UPSET MY FRIEND! DO NOT WORRY THAT ARE NOT TO HELP TO WIN FAME!
AnderGuzmanD said:
After so many failed attempts I found the way to get my phone a brick. Thanks to the rom "XT1625_ATHENE_AMAZON_MPJ24.139-64_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip".
The method only require simple:
- Tool ADB: http://www.mediafire.com/file/9m1dopcvpmm6zif/adb-setup-1.4.3.exe
- Fastboot+abds: http://www.mediafire.com/file/48gtedd1hlodozz/Herramientas+ADB.rar
- Drivers motorola: http://www.mediafire.com/file/90xvah7a3p4l2m4/MotorolaDeviceManager_2.4.5.exe
- Rom moto g4 amazon prime: "up to mega" in the meantime http://www.filefactory.com/file/sks...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
- RSDLite6.2.4.zip: http://rootjunkysdl.com/files/Moto G 4th Gen XT1625/Remove Amazon Bloat Ads/RSDLite6.2.4.zip
After having the essential tools unpack the ROM our "moto g4 amazon".
- Install the drivers phone and ads.
- After you've done this step opens RSD lite.
- Having your phone in bootloader as it is important because running fastboot command.
- Locate the place where you unzipped the rom.
- Select the file "xml" flashfile.xml
- After you have selected the "flashfile.xml" file make sure your phone is connected and that your computer recognizes it.
- Click Start.
If you want to run the fastboot command would these
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img_sparsechunk.0
fastboot flash oem oem.img_sparsechunk.1
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
I hope it will help save many a 'moto g4 "to be a brick.
Click to expand...
Click to collapse
just needed to know if it works on all moto g4 having the same problem
f u i .. i had aversion named xt 1625 athene mj24 139 retail 64 65
does your post works on returning my moto 4 to life ..
it stuck in recovery after 2 weeks of usage .. hate to be like that ..
and last thing .. want know if it will receive ota update or not .. pleas be patient cause its the first time to deal with that situation
herakikoly said:
just needed to know if it works on all moto g4 having the same problem
f u i .. i had aversion named xt 1625 athene mj24 139 retail 64 65
does your post works on returning my moto 4 to life ..
it stuck in recovery after 2 weeks of usage .. hate to be like that ..
and last thing .. want know if it will receive ota update or not .. pleas be patient cause its the first time to deal with that situation
Click to expand...
Click to collapse
good morning, so far only it has been tested for amazon prime version of greetings
AnderGuzmanD said:
good morning, so far only it has been tested for amazon prime version of greetings
Click to expand...
Click to collapse
so what can i do .. need help
this definitely worked for me! after searching hours for the solution, and was about to give up and have it sent for repair! OMG.. this is a lifesaver...:
victory::victory::good::good::good:
this helped me too, thank you!!!
tread should be moved to q&a and pinned
AnderGuzmanD said:
And MUCH THAT YOU UPSET MY FRIEND! DO NOT WORRY THAT ARE NOT TO HELP TO WIN FAME!
Click to expand...
Click to collapse
Maybe when you grow up you'll realize that it is still good manners to give credit for the work of someone else.
Hi.Just some advice please.After the nougat update the bt didn't work.That wasn't so bad.After recent security update WiFi cannot connect at all to any WiFi network.Ive rebooted and lastly did a factory reset but still no WiFi connectivity.Running stock locked bootloader etc.Also will flashing custom ROM and/kernel solve as a last resort.Thanks in advance
If I were in your position I wouldn't risk unlocking the bootloader to root etc.
There is a chance a custom ROM or kernel would help, though it doesn't seem likely if factory reset did nothing. Just remember you cannot lock the bootloader again to claim a replacement with warranty (unless they're nice) if it is a hardware fault.
Thanks for the reply.Is there a way to flash another regions firmware with the STD recovery.
Yeah, I have one from UK and just flashed back to stock using retail Mexican Nougat then did the OTA and it works fine. If you have the Verizon one I'm pretty sure this won't work. (Also mine has unlocked bootloader but don't think it's needed for this)
This is exactly what I did from a bricked phone, but I can't promise it will work for your situation so it's up to you. I got a strange "error" message after flashing this that looks like the no command error, but after holding power it rebooted and haven't seen it since.
Unzipped Mexican Nougat to the same folder as fastboot.
Using Minimal adb and Fastboot:
fastboot flash partition gpt.bin
fastboot flash motoboot boot.img
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 system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Hope this helps!
So to answer your question directly, not from the STD recovery (unless there's a way through side loading) but fastboot will.
---------- Post added at 03:46 PM ---------- Previous post was at 03:35 PM ----------
Here's where I got the firmware:
https://firmware.center/firmware/Motorola/Moto Z/Stock/XT1650-03/
I used this one:
XT1650-03_GRIFFIN_RETMX_7.0_NPL25.86-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
supacrazyguy42 said:
Yeah, I have one from UK and just flashed back to stock using retail Mexican Nougat then did the OTA and it works fine. If you have the Verizon one I'm pretty sure this won't work. (Also mine has unlocked bootloader but don't think it's needed for this)
This is exactly what I did from a bricked phone, but I can't promise it will work for your situation so it's up to you. I got a strange "error" message after flashing this that looks like the no command error, but after holding power it rebooted and haven't seen it since.
Unzipped Mexican Nougat to the same folder as fastboot.
Using Minimal adb and Fastboot:
fastboot flash partition gpt.bin
fastboot flash motoboot boot.img
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 system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Hope this helps!
So to answer your question directly, not from the STD recovery (unless there's a way through side loading) but fastboot will.
---------- Post added at 03:46 PM ---------- Previous post was at 03:35 PM ----------
Here's where I got the firmware:
https://firmware.center/firmware/Motorola/Moto Z/Stock/XT1650-03/
I used this one:
XT1650-03_GRIFFIN_RETMX_7.0_NPL25.86-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Must those commands be done one at a time.
Thanks for yr help
Yeah should just be able to copy paste one after the other, doesn't take too long only the system chunks take a little while to flash. No problem
supacrazyguy42 said:
Yeah should just be able to copy paste one after the other, doesn't take too long only the system chunks take a little while to flash. No problem
Click to expand...
Click to collapse
It doesnt look like its working.
Downloaded the exact file you did. extracted to minimal adb and fastboot file.
Did the commands one at a time. It looks like its doing the job but when you look at the text in the window its filled with" not found" "failed validation "
"system not found " etc.
The fastboot commands are working . I thought maybe its a driver thing but doubt it.
Do you think I must try another regions file
nizaamh said:
It doesnt look like its working.
Downloaded the exact file you did. extracted to minimal adb and fastboot file.
Did the commands one at a time. It looks like its doing the job but when you look at the text in the window its filled with" not found" "failed validation "
"system not found " etc.
The fastboot commands are working . I thought maybe its a driver thing but doubt it.
Do you think I must try another regions file
Click to expand...
Click to collapse
Ah damn, maybe you will need another region as yours was from Malaysia. Sorry I don't know which would suit your phone, is it dual SIM? Maybe you'd need one compatible with that.
supacrazyguy42 said:
Ah damn, maybe you will need another region as yours was from Malaysia. Sorry I don't know which would suit your phone, is it dual SIM? Maybe you'd need one compatible with that.
Click to expand...
Click to collapse
It is dual sim. I will check through the list you sent.
Get back now now
I did also see someone suggest to use mfastboot with those commands but only minimal adb and fastboot worked for me. Maybe you'd have more luck with that.
https://forum.xda-developers.com/ge...ng-mfastboot-exe-to-unbrick-motorola-t3203518
Maybe this guide will suit your situation better though, I used that the first time I "bricked" my Moto Z (it really didn't like system files to be modified when rooted)
https://forum.xda-developers.com/moto-z/how-to/easy-flash-to-nougat-tutorial-unlocked-t3514245
Sorry if I take a while to reply as I'm on holiday in the countryside at the mo, signals temperamental at best.
---------- Post added at 08:23 PM ---------- Previous post was at 08:04 PM ----------
I hope you don't need bootloader unlock for this since yours didn't wanna do that, did you check that it was XT1650-03? If not maybe this thread is useful too. Hope this can help :good:
https://forum.xda-developers.com/moto-z/help/help-moto-z-xt1650-05-sheridan-stock-t3468227
Thanks so much man.i will go through it and check.Sorry to disturb yr holiday so double thanks.I was thinking maybe i just need to flash a radio or modem file if it's just the WiFi giving a problem.What do u think
nizaamh said:
Thanks so much man.i will go through it and check.Sorry to disturb yr holiday so double thanks.I was thinking maybe i just need to flash a radio or modem file if it's just the WiFi giving a problem.What do u think
Click to expand...
Click to collapse
You're welcome. And no problem it was my choice to help Just recently flashed stock myself so remember the threads, I haven't got a clue if that would work tbh. What state is your phone in now? Booting only to fastboot?
I just don't know which firmware would be compatible with your phone or dual SIM, it looked like only the XT1605-05 Chinese ones were dual. At a guess the updating to Nougat via side loading guide maybe the best bet.
No everything else works fine.Just the blooming WiFi.LTE camera everything works well.When the nougat update came it messed up the Bluetooth.everything else was fine.Then a week ago a security update and this killed the WiFi.I did complain with Lenovo but they didn't even reply
nizaamh said:
No everything else works fine.Just the blooming WiFi.LTE camera everything works well.When the nougat update came it messed up the Bluetooth.everything else was fine.Then a week ago a security update and this killed the WiFi.I did complain with Lenovo but they didn't even reply
Click to expand...
Click to collapse
Ah good I didn't know if attempting the fastboot commands ruined it's system, guess it didn't even try to flash it then. Strange, just to check what does your phone say the SKU is in hardware information? Surely a compatible firmware & mfastboot would work..
I'm not sure why the bootloader wouldn't unlock, maybe worth giving the support a call and ask or see if they'd replace under warranty. Wouldn't wanna see it bricked by flashing the wrong firmware and not have that option available
https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/Moto_Z_Force/thread-id/1380/page/2 Saw someone else with similar issue got a replacement, it doesn't sound like a hardware fault but if factory resets do nothing maybe it's the safest way to go even if it is a pain :/ Up to you though of course
If you can guarantee the wifi password is correct, you can restart it again, at least,i did this
The password is correct.All the phone does is search constantly for WiFi networks.
supacrazyguy42 said:
Ah good I didn't know if attempting the fastboot commands ruined it's system, guess it didn't even try to flash it then. Strange, just to check what does your phone say the SKU is in hardware information? Surely a compatible firmware & mfastboot would work..
I'm not sure why the bootloader wouldn't unlock, maybe worth giving the support a call and ask or see if they'd replace under warranty. Wouldn't wanna see it bricked by flashing the wrong firmware and not have that option available
https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/Moto_Z_Force/thread-id/1380/page/2 Saw someone else with similar issue got a replacement, it doesn't sound like a hardware fault but if factory resets do nothing maybe it's the safest way to go even if it is a pain :/ Up to you though of course
Click to expand...
Click to collapse
It's going to be difficult to replace because i bought the phone in Malaysia and I'm in South Africa.I an going to try and get hold of the Lenovo offices here in SA and see what they say.Thanks for yr help.
nizaamh said:
It's going to be difficult to replace because i bought the phone in Malaysia and I'm in South Africa.I an going to try and get hold of the Lenovo offices here in SA and see what they say.Thanks for yr help.
Click to expand...
Click to collapse
Ahh I see, that does sound difficult. Good luck! I guess if that fails you could try to flash stock with the other methods. You're welcome
supacrazyguy42 said:
Ahh I see, that does sound difficult. Good luck! I guess if that fails you could try to flash stock with the other methods. You're welcome
Click to expand...
Click to collapse
Hi.Just wanted to let u know that it looks sorted.After long and hard and nothing wanted to flash using the tools i tried unlocking the bootloader again as a last resort And it went through.Dont know what happened the last time.Anyways also flashed TWRP .This morning i was gonna load a custom ROM and all of a sudden it connected to my home WiFi. Maybe the bootloader was corrupt or the STD recovery.but now it worked.Thanks for yr help and hope yr holiday was great
nizaamh said:
Hi.Just wanted to let u know that it looks sorted.After long and hard and nothing wanted to flash using the tools i tried unlocking the bootloader again as a last resort And it went through.Dont know what happened the last time.Anyways also flashed TWRP .This morning i was gonna load a custom ROM and all of a sudden it connected to my home WiFi. Maybe the bootloader was corrupt or the STD recovery.but now it worked.Thanks for yr help and hope yr holiday was great
Click to expand...
Click to collapse
Ah brilliant! No idea why unlocking bootloader failed the first time, glad it works now.
Thanks!
Your bootloader must be unlocked.
You can't lock the bootloader, to do this you will need a signed firmware from Motorola (and no one found yet). Instead you can use Magisk to hide the unlocked bootloader, bypass SafetyNet and be able to use Google Pay, for example.
You will not get OTA updates from Motorola even if you somehow lock the bootloader because your phone is registered forever to the "retcn" software update channel, instead of "retail" or "retbr".
Recommended: set your Platform Tools (adb and fastboot) system wide using this guide
https://forum.xda-developers.com/android/software/guide-how-to-set-fastboot-adb-to-wide-t3591240
Tested for updating from Oreo stock without wipe.
Steps for clean flashing or update
- Place the suitable script attached on the extracted ROM folder and flash (these scripts are only for XT1710-08 variant to prevent lost modem signal)
- After all the commands succeeded, wait for a full reboot (because of encryption)
- Flash TWRP
- Flash Magisk normally through TWRP
- Be happy
Firmware (you can use this on other XT1710 variants)
Version: PPS29.133-30 (Android 9.0 Pie)
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Other versions:
https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
TWRP
https://forum.xda-developers.com/z2-play/development/-t3715660
Magisk
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Motorola drivers https://motorola-global-en-aus.custhelp.com/app/answers/prod_detail/a_id/86934/p/154,153
Google SDK Platform Tools https://developer.android.com/studio/releases/platform-tools
Commands for flashing and wipe
PS: the difference from the official `flashfile.xml` commands is that it doesn't contains `fastboot erase modemst1` and `fastboot erase modemst2`
Code:
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 system system.img_sparsechunk.12
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Commands for flashing without wipe (update)
PS: the only difference from the previous one is that it doesn't contains `fastboot erase userdata`
Code:
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 system system.img_sparsechunk.12
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Thanks to
@eqbirvin
@Junior Passos
@HTCDevil
Hello. If I use your script is unzipped the rom with update to August 2018 is the same? They are currently on custom rom Firehound! I would like to go back to the Motorola Blur retail. Do I have to give all the commands from fastboot?
cuciu70 said:
Hello. If I use your script is unzipped the rom with update to August 2018 is the same? They are currently on custom rom Firehound! I would like to go back to the Motorola Blur retail. Do I have to give all the commands from fastboot?
Click to expand...
Click to collapse
Yes! To go back to Motorola stock ROM you must follow this tutorial to make a clean flash, using the flash-wipe script.
my post was wrong, Moderators please delete my post.
Did'nt know i can't delete my own post.
felipecassiors said:
Yes! To go back to Motorola stock ROM you must follow this tutorial to make a clean flash, using the flash-wipe script.
Click to expand...
Click to collapse
the password does not work.
I tried to open the file with 7zip and zip extractor pro. I enter the password!
wrong password.
cuciu70 said:
the password does not work.
I tried to open the file with 7zip and zip extractor pro. I enter the password!
wrong password.
Click to expand...
Click to collapse
Firmware:
https://drive.google.com/open?id=1rcgUvLG5c7l9jH8AzuTg3WPJnORQ6VlY
The password is
Code:
MotorolaFirmwaresLB
I use WinRAR, but 7-Zip should work. Try again please, here is working.
Would it be easy to update the system with the latest patch? I have magisk installed with system from April patch. If so what how would be the procedure?
Followed all the steps and got it working. Thanks so much, the original software on this version of the phone is terrible!
One thing, like a few others, my fingerprint sensor isn't working. Is it as simple as a wipe after install?
pjcons said:
Followed all the steps and got it working. Thanks so much, the original software on this version of the phone is terrible!
One thing, like a few others, my fingerprint sensor isn't working. Is it as simple as a wipe after install?
Click to expand...
Click to collapse
Take a look at this post friend:
https://forum.xda-developers.com/z2...reo-retail-via-fastboot-t3786153/post76486376
Try to flash again but evading this 4 commands.
felipecassiors said:
Take a look at this post friend:
https://forum.xda-developers.com/z2...reo-retail-via-fastboot-t3786153/post76486376
Try to flash again but evading this 4 commands.
Click to expand...
Click to collapse
Yes I took those out when flashed and still no fp sensor. Thanks for sending on though. I read everything b4 flash but still no fp sensor.
But I didn't wipe 1st so might flash again and wipe 1st?
Everything else working 100% :good:
pjcons said:
Yes I took those out when flashed and still no fp sensor. Thanks for sending on though. I read everything b4 flash but still no fp sensor.
But I didn't wipe 1st so might flash again and wipe 1st?
Everything else working 100% :good:
Click to expand...
Click to collapse
If you can, please try wiping in first. If still doesn't work, the procedure to solve this is:
- Flash the original ROM (that ugly ZUI one) to get it working again
- Flash the ROM on this thread, wiping, evading that 4 commands
I can help you to find the ZUI ROM if you need.
felipecassiors said:
If you can, please try wiping in first. If still doesn't work, the procedure to solve this is:
- Flash the original ROM (that ugly ZUI one) to get it working again
- Flash the ROM on this thread, wiping, evading that 4 commands
I can help you to find the ZUI ROM if you need.
Click to expand...
Click to collapse
Cheers mate. If u can send me a link to the very ugly Zui rom just in case would be great.
pjcons said:
Cheers mate. If u can send me a link to the very ugly Zui rom just in case would be great.
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=1322778262903986742
Just make sure your device is XT1710-08
Tested on a XT1710-06 full wipe and it works great, because i wanted to do and update and i goot bootloop.
Just in case someone find this, im from México, I flashed this fastboot rom and installed Magisk to get root, used the Canary build to make it work with my fav games that are Fate go and Pokemon go (spoof) and it works like a charm, thanks.
felipecassiors said:
https://androidfilehost.com/?fid=1322778262903986742
Just make sure your device is XT1710-08
Click to expand...
Click to collapse
Yep, it's an XT1710-08 for sure! Thanks again...
pjcons said:
Yep, it's an XT1710-08 for sure! Thanks again...
Click to expand...
Click to collapse
Friend, use the tutorial of this thread, but instead of that script, use this attached to flash the ZUI stock ROM.
8bitcode said:
Tested on a XT1710-06 full wipe and it works great, because i wanted to do and update and i goot bootloop.
Just in case someone find this, im from México, I flashed this fastboot rom and installed Magisk to get root, used the Canary build to make it work with my fav games that are Fate go and Pokemon go (spoof) and it works like a charm, thanks.
Click to expand...
Click to collapse
Friend, for models other than XT1710-08 (outside China), you can use this script attached. It is more recommended.
Thank you for the feedback!
felipecassiors said:
Friend, for models other than XT1710-08 (outside China), you can use this script attached. It is more recommended.
Thank you for the feedback!
Click to expand...
Click to collapse
Hey I got back to ZUI - the Chinese ROM came up. Fingerprint working. So rebooted into BL and flashed the firmware as per OP. Again, no FP sensor.
I'm gonna try again and wipe after install ZUI, BEFORE flash and wipe Oreo.
[2nd try no better??]
It flashes ok but FP sensor just won't work. Everything else working. When you say "Flash the ROM on this thread, wiping, evading that 4 commands" I use the flash and wipe script and remove the 4 commands (the erase modem seem to have been removed already from the script). Any ideas, I'm so close! Have flashed back and forth a few times tonight. It's fun though! Cheers!
pjcons said:
Hey I got back to ZUI - the Chinese ROM came up. Fingerprint working. So rebooted into BL and flashed the firmware as per OP. Again, no FP sensor.
I'm gonna try again and wipe after install ZUI, BEFORE flash and wipe Oreo.
[2nd try no better??]
It flashes ok but FP sensor just won't work. Everything else working. When you say "Flash the ROM on this thread, wiping, evading that 4 commands" I use the flash and wipe script and remove the 4 commands (the erase modem seem to have been removed already from the script). Any ideas, I'm so close! Have flashed back and forth a few times tonight. It's fun though! Cheers!
Click to expand...
Click to collapse
Mine XT1710-08 fingerprint sensor works without removing the 4 commands, I just remove the 2 erase modem (already removed in the flash scripts). Anyway, try to install the ROM of this thread (https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-oreo-retail-via-fastboot-t3786153) and see if it work for you. Please post here if you have news about it.
Rooting
I did all the steps and completely reinstalled android 8.0 on my moto z2 play, I then got twrp and tried flashing magisk 17.1, I got stuck in a bootloop but managed to flash the whole thing again, which solved the problem. To make sure this doesn't happen again, could you please state the steps for rooting. I cant remember if it was because I did not input the code into the terminal. When I input the code am I supposed to get a response or message, because it just stays bank?
Thank you
Just got the edge+ (2023) from Boost Mobile, but they don't enable the esim usage. Currently running build T1TR33.43-48-21, model #XT2301-1
Does anyone know a way to enable this? Is the Edge+ 2023 rootable yet?
fatmanSings said:
Just got the edge+ (2023) from Boost Mobile, but they don't enable the esim usage. Currently running build T1TR33.43-48-21, model #XT2301-1
Does anyone know a way to enable this? Is the Edge+ 2023 rootable yet?
Click to expand...
Click to collapse
Is the device carrier locked? Haven't heard of anyone else not having esim, my converted Edge 40 Pro has it. If you can unlock the bootloader you can root the device; since you just got it you may have to wait around a week or so in order to actually be able to enable it in developer options but idk what the situation is for the US variant.
gibberishman said:
Is the device carrier locked? Haven't heard of anyone else not having esim, my converted Edge 40 Pro has it. If you can unlock the bootloader you can root the device; since you just got it you may have to wait around a week or so in order to actually be able to enable it in developer options but idk what the situation is for the US variant.
Click to expand...
Click to collapse
Great thanks! I'll wait a week and see. Do you know the firmware version I should be using for the US variant?
fatmanSings said:
Great thanks! I'll wait a week and see. Do you know the firmware version I should be using for the US variant?
Click to expand...
Click to collapse
I don't think the firmware has been uploaded yet. You can use ADB commands to extract the boot.img file and use magisk to patch it then flash patch boot, or wait to see if the full firmware gets uploaded. Unless the Edge+ has a different codename from the other Edge variants ( I don't think that's the case ) I couldn't find the full firmware.
gibberishman said:
I don't think the firmware has been uploaded yet. You can use ADB commands to extract the boot.img file and use magisk to patch it then flash patch boot, or wait to see if the full firmware gets uploaded. Unless the Edge+ has a different codename from the other Edge variants ( I don't think that's the case ) I couldn't find the full firmware.
Click to expand...
Click to collapse
Thanks for your help!
The codename should be rtwo, correct? You think I could flash to the RETAIL version? or should I just wait for the RETUS?
fatmanSings said:
Thanks for your help!
The codename should be rtwo, correct? You think I could flash to the RETAIL version? or should I just wait for the RETUS?
Click to expand...
Click to collapse
The model number in those firmware files don't match the model number for the US variant. I'm assuming the firmware hasn't been dumped yet since the phone has only been out a few weeks in the states.
gibberishman said:
The model number in those firmware files don't match the model number for the US variant. I'm assuming the firmware hasn't been dumped yet since the phone has only been out a few weeks in the states.
Click to expand...
Click to collapse
How long does it usually take for the firmware files to get dumped? A month or so?
fatmanSings said:
How long does it usually take for the firmware files to get dumped? A month or so?
Click to expand...
Click to collapse
Maybe a couple weeks if that. It just depends. Not really sure how they dump the firmware and if they need the physical device or not.
gibberishman said:
Maybe a couple weeks if that. It just depends. Not really sure how they dump the firmware and if they need the physical device or not.
Click to expand...
Click to collapse
I unlocked the bootloader and flashed stock firmware, but the software channel is still 'dish wireless' and esim settings are still hidden. Do you know of any other possible solutions to enable e-sim capabilities?
I tried to change the oem config carrier to retus and that didn't work either
fatmanSings said:
I unlocked the bootloader and flashed stock firmware, but the software channel is still 'dish wireless' and esim settings are still hidden. Do you know of any other possible solutions to enable e-sim capabilities?
I tried to change the oem config carrier to retus and that didn't work either
Click to expand...
Click to collapse
You did "fastboot oem config carrier retus" ?
gibberishman said:
You did "fastboot oem config carrier retus" ?
Click to expand...
Click to collapse
yes, it changed the value, but there are no changes to the software channel. Is there a way to change the ro.carrier value?
Do you think I can flash to the RETEU Edge 40 Pro firmware?
fatmanSings said:
yes, it changed the value, but there are no changes to the software channel. Is there a way to change the ro.carrier value?
Do you think I can flash to the RETEU Edge 40 Pro firmware?
Click to expand...
Click to collapse
You may be able to root the device and change the value. Don't thing there's a file you can flash to override the carrier. I wouldn't recommend flashing the EU firmware. The hardware is slightly different, don't know if it would affect anything.
Any updates? In the same situation. Tried flashing retail US firmware and FASTBOOT oem config carrier but it didn’t seem to work.
DeSlaye said:
Any updates? In the same situation. Tried flashing retail US firmware and FASTBOOT oem config carrier but it didn’t seem to work.
Click to expand...
Click to collapse
I tried flashing with the RSA Motorola tool and the MotoFlashPro, but neither worked with the US firmware. I haven't tried anything else yet, since I'm scared I'm going to mess something up. But if you would like to try, you could try rooting and patching some of the files, or try flashing the RETAIL firmware, although it's designed for xt2301-4 and not xt2301-1.
Flashing the RETAIL firmware may work since others have been able to convert from other regions as well. But as @gibberishman mentioned the hardware is slightly different and there have been reports of nfc not working, etc.
fatmanSings said:
I tried flashing with the RSA Motorola tool and the MotoFlashPro, but neither worked with the US firmware. I haven't tried anything else yet, since I'm scared I'm going to mess something up. But if you would like to try, you could try rooting and patching some of the files, or try flashing the RETAIL firmware, although it's designed for xt2301-4 and not xt2301-1.
Flashing the RETAIL firmware may work since others have been able to convert from other regions as well. But as @gibberishman mentioned the hardware is slightly different and there have been reports of nfc not working, etc.
Click to expand...
Click to collapse
I downloaded the RETAIL firmware and attempted to 'spoof' the Boost software by removing the MD5 checks in the flash script but no luck. Half the items didn't flash due to protected partitions so unless I have an unlocked bootloader, it doesn't flash. What's odd is these are legitimate firmware files straight from Motorola. I'm guessing there is a different signature for these from the standard unlocked variant vs Boost/Dish.
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash init_boot init_boot.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot erase apdp
fastboot erase apdpb
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
pause
fastboot reboot
exit
EDIT: Flashing the RETAIL on locked BL caused my device to soft-brick, I had to restore via Motorola Rescue and Smart assistance software which worked like a charm. If open BL, you may be able to change the software/carrier channel then attempt to restore through Motorola tool although YMMV.
Ascertion said:
I downloaded the RETAIL firmware and attempted to 'spoof' the Boost software by removing the MD5 checks in the flash script but no luck. Half the items didn't flash due to protected partitions so unless I have an unlocked bootloader, it doesn't flash. What's odd is these are legitimate firmware files straight from Motorola. I'm guessing there is a different signature for these from the standard unlocked variant vs Boost/Dish.
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash init_boot init_boot.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot erase apdp
fastboot erase apdpb
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
pause
fastboot reboot
exit
EDIT: Flashing the RETAIL on locked BL caused my device to soft-brick, I had to restore via Motorola Rescue and Smart assistance software which worked like a charm. If open BL, you may be able to change the software/carrier channel then attempt to restore through Motorola tool although YMMV.
Click to expand...
Click to collapse
Were you able to unlock the bootloader? Usually you have to unlock the bootloader before flashing.
fatmanSings said:
Were you able to unlock the bootloader? Usually you have to unlock the bootloader before flashing.
Click to expand...
Click to collapse
No, when I go to the unlock site it just gives me a 404 error page after submitting my unlock token. I gave up and decided to just use the Boost firmware. The device is sim-unlocked and supports AT&T/T-Mobile.