Related
Before you get all mad at me, I know there is another thread for this. This is a method that has worked for me when all other methods have failed.
I found out about this after looking around the interwebs for a while when my Kindle was stuck in a recovery loop, or stuck at the boot logo.
Your Kindle is stuck at the boot logo? I think I can help! Follow these steps!
This is WINDOWS ONLY for the time being!
1. Download and extract Kindle Fire Utility. You should be able to easily find it on the xda forums.
2. Reboot your PC.
2.5. If you have FIREFIREFIRE, go into the drivers folder in the Kindle Fire Utility and open up adb_usb.ini. Add the following line:
Code:
0x18d1
Do not delete the other lines.
3. After the reboot, connect your Kindle via USB. Go into where you unzipped Kindle Fire Utility, and run install_drivers.bat
4. Once that's done, open up a command prompt and navigate to the "tools" folder of the Kindle Fire Utility.
You do this by using this command:
Code:
cd (File path to tools folder)
Or in my case:
Code:
cd C:\Users\ZombiePiratez\Desktop\KFire Utility\Kindle Fire Utility\tools
5. After that, run the following commands:
If you DO NOT have FIREFIREFIRE, then use these commands:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
If you DO have FIREFIREFIRE
Code:
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
If all else fails, try these commands:
Code:
fastboot oem idme bootmode 4000
fastboot reboot
6. Hopefully by this point, your Kindle will be rebooting. THIS WILL NOT WORK FOR EVERYONE. Only people stuck at the bootlogo, or in a recovery loop.
Now, go have fun with your newly awesome and unbricked Kindle Fire!
What is firefirefire? Have yet to see a formal definition of that
androidcues said:
What is firefirefire? Have yet to see a formal definition of that
Click to expand...
Click to collapse
Its a bootloader
Sent from my Kindle Fire using xda premium
Thanks Man, I was messing around with CM7 and I rebooted into recovery not knowing that it would keep me in a recovery boot loop and KFU wasn't helping trying to help me.
Tierehl said:
Thanks Man, I was messing around with CM7 and I rebooted into recovery not knowing that it would keep me in a recovery boot loop and KFU wasn't helping trying to help me.
Click to expand...
Click to collapse
Happy to help
Zombiepiratez said:
Before you get all mad at me, I know there is another thread for this. This is a method that has worked for me when all other methods have failed.
I found out about this after looking around the interwebs for a while when my Kindle was stuck in a recovery loop, or stuck at the boot logo.
Your Kindle is stuck at the boot logo? I think I can help! Follow these steps!
This is WINDOWS ONLY for the time being!
1. Download and extract Kindle Fire Utility. You should be able to easily find it on the xda forums.
2. Reboot your PC.
2.5. If you have FIREFIREFIRE, go into the drivers folder in the Kindle Fire Utility and open up adb_usb.ini. Add the following line:
Code:
0x18d1
Do not delete the other lines.
3. After the reboot, connect your Kindle via USB. Go into where you unzipped Kindle Fire Utility, and run install_drivers.bat
4. Once that's done, open up a command prompt and navigate to the "tools" folder of the Kindle Fire Utility.
You do this by using this command:
Code:
cd (File path to tools folder)
Or in my case:
Code:
cd C:\Users\ZombiePiratez\Desktop\KFire Utility\Kindle Fire Utility\tools
5. After that, run the following commands:
If you DO NOT have FIREFIREFIRE, then use these commands:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
If you DO have FIREFIREFIRE
Code:
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
If all else fails, try these commands:
Code:
fastboot oem idme bootmode 4000
fastboot reboot
6. Hopefully by this point, your Kindle will be rebooting. THIS WILL NOT WORK FOR EVERYONE. Only people stuck at the bootlogo, or in a recovery loop.
Now, go have fun with your newly awesome and unbricked Kindle Fire!
Click to expand...
Click to collapse
Unfortunately this will only work if your windows based computer even recognizes the kindle, which mine doesn't. Thanks tho. I've given mine to my tech geek who has access to linux based system, so hopefully he will be able to recover my brick.
Sent from my MB860 using XDA App
Sorry about that. I wish I could help.
I am a newbie. I recover my kf using the recovery boot with kfu and it works fine now. how could
I know if it is in the recovery boot loop? Many thanks.
Sent from my GT-I9100 using XDA App
Zombiepiratez said:
Sorry about that. I wish I could help.
Click to expand...
Click to collapse
Its ok. I read everywhere its impossible to brick a kindle so im hoping that's true.
Sent from my MB860 using XDA App
My Windows PC wouldn't recognize my KF stuck in recovery mode, either. I think it reported in as an "unknown USB device" or something. I had to shut down the Kindle and then plug the USB in, which for whatever reason got my computer to recognize it. I think it might be similar to the effect of a battery drain?
*Snip*
Double post, fail.
CiggyPipe said:
My Windows PC wouldn't recognize my KF stuck in recovery mode, either. I think it reported in as an "unknown USB device" or something. I had to shut down the Kindle and then plug the USB in, which for whatever reason got my computer to recognize it. I think it might be similar to the effect of a battery drain?
Click to expand...
Click to collapse
Did it just immediately recognize it, or did you have to re-install drivers? And i'm not sure about the battery drain thing...
CiggyPipe said:
My Windows PC wouldn't recognize my KF stuck in recovery mode, either. I think it reported in as an "unknown USB device" or something. I had to shut down the Kindle and then plug the USB in, which for whatever reason got my computer to recognize it. I think it might be similar to the effect of a battery drain?
Click to expand...
Click to collapse
Tried that to no avail as well.
Sent from my MB860 using XDA App
Zombiepiratez said:
Did it just immediately recognize it, or did you have to re-install drivers? And i'm not sure about the battery drain thing...
Click to expand...
Click to collapse
I guess I should make note that by this point I'd uninstalled the driver I used. It was recognized as "kindle" once after I plugged it in while off, so then I went ahead and manually reinstalled the driver (from Jayce Ooi's site), which allowed the fastboot commands to work. Otherwise, the command would hang at <waiting for device>.
Thanks! My kindle fire was stuck at the firefirefire logo. My computer couldn't even recognize my kindle but I uninstalled the Android ADB composite interface and plugged it back in, when the kindle was off. Then I used your commands to get fastboot. I installed TWRP, now I'm stuck in TWRP and can't mount my sd... to flash any rom.
Thanks
Thanks for the info. i thought i'd bricked it and the info worked a treat. that will teach me to keep my mouth shut "of course i can root your kindle"
try fixing permissions under advanced, and then make sure only the sdcard box is marked in mount option.
Sent from my Amazon Kindle Fire using xda premium
Zombiepiratez said:
Before you get all mad at me, I know there is another thread for this. This is a method that has worked for me when all other methods have failed.
I found out about this after looking around the interwebs for a while when my Kindle was stuck in a recovery loop, or stuck at the boot logo.
Your Kindle is stuck at the boot logo? I think I can help! Follow these steps!
This is WINDOWS ONLY for the time being!
1. Download and extract Kindle Fire Utility. You should be able to easily find it on the xda forums.
2. Reboot your PC.
2.5. If you have FIREFIREFIRE, go into the drivers folder in the Kindle Fire Utility and open up adb_usb.ini. Add the following line:
Code:
0x18d1
Do not delete the other lines.
3. After the reboot, connect your Kindle via USB. Go into where you unzipped Kindle Fire Utility, and run install_drivers.bat
4. Once that's done, open up a command prompt and navigate to the "tools" folder of the Kindle Fire Utility.
You do this by using this command:
Code:
cd (File path to tools folder)
Or in my case:
Code:
cd C:\Users\ZombiePiratez\Desktop\KFire Utility\Kindle Fire Utility\tools
5. After that, run the following commands:
If you DO NOT have FIREFIREFIRE, then use these commands:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
If you DO have FIREFIREFIRE
Code:
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
If all else fails, try these commands:
Code:
fastboot oem idme bootmode 4000
fastboot reboot
6. Hopefully by this point, your Kindle will be rebooting. THIS WILL NOT WORK FOR EVERYONE. Only people stuck at the bootlogo, or in a recovery loop.
Now, go have fun with your newly awesome and unbricked Kindle Fire!
Click to expand...
Click to collapse
I'm sorry but I tried all the steps above but KF's still stuck at boot logo. I flashed CM9 stock kernel 3.0 with FFF 1.4a and CWR, wiped everything and factory reset, then install...but it just hangs at the blue skating droid logo... any idea?
jamesphan said:
I'm sorry but I tried all the steps above but KF's still stuck at boot logo. I flashed CM9 stock kernel 3.0 with FFF 1.4a and CWR, wiped everything and factory reset, then install...but it just hangs at the blue skating droid logo... any idea?
Click to expand...
Click to collapse
The Unbrick utility won't help in your case. When the device hangs at the boot animation or goes to a blank screen afterwards, the problem is usually one of three things.
* the rom installed is corrupted
* you didn't wipe the necessary data before installing
* you tried flashing a rom that's incompatible with the recovery you are using (I'm betting this is most likely the case)
Try installing a different rom (preferably non-ICS) to see if that fixes the problem. Of so, check to see if you're using the latest version of CWM by Hashcode or install TWRP to run ICS based roms.
Any further questions regarding this matter should be redirected to the Q&A section.
[Edit:] For some reason I thought this was the thread for the Unbrick Utility. Regardless, the solution is still the same.
You are a GENIOUS!!!
Thanks a LOT!!!!!!!!!!
Link to original thread: http://forum.xda-developers.com/showthread.php?t=1452651
This is a specific guide to restoring your Kindle Fire from boot loop caused by changes in the /system/ directory permissions.
The problem:
After rooting my Kindle Fire, I tried to install the Android Market app and while doing so, messed up my read/write permissions of /system/app/
After rebooting my Kindle, the logo animation started looping endlessly, indicating there was a serious issue taking place.
The specs:
Device: Kindle Fire
Firmware: 6.2.1
Desktop: Mac Mini
OS: OS X Lion
The tools:
You will need,
1. The KindleFireRoot Kit from here (It has tools for all OSs)
2. TWRP 2.0 from here
3. The fbmode file found here to be able to stock fastboot in 6.2.1
The steps:
1. Move all the contents from both the downloaded KindleFireRoot Kit and TWRP into a single directory for convenience.
2. Assuming you were able to root your Kindle in the first place, it's likely you already have drivers installed (Windows). Check by opening a Terminal, navigating to the dir with all the tools and doing this on Windows:
Code:
adb kill-server
adb devices
on Mac:
Code:
sudo ./adb kill-server
./adb devices
Your device should be listed. If it is skip to the next step.
If it's not, install the drivers found in the usb_driver directory (Win only). In this directory you can find the adb_usb.ini file which you need to move to the .android directory that's inside /Users/[your_name]/
3. We will now use the fbmode to fastboot to stock 6.2.1 as explained in this thread.
Code:
adb push fbmode /data/local/tmp
adb shell chmod 755 /data/local/tmp/fbmode
adb shell /data/local/tmp/fbmode
adb reboot
4. Now that we can fastboot, we will install TWRP 2.0.
Just run this command:
Code:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
...and reboot. The Kindle should boot into a screen with a yellow triangle and TRWP will install itself.
5. What you need to do now is tap the reboot button onscreen. As it reboots, hold down the Power Button until the light turns orange. You will then boot into TWRP. You will see a Menu with a bunch of Buttons.
6. Now it's time to boot up your Kindle as a USB Drive to repair the permissions.
Touch the Mount button and select the checkbox that says System. After that tap on Mount USB
All you have to do after that is type this in the Terminal and voila:
Code:
adb shell chmod 755 /systme/app
7. Reboot your device and enjoy.
Thanks to everyone who helped me figure that out in the original thread and the threads that I've linked. I might be missing a step. PM if you get stuck or just Reply on this thread.
/system/app kindle fire
Hi,
Thanks for the instructions. I got to the point where the yellow triangle shows up on my kindle fire after doing the fastboot command and touching the reboot button on the kindle screen. However, it just locks up after that and I never get to the subsequent menu. All I see is the yellow triangle on the screen with the instructions to press the power button for recovery. I have reset the power many times and all I get is the yellow fire triangle now. Any ideas how to get out of this loop? Thanks.
fastboot -i 0x1949 oem idme bootmode 5001
fastboot -i 0x1949 reboot
if you'r done you may have to reset the boot mode to normal (when you are in twrp):
adb shell idme bootmode 4000
adb reboot
Windows doesn't seem to be recognizing my device anymore. I get an unknown usb device when I plug it in. When I run the fastboot commands I get a <waiting for device> from which it never returns. I tried to reinstall my android_winusb.ini file to the kindle, but windows says it is up to date. Windows gives me this error in the device manager: " Windows has stopped this device because it has reported problems. (Code 43)" Help!
you have to update the driver manually:
http://forum.xda-developers.com/showpost.php?p=21720811&postcount=41
Thanks, that did it! I also had plugged it into another computer that recognized it as a kindle. I'm not sure if that mattered or not.
This seems to be great. Unfortunately I've got to a different thread and I think I totally bricked my Kindle. I was able to install and run TRWP. However I tried to do a recovery from Amazon Stock img. Then rebooted the kindle. After that the kindle rebooted and got stuck again. I tried to re-run TRWP but this time I got a different error message when tried to run adb shell to go into fastboot. The error message said the system shell could not be found. Adb shell is not accessible and if I do a fastboot command it says waiting for device.
If I do adb devices I can see the actual device # not anymore in recover mode but listed as device. But not able to run the adb shell. I am really frustrated!
that happend many others by trying to flash the original amazon rom
the original rom deletes fff, twrp and root
with a messed up system shell you have no possibility to get to fastboot mode
the only solution is to use a factory cable - you can build or buy one:
http://forum.xda-developers.com/showthread.php?t=1392693
the factory cable forces the kf to fastboot mode
restore with factory cable:
http://forum.xda-developers.com/showpost.php?p=21391952&postcount=38
handling:
http://forum.xda-developers.com/showpost.php?p=21708081&postcount=157
or in short:
You must insert cable, then switch off kindle by pressing button about 20sec and press once again, kindle will be in fastboot.
test with "fastboot getvar product"
After kindle will be in fastboot, with Kindle Fire Utility install TWRP recovery and with recovery install prerooted stock or CM7 firmware.
hi im new in this page and i was searching how to unbrick my kindle fire beacause i make 2 big mistake when i was rooting my kindle fire the last week the first was root twice my kindle fire beacuse the kindle was slow and i think i have to restore it to fabric mode and all my documents was erase it and i think ooooh i have too root again my kindle and in that moment i saw the vido of zedomax how root a 6.21 kindle fire and i do all in correct step but when i have to install the twrp my computer didnt let me upgrade the kindle to twrp because my computer recognizes my kindle fire like a android phone and all the step of zedomax erase the frimware of the kindle so i paid to a guy to repair my kindle and he only can install the twrp be didnt upgrade the frimware beacause the twrp didnt find the zip so i used the java kindle fire brick utilities and i uses the option of flash upgrade and now the kindle get stock in the yellow triangle and my coimputer recognizes the kindle fire like unknown device so what can i do for repair that brick? help me please!!!!!!!!!!!!!!!!!!!!!!!
first you have to get rid of your drivers (update manually):
under android phone it has to be "android adb interface"
cause your kf is in fastboot mode now
adb commands will not work in this mode
then you can try to follow this post starting at point 3:
http://forum.xda-developers.com/showpost.php?p=21803658&postcount=29
but the problem is know because konw my computer reconoigze my kf like unknown system
man the kindle fire isnt in fastboot beacause whe ni type "fastboot -i 0x1949 getvar product" the computer said me "fastboot cant be reconoigze like a command" what i can do please help me
eratos said:
man the kindle fire isnt in fastboot beacause whe ni type "fastboot -i 0x1949 getvar product" the computer said me "fastboot cant be reconoigze like a command" what i can do please help me
Click to expand...
Click to collapse
are you working with the sdk ? - the above message says that you dont have fastboot.exe in your current path - so you cant handle it when it is in fastboot mode.
would recommend to download kfu extract it to c:\ and rename it to "kfu" - now all necessary commands are in c:\kfu\tools - cd with a command promt to c:\kfu\tools and issue the necessary commands
if you have a driver problem you can also use the drivers from kfu - first you can try install_drivers.bat or install them manually - they are in c:\kfu\drivers\kindle
manually updating: http://forum.xda-developers.com/showpost.php?p=21720811&postcount=41
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
if your drivers are correct you can also use kfu - option1 - bootmode normal
If your kindle fire bricked after flashing nipad firmware or other firmware.you will see below two issues.
1.pc show kindle in device manager，can not install driver.
2.kindle fire show yellow fire logo in screen.
I think the kindle fire is under recovery mode(5002). So, You just change the boot mode to normal boot(4000). you can fix it.
how to fix：
1.find your adb driver files，select usbwin.inf to find kindle fire vid and pid.it is replaced 0x18d1 and 0x0100.after saving usbwin.inf you can install the driver
2.after installing，replug your usb cable.
3.you can type fastboot cmd to unbrick. some thing like fastboot oem idme bootmode 4000.
maybe you will see unknow device.this issue belong power key.if your kindle fire was power off，you will only see kindle in device manager.
After reading，do it！no bricks will appear.
good info thx for your post
does anyone have this issue?
Important
before do any fix brick or flash firmware. Please use the normal cable to charge your kindle fire at first. The 950ma charger is best. You charging time is 6-8H(battery empty). most confuse case can be solved!
xiaohewu said:
If your kindle fire bricked after flashing nipad firmware or other firmware.you will see below two issues.
1.pc show kindle in device manager，can not install driver.
2.kindle fire show yellow fire logo in screen.
I think the kindle fire is under recovery mode(5002). So, You just change the boot mode to normal boot(4000). you can fix it.
how to fix：
1.find your adb driver files，select usbwin.inf to find kindle fire vid and pid.it is replaced 0x18d1 and 0x0100.after saving usbwin.inf you can install the driver
2.after installing，replug your usb cable.
3.you can type fastboot cmd to unbrick. some thing like fastboot oem idme bootmode 4000.
maybe you will see unknow device.this issue belong power key.if your kindle fire was power off，you will only see kindle in device manager.
After reading，do it！no bricks will appear.
Click to expand...
Click to collapse
I was looking at this device driver distribution hoping to find something in here that would help people having fastboot problems. When compared to the set of files you'd get in KFU, this one is missing a couple of DLL files and some adb hardware IDs in the INF file.
I think most people would have already installed from KFU or used directions to install from SDK before looking at this set because in most cases, you'd need the adb drivers before the fastboot drivers. Maybe I'm just not understanding why you'd want to just install only the fastboot drivers and skip the adb ones?
kinfauns said:
I was looking at this device driver distribution hoping to find something in here that would help people having fastboot problems. When compared to the set of files you'd get in KFU, this one is missing a couple of DLL files and some adb hardware IDs in the INF file.
I think most people would have already installed from KFU or used directions to install from SDK before looking at this set because in most cases, you'd need the adb drivers before the fastboot drivers. Maybe I'm just not understanding why you'd want to just install only the fastboot drivers and skip the adb ones?
Click to expand...
Click to collapse
The method is not adb driver. it's only recovery mode fastboot driver. and donot need type -i 0x1949.
?
xiaohewu said:
If your kindle fire bricked after flashing nipad firmware or other firmware.you will see below two issues.
1.pc show kindle in device manager，can not install driver.
2.kindle fire show yellow fire logo in screen.
I think the kindle fire is under recovery mode(5002). So, You just change the boot mode to normal boot(4000). you can fix it.
how to fix：
1.find your adb driver files，select usbwin.inf to find kindle fire vid and pid.it is replaced 0x18d1 and 0x0100.after saving usbwin.inf you can install the driver
2.after installing，replug your usb cable.
3.you can type fastboot cmd to unbrick. some thing like fastboot oem idme bootmode 4000.
maybe you will see unknow device.this issue belong power key.if your kindle fire was power off，you will only see kindle in device manager.
After reading，do it！no bricks will appear.
Click to expand...
Click to collapse
how can i find the adb driver files?
visitor831 said:
how can i find the adb driver files?
Click to expand...
Click to collapse
in this mode, can not use adb. If the kf was booted, you can use the adb. below is the adb driver.
my problem is that when i used rom toolbox after flashing twrp recovery from hashcode (do all and dont flash the recovery only)for reset my tab into recovery. my tablet entered in a endless recovery, it charged but i could enter the os, then it was with few battery and i recharged it, then it had a few battery and i dont charged it, and now it dont boot, i charged it and nothing, i know that i can use fastboot but my device wasnt recognoized, so i think i will need the drivers. please help me
Kindle Fire HD and 2 First Aide Software - Noob (Simple) Version
persano said:
my problem is that when i used rom toolbox after flashing twrp recovery from hashcode (do all and dont flash the recovery only)for reset my tab into recovery. my tablet entered in a endless recovery, it charged but i could enter the os, then it was with few battery and i recharged it, then it had a few battery and i dont charged it, and now it dont boot, i charged it and nothing, i know that i can use fastboot but my device wasnt recognoized, so i think i will need the drivers. please help me
Click to expand...
Click to collapse
persano,
OK, so if I understand you correctly, you performed Hascodes steps to install TWRP Recovery and now your device loops the Recovery, correct?
If yes, plug in the Fastboot cable to the Kindle first then to your PC but first use our utility to install the drivers then proceed to recover the device.
Here is a link: http://forum.xda-developers.com/showthread.php?t=2096888
We have an option in the software to install the driver - do not use the backup or OTA disable feature, we are working on that function.
If you have trouble with that driver, which you should not but if you do, reply back and we will add instructions. Do Not worry, we will get you back online.
prokennexusa said:
persano,
OK, so if I understand you correctly, you performed Hascodes steps to install TWRP Recovery and now your device loops the Recovery, correct?
If yes, plug in the Fastboot cable to the Kindle first then to your PC but first use our utility to install the drivers then proceed to recover the device.
Here is a link: http://forum.xda-developers.com/showthread.php?t=2096888
We have an option in the software to install the driver - do not use the backup or OTA disable feature, we are working on that function.
If you have trouble with that driver, which you should not but if you do, reply back and we will add instructions. Do Not worry, we will get you back online.
Click to expand...
Click to collapse
the only option of drivers is the adb one
Kindle Bootloops After Installing TWRP On The Kindle
persano said:
the only option of drivers is the adb one
Click to expand...
Click to collapse
persano,
The ADB Driver and Fastboot driver are one of the same drivers, so having said this when you have a working ADB Driver, you will have a working Fastboot driver. Now, we have no idea what Hashcode did when developing TWRP on the Kindle, although he is a genius so I am sure he thought of everything.
Have you posted the issue in his Thread? He may have a way to recover TWRP directly since our Method will place you back to a stock Kindle.
prokennexusa said:
persano,
The ADB Driver and Fastboot driver are one of the same drivers, so having said this when you have a working ADB Driver, you will have a working Fastboot driver. Now, we have no idea what Hashcode did when developing TWRP on the Kindle, although he is a genius so I am sure he thought of everything.
Have you posted the issue in his Thread? He may have a way to recover TWRP directly since our Method will place you back to a stock Kindle.
Click to expand...
Click to collapse
yeah i posted in his thread
How To End A TWRP Bootloop
persano said:
yeah i posted in his thread
Click to expand...
Click to collapse
persano,
Any response yet? Here are some pointers that apply to TWRP on other Androids, so it should apply to your Kindle:
If you get stuck at a screen with a yellow triangle, run:
Code:
fastboot oem idme bootmode 4000 -i 0x1949
If your device is always booting TWRP run:
Code:
adb shell "idme bootmode 4000"
Step 1: If you still can't get out of booting TWRP (A Bootloop), first run:
Code:
adb shell "idme bootmode 4002"
Step 2: Reboot your device, then run:
Code:
adb shell "idme bootmode 4000"
Step 3: Reboot again and you should be out of your bootloop.
Please let us know if one of these solves your issue.
prokennexusa said:
persano,
Any response yet? Here are some pointers that apply to TWRP on other Androids, so it should apply to your Kindle:
If you get stuck at a screen with a yellow triangle, run:
Code:
fastboot oem idme bootmode 4000 -i 0x1949
If your device is always booting TWRP run:
Code:
adb shell "idme bootmode 4000"
Step 1: If you still can't get out of booting TWRP (A Bootloop), first run:
Code:
adb shell "idme bootmode 4002"
Step 2: Reboot your device, then run:
Code:
adb shell "idme bootmode 4000"
Step 3: Reboot again and you should be out of your bootloop.
Please let us know if one of these solves your issue.
Click to expand...
Click to collapse
but my tablet dont boot, it get out of battery after alot of bootloops
How To End A TWRP Bootloop
persano said:
but my tablet dont boot, it get out of battery after alot of bootloops
Click to expand...
Click to collapse
persano,
So at the moment you battery is dead or your Kindle is dead, period?
If the Kindle is dead and will no longer accept a charge, you will need to send it back to Amazon for replacement. If you are out of Warranty or concerned Amazon will not warranty the device, send it to our office and we will get you a new one. We know you are Argentina but if you send it vis UPS or FedEx we will get it quickly.
If you would like a new Kindle send us a PM and we will post our shipping address.
prokennexusa said:
persano,
So at the moment you battery is dead or your Kindle is dead, period?
If the Kindle is dead and will no longer accept a charge, you will need to send it back to Amazon for replacement. If you are out of Warranty or concerned Amazon will not warranty the device, send it to our office and we will get you a new one. We know you are Argentina but if you send it vis UPS or FedEx we will get it quickly.
If you would like a new Kindle send us a PM and we will post our shipping address.
Click to expand...
Click to collapse
thanks then i will see. i think hashcode is a killer developer xD
and how a new kinlde, what you will do with the old?
i bougth it from ebay, amazon will renplace it ?
How To Ship Th Kindle To Xerocomm, Inc.
persano said:
thanks then i will see. i think hashcode is a killer developer xD
and how a new kinlde, what you will do with the old?
i bougth it from ebay, amazon will renplace it ?
Click to expand...
Click to collapse
persano,
If you ship it to us, we will register the device to our business Amazon account, where we own 40 Kindles, then we will ask Amazon to replace it. The old Kindle will go back to Amazon for parts - we will take care of having the device swapped out for you. Be sure you De-register the device from your Amazon Account, if you did not register the device to Amazon better yet.
The only caveat is the Kindle need to be in excellent condition without signs of being dropped, otherwise Amazon will reject the replacement.
If Hashcode can not fix the problem, ship the Kindle (well packaged and insured) to us:
Xerocomm, Inc.
dba The Noob Series
Attn: Chris Bryant
1684 Northstar Drive
Petaluma, CA 94954-6603
USA
Main Phone: 707-774-5923
prokennexusa said:
persano,
If you ship it to us, we will register the device to our business Amazon account, where we own 40 Kindles, then we will ask Amazon to replace it. The old Kindle will go back to Amazon for parts - we will take care of having the device swapped out for you. Be sure you De-register the device from your Amazon Account, if you did not register the device to Amazon better yet.
The only caveat is the Kindle need to be in excellent condition without signs of being dropped, otherwise Amazon will reject the replacement.
If Hashcode can not fix the problem, ship the Kindle (well packaged and insured) to us:
Xerocomm, Inc.
dba The Noob Series
Attn: Chris Bryant
1684 Northstar Drive
Petaluma, CA 94954-6603
USA
Main Phone: 707-774-5923
Click to expand...
Click to collapse
in the box and with the usb?
its in exellent
II can add a bit to this discussion from what I gather in the bootloader / TWRP thread:
1. i believe that persano has only flashed the recovery.img and not the boot.img or the stack jump file to system. And then issued a "reboot recovery" in ROM toolbox which has probably set the bootmode to 3 or 5, i forget, but it will direct the stock bootloader to jump to recovery directly.
Unfortunately, without a boot.img (containing a 2nd bootloader) and a stack file to match, this ends with an unloadable recovery.img which will hang the device.
2. The solution (in any case) is to use a fastboot cable which will power the device regardless of battery charge and to enter fastboot mode. Which can be configured via the Android SDK install, and perhaps some reinstallation of USB drivers in the Windows device manager (should show "adb composite device").
Here you can flash back the stock recovery (and/or boot.img if needed) as well as reset the bootmode by entering:
fastboot -i 0x1949 oem idme bootmode 1
And all will be good as new.
Sent from my DROID RAZR HD using Tapatalk 2
Hashcode said:
II can add a bit to this discussion from what I gather in the bootloader / TWRP thread:
1. i believe that persano has only flashed the recovery.img and not the boot.img or the stack jump file to system. And then issued a "reboot recovery" in ROM toolbox which has probably set the bootmode to 3 or 5, i forget, but it will direct the stock bootloader to jump to recovery directly.
Unfortunately, without a boot.img (containing a 2nd bootloader) and a stack file to match, this ends with an unloadable recovery.img which will hang the device.
2. The solution (in any case) is to use a fastboot cable which will power the device regardless of battery charge and to enter fastboot mode. Which can be configured via the Android SDK install, and perhaps some reinstallation of USB drivers in the Windows device manager (should show "adb composite device").
Here you can flash back the stock recovery (and/or boot.img if needed) as well as reset the bootmode by entering:
fastboot -i 0x1949 oem idme bootmode 1
And all will be good as new.
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
but my tablet dont boot when i connect it
Hashcode said:
II can add a bit to this discussion from what I gather in the bootloader / TWRP thread:
1. i believe that persano has only flashed the recovery.img and not the boot.img or the stack jump file to system. And then issued a "reboot recovery" in ROM toolbox which has probably set the bootmode to 3 or 5, i forget, but it will direct the stock bootloader to jump to recovery directly.
Unfortunately, without a boot.img (containing a 2nd bootloader) and a stack file to match, this ends with an unloadable recovery.img which will hang the device.
2. The solution (in any case) is to use a fastboot cable which will power the device regardless of battery charge and to enter fastboot mode. Which can be configured via the Android SDK install, and perhaps some reinstallation of USB drivers in the Windows device manager (should show "adb composite device").
Here you can flash back the stock recovery (and/or boot.img if needed) as well as reset the bootmode by entering:
fastboot -i 0x1949 oem idme bootmode 1
And all will be good as new.
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
how to configure it in the sdk
persano said:
but my tablet dont boot when i connect it
Click to expand...
Click to collapse
With fastboot cable?
Maromi said:
With fastboot cable?
Click to expand...
Click to collapse
yeah
persano said:
how to configure it in the sdk
Click to expand...
Click to collapse
in the Android SDK manager
click tools
click manage add-on sites
click user defined sites
click new
paste this address
http://kindle-sdk.s3.amazonaws.com/addon.xml
Maromi said:
in the Android SDK manager
click tools
click manage add-on sites
click user defined sites
click new
paste this address
http://kindle-sdk.s3.amazonaws.com/addon.xml
Click to expand...
Click to collapse
and then
amazon will remplace it !!!!! yeah!!!!
i live in argentina but they will remplace it
How To Stop A Kindle Fire HD Bootloop
persano said:
in the box and with the usb?
its in exellent
Click to expand...
Click to collapse
persano,
No, just the tablet. First open a chat with Amazon, see if they will replace the device, if no, send it to us and we will have the device replaced.