Database Users

How badly have I messed up? (Apparently not a much as I thought)

Ok. So I'm an idiot. I just got my kindle fire today and I was using the Kindle Fire Utility v7. I went to install TWRP and then I accidently closed the window, I went to install it again, but it had partially downloaded TWRP (667 bytes or something) and instead of downloading it again it started installing it.
I am now stuck at a yellow triangle logo with "press power button for recovery" and ADB doesn't recognise it.
Can it be fixed or am I ****ed?

You need to put more obscenities in the title of your post most people only respond if you have 2 obscenities in the post title.

Does windows recognize it?
If so, does your computer make three sounds when you connect the kindle?
Sent from my Kindle Fire using Tapatalk

asb2164 said:
You need to put more obscenities in the title of your post most people only respond if you have 2 obscenities in the post title.
Click to expand...
Click to collapse
Sorry, I'm just really annoyed at myself.
theholyfork said:
Does windows recognize it?
If so, does your computer make three sounds when you connect the kindle?
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
My computer recognises it but it's not installing drivers for it. The drivers were installed otherwise Kindle Fire Utility wouldn't work. Looking through the device info, its has the ID 0x18D1 which is one of the IDs I added to adb_usb.ini

theholyfork said:
Does windows recognize it?
If so, does your computer make three sounds when you connect the kindle?
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Thank you for making me double check. android_winusb.inf did not have the device id for 18D1 so I changed it and I'm hopefully reinstalling the recovery now.

Might be a bit more pleasant if you change the title of your topic. You can edit it you know...

North101 said:
Thank you for making me double check. android_winusb.inf did not have the device id for 18D1 so I changed it and I'm hopefully reinstalling the recovery now.
Click to expand...
Click to collapse
Haha no problem. If that doesn't work I know of another method you can try, I had an issue like that where I couldn't get out of the yellow triangle screen. Took me forever to find a fix, but, obviously I found one.
Sent from my Kindle Fire using Tapatalk

krelvinaz said:
Might be a bit more pleasant if you change the title of your topic. You can edit it you know...
Click to expand...
Click to collapse
Sorry, I missed the advanced option for editing. Done.
theholyfork said:
Haha no problem. If that doesn't work I know of another method you can try, I had an issue like that where I couldn't get out of the yellow triangle screen. Took me forever to find a fix, but, obviously I found one.
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Its fixed. Thanks for the help. I was just really panicking cause I wouldn't be able to afford to replace it.

North101 said:
Sorry, I missed the advanced option for editing. Done.
Its fixed. Thanks for the help. I was just really panicking cause I wouldn't be able to afford to replace it.
Click to expand...
Click to collapse
No problem, glad I was able to!
Sent from my Kindle Fire using Tapatalk

I have the same yellow triangle appear for 15-20 seconds everytime I boot. Is this normal for twrp? Or did I screw up? It boots normal after the 15 second wait period.

moonraider113 said:
I have the same yellow triangle appear for 15-20 seconds everytime I boot. Is this normal for twrp? Or did I screw up? It boots normal after the 15 second wait period.
Click to expand...
Click to collapse
I believe that's normal, since I have the same issue.

michaelkourlas said:
I believe that's normal, since I have the same issue.
Click to expand...
Click to collapse
It is normal....this is the time when you would press the power button to boot into recovery....if nothing is pressed it boots into the ROM.

Disclaimer: I'm really new with all this, so try to go easy on me
Yesterday night, after rooting with the of utility, I ended up stuck in fastboot for a few hours. I finally figured out how to get the Pc to recognize the kindle so I could manually reinstall the drivers, and I used the utility to get it to boot in normal mode.
My questions are:
1) I believe I am rooted but I'm not positive. I downloaded a root only app off amazon, some cache clearer. When I ran the app it asked for SU permissions. But the of utility says I haven no and root.
2) I take it that I didn't properly install.twrp after rooting last night, as that's how I ended up stuck in fastboot. When I power the kindle off and back on, I'm taken to the screen with.the fire logo and "press power for recovery" when I press power it doesn't do anything, and after 10 seconds or so, it boots up normally.
So my question is, how can I reinstall twrp properly? I really don't feel like.being stuck in fastboot again, though
Thanks!

You have to hold power until the light turns orange.

Endless TWRP boot prevention

Every time I install a new zip, I have to reset the IDME boot to 4000 before I can use the device again in Android. What can I do to prevent this?

