[Q] Ubuntu, ADB/Fastboot and the Kindle Fire - Kindle Fire Android Development

Has anyone done it?
I've spent all weekend trying to get Fastboot to work on my kindle fire. I've gotten ADB to work in windows (7 64bit) but not fastboot. I was told Ubuntu might be easier... I now have Ubuntu 11.04 dual booted on my laptop. Android sdk is working as i can do adb commands on my OG Droid, but ADB and Fastboot aren't working...
So, if you have any tips or tricks on getting fastboot and adb working in ubuntu, i would be extremely great full!

ensure that you have created
Entry in ~/.android/adb_usb.ini:
PHP:
[[email protected] ../platform-tools]$ cat ~/.android/adb_usb.ini
0x1949
[[email protected] ../platform-tools]$
Appropriate UDEV rules
PHP:
[[email protected] ../platform-tools]$ cat /etc/udev/rules.d/52-android.rules
# adb protocol for blaze / ottter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTRS{idProduct}=="0006", MODE="0666", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTRS{idProduct}=="0005", MODE="0666", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
[[email protected] ../platform-tools]$

You update the tools package in the sdk manager?

this is the guide i used:
http://forum.xda-developers.com/showthread.php?t=921169
my phone would get pass step 4 letting move onto step 7 (i didn't because this is for my kindle)
my kindle wouldn't pass step 4 leading me to step 5 and it didn't pass that...
thanks for the help, i'll be checking in again tomorrow evening!

Do what Skrobul said in post #2. If it doesn't work, then go back to your 'adb_usb.ini' file and add this line:
0x0006
This is what I have in my file to get the Kindle to be recognized properly. I'm on 11.10 and everything is working fine. As for fastboot, you have to get the fastboot script online and drop it into your 'platform-tools' folder. hope you get it working.

here is the linux fastboot script, I know when I went looking for it, it was a pain in the but to find it. just remove the .zip from the end and put in your platform-tools directory.

Thanks for the help! I'll be trying again after work

thank you everyone for you help!
Adb and fastboot are working!!!!​

ok, ubuntu users, i'm trying to flash a recovery.img
in windows i would put the .img in the same folder as \platform-tools. and run
Code:
fastboot boot <recovery.img> -(to test)
fastboot flash recovery <recovery.img> -(to flash)
in ubuntu i just tried:
Code:
./fastboot boot <recovery.img> -(to test)
and got this:
Code:
cannot load '<recovery.img>'
were do i put files i'd like to flash/test?

Code:
sudo ./fastboot boot <recovery.img>
sudo ./fastboot flash recovery <revocery.img>
works now!

Related

Can't seem to catch a break - adb and fastboot issues

Hey y'all,
I am rooting / rom-ing my third KF.
I could not get TWRP to install so I installed CWM that comes with the KFU
I installed Jandycane and the most current gapps
From then on, the Kindle gets stuck at the boot animation
I have tried other options in KFU, but everything involving fastboot does not work. The kindle shows up as a composite device in the device manager, and is able to be adb-ed into.
In KFU, I see the bootmode being 4000. When I tried the idme command to change it to recovery, it told me that it could not accept the idme command.
I've tried going using the adb shell to push fiels and create directories, but have failed. Su does not work, mkdir does not work, and chmod does not work.
Additionally I have tried the KF Unbrick 1.1 and none of the options seem to do anything.
I am running out of options here. I have tried these procedures on two PCs without avail.
Before I installed the current rom, I have made a backup of the stock rom. Is there any way I could adb into the device and restore it? Would this be a valid way to fix this up?
Can anyone suggest anything else that I have not tried?
Anyone?
When I try to push fbmode from here: http://forum.xda-developers.com/showthread.php?t=1414832
Code:
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>adb push fbmode /data/local/tmp
failed to copy 'fbmode' to '/data/local/tmp': No such file or directory
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>
Now lets see if I can escalate my privileges
Code:
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>adb shell
[email protected]:/ $ su
su
Segmentation fault
[email protected]:/ #
Now lets see if I can push fbmode regardless
Code:
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>adb shell
[email protected]:/ $ cd /data/local/tmp
cd /data/local/tmp
/system/bin/sh: cd: /data/local/tmp: No such file or directory
2|[email protected]:/ $ cd /data/local/
cd /data/local/
/system/bin/sh: cd: /data/local: No such file or directory
2|[email protected]:/ $ cd /data/
cd /data/
[email protected]:/data $ ls
ls
opendir failed, Permission denied
255|[email protected]:/data $
So much for adb ... how about that fastboot
Every time I do anything with fastboot it says waiting for device:
Code:
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>fastboot -i 0x1949 flash recovery twrp.img
< waiting for device >
Are there any devices showing?
Code:
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>fastboot devices
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>adb devices
List of devices attached
0123456789ABCDEF device
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>
fastboot does not see any devices whereas adb does...
I have tried sending the fastboot command while the device is off and then turning it on. The kindle just hangs at the kindle fire screen.
EDIT: I switched computers, and it got back into previous state at being stuck at the animation screen
This is what happens when I try to install TWRP in KFU:
Code:
Installing TWRP...
If we get stuck here for awhile, power the kindle on and off a few times.
You should also check device manager for "kindle" If so, rerun the driver
installer that came packaged with KFU.
***********************************************
* Activating Fastboot (4002) *
***********************************************
failed to copy 'files\fbmode' to '/data/local/fbmode': No such file or directory
Unable to chmod /data/local/fbmode: No such file or directory
/system/bin/sh: /data/local/fbmode: not found
The kindle has been told to reboot in Fastboot Mode.
< waiting for device >
Can you actually put your device into fastboot mode? You can only use fastboot commands when the bootloader has put the device into fastboot mode. If you can get output from any adb commands, you are not in fastboot mode. Look at this guide and see if you can put the KF into fastboot mode...
http://forum.xda-developers.com/showthread.php?t=1668159
What bootloader do you have installed on the device? (Describe the first bootlogo you see. Refer to the above guide.)
What error do you get when you attempt to set the bootmode with idme?
Where are you running your adb commands? When you are stuck on the boot animation or in recovery?
Can you even get to your recovery?
My guess is you've somehow corrupted the system software on your ROM installation. If you can get to recovery, you'll probably need to reflash your ROM. If you can get the device into fastboot mode, you can get to recovery. If can't do either of those, you'll need a factory cable or be willing to open up the case.
kinfauns said:
Can you actually put your device into fastboot mode? You can only use fastboot commands when the bootloader has put the device into fastboot mode. If you can get output from any adb commands, you are not in fastboot mode. Look at this guide and see if you can put the KF into fastboot mode...
http://forum.xda-developers.com/showthread.php?t=1668159
What bootloader do you have installed on the device? (Describe the first bootlogo you see. Refer to the above guide.)
What error do you get when you attempt to set the bootmode with idme?
Where are you running your adb commands? When you are stuck on the boot animation or in recovery?
Can you even get to your recovery?
My guess is you've somehow corrupted the system software on your ROM installation. If you can get to recovery, you'll probably need to reflash your ROM. If you can get the device into fastboot mode, you can get to recovery. If can't do either of those, you'll need a factory cable or be willing to open up the case.
Click to expand...
Click to collapse
That would make sense. I cannot change the bootmode from 4000, so that's why fastboot does not work. I feel dumb for not thinking this through.
It has CWM installed as I could not load TWRP initially due to a poor connection.
This is what I get when I try to change the bootmode:
Code:
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>adb shell su -c 'idme bootmode 4002'
Segmentation fault
<idme> write 4002 to offset 0x1000
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>adb shell idme bootmode 4002
<idme> Invalid permission
I cannot get into recovery as I cannot get the tablet to boot into anything but the ROM istelf (or try to, as it never boots into anything but just loops the boot animation)
Tell me about this factory cable. I'm sure I have it somewhere among all of my micro USB cables...
The boot pattern is as follows: kindle fire (white orange/stock) -> jandycane boot animation that runs forever
There is no triangle or any press the power button to boot into recovery.
http://forum.xda-developers.com/showpost.php?p=30376760
soupmagnet said:
http://forum.xda-developers.com/showpost.php?p=30376760
Click to expand...
Click to collapse
I cannot get the kindle to boot into a ROM, so I cannot use the terminal app.
Can I get an adb shell and push these files?
Also, per my post above, it seems that something sketch is going on with my superuser settings...
Yes, if you have a working adb, you can absolutely push those files. The path will be slightly different though. Instead of ~/local/tmp, you will push the files to /data/local/tmp then execute:
Code:
adb shell chmod 755 /data/local/tmp/rcmode
adb shell /data/local/tmp/rcmode
Looking through your other posts I see you are trying to invoke the shell and enter the commands seperately. Try again, but only this time add "adb shell" to the command itself, as above, and see if that makes a difference.
Also, I've seen both /data/local and /data/local/tmp used but I've always used /data/local/tmp
[Edit:] if you still get a "No such file or directory" error, see if you can create it:
Code:
adb shell mkdir /data/local/tmp
Zlatty said:
I cannot get the kindle to boot into a ROM, so I cannot use the terminal app.
Can I get an adb shell and push these files?
Also, per my post above, it seems that something sketch is going on with my superuser settings...
Click to expand...
Click to collapse
KFU's included version of CWM recovery does not flash ICS (and very likely JB) ROMS correctly. This is a bug known to corrupt the flash.
It not likely you'll be able to do anything meaningful with the system currently installed on your Kindle Fire. Unfortunately for you, that probably includes using idme or pushing anything that might help you change bootmodes. Of course, I may be wrong and you might find another way out of the mess, but the easiest way for you to fix this is to use a factory cable, put the KF into fastboot mode, flash TWRP, boot into recovery so you can flash a new bootloader and ROM.
factory cable...
http://forum.xda-developers.com/showthread.php?t=1550999
fastboot mode...
http://forum.xda-developers.com/showthread.php?t=1668159
beginner's guide...
http://forum.xda-developers.com/showthread.php?t=1552547
supplement for rooting... installing a ROM... etc...
http://forum.xda-developers.com/showthread.php?t=1638452
EDIT: You can try what soupmagnet suggested while I was typing out my post, but you've already shown that you cannot access the /data partition. I think it's going to be something more than simply just an unmounted partition.
I hadn't really thought about mounting the data partition...it's worth a shot either way.
soupmagnet said:
I hadn't really thought about mounting the data partition...it's worth a shot either way.
Click to expand...
Click to collapse
Well my adventure just keeps getting worse and worse. I charged the kindle last night to ensure enough battery life for today. It is suck at the kindle fire logo now. I have the drivers loaded correctly and my computer sees the kindle. However I cannot adb or fastboot the device. It also went from composite device to adb device in the device manager.
EDIT:
Was able to install FFF and got to boot into recovery. CWM 5.2.0.7.
In adb I tried to get super user permissions
C:\android-sdk-windows\platform-tools>adb shell
~ # su
su
/sbin/sh: su: not found
~ #
Click to expand...
Click to collapse
What are my options at this point. KFU cannot download and install TWRP. I cannot manually push it since I dont have su. KFU's install super user function does not work as it tries to install TWRP.
Zlatty said:
Well my adventure just keeps getting worse and worse. I charged the kindle last night to ensure enough battery life for today. It is suck at the kindle fire logo now. I have the drivers loaded correctly and my computer sees the kindle. However I cannot adb or fastboot the device. It also went from composite device to adb device in the device manager.
EDIT:
Was able to install FFF and got to boot into recovery. CWM 5.2.0.7.
In adb I tried to get super user permissions
What are my options at this point. KFU cannot download and install TWRP. I cannot manually push it since I dont have su. KFU's install super user function does not work as it tries to install TWRP.
Click to expand...
Click to collapse
Ok, so while I was in CWM, I mounted the SD card, downloaded and transfered a flashable TWRP found here http://forum.xda-developers.com/showpost.php?p=28664718&postcount=127
I flashed the zip and now I have TWRP working.
Zlatty said:
Ok, so while I was in CWM, I mounted the SD card, downloaded and transfered a flashable TWRP found here http://forum.xda-developers.com/showpost.php?p=28664718&postcount=127
I flashed the zip and now I have TWRP working.
Click to expand...
Click to collapse
I could not get twrp to boot into normal. So I used KFU to change to 4000 mode.
Code:
***********************************************
* Activating Normal (4000) *
***********************************************
< waiting for device >
... OKAY [ 0.081s]
finished. total time: 0.082s
rebooting...
finished. total time: 0.001s
The kindle has been told to reboot in Normal Mode.
Press any key to continue . . .
Everything went better than expected.... w00t!

How to enable adb and fastboot to flash boot.img on last Ubuntu 12.10

hello
After install a many times the adb and fastboot on ubuntu 12.04 with a lot of work to enable them i found on last ubuntu 12.10 a very simple way to do it.
Connect your phone with usb debugging enable to you computer.
Just tape adb on terminal and it ask you to install it than do it of course same for fastboot...
Test with this command if it s work
sudo adb devices
You can now flash boot or recovery in terminal place the boot.img on home folder than tape:
cd
fastboot flash boot boot.img
if you have problem like stuck on "waiting for device" do this:
Create a file named android.rules in /tmp with this followings contents:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
than run theses following commands:
sudo cp /tmp/android.rules /etc/udev/rules.d/51-android.rules
sudo chmod 644 /etc/udev/rules.d/51-android.rules
sudo chown root. /etc/udev/rules.d/51-android.rules
sudo service udev restart
sudo killall adb
disconnect your phone than reconnect, run adb devices*to confirm that now it has permission to access the phone.
With just this everything working ok for me on ubuntu 12.10 with fresh install...and nothing more
I want to thanks the ubuntu team because they work for that...
Sorry for my english
JEZ69 said:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
Click to expand...
Click to collapse
Thanks knew how to get the tools but this fixed my fastboot for me! Worked for my Asus Transformer just had to modify the vender id to match my device with the lsusb command sure it will work for all devices that way.
Wine isn't working for this? Would be perfect
Skickat från min HTC One X via Tapatalk 2
Thank you for this guide. It helped me to get working fastboot on Linux Mint 15.
Take a look here too
http://forum.xda-developers.com/showthread.php?t=2302780
JEZ69 said:
hello
After install a many times the adb and fastboot on ubuntu 12.04 with a lot of work to enable them i found on last ubuntu 12.10 a very simple way to do it.
Connect your phone with usb debugging enable to you computer.
Just tape adb on terminal and it ask you to install it than do it of course same for fastboot...
Test with this command if it s work
sudo adb devices
You can now flash boot or recovery in terminal place the boot.img on home folder than tape:
cd
fastboot flash boot boot.img
if you have problem like stuck on "waiting for device" do this:
Create a file named android.rules in /tmp with this followings contents:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
than run theses following commands:
sudo cp /tmp/android.rules /etc/udev/rules.d/51-android.rules
sudo chmod 644 /etc/udev/rules.d/51-android.rules
sudo chown root. /etc/udev/rules.d/51-android.rules
sudo service udev restart
sudo killall adb
disconnect your phone than reconnect, run adb devices*to confirm that now it has permission to access the phone.
With just this everything working ok for me on ubuntu 12.10 with fresh install...and nothing more
I want to thanks the ubuntu team because they work for that...
Sorry for my english
Click to expand...
Click to collapse
it's because do you need root permissions, use the root user, or add the " sudo " before the commands like : " sudo fastboot flash boot boot.img "
sorry for my english.
matt95 said:
Take a look here too
http://forum.xda-developers.com/showthread.php?t=2302780
Click to expand...
Click to collapse
Nice one. I totally missed that one.
Sent from my Nexus 7 using Tapatalk 4 Beta
slebit said:
Nice one. I totally missed that one.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
it is pretty hidden that's why
You can get fastboot to work with downloading with
sudo apt-get install fastboot
and all commandos must begin with sudo.. I you try it with out this it tell you <waiting for devices>
Gesendet von meinem HTC One X mit Tapatalk 2
-Happy Feet- said:
You can get fastboot to work with downloading with
sudo apt-get install fastboot
and all commandos must begin with sudo.. I you try it with out this it tell you <waiting for devices>
Gesendet von meinem HTC One X mit Tapatalk 2
Click to expand...
Click to collapse
i prefer installing them manually so that you know where your dev path is located
no go
I'm on ubuntu 12.04 trying to get my fastboot commands to work from the home dir. and without "sudo ./fastboot" it's fine and works and all but why should "adb" work from anywhere but not "fastboot" I've googled all over the place and have done a ton of stuff which has only netted my to the point of when I do something like "fastboot devices" instead of getting "waiting for device" or "permission denied" I get a cursor blink and then back to command prompt and no desired result.
htc dna plugged in and in fastboot usb.
sdk, adb android linux installed and updated, edited 51 rules and even made a 99 rules in /etc/udev...inputed all the various chmods..
anyone have anything to add?

[Q] Stuck at < waiting for device>

http://forum.xda-developers.com/showthread.php?t=2277105
I'm trying to follow above tutorial on how to install 2nd bootloader
I put "fastboot -i 0x1949 getvar product" in cmd, it showed "waiting for device" but when I turned it on, it doesn't change
I'm having a rooted 8.3.1 KF
Please help
tkien212 said:
http://forum.xda-developers.com/showthread.php?t=2277105
I'm trying to follow above tutorial on how to install 2nd bootloader
I put "fastboot -i 0x1949 getvar product" in cmd, it showed "waiting for device" but when I turned it on, it doesn't change
Please help
Click to expand...
Click to collapse
With the Kindle powered down, type the following command into a cmd/terminal window on your PC (should return with: < waiting for device> ):
fastboot -i 0x1949 getvar product
Then connect USB to the Kindle and it will boot. It *SHOULD* show a Fastboot screen and your terminal window should show something like:
product: Jem-PVT-Prod-04 this has to be done in a command window opened where fastboot is located. Shift + right click in the folder where fastboot is located select open command window here, then run the command and follow above instructions to get it into fastboot.
Edit also to let you know if you are running system version 8.4.1 other thing will need to be done to install freedom boot and recovery just to send an air of caution if you use the present instructions for this you will become stuck at the blue kindle fire logo so I would wait till methods have been updated.
yes I did that, unplugged my kindle and powered down -> type the command in cmd < waiting for device> -> Plug my kindle in and automatically turn on
The cmd still show < waiting for device> even after it's fully boot, it doesn't show fastboot screen
I managed to go to Fastboot mode by using KF First Aide, but my computer couldn't recognize kindle while it's in fastboot mode. So I couldn't do anything
Edit 1st post: I'm using 8.3.1 rooted
Thepooch helped me through teamviewer on how to install Android and here I share my experience on how to do it.
Your kindle need to be rooted. I suggest to use KF First Aide and root. It's easier
You will need ADB enable by go to settings in Kindle.
Download this file (Amazon 8.4.1 OS): http://d-h.st/VnR and put it in sdcard for backup purpose.
You don't extract ZIP files.
1. Download and extract #1 on below link
http://forum.xda-developers.com/showthread.php?t=2191010
2. Go to Root_with_Restore_by_Bin4ry_v21\stuff -> Shift + Right Click on folder -> Open command window here
*Steps 3,4,5,6,7 are from http://forum.xda-developers.com/showthread.php?t=2128201
3. Use these command to backup your stock partitions, these *.img will be in the Root_with_Restore_by_Bin4ry_v21\stuff folder.
Take 4 of those *.img to somewhere else safe
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img"
adb pull /sdcard/boot0block.img
adb pull /sdcard/stock-boot.img
adb pull /sdcard/stock-recovery.img
adb pull /sdcard/stock-system.img
4. Download these files (go to different topic above for latest version)
http://goo.im/devs/Hashcode/jem/stack
http://goo.im/devs/Hashcode/jem/kfhd8-freedom-boot-8.3.0.img
http://goo.im/devs/Hashcode/jem/kfhd8-twrp-2.4.4.0-recovery.img
5. Install stack:
Code:
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"
*Replace stack with location to your stack file
Example: adb push C:\Users\Admin\Desktop\stack /data/local/tmp/
6. Stop the auto recovery update script (this file may or may not be present): Mine was not present, it will show file not sound after enter 2nd command
Code:
adb shell su -c "mount -o remount,rw ext4 /system"
adb shell su -c "mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak"
adb shell su -c "mount -o remount,ro ext4 /system"
6.5: APPLIES IF YOU ARE ON SOFTWARE VERSION 8.3.0 OR GREATER
Download this: http://goo.im/devs/Hashcode/jem/kfhd8-u-boot-prod-8.1.4.bin
Enter fastboot mode and flash:
Code:
fastboot -i 0x1949 getvar product
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
*You will need a file called fastboot.exe, open command from there, KF First Aide have it
or you can download from here: http://d-h.st/ttL <- Do not use anything from this, just go to tools and open command from there
7. Continue with these command in fastboot mode:
Code:
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.3.0.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.4.4.0-recovery.img
fastboot -i 0x1949 reboot
***If everything is done correctly, when you booting up, the word Kindle Fire should switch from orange -> blue -> orange, then fully boot
***If you get orange screen, then you didn't do step 6.5
8. Download these and put them in sdcard:
http://goo.im/devs/Hashcode/jem/cm10.1/cm-10.1-20130604-UNOFFICIAL-jem.zip
http://goo.im/gapps/gapps-jb-20130301-signed.zip
To enter recovery mode, unplug, shut the kindle down. Plug in (it should power on), when the word Kindle Fire is orange, hold the volume up button, it should switch to blue and then twrp recovery mode. If you failed, hold the power button until it shut down and try again.
8.5. Drivers problem: Kindle not recognized
When I get into recovery mode, my computer couldn't recognize Kindle. So this is what you have to do.
Download this and extract: http://d-h.st/9We
Open android_winusb.inf
Go to/Search for
Code:
;Kindle Fire HD
Now go to Device Manager -> Right Click on "couldn't recognize driver kindle" -> Details -> you will see there are two codes.
Edit android_winusb.inf (below your device, mine is Kindle Fire HD) to match with the two codes.
Then just right click, update driver
9. Now back to Kindle, you should be in TWRP Recovery Mode.
You should backup first: Go to backup -> backup everything and check compression
Next go to Wipe -> Wipe 4 of the thing on the first line (Caches, Dalvik Caches, Factory Reset, System)
Next go to Install, choose 2 of the files at step 8.
Code:
cm-10.1-20130604-UNOFFICIAL-jem.zip
gapps-jb-20130301-signed.zip
Then reboot system
10. Now you should see CyanogenMod (Android) loading
After you are in, don't let Google backup your things. It will somehow messed up your system and will crash when you try to run apps.
Next, go to settings, go to about, and tap the last line 8 times to enable developer mode
Next, check advanced boot and ADB
After that, when hold your power button for a little bit, you will see a boot button, tap it and there should be 3 options to boot in case something happens.
Nice job you make a helper proud.

[HOW-TO] FireFireFire and TWRP on 6.3.3 WITHOUT A FACTORY CABLE!

Disclammar: I TAKE NO RESPONSIBLITY FOR WHAT HAPPENS FOR YOUR DEVICE. YOU FACE THE CONSEQUENCES FOR WHAT YOU DO.
Another note: I took no part in developing any of these tools used, credit goes to their authors
Final note: This is for the ORIGINAL KINDLE FIRE ONLY!
These are instructions for installing FireFireFire bootloader and TWRP recovery
-- THIS GETS YOU INTO FASTBOOT --
Step 1: Root the kindle fire using this method: http://forum.xda-developers.com/kindle-fire/development/how-to-kindle-fire-1-update-6-3-3-t2814955
Step 2: Download fbmode from this: http://forum.xda-developers.com/showthread.php?t=1414832
Step 3: Install fbmode by using adb push fbmode /data/local/tmp
Step 4: Set fbmode permissions by using: adb shell chmod 755 /data/local/tmp/fbmode
Step 5: Run these commands here:
Code:
adb shell
su
cd /data/local/tmp
./fbmode
exit
exit
Step 6: From the command prompt: Run adb reboot
-- TO INSTALL FIREFIREFIRE AND TWRP FOLLOW THESE STEPS --
Step 1: Download SoupKit and install it from here: http://forum.xda-developers.com/showthread.php?t=1850038
Step 2: In soupkit's main menu go to the install menu by entering 2
Step 3: Enter 4 to install a bootloader and than enter 1.
Step 4 :If it says 'Make your selection now" enter 1 again
Step 5: Wait until SoupKit tells you to reboot your device and press enter.
Step 6: Follow the first set off steps to get into fastboot again
Step 7: Go back to the install menu and enter 1 to install TWRP, Than if it prompts you enter 1 again if it says "Make your selection now".
Step 8: Wait until it finishes flashing and prompts you to reboot. Reboot your device and press enter.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------
You now have a rooted FireOS 6.3.3 session with FireFireFire bootloader and TWRP recovery with no factory cable!
Flashing FFF and TWRP without Fastboot Cable or SoupKit
Non SoupKit Method
Watch [Video] [How-To] Flash FFF/TWRP without Fastboot Cable
Step 1:
Root the kindle fire​Step 2:
Download fbmode and unzip.
Download ADB Files
Download fff-u-boot_v1.5.bin
Download a TWRP .img like openrecovery-twrp-2.2.2.1-blaze.img
or the One Zip Kindle.Fire.fastboot.Files.zip md5:5D68723E59AD5C1EFCCD3481C6D8E63B
Verify md5 checksums for files https://sites.google.com/site/sdshadowscollection/home/hash-checksums​Step 3:Create a folder in c drive named adb,
unzip/extract files,
copy AdbWinUsbApi.dll, AdbWinApi.dll, adb.exe, fastboot.exe, fbmode, fff-u-boot_v1.5.bin, and openrecovery-twrp-2.2.2.1-blaze.img to adb folder.​Step 4change directory to adb
Code:
cd\adb
Install fbmode by using
Code:
adb push fbmode /data/local/tmp
Set fbmode permissions by using:
Code:
adb shell chmod 755 /data/local/tmp/fbmode
Step 5:Run these commands here:
Code:
adb shell
su
cd /data/local/tmp
./fbmode
exit
exit
Code:
adb reboot
Kindle reboots to fastboot mode
Note: Fastboot screen is just like the boot up screen, but it doesn't change or have animation.
Step 6Run these commands in command prompt
Code:
fastboot -i 0x1949 flash recovery openrecovery-twrp-2.2.2.1-blaze.img
fastboot -i 0x1949 flash bootloader fff-u-boot_v1.5.bin
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Step 7Done​
Windows 8.1 users seems to be some driver issues, they are able to get drivers working in stock rom, but not Fastboot mode.
For those users, Soupkit maybe the only option.
Also died on me at step 6.... Nothing I've tried got it working...so caution if you're using this on windows 8.1
Sent from my Nexus 5 using XDA Free mobile app
so what do we do if its stuck at the boot screen? i set permissions on fbmode and rebooted and now im stuck at boot
Run the fastboot commands
sd_shadow said:
Non SoupKit Method
Watch [Video] [How-To] Flash FFF/TWRP without Fastboot Cable
Click to expand...
Click to collapse
This worked! I was skeptical about that saferoot utility that didn't say anything about supporting kindle fire, but figured I'd buy a factory cable if it didn't pan out. But it worked just like in the video. The saferoot utility did hang at "waiting for device" the first time I ran it and wouldn't stop even with control-c. I closed the command prompt window, left the KF connected, then restarted saferoot and it did its thing!
The other minor hitch was getting into fastboot. After rooting fbmode wouldn't execute in adb - I got the "couldn't write bp1, panic!" message. So I went into adb shell, did "su", and it worked. The rest was smooth sailing.
I just bought this KF on ebay for cheap because it had bad connection at the power jack. I'm pretty pleased with myself because I was able to reflow the solder this evening and get the microusb connector working again. Then I read that I couldn't root without a factory cable because it was on 6.3.3. I'm stoked that it worked without it. Next it's on to otterx! :good:
Thanks, sd_shadow!:
sd_shadow said:
Run the fastboot commands
Click to expand...
Click to collapse
Ah i never realized it was already in FB mode...maybe you could add that to your guide, works flawlessly but I believe most android users would believe a specific fastboot screen would pop up. I thought it was frozen
Thanks for your methods and help
jtj1825 said:
Ah i never realized it was already in FB mode...maybe you could add that to your guide, works flawlessly but I believe most android users would believe a specific fastboot screen would pop up. I thought it was frozen
Thanks for your methods and help
Click to expand...
Click to collapse
added Note: Fastboot screen is just like the boot up screen, but it doesn't change or have animation.
I have tried researching all day but when I type the "adb push fbmode /data/local/tmp" command, I get "error: device not found". I have tried all the drivers supplied in the various posts from xda to no avail. Any help would be appreciated!
mic81784 said:
I have tried researching all day but when I type the "adb push fbmode /data/local/tmp" command, I get "error: device not found". I have tried all the drivers supplied in the various posts from xda to no avail. Any help would be appreciated!
Click to expand...
Click to collapse
You need to check device manager, how is it listed?
Sent from my Amazon OtterX using Tapatalk
sd_shadow said:
You need to check device manager, how is it listed?
Sent from my Amazon OtterX using Tapatalk
Click to expand...
Click to collapse
Android ADB Interface
mic81784 said:
Android ADB Interface
Click to expand...
Click to collapse
should be in bootloader/fastboot if it says that.
When rom is running should say Android Composite ADB Interface.
If it is Fastboot mode you don't need fbmode command if in fb mode.
if it is running rom, could try rebooting pc and kindle, try a different usb cable or port
sd_shadow said:
Non SoupKit Method
Watch [Video] [How-To] Flash FFF/TWRP without Fastboot Cable
Step 1:
Root the kindle fire​Step 2:
Download fbmode and unzip.
Download ADB Files
Download fff-u-boot_v1.5.bin
Download a TWRP .img like openrecovery-twrp-2.2.2.1-blaze.img
or the One Zip Kindle.Fire.fastboot.Files.zip md5:5D68723E59AD5C1EFCCD3481C6D8E63B
Verify md5 checksums for files https://sites.google.com/site/sdshadowscollection/home/hash-checksums​Step 3:Create a folder in c drive named adb,
unzip/extract files,
copy AdbWinUsbApi.dll, AdbWinApi.dll, adb.exe, fastboot.exe, fbmode, fff-u-boot_v1.5.bin, and openrecovery-twrp-2.2.2.1-blaze.img to adb folder.​Step 4change directory to adb
Code:
cd\adb
Install fbmode by using
Code:
adb push fbmode /data/local/tmp
Set fbmode permissions by using:
Code:
adb shell chmod 755 /data/local/tmp/fbmode
Step 5:Run these commands here:
Code:
adb shell
su
cd /data/local/tmp
./fbmode
exit
exit
Code:
adb reboot
Kindle reboots to fastboot mode
Note: Fastboot screen is just like the boot up screen, but it doesn't change or have animation.
Step 6Run these commands in command prompt
Code:
fastboot -i 0x1949 flash recovery openrecovery-twrp-2.2.2.1-blaze.img
fastboot -i 0x1949 flash bootloader fff-u-boot_v1.5.bin
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Step 7Done​
Click to expand...
Click to collapse
after step 5 my the kindle is not recognized by the usb computer and it says on the command prompt waiting on device what can i do? im stuck on this boot screen plz help
what do i type to get it to at least boot back to normal?
mrdreamers said:
after step 5 my the kindle is not recognized by the usb computer and it says on the command prompt waiting on device what can i do? im stuck on this boot screen plz help
Click to expand...
Click to collapse
See my thread
[How To][Root] Kindle Fire 1 update 6.3.3 [2014]
Sent from my XT907 using Tapatalk
sd_shadow said:
See my thread
[How To][Root] Kindle Fire 1 update 6.3.3 [2014]
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
im not sure how this is going to help im stuck on boot screen on step 5 , can ya explain alittle plz?
mrdreamers said:
im not sure how this is going to help im stuck on boot screen on step 5 , can ya explain alittle plz?
Click to expand...
Click to collapse
Yes that is fastboot mode
Windows version?
Sent from my XT907 using Tapatalk
---------- Post added at 10:22 PM ---------- Previous post was at 10:21 PM ----------
Read my thread watch my video
Sent from my XT907 using Tapatalk
sd_shadow said:
Yes that is fastboot mode
Windows version?
Sent from my XT907 using Tapatalk
---------- Post added at 10:22 PM ---------- Previous post was at 10:21 PM ----------
Read my thread watch my video
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
im on windows 7 ultimate 64 bit
mrdreamers said:
im on windows 7 ultimate 64 bit
Click to expand...
Click to collapse
Used install.drivers.bat from Kindle Fire Utility v0.9.9?
Sent from my XT907 using Tapatalk
sd_shadow said:
Used install.drivers.bat from Kindle Fire Utility v0.9.9?
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
i dont think so i used the exe one, why should i run it?

ADB help

By Hashcode, Senior Recognized Developer on 1st February 2013, 10:57 AM over 5 years ago
STEP 1. Backup your stock partitions to your own HD for later if you need disaster recovery:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img" # This will take a few minutes
adb pull /sdcard/boot0block.img
adb pull /sdcard/stock-boot.img
adb pull /sdcard/stock-recovery.img
adb pull /sdcard/stock-system.img # This will take a few minutes
with that being said here is what happens, i can see adb is working
C:\adb>adb devices
List of devices attached
B0CC060324930545 device
C:\adb>adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
/system/bin/sh: su: not found
C:\adb>
I could go on on but, that would be more gibberish.
So, what is wrong? Did the commands change? Is my path set wrong on my pc? Is there a updated thread i just have not come across yet? Anyone?
I'll thank you now for any help
Nothing changed. If you get the device to show up with the adb devices command, then everything's theoretically set up. The only reason you're getting an error with su not being found is that you aren't rooted. Here's a quick way to get root (like actually super simple, considering you already have ADB working):
1) download the attached 8.1.4 bootloader file (this is ripped straight from my Kindle before I "upgraded" to 8.5.1 to test this out). you may consider placing it in the same folder as the adb program. Also download SuperSU and the latest TWRP build for this device.
2) shut down the kindle and make sure it's plugged in.
3) run fastboot -i 0x1949 getvar product, then power the kindle on. when you see "fastboot mode" on the kindle, you should see something in the command prompt that begins with "Jem". if you do, then it's working.
4) type fastboot -i 0x1949 flash bootloader jem_8-1-4_bootloader.img to flash the 8.1.4 bootloader. this is ESSENTIAL because the kindle won't boot custom (unsigned) images otherwise. more explanation below...
5) next, type fastboot -i 0x1949 flash recovery twrp.img, where twrp.img is the file name of the TWRP image you downloaded earlier.
6) type fastboot -i 0x1949 oem recovery to kick the Kindle into recovery mode. if all goes well, you should see "TWRP" on your device after a few moments.
7) copy the SuperSU zip you downloaded to the kindle's internal storage. then on the kindle, tap Install. Next, on the side menu to the left, swipe up from the bottom and tap "sdcard" (referring to the internal storage that you see on the computer when the kindle's plugged in). Tap the SuperSU .zip, and then swipe where indicated. Feel free to reboot the system, and then voila, you're rooted. You should be able to run those backup commands. As a bonus, you won't have to download TWRP or the bootloader image from that virus-laden d-h.st site - avoid it like the plague.
8) Because TWRP's already flashed, you can type adb reboot recovery from the stock OS to begin flashing a new ROM right away.
A couple side notes...
1) Because you've flashed TWRP, a custom recovery, there is no need whatsoever to run the stock recovery backup command. It's already been overwritten, and if you really need it (which, again, is highly doubted because it only lets you run a factory reset), you can actually extract the recovery image from the system partition. Just run adb pull /system/recovery-prod.img stock-recovery.img instead of the adb shell su... stock-recovery.img one.
2) You have to flash the 8.1.4 bootloader because the one you currently have is more than likely a newer version. Custom ROMs (and even recoveries like TWRP) rely on an exploit in the 8.1.4 bootloader in order to trick the device into running the image (and newer bootloaders have this exploit patched already). So technically, because the exploit has to be run every time, the bootloader is never "unlocked" - merely tricked. Without the older bootloader in place, you get what is referred to as the "red screen of death". It's not pretty, but it's not permanent either. (Just power off the kindle, and then run the fastboot command involving "getvar product" to get it to the bootloader so you can flash the 8.1.4 bootloader and go forward.)
Hope this helps!

Categories

Resources