Few days ago I faced MD5 mismatch error while restoring my backup after messed with my phone. But due to this error I couldn't restore backup. I asked many people but people said that I should now flash sock firmware which was really a headache for me.
Anyway I searched alot on xda & I found very easy solution.
It don't require pc or adb shell etc. It only requires rooted phone with Terminal Emulator app
STEP 1: Open Terminal Emulator
Step 2: Use the following commands. (DON'T FORGET TO REPLACE "2012-01-01.10.09.36" WITH YOUR OWN BACKUP FOLDER NAME WHICH WILL BE PRESENT IN folder /clockworkmod/backup/)
Code:
su
#mount -o remount rw /sdcard
#cd /sdcard/clockworkmod/backup/2012-01-01.10.09.36
#rm nandroid.md5
#md5sum *img > nandroid.md5
STEP 3: (This will create a new "nandroid.md5" file without ANY "md5 mismatch" errors )
Reboot your phone and enter Recovery mode & then restore.
I hope it will help you in future
ENJOY...
IMP NOTE :- Many times people change backup folder name which can create this error. So be sure that you have not changed your backup folder name & also be sure that there is no space in backup folder path.
Credit goes to UsmanJ member. I have just shared with you guys with more good explanation.
Original thread HERE
Click to expand...
Click to collapse
No need these at all you need "root toolbox". and ut works perfectly by the way thanks for sharung this way too
Tapatalk 2 ile GT-I9003 cihazımdan gönderildi
If you do this you can't be sure that your backup isn't broken. md5 needs exactly for checking this. Yes, you cheated the check system, but are you sure that your backup integrity is fine?
This problem is mainly due to folder name change. If you don't change folder name you shouldn't be having this problem.
silentvisitor said:
This problem is mainly due to folder name change. If you don't change folder name you shouldn't be having this problem.
Click to expand...
Click to collapse
Ya but sometimes we have to face this problem even if we dont change folder name like how it was happened in my case few days ago.
Well, I think this is no hint you should use. When creating a new backup md5 hashsums are calculated for each file. If you now want to restore it these hashsums are calculated again and compared to the previous ones. Only if the data is the same as before , in other words your backup hasn't been damaged, the checksums match. You may have had some luck that the error happened in a file that does not get used very often but in general you do not want to do that, just imagine your kernel backup is broken!
Sent from my GT-I9003 using XDA
Thanks, worked just fine for me.:good:
The error is not only because of changing the name of folder, as vishal says md5 mismatch can occur.
I even encountered the following problem with nandroid backup.
stock gb,xxkpu nandroid not compatible over cm9 or miui.
Or miui/CNET not compatible over stock rooted ROM.
I'm not sure of the reason why this error occurs while reporting the nandroid backup, but according to my limited knowledge of Android, I suppose either ext4 partition is not compatible over rfs of stock and vice versa or, out might be a kernel clash.
To be true, I didn't even try to search much about the issue as I'm mostly free and take the pain of customizing three new firmware as power my preference and reinstalling the app
Sent from my GT-I9003 using xda premium
If anyone is sure of the error and it's solution, the answer is most welcome.
P.s. while restoring out doesn't say md5 mismatch (I've also come across this though), the error I stated cannot restore the boot image atty the first place.
Sent from my GT-I9003 using xda premium
@ Iambalvindar
You are right bro. There can be number of reasons about this md5 mismatch error. Actually the solutuion which I have provided is just an option to correct error If error is due to other reason such corrupted backup then obviously the solution given in my thread will not be applicable.
The first two commands ('su' and 'mount') are not necessary because:
You don't need root permissions to edit stuff in /sdcard
/sdcard is always mounted as RW (that's what the second command does.)
EDIT:
I've just remembered that if you don't have busybox installed you don't have the 'md5sum' command avaible for the user.
However our CF-root kernels come with an inbuilt busybox, but it can't be used as normal user, because if I remember correctly all the symlinks are in /sbin, where the user has no access. So, probably, you need to do this as root (= type the 'su' command as in the OP).
Anyway, nandroid.md5 is the last thing made during a backup. That means if you don't have enough space for the backup and it stops, this file is not created. So, when you go to restore that backup, you have the mismatch error. In this case, if you create the nandroid.md5 as vishal wrote, you'll have a usable and damaged backup. So, before doing this, check if nandroid.md5 is there or, when you run "rm nandroid.md5", make sure the output is not "No such file or directory", because it means that most likely the backup is not complete.
All of these to say: be careful and do this if necessary (unless you know what you are doing of course).
A suggestion:
In this situation you can do an "advanced restore" and restore only /data and /datadata if you are using the same ROM you used for the backup (maybe a slightly different ROM is good too). The only things not restored are the mods you applied and system apps, but for the mods, simply reflash them, for the system apps, well, they are always the same. All the apps installed through the market are in /data.
Maybe this will cause bootloops, but in this case you can simply reboot in recovery and do a data wipe/factory reset. This will let you boot without the need of a reflash. You have of course to reinstal all your apps etc, but it's better than starting from scratch.
Or, even better, do a backup before the restore of /data and /datadata, so that in case of problems you can always restore everything.
EDIT 2:
I think you can do this even when you change ROM, as long as it's a stock ROM. That's because stock ROMs are intended to be flashed over another stock ROM and they are made in a way that you don't need to wipe your /data partition. When you use kies to upgrade, you don't loose anything. Restoring /data and /datadata should have the same effect (it's better to wipe the dalvik-cache after this).
@vishal: I'm not referring to corrupted backups. Sometimes later, even working backups fail to be restored after some ROM and kernel change.
Sent from my GT-I9003 using xda premium
iAmBalvinder said:
@vishal: I'm not referring to corrupted backups. Sometimes later, even working backups fail to be restored after some ROM and kernel change.
Sent from my GT-I9003 using xda premium
Click to expand...
Click to collapse
Ya its because different kernels have different cwm version & also different kernels creat different md5 code as per backup.
iAmBalvinder said:
@vishal: I'm not referring to corrupted backups. Sometimes later, even working backups fail to be restored after some ROM and kernel change.
Sent from my GT-I9003 using xda premium
Click to expand...
Click to collapse
I think you can do it, nandroid backups are the exact copy of the ROM you are running (the radio is not backed up).
The problem is that maybe you did a backup of Gingerbread using amit's CWM. His CWM is able to backup the kernel (normalboot.img), but he disabled this feature because he couldn't test it, so he thought it would be safer not to enable it. UC team however enabled it (that's what I can see from their recovery.fstab).
If you used amit's recovery to backup the ROM, when you restored it from CyanogenMod you didn't restore the kernel. So, when you turned the phone on, you tried to boot a stock ROM with a CM kernel.
Maybe if you flash a stock kernel after the restore with odin it will boot.
And if you tried to restore a CM backup (so with the kernel backed up) with amit's kernel, you didn't restore the kernel amit's recovery ignores it, so you tried to boot CM with a stock ROM kernel.
Maybe backups made from different CWM versions are not compatible, but I think Koush is trying to avoid this, but I'm not sure.
Another problem could be that CM is not yet finished and the continous changes in recovery cause new bugs that could affect the way backups are done (it recently happened).
Maybe I'm saying stupid things, but that's what I know. I'm not so interested in backups and restores, I rarely use them, so I've never tried to study well enough how they work etc. Correct me if I wrote something stupid.
Anyway, I'm sure that the md5sum error has nothing to do with the kernel you used to make the backup.
Every file has a unique md5 hash, it doesn't matter if you calculate it with your phone, with your computer or with your fridge (if you can ), the result is always the same. What CWM does before starting a restore is to re-calculate the md5 of each file inside /sdcard/clockwrockmod/backup/XXXXX/ and to compare them with the ones stored in /sdcard/clockwrockmod/backup/XXXXX/nandroid.md5 when you made the backup (open this file with a text editor and see). If they are all equal, it means the backup is not corrupted, so it's safe to start the restore.
I think you could even restore a backup of another phone (maybe there are some other check here and there to prevent this), but of course don't try it .
loSconosciuto said:
I think you can do it, nandroid backups are the exact copy of the ROM you are running (the radio is not backed up).
The problem is that maybe you did a backup of Gingerbread using amit's CWM. His CWM is able to backup the kernel (normalboot.img), but he disabled this feature because he couldn't test it, so he thought it would be safer not to enable it. UC team however enabled it (that's what I can see from their recovery.fstab).
If you used amit's recovery to backup the ROM, when you restored it from CyanogenMod you didn't restore the kernel. So, when you turned the phone on, you tried to boot a stock ROM with a CM kernel.
Maybe if you flash a stock kernel after the restore with odin it will boot.
And if you tried to restore from a CM backup (so with the kernel backed up) with amit's kernel, you didn't restore the kernel amit's recovery ignores it, so you tried to boot CM with a stock ROM kernel.
Maybe backups made from different CWM versions are not compatible, but I think Koush is trying to avoid this, but I'm not sure.
Another problem could be that CM is not yet finished and the continous changes in recovery cause new bugs that could affect the way backup are done (it recently happened).
Maybe I'm saying stupid things, but that's what I know. I'm not so interested in backups and restores, I rarely use them, so I've never tried to study well enough how they work etc. Correct me if I wrote something stupid.
Anyway, I'm sure that the md5sum error has nothing to do with the kernel you used to make the backup.
Every file has a unique md5 hash, it doesn't matter if you calculate it with your phone, with your computer or with your fridge (if you can ), the result is always the same. What CWM does before starting a restore is to re-calculate the md5 of each file inside /sdcard/clockwrockmod/backup/XXXXX/ and to compare them with the ones stored in /sdcard/clockwrockmod/backup/XXXXX/nandroid.md5 when you made the backup (open this file with a text editor and see). If they are all equal, it means the backup is not corrupted, so it's safe to start the restore.
I think you could even restore a backup of another phone (maybe there are some other check here and there to prevent this), but of course don't try it .
Click to expand...
Click to collapse
Cool, thx for the info. Nv knew the difference between the kernels
Sent from my GT-I9003 using xda app-developers app
loSconosciuto said:
I think you can do it, nandroid backups are the exact copy of the ROM you are running (the radio is not backed up).
The problem is that maybe you did a backup of Gingerbread using amit's CWM. His CWM is able to backup the kernel (normalboot.img), but he disabled this feature because he couldn't test it, so he thought it would be safer not to enable it. UC team however enabled it (that's what I can see from their recovery.fstab).
If you used amit's recovery to backup the ROM, when you restored it from CyanogenMod you didn't restore the kernel. So, when you turned the phone on, you tried to boot a stock ROM with a CM kernel.
Maybe if you flash a stock kernel after the restore with odin it will boot.
And if you tried to restore a CM backup (so with the kernel backed up) with amit's kernel, you didn't restore the kernel amit's recovery ignores it, so you tried to boot CM with a stock ROM kernel.
Maybe backups made from different CWM versions are not compatible, but I think Koush is trying to avoid this, but I'm not sure.
Another problem could be that CM is not yet finished and the continous changes in recovery cause new bugs that could affect the way backups are done (it recently happened).
Maybe I'm saying stupid things, but that's what I know. I'm not so interested in backups and restores, I rarely use them, so I've never tried to study well enough how they work etc. Correct me if I wrote something stupid.
Anyway, I'm sure that the md5sum error has nothing to do with the kernel you used to make the backup.
Every file has a unique md5 hash, it doesn't matter if you calculate it with your phone, with your computer or with your fridge (if you can ), the result is always the same. What CWM does before starting a restore is to re-calculate the md5 of each file inside /sdcard/clockwrockmod/backup/XXXXX/ and to compare them with the ones stored in /sdcard/clockwrockmod/backup/XXXXX/nandroid.md5 when you made the backup (open this file with a text editor and see). If they are all equal, it means the backup is not corrupted, so it's safe to start the restore.
I think you could even restore a backup of another phone (maybe there are some other check here and there to prevent this), but of course don't try it .
Click to expand...
Click to collapse
Yeah, most probably be that was the issue... Kernels needed to be changed.
Thanks
And I already saw that my backup was not corrupted with md5 check.
Moreover, I also don't use nandroid much, I always configure new ROM I try, from the scratch.
It's just that I needed to use USB storage urgently, which sadly doesn't work on any ics based ROM. So tried to restore the backup. Alas !
Had to flash again from scratch to get to stock gb, as I didn't have any gb.zip in sd card or computer.
Sent from my GT-I9003 using xda premium
i am not able to restore my backup due to mismatch md5
vishal24387 said:
Few days ago I faced MD5 mismatch error while restoring my backup after messed with my phone. But due to this error I couldn't restore backup. I asked many people but people said that I should now flash sock firmware which was really a headache for me.
Anyway I searched alot on xda & I found very easy solution.
It don't require pc or adb shell etc. It only requires rooted phone with Terminal Emulator app
STEP 1: Open Terminal Emulator
Step 2: Use the following commands. (DON'T FORGET TO REPLACE "2012-01-01.10.09.36" WITH YOUR OWN BACKUP FOLDER NAME WHICH WILL BE PRESENT IN folder /clockworkmod/backup/)
Code:
su
#mount -o remount rw /sdcard
#cd /sdcard/clockworkmod/backup/2012-01-01.10.09.36
#rm nandroid.md5
#md5sum *img > nandroid.md5
STEP 3: (This will create a new "nandroid.md5" file without ANY "md5 mismatch" errors )
Reboot your phone and enter Recovery mode & then restore.
I hope it will help you in future
ENJOY...
IMP NOTE :- Many times people change backup folder name which can create this error. So be sure that you have not changed your backup folder name & also be sure that there is no space in backup folder path.
Click to expand...
Click to collapse
i was using another bootloader and another cwm
Vishal, can you summarize every thing and update first post.
According to my understanding,
1. Do not change backup folder name.
2. Do not restore backup using different recovery than the one used, i.e. Use gb recovery to restore gb Rom, cm7 recovery to restore cm7 Rom and so on.
These are the main cause of md5 error, else better to assume the backup is corrupted.
Recalclating the md5 and restoring could have adverse effect on the system.
Sent from my LT28h using xda premium
ganeshbiyer said:
Vishal, can you summarize every thing and update first post.
According to my understanding,
1. Do not change backup folder name.
2. Do not restore backup using different recovery than the one used, i.e. Use gb recovery to restore gb Rom, cm7 recovery to restore cm7 Rom and so on.
These are the main cause of md5 error, else better to assume the backup is corrupted.
Recalclating the md5 and restoring could have adverse effect on the system.
Sent from my LT28h using xda premium
Click to expand...
Click to collapse
ok buddy I will update information in few minutes
I am still waiting for ur test kernel with modules inbulit in it.
I was on the same issue as all people with MD5 failure, then I rename my backup name with a short name with no space or blank and the it run like a charme !.
Hope it could help.
My GT7+ has the LB2 firmware. I have not seen any copy of this firmware for downloading. Therefore I have been cautious and stick with the stock kernel and FW.
I installed garyd9's CWM and made nandroid backup. I want to try garyd9's custom kernel, but I read the warning on his post about compatibility with some firmwares.
I wonder if I flash his custom kernel and it fails, can I revert back to my stock kernel through nandroid restore?
Thanks.
Nandroid backup is a complete backup of your phone. When we say complete, it means everything on your phone – your apps, data, your current ROM and even the kernel. It is like creating a full system image of your phone that can be restored later, when required. - Restore from a Nandroid Backup via Recovery:
1. The first two steps are same as above. Boot into Recovery and navigate to the Nandroid screen.
2. Select ‘Restore’ to start the process. If you choose the ‘Advanced Restore’ option, you can select which component of the backup to restore – like the boot, system, data or cache. 3. Reboot system. Your system is now restored and is exactly same as the time when the backup was taken.-- Backup and Restore Using ROM Manager:
If you think the above process was easy, backup and restore through ROM Manager is even easier. ROM Manager automates the whole of the above process giving you the option to do these operations with a single touch. Just choose ‘Backup Current ROM’, enter a name for the backup and the phone reboots to start the backup process. There, your backup is complete. To restore, launch the app and select ‘Manage and Restore Backups’. Select the backup that you want restored and ROM Manager will do the rest.
You can delete or rename the backups as well.
Thanks for the reply. Now I feel more comfortable and adventurous.
BTW, I see that there is no copy of the official Samsung LB2 firmware floating around. I do not know how to make a tar file for the firmware / ROM, but would anyone be interested in a nandroid copy of the LB2? I can reset the tablet, go to CWM to save a nandroid copy of the default firmware, then restore my own running copy.
Hello, I have recently been able to install and make a backup of my SGH-I727 using CWM. I have also purchased Titanium backup and made application backups.
I have a few specific questions that I have not been able to find an answer to :
1) Will a CWM backup contain all the apps that are on the phone as well? Meaning, if I restore with a backup image I made, will the
unit be exactly as it was before the backup (i.e. home pages, apps, etc)?
2) If the answer to #1 is YES, then what is the use of Titanium backup/restore?
3) I saw on a YOUTUBE video a user "teaching" how to use CWM, before the RESTORE, he formatted the /cache, /data and /system partitions, then did the RESTORE. Is this needed? required? recommended? best practice?
4) I have gb 2.3.5 on the device now and it works fantastic. I would like to try ICS but before I go there, I want to make sure I have a way to get back to what I have now. Is a CWM backup all I need?
5) Will installing a stock Kernel (ICS AT&T in my case) get rid of CWM Recovery? Or will it be there when I want to go back to the backed up version?
6) Lastly, and maybe this one should not be in this thread but lets try : I am learning about Android, and I see references to the "modem/radio" files for each device. Will a CWM backup also backup the radio/modem code in case the ICS install does not go as planned?
Thank you!!
I think you need to do more reading. Many of these questions have been answered.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
1. Yes a cwm or twrp b/u will put all your apps back just like you never left.!
2. You use titanium when you flash a new rom because of course the new rom won't contain your apps.
3. I've done lots and lots of restores and never wiped first....but wouldn't hurt i guess.
4.yup.!
5.no the recovery remains untouched.
6.I don't think the radio gets backed up or restored. But it's not critical to the rom operation and can be reflashed when ever..
calderonr said:
Hello, I have recently been able to install and make a backup of my SGH-I727 using CWM. I have also purchased Titanium backup and made application backups.
I have a few specific questions that I have not been able to find an answer to :
1) Will a CWM backup contain all the apps that are on the phone as well? Meaning, if I restore with a backup image I made, will the
unit be exactly as it was before the backup (i.e. home pages, apps, etc)?
2) If the answer to #1 is YES, then what is the use of Titanium backup/restore?
3) I saw on a YOUTUBE video a user "teaching" how to use CWM, before the RESTORE, he formatted the /cache, /data and /system partitions, then did the RESTORE. Is this needed? required? recommended? best practice?
4) I have gb 2.3.5 on the device now and it works fantastic. I would like to try ICS but before I go there, I want to make sure I have a way to get back to what I have now. Is a CWM backup all I need?
5) Will installing a stock Kernel (ICS AT&T in my case) get rid of CWM Recovery? Or will it be there when I want to go back to the backed up version?
6) Lastly, and maybe this one should not be in this thread but lets try : I am learning about Android, and I see references to the "modem/radio" files for each device. Will a CWM backup also backup the radio/modem code in case the ICS install does not go as planned?
Thank you!!
Click to expand...
Click to collapse
1. 99.9% back to what you had
2. if you install a new rom you can use titu to restore your apps and settings, 99.9% of apps should work, but some people like reinstalling thier apps fresh and not from backups
3. i wipe b4 i reinstall from backup, but dont wipe/format your sdcards, thats where all the backups of cwm and titu are, good practice is to backup your sdcards onto your computer, that reminds me, i need todo that
4. yes except for the radio
5. if you mean stock firmware , then yes custom recovery gone, you will get everything back to stock - recovery, kernel, rom, radio. if you mean just the kernel then no
6. no cwm/twrp do not backup or wipe the radio , you will still have what you had b4, but the ics stock firmware install you will get another radio and should be fine, worry about flashing the firmware correctly(do the wipes), radio is easy to flash/reflash with custom recovery(cwm/twrp)
vincom said:
1. 99.9% back to what you had
2. if you install a new rom you can use titu to restore your apps and settings, 99.9% of apps should work, but some people like reinstalling thier apps fresh and not from backups
3. i wipe b4 i reinstall from backup, but dont wipe/format your sdcards, thats where all the backups of cwm and titu are, good practice is to backup your sdcards onto your computer, that reminds me, i need todo that
4. yes except for the radio
5. if you mean stock firmware , then yes custom recovery gone, you will get everything back to stock - recovery, kernel, rom, radio. if you mean just the kernel then no
6. no cwm/twrp do not backup or wipe the radio , you will still have what you had b4, but the ics stock firmware install you will get another radio and should be fine, worry about flashing the firmware correctly(do the wipes), radio is easy to flash/reflash with custom recovery(cwm/twrp)
Click to expand...
Click to collapse
Hi Vincom and all,
Thanks for the responses....Very useful and I think I am putting all the dots together now. Before I ask this let me say that I am a computer programmer as well but for IBM mainframe systems, so I am a technical person but the distributed computing world (Windows/Unix/Linux, etc) is not that familiar to me, therefore these follow up questions.
I am trying to understand the difference between FIRMWARE, and ROMS and Kernels.
1A) I gather firmware is the software that drives the hardware like device drivers..correct?
2A) I also gather that the Kernel is the version of the operating system. Correct?
3A) ROM is the one that is stomping me a bit...is that the UI version? Like Gnome in Linux?
When I look at my S2, in About Phone I see the following :
Baseband Version - I727UCKJ2
Kernel Version - 2.6.35.11
Build Number GINGERBREAD.UCKJ2
4A) Lastly, when I do a CWM backup, what am I backing up? The ROM and the Kernel? Does it also back up the firmware?
Anyway thanks to all for your input and help!...I love my Android device!
Hello there, To answer a few of your questions.
1.A. Typically Firmware is a patch or software update/version that affects what the hardware is supposed to do..Google definition-Permanent software programmed into a read-only memory.
2.A. Kernel - pretty good explanation of it...
3.A. Google definition - The Android ROM is the Android operating system. This is the User interface (Sense UI in HTC phones) and the file system for maintaining contacts etc. It is composed of a Linux kernel and various add-ons to achieve specific functionality.- I would define it as a user-developed version of android if we are talking about custom ROMs.
4.A. Yes when you back up it backs up everything except the radio.
To further explain why people might use TIBU and CWM/TWRP is because most people make a full nandroid (cwm backup) for safety / oops moments or just to try out a different rom. TIBU is usually used when users go from rom to rom and dont want to mess with playstore taking its sweet time to reinstall. (only restore app/app data. NEVER RESTORE SYS DATA unless on the same version of android. the sys files are always different rom to rom or version to version)
Baseband is the Radio, Just fyi there are several different versions of radios for our phone but they are typicall Version specific. ie: gb radios wouldnt work on JB
Not as a troll or flame but I am just curious why you are still using GB? My advice is just to install cm10 + gapps and look up installing cyandelta from the playstore.
I offer that as a suggestion because it will update your phone autonomously. also review the forums for which radios are best for cm (I'm still using uclf6 even though there are newer versions)
Hello guys, this is going to be a long post andam very sorry about that. So, I got a Samsung galaxy note2 and I want to install the latest firmware which is version 4.3. Also, I'll like to try some android 4.4 custom rom. Am currently using version 4.1.2. Seriously, i've searched many threads without a satisfactory answer before restorting to start one. Before going on this adventure I'll like to do a complete backup of my original rom so i can go back to it anytime. I've decided to use nandroid for the full image backup (clockworkmod) and titanium for subsequent application and applications data backup. I know what these two apps do but I still have some questions.
1) What's is the safest way to root and unroot my device?
2) what files/apps do I need to do a nandroid and titanium backup and where do I get them?
3) can I keep this backups on my external sdcard, will I be able to access it from external sdcard on recovery mode incase my phone crashes?
4) someone said even after using the nandroid backup, I'll still have to Flash the kernel, what does this mean and how do I do that?
5) I plan using clockworkmod cos it sounds like a good idea. How do I get and use it.
Now I made a mess of myself asking all these questions. I'll still post it nonetheless cos I really need help with these questions or I wouldn't have asked. Thanks in advance guys. Once again, sorry for the long post.
1) any way that has been tested by the device users or devs, instructions should be followed clearly..
2) CWM needed for nandroid backup & Titanium Backup app is needed for data backups.
CWM would be available in dedicated threads for your device.
Titanium Backup app would be available in playstore
3) You can. :thumbup:
4) There are 2 ways AFAIK,
i. adb method to place the kernel inside the device
ii. Zip file flashing through CWM
5) Same answer as for Q2
Hit thanks rather than typing it now Free
Parkourkarthik, thanks so much for your quick response. Sorry to bother you further. About kernel flashing, is it that I'll have to flash the kernel every time I restore from my nandroid backup? I guess I'll have to download the kernel for my device before hand, so where do l keep It so CWM could use it.
adoy005 said:
Hello guys, this is going to be a long post andam very sorry about that. So, I got a Samsung galaxy note2 and I want to install the latest firmware which is version 4.3. Also, I'll like to try some android 4.4 custom rom. Am currently using version 4.1.2. Seriously, i've searched many threads without a satisfactory answer before restorting to start one. Before going on this adventure I'll like to do a complete backup of my original rom so i can go back to it anytime. I've decided to use nandroid for the full image backup (clockworkmod) and titanium for subsequent application and applications data backup. I know what these two apps do but I still have some questions.
1) What's is the safest way to root and unroot my device?
2) what files/apps do I need to do a nandroid and titanium backup and where do I get them?
3) can I keep this backups on my external sdcard, will I be able to access it from external sdcard on recovery mode incase my phone crashes?
4) someone said even after using the nandroid backup, I'll still have to Flash the kernel, what does this mean and how do I do that?
5) I plan using clockworkmod cos it sounds like a good idea. How do I get and use it.
Now I made a mess of myself asking all these questions. I'll still post it nonetheless cos I really need help with these questions or I wouldn't have asked. Thanks in advance guys. Once again, sorry for the long post.
Click to expand...
Click to collapse
for cwm check your device forum and you b=can take nandroid backup and if anything goes wrong you can backup with that
and for your question what all nandroid backup include here is the answer
nandroid backup includes
system partition
cache partition
data partition
boot partition
boot partition means kernel is included in boot partition only so kernel is also backed up in nandroid backup
---------- Post added at 04:39 PM ---------- Previous post was at 04:34 PM ----------
adoy005 said:
Parkourkarthik, thanks so much for your quick response. Sorry to bother you further. About kernel flashing, is it that I'll have to flash the kernel every time I restore from my nandroid backup? I guess I'll have to download the kernel for my device before hand, so where do l keep It so CWM could use it.
Click to expand...
Click to collapse
if you restore nandroid backup you will automatically get stock kernel because nandroid backup includes boot partition where kernel is found
no need to flash kernel everytime
and you can keep kernel anywhere but if you simply download kernel image file or md5 file you an install it only with universal kernel flasher or adb you cant install that file directly in cwm
it must be a flashable zip to install in cwm to install it