http://forum.xda-developers.com/showthread.php?t=1615093
Using ADB Shell (within SuperOneClick), I used the following command to flash the u-boot.bin file to my Kindle Fire.
"dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2"
Now it's stuck on the "FIREFIREFIRE Extended Bootloader" screen. I can't choose boot modes and I can't access the device through ADB (SuperOneClick) or Kindle Fire Utility.
All help is appreciated. Thanks!
http://forum.xda-developers.com/showthread.php?t=1698163
The last post solved my problem. I must've been blind when searching.
I tried numerous updating the drivers, but it wasn't until I actually uninstalled THEN reinstalled the drivers that it worked.
Related
Hello. After a few attempts I was finally able to root my kindle fire using Breakdroid found here: http://forum.xda-developers.com/showthread.php?t=1511757 .(I only have access to an OSX, no windows). I have a dell latitude running snow leopard. (hackintosh)
I can get to the black and red screen.
I downloaded the energy ics apk and tried to install the zip through the CWM-base Recovery v5.0.2.7 FULL (by DooMLorD) and it just loops through the fire screen with the triangle logo. Occasionally you can see the ICS startup screen, but very briefly(like 1 sec) but it goes back to looping through the reset.
I am not new to rooting android devices as I have rooted my phones in the past with no problems.
1. What am I doing wrong?
2. I can try install TWRP but how?(step by step on overwriting the CWM-base Recovery in OSX please, i have adb and tried but it does not see twrp in my file location.
3. is there an updated script for osx that auto installs TWRP?
If someone has time, please post a video please as there are none on installing using OSX on a fire using 6.3 on youtube or anywhere else on the web.
I cant add a new post since im new so Im editing this one:
Thanks! After waiting 15 min for the opening ICS screen, I finally rebooted and had the same problem..
Now the big question... how do you install TWRP using OSX?
tell you the steps I have done with no success...
I went to http://www.teamw.in/project/twrp2 and chose kindle fire
downloaded the .img and placed it in my platforms-tools(and yes, I downloaded the ADB package and added platform-tools)
first did adb devices and got:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
436E000600000001 recovery
then followed the websites direction and started adb shell by typing adb shell and got:
:~ drive$ adb shell
~ #
then followed the websites direction and entered su and got:
~ # su
/sbin/sh: su: not found
~ #
why was su not found?
Think I might gotten closer to a solution to my own problem.. I re-rooted using Breakdroid(auto root method) and now I am getting the full ICS animation screen ... Im going to leave it alone for a bit and see if it actually loads ICS on my fire.. will let you know any findings...
matchnbpm said:
Think I might gotten closer to a solution to my own problem.. I re-rooted using Breakdroid(auto root method) and now I am getting the full ICS animation screen ... Im going to leave it alone for a bit and see if it actually loads ICS on my fire.. will let you know any findings...
Click to expand...
Click to collapse
TWRP is required to run the new ICS roms. CWM usually will not work.
ok.. got su to finally work after reloading kindle fire's image that I did a backup of and let it be on USB mode
got bootmode to go in from the site
tried to fastbook and i get:
# fastboot -i 0x1949 flash recovery openrecovery-twrp-blaze-2.1.1.img
fastboot: not found
.. Edit.. found out that fastboot requires that you exit out of ADB..
now fastboot stuck on 'waiting for device'
matchnbpm said:
ok.. got su to finally work
got bootmode to go in from the site
tried to fastbook and i get:
# fastboot -i 0x1949 flash recovery openrecovery-twrp-blaze-2.1.1.img
fastboot: not found
Click to expand...
Click to collapse
You don't need "su" to enter fastboot commands.
While in recovery, enter:
adb shell idme bootmode 4002
adb reboot
That will restart your kindle in fastboot mode. Then you can enter:
fastboot flash recovery /path/to/twrp.img
Then...
fastboot oem idme bootmode 4000
...and reboot
EDIT:
6.3.1
Wow.. what a pain! Finally got TWRP to load! Here are the instructions for OSX using http://forum.xda-developers.com/showthread.php?t=1511757 (since no one seems to have it)
download breakdroid
start breakdroid (not kindlewater)
press 5 for kindle
press ok
press 1 for autoroot
now this is where you either get it or not.. my first time I got hung at waiting for device, so i simply unplugged it and replugged it and continued the autoroot. The second time after i unrooted my kindle fire and rerooted I did an exit and re rooted and it went all the way through... so your choice...
after you should be able to load kindle fires normal os after you see a triangle with a fire in it
now download TWRP
head over to: http://www.teamw.in/project/twrp2 choose kindle fire from their
'please select device'
download their .img
follow the instruction here to add adb to your MAC: http://forum.xda-developers.com/showthread.php?p=9842005
with the instructions, make sure you do it step by step including the "Now .... I am going to show you how to make your life a lot easier in Terminal to run ADB without having to navigate to the folder every time you want to launch it."
if you did the instructions correctly you made a quick way to start ADB.
you can check if it works by starting a terminal(under applications/utilities(i made a quickstart and pinned it to my bar) and type ADB devices(with caps)
you should see your device there, if not, retrace your steps
move the TWRP .img file to your platform-tools folder
now start your kindle fire to normal mode and plug in your usb.. leave it on USB mode, do not exit
start a terminal and type ADB devices, your kindle fire should NOT be in recovery, should show 'device'
follow the TeamWin directions and type adb shell
type su
type idme bootmode 4002
type exit
quit terminal
restart terminal
type fastboot -i 0x1949 flash recovery openrecovery-twrp-blaze-2.1.1.img
your kindle fire will look like it is locked up after a few min, simply power off your kindle fire after installation of TWRP by pressing the power button until it turns off..
power back on and press and hold until it turns orange, release..
Welcome to TWRP!
Hi I was wondering if I can get any response with my case. Similar to previous posts in this thread, I too bricked my KF.
I installed twrp and flashed it with cm9 and I reversed by reinstalling stock update 6.3.
I used kindle fire utility 0.9.6. after reinstalling the update from amazon, my KF remained at the kindle fire logo screen.
My pc recognizes the kf. the drivers are working on my pc. when i plug it in or out, i get a response from the pc. when i open KFU it recognizes adb status online. root status: unknown. when i go to bootmode in any modes (normal, fastboot, recovery,) i get exec '/system/bin/sh' failed: No such file or directory (2)
the program tells KF to reboot, the KF reboots and thats the extent. I would also try reinstalling twrp or clockwork or fff, i get exec '/system/bin/sh' failed: No such file or directory (2) WAITING FOR DEVICE.
I also tried Kindle Fire Unbrick v1.1 in all the options to try i also receive exec '/system/bin/sh' failed: No such file or directory (2).
I then tried using ubunto Firekit. I used all the command scripts and i get WAITING FOR OMAP44xx device...
when I use cmd prompts, the KF only respond to adb commands. for example, the only comman that the KF understands is /adb reboot. the KF reboots but any other commands i get nothing.
HELP! THIS GIRL IS LOSING HER HAIR....
Huh? kinfauns answered your other post... just wait until you get the factory cable, follow the instructions he gave you and then post if you encounter problems (or to say it's fixed and thank him)...
Regarding the hair loss, a wig may help.
I'll give you a little more information since perhaps you didn't understand the first time.
A shell is a piece of software with a particular set of commands built in that acts as sort of a go-between for the OS and the device hardware. It is necessary to be able to perform a certain set of tasks from within the system. One of those tasks is having the ability to change the bootmode. In some cases, the shell gets corrupted and is no longer able to perform said tasks. Attempting to do so would result in the following error: "exec /system/sbin/sh failed".
The ability to switch between the "normal", "fastboot", and "recovery" bootmodes is key to resolving certain problems within an Android system. Even though you are stuck at the boot screen, which typically means you are in "fastboot" mode, your adb status reads "online", indicating you are in fact in the "normal" bootmode without a working OS. Unfortunately, without a working shell there is only one way to change the bootmode to the necessary "fastboot" mode, and that is with a factory programming cable (not to be confused with an OEM cable). The factory programming cable will instantly put you in fastboot mode so you can change your bootmode without the need of a shell.
It is then necessary to reinstall custom recovery and change your bootmode to "recovery" so you can reinstall your OS and in the process, fix your shell and any other problems.
Are you with FFF1.4a and TWRP? Can you reboot to fastboot?
Gửi từ Kindle Lửa của tôi qua Tapatalk 2
linktohack said:
Are you with FFF1.4a and TWRP? Can you reboot to fastboot?
Click to expand...
Click to collapse
No
erikaz said:
I installed twrp and flashed it with cm9 and I reversed by reinstalling stock update 6.3.
Click to expand...
Click to collapse
Hi,
My Problem:
My kindle fire is stuck in twrp. There are no backups or roms. When I do a Normal Boot, it just gets frozen at the kindle fire boot logo. When I try to mount the USB storage (cache & sd card), my computer can't find it. I do have FireFireFire on it and I have manageed to get it into fastboot mode. Still no luck
How I Tried To Fix it:
I downloaded the kindle fire driver and installed it. I have already done the Android SDK thing too, I've already edited the two files in Notepad. Then, I went on Command Prompt and did the "adb kill-server", "adb start-server", and then "adb devices" but it doesn't list my kindle fire. Under device and printers on my PC, it does list the driver for kindle, but when you click on properties it says only "Android ADB Interface".
Can anyone help me with this? Please?
I can post it again here if you can't fix it in windows try this http://forum.xda-developers.com/showthread.php?t=1882565
OK. Do you know how to get command prompt, under adb, to show my kindle? I do adb shell but it returns with "error: device not found". When it says Android ADB Interface it knows it's a Kindle Fire. But it only says "Android ADB Interface" under device & printers
This method is with Linux it will show your kindle attatched in what form is yet to be determined
Thepooch said:
This method is with Linux it will show your kindle attatched in what form is yet to be determined
Click to expand...
Click to collapse
OH MY GOD!! I got it working!
:-|
threed42 said:
Hi,
My Problem:
My kindle fire is stuck in twrp. There are no backups or roms. When I do a Normal Boot, it just gets frozen at the kindle fire boot logo. When I try to mount the USB storage (cache & sd card), my computer can't find it. I do have FireFireFire on it and I have manageed to get it into fastboot mode. Still no luck
How I Tried To Fix it:
I downloaded the kindle fire driver and installed it. I have already done the Android SDK thing too, I've already edited the two files in Notepad. Then, I went on Command Prompt and did the "adb kill-server", "adb start-server", and then "adb devices" but it doesn't list my kindle fire. Under device and printers on my PC, it does list the driver for kindle, but when you click on properties it says only "Android ADB Interface".
Can anyone help me with this? Please?
Click to expand...
Click to collapse
it did not work 4 me
Ok so I screwed up.
But I should say I'm not a complete newbie at rooting KF and KF2s. I've successfully rooted and put custom ROMs on a number of these devices before. Yes KF2s are harder to root and customize than KFs, I understand that.
Here's what I did.
Checked stock Kindle OS version (10.4.x). Turned on ADB etc before starting.
Rooted as per this page: http://forum.xda-developers.com/showthread.php?t=2075959
Booted up into Kindle OS.
Connected to PC, ran elevated CMD.
adb push stack /data/local/tmp/
adb shell su -c "dd if=/data/local/tmp/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
adb shell su -c "reboot bootloader" (with fastboot cable attached)
fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin (to install more hack-friendly bootloader)
fastboot -i 0x1949 flash boot otter2-freedom-boot.img
fastboot -i 0x1949 flash recovery otter2-twrp-2.4.4.0-recovery.img
fastboot -i 0x1949 reboot
Ok so here is where I am at. I can boot to TWRP, no problem. I just have no ROM and GApps to flash.
If I do adb devices, it does not give me an error, but lists no devices, I just get 'List of devices attached' with no list of devices.
If I try:
adb push cm-10.1.3-otter2.zip /sdcard/
I get
error: device not found
despite the Android ADB Device being listed correctly in device mangler, and apparently working properly.
I tried to mount the data partition in TWRP, and tried
adb shell mount /sdcard
but still no joy.
So anyone any idea how I can copy the ROM and GApps to the sdcard partition on the KF2 using adb or some other way.
The device won't boot and recovery to factory defaults doesn't work either, I get the boot loop to the red triangle that others have.
I'm confused I thought you said it would go into twrp recovery but the red triangle is stock recovery, if its stock recovery there is no adb, you will need a fastboot cable. If you are getting twrp then try uninstalling the adb device and reinstalling it with the drivers in my signature.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I can get into TWRP without an issue. If I let the device try and boot the Kindle OS it reboots a couple of times then I get the triangle saying it can't boot.
I guess I can try reinstalling the drivers.
Thanks.
When you can get in to TWRP you can use "adb sideload" or "adb push" to transer your data over to your kindle.
flopower1996 said:
When you can get in to TWRP you can use "adb sideload" or "adb push" to transer your data over to your kindle.
Click to expand...
Click to collapse
No, I can't.
In my original post I said that I'd tried that, and what happened when I did.
stunts513 said:
I'm confused I thought you said it would go into twrp recovery but the red triangle is stock recovery, if its stock recovery there is no adb, you will need a fastboot cable. If you are getting twrp then try uninstalling the adb device and reinstalling it with the drivers in my signature.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Your drivers worked, thanks!
Although I am not sure why the previous driver I had installed didn't work, since I've had KF2s hooked up to this same computer before.
In any case, I booted up the device to TWRP, plugged it in, installed the driver, and used adb push to copy the ROM and GApps over.
Thanks again.
Hello,
I successfully rooted my KFHD 8.9" with Bin4ry's "root many android." I want to install Cyanogenmod on my tablet, so I installed the android adt bundle. The problem I have is that I'm unable to fastboot the Kindle. Typing "adb devices" in the command prompt looks like this:
adb devices
B0C91101319300F6 device
However, typing "fastboot devices" in the prompt returns nothing. I've also tried powering off and unplugging my Kindle, typing this:
fastboot -i 0x1949 getvar product
into the command prompt and then pluggin in the device. However, the command prompt just stays at < waiting for device > and the Kindle powers on normally (not fastboot mode).
Did anyone have this same problem? If you were able to fastboot successfully, which drivers did you use (where did you download them from)? I tried the drivers from here http://forum.xda-developers.com/showthread.php?t=1893838 and here http://forum.xda-developers.com/showthread.php?t=2337634. Niether worked.
Thanks!
If you have adb access try "adb reboot bootloader", or if rooted run
Code:
adb shell "su -c 'reboot bootloader'"
That should get you into fastboot so you can install the drivers in my signature, from there on the method you were previously trying should work.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
If you have adb access try "adb reboot bootloader", or if rooted run
Code:
adb shell "su -c 'reboot bootloader'"
That should get you into fastboot so you can install the drivers in my signature, from there on the method you were previously trying should work.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Sorry, I'm a bit confused, which drivers? Also, where to install the drivers computer, Kindle?
The drivers are in my signature(my signature is only viewable when not in a tapatalk or equivalent app, like if you view this thread on your pc.), download them onto your computer and extract them somewhere, open the device manager with kindle plugged in and USB debugging enabled and you should see a device with a yellow triangle next to it. Right click it and hit update driver, and tell it to search the directory you extracted my drivers to and it should install. If you are on windows 8 you will have to disable driver signature enforcement first.
Sent from my Amazon Tate using Tapatalk
Just use fireflash Google the apk. I had the same problem. The only tutorials were for the 7 in, but find one. Don't use the files they tell you to use. Go to hashcodes goo.im and find the ones for the 8.9.
Sent from my Amazon Jem using Tapatalk
Or you can use the fireflash tutorial for 8.9", its stickied in the 8.9 dev section. http://forum.xda-developers.com/showthread.php?t=2277105
While the fireflash method is easier, you have to make sure you check the box that downgrades the bootloader or you will have a red screen brick upon reboot. The box to check has red warning text under it. somehow people miss it.
Sent from my Amazon Tate using Tapatalk