[Q] MD5 mismatch on fresh cyanogenmod9 - General Questions and Answers

Hello, i'm new to flashing roms. I have downloaded cyanogen 9 for sgs2. I had alot of trouble flashing my device as I kept getting md5 mismatch. Eventually I got it to work by using clockworkmod and flashing from the device (not in recovery mode). However I reverted back to my original rom which came with my sgs2. I attempted once again to flash cyanogenmod 9 and still get the md5 mismatch. I cannot flash it from the clockworkmod application either, when my phone boots up I get an error:
E: cant open /sdcard/external_sd/cm-9.1.0-galaxys2.zip
(no such file or directory)
Installation aborted
I really like the look of this mod, but i'm not sure what I am doing wrong. Elsewhere on the internet it seems people who have problems with the md5 mismatch have made a mistake backing up a previous flash. But I'm using a fresh untouched cyanogenmod 9.
Hope i've been clear enough.
[sgs2 i9100]
[ics]

Well, its all sorted now. It seems I was going about the flash all WRONG! I was initially using the 'restore' function to flash a clean new rom (so ovcourse the restore process would not find an md5 because one had not been generated!)
If anybody has difficulty and is noobish like me you need to boot into CWM and then browse to 'install zip from sd' or wherever your rom is, and just install it. Kinda obvious now

Related

CyanogenMod Magic 32b

I'm a noob and I know this, but still need some help...
I have a MyTouch 3G and have followed just about every step shown here:
wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_MT3G/Magic_Firmware_to_CyanogenMod
I used the Latest FlashRec:
zenthought.org/system/files/asset/2/flashrec-1.1.3-20091107-2.apk
And used AppInstaller to load it. I've done the Recovery and used:
recovery-RA-sapphire-v1.5.2G.img from
forum.xda-developers.com/showthread.php?t=530492
as the recovery image.
Everything went smooth and well until I got to the 'Flash zip from SDCard' section.
Obtained and flashed the DRC83_base_defanged as follow
mediafire.com/file/nymkxjmndzd/DRC83_base_defanged.zip
And then tried to load the latest CyanogenMod: update-cm-4.2.14.1-signed.zip
Which ended up with the following error:
E: Failure at line 79
copy_data.
Anyone faced this? I saw a couple of thread with this error but no true solution. Should I try another ROM?
I'm new to the MyTouch 3G ROM world and thus could've picked the wrong rom.
Any help would be appreciated!
it's not uncommon. you either did not Wipe. or got a bad downloaded image. restart into recovery wipe the restart into recovery flash base restart into recovery and flash cyanogen. just download another image bc it sounds like you have a bad one.
cool thanks for the tip - As a side question, what does the wipe really do, just remove personal data?
How is it different from the oem wipe data?

ROM Manager error I NEED Help Plz

