[Q] Failed recovery of nandroid backup - why??? - Galaxy S 4 Q&A, Help & Troubleshooting

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

Related

CWM backups fail to restore

Hi all. First, forgive me if this has been questioned and answered before, but I face a really BIG BIG problem with my CWM made backups...
Regardless the are created right, and restored, the restored ROM gives me android.core.gapps errors continuously, rendering the phone unusable...
Maybe it's only my phone, I don't know, maybe CWM recoveries are young on my S4 variant and have bugs...
BTW: I own an S4 LTE Advanced (GT-I9506)
I have had the exact same issue. I have a Samsung note 2 N7105. I rooted made a backup in CWM and flashed ditto n3/s5 rom made another backup in CWM. No issues. Got a bit cocky seen as it was my first time doing anything like that. My next adventure was to try a custom kernel (agni). This didn't go so well, so I tried to do a restorw to my working backup of ditto n3/s5 rom through CMW. restore went smoothly and the phone booted. once I opened the lock screen I got the gapps error as described. I had to do a factory reset to get the phone working and then re-flashed ditto n3/s3. I've since flashed other roms and when ever I try to do a restore, I get the issue described. Note I am using the latest CWM. I putting off flashing and trying any other ROMs because of this issue. I do love dn3/s5 but id love to try others. Anyone can help it would be appreciate.

Fix for people with a corrupt EFS (No network connection or bluetooth)

