Ive tried both Rogue and Roach's recoveries.
Every time i backup and restore (i wipe first), it is always successful.
Upon a reboot, it hangs at the very first Asus screen, never gets to the animation.
Ive always had success nandroiding my hero, nexus and evo 3d but cannot get a restore to work on my Transformer.
Kinda frustrating but im getting good at starting fresh. (Fast anyways)
Any ideas or help would be greatly appreciated.
Thanks!
After you restore the backup, then flash a kernel. That will allow it to boot up normally..
Is that the proper way to restore?
I realize that will probably work as I have to fastboot flash boot.img every rom change on my 3D
That means I need a flashable zip of each kernel of every nandroid I make in order to restore? Or fastboot the kernel.
There has to be something I'm missing or an easier way.?
Anyone?
Sent from my Transformer TF101 using xda premium
The only time you need to flash a kernel would be restoring back to HC from ICS as CWM doesn't restore the kernel. I have been jumping from ROM to ROM testing which one I like and no problems nandroid restoring my backup. I'm using Team Rouge version recovery.
I have some weird issues then.
I'm assuming the best bet for me as of now would to restore then immediately flash the rom on top of the restore.
Sent from my Transformer TF101 using xda premium
Related
Hey.
If I flash custom rom and then decide to go back to stock rom, do I just run the nandroid backup on top of the custom rom, or I have to wipe or something to make it run smooth and fast?
Thanks.
I just restore. But if u feel a lil frantic about issues do the normal wipe process
Sent from my LG-P999 using XDA Premium App
SAme here, never wiped, always worked great.
It wont hurt, but it wont change anything either, because restoring the nandroid rom actually does that for you automatically
Strange problem on my wife's Charge. I just got her rooted, onto GB EP1W, and put her on TeamSBrissenMod's ROM, which I have been happily running for days.
After flashing last night, I let her spend this morning restoring her apps, wallpapers, themes, etc. She likes pink, lol. Well, after all of that, when she was done and satisfied, I showed her how to access CWM and create a backup. She did it, but when she rebooted, the phone has reset itself back to the point where it would look like the ROM was just freshly installed. No apps, no nothing, right back down to the default ROM wallpaper.
I tried to go back and restore the backup she just created, but its just the same thing, vanilla, freshly installed ROM. Im at a loss, never seen this happen before, and she certainly didn't make a mistake and reset anything as she backed up.
Sent from my SCH-I510 using Tapatalk
And no i didnt flash some odd CWM from ROM Manager or anything strange. Used the (imnuts?) fixed recovery dated 8/17
Sent from my SCH-I510 using Tapatalk
unfortunately this is a known issue that CWM wipes data on first boot into it after installing the rom... same issue that was happening with earlier Gummy GB versions
Sent from my SCH-I510 using XDA App
This is a known issue with the Infinity ROM. Specifically, it is with the kernel that ships with the ext4 version of the ROM. imoseyon's kernel does not have this issue, and it is fully compatible with the ROM.
Ok two answers, and I appreciate both, but which is it? An issue with the kernel, or this version of CWM? If its CWM, that makes me not want to boot into CWM ever..how do i resolve/get around it? I was intending on doing my own backup today as a matter of fact. Now, not so sure lol. I'll go back to the ROM thread too to see who has had the issue previously.
Sent from my SCH-I510 using Tapatalk
Well the answer seems to be to avoid CWM while on Infinity. Guys have tried every CWM version there is and data wipes on each one.
Is there expected "official" support from Clockworkmod on it's way for the Charge?
Sent from my SCH-I510 using Tapatalk
richm052569 said:
Well the answer seems to be to avoid CWM while on Infinity. Guys have tried every CWM version there is and data wipes on each one.
Is there expected "official" support from Clockworkmod on it's way for the Charge?
Sent from my SCH-I510 using Tapatalk
Click to expand...
Click to collapse
The wipe has *nothing* to do with CWM. It has everything to do with the kernel. imnuts has said this. imoseyon's kernel does not cause wipes on any version of CWM. This is 100% verified.
Here's the link if you want it: http://rootzwiki.com/showthread.php...n-kernel-(stock-repacked-v2.3.2voodoo-9-28-11)
shrike1978 said:
The wipe has *nothing* to do with CWM. It has everything to do with the kernel. imnuts has said this. imoseyon's kernel does not cause wipes on any version of CWM. This is 100% verified.
Here's the link if you want it: http://rootzwiki.com/showthread.php...n-kernel-(stock-repacked-v2.3.2voodoo-9-28-11)
Click to expand...
Click to collapse
also (for myself anyway) it is only wiping data on the first boot into CWM... I flashed the Infinity rom, discovered it wasn't rooted so I booted into CWM and flashed superuser then booted up and was wiped but rooted, after that I've had no wipes
anoninja118 said:
also (for myself anyway) it is only wiping data on the first boot into CWM... I flashed the Infinity rom, discovered it wasn't rooted so I booted into CWM and flashed superuser then booted up and was wiped but rooted, after that I've had no wipes
Click to expand...
Click to collapse
I will second what shrike is saying. I have also started using imoseyon's kernel and have had no problems going into CWM for any installs since using them.
The reason your data is getting wiped only on the first time is because two of the EXT4 partitions (I think they're Cache and Data) get reformatted back to RFS by the kernel (after you reboot). This is what wipes your phone. The second time you go into CWM and reboot, those partitions are already RFS, so the kernel doesn't have to reformat them, and your data stays.
I can't restore my CWM backups. I get an error saying unable to mount system.
I'm not using ROM Manager and I even tried reinstalling the same ROM that I made the backup from and then restoring the backup, but it still doesn't work. I'm using Octane 2.x with DrHonk's KJ1 Kernel and my CWM version is 3.0.2.8x
I've seen several posts on this issue, but haven't seen a clear answer. Some people say it doesn't work and others have said it does. If anyone can provide some help, I'd appreciate it. I like to try out different ROMS and with other phones such as the Vibrant (yes I know this phone is different) I have always made a backup with CWM and if I didn't like the ROM I could go right back to my previous one with very little work. I know I can use Titanium and I do that, but you can't restore everything so I end up having to redo a lot of stuff.
If anyone can provide some help with this, I would appreciate it.
Thanks,
From what I understand, you'll get that error when you restore a GB backup. Froyo works fine.
As a work around, you can boot into CWM, flash Dr Honks Bali kernel, then goto advanced>reboot recovery. When CWM boots again, you can restore your backup.
Another work around that I've seen mentioned is to boot into CWM, reflash the ROM of the backup you want to restore. Once the ROM flashes, goto backup/restore>advanced restore and backup the data only. That way you get the system partition from flashing the ROM, and your old data partition from your backup.
I haven't tried either of these methods. Guess I probably should have disclosed that first, but this is what I have gathered by reading some of these threads.
Sent from my SGH-T959V using XDA App
dbldown7 said:
From what I understand, you'll get that error when you restore a GB backup. Froyo works fine.
As a work around, you can boot into CWM, flash Dr Honks Bali kernel, then goto advanced>reboot recovery. When CWM boots again, you can restore your backup.
Another work around that I've seen mentioned is to boot into CWM, reflash the ROM of the backup you want to restore. Once the ROM flashes, goto backup/restore>advanced restore and backup the data only. That way you get the system partition from flashing the ROM, and your old data partition from your backup.
I haven't tried either of these methods. Guess I probably should have disclosed that first, but this is what I have gathered by reading some of these threads.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
This is mostly correct. Just left one thing out. Make sure after you flash Bali and restore your nandroid that you also reflash cwm/voodoo kernel.
Sent from my SGH-T959V using Tapatalk
dbldown7 said:
From what I understand, you'll get that error when you restore a GB backup. Froyo works fine.
As a work around, you can boot into CWM, flash Dr Honks Bali kernel, then goto advanced>reboot recovery. When CWM boots again, you can restore your backup.
Another work around that I've seen mentioned is to boot into CWM, reflash the ROM of the backup you want to restore. Once the ROM flashes, goto backup/restore>advanced restore and backup the data only. That way you get the system partition from flashing the ROM, and your old data partition from your backup.
I haven't tried either of these methods. Guess I probably should have disclosed that first, but this is what I have gathered by reading some of these threads.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Thanks for the response. I guess I'll try to doing an advanced restore of the data the next time since that sounds like the least painful method. If that doesn't work I'll try the bali kernel.
Please keep in mind that you CANNOT perform an advanced data restore from Froyo to GB. It will cause issues, such as incoming calls going directly to voice mail.
If you are moving from Froyo to GB, be sure to create a backup of your apps and data using Titanium Backup. Restore everything once you're on GB and it'll work fine.
bkoon1218 said:
Please keep in mind that you CANNOT perform an advanced data restore from Froyo to GB. It will cause issues, such as incoming calls going directly to voice mail.
If you are moving from Froyo to GB, be sure to create a backup of your apps and data using Titanium Backup. Restore everything once you're on GB and it'll work fine.
Click to expand...
Click to collapse
I'm doing GB to GB.
dbldown7 said:
From what I understand, you'll get that error when you restore a GB backup. Froyo works fine.
As a work around, you can boot into CWM, flash Dr Honks Bali kernel, then goto advanced>reboot recovery. When CWM boots again, you can restore your backup.
Another work around that I've seen mentioned is to boot into CWM, reflash the ROM of the backup you want to restore. Once the ROM flashes, goto backup/restore>advanced restore and backup the data only. That way you get the system partition from flashing the ROM, and your old data partition from your backup.
I haven't tried either of these methods. Guess I probably should have disclosed that first, but this is what I have gathered by reading some of these threads.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
I followed the first suggestion, flashing Dr Honks Bali 3.3 Kernel and it worked great. Just make sure you re-flash your old kernel before you reboot and you'll be fine. Thanks for this.
I decided to try out the cornerstone aosp so I made a nandroid backup, did the usual stuff and tried it out. Once I was done messing around, I wanted to restore my nandroid but after I do it doesn't boot. Nothing I try works so I end up wiping everything and installing fresh. Second time its happened where restoring wouldn't work. Anyone else have this issue? Also could u take that backup and put it as a zip file, place it on ur SD card and flash it through recovery? Would probably get the same result though
Sent from my XT862 using XDA App
its not an issue nandroid does not restore your kernel. You need to restore your nanadroid then reflash the rom that you were using when you took the nandroid
mrevankyle said:
its not an issue nandroid does not restore your kernel. You need to restore your nanadroid then reflash the rom that you were using when you took the nandroid
Click to expand...
Click to collapse
So I need to just restore then flash the rom that the restore was based off of? Thats easy enough. But I thought there was only one kernal across ics for the tf101 atm
Sent from my XT862 using XDA App
asop and asus based slightly different not sure if its the kernel though so there are some issues there
mrevankyle said:
asop and asus based slightly different not sure if its the kernel though so there are some issues there
Click to expand...
Click to collapse
Ah alright. Well I'll give that a shot maybe tomorrow, thanks
Sent from my XT862 using XDA App
I was running a ROM versed on ulcb3 and using the entropy DD kernel. I just restored a nandroid backup to an L2 based ROM that was packaged with infusion-GB A2. I wiped prior to restore in cwm.
My settings now tells me I'm using the b3 baseband, and I can't tell what kernel I'm on. does a nandroid backup restore the modern and the kernel? I'm guessing kernel yes, modem no. Can anyone confirm?
Sent from my SAMSUNG-SGH-I997 using XDA App
You have to flash the kernel you were using with the backup. I wipe data, flash the kernel that is supposed to be with my restore then ill do my nandroid restore. You then have to flash the modem that you want. Doing restores on the infuse is a little tricky at first.
Sent from my SGH-I997 using xda premium
On a similar note.... when switching between roms that are both nandroided, full wipe, cache, and dalvic are still necessary? I figured a nandroid restore would rebuild the whole phone to the snapshot that was taken at the time of backup......
Sent from my SAMSUNG-SGH-I997 using XDA
chipstien said:
On a similar note.... when switching between roms that are both nandroided, full wipe, cache, and dalvic are still necessary? I figured a nandroid restore would rebuild the whole phone to the snapshot that was taken at the time of backup......
Sent from my SAMSUNG-SGH-I997 using XDA
Click to expand...
Click to collapse
I do a full wipe. It only takes 20 seconds extra.
Sent from my SAMSUNG-SGH-I997 using xda premium
Ya for some odd reason when i attempt to use the nandroid back up & restore future i get bootloops on the samsung screen upon restoring, i don't get it. On my HTC i can do it without any problems. Do i have to flash the appropriate kernel for the ROM when i want to revert to it?
slicingtaco said:
Ya for some odd reason when i attempt to use the nandroid back up & restore future i get bootloops on the samsung screen upon restoring, i don't get it. On my HTC i can do it without any problems. Do i have to flash the appropriate kernel for the ROM when i want to revert to it?
Click to expand...
Click to collapse
Never had luck with the nan backup...I use Zen tool kit for the infuse...to do a full back up...works great...
Sent from my SGH-I997 using xda premium
slicingtaco said:
Ya for some odd reason when i attempt to use the nandroid back up & restore future i get bootloops on the samsung screen upon restoring, i don't get it. On my HTC i can do it without any problems. Do i have to flash the appropriate kernel for the ROM when i want to revert to it?
Click to expand...
Click to collapse
When restoring a nandroid, you should only restore the data in the advanced restore option. Make sure to do wipes prior to flashing a new ROM.
Sent from my Kindle Fire using Tapatalk 2