Related
ive installed a rom and it wont boot (FC's loop), i tried to enter recovery (-vol and power when phone is off) but it keeps trying to boot, ive flashed loads of roms and entered recovery a fair few times so i dont know why i cant do it now!
Do you have the Android SDK or any other adb tool installed on your PC? If you do, try plugging the phone in to the USB port on the PC and open a command prompt.
Type this:
Code:
adb reboot recovery
Not sure if that will work if the phone doesn't boot into Android though. You might have to time it just right, to find a point when the phone responds to adb commands but before it reboots.
How far does the phone get before it reboots? Do you just get the splash screen, the bootanimation, or what exactly happens?
Actually, you might have more luck with using fastboot from a command prompt:
Code:
fastboot reboot-bootloader
First off, thanks to everyone on here who's posted numerous help guides that have helped me in the past. I've rooted several phones in the past and figuered I'd try to root and install Jelly Bean on a Kindle Fire I won at a work event (woohoo!).
The problem right now is the kindle is stuck in fastboot (no root, twrp installed) it boot into the non-animated white and orange "kindle fire" logo screen and stays there.
What I did to put it there:
On a Windows 7 machine, I used KFU 0.96. After reading instructions, I installed TWRP.
Since then, it is not repsonding to adb commands. It will mount the drive to the computer, and the drivers show it's using the correct one from Google Composite device.
After researching, I found someone who mentioned that after several restarts, and smashing "normal boot" commands thru adb while the kindle was starting up (and before it went unresponsive) he was able to move along. When I did this (with KFU), Kindle went into TWRP. From there I followed instructions on flashing pre-rooted 6.2.2 (as the guide indicated, doing wipes) but the flash always failed.
Assuming something wasn't working with Windows, I've gone home to my macbook running Ubuntu 12.04, and while installing SDK from Google, I can not figure out how to get the google sdk running. I followed this guide http://forum.xda-developers.com/showthread.php?t=1550414 but I can't get to step 5, I cannot get the Android SDK Manager to run!!
I have access to dozens of Windows computers, I'm fine with going back to them, but everything I've read makes me think I've got a better shot with Linux due to driver problems on windows.
Also, when I had TWRP loaded on the Kindle, and connected it to KFU 0.96 it said my boot mode was 0x5003.
fastboot commands will not execute. I'm sending them like this:
(Devices list)
[email protected]:~/Android/KR$ ./adb-linux devices
List of devices attached
???????????? no permissions
fastboot:
[email protected]:~/Android/KR$ fastboot getvar product
fastboot: command not found
Someone had a similar problem here- http://forum.xda-developers.com/showthread.php?t=1765546 but I want to see if I should follow that thread or try something else instead, before I go making more changes.
Thanks for reading! Will gladly send pizza to someone who can help
I'm not an expert at fastboot and adb stuff but I can try to help.
As far as I know, the Kindle needs to be in fastboot mode for you to be able to use fastboot commands. The boot mode has to be 4002.
Are you still able to connect to your Kindle using KFU?
veeman said:
I'm not an expert at fastboot and adb stuff but I can try to help.
As far as I know, the Kindle needs to be in fastboot mode for you to be able to use fastboot commands. The boot mode has to be 4002.
Are you still able to connect to your Kindle using KFU?
Click to expand...
Click to collapse
yes. but it also spits out "-exec '/system/bin/sh' failed: No such file or directory (2) -" when I send the command to reboot into fastboot 4002, the kindle then reboots, and has the white and orange "kindle fire" logo.
also: C:\KFU\tools>fastboot devices
returns blank, goes back to prompt. so I try
C:\KFU\tools>fastboot devices
< waiting for devices >
and does nothing
Where to now?
Josepho1997 said:
Try uninstalling and reinstalling the drivers. If your in fastboot mode, adb wont work. After reinstalling the drivers, type:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
If the drivers installed correctly, these commands should work and get you out of fastboot(which it seems your stuck in)
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
drivers installed. command input. no response. Id like to install screenshots, but I'm new user.
hardware driver reads Google ADB interface 4.0.0
c:\KFU\tools>fastboot -i 0x1949 oem idme bootmode 4000
< waiting for device >
.....nothing?!
wheelzr said:
yes. but it also spits out "-exec '/system/bin/sh' failed: No such file or directory (2) -" when I send the command to reboot into fastboot 4002, the kindle then reboots, and has the white and orange "kindle fire" logo.
also: C:\KFU\tools>fastboot devices
returns blank, goes back to prompt. so I try
C:\KFU\tools>fastboot devices
< waiting for devices >
and does nothing
Where to now?
Click to expand...
Click to collapse
"-exec '/system/bin/sh' failed: No such file or directory (2) -" means your system software is broken, so it probably won't boot. In addition, either the "sh" binary doesn't exist there or the KF is not mounting the system partition to let you execute "sh" to run "adb shell" commands. To clarify, you need "/system/bin/sh" to run any "adb shell" commands. Because you don't have access to it, you cannot change the bootmode this way. There is no "command to reboot into fastboot 4002"... you have to set the bootmode to fastboot (4002) and reboot it. Because you cannot run "adb shell" commands, you cannot change the bootmode. Your next reboot just boots into whatever the bootmode happened to be at the time you tried (but failed) to change the bootmode. All of this is spelled out here...
http://forum.xda-developers.com/showthread.php?t=1668159
It's very likely that you'll have to get a factory cable to force the device into fastboot mode... that is unless you want to open the back cover up and tinker with the motherboard.
Also, you have permission problems when you try to run adb. You either have to run adb as root, or use this guide...
http://forum.xda-developers.com/showthread.php?t=1475740
and set things up so a regular user won't need root privileges to access the USB ports.
kinfauns said:
"-exec '/system/bin/sh' failed: No such file or directory (2) -" means your system software is broken, so it probably won't boot. In addition, either the "sh" binary doesn't exist there or the KF is not mounting the system partition to let you execute "sh" to run "adb shell" commands. To clarify, you need "/system/bin/sh" to run any "adb shell" commands. Because you don't have access to it, you cannot change the bootmode this way. There is no "command to reboot into fastboot 4002"... you have to set the bootmode to fastboot (4002) and reboot it. Because you cannot run "adb shell" commands, you cannot change the bootmode. Your next reboot just boots into whatever the bootmode happened to be at the time you tried (but failed) to change the bootmode. All of this is spelled out here...
http://forum.xda-developers.com/showthread.php?t=1668159
It's very likely that you'll have to get a factory cable to force the device into fastboot mode... that is unless you want to open the back cover up and tinker with the motherboard.
Also, you have permission problems when you try to run adb. You either have to run adb as root, or use this guide...
http://forum.xda-developers.com/showthread.php?t=1475740
and set things up so a regular user won't need root privileges to access the USB ports.
Click to expand...
Click to collapse
So, witout popping the cover and screwing with the mobo this thing is bricked?
wheelzr said:
So, witout popping the cover and screwing with the mobo this thing is bricked?
Click to expand...
Click to collapse
</thread>
Just sold the kindle on craigslist for $40 as a bricked device.
wheelzr said:
Just sold the kindle on craigslist for $40 as a bricked device.
Click to expand...
Click to collapse
Oy vey... I'd give you $50 for the "brick" to be used to help others here.
kinfauns said:
Oy vey... I'd give you $50 for the "brick" to be used to help others here.
Click to expand...
Click to collapse
for real, I probably would have paid $50-60 too, it should be an easy fix with a factory cable. (which I already have one of after I bricked my kindle once)
Also, as a side note - Amazon will replace it for $100 "not under warranty" because you bricked it through the tinkering process.
Actually, it turned out better than I could have planned. I told the company whom gifted to me t did not work, they sent a bike ,messenger to exchange it for me! Naturally the first thing I did with the new one was fire up kfu .96 and it worked perfectly this time. Stoked on this hashtaag jelly bean ROM. Hate the keyboard tho. And Google cards are fc'ng.
Love life.
Sent from my Amazon Kindle Fire using xda app-developers app
Hey folks! First, thanks for all of your hard work on this! I'm surprised at how active these forums are even with developers moving on to newer tablets - it's really impressive to have such an active community!
My problem:
Kindle won't boot; not recognized by ADB or FastBoot on multiple computers/OS's. Likely bad bootloader but can't push stock bootloader without ADB/FastBoot.
How I got there:
Alright, so, I recently received a Kindle HD 8.9" from a friend and tried to unroot it in Windows. I didn't get very far with multiple attempts and, eventually, got to a place where the adb labeled the device as "offline." After updating the SDK and adb, uninstalling and reinstalling drivers and so on, the Kindle was still listed as "offline." Tried different USB ports and so on, still offline, so I followed the "try a different computer" advice. Fed up and remembering how easy it was to unroot and mod my old Evo 4G in OS X, I decided to boot into OS X.
I quickly came across BreakDroid (KindleWater), which one thread or another suggested would work with the Kindle Fire HD 8.9". I started it up and got further than I had ever gotten before but with errors - the flash at the end of the "Step 1" script worked, but there were permissions error prior.
Stuck in fastboot, I turned off my Kindle and then decided to log-in as root and restart the process, thinking this would resolve any permissions issues, but my Kindle never turned back on. Now my Kindle will not turn on at all (even while holding down volume buttons) and is not recognized by 2 different macs and a windows pc. When issuing "sudo fastboot -i 0x1949 getvar product" I get "ERROR: Unable to create a plug-in (e00002be)" after some time. ADB shows nothing and no device drivers load in Windows.
So, a few questions:
First, Is there anyway to get my Kindle to boot? Looking into it a little, it appears (although is unclear) that BreakDroid is only for the 7". You can see the code attached below - is my phone bricked? I'm going to boot back into Windows and try KFFirstAide and "KFHD System.img Recovery Tool" and, if those don't work, try Ubuntu and SoupKit. I do have a system backup that was made with KFFirstAide. Any thoughts on how to get it up and running again? Although I'm not that fluent in the Windows environment I'm pretty savvy with Linux and OS X.
Second, if it is bricked and I have to send it back to Amazon what risks do I face? Is it likely they'll just send it back fixed and all will be well, or will they keep it and/or sue me for messing with the boot loader? Would I be better off sending it to someone who unbricks and roots Kindles to avoid additional frustration from a gift?
Any thoughts and help are greatly appreciated! Thanks!
P.S. Here is the code BreakDroid ran. I recall "file already exists" and "unable to copy" due to permissions errors but, unfortunately, I killed the terminal before copying the output thinking I could just log-in as root and redo the process (which I did not attempt). The flash at the end of the code, however, was successful (confirmed on Kindle's display).
Code:
/Volumes/BreakDroid/.files/android-sdk/platform-tools/adb kill-server
sleep 5
/Volumes/BreakDroid/.files/android-sdk/platform-tools/adb push /Volumes/BreakDroid/.files/root/fbmode /data/local/fbmode
sleep 5
/Volumes/BreakDroid/.files/android-sdk/platform-tools/adb shell chmod 755 /data/local/fbmode
sleep 2
/Volumes/BreakDroid/.files/android-sdk/platform-tools/adb shell /data/local/fbmode
sleep 5
/Volumes/BreakDroid/.files/android-sdk/platform-tools/adb reboot
sleep 20
/Volumes/BreakDroid/.files/android-sdk/platform-tools/fastboot -i 0x1949 flash bootloader /Volumes/BreakDroid/.files/kindle_files/u-boot.bin
sleep 10
## applescript dialog "Hold the power button until the light goes off" then turn it back on and wait until it is on then continue
Just tried to install an unlocked bootloader from cyanogenmod's jem page (I can't link because I don't have enough posts! - Install_CM_for_jem on the cyanogenmod wiki) but no dice, fastboot just hangs at "waiting for device" on the computer that was able to get the "unable to create a plug-in" error, regardless of USB port, using "sudo ./fastboot -i 0x1949 flash bootloader /Users/USER/Documents/kfhd8-u-boot-prod-8.1.4.bin". Any help or return/warranty advice is appreciated!
Make sure the device is powered off use Ubuntu with soup kit then run the command sudo fastboot -i 0x1949 getvar product then plug in the tablet. That should get you into fastboot.
macman005 said:
Make sure the device is powered off use Ubuntu with soup kit then run the command sudo fastboot -i 0x1949 getvar product then plug in the tablet. That should get you into fastboot.
Click to expand...
Click to collapse
After a lot of effort to get SoupKIt installed (finally got a working install with an i386 version of Ubuntu 12.04, where you'd think that Android development is 64-bit...), I was unable to get fastboot to recognize my Kindle, regardless of which USB controller I used.
Of note, I also wasn't able to use fastboot with sudo, only as the user. Is this because I'm on a live-installation or is SoupKit supposed to be on a 64-bit OS?
Any further suggestions on how to revive this Kindle?
The sudo might not be important when you run the command
fastboot -i 0x1949 getvar product
Do you get a waiting for device?
If so this is when you should plug the tablet in via usb
macman005 said:
The sudo might not be important when you run the command
fastboot -i 0x1949 getvar product
Do you get a waiting for device?
If so this is when you should plug the tablet in via usb
Click to expand...
Click to collapse
I did get "waiting for device" with my Kindle unplugged. I then tried several USB ports, waiting a few minutes at each (~15 minutes), with no luck. :crying: Any thoughts?
I am on Wolla 5.0 and elementalx 6 something but I don't think these caused the stuck as the phone had been working fine.
Right before the phone was stuck, I updated an app called Lucky Patcher; I then restarted the phone and it's been stuck.
Under Devices manager My HTC shows this device is working properly.
M8 was detected by Adb. But when I typed commands such as "fastboot reboot bootloader" or "fastboot reboot recovery" ADB shows and stuck at "Waiting for device".
it has been like this for two hours.
Please help.
Whileitlasted said:
I am on Wolla 5.0 and elementalx 6 something but I don't think these caused the stuck as the phone had been working fine.
Right before the phone was stuck, I updated an app called Lucky Patcher; I then restarted the phone and it's been stuck.
Under Devices manager My HTC shows this device is working properly.
M8 was detected by Adb. But when I typed commands such as "fastboot reboot bootloader" or "fastboot reboot recovery" ADB shows and stuck at "Waiting for device".
it has been like this for two hours.
Please help.
Click to expand...
Click to collapse
That's what you get for using Lucky Patcher I guess. Get rid of it and stop ripping developers off.
Okay........................ the problem is you are using fastboot commands while booted to system would be my guess.
Try this:
adb reboot bootloader
You can only use fastboot commands while booted into bootloader. While booted into system (into your ROM or recovery) you can only use adb commands
xunholyx said:
That's what you get for using Lucky Patcher I guess. Get rid of it and stop ripping developers off.
Okay........................ the problem is you are using fastboot commands while booted to system would be my guess.
Try this:
adb reboot bootloader
You can only use fastboot commands while booted into bootloader. While booted into system (into your ROM or recovery) you can only use adb commands
Click to expand...
Click to collapse
Hi, I already tried the adb commands (reboot, reboot recovery, reboot bootloader) along with the fastboot ones; the adb ones didn't even show "waiting for device", instead a new command line was show, i.e. as if it was not aware of the adb commands.
I let the battery ran out (nothing I could do about it anyway) and after a full charge, the phone is now working with god knows why/how. The app is also working fine and no further issues happen. I will keep an eye on it and see how it goes.
Although phone is working, I am still very curious with what exactly happened...
hi all, sorry if this has beeen posted before but its bugging me as i spent literally 4-5 hours lastnight trying to sort it, i havee rooted 4-5 android phones in the past but im just having no luck with this one
i installed adb / fastboot minimal, enabled what needed to be enabled in developer options on the swift, booted the swift into fastboot mode, then when i run adb on my computer, the first command works 'fastboot oem unlock' but after that its constantly saying 'waiting for devices' whenever i try the next phase of commands ie. fastboot -i 0x2970 oem unlock-go etc it just wont detect the device at all in windows on adb, is there any suggestions anyone could throw out there before i end up sending it back and getting an alternative android phone thats easier to root? the only thing i can think off is its a usb driver issue? but i installed the gloogle usb drivers and it picks up the phone for file transfer etc so im not sure if this is the issue. many thanks!
yodjone1 said:
hi all, sorry if this has beeen posted before but its bugging me as i spent literally 4-5 hours lastnight trying to sort it, i havee rooted 4-5 android phones in the past but im just having no luck with this one
i installed adb / fastboot minimal, enabled what needed to be enabled in developer options on the swift, booted the swift into fastboot mode, then when i run adb on my computer, the first command works 'fastboot oem unlock' but after that its constantly saying 'waiting for devices' whenever i try the next phase of commands ie. fastboot -i 0x2970 oem unlock-go etc it just wont detect the device at all in windows on adb, is there any suggestions anyone could throw out there before i end up sending it back and getting an alternative android phone thats easier to root? the only thing i can think off is its a usb driver issue? but i installed the gloogle usb drivers and it picks up the phone for file transfer etc so im not sure if this is the issue. many thanks!
Click to expand...
Click to collapse
Hi,
I had the same issue. When that happens, do commands without the -i 0x2970 bit. So for example:
fastboot -i 0x2970 erase recovery
becomes:
fastboot erase recovery
Hope this helps
-Jev
I tried this but it still says 'waiting for any device' My initial command worked for fastboot oem unlock, but then I just couldnt do the following commands, and as a result whenever i tried to install a custom recovery / rom it gave me the error along the lines of 'unable to verify....'
edit: when i missed out the -i part, then said its already unlocked. however i still am not able to install supersu or the recovery as it still gives me the error 'signature verification failed'
yodjone1 said:
I tried this but it still says 'waiting for any device' My initial command worked for fastboot oem unlock, but then I just couldnt do the following commands, and as a result whenever i tried to install a custom recovery / rom it gave me the error along the lines of 'unable to verify....'
edit: when i missed out the -i part, then said its already unlocked. however i still am not able to install supersu or the recovery as it still gives me the error 'signature verification failed'
Click to expand...
Click to collapse
Hi,
OK, what recovery are you trying to install? I would recommend TWRP 3.0.2 by Beroid (in the development section) because it's easy to use and it works. Get the image and put it in your adb folder is. Make sure you are in fastboot. Then run commands
- fastboot erase recovery
- fastboot flash recovery (name of file).img
Disconnect the device from your computer. Then remove the battery. Then replace the battery and press VOLUME DOWN and POWER to rebbot in to recovery mode to verify the installation.
You should now be in the recovery. You can flash custom roms and supersu within this new recovery.
Hope this helps
-Jev