Related
edit: Kindle Fire fastboot working. Allows for reflashing ROMs and booting over USB.
Recommended that you have your kindle already opened so that you can get to the battery cable to hard reset if necessary.
Instructions to follow.
transfuntioner said:
<posting here as i dont have access to devel forum yet>
Looking at the bootloader & the u-boot source, it looks like there's 2 ways to get to fastboot. The bootmode nvram setting, and a special usb cable.. I think I'll go the nvram route though I havent investigated how to set it yet.
Just to be prepared I'm going to add usb driver's inf.
%SingleBootLoaderInterface% = USB_Install, USB\VID_1949&PID_0FFF
So .. anyone else working on this?
Click to expand...
Click to collapse
I dont have a gingerbread build handy, is there another dev that can build me a fastboot.exe to include 0x1949?
I think my fire is stuck in fastboot mode.
transfuntioner said:
I dont have a gingerbread build handy, is there another dev that can build me a fastboot.exe to include 0x1949?
I think my fire is stuck in fastboot mode.
Click to expand...
Click to collapse
NVM on the fastboot.exe request, I have a working one.
fastboot mode is confirmed .. i have a fastboot talking to the fire. It shows up in 'fastboot devices' (the id is 0123456789abcdef), and responds to reboot & boot commands.
Now trying to boot out of fb mode, I should have set the 'other' nvram bootmode
NOTE: Instructions are terse and intended towards developers for now.
Standard disclaimer, I am not liable if you brick your fire.
Requisities:
- working adb, (on windows) with the additional %SingleBootLoaderInterface% entry mentioned
- working fastboot binary that recognizes / allows specifying the vendor id (0x1949)
- root. it may work without, but you probably want or have it already
Also recommended:
- boot.img from the latest sw update.
Procedure:
- get a adb shell
- use the '/system/bin/idme' command to set the bootmode. I suggest you first run 'idme ?' and write down your default, mine is "4000 0".
- if you set bootmode to 0x4002, the fire will stay in fastboot mode when it reboots
- if you set bootmode to 0x4003, it's supposed to timeout from fastboot mode, but I did not have much luck getting a normal boot after the timeout (did not play too much here).
- if you decide you dont want fastboot mode, run 'idme bootmode "4000 0"' to reset back to default for normal booting.
WARNING:
IF YOU REBOOT AT THIS POINT THE FIRE WILL BE IN THE FASTBOOT MODE. I HAVE NOT FOUND A WAY TO EXIT THIS MODE AND RETURN TO THE NORMAL OS WITHOUT A WORKING FASTBOOT CLIENT.
REPEAT:
YOU MAY BE BRICKED IF YOU DONT HAVE WORKING TOOLS.
When you boot into fastboot mode, it will show the "Kindle Fire" logo. The power button does not appear to do anything; therefore, if you boot a bad kernel/image it may get stuck and require a hard reset (pulling the battery cable).
You should now have access to the standard flashboot functionality (update, flash, usb boot, etc). Note that reboot-bootloader will bring you back to fastboot.
I currently use 'fastboot boot boot.img' (from the sw update) to get back to a working state. Once booted, use idme to disable fastboot.
Now, on to recovery's & custom roms!
so any more information on the "special usb cable" like what size resistor on pin 4?
death2all110 said:
so any more information on the "special usb cable" like what size resistor on pin 4?
Click to expand...
Click to collapse
I dont have hardware handy to determine this, but having a cable will definitely make things easier going forward.
Brief updates..
Unlike previously mentioned, it looks like long press power button typically should work.
The idme command is available in the bootloader. So you can set normal bootup mode from fastboot, then reboot. eg.
fastboot oem idme bootmode 4000
fastboot reboot
How to get latest update pack ?
Sent from my SAMSUNG-SGH-I777 using XDA Premium App
any idea what tools i can use to check what amount of resistance i need? I may just go out to the garage and grab 3 100k resistors and try the numerous SGS2 methods (specifically 3 resistors twisted together and jumping pins 4 & 5
Stuck in fastboot
Hello,
I followed these steps including adding the %SingleBootLoaderInterface% line mentions to the usb inf. I was able to get the Kindle Fire to set bootmode to 0x4002.
I downloaded fastboot from here, 32-bit only?
http://forum.xda-developers.com/showthread.php?t=463627
Tried to get fastboot 64-bit via this route, no good:
http://rootzwiki.com/topic/4551-guide-making-fastboot-work-on-64-bit-windows-7-systems/
Now that it's in bootmode, neither my x64 PC or x86 Mac can see the device via a recent fastboot.exe and fastboot-mac application using a standard mini-USB cable. Suggestions? Is there a different fastboot.exe that I should be using?
transfuntioner said:
NOTE: Instructions are terse and intended towards developers for now.
Standard disclaimer, I am not liable if you brick your fire.
Requisities:
- working adb, (on windows) with the additional %SingleBootLoaderInterface% entry mentioned
- working fastboot binary that recognizes / allows specifying the vendor id (0x1949)
- root. it may work without, but you probably want or have it already
Also recommended:
- boot.img from the latest sw update.
Procedure:
- get a adb shell
- use the '/system/bin/idme' command to set the bootmode. I suggest you first run 'idme ?' and write down your default, mine is "4000 0".
- if you set bootmode to 0x4002, the fire will stay in fastboot mode when it reboots
- if you set bootmode to 0x4003, it's supposed to timeout from fastboot mode, but I did not have much luck getting a normal boot after the timeout (did not play too much here).
- if you decide you dont want fastboot mode, run 'idme bootmode "4000 0"' to reset back to default for normal booting.
WARNING:
IF YOU REBOOT AT THIS POINT THE FIRE WILL BE IN THE FASTBOOT MODE. I HAVE NOT FOUND A WAY TO EXIT THIS MODE AND RETURN TO THE NORMAL OS WITHOUT A WORKING FASTBOOT CLIENT.
REPEAT:
YOU MAY BE BRICKED IF YOU DONT HAVE WORKING TOOLS.
When you boot into fastboot mode, it will show the "Kindle Fire" logo. The power button does not appear to do anything; therefore, if you boot a bad kernel/image it may get stuck and require a hard reset (pulling the battery cable).
You should now have access to the standard flashboot functionality (update, flash, usb boot, etc). Note that reboot-bootloader will bring you back to fastboot.
I currently use 'fastboot boot boot.img' (from the sw update) to get back to a working state. Once booted, use idme to disable fastboot.
Now, on to recovery's & custom roms!
Click to expand...
Click to collapse
I had the same issue....but i fixed it!
Code:
fastboot -i 0x1949 oem idme bootmode 0x4000
fastbooot -i 0x1949 reboot
Played with the 0x4003 fastboot "countdown" mode a bit. Seems like it is timing out of fastboot, but not continuing to boot up the rest of the way. After a few seconds the kindle fire logo goes away and the device no longer responds to fastboot commands. Waited maybe a minute or so after it left fastboot and it didn't boot. Though since you found that we can set the bootmode value from fastboot it doesn't really matter.
Also have been playing around with attempting to get my fire to boot a modified boot image. So far I've simply extracted the kernel/initrd from the 6.1 update boot.img and repacked it without modifications. Unfortunately the Fire refused to boot the resulting image.
Going to continue fiddling.
Well managed to successfully repack a boot.img.
The problem i was facing was caused by 2 issues while running mkbootimg.
1) Derped and didn't specify the correct page size (4096)
2) Needed to include a base address of 0x80000000.
wait i'm stuck in the phase where it times out after the kindle logo and it doesn't respond to fastboot commands... what did you do to get out of that?
any help would be GREATLY appreciated before my battery dies. i have my clockwork port saved on the sdcard!
or if somebody can upload their fastboot binary
edit: got it, i needed to specify the vendor id as mentioned on the bottom of page one
thanks to those who were trying to help me (although probably nobody as it's 3am...)
JackpotClavin said:
wait i'm stuck in the phase where it times out after the kindle logo and it doesn't respond to fastboot commands... what did you do to get out of that?
any help would be GREATLY appreciated before my battery dies. i have my clockwork port saved on the sdcard!
or if somebody can upload their fastboot binary
Click to expand...
Click to collapse
I did a long press of the power button and it turned off. Then before turning it back on i ran:
Code:
fastboot oem idme bootmode 4000
Let it sit in "waiting for device" and powered the kindle back on.
Attached my fastboot binary for linux if it's useful for you. It's compiled from AOSP with the 0x1949 vendorid added in.
I don't have the -i option on my version of fastboot. Could you post a windows version of the one you're using?
Edit: found version of fastboot.exe that supports -i in SDK_r07.
I can't post outside links yet, but here's the URL:
code.google.com/p/softy-warely/downloads/detail?name=android-sdk_r07-windows.zip&can=2&q=
Thanks death2all110. Got it to reboot to break out of the fastboot cycle.
New question:
I did fastboot -i 0x1949 boot recovery.img (from the Kindle 6.1 update) and now I can't fastboot back in to break out of the fastboot cycle again:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot -i 0x1949 oem idme bootmode 4000
< waiting for device >
I'm giving CM7 a shot right now. Gonna fastboot flash the system.img generated as well as the boot.img although I doubt this will work
death2all110 said:
any idea what tools i can use to check what amount of resistance i need? I may just go out to the garage and grab 3 100k resistors and try the numerous SGS2 methods (specifically 3 resistors twisted together and jumping pins 4 & 5
Click to expand...
Click to collapse
I dont think it'll hurt to try.. FWIW I didnt see anythign obvious in the source or from quick googling for the specs. Didnt spend a lot of effort on it though.
JackpotClavin said:
I'm giving CM7 a shot right now. Gonna fastboot flash the system.img generated as well as the boot.img although I doubt this will work
Click to expand...
Click to collapse
Yeah I am going to play with existing gingerbread builds as well because I dont think ICS will ever finish building on my machine!
I am planning on just flashing system.img and then usb boot with the stock kindle kernel / boot.img.
It didnt do anything, I found a Micro USB for LG Devices with selectable resistance. But I might buy an actual USB jig for the SGS2 but i dont want to waste my money on it if it doesn't work...
Hmm. Theres gotta be a way...
careful flashing
This may be known to experienced android devs but I thought I'd mention as I am not & just ran into it.
When you flash an individual partition you're limited by the ram, in this case the image size needs to be less than the value reported.
fastboot getvar downloadsize
downloadsize: 1d0000000
So around 486 megs.. just some extras steps needed if you're working with the 512M system partition.
I have bricked Kindle fire while trying to install Android Market. To the point that shell doesn't work.
I made myself a factory cable. So I can easily go into fastboot mode. I tried various ways that people post in different threads. None seem to work as expected.
Is there a way to completely flash the original amazon ROM in fastboot?
Update: fastboot gives me < waiting for device > now. I'm still using the same factory cable that I made myself and KF looks like it is in fastboot state - the logo shows up on the screen.
I will recheck factory cable a little later. Maybe it broke or something. Though KF still recognizes it and goes into fastboot mode.
Any ideas?
There seems to be very little help on how to use a factory cable. I am in a similar boat as you. Shell works for me but adb commands do not. I can't push or pull or install. I can navigate, change file names, and move files to some directories. My problem is that I don't know how to put the stock rom on and flash it. I actually have 6.2 on the sdcard but don't know what to do with it.
As for your problem, I experienced the same thing. adb devices didn't list my KF but I could see it in lsusb. I typed the usb description at $ "1949:0006 Lab126" and it called me an idiot or something but then I typed ./adb shell and vioala. I'm sure that didn't do anything and won't ever work again but there you have it.
I have a couple of open questions out there to see if we can get help and if I learn anything I will make sure you hear it next.
ToonaKan
Dmitry_G said:
Update: fastboot gives me < waiting for device > now. I'm still using the same factory cable that I made myself and KF looks like it is in fastboot state - the logo shows up on the screen.
I will recheck factory cable a little later. Maybe it broke or something. Though KF still recognizes it and goes into fastboot mode.
Any ideas?
Click to expand...
Click to collapse
You must insert cable, when switch off kindle by pressing button about 20sec and press once again, kindle will be in fastboot.
After kindle will be in fastboot, with Kindle Fire Utility v.6 install TWRP recovery and with recovey install stock or CM7 firmaware.
Admittedly, I am a little green when it comes to this but I never got it to list in fastboot devices either with a cable (and I am not sure I am supposed to), you can check if its connected in fastboot mode by:
fastboot -i 0x1949 getvar product
it should return "kindle"
from there I did:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
fastboot oem idme bootmode 4000
fastboot reboot
To get twrp up and running then I flashed the prerooted 6.2.1. Going back to the orginal rom should be similar
Ok. Passing "-i 0x1949" to fastboot helped and now I can communicate with KF in fastboot.
But a new problem has surfaced. I'm trying to install TWRP:
Code:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
It writes "downloading 'boot.img'" and gets stuck there. I waited for 15 minutes.
Ideas?
You need to now check to make sure your drivers are now up to date.
So it seems that I can't really do any operations with fastboot. Every command just freezes at the first thing it does. Weird.
I'm on a mac. I never installed any drivers for KF - it just worked. Do I even need a driver for KF on a mac?
There must have been something with the factory cable. I finally managed to load TWRP.
Now I'm trying to install stock ROM renamed to update.zip. I push it into /sdcard. Then in TWRP I tap on Install and select update.zip.
I get:
E:failed to mount /sdcard (Invalid argument)
E:Can't mount /sdcard/update.zip
What does that mean?
Ok guys. I found the solution. "E:failed to mount /sdcard (Invalid argument)" tells you that your sdcard is not formatted correctly. Here is the fix I did.
I already have TWRP installed and also have a factory cable. But I still have a few questions.
1. With a factory cable, is there any way to directly flash the stock firmware or do you always have to install and use TWRP?
2. From reading about TWRP, it seems that after installing it, you can then load the stock firmware onto the sdcard directory and then complete the restore operation. As a safeguard, and to make things easier, I have already put a copy of 'update.zip' on there just in case I need it. My question is - on an unrooted Fire, would it not be a good idea to stick 'update.zip' on the sdcard before rooting? That way if something goes wrong, all you need to do is get TWRP on there and the restore file is already in place. Or am I being overly cautious?
As a disclaimer, I've searched for this question, but have only found when the question is asked as a much broader topic and goes unanswered.
That being said, I can't seem to get TWRP 2.0 installed through using "fastboot boot", the Kindle Fire Utility, or the technique using dd to rewrite the contents of the parttitions.
The closest I've come is getting FIREFIREFIRE to start up using the "dd" technique, but TWRP still will not start when I hit the power button for recovery. And yes, I did use "dd" on the TWRP image file as well.
Also, I even tried using fastboot to flash u-boot.bin onto the bootloader partition, and twrp onto the recovery partition. Still, I can get to the yellow, but no further into starting TWRP.
Any help would be appreciated. At current time, I have the stock bootloader and recovery partitions on the Fire and it is rooted.
Thanks.
maybe your in fastboot mode and hopefully your drivers are installed correctly you can use:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot oem idme bootmode 4000
fastboot reboot
this should bring you to normal bootmode
I've tried that in case there was an issue. In fact, if I don't press the power button during the yellow triangle, the Kindle Fire OS will start as normal after 10-15 seconds. So, it looks like the bootloader is working right and I'm in the correct bootmode. But, if I hold down the power on the yellow triangle (which is supposed to start TWRP), I just get stuck and nothing starts.
That being said, I think I'm in the correct bootmode.
if i don't remember wrong there is an issue with installing twrp with dd
i think you could retry the installation or simply use KFU (but don't use the drivers of kfu if you have working ones)
Thanks.. I'll give it another shot tonight, and then.
when the device starts and the Triangle appears, are you just pressing the power button once? or are you pressing it until it turns orange?
I have to press it a few times before it changes color to orange and then just let it alone. A long press doesn't work for me.
I can get it to turn orange. I think the long press worked for me on that one. Though, I do know I did the multiple presses as well and didn't get any further.
Is it possible that it might be goofed up because I used SuperOneClick for the original root on 6.2 instead of KFU?
not possible - had the same - rooted with superoneclick on 6.2 then updated
i think your twrp install failed - would retry
I finally figured out my problem. For whatever reason (which is still unknown to me), the Kindle Fire Utility was not able to properly download the twrp.img. The file that was downloaded was 8K (which I'm guessing was some sort of error web page). Anyway, I went straight to teamw.in and downloaded the latest version that clocked in at around 10MB, installed it via the "fastboot -i 0x1949 boot twrp.img" command and all is well now.
If anybody is having similar problems, you might want to check the size of the twrp.img file. 10M = good, 8K = bad.
vaporofnuance said:
I can get it to turn orange. I think the long press worked for me on that one. Though, I do know I did the multiple presses as well and didn't get any further.
Is it possible that it might be goofed up because I used SuperOneClick for the original root on 6.2 instead of KFU?
Click to expand...
Click to collapse
It turns orange the second it starts booting recovery. That's when you should let go. Holding the power button for ~30 seconds for any reason is a hard signal to the PMIC chip to power off.
good that it works again ...
please mark the subject of the topic (edit first post) to [Solved]
Ok, still have prob with kf...I think all i have on here is TWRP, so with some help from ppl on here i now have the KINDLE FIRE on screen. Still cant get anything else. So is there any way i could format & load any other program on here. I dont care about kindle fire i was going to root it again anyways. Please help .....
as long as you don't get adb working there is'nt much you can do
allready tried firekit ?
I see i tried the things you said well i think i did them right. iam not sure...
I done so much. I just dont know why it wornt pick it up, i can get it to see it on one computer but it has the yellow mark on it & then the other computer dont see it as kindle just as the phone. so even if it format it still wont help (its not like a computer you can load a program on it)
what is it when they get a cable when they brick them?
that is a factory cable - it forces the kf to fastboot mode
that will not help in your case because you can get to fastboot mode
and fastboot commands are working
you can't get adb commands to work - this is the problem !
firekit is'nt working eighter ?
ok i see i dont understand i had it on both of my compter and they work fine because i rooted the kindle on these. ther must be something with the way its loading on here. maybe i can try the other compter i have....
you'r talking about firekit ? other computer is a good choice anyway
did you allready read this one :
http://forum.xda-developers.com/showthread.php?t=1552547
it clears up how the kf is working
someone said something about turning off debuging on the computer what do you think?
???
don't know such a option on a computer/win system
Well someone said to mount and download Kindle OS 6.3 and it sould let me boot up. I loaded it backed it up installed it did averything i was told to......but still no work. it still boots up to kindle fire on screen but wont do anything else.
So anybody got anything else i can try?
you where able to copy a new rom to the kf ?
if so that is a great progress - would recommend this one:
http://www.mediafire.com/?8h485buu55cawc5
to clean up partitioning/restore factory partitioning you can use this, just use the newer rom linked above:
http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4
btw first boot after flashing can need up to half an hour
Hi, yes i was able to get the 6.3 update on here by doing mount and sending it as a drive F and it seam to be there. you say it mite take a long time to boot up with this one i wounder it its takes a long time with what i have on there now. maybe it just didnt have time, i did leave it for about 45 min.
This is the one i loaded on here already is this the same one? http://forum.xda-developers.com/showthread.php?t=1569298
the other download you have here sould it be done after the frist or before, I can do a lot of thing on here but some iam not sure if iam doing them the right way, i think that why it didnt get backup the frist time....
that is realy too long - would try to restore factory partitioning as suggested in my last post:
1. set bootmode to fastboot -> fastboot oem idme bootmode 4002
2a. if you'r not in fastboot now pwr off / on the kf - the command should resume and finish - a second pwr off / on should boot fastboot
2b. boot to fastboot -> fastboot reboot
3. download fff 1.2 and extract to your tools folder
4. update fff -> fastboot -i 0x1949 flash bootloader u-boot.bin
5. reboot -> fastboot reboot
6. restore factory partitioning -> fastboot oem format
7. set bootmode to recovery -> fastboot oem idme bootmode 5001
8. boot to recovery -> fastboot reboot
9. flash new rom in recovery -> look at the op of the rom what and when to purge something
10. set bootmode to normal -> fastboot oem idme bootmode 4000
11. pwr off / on the kf - the command should resume and finish - a second pwr off / on should boot up the new system
btw yes it is this one - i recommend and linked in the unsecure version
ok got this thing to this point and dont want to mess up but not sure what to do with bootmode, fastboot not sure where i need to go to get into them
updated my last post and gave you a pm
b63 said:
updated my last post and gave you a pm
Click to expand...
Click to collapse
YEAAAA iamback up and running.....thanks to b63......I want to give a big thanks to b63 for a lot of help with this. Work with me to get it going, getting on my computer and doing what needed to get done. I tried all the things others had said but didnt work. If anyone else is lucky to get help from him then get it, He is very helpfull. Again THANK YOU for all your help.
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.