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!
Related
My Nexsus 4 was at 5.0.1 updated OTA, I rooted and installed recovery and created a nandriod backup on the internal SD card. The phone was working fine for the most part except it was having issues with the screen going black when making a call and would not come out of that state. I wanted to revert back prior backup so I did a nandriod restore with CWM v6.0.4.7 and now my phone is in a bootloop. I've tried wipe data/factory reset, also tried wipe cache partition, but still stuck in bootloop. I'm not sure what else I can do to get out of this bootloop state/ Any suggestions would be greatly appreciated.
Fixed it by using Nexus Root Tool Kit to flash stock image. Not sure what happened but I'm switching to TWRP. First time using CWM and things didn't work out well for me using it.
Guys,
I have an S5 running Cyanogen Lollipop and Philz Touch 6.26.2 as the recovery. I was experimenting with flashing a new camera .ZIP earlier today but BEFORE doing so I used Philz to create a backup. The flash of the .zip for the camera went wrong and ended up prompting the phone to hang on boot.
I booted into Recovery and restored my backup...restarted the phone and it then booted as normal BUT as soon as Android had booted, it was unusable as I just kept getting the "##### has stopped" error messages, one after the next - the launcher doesn't appear and the phone is completely unusable.
I have tried a 'Factory Reset' and wiping the Dalvik cache, on boot it optimises all apps but then does precisely the same.
Please help as I'm travelling tomorrow and need to sort this tonight!!
Cheers
sergeantash said:
Guys,
I have an S5 running Cyanogen Lollipop and Philz Touch 6.26.2 as the recovery. I was experimenting with flashing a new camera .ZIP earlier today but BEFORE doing so I used Philz to create a backup. The flash of the .zip for the camera went wrong and ended up prompting the phone to hang on boot.
I booted into Recovery and restored my backup...restarted the phone and it then booted as normal BUT as soon as Android had booted, it was unusable as I just kept getting the "##### has stopped" error messages, one after the next - the launcher doesn't appear and the phone is completely unusable.
I have tried a 'Factory Reset' and wiping the Dalvik cache, on boot it optimises all apps but then does precisely the same.
Please help as I'm travelling tomorrow and need to sort this tonight!!
Cheers
Click to expand...
Click to collapse
Backup restore also system apps and sometimes there are problems. I think you must flash the rom without backup.
davyleggend said:
Backup restore also system apps and sometimes there are problems. I think you must flash the rom without backup.
Click to expand...
Click to collapse
Ok, this has given me an idea - I have flashed fresh Cyanogen and now I'm attempting to restore just the 'data' and 'cache' elements of my backup by using the Philz 'Custom Restore' feature...fingers crossed!
So, my idea worked...my phone is now back up and running, what a relief!
I just got a s5. And I got it succesfully rooted and also got TWRP working on it.
All the data from my previous phone was transfered to the s5.
Now I made some backups with TWRP with the default settings: Partitions boot, system and data.
With the backups in mind I was thinking I could easily restore it to a previous state.
Thinking I backed up all the data and wanted to make it fresh again, I wanted to restore it.
In the menu I chose the restore option with the same settings as the backup: Partitions boot, system and data.
And it gives a message restoring system succesfull.
But when rebooting, it keeps hanging and at the moment of loading the android system every bit of the system keeps 'hanging'
It keeps saying
'Unfortunately touchwiz startup unsuccesfully'
'Unfortunately youtube startup unsuccesfully'
'Unfortunately greenify startup unsuccesfully'
'Unfortunately app whatever startup unsuccesfully'
And so on and so on
Eventually it starts with a black screen with nothing loaded. Complete blackout.
So this backup doesn't work. And I try my second backup.
Unfortunately also the second backup gave these errors.
And also the third backup!
So the backup files seem the right size, it's some gigabytes, and it alway's keeps saying backup/restore succesfully.
But now it fails to restore and boot the backup
The things I tried.
-Trying three different backups
-Wiping cleaning data/dalvik/cache etc etc
-Restoring a part of the backup. First system, then data, then boot, no succes.
So i'm totally lost! Does somebody know how to fix this? Or have some tips to try??
You can't restore system and boot from a different model phone
That would be like trying to flash a ROM for one model phone to another without porting it
If it was an S5 you backed up, was it the exact same model (ie: G900F etc?)
Flash back to stock, then try restoring only DATA
Or use TiBu to restore your apps from the TWRP backup
*Detection* said:
You can't restore system and boot from a different model phone
That would be like trying to flash a ROM for one model phone to another without porting it
If it was an S5 you backed up, was it the exact same model (ie: G900F etc?)
Flash back to stock, then try restoring only DATA
Or use TiBu to restore your apps from the TWRP backup
Click to expand...
Click to collapse
Thanks for the reply! It was a backup and restore on the same phone. So that is why I thought it was supposed to be a easy restore.
But I found the solution hidden somewhere in one message on XDA:
"Originally Posted by Dr. Fed
Would you happen to know why, when restoring a TW 4.4.2 nandroid using TWRP 2.8.1 or 2.8.4, after running an AOSP lollipop ROM like CM12, the TW ROM boots but then the whole system force-closes? Before restoring the nandroid, I advance wipe system, data, cache, and dalvik. Then I restore the nandroid. It boots, but then some daemon crashes. Then all processes and apps. The screen goes black after a few crashes.
So, what I do is pull out the battery, boot into recovery, advance wipe system, data, cache, dalvik, flash a CM11 ROM, reboot. I let CM11 start up, skip the set-up, then I boot back to TWRP (2.8.1 and now 2.8.4), advanced wipe, restore TW nandroid, and now it works just fine.
It seems like TWRP doesn't fully wipe."
Here the steps for if other people will run into the same problem:
Problem: Android 5 is running, with twrp 2.7 performed a back up = Restoring the backup is difficult because it problably doesn't do a clean wipe somehow.
1. I downloaded a cyanogen 11 rom, a Android 4 version.
2. Installed it with TWRP. Somehow it 'wipes' it more efficiently.
3. From cyanogen 11 back to booting TWRP.
4. In TWRP trying the Android 5 restore.
And Amazingly this worked!! = Celebrate!!
chokolademan said:
Thanks for the reply! It was a backup and restore on the same phone.
Click to expand...
Click to collapse
Confused me with this line
chokolademan said:
All the data from my previous phone was transfered to the s5.
Click to expand...
Click to collapse
Good to see you solved it
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
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?