Hi. I have a Moto G Plus US variant XT1644. I did a clean backup (stock ROM) when I was on NPJS25.93-14.7-3 (boot, system and data).
After that I installed many custom ROMs, all of which caused my phone to drain battery and heat up so I decided to go back to stock by restoring my backup.
After I restored my backup I instantly received a new update via OTA (build NPJS25.93-14.7-5). So in order to install it "officially" I grabbed a stock recovery.img (in this forum) and flashed it before tapping on INSTALL so that everything keeps unmodified before applying the update. But when it reboots and tries to install the update I get a message "Error!".
Please any help would be much appreciated.
1)When you took the TWRP backup, do you remember if swipe to allow modifications was allowed in TWRP? If so, then the system partition in your backup might be flagged as read write, which would prevent the OTA from flashing.
2)Is the recovery from the same build as NPJ25.93-14.7-3?
3)Do you have a custom logo.bin to hide the bootloader warning?
echo92 said:
1)When you took the TWRP backup, do you remember if swipe to allow modifications was allowed in TWRP? If so, then the system partition in your backup might be flagged as read write, which would prevent the OTA from flashing.
2)Is the recovery from the same build as NPJ25.93-14.7-3?
3)Do you have a custom logo.bin to hide the bootloader warning?
Click to expand...
Click to collapse
I think he can flash the 14.7 US Retail without deleting the Data Partition to get back to Stock and then do the OTA updates.
He can check this thread out:
https://forum.xda-developers.com/mo...e-security-patch-usa-february-t3745147/page15
echo92 said:
1)When you took the TWRP backup, do you remember if swipe to allow modifications was allowed in TWRP? If so, then the system partition in your backup might be flagged as read write, which would prevent the OTA from flashing.
2)Is the recovery from the same build as NPJ25.93-14.7-3?
3)Do you have a custom logo.bin to hide the bootloader warning?
Click to expand...
Click to collapse
1) I definitely took the backup after allowing modifications so this is probably why.
2) yes
3) no
Danny1976 said:
I think he can flash the 14.7 US Retail without deleting the Data Partition to get back to Stock and then do the OTA updates.
He can check this thread out:
https://forum.xda-developers.com/mo...e-security-patch-usa-february-t3745147/page15
Click to expand...
Click to collapse
Yeah, I´ve been following that thread. I will try to do that and try to make clean backups (without allowing modifications). BTW how should I make a backup of the recovery and bootloader with TWRP ? Thanks.
hernaner28 said:
1) I definitely took the backup after allowing modifications so this is probably why.
2) yes
3) no
Yeah, I´ve been following that thread. I will try to do that and try to make clean backups (without allowing modifications). BTW how should I make a backup of the recovery and bootloader with TWRP ? Thanks.
Click to expand...
Click to collapse
You don't have to flash TWRP, just boot to it. Use the command fastboot boot twrp-3.1.1.0-athene.img and keep it read only. Make a backup of the system and boot. Root with ElementalX and Magisk. Then use Flashify to backup recovery, if you have not flashed TWRP.
Related
Hey guys and gals!
After a few weeks of using the phone, I now feel comfortable doing a Nandroid Backup (TWRP).
I used to do it all the time on my OPO Kitkat, but now with Android Marshmallow, it's quite different.
Here is my situation:
A2017U (us version)
TWRP 3.0.2.2 Installed
Bootloaded Unlocked
Rooted
Xposed Framework v87 installed
Update B29 installed
Inside TWRP>Backup I have many options:
1- Boot (64MB)
2- Cache (2MB)
3- Data(6969MB)
4- Recovery (64MB)
5- System (3723MB)
6- System Image (6144MB)
7- EFS (4MB)
By default, the "Boot", "Data" and "System" are selected, but after some reading I could also backup "System Image" for a near-perfect restore.
Also, some said to backup the EFS in-case it gets corrupted/damage, but some say it can brick your device.
Could anyone tell me what should I backup in case I get stuck somewhere in the future.
Thank you !!
P.S: I have removed any fingerprints and set the lock screen to "Swipe" (no pattern).
First, make sure to flash the official twrp. Do not keep the one we use to unlock bootloader.
There is no harm in backing up efs, in fact it is a good idea to do so. Just do not select it during a restore unless something has wiped your current efs and its the only way to fix.
I don't see a need to back up a full system image but couldn't hurt to at least have one for safe keeping.
Boutchoo said:
Hey guys and gals!
After a few weeks of using the phone, I now feel comfortable doing a Nandroid Backup (TWRP).
I used to do it all the time on my OPO Kitkat, but now with Android Marshmallow, it's quite different.
Here is my situation:
A2017U (us version)
TWRP 3.0.2.2 Installed
Bootloaded Unlocked
Rooted
Xposed Framework v87 installed
Update B29 installed
Inside TWRP>Backup I have many options:
1- Boot (64MB)
2- Cache (2MB)
3- Data(6969MB)
4- Recovery (64MB)
5- System (3723MB)
6- System Image (6144MB)
7- EFS (4MB)
By default, the "Boot", "Data" and "System" are selected, but after some reading I could also backup "System Image" for a near-perfect restore.
Also, some said to backup the EFS in-case it gets corrupted/damage, but some say it can brick your device.
Could anyone tell me what should I backup in case I get stuck somewhere in the future.
Thank you !!
P.S: I have removed any fingerprints and set the lock screen to "Swipe" (no pattern).
Click to expand...
Click to collapse
lafester said:
First, make sure to flash the official twrp. Do not keep the one we use to unlock bootloader.
There is no harm in backing up efs, in fact it is a good idea to do so. Just do not select it during a restore unless something has wiped your current efs and its the only way to fix.
I don't see a need to back up a full system image but couldn't hurt to at least have one for safe keeping.
Click to expand...
Click to collapse
How do I know which TWRP I installed ?
Do you have a link for the official TWRP for the Axon 7 ?
Its in the dev forum titled official twrp.
lafester said:
Its in the dev forum titled official twrp.
Click to expand...
Click to collapse
This? :
https://twrp.me/devices/zteaxon7.html
https://dl.twrp.me/ailsa_ii/
Edit: Looks like there's twrp-3.0.3-0-ailsa_ii Out for the Axon 7
But the official XDA Forum Page it's twrp-3.0.2-0-a2017u
After flashing the 3.0.2-0-a2017u, I now have in the backup sections: Modem (NON-HLOS) (95MB), I don't know if I should back it up.
hello all
i have ZTE AXON 7 U model.
i did bootloader unloock and instaled TWRP 3041 and did this "Once you booted to TWRP , Tap Mount and Check "Mount, System as Read-only", this is very important".
now im on the A2017UV1.1.0B15_systemstock_by_DrakenFX.zip. all works great.
in twrp when i do backup and want to restore it i get this massage: " cannot restore system--mounted read only".
how can i backup and restore in the wright way?
ty all
le011 said:
hello all
i have ZTE AXON 7 U model.
i did bootloader unloock and instaled TWRP 3041 and did this "Once you booted to TWRP , Tap Mount and Check "Mount, System as Read-only", this is very important".
now im on the A2017UV1.1.0B15_systemstock_by_DrakenFX.zip. all works great.
in twrp when i do backup and want to restore it i get this massage: " cannot restore system--mounted read only".
how can i backup and restore in the wright way?
ty all
Click to expand...
Click to collapse
"Mount and Check "Mount, System as Read-only", this is very important".
What you have quoted is only to complete the installation Flash. Go ahead and uncheck 'Mount System Read-Only' for normal operation and you are ready to go!
amphi66 said:
"Mount and Check "Mount, System as Read-only", this is very important".
What you have quoted is only to complete the installation Flash. Go ahead and uncheck 'Mount System Read-Only' for normal operation and you are ready to go!
Click to expand...
Click to collapse
To for your replay.
When I unchecked the System read only and trying to restore the phone from the backup I made in Twrp the phone stucks after reboot on the screen that says the bootloader is unlocked and that's it.
le011 said:
To for your replay.
When I unchecked the System read only and trying to restore the phone from the backup I made in Twrp the phone stucks after reboot on the screen that says the bootloader is unlocked and that's it.
Click to expand...
Click to collapse
You should see that screen and the phone should continue to boot after 5 seconds.
To recap:
1. You stated all was fine in B15 after following the upgrade steps.
2. You made a TWRP backup (system, data & boot) of your new B15
3. When attempting to TWRP restore the B15 backup it could not as system was still mounted "read only"
4. You unchecked "read only" and then did the restore
5. Now system does not boot (hangs on bootloader unlocked warning screen)
If that is correct it sounds as if you have a bad or incomplete B15 backup or you are attempting to restore a B29 backup to a B15 bootstack.
amphi66 said:
You should see that screen and the phone should continue to boot after 5 seconds.
To recap:
1. You stated all was fine in B15 after following the upgrade steps.
2. You made a TWRP backup (system, data & boot) of your new B15
3. When attempting to TWRP restore the B15 backup it could not as system was still mounted "read only"
4. You unchecked "read only" and then did the restore
5. Now system does not boot (hangs on bootloader unlocked warning screen)
If that is correct it sounds as if you have a bad or incomplete B15 backup or you are attempting to restore a B29 backup to a B15 bootstack.
Click to expand...
Click to collapse
All correct.
After Im making backup, I'm wiping, and trying to restore the backup I just did.
No luck.
le011 said:
All correct.
After Im making backup, I'm wiping, and trying to restore the backup I just did.
No luck.
Click to expand...
Click to collapse
Confusing to me. How are you using phone after a bad restore?
What revision TWRP did you flash? Did you flash SU 2.79 after flashing ROM?
Perhaps someone w/ more knowledge can chime in, but sounds as if you are a candidate to begin again following the steps carefully
Goodluck
amphi66 said:
Confusing to me. How are you using phone after a bad restore?
What revision TWRP did you flash? Did you flash SU 2.79 after flashing ROM?
Perhaps someone w/ more knowledge can chime in, but sounds as if you are a candidate to begin again following the steps carefully
Goodluck
Click to expand...
Click to collapse
hi
i have TWRP version 3041.
after i'm trying to restore and wont succeeded , i flash the rom again. the rom im flashing is : A2017UV1.1.0B15_systemstock_by_DrakenFX.
then the phone boot up and work great.
im not flashing supersu because i dont want root.
le011 said:
hi
i have TWRP version 3041.
after i'm trying to restore and wont succeeded , i flash the rom again. the rom im flashing is : A2017UV1.1.0B15_systemstock_by_DrakenFX.
then the phone boot up and work great.
im not flashing supersu because i dont want root.
Click to expand...
Click to collapse
Interesting. How long are you waiting on the Bootloader unlocked warning screen?
Next time in TWRP look at the data partition and verify it is formatted as ext4 not f2fs. I might also download a different version of TWRP and reflash the IMG file from within TWRP. I reference @DrakenFX here as he may have the easy solution.
amphi66 said:
Interesting. How long are you waiting on the Bootloader unlocked warning screen?
Next time in TWRP look at the data partition and verify it is formatted as ext4 not f2fs. I might also download a different version of TWRP and reflash the IMG file from within TWRP. I reference @DrakenFX here as he may have the easy solution.
Click to expand...
Click to collapse
How i check in TWRP how the data partition formated?
I trayid the new version of TWRP 3100 and same thing.
after restoring the phone stuck on the Bootloader unlocked warning screen -last time i waited for 5 min before i
shut down whit power button.
le011 said:
hi
i have TWRP version 3041.
after i'm trying to restore and wont succeeded , i flash the rom again. the rom im flashing is : A2017UV1.1.0B15_systemstock_by_DrakenFX.
then the phone boot up and work great.
im not flashing supersu because i dont want root.
Click to expand...
Click to collapse
amphi66 said:
Interesting. How long are you waiting on the Bootloader unlocked warning screen?
Next time in TWRP look at the data partition and verify it is formatted as ext4 not f2fs. I might also download a different version of TWRP and reflash the IMG file from within TWRP. I reference @DrakenFX here as he may have the easy solution.
Click to expand...
Click to collapse
Easy fix, go back to TWRP,
* Wipe Data (if you are in different ROM a or version) - Dalvik- Cache
* Check MOUNT SYSTEM AS READ-ONLY
* Reflash B15 system
Happy reboot
If you Previously were using B15 , you may restore data only, other wise is a no go.
DrakenFX said:
Easy fix, go back to TWRP,
* Wipe Data - Dalvik- Cache
* Check MOUNT SYSTEM AS READ-ONLY
* Reflash B15 system
Happy rebokt
Click to expand...
Click to collapse
hi
i did that for 3 tomes ending whit the same result :
the rom working great after clean instal...restoring from TWRP....ending whit stuck phone.
le011 said:
How i check in TWRP how the data partition formated?
I trayid the new version of TWRP 3100 and same thing.
after restoring the phone stuck on the Bootloader unlocked warning screen -last time i waited for 5 min before i
shut down whit power button.
Click to expand...
Click to collapse
You may not have seen this on another thread with a similar issue:
"did find something else out. Under [TWRP] settings, if I enabled the "Use rm -rf instead of formatting", then I can restore successfully."
Goodluck
amphi66 said:
You may not have seen this on another thread with a similar issue:
"did find something else out. Under [TWRP] settings, if I enabled the "Use rm -rf instead of formatting", then I can restore successfully."
Goodluck
Click to expand...
Click to collapse
OK ty
i will try that and post if sucssed.
I'm not sure what happened, but my phone lost root and couldn't boot into system due to a problem with encryption. I had to do a reset. I'm now on 10k with no TWRP or root.
I assume I need to roll back to 10p or 10i stock and re-root. However, I can't find the programs and the stock 10i or 10p files.
EDIT: Apparently, the firmwares site doesn't like Firefox. It wasn't showing any of the firmwares for download. I had to use a different browser.
I was able to roll back to 10p. Install TWRP, and flash 10k with Magisk.
I don't want to have whatever happened to me again. Does anyone know why I lost lost TWRP and had to reset?
Sizzlechest said:
I was able to roll back to 10p. Install TWRP, and flash 10k with Magisk.
I don't want to have whatever happened to me again. Does anyone know why I lost lost TWRP and had to reset?
Click to expand...
Click to collapse
Did you flash anything recently that may have caused you to lose root? if I'm not mistaken, if you flash a boot image without flashing root after that will cause you to lose root and if you boot without root it will restore your backup recovery partition removing TWRP. I've actually dd'd my recovery partition over the backup so this doesn't happen, but I'm sure there are other ways to lose root...
dimm0k said:
Did you flash anything recently that may have caused you to lose root? if I'm not mistaken, if you flash a boot image without flashing root after that will cause you to lose root and if you boot without root it will restore your backup recovery partition removing TWRP. I've actually dd'd my recovery partition over the backup so this doesn't happen, but I'm sure there are other ways to lose root...
Click to expand...
Click to collapse
I suspect the person "fooling around" with my phone was in the SuperSU app. The only potentially destructive thing in there would be full unroot since you can remove TWRP from there. It's just a theory. Even if you dd the recovery partition, how would you get it back without TWRP or root?
Sizzlechest said:
I suspect the person "fooling around" with my phone was in the SuperSU app. The only potentially destructive thing in there would be full unroot since you can remove TWRP from there. It's just a theory. Even if you dd the recovery partition, how would you get it back without TWRP or root?
Click to expand...
Click to collapse
from what I've gathered, there are two recovery partitions, one is the main and then there is another that's a backup. when you install TWRP it always installs to the main one leaving the backup intact. when recovery gets reset, it pulls it from the backup... however if it didn't and the main is messed up then you might be screwed
I'm currently running magisk, I've been trying to do everything systemlessly but it's getting frustrating, failed boots, bugs, limitations... I want to stick with systemless so I can count on my warranty which I can get back with two commands. Now, my question is, how hard and risky is to get stock recovery and lock back the bootloader once twrp is installed. Another thing I'm concerned about is if OTA update kicks in, I uninstall magisk and update it and it fails, I'm stuck, can't get any data or backup. Twrp would help a ton and I'm pretty sure I can just flash the new OTA image from twrp. But how hard and risky is restoring factory phone image (system+bootloader+recovery) once lord twrp is installed?
Why do you need to install TWRP if you can just boot it from fastboot? Well, using Magisk and updating system is always a bit risky, they have a guide on how to update and temporary remove Magisk, but it is always recommended to do a full backup.
To restore your device to a stock state, you can use MiFlash or download the fastboot version of the ROM, inside there is a script that will wipe everything and relock the bootloader, leaving no traces of your voided warranty.
Daydreamaway said:
Why do you need to install TWRP if you can just boot it from fastboot? Well, using Magisk and updating system is always a bit risky, they have a guide on how to update and temporary remove Magisk, but it is always recommended to do a full backup.
To restore your device to a stock state, you can use MiFlash or download the fastboot version of the ROM, inside there is a script that will wipe everything and relock the bootloader, leaving no traces of your voided warranty.
Click to expand...
Click to collapse
That's great, and fastboot is always available no matter how corrupt the system is, right? What do you recommend for a full backup and what about allowing system modifications when twrp boots?
I really want to have TWRP installed on my device and have OTA, is there anyway I can achieve this, maybe a flashabe zip that updates the device?
Let's start from the scratch. Unlock the bootloader and grab latest recovery image. Put your device into fastboot mode. Now boot into recovery temporarily and don't flash twrp. Now go to Backup and take a backup of Boot partition (make sure it's completely virgin). Now you can flash twrp and Magisk if you wish. When an OTA comes in, just reboot to twrp and restore the boot partition. Now your device is free from twrp and magisk and ready to get OTA update. But make sure you don't play with build.prop or uninstall any System app or play with System partition.If you change anything on System partition, you need to un-change them before trying to get OTA update. Boot partition will only help you to get rid of twrp and magisk. But if you wanna play with System partition, it's better to take a complete nandroid backup the same way I told you.
Rowdyy Ronnie said:
Let's start from the scratch. Unlock the bootloader and grab latest recovery image. Put your device into fastboot mode. Now boot into recovery temporarily and don't flash twrp. Now go to Backup and take a backup of Boot partition (make sure it's completely virgin). Now you can flash twrp and Magisk if you wish. When an OTA comes in, just reboot to twrp and restore the boot partition. Now your device is free from twrp and magisk and ready to get OTA update. But make sure you don't play with build.prop or uninstall any System app or play with System partition.If you change anything on System partition, you need to un-change them before trying to get OTA update. Boot partition will only help you to get rid of twrp and magisk. But if you wanna play with System partition, it's better to take a complete nandroid backup the same way I told you.
Click to expand...
Click to collapse
So when I boot TWRP to backup the boot partition, I should keep read only?
ibooth2004 said:
So when I boot TWRP to backup the boot partition, I should keep read only?
Click to expand...
Click to collapse
Don't worry about it. When you boot into twrp (temporarily), just swipe to allow modification and head on to Backup and take a backup of boot partition. Thats it.