Database Users

Yellow Triangle Bootloop

I've checked the other two threads to know avail. My device reboots up to the yellow triangle, and then reboots infinitely. Here's my situation:
1. I think i booted into recovery using my roms reboot into recovery option.
2. My kindle fire is in a state of it can't turn on unless it is plugged into a computer/charger.
3. I don't see "kindle fire" in my devices on windows 7 and I don't see ADB composite device thing.
4. Using the install drivers.bat that is in the kindle fire utility says Driver name "Google, Inc (WinUSB) Status Ready to use.
5. I have tried the kindle fire utility to set boot mode to normal but adb and fastboot don't recognize it.
6. Also I've tried plugging into the computer with a factory usb cable and that also didn't work.
I'm wondering if i'm SOL.
[FIXED]
Okay, So I finally got my fire working! Charged it up through a charger for a little while. Booted into ubuntu 11.10 (32bit) with the firekit file and ran the install recovery script. It hung at waiting for device. I unplugged it and plugged it back in and tried turning it on and off and holding the power of the device for awhile and one time it just worked. Was able to reboot and boot into recovery and flash a rom.

mjm128 said:
I've checked the other two threads to know avail. My device reboots up to the yellow triangle, and then reboots infinitely. Here's my situation:
1. I think i booted into recovery using my roms reboot into recovery option.
2. My kindle fire is in a state of it can't turn on unless it is plugged into a computer/charger.
3. I don't see "kindle fire" in my devices on windows 7 and I don't see ADB composite device thing.
4. Using the install drivers.bat that is in the kindle fire utility says Driver name "Google, Inc (WinUSB) Status Ready to use.
5. I have tried the kindle fire utility to set boot mode to normal but adb and fastboot don't recognize it.
6. Also I've tried plugging into the computer with a factory usb cable and that also didn't work.
I'm wondering if i'm SOL.
Click to expand...
Click to collapse
You're fine.
First, charge the fire fully.
Second, read some of the threads in the development forum on getting it out of fastboot mode, because you are stuck in fastboot.
Third, do NOT reboot into recovery on the fire, it puts you into fastboot and....well you already see what that looks like.
Fourth, plug your fully charged fire into your computer and issue the commands to take it out of fastboot.
Sent from my Amazon Kindle Fire using xda premium

the command would be:
"fastboot oem idme bootmode 4000"
and
"fastboot reboot"
if it says <waiting for device> power it off by holding the pwr button for ~20sec till it turns of - pwr on again - the command should resume and finish
a second pwr off/on will bring you back to normal

I can't turn the power off though. Holding it down for any amount of time won't turn it off, and I can't get the driver to install. I can't get it to recognize it as an ADB device or a kindle.

nevertheless - to stop the bootloop you will need to charge it
do you use the original wall charger ?
if not take care the replacement charger has ~1.8A
if you plug it to the charger it would be fine if you can turn it off for better charging
if you can't turn it off - leave it - try again to power off after an hour
what happens:
if you plug it to a power source it tries to start - battery breaks down - tries to start - ...

If I plug it in to any source pc or charger it turns on gets to the triangle and then reboots, and does that for as long as it's plugged in. I've had it plugged in like this for a few hours and the only way to "turn it off" is to unplug it.

yes - this is a sign for a empty battery - atm the search function is'nt working but there are ~20 threads with the same problem - it was allways the battery besides 1 or 2 where the battery was so deep empty that they had to return it
charging with the computer will not work in this situation - the computer delivers only 500ma - that is too few
you can try to switch it to fastboot mode because then it starts the bootloader and don't go further (so it uses fewer power) - this is done by issuing: "fastboot oem idme bootmode 4002" - then let it do a bootloop - it should pickup the command

The drivers won't install for the kindle fire though, I don't think it's going to work that way. I'll try it again, but I've done this like 5 times to no avail.

if the right drivers are not allready on the machine you can't install them until you get it to stable state
the only solution (besides a factory cable) to change the bootmode in this situation would be firekit - this is a special crafted ubuntu on a usb stick because linux don't need drivers
http://forum.xda-developers.com/showthread.php?t=1430038
maybe you want to give it a try ...

Okay, So I finally got my tab working! Charged it up through a charger for a little while. Booted into ubuntu 11.10 (32bit) with the firekit file and ran the install recovery script. It hung at waiting for device. I unplugged it and plugged it back in and tried turning it on and off and holding the power of the device for awhile and one time it just worked. Was able to reboot and boot into recovery and flash a rom.

good to hear that you got it working - good luck with your kf

