Im running 2.3.3 on firmware 3.0, with doomlord's kernel.
I managed to make a nandroid with the cwm recovery built in the kernel, a gigantic 900mb file was created..
From what I understand the nandroid will help to restore the phone back to the backup I created ..
So, here's my question.
If I flash cm7 rom ( using stock rom now) and I don't like it, I can restore back to stock via nandroid? Also, when I flash a different rom will the kernel be affected?
Thanks!
LemonPlusTea said:
Im running 2.3.3 on firmware 3.0, with doomlord's kernel.
I managed to make a nandroid with the cwm recovery built in the kernel, a gigantic 900mb file was created..
From what I understand the nandroid will help to restore the phone back to the backup I created ..
So, here's my question.
If I flash cm7 rom ( using stock rom now) and I don't like it, I can restore back to stock via nandroid? Also, when I flash a different rom will the kernel be affected?
Thanks!
Click to expand...
Click to collapse
I made one with 2.3.3 R800at AT&T stock FW and it was less than 300MB and then I made one of the 2.3.4 R800a generic North American FW and it was over 900MB. I can't figure why. The Bruce Lee game it includes isn't nearly that large and it also gives up more than it adds (no SIMS3 or TBloxx My City).
On our PLAYs, nandroid backs up all data except the kernel. You must save a backup copy of the kernel by yourself (just don't delete it after flashing it). Flashing a new rom does nothing to the kernel, again you must flash the new kernel yourself
Related
Hi,
I just flashed the new rmk gingerbread sense ROM to my Desire Z, and I'm thinking of trying the unity v3 kernel since it seems to have better battery life and performance from what I'm reading.
I've never flashed a kernel before. It seems like the flash process is identical to flashing a ROM? i.e. place the zip file in my sdcard, go to ROM manager and flash it there?
How do I backup the previous kernel though? Do I just do a backup via the ROM manager, which backs up everything, or do I backup just the existing kernel? Also, if I have the rmk ROM zip in my sdcard, if anything goes wrong with the kernel flash, can I just flash that zip in recovery boot? That way I don't have to backup anything.
Also, do I still need SetCPU to manage governors and clockspeeds? Not sure if anything has changed...
Thanks!
Do a full nandroid backup before flashing a new kernel. Nandroid backup will back-up the kernel and the entire ROM.
Flashing a kernel.zip is the same as flashing a ROM. Enter recovery, select "install .zip from SDcard" and proceed from there.
If the kernel causes problems or isn't working properly, revert to your previous nandroid backup.
Depending on the ROM and kernel combination, SetCPU may be required or advised, such as with a high OC kernel. Everyone has their own method to setting profiles, however.
Thanks.
I'm using rmk vision gingerbread sense 2.42. If I already have this downloaded ROM zip file in my sdcard, can I just flash back to this, rather than do a nandroid backup and restore to that? Does the nandroid backup keep my user settings?
Thanks.
goister said:
Thanks.
I'm using rmk vision gingerbread sense 2.42. If I already have this downloaded ROM zip file in my sdcard, can I just flash back to this, rather than do a nandroid backup and restore to that? Does the nandroid backup keep my user settings?
Thanks.
Click to expand...
Click to collapse
No, don't just flash over it. You're best off simply using CWM to backup and restore. The nandroid backup makes a complete perfect copy of the state of your phone at that time, restoring to it makes it seem as though nothing has happened after that point.
I've been playing around and checking out a few ROMS (CM9 and CM10), but since they aren't fully complete I want to go back to stock. when I rooted I made a Nandroid backup in recovery. Now If i want to go stock again do I just wipe everything and use the backup I made. Still confused because I flashed kiss kernal. Will restoring remove the kiss kernal?
No need to wipe before you restore your backup, and it will install the stock kernel also
Sent from my One V using xda premium
No... restoring from nandroid will not removed the flashed kiss kernel.
You need to flash a stock boot.img first before nandroid restore or you can flash kiss kernel that is meant for a sense rom first. Without reflashing kernel, you'll be in bootloop.
My bad
Sent from my One V using xda premium
Thanks a lot!
Twner said:
I've been playing around and checking out a few ROMS (CM9 and CM10), but since they aren't fully complete I want to go back to stock. when I rooted I made a Nandroid backup in recovery. Now If i want to go stock again do I just wipe everything and use the backup I made. Still confused because I flashed kiss kernal. Will restoring remove the kiss kernal?
Click to expand...
Click to collapse
Can you share me the stock backup, upload to mediafire or something. i just want to go back to stock rom too. thanks a lot if can
chiplovez9x said:
Can you share me the stock backup, upload to mediafire or something. i just want to go back to stock rom too. thanks a lot if can
Click to expand...
Click to collapse
I asked this in the IRC and was told you would need to flash the stock ROM (RUU?).
Think its this thread:
http://forum.xda-developers.com/showthread.php?t=1591059
Someone could verify.
Not sure how to tell which one you need either. Anyone know what I'd need for Koodo Canada version?
chiplovez9x said:
Can you share me the stock backup, upload to mediafire or something. i just want to go back to stock rom too. thanks a lot if can
Click to expand...
Click to collapse
I would but I have the Middle Eastern model (PrimoU), and im kind of a noob. But if you think it will work on your message me and i'll upload .
atonz said:
Not sure how to tell which one you need either. Anyone know what I'd need for Koodo Canada version?
Click to expand...
Click to collapse
I would get the Telus RUU, but only flash the kernel (boot.img) as I imagine that even if their ROMs are different, they'll be running the same kernel.
Here's how to get the boot.img out of the RUU:
Run the RUU (no need to connect the phone, all you want it to do is extract)
Go to %temp% (Start, Run..., enter %temp%)
Sort by date to find the most recent folder
Find rom.zip in there, open it and extract the boot.img wherever you like
After that you should be able to just fastboot flash boot boot.img like any other kernel, and restore your original nandroid.
formicae said:
I would get the Telus RUU, but only flash the kernel (boot.img) as I imagine that even if their ROMs are different, they'll be running the same kernel.
Here's how to get the boot.img out of the RUU:
Run the RUU (no need to connect the phone, all you want it to do is extract)
Go to %temp% (Start, Run..., enter %temp%)
Sort by date to find the most recent folder
Find rom.zip in there, open it and extract the boot.img wherever you like
After that you should be able to just fastboot flash boot boot.img like any other kernel, and restore your original nandroid.
Click to expand...
Click to collapse
Thank you, I've bookmarked this thread for my future use
Loving the speed of CM9 since I'm assuming its mostly due to the OC'd processor.
Twner said:
I've been playing around and checking out a few ROMS (CM9 and CM10), but since they aren't fully complete I want to go back to stock. when I rooted I made a Nandroid backup in recovery. Now If i want to go stock again do I just wipe everything and use the backup I made. Still confused because I flashed kiss kernal. Will restoring remove the kiss kernal?
Click to expand...
Click to collapse
you need to restore a kernel that is compatible with stock roms, or either the stock kernel itself. Please note, that the boot.img inside the nandroid is NOT a fastboot flashable one, and cwm will NOT flash the boot file.
Also, it is unsure, that one phones nandroid will work in an other phone, not to mention that if cid mismatches it won't even work (this is a lesson I have learned in my own faliures).
Ken-Shi_Kun said:
Also, it is unsure, that one phones nandroid will work in an other phone, not to mention that if cid mismatches it won't even work (this is a lesson I have learned in my own faliures).
Click to expand...
Click to collapse
I can confirm the nandroid from other phone is working for another phone. I just tested that. Use the nandroid backup for my phone and restore it on my wife's phone. Tested with a 2.09.707.1 nandroid backup. Once reboot, the OTA update notification is there.
Hi all,
I'm having trouble restoring backups when I go between GB and JB. Sbrissen's lastest Alpha build is the JB I'm using. Everything goes fine with the restore until "Data". Then the restore fails. I mobile odin the EL29 with autoboot into recovery, install the ROM (JB in this example) . I then try to restore a backup I made with the same exact version of CWM from the same exact ROM that I used to create the back up. Maybe a better question is How can I create a JB backup, go back to GB, and return to JB and restore that backup. Cause what I'm doing isn't working.
Thanks
Which GB ROM are you coming from? GB recoveries should be safe so you shouldn't have to Odin to EL29, unless you're on a stock ROM without a custom recovery. Also are you wiping system, data, cache, and dalvik cache prior to restoring your backup?
mwcarnage said:
Which GB ROM are you coming from? GB recoveries should be safe so you shouldn't have to Odin to EL29, unless you're on a stock ROM without a custom recovery. Also are you wiping system, data, cache, and dalvik cache prior to restoring your backup?
Click to expand...
Click to collapse
I'm using the latest Blazer GB Rom. I'm wiping everything also,factory reset,cache,dalvik cache, etc. I have to flash back to GB to update an app that requires my correct serial number to work, JB Roms do not do this at the moment so the app wont work. That is the reason for flashing back to GB (didn't want to mess with ICS for obvious reasons). I'm coming from HTC Evo 4g so things are a little different. On the Epic 4G, I was under the impression you had to use the same recovery to restore that was used to create the backup. Can I just jump back and forth between GB and JB using the nand backup with each others recovery? GB's CWM is 5 and JB's CWM is 6. I didn't think you could because if the backup won't restore with the same CWM is was created with, how would it restore with another version? Still a little foggy on the process E4GT uses.
Thanks
dal320driver said:
I'm using the latest Blazer GB Rom. I'm wiping everything also,factory reset,cache,dalvik cache, etc. I have to flash back to GB to update an app that requires my correct serial number to work, JB Roms do not do this at the moment so the app wont work. That is the reason for flashing back to GB (didn't want to mess with ICS for obvious reasons). I'm coming from HTC Evo 4g so things are a little different. On the Epic 4G, I was under the impression you had to use the same recovery to restore that was used to create the backup. Can I just jump back and forth between GB and JB using the nand backup with each others recovery? GB's CWM is 5 and JB's CWM is 6. I didn't think you could because if the backup won't restore with the same CWM is was created with, how would it restore with another version? Still a little foggy on the process E4GT uses.
Thanks
Click to expand...
Click to collapse
dal320driver said:
Hi all,
I'm having trouble restoring backups when I go between GB and JB. Sbrissen's lastest Alpha build is the JB I'm using. Everything goes fine with the restore until "Data". Then the restore fails. I mobile odin the EL29 with autoboot into recovery, install the ROM (JB in this example) . I then try to restore a backup I made with the same exact version of CWM from the same exact ROM that I used to create the back up. Maybe a better question is How can I create a JB backup, go back to GB, and return to JB and restore that backup. Cause what I'm doing isn't working.
Thanks
Click to expand...
Click to collapse
I've gone from rooted EL29 back to a a JB ROM and restored with no issues. The ROM I use is Paranoid Android. I usually allow my phone to boot then reboot into recovery before restoring. Hopefully this isn't a stupid question, but sometimes things get forgotten/overlooked when flashing ROMs. Anyways, did you flash the JB gapps after flashing the ROM? Just asking since this step was not in your posts.
mwcarnage said:
Which GB ROM are you coming from? GB recoveries should be safe so you shouldn't have to Odin to EL29, unless you're on a stock ROM without a custom recovery. Also are you wiping system, data, cache, and dalvik cache prior to restoring your backup?
Click to expand...
Click to collapse
kmok said:
I've gone from rooted EL29 back to a a JB ROM and restored with no issues. The ROM I use is Paranoid Android. I usually allow my phone to boot then reboot into recovery before restoring. Hopefully this isn't a stupid question, but sometimes things get forgotten/overlooked when flashing ROMs. Anyways, did you flash the JB gapps after flashing the ROM? Just asking since this step was not in your posts.
Click to expand...
Click to collapse
Yes, I flashed JB gapps also. I'm not having trouble re-flashing the ROM's back and forth. . This part is successful. The problem is when I go back into recovery and try to restore a backup (of either ROM just flashed) it isn't working. Sorry for the confusion.
Thanks
dal320driver said:
Yes, I flashed JB gapps also. I'm not having trouble re-flashing the ROM's back and forth. . This part is successful. The problem is when I go back into recovery and try to restore a backup (of either ROM just flashed) it isn't working. Sorry for the confusion.
Thanks
Click to expand...
Click to collapse
Okay, I was just making sure something wasn't forgotten when you were going back to JB this time around. I figured you were able to get the different ROMs working since you were able to make a backup of the JB ROM you were using. AFAIK the different versions of CWM (5 vs 6) shouldn't matter in this situation. Hopefully someone else has had the same problem and will be able to chime in.
CWM6 creates backups differently than CWM5 or most other recoveries. Instead of putting the entire backup in one folder, it has a separate Blobs folder that contains a lot of the data. If the folders get separated, the backup won't get restored correctly. Did you by any chance move the main folder or delete the blobs folder?
I am currently using cm10 with hellboy kernel and have a cvm backup of stock rom. I was wondering if *touchwood* something were to happen to the custom rom will a simple recovery be enough to get back to sense? or is there some kernel which will have to be flashed first? or is ruu the only way of going back to sense?
if u have a nandroid backup of stock ROM u can restore it and flash the boot.img found inside that particular backup.if u do not have a stock backup u will have to apply ruu or u can even restore nandroid backups of stock ROM found on XDA.
Sent from my One V
Hello,
This is probably a silly question but I was just wondering if I had to reflash the correct kernel when I restore a ROM. Let me give a scenario as I don't think I can find a decent way to word it.
Lets say I flashed PACman last week and that runs on Hellboy CM10 kernel but then I fancied a change so I did a Nandroid backup in CWM, flashed a Sense kernel (Like Titanium Kiss) then flashed a Sense ROM such as SuPrimo. If I decided to switch back to PACman would I have to flash the boot.img (Hellboy CM10 in this case) before hand or is the boot.img stored in the Nandroid backup?
I'm just curious.
Thank you,
Curtis.
Hello Curtis,
The boot.img is backed up in the nandroid backup.if you open the backup using winrar,you will be able to see it.
you will need to flash the Hellboy kernel again or Pacman will not boot.
If our device was s-off,there would be no need to flash the kernel as it would automatically flash it.
It(boot.img) is stored in the backup,but you must flash it.
U must flash boot.IMG while restoring pacman... that's what while restoring ROM first u should flash boot.IMG
Sent from my One V using Tapatalk 2