hey guys i had andromeda installed but messed the flash up by disabling lots of system stuff so i one clicked back to stock, rooted, installed rom manager like normal but every time i try to flash clockwork recovery mod it keeps telling me "An error occurred while downloading your recovery." and i cant install it so i can re-flash the rom plz help me i dont know what to do thx ahead of time
praramis said:
hey guys i had andromeda installed but messed the flash up by disabling lots of system stuff so i one clicked back to stock, rooted, installed rom manager like normal but every time i try to flash clockwork recovery mod it keeps telling me "An error occurred while downloading your recovery." and i cant install it so i can re-flash the rom plz help me i dont know what to do thx ahead of time
Click to expand...
Click to collapse
Put this on your internal SD card along with your ROM of choice. Reboot in to recovery and install packages 2 times. The second time it will be in clockwork recovery and you can flash your ROM.
I just had the same problem after doing countless ROM flashes in the past. Perhaps its something in their server preventing the download of CWM? Anyways, thanks for the .zip. Worked like a charm!
yes thank you very much for that zip u saved my life well appreciated
Keep that .zip on your HDD and you can bypass Rom Manager (and all the associated problems) altogether.
I have my phone rooted and unlocked. It's the AT&T Captivate but I'm using it on T-Mobile. I've had no problems so far with it.
I downloaded Clockwork's Rom Manager (v3.0.0.7) and tried to Flash ClockworkMod Recovery to begin experimenting with ROMs.
When I click on that it tells me "An error occurred while downloading your recovery."
I have over 4 gigs of memory left and I have 3 bars on 3g and WiFi going. No internet connection problems (i checked the net using market and using the browser, it works fine.)
What else could be causing the problems.
I'm just wanting to get a good stable rom going which ditches all the junk AT&T put on the phone.
Jonathan
lanternslight456 said:
I have my phone rooted and unlocked. It's the AT&T Captivate but I'm using it on T-Mobile. I've had no problems so far with it.
I downloaded Clockwork's Rom Manager (v3.0.0.7) and tried to Flash ClockworkMod Recovery to begin experimenting with ROMs.
When I click on that it tells me "An error occurred while downloading your recovery."
I have over 4 gigs of memory left and I have 3 bars on 3g and WiFi going. No internet connection problems (i checked the net using market and using the browser, it works fine.)
What else could be causing the problems.
I'm just wanting to get a good stable rom going which ditches all the junk AT&T put on the phone.
Jonathan
Click to expand...
Click to collapse
Read the above solution...
I Can't get the update.zip file to work. After I reinstall packages is says E:Can't open /sdcard/update.zip (No such file or derectory) Installation aborted. I've tried it probably 20 times today with no luck.
Thank You
Nothing like flashing to find out it wasn't working. Thanks for making my day go better.
Noobie Mistakes
Just like everyone in this forum I'm having the same problem, I followed your instructions posted, but every time I reinstall packages in recovery mode a whole list of new problems comes up..... see below.
---Install from sdcard---
Finding update package...
Opening update package....
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
PLZ Help.......
Thanks
i have been fight this same thing for 2 days. im going to try the update.zip he posted i hope it works
npe didnt work. still says error downloading
tat2messiah said:
npe didnt work. still says error downloading
Click to expand...
Click to collapse
if the update.zip is already on your /sdcard/ then there is no reason to try and download/flash clockwork recovery.....thats what the update.zip IS
thats what i thuoght but not true. even goin in normal recovery and selecting to install packages gets a error some about no such directory or something even though updat.zip is there even fix permissions gives a error
I'm having the exact same problem. After reading the development section I have decided to flash a custom rom from my stock rom. Installed "Rom manger" from market, then tried to run the "recovery" got the same error msg. Also uploaded the update.zip to my /sdcard the I got the below errors:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
tat2messiah said:
thats what i thuoght but not true. even goin in normal recovery and selecting to install packages gets a error some about no such directory or something even though updat.zip is there even fix permissions gives a error
Click to expand...
Click to collapse
Did you flash back to stock JF6 first not JI6?
try this cuz this is what i did and the update.zip worked just fine for me
1. one click back to stock jf6
2. master clear
3. root with galaxy s one click root
(after the root there should be an update.zip in your sdcard)
4. replace the update.zip in the root of your sd card with the one here posted which is the clockwork recovery one and if you want while u do that you can throw in the rom that you want to flash in there as well to kill 2 birds with one stone
(i will re post the update.zip for cwm just in case)
5. power off the phone and boot into stock recovery and hit reinstall packages two times
6. you should now be in clockwork mod recovery and can now flash the rom of your choice
this is what i did and everything went smoothly but this is just me if this helps someone else plz let me know if this works for you
p.s. i will make a video if needed just ask
Try This
After flashing back to stock do a master clear from Odin3
Put update.zip onto internal sd
Boot into recovery
Reinstall packages
After boot enable USB debugging and mock locations
Get Rom Manager from market
Start Rom Manager
Flash ClockworkMod Recovery
Flash away
jhernand1102 said:
Put this on your internal SD card along with your ROM of choice. Reboot in to recovery and install packages 2 times. The second time it will be in clockwork recovery and you can flash your ROM.
Click to expand...
Click to collapse
You guys are making it harder then necessary, the update zip I posted is the clockwork recovery MOD, just flash stock, reboot into recovery and reinstall packages 2 times and you will be in the green clockwork recovery then you can install zip from sd and choose your ROM you placed on your internal sd card. No need to root every again as long as you keep this update zip handy.
I too am having problems with Rom Manager. I just wanted to change modems. No go. So I used the power button to go into Recovery mode, picked the modem file, flashed it then told the menu to reboot system.
Sent from my Samsung Captivate with Perception 10.3, Firebird2 v0.8 #77 Kernel, Firmware 2.2.1, Modem T9000UGJL2 using XDA App