I've heard that one way to prevent this (not sure if this is your problem or not) is to only boot to TWRP from firefirefire. IE, if you are running CM7, don't select reboot to recovery, or something like that.
The reason being, there is a bug in TWRP which causes it to not reset the bootmode when you select reboot.
I have always done it this way (saw someone mention it in a post) and have never had the problems of TWRP endless reboots that I keep seeing...

podspi said:
I've heard that one way to prevent this (not sure if this is your problem or not) is to only boot to TWRP from firefirefire. IE, if you are running CM7, don't select reboot to recovery, or something like that.
The reason being, there is a bug in TWRP which causes it to not reset the bootmode when you select reboot.
I have always done it this way (saw someone mention it in a post) and have never had the problems of TWRP endless reboots that I keep seeing...
Click to expand...
Click to collapse
For my one information, what is "firefirefire"? Is that pushing the on button several times to get the TWRP to come up?

ontwowheels said:
For my one information, what is "firefirefire"? Is that pushing the on button several times to get the TWRP to come up?
Click to expand...
Click to collapse
Yes, firefirefire is the yellow triangle.
To clarify the answer to to OP. Always turn POWER OFF before installing a new rom. Don't reboot into TWRP and you won't get stuck in the boot loop.

furtom said:
Yes, firefirefire is the yellow triangle.
To clarify the answer to to OP. Always turn POWER OFF before installing a new rom. Don't reboot into TWRP and you won't get stuck in the boot loop.
Click to expand...
Click to collapse
Thanks....I currently have this and TWRP installed via the KFUtility.

Can also verify I have avoided this by always powering down and not rebooting into recovery. At least with the 4 zips I have flashed.

install clockworkmod touch recovery
twrp never fixed the reboot option.
Sent from my HTC Glacier using xda premium

Fix TWRP boot loop
Turn off Kindle. Plug Kindle into computer. Load fire utility. Choose option 5 for TWRP install, but don't hit enter yet. Turn on Kindle. Once yellow triangle appears, hit enter on keyboard to install TWRP, let it power cycle one or two times. This fixes boot loop.

citizenandroid said:
Turn off Kindle. Plug Kindle into computer. Load fire utility. Choose option 5 for TWRP install, but don't hit enter yet. Turn on Kindle. Once yellow triangle appears, hit enter on keyboard to install TWRP, let it power cycle one or two times. This fixes boot loop.
Click to expand...
Click to collapse
Thank you for this! I've been looking through the forums trying to find something that would work. ADB won't launch for me, something I need to look into, but this worked. Thank! :]

[Q] Stuck cant restrore kindle only have clockwork recovrery device cant be found.

I rooted my kindle fire installed clockwork recovery and install this rom http://forum.xda-developers.com/showthread.php?t=1528024
I am trying to restore it to factory or any other rom. I cant get it to boot into recovery mode using kindle fire utility or kindle unbrick utility they both wont detect the kindle at any point of booting.
What cant I do to restore my kindle to stock?
Thank you for your help I am so stuck right now.

PanicFusion said:
I rooted my kindle fire installed clockwork recovery and install this rom http://forum.xda-developers.com/showthread.php?t=1528024
I am trying to restore it to factory or any other rom. I cant get it to boot into recovery mode using kindle fire utility or kindle unbrick utility they both wont detect the kindle at any point of booting.
What cant I do to restore my kindle to stock?
Thank you for your help I am so stuck right now.
Click to expand...
Click to collapse
You can't turn it off then turn it back on and hold the power button till it turns amber
Sent from my LG G2x using Tapatalk 2

I can it still doesnt detect the device when I run the utilities.

PanicFusion said:
I can it still doesnt detect the device when I run the utilities.
Click to expand...
Click to collapse
if you have cwm installed you dont need the utilities
---------- Post added at 11:16 PM ---------- Previous post was at 11:14 PM ----------
can you boot into cwm?

I tried to hold the power button after powering on but it just turns off never changes color. How long would I need to hold it for? It never turns amber.

PanicFusion said:
I tried to hold the power button after powering on but it just turns off never changes color. How long would I need to hold it for? It never turns amber.
Click to expand...
Click to collapse
when you turn it on do you see the triangle or android dude with kindle fire under him

I dont see it

PanicFusion said:
I dont see it
Click to expand...
Click to collapse
Sounds like you dont have bootloader or cwm installed. you had it before and flashed that rom? did you try and delete it?

All I did was flash the rom and wipe factory settings and few others. If I dont have either is there anyway to restore or am I stuck?

PanicFusion said:
All I did was flash the rom and wipe factory settings and few others. If I dont have either is there anyway to restore or am I stuck?
Click to expand...
Click to collapse
theres always a way .. can you still boot into the rom

i can boot into the rom and browse the google play store and everything yes