[Q] stuck in ATX mode

I tried to downgrade from 3.2 with that tool and every time it shows me that the operation had failed
Now i am stuck in APX mode help

please anyone????

jimmis1996 said:
please anyone????
Click to expand...
Click to collapse
Reinstall your USB drivers and try again.
And make sure your tablet is in apx mode.
How :
Connect tablet with USB cable when it is off.
Now with paperclip press the reset button and power button together for 3 seconds, then release power button and one second later you release the reset button ( screen of tablet stays black but you will see that in device manager on your pc under USB devices you should see Acer Picasso recovery driver listed , then you know your tablet is in apx mode and connected.)
Now you can Start.

civato said:
Reinstall your USB drivers and try again.
And make sure your tablet is in apx mode.
How :
Connect tablet with USB cable when it is off.
Now with paperclip press the reset button and power button together for 3 seconds, then release power button and one second later you release the reset button ( screen of tablet stays black but you will see that in device manager on your pc under USB devices you should see Acer Picasso recovery driver listed , then you know your tablet is in apx mode and connected.)
Now you can Start.
Click to expand...
Click to collapse
i done it a lot of times but i still says tha the operation cannot be completed.
Could i leave APX mode and boot normally?

HELP PLEASE

OOF!!!!
Well i managed to boot again by using an other pc
Thanks for your help

Did I bricked my Kindle HD?

Hi all, I was following this thread to install bootloader and twrp:
http://forum.xda-developers.com/showthread.php?t=2271909
I thought i followed step by step but after flashing with fireflash, and reboot (turn off, turn on?), despite pressing volume up button, the kindle fire splash screen never turned blue and go no further.
Does this qualify as a brick? I guess I need to order the factory cable to recover....:crying:

ghpham said:
Hi all, I was following this thread to install bootloader and twrp:
http://forum.xda-developers.com/showthread.php?t=2271909
I thought i followed step by step but after flashing with fireflash, and reboot (turn off, turn on?), despite pressing volume up button, the kindle fire splash screen never turned blue and go no further.
Does this qualify as a brick? I guess I need to order the factory cable to recover....:crying:
Click to expand...
Click to collapse
Yea you need a fastboot factory cable. Then restore with Kindle Fire FirstAide and you can try again.

LinearEquation said:
Yea you need a fastboot factory cable. Then restore with Kindle Fire FirstAide and you can try again.
Click to expand...
Click to collapse
Not sure where I went wrong. Is there supposed to be a reboot button that I was supposed to press? Looks like I hard booted and that's causing the failure.

Nvidia Shield Pro Stuck in bootloop

OK here is what happened. I am running zulu99 full android os. Worked great. I downloaded an app from the Google play store to change the dpi. After I made the change to the dpi settings the app ask me to OK a reboot. Now my Shield TV Pro is stuck on a bootloop and I cant get it into hardware recovery. Any ideas on how to enter recovery another way? I tried unplugging the shield plugged the power back in . Then I hold down the power button for 3 seconds let the power button go and press it down again for a second. I tried this many times and I just end up back in bootloop. Is there any other way to get into fastboot to flash back to stock ? Or do I now have a paper weight ?
Thank you

milko002 said:
OK here is what happened. I am running zulu99 full android os. Worked great. I downloaded an app from the Google play store to change the dpi. After I made the change to the dpi settings the app ask me to OK a reboot. Now my Shield TV Pro is stuck on a bootloop and I cant get it into hardware recovery. Any ideas on how to enter recovery another way? I tried unplugging the shield plugged the power back in . Then I hold down the power button for 3 seconds let the power button go and press it down again for a second. I tried this many times and I just end up back in bootloop. Is there any other way to get into fastboot to flash back to stock ? Or do I now have a paper weight ?
Thank you
Click to expand...
Click to collapse
==========
HowTo Flash:
==========
Before flashing images from this build to your SHIELD, connect your SHIELD
via USB to the PC where you built this tree.
Next, put your SHIELD into fastboot mode using following method:
SW method:
Boot to android home screen
Connect the device to linux system
Open terminal(on linux)
Type "adb reboot bootloader" in terminal
HW method:
Disconnect power cable
Insert USB OTG cable and make sure to connect other end to a host PC
Connect power cable to SHIELD
Quickly start pressing power button for ~3 seconds
Do not hold the button and connect power supply afterwards
HDMI TV should be always connected to SHIELD
Alternative method:
Perform software shutdown on SHIELD by holding Power button for 10 seconds
Connect USB OTG cable to SHIELD
Start pressing power button for 3 seconds
HDMI TV should be always connected to SHIELD
Click to expand...
Click to collapse
source: http://nv-tegra.nvidia.com/gitweb/?...ob_plain;f=README_SHIELD;hb=rel-22r18-partner
I suggest you keep trying those methods. There's some issues with the current bootloader, so if you can't get it to work eventually you'll be stuck with having to rma it. If you get it working, I suggest you stop messing with it until after the next OTA, which is supposed to fix the bootloader issues.
Some of the issues are mentioned here, with a response from nvidia: https://forums.geforce.com/default/topic/893616/bootloader-issues

