So I was on stock rom that was unlocked plus rooted,I was also on a different kernel. Before flashing that kernel, I had taken a full backup(It had magisk installed) through TWRP. Full means I didn't leave any of the boxes unchecked,it was a 11GB+ backup. Then it was all well and fine until I found that these kernels weren't liking my 64gb sd card(I created a thread earlier). So I went back to TWRP to restore my backup, I did so, well and smooth no issues. Now when I booted my phone, my phone would just turn off after showing the Asus LOGO, I tried multiple times to no success. It would just turn off after showing ASUS logo. To get out of this mess, I flashed Stock rom through TWRP.
Now I'm clean and fresh, I want to take a good backup and then flash AEX rom! What partitions should I backup??
Backup
Deeptesh Basak said:
What partitions should I backup??
Click to expand...
Click to collapse
Backup:
Data
Boot img
System
You may have to flash magisk/SU again after restoring in some cases...
Deeptesh Basak said:
So I was on stock rom that was unlocked plus rooted,I was also on a different kernel. Before flashing that kernel, I had taken a full backup(It had magisk installed) through TWRP. Full means I didn't leave any of the boxes unchecked,it was a 11GB+ backup. Then it was all well and fine until I found that these kernels weren't liking my 64gb sd card(I created a thread earlier). So I went back to TWRP to restore my backup, I did so, well and smooth no issues. Now when I booted my phone, my phone would just turn off after showing the Asus LOGO, I tried multiple times to no success. It would just turn off after showing ASUS logo. To get out of this mess, I flashed Stock rom through TWRP.
Now I'm clean and fresh, I want to take a good backup and then flash AEX rom! What partitions should I backup??
Click to expand...
Click to collapse
Backup everything for your first backup.
For incremental backups - boot, system, vendor & data should suffice.
While restoring only select the above four i mentioned. For cross rom restore functionality vendor partition is required.
For restoring stock rom from stock - only boot, system and data should be enough.
Related
Ok, so I have NEVER been able to successfully restore from a backup made using TWRP when the backup was of a Cyanogen based ROM.
I've tried selecting every box/option for the backup thus creating a big arse file and even those don't successfully install during a restore attempt.
The only backup I have the will successfully install is the one I made immediately after installing TWRP of the stock rom.
When I attempt to restore my CM13 rom it usually gets to around 10 to 14 percent complete and then suddenly just reboots and seems to be stuck on the boot loading image forever until my patience runs out and I flash back to stock.
Any ideas guys? I would LOVE to be able to restore one of my CM13 backups.
I'm on Nexus 6p using newest TWRP and had backed up a couple CM13 nightlies.
Currently running CM13 snapshot.
theinvid said:
Ok, so I have NEVER been able to successfully restore from a backup made using TWRP when the backup was of a Cyanogen based ROM.
I've tried selecting every box/option for the backup thus creating a big arse file and even those don't successfully install during a restore attempt.
The only backup I have the will successfully install is the one I made immediately after installing TWRP of the stock rom.
When I attempt to restore my CM13 rom it usually gets to around 10 to 14 percent complete and then suddenly just reboots and seems to be stuck on the boot loading image forever until my patience runs out and I flash back to stock.
Any ideas guys? I would LOVE to be able to restore one of my CM13 backups.
I'm on Nexus 6p using newest TWRP and had backed up a couple CM13 nightlies.
Currently running CM13 snapshot.
Click to expand...
Click to collapse
Have you read my guide?
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
You definitely shouldn't be selecting all options in the backup menu. You only need to select system, data, boot, and vendor. And obviously only restore those.
Heisenberg said:
Have you read my guide?
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
You definitely shouldn't be selecting all options in the backup menu. You only need to select system, data, boot, and vendor. And obviously only restore those.
Click to expand...
Click to collapse
Thanks for the information. Ok I made a backup of only the 4 things listed...before I made the backup I made sure that I had NO security of any kind.
This time the backup got to 100% and then asked me to reboot the system. I was excited...thinking this had actually worked this time...only to find that it stays stuck io the GOOGLE plash screen...it never makes it to the boot animation.
The original stock backup still works...and in looking at that backup it only had 3 things backed up (no vendor).
Suggestions???
At this point a backup has failed once again and I'll have to spend hours getting it back the way I had it.
theinvid said:
Thanks for the information. Ok I made a backup of only the 4 things listed...before I made the backup I made sure that I had NO security of any kind.
This time the backup got to 100% and then asked me to reboot the system. I was excited...thinking this had actually worked this time...only to find that it stays stuck io the GOOGLE plash screen...it never makes it to the boot animation.
The original stock backup still works...and in looking at that backup it only had 3 things backed up (no vendor).
Suggestions???
At this point a backup has failed once again and I'll have to spend hours getting it back the way I had it.
Click to expand...
Click to collapse
You could try restoring the backup without the vendor, but then you'll need to flash the appropriate vendor image to suit the ROM that you're restoring.
tried
Heisenberg said:
You could try restoring the backup without the vendor, but then you'll need to flash the appropriate vendor image to suit the ROM that you're restoring.
Click to expand...
Click to collapse
tried that. it also failed.
Now things seem to be worse. I restore the original stock backup and then from there begin the process again of installing Cyanogenmod 13...only no matter what I do to install it...it gets stuck on the Google unlock screen.
I've tried.
Factory Reset - Install Just CM13 snapshot = fail
Factory Reset - Install CM13 snapshot and Gapps = fail
Factory Reset - Install CM13 snapshot and Gapps and Xposed and Vendor file fix thingy = Fail
a few other combinations all failing the same way.
A phone is worthless to me if I can't run CM13 I "NEED" to customize!!
Please help.
theinvid said:
tried that. it also failed.
Now things seem to be worse. I restore the original stock backup and then from there begin the process again of installing Cyanogenmod 13...only no matter what I do to install it...it gets stuck on the Google unlock screen.
I've tried.
Factory Reset - Install Just CM13 snapshot = fail
Factory Reset - Install CM13 snapshot and Gapps = fail
Factory Reset - Install CM13 snapshot and Gapps and Xposed and Vendor file fix thingy = Fail
a few other combinations all failing the same way.
A phone is worthless to me if I can't run CM13 I "NEED" to customize!!
Please help.
Click to expand...
Click to collapse
Are you flashing the appropriate vendor image for the ROM after you've flashed the ROM? When you say factory reset are you just choosing the factory reset option in TWRP? If so, you should instead go into the advanced wipe section and wipe system, data, cache, and dalvik cache. CM isn't the only ROM out there with customisation, there are other ROMs that have the same or more level of customisation available.
theinvid said:
tried that. it also failed.
Now things seem to be worse. I restore the original stock backup and then from there begin the process again of installing Cyanogenmod 13...only no matter what I do to install it...it gets stuck on the Google unlock screen.
I've tried.
Factory Reset - Install Just CM13 snapshot = fail
Factory Reset - Install CM13 snapshot and Gapps = fail
Factory Reset - Install CM13 snapshot and Gapps and Xposed and Vendor file fix thingy = Fail
a few other combinations all failing the same way.
A phone is worthless to me if I can't run CM13 I "NEED" to customize!!
Please help.
Click to expand...
Click to collapse
also simply tried a Factory Reset followed by reboot and that failed in the same way.
currently it would seem that Screw'd ROM is successfully installing. hmm
what's up with my CM13??
I hope I like this ROM
theinvid said:
currently it would seem that Screw'd ROM is successfully installing. hmm
what's up with my CM13??
I hope I like this ROM
Click to expand...
Click to collapse
I really don't know, there's no reason it shouldn't install. You must be missing something, or perhaps the zip is corrupt, did you check the MD5?
So I have been running Pure Nexus rom with Elemental X kernel and SuperSU and it's been working just fine. Well I made a nandroid, and flashed a couple new roms to try out. Didn't like any of them better so I decided to restore back to my nandroid. I used TWRP 3.0.2-2 to make the nandroid and when I tried to restore using same version it just constantly bootloops between the Google splash screen and the"Your device software cannot be checked etc etc screen". I did update my radio and bootloader to the newest versions via a flashable zip and also updated my vendor to the latest vendor image N4F26J. One of the roms said my vendor image was out of date or whatever but still booted fine for me to try out. Regardless I have factory reset phone including internal storage and flashed the factory OTA image and still no luck. Odd thing is I can still boot TWRP and also access my internal storage and move files from PC to my phone. It will even flash Roms and everything but it will not get past the Google splash screen. So wth do I do lol?
Kochoa940 said:
So I have been running Pure Nexus rom with Elemental X kernel and SuperSU and it's been working just fine. Well I made a nandroid, and flashed a couple new roms to try out. Didn't like any of them better so I decided to restore back to my nandroid. I used TWRP 3.0.2-2 to make the nandroid and when I tried to restore using same version it just constantly bootloops between the Google splash screen and the"Your device software cannot be checked etc etc screen". I did update my radio and bootloader to the newest versions via a flashable zip and also updated my vendor to the latest vendor image N4F26J. One of the roms said my vendor image was out of date or whatever but still booted fine for me to try out. Regardless I have factory reset phone including internal storage and flashed the factory OTA image and still no luck. Odd thing is I can still boot TWRP and also access my internal storage and move files from PC to my phone. It will even flash Roms and everything but it will not get past the Google splash screen. So wth do I do lol?
Click to expand...
Click to collapse
Maybe stupid answer : 1 did you flashed boot.img ?
2. Is your data partition anything like ex4 or f2fs ?
Will it stuck on google logo ? (I had stucl for 10 min once ) or it just bootloops
Why not try to flash 3.0.3.0 recovery and try again?
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
Vaseag said:
Maybe stupid answer : 1 did you flashed boot.img ?
2. Is your data partition anything like ex4 or f2fs ?
Will it stuck on google logo ? (I had stucl for 10 min once ) or it just bootloops
Why not try to flash 3.0.3.0 recovery and try again?
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
Click to expand...
Click to collapse
I tried flashing the factory image via command prompt but still bootlooping. data partition has not been modified it is still same as stock.
Kochoa940 said:
I tried flashing the factory image via command prompt but still bootlooping. data partition has not been modified it is still same as stock.
Click to expand...
Click to collapse
Did you try to flash the OTA image or full factory image? I think there is a known problem with the latest build of Pure nexus where some people can't boot past the Google logo. If that's your issue there are workarounds. You should check the Pure nexus thread.
Try a full wipe(without internal) and restore your nandroid without the data partition and let me know how it went.
If your nandroid contained the efs backup (3.0.2-2 backs it up by default) and you restored your backup with the efs partition your borked since you used TWRP 3.0.2-2. That TWRP has a bug restoring EFS as there is efs.1 and efs.2 and I think it writes both efs 1 and 2 to just efs.1 on the phone which causes the boot loop.
You need to have had an EFS backup and then roll back your twrp to 3.0.0-0 and restore your EFS back from there.
---------- Post added at 05:00 PM ---------- Previous post was at 04:54 PM ----------
Kochoa940 said:
So I have been running Pure Nexus rom with Elemental X kernel and SuperSU and it's been working just fine. Well I made a nandroid, and flashed a couple new roms to try out. Didn't like any of them better so I decided to restore back to my nandroid. I used TWRP 3.0.2-2 to make the nandroid and when I tried to restore using same version it just constantly bootloops between the Google splash screen and the"Your device software cannot be checked etc etc screen". I did update my radio and bootloader to the newest versions via a flashable zip and also updated my vendor to the latest vendor image N4F26J. One of the roms said my vendor image was out of date or whatever but still booted fine for me to try out. Regardless I have factory reset phone including internal storage and flashed the factory OTA image and still no luck. Odd thing is I can still boot TWRP and also access my internal storage and move files from PC to my phone. It will even flash Roms and everything but it will not get past the Google splash screen. So wth do I do lol?
Click to expand...
Click to collapse
If your nandroid contained the efs backup (3.0.2-2 backs it up by default) and you restored your backup with the efs partition your borked since you used TWRP 3.0.2-2. That TWRP has a bug restoring EFS as there is efs.1 and efs.2 and I think it writes both efs 1 and 2 to just efs.1 on the phone which causes the boot loop.
You need to have had an EFS backup and then roll back your twrp to 3.0.0-0 and restore your EFS back from there.
Vaseag said:
Maybe stupid answer : 1 did you flashed boot.img ?
2. Is your data partition anything like ex4 or f2fs ?
Will it stuck on google logo ? (I had stucl for 10 min once ) or it just bootloops
Why not try to flash 3.0.3.0 recovery and try again?
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
Click to expand...
Click to collapse
Eric214 said:
If your nandroid contained the efs backup (3.0.2-2 backs it up by default) and you restored your backup with the efs partition your borked since you used TWRP 3.0.2-2. That TWRP has a bug restoring EFS as there is efs.1 and efs.2 and I think it writes both efs 1 and 2 to just efs.1 on the phone which causes the boot loop.
You need to have had an EFS backup and then roll back your twrp to 3.0.0-0 and restore your EFS back from there.
---------- Post added at 05:00 PM ---------- Previous post was at 04:54 PM ----------
If your nandroid contained the efs backup (3.0.2-2 backs it up by default) and you restored your backup with the efs partition your borked since you used TWRP 3.0.2-2. That TWRP has a bug restoring EFS as there is efs.1 and efs.2 and I think it writes both efs 1 and 2 to just efs.1 on the phone which causes the boot loop.
You need to have had an EFS backup and then roll back your twrp to 3.0.0-0 and restore your EFS back from there.
Click to expand...
Click to collapse
Ok I am gonna try and revert to 3.0.0 and restore the EFS and then the backup. Would that be the correct resolution?
Ok so I fixed it!!!!! Btw thank you guys for all your responses!!!
Even though my version of TWRP was 3.0.2-2 this still worked for me following these commands. I randomly found this page and said what the hell I have nothing to lose so I did it and it freakin' worked! anyways here's the link in case anyone else has this issue of not booting past google splash screen
http://www.droidorigin.com/warning-nexus-6p-users-twrp-3-0-2-1/
Again thanks to those who responded and tried to help!
Attempt 1 to install Lineage
Tried installing the Lineage 14.1, it kept doing a blank-but-illuminated screen, then turned off and back on, resulting in a boot loop.
We tried a couple of things - first the more conservative wiping of just data, dalvik and cache.
This did the boot loop described above. I then restored the stock backup and all was well.
Attempt 2 to install Lineage
The second time we wiped the system partition in addition to the above. Same bootloop.
Went to restore the backup of stock again, but now it's getting stuck at "I'm not a phone I'm a comprehensive yada yada" screen. It never progresses past this.
Attempts to get Stock Restore working
We've tried restoring just the system, data and dalvik
We've also tried System Image in addition to these.
No joy.
We don't have a laptop or other device to hand for a few days so we have just what's on the phone - the Lineage 14.1 zip, the stock backup and TWRP.
Any ideas how we can get back to a working phone with either OS?
What type of LePro3 do you have?
X720,X722,X727?
It's the X722
kenbw2 said:
It's the X722
Click to expand...
Click to collapse
The X722 model is not supported by Lineage.
I think that you have a problem. Hope anyone can help you to go back to stock successfully.
When doing the stock restore, we didn't restore the boot image.
Is that something worth trying?
kenbw2 said:
When doing the stock restore, we didn't restore the boot image.
Is that something worth trying?
Click to expand...
Click to collapse
Yes, you could try it. Please, write, was it useful or not)
Success!
Restored System,. System Image, Cache, Data and Boot partitions and all is now back to normal.
Phew!
kenbw2 said:
Success!
Restored System,. System Image, Cache, Data and Boot partitions and all is now back to normal.
Phew!
Click to expand...
Click to collapse
That is great. So, is bluetooth works fine after that?
Before going into the subject, I'll say that I have tried to seach this matter in XDA and Google, but nothing showed up.
Okay, so my matter is that I can't restore my backup of stock rom(8.0) after I flash a 8.1 rom. I've backuped with official TWRP "recovery-3.2.1-2-oreo.img".
My procedures are :
back up stock 8.0(system, data, cache, efs) with official TWRP "recovery-3.2.1-2-oreo.img"
flash oreo rom(with wiping internel, data, system, cache) and boot it fine.
restore my stock backup with same TWRP
boot system
The results are :
Goes past boot logo
Boot animation('android one' with colors sliding) shows up
and... just infinite loop of boot animation.
The ROM I used is RR.
I think the main problem is related with encryption.... Just my thought, tho.
So what I'm asking is :
1. If you face the same problem as me?
2. If you aren't and you restore goes fine, please tell me your procedures including ROM used and TWRP used.
3. Whether it is safe to decrypt stock rom?
Thanks in advance!
You don't need to flash stock ROM again. You have a system image backup(system, data, cache, efs), right? Wipe data , system, cache if you are coming from any other ROM. Then reboot to bootloader. Boot into latest TWRP from Fastboot (don't flash). Then go to restore and restore the system image you had backed up. Don't restore efs if you haven't lost your IMEI.
I've done exactly as ypu told, but it doesn't boot...
Did you manage to restore without problem with your method?
Yes I was able to. No problem here.
What TWRP did you use? Also, what ROM have you flashed?
Used the latest TWRP by MohanCM for Oreo. I did it when I was on Lineage os and wanted to go to stock
@guy_infinity Okay, thanks for your answer! Gonna try out later, once more.
Hmmm.... Still didn't boot up.
I thought I had to do everything from the begining, but flashing stock with save userdata option rescued me.
P.S. does anyone know about the error E: recv error on uevent?
try flashing stock rom using mi flash and after flashing restore normally using latest twrp/deadman's without system image voila everything will be back
@arjunbalan1994 Big thanks for your suggestion! Will try that too later
Hi, did you solve your restore problem? I have the same w/ my Redmi Note 5 and stock Miui backup after flashing RR.
Thanks for your help
I was use 8.1 root and twrp recovery. Yesterday fastboot flash may rom and update 2nd may OTA
Don't understand : May rom is Miui rom?
And did you restore your miui rom 8.0 backup ith twpr after the fastboot flash stock?
Hi,
I've flashed TWRP for a sm-G900f via heimdall, booted into TWRP-Recovery, made an backup from the working Stock ROM to sd card, flashed lineage open gapps etc., all works well.
Because of somtimes not working Sensors I've tried to test if the sensor problem is an hardware or an software issue, so recovered the stock rom backup using the installed twrp 3.2.1-0. Therefor I've made these steps :
Boot into recovery
Wipe cache, system, davlink-cache, format data
restore the stock rom backup
reboot
Every reboot results in booting to recovery, Samsung system won't start.
Tried to disconnect battery for a few minutes etc.
Where is my mistake ? Could someone give me an advice ?
Every restore of the lineage backups using this way works well.
Regards
Fred
fred06007 said:
Hi,
I've flashed TWRP for a sm-G900f via heimdall, booted into TWRP-Recovery, made an backup from the working Stock ROM to sd card, flashed lineage open gapps etc., all works well.
Because of somtimes not working Sensors I've tried to test if the sensor problem is an hardware or an software issue, so recovered the stock rom backup using the installed twrp 3.2.1-0. Therefor I've made these steps :
Boot into recovery
Wipe cache, system, davlink-cache, format data
restore the stock rom backup
reboot
Every reboot results in booting to recovery, Samsung system won't start.
Tried to disconnect battery for a few minutes etc.
Where is my mistake ? Could someone give me an advice ?
Every restore of the lineage backups using this way works well.
Regards
Fred
Click to expand...
Click to collapse
Corrupted backup maybe?
A long time ago I made a backup of stock and was able to go back and forth with no issues. You can try and go back to stock, root again and try another back up.
Corrupted backup ? It's the only one I've made after flashing TWRP and before installing Lineage.
fred06007 said:
Corrupted backup ? It's the only one I've made after flashing TWRP and before installing Lineage.
Click to expand...
Click to collapse
It happens sometimes, I had an SD card with a bad sector so every time I would make a back up it would get corrupted if I deleted the back up. I ended up leaving the backup so it will no longer write on the bad sectors.
fred06007 said:
Where is my mistake ? Could someone give me an advice ?
Click to expand...
Click to collapse
I think, you have to flash or restore the right kernel.
Which partitions have you backed up?
Sorry for the late response, the backup includes in my mind system, data and boot partition because the backup consit's of the following files:
boot.emmc.win
boot.emmc.win.sha2
data.ext4.win
data.ext4.win.sha2
data.info
recovery.log
system.ext4.win000
system.ext4.win000.sha2
system.ext4.win001
system.ext4.win001.sha2
system.info