i have just flashed a new recovery, and everything is just fine until i typed this:
fastboot reboot
and it does not reboot fastboot,stucks on first screen but!
pull out battery and entering by hardware key works, all fastboot, bootloader, my ROM, the new recovery.
so that confuses me, i can enter manually, but by adb i cant?
ADB works at the Bootloader and Recovery.
Fastboot works at the Fastboot mode.
Fastboot != ADB
Different commands, different purpose.
If you need reboot to fastboot command is:
"fastboot reboot-bootloader"
"fastboot reboot" just reboots your phone.
this is what I had to do on Linux Mint 12 but should work with most ubuntu based distros
1: download twrp
2: if you dont already have it then you need to download the linux fastboot binary, extract the .zip and place the extracted file in your androidsdk/platform-tools directory
2: place the file you downloaded from TWRP into your androidsdk/platform-tools directory
3: connect your fire to your computer and disable mass storage mode
4: open a terminal and cd to your androidsdk/platform-tools directory and enter the following commands pressing enter after each line
Code:
./adb shell
su
idme bootmode 4002
then back out of the adb shell by
Code:
exit
exit
then
Code:
./adb reboot
after it reboots to the "Kindle Fire" boot screen its time to flash the recovery
Code:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
once flashed and it installs and boots to the "firefirefire" screen (screen with the yellow sign and text that says "press power for recovery" you have to change the boot mode back out of fastboot
Code:
sudo ./fastboot oem idme bootmode 4000
sudo ./fastboot reboot
it should reboot to the "firefirefire" screen, to enter recovery press and hold the power button until it turns from green to orange then let go. You should boot into TWRP and be able to make your first backup.
from now on if you dont want to go into recovery then just let it sit and it will boot normally
Thanks to all the Teamwin members, agrabren for the port, pyrostic for testing, pokey9000 for the "FireFireFire" bootloader, and I am sure there are more but I dont know who you are so thank you.
if you can donate to these guys please do becuase without them we would just have an e-reader.
I am not responsable for any damage that YOU may cause buy following these directions.
not sure where i went wrong. i followed every step, it flashed, im stuck at the yellow triangle guessing im in fastboot.
i do fastboot oem bootmode 4000 and it gets stuck at waiting for devices.
issue the command with sudo
Nevermind, wasn't using ./ when I was issuing commands. As usual, need to pay better attention.
Thanks OP. Sweet.
My Fire got stuck at the splash screen after issuing the command idme bootmode 4002 and it won't load up. I can't get adb to recognize it anymore. Any advice?
abiezer said:
My Fire got stuck at the splash screen after issuing the command idme bootmode 4002 and it won't load up. I can't get adb to recognize it anymore. Any advice?
Click to expand...
Click to collapse
adb wont recogonize it after you change the boot mode thats where you issue the fastboot commands
smirkis said:
not sure where i went wrong. i followed every step, it flashed, im stuck at the yellow triangle guessing im in fastboot.
i do fastboot oem bootmode 4000 and it gets stuck at waiting for devices.
Click to expand...
Click to collapse
Download this file and place it in the folder your fastboot is located in: http://techerrata.com/file/twrp2/twrp-blaze-2.0.0RC0.img
do the following
open a command window where fastboot is located:
Step 1:
Code:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
if your window says "waiting for device" then reboot your device. if it boots into TWRP 2.0 then you are set move to Step 3. if it still says "waiting for device" close the window and then then open a command window where fastboot is located and do step 2.
Step 2:
Code:
fastboot -i 0x18d1 boot twrp-blaze-2.0.0RC0.img
if your window says "waiting for device" then reboot your device. if it boots into TWRP 2.0 then you are set move to Step 3. If it is still not doing anything, this is where my knowledge is no good anymore, and you should consult someone else.
TWRP should be showing on your screen. Close your old fastboot window and open a new command window where ADB is located. Proceed to Step 3.
Step 3:
Code:
adb shell
idme bootmode 4000
reboot
your device should reboot, and if you had problems with Step 3 try the following from your ADB command window
Code:
su
adb kill-server
adb start-server
adb devices
your device should be listed. If so try Step 3 again.
hope this helps or at least puts you in the right direction.
After executing fastboot, I get the following and the device stays on "Kindle Fire" splash screen. Any ideas?
Code:
$ ./fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
creating boot image...
creating boot image - 10240 bytes
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.006s]
booting...
OKAY [ 0.003s]
finished. total time: 0.009s
craftyguy said:
After executing fastboot, I get the following and the device stays on "Kindle Fire" splash screen. Any ideas?
Code:
$ ./fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
creating boot image...
creating boot image - 10240 bytes
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.006s]
booting...
OKAY [ 0.003s]
finished. total time: 0.009s
Click to expand...
Click to collapse
Sounds like you are in fastboot, but I would expect to see the yellow triangle logo and not the Kindle Fire one. Anyway, try to see if running the following works:
Code:
./fastboot oem idme bootmode 4000
./fastboot reboot
sl0ttedpig said:
Sounds like you are in fastboot, but I would expect to see the yellow triangle logo and not the Kindle Fire one. Anyway, try to see if running the following works:
Code:
./fastboot oem idme bootmode 4000
./fastboot reboot
Click to expand...
Click to collapse
Tried setting bootmode with fastboot, but it just sits there at "< waiting for device> ". Tried rebooting Kindle but fastboot is still hanging up there.
EDIT: Ok, had to pass "-i 0x1949" to fastboot. Got the device back, going to try it all over again
craftyguy said:
Tried setting bootmode with fastboot, but it just sits there at "< waiting for device> ". Tried rebooting Kindle but fastboot is still hanging up there.
Click to expand...
Click to collapse
what os is on ur computer? sounds like a driver issue.
Sent from my HTC Glacier using xda premium
smirkis said:
what os is on ur computer? sounds like a driver issue.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
I'm on Fedora 16 x86_64. I did all of the adb interactions on a Windows 7 system, however it looks like adb isn't set up correctly on this Fedora box I'm on now. I have (what I think at least) the udev rules set for Kindle Fire. Looks like I have some more reading to do!
EDIT: adb up and running. For anyone who has this issue, add "0x1949" to ~/.android/adb_usb.ini, and restart adb!
---------- Post added at 12:15 PM ---------- Previous post was at 11:32 AM ----------
Alright, my week-old Kindle Fire does not agree with this procedure. The twrp image does not seem to be flashing at all (fastboot returns after .009s and device never reboots to recovery)
try rebooting manually n see if u get fastbot.
Sent from my HTC Glacier using xda premium
craftyguy said:
I'm on Fedora 16 x86_64. I did all of the adb interactions on a Windows 7 system, however it looks like adb isn't set up correctly on this Fedora box I'm on now. I have (what I think at least) the udev rules set for Kindle Fire. Looks like I have some more reading to do!
EDIT: adb up and running. For anyone who has this issue, add "0x1949" to ~/.android/adb_usb.ini, and restart adb!
---------- Post added at 12:15 PM ---------- Previous post was at 11:32 AM ----------
Alright, my week-old Kindle Fire does not agree with this procedure. The twrp image does not seem to be flashing at all (fastboot returns after .009s and device never reboots to recovery)
Click to expand...
Click to collapse
woot for fedora! anyway, i set things up via /etc/udev/rules.d/51-android.rules and at first I had this...
SUBSYSTEM=="usb", SYSFS{idVendor}=="1949", MODE="0666"
and everything was cool. but after flashing twrp, i noticed there was firefirefire 1.0 out where previously i had flashed .9 so i thought id update I went to update and after putting the device in fastboot mode, it rebooted to the bootloader where fastboot wasnt recognizing the device started digging around and found windows users having driver issues and thought to myself... we dont have drivers BUT we do have rules!! added this line to the udev rules
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
and everything working as it should again
Hi, I am trying to Re-Lock my Galaxy Nexus GSM version, I've downloaded the SDK files (adb-mac and fastboot-mac) and all the image files and I am trying to execute the following commands:
adb reboot bootloader
fastboot flash bootloader bootloader-toro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.ek02.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img
fastboot reboot-bootloader
fastboot -w update image-mysid-icl53f.zip
fastboot reboot-bootloader
fastboot oem lock
With the phone in normal mode I connect the USB cable to the computer, start Terminal windows and run the first command, "./adb-mac reboot bootloader" and the phone will boot into the "Fastboot Mode", then I try to execute "./fastboot-mac devices" to make sure the phone is connected and properly detected and I get nothing.
If I try to execute "./fastboot-mac flash bootloader bootloader-toro-primekk15.img" I get the message <waiting for device> and it will stay there forever.
Do you know what might be the problem ?, is there other method to do this ?, go back to Stock ROM and Re-Lock the device ?, thanks
You must also install the Samsung usb drivers. I have no idea how to do this in mac. A simple search will help you tho.
Been an incredibly bad week for me as far as technology is concerned. Everything around me seems to be breaking apart form my new One X. That is of course.. until now..
I'm trying to flash TripNDroid's CM10 Rom to my phone by following my self written instructions that have worked like a charm for me so far.
Enter Fastboot on phone. Open the command line window in the relevant place in windows and check it's connected using 'fastboot devices' command. Then:
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot erase recovery
fastboot flash recovery-clockwork-touch-5.8.4.0-endeavoru.img
fastboot flash boot boot.img
Enter recovery and flash the ROM.
However, I'm getting mixed responses in the command line. Very occasionally I will type a command in and it will accept it. and say 'Done' but 90% of the time it will say 'FAILED (remote: 0000004)' or occasionally 'remote: not allowed'
I have checked that the usb is connected (it is the original cable) and used the fastboot devices command to confirm this. I have tried rebooting the bootloader and redownloading fastboot and the files to be flashed. Completely stuck D:
My kindle fire is bricked. I'm not sure it can be undone, as fastboot can't seem to change the bootmode.
Where I'm at (short version):
Mac os x 10.6.8
Kindle stuck on the amazon stock "Kindle fire" logo.
Kindle connected with factory cable.
Log:
> fastboot -i 0x1949 getvar product
product: kindle
finished. total time: 0.000s
> fastboot -i 0x1949 oem idme bootmode 4000
...
^C
How I go here:
I tried the KFU on a Windows VM running on Mac osx 10.6.8. Yes, that was dumb.
I went for the quick and dirty solution, it did not end well.
I've read the kindle beginners guide. Excellant resource. Switched to the Mac terminal interface.
My Knowledge:
I'm a knowledgeable unix user, android newbie. Meaning I know just enough to get myself in trouble.
Any suggestions would be appreciated. About the only other thing I can think to try is a linux interface instead of MAC.
Thanks,
Ann
The command you posted was successful. Did you reboot the device?
soupmagnet said:
The command you posted was successful. Did you reboot the device?
Click to expand...
Click to collapse
Yes I tried issuing the reboot command to the same result. Neither command returns to the command prompt, a ^C is required.
(apologies if this post appears twice.)
adavis749 said:
Yes I tried issuing the reboot command to the same result. Neither command returns to the command prompt, a ^C is required.
(apologies if this post appears twice.)
Click to expand...
Click to collapse
i think u dont have a recovery software and a rom flashed on ur kindle fire..first flash twrp.img(u can have it downloaded for u by KFU) from terminal..dont forget to open terminal in the location of twrp.img..then
fastboot flash recovery twrp.img
fastboot oem idme bootmode 5001
fastboot reboot
this should install twrp on ur KF
then mount it as usb mass storage through twrp and format it on ur mac or pc or whatever..sdcard partition needs to be formatted
then u can transfer .zip(ROM) file to it and flash it from twrp
after all this again revert bootmode to 4000 and u shud have ur kf running ur rom..
feel free to thank helpers!!!
prahladvarda said:
i think u dont have a recovery software and a rom flashed on ur kindle fire..first flash twrp.img(u can have it downloaded for u by KFU) from terminal..dont forget to open terminal in the location of twrp.img..then
fastboot flash recovery twrp.img
fastboot oem idme bootmode 5001
fastboot reboot
this should install twrp on ur KF
then mount it as usb mass storage through twrp and format it on ur mac or pc or whatever..sdcard partition needs to be formatted
then u can transfer .zip(ROM) file to it and flash it from twrp
after all this again revert bootmode to 4000 and u shud have ur kf running ur rom..
feel free to thank helpers!!!
Click to expand...
Click to collapse
That shouldn't matter. Even without recovery or a ROM installed, the device will still boot to a blank screen.
Sometimes after changing bootmodes in fastboot, the reboot command doesn't work. Just hold the power button until it shuts off and start it again.
soupmagnet said:
That shouldn't matter. Even without recovery or a ROM installed, the device will still boot to a blank screen.
Sometimes after changing bootmodes in fastboot, the reboot command doesn't work. Just hold the power button until it shuts off and start it again.
Click to expand...
Click to collapse
I have tried that as well.