I have a 6P running PA and after flashing the update 6.0.3 i realized wifi wasnt working so i decided to restore back to 6.0.1.
Its stuck at the boot animation now and i dont know what to do. my backup has lots of important texts, notes etc.
I didnt wipe anything before hand and restored to my previous backup. Rebooted system right after it says restore successful in TWRP 3.0.2
avEmonsta said:
I have a 6P running PA and after flashing the update 6.0.3 i realized wifi wasnt working so i decided to restore back to 6.0.1.
Its stuck at the boot animation now and i dont know what to do. my backup has lots of important texts, notes etc.
I didnt wipe anything before hand and restored to my previous backup. Rebooted system right after it says restore successful in TWRP 3.0.2
Click to expand...
Click to collapse
If you backed up and restored your EFS it may be a bug that corrupts the partition and forces you to erase it via fastboot, tho my understanding is that the bug was limited to -1 version. -2 has other issues with Nougat. 3.0.2-3 is solid and bug-free. The forum you should probably be in is http://forum.xda-developers.com/showthread.php?t=3453119
Good luck.
Sent from my Nexus 6P using Tapatalk
Related
Hello,
I have a Nexus 10 (manta) tablet and made a full nandroid backup 10 days ago of the stock+root Android installation. I did that so I would be able to revert back to it if need be after trying out CM 10.1. I found that CM still required some refinement for manta so I wiped the system, did a factory reset and wiped the dalvic cache, then tried restoring the previous backup I made, of the stock system. The backup folder is 2.46GB big and the /data partition is split between two archives. When restoring, the system partition and first data archive seem to backup properly, but after that, the tablet reboots, omitting the second data archive which is pertinent for me to restore all of my apps.
I've installed the latest TWRP, version 2.4.0.0 just in case there was a bug.
How can I fix this and get my tablet back to normal?
Thanks XDA,
Spike
Note: My tablet isn't bricked, I can still boot to the stock rom after doing the incomplete restore but my apps are incomplete.
Edit: I've just updated TWRP to 2.4.1.0 and get a little farther this time. It begins restoring the second /data archive but still reboots during the process.
I'm currently having this issue. Did you ever get it resolved?
Sent from my Nexus 7 using xda app-developers app
I had the same problem, posted a day ago or so about it, but I used this http://forum.xda-developers.com/showthread.php?t=2121673 and now everything is all good. I just flashed the super wipe zip and then restored and it did NOT reboot during the restore.
Sent from my Nexus 10 using xda app-developers app
I had this problem as well. It was really pissing me off, I think it happens when you have a large backup. Anyways, I just kept trying it, and on the third time it worked for me. Maybe I just got lucky. When restoring it wipes everything anyways, but you can try wiping data, system, and cache beforehand and see if it helps.
Sent from my SCH-I535 using Tapatalk 2
My backups are 10GB+ each(I basically make full images to restore to for each ROM) and I never had this issue in the dozens of restores I've done. I always factory reset, wipe cache/dalvik, and then format system(wipe ROM) in that order before restoring the image. In a worst case scenario you can factory image the tablet if the restore fails after the stock ROM has been wiped.
Also you said two archives? My backups are just 1 folder with the 5 partitions and 5 md5 files?
I had this issue as well, after trying to restore from checking out the Ubuntu preview. Ended up giving up on it and enjoying as best I can the clean install. Would still like to restore it if possible though.
I was "finally" able to do a full restore of a backup. I had to break up the restore process though. First I restored system and boot. Once that restored I restored data and was able to get a full data restore as well.
Sent from my Nexus 7 using xda app-developers app
I was running teamub 1/11 and today a update rolled out (1/19) that multiple users have confirmed is causing a boot loop. I tried dirty flashing back to 1/11 but got weird issues. Either boot loop, or OS would boot but would just be a black screen with my time/bars/etc but nothing else. System wipe clean flash to 1/11 got the phone up and working but super bummed about the lost data.
I backed the data up from the phone, and was wondering if it would be possible to restore that data over my current install?
any advice is appreciated, thank you!
Hey,
I've had this problem for ages now, and always gave up on my data, but now I really want to fix this for good.
Yesterday I was ready to update my CM12 nightly to the lastest version (didn't see it was actually CM13), and did a backup in cwm before the update. The backup succeeded, but it gave the message that .android_secure couldn't be found and it didn't back that up. It always gives me this message after a backup and after google searching, it seems to me that it doesn't matter.
After installing the update, I noticed it was CM13, and my gapps wasn't updated to the marshmellow stock, as expected, so errors occured all the time.
I didn't want to upgrade to CM13 just yet, so I decided to restore my backup.
As always, the restore process goes without errors, but upon reboot I'm stuck at the CM logo. I can wait untill the battery is dead or ignites from the heat, but nothing happens. This has also happened to me every time I make a backup. I've watched about every video on youtube on how to do a proper backup and how to restore one, so I'm confident that I did it right.
For some reason, any backup I make, no matter what android version (didn't work with stock kitkat, either, before I switched to CM12) it never works and I'm forced to do a clean install and start over again.
I've tried to do partial restores from the backup file, and if I only restore the data partition (and wipe dalvik) It does boot, but gives me non stop errors that apps are crashing.
I've tried to do a dirty flash to no avail, always endless error messages.
When I do a clean install and check the MK5 of the backup with nandroid manager it gives no errors.
Is there anything wrong with my phone or something? I'm not making backups to be unable to restore them.
Can anyone help me out with this?
(I have a i9505)
Try a different recovery. CWM is outdated. TWRP is nice. Worked for ne every time. There are TWRP flashable zips so you won't have to mess around with Odin.
GDReaper said:
Try a different recovery. CWM is outdated. TWRP is nice. Worked for ne every time. There are TWRP flashable zips so you won't have to mess around with Odin.
Click to expand...
Click to collapse
Won't changing recovery make my old backups useless? I'm all for changing to TWRP, but first I'd love to restore my CWM backup...
Yes it will. Unfortunately I don't know what to suggest. Haven't used CWM since I switched to the S4.
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!
So... I installed LOS & it all went fine, but when I restored my MIUI backup with TWRP, the phone is stuck on the very first boot screen (on which it says Redmi by Xiaomi) & won't move any further. I've wiped the system, data & boot partitions yet no luck. What could be wrong? I want to go back to MIUI to backup my apps
it happened to me too.
when i done updating my device to newer nightly update, i got stuck on twrp decrypt data password. trying to restore back to miui, but then getting stuck on the very first boot screen.
i got no luck when trying several times restoring twrp recovery and miui, so i stay in LOS with no other options.
if someone could help please show me the guide.
thanks