A few people have had issues with the EFS getting corrupt or wiped on their OPO before they had a working backup. This guide has so far worked for 4 people to restore their EFS allowing them to access mobile data and bluetooth again.
Note: I really don't know why this works, I have contacted the dev of this rom to ask if he has any ideas but still waiting on a response.
1. Flash official TWRP
2. Flash this ColorOS rom using TWRP - http://forum.xda-developers.com/showthread.php?t=2772627 (you can skip all the account setups if you want)
3. Factory reset
4. Boot and setup ColorOS (you should see a network connect now with your sim card inserted, you will need to toggle mobile data on to test that)
5. If you have data in ColorOS you are good to flash back to CM11S anyway you want (you will need to factor reset after flashing back)
6. Save yourself the headache in the future and backup your EFS
Please post if this fix works for you.:victory:
Edit: I've went ahead and downloaded the ROM and I will hold on to it incase the original mirrors go down for some reason. Please PM me if they do.
One of the ones who can confirm this works. Will post in the official thread.
Worked for me also.
Wholy moly ... I have a mobile data network !!
Still on ColorOS, but this is VERY promising !!!
IMEI is correct, it's the one on the box !
Still no WiFi nor Bluetooh mac addresses, though...
Will keep you posted, but this is a HUGE step forward !
Thanx a lot for sharing this !
BTW, serial number is still unchanged and correct.
JP.
EDIT:
Unfortunately it didn't fix my issue, back to CM11S I am greeted by an AudioFX FC... Device pretty much unusable, the FC pops up the milisecond you click OK ...
Will try a different ROM...
EDIT 2:
SlimKat, CM11 Nightly both boot to the welcome screen, then reboot about 1 second later.
Only ColorOS seems to actually run ?!
A bit disgusted right now
tw1tch175 said:
A few people have had issues with the EFS getting corrupt or wiped on their OPO before they had a working backup. This guide has so far worked for 3 people to restore their EFS allowing them to access mobile data and bluetooth again.
Note: I really don't know why this works, I have contacted the dev of this rom to ask if he has any ideas but still waiting on a response.
1. Flash official TWRP
2. Flash this ColorOS rom using TWRP - http://forum.xda-developers.com/showthread.php?t=2772627 (you can skip all the account setups if you want)
3. Factory reset
4. Boot and setup ColorOS (you should see a network connect now with your sim card inserted, you will need to toggle mobile data on to test that)
5. If you have data in ColorOS you are good to flash back to CM11S anyway you want (you will need to factor reset after flashing back)
6. Save yourself the headache in the future and backup your EFS
Please post if this fix works for you.:victory:
Click to expand...
Click to collapse
Hi, i failed and i wiped EVERYTHING of my phone, i only had the fasboot mode, i installed CWM and the cyanogemod rom, now everything works, and i have the imei in the box, however, i dont have the possibility of EFS backup anymore.... any ideas..?
Gambalajillo said:
Hi, i failed and i wiped EVERYTHING of my phone, i only had the fasboot mode, i installed CWM and the cyanogemod rom, now everything works, and i have the imei in the box, however, i dont have the possibility of EFS backup anymore.... any ideas..?
Click to expand...
Click to collapse
Official TWRP doesn't have EFS backup in it, you have the get the unofficial one http://forum.xda-developers.com/oneplus-one/development/recovery-unofficial-twrp-2-7-1-0-t2815247
Yank555 said:
Wholy moly ... I have a mobile data network !!
Still on ColorOS, but this is VERY promising !!!
IMEI is correct, it's the one on the box !
Still no WiFi nor Bluetooh mac addresses, though...
Will keep you posted, but this is a HUGE step forward !
Thanx a lot for sharing this !
BTW, serial number is still unchanged and correct.
JP.
EDIT:
Unfortunately it didn't fix my issue, back to CM11S I am greeted by an AudioFX FC... Device pretty much unusable, the FC pops up the milisecond you click OK ...
Will try a different ROM...
EDIT 2:
SlimKat, CM11 Nightly both boot to the welcome screen, then reboot about 1 second later.
Only ColorOS seems to actually run ?!
A bit disgusted right now
Click to expand...
Click to collapse
Odd, maybe you could try using TWRP to delete everything again including system, then sideload and boot ColorOS.
tw1tch175 said:
Official TWRP doesn't have EFS backup in it, you have the get the unofficial one http://forum.xda-developers.com/oneplus-one/development/recovery-unofficial-twrp-2-7-1-0-t2815247
Click to expand...
Click to collapse
To add to that you can just boot the unofficial recovery using "fastboot boot recovery.img" to do your efs backup if you would prefer to keep the official TWRP installed. That way it only boots that recovery to allow you to do the backup of your EFS partition and doesn't erase your current recovery. That's how I did it.
sabbotage said:
To add to that you can just boot the unofficial recovery using "fastboot boot recovery.img" to do your efs backup if you would prefer to keep the official TWRP installed. That way it only boots that recovery to allow you to do the backup of your EFS partition and doesn't erase your current recovery. That's how I did it.
Click to expand...
Click to collapse
WOW thanks, i do it and and i tell you how did it go in a few minutes.
I see that the OP has been thanked and this thread has a few success stories so I am giving it a bump for others to view in case of the same issue.
I just flashed the factory image... I never had the problem again
Yank555 said:
Wholy moly ... I have a mobile data network !!
Still on ColorOS, but this is VERY promising !!!
IMEI is correct, it's the one on the box !
Still no WiFi nor Bluetooh mac addresses, though...
Will keep you posted, but this is a HUGE step forward !
Thanx a lot for sharing this !
BTW, serial number is still unchanged and correct.
JP.
EDIT:
Unfortunately it didn't fix my issue, back to CM11S I am greeted by an AudioFX FC... Device pretty much unusable, the FC pops up the milisecond you click OK ...
Will try a different ROM...
EDIT 2:
SlimKat, CM11 Nightly both boot to the welcome screen, then reboot about 1 second later.
Only ColorOS seems to actually run ?!
A bit disgusted right now
Click to expand...
Click to collapse
Im having the same problem as you have Yank555. It started with the AudioFX FCs rendering the device useless.
Next i tried to reflash the standard CM11s 25R rom back to get my phone normal again, it didnt work.
Then i remember i have a nandroid from a few days ago. Not thinking to read up on known issues with the OPO EFS i tried a restore.
My EFS is gone and the phone will not work unless im on ColourOs120. Wifi doesnt work, just basic phone functions.
Still waiting for a miracle for this problem.
Any suggestion guys?
jwai85 said:
Im having the same problem as you have Yank555. It started with the AudioFX FCs rendering the device useless.
Next i tried to reflash the standard CM11s 25R rom back to get my phone normal again, it didnt work.
Then i remember i have a nandroid from a few days ago. Not thinking to read up on known issues with the OPO EFS i tried a restore.
My EFS is gone and the phone will not work unless im on ColourOs120. Wifi doesnt work, just basic phone functions.
Still waiting for a miracle for this problem.
Any suggestion guys?
Click to expand...
Click to collapse
Did you open a service request ? Any response ? So far all I got 5 days later was a "please fastboot flash factory images, case closed." which quite obviously did not help, so case reopened, but again nothing from them in 4 days, now.
But I wonder if my first thought is still correct, flawed emmc as flashing seems to work ... might be a radio hardware issue ? Just don't quite get what the AudioFX has to do with that... cause simply rooting the device and installing apps and making a few nandroid backups is no way to brick anything.
But anyway, tbh, OnePlus is mostly dead to me as a company, worst invest ever so far, nice if your device works, but service is not even close to bad, it's pretty much non-existing ... and for a supposedly "best service ever" it's quite, let's say, "impressing"
JP.
Nope, i have not tried opening a ticket, mine is a grey import from China.
There is something terribly wrong somewhere hardware wise. The audiofx problem only happens if i flash the CM11s. After ColourOS i have tried flashing the CM11 M8.
Im also wondering if i should try to use this OPO made rom to see if it can help.
https://forums.oneplus.net/threads/rom-official-4-4-4-oneplus-aosp.65482/
jwai85 said:
Nope, i have not tried opening a ticket, mine is a grey import from China.
There is something terribly wrong somewhere hardware wise. The audiofx problem only happens if i flash the CM11s. After ColourOS i have tried flashing the CM11 M8.
Im also wondering if i should try to use this OPO made rom to see if it can help.
https://forums.oneplus.net/threads/rom-official-4-4-4-oneplus-aosp.65482/
Click to expand...
Click to collapse
Give it a go, not much to lose. Didn't work for me, though.
JP.
Sent from my Nexus 5 running stock rooted AOSP on Yank555.lu v1.0-alpha5 kernel.
This worked for me! I'm back in business! Thanks guys for getting this figured out, I thought my phone was done.
I hate to bring this back up.
I have a Nandroid of my stock CM11S on my phone. I used it for the update to 300 to get firmware, then made a backup of it and went back to the custom Rom I had been on.
Today, I went and restored the backup of CM11S to sideload the newest update. Weirdly, after restoring I have an unknown baseband. But if I go back to the custom Rom backup I still have a baseband.
I wonder if TWRP just didn't backup the correct partitions? I am on the offficial TWRP. But I do have a backup that contains my EFS backup from the other TWRP that has that option.
I think I know what corrupted my efs....I used the official twrp 2.7.1.1 which for some reason saves modemst1. I remember restoring st1 when I corrupted it the first time with the official 2.7.1.1. Well I did it again trying to restore a nandroid with the official twrp 2.7.1.1. Do not restore the saved modemst1 from the official twrp 2.7.1.1. You will encounter problems.
So, this same thing happened to me...i happily using 30O and not really any issues and getting good battery life~17 hrs w/moderate use. And no other bugs.
Found the 33R update here on the forums and downloaded it and flashed through TWRP.
Thats when trouble found me, lost network and wifi stuck trying to turn on but never finds wifi. Then reading through xda someone suggested to check IMEI and it was gone. I had NOT done any prior back ups other than Nandroid prior to flashing update.
Restore still didn't fix it.
I tried this (flash ColorOS and CM11) but still didnt fix it. I was bummed as my OPO is very new and I had been happy with it.
CM11 or by restore, windows will not detect it even with drivers loaded. Flashing colorOS would allow windows XP to recognize internal and allow me to send files so i tried custom ROMs and CM stock and Mahdi but none worked. Luckily my TWRP still works and i am able to boot and get into fasboot.
I finally got mine fixed with rooted stock 33R from here on xda!
Now my OPO is back in business!!!
Save st1 and st2 with vonnegut's method http://forum.xda-developers.com/showthread.php?p=54623075.. Put it in a safe place for later. I uploaded them to google drive and onedrive . It saved me today.
For those of you that were able to recover, did you lose your entire EFS folder? Mine is completely gone and I don't think this ColorOS trick works either. I've tried it all last night and I fell asleep at my desk

