Whenever I try to flash anything I get a error of MD5 check error. There is no problem with the files because I flash the ROM few days back. Now I decided to change ROM then I am getting this error. Here are the screenshots of the error.
Please help me out.
Related
When I am trying to go back to my previous ROM, I am getting the following error: "error while flashing boot image".
Initially i got "check MD5 failed" error. But after removing the spaces in the recovery file name, md5 error gone, but got error for flashing boot image.
How can I fix it? other than reflash.. I want to restore my settings.
Thanks in advance
bump
any idea? is this error message depend on current ROM?
Hi,
I'm working on this problem for three days now, dont know what else I can do.
I have an htc one s (s3), hboot version 3.1.0, cid htc 612, twrp v 5.0.0.
My phone is stuck on the htc white screen (quitely brilliant, this build is for...).
I could not find the correct ruu in the web so I cant go back to stock.
When I try to install a rom, it just says:
Checking for md5: no md5 file found..
Skipping md5 check: no md5 file found..
Error flashing zip 'rom name'
And thats it! I cant even understand where it fails.
Does anyone have any idea how to fix it?
I keep working on it and still can't find a solution.
Currently all i want to do is to run "su" command, but i get the error:
/sbin/sh: su: not found.
I have tried to root my phone and it seems to be rooted, and I have no idea
what this error is.
Please help me solve that -
How can I run adb su while having no rom?
can you flash CM recovery?. TWRP have problem with some roms. I come across some roms that twrp will not flash, but cm will.
Unfortunately I can't :/
It installs the zip, but when i go to recovery in the bootloader,
It just get stuck on the "entering recovery" message..
http://forum.xda-developers.com/images/smilies/confused.gif
If you can get into fastboot you should be able to flash a new recovery.
Yes as I said, it flashes the recovery but when I try to enter it,
It gets stuck on the "entering recovery" messagel
I'm updating the status in case anyone will have an idea.
I found out that my problem is not root, its that after I make changes via ADB SHELL, they won't SURVIVE REBOOT.
Meaning - if I change the cid, the changes will not be saved after reboot,
Does anyone knows how to solve that issue? :angel:
Everytime I attempt to flash from a zip file in recovery mode I get operation aborted and error message. I never abort it. I have unlocked my bootloader and s-off my phone. I noticed in recovery it says (Tamper) and ideas how to bypass this message. Its annoying and I am unable to install a custom rom due to this. I have been using weaksause to root while phone is on and SuperSU will not install continues to give error messages. I am not sure what I am doing wrong. I have googled and tried so many ways without luck. I am a noob at most of this but have used google a lot and understand quite a bit but I am lost.
I can't flash roms anymore and I don't know the reason why. Everytime I try to flash one I get a red error message : " E:Error executing updater binary in zip '/sdcard/romname.zip' " I tried changing to an other custom recovery, got my phone back to stock but it's still doesn't work. Do some of you know what the problem could be? Thanks!
SOLVED : I flashed a firmware update (https://mega.co.nz/#!acIjQRYJ!3vVAuOCfwNStSl3AcrDnQJYs1IgchuHZU7QyutNYf7c) and it's working now.
Hello, I currently have Cyanogenmod 11 on my device, but I want to revert to the stock ROM again.
I have the B127 FW on my external SD as the UPDATE.APP within the dload folder.
I flashed stock recovery and after rebooting a couple of times, the update seemed to work at first, as there was a bar to indicate the progress of the install. But I get a failure to install error. Saying there is no UPDATE.APP.. which I obviously do have.
Anyone know what is wrong? I tried unrooting, putting the dload folder on internal SD, switching FW versions in dload folder (B130, B127, etc.)
I keep getting this error though and I have no clue what is wrong and searching yields no results.
Bump
Time ago I had the same problem. At that time (in my case) I solved changing the SD card, re-downloding the ROM (maybe was corrupted), and obtaining the stock recovery by unpacking the just downloaded ROM. You can try the sme way. For me worked fine.
Thanks for the reply! I will try this and report back on status.
So no thing is working. No matter what I do, I get "there is no UPDATE.APP", any more suggestions?
Try downloading the correct stock recovery. Most of the times it has been reported that as the problem.
Try several version of stock recovery. In this forum, somewhere, there's the link where to download from.
Thanks so much! It finally worked! I just downloaded the B137 FW and used this tool: http://forum.xda-developers.com/showthread.php?t=2433454 to get the recovery.
my problem is the same as above but the phone says i have unlocked device but i never unlocked the bootloader cant flash anything through fastboot except "fastboot update" cant flash recovery or anything cuz technically my bootloader is still locked and now im stuck at rescue mode screen with "attention please update system again" and at the bottom is says "Error Func NO:12(FUNC_LOAD_IOM3)
Error NO: 1
any ideas it would be much appreciated thanks
mattwheat said:
my problem is the same as above but the phone says i have unlocked device but i never unlocked the bootloader cant flash anything through fastboot except "fastboot update" cant flash recovery or anything cuz technically my bootloader is still locked and now im stuck at rescue mode screen with "attention please update system again" and at the bottom is says "Error Func NO:12(FUNC_LOAD_IOM3)
Error NO: 1
any ideas it would be much appreciated thanks
Click to expand...
Click to collapse
Hi. That error has something to do with the sensors I think.
read this: http://forum.xda-developers.com/mate-7/help/factory-reset-rooted-mate-7-t3096641
On page 2 I posted two links, one in chinese and one in italian. In the one in chinese they are talking that this error it's from the sensors. In the second link, that it is in italian I saw that in last post someone told that he had the same error and fixed in service.