[Q] Update Binary Script

Hey,
having a problem with installing zips
phone doesn't seem to be able to install any ROM or superuser but can install gapps, google now, recoveries, etc.
the error looks like this
E: error in sdcard/roms/path
(Status 0)
Aborted
Been looking around and people with status 0 problems normally get them by doing something wrong with the update binary when developing their own roms. I recently messed up my phone a little and although I got it working again I think the update binary might still be changed.
Since I know nothing about any of this kind of thing,
Does anyone have access to a stock or tested and working update-binary file that I can replace mine with,
or at least check to see if there's any differences, to see if that's the problem?
If anyone has any ideas about what might be causing the problem i'd appreciate help
Thanks
i would start be reflashing the recovery becasue i highly doubt that the roms that all these DEV have built is the issue with binary script if you want to pull one from a stock rom. you can grab one from Vincoms thread. and not to mention make sure you have atleast attempted to download the rom twice incase you have a bad zip folder. another thing you cant would be to flash from the internal
crashpsycho said:
i would start be reflashing the recovery becasue i highly doubt that the roms that all these DEV have built is the issue with binary script if you want to pull one from a stock rom. you can grab one from Vincoms thread. and not to mention make sure you have atleast attempted to download the rom twice incase you have a bad zip folder. another thing you cant would be to flash from the internal
Click to expand...
Click to collapse
No it's 100% a problem with the phone,
I've tried multiple recoveries, multiple roms, that were downloaded multiple times from multiple sources, and while running multiple roms (from recoveries) and all give the exact same error. TWRP's error looks a little different but I'm pretty sure its the same thing.
I thought there was just a .tar file on vincom's thread for the stock firmware
i'll check again to see if I can find what I need from there though,
thanks.
there is a zip stock recovery fashable file, but not a tar one, either revert to full stock via odin then reinstall a custom recovery, or backup your sdcards and reformat them to see if that corrrects your problem

CWM restore - MD5 mismatch (XBSA ICS 5.2)

Hi everybody!
I'm on my learning curve with "brand new" o3D - xbsa ics
I love it.
Yesterday I installed CWM 6.0.1.5 using dexter's guide (fastboot etc). Now I have nice touch recovery.
Just to check I did system backup. Then I tried to restore it. And got message:
E: Invalid command argument
and then
MD5 checksum mismatch
Any ideas why? And more important - how to get it work? CWM without restore is pretty useless...
I tried renaming backup to one word without spaces etc - didn't help... And I don't see md5 file in backup folder...
Thanks in advance!
With ICS i never used CWM, so far with TWRP Recovery never had that issue.
Same problem here, I have a cwm backup I want to restore, but always get a md5 mismatch error, anyone got this one solved?
daniel.mota said:
Same problem here, I have a cwm backup I want to restore, but always get a md5 mismatch error, anyone got this one solved?
Click to expand...
Click to collapse
latest version of cmw 6.x has a lot of bugs... try restoring with cwm 5.x and you should be allright.
ptmaniac said:
latest version of cmw 6.x has a lot of bugs... try restoring with cwm 5.x and you should be allright.
Click to expand...
Click to collapse
I don't think I can use CMW 5.x with ported ICS... I've tried...

[HELP THREAD] cm-13 on gt-p5100