[Q] Galaxy S5 android 5.0 and recovery

Hi guys
I'm using samsung galaxy S5 (4.4.2) and recently upgraded to 5.0 using custom rom which I found here. It was working just great. I created 2 Nandroid using TWRP. One after a fresh installation another one after restoring my file contents from Helium and Titanium backup..
However something went wrong and i decided to restore my nandroid backup to revert back my changes. To my surprise both nandroid backup failed. I got a success message (using recovery mode) however when i reboot my phone im getting tons of messages like "System failed to start" "process failed to start" wait or press ok.
When I reflash the custom rom, it works fine, however i couldnt recover my system from nandroid backup.
I repeated several times but both nandroid gave me this same error. I even tried fixing permissions but no use. Then I used odin to flash a stock rom (BOA3) and rooted that using TWRP and most recent SU binaries. Its working great now, however I just wanted to know what is the best method to take a nandroid backup now? I'm afraid TWRP will bail out on me once again.
All the while I used CWM and it was great however 5.0 requires latest binaries and only can be rooted via TRWP recovery. Any suggestion? I just want to take a complete nandroid backup and save it in case if something goes wrong.
Thanks
sam20e said:
when i reboot my phone im getting tons of messages like "System failed to start" "process failed to start" wait or press ok.
Click to expand...
Click to collapse
I'm being plagued by this problem since I updated, flashing stock Lollipop using odin.
The problem first appeared after trying to restore my app+data using Titanium.
I went back to the beginning and flashed again but my phone is still unstable and I still occasionally get the '"System failed to start" "process failed to start" wait or press ok' issue that you have. A reboot generally sorts it out but the update has made my phone very unstable.
I also have big problems entering recovery and download modes using the buttons.
Cleaning my cache/davlik hasn't solved it either.
Hopefully someone can help us.
Anyone?
Got "Reactivation Lock" disabled?
Settings > General > Security
*Detection* said:
Got "Reactivation Lock" disabled?
Settings > General > Security
Click to expand...
Click to collapse
Yes. Thanks for the suggestion though.
Trouble in Galaxy town
Hi, I'll try make myself short.
1) Back when I had an Galaxy S2 i modded it a little bit but I haven't done it at all since then.
2) Now a few years later I got bored/sick of the stock ROM that comes with the S5 so I wanted to install something I knew had a good reputation, Cyanogenmod.
3) Getting a new recovery was an nightmare itself but eventually I got it working and made an backup so I could roll back if needed to.
4) Now, 24 hours of using CM12 I can only say one sentence: "What kind of crap is this?!" It's so unstable it's almost ridiculous. Bluetooth hangs up all the time thus requiring a reboot which leads to most-annoying-thing-ever-#2. The clock resets itself upon EVERY boot which makes WhatsApp go bananas. Doesn't matter if I previously set the time/date manually or let the phone do it automatically. Then there are the random hang ups that occur all the time and one third thing. Hardware acceleration in BS Player doesn't work AT ALL!
5) Said and done I reversed to the back up but oh man the phone wasn't happy about this (yes I made a wipe before recovering the backup). Nearly every basic service malfunctioned and were forcibly shut down. A factory reset made no difference...
6) For some reason I opened KIES and found out that an update with android lollipop was available so I (in a moment of despair) installed that hoping for salvation.
7) The phone boots properly and everything seems to be going wonderful until I realize that my network connection is high on something. Loses connectivity to my provider all the time thus the phone is totally useless.
8) I HAD to have a working phone for work and since no support is given on Sundays from Samsung I again installed CM12 just for the day.
Now to the good part!
9) When trying to recover the backup once again it's gone corrupt! Can't recover so now I'm stuck with buggy-as-h*ll-cyanogemmod12 with no means of reverting.
What-the-actual-****-do-I-do? Been trying to make some sense from the thread "Galaxy S 5 Original Android Development" but I feel so lost. So if someone could point me in the right direction I would be very grateful!
EDIT: What I want is to reverse back to original stock ROM. Screw the bloatware. I just need the phone stable and working!
EDIT2: After some more googeling I've figured out I need a stock ROM with the right CSC. I use a swedish carrier other than 'tre'. Shall I look for ROMs with CSC 'HTS' anyway? Can't find any info about other carriers in sweden.
EDIT3: Now I've found what I think is right on sammobile.com/firmwares/database/ (search query: 'g900f', first hit 'Sweden' CSC 'VDS'). Worried thou as it's Android Lollipop which made my phone go nuts. Can't find the KitKat version on that site...
EDIT4: Found the KitKat version on samsung-updates.com. The download speed is sooooooo slow (~6 hours)! Download limits should be illegal...
Thanks! //R

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

[HELP] Stuck in Boot Animation

I encounter this many many times especially on Custom ROM.
The problem occur always occuring when my phone turned off because of empty battery, and charged it so I can open it up. This occur always in different Custom ROM. Always got stuck on Boot Animation. The only solution I found is wiping my data. But I'm so sicked and tired of backing up my whole rom using TWRP and restoring my Messages backup using Titanium Backup(because the apps can't be restored using Titanium Backup if you back it up using TWRP) so anyway, if you have encounter this kind of issue and have a better solution to fix this without wiping like using ADB, accessing system, logs to see what is the real problem of this kind of problem and so on.
Will be much appreciated
Flash a different ROM, or move to stock? Or don't let your battery run out completely?
Every custom rom i tried occur problem like this. I'm really not fond of Stock Rom so no. I already tried that but sometimes I keep forgetting it. It's still not a permanent solution
Well if you're not willing to try stock, sorry, can't help

Categories

Resources