Should I be able to find my adb device while my phone is only booting to HBOOT 0.93.0001?
Been stuck on this for days...and it's killing me!
PS. When I plug my phone in to
PC it says "Android ADB interface installed" "Ready to use"
But when I cmd the adb to find devices "adb devices" it shows blank
P.S. Phone: HTC Desire
Unrooted
S-ON
Unable to boot, can only get to HBOOT.(so cant turn debugging on)
Trying to get a goldcard to flash a new rom and see if i can unbrick
Reason for unable to boot is - It had been rebooting itself for weeks, slowly getting worse, until now, when I cant get it booted at all.
budron said:
Should I be able to find my adb device while my phone is only booting to HBOOT 0.93.0001?
Been stuck on this for days...and it's killing me!
PS. When I plug my phone in to
PC it says "Android ADB interface installed" "Ready to use"
But when I cmd the adb to find devices "adb devices" it shows blank
P.S. Phone: HTC Desire
Unrooted
S-ON
Unable to boot, can only get to HBOOT.(so cant turn debugging on)
Trying to get a goldcard to flash a new rom and see if i can unbrick
Reason for unable to boot is - It had been rebooting itself for weeks, slowly getting worse, until now, when I cant get it booted at all.
Click to expand...
Click to collapse
adb won't work when you are in bootloader (It won't work until Linux is up). "fastboot" will work over USB in bootloader->Fastboot.
I believe RUU will work on fastboot mode.
Related
I boot my Acer Iconia Tab A200 into fastboot mode (robot lying down and RED exclamation mark over it). I plug it into my Windows 7 (64bit) desktop computer with SDK installed, and from the directory with fastboot.exe I type FASTBOOT DEVICES but the device is not being seen, it just goes back to the prompt, like the command executed but didn't do anything. I assume this is because the drivers aren't installed. But I don't know how to install the "adb drivers". How is this done?
Go to Acer support page, you'll get the drivers there.
This device will not fully boot. It gets stuck at an "encryption unsuccessful" message. I'm trying to flash a rom image from my desktop computer using fastboot, but when my tablet is in fastboot mode, my desktop computer won't recognize it. ie adb devices command doesn't show that there is any device connected, and I think it's because the drivers aren't installed. I think those Acer drivers only work if the tablet can be fully booted.
Installed the Google USB Drivers from the SDK Manager already. Don't know what's wrong.
Alright I figured out how to get fastboot to interface with my Android tablet. The problem was that I wasn't getting the tablet into fastboot mode to recieve commands.
But now it's working. However, I'm trying to unlock the bootloader and it gives me an errors that says:
SetUnlockedMode: Error occured while unlock the device ...
Fastboot: Failed to set unlock mode
I have to unlock the bootloader before I flash an image to the tablet, right ?
Yep, surely.
Okay, so basically I am a HUGE idiot. My phone has been running the latest version of ParanoidAndroid and I decided that I wanted to try MIUI. I booted into TWRP v2.6.3 and wiped everything a couple of times before installing it, and I forgot to install the boot.img afterwards (it was s-on). So now everytime I turn the phone on, it is just always on the boot animation for an eternity, and my computer won't recognize my phone so I can't use fastboot or use an RUU. I am also unable to flash PH98IMG from the phone itself. Is there anything I can do to fix this? Thank you very much in advance.
trp6senile said:
Okay, so basically I am a HUGE idiot. My phone has been running the latest version of ParanoidAndroid and I decided that I wanted to try MIUI. I booted into TWRP v2.6.3 and wiped everything a couple of times before installing it, and I forgot to install the boot.img afterwards (it was s-on). So now everytime I turn the phone on, it is just always on the boot animation for an eternity, and my computer won't recognize my phone so I can't use fastboot or use an RUU. I am also unable to flash PH98IMG from the phone itself. Is there anything I can do to fix this? Thank you very much in advance.
Click to expand...
Click to collapse
Take out the battery, put it back together, power on the phone while holding down the volume down key til you get the splash screen, that'll boot you to the bootloader...
No I understand that, but there's nothing I can do from the bootloader. Once I get there, I can either go to TWRP or choose Fastboot. When I choose fastboot, it will say Fastboot USB after connecting to my PC but it will still not show up or be recognized (and I have the drivers). My only other options are Recovery (TWRP), factory reset (also TWRP), clear storage, simlock, and image crc. All I need to do is load the boot.img file, but it appears to me I have no way of doing that now.
trp6senile said:
No I understand that, but there's nothing I can do from the bootloader. Once I get there, I can either go to TWRP or choose Fastboot. When I choose fastboot, it will say Fastboot USB after connecting to my PC but it will still not show up or be recognized (and I have the drivers). My only other options are Recovery (TWRP), factory reset (also TWRP), clear storage, simlock, and image crc. All I need to do is load the boot.img file, but it appears to me I have no way of doing that now.
Click to expand...
Click to collapse
Being seen in fastboot has nothing to do with the ROM at all, you need to troubleshoot this from the PC end. When you start fastboot on the phone and connect to your PC you get nothing? Not even a connect sound?
acejavelin said:
Being seen in fastboot has nothing to do with the ROM at all, you need to troubleshoot this from the PC end. When you start fastboot on the phone and connect to your PC you get nothing? Not even a connect sound?
Click to expand...
Click to collapse
I do get the connect and disconnect sounds. Whenever it makes the connect sound, it doesn't show up under "Devices with Removable Storage." When I heard the connect sound the first time I went to the cmd prompt and typed "fastboot devices" but it showed nothing.
trp6senile said:
I do get the connect and disconnect sounds. Whenever it makes the connect sound, it doesn't show up under "Devices with Removable Storage." When I heard the connect sound the first time I went to the cmd prompt and typed "fastboot devices" but it showed nothing.
Click to expand...
Click to collapse
It won't show up as a drive at all in Fastboot mode, to see if it is connected properly go to Device Manager and look for ADB Interface -> My HTC, if it isn't there then your drivers are not installed properly. Drivers come from HTC Sync, which can be downloaded here: http://www.htc.com/us/support/content.aspx?id=6196 once installed and the connections in Fastboot and ADB verified to be working, HTC Sync can be uninstalled (the drivers will stay).
When you run "fastboot devices" you get nothing? Or do you get something like "< waiting for device >" or literally nothing?
What version of Windows are you running, you need to be on Windows 7 or older? Running under Windows 8 is not recommended.
acejavelin said:
It won't show up as a drive at all in Fastboot mode, to see if it is connected properly go to Device Manager and look for ADB Interface -> My HTC, if it isn't there then your drivers are not installed properly. Drivers come from HTC Sync, which can be downloaded here: <link> once installed and the connections in Fastboot and ADB verified to be working, HTC Sync can be uninstalled (the drivers will stay).
When you run "fastboot devices" you get nothing? Or do you get something like "< waiting for device >" or literally nothing?
What version of Windows are you running, you need to be on Windows 7 or older? Running under Windows 8 is not recommended.
Click to expand...
Click to collapse
Ah, that may be my problem then, as I am on a Windows 8 computer. I will try all of this on a friends W7 computer in the next few hours and report back with the results. And when I did fastboot devices it literally said nothing and was ready for another command. Thanks for the help!
trp6senile said:
Ah, that may be my problem then, as I am on a Windows 8 computer. I will try all of this on a friends W7 computer in the next few hours and report back with the results. And when I did fastboot devices it literally said nothing and was ready for another command. Thanks for the help!
Click to expand...
Click to collapse
You can also use a live Linux CD like Ubuntu and boot that and install the Linux version of ADB, it works fine.
I just flashed this rom http://forum.xda-developers.com/showthread.php?t=2752956 (odexed) but something went wrong and the phone won't boot. I
If i let it boot past the bootloader, all i get is a dark screen. I can tell the screen is on but nothing else happens. If i reboot with volup/power and then press voldown I only get the hboot screen. Pc does not recognize the phone in ether mode. HTC sync just says no device connected as well as adb commands. cmd promts just get stuck on "waiting for device"
Any help would be appreciated
ok, i was able to fix it. I hadn't tried adb while on the blank screen. It responded to adb commands then and was able to reboot into recovery that way. This thread can be deleted or left for future reference.
Thanks Alliance!!!
I unlocked the bootloader and went to root. on the first reboot after rooting it's stuck on the boot animation. When i plug the device into my PC and use the cmd prompt "adb devices" it won't see it. I help the power button and vol down to get to fastboot and my pc still won't see it. i've tried to factory reset though fast boot, says erasing, then reboots and still stuck. I updated everything in adb and still nothing. Everything went fine with unlocking the bootloader, but rooting it totally messed something up.
I can't seem to figure out how to get my PC to see this thing again. It's kind of a crap tablet to begin with, and now i brick it? totally frustrated.
Thanks
when you connect to pc,did you hear pop up connect sound..if yes then you connect to your pc..download google factory image,flash system.img,boot.img and all other .img image..hopefully you can restore tab back to nermal..good this is your tablet already unlocked bootloader.
Sent from my Nexus 9 using Tapatalk
Adb can do almost nothing when your device is in fastboot mode. Use fastboot to see if your device is connected to your computer if you didn't do so.
try "fastboot devices".
corkiejp said:
try "fastboot devices".
Click to expand...
Click to collapse
I just got "waiting for any device". I have the path set up to "C:\android-sdk\tools;C:\android-sdk\platform-tools". I haven't changed anything since i unlocked the bootloader so i'm just confused.
kacang87 said:
when you connect to pc,did you hear pop up connect sound..if yes then you connect to your pc..download google factory image,flash system.img,boot.img and all other .img image..hopefully you can restore tab back to nermal..good this is your tablet already unlocked bootloader.
Click to expand...
Click to collapse
The safely removed hardware icon does show up in the task bar. When i got to printers and devices there is an "android".
https://www.dropbox.com/s/a5chez6r9cuxjzo/Capture.JPG?dl=0
Can i use that port to force adb to see it? Not sure if this helps
gotta run to work, i'll mess with it this afternoon. Thanks guys.
First make sure your in "fastboot" mode and not in the bootloader.
Your device should show up as under Android Device as "Android Bootloader Interface" in device manager on your PC.
If not there then your drivers are not configured correctly, Nexus Root Toolkit has a guide on how to setup drivers correctly.
corkiejp said:
First make sure your in "fastboot" mode and not in the bootloader.
Your device should show up as under Android Device as "Android Bootloader Interface" in device manager on your PC.
If not there then your drivers are not configured correctly, Nexus Root Toolkit has a guide on how to setup drivers correctly.
Click to expand...
Click to collapse
I tried uninstalling the drivers from device manager and that didn't seem to do it. I went into the sdk and deleted them from the sdk then reinstalled them through the sdk and that seemed to work. I feel like i should have thought of that! duh. flashing CM13 now! hope i can get this to work haha jeeze.
thanks for the help guys
i have a linsay 7-xhd that got stuck after using the above command have no adb access from the boot screen and it will not boot into recovery. any ideas to get to recovery or fix? there is no roms firmware or anything available for this device?
I let the battery drain all the way (thankfully the battery isn't great and wasn't fully charged) and i was able to boot into the os. i still wish to access the bootloader any ideas why it would cause a boot loop?
This won't really help, but next time make sure the device is recognized first. That way you know the computer sees it. I start a terminal session with adb devices command first. If nothing comes up( if the phone's on, I get the serial number, if it's on twrp, I get the dev name as in the one in build prop) adb doesn't see it. I go from there, and do what I am trying to do, then use adb reboot bootloader to reboot. The good thing about using twrp is that internal storage shows up, plus sdcard access is shown on the computer, when adb is working right. I don't use windows though, seems that things work better with ubuntu.