Hello people!
I'm having a hard time here.
I've rooted my device, and instaled a recovery method (not the TWRP, a red letter one), wiped cache and dalvik, flashed jandycane room and now i'm stuck on loop triangle boot.
In KFU my device are online and in normal boot (4000), but any options seems to work. He don't appear o pc and i'm already removed a re installed the drivers.
PS: I don't flashed GApps.
I tryied to enter in recovery mode but I get this:
I'm trying to but, but when I try to enter in recovery mode, i get this:
The system cannot find the drive specified.
Failed to Copy 'files\rcmode' to 'data/local/rcmode' : permission denied
unable do chmode /data/local/rcmode: no such file or directory
/system/bin/sh: data/local/rcmode: not found
I'm lost here, please help!
Install TWRP
soupmagnet said:
Install TWRP
Click to expand...
Click to collapse
There is another way to install without thr KFU? In KFU nothings happens too, stay trying to switch to fastboot and stuck in that.
Reinaque said:
There is another way to install without thr KFU? In KFU nothings happens too, stay trying to switch to fastboot and stuck in that.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1638452
Sent from my Nexus 7 using Tapatalk 2
The TWRP.img file that comes with KFU is not TWRP. If I had to guess, it probably uses wget to download the file, for legal reasons? Maybe? Who knows? Replacing it with one downloaded from the TWRP website would probably be the easiest route.
soupmagnet said:
The TWRP.img file that comes with KFU is not TWRP. If I had to guess, it probably uses wget to download the file, for legal reasons? Maybe? Who knows? Replacing it with one downloaded from the TWRP website would probably be the easiest route.
Click to expand...
Click to collapse
I'm already tryied that, but when the KF try to switch to fastboot in order to install the TWRP, he stuck in there and nothing happens.
Reinaque said:
I'm already tryied that, but when the KF try to switch to fastboot in order to install the TWRP, he stuck in there and nothing happens.
Click to expand...
Click to collapse
You're going to have to clarify that a bit. Stuck where? The Kindle Fire screen? If so what does it look like?
The situation changes.
I dunno ecxactly i did, but my KF begins to stuck in the KF logo Screen, not anymore on loop triangles and windows begin to see my device.
So I tried the fastboot commands, but choose wrong:
fastboot -i 0x1949 oem idme bootmode 4000
and now my KF stuck in triangles loop again and the windows can't se him anyomre.
What does your Kindle Fire logo look like?
soupmagnet said:
What does your Kindle Fire logo look like?
Click to expand...
Click to collapse
Kindle Fire wrote on White and Orange.
But don't stuck there, after the logo disapear the triangles begin to turn in loop.
Try to pay attention. You are in normal bootmode, with a corrupt file system caused by CWM. When the device is "stuck" at the boot logo it is in fastboot. Fastboot mode is needed to install TWRP and a host of other activities. All of this you would understand if you had read the Kindle Fire for Beginners guide stickied at the top of the Kindle Fire General forum. You would have been directed to that page if you had read the sticky at the top of this forum, labeled "Before Asking For Troubleshooting Help...". With the exception of CWM acting up (arguably), these are the most basic of Kindle Fire problems and it is a waste of time for people to have to go over them constantly, and unecessarily.
soupmagnet said:
Try to pay attention. You are in normal bootmode, with a corrupt file system caused by CWM. When the device is "stuck" at the boot logo it is in fastboot. Fastboot mode is needed to install TWRP and a host of other activities. All of this you would understand if you had read the Kindle Fire for Beginners guide stickied at the top of the Kindle Fire General forum. You would have been directed to that page if you had read the sticky at the top of this forum, labeled "Before Asking For Troubleshooting Help...". With the exception of CWM acting up (arguably), these are the most basic of Kindle Fire problems and it is a waste of time for people to have to go over them constantly, and unecessarily.
Click to expand...
Click to collapse
I undestand that, but i'm trying to switch to fastboot without sucesses. Tryied everething i've read here, but i'm stuck on that.
Use CWM to reboot to fastboot
soupmagnet said:
Use CWM to reboot to fastboot
Click to expand...
Click to collapse
When I try to install the CWR in KFU, I got this:
When I try to instal the FF in KFU, I got this:
***********************************************
* FireFireFire Installer *
***********************************************
fff.bin is missing.
So we will download it for you!
wget: missing URL
Usage: wget [OPTION]... ...
Try `wget --help' for more opt...ad 'recovery\fff.bin'
< waiting for device >
Reinaque said:
I've rooted my device, and instaled a recovery method (not the TWRP, a red letter one),
Click to expand...
Click to collapse
The "red letter one" is CWM. You already have it installed. (I shouldn't have assumed you had access to it)
Reinaque said:
So I tried the fastboot commands, but choose wrong:
fastboot -i 0x1949 oem idme bootmode 4000
Click to expand...
Click to collapse
As I said before, that put you in normal bootmode. And, as it is said in the KFFB, you can only issue adb commands in normal mode. Issue the adb command to change the bootmode to fastboot (4002) or recovery (5001).
[Edit:]Use your command line to change the bootmode. If your computer won't detect the device for adb, there is a problem with the device drivers (also covered in the KFFB) and need to be reinstalled.
soupmagnet said:
The "red letter one" is CWM. You already have it installed. (I shouldn't have assumed you had access to it)
As I said before, that put you in normal bootmode. And, as it is said in the KFFB, you can only issue adb commands in normal mode. Issue the adb command to change the bootmode to fastboot (4002) or recovery (5001).
[Edit:]Use your command line to change the bootmode. If your computer won't detect the device for adb, there is a problem with the device drivers (also covered in the KFFB) and need to be reinstalled.
Click to expand...
Click to collapse
Yeah, I undestand that. The problem is that I don't know what I exactly donne to KF acept my commands. The only thing i've donne for sure is that I change the USB port, but I tryed again with no sucess.
I am stuck also at the Boot Triangles in loop - I am having the exact same problems as you are Reinaque, so just know your not the only one.
I have tried all of the different tools, but I am still stuck in the CM10 boot logo. Also I am stuck on "Waiting for device". My kindle is recognized by my computer on 4000 boot mode through KFU.... It won't allow me to write any commands through ADB... Stuck with you!
EDIT
It will not for the life of it let me get into fastboot!
Well, I don't know what to do anymore.
I tryed with another PC, installed the correct drivers and try almost every fastboot command with no sucess, the KF still don't aceppt the commands.
I will try something with firekit.
Damm, I really think that I lost my new KF =[
Reinaque said:
Well, I don't know what to do anymore.
I tryed with another PC, installed the correct drivers and try almost every fastboot command with no sucess, the KF still don't aceppt the commands.
I will try something with firekit.
Damm, I really think that I lost my new KF =[
Click to expand...
Click to collapse
You didn't lose your Kindle. Check your messages.
Related
My Kindle was rooted but I decided to try my hand at installing a custom ROM. However, the ROM I tried would not work and the screen stayed black. However, thanks to TWRP I could install Kindle from Amazon again. The installation went thru smoothly, or so I thought. Now, when I boot the Kindle, I see the Kindle Fire Logo and it stays there. The Computer can see the Kindle as an Android device, Android Composite Device. But Kindle Fire Utility cannot see it so I could try and re-install it again. Any suggestions?
Lacking information, so I'll just fill the voids with assumptions.
I *assume* you didn't wipe cache, dalvik-cache and most important when switching from a ROM to another, Factory Reset - this is the reason said custom ROM wouldn't work, and the reason flashing back update.zip (as you said you installed it, rather than restoring a backup) caused your KF to get stuck in a semi brick.
The most important question here is, do you have FFF installed?
If you do, fixing this is trivial. Just get into TWRP from FFF, wipe cache, dalvik-cache and factory reset and then install whatever ROM you'd like to try or use.
If you don't have FFF installed, then your solutions are to either get a factory cable (recommended) or to crack open the case and do the USB pin short trick. From there you can use fastboot to install FFF and boot into TWRP.
Alternatively, you can try "fastboot getvar product" or "adb shell idme bootmode 5001" to see if you get lucky.
Dasanko said:
Lacking information, so I'll just fill the voids with assumptions.
I *assume* you didn't wipe cache, dalvik-cache and most important when switching from a ROM to another, Factory Reset - this is the reason said custom ROM wouldn't work, and the reason flashing back update.zip (as you said you installed it, rather than restoring a backup) caused your KF to get stuck in a semi brick.
The most important question here is, do you have FFF installed?
If you do, fixing this is trivial. Just get into TWRP from FFF, wipe cache, dalvik-cache and factory reset and then install whatever ROM you'd like to try or use.
If you don't have FFF installed, then your solutions are to either get a factory cable (recommended) or to crack open the case and do the USB pin short trick. From there you can use fastboot to install FFF and boot into TWRP.
Alternatively, you can try "fastboot getvar product" or "adb shell idme bootmode 5001" to see if you get lucky.
Click to expand...
Click to collapse
I tried the USB pin short trick but now my Kindle won't turn on at all nor will it charge. Thanks anyways!
i have similar problem ......please need help
After successfully rooting kf with kfu and making a backup ... I did factory reset and flashed a custom rom ... now kindle is stuck on " kindle fire" logo and just keeps flashing and rebooting . My computer recognizes it as android phone ( android adb ) and kfu does too but only for a couple of seconds . During those few seconds I try recovery ... fast boot ...normal boot... n none seem to work . Kf just reboots n returns to boot loop . Any advice is appreciated .. thanks
Start a new thread when you're posting your own issues.
What colour is the "kindle fire" logo when you turn on your KF?
Force Kindle into Fastboot
Ok, so I have finally got my Kindle to turn on, using the USB Short Trick. Now my only question is about getting the Kindle to boot into fastboot mode so I can re-format the sdcard partition and finally load a new ROM. I have tried several different commands and they all seem to miss the window of opportunity to start the kindle in fastboot mode. Is there any way, short of a factory cable, that one can make the kindle start in fastboot mode?
Not fastboot get var
ComputerGenuis2.0 said:
Ok, so I have finally got my Kindle to turn on, using the USB Short Trick. Now my only question is about getting the Kindle to boot into fastboot mode so I can re-format the sdcard partition and finally load a new ROM. I have tried several different commands and they all seem to miss the window of opportunity to start the kindle in fastboot mode. Is there any way, short of a factory cable, that one can make the kindle start in fastboot mode?
Click to expand...
Click to collapse
fastboot getvar product doesn't seem to do the trick. The kindle seems to be in fastboot mode but the adb shell cannot access the device.
The problem is that you don't have the fastboot drivers installed (also, ADB will not work while fastboot is active) - Windows is painfully slow at detecting a device and installing its drivers, so by the time it even notices anything, the fastboot window is already over.
To solve this, use firekit: http://forum.xda-developers.com/showthread.php?t=1430038
The script that will probably suit your needs the most is usb_install_fff_twrp.
Used Firekit
Dasanko said:
The problem is that you don't have the fastboot drivers installed (also, ADB will not work while fastboot is active) - Windows is painfully slow at detecting a device and installing its drivers, so by the time it even notices anything, the fastboot window is already over.
To solve this, use firekit: http://forum.xda-developers.com/showthread.php?t=1430038
The script that will probably suit your needs the most is usb_install_fff_twrp.
Click to expand...
Click to collapse
I have TWRP and FFF installed. However, upon booting into TWRP, the sdcard partition cannot be mounted, to the Kindle that is, and as such, I cannot mount the sdcard to the computer. When I researched this some more, I found that I can fix this by using a command via adb shell. The guide instructed using fastboot to achieve this. When would be the best time to use adb shell?
What's the output of partitions.txt? (type the following from TWRP)
adb shell parted /dev/block/mmcblk0 p > partitions.txt
Can't use adb
Dasanko said:
What's the output of partitions.txt? (type the following from TWRP)
adb shell parted /dev/block/mmcblk0 p > partitions.txt
Click to expand...
Click to collapse
The problem at hand is using adb. I can never time it exactly right to open adb. I always get an "error: device not found". Windows even recognizes that Android ADB Interface is plugged in.
Okay, things are getting awfully confusing here.
What exactly is it that you can do and that you cannot do?
For example, are FFF and TWRP functional?
GOT IT!
Thank you! I finally figured out that the wrong driver had reinstalled and that was causing my computer to not be able to use adb shell. I fixed that and voila, I am now running CM9. Thanks again!
Hi,
I tried to install the original ROM by TWRP but the process stopped and the kindle fire rebooted.
Now it is stucked on orange boot logo.
When I try to invoke ANY command on KFU, on the screen appears the message <waiting for device>
When I try to invoke ANY "fastboot" command manually, on the screen appears the message <waiting for device>
If I delete the windows drivers and plug the device, I can see the memory but I can't read the content and I can't write any file.
If I install the drivers from the KFU folder (install_drivers.bat), the devices is recognized correctly by the system, but I can't see the memory on pc resources(only on system)
Anyone has some ideas or suggestions in order to install TWRP or the original ROM On my kindle?
Could I solve my problem by a factory cable?
Thanks in advance
It's going to be important for you to figure out where your device is in the booting process when it gets stuck...
http://forum.xda-developers.com/showthread.php?t=1668159
If by "memory" you mean the storage area in the /sdcard partition and it can be mounted on the desktop, you are not going to be in fastboot mode. If it's trying to boot into the system software but it doesn't quite get there, you need to see if you can use an appropriate "adb shell" command to change the bootmode to fastboot. If you can't do that, your next best option is probably to get a factory cable and see if your bootloader can be put into fastboot mode. If what I just said in this paragraph doesn't make any sense to you, take a good look at the guide mentioned in the beginning of the post above.
kinfauns said:
It's going to be important for you to figure out where your device is in the booting process when it gets stuck...
http://forum.xda-developers.com/showthread.php?t=1668159
If by "memory" you mean the storage area in the /sdcard partition and it can be mounted on the desktop, you are not going to be in fastboot mode. If it's trying to boot into the system software but it doesn't quite get there, you need to see if you can use an appropriate "adb shell" command to change the bootmode to fastboot. If you can't do that, your next best option is probably to get a factory cable and see if your bootloader can be put into fastboot mode. If what I just said in this paragraph doesn't make any sense to you, take a good look at the guide mentioned in the beginning of the post above.
Click to expand...
Click to collapse
Thanks a lot for your answer...
The "memory" are the storage area of my Kindle, and it can be mounted on the desktop but is not accessible.
I have tried to boot the system in all fastboot mode (4000, 4002, 5001) but the system shows the <waiting for device> message. I have tried to activate the fastboot also using "adb" command, but I have the same result.
I could reinstall TWRP or the original ROM with the factory cable? When I plug my kindle by the factory cable my pc can communicate with it?
Thanks for your help
kinfauns said:
It's going to be important for you to figure out where your device is in the booting process when it gets stuck...
Click to expand...
Click to collapse
You look like you could use some help figuring this out.
kinfauns said:
Recognizing fastboot mode
The Display - As the bootloader loads up on the device, one of the previously mentioned bootlogos will appear on the display. With fastboot mode enabled, that bootlogo will be persistent and remain bright on the display. If the display blacks out and redisplays the bootlogo with the backlight slightly dimmed, the bootloader has bypassed fastboot mode and moved on in the boot process.
Click to expand...
Click to collapse
Now, are you in fastboot or not?
The orange logo is persistent on the screen, but if i press for 20 sec the power button on reboot the display shows the orange logo, then the display blacks out and redisplays the bootlogo with the backlight slightly dimmed.
I think thant the kindle not is in fasboot mode...is correct?
alchemist said:
The orange logo is persistent on the screen, but if i press for 20 sec the power button on reboot the display shows the orange logo, then the display blacks out and redisplays the bootlogo with the backlight slightly dimmed.
I think thant the kindle not is in fasboot mode...is correct?
Click to expand...
Click to collapse
Anyone?
alchemist said:
The orange logo is persistent on the screen, but if i press for 20 sec the power button on reboot the display shows the orange logo, then the display blacks out and redisplays the bootlogo with the backlight slightly dimmed.
I think thant the kindle not is in fasboot mode...is correct?
Click to expand...
Click to collapse
No, it's not in fastboot mode. Use the Fastboot guide I referred to earlier and try to get the system to set the bootmode to fastboot. This is your next best option to getting the device fixed. I'm pretty sure you have an unrooted stock device, so you'll have to use pokey9000's fbmode. If you can't get it to fastboot mode this way, you need a factory cable. If you don't have a factory cable and you can't make or buy one, then the only option you have left is to open up the case and use Firekit. All of this is detailed in the Fastboot guide. I highly recommend you try using the factory cable.
Once you get the device into fastboot mode, you'll need to follow this guide to flash TWRP and FFF again...
http://forum.xda-developers.com/showthread.php?t=1638452
Once you've done that, the same guide contains instructions on how to revert back to the stock software. Follow those instructions carefully and it will walk you through the process.
Kindle fire stuck on boot logo...the device is corrupted? [SOLVED]
Problem solved by factory cable. In fastboot mode I have installed TWRP and I have launched the restore of a old backup (boot and data).
My Kindle is alive!
Thanks a lot for help.
alchemist said:
Problem solved by factory cable. In fastboot mode I have installed TWRP and I have launched the restore of a old backup (boot and data).
My Kindle is alive!
Thanks a lot for help.
Click to expand...
Click to collapse
I have an other problem. In Kindle Fire Utility the kindle is always offline, and the boot status is unknow (and I can't install FFF and EX Launcher...)
I tried to reboot in normal mode or fastboot mode with KFU and "fastboot" command, but my pc show <waiting device> message.
What kind of command I need to use?
The KFU problem is due to driver issues with Windows.
If you are booted normally, you can use the command line or Pokey9000's bootmode binaries from a terminal emulator to change your bootmode.
soupmagnet said:
The KFU problem is due to driver issues with Windows.
If you are booted normally, you can use the command line or Pokey9000's bootmode binaries from a terminal emulator to change your bootmode.
Click to expand...
Click to collapse
I tried this and it stopped the boot looping but stuck on the Boot Logo. I used the unbrick method and it went back to boot looping. I have restored my KF several times in the past but this one has really stumped me. I have never had this problem. Are there any other solutions out there?
Kindle Fire Stuck at Logo and Screen Flashing
hi i have a kindle fire that is stuck at the boot logo the screen is flashing every 3 seconds or so and the light is flashing as well it has stock everything but the soupkit is just stuck here at waiting for device
truckaveli said:
hi i have a kindle fire that is stuck at the boot logo the screen is flashing every 3 seconds or so and the light is flashing as well it has stock everything but the soupkit is just stuck here at waiting for device
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2166668
#31
thanks
soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=2166668
#31
Click to expand...
Click to collapse
thanks i will try this and see what happens i also have another kindle fire that is operational but the screen flashes randomly and the touch screen in the game sometimes jumps all over the place like i would be touching one area and a selection for another area comes up
Not working
i charged the kindle entire day still no change it wont even read in the system i am in ubuntu 12.04 nothing in soupkit is helping as it is just hanging <waiting for devices>
Did you follow the instructions? What steps did you take to charge it? Is it still on a 3 second bootloop?
hi all
I have a problem on getting TWRP to work properly.
I initially used BreakDroid to install TWRP, everything worked fine.
I tried to install the cm-11-20140512.1655-SKANKY-otter.zip OS but I first got the "error 7", fixed that, and then it was stuck at "updating package" (or similar)....
then I saw an updated version of TWRP, without realizing that it was for an asys TF101 tablet (http://forum.xda-developers.com/showthread.php?t=2434422)...I installed that and now twrp doesn't work because the screen is the wrong size and I can't get to various buttons including flash/wipe etc..
I can still mount it tho so I thought about using adb/flashboot...but I can't seem to override that version of TWRP.
...best part...i cannot restore the original amazon OS since I didn't do a backup (...i know...:angel
does anyone have any idea about how I can fix that and install a kitkat rom?
I have nandroid backup of stock in my list.
sd_shadow's collection of links for: Kindle Fire 1
Sent from my Amazon Kindle Fire using Tapatalk
sd_shadow said:
I have nandroid backup of stock in my list.
Click to expand...
Click to collapse
thanks for the reply.
I did look at it but my problem is that I don't need to backup the system, I need to be able to install a recovery tool (twrp or cwmr) that will allow me to flash a rom on my kindle.
my problem now is that I can't seem to be able to do that since the recovery I have is for a different tablet and the screen won't allow me to get to the right buttons...I can only turn the kindle on and off .
SbDROID2012 said:
thanks for the reply.
I did look at it but my problem is that I don't need to backup the system, I need to be able to install a recovery tool (twrp or cwmr) that will allow me to flash a rom on my kindle.
my problem now is that I can't seem to be able to do that since the recovery I have is for a different tablet and the screen won't allow me to get to the right buttons...I can only turn the kindle on and off .
Click to expand...
Click to collapse
you tried
with kindle fire in twrp, connected to mac
adb shell
su
idme bootmode 4002
reboot
# back in your PC shell
fastboot -i 0x1949 flash recovery openrecovery-twrp-2.6.3.1-otter.img
fastboot reboot
I don't have a mac, so commands might not be quite right
may want to read [GUIDE] Set up ADB and Fastboot on a Mac easily
and you will need openrecovery-twrp-2.6.3.1-otter.img
sd_shadow said:
you tried
with kindle fire in twrp, connected to mac
adb shell
su
idme bootmode 4002
reboot
# back in your PC shell
fastboot -i 0x1949 flash recovery openrecovery-twrp-2.6.3.1-otter.img
fastboot reboot
I don't have a mac, so commands might not be quite right
may want to read [GUIDE] Set up ADB and Fastboot on a Mac easily
and you will need openrecovery-twrp-2.6.3.1-otter.img
Click to expand...
Click to collapse
I did try to do that but
1)
adb shell
Click to expand...
Click to collapse
--> doesn't work and I get "error: device not found"
i did the "./android update adb" with "adb kill-server" and "adb start-server" but nothing changed..
2) I installed the img file anyway through
fastboot flash recovery
Click to expand...
Click to collapse
the img file but i still cannot get the twrp with the view for kindle...see attached image. i have NO ACCESS to some of the buttons, therefore I can't do much with it.
I would REALLY like to be able to install a CWM...i tried the one here http://forum.xda-developers.com/showthread.php?t=1454241 using
fastboot flash recovery cwm-file-here.img
Click to expand...
Click to collapse
but it gets to the boot page, I select "recovery" and then it's stuck with the kindle logo and the small "booting..." at the bottom of the screen...so I re-installed twrp even tho i still have that damn "build for Asus TF101 Series Tablets" (see attachment) warning on top!!
any help would be HUGELY appreciated!!
also, using "adb devices" I still can't see it.
Run this command from your computer with your kindle connected when you turn it on:
fastboot getvar product
The FFF bootloader temporarily enables fastboot as the device boots up. When you issue this command, it puts the device into permanent fastboot mode. Just flash the correct recovery after that:
fastboot -i 0x1949 flash recovery your-recovery.img
fastboot reboot
Duchman said:
Run this command from your computer with your kindle connected when you turn it on:
fastboot getvar product
The FFF bootloader temporarily enables fastboot as the device boots up. When you issue this command, it puts the device into permanent fastboot mode. Just flash the correct recovery after that:
fastboot -i 0x1949 flash recovery your-recovery.img
fastboot reboot
Click to expand...
Click to collapse
ok...that doesn't work...
I get the same problem, if I download the correct twrp from here http://teamw.in/project/twrp2/79 I get exactly the same screenshot I posted above..
and the cwm recovery is not available anymore so I don't really know how to fix this...without working recovery I can't install any rom!!
SbDROID2012 said:
ok...that doesn't work...
I get the same problem, if I download the correct twrp from here http://teamw.in/project/twrp2/79 I get exactly the same screenshot I posted above..
and the cwm recovery is not available anymore so I don't really know how to fix this...without working recovery I can't install any rom!!
Click to expand...
Click to collapse
When you are flashing TWRP image in bootloader/fastboot do you see sending ... writing... in command prompt?
like this?
sd_shadow said:
When you are flashing TWRP image in bootloader/fastboot do you see sending ... writing... in command prompt?
like this?
Click to expand...
Click to collapse
When I launch the fastboot flash in fastboot mode I do get nothing but the blank cursor on a new line, although I see the device with "fastboot devices". After a few min that was stuck then I turned it off and the first part came up saying " sending file" but then it gave me an error saying that the connection was lost...which makes sense cause i turned it off..
If instead I launch the command and THEN turn the kindle on it does show me the correct output in a couple of secs as your showed. But then even if I do fastboot reboot, it does reboot it but no correct recovery is loaded...still the wrong screen size... Very very frustrating...
And btw...thanks for bearing with me through this!!!
---edit---
Now that I think about it...the twrp screen, although the wring size, actually reflects the VERSION of twrp that I'm installing through fastboot...it's as if the twrp I got from here ( http://forum.xda-developers.com/showthread.php?t=2434422) controls the size of the screen while I'm able to change the version of twrp...I think that that is a recovery GUI for the Asus tablet, any idea if I can install another GUI?...hopefully this helps...
SbDROID2012 said:
When I launch the fastboot flash in fastboot mode I do get nothing but the blank cursor on a new line, although I see the device with "fastboot devices". After a few min that was stuck then I turned it off and the first part came up saying " sending file" but then it gave me an error saying that the connection was lost...which makes sense cause i turned it off..
If instead I launch the command and THEN turn the kindle on it does show me the correct output in a couple of secs as your showed. But then even if I do fastboot reboot, it does reboot it but no correct recovery is loaded...still the wrong screen size... Very very frustrating...
And btw...thanks for bearing with me through this!!!
---edit---
Now that I think about it...the twrp screen, although the wring size, actually reflects the VERSION of twrp that I'm installing through fastboot...it's as if the twrp I got from here ( http://forum.xda-developers.com/showthread.php?t=2434422) controls the size of the screen while I'm able to change the version of twrp...I think that that is a recovery GUI for the Asus tablet, any idea if I can install another GUI?...hopefully this helps...
Click to expand...
Click to collapse
Your guess is right, installing another TWRP version doesn't affect the theme you are using, unless it has a theme of its own. You could delete the ui.zip from the TWRP folder and that would solve it. The folder should be in sdcard.
Duchman said:
Your guess is right, installing another TWRP version doesn't affect the theme you are using, unless it has a theme of its own. You could delete the ui.zip from the TWRP folder and that would solve it. The folder should be in sdcard.
Click to expand...
Click to collapse
so..the problem with that is that I could not access the sdcard since adb doesn't work...however...as of now I've been able to fix the layout problem by using
fastboot -w
fastboot flash recovery twrp.2.7.0.1.img
fastboot reboot
Click to expand...
Click to collapse
once rebooting I had to re-wipe (advance wipe) sdcard/cache/data since when I tried to mount them I could not check the boxes.
now i STILL cannot mount it and adb does not recognize it.
I'm using mac and I tried
android update adb
Click to expand...
Click to collapse
but still adb can't see the kindle and I can't mount it through twrp
...however, I'm still able to reboot in bootloader and use fastboot
I don't think I can flash a .zip rom from fastboot tho...and I'm not sure how to transfer files on the kindle to flash them from twrp...any idea?
thanks a ton!!
-- edit --
i already modified the ~/.android/adb_usb.ini file adding 0×1949 and then running
adb kill-server
adb devices
but what I get is just
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
and nothing to it...the "adb shell" still gives me "device not found"!!
try flashing Cannibal Open Touch Recovery see http://forum.xda-developers.com/showthread.php?t=2025793
links are bad so uploaded my copy to http://d-h.st/XWy
sd_shadow said:
try flashing Cannibal Open Touch Recovery see http://forum.xda-developers.com/showthread.php?t=2025793
links are bad so uploaded my copy to http://d-h.st/XWy
Click to expand...
Click to collapse
SCORE !!!
dunno why twrp was the problem! the new recovery that you linked worked like magic, adb worked perfectly, I already flashed a rom and it works!!
so...why wouldn't twrp allow me to use adb or mount disks through usb?!
thanks so much for the help!!
Guessing it doesn't use the twrp theme, that was causing trouble.
Sent from my Amazon OtterX using Tapatalk
I've been trying to root my Kindle Fire running 6.3.3. I bought a fastboot cable and got it to boot into fastboot mode to flash TWRP and firefirefire. I ran the commands and TWRP failed but firefirefire installed. Now when the kindle boots I get the firefirefire bootloader but it cant boot into the recovery because the TWRP never installed. Also, I can't get it to fastboot anymore, not even with the cable. Can anyone please help me get TWRP installed? I've read many forums and tried about everything I found.
kas782000 said:
I've been trying to root my Kindle Fire running 6.3.3. I bought a fastboot cable and got it to boot into fastboot mode to flash TWRP and firefirefire. I ran the commands and TWRP failed but firefirefire installed. Now when the kindle boots I get the firefirefire bootloader but it cant boot into the recovery because the TWRP never installed. Also, I can't get it to fastboot anymore, not even with the cable. Can anyone please help me get TWRP installed? I've read many forums and tried about everything I found.
Click to expand...
Click to collapse
FFF bootloader supports fastboot commands, but the flash command is now
fastboot flash recovery file name
ie drop the -i 0x1949
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.1-otter.img
because the fastboot mode window is short
with kindle connected to pc, power off kindle, enter commands, then power on kindle
sd_shadow said:
FFF bootloader supports fastboot commands, but the flash command is now
fastboot flash recovery file name
ie drop the -i 0x1949
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.1-otter.img
because the fastboot mode window is short
with kindle connected to pc, power off kindle, enter commands, then power on kindle
Click to expand...
Click to collapse
I've been trying this for about 30 minutes or so with no luck...I even downloaded a different version of the twrp image. Do I have to wait for the fastboot screen to start the command or do I start the process before powering on the device? I'm not really sure what I'm doing wrong here.
kas782000 said:
I've been trying this for about 30 minutes or so with no luck...I even downloaded a different version of the twrp image. Do I have to wait for the fastboot screen to start the command or do I start the process before powering on the device? I'm not really sure what I'm doing wrong here.
Click to expand...
Click to collapse
Should be able to do it either way but I press enter, before the power button
This will not work if drivers are not correct
could try
Code:
fastboot devices
as a test should get something like
Code:
123456789 bootloader
back in command prompt
I finally got it to work and I can't thank you enough. You were right. I knew my computer recognized the device with adb in normal boot but my computer wouldn't recognize the device in fastboot mode until i reinstalled the android driver while it was in fastboot mode. Now I have a custom ROM running Google Play apps! Again, thank you!
Hey, I don't know if this will help others, but I had a hell of a time trying to get my kindle to recognize while in the bootloader/fastboot mode... It frustrated me so much that I had to write about it.
I recently switched to Windows 10, so it seems like my computer is relearning drivers and stuff...
My kindle was fine when on, and I could issue adb commands from the main screen, but when in fastboot mode, I couldn't get it detected. I knew the drivers were an issue, but I couldn't figure out how to do it. I looked at Amazon's support pages, went through the SDK route, tinkered with the adb.ini and so forth... to no avail.
Post after post said that the easiest way to install the drivers was through the Kindle Fire Utility, but for some reason, the drivers in the .bat file kept failing and would not load. It took a good few hours to figure out the solution.
When I asked the Web why the drivers kept failing, I came across a post that said Windows was actually blocking unknown drivers from loading onto my system. I really wish Windows had told me that instead of just saying "Fail"...
I had to hold down the shift button and click restart on the start menu, and when the computer restarted, I when through: troubleshoot -> advanced options -> startup settings and clicked on Restart. It eventually gave me the option to disable that signature verification [F7]
My explanation is crude, because I want you to look it up properly. Just search for "disable driver signature enforcement" and you should be fine.
Hope this helps others out. I may have to revisit my own post just to see how to do this again.
So i been trying to find the answer to my issue everywhere. everything i try fails.
So basically my Kindle fire hd 8.9 is in a constant boot loop. it goes from orange w/animation, then blue w/animation... then after a period of time it says that it cant boot gives me option to factory restore (which does nothing).
when i have it hooked up to a computer, it connects for 1 second, then quickly disconnects. In device manager it comes up as "jem-pvt-prod-04" with the yellow "!". i even tried to use the amazon drivers from another post on xda, in that split second it would appear in device manager, i would update device and point it to the driver. then i will get an error saying it encountered an error installing Android ADB interface. problem encountered while trying to add driver.
Does anyone have any tips for me. im kinda stuck here and desperate with a very expensive paperweight. very upsetting!
I never tried to root, or mod this kindle fire. this problem happened on its own. or possibly after an update of some sort.
thanks guys.
piffdaddy420 said:
So i been trying to find the answer to my issue everywhere. everything i try fails.
So basically my Kindle fire hd 8.9 is in a constant boot loop. it goes from orange w/animation, then blue w/animation... then after a period of time it says that it cant boot gives me option to factory restore (which does nothing).
when i have it hooked up to a computer, it connects for 1 second, then quickly disconnects. In device manager it comes up as "jem-pvt-prod-04" with the yellow "!". i even tried to use the amazon drivers from another post on xda, in that split second it would appear in device manager, i would update device and point it to the driver. then i will get an error saying it encountered an error installing Android ADB interface. problem encountered while trying to add driver.
Does anyone have any tips for me. im kinda stuck here and desperate with a very expensive paperweight. very upsetting!
I never tried to root, or mod this kindle fire. this problem happened on its own. or possibly after an update of some sort.
thanks guys.
Click to expand...
Click to collapse
You're not hopelessly bricked if your Kindle still boots to the orange logo.
Might I ask what Windows version you're using? Newer versions enforce driver signatures, and that enforcement will cause failed installations in Windows 8+ unless you disable the enforcement before installing the drivers. I would also suggest installing ADB and fastboot if you haven't already done so. (Use the 15 second ADB installer - it's on XDA, and it works wonders!)
Sent from my Amazon Jem using XDA Labs
monster1612 said:
You're not hopelessly bricked if your Kindle still boots to the orange logo.
Might I ask what Windows version you're using? Newer versions enforce driver signatures, and that enforcement will cause failed installations in Windows 8+ unless you disable the enforcement before installing the drivers. I would also suggest installing ADB and fastboot if you haven't already done so. (Use the 15 second ADB installer - it's on XDA, and it works wonders!)
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Yes, actually i am using windows 10. My thinkpad has windows 7, so i will try to do this using windows 7. i will post back with results. its funny, out of everywhere i looked nobody mentioned windows 8+ having to disable enforcement. actually it will probably just be easier just to disable the enforcement. ill give it a try and report back.
still no luck. i was able to install the driver. but it still does the same thing. only connects for 1 second when i first turn it on. idk where to go from here? any suggestions?
piffdaddy420 said:
still no luck. i was able to install the driver. but it still does the same thing. only connects for 1 second when i first turn it on. idk where to go from here? any suggestions?
Click to expand...
Click to collapse
Completely turn off the kindle and unplug it from your PC if it's connected. Open Command Prompt and type fastboot -i 0x1949 getvar product. Plug in the kindle when you see <waiting for device> outputted. The kindle should now boot into fastboot mode, from which point you can reflash the bootloader, TWRP, and the freedom-boot image in Hashcode's thread.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Completely turn off the kindle and unplug it from your PC if it's connected. Open Command Prompt and type fastboot -i 0x1949 getvar product. Plug in the kindle when you see <waiting for device> outputted. The kindle should now boot into fastboot mode, from which point you can reflash the bootloader, TWRP, and the freedom-boot image in Hashcode's thread.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
ok so im in fastboot mode now. i checked out that thread that you sent. but i have another problem, how am i supposed to get cm and gapps onto the kindle? is there a command i can use to put the files on the internal sd card? and i cant do the adb commands to push the stack, and do the other commands adb since i couldnt get it loaded to begin with, i am not able to enable developer mode. it would be nice if i could do those commands in fastboot mode. there has to be a way to do this....
maybe if someone can send me the stock partitions that they backed up stock boot partititons when they did it. maybe if i flashed them onto my kindle it will allow me to get it to atleast boot up so i can get into adb.
right now this is completely bricked.
can anyone help me? i just need the original boot loader, boot, recovery... basically whatever was backed up before you flashed it.
i aam looking for the original because i know mine was corrupt to begin with. my theory is if i load the original boot loaders and everything then maybe i can get into the kindle just so i can run the abd commands and then put cyanogenmod on it. unless someone has a suggestion on how i can get my device to be detected by adb ? the furthest i can get into is fastboot.
piffdaddy420 said:
can anyone help me? i just need the original boot loader, boot, recovery... basically whatever was backed up before you flashed it.
i aam looking for the original because i know mine was corrupt to begin with. my theory is if i load the original boot loaders and everything then maybe i can get into the kindle just so i can run the abd commands and then put cyanogenmod on it. unless someone has a suggestion on how i can get my device to be detected by adb ? the furthest i can get into is fastboot.
Click to expand...
Click to collapse
Once you're in fastboot, you should run these fastboot commands (most of which I ripped from Hashcode's thread) to flash the bootloader, etc.:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
fastboot -i 0x1949 oem recovery
after that, you should be in TWRP, from which point you can use ADB sideload (enable in TWRP through Advanced -> ADB sideload) to flash CM. After running ADB sideload, you need to re-enable it in TWRP for each subsequent zip you want to flash.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Once you're in fastboot, you should run these fastboot commands (most of which I ripped from Hashcode's thread) to flash the bootloader, etc.:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
fastboot -i 0x1949 oem recovery
after that, you should be in TWRP, from which point you can use ADB sideload (enable in TWRP through Advanced -> ADB sideload) to flash CM. After running ADB sideload, you need to re-enable it in TWRP for each subsequent zip you want to flash.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Yes, i did all of those steps, however i never did the final step the oem recovery one...
everytime i try it now the screen turns completely red and stays there.
piffdaddy420 said:
Yes, i did all of those steps, however i never did the final step the oem recovery one...
everytime i try it now the screen turns completely red and stays there.
Click to expand...
Click to collapse
That's going to be a problem... hold down the Kindle till it completely powers off. Then open command prompt, type fastboot -i 0x1949 getvar product , and plug in the Kindle when you see <waiting for device>. Does this get you into fastboot mode?
Sent from my Amazon Jem using XDA Labs
monster1612 said:
That's going to be a problem... hold down the Kindle till it completely powers off. Then open command prompt, type fastboot -i 0x1949 getvar product , and plug in the Kindle when you see <waiting for device>. Does this get you into fastboot mode?
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
yes it does
piffdaddy420 said:
yes it does
Click to expand...
Click to collapse
It sounds like you've got a newer bootloader that's been patched. Go ahead and download the files from Hashcode's thread, and type in all of the commands exactly as given in step 5. Those should fix the red screen issue and allow you to boot normally (or into TWRP, from which point you can ADB sideload CM).
Sent from my Amazon Jem using XDA Labs
monster1612 said:
It sounds like you've got a newer bootloader that's been patched. Go ahead and download the files from Hashcode's thread, and type in all of the commands exactly as given in step 5. Those should fix the red screen issue and allow you to boot normally (or into TWRP, from which point you can ADB sideload CM).
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
i followed that exact, i tried it a couple times before you even mentioned it. but i did it again, i redownloaded everything and did it again. just to be sure. but it still continues to do the same thing with the red screen. it goes from kindlefire for 2 seconds then red screen comes across it and stays red. idk what to do. i am so upset.
piffdaddy420 said:
i followed that exact, i tried it a couple times before you even mentioned it. but i did it again, i redownloaded everything and did it again. just to be sure. but it still continues to do the same thing with the red screen. it goes from kindlefire for 2 seconds then red screen comes across it and stays red. idk what to do. i am so upset.
Click to expand...
Click to collapse
Do you happen to have any stock OS backups? If you do, you should remain able to flash those over fastboot.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Do you happen to have any stock OS backups? If you do, you should remain able to flash those over fastboot.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
no, i wish i did. the whole reason i started trying this was because the kindle was in a bootloop without even trying to flash it. it would go from kindlefire (orange) then blue, then it will ask me to do factory reset. and nomatter what i did i would keep going in the same bootloop.
so i turned to here for help, and following instructions now i am in this situation.
unfortunatley since i wasnt able to get into the kindle, i was never able to do any abd backups. so i just took my chances with it.
i was actually originally asking if anyone had the original files they can send me so i can try to flash those. atleast i can get it up and running because i really have a feeling this isnt working because i need to push the stack file over thru abd first.
piffdaddy420 said:
no, i wish i did. the whole reason i started trying this was because the kindle was in a bootloop without even trying to flash it. it would go from kindlefire (orange) then blue, then it will ask me to do factory reset. and nomatter what i did i would keep going in the same bootloop.
so i turned to here for help, and following instructions now i am in this situation.
unfortunatley since i wasnt able to get into the kindle, i was never able to do any abd backups. so i just took my chances with it.
i was actually originally asking if anyone had the original files they can send me so i can try to flash those. atleast i can get it up and running because i really have a feeling this isnt working because i need to push the stack file over thru abd first.
Click to expand...
Click to collapse
You should be able to separately flash the system.img, boot, and recovery from this tool via fastboot. It's stock OS 8.1.4, but it should work.
monster1612 said:
You should be able to separately flash the system.img, boot, and recovery from this tool via fastboot. It's stock OS 8.1.4, but it should work.
Click to expand...
Click to collapse
ok, it provided me with all the files except the bootloader. i did it step by step... but it only gave me original recovery, and original boot.img but it didnt give me the bootloader (and yes it is still turning red)
piffdaddy420 said:
ok, it provided me with all the files except the bootloader. i did it step by step... but it only gave me original recovery, and original boot.img but it didnt give me the bootloader (and yes it is still turning red)
Click to expand...
Click to collapse
anyone have any suggestions or can help me with my situation?? i am wondering if maybe someone could just send me the original backed up bootloader, boot, and recovery. i tried the original ones that were posted with that srt file. but it included everything but the bootloader. which is what i need. i know that in original thread they recommended to back up your original files (i was unable to do so because my kindle woulnt boot so i couldnt use adb to back up these files).
so if someone on here can send me the original files so i can try to get my kindle booted back up. that so far is my only theory because i tried everything else. i know people with advance knowledge would be able to help me in a heartbeat. any devs out there wanna help me out? i would greatly appreciate it!
anyone?