My questions are at bottom.
Context:
I recently tried to go back to my stock from lineageos. I successfully did it through this youtube video but I've run into a couple of problems.
Youtube Video Titled: MOTO G5 PLUS STOCK ROM FLASHING | UNBRICK/UNROOT MOTO G5 PLUS
(I'm not allowed to post links)
I used firmware NPN25.137-35
after I flashed twrp, no-verity-check and magisk v14
After mistakenly tried to apply an OTA update(I know better now) my phone always boots into recovery. I discovered this when the updated tried to restart to install. I have to boot to bootloader and press the power button when the selection is on "start". I'm not sure if the OTA had anything to do with that.
The fastboot commands I used where this to install the stock ROM
Code:
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
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 oem fb_mode_clear
fastboot reboot
Questions:
1. If I want to download the stock image directly from the "firmware.center" which one do I choose and how do I know? There are 9 of them..
2. Do I ever need to unlock my bootloader again or is that a one time thing?
3. Do those fastboot commands and the stock image bring my moto g5 plus back to the way it was completely when I unpackaged it (minus unlocked bootloader)?
4. Can I run those fastboot commands without unzipping the stock *.xml.zip?
5. Where did these commands come from? Is it common knowledge that they work? Or is a fastboot sequence provided by motorola?
6. Does "just" attempting an OTA update mess stuff up on a rooted android?
Related
Hello,
Last night I tried to root my new moto x play
the root failed and it went to bootloader, where after much looking around I found a website through here that showed me how to flash, used to correct latest firmware.
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 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 reboot
my current error message is failed to validate system image and this shows when I try to access recovery as well.
Any advice would be greatly appreciated.
Model XT1562
Edit, I have motorola device manager installed, both rsd lite and verizon wireless softwear upgrade cannot detect phone.
If you were flashing the most up to date firmware then you definitely missed a couple of sparsechunks. Use fastboot to flash everything (check flashfile.xml for proper fastboot commands)
minimale_ldz said:
If you were flashing the most up to date firmware then you definitely missed a couple of sparsechunks. Use fastboot to flash everything (check flashfile.xml for proper fastboot commands)
Click to expand...
Click to collapse
Cheers for the help mate.
all sorted just missed number 8.
Hi guys,
I got a new Moto G 4th gen Xt1621 and tried to root it but after that it wouldn't boot anymore, I tried flashing back the firmware (which I found on a google search on a gammerson website) but now it won't boot, it shows the screen saying that the bootloader is unlocked so the warranty is void and the message that it will boot up in 5 seconds, and it gets there forever.
Is there any way I can get back the original firmware? Or a custom one, or really anything to make it usable?
Thanks a lot,
XNP
xnpsdslf said:
Hi guys,
I got a new Moto G 4th gen Xt1621 and tried to root it but after that it wouldn't boot anymore, I tried flashing back the firmware (which I found on a google search on a gammerson website) but now it won't boot, it shows the screen saying that the bootloader is unlocked so the warranty is void and the message that it will boot up in 5 seconds, and it gets there forever.
Is there any way I can get back the original firmware? Or a custom one, or really anything to make it usable?
Thanks a lot,
XNP
Click to expand...
Click to collapse
Hi guys,
I manage to fix my problem with the firmware XT1621_ATHENE-IUSMX_MPJ24.139-48_cid50_subsidy-IUSMXLA_regulatory-DEFAULT_CFC_v2.xml
And this procedure:
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
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 oem fb_mode_clear
fastboot reboot
I got it from the stechguide page, but I can't post the link here unfortunately.
Thanks,
XNP
it is a exclusive xt1621 problem?
Help needed. NEWBIE alert.
Last week I unlocked my UK G4+ and failed to install SuperU and ended up with a brick. Got it back working using a script to reflash to stock and it was all working fine.
So today tried to install a custom rom and again it killed the phone.
Again, wiped the phone, reflashed as before to stock, now stuck on the Welcome Screen. No touch screen to progress.
When I press the power button, the Power Off prompt comes on and I can power off. So the tough screen is working for that.
I am getting these fastboot errors but carried on anyway.
GPT.BIN
(bootloader) Preflash validation failed
FAILED (remote failure).
How can I get the UK phone back to Stock?
What's your XT model? (in the battery it says the model)
XT1642
I just want it back to original stock and locked now.
Thanks
Try this YouTube video. Make sure you get the correct firmware. This worked for me with no issues. Also make sure you have the correct drivers.
thanks, i'll take a look
Stock ROM: http://www.filefactory.com/file/1pq...24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml.zip
Commands:
Code:
fastboot oem lock begin
fastboot oem lock begin
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
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 oem lock
I believe this happened after the various modifications I made, I am currently in stock 7.0, whenever I switch off the phone and start again it sends me directly to the Fastboot screen, as if I was calling it with Power + Volume Down, I would like To know what I can do to solve this
lukasth said:
I believe this happened after the various modifications I made, I am currently in stock 7.0, whenever I switch off the phone and start again it sends me directly to the Fastboot screen, as if I was calling it with Power + Volume Down, I would like To know what I can do to solve this
Click to expand...
Click to collapse
Usually happens when you don't give the clear fb mode command while flashing a stock ROM via fastboot.
I dunno if you need to reflash, but you need to give that command to your phone so it doesn't boot to FB mode.
Sent from my Moto G (4) using Tapatalk
lukasth said:
I believe this happened after the various modifications I made, I am currently in stock 7.0, whenever I switch off the phone and start again it sends me directly to the Fastboot screen, as if I was calling it with Power + Volume Down, I would like To know what I can do to solve this
Click to expand...
Click to collapse
This is maybe due to corrupted rom. Do a factory reset. If you still face any problems install rom via fastboot
1chrome said:
Usually happens when you don't give the clear fb mode command while flashing a stock ROM via fastboot.
I dunno if you need to reflash, but you need to give that command to your phone so it doesn't boot to FB mode.
Sent from my Moto G (4) using Tapatalk
Click to expand...
Click to collapse
Would you help me? First I installed the MPJ24.139-63 (6.0.1) build and used the following command line:
Fastboot flash partition gpt.bin
Fastboot flash bootloader bootloader.img
Fastboot flash logo logobin
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
Fastboot flash dsp adspso.bin
Fastboot flash oem oem.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 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 reboot
What command line should I add to resolve this problem? I will reinstall that same build and then put the Nougat build.
lukasth said:
What command line should I add to resolve this problem? I will reinstall that same build and then put the Nougat build.
Click to expand...
Click to collapse
FB_mode_clear is missing,
Compare here, https://forum.xda-developers.com/showpost.php?p=67031808&postcount=4
fastboot oem fb_mode_set
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
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 oem fb_mode_clear
This isn't my script - it's from the run.bat file elsewhere on XDA, note the fastboot oem fb_mode_clear at the bottom. I'll try to find the source to that run.bat and link it, I've used that to reflash MM 139-63/64 and use that same system to upgrade to Nougat with no problems.
EDIT: Credit to Techburner and their guide here: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-downgrade-to-marshmallow-nougat-t3515961
lukasth said:
I believe this happened after the various modifications I made, I am currently in stock 7.0, whenever I switch off the phone and start again it sends me directly to the Fastboot screen, as if I was calling it with Power + Volume Down, I would like To know what I can do to solve this
Click to expand...
Click to collapse
Try
Fastboot oem fb_mode_set
Fastboot oem fb_mode_clear
Fastboot oem fb_mode_set and Fastboot oem fb_mode_clear they worked for me, thanks a lot.
So I wanted to revert back from lineage OS 14.1 to stock and do all the stock ROM OTA updates to oreo. After flashing retail 137-35 it would not properly update boot.img during that process and would not relock bootloader.
It booted fine though and stock ROM immediately OTA updated each of the following:
137-35-5
137-83
137-93
137-93-4
137-93-8
137-93-10
137-93-14
137-93-18
I'm getting close to the oreo update patch w/ an open bootloader. Is there a concern here? I know the oreo updates have been causing problems for some. Do I need to stop the updates?
badtlc said:
So I wanted to revert back from lineage OS 14.1 to stock and do all the stock ROM OTA updates to oreo. After flashing retail 137-35 it would not properly update boot.img during that process and would not relock bootloader.
It booted fine though and stock ROM immediately OTA updated each of the following:
137-35-5
137-83
137-93
137-93-4
137-93-8
137-93-10
137-93-14
137-93-18
I'm getting close to the oreo update patch w/ an open bootloader. Is there a concern here? I know the oreo updates have been causing problems for some. Do I need to stop the updates?
Click to expand...
Click to collapse
It's pretty normal to get OTA updates with an unlocked bootloader, Motorola itself gives you the unlock key. It's a common misconception that the BL status has anything to do with OTA.
Only rooting, twrp and any change in system or vendor prevents the update process.
Just being on untouched stock firmware incl stock recovery and boot.img is enough.
You can install the updates if that's the case for you.
Wolfcity said:
It's pretty normal to get OTA updates with an unlocked bootloader, Motorola itself gives you the unlock key. It's a common misconception that the BL status has anything to do with OTA.
Only rooting, twrp and any change in system or vendor prevents the update process.
Just being on untouched stock firmware incl stock recovery and boot.img is enough.
You can install the updates if that's the case for you.
Click to expand...
Click to collapse
I dont think the stock boot.img every wrote properly and I cannot seem to get the bootloader locked no matter what I do. Is there a way to verify everything really is stock?
badtlc said:
I dont think the stock boot.img every wrote properly and I cannot seem to get the bootloader locked no matter what I do. Is there a way to verify everything really is stock?
Click to expand...
Click to collapse
Try locking again with the updated firmware. If the boot.img failed to write then it would have shown error in cmd.
badtlc said:
I dont think the stock boot.img every wrote properly and I cannot seem to get the bootloader locked no matter what I do. Is there a way to verify everything really is stock?
Click to expand...
Click to collapse
Agree, if there was no error in the fastboot log it was ok. If you want to relock the bootloader (there's no good reason for it unless you want to sell the device) here are the locking and flashing commands. You need the exact same firmware you're on for locking!
For Oreo the whole sets of commands are for
Locking:
-----------------
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.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 boot boot.img
fastboot oem lock
-------------------
Flashing:
-------------------
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 erase modemst1
fastboot erase modemst2
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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
-----------------------------------
The same commands for Nougat:
Flashing:
-----------------------------------
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
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 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 oem fb_mode_clear
--------------------------
Locking:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.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 boot boot.img
fastboot oem lock
I will try those. They look very similar to what I tried already. I always got a fastboot write error for the boot.img and of course the can't OEM lock error.
If the boot.img didn't write properly, would I even be able to boot into the stock ROM? The fact it is working just has me paranoid I'm missing something and about to brick my phone by mistake.
badtlc said:
If the boot.img didn't write properly, would I even be able to boot into the stock ROM?
Click to expand...
Click to collapse
No