I'm using CWR v4.0.0.4 for AlphaRevX and I renamed the restore image file names to better track them. Now I get a MD5 mismatch on every one of them. Does the file name have to left unchanged? Is there any way to get back to good now?
t0adman said:
I'm using CWR v4.0.0.4 for AlphaRevX and I renamed the restore image file names to better track them. Now I get a MD5 mismatch on every one of them. Does the file name have to left unchanged? Is there any way to get back to good now?
Click to expand...
Click to collapse
Give this a try. It's happened to me twice and this fixed it both times.
http://forum.xda-developers.com/showthread.php?t=714114
andybones said:
Give this a try. It's happened to me twice and this fixed it both times.
http://forum.xda-developers.com/showthread.php?t=714114
Click to expand...
Click to collapse
I owe you more thanks than I can give to one post. You're the MAN! All I had to do was remove spaces from the directory name and it worked again.
Related
Actually i am new at the android development, but i have seen so many people who complain about getting error during flash a new rom or any other patch from recovery mode.
may be it is funny for you guys the solution that i am going to explain but may be some of you dont know about it. for me also it was happened few times and got an error regarding a missing some thing on the zip file!!
usually these files are zipped, so when we download them, sometimes download manager is not able to do the process successfully specially when so many people are trying to access to the server and download the new roms or kernels.
u guys just try to unzip file 1st in a different folder and see u get an error during unzip or not!! usually if the zip file is corrupted it will show you which file hasnt download successfully for example it mention about peep.apk error. so u dont need to download the zip file again!! just try to remove it first and replace the apk file with the new one!! that's it. for me most of the time it works!! as there are so many .apk files in the rom, so the error is belong to one or few of those apk files!!
sorry for my bad written @ grammar!!
Oh my god, you've opened my eyes! CORRUPTED ZIP FILES CAN'T BE FLASHED! I have never thought about it!
Sent from my HTC Desire using XDA App
K900 said:
Oh my god, you've opened my eyes! CORRUPTED ZIP FILES CAN'T BE FLASHED! I have never thought about it!
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Haha
But it's true: Before you flash a zip file, try to extract it before you try to install it
But even easier: Check the MD5 sum if provided by the developer!
Frozen-GPU said:
Haha
But it's true: Before you flash a zip file, try to extract it before you try to install it
But even easier: Check the MD5 sum if provided by the developer!
Click to expand...
Click to collapse
I think it's easier to test extract it . You know.... i've never used an MD5 in my life.
fllash said:
I think it's easier to test extract it . You know.... i've never used an MD5 in my life.
Click to expand...
Click to collapse
me 2.
i dont know how to use the MD5 also and i didnt find any thread to show where and when we can use those hash files or for which purpose!!
that's why the extracting zip file would be the best way to find out is there any corrupted file in it or not!! and 95% of time one of those apk files has problem and u can just replace it with another one or if u dont want it just remove it!!
OMG... seriously people... MD5 is faster. Just download any MD5 checker, compare the MD5 hash code with the file, and that's it.
Or, use Firefox with DTA, and you'll always get the full file.
This may be a noob question.... So I renamed one of my nand backups and now I get an error when restoring.... "Error : run 'nandroid-mobile.sh restore' via adb!"
Any ideas?
Cleetis said:
This may be a noob question.... So I renamed one of my nand backups and now I get an error when restoring.... "Error : run 'nandroid-mobile.sh restore' via adb!"
Any ideas?
Click to expand...
Click to collapse
how charged on your battery ? i get that when my battery is low
I'd say battery as well. Also remember not to put any funky characters when you rename
~ I'm a fungi
My battery is at 98%. I named the backup "Stock FroYo". Without the quotes. Should I rename it again?
Thanks guys!
If your file was something like BCDS-20110104-1014 then you should rename it BCDS-20110104-1014namehere Important thing to do is to keep the original file name and whatever you add must have no spaces in it.
Or, as others have suggested, it could be low battery. You can move the log to your sdcard in recovery or run it from adb to get more info on the exact error.
Cleetis said:
My battery is at 98%. I named the backup "Stock FroYo". Without the quotes. Should I rename it again?
Thanks guys!
Click to expand...
Click to collapse
I_don't_use_spaces_just_underscores. But I do rename the whole. Typically by rom name,date,version,etc
~ I'm a fungi
Yes I believe its the space. Had the same issue.
Sent from my PC36100 using XDA App
Thanks guys! Sorry for the noob problem as I'm sure it was. I have only had my EVO rooted as of this past weekend. I guess I should have known about not having spaces.... That was it! I renamed it without the spaces and booted right up!
Thanks everyone!
You saved me! lol
Cleetis said:
Thanks guys! Sorry for the noob problem as I'm sure it was. I have only had my EVO rooted as of this past weekend. I guess I should have known about not having spaces.... That was it! I renamed it without the spaces and booted right up!
Thanks everyone!
You saved me! lol
Click to expand...
Click to collapse
Happy it worked.
Don't forget to post your questions in the q&a section for the future
sent from my manila carbon rom
Sorry about that! Will do though. From here on out.
Clint
Hi there.
As per the title says, how do I actually check what md5 sum i am using? I am aware that different ROM requires a different md5 but am not sure what is this actually for.
If i found that my current md5 is not the matching one, I flash it through using CWM right?
Thanks.
md5 sum is a method to check that a file has been downloaded correctly; each file has a calculated md5 value provided by the person supplying the file, you can then calculate the md5 for the file you received, and if they match you know the file is correct. That's a pretty shoddy explanation, but you can get a better one by googling or on Wikipedia.
Long story short, it's not something that you use or flash as part of your ROM.
//sent from my Desire HD using Tapatalk; all errors entirely intentional.
LOL! okok now i got it. sorry that I am not "fluent" in this area. asking such a dumb question. xD
Thanks man!
Click the link in my sig and head to tools. There is an MD5 generator/checker there. Very quick & simple to use.
hey everybody
how do i can check md5 through better terminal in DHD ?
Ive been having problems flashing ARHD succesfully, ive done a superwipe several times and retried and Cant think of anything else I may be doing wrong, so I figure the MD5 Sum is wrong or something? Any help would be greatly appreciated, thanks!
It's also probably easier to know that Most graphical file manager applications such as ES file explorer (free) and root explorer, have an md5 option within file properties
Swyped from my Desire S using XDA Premium
also, if you download directly to your device there is a free app on the market called "MD5CHECKER" which works well.
always check before flashing!
---------- Post added at 11:31 AM ---------- Previous post was at 11:28 AM ----------
IanD91 said:
Ive been having problems flashing ARHD succesfully, ive done a superwipe several times and retried and Cant think of anything else I may be doing wrong, so I figure the MD5 Sum is wrong or something? Any help would be greatly appreciated, thanks!
Click to expand...
Click to collapse
have you been able to flash other roms ok? or is this your first flash?
You know when you type a huge response... only to post it in the wrong thread >_>
Well, the info in here was useful anyway =)
Im making a battery mod for simple CM9. it is supposed to just replace my framework-res.apk with mine.Every time i go to flash it, it says
Finding update package
opening update package
Installing update
Error Flashing zip 'sdcard/................'
here is the updater-script:
copy_dir PACKAGE:system SYSTEM:
I have the flashable zip attached.
josepho1997 said:
Don't let it check the md5(deselect the option). Then it should work. It worked for me
______________________________________________________________________Thank me if I helped you.(Please )
Click to expand...
Click to collapse
thanks but force md5 is not checked, unless you are talking about doing this in code?
And in the log it says
verify md5 for /sdcard...........
No md5 file found, ignoring.
If it is an md5 problem then where and what do i put the md5 file.
josepho1997 said:
Well you could try rebooting your device. If that doesn't work, boot your device into recovery mode(5001). If that doesn't work boot back into normal(4000). Make sure TWRP is updated.(or CWM). Or you could try to flash it manually with your computer.
Click to expand...
Click to collapse
well i think i didnt make the update script right or something. I need someone to check out the zip.
josepho1997 said:
I would test it out but i don't have my Kindle Fire. The USB Port was loose and I'm waiting on my new one. They shouldn't find out I rooted because I unrooted, deleted any app that hinted towards me rooting it, and my battery is completely dead and it can't charge, so I think I'm safe
Click to expand...
Click to collapse
Well its not really a matter of testing it because I'm pretty sure it won't work on any fire because I think I formatted the zip the wrong way. All I need is someone who has made a flash able zip to check the zip out and see what I did wrong. This is my first flash able zip I've ever made. It is a very simple one too.
Sent from my Amazon Kindle Fire using XDA
You are correct that the zip file was formatted wrong. I redid the META-INF you was missing update-binary file and your updater-script was incorrect.
I attached it again with the fixes.
Tera Tike said:
You are correct that the zip file was formatted wrong. I redid the META-INF you was missing update-binary file and your updater-script was incorrect.
I attached it again with the fixes.
Click to expand...
Click to collapse
Thank you so much.I ran out or thanks. I will be sure to thank you tomorrow.Do you ever have to change the binary? Like if I make a different flashable zip can i just keep the update-binary the same? And can you reccomend something for linux to sighn zips. I had to use windows to sighn the one I attached?
Edit: when I flashed a zip it deleted all app data or something? Do you know why?
Sent from my Amazon Kindle Fire using XDA
powerpoint45 said:
Do you ever have to change the binary?
Click to expand...
Click to collapse
No.
powerpoint45 said:
Like if I make a different flashable zip can i just keep the update-binary the same?
Click to expand...
Click to collapse
Yes.
powerpoint45 said:
And can you reccomend something for linux to sighn zips. I had to use windows to sighn the one I attached?
Click to expand...
Click to collapse
I use jarsigner, I they have a Linux version.
powerpoint45 said:
Edit: when I flashed a zip it deleted all app data or something? Do you know why?
Click to expand...
Click to collapse
No I do not, I use this same script to update my device with no issues.
I had a backup of stock before root but when i tried to back up to it today it gave me a md5 mismatch so i couldnt back up to it. From what I seen in beaups thread that I need to be on a stock rom and stock kernal for his s-off method to work. Is there a stock rom that I could flash to use the s-off method?
I'd like this answered as well. I think andy's stock rom near the bottom of the page works, but I haven't had a confirmation yet. Also wondering if odex versus deodexed versions matter.
Same boat im in just waiting for somebody to say which one we can use when we are already rooted and unlocked. I dont know how my md5's mismatched on my stock before root backup but I can't go back to it so Im kinda stuck here until we get a answer.
Aggies1288 said:
Same boat im in just waiting for somebody to say which one we can use when we are already rooted and unlocked. I dont know how my md5's mismatched on my stock before root backup but I can't go back to it so Im kinda stuck here until we get a answer.
Click to expand...
Click to collapse
Just heard andy's bonestock works trying it myself to confirm.
EDIT: Downloading the 1.1 download not the newest. Under old downloads. I would think the more stock the better.
cstrife999 said:
Just heard andy's bonestock works trying it myself to confirm.
EDIT: Downloading the 1.1 download not the newest. Under old downloads. I would think the more stock the better.
Click to expand...
Click to collapse
Just tried v1.0a..... No dice.
I'd test 1.1 but for some reason it won't let me copy the zip over to my phone... Keeps saying the device has stopped working or has been disconnected. Tried many different USB ports.... Going to have to bluetooth it which is going to take even more time...
cstrife999 said:
I'd test 1.1 but for some reason it won't let me copy the zip over to my phone... Keeps saying the device has stopped working or has been disconnected. Tried many different USB ports.... Going to have to bluetooth it which is going to take even more time...
Click to expand...
Click to collapse
Im downloading 1.1 now. Ill get back with y'all on how it went.
Aggies1288 said:
Im downloading 1.1 now. Ill get back with y'all on how it went.
Click to expand...
Click to collapse
I found VZW_Stock_Rooted_deodex from Andy
Trying that now..
mcampos7 said:
I found VZW_Stock_Rooted_deodex from Andy
Trying that now..
Click to expand...
Click to collapse
This is what I've been on since launch day. Curious if this will work.
m4rk0358 said:
This is what I've been on since launch day. Curious if this will work.
Click to expand...
Click to collapse
Actually I'm having more problems with this than I did trying it on 1.0a and NOS...
I'm trying to find my nandroid of stock rooted but I think it was on a drive that failed.
Linux boot, next???
mcampos7 said:
Actually I'm having more problems with this than I did trying it on 1.0a and NOS...
I'm trying to find my nandroid of stock rooted but I think it was on a drive that failed.
Linux boot, next???
Click to expand...
Click to collapse
Yea i got made fun of when using that lol...
SUPER MEGA ULTIMATE DISCLAIMER: IIRC = IF I REMEMBER CORRECTLY. I AM NOT RESPONSIBLE IF THIS DOESN'T WORK/SCREWS UP YOUR DEVICE/BRICKS/ETC. YOU ARE WARNED. THIS WORKED FOR ME IN THE PAST WITH MY GALAXY NEXUS BACKUPS USING CWMTOUCH 6.0.3.6 AND 6.0.4.3.
YOU ARE WARNED.
I HAVE NEVER USED TWRP FOR BACKUPS. IT IS A MERE SUGGESTION THAT THIS METHOD WILL WORK WITH SIMILAR RESULTS. I HAVE NEVER BROWSED A BACKUP FOR TWRP. ANY ATTEMPT YOU MAKE USING A TWRP BACKUP IS OF YOUR OWN COGNIZANCE. YOU HAVE BEEN WARNED.
YOU ARE WARNED.
YOU ARE WARNED.
IIRC: If you have an md5 mismatch while trying to restore in a recovery, try this process:
IF YOU HAVE A BACKUP I HIGHLY SUGGEST STORING THE BACKUP FILE ON YOUR DESKTOP JUST IN CASE!!!!
Boot into whatever ROM you're on ATM.
Browse to your ClockworkMod (or TWRP backup must have an accessible folder for it's backups) using a Root file explorer, which I happen to use "Root Explorer" and open the backup file you just made.
Inside of that will be a nandroid.md5.
Delete that file and reboot into recovery, and try restoring again.
SUPER MEGA ULTIMATE DISCLAIMER: IIRC = IF I REMEMBER CORRECTLY. I AM NOT RESPONSIBLE IF THIS DOESN'T WORK/SCREWS UP YOUR DEVICE/BRICKS/ETC. YOU ARE WARNED. THIS WORKED FOR ME IN THE PAST WITH MY GALAXY NEXUS BACKUPS USING CWMTOUCH 6.0.3.6 AND 6.0.4.3.
YOU ARE WARNED.
YOU ARE WARNED.
YOU ARE WARNED.
This method did work for me several times on several backups, but root and S-Off being so new, I cannot attest that it works for the One. YOU ARE WARNED**!!
cstrife999 said:
Yea i got made fun of when using that lol...
Click to expand...
Click to collapse
For using what? Linux? NOS?
mcampos7 said:
For using what? Linux? NOS?
Click to expand...
Click to collapse
The sojo app called my issues dumb lol. It's hard to get frustrated when humor is involved with the errors.
cstrife999 said:
The sojo app called my issues dumb lol. It's hard to get frustrated when humor is involved with the errors.
Click to expand...
Click to collapse
Looks like we may have to flash the boot.img that they are talking about in the s-off thread anybody have a guide for doing that?
I take it nobody tried deleting the nandroid.md5?
rmaccamr said:
I take it nobody tried deleting the nandroid.md5?
Click to expand...
Click to collapse
I just tried looking for where the nandroid file was. I went to my sdcard on root explorer then to clockworkmod and didn't find any of my backups there. Is there another spot that i need to look in to do that?
Aggies1288 said:
I just tried looking for where the nandroid file was. I went to my sdcard on root explorer then to clockworkmod and didn't find any of my backups there. Is there another spot that i need to look in to do that?
Click to expand...
Click to collapse
If using CWM, they will be under the /data/clockworkmod/backup directory, not /sdcard/clockworkmod/backup.
I tried the odex stock rom, but it won't flash... Anybody have this issue?
santod040 said:
If using CWM, they will be under the /data/clockworkmod/backup directory, not /sdcard/clockworkmod/backup.
Click to expand...
Click to collapse
Ok i found it it was under /data/media/clockworkmod/backup but i dont see any files inside of that that are a md5 file im going to look in the data.ext4.tar file and the system.ext4.tar.a. Does any of those ring a bell? i see the boot.img, data.ext4.tar.a, recovery.img, system.ext4.tar.a, and system.ext4.tar.b. Thats all the files inside the backup i made before i rooted.