So I've seen some questions on restoring nandroid backups once we've flashed the CWM builds.
Before doing any flashing, I did a simple backup using nandroid. I then flashed 2.3.4 using fastboot images and then unpacked nava's 1.6 on top of it. I then, without doing anything else, attempted to restore my 1.8.3 install via nandroid.
It appeared to work perfectly. Bootsplash looks good, everything looked good. I unlocked it using my fingerprint which was saved. However, once the screen is unlocked, the homescreen is unusable and frozen and it appears as though the Phone icon is depressed. I haven't been able to make any more progress yet but I'm working on it.
Just a precautionary tale for those of us thinking about using CWM to backup/restore.
I tried restoring the /pds using the blank atrix dev mmcblk0p3 to no avail. I ended up going back to 2.3.4 and will just have to deal with it for the time being.
I was successfully able to do a nandroid restore to 1.8.3 from 2.3.4 by following these steps:
sbf_flash (or RSD Lite) to 1.8.3 full (from the Atrix Firmware Superthread)
root, sideload and install the old CWM app
nandroid restore
Not sure if this re-locks your bootloader, but with one 2.3.4 buggy ROM, I don't particularly care, as I can always unlock again
Hope this helps!
Related
So i'm pretty noob with all this stuff but i finally decided to try flashing my phone and, in the end, ended up with a "bricked" (or the extent a vibrant can be bricked) phone. Thanks in advance for the advice.
what i did
I followed the flashing guide in the sticky post "** GUIDE - TIPS - TRICKS ** Last Update 12/03/10 ** READ BEFORE ASKING" and everything worked great. I downloaded Rom manager, made a nandroid backup of my stock rom, flashed it with bionix fusion and everything worked great. I didn't do the titanium backup and there was an app that i needed to use the next day so on the way to work, i decided to restore back to the stock thinking that i could go back for the day, use the apps that i needed and when i got home got home, back up my apps with titanium back up and restore again back to the bionix fusion. So i did that. I went to rom manager and I first backed up my bionix fusion rom and then tried to recover my stock rom. When the phone restarted, it didn't go past the vibrant/samsung screen.
The question...
what went wrong? based on some reading i think it has something to do with the kernel but i'm not really sure.
but the real question is, how do i avoid from this happening again? did i do the recovery wrong? what's the best way to unbrick my phone back to stock without losing any data on the phone. is it possible????
at this point, i can go into download mode. what should be my next move?
Thank you again if you can provide any insight.
*edit*
So looking at some posts, I looks like I need to flash the stock kernel. can anyone tell me how to flash just the kernel using odin? I've never used it and I can't seem to find anything on flashing just the kernel. Thank you.
Problem SOLVED!
ok. not completely solved T_T.
What i've done.
I've flashed back to stock vibrant firmware and that works fine. When i try to restore my nandroid backup, and it reboots, I get stuck back to the same place i was. I made two nandroid backups and tried them both but neither of them work. am i doing it wrong? I have even re-rooted my vibrant and downloaded rom manager again and tried it through there and still get the problem. have tried it about 4 times now with no luck.
Again, any help is appreciated.
Nandroid doesnt replace the kernal
Sent from my SGH-T959 using XDA App
Exactly, nandroid doesn't replace the kernel. If you want to run a nandroid restore, you have to either flash the rom the nandroid was created on, then restore (safest imho), or flash a compatible kernel for the rom from which your nandroid was created, then run your nandroid restore.
Sent from my Vibrant running Macnut R13 w/JK6 Modem and Black Froyo
Pretty sure this was in the sticky too
Recently, I reflashed 1.26, rooted via gladroot, then updated via OTA to 1.57 then 1.83, retaining root both times. I immediately backed up my system via CWM. At that point, I was running stock, rooted 1.83, and did not download anything and did not change any settings.
My question is, if I want to uninstall a theme or gingerblur, or if I screw something up, would it be cleaner to re-flash 1.26 and re-do all the steps above, or will simply restoring from CWM put me in the exact same spot?
Thanks.
Nobody? I can't post in the development forum, otherwise I would have asked in Tenfar's thread.
beans3660 said:
Recently, I reflashed 1.26, rooted via gladroot, then updated via OTA to 1.57 then 1.83, retaining root both times. I immediately backed up my system via CWM. At that point, I was running stock, rooted 1.83, and did not download anything and did not change any settings.
My question is, if I want to uninstall a theme or gingerblur, or if I screw something up, would it be cleaner to re-flash 1.26 and re-do all the steps above, or will simply restoring from CWM put me in the exact same spot?
Thanks.
Click to expand...
Click to collapse
I believe you can restore with CWM if you want to go back to the same point, but not if you want to restore apps and data to a later updated firmware revision.
I haven't tried this myself yet, but will the next time I clean off my phone for whatever reason............new "ROM" maybe. I up till now have been flashing back to 4.1.26 and then updating to keep everything clean.
So, I have a small problem. I compiled an alpha version of CyanogenMod from the Atrix-Dev-Team github, and I got it to boot on my phone. Sadly, it has no radio image, so it doesn't let you call, text, listen to pandora while you drive, etc. so I decided to use my nandroid backup to go back to the official 2.3.4 ROM, and it is now in a boot loop. I can flash back to CyanogenMod, but when I flash the backup, it just boot loops about a second after it passes the bootloader screen. I am thinking about sbf flashing the 2.3.4 with the unlocked bootloader integrated into it, but I have hard-bricked once from sbf flashing, so I'm scared.
The point of all of this is do you think I will hard brick if I flash back to the sbf?
IIxShockwavexII said:
So, I have a small problem. I compiled an alpha version of CyanogenMod from the Atrix-Dev-Team github, and I got it to boot on my phone. Sadly, it has no radio image, so it doesn't let you call, text, listen to pandora while you drive, etc. so I decided to use my nandroid backup to go back to the official 2.3.4 ROM, and it is now in a boot loop. I can flash back to CyanogenMod, but when I flash the backup, it just boot loops about a second after it passes the bootloader screen. I am thinking about sbf flashing the 2.3.4 with the unlocked bootloader integrated into it, but I have hard-bricked once from sbf flashing, so I'm scared.
The point of all of this is do you think I will hard brick if I flash back to the sbf?
Click to expand...
Click to collapse
If pudding is built in, you should be fine. But I suggest trying sam's fruitcakes or one of the CWM (tenfars) flashable ROMs like alien, ninja, cherry etc. Don't forget to wipe.
don't use .sbf...just use fruitcakes like other guy mentioned..but those roms aren't rooted....may as well flash rooted rom..like alien, ninja, cherrypi...etc..
Are you sure you wiped before and after restoring the backup?
Hello, I need some help with restoring via CWM on the Galaxy S3.
On the S2 I pretty much always used CM9 and jumped back and forth between versions and backing up/ restoring was never an issue.
Now however I am using the stock ROM and its rooted of course.
I made a back up of my stock rom 'cause I wanted to try and install some stuff.
I tried installing the jelly bean transition effects but the install failed, the device felt kinda sluggish (maybe my imagination) afterwards so I decided to restore my phone. The restoring went good but the last ting that happens is that CWM says that restoring /Data failed.
I reboot my phone and I come to the first start up screen where I get to choose language and so on. Everything but photos has been deleted. I try to install CM9, and I do that without any issues. Then I trie to backup my stock backup but I get the same error message and I get back to stock setup page.
My backup is a staggering 6GB, and I read somewhere that CWM can only restore 2GB?
I've deleted that backup and done another one but that is also 6GB.
Does anyone know how to restore from that first restore or how to make future restores work?
undegaard said:
Hello, I need some help with restoring via CWM on the Galaxy S3.
On the S2 I pretty much always used CM9 and jumped back and forth between versions and backing up/ restoring was never an issue.
Now however I am using the stock ROM and its rooted of course.
I made a back up of my stock rom 'cause I wanted to try and install some stuff.
I tried installing the jelly bean transition effects but the install failed, the device felt kinda sluggish (maybe my imagination) afterwards so I decided to restore my phone. The restoring went good but the last ting that happens is that CWM says that restoring /Data failed.
I reboot my phone and I come to the first start up screen where I get to choose language and so on. Everything but photos has been deleted. I try to install CM9, and I do that without any issues. Then I trie to backup my stock backup but I get the same error message and I get back to stock setup page.
My backup is a staggering 6GB, and I read somewhere that CWM can only restore 2GB?
I've deleted that backup and done another one but that is also 6GB.
Does anyone know how to restore from that first restore or how to make future restores work?
Click to expand...
Click to collapse
I had this problem with my sisters Xperia X8,couldn't restore anything that i backed up.It goes for a while and stops.But she had bootloader locked.I was shore that i unlocked her bootloader but i didn't,so i unlocked bootloader,and tried to backup and restore and it worked fine.
I'm not 100% and i don't know is that the way CWM works,but i think in order to restore your data,that you backed up,you have to unlock your bootloader.But it's the best to wait someone who knows this for 100% sure.
If you haven't unlocked bootloader try that,or you don't won't to lose your warranty!?
Good luck!
I don't think that CWM has size limitation but i can be wrong.
Have you made sure that your CWM is up-to-date? if in doubt flash the latest CF-root.
was there ever a resolution to this problem? I did the same thing, rooted the galaxy s 3 and unlock the bootloader. Get a backup of my stock set up using clockwork recovery mod. Now when I try to restore, it does not restore the data. All of my apps look like they are there, but none of them are really installed. I think I can just reinstall all of the apps by hand, I would like to know how to get over this.
1. Hi, I have a locked ST18a that was on Forsaken GB v3.0 as of recent. While I was on the rom, curiosity got the better of me I applied part of the root keeping process as found in the m/h dpi root tutorial, the local prop hack. It was my intention to upgrade to ICS, but I was wondering what would happen if I tried to do it straight from a custom GB rom (bad idea, I know) and continued from there. The script created a /data/local.prop to enable android emulator hack. I then went into recovery and made a nandroid backup (I know I should have done it before applying anything new) and it carried on without a hitch. However, when I powered off and back on, I was stuck on the boot logo. No matter what I did, I couldn't get it to work, so I went to flashtool and flashed stock GB, then rooted and installed recovery again. I then went into recovery and restored my nandroid, but I had the same issue again. I reflashed stock, but this time I went all the way to rooted ICS and installed appextractor, to restore my appdata and sms data from the weird nandroid. I could install apps, but could not restore their data or my messages. So, with all this background info, can adding a local.prop mess up a nandroid that badly? Was appextractor not working as a result of that nandroid with local.prop, or is it appextractor's problem? Also, I had backed up my messages through sms backup as well. A local.prop shouldn't have any effect on a xml. type backup, right? My sms backups would not restore either.
Edit: Was able to extract asp data through titanium backup, but there's an error with the xml and I still can't restore my messages.
2. Also, while this is a completely different issue, I noticed that although they are the same recovery and should both be in /system, the CWM from xParts and RecoverX tools (the same 5.0.27 by nobodyAtall) seem to be different. If I format /system (a requirement for roms I use with locked bootloader) on the xParts version of the recovery, nothing happens. I am able to continue my flashing process. However, when I try that with the RecoverX version of CWM, the recovery crashes and I am stuck on a blank screen no matter what I do. What is going on here?
3. Also, one more question: I have the ST18a, the North American version of the Xperia Ray. All roms are developed as ST18i roms. I've been googling some info, and there doesn't seem to be any negative effects after installing an ST18i firmware or rom on my ST18a, but I did notice weaker signal (bigger dBm, eg -85 instead of -77), and faster battery drain in standby and normal usage than if I had a stock ST18a rom. What difference do the different frequencies make?
Could you please answer my three questions? And sorry for the long paragraphs.