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
Related
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 was trying to change the keyboard and have converted KF to brick
The mistake that i done was that i had uploaded wrong settings.db and now KF its stuck at boot logo... i can see the animation and when i connect device to computer (Win) it makes 2x sounds (Beep-beep), the device its visible in "safely remove hardware..." and new "Removable media" its visible in My Computer, but its disabled.
I have already read&tried tons of possible things, like "Kindle Fire Utility", "fastboot ...", "adb ..."...
- http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4
- http://forum.xda-developers.com/showthread.php?t=1356257&page=70
- ...
but with no luck
When i try to run commands adb or fastboot (with -i 0x1949) its just says "waiting for device" and nothing happens... not even if i reboot manually (~20s power button press) or disconnect&connect KF.
Is there still chance for my KF?
-----------------
EDIT: Solved by b63
there is always a chance - only a question of tools an effort ...
do you have fff (the yellow triangle) and twrp on the kf ?
None... i was think of instaling TWRP, but first i wanted to change the keyboard
bad decision - now you have to get to fastboot somehow
to have all tools available i would recommend to download kfu (if you not allready have), extract it to c:\ and rename to "kfu" that it is c:\kfu
all needed commands are in the tools directory of kfu (c:\kfu\tools)
open a (elevated) command prompt and cd to c:\kfu\tools
issue "fastboot -i 0x1949 oem idme bootmode 4000"
when it says <waiting for device> power off the kf by holding power button for ~20sec till it turns off
power on again
the command should be picked up and finished
power off/on again
the kf should stay at "kindle fire" static (fastboot)
check with "fastboot -i 0x1949 getvar product"
tell me if you'r gone so far ...
no luck... boot animation is in loop and fastboot is waiting for device
ok - need to try an other method
what says your device manager under "android phone" ?
do you see "kindle" or "unknown device" ?
if yes you should update the driver
which drivers do you use ? kfu or sdk ?
when you say boot animation in loop means the "kindle fire" animated - right ?
or is it boot looping ? - then you will have to charge it for some hours with the wall charger
container.mariborcan.net/datoteke/kfdm.jpg (can't add img link, because i'm new on forum )
everything worked until now...
when you say boot animation in loop means the "kindle fire" animated - right ?
Click to expand...
Click to collapse
it's animated... then disapperes for second... then animates... disappears for second... and looping again and again...
sounds like the 3-5 sec bootloop -> out of battery
in this case -> wall charger and hard power off to allow charging
or are you absolutely shure it's fully loaded ?
what about the device manager ?
b63 said:
sounds like the 3-5 sec bootloop -> out of battery
in this case -> wall charger and hard power off to allow charging
or are you absolutely shure it's fully loaded ?
Click to expand...
Click to collapse
i will try to charge it once more...
b63 said:
what about the device manager ?
Click to expand...
Click to collapse
device manager says "Android Composite ADB interface" (container.mariborcan.net/datoteke/kfdm.jpg), "safely remove hardware" recognize device as "Kindle"
sounds good - any reaction on "adb devices" ?
have made a little batch file to test adb connection
please place it in the tools directory of kfu, rename from .txt to .bat and run it from the command line
it should check if you can reach adb commands - if yes then there is a chance to switch the kf to fastboot mode - this is necessary to install fff & twrp
the batch is waiting for device - means if the output don't change for some seconds please restart the kf and check if the commands are resumed
maybe copy and paste the output
would also check the adb_usb.ini in the .android folder in your personal directory
it should include 0x1949
if you get response to "adb devices" you can follow this post:
http://forum.xda-developers.com/showpost.php?p=21803658&postcount=29
usb driver are working ok...
i have rechanged KF and now i "adb devices" recognizes KF...
C:\kfu\tools>adb devices
List of devices attached
3700002600000001 device
Click to expand...
Click to collapse
but if i run "fastboot devices" it doesnt show anything and it's still "waiting for devices" if i try to "fastboot -i 0x1949 oem idme bootmode 4002"
you'r missing point 2 of the description
first you need to switch to fastboot mode - then you can use the fastboot commands
a other option is to try to use kfu option 5 to install twrp - it should do it for you
btw. since fastboot commands only work in fastboot mode your above command wont make sense - see here:
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
here all the possible commands to change bootmode:
with adb (secure kernel):
adb shell su -c "idme bootmode 4000"
adb reboot
or (twrp or unsecure kernel):
adb shell 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
the number is the bootmode you want to switch to:
normal boot -> 4000
fastboot -> 4002
boot to recovery -> 5001
and if you know:
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
then you only have to count 1 and 1 together and can master nearly each hanging situation !
Click to expand...
Click to collapse
My KF is stuck at the KF logo too.. windows sees adb device but when using the command "adb devices" nothing shows up. It did work when I was trying to install recovery then this happened.. I read about a "factory cable" which I am trying to make or get.. So am I correct in assuming that is my only real way of saving my device since adb won't connect?
Sent from my Galaxy Nexus using XDA App
not necessarily - your device might be in fastboot mode - only fastboot commands are working
try "fastboot -i 0x1949 getvar product" and see if something returns
if you did with kfu just select option 1 - bootmode normal
or manually:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
b63 said:
not necessarily - your device might be in fastboot mode - only fastboot commands are working
try "fastboot -i 0x1949 getvar product" and see if something returns
if you did with kfu just select option 1 - bootmode normal
or manually:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
wow THANKS where is the :doh: button... i used the KFU and option 1 and normal bootmode and it rebooted and came back.. you R the MAN!!
I can't believe i didn't do that last night with all the other stuff i tried..
I now have a fully working kindle fire AGAIN
it wont work...
i have changed driver front and back "android composite adb interface/android adb interface", tryed everything and it just wont go i can't get it in fastboot...
b63 please read my PM...
allready replied ...
b63 solved the problem
to sum up what he did... (all console commands are written with prefix >>)
transfered files from fbmode-0.9.zip (http://forum.xda-developers.com/showthread.php?t=1414832) to KF to folder /data/local/tmp
>> adb push fbmode /data/local/tmp
>> adb shell chmod 755 /data/local/tmp/fbmode
>> adb shell /data/local/tmp/fbmode
>> adb reboot
than checked device...
>> fastboot -i 0x1949 getvar product
it's should give:
product: kindle
finished. total time: 0.004s
than installed TWRP...
>> fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
downloading 'boot.img'... OKAY [ 2.892s]
booting... OKAY [ 0.001s]
finished. total time: 2.901s
checked again:
>> fastboot -i 0x1949 getvar product
product: kindle
finished. total time: 0.001s
than flashed bootloader...
>> fastboot flash bootloader u-boot.bin
sending 'bootloader' (211 KB)... OKAY [ 0.063s]
writing 'bootloader'... OKAY [ 0.507s]
finished. total time: 0.570s
than changed bootmode to recovery
>> fastboot oem idme bootmode 5001
... OKAY [ 0.196s]
finished. total time: 0.198s
rebooted...
>> fastboot reboot
rebooting...
finished. total time: 0.014s
checked if device is in recovery
>> adb devices
List of devices attached
37************ recovery
then we fixed settings.db file that I have f*** up ... we installed old file and rewrited permissions to system.system with 666
on the end we switched back to normal bootmode and rebooted...
>> adb shell idme bootmode 4000
<idme> write 4000 to offset 0x1000
>> adb reboot
Click to expand...
Click to collapse
Hope this helps someone...
hello guys,
i rooted my phone, but it has a display mistake and i will send it to zte.
i flashed the original stock rom with twrp, and i flashed the stock recovery with twrp! with adb and fastboot not working!!
FAILED (remote: unknown command) by any commands, example: fastboot flash recovery recovery.img the failure!
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
364f5261 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
364f5261 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
FAILED (remote: unknown command)
finished. total time: 0.016s
i dont know if my bottloader is locked or unlocked and i must locked it because i want to sent my device to zte!
any ideas?
thank you very much
my device axon7 2017G.
If you never connected the A7 to your computer and sent the fastboot command "fastboot oem unlock" to your device, it's still locked.
Additionally, when you reboot into bootloader, it'll display the lock status on the screen.
xtermmin said:
If you never connected the A7 to your computer and sent the fastboot command "fastboot oem unlock" to your device, it's still locked.
Additionally, when you reboot into bootloader, it'll display the lock status on the screen.
Click to expand...
Click to collapse
Hello i rooted My device with the axon7 root tutorial, ADB reboot edl and axon7root.exe and so on.
After that method is the bootloader locked or unlocked?
If i reboot in fastboot modus, there is only a zte Android sign, nothing lock status in screen.
pocco00 said:
Hello i rooted My device with the axon7 root tutorial, ADB reboot edl and axon7root.exe and so on.
After that method is the bootloader locked or unlocked?
If i reboot in fastboot modus, there is only a zte Android sign, nothing lock status in screen.
Click to expand...
Click to collapse
Rooting with axon7root.exe does not unlock your bootloader. If you never followed this guide (http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165) or never sent the fastboot command "fastboot oem unlock" to your device, you're still locked.
If ADB shows devies correct then use fastboot with sudo command.
ie, sudo fastboot reboot