I downloaded the OTA update for my flo (nexus 7 wifi 2013). Checked the md5 checksum and it passes. tried to install it via asb sideload. Unlocked bootloader, stock recovery, stock system image and it says "whole-file verification", "signature verification failed", "installation aborted.
Im at at my wits end why? Everything is ****ing stock and I have re-imaged everything to ****ign stock to be sure and haven't been able to solve this for the last hour.
Any help or insight would be appreciated.
Update: Yes, I've searched this forums and others and most people come up with "its probably a corrupt download". And it is not. Also, tried iinstalled it with TWRP 2.6.3.1 , it still aborts, albeit with a different error (cant recall).
NoobieExtraordinare said:
I downloaded the OTA update for my flo (nexus 7 wifi 2013). Checked the md5 checksum and it passes. tried to install it via asb sideload. Unlocked bootloader, stock recovery, stock system image and it says "whole-file verification", "signature verification failed", "installation aborted.
Im at at my wits end why? Everything is ****ing stock and I have re-imaged everything to ****ign stock to be sure and haven't been able to solve this for the last hour.
Any help or insight would be appreciated.
Update: Yes, I've searched this forums and others and most people come up with "its probably a corrupt download". And it is not. Also, tried iinstalled it with TWRP 2.6.3.1 , it still aborts, albeit with a different error (cant recall).
Click to expand...
Click to collapse
You mentioned that it's not corrupt, but have you verified that the file isn't corrupt via something like an MD5 hash? There are numerous programs you can grab from google to do this.
The MD5 for the copy I downloaded from google: ce344ae6d5d2f74f80c9009947c9cbe9
That really should be the only reason you get that error in my experience...if you could find out what the TWRP log says that would help as well.
WHy not just go the rooted route and install this Stock Rooted 4.4.1 - KOT49E - Official Google OTA! http://forum.xda-developers.com/showthread.php?t=2558756
Ummm....yes....
OJ in Compton said:
You mentioned that it's not corrupt, but have you verified that the file isn't corrupt via something like an MD5 hash? There are numerous programs you can grab from google to do this.
The MD5 for the copy I downloaded from google: ce344ae6d5d2f74f80c9009947c9cbe9
That really should be the only reason you get that error in my experience...if you could find out what the TWRP log says that would help as well.
Click to expand...
Click to collapse
I mentioned that in my original post. Twice. I appreciate the response, but no that isn't the issue.
Because...
naturecannon said:
WHy not just go the rooted route and install this Stock Rooted 4.4.1 - KOT49E - Official Google OTA! http://forum.xda-developers.com/showthread.php?t=2558756
Click to expand...
Click to collapse
I want this stock without root. I guess, it is an option, but then I'd have to unroot it?
NoobieExtraordinare said:
I mentioned that in my original post. Twice. I appreciate the response, but no that isn't the issue.
Click to expand...
Click to collapse
I'm an idiot. Not sure how I managed to miss your first sentence, sorry about that.
Does it not say where the verification failed? It checks each system file that needs to be patched one by one and when it gets to one that's been modified it aborts the update, whenever this happens for me it says exactly which file it failed on
Nope
AlderCass said:
Does it not say where the verification failed? It checks each system file that needs to be patched one by one and when it gets to one that's been modified it aborts the update, whenever this happens for me it says exactly which file it failed on
Click to expand...
Click to collapse
Says "whole-file verification failed", "signature verification failed" and "installation aborted", like i mentioned in my post.
Related
I tried restoring back to uprooted original Rom but the RUU errors out. Even downloaded new one.
I then extracted the boot and system image and the boot will flash but the system shows as bad and will not flask.
Rebooted and tried to recovery the rom zip but again fails as bad.
So right now I am at a lost on how to restore to a factory fresh system.
Thanks
EdwardLotz said:
I tried restoring back to uprooted original Rom but the RUU errors out. Even downloaded new one.
I then extracted the boot and system image and the boot will flash but the system shows as bad and will not flask.
Rebooted and tried to recovery the rom zip but again fails as bad.
So right now I am at a lost on how to restore to a factory fresh system.
Thanks
Click to expand...
Click to collapse
Is this the error you are getting?
Error Code: -5001 : 0x80070002
Error Information:
>SetupNew\setup.cpp (142)
I'm getting the same thing with the RUU I downloaded and am seeking to get back to stock. So far no success, but see my thread below to see if something I've tried might work for you.
http://forum.xda-developers.com/showthread.php?p=30025087#post30025087
It'll be easier to diagnose your problem if you post any error messages.
You need to have stock recovery before running an RUU.
BenPope said:
It'll be easier to diagnose your problem if you post any error messages.
You need to have stock recovery before running an RUU.
Click to expand...
Click to collapse
I have the stock RUU I used it last month without issue. When running it when it try's to update ram I get an unknown error 155. Make sure you have correct software.
When I extract the rom to flask. It fails and says bad rom.
I was able to find a zip original rom and using recovery from zip I was able to install and revert to 1.29.401.11
But trying download the software update to the new version after installing the original recovery and relocking it fails on install. It get about a quarter of the way through then recovery gets a red exclamatory or something and installation stops. So I tried installing the RUU again and still get the same error hoping that a fresh install would correct the update issue.
I hope this helps
EdwardLotz said:
But trying download the software update to the new version after installing the original recovery and relocking it fails on install. It get about a quarter of the way through then recovery gets a red exclamatory or something and installation stops......
Click to expand...
Click to collapse
Did you try power and up-vol at the red exclamation screen. I thought I saw somewhere that this will work (trying to find the link for it)? Give it a shot and let us know.
requiem11 said:
Did you try power and up-vol at the red exclamation screen. I thought I saw somewhere that this will work (trying to find the link for it)? Give it a shot and let us know.
Click to expand...
Click to collapse
Get the details of install
Gets downto verifying current system...
Assert failed: apply patch check /system /app/7digital3.apk
E:error in //internal_sdcard/download/ota (file)
Status 7
Installation aborted
I hope this helps
EdwardLotz said:
Get the details of install
Gets downto verifying current system...
Assert failed: apply patch check /system /app/7digital3.apk
E:error in //internal_sdcard/download/ota (file)
Status 7
Installation aborted
I hope this helps
Click to expand...
Click to collapse
OK, I get it, you don't have a problem getting back to stock, but rather it's an OTA update error you have. I don't know anything about OTA updates but this error message should help someone else troubleshoot what's going on. Is it possible that you've used the incorrect RUU, but it just happened to work for you and now your image does not correspond with your correct OTA? Maybe post the exact file name of your RUU and the results of "fastboot getvar cid" and "fastboot getvar version-main".
Good luck!
hey everyone,
so what's happened is my phone refuses to flash anything in TWRP :T
anything i attempt to flash aborts at md5 and says FAILED in red letters.
im guessing the internal mightve gotten corrupted cause i've used multiple different zips that ive flashed before.
even redownloaded some of them and tried again.
already checked the forums, and found nada so i was hoping someone out their could help me out on this one.
try to check md5 of your zip manually, with md5 checker, or reflash recovery only with tool.... : D
thanks a lot man, i really appreciate it! turns out md5s were fine, the recovery was just borked. so i used tool to install cwm for a while.
i use twrp and see no such issue.
sent from my i9250
bk201doesntexist said:
i use twrp and see no such issue.
sent from my i9250
Click to expand...
Click to collapse
There are some compatibility issues with TWRP when trying to flash certain zips that have dynamically linked binaries (like zipalign). TWRP needs static binaries that don't link to any libraries. See here.
I am having difficulty installing new rom. I am currently using cwm 5.0.4 which I is old version but cannot figure out how to upgrade as ROM manager does not suppot my device I747M. I also tried using twrp but with both the recoveries it gives me error md5 sum not found. Can anyone suggest a solution please..
amonrule said:
I also tried using twrp but with both the recoveries it gives me error md5 sum not found. Can anyone suggest a solution please..
Click to expand...
Click to collapse
You have signature verification enabled; in TWRP you would go to Settings and uncheck "signature verification". (I'm not sure how you would do that in CWM.)
NO thats not the reason. I have unchecked signature verificartion still it shows failed.. N e other solution?
Can someone please let me know what I'm missing. I'm rooted, and have even flashed a couple ROMs successfully but most of them will fail to install withan error saying "E: No MD5 file found for [insert whatever ROM]. I'm running TWRP recovery (v.2.3.3.1)
Sprint Galaxy S III
esco_three said:
Can someone please let me know what I'm missing. I'm rooted, and have even flashed a couple ROMs successfully but most of them will fail to install withan error saying "E: No MD5 file found for [insert whatever ROM]. I'm running TWRP recovery (v.2.3.3.1)
Sprint Galaxy S III
Click to expand...
Click to collapse
In the settings (either in "advanced" or on the install menu) on TWRP you can choose to verify the MD5 sum. I believe that if you uncheck that option it should work.
Let me know if this works!
topherk said:
In the settings (either in "advanced" or on the install menu) on TWRP you can choose to verify the MD5 sum. I believe that if you uncheck that option it should work.
Let me know if this works!
Click to expand...
Click to collapse
I have tried that, for multiple ROMs, but still fails.
esco_three said:
I have tried that, for multiple ROMs, but still fails.
Click to expand...
Click to collapse
Are you on the latest version of TWRP? If not, try updating and see if that fixes it
And what rom is it thats failing?
CNexus said:
Are you on the latest version of TWRP? If not, try updating and see if that fixes it
And what rom is it thats failing?
Click to expand...
Click to collapse
I will try the latest version of TWRP and see if that works.
The fail has been happening on multiple ROMs. AOSPA 3.15: Hybrid Mode, MIUIAndroid v4.1 & Avatar ROM to name a few. All the same issue.
No MD5 file found
I am having the same issue! this happened on multiple ROMs from various developers, I have tried every thing suggested and verified rooted.
Badfish63 said:
I am having the same issue! this happened on multiple ROMs from various developers, I have tried every thing suggested and verified rooted.
Click to expand...
Click to collapse
It's not really an error, TWRP just checks to see if there's a corresponding md5 file with the md5 checksum for whatever it is that you're flashing
You can flash any rom perfectly fine without it, but I would make sure that you check the md5sum against the one that the ROM thread or ROM download site gives you
No MD5 file found
CNexus said:
It's not really an error, TWRP just checks to see if there's a corresponding md5 file with the md5 checksum for whatever it is that you're flashing
You can flash any rom perfectly fine without it, but I would make sure that you check the md5sum against the one that the ROM thread or ROM download site gives you
Click to expand...
Click to collapse
Thanks! But I can't seem to even do my first flash! I noticed in any of the ROMS I download for some reason it does not pull the MD5 file. I have downloaded from here XDA and other sites, and android forums. I don't get it. this should be fairly easy according to all the research I have done even before my first attempt.
no md5 file--please help
can someone help me. I am fairly new at custom rom work, but I rooted my galaxy note 3 (Verizon) using kingo, and installed safestrap (latest version) and attempted to install cm11 but while installing it does a md5 file check and says no md5 file found. when I reboot, the Samsung screen comes up and then it goes and stays black. I have to pull battery and go back to stock rom. I have tried reformatting my ext. storage and reinstall..no go. please help. thank you very much in advance.
west1986 said:
can someone help me. I am fairly new at custom rom work, but I rooted my galaxy note 3 (Verizon) using kingo, and installed safestrap (latest version) and attempted to install cm11 but while installing it does a md5 file check and says no md5 file found. when I reboot, the Samsung screen comes up and then it goes and stays black. I have to pull battery and go back to stock rom. I have tried reformatting my ext. storage and reinstall..no go. please help. thank you very much in advance.
Click to expand...
Click to collapse
You might have a better chance at an answer in the forum for your specific carrier and device, this is the forum for the Sprint Samsung Galaxy S3.
topherk said:
In the settings (either in "advanced" or on the install menu) on TWRP you can choose to verify the MD5 sum. I believe that if you uncheck that option it should work.
Let me know if this works!
Click to expand...
Click to collapse
I'm experiencing the same issue.
L710 currently Slimbean, updating to Slimkat 4.4.2 I get the fail for the MD5
I have TWRP 2.6.0.0
I don't see any uncheck MD5 option only in settings and these are already unchecked.
When flashing back to Slimbean 4.3 I get the error
E: error opening '/data/lost + found'
E: error no such file or directory
But it still passes and I'm on 4.3
Reivaj1803 said:
I'm experiencing the same issue.
L710 currently Slimbean, updating to Slimkat 4.4.2 I get the fail for the MD5
I have TWRP 2.6.0.0
I don't see any uncheck MD5 option only in settings and these are already unchecked.
When flashing back to Slimbean 4.3 I get the error
E: error opening '/data/lost + found'
E: error no such file or directory
But it still passes and I'm on 4.3
Click to expand...
Click to collapse
It finally worked!
I updated TWRP to the latest 2.6.3.1 and Slimkat flashed with no problems.
This new setup took me for a loop, wasn't expecting it. After all said and done, I am running. :good: :good:
Reivaj1803 said:
It finally worked!
I updated TWRP to the latest 2.6.3.1 and Slimkat flashed with no problems.
This new setup took me for a loop, wasn't expecting it. After all said and done, I am running. :good: :good:
Click to expand...
Click to collapse
I was going to suggest that you should try flashing over the new TWRP recovery. Best of luck!
Dolby
CNexus said:
Are you on the latest version of TWRP? If not, try updating and see if that fixes it
And what rom is it thats failing?
Click to expand...
Click to collapse
I am trying to flash dolby. The flash is successful but the app icon doesn't appear on the screen. In the recovery log it says md5 file not found. I've tried flashing viper too but the condition is the same. Please help.
Mr. Struck said:
You might have a better chance at an answer in the forum for your specific carrier and device, this is the forum for the Sprint Samsung Galaxy S3.
Click to expand...
Click to collapse
1. Installed Stock ROM, using Odin3_v3.11.2 (Run as Adminstrator)
N900XXUEBPB1_N900ODDEBPB1_N900DDUEBOB1_HOME.tar.md5
My "Samsung Galaxy Note 3 SM-N900" Running on 5.0 lollipop
2. I have rooted my "Samsung Galaxy Note 3 SM-N900" using followiing file using Odin3_v3.11.2 (Run as Adminstrator)
CF-Auto-Root-ha3g-ha3gxx-smn900
3. Later I've installed TWRP recovry, using Odin3_v3.11.2 (Run as Adminstrator)
twrp-3.0.2-0-ha3g.img_safe.tar
Now when I try to install MIUI for "Samsung Galaxy Note 3 SM-N900" port ROM, either getting Failed or If it is success my phone does not startup hung at SAMSUNG logo (Waited for nearly 2 hrs).
miui_n900_lushengduan_6.5.27_19d567b4f3_4.4.zip
miui_n9005_bhflower_6.5.27_e7133a52f8_4.4.zip
- Tried above method after wiping the cache and internal drive still the same.
- Tried to install from external card same error
- Tried to install from internal card same error
PLEASE HELP.I HAVE STRUGGLING FROM LAST 1 WEEK WITH ALL THE TRIEL AND ERROR METHOD.
Is there any solution to this problem? im also experiencing today.
my unit is galaxy n3 international im running with the rom cm 14.1 cyanogenmod using TWRP 3.0.2-1 and i want to install different rom's but i always got stuck whenever i swipe to flash the new rom it say's no md5 after a minute my system is restarting and nothing's happen.
ken041387 said:
Is there any solution to this problem? im also experiencing today.
my unit is galaxy n3 international im running with the rom cm 14.1 cyanogenmod using TWRP 3.0.2-1 and i want to install different rom's but i always got stuck whenever i swipe to flash the new rom it say's no md5 after a minute my system is restarting and nothing's happen.
Click to expand...
Click to collapse
Turn off md5 verification in twrp settings
I also have this problem on my galaxy alpha sm-g850f I'm running TWRP 2.8.7.0 it says "no Md5 file found" can someone help me
Hi guys,
Turns out I have been trying to root my s4 mini for hours now, but without success. I got up to the step of booting into CWM, however, I do not see a "install from ZIP" option. The closest option to it that I see is "apply update from external storage". Though, if I go and select the "S4Mini_RootKit_v2.zip" file, I get the following error:
E:footer is wrong
E:signature verification failed
I have been trying rooting using this method:"
http://forum.xda-developers.com/showthread.php?t=2494435
Can someone please help me? I tried looking up, but can't seem to find a solution!!
Rizera said:
Hi guys,
Turns out I have been trying to root my s4 mini for hours now, but without success. I got up to the step of booting into CWM, however, I do not see a "install from ZIP" option. The closest option to it that I see is "apply update from external storage". Though, if I go and select the "S4Mini_RootKit_v2.zip" file, I get the following error:
E:footer is wrong
E:signature verification failed
I have been trying rooting using this method:"
http://forum.xda-developers.com/showthread.php?t=2494435
Can someone please help me? I tried looking up, but can't seem to find a solution!!
Click to expand...
Click to collapse
boot into cwm recovery & flash it - https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
You haven't installed a "custom recovery". From what you've described it sounds like your using stock recovery which can't flash custom zips.
Sureshtuty said:
boot into cwm recovery & flash it - https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Click to expand...
Click to collapse
Thanks for the help, but it did't work. I got the same error
RuffBuster said:
You haven't installed a "custom recovery". From what you've described it sounds like your using stock recovery which can't flash custom zips.
Click to expand...
Click to collapse
Looks like you are absolutely right. I have no idea why is that though. I have done the process of flashing the md5 file through Odin and according to it, with "success". However, it looks like it did not install. Why could that be?! Maybe because I am using Windows 10?
Thanks a lot for the help.
Rizera said:
Why could that be?! Maybe because I am using Windows 10?
Thanks a lot for the help.
Click to expand...
Click to collapse
That could be an issue. Do a Google search for Samsung Odin windows 10. Also make sure your anti virus is off. I know their were a lot of issues with Windows 8 so..
RuffBuster said:
That could be an issue. Do a Google search for Samsung Odin windows 10. Also make sure your anti virus is off. I know their were a lot of issues with Windows 8 so..
Click to expand...
Click to collapse
You were absolutely right...I just tried it on a Windows 8 PC and I got it working on the very first try...
It is crazy, because according to Odin, it shows as "success" when I try to flash the file, even though it does not work.
Thanks a lot for the heads up. I am sure it will affect other people, though.