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
I have jellybean 4.1.2 stock and rooted. I also have twrp 2.5 installed.
I am trying to install this rom: Jedi Mind Trick JB3 !-- http://d-h.st/xPj
These are the steps I did:
1. Downloaded ROM and used USB Storage to transfer to phone
2. Made a backup using rom toolbox app
3. Wiped data (factory data reset) using TWRP
4. Clicked Install in TWRP and selected ROM. When I tried installing I got the error below:
Checking for MD5 file...
Skipping MD5 Check; no MD5 file found.
Verifying zip signature...
E:Zip signature verification failed: 1
Error flashing zip '/sdcard/Douwnload/JedimindTrick....
Updationg partition details:
FAILED.
============
Anyone know what i'm doing wrong? Please help me!
I just noticed after my phone rebooted I no longer have working phone service and none of my google apps are working. Please help me.
nursebro said:
I have jellybean 4.1.2 stock and rooted. I also have twrp 2.5 installed.
I am trying to install this rom: Jedi Mind Trick JB3 !-- http://d-h.st/xPj
These are the steps I did:
1. Downloaded ROM and used USB Storage to transfer to phone
2. Made a backup using rom toolbox app
3. Wiped data (factory data reset) using TWRP
4. Clicked Install in TWRP and selected ROM. When I tried installing I got the error below:
Checking for MD5 file...
Skipping MD5 Check; no MD5 file found.
Verifying zip signature...
E:Zip signature verification failed: 1
Error flashing zip '/sdcard/Douwnload/JedimindTrick....
Updationg partition details:
FAILED.
============
Anyone know what i'm doing wrong? Please help me!
Click to expand...
Click to collapse
U need to flash SGH-T989_DARKSIDE.SUPER.WIPE_EXT4.zip first then the rom :thumbup:
Sent from my SGH-T989 using Tapatalk 2
i tried flashing above file now my phone is stuck in the samsung gs2 splash screen. Does this mean im bricked?
im so sad. please help me someone.
nursebro said:
i tried flashing above file now my phone is stuck in the samsung gs2 splash screen. Does this mean im bricked?
im so sad. please help me someone.
Click to expand...
Click to collapse
Can you boot into twrp or download mode?
your phones not bricked unless its totally off and wont turn back off.
You just have a boot loop, its no big deal.
nursebro said:
i tried flashing above file now my phone is stuck in the samsung gs2 splash screen. Does this mean im bricked?
im so sad. please help me someone.
Click to expand...
Click to collapse
If you are running TWRP 2.5.0.0 like me
do this...
Boot into recovery...
go to Wipe
go to advanced wipe
select dalvik cache, data, system,cache and preload only
swipe to wipe
go to install
select JMT JB 3 rom
flash it
do not wipe anything else after
dont fix permissions
just reboot
it will work
be patient takes a few minutes to load
IVIorph said:
If you are running TWRP 2.5.0.0 like me
do this...
Boot into recovery...
go to Wipe
go to advanced wipe
select dalvik cache, data, system,cache and preload only
swipe to wipe
go to install
select JMT JB 3 rom
flash it
do not wipe anything else after
dont fix permissions
just reboot
it will work
be patient takes a few minutes to load
Click to expand...
Click to collapse
I dont think i can boot into recovery. my phone keeps getting stuck in galaxy s2 loading screen. is there another way to get into recovery to do the wipe?
I really hope my phone is not already bricked.
nursebro said:
I dont think i can boot into recovery. my phone keeps getting stuck in galaxy s2 loading screen. is there another way to get into recovery to do the wipe?
I really hope my phone is not already bricked.
Click to expand...
Click to collapse
make sure your phone is not connected to usb
you must hold down volume up at down and power until you feel a vibration
when you feel a vibration let go of the power button only
this will get you to recovery... then follow my steps
and let us know how it went... good luck m8
IVIorph said:
make sure your phone is not connected to usb
you must hold down volume up at down and power until you feel a vibration
when you feel a vibration let go of the power button only
this will get you to recovery... then follow my steps
Click to expand...
Click to collapse
ok i will try it. please stay incase i need help.
nursebro said:
ok i will try it. please stay incase i need help.
Click to expand...
Click to collapse
Oh one more thing...
you might want to try to redownload the rom
just in case its fragmented somehow
if you get into recovery you can copy over the rom again while in recovery
make sure you are usb unplugged
boot recovery
plug usb into computer
go to mount
only cache, internal sdcard and micro sdcard are selected on mine
then click on mount usb storage
copy over fresh copy of rom
then follow my flash instructions
IVIorph said:
Oh one more thing...
you might want to try to redownload the rom
just in case its fragmented somehow
if you get into recovery you can copy over the rom again while in recovery
make sure you are usb unplugged
boot recovery
plug usb into computer
go to mount
only cache, internal sdcard and micro sdcard are selected on mine
then click on mount usb storage
copy over fresh copy of rom
then follow my flash instructions
Click to expand...
Click to collapse
You are a genius. I followed the steps you mentioned and now have Jedimind ROM installed. Thank you so much for your help. I felt like i was going to have a heart attack because i thought my phone was bricked.
nursebro said:
You are a genius. I followed the steps you mentioned and now have Jedimind ROM installed. Thank you so much for your help. I felt like i was going to have a heart attack because i thought my phone was bricked.
Click to expand...
Click to collapse
cool glad I could help
just don't forget to hit the thanks button m8 cheers!
IVIorph said:
cool glad I could help
just don't forget to hit the thanks button m8 cheers!
Click to expand...
Click to collapse
I sure will!
:good::good::good::good::good::good::good::good::good:
esema1o said:
U need to flash SGH-T989_DARKSIDE.SUPER.WIPE_EXT4.zip first then the rom :thumbup:
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
To the OP, I'm glad you got it working. JMT JB3 is great. I'm on it too. I love it.
Just a side note on these scripts. Darkside does not work with anything based off of the official 4.1.2 release because of the Preload that is included. You need to use the new modified ones from here: http://forum.xda-developers.com/showthread.php?t=2235141
nursebro said:
I have jellybean 4.1.2 stock and rooted. I also have twrp 2.5 installed.
I am trying to install this rom: Jedi Mind Trick JB3 !-- http://d-h.st/xPj
These are the steps I did:
1. Downloaded ROM and used USB Storage to transfer to phone
2. Made a backup using rom toolbox app
3. Wiped data (factory data reset) using TWRP
4. Clicked Install in TWRP and selected ROM. When I tried installing I got the error below:
Checking for MD5 file...
Skipping MD5 Check; no MD5 file found.
Verifying zip signature...
E:Zip signature verification failed: 1
Error flashing zip '/sdcard/Douwnload/JedimindTrick....
Updationg partition details:
FAILED.
============
Anyone know what i'm doing wrong? Please help me!
Click to expand...
Click to collapse
So guys, what was supposed to be the correct procedure for this installation?
sojay said:
So guys, what was supposed to be the correct procedure for this installation?
Click to expand...
Click to collapse
The procedure for a rom installation is usually listed on its OP<-Opening Page
One more thing... you asked me in a text message about root...
TWRP 2.5.0.0 has the ability to root a device...
here is... IMO the easiest procedure to install stock 4.1.2, recovery and root
flash stock rom with odin (I rebooted to system looked at the sock rom quick and went back to odin(should still work without restart toggle on))
flash TWRP 2.5.0.0 (with reboot toggle on)
open TWRP go to reboot and reboot system (it will prompt you to install root)
when phone boots open SU update done!
nursebro said:
I have jellybean 4.1.2 stock and rooted. I also have twrp 2.5 installed.
I am trying to install this rom: Jedi Mind Trick JB3 !-- http://d-h.st/xPj
These are the steps I did:
1. Downloaded ROM and used USB Storage to transfer to phone
2. Made a backup using rom toolbox app
3. Wiped data (factory data reset) using TWRP
4. Clicked Install in TWRP and selected ROM. When I tried installing I got the error below:
Checking for MD5 file...
Skipping MD5 Check; no MD5 file found.
Verifying zip signature...
E:Zip signature verification failed: 1
Error flashing zip '/sdcard/Douwnload/JedimindTrick....
Updationg partition details:
FAILED.
============
Anyone know what i'm doing wrong? Please help me!
Click to expand...
Click to collapse
That looks like a bad download to me.
Sent from my SGH-T989 using xda app-developers app
---------- Post added at 03:35 PM ---------- Previous post was at 02:58 PM ----------
PJcastaldo said:
That looks like a bad download to me.
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Redownload the ROM. Also turn off sig verification in twrp.
Flashing a ROM isn't as hard as some people make it. All these crazy steps.. And waiting and blah blah.. Useless.
Sent from my SGH-T989 using xda app-developers app
nursebro said:
i tried flashing above file now my phone is stuck in the samsung gs2 splash screen. Does this mean im bricked?
im so sad. please help me someone.
Click to expand...
Click to collapse
There is no ROM on your device. That's why it gets stuck on the splash screen... No OS to boot into.
Sent from my Galaxy Nexus using xda premium
when i tried to install d update.zip the teminal is showing this:
Installing ‘/sdcard/update.zip
Checking for MD5 file …
Skipping MD5 check: no MD5 file found (True, there isn’t one in the ZIP file)
assert failed: getprop(“ro.product.device”) == “blaze” ||
E:unknown command [err_string]
getprop(“ro.product.device”) == “blaze”
E:unknown command [err_string]
E:Error executing updater binary in zip ‘/sdcard/update.zip’
Error flashing zip ‘/sdcard/update.zip’
Updating partition details…
i am getting above errors.i Dont know why this kindle is making me irritated .Please anyone help me with this.,.
You are using new a version of TWRP, right?, like 2.6? I suggest to use TWRP 2.2
Sent from my Amazon Kindle Fire using xda app-developers app
404-Not Found said:
You are using new a version of TWRP, right?, like 2.6? I suggest to use TWRP 2.2
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Sorry for the late reply . it took some time for me for this (as i am a beginner) . I have install 2.2 and installed update.zip file
terminal lines:
verifying update.zip
verifying portions.,.
and i selected reboot
on reboot there is kindle fire logo(white and orange) and led light(orange) .,.,and thats all its not going any further
Did you factory reset first?
soupmagnet said:
Did you factory reset first?
Click to expand...
Click to collapse
yea soupmagnet i did it . i have swiped dalvik,cache and did a factory reset
kvnkarthik said:
yea soupmagnet i did it . i have swiped dalvik,cache and did a factory reset
Click to expand...
Click to collapse
You you get the same results with every ROM or just this one?
kvnkarthik said:
Sorry for the late reply . it took some time for me for this (as i am a beginner) . I have install 2.2 and installed update.zip file
terminal lines:
verifying update.zip
verifying portions.,.
and i selected reboot
on reboot there is kindle fire logo(white and orange) and led light(orange) .,.,and thats all its not going any further
Click to expand...
Click to collapse
That error happened to me before, but it was only when I used 2.6 Now I use 2.2
Sent from my Amazon Kindle Fire using xda app-developers app
soupmagnet said:
You you get the same results with every ROM or just this one?
Click to expand...
Click to collapse
i tried to install http://forum.xda-developers.com/showthread.php?t=2041694 rom onto kindle but i was stuck at the first itself.i had problem with rooting .i chked status of the device and unrooted it by using adb commands.i have installed twrp to revert kindle to stock and i am getting this. shall i try installing another ROM
kvnkarthik said:
i tried to install http://forum.xda-developers.com/showthread.php?t=2041694 rom onto kindle but i was stuck at the first itself.i had problem with rooting .i chked status of the device and unrooted it by using adb commands.i have installed twrp to revert kindle to stock and i am getting this. shall i try installing another ROM
Click to expand...
Click to collapse
By all means, yes, try a different ROM.
soupmagnet said:
By all means, yes, try a different ROM.
Click to expand...
Click to collapse
its showing an error when i try to enter recovery or fastboot mode .KFU is showing that adb status is online and device status as unknown. please tell me how could i got to TWRP mode.since adb is active i have tried to run in shell then it showed me an error -"exec '/system/bin/sh' failed:no such file or dicrectory(2)\"
kvnkarthik said:
its showing an error when i try to enter recovery or fastboot mode .KFU is showing that adb status is online and device status as unknown. please tell me how could i got to TWRP mode.since adb is active i have tried to run in shell then it showed me an error -"exec '/system/bin/sh' failed:no such file or dicrectory(2)\"
Click to expand...
Click to collapse
Hmm...as I suspected, that is the exact error you would receive if you tried to flash a ROM without first performing a factory reset (perhaps you were mistaken in thinking you did so?).
Your shell is unavailable, which means you cannot use it to change the bootmode to access recovery. However, if you have FireFireFire installed, you can use it to access custom recovery with the power button. If you don't have FireFireFire installed, then shame on you :wags finger: because you'll need a factory cable to get into fastboot so you can access recovery from there.
soupmagnet said:
Hmm...as I suspected, that is the exact error you would receive if you tried to flash a ROM without first performing a factory reset (perhaps you were mistaken in thinking you did so?).
Your shell is unavailable, which means you cannot use it to change the bootmode to access recovery. However, if you have FireFireFire installed, you can use it to access custom recovery with the power button. If you don't have FireFireFire installed, then shame on you :wags finger: because you'll need a factory cable to get into fastboot so you can access recovery from there.
Click to expand...
Click to collapse
:silly: :silly: i don't have a factory cable but i have usb cable and i have adb online .what can i do to get out from here
kvnkarthik said:
:silly: :silly: i don't have a factory cable but i have usb cable and i have adb online .what can i do to get out from here
Click to expand...
Click to collapse
Get a factory cable. That's all you can do...that is, without opening the device and shorting a certain pin to drop the device into usbboot so you can install a new bootloader and custom recovery, which would also put the device into fastboot mode afterwards...but I would suggest you steer clear from that option until you have no other choice.
soupmagnet said:
Get a factory cable. That's all you can do...that is, without opening the device and shorting a certain pin to drop the device into usbboot so you can install a new bootloader and custom recovery, which would also put the device into fastboot mode afterwards...but I would suggest you steer clear from that option until you have no other choice.
Click to expand...
Click to collapse
I have the same problem as the OP and I'm at my wits end with this. Curiously, everything works if I flash other rom like cm 10.1 but the update zip.
Any help would be greatly appreciated.
[email protected] said:
I have the same problem as the OP and I'm at my wits end with this. Curiously, everything works if I flash other rom like cm 10.1 but the update zip.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
did u get the same error ?? are u in TWRP ??
[email protected] said:
I have the same problem as the OP and I'm at my wits end with this. Curiously, everything works if I flash other rom like cm 10.1 but the update zip.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Did you read the thread that you posted this question in? How exactly are you having the same problem as the OP if you are able to flash any ROMs at all? Did you factory reset before flashing the update.zip? What error messages are you receiving? Do you have FireFireFire installed? What version of TWRP are you using? Do you have a factory cable?
Information like this is the key toward getting the help you need.
kvnkarthik said:
did u get the same error ?? are u in TWRP ??
Click to expand...
Click to collapse
Yes the very same error on your first post, TWRP v2.6.0
---------- Post added at 11:19 PM ---------- Previous post was at 11:02 PM ----------
soupmagnet said:
Did you read the thread that you posted this question in? How exactly are you having the same problem as the OP if you are able to flash any ROMs at all? Did you factory reset before flashing the update.zip? What error messages are you receiving? Do you have FireFireFire installed? What version of TWRP are you using? Do you have a factory cable?
Information like this is the key toward getting the help you need.
Click to expand...
Click to collapse
FFF is installed, TWRP v2.6 and I'm using the cable that came with my Galaxy S3. It's the same error that I am getting as the OP when flashing the update zip. And like what Ive said it works fine if I flash other ROM(in my case cm 10.1 and AOSP 4.2) that's why it baffles me.
[email protected] said:
Yes the very same error on your first post, TWRP v2.6.0
---------- Post added at 11:19 PM ---------- Previous post was at 11:02 PM ----------
FFF is installed, TWRP v2.6 and I'm using the cable that came with my Galaxy S3. It's the same error that I am getting as the OP when flashing the update zip. And like what Ive said it works fine if I flash other ROM(in my case cm 10.1 and AOSP 4.2) that's why it baffles me.
Click to expand...
Click to collapse
As mentioned previously, that error is from not performing a factory reset when flashing a ROM. As a result, you need a factory cable to enable fastboot, and in effect, access custom recovery so a factory reset can be performed.
Ok I Fixed it, COTR did it for me. @kvnkarthik if you could find a way to replace twrp with cotr that would solve your problem in flashing update.zip. Also I used the stock rom downloaded through kfu which is already in zip file, no need to rename it. Once you're in cotr, do a pre-flash wipe then install it and you're good to go. And no, I'm not using a factory cable just the one that I used on my phone.
Good luck. Hope it helps.
Hi, everyone. Having a problem trying to flash back to the stock fire rom. I'm pretty sure I botched something up when I was trying to reset it last night, but like an idiot I didn't make a backup before I tried to reset it. Now I still have FFF 1.4 and TWRP 2.6. and I can get into fastboot, or that's what KFU will show. But when ever I try to flash update.zip I get an error saying:
Error executing update binary in the zip '/sdcard/update.zip
Error flashing zip '/sdcar/update.zip
Updating partition details....
I can still flash other roms, since I tried last night to make sure. So I'm stuck on where to go from here. Anyone have any ideas.
Make sure you wipe System, Cache, and Dalvik, before flashing..
Sent from the 404
404-Not Found said:
Make sure you wipe System, Cache, and Dalvik, before flashing..
Sent from the 404
Click to expand...
Click to collapse
Thanks for the reply. I don't have to in fast boot when doing this do I?
Kirha said:
Thanks for the reply. I don't have to in fast boot when doing this do I?
Click to expand...
Click to collapse
Those partitions should have no bearing on whether or not the updater script executes properly. You might want to check the md5 of the update.zip and make sure you don't have a corrupted download.
soupmagnet said:
Those partitions should have no bearing on whether or not the updater script executes properly. You might want to check the md5 of the update.zip and make sure you don't have a corrupted download.
Click to expand...
Click to collapse
what if I forgot to check the md5? Then now my KF is stucking at logo and can't be accessed, adb status is offline and boot status is unknow,
takieuanh said:
what if I forgot to check the md5? Then now my KF is stucking at logo and can't be accessed, adb status is offline and boot status is unknow,
Click to expand...
Click to collapse
Okay then, let's address that for a moment.
Is the Kindle Fire logo the stock (orange & white) Kindle Fire logo, or the FireFireFire (blue & white) Kindle Fire logo? If the Kindle Fire logo is stock, does it stay brightly lit upon booting, or does it flash and/or go dim at any point?
soupmagnet said:
Okay then, let's address that for a moment.
Is the Kindle Fire logo the stock (orange & white) Kindle Fire logo, or the FireFireFire (blue & white) Kindle Fire logo? If the Kindle Fire logo is stock, does it stay brightly lit upon booting, or does it flash and/or go dim at any point?
Click to expand...
Click to collapse
It's the stock logo (orange and white) and it flash some times (2 or 3) then it stays bright till out of energy.
takieuanh said:
It's the stock logo (orange and white) and it flash some times (2 or 3) then it stays bright till out of energy.
Click to expand...
Click to collapse
You need a factory cable
soupmagnet said:
You need a factory cable
Click to expand...
Click to collapse
Thanks guy. I will try
Similar but different
Kirha said:
Hi, everyone. Having a problem trying to flash back to the stock fire rom. I'm pretty sure I botched something up when I was trying to reset it last night, but like an idiot I didn't make a backup before I tried to reset it. Now I still have FFF 1.4 and TWRP 2.6. and I can get into fastboot, or that's what KFU will show. But when ever I try to flash update.zip I get an error saying:
Error executing update binary in the zip '/sdcard/update.zip
Error flashing zip '/sdcar/update.zip
Updating partition details....
I can still flash other roms, since I tried last night to make sure. So I'm stuck on where to go from here. Anyone have any ideas.
Click to expand...
Click to collapse
I'm currently running FireFireFire 1.42a, TWRP 2.6.0.0 and ROM 6.3.2_stock_04.22.13-primary.zip from tobiascuypers. It seems to be working just fine except when I try to access Amazon's Instant video. Then I get the error that: "Your device is no longer configured correctly to play Amazon videos..." I'd also like to explore just what the vanilla version of the Kindle can do before I start playing with it. So I tried following kinfaun's instructions to revert to Stock Software, but...
When I try to flash the original 6.3.2 file from Amazon, I get the following results:
Installing /sdcard/update.zip
Checking for MD5 file...
Skipping MD5 check: no MD5 file found...
assert failed: get prop("ro.product.device") == "blaze" ||
E:unknown command [err_string]
getprop("ro.build.product") == "blaze"
E:unknown command [err_string]
E:Error executing updater binary in zip '/sdcard/update.zip'
Error flashing zip '/sdcard/update.zip'
Updating partition details...
Someplace, I picked up the idea that "blaze" is the code for a newer kindle and that I'm trying to flash an image from "otter" or vice versa. I suppose it is possible since I got this thing used and bricked, but... If that's the case, how was I able to run tobiascuypers ROM??? How can I tell if the device is 1st or 2nd generation?
Thanks for any and all help.
SampleAndy said:
How can I tell if the device is 1st or 2nd generation?
Click to expand...
Click to collapse
If you have FireFireFire installed and your device isn't hard-bricked, you have a first generation KF. As far as your recovery problem, install an earlier version, or install COTR instead.
soupmagnet said:
If you have FireFireFire installed and your device isn't hard-bricked, you have a first generation KF. As far as your recovery problem, install an earlier version, or install COTR instead.
Click to expand...
Click to collapse
uhh... Thanks, but when you say an earlier version, do you mean an earlier version of FireFireFire or of TWRP?
The case is solved!
SampleAndy said:
uhh... Thanks, but when you say an earlier version, do you mean an earlier version of FireFireFire or of TWRP?
Click to expand...
Click to collapse
OK, on a video on youtube (that I can't include a link to...), I watched a guy named Tomsgt123 reset his Kindle to stock. I saw that he was running TWRP 2.2.2.1. I did a google search for it and downloaded it. I followed the instructions to replace the existing twrp.img file in KFU with the new (old) one, but couldn't catch the Kindle in the right mood to let me flash it. I finally got disgusted and got out the factory cable, and problem solved. Since I forgot to wipe... ANYthing, all my books and other stuff were still there.
Now I can fade into the background until I actually learn something about these damn things. My thanks to anybody who created some of the tools that let me fix this beast. :laugh:
If anybody else finds themselves in the same boat, let me know, and I will send you the links to the stuff I used. Since it IS the internet, I can't guarantee that the links will still be good tomorrow.
I was running 3.2.8 as of this morning but decided to go back to stock, so I:
flashed stocked recovery
installed 3.2.8
setup my phone, etc
connected to my vpn
downloaded and installed the update
phone boots to 6.0.1/OOS 3.2.8
I don't get it. Originally I had an issue with the update, it wouldn't install. SO I rebooted to (stock) recovery and wiped cache, rebooted and was able to perform the update. But when the phone rebooted it booted to OOS 3.2.8. WTF?!
Update - it does NOT say update successful, okay so that's a little better. But why the OTA is failing is unknown.
dcdevito said:
Update - it does NOT say update successful, okay so that's a little better. But why the OTA is failing is unknown.
Click to expand...
Click to collapse
Why don't you try installing the update manually?
Formhault said:
Why don't you try installing the update manually?
Click to expand...
Click to collapse
I tried side loading but I get "can't read [filename].Zip"
dcdevito said:
I tried side loading but I get "can't read [filename].Zip"
Click to expand...
Click to collapse
Download the file again. It could be a bad download.
Also, make sure you're using the stock Nougat recovery.
Formhault said:
Download the file again. It could be a bad download.
Also, make sure you're using the stock Nougat recovery.
Click to expand...
Click to collapse
I reinstalled adb drivers and I can at least get the stock recovery to attempt to sideload it, but the install fails like it does from the system updater.
Could be the stock Nougat recovery that I am not using - perhaps I am using an older version - where can I verify the download for that?
For reference this is where I got the stock recovery - https://s3.amazonaws.com/oxygenos.oneplus.net/recovery.img
(Update)
Got it to work - I get a dm-verity error on bootup, did a factory reset after the update but still get the error - but I got it. Thanks for your help, cheers
dcdevito said:
(Update)
Got it to work - I get a dm-verity error on bootup, did a factory reset after the update but still get the error - but I got it. Thanks for your help, cheers
Click to expand...
Click to collapse
How did you get it to work? Just curious.
About the dm-verity error... See this : https://forum.xda-developers.com/oneplus-3t/how-to/how-to-fix-dm-verity-issue-7-0-flashed-t3529680
Edit : whoops, it's for the 3T. Oh well...
Formhault said:
How did you get it to work? Just curious.
About the dm-verity error... See this : https://forum.xda-developers.com/oneplus-3t/how-to/how-to-fix-dm-verity-issue-7-0-flashed-t3529680
Edit : whoops, it's for the 3T. Oh well...
Click to expand...
Click to collapse
I re-downloaded the zip, I just wish I knew if the one I have was the latest version, and thus correct one.
Also, yeah I wish there was a OnePlus 3 Toolkit, not that I mind doing it all manually, I just don't have much time on weekdays to do this.....
dcdevito said:
I re-downloaded the zip, I just wish I knew if the one I have was the latest version, and thus correct one.
Click to expand...
Click to collapse
I see
dcdevito said:
Also, yeah I wish there was a OnePlus 3 Toolkit, not that I mind doing it all manually, I just don't have much time on weekdays to do this.....
Click to expand...
Click to collapse
Well, you missed this
Formhault said:
How did you get it to work? Just curious.
About the dm-verity error... See this : https://forum.xda-developers.com/oneplus-3t/how-to/how-to-fix-dm-verity-issue-7-0-flashed-t3529680
Edit : whoops, it's for the 3T. Oh well...
Click to expand...
Click to collapse
Formhault said:
I see
Well, you missed this
Click to expand...
Click to collapse
Cool, thanks - but I'm assuming this wasn't updated for Nougat, right?
dcdevito said:
Cool, thanks - but I'm assuming this wasn't updated for Nougat, right?
Click to expand...
Click to collapse
I stand correctd - looks like it TWRP and SU were indeed updated