I have a rooted G7 that I rooted (unofficial twrp and then Magisk) when it was still at the original January android version. How do I get its android version updated? I've read others
https://forum.xda-developers.com/moto-g7/help/loader-file-to-unbrick-moto-g7-t3938342/page4
who bricked their phones trying to do this.
Is there a way to safely get the ota updates?
How?
maybeme2 said:
I have a rooted G7 that I rooted (unofficial twrp and then Magisk) when it was still at the original January android version. How do I get its android version updated? I've read others
https://forum.xda-developers.com/moto-g7/help/loader-file-to-unbrick-moto-g7-t3938342/page4
who bricked their phones trying to do this.
Is there a way to safely get the ota updates?
How?
Click to expand...
Click to collapse
OTA on a rooted device? No. Do the update yourself and save the headache:
1. Download the latest firmware here.
2. Install adb & fastboot
windows:
download
linux:
Code:
sudo apt install adb fastboot -y
if you have Debian/Ubuntu family of OS
download here if you don't
3. Flash with these commands:
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 erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash dtbo dtbo.img
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 system system.img_sparsechunk.9
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 vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
4. Install TWRP and reroot
Thank you very, very much.
Will I lose my installed apps including Titanium Backup to restore app data?
maybeme2 said:
Thank you very, very much.
Will I lose my installed apps including Titanium Backup to restore app data?
Click to expand...
Click to collapse
If you skip the command:
Code:
fastboot erase userdata
then all your data stays. Do all the other commands.
ptn107 said:
1. Download the latest firmware here.
Click to expand...
Click to collapse
May I ask where this firmware comes from? Is it authentic Moto firmware or extracted and possibly modified?
Thanks again.
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.
I flashed AICP last week then i got back to Stock rom but now everytime i restart or switch on my phone gets into bootloader mode even when i try to install ota i get into bootloader mode then i have to get onto recovery mode to install ota.please help
Volume down button stuck?
I've seen this come up before... Did read through q&a?
lafester said:
I've seen this come up before... Did read through q&a?
Click to expand...
Click to collapse
Yeah but i can't find any give me the link.
You are probably still in oem flash mode, after you flashed stock ROM did you enter 'fastboot oem fb_mode_clear'? If you didn't, everytime you restart it will return to the bootloader.
acejavelin said:
You are probably still in oem flash mode, after you flashed stock ROM did you enter 'fastboot oem fb_mode_clear'? If you didn't, everytime you restart it will return to the bootloader.
Click to expand...
Click to collapse
I followed the commands given in forum for installing stock rom the final command was 'fastboot reboot' it didn't have the command you mentioned.
[email protected] said:
I followed the commands given in forum for installing stock rom the final command was 'fastboot reboot' it didn't have the command you mentioned.
Click to expand...
Click to collapse
It should be the command right before the reboot. I don't know what instructions your following, but I've flashed several Motos.
Sent from my XT1575 using Tapatalk
acejavelin said:
It should be the command right before the reboot. I don't know what instructions your following, but I've flashed several Motos.
Click to expand...
Click to collapse
CODE]adb reboot bootloader
fastboot flash partition gpt.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot[/CODE]
I used these commands to flash the rom does adding the command you mentioned before 'fastboot reboot' solve the problem. By the way thanks for replying.
[email protected] said:
CODE]adb reboot bootloader
fastboot flash partition gpt.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot[/CODE]
I used these commands to flash the rom does adding the command you mentioned before 'fastboot reboot' solve the problem. By the way thanks for replying.
Click to expand...
Click to collapse
Hmmm... this is the procedure I have, granted it's from the Moto G3, but both the X Pure/Style and G 2015 are Moto 3rd Gen devices...
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 system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
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
acejavelin said:
Hmmm... this is the procedure I have, granted it's from the Moto G3, but both the X Pure/Style and G 2015 are Moto 3rd Gen devices...
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 system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
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
Click to expand...
Click to collapse
Thanks will try this commands
[email protected] said:
Thanks will try this commands
Click to expand...
Click to collapse
Look at the servicefile.xml in the image, it should contain all the commands, it gives the exact procedure, you just have to interpret it correctly.
I installed and rooted with TWRP in June. I thought it just installs updates via bootloader, but it needs stock recovery. So, I'm stuck with a update waiting, and it's required to update to Naugat. I tried installing Naugat from a zip, but I kept getting errors. Help?
http://www.filefactory.com/file/x59...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
This is the link ,
Install commands are
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin mfastboot 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
Extract the file where you have twrp copy. So you dont have to install any driver.
Then run command prompt type "fastboot devices"
It will show som3 id if you device should be detected. Befor doing this you must be in bootloader state
Akash Sharma123 said:
http://www.filefactory.com/file/x59...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
This is the link ,
Install commands are
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin mfastboot 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
Extract the file where you have twrp copy. So you dont have to install any driver.
Then run command prompt type "fastboot devices"
It will show som3 id if you device should be detected. Befor doing this you must be in bootloader state
Click to expand...
Click to collapse
I keep getting errors where it cant find it.
lometon said:
I keep getting errors where it cant find it.
Click to expand...
Click to collapse
Im stupid. I was putting it in the wrong folder... I had to put it in Program Files. *facepalm*
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
Hi, I need help since 1 week ago I unlocked my bootloader and install HavocOS, but in the end I did not like it and decided to go back to the Stock ROM and block my Bootloader (All for ADB) but when I try, the Bootloader does not block, before if it worked for me but in this last situation, no, does anyone know what it could be? The Stock version that I try to install is 8.1.0, February patch. I want to block my Bootloader to be calmer. Thank you.
JuanM28 said:
Hi, I need help since 1 week ago I unlocked my bootloader and install HavocOS, but in the end I did not like it and decided to go back to the Stock ROM and block my Bootloader (All for ADB) but when I try, the Bootloader does not block, before if it worked for me but in this last situation, no, does anyone know what it could be? The Stock version that I try to install is 8.1.0, February patch. I want to block my Bootloader to be calmer. Thank you.
Click to expand...
Click to collapse
Why? What's the advantage of a locked bootloader?
If you want to lock it:
Commands to flash stock (Oreo!) ROM:
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
Commands to relock the bootloader:
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
Sent from my Moto G5 Plus using XDA Labs