Unable to Flash the LG-E980 KitKat backup posted in this link - LG Optimus G Pro

Original Post here:
http://forum.xda-developers.com/showthread.php?t=2760895
I have downloaded the backup zip file, extracted it, copied to the sdcard, booted into recovery but when I attempt to restore I get a "MD5 Mismatch" error.
I've read through quite a few pages of the original post, but all I see is a lot of people saying it worked for them.
I am running 4.1.2 rooted, CWM 6.0.4x.
Can someone shed some light on what I'm doing wrong?
Thanks,
Mike

SOLVED
I found the issue on page 8 of the original thread. I read up to page 6 before I figured I was the only one having the issue and posted.
It was of course the fact that the files were extracted into an additional subdirectory and I was not pointing the recovery to that extra sub-dir. Once I moved the files up one level the restore went perfectly.
Mike
valgrom said:
Original Post here:
http://forum.xda-developers.com/showthread.php?t=2760895
I have downloaded the backup zip file, extracted it, copied to the sdcard, booted into recovery but when I attempt to restore I get a "MD5 Mismatch" error.
I've read through quite a few pages of the original post, but all I see is a lot of people saying it worked for them.
I am running 4.1.2 rooted, CWM 6.0.4x.
Can someone shed some light on what I'm doing wrong?
Thanks,
Mike
Click to expand...
Click to collapse

Related

Flashing Android Revolution, Installation aborted (BAD), checksum fine

I tried to flash my Desire HD today.
I followed this guide http://forum.xda-developers.com/showthread.php?t=964996&highlight=Installation+aborted.
Followed it down to every detail, but after i have runned the FULL-WIPE-1-2-3, and started installing the Android Revolution rom i get this error message:
E:Cant't open /sdcard/Android_Revolution_HD-4G-3.2.zip
(bad)
Installation aborted.
I tried to download from another mirror, and ran a MD5 checksum on the file after download, and checked it up against the MD5 checksum that i found in the Android Revolution thread, and it was exactly the same.
What the hell is wrong?
May be a problem with your SD card. Do you have access to another one?
Hmm, no i dont have another SD card
I said i followed the guide to every bit, but i forgot that i skipped the radio step.
I did not flash the radio because i didnt know which radio to flash.
But now i saw that in the Android Revolution thread the recommended a radio, so i downloaded that radio and flashed it.
Could this cause the problem i had? That i didnt flash the radio before i flashed the Android Revolution rom?
I restored the nanodroid backup in clockwork so that i now have a working phone again, but damn i want this to work. If i do a wipe again will it delete the backup i made in clockwork recovery or do i have to make a new backup after i wipe?
SOLVED!!
I got it right now. Dont know for sure which of the things i did that made it working, but ill write em down if someone else has this problem.
- Downloaded the radio suitable for the rom, and flashed it
- Downloaded the rom flash image for the 5th time, this time i downloaded it via torrent
- Renamed the Android_Revolution_HD-4G_3.2.zip to update.zip
b1rken said:
SOLVED!!
I got it right now. Dont know for sure which of the things i did that made it working, but ill write em down if someone else has this problem.
- Downloaded the radio suitable for the rom, and flashed it
- Downloaded the rom flash image for the 5th time, this time i downloaded it via torrent
- Renamed the Android_Revolution_HD-4G_3.2.zip to update.zip
Click to expand...
Click to collapse
Thanks SO MUCH it helped! I redownloaded file (now 198 Mb to 128 Mb I had primordially) and renamed it to update.zip
P.S. I have HTC Desire, but I guess this problem is common
Solved, too.
Seems that I've solved the same problem in a much more weird and simpler one. Reboot, redo it, done!
Got a similar problem when installing the revolutionhd rom stuff next, and reboot, redo it, done!
No idea coz I'm a noob and would love to be a noob. I hate the processes to get the result I desire, so I have to suffer from it like a soldier who has to plant lots of flowers to get to the girl.

[Q] Bad .zip error

