Related
I know that many of you has faced problems with restoring stock touchwiz 4.4.2 rom.
But, after reading in these forums i've found the right way to restore your backup
I used twrp and i didn't tested it on cwm recovery.
So follow me.
First, boot in recovery and restore everything you have backed up except DATA and Boot
Then, boot your device and set it up and reboot in recovery again and restore your DATA and Boot
Voilà that should work i tested it with my s3 neo it really works.
Help me by pressing thanks.
ziad311 said:
I know that many of you has faced problems with restoring stock touchwiz 4.4.2 rom.
But, after reading in these forums i've found the right way to restore your backup
I used twrp and i didn't tested it on cwm recovery.
So follow me.
First, boot in recovery and restore everything you have backed up except DATA and Boot
Then, boot your device and set it up and reboot in recovery again and restore your DATA and Boot
Voilà that should work i tested it with my s3 neo it really works.
Help me by pressing thanks.
Click to expand...
Click to collapse
Thank you, you saved me hours of time!
If you dont have backup you must use ODIN and download the firmware from sammobile. It's not worth because original firm is slow and has heating problems.
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.
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
Hi experts,
I would very much appreciate some help regarding the following:
I have a Samsung Galaxy S5 SM-G900F with factory installed stock rom G900FXXU1BPA2 (Android 5.0). I used the SkipSoft Unified Android Toolkit 1.4.5 to root the phone and install TWRP recovery (2.7.1.0-klte as recommended by Unified Android Toolkit). I made a first Nandroid Backup and was able to successfully restore this backup (I restored boot, system and data to verify that Nandroid restore works). I then used Titanium Backup to restore my apps from another phone, and all was well.
A week or so later I wanted to modify something I wasn't sure I wanted to keep (using apktool). I therefore made a second Nandroid backup and then proceeded to make modifications to the phone. After I saw the result, I didn't like it, and therefore restored the second Nandroid backup. After rebooting, the phone gave a flurry of forced stops ("Unfortunately XXX has stopped"). It is not a bootloop but I can't do anything meaningful with the phone other than restart it.
To try and resolve this, I used TWRP to wipe cache and dalvik cache and rebooted. The phone went through the lengthy "Android is upgrading" process but the result was the same: all my apps force stop.
I then decided to try and restore the original first Nandroid backup (which I had been able to restore successfully earlier), and this resulted in the same issue. Since I have several backups of this first backup I was able to verify that the files were good. Also did MD5 checksum verification in TWRP and it all checked out.
Using Odin, I was able to restore a stock ROM from SamMobile (G900FXXU1BOL1_G900FOJK1BOL1_ILO) and after restart, the phone works as usual, but of course all my apps and data were gone.
I was then able to use TWRP to restore only boot and system from the second backup, so I would be back on the exact same ROM that my phone came with, and this worked just fine; the phone started as if factory restored.
I then used TWRP to restore only data, and this resulted again in the same problem: all apps force close. Note that this is a restore of data only to the same phone running the exact same ROM that the Nandroid backup was made on, and it still did not work.
I have been thinking about this issue and searching through the various forums but I did not find anyone having this same exact issue. Here are some questions I came up with:
1. Is TWRP 2.7.1.0 completely compatible with this phone and with Android 5.0? Would it help if I installed a newer version of TWRP? Would I be able to restore Nandroid backups made with TWRP 2.7.1.0 with TWRP 3.X?
2. Assuming my second Nandroid backup is not corrupt, is there a better (less intrusive) restore I can do of the apps? Can Titanium Backup read TWRP 2.7.1.0 backups and restore them, including SMS?
3. What could be the reason for TWRP 2.7.1.0 restore not to be working properly? I did activate the fingerprint reader after the first Nandroid Backup, but if that is the issue I would have expected that first backup (in which fingerprints were not yet enabled) to restore properly and it doesn't.
Would appreciate any help!
Thanks,
AH
That version of TWRP is pretty old, possible it doesn't fully support 5.0
Grab 3.0.0.0 from here (newer versions are not fully bug free yet)
https://dl.twrp.me/klte/
Flash .tar version with ODIN 3.10.7
TiBu can read Nandroid backups and restore apps yes
Not sure about SMS
The method you used to root and flash TWRP is not a usual method used here, most of us use ODIN to flash TWRP and then flash SuperSU from recovery
or use CF Auto Root to root, and then flash TWRP with ODIN
I'd flash stock again, factory reset, and then flash TWRP and SuperSU, then try restoring your apps with TiBu
*Detection* said:
That version of TWRP is pretty old, possible it doesn't fully support 5.0
Grab 3.0.0.0 from here (newer versions are not fully bug free yet)
dl.twrp.me/klte
Flash .tar version with ODIN 3.10.7
Click to expand...
Click to collapse
Thanks *Detection*! I installed TWRP 3.0.0.0 as per your instructions and restored just data. Same result as before.
Then I used TWRP 3.0.0.0 to restore the entire backup including system, boot, recovery, and data. Same result (of course I lost TWRP 3.0.0.0 and was back on TWRP 2.7.1.0).
This exercise was useful for one reason: I now know that TWRP 3.0.0.0 is able to read Nandroid backups from TWRP 2.7.1.0.
This is quite crazy but I seem to be unable to restore a full Nandroid backup and get a working system.
Am going to try Titanium Backup.
Thanks again!
AH
I'm having issues with restoring the factory image of stock Android 6.0.1, I'm using
@Heisenberg guide to create the fresh back up image on TWRP-3.0.2-0. Once I create
the back up, I boot into the OS and perform a factory reset, when i do that the phone resets
into TWRP, and performs the wipe to the device, when i go to do the restore, it freezes
at about 39%, and reboots fully trying to enter the OS, but its corrupt due to TWRP restarting
in the middle of the recovery.
I did at one point upgrade to Android N, but reverted back to android 6.0.1 if that makes a difference.
TL;DR - Created a fresh factory image of 6.0.1 using TWRP, cannot recover with it, TWRP freezes at 39% every time.
What options are you selecting to backup/restore?
Heisenberg said:
What options are you selecting to backup/restore?
Click to expand...
Click to collapse
I'm doing a back up selecting the system/data/boot/vendor boxes, leaving everything else unchecked, and a second back up with only the EFS,
When i go to restore, I'm just using the first back up, leaving the EFS alone unless ever needed, and am selecting the system/data/boot/vendor boxes
DeathSentinels said:
I'm doing a back up selecting the system/data/boot/vendor boxes, leaving everything else unchecked, and a second back up with only the EFS,
When i go to restore, I'm just using the first back up, leaving the EFS alone unless ever needed, and am selecting the system/data/boot/vendor boxes
Click to expand...
Click to collapse
I can only think that your backup is corrupt. Also, instead of booting into Android and performing a factory reset that way, just go into the advanced wipe section of TWRP and wipe only data. Maybe you'll just need to flash the factory images to get the phone booting up fresh again.
That's where it gets interesting, I've flashed the factory 6.0.1 image, then flashed twrp, created the back up again, did the advanced wipe as you said, did the restore again, and same result, at around 39% of the recovery the phone reboots and the back up gets corrupt. My main goal is to make sure this back up absolutely works before I root and start playing around with flashing xposed modules, but I'm unable to do a successful restore for the life of me.
DeathSentinels said:
That's where it gets interesting, I've flashed the factory 6.0.1 image, then flashed twrp, created the back up again, did the advanced wipe as you said, did the restore again, and same result, at around 39% of the recovery the phone reboots and the back up gets corrupt. My main goal is to make sure this back up absolutely works before I root and start playing around with flashing xposed modules, but I'm unable to do a successful restore for the life of me.
Click to expand...
Click to collapse
I'm stumped, I really don't know why it wouldn't be working if you're performing the backup the way you say you are. Sorry I can't be more helpful. If it's any consolation, a backup probably isn't strictly necessary because you can always get back to stock by flashing the factory images.
Heisenberg said:
I'm stumped, I really don't know why it wouldn't be working if you're performing the backup the way you say you are. Sorry I can't be more helpful. If it's any consolation, a backup probably isn't strictly necessary because you can always get back to stock by flashing the factory images.
Click to expand...
Click to collapse
I'm stumped too, I've been able to do this effortlessly in the past with this phone, my Nexus 9 and m8 GPE, it wasn't until I upgraded to N and reverted back to 6.0.1 this started to happen. I've even gone as far as trying different versions of twrp, but have had the same result.
I'm just worried in a worst case scenario I'm away from a comp, something crashes and I can't do a restore via twrp, I could be SOL until I get to a comp with adb.
i had a similiar problem , but when i got into the stock image , i went into settings and did a factory reset from there , no worries your BL stays unlocked , once thats done get whatever apps you want back , disable fingerprint /security junk , then boot into bl just like the guide says , youll be able to fastboot install recovery , (boot back into bl, then scroll to recovery and start a gain) then make your backups yor OG & EFS , then reboot , get su reboot into recovery install and yould be be fine , i think you can also try fastboot format userdata , as well
DeathSentinels said:
I'm stumped too, I've been able to do this effortlessly in the past with this phone, my Nexus 9 and m8 GPE, it wasn't until I upgraded to N and reverted back to 6.0.1 this started to happen. I've even gone as far as trying different versions of twrp, but have had the same result.
I'm just worried in a worst case scenario I'm away from a comp, something crashes and I can't do a restore via twrp, I could be SOL until I get to a comp with adb.
Click to expand...
Click to collapse
Just keep a ROM zip + gapps on your phone at all times, if you run into trouble you can flash that.
That definitely makes sense , i always dk that
Sent from my Nexus 6P using XDA-Developers mobile app