When you back up your current rom in rom manager or clockwork foes it back up the kernal too?
Yes, if you notice whenever you restore a backup it also restores whatever kernel you had flashed at the time.
Related
How do you dump an image of the phone's ROM to a file, and is it flashable via Odin when you dump it? If it is not Odin flashable, how do you make it so it can be flashed with Odin?
99% sure this isn't possible.
Closest you will get is doing a backup with ClockWork and then you can restore it to bring the phone back to the identical state it was when you made the backup.
You could probably dump the /system and make a .zip to get a flashable zip file but that's about it.
TheDub said:
99% sure this isn't possible.
Closest you will get is doing a backup with ClockWork and then you can restore it to bring the phone back to the identical state it was when you made the backup.
You could probably dump the /system and make a .zip to get a flashable zip file but that's about it.
Click to expand...
Click to collapse
So how do we get the flashable files, such as "SPH-D700-DI18-8Gb-REL.tar" that we can flash via Odin? My main issue with CWM is for when I'm messing with other ROMS. To date, despite clearing all caches and data multiple times, I've never been able to do a CWM restore without first Odin flashing the base system (Stock DI18 or DK28). Every time I've backed up (say DI18) with CWM, flashed DK28, decided to go back to my original DI18, it would never restore right. It would only do so if I first Odin'ed the stock DI18, then restored the backup.
I'd love to be able to dump my own Odin flashable backup for these purposes.
Now if CWM was a full Nandroid backup that completely re-flashed the ROM top to bottom, that would be different.
SubnetMask said:
So how do we get the flashable files, such as "SPH-D700-DI18-8Gb-REL.tar" that we can flash via Odin? My main issue with CWM is for when I'm messing with other ROMS. To date, despite clearing all caches and data multiple times, I've never been able to do a CWM restore without first Odin flashing the base system (Stock DI18 or DK28). Every time I've backed up (say DI18) with CWM, flashed DK28, decided to go back to my original DI18, it would never restore right. It would only do so if I first Odin'ed the stock DI18, then restored the backup.
I'd love to be able to dump my own Odin flashable backup for these purposes.
Now if CWM was a full Nandroid backup that completely re-flashed the ROM top to bottom, that would be different.
Click to expand...
Click to collapse
Were you making sure to flash a kernel when restoring your backup? Nandroid doesn't backup or restore your kernel. So if you updated to dk28 and then tried to restore back to di18, you would still have the dk28 kernel and would have problems. If you flash a di18 based kernel after restoring your di18 backup, you should be fine. I've found the easiest way to restore a backup is just to reflash the rom and then advanced restore /data. Your data partition is where your apps and settings will be.
hey i had skyraider then used chad's kernal and it got stuck in the boot loop. so i just restored it using the clockwork. now everything is back to normal just rooted. so...if i ever decide i want to go back to stock rom and kernal when i have custom roms and kernals cant i just restore it back to normal? does this make sense?
Is the backup you have of SkyRaider or a backup of the Stock ROM you made after rooting? You can always restore backups of anything you make to the point in which the backup was made. You should backup before flashing something new, in case you don't like it...saves lots of work.
If you want to go back to complete stock, un-rooted and all, you'd have to use the RUU. This would be putting the phone to the point just like it was when you unboxed it and turned it on.
ah ok i get it. yea i backed up before i flashed skyraider and the kernel. Thx
No problem, just some added info: the backup you make will also keep the kernel, so if you flash a custom kernel and backup the ROM, it'll keep that kernel too. So there's no need to reflash that if you restore a backup.
And s-on patch to unroot. Dont get in the situation like me where you can't s-on and use your warranty
Sent from my DROID2 using Tapatalk
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 made a nandroid backup in clockwork of the stock rom. Since then I went to a custom rom. I was wondering if I could restore the backup while on a custom rom or if I have to go back to stock and then restore it.
2. How would I get back to stock if I needed to?
Thanks
Sent from my GNex running gummy v0.7.0
You can boot into cwm from your custom rom and use it to restore the nandroid backup which will take you back into the rom as it was when you backed it up.
I suggest you make a nandroid of your current setup before hand - one can never have too many backups!
Lets say I am on a fairly stock rom and have a good TWRP backup and try a radically different rom (like a CM 10.x) and decide to go back to what I had before do I have to flash the old rom file then restore the back up file or can I just restore the TWRP backup?
You can just restore the backup but do a reset first. Eg wipe to install new rom
DavidEQ said:
Lets say I am on a fairly stock rom and have a good TWRP backup and try a radically different rom (like a CM 10.x) and decide to go back to what I had before do I have to flash the old rom file then restore the back up file or can I just restore the TWRP backup?
Click to expand...
Click to collapse
Hi - it depends on what you include in the backup on TWRP. If you select also Boot, System, Data and Recovery you will get back really everything you had. If you don't have a backup of EFS I would include that too. I did that quite often. When restoring backup you have also your old kernel/modem as it was working before. I never had bad experience with that. Whenever I'm now on CWM 6.0.3.5 as I'm using Android 4.3 (Probam 4.4).