Database Users

[Q] Failed recovery of nandroid backup - why???

Hi all,
Some time ago i asked, and received, some support on these forums on how to properly carry out a nandroid backup... following the sound advice i got, i carried out my backup (using TWRP for the record, with all the options checked), and stored it away for a rainy day... said day came yesterday, when i messed up my system and rendered it instable (i tried to manually delete the dalvik cache directory in order to free up the 2,5GB of space it was taking)... since i knew there was i high chance of this ending in disaster, the last thing i did before the delete was carry out another nandroid, so i could easily return to where i had left off... how wrong i turned out to be
as soon as i the system became instable following my experiment of deleting the d. cache directory, i recovered the latest nandroid (i.e. the one i had made just hours before) and everything seemd to go smoothely until the first reboot... when the following happened:
- first reboot after recovery took ages, much like the first reboot following the flashing of a new rom... not the end of the world, but that was the first sign that all was not well
- the status bar disappeared, and there was no way of making it come back (i.e. nothing to do with the launcher, i typically use apex but i i tried switching to both nova and touchwiz which i also kept up to date but the stats bar was nowhere to be seen)
- even if not having a status bar with all the info on it is acceptable (which of course it isn't, but lets just say), the sytem became completely instable after 5minutes of operation... with each app taking turns to shutting down until i kept getting the message "system UI has closed" over and over, to the point that doing a reboot was challenging since i barely had the time to press on the screen between instances of this bloody error message appearing...
...i did of course try and return to my older nandroid backup, but... lo and behold... exactly same behaviour...
so now i have resorted to formatting the internal memory card and flashing a new rom and basically starting over... just what i hope the nandroid would spare me basically :/
question is: does this sort of error sound familiar to anyone? can someone give me a tip maybe on what i may have done wrong?
any opinion, tips& advice much appreciated

I have the exact same problem. It happens on TW Lollipop ROMs. Haven't found a fix. I'm using Philz Touch Recovery and the old no knox bootloader.

Anyone? I have researched this but cannot find any similar problems reported... it can't just be me and pavelcheto...

Maybe it a recovery fault. Faulty backup or faulty restore.

No problems with my older backups. I restored my KitKat TW backup, working fine. Restoring CM12 backups also works fine. I've looked for a new recovery, Philz is discontinued, CWM hasn't been updated for a year and I really don't like TWRP.

I use TWRP 2.8.3.0 and never have (and hopefully never will) encountered any issues with restoring backups.

Considering i recovered 2 separate backups for a total of 3 times (i tried recovering the first backup twice) i doubt the issue was with the recovery itself... however since pavelcheto had no issues with the kk recovery maybe it could be lollipop related?
Anyone successfully recovered a lollipop nandroid backup?

platypus78 said:
Considering i recovered 2 separate backups for a total of 3 times (i tried recovering the first backup twice) i doubt the issue was with the recovery itself... however since pavelcheto had no issues with the kk recovery maybe it could be lollipop related?
Anyone successfully recovered a lollipop nandroid backup?
Click to expand...
Click to collapse
I recovered my lollipop gpe backup a couple of times without a problem.
Data encryption may cause restoring problems.

I have restored CM12 backups (based on 5.0.2) serveral times, no problem there. I've had issues only with TouchWiz Lollipop ROMs, I have tried different custom roms, all get bugged at restore.

pavelcheto said:
I have tried different custom roms, all get bugged at restore.
Click to expand...
Click to collapse
Just to make sure I understand correctly : you mean all TW custom roms you've restored have had problems?
Wonder if anyone else has managed a bug-free restore of a 5.x TW?

Yes, but only on Lollipop. KitKat TW roms restore just fine. I am using Philz Touch Recovery. I have tried 3 different TW Lollipop roms and they all fail to restore properly. No wallpaper, black wallpaper and no status bar. And after a minute or two System UI starts crashing. If then I do factory reset from recovery and the rom starts normally (welcome guide and stuff) and works fine.

bumping this thread because i cant seem to find a solution for this anywhere.

TheAwesomeBit said:
bumping this thread because i cant seem to find a solution for this anywhere.
Click to expand...
Click to collapse
There's no solution for this as per comments above. TW LP is not restorable. You can flash a new lollipop ROM tho'
Sent from my GT-I9505

TWRP Restore

I apologize if this is already covered in another thread. I wasn't able to find anything.
I am having an issue with restoring a backup I created in TWRP. I backed up only System and Data. I was able to restore one backup but then realized I forgot to remove my lock screen security (I have since found a way to fix this issue in another thread). Then when I tried restoring a different one, backed up the same way, I got a bootloop. I got the bootloop with two different backups.
I let it sit for about 10 minutes on the boot animation. Do I need to wait longer?

bretrick30 said:
I apologize if this is already covered in another thread. I wasn't able to find anything.
I am having an issue with restoring a backup I created in TWRP. I backed up only System and Data. I was able to restore one backup but then realized I forgot to remove my lock screen security (I have since found a way to fix this issue in another thread). Then when I tried restoring a different one, backed up the same way, I got a bootloop. I got the bootloop with two different backups.
Also, when starting the restore it gave me the option to restore Data, System, and EFS. I only checked Data and System. Is that correct?
I let it sit for about 10 minutes on the boot animation. Do I need to wait longer?
Click to expand...
Click to collapse
I feel your pain. Many people have the same restore problem, and it is unclear to me ( from reading) how to get the recovery working well so one can go back and forth between several roms, including a stock rom. Dees Troys' instructions, for first time Omnirom installers, states that once TWRP is installed, you not only do the TWRP factory reset, but you must format the data partition if you previously had a stock encrypted rom on your device. You will lose all data if you do this, but I think this is the only way to have a fully functional TWRP recovery. I haven't tried this yet, but probably will when I have hours of spare time.
bretrick30 said:
I apologize if this is already covered in another thread. I wasn't able to find anything.
I am having an issue with restoring a backup I created in TWRP. I backed up only System and Data. I was able to restore one backup but then realized I forgot to remove my lock screen security (I have since found a way to fix this issue in another thread). Then when I tried restoring a different one, backed up the same way, I got a bootloop. I got the bootloop with two different backups.
I let it sit for about 10 minutes on the boot animation. Do I need to wait longer?
Click to expand...
Click to collapse
Sent from my Nexus 6P using Tapatalk

Nandroid Backup Issue

Hello Nexus 6P Users,
today i tried to flash Cyanogenmod on my Huawei Nexus 6P.
Before doing this, i used to backup my data with TWRP. (Nandroid)
I copied the backup on my PC and flashed CM. After that, i wanted to go back to stock.
So i restored with backup. Now the problem:
Since Android 6.0 (I think) you can adjust, that you have to put in your Code/Password/Pattern.
Nandroid changed mine. I don't know why. There is NO way to bypass this code.
So i had to flash the FactoryImage, and now, my data is wiped .
Did one of you had the same Issue?
markus

markus2801 said:
Hello Nexus 6P Users,
today i tried to flash Cyanogenmod on my Huawei Nexus 6P.
Before doing this, i used to backup my data with TWRP. (Nandroid)
I copied the backup on my PC and flashed CM. After that, i wanted to go back to stock.
So i restored with backup. Now the problem:
Since Android 6.0 (I think) you can adjust, that you have to put in your Code/Password/Pattern.
Nandroid changed mine. I don't know why. There is NO way to bypass this code.
So i had to flash the FactoryImage, and now, my data is wiped .
Did one of you had the same Issue?
markus
Click to expand...
Click to collapse
There is a thread already about TWRP and lockscreen security:
http://forum.xda-developers.com/nexus-6p/general/psa-twrp-backups-lockscreen-security-t3245070

Thanks man. I didnt See this.

Help please! S8 bricked after downgrade attempt following OTA update

I have a Samsung s8 snapdragon 950U, T-mobile, running android 7.0, baseband - G950USQU2BQK5, build - nrd90m.G950USQS2BQL1. A couple weeks ago the mic stopped working so that I could not use speech-to-text which I rely on heavily. Nothing fixed it until I reflashed the phone with the same firmware. Before that I performed a ROM backup using clockworkmod and moved the backup files to my computer. I also used Titanium to backup system data like sms messages. After that, just as I was going to restore data, I get TMobile message that I’ve never seen before about a firmware update. I figured if it’s Oreo the update would fail because I have a custom ROM. Stupidly I chose to update and the next thing I know I have Android 8 – NOT rooted. That prevented me from using Titanium to restore settings.
Stupidly again, I decided to go back to the android 7 firmware and proceeded to root and flash the phone as I did before. This time it failed. I tried the SAMPWN and SAMFAIL methods repeatedly without success. Now I have bricked phone that just loops through a screen that says “Installing system update” followed immediately by another blue screen with a defunct android that says “no command.” I can get to download mode which Odin sees, but not to recovery, or anything that Smart Switch(which isn’t so smart) sees.
I have been downloading the Oreo firmware G950USQU4CRE9_G950UOYN4CRE9 for the past 4 hours hoping that I can maybe flash that. HELP! Can I somehow restore the nandroid backup using my computer? What should I do. I just need a working phone or I’m in big trouble.

frankygoes said:
I have a Samsung s8 snapdragon 950U, T-mobile, running android 7.0, baseband - G950USQU2BQK5, build - nrd90m.G950USQS2BQL1. A couple weeks ago the mic stopped working so that I could not use speech-to-text which I rely on heavily. Nothing fixed it until I reflashed the phone with the same firmware. Before that I performed a ROM backup using clockworkmod and moved the backup files to my computer. I also used Titanium to backup system data like sms messages. After that, just as I was going to restore data, I get TMobile message that I’ve never seen before about a firmware update. I figured if it’s Oreo the update would fail because I have a custom ROM. Stupidly I chose to update and the next thing I know I have Android 8 – NOT rooted. That prevented me from using Titanium to restore settings.
Stupidly again, I decided to go back to the android 7 firmware and proceeded to root and flash the phone as I did before. This time it failed. I tried the SAMPWN and SAMFAIL methods repeatedly without success. Now I have bricked phone that just loops through a screen that says “Installing system update” followed immediately by another blue screen with a defunct android that says “no command.” I can get to download mode which Odin sees, but not to recovery, or anything that Smart Switch(which isn’t so smart) sees.
I have been downloading the Oreo firmware G950USQU4CRE9_G950UOYN4CRE9 for the past 4 hours hoping that I can maybe flash that. HELP! Can I somehow restore the nandroid backup using my computer? What should I do. I just need a working phone or I’m in big trouble.
Click to expand...
Click to collapse
update: i was able to flash the oreo firmware basically puts me back at step 2. becasue i backed up when rooted my backups now cannot be restored, or can they, at least in part? Is there any way i can restore some of the data in either the nandroid or titanium backups to my nonrooted oreo s8?

No Sim on Pie but works fine on Oreo backup??

Hi all
So i installed AICP 14, all worked fine, wanted Dt2W so put Fk r77 kernel on and within an hour i got a reboot while talking on the phone, then a strange error with my keyboard not working (not sure if both problems were kernel related but never had them before).
I had done a twrp backup before installing the kernel so i thought i can live without Dt2W i restored from the backup, BUT this i when i realised i had fkd up because i hadn't taken off my pattern lock before doing the backup.....so the restore didnt work(got an error at end of running the restore and phone hung on google screen)
So luckily i still had my Oreo back up, restored that and that works fine.
But now when i try a fresh install of any Pie rom (Tried AICP and RR) the sim card isnt detected? Did i quick google yesterday and ran some #*#*4636*#*# service code which reported there was no IEMI number?
So is it a EFS partition problem?
Tia.

r3k0 said:
Hi all
So i installed AICP 14, all worked fine, wanted Dt2W so put Fk r77 kernel on and within an hour i got a reboot while talking on the phone, then a strange error with my keyboard not working (not sure if both problems were kernel related but never had them before).
I had done a twrp backup before installing the kernel so i thought i can live without Dt2W i restored from the backup, BUT this i when i realised i had fkd up because i hadn't taken off my pattern lock before doing the backup.....so the restore didnt work(got an error at end of running the restore and phone hung on google screen)
So luckily i still had my Oreo back up, restored that and that works fine.
But now when i try a fresh install of any Pie rom (Tried AICP and RR) the sim card isnt detected? Did i quick google yesterday and ran some #*#*4636*#*# service code which reported there was no IEMI number?
So is it a EFS partition problem?
Tia.
Click to expand...
Click to collapse
Very likely corrupt radio. Try reflash stock rom before trying top flash a pie rom

ok, downloaded the last stock from google, twrp gave an error when trying to install it? wrong kind of zip ?

r3k0 said:
ok, downloaded the last stock from google, twrp gave an error when trying to install it? wrong kind of zip ?
Click to expand...
Click to collapse
Late Reply...Just Read it today
Stock factory files can be flashed through fastboot don't you know that?
And your problem got solved or not?