Hi now im runing cm9 , and i was thinking to return to my stock os , but when i tried to do the restore in cwm , it showed me that md5.mismatch, i dont know what to do :/
and there is no nandroid.md5
my tab is 2 , 10.1
If you want to return to stock but your nadroid back-up got somehow corrupted then you flash a stock Rom through Odin.
There are not that many FW's for our devices, especially specific region or CSC, so you will have to use a FW with MULTI-CSC. But still this will be stock.
I had installed CWM for the GT-P5100 as opposed to the correct version for my hardware.
Prior to installing Cyanogen9 I performed a backup using cwm which went fine, but when I went to install Cm9 it failed, this was due to me installing the wrong version of cwm.
When I realised my mistake I installed cwm for the 5110 tab and my install went sweet as a nut, however, I am unable to restore my backup due to a MD5 mismatch, not being an expert I would put this down to installing the correct version of cwm for my tab, but using a different version for the backup.
Perhaps you had a similar experience hence why there is a mismatch.
Sent from my GT-P5110 using xda premium
Related
Okay so i'm not new to flashing just made a stupd mistake, i have a Bell i9000M and installed CM9.1 and everything went fine and then installed the S3 addon pack that caused a bootloop so went into recovery and flashed back my nandroid here is where i made the mistake and restored back to GB and caused all sorts of problems but long story short I am now 100% stock running GB 2.3.3 and for the life of me cannot get CWM recovery on the phone.
Everytime i install a kernal it bootloops and looks like I can't even get into stock recovery now. I used odin and flashed PDA,CSC,PHONE and tried using 512 pit file.
The phone works just can't get recovery to work or even install a custom kernal like hardcore speedmod.
Tried follow the CM wiki and no luck, that just causes a bootloop on the startup screen.
Firmware:
GT_I9000M_UGKG3_UGKG3_BMCKG3_Sbl
jebise101 said:
Firmware:GT_I9000M_UGKG3_UGKG3_BMCKG3_Sbl
Click to expand...
Click to collapse
you need root, use UGKG3 rooting kernel from My Android Collections
Thanks, I was able to get back to CM9 and finially installed the correct NANDROID using this, which is for my device
I have the international i9500 and i wanna install a custom rom (AOKP to be exact)
now my question is can i backup the official samsung rom and then return to it using recovery?
if i can so which recovery should i use? (CWM or TWRP)
i'm asking that because i couldn't backup the official samsung rom on any other device i had (S1 and S2 i9100) but maybe i did something wrong!
Anyone?
Sent from my GT-I9500 using xda app-developers app
Afaik I don't think you can literally backup any ROM. U have to have a flashable copy of it be it .tar or .zip and just backup apps
Sent from my GT-I9505 using xda premium
You can try to backup in newest CWM.
LSGio said:
I have the international i9500 and i wanna install a custom rom (AOKP to be exact)
now my question is can i backup the official samsung rom and then return to it using recovery?
if i can so which recovery should i use? (CWM or TWRP)
i'm asking that because i couldn't backup the official samsung rom on any other device i had (S1 and S2 i9100) but maybe i did something wrong!
Click to expand...
Click to collapse
You can do this from both type of recovery. Take backup on external sd card and save it to some where on HDD.
Yes flash a custom recovery (cwm etc) and backup from within there. If you ever need to reinstall, restore it also from cwm recovery and flash stock recovery and that's it. Burn to fully stock.
Sent from my GT-I9505 using xda premium
LSGio said:
I have the international i9500 and i wanna install a custom rom (AOKP to be exact)
now my question is can i backup the official samsung rom and then return to it using recovery?
if i can so which recovery should i use? (CWM or TWRP)
i'm asking that because i couldn't backup the official samsung rom on any other device i had (S1 and S2 i9100) but maybe i did something wrong!
Click to expand...
Click to collapse
I think yes.. you can back up.. (maybe Im not sure with this one)
But before restoring your back up from stock and you are coming from aokp make sure that you flash first stock rom in odin to avoid problems..
The answer is No, you can't back up your stock unrooted rom.
You can however root it, install a custom recovery and backup the rooted rom on your phone. You will need to check if it was backed up on your internal drive 1st before flashing as you will loose it if you wipe the data on your phone.
You can also go to Sammobile.com and see if they have your rom there. Go to the firmware part then check your firmware at the top . It will ask you for you device (I9500) and country then give you the latest firmware available. You will need to register to download these roms...
ultramag69 said:
The answer is No, you can't back up your stock unrooted rom.
You can however root it, install a custom recovery and backup the rooted rom on your phone. You will need to check if it was backed up on your internal drive 1st before flashing as you will loose it if you wipe the data on your phone.
Click to expand...
Click to collapse
You don't have to be rooted to flash / use a custom recovery. Therefore he can backup without rooting his device.
I did it myself before I rooted / customised my stock rom.
Sent from my GT-I9505 using xda premium
After rooting, I backup my stock rom to a external card before I start messing around. Just restore using CWM when u have a corrupted S4.
Hello, I am a novice at best when it comes to this. That being said I have successfully Unlocked my boot-loader, rooted and installed roms to my phone. Recently when using TWRP 2.7 I noticed that it would not mount data when restoring my backup. I then noticed it would not mount data when creating a new backup while using TWRP 2.7. I then installed CWM latest recovery. It does the same thing. In the process I got stuck in CWM and had to AP Fastboot to stock 4.4.2. Now with CWM it will not mount data when doing a backup. I cant load a rom without having a secure backup. What can I do? Need help! Calling all devs!
I'm pretty sure that the only recovery available is CWM for the RAZR HD. However, that recovery can't mount data. I don't think there is a custom recovery right now that had full functionality for the RAZR M.
With that said, the kernel sources have been released, so I would say its only a matter of time before an updated recovery is available that can support mounting data.
Sent from my XT907 using Tapatalk
queue72 said:
I'm pretty sure that the only recovery available is CWM for the RAZR HD. However, that recovery can't mount data. I don't think there is a custom recovery right now that had full functionality for the RAZR M.
With that said, the kernel sources have been released, so I would say its only a matter of time before an updated recovery is available that can support mounting data.
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
I have had TWRP work just fine in the past. Others are having no problem with them as I can tell. This is an original Razr M.
ehunter74 said:
I have had TWRP work just fine in the past. Others are having no problem with them as I can tell. This is an original Razr M.
Click to expand...
Click to collapse
There is no TWRP designed for the KK update, yet. CWM is only working aftermarket recovery right now. TWRP should be out any day.
OK let me give more details. I was running Beanstock Rom with Android 4.3 on my ORIGINAL XT907. I was running TWRP 2.6 flawlessly. I tried to load a new ROM (KitStock 4.4.2). When I tried to backup my current configuration with TWRP it would not mount data during the backup procedure. I panicked and backed out. I seen that CWM was a better choice and installed CWM v6.0.4.8 It also would not load data during backup. I then tried to back out of that and it got stuck on boot. would not go past no matter what. tried to load KitStock ROM anyway. Same effect. I could still get back into CWM recovery and also bootloader. I then installed the latest STOCK ROM I could find and it is version 183.46.10XT907.Verizon.en.US. Kernal is [email protected]#1. Build number KDA20.62-10.1 Android version 4.4.2
I think what I have discovered is that I must have a "working" corrupted file script whit this stock ROM. I discovered that if I formatted my SD card I could mount the data and backup my nandroid. So my SD card was corrupted??? Also after I knew I had a good backup when I tried to install CM10.1 it gave me a status 7 error. Ok did the status 7 fix by editing the script on two different ROMs. It still aborts installation. Now I consider myself a noob but I'm no stranger to the ROM installation process. I've done all the right steps. Backup. Wipe 3x, mount system, install. This seems like a deeper problem. Please HELP!
Hi
I am using a GT-i9505 black international edition running stock 4.4.2 kit kat.build id kot49h using a 16 gb ext sd with the rw fix
I've tried CWM touch, twrp , old and new philz touch, online nandroid, rom manager, twrp manager. they all install well, they make backups, but at the actual recovery they all fail to put my backup back. my phone keeps in same state, (i change the wallpaper to see if it works)
Any of you familiar with this problem, i've been searching for a long time now to find answers. A friend of mine has same problem same phone using twrp/
ANy help please?
rockah said:
Hi
I am using a GT-i9505 black international edition running stock 4.4.2 kit kat.build id kot49h using a 16 gb ext sd with the rw fix
I've tried CWM touch, twrp , old and new philz touch, online nandroid, rom manager, twrp manager. they all install well, they make backups, but at the actual recovery they all fail to put my backup back. my phone keeps in same state, (i change the wallpaper to see if it works)
Any of you familiar with this problem, i've been searching for a long time now to find answers. A friend of mine has same problem same phone using twrp/
ANy help please?
Click to expand...
Click to collapse
Anyone please?
I deleted some knox files from my gt i9505 and then my phone wouldnt boot up. It would get stuck on samsung logo. When i tried to restore a nandroid backup it said md5 mismatch. Btw i did rename thr backup and afterwards i heard this could cause problems. Then i went to the settings of philz recovery and unchecked the option where the recovery checks the md5 sum. After that i decided to try to restore again with the md5 thing off. It began to restore but then it said error restoring /system or something like that.
I managed to get my phone working again by flashing stock firmware. So how can i fix that nandroid backup?
Sent from my GT-I9505 using XDA Free mobile app
Have you tried restoring the backup again after changing to stock?
Maybe try with a different recovery if it is compatible
No
Sent from my GT-I9505 using XDA Free mobile app
And no i haven't tried a different recovery. I don't think it will wo t k because of the md5 problem.
Sent from my GT-I9505 using XDA Free mobile app
Why not try? What do you have to lose? You can always flash philz recovery back
The only other recoveries i know of is cwm. I doubt it will work because the nandroid file is in cwm format.
I still don't understand why after i skipped the step where it checks the md5 and when it finally began to restore i got the error message "error restoring /system".
Sent from my GT-I9505 using XDA Free mobile app
There is also twrp recovery. Maybe the backup got corrupted.
I used to have cwm recovery on my old device. Never had any problems with it. Since I got my S4 I'm using twrp which also seems to work without a problem. Twrp is touch based so no worries about tedious button mashing to navigate
Maybe switch to one of those as they seem to be the most popular (which also means they have better support) and they work on pretty much any device.
Okay i might switch to twrp but i wont be able to restore that nandroid backup using twrp.
Sent from my GT-I9505 using XDA Free mobile app
Try this
It's for cwm. But since your recovery is based on cwm, it should work. Alternatively you could flash cwm and try it after that guide.
If this doesn't work then do some more searching. Just google "md5 mismatch" it should give you something to work with and, hopefully, a solution.
just reflash your rom, i had this too and what helped was a clean install