PanicFusion said:
i can boot into the rom and browse the google play store and everything yes
Click to expand...
Click to collapse
awesome then you can deff fix it... hold on a min i gotta get some files together

Thank you very much

Sorry been awile since i had to use kfu, try reinstalling the drivers go into device manager and delete the old drivers and then reinstall them
Basicly you have to reflash firefirefire and reflash cwm some times you have to reinstall the drivers for kfu to recognize the kindle again

I deleted the the usb drive for kindle and ran the usb drive that was with kindle fire utility and it still wont detect it

PanicFusion said:
I deleted the the usb drive for kindle and ran the usb drive that was with kindle fire utility and it still wont detect it
Click to expand...
Click to collapse
when you plug in your kindle in device manager uninstall adb composite device driver
EDIT on your kindle in setting under development is usb debugging enabled

Installed firefirefire and installed TWRP I got the stock version of kindle software what do I need to do to prep for install? Thank you so much for your help.

PanicFusion said:
Installed firefirefire and installed TWRP I got the stock version of kindle software what do I need to do to prep for install? Thank you so much for your help.
Click to expand...
Click to collapse
boot into twrp but holding the power button, factory reset,wipe cache,wipe davlik cache, then flash the zip
is it factory zip from amazon? if so it will delete fff twrp and root

I've proven myself an expert at bricking a Kindle Fire

