Related
i have an unlocked rooted but otherwise stock G4P and it has an OTA but fails to install. Is there a full ROM I can apply which won't wipe? Or some other way which is not involving a full wipe?
nigelhealy said:
i have an unlocked rooted but otherwise stock G4P and it has an OTA but fails to install. Is there a full ROM I can apply which won't wipe? Or some other way which is not involving a full wipe?
Click to expand...
Click to collapse
I tried, failed, and eventually gave up. I haven't had the motivation to do a full wipe/flash, but I tried everything else I could think of before giving up.
hp420 said:
I tried, failed, and eventually gave up. I haven't had the motivation to do a full wipe/flash, but I tried everything else I could think of before giving up.
Click to expand...
Click to collapse
Did you tryied reinstall the full stock rom & recovery (through Fastboot) without wipe?
rafaelrgi said:
Did you tryied reinstall the full stock rom & recovery (through Fastboot) without wipe?
Click to expand...
Click to collapse
I had a twrp backup of my system partition, which I restored, then fastboot flashed the stock kernel, and wiped caches. Safetynet passed, but the ota would not flash. It said there was an unexpected change in the system, or something to that affect.
I'm not aware of any true, untouched flashable rom zip available. I suppose it wouldn't take long to make one, I just didn't have one available to me.
hp420 said:
I had a twrp backup of my system partition, which I restored, then fastboot flashed the stock kernel, and wiped caches. Safetynet passed, but the ota would not flash. It said there was an unexpected change in the system, or something to that affect.
I'm not aware of any true, untouched flashable rom zip available. I suppose it wouldn't take long to make one, I just didn't have one available to me.
Click to expand...
Click to collapse
To install the OTA update the stock recovery is required, and Twrp is a custom recovery.... after restore the backup you should reinstall the stock recovery before apply the OTA.
rafaelrgi said:
To install the OTA update the stock recovery is required, and Twrp is a custom recovery.... after restore the backup you should reinstall the stock recovery before apply the OTA.
Click to expand...
Click to collapse
sorry, didn't see you were asking about fastboot. no, I didn't flash the factory image. I didn't want to go that far and didn't really care enough to do a full wipe
Have you tried Magisk? Could potentially work
hp420 said:
I had a twrp backup of my system partition, which I restored, then fastboot flashed the stock kernel, and wiped caches. Safetynet passed, but the ota would not flash. It said there was an unexpected change in the system, or something to that affect.
I'm not aware of any true, untouched flashable rom zip available. I suppose it wouldn't take long to make one, I just didn't have one available to me.
Click to expand...
Click to collapse
A TWRP backup restore doesn't fix the issue. You have to reflash SYSTEM , BOOT(if modified), RECOVERY(if modified), and OEM through fastboot. That is a "block flash," instead of TWRP, which is "file based restore."
apply OTA to rooted phone
Could someone please give me this zip ota moto g4 play I need this file since I thank you.
VR25 said:
A TWRP backup restore doesn't fix the issue. You have to reflash SYSTEM , BOOT(if modified), RECOVERY(if modified), and OEM through fastboot. That is a "block flash," instead of TWRP, which is "file based restore."
Click to expand...
Click to collapse
What about other partitions :
gpt, bootloader, adspso, modem
Must they be restored ?
Just after OTA, is it possible to make a raw image backup with TWRP in R/O mode ?
hamelg said:
What about other partitions :
gpt, bootloader, adspso, modem
Must they be restored ?
Just after OTA, is it possible to make a raw image backup with TWRP in R/O mode ?
Click to expand...
Click to collapse
You only need to restore SYSTEM, OEM, BOOT AND RECOVERY images. That's all you'll ever need. NEVER touch other partitions, unless you are upgrading.
To make RAW image backups of SYSTEM and OEM partitions, use terminal in TWRP
Or "adb shell" from your computer (running as root)
adb shell
ls -al /dev/block/platform/soc/7824900.sdhci/by-name
This command will give you the names of the SYSTEM and OEM partitions of your device, Moto G4 Plus. For example, for Moto Z Play (my device), they are mmcblk0p53 and mmcblk0p51 respectively.
So, the commands would be (again, that's an example for MOTO Z PLAY):
Backup
dd if=/dev/block/mmcblk0p53 of=/sdcard/system.img
dd if=/dev/block/mmcblk0p51 of=/sdcard/oem.img
Restore
dd if=/sdcard/system.img of=/dev/block/mmcblk0p53
dd if=/sdcard/oem.img of=/dev/block/mmcblk0p51
Thanks much VR25.
With your help, I have successfully applied the latest OTA
hamelg said:
Thanks much VR25.
With your help, I have successfully applied the latest OTA
Click to expand...
Click to collapse
Confused. The VR25 guidance is when you had taken a full backup when stock, how to restore back to stock to then apply the OTA. You are describing how to apply the OTA on a rooted device without a pre-rooted backup?
You don't need backups to apply the latest OTA.
Get the stock corresponding to your device.
flash LOGO, SYSTEM, OEM, BOOT AND RECOVERY images.
Apply November OTA
Apply February OTA
I did that without wiping my data.
If you want to avoid reset to stock & apply all OTAs, you must have a binary backup of system partition, not a file based backup (see comment #8).
I asked about this issue here :
https://forum.xda-developers.com/showpost.php?p=72029402&postcount=55
hamelg said:
You don't need backups to apply the latest OTA.
Get the stock corresponding to your device.
flash LOGO, SYSTEM, OEM, BOOT AND RECOVERY images.
Apply November OTA
Apply February OTA
I did that without wiping my data.
If you want to avoid reset to stock & apply all OTAs, you must have a binary backup of system partition, not a file based backup (see comment #8).
I asked about this issue here :
https://forum.xda-developers.com/showpost.php?p=72029402&postcount=55
Click to expand...
Click to collapse
Where is the stock for my device
Where is the OTA for my device
My device is the USA unlocked G4P XT1607
nigelhealy said:
Where is the stock for my device
Where is the OTA for my device
My device is the USA unlocked G4P XT1607
Click to expand...
Click to collapse
Exactly this question, but then the XT1602. Flashed the stock parts, but no message of an OTA and they are nowhere to be found. Or does anyone have latest stock version full ROM?
TheEvilVirus said:
Exactly this question, but then the XT1602. Flashed the stock parts, but no message of an OTA and they are nowhere to be found. Or does anyone have latest stock version full ROM?
Click to expand...
Click to collapse
Yeah, others were just saying too high a level to not actually helpful. As I did this last week I'll tell you now is as step by step as I can to actually try to be helpful.
Firstly you need to know you will wipe data, there's no avoiding it, that I could find so backup everything, that can be a mix of TWRP backup of data to SDCARD external, USB OTG, or Titanium backup to online / SD / OTG. In my case I prefer to simply install everything and configure everything from scratch.
Follow this guide to return to stock.
In my case I'm on Ubuntu Linux desktop, fastboot got a "no permissions" type message so I had to sudo in front.
The stock for your device, well look at your device Status page now before you start, Settings -> About Phone -> it says Software Channel "retus" so when I go to the list of ROMs in the above guide go to mirrors.lolinet.com - firmware - moto - harpia - official - then I went to Retus, you'd go to a different one probably.
Note these are old stock ROMs I think from September so there have been one or two updates since then.
Follow the step by step guide, basically lots of fastboot commands.
The step where it says fastboot oem lock it bawks and say fastboot oem lock begin and that will do another wipe, so given a later fastboot oem unlock would do a 3rd wipe I didn't do the oem lock, I left mine unlocked and that worked fine.
Let it boot, setup, you will then be in an old stock ROM, then if it doesn't offer to do an update, go into Settings, System Updates, and trigger it to look. It will then download and apply a stock OTA ontop of the stock ROM. In my case it was 1 OTA, 1 update, then that that complete. You then are on stock current ROMs.
Then root and whatever you want.
But note, to get to the impending N OTA, you'll probably have to right back to the top here because your rooted Moto G4 Play will likely refuse the future OTA as the system is modified, so you'd have to repeat, return to an old stock ROM and then let it go through the 1 or 2 or 3 OTAs to get to that future release.
Hence you'd be doing the return to stock twice.
If the mirrors could be updated to newer stocks it would bypass the OTA. My other phone - the OnePlus3T they offer mirrors of full ROMs, they are far easier to use because if you are rooted you download the full ROM not just the delta incremental of the change of the OTA, and then you can flash in recovery the full ROM and it ignores the system state, and no wiping of data. The fact the mirror site is out of date is causing the need to wipe so the OTAs work on an unmodified system.
Fortunately I have multiple phones so I can use another for the few hours this all takes.
works great, I just flash it and without wiping data
hamelg said:
You don't need backups to apply the latest OTA.
Get the stock corresponding to your device.
flash LOGO, SYSTEM, OEM, BOOT AND RECOVERY images.
Apply November OTA
Apply February OTA
I did that without wiping my data.
If you want to avoid reset to stock & apply all OTAs, you must have a binary backup of system partition, not a file based backup (see comment #8).
I asked about this issue here :
https://forum.xda-developers.com/showpost.php?p=72029402&postcount=55
Click to expand...
Click to collapse
works great and finally my phone can upgrade the OTA updates:laugh::good:
VR25 said:
To make RAW image backups of SYSTEM and OEM partitions, use terminal in TWRP
Or "adb shell" from your computer (running as root)
...
Restore
dd if=/sdcard/system.img of=/dev/block/mmcblk0p53
dd if=/sdcard/oem.img of=/dev/block/mmcblk0p51
Click to expand...
Click to collapse
Here is time to apply the may OTA MPIS24.241-15.3-21.
I restored the vanilla system.img MPIS24.241-15.3-16 with dd, but it didn't work. The OTA failed with the error "system partition has unexpected content" because the sha1sum was incorrect.
Here is the solution :
Before restoring with dd, you must check "Mount System partition read only" is enable in the MOUNT menu of TWRP.
With TWRP 3.1, you need no more to use dd. Now, the feature "system image backup" is available
Received security update notification from Moto, and installed.
Moto G4+ XT1644 (4GB/64GB)
TWRP 3110, ElementalX kernel, Magisk rooted, custom logo
bootloader unlocked
Latest TWRP backup on 08/31/17
After install:
Phone now always reboots to TWRP
tried wiping data, cache, Dalvik but no difference
tried restore backup but still reboots to TWRP
Can only shut phone off via power button
Any advice to get my phone back to normal will be greatly appreciated. Thanks.
mel2000 said:
Received security update notification from Moto, and installed.
Moto G4+ XT1644 (4GB/64GB)
TWRP 3110, ElementalX kernel, Magisk rooted, custom logo
bootloader unlocked
Latest TWRP backup on 08/31/17
After install:
Phone now always reboots to TWRP
tried wiping data, cache, Dalvik but no difference
tried restore backup but still reboots to TWRP
Can only shut phone off via power button
Any advice to get my phone back to normal will be greatly appreciated. Thanks.
Click to expand...
Click to collapse
You messed up your rom by installing official update on custom kernel. Can you boot from twrp to system? What happens if you do that? Which stock rom you have exactly? Otherwise you can flash stock rom with fastboot, but never downgrade!
strongst said:
Can you boot from twrp to system? What happens if you do that? Which stock rom you have exactly? Otherwise you can flash stock rom with fastboot, but never downgrade!
Click to expand...
Click to collapse
Thank you for your reply, strongst. When I press the Reboot->System buttons in TWRP, the phone boots back to TWRP recovery.
Here are the stats I recorded before things went sideways:
Original stock firmware Build Number - NPJS25.93-14-4
Original OS version - 7.0
Original Kernel - 3.10.84-gb9596e1 [email protected] #1 Fri Mar 3 02:04:02 CST 2017
Original Baseband version - M8952_70030.25.03.62RATHENE_RETUSA_CUST
Updated Kernel - 3.10.84-ElementalX-G4-1.04 [email protected] #1 Sat Mar 11 14:16:55 EST 2017
Note: I found NPJS25.93-14-4 firmware at
https://www.getdroidtips.com/npjs25-93-14-4-march-security-moto-g4-plus
but it's titled as "March 2017 security patch" OTA update. I'm not sure if that is full replacement firmware or not.
If necessary, should I simply flash NPJS25.93-14 (full firmware) via fastboot and allow Moto to finish the updates via OTA?
mel2000 said:
Thank you for your reply, strongst. When I press the Reboot->System buttons in TWRP, the phone boots back to TWRP recovery.
Here are the stats I recorded before things went sideways:
Original stock firmware Build Number - NPJS25.93-14-4
Original OS version - 7.0
Original Kernel - 3.10.84-gb9596e1 [email protected] #1 Fri Mar 3 02:04:02 CST 2017
Original Baseband version - M8952_70030.25.03.62RATHENE_RETUSA_CUST
Updated Kernel - 3.10.84-ElementalX-G4-1.04 [email protected] #1 Sat Mar 11 14:16:55 EST 2017
Note: I found NPJS25.93-14-4 firmware at
https://www.getdroidtips.com/npjs25-93-14-4-march-security-moto-g4-plus
but it's titled as "March 2017 security patch" OTA update. I'm not sure if that is full replacement firmware or not.
If necessary, should I simply flash NPJS25.93-14 (full firmware) via fastboot and allow Moto to finish the updates via OTA?
Click to expand...
Click to collapse
You can also flash the latest available for your device with June security patch. After that you can root again with ex kernel if you want https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Make sure to mount storage within twrp first and save your internal memory before flashing stock rom!
In future, if that happens, you could try booting to the bootloader, then on the bootloader screen, press 'Start' and try to get your device to boot normally. Credit to: https://forum.xda-developers.com/showpost.php?p=72114657&postcount=170
Personally, I'd go with strongst's suggestion to flash the June 2017 stock fastboot ROM - you'd have to revert to stock (completely) anyway to accept the OTA - as you've found out, OTAs will only successfully flash onto a device with stock recovery, kernel, and unmodified system including no root. You may as well update at the same time to the same patch level that the OTA would have brought you up to.
echo92 said:
In future, if that happens, you could try booting to the bootloader, then on the bootloader screen, press 'Start' and try to get your device to boot normally. Credit to: https://forum.xda-developers.com/showpost.php?p=72114657&postcount=170
Personally, I'd go with strongst's suggestion to flash the June 2017 stock fastboot ROM - you'd have to revert to stock (completely) anyway to accept the OTA - as you've found out, OTAs will only successfully flash onto a device with stock recovery, kernel, and unmodified system including no root. You may as well update at the same time to the same patch level that the OTA would have brought you up to.
Click to expand...
Click to collapse
This 100%. Boot into bootloader and choose start from there. I ran into the same issue last night whilst trying to update my XT1644 and figure this out through trial and error. Once I got it back up though, flashing many stock recoveries that I found online couldn't get the update to work either. It would error out a few seconds after booting into the stock recovery and starting the update. I finally resigned to re-flashing a stock image of marshmallow and updating it all again from there. I wanted to pull the stock recovery before I replaced it with TWRP again but I couldn't find a way to do that. Any method I found required having root access already, and of course I can't get root access without flashing a custom recovery first.
echo92 said:
In future, if that happens, you could try booting to the bootloader, then on the bootloader screen, press 'Start' and try to get your device to boot normally.[/url]
Click to expand...
Click to collapse
Thanks for all replies. Rebooting from the bootloader screen brought my phone back to normal. Same March 2017 patch, as well as the same TWRP and ElementalX kernel and build number. Unlocked bootloader logo.bin remains intact. Magisk is still at v13.3 and it passes SafetyNet. Internal memory intact. I'm relieved.
Settings->System Updates->New version NPJ25.93-14.5
However, I'm now contemplating whether it'll be worthwhile to patch my phone to the NPJ25.93-14.5, June 2017 update.
Can I assume that the June 2017 1.1 GB "patch" contains the full NPJ25.93-14.5 firmware for XT1644?
( https://www.androidfilehost.com/?fid=889764386195918175 )
Is there a way to flash the June 2017 ROM via TWRP, and without having to reinstall ElementalX kernel, etc.?
mel2000 said:
Thanks for all replies. Rebooting from the bootloader screen brought my phone back to normal. Same March 2017 patch, as well as the same TWRP and ElementalX kernel and build number. Unlocked bootloader logo.bin remains intact. Magisk is still at v13.3 and it passes SafetyNet. Internal memory intact. I'm relieved.
Settings->System Updates->New version NPJ25.93-14.5
However, I'm now contemplating whether it'll be worthwhile to patch my phone to the NPJ25.93-14.5, June 2017 update.
Can I assume that the June 2017 1.1 GB "patch" contains the full NPJ25.93-14.5 firmware for XT1644?
( https://www.androidfilehost.com/?fid=889764386195918175 )
Is there a way to flash the June 2017 ROM via TWRP, and without having to reinstall ElementalX kernel, etc.?
Click to expand...
Click to collapse
Yes it's the full rom. And no, you need to flash kernel and magisk after every rom flash, stock twrp, fastboot or custom rom doesn't matter(otherwise it's already included).
strongst said:
Yes it's the full rom. And no, you need to flash kernel and magisk after every rom flash, stock twrp, fastboot or custom rom doesn't matter(otherwise it's already included).
Click to expand...
Click to collapse
Thanks again strongst. I'm still contemplating because of the complexity. However, the constant phone notification to update is weakening my resistance. Not sure I want to have to look at that for days on end.
Just to clarify, are you stating that I won't have to reinstall TWRP? That would be a relief.
Would it suffice to copy my internal SD to my PC and restore it later? Do I need to copy everything? Will my Nandroid backup save my Magisk settings?
I did make a TWRP backup of the XT1644 updated to NPJ25.93-14.5. I could share it with you if you'd like. However, you'd still need to flash ElementalX and root after.
mel2000 said:
Thanks again strongst. I'm still contemplating because of the complexity. However, the constant phone notification to update is weakening my resistance. Not sure I want to have to look at that for days on end.
Just to clarify, are you stating that I won't have to reinstall TWRP? That would be a relief.
Would it suffice to copy my internal SD to my PC and restore it later? Do I need to copy everything? Will my Nandroid backup save my Magisk settings?
Click to expand...
Click to collapse
You need to flash twrp after you flashed the stock rom cause the stock rom flash the stock recovery. Copy the whole internal memory, better to save everything when you don't know exactly what you need
Restore the whole internal memory isn't good, just restore what's missing if you recognize it. Your magisk settings will be saved with nandroid, that's true, but don't restore your partitions from nandroid backup from your prior rom version to the new, that cause trouble. Make backup of your apps with titanium backup instead.
Just to clarify - are you on the Amazon software channel (amz) or do you have the Amazon Prime edition of the XT1644 (with the ads on the lockscreen)? I'm just curious as whether this NPJ25.93-14.5 update is exclusive to Amazon or if it's more widespread.
EDIT - seen a couple of users reporting they've received it on the retus channel, so maybe more widespread to US users, maybe to include the Verizon emergency calling patch that the G5 Plus got too?
tmp000 said:
I did make a TWRP backup of the XT1644 updated to NPJ25.93-14.5. I could share it with you if you'd like. However, you'd still need to flash ElementalX and root after.
Click to expand...
Click to collapse
That sounds great tmp000. I'd definitely like you to share it. How would I go about flashing it? Any particular precautions? Thanks.
mel2000 said:
That sounds great tmp000. I'd definitely like you to share it. How would I go about flashing it? Any particular precautions? Thanks.
Click to expand...
Click to collapse
Sorry, I'm not an expert, so I can't say much about precautions. What I will do is tell you what I did to get my phone to its current state now is:
Backup my data
After failing to apply the NPJ25.93-14.5 update many times through a bunch of different stock recoveries that I found online (including versions extracted from full stock ROMs), I found a way to downgrade back to the stock ROM of Marshmallow for the XT1644. I applied all the OTA updates, all the way to NPJ25.93-14.5.
At this point, I flashed TWRP recovery again. At the same time, right after running the command to flash TWRP with fastboot, I also flashed logo.bin to get rid of that unlocked bootloader message. I then booted into TWRP and then backed up the system and boot partition as it was (so stock kernel and no root).
In TWRP, I flashed ElementalX, and then SuperSU after that (I know you are using a different root method so flash yours).
Then I restored the data (data partition only) of the backup I made.
After that, I rebooted into system and everything booted up just fine. I had root access and all of my data was intact. Your steps 2 and 3 would be:
Put my backup with your other backups in the TWRP folder
Do an wipe in TWRP to wipe dalvik cache, cache, system, and boot. DO NOT WIPE INTERNAL STORAGE
Then continue on with step 4 from above. And of course, I can't emphasize enough to back up your data. Not just through TWRP, but any photos, etc that you can copy onto your computer first. I'll PM you a link to my backup.
strongst said:
Your magisk settings will be saved with nandroid, that's true, but don't restore your partitions from nandroid backup from your prior rom version to the new, that cause trouble.
Click to expand...
Click to collapse
Thanks for the advice. However, I'm having trouble determining exactly what I need to backup before the firmware flash.
Which folders from the Root dir of internal memory need to be saved?
Do I need to save the SDCARD directory?
Can I use TWRP to restore individual apps within the Nandroid backup instead of the whole archive?
Just trying to be extra careful to preempt things from going sideways. Thanks.
echo92 said:
I'm just curious as whether this NPJ25.93-14.5 update is exclusive to Amazon or if it's more widespread.
Click to expand...
Click to collapse
I have the retail version of xt1644 and hope that NPJ25.93-14.5 is intended for or compatible with that.
tmp000 said:
I'm ready to do the NPJ25.93-14..5 update. For clarity, I reordered your steps for the update:
Backup my data
Put my backup with your other backups in the TWRP folder
Do an wipe in TWRP to wipe dalvik cache, cache, system, and boot.DO NOT WIPE INTERNAL STORAGE
In TWRP, I flashed ElementalX, and then SuperSU after that (I know you are using a different root method so flash yours).
Then I restored the data (data partition only) of the backup I made.
Click to expand...
Click to collapse
Am I to assume that after step 2 or 3, the actual updating consists of doing a TWRP Restore using the NPJ25.93-14.5 folder that I downloaded? Do I do the wipes before the Restore update? Thanks again for all your help.
mel2000 said:
Am I to assume that after step 2 or 3, the actual updating consists of doing a TWRP Restore using the NPJ25.93-14.5 folder that I downloaded? Do I do the wipes before the Restore update? Thanks again for all your help.
Click to expand...
Click to collapse
Yes, wipe then restore the backup. Sorry for the terrible instructions with missing steps.
mel2000 said:
Received security update notification from Moto, and installed.
Moto G4+ XT1644 (4GB/64GB)
TWRP 3110, ElementalX kernel, Magisk rooted, custom logo
bootloader unlocked
Latest TWRP backup on 08/31/17
After install:
Phone now always reboots to TWRP
tried wiping data, cache, Dalvik but no difference
tried restore backup but still reboots to TWRP
Can only shut phone off via power button
Any advice to get my phone back to normal will be greatly appreciated. Thanks.
Click to expand...
Click to collapse
When you are booted in twrp, reboot to bootloader of system (obviously). Then press power button when it displays start. Like this the phone will boot into system and not in recovery
Or
Just reboot to bootloader and read the thread attached with it.
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Be sure to turn on usb debugging and oem unlock mode
DgnrtnX said:
When you are booted in twrp, reboot to bootloader of system (obviously). Then press power button when it displays start. Like this the phone will boot into system and not in recovery
Or
Just reboot to bootloader and read the thread attached with it.
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Be sure to turn on usb debugging and oem unlock mode
Click to expand...
Click to collapse
Thank you for your reply DgnrtnX. It matches the successful solution I received from exho92 on 09/01/17. The only issue is that I need to boot via that method each time. I no longer boot directly into my system. However I plan to update to NPJ25.93-14.5 shortly so I'm hoping the reboot issue will go away if that upgrade goes well.
USB debugging and OEM unlock were already enabled and remain so.
My only question, why do all these people keep hard bricking their phones? Please, your first step after unlocking your bootloader should be a full Nandroid backup, and download of the stock recovery. That way you have the full stock system, kernel and recovery in case of any mistake, OTA, or any other reason to go back to pure stock. If you need to back to stock, restore your backup, then flash the stock recovery in fastboot. Boom, pure stock, able to accept OTA updates, no issues. Please, for the love of God, make a backup before you make any modifications to your phone. Rant over, thanks for your patients.
Sent from my Moto G (5) Plus using Tapatalk
riggerman0421 said:
My only question, why do all these people keep hard bricking their phones? Please, your first step after unlocking your bootloader should be a full Nandroid backup, and download of the stock recovery. That way you have the full stock system, kernel and recovery in case of any mistake, OTA, or any other reason to go back to pure stock. If you need to back to stock, restore your backup, then flash the stock recovery in fastboot. Boom, pure stock, able to accept OTA updates, no issues. Please, for the love of God, make a backup before you make any modifications to your phone. Rant over, thanks for your patients.
Click to expand...
Click to collapse
Can I also flash the same fastboot ROM on which my device was while on stock (considering I was on the latest update and was trying to flash the fastboot ROM of the same version) if I forgot to make a nandroid backup?
psychopac said:
Can I also flash the same fastboot ROM on which my device was while on stock (considering I was on the latest update and was trying to flash the fastboot ROM of the same version) if I forgot to make a nandroid backup?
Click to expand...
Click to collapse
That should be okay, though be aware that doing so may erase your data in the process. If you need to, make a backup of your device as it currently is in nandroid/TWRP and move it off your device. That way, if anything happens, then you may be able to copy the TWRP backup back and restore your device.
---------- Post added at 05:42 AM ---------- Previous post was at 05:26 AM ----------
riggerman0421 said:
My only question, why do all these people keep hard bricking their phones? Please, your first step after unlocking your bootloader should be a full Nandroid backup, and download of the stock recovery. That way you have the full stock system, kernel and recovery in case of any mistake, OTA, or any other reason to go back to pure stock. If you need to back to stock, restore your backup, then flash the stock recovery in fastboot. Boom, pure stock, able to accept OTA updates, no issues. Please, for the love of God, make a backup before you make any modifications to your phone. Rant over, thanks for your patients.
Sent from my Moto G (5) Plus using Tapatalk
Click to expand...
Click to collapse
Unfortunately, in the majority of hard brick cases, a backup won't save your device, as it's not the system side of things that causes headaches, it's the underlying bootloader.
The main reason is, from what I've observed, is users flashing either the wrong firmware for their device (e.g. US firmware on an Indian device or vice versa) or attempting to downgrade their firmware. Either method can leave you with a mismatched bootloader and system. OTA updates check what system you have for installation purposes, but appear to assume the bootloader is the same patch level as your system. (Should they check for bootloader as well? That check would go some way to preventing hard bricks, but appears Motorola assumes you wouldn't flash firmware not intended for your device or downgrade...)
Thus, because you have a mismatched bootloader and system patch level, you can run into hard bricks when users attempt to subsequently take OTA updates, especially with bootloaders updated to May 2017 or newer.
E.g. a user flashed the US retail NPNS25.137-35-5 with May 2017 firmware onto their device, but wanted to revert back to the Indian firmware. They flashed back to NPN25.137-15 (Jan 2017 security patch) without being able to flash the bootloader, since bootloaders do not permit downgrading of bootloaders generally, and especially after the May 2017 patch. So you have a May 2017 bootloader but a Jan 2017 system. The OTA update downloads and begins flashing believing that your system is Jan 2017 and applies updates to your bootloader thinking it too is at the Jan 2017 patch level too. Of course, it's not - it's May 2017 - and thus causes a hard brick.
The current resolution for hard bricks is blankflashes to reset the bootloader. The only other resolution is that users do not downgrade their firmware, and are very careful with what they flash, and only flash the same firmware as they had or newer firmware that is a direct update of their existing firmware. Alternatively, flashing TWRP images of stock ROMs may be preferable, as these images only flash the system side of things (like a TWRP nandroid backup), so do not affect the bootloader.
echo92 said:
That should be okay, though be aware that doing so may erase your data in the process. If you need to, make a backup of your device as it currently is in nandroid/TWRP and move it off your device. That way, if anything happens, then you may be able to copy the TWRP backup back and restore your device.
Click to expand...
Click to collapse
That's absolutely okay with me as I always like to clean flash ROMs and I don't mind the data partition being erased.
echo92 said:
That should be okay, though be aware that doing so may erase your data in the process. If you need to, make a backup of your device as it currently is in nandroid/TWRP and move it off your device. That way, if anything happens, then you may be able to copy the TWRP backup back and restore your device.
---------- Post added at 05:42 AM ---------- Previous post was at 05:26 AM ----------
Unfortunately, in the majority of hard brick cases, a backup won't save your device, as it's not the system side of things that causes headaches, it's the underlying bootloader.
The main reason is, from what I've observed, is users flashing either the wrong firmware for their device (e.g. US firmware on an Indian device or vice versa) or attempting to downgrade their firmware. Either method can leave you with a mismatched bootloader and system. OTA updates check what system you have for installation purposes, but appear to assume the bootloader is the same patch level as your system. (Should they check for bootloader as well? That check would go some way to preventing hard bricks, but appears Motorola assumes you wouldn't flash firmware not intended for your device or downgrade...)
Thus, because you have a mismatched bootloader and system patch level, you can run into hard bricks when users attempt to subsequently take OTA updates, especially with bootloaders updated to May 2017 or newer.
E.g. a user flashed the US retail NPNS25.137-35-5 with May 2017 firmware onto their device, but wanted to revert back to the Indian firmware. They flashed back to NPN25.137-15 (Jan 2017 security patch) without being able to flash the bootloader, since bootloaders do not permit downgrading of bootloaders generally, and especially after the May 2017 patch. So you have a May 2017 bootloader but a Jan 2017 system. The OTA update downloads and begins flashing believing that your system is Jan 2017 and applies updates to your bootloader thinking it too is at the Jan 2017 patch level too. Of course, it's not - it's May 2017 - and thus causes a hard brick.
The current resolution for hard bricks is blankflashes to reset the bootloader. The only other resolution is that users do not downgrade their firmware, and are very careful with what they flash, and only flash the same firmware as they had or newer firmware that is a direct update of their existing firmware. Alternatively, flashing TWRP images of stock ROMs may be preferable, as these images only flash the system side of things (like a TWRP nandroid backup), so do not affect the bootloader.
Click to expand...
Click to collapse
That is the point of having a backup. You don't have to flash anything in fastboot. You have your OWN firmware backed up on YOUR OWN DEVICE and don't have to worry about any mismatch issues.I have been rooting and flashing custom ROMs for 5 years on 7 different devices( this is the first phone I have not rooted...yet). The first thing I always do after installing a custom recovery is make a full backup. That way if I do something wrong, I always have the stock ROM to go back to. I firmly believe all unlocking and rooting guides should have this step included and not listed as optional but as required. This would help prevent a lot trouble from users flashing the wrong firmware on their phones.
For what it is worth, I have rooted and ROMed: LG Optimus V, Nexus 7 (WIFI tablet), HTC One V, Samsung Galaxy 3, HTC Desire 820, Asus Transformer TF101 (tablet) and Motorola Moto G3. On all these devices I had a full backup of the stock system.
riggerman0421 said:
That is the point of having a backup. You don't have to flash anything in fastboot. You have your OWN firmware backed up on YOUR OWN DEVICE and don't have to worry about any mismatch issues.I have been rooting and flashing custom ROMs for 5 years on 7 different devices( this is the first phone I have not rooted...yet). The first thing I always do after installing a custom recovery is make a full backup. That way if I do something wrong, I always have the stock ROM to go back to. I firmly believe all unlocking and rooting guides should have this step included and not listed as optional but as required. This would help prevent a lot trouble from users flashing the wrong firmware on their phones.
For what it is worth, I have rooted and ROMed: LG Optimus V, Nexus 7 (WIFI tablet), HTC One V, Samsung Galaxy 3, HTC Desire 820, Asus Transformer TF101 (tablet) and Motorola Moto G3. On all these devices I had a full backup of the stock system.
Click to expand...
Click to collapse
I agree with what you wrote, a backup in TWRP and having the same stock ROM is essential to a safe and working device... A stock ROM is always useful in flashing the stock recovery and other stock firmware prior to taking an OTA update. With TWRP backups, you now have to be careful not to allow modifications before you take the backup, else the OTA detects the system partition is no longer readonly, if I recall.
Course, this would be much easier if Motorola/Lenovo released the stock firmware rather than having to depend on leaks, but I'm guessing they don't want to deal with users that flash the incorrect firmware for their device.
I have never flashed a phone before.
It seems I have a virus/malware that's inserted itself into the ROM on my phone. I perform a factory wipe and reset but the malware is there on the fresh install, redirecting webpages to a pop-up about Amazon or Walmart gift cards. Backing up the stock ROM seems not an option for me. Is it possible to download a stock ROM somehow?
vantastic415 said:
I have never flashed a phone before.
It seems I have a virus/malware that's inserted itself into the ROM on my phone. I perform a factory wipe and reset but the malware is there on the fresh install, redirecting webpages to a pop-up about Amazon or Walmart gift cards. Backing up the stock ROM seems not an option for me. Is it possible to download a stock ROM somehow?
Click to expand...
Click to collapse
We have all the stock firmwares posted here...
https://forum.xda-developers.com/g5-plus/how-to/stock-firmware-npn25-137-67-5-fastboot-t3694738
And TWRP flashable stock ROMs here...
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Hi, i just got the moto g5 plus, i always have phones that from the moment i bought them they wouldn recive any updates, so i realy didnt care if unlocking the bootloader installing new recoverys will affect the OTA updates. So i have a couple of questions.
1- first i want to at least have a stock firmware just in case, but i cant figure out which one should i download from here
firmware.center/firmware/Motorola/Moto%20G5%20Plus/Stock/
Before i always use sammobile.com and it was really easy to found a stock firmware from Argentina. My compilation number is: npns25.137-15-11 this means that i suppose to download that one XT1681-XT1683_POTTER_BRASIL_LATAM_MEXICO_7.0_NPN25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip ?
2- it is possible to unlock the bootloader and root your phone without installing a new recovery? i was reading some post and when you change your recovery or you modify something the OTA update will stop working. they are some methods like the magisk but they seem i little bit too complex for me and i don't want to do it every time that a new update is available.
thanks for the help, and sorry for my English i am from Argentina.
1. yes, but any build will flash and run, so it doesn't really matter that much...
2. Nope. You need to flash TWRP in order to root. This is because the stock recovery will only flash signed images... You can use Magisk, after backing up a stock build. Anytime there is an OTA, just restore to that system image, Flash the original recovery via fastboot, and then take the OTA. Once you have it, flash TWRP again, and restore to your other build. Or just run a custom room like Lineage or RR, and this whole thing isn't really an issue anymore.
Karlinski said:
1. yes, but any build will flash and run, so it doesn't really matter that much...
2. Nope. You need to flash TWRP in order to root. This is because the stock recovery will only flash signed images... You can use Magisk, after backing up a stock build. Anytime there is an OTA, just restore to that system image, Flash the original recovery via fastboot, and then take the OTA. Once you have it, flash TWRP again, and restore to your other build. Or just run a custom room like Lineage or RR, and this whole thing isn't really an issue anymore.
Click to expand...
Click to collapse
yeah i know i had a samsung galaxy s3 until now, and i always have cyanogen, slimrom or now lineage, but this is the first device that i have one that will get updates (at least 1 more :S) and i want to seize that
i will start downloading that file just in case
1- ok so unlocking the bootloader doesn't affect updates only when you modify files? when the update is installing is basically comparing the files that you have with the ones that you suppose to have and if there is something different it will fail? its something like that?
2-dumb question how do you do a full backup in the stock recovery there is no option no do a nandroid backup or it will appear after i just unlock the bootloader?
Hello, I have a brazilian G5 Plus that originally didn't have the retail Nougat image Installed (bought form a carrier), but I was able to update to the leaked brazilian 8.1 update. The phone was never bootloader unlocked or rooted, however I'm willing to return to stock nougat in order to try Pie roms and not lose the fingerprint function. What I want to know is A) can i flash retail nougat images on my phone (as it wasnt retail at first)? and B) at what time should I make backups of EFS and Persist partitions?
Should I unlock bootloader while on oreo. install twrp, make backups of efs and persist and then flash stock nougat?
Or should I be able to downgrade to Nougat without any issues, and take backups of EFS and Persist before flashing Pie Roms?
Any clarification on the subject would be deeply appreciated.
Thanks in advance.
Mrkblo said:
Hello, I have a brazilian G5 Plus that originally didn't have the retail Nougat image Installed (bought form a carrier), but I was able to update to the leaked brazilian 8.1 update. The phone was never bootloader unlocked or rooted, however I'm willing to return to stock nougat in order to try Pie roms and not lose the fingerprint function. What I want to know is A) can i flash retail nougat images on my phone (as it wasnt retail at first)? and B) at what time should I make backups of EFS and Persist partitions?
Should I unlock bootloader while on oreo. install twrp, make backups of efs and persist and then flash stock nougat?
Or should I be able to downgrade to Nougat without any issues, and take backups of EFS and Persist before flashing Pie Roms?
Any clarification on the subject would be deeply appreciated.
Thanks in advance.
Click to expand...
Click to collapse
Don't try to downgrade your bootloader as it going to brick your device. If you want to make back up made the back up of Oreo(now in which your using) and nougat also, as we can't say where it goes wrong. And you can flash retail nougat image but don't flash gpt and bootloade so it don't brick your device.
Read this: https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482
If you want to try some custom rom and not lose fingerprint, all you have to do is run the persist fix, flash a 7.0 TWRP-flashable stock build and THEN flash your custom rom. No need to fastboot flash the stock image. Of course also backup your persist and EFS as soon as you first boot into TWRP.
prokaryotic cell said:
Read this: https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482
If you want to try some custom rom and not lose fingerprint, all you have to do is run the persist fix, flash a 7.0 TWRP-flashable stock build from and THEN flash your custom rom. No need to fastboot flash the stock image. Of course also backup your persist and EFS as soon as you first boot into TWRP.
Click to expand...
Click to collapse
Thanks, will have a look at it.