I tried to root my girlfriend's kindle today, and I did everything right, up until I had to install twrp with the kfu. She pulled the usb out before it could install, and now im stuck at the yellow triangle. Ive been able to get my computer to recognize it as "kindle" under device manager, but Im lost as to what to do next. Ive tried to update the drivers but it wont install. I REALLY WOULD APPRECIATE ANY HELP!!!
Try booting into recovery, if that doesn't work then try getting the kindle fire utility to get stock update.zip (#4 in run). If that doesn't work then I have no idea.
Sent from my Kindle Fire
Im not sure how to boot into recovery, wen I turn the kindle on, its on the yellow triangle. I press power and nothing happens but i dont think twrp was ever installed. nd I tried that too, it just hangs after waiting on device
King_Me said:
Im not sure how to boot into recovery, wen I turn the kindle on, its on the yellow triangle. I press power and nothing happens but i dont think twrp was ever installed. nd I tried that too, it just hangs after waiting on device
Click to expand...
Click to collapse
To get into recovery (or at least try), on the screen with the yellow triangle hold the power button until it turns orange (the button, not the triangle) then the screen should do a small flash and go back to the yellow triangle, after 5-10 sec it should say on the screen "teamwin" and then slide up to TWRP if you installed recovery. From there, you can mount usb storage from recovery and get a rom on it to flash (I prefer CM9) and then when it boots into CM9 it will be rooted.
I figured it out. lol. Thanks man. I had to install the drivers that came with the kfu. I forgot that part. *face palm*
King_Me said:
I figured it out. lol. Thanks man. I had to install the drivers that came with the kfu. I forgot that part. *face palm*
Click to expand...
Click to collapse
Lol well that's good.
Sent from my SGH-T989 with CM7
colorblind
BiteBlaze said:
To get into recovery (or at least try), on the screen with the yellow triangle hold the power button until it turns orange (the button, not the triangle) then the screen should do a small flash and go back to the yellow triangle, after 5-10 sec it should say on the screen "teamwin" and then slide up to TWRP if you installed recovery. From there, you can mount usb storage from recovery and get a rom on it to flash (I prefer CM9) and then when it boots into CM9 it will be rooted.
Click to expand...
Click to collapse
I'm there too but (gulp) colorblind, it might turn orange but I don't see it. I am stuck at triangle not being recognised by computer.
http://forum.xda-developers.com/showthread.php?t=1552547
would also read post #2 about drivers
if you got the drivers right, some more information would be helpful
what is your problem ? - what exactly have you done/tried ?
b63 said:
http://forum.xda-developers.com/showthread.php?t=1552547
would also read post #2 about drivers
if you got the drivers right, some more information would be helpful
what is your problem ? - what exactly have you done/tried ?
Click to expand...
Click to collapse
Hi, I have a similar (maybe the same) problem: my KF has blocked the yellow triangle.
This happened after that I tried for the second time to apply the "Install permanet root with superuser" from the Kindle Fire Utility 0.9.5.
The first time everything went fine except the subsequent installation of Extras returning error at the following lines:
tools\adb push apps\system\vending.apk /system/app
tools\adb push apps\system\GoogleCalendarSyncAdapter.apk /system/app
tools\adb push apps\system\GoogleContactsSyncAdapter.apk /system/app
The error was: permission denied.
So, I tought that somenting wen wrong in the previous installation and I tried again.
This time something went really wrong: the KF is in the state I told: yellow triangle.
I tried to turn off and on again but it is in the same state.
I tried to push the button waiting for the TWRP to get up, but nothing happened.
I tried to connect with PC, but the KF is not visible.
What can I do? Does somebody have any hint?
Thank you.
Related
Things I can do:
- Get to bootloader screen
- Plug in USB, pop in batter and get to fastboot USB (PC detects "Android 1.0" at this point but can't find a driver for it).
- Attempt to load ESPRIMG.zip from root of sdcard but always get "Main version is older!" and "update failed!" followed by a prompt to reboot device.
Things I can't do:
- Boot up the phone past the splash screen
- Go into recovery/fastboot; recovery dumps me to the splash and hangs there and fastboot just brings me right back to the bootloader menu.
Phone was working a few hours ago and then when I powered it down it never made it back past the splash screen.
Am I screwed?
jhinckley said:
Things I can do:
- Get to bootloader screen
- Plug in USB, pop in batter and get to fastboot USB (PC detects "Android 1.0" at this point but can't find a driver for it).
- Attempt to load ESPRIMG.zip from root of sdcard but always get "Main version is older!" and "update failed!" followed by a prompt to reboot device.
Things I can't do:
- Boot up the phone past the splash screen
- Go into recovery/fastboot; recovery dumps me to the splash and hangs there and fastboot just brings me right back to the bootloader menu.
Phone was working a few hours ago and then when I powered it down it never made it back past the splash screen.
Am I screwed?
Click to expand...
Click to collapse
Delete ESPRIMG.zip from your sd card. It tries to load it every time you start up.
That happened to me before and I didn't know what was going on lol.
It wasn't on there before I put it there. I was trying to get it back to the factory image. Whenever I went to the boot screen it was always looking for ESPRDIAG.zip or ESPRIMG.zip. If I delete it, nothing new happens, still hangs.
/bump
Still stuck. :/
Hmm odd situation.I no I had a problem but I left it on the splash screen for about five minutes and it finally booted you can try leaving it there and see of it eventually boots but if it takes 10 minutes plus then forget it. Though idk why you can't boot into recovery. when you have it plugged into your computer does adbe recognize it? Maybe you can do something with adb
Sent from my T-Mobile myTouch 3G Slide using XDA App
This is happening to me too. Anyone know the solution?
If I delete ESPRIMG.zip will anything bad happen?
same thing here...lol
total noot to the mytouch.
i am trying to fix for a friend, and i get endless boot loops. can acess recovery and bootloader
acejoker25000 said:
Hmm odd situation.I no I had a problem but I left it on the splash screen for about five minutes and it finally booted you can try leaving it there and see of it eventually boots but if it takes 10 minutes plus then forget it. Though idk why you can't boot into recovery. when you have it plugged into your computer does adbe recognize it? Maybe you can do something with adb
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Adb only sees the phone if its in recovery or fully booted. I'm pretty sure fastboot.exe is what is used to debug fastboot and earlier boot stages.
unknownally said:
This is happening to me too. Anyone know the solution?
If I delete ESPRIMG.zip will anything bad happen?
Click to expand...
Click to collapse
No, nothing bad will happen
dapoharoun said:
same thing here...lol
total noot to the mytouch.
i am trying to fix for a friend, and i get endless boot loops. can acess recovery and bootloader
Click to expand...
Click to collapse
You're hijacking a thread, you should make your own. Simple answer to your question though; reflash a rom in recovery. If you need more info make your own thread.
Sent from my T-Mobile myTouch 3G Slide
I made my own thread here: http://forum.xda-developers.com/showthread.php?t=890386 with no luck.
I didn't have ESPRING.zip to begin with since I deleted it after rooting. So I download the stock ESPRING and ran it through Bootloader. It prompted me to update so I did.
After the update finishes it asks me to reboot. So I do and then I'm stuck on the splash/boot screen again.
When I first rooted I deleted the expressimg.zip and left the update.zip (recovery) just incase something like this happened ...
Boot up using power + volume down then its gonna try to look for espressimg.zip ...it will tell you its not found..then use the volume button to go to recovery..push power to select then its gonna take you to the screen with the red triangle/exclamation mark screen ..press and hold power and volume up for a little (if it doesn't work keep tryn till you get the stock blue recovery to pop up)...the stock recovery will pop up..then it will prompt you to apply update. Zip from sd card (clockwork recovery) ..select it and you should be in clockwork ...then do what you gotta do...
Its happened to me a few times and this always does the job
Hope this helps if not I'm sorry and keep tryn
You HAVE to have update.zip (clockwork recovery) on your SD card..(not in any folders, on the root of the card) in order for this to work!!!
If you don't have it push to SD card via adb
Sent from my T-Mobile myTouch 3G Slide using XDA App
JeezyMT3G said:
When I first rooted I deleted the expressimg.zip and left the update.zip (recovery) just incase something like this happened ...
Boot up using power + volume down then its gonna try to look for espressimg.zip ...it will tell you its not found..then use the volume button to go to recovery..push power to select then its gonna take you to the screen with the red triangle/exclamation mark screen ..press and hold power and volume up for a little (if it doesn't work keep tryn till you get the stock blue recovery to pop up)...the stock recovery will pop up..then it will prompt you to apply update. Zip from sd card (clockwork recovery) ..select it and you should be in clockwork ...then do what you gotta do...
Its happened to me a few times and this always does the job
Hope this helps if not I'm sorry and keep tryn
You HAVE to have update.zip (clockwork recovery) on your SD card..(not in any folders, on the root of the card) in order for this to work!!!
If you don't have it push to SD card via adb
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
what if ur not rooted?
dapoharoun said:
what if ur not rooted?
Click to expand...
Click to collapse
Then root
Sent from my T-Mobile myTouch 3G Slide using XDA App
It's my understanding that without having the security off on our phones, the espresso recovery is not modifiable. What this essentially means is that, either the recovery should be there and fine (and by "fine" I mean, you get a triangle with an exclamation mark in it) because no ROM can currently touch it.
Me thinks that, if you are not able to get to the stock recovery (not Clockwork, but the basic, bare bones one) than your phone is probably having bigger issues. I would test this by doing the following:
1. Boot into the boot loader (I believe it's power and Volume Down at the same time when the device is turned off).
2. Wait for the device to finish it's grumblings (if you have the ESPER.IMG file on there, I think it actually checks it and even asks if you want to install it -- if it does, say no).
3. Select the option for recovery (with the volume keys).
4. I think it's power again to execute the option.
If you get to a nice black screen with a picture of your phone on there with a red triangle, then your phone is in business. We can probably convince it to behave. If that far doesn't go, me thinks something is wrong with the bits of your phone that current ROM modders can't write to...
sleepykit said:
It's my understanding that without having the security off on our phones, the espresso recovery is not modifiable. What this essentially means is that, either the recovery should be there and fine (and by "fine" I mean, you get a triangle with an exclamation mark in it) because no ROM can currently touch it.
Me thinks that, if you are not able to get to the stock recovery (not Clockwork, but the basic, bare bones one) than your phone is probably having bigger issues. I would test this by doing the following:
1. Boot into the boot loader (I believe it's power and Volume Down at the same time when the device is turned off).
2. Wait for the device to finish it's grumblings (if you have the ESPER.IMG file on there, I think it actually checks it and even asks if you want to install it -- if it does, say no).
3. Select the option for recovery (with the volume keys).
4. I think it's power again to execute the option.
If you get to a nice black screen with a picture of your phone on there with a red triangle, then your phone is in business. We can probably convince it to behave. If that far doesn't go, me thinks something is wrong with the bits of your phone that current ROM modders can't write to...
Click to expand...
Click to collapse
Ummm that's exactly what I already said 0_o
Sent from my T-Mobile myTouch 3G Slide using XDA App
For reasons that I don't quite understand I always like instructions in step by step order so I thought it might help. If not, oh well...
I do wonder what could cause someone to lose their recovery on a Slide (at least before this afternoon)...
sleepykit said:
I do wonder what could cause someone to lose their recovery on a Slide (at least before this afternoon)...
Click to expand...
Click to collapse
Lol me too
Sent from my T-Mobile myTouch 3G Slide using XDA App
ok not my thread but im need help to.
my phone wont boot, so theres no way to root.....i tired.
i can get the red triangle and phone: pics in my thread.
http://forum.xda-developers.com/showthread.php?t=891312
thanks you
dapoharoun said:
ok not my thread but im need help to.
my phone wont boot, so theres no way to root.....i tired.
i can get the red triangle and phone: pics in my thread.
http://forum.xda-developers.com/showthread.php?t=891312
thanks you
Click to expand...
Click to collapse
Hm... Does your Slide have a 0 on the keyboard or a 0 with a line through it (where the 0 key actually is)? I know this sounds like an odd questions, but bear with me for a moment...
For the first however many months, Slides could be rooted by fooling the thing into booting a modded Clockwork Recovery and then gaining root that way. All the work had to basically be done while in recovery (unlike the exploid method). The newer Slides, from what I understand, no longer have that flaw and the method doesn't work.
This method (http://forum.cyanogenmod.com/topic/1856-rooting-the-slide/page__p__17094#entry17094) (sorry have no idea where Eugene's copy of this has gone in the dev section).
JeezyMT3G said:
When I first rooted I deleted the expressimg.zip and left the update.zip (recovery) just incase something like this happened ...
Boot up using power + volume down then its gonna try to look for espressimg.zip ...it will tell you its not found..then use the volume button to go to recovery..push power to select then its gonna take you to the screen with the red triangle/exclamation mark screen ..press and hold power and volume up for a little (if it doesn't work keep tryn till you get the stock blue recovery to pop up)...the stock recovery will pop up..then it will prompt you to apply update. Zip from sd card (clockwork recovery) ..select it and you should be in clockwork ...then do what you gotta do...
Its happened to me a few times and this always does the job
Hope this helps if not I'm sorry and keep tryn
You HAVE to have update.zip (clockwork recovery) on your SD card..(not in any folders, on the root of the card) in order for this to work!!!
If you don't have it push to SD card via adb
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Hey,
thanks for the help. I just have a problem.
I can't get to recovery. When I do, it goes to the T-Mobile splash screen. I do have update.zip and ESPRING.zip in the root of my SD card, but I don't have exspressimg.zip. However, I don't think it matters since I can't get into recovery.
I also tried using a different update.zip from http://forum.xda-developers.com/wiki/index.php?title=HTC_Espresso with no luck.
unknownally said:
Hey,
thanks for the help. I just have a problem.
I can't get to recovery. When I do, it goes to the T-Mobile splash screen. I do have update.zip and ESPRING.zip in the root of my SD card, but I don't have exspressimg.zip. However, I don't think it matters since I can't get into recovery.
I also tried using a different update.zip from http://forum.xda-developers.com/wiki/index.php?title=HTC_Espresso with no luck.
Click to expand...
Click to collapse
ESPRIMG.zip is what I meant lol sorry
And no it doesn't matter.... does this happen when you select "recovery" from fastboot? Or when youre on the red triangle/exclamation point screen? you shouldn't be taken to the tmo splash screen...don't hold power and vol up for too long cuz it will reboot the phone and take you to splash screen (maybe that's what ur doing)
If you're in the red triangle screen hold power and vol up for no more then one second..keep pushing till the blue stock recover pops up
Sent from my T-Mobile myTouch 3G Slide using XDA App
I have rooted an evo 4g, a droid x, and 2 galaxy nexus' and i've never had this much trouble. I installed AOKP and gapps via TWRP and sometimes the device just wont boot. I hit the power button and it flashes green and does nothing. Sometimes if i plug it into my PC and hit the power button the option to hit power to bring up recovery comes up, and I just sit there not knowing where to go next. What should I do? KFU says it's boot status is 4000 and just hangs at activated fastboot.
edit - didnt realize this version of twrp allowed usb mounting, all is good.
Hi friend. These ics rom use kernel 3.0.. If you shut down, hold the power button for 30 seconds until it fully power down... After you see the screen completely dark, then press the power button again, it will turn on. At least that my experience from the first time use ics on kindle fire. Hope that help.
well, theres a new problem now. I turn it on and it just shows the kindle fire splash with an android above it. if I plug it in, it turns on instantly. KFU isnt reading it as anything but windows sees it as android adb interface. doing adb reboot fastboot says device not found. adb devices shows no devices.
I bought up KFU and installed firefirefire though that interface, then switched to cmd prompt and manually used fastboot flash recovery twrp.img after cd'ing android platform tools and putting that latest twrp downloaded from their site in that folder (platform tools)
this happened when using fastboot flash recovery twrp.img in command prompt. It was in this screen while flashing. I did this because KFU wasnt flashing the latest version.
So yup...
edit - this is now fixed. Back to my original problem however.
I install AOKP and Gapps, but after the recovery ! screen it just blacks out. no boot animation or anything. I can get back into recovery and flash back to stock, but, ya know. I want AOKP. What's going on? Yes I am wiping everything.
Sorry wish I could help but this is way over my head....I hope someone else with knowledge will come along and help you...Good Luck!
a few people in the AOKP forums have the same issue, say to just wait forever or keep rebooting....I dunno bout that. I'm not seeing any progress.
patass said:
a few people in the AOKP forums have the same issue, say to just wait forever or keep rebooting....I dunno bout that. I'm not seeing any progress.
Click to expand...
Click to collapse
You need to start by reading this:
http://forum.xda-developers.com/showpost.php?p=23747567
Actually it was just the official aokp rom. Other roms are flashing fine. Dunno what's up with that.
Sent from my Galaxy Nexus using xda premium
I rooted my KF about a month ago, and its been working fine since, then my friend told me to download firefirefire and NWRP from the kindle fire utility(which i used to root). In the process of downloading firefirefire, a boot symbol pops up with the kindle fire logo and an android bot over it. Its been stuck like that since, and my computer wont read the kindle when its plugged into the usb. Im also sort of a noob, so please help?
You admittedly said you're a noob so you should read this http://forum.xda-developers.com/showthread.php?t=1552547 . Your kindle isn't bricked. It's in fastboot mode. There are a few ways you can handle this situation. Search the forums as your situation is not unique and has been discussed all over these threads. If your still having problems and can't figure it out come back here for help.
The screen your looking at is the bootloader screen the problem is your still looking at it. This replaced the old fff boot loader the yellow triangle. If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on. This sometimes happens, I have yet to find a clean solution If you end up stuck with a yellow triangle, do not EVER unplug it. Leave it plugged in. Check the windows drivers to make sure it isnt showing as "kindle" again. Fastboot is different and can cause this.
You can hold down the power button till it fully powers off ,then power it on when you see the screen your stuck at hold the power button again till it turns orange and twrp opens up if not read more to find out what to do next
AKbambi said:
I rooted my KF about a month ago, and its been working fine since, then my friend told me to download firefirefire and NWRP from the kindle fire utility(which i used to root). In the process of downloading firefirefire, a boot symbol pops up with the kindle fire logo and an android bot over it. Its been stuck like that since, and my computer wont read the kindle when its plugged into the usb. Im also sort of a noob, so please help?
Click to expand...
Click to collapse
If you get your kindle booting correctly I suggest you flash the new bootloader 1.4a by Hashcode. You can find that here http://forum.xda-developers.com/showthread.php?t=1632375 This new bootloader has some additional options, one which will allow you to tell the KF to boot normally if you were to find yourself in this situation again.
Thepooch said:
If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on.
This did not work.. i dont have the yellow triangle, i have the kindle fire logo with a bot on top... again, im probably stupid for not knowing how to fix this, but what do i do now?
Click to expand...
Click to collapse
actually, nevermind.. i forgot to install the driver, and when i did, KF unbricking utility was very helpful and i got my kindle to work again.
AKbambi said:
Thepooch said:
If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on.
This did not work.. i dont have the yellow triangle, i have the kindle fire logo with a bot on top... again, im probably stupid for not knowing how to fix this, but what do i do now?
Click to expand...
Click to collapse
The kindle fire screen with the android is the same as the yellow triangle glad you fixed it
Click to expand...
Click to collapse
Hey guys. I actually bricked my Kindle Fire over a month ago after I rooted it with KFU. I had the boot problem with the yellow triangle and orange power button. I came here and someone told me I was stuck in "Fastboot Mode." But before I got to fix it, I rebooted my kindle, the yellow triangle screen appeared for a few seconds, but THEN I GOT INTO THE SYSTEM! I decided it was better to not mess with it further. I have nothing else installed. No TWP, no FireFire.
It was working fine until, after I recharged it one day, the same boot problem with the yellow triangle came back! But this time, no matter how many times I rebooted it, I could not get back into the system. My Device Manager also could not recognize my Kindle. (Its listed as an "Unknown Driver")
I came back here and everyone pointed to this thread:http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2.
I uninstalled the "Unknown Driver," reinstalled the drivers with the .bat file from KFU, and then plugged in my Kindle. I get a message "Drivers successfully installed." On my Device Manager, I see the "Android Phone" driver, BUT THEN THE DEVICE MANAGER SCREEN FLASHES AND THEN THE ANDROID PHONE DRIVER DISAPPEARS! I try "scan for hardware changes" and the "Unknown Device" driver re-appears!!
i tried different USB ports and I get the same problem. Is there anything else I can do? Please help!
P.S. I still have a warranty on it, but I'm assuming, by rooting it, its voided right?
EDIT: I used FireKit to temporarily get into the system for a few seconds. However the KF reboots by itself and then I'm stuck with the yellow triangle screen again. Check out this video http://www.youtube.com/watch?v=DiEld...ature=youtu.be
The yellow triangle you see is FireFireFire, and I'm willing to bet you have TWRP installed as well.
When you boot up and see the yellow triangle, hold the power button until it turns orange and release. Your device should boot into recovery.
If that's the case, your problem should be relatively easy to fix.
soupmagnet said:
The yellow triangle you see is FireFireFire, and I'm willing to bet you have TWRP installed as well.
When you boot up and see the yellow triangle, hold the power button until it turns orange and release. Your device should boot into recovery.
If that's the case, your problem should be relatively easy to fix.
Click to expand...
Click to collapse
Oh, I wasn't aware I had those installed. I did as you said. Hold power button until it turns orange and then release. Nothing happens afterwards. It's stuck in the same screen with the yellow triangle and "press power button for recovery" message.
Could try this http://forum.xda-developers.com/showthread.php?t=1672583
I figured out why the Android Driver keeps disappearing. Basically, when I plug the Kindle in, the power button glows green at first, and thats when my computer senses the android driver. Then I hear a disconnect "beep" sound on my computer and the Kindle power button turns orange. That's when the Android Driver disappears and I get the "Unknown" driver back.
Thepooch said:
Could try this http://forum.xda-developers.com/showthread.php?t=1672583
Click to expand...
Click to collapse
I gave this a try. I replaced the files from kfu with the files that the thread starter attached. I plugged in my kindle and I get the same problem as above. The Android Driver shows up for a second, but then the power button turns orange and the usb automatically disconnects. Also, I don't know how to use the cmd function. Can someone please teach me?
Please help!
You need to uninstall the driver you have select delete from computer or windows will continue to try to reinstall it.
I got the same problem but resolved by Firekit, pls see the last post of the below link.
http://forum.xda-developers.com/showthread.php?t=1639905&page=3
Thepooch said:
You need to uninstall the driver you have select delete from computer or windows will continue to try to reinstall it.
Click to expand...
Click to collapse
When I right click->uninstall, I'm not given the option to "delete from computer." I am aware that there should be a checkbox for that. But for some reason, the "Unknown Device" driver doesn't have that checkbox.
tkcctkcc said:
I got the same problem but resolved by Firekit, pls see the last post of the below link.
http://forum.xda-developers.com/showthread.php?t=1639905&page=3
Click to expand...
Click to collapse
I will give this a try when I find a USB drive.
Thanks for continuing to help me guys!
Hey I gave the firekit a try and it worked like a charm...for a minute. Then when I turn it off, I get stuck on the yellow triangle again. Is there something wrong with my root? Should I reflash my KF?
spacebow said:
Hey I gave the firekit a try and it worked like a charm...for a minute. Then when I turn it off, I get stuck on the yellow triangle again. Is there something wrong with my root? Should I reflash my KF?
Click to expand...
Click to collapse
Just change your bootmode back to 4000
soupmagnet said:
Just change your bootmode back to 4000
Click to expand...
Click to collapse
Is that the same thing as normal boot? Cuz I tried doing that with firekit, but my device keeps powering off by itself. And then when I restart it, I get stuck with the yellow triangle again.
spacebow said:
Is that the same thing as normal boot? Cuz I tried doing that with firekit, but my device keeps powering off by itself. And then when I restart it, I get stuck with the yellow triangle again.
Click to expand...
Click to collapse
Yes thats normal boot post a video of what happening cause sounds like your having more issues.
http://www.youtube.com/watch?v=DiEld5TzZG8&feature=youtu.be
Please check the above video for my issue. I listed all the observable problems in the description as well.
Please help!
Ok i think I finally fixed it. I used FireKit to completely reflash TWRP and FFF onto the stock ROM. Appears to be working fine now!
Having a small issue with my device, and I could do with getting in to fastboot to troubleshoot.
I have TWRP installed along with a nightly version of CM10.1, When I try ADB reboot bootloader The device reboots, flashes the first bootscreen for a second(Orange and White Kindle Fire) and then shuts itself down.
Any suggestions that don't involve getting a fastboot cable? I can make one if I have too, but I would rather try and find out why it wont work this way.
Nvmd
So, you don't see the blue Kindle Fire logo at all?
I see the Orange and white, then the Blue and White, and then it boots, When I try and reboot to bootloader, I see the Orange and White, and then it shuts down.
Jackering said:
I see the Orange and white, then the Blue and White, and then it boots, When I try and reboot to bootloader, I see the Orange and White, and then it shuts down.
Click to expand...
Click to collapse
Why don't you use the volume button to access recovery?
Hashcode said:
TO ENTER RECOVERY:
Press the left volume button (volume up) while the logo is still YELLOW and keep pressing until the logo turns BLUE. Wait a moment and you should enter recovery.
Click to expand...
Click to collapse
I can enter recovery fine, I want to get in to Fastboot to test something.
Jackering said:
I can enter recovery fine, I want to get in to Fastboot to test something.
Click to expand...
Click to collapse
If your device boots into recovery, you can issue the "reboot bootloader" command from there
If you are able to get into fastboot from there, you know it's the nightly version of CM10.1 that is the problem and not the bootloader. If that's the case, install a different ROM.
[Edit:] For curiosity's sake, what "troubleshooting" are you expecting to do in fastboot?
soupmagnet said:
If your device boots into recovery, you can issue the "reboot bootloader" command from there
If you are able to get into fastboot from there, you know it's the nightly version of CM10.1 that is the problem and not the bootloader. If that's the case, install a different ROM.
[Edit:] For curiosity's sake, what "troubleshooting" are you expecting to do in fastboot?
Click to expand...
Click to collapse
From ADB on the device?
Edit; I get a message "Error: Command not found" or something like that trying to run it on the device.
I just wish to test a reboot to fastboot mode, thats all :good:
Edit2:
Just noticed that when in recovery, Windows Device Manager has an ! next to "Amazon KindleFire2" Yet, There is no ! once booted, Interesting.
Jackering said:
From ADB on the device?
Edit; I get a message "Error: Command not found" or something like that trying to run it on the device.
I just wish to test a reboot to fastboot mode, thats all :good:
Edit2:
Just noticed that when in recovery, Windows Device Manager has an ! next to "Amazon KindleFire2" Yet, There is no ! once booted, Interesting.
Click to expand...
Click to collapse
Oh nevermind, I was wrong. Typically you would use 'idme' to change the bootmode then reboot, but 'idme' isn't included in our version of TWRP. I thought maybe it could be pushed to recovery then executed, but I keep getting a "Segmentation fault" error on this version when trying it on my end. I'm not sure what's causing that other than perhaps this version wasn't made with 'idme' in mind, but that's purely speculation on my part. If you had any other device than a Kindle Fire 2 you wouldn't have any problem accessing fastboot, but as it stands now, I think your only option (to get into fastboot) is to acquire a factory cable or install a different ROM.
But even with fastboot, that's still not addressing your original problem. The fastboot binary is really only useful for overwrite\ing partitions and changing the bootmode. Whatever your problem is, it will likely be fixed by installing a non-nightly version of CM10.1 (nightly = not so stable).
As for your device manager, later versions of TWRP have different hardware IDs than that of the stock OS. Just add the hardware ID to your 'android_winusb.inf' and reinstall it.
soupmagnet said:
Why don't you use the volume button to access recovery?
Click to expand...
Click to collapse
Btw- we don't have volume buttons. Drives me nuts
Sent from my SGH-I727 using Tapatalk 2