Okay so I flashed a rom and im stuck in a bootloop, but I cant get into recovery to restore a nandroid. My power button receded so as soon as I put in a battery it immediately turns on. But if i go into bootloader, not the power button nor the volume keys will work. So I cant get into recovery that way. Is there any other way like with adb in bootloader? Or am i screwed lol.
Thanks in advance for help, I could really use it.
adb reboot bootloader
adb reboot recovery
It should be obvious what they do. Bootloader won't do you much good without a power button.
Sent from my HTC Glacier using XDA App
estallings15 said:
adb reboot bootloader
adb reboot recovery
It should be obvious what they do. Bootloader won't do you much good without a power button.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
I tried running adb in the bootloader but it wont connect to my phone. What exactly should I be typing to connect it? Its plugged in with a usb cord. Sorry, obviously im a huge newb
perhac89 said:
I tried running adb in the bootloader but it wont connect to my phone. What exactly should I be typing to connect it? Its plugged in with a usb cord. Sorry, obviously im a huge newb
Click to expand...
Click to collapse
if you are in bootloader mode, make sure the phone says FASTBOOT USB somewhere on the screen when connected to the computer.
then type
Code:
fastboot reboot (whatever it is you want to reboot to)
adb only works in recovery or android itself.
saranhai said:
if you are in bootloader mode, make sure the phone says FASTBOOT USB somewhere on the screen when connected to the computer.
then type
Code:
fastboot reboot (whatever it is you want to reboot to)
adb only works in recovery or android itself.
Click to expand...
Click to collapse
Then only thing Im getting is Hboot Usb Plug, not Fastboot Usb
Edit: Okay now I have Fastboot USB showing, but cmd doesnt recognize fastboot, nor will it connect to my device
Just boot the phone in the regular way.
While it boots, in bootanimation or even a bit before that, execute "adb reboot recovery".
Jack_R1 said:
Just boot the phone in the regular way.
While it boots, in bootanimation or even a bit before that, execute "adb reboot recovery".
Click to expand...
Click to collapse
All Im getting when I do this is error device not found
Bump.
I can't get it back into fastboot usb either, I think the power button fixed for a second before and selected fastboot.
Do you have a warranty on this phone?
If not, you may want to open it where you can access the power button more easily.
Before you do that though, get it caught in a bootloop and try adb reboot recovery. Reboot and try again at a different point. It should work eventually. Persistence might pay off.
Sent from my HTC Glacier using XDA App
perhac89 said:
All Im getting when I do this is error device not found
Click to expand...
Click to collapse
Since you're in the bootloop, your device is connecting and disconnecting. See when it connects (easily recognized Windows "USB device connected" sound), then execute "adb reboot recovery" until the command catches or the phone reboots. Attempt several times.
If it won't work - open the phone and fix the button.
Plugged in device. Drivers loaded. Turned off tablet. Restarted into bootloader (both volume buttons held, hold power until vibrate)
In cmd prompt, navigate to folder with fastboot.
typed "fastboot devices" (without quotes) and it returned nothing. Shouldn't it return the device ID or something?
All I want is to unlock my bootloader and root the device!
No search has helped me. Hopefully someone hear can!
Are you sure the ADB driver was installed for the device? Try reading through this:
http://trevorsullivan.net/2012/07/03/forcibly-installing-the-android-usb-driver-in-windows-7/
couple things to try
As silly as it sounds with modern computers, but make sure you are plugging into the back of your PC rather than a a usb port on the front.
Also, even if fastboot devices comes back blank, try typing the fastboot oem unlock anyways. 9/10 times my computer comes up empty when I query for the device but then am able to flash recovery, unlock etc with no prob
Blueback22 said:
Plugged in device. Drivers loaded. Turned off tablet. Restarted into bootloader (both volume buttons held, hold power until vibrate)
In cmd prompt, navigate to folder with fastboot.
typed "fastboot devices" (without quotes) and it returned nothing. Shouldn't it return the device ID or something?
All I want is to unlock my bootloader and root the device!
No search has helped me. Hopefully someone hear can!
Click to expand...
Click to collapse
Blueback22 said:
Plugged in device. Drivers loaded. Turned off tablet. Restarted into bootloader (both volume buttons held, hold power until vibrate)
In cmd prompt, navigate to folder with fastboot.
typed "fastboot devices" (without quotes) and it returned nothing. Shouldn't it return the device ID or something?
All I want is to unlock my bootloader and root the device!
No search has helped me. Hopefully someone hear can!
Click to expand...
Click to collapse
As mentioned in the above post... I've had a handful of devices that won't return a fastboot id, however they except commands just fine.
dannymac77 said:
As silly as it sounds with modern computers, but make sure you are plugging into the back of your PC rather than a a usb port on the front.
Also, even if fastboot devices comes back blank, try typing the fastboot oem unlock anyways. 9/10 times my computer comes up empty when I query for the device but then am able to flash recovery, unlock etc with no prob
Click to expand...
Click to collapse
Thank you to everyone for your help.
First thing I did was force the driver. It was showing up under mobile devices as Nexus 10, but I pushed the Google USB drivers anyway
This didnt help show the device ID when using fastboot devices, but I followed the above instructions anyway and it unlocked.
It's now at the X boot screen and taking a while. I hope I'm not in a boot loop. I dont know why I would be as all I did was unlock the bootloader and going to give it another minute before I reboot.
OK. It did boot loop. To fix this, follow this video to do a factory reset:
http://youtu.be/T1Se7Hr9Cww
I had the same issue as you with my Galaxy Nexus recently, and force installing the USB drivers does the trick every time. I think it has to do with Windows seeing the device as a media device (external MP3 player, or similar), rather than as an ADB interface. That's why you have to tell it to forcefully install the ADB driver, so it can talk ADB, rather than treating it as a media device.
Glad you got it working. Cheers
OKay I cannot for the life of me get this to work at all. I have never had a problem unlocking an HTC device, but anytime it comes to a samsung it doesn't work. I've tried the steps listed here, I've watched a video guide on unlocking from another post, I have the SDK updated, it sees the device as Android Bootloader Interface in Device Manager, I've rebooted straight to bootloader on the tablet, I've tried two different USB ports in the rear, fastboot will not read this device or give it commands at all. No reboot, no unlock, nothing. I'm seriously starting to freak out here. Been at this for 2 and a half hours now.
Varekai said:
OKay I cannot for the life of me get this to work at all. I have never had a problem unlocking an HTC device, but anytime it comes to a samsung it doesn't work. I've tried the steps listed here, I've watched a video guide on unlocking from another post, I have the SDK updated, it sees the device as Android Bootloader Interface in Device Manager, I've rebooted straight to bootloader on the tablet, I've tried two different USB ports in the rear, fastboot will not read this device or give it commands at all. No reboot, no unlock, nothing. I'm seriously starting to freak out here. Been at this for 2 and a half hours now.
Click to expand...
Click to collapse
I'm sure you did this right, but let's walk through the steps again anyway...
1) turn on tab and plug into USB do windows can install drivers
2) force ADB drivers according to link at the beginning of this thread
( it wouldn't hurt to reboot windows between steps 2 and 3)
3) shutdown tab and lead into boot loader
- do this by holding down all buttons while tab is off. When it vibrates, let go of power button until boot loader comes up
4) make sure USB is connected to back of PC and to tab
5) open terminal by going into start menu and typing CMD
6) change directory to location of fastboot
7)type fastboot devices
8) if ID comes up, you're home free. If nothing comes up, try step 9 anyway
9) type fastboot OEM unlock
10) follow instructions on tab screen
Let us know if any step failed.
Sent from my Galaxy Nexus using Tapatalk 2
pcgeek86 said:
I had the same issue as you with my Galaxy Nexus recently, and force installing the USB drivers does the trick every time. I think it has to do with Windows seeing the device as a media device (external MP3 player, or similar), rather than as an ADB interface. That's why you have to tell it to forcefully install the ADB driver, so it can talk ADB, rather than treating it as a media device.
Glad you got it working. Cheers
Click to expand...
Click to collapse
I had to do this with the Nexus 10, as well, after messing with it for a while.
Sent from my Galaxy Nexus using Tapatalk 2
Blueback22 said:
I'm sure you did this right, but let's walk through the steps again anyway...
1) turn on tab and plug into USB do windows can install drivers
2) force ADB drivers according to link at the beginning of this thread
( it wouldn't hurt to reboot windows between steps 2 and 3)
3) shutdown tab and lead into boot loader
- do this by holding down all buttons while tab is off. When it vibrates, let go of power button until boot loader comes up
4) make sure USB is connected to back of PC and to tab
5) open terminal by going into start menu and typing CMD
6) change directory to location of fastboot
7)type fastboot devices
8) if ID comes up, you're home free. If nothing comes up, try step 9 anyway
9) type fastboot OEM unlock
10) follow instructions on tab screen
Let us know if any step failed.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I've done every one of those steps to the T. Rebooted multiple times, tried different USB cables, tried every port in the back, plus both up front just for extra measure. USB port works on the tab because I'm transferring media files to it right now, it recognizes as an ADB device, drivers were also force installed from SDK Toolkit, but it won't take commands, not reboot, not ID, and certainly not unlock. The only other thing I can try is using my fiance's laptop and see if for some reason it's just an issue with my PC, because if not then it's an issue with the tablet, for whatever reason, and not being able to root this is not an option for me.
Varekai said:
I've done every one of those steps to the T. Rebooted multiple times, tried different USB cables, tried every port in the back, plus both up front just for extra measure. USB port works on the tab because I'm transferring media files to it right now, it recognizes as an ADB device, drivers were also force installed from SDK Toolkit, but it won't take commands, not reboot, not ID, and certainly not unlock. The only other thing I can try is using my fiance's laptop and see if for some reason it's just an issue with my PC, because if not then it's an issue with the tablet, for whatever reason, and not being able to root this is not an option for me.
Click to expand...
Click to collapse
If you'd like, I can remote into your computer and walk through it with you to see if I can help in anyway. Let me know.
I will PM you my phone number so you can text me if you want to try this.
I am presently having the EXACT same problem. I have a Mac mini (mountain lion) and Windows 8 (vmware). Under osx I follow all the steps and similarly I can't get fastboot to give me the ID or recognize the unlock command. In Windows it recognizes the tablet when it's booted up normally. But with fastboot in the cmd prompt I get the exact same results as in osx.
P.s. I also had the same issue with my Samsung galaxy 3. Wound up having to root it at a friend's house.
Sent from my SPH-L710 using xda premium
Blueback was able to solve all my woes, thanks!
verusevo said:
I am presently having the EXACT same problem. I have a Mac mini (mountain lion) and Windows 8 (vmware). Under osx I follow all the steps and similarly I can't get fastboot to give me the ID or recognize the unlock command. In Windows it recognizes the tablet when it's booted up normally. But with fastboot in the cmd prompt I get the exact same results as in osx.
P.s. I also had the same issue with my Samsung galaxy 3. Wound up having to root it at a friend's house.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
I just fixed this for the other guy. What is the file path of your fastboot.exe file?
Its in user/downloads/root. on both my osx/windows drives.
Sent from my SPH-L710 using xda premium
verusevo said:
Its in user/downloads/root. on both my osx/windows drives.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
In your windows VM, is it inside of the Android SDK/Platform-Tools/ folder?
Sent from my Galaxy Nexus using Tapatalk 2
No its on the virtual C: drive in the downloads/root folder. Root being the folder I created to extract all relevant unlocking rooting files to
Sent from my Nexus 10 using XDA Premium HD app
verusevo said:
No its on the virtual C: drive in the downloads/root folder. Root being the folder I created to extract all relevant unlocking rooting files to
Sent from my Nexus 10 using XDA Premium HD app
Click to expand...
Click to collapse
Download and install the Android SDK. Use the fastboot tool that is inside of the Android SDK/platform-tools/ folder. I can almost guarantee success.
My win 7 didn't recognize my n10 fastboot too, so I went into device manager and updated the android 1.0 or something by selecting the main SDK folder in the android SDK as an update source
Same for adb
Sent from my Nexus 10 using XDA Premium HD app
Hi everyone,
I tried every way I can to install the driver but I still cannot get ADB to recognize the phone. Can anyone please help me with this?
Windows 7 x64. ROM: PA
Thanks,
Edit: so I tried the PDANet driver installer. adb now can see the phone if it is in recovery mode. fastboot and usb debugging still cannot be recognized by adb.
KyraOfFire said:
Hi everyone,
I tried every way I can to install the driver but I still cannot get ADB to recognize the phone. Can anyone please help me with this?
Windows 7 x64. ROM: PA
Thanks,
Edit: so I tried the PDANet driver installer. adb now can see the phone if it is in recovery mode. fastboot and usb debugging still cannot be recognized by adb.
Click to expand...
Click to collapse
Fastboot and adb are not the same thing. They are separate executables. You can't use adb commands in the bootloader, you use fastboot.
Sent from my Nexus 7 using Tapatalk HD
El Daddy said:
Fastboot and adb are not the same thing. They are separate executables. You can't use adb commands in the bootloader, you use fastboot.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks for reminding me. After 2 hours fighting with Windows 7, my mind went dumb and I forgot the basic. Now things are fine. Also, I realize how stupid Windows *really* is :silly: you can do basically anything with Nexus 4 in a breeze, but anything with Windows require luck, magic and voodoo charms....
the most important step was disabling Window's automatic driver installation. It kept installing the incorrect drivers. After that, things were easy, except that I forgot in fastboot I have to use fastboot commands ... :silly:
Thanks again, El Daddy. You're always the man!
Download the nexus 4 root toolkit or whatever it's name is. It'll guide you step by step. Also, qbking77 has some nice videos on YouTube... Check them out.
Sent from my Nexus 4 using xda app-developers app
when i type adb devices it says my device is offline but gives the serial number, but commands like adb reboot won't work, but when im in recovery it says recovery on my computer and commands work any ideas? thanks
https://www.google.com/search?q=adb+devices+offline
ksilver89 said:
https://www.google.com/search?q=adb+devices+offline
Click to expand...
Click to collapse
tried that guide/fix and didn't work, i think it's because i haven't gotten the screen where it says to accept adb or whatever but how can i get it to pop again?
http://forum.xda-developers.com/showthread.php?t=2401452
Check adb version, it should be 1.3.0 or something basically the latest version of adb, then switch on USB debugging mode, plug in phone and a window should pop up on the nexus 4, accept than do adb devices, should say online and good to go...
"iPhone=Boat shoes,sweaters over shirt/tie,whores,non prescriptive glasses with slicked hair,hipster concerts,too much ignorance"-sent from my NEXUS 4
Okay guys, I've exhausted all my own resources and would really appreciate your help.
Long story short- I have TWRP installed with NO backup files or roms on the device. I made a TWRP backup and put it on my PC pre brick...
When I turn the G2 on and plug it into my PC i get an unknown deivce which has the hardware id: USB\VID_18D1&PID_D001&REV_0232
I attempted to use the TWRP sideload with no benefit- if i can use ADB i know how to push my image but i CANNOT get adb to see the device..
any help will be greatly appreciated!!!
-THank you
Dana
I am not familiar with adb when device is off or fastboot. So if you are desperate follow one of the guides on un-bricking the g2 (which will bring it back to stock and wipe data) but then you'll be up and running and you would just have to re-root and unlock it
djohnson308 said:
Okay guys, I've exhausted all my own resources and would really appreciate your help.
Long story short- I have TWRP installed with NO backup files or roms on the device. I made a TWRP backup and put it on my PC pre brick...
When I turn the G2 on and plug it into my PC i get an unknown deivce which has the hardware id: USB\VID_18D1&PID_D001&REV_0232
I attempted to use the TWRP sideload with no benefit- if i can use ADB i know how to push my image but i CANNOT get adb to see the device..
any help will be greatly appreciated!!!
-THank you
Dana
Click to expand...
Click to collapse
Assuming that you can boot into TWRP, then you probably just need to install the right drivers. Search around the forums.
Stock lg drivers don't seem to recognize phone in recovery mode install pdanet and then connect phone to pc while in recovery mode and open pdanet app in pc and follow instructions to install lg drivers and then pc will find ur device it worked for me when l had the same problem.
Sent from my LG-D800 using xda app-developers app
So i cannot seem to get my computer to install pdanet. i searched for a unbrick thread and found one.. i waited an hour for it to download a 2gig file, the lg program said it was pushing to phone which took 15 seconds (no way it pushed 2gigs that fast) then it said reboot the phone then do a hard reset... i went to do that and the phone just pushed me to TWRP. ahhhh losing my mind
What's the message when installing pdanet
Sent from my LG-D800 using xda app-developers app
access denied followed by x64 issues... Im the domain admin, and the website says its good for x64...
well lets see here are you on windows 8 or 7 ?
this is what i did
I put the phone into fastboot mode then connected it to the computer, well now the customer doesn't recognize it and you should have the drivers installed then what you want to do is search for device manager, look under the Universal Serial Bus Controllers and you will see USB connect with an "!" what you need to do is right click on it then go to update drivers, from there you need to select browse my computer for the drivers not the automatic one then select "let me from a list of devices. next you want to unchecked show compatible hardware now look for Lg in the manufacture list and there should be one that says something about "adb interface" and select it.
Now try using a cmd windows and adb. what i did was i download a fastboot.zip it has adb interface in that zip file then i opened a cmd prompt in that folder by holding shift and right clicking. now once it was open i typed adb list and it recognized my phone
then i went into twrp and adb sideload and I side loaded a stock zip now you be fine and back to square one.