I rooted my Vibrant a week or so ago.
I flashed an update.zip and installed Clockwork Recovery Mod.
I immediately took a nandroid update of the stock, rooted system.
I tried out the AOSPish 1.4 Eclair rom (stock kernel) from the Development section, which works quite well.
My problem is that I cannot restore the nandroid backup I took before flashing teh AOSPish rom. I did a data/cache wipe in Clockwork, restored the nandroid backup, and it hangs at the Vibrant boot logo.
I can restore the AOSPish nandroid backup just fine.
I'm pretty sure it wont work...you have to Odin stock JI6 then restore your JI6 nandroid
Sent from my SGH-T959 using XDA App
Fair enough. I'm happy with the AOSPish rom anyway, just wanted to see if it could even be done.
Related
Im running fresh 0.5.3 and have the latest amon recovery, i can do a ext+nandroid backup fine but when i try to restore after i reboot, it gets hung on the
htc screen and will not load. Ive tried several backups and it will not work when restoring. Any ideas?
Make sure you're wiping the data, cache and dalvic before restoring the backup.
Are you sure the backup is getting created?
I know SteelH was posting yesterday about the NAND + EXT backup not even working with amon recovery.
I personally don't even know what it does, but all my backups are just "NAND backups and seem to work fine.
I'm assuming you used Amon_ra to create the backup and you're using Amon_ra to restore?
I created a backup with amon_ra and tried to restore with Clockworkmod and the backup doesn't even show up and vice versa. I found out by trial and error that backups created by clockworkmod have to be restore with clockworkmod and backups created by amon_ra have to be restored with amon_ra.
I don't know if that's the case for everyone, but it sure is for me. I'm running whitslack's 1.47 and Evolution V9.
Back to the Nand+Ext, maybe SteelH has figured it out, maybe send him a pm or search for his posts in the Q&A forum from yesterday.
make sure your batt has enough power
I am fully charged when i nandroid. It creates the backup and restores it but when i reboot it freezes on the htc screen. So this is a bug with the amon recovery image then? It would be nice to be able to backup & restore my ext apps because i use apps2sd. I could use titanium backup but nandroid is faster.
CW 3.0.0.5 or cw 2.5.1.2?
Does it make a difference which I use to do my nandroid backups? I'm using Nebula which still requires flashing in CW 2.5...so that's why I ask.
Also I did a backup yesterday in each, and when I tried to restore from both they both said md5 checksum fail. I had to restore from an older backup. What would cause that?
Did you rename the backup? That messes it up.
I dont think the CWM version matters, I restored a backup from 2.5 in 3 after an upgrade
Yeah I renamed them. thanks for the answer on that.
When renaming don't use space and keep it simple some characters don't work (for me).
dito33
Not sure how it's done on the epic side of things, but nobody does nandroid backups in the captivate, vibrant, or i9k forums. Clockworkmod doesn't save the modems or kernals and such all the time so it doesn't back em up. Therefore you can be restoring a rom over a bad kernal flash, or incompatible modem, ect. Just keep the cw update.zip on the sd, odin to stock, use titanium backup to restore apps. Android ID changer to restore id and your good.
instead of SBFing back to stock completely so I can flash the rooted GB? I'd rather not mess with the hassle of SBFing. To be more clear, I rooted, made a backup, and flashed Liberty 1.5 to be where I am now. Can I just restore that first backup and then flash GB? Thx.
If the backup is based on 2.3.20 then yes you can flash GB from that.
sweet thx a lot
Now, I haven't cared too much about Nandroid backups since nothing is too important for me to save, and I'm running a different ROM almost every day... But what do Nandroid backups backup ? Just the ROM? ROM and data + Kernel ? And If I do a full wipe and I have a Nandroid backup, do I have to Flash the ROM first, then flash the Nandroid over it? Or can I just full wipe and flash the nandroid?
Nandroid isn't something I use a lot (or at all), so this is kinda odd to me.
A nandroid backup is essentially an image of your entire phone. The entire OS, phonebook, messages, settings...everything.
Awesome, so I can just flash the nandroid right after a full wipe, correct?
Yep, absolutely. Just don't forget that only CWM 3.0.0.6 can flash and restore anything. The other versions are limited to Froyo or Gingerbread, not both.
Yeah I know, I flashed 3.0.0.6 the second i saw it did both ROMs, I haven't had a problem since ^_^ But thanks !
+2 to your Thanks Meter
Glad you got it worked out.
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.