Related
I had Jandycane installed and wanted to go back to the stock rom and I guess I didn't wipe everything I should have. The Kindle now boots into what appears to be a stock rom and then I get several popup errors and then it reboots. I have tried to quickly get into the factory reset but it reboots while trying to reset. The final says that "billing is not supported on this version of android market" If I ignore the error or if I don't swipe to log in it reboots anyway after about 10-15 seconds.
I have the Kindle fire utility installed but I don't see how I could mount if the unit won't stay on.
I don't see anyway to get into TWRP. The unit goes right into the kindle fire startup, so option for bootloader.
Anything I can try?
From the command prompt, with device turned off, enter:
Code:
adb wait-for-device shell idme bootmode 4002
…then turn the device on. That should put you back in fastboot, assuming the shell still works.
soupmagnet said:
From the command prompt, with device turned off, enter:
Code:
adb wait-for-device shell idme bootmode 4002
…then turn the device on. That should put you back in fastboot, assuming the shell still works.
Click to expand...
Click to collapse
It just boots to the Kindle Fire rom and reboots.
That's all? No messages in the command window? No errors or confirmations of any sort?
soupmagnet said:
That's all? No messages in the command window? No errors or confirmations of any sort?
Click to expand...
Click to collapse
Nothing. I tried the cable in a different port and the command window doesn't change. The Kindle Fire will say a USB cable is connected after I swipe into the Fire OS. It reboots after 10 or so seconds. One of the error in the Fire OS has to do with Calender and the other with android.process.acore.
You can try the Linux approach, but I doubt it would help in your situation.
You'll probably need to get a factory cable to get the device in fastboot before you can fix anything.
All fixed.
soupmagnet said:
You can try the Linux approach, but I doubt it would help in your situation.
You'll probably need to get a factory cable to get the device in fastboot before you can fix anything.
Click to expand...
Click to collapse
Cable bought, cable received, read the forums, got into TWRP again, wiped everything, installed clean ROM, ALL BETTER.
Thanks for your help and thanks to SkOrPn for the cable.
After spending a whole day on figuring out how to root my kindle fire 2 and install android 4.1, I nailed it by trying to push TWRP to my previously rooted kindle (using the kindle hd method) using:
adb push u-boot.bin /sdcard/
adb push twrp-blaze-2.0.0RC0.img /sdcard/
adb shell
su
dd if=/sdcard/twrp-blaze-2.0.0RC0.img of=/dev/block/mmcblk0p5
dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
exit
adb reboot
The screen never went back on and just stays black. It doesn't even seem to get any power at all anymore, no usb-connection, nothing. I tried holding the power-button for a very very long time, but nothing works. I tried charging on different computers and adapters and even praying. Even the light of the power-button doesn't show any reaction whatsover.
While I expected things to go wrong, I didn't expect them to go wrong in such a manner. What kind of most vicious root protection is that? Is there any hope? Does anybody have an idea?
Help would be very much appreaciated.
I'm sorry to say, but there isn't anything you can do.
You flashed an unsigned bootloader on a device with OMAP4 High Security. It's embedded into the hardware and unfortunately there is no way to fix it. You can thank Amazon for that little contribution.
ketspct the
Looks bad.
Does it make any sound when connect to pc?
Maybe try Amazon to replace it.
Tell then it was working then it wasn't
Or if you bought it in a local store rather than amazon try to get a replacement device
In November (just about one week after the warranty was up) the $300++ Kindle Fire HD we bought just stopped working. Amazon basically said sorry, your warranty is up - wanna buy another? (no thanks)
When it's turned on, the Kindle Fire logo appears, then the screen goes black. Nothing else.
We've tried the usual tricks. I bought a fastboot cable and tried the KFHD System.img Recovery Tool and all I get is "device not found." My computer doesn't seem to recognize the device at all.
Is there anything else I can try.... or is it just a lost cause??
Peppsico said:
In November (just about one week after the warranty was up) the $300++ Kindle Fire HD we bought just stopped working. Amazon basically said sorry, your warranty is up - wanna buy another? (no thanks)
When it's turned on, the Kindle Fire logo appears, then the screen goes black. Nothing else.
We've tried the usual tricks. I bought a fastboot cable and tried the KFHD System.img Recovery Tool and all I get is "device not found." My computer doesn't seem to recognize the device at all.
Is there anything else I can try.... or is it just a lost cause??
Click to expand...
Click to collapse
first of all, is it a 8.9 inch? if so DO NOT use fastboot cable, it can actually CAUSE damage to 8.9 incher. you just need the regular microUSB that came with your kindle. "special" fastboot cables are only required for the 7 incher... if you have the 8.9 inch "jem" i can try to point you to a few threads that may help unbrick it.
Mike
Thanks... Yes it is 8.9! I'd greatly appreciate any help!!
Anybody?
If I could get a computer to recognize the Kindle, I'm sure I could apply some of the fixes and find something to get it going again. It doesn't show up in device manager and makes an 'error' sound.
You can recover from this but first i will need to know how you bricked it, which operating system do you have, and do you have a sdk installed.
A few moths ago i ran into the same problem but now my kindle is working just fine.
DO NOT USE THE FASTBOOT CABLE TO DO ANYTHING IT CAN DAMAGE YOUR KINDLE
skullarc said:
You can recover from this but first i will need to know how you bricked it, which operating system do you have, and do you have a sdk installed.
A few moths ago i ran into the same problem but now my kindle is working just fine.
DO NOT USE THE FASTBOOT CABLE TO DO ANYTHING IT CAN DAMAGE YOUR KINDLE
Click to expand...
Click to collapse
In an attempt to not start new threads where they aren't needed. I'm in a very similar boat, so here are the answers to your questions:
I was attempting to flash CM11 to my 8.9 Kindle. I was following the following instructions:
wiki.cyanogenmod.org/w/Install_CM_for_otter2
Parts 1-6 of Step 1 completed successfully, and somewhere between Step 1 and 3 the screen turned off. I have not yet been able to get the screen to turn on again or the device to light up when charging or anything.
Thoughts?
clemsongt said:
In an attempt to not start new threads where they aren't needed. I'm in a very similar boat, so here are the answers to your questions:
I was attempting to flash CM11 to my 8.9 Kindle. I was following the following instructions:
wiki.cyanogenmod.org/w/Install_CM_for_otter2
Parts 1-6 of Step 1 completed successfully, and somewhere between Step 1 and 3 the screen turned off. I have not yet been able to get the screen to turn on again or the device to light up when charging or anything.
Thoughts?
Click to expand...
Click to collapse
Can you get into fastboot? I was able to recover mine by restoring my backup and then starting over with pushing stack and all that stuff. So getinto adb wtih the getvar, then just plug a normal cable into the kindle, and see if your PC recognizes it, and it drops into fastboot.
turn off your device and then connect your normal cable then type
fastboot -i 0x1949 getvar product
in your cmd or shell (if you are using linux or unix based operating system)
it should show
< waiting for device >
then turn on your device
it should go into fastboot then download the neccery files follow step 5 form the link
forum.xda-developers.com/showthread.php?t=2128175
and
follow the installation for cyanogenmod from
forum.xda-developers.com/showthread.php?t=2543481
skullarc said:
turn off your device and then connect your normal cable then type
fastboot -i 0x1949 getvar product
in your cmd or shell (if you are using linux or unix based operating system)
it should show
< waiting for device >
then turn on your device
it should go into fastboot then download the neccery files follow step 5 form the link
forum.xda-developers.com/showthread.php?t=2128175
and
follow the installation for cyanogenmod from
forum.xda-developers.com/showthread.php?t=2543481
Click to expand...
Click to collapse
I'm on Windows with minimal adb and fastboot. I get the < waiting for device > but when I plug in in my tablet nothing happens on either end. It doesn't matter if I have the device plugged in before or after running the command.
mrcpu said:
Can you get into fastboot? I was able to recover mine by restoring my backup and then starting over with pushing stack and all that stuff. So getinto adb wtih the getvar, then just plug a normal cable into the kindle, and see if your PC recognizes it, and it drops into fastboot.
Click to expand...
Click to collapse
By get into fastboot, I assume you mean with the command skullarc referenced since there is no button combination one can use to get into fastboot? Then your answer is shown above. The device has been completely unresponsive to anything I throw its way so far.
when you turn on your kindle what does it show?
If it does not even turn on then press the power button continuously for 20-30 seconds. Then press the power button again
skullarc said:
when you turn on your kindle what does it show?
If it does not even turn on then press the power button continuously for 20-30 seconds. Then press the power button again
Click to expand...
Click to collapse
It does not respond to anything I throw at it. If you mean to press and hold the power button for 30 seconds, let go, then press and release, that also gets no response.
clemsongt said:
It does not respond to anything I throw at it. If you mean to press and hold the power button for 30 seconds, let go, then press and release, that also gets no response.
Click to expand...
Click to collapse
Could it be that your charger is not working and doesn't device even blink when you press the power button
skullarc said:
Could it be that your charger is not working and doesn't device even blink when you press the power button
Click to expand...
Click to collapse
Not a charger issue, as I have used a known good one overnight with no difference.
clemsongt said:
Not a charger issue, as I have used a known good one overnight with no difference.
Click to expand...
Click to collapse
were you able to perform the third step ?
skullarc said:
were you able to perform the third step ?
Click to expand...
Click to collapse
What's the third step?
clemsongt said:
What's the third step?
Click to expand...
Click to collapse
Third step in installing CM11 and did you use fastboot cable ?
skullarc said:
Third step in installing CM11 and did you use fastboot cable ?
Click to expand...
Click to collapse
The third step found here?
http://forum.xda-developers.com/showthread.php?t=2128175
hashcode said:
STEP 3. Install the stack override in /system:
ADB commands entered while booted up into STOCK *rooted* Amazon Kindle OS -- May need to enable ADB debugging in Settings:
[2013-08-21] edited the location where stack is placed on device due to permissions changes
Code:
adb push stack /sdcard/
adb shell su -c "dd if=/sdcard/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/s
Click to expand...
Click to collapse
If so, I got the response "device not found" when attempting to push to sd card.
I tried with and without fastboot cable (have not verified functionality of fastboot cable as it was bought after bricking my device(.
clemsongt said:
The third step found here?
http://forum.xda-developers.com/showthread.php?t=2128175
If so, I got the response "device not found" when attempting to push to sd card.
I tried with and without fastboot cable (have not verified functionality of fastboot cable as it was bought after bricking my device(.
Click to expand...
Click to collapse
I was trying to ask at what step did your kindle turn off when you were trying to install cm11 and was bricked in this were you able to start the 3rd step
skullarc said:
I was trying to ask at what step did your kindle turn off when you were trying to install cm11 and was bricked in this were you able to start the 3rd step
Click to expand...
Click to collapse
Ohhhh...Sorry for being confused.
following these steps, I was able to successfully complete all of step 1, step 2, and step 3. it was in recovery while I was reading up on the "Installing CyanogenMod from recovery" section and when I looked back at the device, the screen had gone black. Since then I have not gotten it to do anything.
wiki.cyanogenmod.org/w/Install_CM_for_otter2
clemsongt said:
Ohhhh...Sorry for being confused.
following these steps, I was able to successfully complete all of step 1, step 2, and step 3. it was in recovery while I was reading up on the "Installing CyanogenMod from recovery" section and when I looked back at the device, the screen had gone black. Since then I have not gotten it to do anything.
wiki.cyanogenmod.org/w/Install_CM_for_otter2
Click to expand...
Click to collapse
Did you check the md5sum for the files that you flashed in step 3 and downloaded in step 2
it will tell you if they are corrupt
Hi,
I think I have bricked my Fire TV stick in a weird way.
I tried to root it using this tutorial:
http://www.aftvnews.com/how-to-inst...d-an-initial-rom-on-a-rooted-fire-tv-stick-1/
I managed to get root and su command working (used the chinese PC version of KingRoot, worked on the 3rd attempt). Next, on step 10, "Install TWRP custom recovery by running the command:sh /data/media/0/montoya_recovery_v1.zip" I stopped, because the adb shell showed the message "device read only or busy" or something similar.
I decided to eject the device and reboot it to try again. After this, the device boots into a splashscreen (Teamwin Recovery Project 3.0.0.7) where I have the choice to press left to boot normally and right to launch recovery. There also is a timer that after 5 seconds will boot into the selected choice.
The problem is that the remote left or right are not working and I cannot choose anything. After 5 seconds (the default choice is boot normally so it should work ok) the device boots into an amazon splashscreen and remains this way.
When I connect it to the computer via usb cable and start adb it recognizes the device, but only on the period that the 5 second timer runs. And some weird characters appear, SU is not working. The reboot command works in adb, but not much use. Also, if I list the adb devices, the serial number appears followed by "Recovery".
I tried plugging it into a normal charger (i do not have the genuine amazon one anymore) and no luck.
I have attached pictures of what appears on the tv with the connected device and on the command prompt console.
Thank you in advance!
b3cks89 said:
Hi,
I think I have bricked my Fire TV stick in a weird way.
I tried to root it using this tutorial:
http://www.aftvnews.com/how-to-inst...d-an-initial-rom-on-a-rooted-fire-tv-stick-1/
I managed to get root and su command working (used the chinese PC version of KingRoot, worked on the 3rd attempt). Next, on step 10, "Install TWRP custom recovery by running the command:sh /data/media/0/montoya_recovery_v1.zip" I stopped, because the adb shell showed the message "device read only or busy" or something similar.
I decided to eject the device and reboot it to try again. After this, the device boots into a splashscreen (Teamwin Recovery Project 3.0.0.7) where I have the choice to press left to boot normally and right to launch recovery. There also is a timer that after 5 seconds will boot into the selected choice.
The problem is that the remote left or right are not working and I cannot choose anything. After 5 seconds (the default choice is boot normally so it should work ok) the device boots into an amazon splashscreen and remains this way.
When I connect it to the computer via usb cable and start adb it recognizes the device, but only on the period that the 5 second timer runs. And some weird characters appear, SU is not working. The reboot command works in adb, but not much use. Also, if I list the adb devices, the serial number appears followed by "Recovery".
I tried plugging it into a normal charger (i do not have the genuine amazon one anymore) and no luck.
I have attached pictures of what appears on the tv with the connected device and on the command prompt console.
Thank you in advance!
Click to expand...
Click to collapse
While the stick is plugged into your computer and it boots to the TWRP selection screen in your ADB / command terminal (with the weird character's you see) using your keyboard type in mouse.
Then use press d then enter. This will highlight recovery and allow you to boot into recovery. You use key presses on your keyboard to navigate in TWRP.
While your in recovery and if you have not pushed the previous rooted zip over do this now.
Make sure you read exactly what your next steps are very close on how to proceed with flashing a pre rooted rom.
If you make a mistake doing this you will brick your stick.
What he said. Welcome to rooting FTV sticks...
Michajin said:
What he said. Welcome to rooting FTV sticks...
Click to expand...
Click to collapse
It worked, my stick is now up and going. Thank you very much, you are a genius!
:highfive:
Hey I got a question. Which fireOS version was on your stick while rooting it? Because I can't wait for a rooting method for 5.2.1.1
Pottkopp said:
Hey I got a question. Which fireOS version was on your stick while rooting it? Because I can't wait for a rooting method for 5.2.1.1
Click to expand...
Click to collapse
I think many of us updated to 5.0.5 and stayed there when news of root methods hit.
Yep. I missed that point and looked for any progress on rooting when my stick already updated itself to 5.2.1.1... But now I won't let it update anymore. Hopefully someone will find a new method soon.
Sorry for the late reply. 5.0.5. is my version
Hello.
I have a Fire TV (2nd gen.) and whenever I start it, the Amazon logo is displayed and that's that. It does not advance any further no matter how long Ieave it like that.
The device is not rooted.
I would like to somehow reset my box to its factory state, but so far nothing I've tried has worked.
Here's what I've tried so far:
1. Most of the stuff mentioned here:
a) Recovery via the Fire TV Remote
Nothing happens no matter how many times I try.
b) Recovery via a USB Keyboard (the “Alt+i+PrntScrn” method)
I've tried 4 different keyboards, both wireless and wired, (that work fine on a PC) and none of them get me into the recovery screen. I've tried one the keyboards with another FireTV and it eventually got to the recovery screen. So I'm guessing there's an(other) issue with this FireTV, from this point of view.
c) Recovery via ADB
This actually did something.
I ran the following command:
Code:
adb reboot recovery
In theory this should take me to the Android system recovery screen where I could select wipe cache, reset factory settings etc.
However, it takes me to the Amazon system recovery, which is a screen where there are no options. There's just some red text that says the following:
"Amazon system recovery <3e>
Your Amazon Fire TV will restart in a few minutes
and should resume normal operation
If it does not restart, please unplug the power cable and plug it back in
to force a restart. If you need assistance, please contact support at:
www.amazon.com/firetvsupport"
Needless to say that unplugging and plugging it back in didn't help.
2. Wiping data
I tried the following commands:
Code:
adb shell recovery --wipe_data
/system/bin/sh: recovery: not found
I managed to find an alternate solution for this:
Code:
adb shell wipe data
Wiping /data
Error opendir'ing /data 'Permission denied'
Done wiping /data
But it didn't seem to make any difference.
3. Fastboot
Code:
adb reboot bootloader
fastboot devices (I saw my device listed after this)
fastboot -w
Erase successful, but not automatically formatting.
File system type unknown not supported.
Erase successful, but not automatically formatting.
File system type unknown not supported.
erasing 'userdata'...
FAILED (remote: UnKnown Command)
finished. total time: 0.004s
Code:
fastboot erase userdata
erasing 'userdata'...
FAILED (remote: UnKnown Command)
finished. total time: 0.004s
This didn't seem to work either.
4. Sending a MASTER_CLEAR intent
Apparently it's possible to factory reset via adb.
Code:
adb shell am broadcast -a android.intent.action.MASTER_CLEAR
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system running?
at com.android.commands.am.Am.onRun(Am.java:299)
at com.android.internal.os.BaseCommand.run(BaseCommand.java:47)
at com.android.commands.am.Am.main(Am.java:97)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:256)
Sadly, it also failed...
Other (possibly) useful/relevant information include the following:
Code:
adb root
adbd cannot run as root in production builds
Code:
adb shell getprop ro.build.version.release
5.1.1
Code:
fastboot oem device-info
...
FAILED (remote: UnKnown Command)
finished. total time: 0.004s
The only options that I have left are the following:
1. The solution suggested here.
The problem described there seems to be the same on as mine. However, as mentioned here, this only works with FireOS 5.2.1.0 or lower. As far as I can tell, I have 5.2.4.0.
So, unless I can find a way to determine my FireOS version for sure and it turns out it's actually 5.2.1.0 or lower, or if somebody makes a recovery image that works for 5.2.4.0, this isn't really a solution...
2. Send it back to Amazon
I'm not sure if the warranty still covers it, but if it does and I don't find a way to fix this, I think this is the best choice.
3. Root it and try some root-related solutions.
So far I've only been able to try non-root solutions.
This, of course, will void my warranty, so I'd like to try this only as a last resort.
I'm not even sure I can root it in this state. From what I read on the web, at some point I'll have to select accept when superSU asks for permissions the first time. Since I can't get pass the boot screen, I don't know how I'll be able to do this...
4. Nothing
If nothing works, I guess I'll have to just cut my losses, and get a new Fire TV.
Apart from the things mentioned above I've also tried/read most the posts on xda mentioning similar problems but I haven't found anything useful.
As mentioned at the beginning of the post, I just want to reset it to its factory state. I don't care about losing everything that's on it. I just want it to be like it was after it was unboxed.
Any kind of advice/help/solution is welcomed.
Determine FireOS version
conectionist said:
So, unless I can find a way to determine my FireOS version for sure
Click to expand...
Click to collapse
Code:
adb shell getprop ro.build.version.fireos
2WhlWzrd said:
Code:
adb shell getprop ro.build.version.fireos
Click to expand...
Click to collapse
Thank you. I spent some time googling how to get the fireOS version but I gave up at some point.
Unfortunately, it's as I suspected:
Code:
adb shell getprop ro.build.version.fireos
5.2.4.0
So I guess I can write off "solution" #1.
Ok, so I don't know what happened, but after leaving it alone for about 3-4 hours, suddenly, out of no where, a partial home screen appeared. Then, after a few seconds, a network connection alert dialog appeared. The remote wasn't working so I had to use adb keyevent to simulate the remote control commands.
I closed the dialog, then went to settings and restored the box to factory settings.
So, basically, if none of the above work for you, the only solution is to simply leave it alone for a few hours and, if you're lucky, it might fix itself. :laugh:
Wow. I have to try and leave it plugged in for a few hours and just hope for the best. On mine cant even do the ADB commands and stuck with a white amazon logo and pulsing orange to white led light.
DhiJay23 said:
Wow. I have to try and leave it plugged in for a few hours and just hope for the best. On mine cant even do the ADB commands and stuck with a white amazon logo and pulsing orange to white led light.
Click to expand...
Click to collapse
Hello, I'm facing the same exact issue that you've described. Not able to connect through adb and tried all the approaches described in this post.
Have you been able to fix that or what is the recommendation?
Thank you!
I have read elsewhere that people have left it plugged in, and overnight, after a few hours, they came back to it in the morning and it was operating normal .... go figure?
Oneacer said:
I have read elsewhere that people have left it plugged in, and overnight, after a few hours, they came back to it in the morning and it was operating normal .... go figure?
Click to expand...
Click to collapse
Yeah, tried that with no luck. Is there any option to reset the device completely?
Thank you.
dmkravch said:
Yeah, tried that with no luck. Is there any option to reset the device completely?
Thank you.
Click to expand...
Click to collapse
i got no luck too. left it for a few hours with no fortune. I was wondering if short pin method is possible with this device like any android boxes.
DhiJay23 said:
i got no luck too. left it for a few hours with no fortune. I was wondering if short pin method is possible with this device like any android boxes.
Click to expand...
Click to collapse
Hello, I've got it fixed by plugging it into another TV, it worked and then I went home and connected to mine and for some reason it is functional now.
Oneacer said:
I have read elsewhere that people have left it plugged in, and overnight, after a few hours, they came back to it in the morning and it was operating normal .... go figure?
Click to expand...
Click to collapse
TRied this but it wont work for me.
I had the same issue this morning. My young kids were freaking out that they might have broken the TV. I didn't admit it might have been me trying to get sideloaded Peacock to run last night. Anyway I was trying everything and was repeated trying the ALT i PrtScn to no avail, and was about to give up when by itself it booted in SAFE MODE. I have never seen that and none of the guides mention SAFE MODE. I put in caps as that is how it's displayed on screen. Anyway from there I was able to do a Factory Reset and everything is back. No idea what triggered it but the SAFE MODE was just like Windows Safe Mode. It had been about 2 hours of the boot loop.