Related
I rooted my kindle fire using kfu 9.8. As of this moment when I install roms they do not boot up and they stay at the boot logo. I dont know if it has to do with TWRP or the roms, but I have tried 2 cm10 roms and one AOSP 4.2.2 rom. I will tell you exactly what I did.
1. Rooted with kfu
2. went straight to recovery, flashed the aosp rom + google apps
3. Booted up and it stayed at the boot screen
4. Tried another rom, put it onto the device through usb mounting with twrp
5. Still stuck at boot logo
6. Tried the last rom but still stuck!!
After that I tried to flash back to stock using this
(doesnt let me post a link if requested I will pm)
But twrp gave an error and it did not install, it said somewhere an error doesnt matter and you would boot up fine but I didnt
Between installing all Roms I wiped cache, dalvik, and factory reset.
Thanks in advnce!
EDIT
Used this to try to bring to stock
theunlockr DOT com/2012/10/29/how-to-unroot-the-amazon-kindle-fire
Used these roms (all on xda)
/showthread.php?t=2100963
/showthread.php?t=2041694
cant find the third rom
EDIT
I have no problem using adb or fastboot so feel free to try and fix my problem with those.
Ilia Goro said:
But twrp gave an error and it did not install it said somewhere an error doesnt matter and you would boot up fine but I didn't
Click to expand...
Click to collapse
It would be very helpful to know exactly what error you are receiving.
soupmagnet said:
It would be very helpful to know exactly what error you are receiving.
Click to expand...
Click to collapse
assert failed:getprop ("ro.product.device") == "blaze" l l
E:unknown command {err_string}
getprop ("ro.product.device") == "blaze"
E:unknown command {err_string}
E:Error in sdcard/update.zip
Status 7
Error flashing zip /sdcard/update.zip
Updating partition details
That is exactly what I get while flashing
Im sorry for making the topic and/or wasting your time, before installing the rom I wiped every single thing possible and it succesfully nstalled.
I have no problem if you lock.
Ilia Goro said:
assert failed:getprop ("ro.product.device") == "blaze" l l
E:unknown command {err_string}
getprop ("ro.product.device") == "blaze"
E:unknown command {err_string}
E:Error in sdcard/update.zip
Status 7
Error flashing zip /sdcard/update.zip
Updating partition details
That is exactly what I get while flashing
Im sorry for making the topic and/or wasting your time, before installing the rom I wiped every single thing possible and it succesfully nstalled.
I have no problem if you lock.
Click to expand...
Click to collapse
Any update on this? I'm getting the same issue on mine.
Runaround said:
Any update on this? I'm getting the same issue on mine.
Click to expand...
Click to collapse
I had the same issue using TWRP 2.4.x.x. I was able to return to stock by downgrading to TWRP 2.2.2.1. Good luck.
Sent from my Nexus 7 using xda app-developers app
philipsw said:
I had the same issue using TWRP 2.4.x.x. I was able to return to stock by downgrading to TWRP 2.2.2.1. Good luck.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
By any chance, can you please give me the link to the TWRP 2.2.2.1?
TIA.
votinh said:
By any chance, can you please give me the link to the TWRP 2.2.2.1?
TIA.
Click to expand...
Click to collapse
http://www.teamw.in/project/twrp2/79
Sent from my Nexus 7 using xda app-developers app
philipsw said:
http://www.teamw.in/project/twrp2/79
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks philipsw, I found the 2.2.2.1 flashable zip file too.
2.2.2.1 zip?
votinh said:
Thanks philipsw, I found the 2.2.2.1 flashable zip file too.
Click to expand...
Click to collapse
where did you find the zip file?
TWRP
You need TWRP 2.6.3.1 too install KitKat Roms here is the link for your first gen fires you need the otter.img
TWRP
PLEASE HELP! Kindle Fire 1st Gen. I've looked everywhere for answers
Okay, This is the first time Ive ever posted anything on this site. Normally I just search for answers and people usually have already solved the problem so I just go off what other people post. But now I cannot seem to find any fix I rooted my Kindle Fire 1st Generation. I was running TWRP 2.2.2. and a Hellfire ROM. I went on vacation and left my Kindle at home. When I got back, most of my apps weren't working properly and my keyboard was glitching so I tried to update my ROM. It was unsuccessful. So I thought maybe if I upgraded my TWRP Recovery to the latest version It would fix the problem... I was wrong. Whenever I try to flash any ROM I get an error like this... (E:Error executing updater binary) I have searched for answers for about a month now and nothing seems to work. I dont know what to do and I feel like crying. Can someone please help me? Please?
Feedback
DroidLover93 said:
Okay, This is the first time Ive ever posted anything on this site. Normally I just search for answers and people usually have already solved the problem so I just go off what other people post. But now I cannot seem to find any fix I rooted my Kindle Fire 1st Generation. I was running TWRP 2.2.2. and a Hellfire ROM. I went on vacation and left my Kindle at home. When I got back, most of my apps weren't working properly and my keyboard was glitching so I tried to update my ROM. It was unsuccessful. So I thought maybe if I upgraded my TWRP Recovery to the latest version It would fix the problem... I was wrong. Whenever I try to flash any ROM I get an error like this... (E:Error executing updater binary) I have searched for answers for about a month now and nothing seems to work. I dont know what to do and I feel like crying. Can someone please help me? Please?
Click to expand...
Click to collapse
Just need a little more info... What TWRP version are you running?? What android version are you trying to flash??
lj50036 said:
Just need a little more info... What TWRP version are you running?? What android version are you trying to flash??
Click to expand...
Click to collapse
I'm currently running TWRP v2.6.0.0
And I'm trying to flash ANY android version.
So far I have tried flashing the latest HellFire, Kit Kat, and Jellybean Stock Roms, All have been unsuccessful.
All I want is to be able to use my kindle without wanting to smash it to pieces, lol. I'm tired of getting booted off the internet every 2 minutes and my apps to force closing on me.
DroidLover93 said:
I'm currently running TWRP v2.6.0.0
And I'm trying to flash ANY android version.
So far I have tried flashing the latest HellFire, Kit Kat, and Jellybean Stock Roms, All have been unsuccessful.
All I want is to be able to use my kindle without wanting to smash it to pieces, lol. I'm tired of getting booted off the internet every 2 minutes and my apps to force closing on me.
Click to expand...
Click to collapse
And you are using the firefirefire utility??
lj50036 said:
And you are using the firefirefire utility??
Click to expand...
Click to collapse
Yes, I believe so.
TWRP
DroidLover93 said:
Yes, I believe so.
Click to expand...
Click to collapse
We need to get you on the latest version of twrp....http://techerrata.com/browse/twrp2/blaze
Go here and get version 2.6.3.1 make sure your get the otter.img as the blaze is for the 2nd gen fire....
Let me know if you need any help with this.. Let me know when you have it installed....Thx lj
---------- Post added at 10:51 PM ---------- Previous post was at 10:46 PM ----------
Do you have fastboot and adb drivers for your PC?? Do you have fastboot.exe and adb.exe... I assume your running windows....
@lj50036
Do you have fastboot and adb drivers for your PC?? Do you have fastboot.exe and adb.exe... I assume your running windows...
Thank you! I will do this now and I will let you know when I have it installed. Do I just flash it through recovery or?...
Also, I do not have fastboot and adb drivers on my PC. Where do I go to get them? Running Windows 7
Feedback
DroidLover93 said:
@lj50036
Do you have fastboot and adb drivers for your PC?? Do you have fastboot.exe and adb.exe... I assume your running windows...
Thank you! I will do this now and I will let you know when I have it installed. Do I just flash it through recovery or?...
Also, I do not have fastboot and adb drivers on my PC. Where do I go to get them? Running Windows 7
Click to expand...
Click to collapse
Check this forum for your fastboot adb driver needs...http://forum.xda-developers.com/showthread.php?t=2588979
Hold on a sec I will make you a flashable recovery zip for easy of installation...
TWRP 2.6.3.1
Here is a flashable zip twrp recovery v 2.6.3.1... Just flash it than do a reboot before trying to enter recovery... Let me know if that fastboot/adb stuff is working for you we will still need adb drivers and adb installed on your PC...Thx lj
View attachment 2578399
lj50036 said:
Here is a flashable zip twrp recovery v 2.6.3.1... Just flash it than do a reboot before trying to enter recovery... Let me know if that fastboot/adb stuff is working for you we will still need adb drivers and adb installed on your PC...Thx lj
View attachment 2578399
Click to expand...
Click to collapse
Thanks! Okay so TWRP update was successful. Then I followed the link for ADB and fastboot. I installed them to PC. Now, just to be clear.. Was I supposed to do that with the USB connected to my device? or was that just for my PC? I just dont want to mess anything up.
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.
[This thread has been created
for
Questions & Answers/Troubleshooting
Specific to
Kindle Fire Flashable Recoveries TWRP/COTR/CWM[2014]
Click link here>> (http://forum.xda-developers.com/kin...indle-fire-flashable-recoveries-twrp-t2811253) <<Click link here
Please feel free to share issues, questions and offer help
It is always best to thank a ROM OP, in lieu of simply posting "Thank you".
Please keep discussion focused, on the topic described in the OP
Ok, I have one doozy of a problem.
It started off when I tried to reflash my kindle back to stock. That failed, and in the process of trying to fix it I wiped the bootloader, recovery, and ROM. (don't ask how, it's a long story)
I got a hold of a factory cable, got into fastboot, and was able to get the kindle fire utility to install FFF and TWRP 2.7.0.1. I tried installing the stock rom and kept getting an error including the line:
Code:
assert failed: getprop ("ro.product.device") == "blaze" ||
Saw this was because TWRP is apparently an "otter" build and the stock rom is a "blaze" build. (I am totally not sure what these are referring to.)
So I tried installing the blaze version of TWRP. I didn't get the error, but instead, as soon as I go to install the ROM it crashes TWRP and brings it back to the teamwin loading screen and then back to the home screen. I cannot get past this part. I've tried multiple ROMS, I've tried downgrading to twrp 2.2.2.1, I've tried otter builds and blaze builds on twrp and the ROMS. when the blaze/otter matches, it crashes, when it doesnt' match I get the assert failed error.
HELP!
asrrin29 said:
Ok, I have one doozy of a problem.
It started off when I tried to reflash my kindle back to stock. That failed, and in the process of trying to fix it I wiped the bootloader, recovery, and ROM. (don't ask how, it's a long story)
I got a hold of a factory cable, got into fastboot, and was able to get the kindle fire utility to install FFF and TWRP 2.7.0.1. I tried installing the stock rom and kept getting an error including the line:
Code:
assert failed: getprop ("ro.product.device") == "blaze" ||
Saw this was because TWRP is apparently an "otter" build and the stock rom is a "blaze" build. (I am totally not sure what these are referring to.)
So I tried installing the blaze version of TWRP. I didn't get the error, but instead, as soon as I go to install the ROM it crashes TWRP and brings it back to the teamwin loading screen and then back to the home screen. I cannot get past this part. I've tried multiple ROMS, I've tried downgrading to twrp 2.2.2.1, I've tried otter builds and blaze builds on twrp and the ROMS. when the blaze/otter matches, it crashes, when it doesnt' match I get the assert failed error.
HELP!
Click to expand...
Click to collapse
just use my [2014][Pre-Rooted][Stock]System Version 6.3.3-Original Kindle Fire Only
another option is use COTR recovery.zip
sd_shadow said:
just use my [2014][Pre-Rooted][Stock]System Version 6.3.3-Original Kindle Fire Only
Click to expand...
Click to collapse
Small addendum, the TWRP version I used was 2.6.3.1. Let me know if there is an updated TWRP to use, but I pulled this using Kindle Fire Utility.
I grabbed your ROM, and did a Dalvik Cache wipe and factory reset, and the ROM installs without crashing TWRP! however, when I try to boot into the ROM it crashes and goes back into recovery.
---------- Post added at 11:08 PM ---------- Previous post was at 11:04 PM ----------
sd_shadow said:
another option is use COTR recovery.zip
Click to expand...
Click to collapse
I tried using COTR and got the same issue with successfully getting the ROM installed but being unable to boot into it.
asrrin29 said:
Small addendum, the TWRP version I used was 2.6.3.1. Let me know if there is an updated TWRP to use, but I pulled this using Kindle Fire Utility.
I grabbed your ROM, and did a Dalvik Cache wipe and factory reset, and the ROM installs without crashing TWRP! however, when I try to boot into the ROM it crashes and goes back into recovery.
---------- Post added at 11:08 PM ---------- Previous post was at 11:04 PM ----------
I tried using COTR and got the same issue with successfully getting the ROM installed but being unable to boot into it.
Click to expand...
Click to collapse
which bootloader is installed 1.4, 1.4a, 1.5?
sd_shadow said:
which bootloader is installed 1.4, 1.4a, 1.5?
Click to expand...
Click to collapse
1.4a
asrrin29 said:
1.4a
Click to expand...
Click to collapse
try fff-u-boot_v1.5.zip
sd_shadow said:
try fff-u-boot_v1.5.zip
Click to expand...
Click to collapse
Kindle Fire Utility is not letting me flash the updated bootloader. I'm looking right now for the manual adb push commands to do it manually.
Update: just tried flashing FFF1.5 through TWRP, said it was successful, rebooted and it's still at 1.4a.
Update 2: Just for giggles, I tried flasshing FFF1.5 again via TWRP, and it too is now causing TWRP to crash when trying to install it. Same thing is happening with the stock ROM 6.3.3 you linked me, even after I did a reboot and factory wipe and dalvik cache wipe.
asrrin29 said:
Kindle Fire Utility is not letting me flash the updated bootloader. I'm looking right now for the manual adb push commands to do it manually.
Update: just tried flashing FFF1.5 through TWRP, said it was successful, rebooted and it's still at 1.4a.
Click to expand...
Click to collapse
download fff-u-boot_v1.5.bin
verify md5 checksumMD5: 0fad8ea0b1f211e9d3701d8228327cbe https://sites.google.com/site/sdshadowscollection/home/hash-checksums
Kindle In bootloader
on PC in command prompt
Code:
fastboot devices
should see something like
Code:
123456789 fastboot
if yes
Code:
fastboot flash bootloader fff-u-boot_v1.5.bin
then
Code:
fastboot reboot
Verified md5 checksum.
Code:
C:\KindleFire\tools>fastboot devices
0123456789ABCDEF fastboot
C:\KindleFire\tools>fastboot flash bootloader fff-u-boot_v1.5.bin
sending 'bootloader' (243 KB)...
OKAY [ 0.078s]
writing 'bootloader'...
OKAY [ 0.047s]
finished. total time: 0.125s
C:\KindleFire\tools>fastboot reboot
rebooting...
finished. total time: 0.009s
C:\KindleFire\tools>
Reboots into bootloader and it still says 1.4a
download FIREFIREFIRE 1.3
unzip
verify md5:928ae401d91963e1cb8f4dae6ca9519b for u-boot.bin
Code:
fastboot flash bootloader u-boot.bin
sd_shadow said:
download FIREFIREFIRE 1.3
unzip
verify md5:928ae401d91963e1cb8f4dae6ca9519b for u-boot.bin
Code:
fastboot flash bootloader u-boot.bin
Click to expand...
Click to collapse
I'm now at a bootloader screen with the green android alien, and the orange kindle fire logo. Should I try to flash 1.5 from here?
asrrin29 said:
I'm now at a bootloader screen with the green android alien, and the orange kindle fire logo. Should I try to flash 1.5 from here?
Click to expand...
Click to collapse
Yes that should be fine.
sd_shadow said:
Yes that should be fine.
Click to expand...
Click to collapse
aaand it's back to 1.4a. I verified I used the fff-u-boot_v1.5.bin file you linked me.
asrrin29 said:
aaand it's back to 1.4a. I verified I used the fff-u-boot_v1.5.bin file you linked me.
Click to expand...
Click to collapse
think that is fine, hashcode may not have changed the name right.
try reflashing twrp
download 2.2.2.1.twrp.img
verify md5:e6183f4c6043f2c6a0d519d9f660ee98
Code:
fastboot flash recovery twrp-2.2.2.1-blaze.img
actually FFF 1.3 and TWRP 2.2.2.1 are fine for stock
sd_shadow said:
think that is fine, hashcode may not have changed the name right.
try reflashing twrp
Click to expand...
Click to collapse
Went to http://www.teamw.in/project/twrp2/79 and downloaded TWRP 2.7.1.0 Otter. Verified md5sum. Successfully flashed it. Factory reset and tried to install your 6.3.3 ROM, and again TWRP crashed and brought me back to the home screen.
If fff 1.3 and twrp 2.2.2.1 won't work could be a partition error
Sent from my DROIDX using Tapatalk
I have the WiFi version of the Nexus 7 (2013). It is on KTU84P (Android 4.4.4). Bootloader is unlocked, TWRP 2.7.1.1 is installed for recovery and it is rooted.
I downloaded the OTA zip and have tried to install it in 2 different ways:
In TWRP, going to Advanced->ADB Sideload. Then from the connected PC, running "adb sideload <downloaded zip file>"
From TWRP on the device, going to Install, and selecting the downloaded zip.
In both cases, I get the same error:
Package expects build fingerprint of google/razor/flo:4.4.4/KTU84P/1227136:user/release-keys or google/razor/flo:5.0/LRX21P/1570855:user/release-keys; this device has google/razor/flo:4.3/JSS15Q/779366:user/release-keys.
Click to expand...
Click to collapse
I'm not real sure what that error means, or how to go about addressing it. Any suggestions?
Thanks
You can't flash the OTA in TWRP, at least I don't think so, but I do know that 5.0 requires the latest version of TWRP, think it's 2.8.1.0
Sent from my 2013 Nexus 7
"Until death, I will remain a Dirty Unicorn.."
Tried updating to TWRP 2.8.1.0, I couldn't even get adb to recognize the tablet when in sideload. Just gave me device not found.
But, based on your other comment, I grabbed Wug's Nexus Root Toolkit and reflashed the stock recovery. Sideload is now in progress, I think I'm good to go (I probably just jinxed it!)
Thanks a lot for the help. I had thought it would just replace the recovery - I didn't realize that actually prevented it from running.
Update TWRP in bootloader. Fasboot flash recovery recovery.img
cabadam said:
I have the WiFi version of the Nexus 7 (2013). It is on KTU84P (Android 4.4.4). Bootloader is unlocked, TWRP 2.7.1.1 is installed for recovery and it is rooted.
I downloaded the OTA zip and have tried to install it in 2 different ways:
In TWRP, going to Advanced->ADB Sideload. Then from the connected PC, running "adb sideload <downloaded zip file>"
From TWRP on the device, going to Install, and selecting the downloaded zip.
In both cases, I get the same error:
I'm not real sure what that error means, or how to go about addressing it. Any suggestions?
Thanks
Click to expand...
Click to collapse
The error message is simply saying that the file you are trying to flash is to update from 4.4.4 to 5.0. But your device is at 4.3, and so, you cannot flash this file.
You will need to first upgrade to 4.4.4 and then flash from 4.4.4 to 5.0
jj14 said:
The error message is simply saying that the file you are trying to flash is to update from 4.4.4 to 5.0. But your device is at 4.3, and so, you cannot flash this file.
You will need to first upgrade to 4.4.4 and then flash from 4.4.4 to 5.0
Click to expand...
Click to collapse
No, it was at 4.4.4. For some reason it just didn't like TWRP. When I went back to stock recovery, it sideloaded just fine. I'm up and running now on 5.0.
cabadam said:
No, it was at 4.4.4. For some reason it just didn't like TWRP. When I went back to stock recovery, it sideloaded just fine. I'm up and running now on 5.0.
Click to expand...
Click to collapse
Weird - did you modify your build.prop for any reason?
jj14 said:
Weird - did you modify your build.prop for any reason?
Click to expand...
Click to collapse
Nope. When I got the tablet, I rooted it, flashed TWRP, but didn't modify anything else. And basically the root was just so I could do full backups.
I tried twrp amd cwm and both wont work. Twrp shows jelly bean and cwm shows previous version of kitkat. Both are not showing ktu84p
Build fingerprint error when flashing 5.0 OTA via stock recovery
ImjuzCY said:
I tried twrp amd cwm and both wont work. Twrp shows jelly bean and cwm shows previous version of kitkat. Both are not showing ktu84p
Click to expand...
Click to collapse
Hello!
Really want to flash the OTA without a total wipe.
First flashed it from TWRP 2.8.1.0 and got the wrong build finger print says I have Flo:4.3/JSS15Q/779366 and it expects KTU84P/1227136
Then using WugFresh 1.9.4 flashed stock recovery so I could sideload then encountered the whole adb disappearing in recovery - eventually solved that and finally managed to adb sideload saw my screen saying it was installing the update using the stock recovery - YAY! It was short lived as the stock recovery screen told me the exact same thing that TWRP had told me.
I looked at my build.prop and it says my ro.build.fingerprint=google/razor/flo:4.4.4/KTU84P/1227136. user/release-keys
Can someone enlighten me? I've wasted so much time on this I would love some keen insight - PLEASE!!
Thanks for any and all help!
Edbogue
Same problem
Hey guys!
I have the exact same problem as OP.
tried installing the zip using the latest version of TWRP and got the same error as OP.
I reverted back to stock recovery and tried to install the OTA update and I got a similar error (image attached).
I'm stuck, could someone help?
Rooted Nexus 7 2013 running 4.4.4 with TWRP 2.8.1.0
Same here. Build.prop has the desired release keys but cwm is giving me the exact same error. Anyone have any suggestions?
open the zip file,
edit META-INF/com/google/android/updater-script
just comment the following three lines:
#getprop("ro.build.fingerprint") == "google/razor/flo:4.4.4/KTU84P/1227136:user/release-keys" ||
# getprop("ro.build.fingerprint") == "google/razor/flo:5.0/LRX21P/1570855:user/release-keys" ||
# abort("Package expects build fingerprint of google/razor/flo:4.4.4/KTU84P/1227136:user/release-keys or google/razor/flo:5.0/LRX21P/1570855:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
then the update will go through.
you will take this workaround at your own risk.
make sure the version is 4.4.4/KTU84P already.
You need to be in kk stock with all apps from Google. !
I used NRT with sideload and no problem to flash 5.0 !
ahmao said:
open the zip file,
edit META-INF/com/google/android/updater-script
just comment the following three lines:
#getprop("ro.build.fingerprint") == "google/razor/flo:4.4.4/KTU84P/1227136:user/release-keys" ||
# getprop("ro.build.fingerprint") == "google/razor/flo:5.0/LRX21P/1570855:user/release-keys" ||
# abort("Package expects build fingerprint of google/razor/flo:4.4.4/KTU84P/1227136:user/release-keys or google/razor/flo:5.0/LRX21P/1570855:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
then the update will go through.
you will take this workaround at your own risk.
make sure the version is 4.4.4/KTU84P already.
Click to expand...
Click to collapse
ahmao, when you say comment you mean this
Code:
/*comment goes here*/
as they do with CSS?
open the zip file,
edit META-INF/com/google/android/updater-script
just comment the following three lines:
#getprop("ro.build.fingerprint") == "google/razor/flo:4.4.4/KTU84P/1227136:user/release-keys" ||
# getprop("ro.build.fingerprint") == "google/razor/flo:5.0/LRX21P/1570855:user/release-keys" ||
# abort("Package expects build fingerprint of google/razor/flo:4.4.4/KTU84P/1227136:user/release-keys or google/razor/flo:5.0/LRX21P/1570855:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
then the update will go through.
you will take this workaround at your own risk.
make sure the version is 4.4.4/KTU84P already.
Click to expand...
Click to collapse
As suggested, I tried that. Commented out the lines. Now when trying to flash it just says "Installing Update" then "Installation Aborted" gives no further details. Thanks for the suggestion though.
I had same problems on n4.
I tried flashing stock recovery. Doesn't work. So, I flashed the whole stock 4.4.4 rom, and then apply the Ota. And it worked.
But I had to wipe my user data. (maybe not necessary)
Envoyé de ma Nexus 7.2 depuis tapatalk
I finally waved the white flag and used WugFresh's toolkit 1.9.8. Cool thing though. I was planning on using it to restore to stock 4.4.4. When chose the option to Flash Stock it actually downloaded and flashed the lollipop factory image instead of the latest kitkat. Did wipe data as expected with a factory image but still saved a step. Even though the bootloader was updated, it remained unlocked so I was able to immediately root. I am normally not a fan of toolkits and am more inclined to do things myself (with lots of help from forums of course) for educational purposes but I spent 2 days working on it the other way and got it done this way in under an hour.
comment means add a hash "#" in front of the script line.
if further check fails, just find the line and comment out the app_check line.
bwat1009 said:
I finally waved the white flag and used WugFresh's toolkit 1.9.8. Cool thing though. I was planning on using it to restore to stock 4.4.4. When chose the option to Flash Stock it actually downloaded and flashed the lollipop factory image instead of the latest kitkat. Did wipe data as expected with a factory image but still saved a step. Even though the bootloader was updated, it remained unlocked so I was able to immediately root. I am normally not a fan of toolkits and am more inclined to do things myself (with lots of help from forums of course) for educational purposes but I spent 2 days working on it the other way and got it done this way in under an hour.
Click to expand...
Click to collapse
Thanks man!
That worked perfectly!
I lost all my data (which is fine) plus I really needed to start from scratch at some point.
I'm trying to install TWRP custom recovery, but it seems to be crashing all the time.
Does TWRP support Android 5.0 yet?