I did adb reboot bootloader and it goes into starting fastboot.
Then i do fastboot flash boot boot.img and says in CMD fastboot is not recognized as internal or external command.
So the ADB is working just not the fastboot command.
Google fastboot binary. Download the file for your OS and put it in the same directory as your adb files.
so i keep having the disappearing status bar issue on CM7 so i booted into TWRP, fixed permissions wiped cache and dalvik and hit reboot system. now my kindle will only boot into TWRP. anyone know how to get it to boot to CM7?
Sent from my SGH-T959V using xda premium
Please use the search feature, this has been discussed countless times!! You need to set your device to boot in 'normal' mode via adb. The kindle fire utility also has an option to do this....
Sent from my Kindle Fire using Tapatalk
you said "boot to recovery" in cm7 - disable this option for the future !
http://forum.xda-developers.com/showthread.php?t=1399889
or
http://forum.xda-developers.com/showthread.php?t=1428428
or
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot oem idme bootmode 4000
fastboot reboot
b63 said:
you said "boot to recovery" in cm7 - disable this option for the future !
http://forum.xda-developers.com/showthread.php?t=1399889
or
http://forum.xda-developers.com/showthread.php?t=1428428
or
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot oem idme bootmode 4000
fastboot reboot
Click to expand...
Click to collapse
i wish i knew how to use adb commands
Sent from my SGH-T959V using xda premium
then use the unbrick utility (second link) - extract it to c:\ - run it
use option 2 - recovery loop
b63 said:
then use the unbrick utility (second link) - extract it to c:\ - run it
use option 2 - recovery loop
Click to expand...
Click to collapse
i can't as i'm on a mac and have no access to a windows computer...
i don't know about a mac
but you should have a directory where an adb executable is located
there you should open a command shell and issue the nessesary commands
this is what i found:
Android SDK Mac: http://developer.android.com/sdk/index.html
Platform tools installed: Go to the tools folder in the sdk. Make sure fastboot and adb are there. IMPORTANT: Check fastboot by doubling clicking it (make sure it doesn't say binary doesn't execute).
Adjustments: Make sure that you are using the ./ version of the commands. When it says to input SU, input su.
FAQ: Stuck at fastboot, and adb is not connecting? Depending on circumstances, answer may vary. In my case, here is the terminal log (AMA is my computer):
AMA:~ Aidan$ cd /Users/Aidan/Android/android-sdk-mac/platform-tools
AMAlatform-tools Aidan$ ./adb devices
List of devices attached
AMAlatform-tools Aidan$ sudo ./fastboot oem idme bootmode 4000
then power off / on
update:
think you can use my previous commands:
now you need to first navigate to your platform-tools folder in your android sdk folder using terminal.
Go to utilities in the applications tab in finder. Open up Terminal.
Now type the following line to navigate to the platform-tools folder.
cd ~/androidsdk/platform-tools
for me it is this because my SDK folder is named "androidsdk", if your's is named differently, insert it's name where androidsdk is.
followed by that you can start using ADB. Instead of running things as
adb root, or adb reboot, you need to include
./ before the commands, IE: ./adb root, or ./adb push
IE THE FIRST STEP IS "adb root", rewrite this is "./adb root"
from then on, include that ./ before any command.
ok so i have both fastboot and adb working, now what do i have to type in order to get this to reboot properly (i'm sorry for asking so much, but i'm a COMPLETE adb noob).
we have look what you have available - adb or fastboot
as first:
./adb devices
get a response ?
if not:
./fastboot -i 0x1949 getvar product
it should return "kindle"
gimme the results
the first time it worked and then when i did it again as a double check, my kindle started to boot (as it always does when it's plugged in and now it is stuf at the yellow triangle....
EDIT: finally got it to turn off, so fastboot registers it, what next
what commands did you exactly enter in the terminal ?
both the adb and fastboot commands you just showed me. but everything is back to normal, what do i do know that the kindle is recognized?
please copy and paste what is in the terminal window, that i can see to which command it has responded
what do you mean with back to normal ?
normal boot to os ? or to twrp again ?
basically the commands are the same as for windows - you have just to add ./ in the front:
this are the comands to set bootmode to normal:
when you have fastboot available:
./fastboot -i 0x1949 oem idme bootmode 4000
./fastboot -i 0x1949 reboot
or
./fastboot -i 0x18d1 oem idme bootmode 4000
./fastboot -i 0x18d1 reboot
or
./fastboot oem idme bootmode 4000
./fastboot reboot
when you have adb available:
./adb shell su -c "idme bootmode 4000"
./adb reboot
fastboot is the one that responded.
Code:
Macintosh:platform-tools recardeeps317$ ./fastboot oem idme bootmode 4000
< waiting for device >
...
OKAY [ 0.201s]
finished. total time: 0.201s
Macintosh:platform-tools recardeeps317$ ./fastboot reboot
but it doesnt actually reboot the Kindle. it gets hung at the triangle still. if i get it to boot back to TWRP could i just make a back up and reflash CM7?
EDIT:
finally got it to reboot into CM7 with:
Code:
Macintosh:platform-tools recardeeps317$ ./fastboot -i 0x18d1 reboot
< waiting for device >
rebooting...
finished. total time: 0.000s
ok - now we know it is responding to fastboot without the address initialisation commands (that depends on the version of fff - the bootloader)
did you try to power it off manually (pwr button ~30sec) ?
why would you like to reflash ? is it defect or now just not starting ?
and yes you can switch it to other bootmodes as well:
normal = 4000
fastboot = 4002
recovery = 5001
now it's up to you what you will like to do ...
UPDATE: hurraaa !!! congratulations ! - glad that it's working again !
please mark the subject of the topic (edit first post) to [Solved]
I made a mistake that when I do the following commands:
Code:
unzip fbmode.zip
adb push fbmode /data/local/fbmode
adb shell chmod 755 /data/local/fbmode
adb shell /data/local/fbmode
adb reboot
But i forgot to copy the TWRP 2.0.img to the device.
Now KF stuck in the fbmode, i can not get out of it. Anyone know the command to get out of fbmode, I did try fastboot -i 0x1949 reboot but it always boot to fbmode.
Thank you.
*************
I try the command
Code:
fastboot -i 0x1949 oem idme bootmode 5002m
then my KF has boot into normal mode.
Problem solve. Search button win )
Code:
fastboot -i 0x1949 oem idme bootmode 4000
That should do it.
If you are trying to install it, just run...
Code:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
u copy twrp to your fastboot folder not your kf, than do fastboot boot twrp2.0.img or whatever u have it named.
Sent from my HTC Glacier using xda premium
smirkis said:
u copy twrp to your fastboot folder not your kf, than do fastboot boot twrp2.0.img or whatever u have it named.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
I did copy to my fastboot folder in my PC but didnt work, I think the correct way its copy into device root folder.
Hi all,
I have an issue where my device is not recognized by adb when in recovery.
it shows something like below when in recovery
adb devices
000000000 device
when is device is in fastboot
fastboot devices
it shows the serial number
but when i run command
fastboot reboot
rebooting...
finished. total time: 0.001s
and the device wont reboot,
also other fastboot commands like
fastboot flash recovery /(whatever path) will end up with some error
Please can any one help me out with this...
FYI: all commands in adb work fine with my Nexus one but these are the issues with HTC hero G2.
Wrong section, this should be on Q and A
If you are on linux try sudo adb kill-server and then sudo adb start-server
Recently,something went wrong with my PH-1,so I decided to restore my phone.
My PC has been installed ADB and Fastboot system-wide with 15 seconds ADB Installer v1.4.3.It works fine with my Oneplus3 and Nexus6P but ruined my PH-1.
After unlocking the bootloader, the PH-1 was not being recongized via fastboot.Only with vendor ID,fastboot can work.
Code:
Code:
fastboot devices -i 0x2e17
I didn't treat it as a big deal.I fellow this thread [STOCK][DUMPS][FIRMWARE] Essential stock firmware and rom dumps to restore my PH-1.I got no errors, but unfortunately,my PH-1 was caught in a bootloop,it was keeping reboot into bootloader.I tried running flash-all.sh in Ubuntu,but changed nothing.
After a few days working on this problem,I finally figure out that maybe outdated fastboot were to blame. I uninstalled old fastboot driver and executables and replace them with Offical Essential device driver.Finally,after running one-click script flash-all.bat,my PH-1 come back to live!
If you run into those problem below,you may need to replace your installed fastboot with offical driver:
1. In Fastboot, you can use this command:
Code:
fastboot devices
After you run this command and you got nothing return.It means fastboot doesn't recognise your PH-1.
2. In Fastboot, you can use this command:
Code:
fastboot getvar current-slot
After you run this command and you cannot get a result of what partition your system is currently on (a or b).
3. When fastboot sends a large partition image( e.g. system) to PH-1 ,fastboot doesn't send it separately.
Normally fastboot will separate system image into four parts.