The HW method worked .
Thanks For the help !

Rooting Fire HD 8 (kamak) 6.3.1.2 - Bricked

Hi together,
thanks especially to xyz` and k4y0z for your effort and your contributions! This is amazing!
I have an Amazon Fire HD 8 (karnak) with FireOS 6.3.1.2 which I want to root, unlock and install LineageOS on.
With 6.3.0.0 on another tablet, I already performed this procedure successfully.
As k4y0z writes in https://forum.xda-developers.com/hd...nlock-fire-hd-8-2018-karnak-amonet-3-t3963496 that a hardware-change in combination with the soft-brick method could lead to a real brick rendering the device unusable, I went for the hardware method.
What I did:
1. Disconnect tablet
2. Run "bootrom-step.sh"
3. Shorten CLK to GND and at the same time connect the tablet to USB
4. I get the message to remove the short and confirm with ENTER
--> flashing occurs and I find myself in fastboot mode (the tablet also shows up when I do a "fastboot devices")
5. Run "fastboot-step.sh"
--> flashing of recovery and misc occurs, followed by a reboot
Then I see the "Amazon" logo flashing shortly and then the screen stays black. I tried pressing power and the volume-keys shortly, twice, for a long time, ... nothing happens.
If I disconnect and reconnect USB I see the "Amazon" logo flashing again. The device is not in fastboot mode, ("fastboot devices" shows no device) nor is it in adb mode ("adb devices" also shows no device).
Luckily the steps below can be performed again and the flash procedure happens again so I can always get into fastboot mode but then I'm stuck flashing the TWRP with the fastboot-step.sh...
I tried the files from karnak-3.0, karnak-3.0.1 as well as the original amonet-v2, all with the same issue.
Can anybody please shed some light here? What am I doing wrong? Is there anything else I can try or is the tablet unusable now (which I cannot believe as there is fastboot access).
I am in fact running Debian 10 on a VirtualBox on my MacBook with USB forwarding to the Virtual Machine but I'm not sure if that can be the issue as all the flashes are working just fine.
Thanks for your support!

How old is the tablet? Anything bought January or newer is potential unlock-blocked....

Thanks for your answer, Michajin.
The tablet was bought in February 2020. Does that mean I'm out of luck getting LineageOS to run on this tablet?
Would the error I am seeing fit the unlock-block? I had the feeling that all the installing went through just fine, just TWRP is not loaded correctly, right?
Thanks!
Michajin said:
How old is the tablet? Anything bought January or newer is potential unlock-blocked....
Click to expand...
Click to collapse

freddy40 said:
Thanks for your answer, Michajin.
The tablet was bought in February 2020. Does that mean I'm out of luck getting LineageOS to run on this tablet?
Would the error I am seeing fit the unlock-block? I had the feeling that all the installing went through just fine, just TWRP is not loaded correctly, right?
Thanks!
Click to expand...
Click to collapse
If the fastboot-step finishes as success you have TWRP (fastboot step is just the flashing of twrp replacing stock recovery). You should be able to hold the volume down and press the power button, this will boot the device into recovery.

Thanks, Michaejin! That did the trick. Pressing those buttons yesterday didn't help as the tablet was somehow turned on, now I disconnected and reconnected the battery and pressed VolDown + Power and got into TWRP!
Great! Thanks again!
Michajin said:
If the fastboot-step finishes as success you have TWRP (fastboot step is just the flashing of twrp replacing stock recovery). You should be able to hold the volume down and press the power button, this will boot the device into recovery.
Click to expand...
Click to collapse

freddy40 said:
Thanks, Michaejin! That did the trick. Pressing those buttons yesterday didn't help as the tablet was somehow turned on, now I disconnected and reconnected the battery and pressed VolDown + Power and got into TWRP!
Great! Thanks again!
Click to expand...
Click to collapse
You can also hold the power button for about 10 seconds to force a power down, so you should have to pull the cover off in case something goes wrong. Likely the device was stuck in preloader or bootrom.