Related
I have an unlocked and rooted Samsung Galaxy S2. I installed MIUI and am now experimenting with different kernels.
Is there a way to backup and restore the kernel only, rather than doing a full nandroid backup and restore? I searched all over the web and all I could find was this advice to:
"just grab the boot.img and contents of /system/lib/modules from your rom zip and make your own update.zip."
http://forum.xda-developers.com/archive/index.php/t-1059412.html
But I found no comment confirming it actually does work. There is a kernel flasher app that's supposed to backup and restore kernels, but it only works on the Galaxy S (not the S2).
Thoughts?
Thanks!
In the past, I used SGS Kernel Flasher to backup a kernel before flashing new one. However, I'm on ICS now and SGS Kernel Flasher say it is incompatible and supported after loading it. I want to try new kernel but want to take a backup of existing kernel before testing new one. How do I do it manually? Do I just take files and drop it in zip? Also, what's the easier way to back it up?
I'm have paid ROM Manager, Titatium backup, and Root Explorer.
If you look inside a kernel zipfile, there is quite a lot going on in addition to just flashing boot.img to the boot partition. To do it right, you'd need to copy not just the boot.img but all other files installed, and on reinstall you would need to do everything the updater-script does with permissions, etc.
If you are on ICS, and I'm not mistaken a full nandriod also now backs up your kernel.
Nandroid backup, try the new kernel, restore if needed.
Hey guys,
So I heard somewhere on various posts that Nandroid backup through CWM doesn't backup your stock kernel, only /system+ROM. Is that true, and if so, how do I actually backup my stock kernel? I have an HTC Explorer.
Thanks.
AIndoria said:
Hey guys,
So I heard somewhere on various posts that Nandroid backup through CWM doesn't backup your stock kernel, only /system+ROM. Is that true, and if so, how do I actually backup my stock kernel? I have an HTC Explorer.
Thanks.
Click to expand...
Click to collapse
CWM does backup your stock kernel in boot.img extract that and take out the zImage if you only want the kernel, or just keep the whole boot.img in the backup folder
CdTDroiD said:
CWM does backup your stock kernel in boot.img extract that and take out the zImage if you only want the kernel, or just keep the whole boot.img in the backup folder
Click to expand...
Click to collapse
thanks for info.. im searching for this..
So, anyone knows an nandroid backup explorer for backups made with CWM 6+? Neither App Extractor and Nandroid explorer works.
"I got my values. So you can keep yours, OK?"
Ugh I'm looking for the same. Titanium Backup won't read them either. Need a file out of my nandroid and going crazy trying to find a way.
I'm using Unstable Apps Touch CWMR latest.. it's CWM 6 based.
Hi, all.
I've been reading and searching, but haven't found any info related to my problem.
Prior to upgrading to 4.2.1, I made a NANDROID backup of my Nexus 7 (4.1.2) using mskip's toolkit. The restoration method copies the backup folder to the device (/sdcard/clockworkmod/backup/), then boots it into custom recovery. At first I was using TWRP 2, but I think I need to be using CWM, so I flashed CWM Touch. I actually went through the motions again of copying the backup over to the Nexus 7, but CWM Touch doesn't see the backup folder. It returns two messages when attempting to Restore:
1. Couldn't open directory
2. No files found
Same with Advanced Restore.
The folder containing the NANDROID backup and all parent folders are readable/writable/NOT Hidden, according to ES File Explorer, but I wonder about ownership.
I'm rooted with SuperSU 0.99.
Anyone have any suggestions about how to make CWM Touch, TWRP 2 or some manual method recognize and restore a NANDROID backup?
I know I could just flash stock 4.1.2 and start from scratch (I have apps + data backed up), and if it comes to it, I'll do that, but while I have some time, I thought I'd make this a learning experience.
Thanks.
ThurstonX said:
...
Click to expand...
Click to collapse
Same problem here, any solutions?
xXSturmiXx said:
Same problem here, any solutions?
Click to expand...
Click to collapse
I posted this a few minutes ago. It may be TL;DR, but it's got all the gory details.
I'm not sure exactly what's going on, but in essence, you can use adb to push the NANDROID backup folder to /data/media/clockworkmod/backup/, then boot into recovery and CWM will see it.
The weird thing is, after I restored the 4.1.2 factory ROM, rooted, flashed CWM Touch, and then ran a backup from within CWM to create /data/media/clockworkmod/backup/ ... /sdcard/clockworkmod/backup/ was also created. I guess it's a symlink...? Haven't explored that yet, but I seriously doubt the backup data is being duplicated.
Anyway, after pushing my original backup folder to /data/media/clockworkmod/backup/, it's also listed under /sdcard/clockworkmod/backup/ That's why I say symlink.
I was able to restore while still running 4.2.1, but /sdcard/0 still had all apps and data there, which is why I decided to just go back to stock 4.1.2 before restoring my 4.1.2 NANDROID backup. Maybe I did something wrong, but I don't think so.
So yeah, the new CWM Touch Recovery is backward compatible. My 4.1.2 backup did NOT use CWM, so no "blobs" and all that. Good news there.
I suppose if you're restoring a 4.2.x backup over a custom ROM based on 4.2.x, but CWM can't see the backup folder under /sdcard/clockworkmod/backup/ just push it to /data/media/clockworkmod/backup/ and you should be good to go.
Anyone know if a 4.1.2 NANDROID backup can/should be restored over a 4.2..x install? Is the /sdcard/0 problem really a problem. NANDROID doesn't back up /sdcard, correct? I'm guessing it does not.
Boot into recovery w/your tablet plugged into your computer
Code:
adb devices
adb remount
abd pull ./where/your/backup/is/located
adb push ./yourbackup /where/it/needs/tobe
or if you have a jacked rom and cant do anything, you can do what I did
Code:
adb devices
adb remount
adb push ./newrom /sdcard
adb reboot recovery
then wipe and flash your new rom