I get the error:Can't open /sdcard/.....zip(bad)
Any other solutions besides the one in the older thread. It's directions were not clear at all.
It's a bad dowload.....try redownloading....happens to me all the time when DL'in from my PC....not sure what the other responses to u were.....but that's what's happeneing
Sent from my PC36100 using XDA Premium App
Reverepats...I downloaded two different MikG Roms and neither worked, I also tried Kings Alliance it had the same error. When I ran the Rom I was running before, SalvageRom, it worked. I see you are running MikG, where did u download from?
I'm assuming that you've tried reflashing recovery? Or possibly switching recoveries?
(from... Evo/MIUI/Tapatalk)
The file corrupted, and you just need to download it again.
No Plainjane, I didn't try flashing recoveries. I am currently using Amon RA's recovery v 2.3 I believe. Is there a newer version? If so, where do I find it to flash?
corey140 said:
No Plainjane, I didn't try flashing recoveries. I am currently using Amon RA's recovery v 2.3 I believe. Is there a newer version? If so, where do I find it to flash?
Click to expand...
Click to collapse
2.3 is the latest version. If you choose to reflash just do it via PC36IMG; though I'm positive its just a bad download.
teh roxxorz, I tried the download from HTCEVOHacks.com and MikMik Website and they both failed. I think both were 250MB, which was bigger than usual so it is possible, but I also tried flashing the Alliance Kingdom Rom from this site and got the same error. That's why I figured it was something with my phone. I got an (Oops Error, something went wrong, when I tried to do a Nandroid Restore also. I was able to reflash Salvage Rom and it worked perfect. SO CONFUSED...LOL!
corey140 said:
teh roxxorz, I tried the download from HTCEVOHacks.com and MikMik Website and they both failed. I think both were 250MB, which was bigger than usual so it is possible, but I also tried flashing the Alliance Kingdom Rom from this site and got the same error. That's why I figured it was something with my phone. I got an (Oops Error, something went wrong, when I tried to do a Nandroid Restore also. I was able to reflash Salvage Rom and it worked perfect. SO CONFUSED...LOL!
Click to expand...
Click to collapse
Well the bad zip [can't flash] means something is wrong with the zip file, the 'oops something went wrong,' means that the backup became corrupted.
http://dl.dropbox.com/u/19699565/PC36IMG.zip
Download that [ra recovery] place on the root of your sd card, boot into the bootloader, then apply update, reboot; and amon_ra 2.3 will be reflashed.
teh roxxorz said:
Well the bad zip [can't flash] means something is wrong with the zip file, the 'oops something went wrong,' means that the backup became corrupted.
http://dl.dropbox.com/u/19699565/PC36IMG.zip
Download that [ra recovery] place on the root of your sd card, boot into the bootloader, then apply update, reboot; and amon_ra 2.3 will be reflashed.
Click to expand...
Click to collapse
I really appreciate your help!!! So this flash will enable me to perform my Back-up right. I apologize for all the questions, I just started flashing and I am learning the basics.
corey140 said:
I really appreciate your help!!! So this flash will enable me to perform my Back-up right. I apologize for all the questions, I just started flashing and I am learning the basics.
Click to expand...
Click to collapse
You're straight, and well, potentially. IF the recovery backup itself is corrupted, you'll get the 'oops, something went wrong' error; if it was the recovery. Though you will be able to create and restore backups.
teh roxxorz said:
You're straight, and well, potentially. IF the recovery backup itself is corrupted, you'll get the 'oops, something went wrong' error; if it was the recovery. Though you will be able to create and restore backups.
Click to expand...
Click to collapse
Cool, downloaded the Amon RA Recovery you posted in the link. Flashed it and it went through. Will try to perform my Nandroid backup and post results.
corey140 said:
Cool, downloaded the Amon RA Recovery you posted in the link. Flashed it and it went through. Will try to perform my Nandroid backup and post results.
Click to expand...
Click to collapse
OK, it went more than the first time, but then got the same error:
Oops... something went wrong!
Please check the recovery log!
corey140 said:
OK, it went more than the first time, but then got the same error:
Oops... something went wrong!
Please check the recovery log!
Click to expand...
Click to collapse
Yea, unfortunately, that backup is corrupted, and you'll have to scrap it. Hopefully you have another one, or in a position to create a newer one.
Can I just Reboot and go back to what I was using?
corey140 said:
Can I just Reboot and go back to what I was using?
Click to expand...
Click to collapse
If you reboot, you'll be on whatever you were running before; as long as the backup didn't restore.
teh roxxorz said:
If you reboot, you'll be on whatever you were running before; as long as the backup didn't restore.
Click to expand...
Click to collapse
Cool that's what I will do. Hopefully I can get one of the new Gingerbread Roms here(MikG Preferably) with a .zip that is not corrupted. Since you and Plainjane are pretty sure it is the file that is corrupted. THANKS for all the help.
corey140 said:
Cool that's what I will do. Hopefully I can get one of the new Gingerbread Roms here(MikG Preferably) with a .zip that is not corrupted. Since you and Plainjane are pretty sure it is the file that is corrupted. THANKS for all the help.
Click to expand...
Click to collapse
Well I'm certain it is.
IF all else fails, go to the link on your evo, then download the zip from your phone, make your backup, do a full wipe, then locate it in the folder when you flash.
I'm almost certain it's an issue with your SD card. I've seen it before, but just recently remembered what the problem was. Sorry for the late reply, I was at work.
Backup everything on your card to your computer, this will erase all of your files. Also try to have a full battery, this could take some time depending on the size of your SD card, the class, and the number of files. Then, boot into recovery and select partition SD card (I can't remember where it is, sorry). If you move apps to your SD card - which I think is kind of necessary with the ginormous Sense 3.0 roms - use a larger size for the Ext partition. I never move apps to my SD card, so I set mine to the smallest option other than zero. For the swap size you can use the default 32mb - you may want to look into this more to see if there's a more recommended size.
When it finishes partitioning, go back to the main screen in recovery, plug your phone into your computer and select USB-MS toggle. This will mount your SD card so you can move files back to the SD card. If you're using Windows, it may want to scan and fix the card... just skip it. If you want to save time and/or battery, you can power down the phone and use a card reader instead. Then you can try to restore/make a nandroid backup or flash a rom - it should work.
Good luck, hope you get it fixed!
(from... Evo/MIUI/Tapatalk)
Download MikG 1.04 from http://dev-host.org/lv6fjpxaq9x4/MikG-Sense2.1-v1.04-signed.zip
After downloading the file, get an MD5 checker application such as this one: http://getmd5checker.com/download
The MD5 sum for the zip of MikG 1.04 is: fb81c61a19b5db6d4fa67acbfb17907f
When you run the MD5 check on the downloaded zip, it should match.
If it doesn't then the download is corrupted.
If it does match but you're still having issues flashing it, then there's a pretty good chance that it's the SD card. MicroSD cards are a dime a dozen nowadays so it should be pretty trivial to get some other card that you can pop in and try to flash with.

Can't restore backup img from one Gnex to another

So I borrowed my friend's Gnex so I could send mine in for warranty. His phone is rooted, unlocked bootloader, and running 4.1.1 stock ROM. I backed up his file, and transferred my own backup img to his phone. When I tried to restore my img onto his phone, CWM tells me I have an MD5 mismatch.
I've never tried this before since I've only owned one Gnex, so I'm not even sure if this is possible (which I obviously thought it was). I've tried renaming the folder that the img is located in (as opposed to keeping it in the "backup date" format), and I'm not sure if this is what's causing an MD5 mismatch.
Any insight?
More info... what did you back up? What firmware was yours running etc? What is the .img of?
Sent from my Transformer Prime TF201 using xda premium
rice923 said:
and I'm not sure if this is what's causing an MD5 mismatch.
Any insight?
Click to expand...
Click to collapse
The file hash isn't matching, which means bits have changed since the MD5 was written into the image. That usually means that it transferred improperly, whether it was just generally corrupted during transfer or transferred improperly (say, ascii transfer mode in FTP). I'd try copying it from the original source again.
You can fix the md5 mismatch quite easily http://forum.xda-developers.com/showthread.php?t=714114
Cilraaz said:
The file hash isn't matching, which means bits have changed since the MD5 was written into the image. That usually means that it transferred improperly, whether it was just generally corrupted during transfer or transferred improperly (say, ascii transfer mode in FTP). I'd try copying it from the original source again.
Click to expand...
Click to collapse
Would me changing the folder name that the backup is located in cause the mismatch?
stinky73: I backed up my entire phone in cwm. My original phone was running 4.1.2, but the phone I'm trying to go to is 4.1.1. I don't believe that would make a difference since I'm flashing over the original anyways, or am I mistaken?
peachpuff: I will be reading that link for some brain food. Thanks for pulling it up!
In any case, I may just try to transfer the files again and give it another go.
rice923 said:
Would me changing the folder name that the backup is located in cause the mismatch?
Click to expand...
Click to collapse
Yes it very well may have caused your problem
3rdstring said:
Yes it very well may have caused your problem
Click to expand...
Click to collapse
I just used the original name for all the folders and files of my backup img, and it no longer states a mismatch MD5. However, it now says "Error while restoring /system!"
Starting to think I really gotta be on 4.1.2 in order for it to restore correctly. Any other thoughts?
Hey if you ever figure this out, let us know. I have tried to restore backups from one gnex to another with no luck. I have used CWM and TWRP. Tried leaving the files as is and also renaming them. I tried transferring them via computer as well as uploading them to dropbox and downloading from there. Someone told me a while ago it could be done but I sure couldn't get it to work when I went through several replacement phones. :/
RoyJ said:
Hey if you ever figure this out, let us know. I have tried to restore backups from one gnex to another with no luck. I have used CWM and TWRP. Tried leaving the files as is and also renaming them. I tried transferring them via computer as well as uploading them to dropbox and downloading from there. Someone told me a while ago it could be done but I sure couldn't get it to work when I went through several replacement phones. :/
Click to expand...
Click to collapse
My plan for tomorrow is to flash a current PA 2.53 ROM onto the said device, and then restore the backup from there. My theory is that the phone won't take the backup img properly because of a mismatched OS version (4.1.1 going to 4.1.2). By flashing the PA 2.53 ROM, I will then be on 4.1.2, and I can flash the backup from there (so that I don't have to reload all my apps and data manually).
That's just speculation tho, so I could very well be wrong. Will report back when I try it!
peachpuff said:
You can fix the md5 mismatch quite easily http://forum.xda-developers.com/showthread.php?t=714114
Click to expand...
Click to collapse
Nice thread, hadn't come across it, it's indeed a easy fix. Use the command all the time, well actually
sha256. 8 thanks limit per day reached.
3rdstring said:
Yes it very well may have caused your problem
Click to expand...
Click to collapse
2nd or 3rd post of the thread linked by peachpuff also said that. they dont like to read. 8 thanks limit per day reached.
rice923 said:
My plan for tomorrow is to flash a current PA 2.53 ROM onto the said device, and then restore the backup from there. My theory is that the phone won't take the backup img properly because of a mismatched OS version (4.1.1 going to 4.1.2). By flashing the PA 2.53 ROM, I will then be on 4.1.2, and I can flash the backup from there (so that I don't have to reload all my apps and data manually).
That's just speculation tho, so I could very well be wrong. Will report back when I try it!
Click to expand...
Click to collapse
Try this: format /system before restoring the backup, if /system was also backed up.
Sent from my i9250
bk201doesntexist said:
Nice thread, hadn't come across it, it's indeed a easy fix. Use the command all the time, well actually
sha256. 8 thanks limit per day reached.
2nd or 3rd post of the thread linked by peachpuff also said that. they dont like to read. 8 thanks limit per day reached.
Try this: format /system before restoring the backup, if /system was also backed up.
Sent from my i9250
Click to expand...
Click to collapse
Yes, I actually read the thread and found that response. I just happened to post my question before reading the thread.
Anywhoo, nothing has actually worked so far. I'm actually ready to cave in and just do a fresh start. Sorry to let ya down RoyJ
6.x CWM issue?
what version of CWM are you using? if you are using version 6.x did you also transfer the "/sdcard/clockworkmod/blobs" folder to the new phone?

[Q] recovery problem

I want to return to stock m8. I have the twrp back up and followed instructions putting it in to folder twrp-backup but when i boot into recovery the file folder isnt visable in the restore section. I can find the folder in the install section but without any executable files in. Im really stuck bin at this for hours. I followed the youtube video to the letter combining with the written instruction and cant understand where im going wrong. If it helps im on three uk. Any help would really be appriciated
Make sure the extracted backup folder is placed at TWRP/BACKUPS/YourDeviceSerialNo/FOLDER here
thanks for the quick reply, however the problem persists.
nothing is showing up in restore. when i rooted the handset i didnt install a custom rom just the custom recovery. now following the instructions for unroot i have to install a stock rom?? the version main on my m8 is 1.54.771.9 but the version of the stock im trying to install is 1.54.771.5 for three uk. i dont know if its because i have a stock rom onboard and the new one is an earlier version. if i dindnt install a custom rom why do i need to install a stock for unroot? cant i unroot using superuser then flash stock recovery then relock bootloader?
sorry its turned into a Q and A but i really dont understand
Can you make a backup with the TWRP recovery that you have now, only backup the boot.img. Then check in restore whether you can see it, if yes that's the place to put your full backup
From where that you got the 1.54.771.5 backup ? If it is from http://forum.xda-developers.com/showthread.php?t=2701376
this backup is for Philz recovery.
Oh yes your right but i was mistaken iv actually downloaded the twrp above it as its the only twrp avail for my cid this is the recovery iv tried but no luck. I will google how to make a back up of the twrp im running and give it a try. Is there no set default location the restore option would be looking for the recovery? Also in the stock rom i downloaded there are 9 entries inside but on the video tutorial his has more. xda is the only repo for these stock roms i can find so if its not a complete img then what do i do?
The location is as I mentioned above for TWRP.
I have no idea what video you're talking about.
I've seen many follow links outside of XDA but when they have problem, they come here .. I don't know why they can't get help from those outside links.
About the content of a TWRP backup, usually is 9 when there is no md5 created. In my nandroid backups that uploaded, there are only 8 files because I remove the recovery.log too.
And CWM or Philz recovery have about 14 or more
1anmu77ay said:
xda is the only repo for these stock roms i can find so if its not a complete img then what do i do?
Click to expand...
Click to collapse
Just google for outside links if you can find one that are not linked back to XDA.
For me, what we have on XDA is good enough.

Easy-to-flash backup of VUPMP.GPRO.sG3.Stable

UPDATE:
Flash using **CWM from Freegee**( I previously recommended Philz for the updated look and features but it is SUPER inconsistent and unfortunately unreliable, I do not mean any offense to its creator/developer, it is just too much hassle and this thread is meant for easy flashing and I was already posting the work around for the Philz bootloop issue which killed the purpose of easy flashing...)
Remember to make a nandroid/backup using CWM, if you forgot to make one, PM me to help you sideload a Rom using ADB. (will save you the hassle of going through stock and go directly to any custom rom of your preference)
Hello dear people with an E980:
I'm here to share a backup I made for my personal use to avoid the hassle of having to return to stock to flash the VUPMP stable rom and deleting the recovery folder inside the Rom, pretty much in other words it's just an "easy-to-flash" backup.
Rom comes from:
http://forum.xda-developers.com/opt...om-20140920-vupmp-gpro-sg3-stable-lg-t2902595
Here is the backup!, it is flashable so don't extract it, it includes a boot.img (kernel) so you can restore from any rom, no need to come from stock:
https://www.androidfilehost.com/?fid=95747613655048316
MD5: f50a74eb5ceb7600d0ea609192d5c258
On this particular backup, I applied the following fixes for E980:
-Volume restore fix
-Video recording fix
-Removed a system apk which seemed to be a calendar in viet (for the sake of clean and stock look).
It is highly recommended to wipe before flashing:
-Data (without wiping data/media, if you don’t know how to do this just ask in the Q&A section or PM me!!)
-Cache & Dalvik cache
-System
-Please, don't report bugs if doing a "dirty" flash.
Special thanks to:
@datphu2811 for developing such a cool ROM
@Chairizkuro for the video recording fix
anyone who contributed with this files linked above!
Remember:
Flash at your own risk!
Anyone try yet?
Anybody try this yet? Looks cool! Sounds easy.
DollarStrawz said:
Anybody try this yet? Looks cool! Sounds easy.
Click to expand...
Click to collapse
I did, I followed the instructions but got stuck in a boot loop and it didn't fix when I applied the aforementioned zip. I just went back to stock the normal way and everything worked out. That's just my experience though, you could have completely different results.
GreatCaesar said:
I did, I followed the instructions but got stuck in a boot loop and it didn't fix when I applied the aforementioned zip. I just went back to stock the normal way and everything worked out. That's just my experience though, you could have completely different results.
Click to expand...
Click to collapse
Man thanks!! I was just about to do it.
GreatCaesar said:
I did, I followed the instructions but got stuck in a boot loop and it didn't fix when I applied the aforementioned zip. I just went back to stock the normal way and everything worked out. That's just my experience though, you could have completely different results.
Click to expand...
Click to collapse
Can you describe your problem? What kind of bootloop did you get?
A) it kept booting to recovery (that's what the zero zip is for)
B) it kept stuck in the lg logo
If B)
Did you performed a full wipe of data (without data media), system and cache? Did the flash took an unexpected amount of time (2 seconds instead of 2 minutes)?
Additionally, why did you totted back? Didn't you made a backup first?, in case you made a backup, did the recovery rendered useless after flashing my backup?
Did you get any lokifying errors?
DollarStrawz said:
Man thanks!! I was just about to do it.
Click to expand...
Click to collapse
Please let the person answer those questions before walking away scares, I've tried my own backup several times and I assure you it works properly if following the instructions. Even further, it's common sense to do a backup even without being warned about it.
OK yeah thanks I will still try it. Thanks for making this. It looks super cool and easy.
DollarStrawz said:
OK yeah thanks I will still try it. Thanks for making this. It looks super cool and easy.
Click to expand...
Click to collapse
Please use CWM from Freegee, I have been getting reports from a few friends testing on how Philz touch is being inconsistent, I'm about to update main post.
Md5 Mismatch
I followed ever4ything I think. I extracted it on my desktop then copied that folder over to Clockworkmod/backup folder. After wipingt everything I went to restore and got Md5 Mismatch. What did I do wrong?
DollarStrawz said:
I followed ever4ything I think. I extracted it on my desktop then copied that folder over to Clockworkmod/backup folder. After wipingt everything I went to restore and got Md5 Mismatch. What did I do wrong?
Click to expand...
Click to collapse
Can you please manually check the MD5 sum of your downloaded file? Let me know if you don't know how to do it I can show an easy method.
Jose-MXL said:
Can you please manually check the MD5 sum of your downloaded file? Let me know if you don't know how to do it I can show an easy method.
Click to expand...
Click to collapse
I checked the re-downloaded one and they match. I used an Md5 checker?? So am I on the right track by extracting and copying that folder to clockwork backup? Then in CWM go to Mounts and Storage and format /data, format /system, format /cache and wipe dalvik. THEN restore the folder copied earlier. Just want to make sure I'm not missing anything. Thanks!!
DollarStrawz said:
I checked the re-downloaded one and they match. I used an Md5 checker?? So am I on the right track by extracting and copying that folder to clockwork backup? Then in CWM go to Mounts and Storage and format /data, format /system, format /cache and wipe dalvik. THEN restore the folder copied earlier. Just want to make sure I'm not missing anything. Thanks!!
Click to expand...
Click to collapse
Oh! OH! OH!!, I know what's going on, this is a flashable zip lol, you are not supposed to extract it, sorry if I provided misleading instructions so I can change them
AWESOME
Loving this ROM everything works great!!
Can't get LTE To Stick
Everything works great but the one thing bothering me is I can't seem to get Global + LTE to stick after following the steps:
- Input 5457#*988# from dial pad
- Find "Network Mode" set value "Global + LTE"
- Find "CDMA Subsciption" set value "USIM"
When I try to switch from NIV to USIM the phone instantly reboots and reverts the network back to WCDMA. Does anyone know how to fix this?
Jose-MXL said:
Oh! OH! OH!!, I know what's going on, this is a flashable zip lol, you are not supposed to extract it, sorry if I provided misleading instructions so I can change them
Click to expand...
Click to collapse
How is the flushable ROM running. Thinking about flashing. Any differences from other VROM

Categories

Resources