Hello guys,
I installed cm-13 successfully and it was operating fine until yesterday. Today I tried to install a theme or something and it hung. So i just felt like doing a factory reset and I did it through my cwm recovery. But before that i made a backup, then i did the reset, then i did the restore...ever since then i havent been able to open the OS...it gets stuck on the samsung GALAXY Tab2 10.1 screen. I can however access the cwm recovery. I did infact try to unzip the cm-13 that i had previously used, and it doesnt work...
Please help guys!
I am pretty new to this and i feel like i cant figure out what to do next.
Is there a way to maybe restart the whole process, like get rid of the cm-13 that is already installed and redo the whole thing again?
Kindly help guys, i was really enjoying the cm experience and i messed it up :/
killermara said:
Is there a way to maybe restart the whole process, like get rid of the cm-13 that is already installed and redo the whole thing again?
Kindly help guys, i was really enjoying the cm experience and i messed it up :/
Click to expand...
Click to collapse
you did a backup before factory reset, then you restored the same data after reset. this hardly changed anything. the reason it didn't boot, is that The problem lies at the system partition, you should wipe system partition, data partition as well and flash the same cm-13 zip again along with gapps, if you had.
now let the system start. it should boot up with a clean installation. you can then try to advance restore and chose only data partition.
later just switch to twrp recovery by Android-Andi
HELP!
billysam said:
you did a backup before factory reset, then you restored the same data after reset. this hardly changed anything. the reason it didn't boot, is that The problem lies at the system partition, you should wipe system partition, data partition as well and flash the same cm-13 zip again along with gapps, if you had.
now let the system start. it should boot up with a clean installation. you can then try to advance restore and chose only data partition.
later just switch to twrp recovery by Android-Andi
Click to expand...
Click to collapse
Hello, actually I did exactly that, i wiped system partition and all of that...then i did try with cwm, and it didnt work, what is happening is that i select the option to flash the ROM, then the screen goes blank for a second and comes back to the home screen of the cwm recovery. So basically i selected the zip and nothing happened! I then tried flashing using twrp and the problem now was that there was the "no md5 file found" message and the installation would not stop, it would go on for too long, like some sort of loop. I then switched back to cwm and tried again and it still doesnt seem to work...kindly advice on what to do next
killermara said:
Hello, actually I did exactly that, i wiped system partition and all of that...then i did try with cwm, and it didnt work, what is happening is that i select the option to flash the ROM, then the screen goes blank for a second and comes back to the home screen of the cwm recovery. So basically i selected the zip and nothing happened! I then tried flashing using twrp and the problem now was that there was the "no md5 file found" message and the installation would not stop, it would go on for too long, like some sort of loop. I then switched back to cwm and tried again and it still doesnt seem to work...kindly advice on what to do next
Click to expand...
Click to collapse
first thing check if you have updated to last official stock jellybean rom prior to cm13 upgrade.
this thread will help you to update your bootloader to jb from ics. if you have a jb bootloader already. you can skip this.
forum.xda-developers.com/showthread.php?t=2642005
next thing you should get twrp 3.0.2.8
https://www.androidfilehost.com/?w=files&flid=48848&sort_by=date&sort_dir=DESC
after wiping, restart recovery, then flash the Rom zip
it takes time with the new CM13 builds to complete installation. some earlier twrp recoveries had issues(3.0.0.1 and 0.2, not sure right now, try latest only). cwm is not supported and twrp is the only preferred recovery by the Rom developers to flash the newer roms.
remember p5100 tab is called espresso3g now, since development has been unified. you need files marked as espresso3g for your p5100.
I don't which files are you using, development has changed so confirm the files that you're using are for unified builds and not device specific.
billysam said:
first thing check if you have updated to last official stock jellybean rom prior to cm13 upgrade.
this thread will help you to update your bootloader to jb from ics. if you have a jb bootloader already. you can skip this.
forum.xda-developers.com/showthread.php?t=2642005
next thing you should get twrp 3.0.2.8
https://www.androidfilehost.com/?w=files&flid=48848&sort_by=date&sort_dir=DESC
after wiping, restart recovery, then flash the Rom zip
it takes time with the new CM13 builds to complete installation. some earlier twrp recoveries had issues(3.0.0.1 and 0.2, not sure right now, try latest only). cwm is not supported and twrp is the only preferred recovery by the Rom developers to flash the newer roms.
remember p5100 tab is called espresso3g now, since development has been unified. you need files marked as espresso3g for your p5100.
I don't which files are you using, development has changed so confirm the files that you're using are for unified builds and not device specific.
Click to expand...
Click to collapse
I followed all the steps that you suggested, and the thread suggested.
I installed custom recovery, then I updated the bootloader.
Then i flashed the new twrp, which is alot more easier to operated compared to the cwm .
then i wiped , restarted recovery, then flashed the rom,
the exact same thing that was previously happening with the cwm happened : I tapped on the rom, then a blank screen appeared and it went back to the main menu of the twrp...
The ROM i am using is: cm-13.0-20160220-1347-UNOFFICIAL-p5100.zip
i also tried using the ROM i got from get.cm : cm-11-20160822-NIGHTLY-p5100.zip
Okay so i played a slow mo video to see what the screen says before it goes back to the welcome screen:
Updating partition details. . .
. . . done
Full SElinux support is present.
MTP Enabled
Then after this pops up, it goes back to the main menu of the twrp.
What if i just reinstall the stock OS then do the whole process of getting cyanogenmod again from rooting onwards?
Kindly assist!!
killermara said:
I followed all the steps that you suggested, and the thread suggested.
I installed custom recovery, then I updated the bootloader.
Then i flashed the new twrp, which is alot more easier to operated compared to the cwm .
then i wiped , restarted recovery, then flashed the rom,
the exact same thing that was previously happening with the cwm happened : I tapped on the rom, then a blank screen appeared and it went back to the main menu of the twrp...
The ROM i am using is: cm-13.0-20160220-1347-UNOFFICIAL-p5100.zip
i also tried using the ROM i got from get.cm : cm-11-20160822-NIGHTLY-p5100.zip
Okay so i played a slow mo video to see what the screen says before it goes back to the welcome screen:
Updating partition details. . .
. . . done
Full SElinux support is present.
MTP Enabled
Then after this pops up, it goes back to the main menu of the twrp.
What if i just reinstall the stock OS then do the whole process of getting cyanogenmod again from rooting onwards?
Kindly assist!!
Click to expand...
Click to collapse
OKAY! So i have had some progress in the situation i got myself into! Now i just changed the sd card and tried to flash the ROM, so it didnt successfully flash, it says:
Zip file is corrupt!
Error installing zip file ..*the directory of the ROM*
This doesnt make sense though because i used the exact same ROM earlier and it worked, i used it for a whole day and it was fine...
killermara said:
OKAY! So i have had some progress in the situation i got myself into! Now i just changed the sd card and tried to flash the ROM, so it didnt successfully flash, it says:
Zip file is corrupt!
Error installing zip file ..*the directory of the ROM*
This doesnt make sense though because i used the exact same ROM earlier and it worked, i used it for a whole day and it was fine...
Click to expand...
Click to collapse
do what @billysam said.
dont use device specific stuff. the latest twrp will only work with unified builds. for your device you need espresso3g builds.
you will find the latest roms on android-andis github site http://andi34.github.io/index.html
killermara said:
OKAY! So i have had some progress in the situation i got myself into! Now i just changed the sd card and tried to flash the ROM, so it didnt successfully flash, it says:
Zip file is corrupt!
Error installing zip file ..*the directory of the ROM*
This doesnt make sense though because i used the exact same ROM earlier and it worked, i used it for a whole day and it was fine...
Click to expand...
Click to collapse
you're using device specific Rom build, cm13.0 unofficial p5100, the latest twrp recovery you have, is a unfied espresso3g one.
latest roms, are build upon espresso3g for p5100,p3100 and espressowifi for p5110,p5113 p3113.
use latest cm13 rom zip, marked espresso3g.
there are device specific roms and recovery, which developers have stopped working on, your issue is because of this. get unified recovery and rom.
billysam said:
you're using device specific Rom build, cm13.0 unofficial p5100, the latest twrp recovery you have, is a unfied espresso3g one.
latest roms, are build upon espresso3g for p5100,p3100 and espressowifi for p5110,p5113 p3113.
use latest cm13 rom zip, marked espresso3g.
there are device specific roms and recovery, which developers have stopped working on, your issue is because of this. get unified recovery and rom.
Click to expand...
Click to collapse
Yea i thought so too, thats why i downloaded the cm-13.0-20161117-NIGHTLY-espresso3g.zip, then i wiped and tried to flash this rom, this also gave me the same error,
i also noticed that before the lines
Zip file is corrupt
there was:
Checking for MD5 file. . .
Skipping MD5 check: no MD5 file found.
killermara said:
Yea i thought so too, thats why i downloaded the cm-13.0-20161117-NIGHTLY-espresso3g.zip, then i wiped and tried to flash this rom, this also gave me the same error,
i also noticed that before the lines
Zip file is corrupt
there was:
Checking for MD5 file. . .
Skipping MD5 check: no MD5 file found.
Click to expand...
Click to collapse
maybe the zip got corrupted, checked your pc with anti-virus? are you downloading the zip file from androidfilehost of android-andi? or some other source? checked your sd card as well?

Categories

Resources