Related
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
Hey folks, I recently rooted my LG G3 D850 earlier this week on Lollipop stock. When I go to the Flashify app, recovery image, choose a file, twrp.2.8.0_d850-signed.img, and try to flash it from there, it says error on the screen, and my led light keeps flashing in different colors. Thankfully, I can pull the battery out, and turn it back on to normal. Any help? Thank you.
YoCrae said:
Hey folks, I recently rooted my LG G3 D850 earlier this week on Lollipop stock. When I go to the Flashify app, recovery image, choose a file, twrp.2.8.0_d850-signed.img, and try to flash it from there, it says error on the screen, and my led light keeps flashing in different colors. Thankfully, I can pull the battery out, and turn it back on to normal. Any help? Thank you.
Click to expand...
Click to collapse
Please try the imageprep procedure... Flashing twrp on lollipop doesn't work. You can use either 1.4 or the latest 1.5 version of imageprep by @topet2k12001
Sent from my LG-D855 using Tapatalk
Can I go to flashify, zip file, choose a file, and select imageprep1.4.zip?
http://forum.xda-developers.com/showpost.php?p=59931455&postcount=104 works perfect
linux_svk said:
http://forum.xda-developers.com/showpost.php?p=59931455&postcount=104 works perfect
Click to expand...
Click to collapse
I have the G3 D850. That says D855. It will still work?
YoCrae said:
Can I go to flashify, zip file, choose a file, and select imageprep1.4.zip?
Click to expand...
Click to collapse
@YoCrae, if you want to use imageprep 1.4 or 1.5 please see http://forum.xda-developers.com/showthread.php?p=59287063. The instructions are very clear. Any doubts just drop a message [emoji6]
Sent from my LG-D855 using Tapatalk
YoCrae said:
Hey folks, I recently rooted my LG G3 D850 earlier this week on Lollipop stock. When I go to the Flashify app, recovery image, choose a file, twrp.2.8.0_d850-signed.img, and try to flash it from there, it says error on the screen, and my led light keeps flashing in different colors. Thankfully, I can pull the battery out, and turn it back on to normal. Any help? Thank you.
Click to expand...
Click to collapse
here dude use this method to downgrade your bootloader to the kk version and your download mode partition to kk and then flash the modded boot.img so your phone can boot again with the kk partitions. i have a d850 and this worked perfectly i ran the commands using a terminal emulator and then i pulled the battery out for it to boot again (and you have to keep doing this for some reason) http://forum.xda-developers.com/lg-g3/orig-development/recovery-twrp-touch-recovery-2-8-2-0-t2966129 without doing this you'll keep getting the boot error and the flashing led's. make sure you follow the instructions carefully, good luck!
Hello please help. So I unlocked bootloader, set up Google and finger scanning password. Flashed SuperSU and that's when everything went wrong. Got stuck on the boot logo. Any suggestions? I've read about using the Qualcomm driver method but I'm unsure if it'll work on a Mac? Any help ? I've used twrp to flash ROM no luck. Used stock recovery but adb doesn't detect my devices I guess I didn't enable USB debugging after unlocking the bootloader.
jasj0410 said:
Hello please help. So I unlocked bootloader, set up Google and finger scanning password. Flashed SuperSU and that's when everything went wrong. Got stuck on the boot logo. Any suggestions? I've read about using the Qualcomm driver method but I'm unsure if it'll work on a Mac? Any help ? I've used twrp to flash ROM no luck. Used stock recovery but adb doesn't detect my devices I guess I didn't enable USB debugging after unlocking the bootloader.
Click to expand...
Click to collapse
Flashing the stock firmware using TWRP should do it for you. Just perform a FULL WIPE (formatting all partitions) before flashing the rom and keep in mind that you need a modified TWRP version to flash Oxygen OS based roms. The official TWRP won't do it.
Can you explain what you mean by "formatting all partitions"?
I have a modified twrp recovery. When I click on wipe there is two options " advance wipe" and "format data" is the 2nd optioption the one your referring too as well? I flashed ROM.zip with the modified twrp without formatting data (I rather wait on your reply to be sure) and instead of getting stuck on the boot logo it is doing a bootloop now. Thanks for your assistance BTW.
jasj0410 said:
Can you explain what you mean by "formatting all partitions"?
I have a modified twrp recovery. When I click on wipe there is two options " advance wipe" and "format data" is the 2nd optioption the one your referring too as well? I flashed ROM.zip with the modified twrp without formatting data (I rather wait on your reply to be sure) and instead of getting stuck on the boot logo it is doing a bootloop now. Thanks for your assistance BTW.
Click to expand...
Click to collapse
Advanced Wipe
--> mark
"ART Cache"
"Cache"
"Data"
"Internal Storage"
"System"
--> swipe to wipe
If you don't get any errors
--> restart TWRP (Or you can't access the storage)
--> flash rom
Did that no luck. I'm trying to flash 3.2.7 anything tricky/specific I should be doing ?
I'm going to flash 3.2.6 tomorrow when I get near Wi-Fi and See what happens.
Should I be downloading "OTA zip" or" oxygenOS 3.2.6 full zip"
jasj0410 said:
Did that no luck. I'm trying to flash 3.2.7 anything tricky/specific I should be doing ?
I'm going to flash 3.2.6 tomorrow when I get near Wi-Fi and See what happens.
Should I be downloading "OTA zip" or" oxygenOS 3.2.6 full zip"
Click to expand...
Click to collapse
OTA = on the air update // for upgrading your android version e.g. OOS 3.2.6 --> 3.2.8 // NOT for solo installation!
You can either use OOS 3.2.6 or the very awesome Open Beta 7 (Don't be irritated because there is "OTA" in the filename, both are complete roms)
These are full roms officially from OnePlus.net and I'm pretty sure that they will work together with TWRP 3.0.2-22.
I suppose you simply used the wrong files. Could you tell me where you downloaded the files?
LS.xD said:
OTA = on the air update // for upgrading your android version e.g. OOS 3.2.6 --> 3.2.8 // NOT for solo installation!
You can either use OOS 3.2.6 or the very awesome Open Beta 7 (Don't be irritated because there is "OTA" in the filename, both are complete roms)
These are full roms officially from OnePlus.net and I'm pretty sure that they will work together with TWRP 3.0.2-22.
I suppose you simply used the wrong files. Could you tell me where you downloaded the files?
Click to expand...
Click to collapse
i literally downloaded those files you linked to me and still no luck. it shouldn't be a problem that I'm using android file manager to transfer the rom over to my phone right? I'm going to wipe everything and go to stock recovery and use adb push to flash stock rom. any other suggestions you got?
Anyone please? I've rooted moto g 1st and 4th grn so it's not the fact that I'm being a complete noob. I've downloaded the modified twrp flashed 3.2.6, beta 7 and cyanogenmod. No luck on anything.
jasj0410 said:
Anyone please? I've rooted moto g 1st and 4th grn so it's not the fact that I'm being a complete noob. I've downloaded the modified twrp flashed 3.2.6, beta 7 and cyanogenmod. No luck on anything.
Click to expand...
Click to collapse
Use this guide and try both methods.
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
tnsmani said:
Use this guide and try both methods.
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Click to expand...
Click to collapse
thanks for your reply. i managed to fix it. the other guy's link for a modified twrp didn't work (the custom recovery not the link) so i downloaded another and ended up installing beta 7 which worked. for future reference the link (mega unbrick) you provided me would that work with a mac?
jasj0410 said:
thanks for your reply. i managed to fix it. the other guy's link for a modified twrp didn't work (the custom recovery not the link) so i downloaded another and ended up installing beta 7 which worked. for future reference the link (mega unbrick) you provided me would that work with a mac?
Click to expand...
Click to collapse
I doubt that though there is no specific info on this .
Due to a number of reports of people bricking their devices, I have removed this tutorial.
For instructions to get your device unbricked, please read here.
I'm terribly sorry for the inconvenience.
Hello,
thanks for sharing, but do you also know a way back to wileyfox stock rom? I don't think a twrp backup holds all nand data. When flashing GM4G rom, you also flash ie. modem partition, and I don't think that this is covered by a twrp backup.
bye...DonQ
Seed has a TWRP patched for cm updater. I'm a seed user but I prefer crackling roms
DonQuichotte said:
Hello,
thanks for sharing, but do you also know a way back to wileyfox stock rom? I don't think a twrp backup holds all nand data. When flashing GM4G rom, you also flash ie. modem partition, and I don't think that this is covered by a twrp backup.
bye...DonQ
Click to expand...
Click to collapse
Flash the factory image.
[email protected] said:
Seed has a TWRP patched for cm updater. I'm a seed user but I prefer crackling roms
Click to expand...
Click to collapse
I can't find a link for the Seed TWRP patched for CM Updater. Can you share it?
seb5049 said:
I can't find a link for the Seed TWRP patched for CM Updater. Can you share it?
Click to expand...
Click to collapse
Yeah I would like to know too
VivaLaVent said:
Flash the factory image.
Click to expand...
Click to collapse
I'm not sure this is enough, cause with the GM4G rom some partitions (.img) get flashed, that are not in the swift factory rom...oem.img, devinfo.bin. I think about switching to seed, cause no more nigthlies and seed has official CM14.1 already. But there has to be a bullet-proof way to return to stock...just in case.
bye DonQ
twrp patched by Arvin Quilao
VivaLaVent said:
Yeah I would like to know too
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=457095661767122264 i use this and updated via cm updater twice with no problem....
[email protected] said:
https://www.androidfilehost.com/?fid=457095661767122264 i use this and updated via cm updater twice with no problem....
Click to expand...
Click to collapse
Okay so I'm guessing updating with CM updater does work, but the recovery you linked is not the latest version of TWRP.
Hello, I've tried to flash this rom General Mobile 4G (seed) and it finishes OK, but device does not restart ( brick but USB COM port detected), I've reinserted the battery and device does not turn on, googled a bit, and used qualcomm flash tool to unbrick my wileyfox.
What am I doing wrong here ?
I've also tried with GM_4G_7.0_NRD90R_FASTBOOT_STOCK_ROM_BY_TURKDEVS same problem device is bricked
Also I've tried from stock Cynogen OS (12.1-YOG4PAS33J) but same result device bricked
PS. downloaded files are ok, not corrupted....
Twrp version status...
VivaLaVent said:
Okay so I'm guessing updating with CM updater does work, but the recovery you linked is not the latest version of TWRP.
Click to expand...
Click to collapse
Yeahhh it isnt the latest i know. The latest is 3.0.2-1 but isnt patched for cm ota updates like that shared by me later. The dev stated the official version patched from twrp website will come later. Using it dnt create any prblm.
piromanneo said:
Hello, I've tried to flash this rom General Mobile 4G (seed) and it finishes OK, but device does not restart ( brick but USB COM port detected), I've reinserted the battery and device does not turn on, googled a bit, and used qualcomm flash tool to unbrick my wileyfox.
What am I doing wrong here ?
I've also tried with GM_4G_7.0_NRD90R_FASTBOOT_STOCK_ROM_BY_TURKDEVS same problem device is bricked
Also I've tried from stock Cynogen OS (12.1-YOG4PAS33J) but same result device bricked
PS. downloaded files are ok, not corrupted....
Click to expand...
Click to collapse
I'm having the same problem.
seb5049 said:
I'm having the same problem.
Click to expand...
Click to collapse
I'm starting to think I made an error, can anyone confirm they successfully used this method?
VivaLaVent said:
I'm starting to think I made an error, can anyone confirm they successfully used this method?
Click to expand...
Click to collapse
I was unsuccessful with your method. I even tried two times then I gave up and restored my backup with cm-13
How is it running on CM 14? Is there noticeable lag and such?
If you want CM14, try crDroid, it works great. I'm using it for two weeks now, no FC errors, good battery performance, no serious lags.
When I read the bricks of some users trying to flash a ROM that is meant for a clone with ALMOST the same hardware - I won't try this.
I am considering doing this update. But I have an issue. Since Android 6 has integrated sdcards, I had to reformat the sdcard on every update which is a pain in the ass. I using mixed mode. Is there any way to do an update which allows to reintegrate the sdcard without reformatting the sdcard?
piromanneo said:
Hello, I've tried to flash this rom General Mobile 4G (seed) and it finishes OK, but device does not restart ( brick but USB COM port detected), I've reinserted the battery and device does not turn on, googled a bit, and used qualcomm flash tool to unbrick my wileyfox.
What am I doing wrong here ?
I've also tried with GM_4G_7.0_NRD90R_FASTBOOT_STOCK_ROM_BY_TURKDEVS same problem device is bricked
Also I've tried from stock Cynogen OS (12.1-YOG4PAS33J) but same result device bricked
PS. downloaded files are ok, not corrupted....
Click to expand...
Click to collapse
I seem to have the same problem as you, device doesn't respond, no boot or whatever.
Could you link me to the solution you used to unbrick the device?
Due to a number of reports of people bricking their devices, I have removed this tutorial.
For instructions to get your device unbricked, please read here.
I'm terribly sorry for the inconvenience.
Hi.
Today, during the installation of a custom rom (liquid death, coming from lineage), i accidentally checked the wipe internal storage box so i reinstalled the last marshmallow stock firmware and twrp with odin.
Then i downloaded the rom again and flashed it with twrp, but during boot always appear a message saying "kernel is not seandroid enforcing", then the device starts normally.
How can i fix this error?
Thank you for your help and sorry for my bad english.
Hello
Same problem here
Does someone have a solution ?
Thx
Me too
m21an said:
Hi.
Today, during the installation of a custom rom (liquid death, coming from lineage), i accidentally checked the wipe internal storage box so i reinstalled the last marshmallow stock firmware and twrp with odin.
Then i downloaded the rom again and flashed it with twrp, but during boot always appear a message saying "kernel is not seandroid enforcing", then the device starts normally.
How can i fix this error?
Thank you for your help and sorry for my bad english.
Click to expand...
Click to collapse
Same here on custom ROM.its all to do with the bootloader but I have the correct cpk2 one installed
m21an said:
Hi.
Today, during the installation of a custom rom (liquid death, coming from lineage), i accidentally checked the wipe internal storage box so i reinstalled the last marshmallow stock firmware and twrp with odin.
Then i downloaded the rom again and flashed it with twrp, but during boot always appear a message saying "kernel is not seandroid enforcing", then the device starts normally.
How can i fix this error?
Thank you for your help and sorry for my bad english.
Click to expand...
Click to collapse
Did you fix your problem ? I am having the same one. I appreciate any kind of help
Same issue.
medogan said:
Did you fix your problem ? I am having the same one. I appreciate any kind of help
Click to expand...
Click to collapse
Anyone find a fix?
katrsx said:
Anyone find a fix?
Click to expand...
Click to collapse
Just flash supersu and it will go away.
Not seandroid enforcing
ashyx said:
Just flash supersu and it will go away.
Click to expand...
Click to collapse
Does this error effect functionality? Like some apps are "not optimized for my device" error?