installed MIUI on my KF using TWRP a few days back. went well, played around with it, then decided to go back to stock.
Wiped caches and flashed update.zip (stock rom for KF) and all appeared to have gone well..... BUT..... the battery was/is apparently too low for the device to charge (but wait, it gets better)...
when the device fires up I get the white/orange kf logo animation, then when boots I see the homescreen (without the notification/toolbar at top (just bookshelves,standard icons and bottom row of icons).... as soon as that appears I get forceclose messages for
-android.process.acore
-process.android.providers.calendar
(happens right after the UI starts loading ... if Im quick enough I can get one of the homescreen apps to load, but the device (after just a couple of seconds) just goes back to the white/orange logo animation and starts the boot process all over... whether I click force close or not it just restarts the nasty process).
in the brief time Im able to have it on I cant get the kindle fire utility to recognize it so I can get TWRP back on the device to try to re-flash stock.
probably just a paper weight now Im guessing, so I'll either take over my wifes KF or get a new one, but thought I'd mention my experience here to see if anyone has seen/heard of this before and as a warning to other noobs who know just enough to be dangerous like me!
Thanks all.

Have you tried charging it? Just plug it in with the stock charger and let it sit overnight. Then try the re-flash.

Let it charge, then just flash a new rom.

left plugged in with AC charger all night... the force closes just happen over and over and because it doesnt fully boot (Im guessing) I cant get to point where I can use kf utility to get twrp back on to handle boot. i think trying to flash with such a low battery made the flash go horribly wrong and thats the cause of the force closes??? I wish it had hardware buttons like my galaxy s!

Your device is not bricked alright?
Now that the device is fully charged, just go to KFU, on the option 1 (bootmode), choose recovery (5001).
Then turn off the device completely holding the power button for 15 secs or more.
Then plug it to USB and let the KFU set your device to recovery.
Then it will restart and go directly to TWRP

The fact that it boots at all goes to show you didn't brick it.
A few months ago I couldn't get passed the splash screen.

vbdss said:
Your device is not bricked alright?
Now that the device is fully charged, just go to KFU, on the option 1 (bootmode), choose recovery (5001).
Then turn off the device completely holding the power button for 15 secs or more.
Then plug it to USB and let the KFU set your device to recovery.
Then it will restart and go directly to TWRP
Click to expand...
Click to collapse
Thanks... KFU doesnt recognize the device at all during the 'boot loop-like' process it runs through before the 2 force closes and the eventual automatic reboot..... I followed your steps and it just kept showing waiting for device and the KF goes through the boot > force close > restart process.... its like ground hog day.
Thanks though, I appreciate the response/help.

shobon said:
The fact that it boots at all goes to show you didn't brick it.
A few months ago I couldn't get passed the splash screen.
Click to expand...
Click to collapse
Yeah, I see your point... but the force closes and the fact that it never shows the menus / top notification bar and icons, etc. and that seemingly, the KF os never loads fully keeps me from getting to a point where the windows drivers recognize the device and then allows me to get KFU to work with the device.
sort of stuck but not technically a brick I guess.

There is no such thing like KF never loads fully.
Or it loads or not. FCs is something that happened on the install of the rom
You have TWRP and cant fastboot?
Try to redo the steps to install TWRP and install FFF 1.4a by hashcode

He doesn't have FFF or TWRP anymore, as he flashed Amazon's stock update.zip
Your only solutions are either the USB trick (cracking open the KF's case and shorting specific pins) or getting a factory cable (recommended) to force the KF into fastboot mode, from which you can flash FFF and TWRP, then boot into TWRP and fix the mess.

Sorry, after i went from stock to custom roms, i never tried to go back to stock, didnt know that we lost fff and twrp when doing it.

Thanks, Dasanko, I'll do a search for the cable and see where to buy it and will go that route. Thanks again all.

FastBoot
Something similar happened to me and I did this:
Even though your Kindle Fire isn't recognized by KFU you can run it and select the option #5 (Install Latest FireFireFire).
When you do it'll probably error out attempting to get your device into fastboot but you'll get the prompt "( waiting for device )". Once that happens let your fire loop again and this time the window will be big enough for FireFireFire to be flashed into your device and leave the device in FastBoot...
After FireFireFire gets installed run KFU again to install TWRP and you'll be able to boot into recovery by poking the power button repeatedly in the new boot logo.
Hope that helps! (That's how I un-looped mine)

vbdss said:
Sorry, after i went from stock to custom roms, i never tried to go back to stock, didnt know that we lost fff and twrp when doing it.
Click to expand...
Click to collapse
Np, it's just it doesn't flash just over the system, but also overwrites the recovery and bootloader with their crappy stock ones.

darkjz said:
Something similar happened to me and I did this:
Even though your Kindle Fire isn't recognized by KFU you can run it and select the option #5 (Install Latest FireFireFire).
When you do it'll probably error out attempting to get your device into fastboot but you'll get the prompt "( waiting for device )". Once that happens let your fire loop again and this time the window will be big enough for FireFireFire to be flashed into your device and leave the device in FastBoot...
After FireFireFire gets installed run KFU again to install TWRP and you'll be able to boot into recovery by poking the power button repeatedly in the new boot logo.
Hope that helps! (That's how I un-looped mine)
Click to expand...
Click to collapse
I like this approach and think it MIGHT yield some results (but what do I know- I caused this afterall!).... Im going to let it stay in its little reboot / force close loop and have KFU sitting at FFF (waiting for device).... then if it looks like this works (how will I know exactly? the boot process will change how exactly (what should I look for, basically)) then I will do same with KFU and TWRP installation option do its thing. Thanks.

Something similar happened to me too. I was reverting my CM9 modded Kindle to a stock one. After flashing the 6.3.1 update, I was getting weird FCs whenever I would boot into the stock OS. I finally managed to get to the Factory reset option in the menu and that fixed the issue for me.
Sent from my Amazon Kindle Fire using xda app-developers app

freefaling said:
Something similar happened to me too. I was reverting my CM9 modded Kindle to a stock one. After flashing the 6.3.1 update, I was getting weird FCs whenever I would boot into the stock OS. I finally managed to get to the Factory reset option in the menu and that fixed the issue for me.
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Encouraging!.... what exactly did you do to get it to work for you - if you recall... i've just had it spinning through the loop with KFU sitting at waiting for device -- no results though... so seems pointless for me so far.

Little bit of info as to why/what is causing the issues discussed here:
The stock bin backs up data during the restore process and than restores it back along with the ROM (those of you familiar will already see the issue here but I'll continue); problem of course being there that if you restore data from a ROM like CM9 to the gingerbread based/neutered stock OS (or even to CM7 for that matter), it is going to cause all sorts of headaches with force closes and stuff just plain not working.
In short, for those considering trying to return to stock please remember to wipe data before attempting to flash the bin (at least until someone decides there's enough of a demand to make a cleaner return to stock method).
As for the OP, do what was suggested with the factory cable and you should be set; good luck.
Edit: the above posts regarding factory reset might work to as that will delete data but you would have to be able to get to that part of the settings menu, which depending on what's force closing may or may not be possible.

Your exactly right Sblood86 many are slipping on this bannana peel here lately trying to revert back to stock some with even more dire consequences not just a literal shock to it completely changing systems but also how data is rehandled. Could be a better option for some to do full wipes and flash something near stock like modaco to prevent this mishap.

This entire thread is ridiculous.

[BRICK] Nexus 7 (2012) wont turn OFF (yes!!), Bricked at Boot, Cant access Recovery

The current state of my tablet is quite curious: Its stuck on Google logo and it will be this way until the battery completely drains.
What I've tried:
- Holding the Power button shuts it down for 1 second...then it boots right back up by itself.
- Recovery (POWER+VOL DOWN) doesnt work, it goes straight to Google screen.
- Connecting via USB to the computer, Windows doesnt recognize the device.
In fact, the only way I found to Turn the Tablet off is popping the back cover and unplugging the battery cable. I've left it unplugged at night, hoping it would clear some sort of Cache, didnt work. Also I've tried unplugging the battery cable, plugging it back and Turning it on with POWER+VOL DOWN in hopes of acessing recovery but it goes straight to Google screen.
Additional Info:
- This happened while I was trying to downgrade from 5.1 to 4.4.4.
- My device is the LTE version of N7 2012
- My device is currently rooted.

@RavenEffect hold down the power button for at least 20 seconds to turn it off, 1 second is not enough
How did you try to downgrade? Probably flashing went wrong? In worst cases the bootloader was erased during downgrade ... in that case ther will be no hope.

AndDiSa said:
@RavenEffect hold down the power button for at least 20 seconds to turn it off, 1 second is not enough.
Click to expand...
Click to collapse
1 second is the ammount of time the tablet remains off, not the ammount of time i've pressed it. Yes, I've held it 20 seconds obviously.
AndDiSa said:
How did you try to downgrade? Probably flashing went wrong? In worst cases the bootloader was erased during downgrade ... in that case ther will be no hope.
Click to expand...
Click to collapse
Followed this guide right here: https://drive.google.com/file/d/0Bz6x7k-VkpUJU09paVM5cmh2Xzg/view
All the steps worked until the fastboot flash boot .\boot.img command. Sometimes it would get stuck on the command prompt and the tablet was frozen in Recovery Mode. I had to close the command Prompt, reboot the tablet into recovery again and Flashing another thing first, like recovery and system and THEN i would flash the boot.img.
So theres no hope?

First of all which factory image package did you use?
Sent from my Nexus 7 using XDA Labs

AndDiSa said:
First of all which factory image package did you use?
Sent from my Nexus 7 using XDA Labs
Click to expand...
Click to collapse
The one indicated on the guide, named razorg-mob30x-factory-10b7ca08.zip, the link is in the guide link also.

I suppose you have flashed the Nexus 7(2013) images onto your Nexus 7(2012) device ... that's not a good idea.
Sent from my Nexus 7 using XDA Labs

AndDiSa said:
I suppose you have flashed the Nexus 7(2013) images onto your Nexus 7(2012) device ... that's not a good idea.
Sent from my Nexus 7 using XDA Labs
Click to expand...
Click to collapse
Oh Crap, really? Is there a fix?

Yup, same deal here, not done by me. Now I am stuck in APX mode and I need to somehow flash bootloader back into the tablet. Please, don't tell me there isn't any way to do this...

RavenEffect said:
Oh Crap, really? Is there a fix?
Click to expand...
Click to collapse
Have you tried flashing the images google gives on their website? (they also give a helpful guide)

Charles IV said:
Have you tried flashing the images google gives on their website? (they also give a helpful guide)
Click to expand...
Click to collapse
Yeah, of course, but there is one problem. I can't boot into recovery mode, the bootloader got destroyed. So the only thing I have is either google logo with padlock on the bottom or nothing with APX mode. So no ADB, no FASTBOOT.

krivulak said:
Yeah, of course, but there is one problem. I can't boot into recovery mode, the bootloader got destroyed. So the only thing I have is either google logo with padlock on the bottom or nothing with APX mode. So no ADB, no FASTBOOT.
Click to expand...
Click to collapse
I know for mediatek, there is smartphoneflashtool, which flashes to the device when it's turned off. I don't know if there is an equivalent that you can use.
I don't think NRT does it, so you might be screwed.

There is nvflash ... but only if you have backed up *your* individual device images before you need them. So if your device is already bricked there is no chance ...
Sent from my Nexus 7 using XDA Labs

krivulak said:
Yeah, of course, but there is one problem. I can't boot into recovery mode, the bootloader got destroyed. So the only thing I have is either google logo with padlock on the bottom or nothing with APX mode. So no ADB, no FASTBOOT.
Click to expand...
Click to collapse
Problem is that, when you plug the Tablet to the PC via USB, it doesnt recognize the device, like I've stated on the original post, so I cant even get to a step where I can flash any sort of file.

Well, if I think about it, only the bootloader got destroyed. The image is free on google sites. I just have to put the bootloader image into the tablet so I can get to the bootloader and flash everything else with fastboot. There has to be way to do that. I mean if the "BIOS" (screen with google logo) got destroyed, that is bad, but it is just matter of damage on free to share universal loader. There has to be way...