I was on Google edition using faux kernal. I decided to restore my stock rooted nandroid using twrp and I believe something went wrong. My phone rebooted on its own after the restore and everything went wrong from there. Force closes galore. I checked the kernal and it was still faux kernal so I figured that was the problem. I decided to wipe and restore one more time. This time it went smooth and I had the option to reboot when it was complete. Everything is running perfect but the weird thing is that the kernal appears to be stock now...
I'm very confused. Some Google searches led me to believe that a nandroid does not save your kernal but my kernal clearly changed on my second restore.
Does a nandroid restore kernal? What is the stock kernal for the i337 and is it around this site because I can't find it anywhere?
My kernal version reads...
3.4.0-453947
[email protected] #1
Sat April 27 17:06:05 kst 2013
Can someone confirm this is stock?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Cataligh said:
I was on Google edition using faux kernal. I decided to restore my stock rooted nandroid using twrp and I believe something went wrong. My phone rebooted on its own after the restore and everything went wrong from there. Force closes galore. I checked the kernal and it was still faux kernal so I figured that was the problem. I decided to wipe and restore one more time. This time it went smooth and I had the option to reboot when it was complete. Everything is running perfect but the weird thing is that the kernal appears to be stock now...
I'm very confused. Some Google searches led me to believe that a nandroid does not save your kernal but my kernal clearly changed on my second restore.
Does a nandroid restore kernal? What is the stock kernal for the i337 and is it around this site because I can't find it anywhere?
My kernal version reads...
3.4.0-453947
[email protected] #1
Sat April 27 17:06:05 kst 2013
Can someone confirm this is stock?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Yep, that's the stock kernel.
I'm not sure about TWRP. I know there are different options to save different partitions when creating a Nandroid with TWRP.
But there is something else I've been noticing through various posts about the S4. It seems that sometimes, with CWM, TWRP, or even ODIN, that some people have to flash files twice before they take. I'm not sure why it would be that way or if it's just a bunch of people screwing up on the first flash, but it sure seems that way. Maybe this is just one of those phones that depending on which lot you get, needs to be flashed twice?
yeah, Scott may be right. I don't think these recoveries are quite up to speed yet for the S4. Esp TWRP. I just like and have been use to TWRP UI.
Heard good things about Phil's Touch CWM--haven't tried yet. But, haven't restored yet either. Shabby's seems solid too. But, Phil's will restore both TWRP and CWM nandroids.
If you nandroided boot partition then the kernel should be restored
Only thing not touched in nandroids is radio
simply restoring the boot image from a nandroid will restore the kernel to what was backed up. I ALWAYS have a nandroid of a full factory ROM on my SD card in case I get problems. technically you don't even need to clear cache / dalvik cache.
note that some kernels actually flash more than the kernel and update Bluetooth and/or WiFi drivers, and would require more than the boot image to be restored.
keeping a fully stock ROM nandroid should be flashing 101... I've gotten into situations where I've had md5 mid matches when restoring backups, lost imei, all kinds of fun stuff. almost always doing a full factory reset/cache wipe/dalvik wipe/system format before restoring stock will fix those type of problems. after that I've had good luck then restoring the "problem" backup. very rarely have I ever had to Odin back to stock.
I installed a custom rom(GPE 5.0)on my i337m from Android 4.4.2 Stock ROM. I made a Nandroid backup with twrp 2830 before flashing the new rom. After playing with it a while I decided to go back to 4.4.2 using the Nandroid backup.
The Nandroid restore was successful(did a factory wipe before restore). However now I am getting force close non stop(seems like every app after the boot animation). I did a second restore without factory wipe and same problem. How can I get my backup restored properly?
If I install a custom rom(tried Goldfinger v9 among others), they boot fine. Any help would be greatly appreciated.
Thanks
TRoN_1 said:
I installed a custom rom(GPE 5.0)on my i337m from Android 4.4.2 Stock ROM. I made a Nandroid backup with twrp 2830 before flashing the new rom. After playing with it a while I decided to go back to 4.4.2 using the Nandroid backup.
The Nandroid restore was successful(did a factory wipe before restore). However now I am getting force close non stop(seems like every app after the boot animation). I did a second restore without factory wipe and same problem. How can I get my backup restored properly?
If I install a custom rom(tried Goldfinger v9 among others), they boot fine. Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
Sounds like your nandroid is corrupted.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Sounds like your nandroid is corrupted.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I tried again, this time I did advanced wipe and selected the usual system, cache, dalvik etc...and also format internal sd. When I restored the nandroid backup it finally worked properly. Pretty sure the backup is not corrupted.
Related
I'm having trouble restoring a nandroid backup.
I had CM7 running nicely running from internal. But I got bored and wanted to try an ICS ROM. So, I booted into CWM recovery, and did a backup first thing. Then I did the whole wipe and flash thing, and got the new ROM up and running. After a couple days, I decided that ICS is still too flaky for everyday use, so I decided to flash back to my good ol' stable CM7. So I booted back into recovery, wiped, and restored the backup I had made previously. But when I boot up, things are wonky. I have my homescreen and wallpaper back, and many of my other customizations, but none of my apps seem to be installed. My homescreens have placeholder icons, and the widgets all have an error message.
I've tried restoring several times, with different combinations of wiping system, cache, dalvik, etc. But I've yet to hit the right sequence. What's the "correct" way to restore back to what I had? I hate to have to set everything up all over again.
What version of CWM are you using? Some of the older versions do not wipe the newer nooks properly.
If you really want to be sure you have wiped everything, go to my tips thread linked in my signature and get version 5.5.0.4 either for emmc or a bootable SD. Then flash my format partitions 5, 6, and 7 zip. Then restore your backup and see if that does it.
leapinlar said:
What version of CWM are you using? Some of the older versions do not wipe the newer nooks properly.
If you really want to be sure you have wiped everything, go to my tips thread linked in my signature and get version 5.5.0.4 either for emmc or a bootable SD. Then flash my format partitions 5, 6, and 7 zip. Then restore your backup and see if that does it.
Click to expand...
Click to collapse
I have version 2.5.0.1 now. Took a quick look at your tips thread - looks like I have some reading to do! I'll get a newer CWM and see how it goes. Thanks!
Sent from my NookColor using xda app-developers app
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
Do I need to do a full factory reset if I bootloop before trying to do CWM restore. I have been unsuccessful in making the restore stick. I have bootlooped a couple of times and the CWM restore would not successfully boot, it too kept bootlooping. SO I was wondering what the HECK am I doing wrong . I need to understand this before diving into the phone too much. Also having problems getting adb to install from the android sdk, but that is probably just not enough time spent looking at proper install instructions. That's what I get when I only have about 30 minutes a day to actually plug into the laptop and work on these things.
I found what I was looking for. Needed to be on working rom then restore works. Got it.
Never mind... You got it.
Sent from my SCH-I400 using xda app-developers app
Or so I thought. Do I need to wipe personal data? Basically do the factory restore/reset? If yes then is that done through CWM or through settings menu? In my head I think doing it through CWM is the more appropriate place, then Get to working ROM then do a restore? Final question for this post, do I need to reflash the mods on their own or is that part of the restore.
I have not needed to officially complete a restore as I do not have much that is not already on sd card that I need to keep. But it is important to know how to do a restore in the event it is needed. It does get annoying when I bootloop and can't restore to my previously working settings, especially if it was a setup that I was particularly fond of.
How about this for steps?:
Wipe data
Flash EG04 Deo.zip
Wipe Dalvik
Reboot
Recovery mode
CWM Restore
Reboot
Okay, in trying to follow you on this. If you made a backup with CWM recovery when your phone was working, you should be able to flash it at any time. So let's say for some reason your phone starts bootlooping, you should:
Boot into recovery
Wipe cache partition
Wipe dalvik cashe
Flash your backup
IF your backup had any mods you WILL need to flash them after you flash the backup. If you don't the phone probably will bootloop..
Cross fingers
Reboot phone
Your back up should have been made with a working rom, so you shouldn't need to flash one before you flash the backup.
Someone else please jump in if I missed something!!
Sent from my SCH-I400 using xda app-developers app
roaddog665 said:
Okay, in trying to follow you on this. If you made a backup with CWM recovery when your phone was working, you should be able to flash it at any time. So let's say for some reason your phone starts bootlooping, you should:
Boot into recovery
Wipe cache partition
Wipe dalvik cashe
Flash your backup
IF your backup had any mods you WILL need to flash them after you flash the backup. If you don't the phone probably will bootloop..
Cross fingers
Reboot phone
Your back up should have been made with a working rom, so you shouldn't need to flash one before you flash the backup.
Someone else please jump in if I missed something!!
Sent from my SCH-I400 using xda app-developers app
Click to expand...
Click to collapse
And here is even more fun. I was booting up into recovery every time for awhile because it didn't like something I flashed. So I erased all my data and had to reflash eg04 deo twice before it took. Right now rebuilding the phone. Everything seems to be working correctly now. I didn't even try the restore because it didn't work.
Back to the using restore issue. What I'm hearing is that I can flash restore at anytime, and maybe have to flash the mods (is 1-3 TB101 everything mod) if it doesn't boot properly. I use EG04 deo topped with TB 101 mod and ciscogee's i400 SuperSU zip.
jaycush said:
Back to the using restore issue. What I'm hearing is that I can flash restore at anytime, and maybe have to flash the mods (is 1-3 TB101 everything mod) if it doesn't boot properly. I use EG04 deo topped with TB 101 mod and ciscogee's i400 SuperSU zip.
Click to expand...
Click to collapse
That would be correct. I use TB's mods also, and anytime I restore a backup I have to flash the mod too. Not sure why, because the backup "should" have the mod in it also, but that's the way it is.
Sent from my SCH-I400 using xda app-developers app
Today I successfully comlpeted my first restore. I flashed the restore and immediately went and flashed the TB mod and it worked. Very cool, and thanks a lot for the help.
jaycush said:
Today I successfully comlpeted my first restore. I flashed the restore and immediately went and flashed the TB mod and it worked. Very cool, and thanks a lot for the help.
Click to expand...
Click to collapse
Awesome... Glad you got it working!
Sent from my SCH-I400 using xda app-developers app
So I was running CM10.1 nightlies with Franco Kernel and decided to make the jump to CM10.2. The ROM and gApps flash went just fine, but like a dummy, I flashed the version of Franco kernel that I'd been using before, which I guess is not compatible with 4.3. The phone seemed to be softbricked and would just hang at the Cyanogen boot animation. I can get into recovery and I've tried to reflash both CM10.1 and CM10.2 - both hang at the boot animation. I can go back to my stock backup just fine, but then when I try to flash CM again (either version), I have the same hanging problem. Does CM store like a memory of the kernel that you have flashed and try to revert to that? Why can't I flash CM again once I've gone back to stock (and the stock kernel)? Would reflashing the stock image fresh (rather than using a TWRP backup) change anything? I'm pretty inexperienced with this and would appreciated any help. Thanks in advance!
alphamini said:
So I was running CM10.1 nightlies with Franco Kernel and decided to make the jump to CM10.2. The ROM and gApps flash went just fine, but like a dummy, I flashed the version of Franco kernel that I'd been using before, which I guess is not compatible with 4.3. The phone seemed to be softbricked and would just hang at the Cyanogen boot animation. I can get into recovery and I've tried to reflash both CM10.1 and CM10.2 - both hang at the boot animation. I can go back to my stock backup just fine, but then when I try to flash CM again (either version), I have the same hanging problem. Does CM store like a memory of the kernel that you have flashed and try to revert to that? Why can't I flash CM again once I've gone back to stock (and the stock kernel)? Would reflashing the stock image fresh (rather than using a TWRP backup) change anything? I'm pretty inexperienced with this and would appreciated any help. Thanks in advance!
Click to expand...
Click to collapse
Just to be sure how much juice was left while you were flashing CM rom?? Reading your problem I would suggest you to do a fresh Stock image installation and then try flashing CM 10.2.
Have you tried restoring your NANDROID backup, if you made one??
Rohit02 said:
Just to be sure how much juice was left while you were flashing CM rom?? Reading your problem I would suggest you to do a fresh Stock image installation and then try flashing CM 10.2.
Have you tried restoring your NANDROID backup, if you made one??
Click to expand...
Click to collapse
I have restored the NANDROID backup successfully, but unfortunately I was lazy and only have the backup from when I first got the phone.
I backed everything up with Titanium Backup right before I tried to flash CM10.2. If I do a complete stock reflash, do I lose all the data I backed up with TB? I do have some app data that I would really like to keep if possible.
One other resort I thought of was flashing a different custom ROM (Paranoid Android maybe?) and then restoring my TB backup. Would there be any reason that I shouldn't be able to reflash CM after I've restored the stock NANDROID?
alphamini said:
I have restored the NANDROID backup successfully, but unfortunately I was lazy and only have the backup from when I first got the phone.
I backed everything up with Titanium Backup right before I tried to flash CM10.2. If I do a complete stock reflash, do I lose all the data I backed up with TB? I do have some app data that I would really like to keep if possible.
One other resort I thought of was flashing a different custom ROM (Paranoid Android maybe?) and then restoring my TB backup. Would there be any reason that I shouldn't be able to reflash CM after I've restored the stock NANDROID?
Click to expand...
Click to collapse
Try this.
As you are able to go in recovery,
Wipe cache , dalvik cache, system, data install PA 3.97 flash pa_gapps then supersu v1.51(for root,also enable app+adb from developer option)
wipe cache and dalvck again and reboot..
P.S : Charge your battery first to 80% minimum and flash the rom.
If the above doesn't help,
Backup all you valuable data into pc, backup app+data through TB move it to pc and flash the factory image through fastboot.
Rohit02 said:
Try this.
As you are able to go in recovery,
Wipe cache , dalvik cache, system, data install PA 3.97 flash pa_gapps then supersu v1.51(for root,also enable app+adb from developer option)
wipe cache and dalvck again and reboot..
P.S : Charge your battery first to 80% minimum and flash the rom.
If the above doesn't help,
Backup all you valuable data into pc, backup app+data through TB move it to pc and flash the factory image through fastboot.
Click to expand...
Click to collapse
I ended up flashing the stock image and completely wiping all data. I then tried to install CM10.2 again and it still hung at the CM boot animation for about 15 minutes. It shouldn't take that long to flash, right?
alphamini said:
I ended up flashing the stock image and completely wiping all data. I then tried to install CM10.2 again and it still hung at the CM boot animation for about 15 minutes. It shouldn't take that long to flash, right?
Click to expand...
Click to collapse
Did you use the Franco.Kernel for the JSS build?
Sent from my Nexus 4 using Tapatalk 4
I was on CM12 nightly, and it was working fine. I decided to flash the latest update, but before I did I performed a nandroid backup. Right after rebooting after flashing, I kept getting errors about Timely has stopped working, or Google Play Services has stopped working. In short, the phone was unusable.
So I restored my nandroid backup, and the first thing I got was that Nova Launcher has stopped working. I couldn't get it to launch into my home screen. I went with Trebuchet, and opened WhatsApp, and it says that the messages have been corrupted.
What is happening?
It's urgent because I'm flying off soon.
Did u change the kernel of your phone? Did u wipe dalvik cache and cache after installation?
Sent from my SM-N9005 using Tapatalk
kurpen said:
Did u change the kernel of your phone? Did u wipe dalvik cache and cache after installation?
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I think it's related to this: when restoring the nandroid backup, it never gets to completion. Instead, somewhere around 2/3 through, it shuts off and reboots into recovery. So the restore isn't complete.
I'm thinking of switching my custom recovery to TWRP. I'm currently on CWM-based Recovery v6.0.4.7 Compiled by Xiaolu. Do I just download the new recovery in .zip and flash it as per normal?
It might just show it's 2/3 but in fact finish it anyways however I am not sure about this ;/ try to wipe everything (dalvik, cache, data) and then restore your backup. If that doesn't help do the wipes again and this time wipe system partition as well.
Sent from my SM-N9005 using Tapatalk
kurpen said:
It might just show it's 2/3 but in fact finish it anyways however I am not sure about this ;/ try to wipe everything (dalvik, cache, data) and then restore your backup. If that doesn't help do the wipes again and this time wipe system partition as well.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I think the backup is faulty. I tried using PhilZ recovery to restore, and the /data and /system restores were incomplete (I know because it says Done: 600/700MB). Now it's unbootable. I'm gonna try using Chenglu to restore, then get it partially working, then use TiBa to backup all my apps before clean-flashing the latest ROM.
Let me know what the outcome is
Sent from my SM-N9005 using Tapatalk
kurpen said:
Let me know what the outcome is
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Ended up reflashing Chenglu's recovery to restore the nandroid backup, went in to backup everything with Titanium Backup, then flashed the latest ROM (wiped everything) and set up everything from scratch
Have moved on to Philz recovery now.
fterh said:
Ended up reflashing Chenglu's recovery to restore the nandroid backup, went in to backup everything with Titanium Backup, then flashed the latest ROM (wiped everything) and set up everything from scratch
Have moved on to Philz recovery now.
Click to expand...
Click to collapse
Hey, but u got it working I hope you're not gonna need to do it again
Cheers
Sent from my SM-N9005 using Tapatalk