I was flashing back to the stock Asus US 4.1 Rom from asus.com and that worked fine, but in the process I lost root. Now the operating system runs just fine, but when I power on into bootloader that works, but if I try recovery I get the android with the red ! (eclimation point), and if it try fastboot it says its starting fastboot, but just sits there.... Can someone please help me. Anything will help, and I mean anything. if there is a way to get root back or recovery through apx or anything. Any help will be much appreciated! thanks
If you are referring to what it says on the tablet saying fastboot is enable or something like that doesn't say any thing mire than that has long has you type fastboot devices in terminal under sdk/platform-tools and comes up with a serial number your good to go? If that helps?
Sent from my Galaxy Nexus using xda premium
larryv1979 said:
If you are referring to what it says on the tablet saying fastboot is enable or something like that doesn't say any thing mire than that has long has you type fastboot devices in terminal under sdk/platform-tools and comes up with a serial number your good to go? If that helps?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Sorry I should have been specific but I was at work. After I press vol and power and then go to the usb symbol; on the tablet it says "starting fastboot USB download protocol". On the computer it loads the driver for the "ASUS Android Bootloader Interface". I can't get the computer to comunicate with the tablet at all like this..."Fastboot devices" in cmd prompt does nothing. any advice?
Related
Hey guys, my computer won't pick up my phone at hboot anymore even though i deleted 0 files whatsoever and changed nothing, I need the computer to pick up my phone at hboot so that i can flash the boot.img files otherwise roms dont work for me, when i press fastboot, it doesnt say fastboot usb, but when i press down with the volume key it says fastboot usb but no commands work in the command prompt , it just gets stuck at waiting for device. I know it's not the cable, I tried it with my friends, any solutions?
I'm having the "< waiting for device >" hanging problem when trying to run the fastboot command from the Android SDK. I've searched around and seen many with this problem, but no single fix. I've reinstalled the SDK and drivers, made sure HTC Sync and other syncing processes are not running, and made sure USB debugging is on. "adb devices" and "adb shell" work fine. I've also tried rebooting the phone while "waiting." All to no avail.
What could be causing this? What can I do to successfully run fastboot?
This is on an HTC Sensation running SuperSensation v.1.0.5 (Android 2.3.5), connected to a Windows 7 PC.
Thanks for helping with a noobie question.
mturk
sensation lover said:
Hey guys, my computer won't pick up my phone at hboot anymore even though i deleted 0 files whatsoever and changed nothing, I need the computer to pick up my phone at hboot so that i can flash the boot.img files otherwise roms dont work for me, when i press fastboot, it doesnt say fastboot usb, but when i press down with the volume key it says fastboot usb but no commands work in the command prompt , it just gets stuck at waiting for device. I know it's not the cable, I tried it with my friends, any solutions?
Click to expand...
Click to collapse
So "adb devices" when booted, and "fastboot devices" when in bootloader returns nothing, or "waiting for device"?
You have both adb and fastboot drivers in the same location you are issuing these commands from?
Sent from my Pyramid-T
Oh......
I didn't realize that "fastboot" was to be run while in the bootloader. I think I tried that without success earlier, but am not sure - in any case, it worked this time.
Many thanks...!
Hi All,
i rooted my phone using what i thought was the right img file, but i can only assume it was the wrong file as i can now do nothing, i can boot into the Moto symbol, i can get to the droid with the warning triangle and into the fastboot section but i can no longer detect it when connected to the usb...
can anyone suggest a fix or am i screwed ??
thanks for any help
Try reflashing it with my tool, using unbrick feature, maybe you need fastboot drivers, just download it from sdk
Sent from my awesome ICS Xoom with xda Premium HD
cheers xxlordxx
ill give that a go, which drivers do i need to install for the fastboot ?
i downloaded the google usb driver package via the SDK last time, but it seems they are not firing up when i connect the tab.
TheWhiteDragon said:
cheers xxlordxx
ill give that a go, which drivers do i need to install for the fastboot ?
i downloaded the google usb driver package via the SDK last time, but it seems they are not firing up when i connect the tab.
Click to expand...
Click to collapse
If you can boot, you are not bricked - just start over with the root process using the correct image.
hey guys,
i have downloaded LAIOT but im not sure its detecting the pad, currently im getting
Searching For Device
List Of Devices
(Nothing listed)
on the pad
Starting Fastboot Protocol Support
tried doing the same using the different modes.
on Pad
Starting RSD Protocol Support
Same result on LAIOT
Recovery -
Same result.
this has all been done on a windows 7 laptop,
i have a linux laptop, will i get any more success using that with the google driver ?
just had a brain wave, checked device manager - i have an unknown device detected.. thats where the sodding thing has been hiding...
any ideas what drivers i need to get the dam thing detected correectly ?
just going to try using the default google ones from the SDK.
TheWhiteDragon said:
just had a brain wave, checked device manager - i have an unknown device detected.. thats where the sodding thing has been hiding...
any ideas what drivers i need to get the dam thing detected correectly ?
just going to try using the default google ones from the SDK.
Click to expand...
Click to collapse
Try a diff USB cable - download drivers from MOTOROLA website get this file - MotoHelper_2.1.32_Driver_5.4.0.exe
Okay here we go....
first thing let your xoom stuck on M logo.
Then hold power+volume up.
while power up press volume down to get firstboot.(make sure your PC and xoom know each other.)
You will see some text firstboot bla bla bla on left, top of screen.
Second thing open window cmd.exe
then type ...
cd /AndroidSDK/tools (where ever your adb.exe is located)
fastboot flash boot boot.img (the right boot image)
fastboot flash system system.img
fastboot erase cache
fastboot reboot
wait for reboot. You should see splash screen and you smile on your face.
TheWhiteDragon said:
hey guys,
i have downloaded LAIOT but im not sure its detecting the pad, currently im getting
Searching For Device
List Of Devices
(Nothing listed)
on the pad
Starting Fastboot Protocol Support
Click to expand...
Click to collapse
I need to fix it then...
Sent from my awesome ICS Xoom with xda Premium HD
thanks Mjamocha
ill give it ago tomorrow, sorry been flat out at work.
ill also try xxlords again on another machine just incase its the drivers on the laptop which are the problem.
XxLordxX said:
I need to fix it then...
Sent from my awesome ICS Xoom with xda Premium HD
Click to expand...
Click to collapse
sorry guys i have been flat out at work, SCCM deployment is taking a while to learn & play with.
but im back now and hopefully unbuggering my phone
i am going to redo all the bits you guys suggested on my PC rather than Craptop.
hopefully ill have more joy, ill let ya know how i get on 8)
What about using RDS?
woot im back
Thanks guys, just needed a fresh machine to do it on, think the craptop was a bit confused with the drivers.
TheWhiteDragon said:
woot im back
Thanks guys, just needed a fresh machine to do it on, think the craptop was a bit confused with the drivers.
Click to expand...
Click to collapse
Glad you got it going!
Had a similar problem where I had a boot loop and adb didn't recognise my device, but I could still put it into fastboot or recovery with power + vol down.
What I did was boot the Xoom so that it was stuck at the Moto logo, connected to the PC and queued up the fastboot command (fastboot flash boot boot.img) so the command window said "Waiting for device...", then reset the Xoom and manually put it into fastboot again at which point it picked up the queued command and started flashing.
Hi,
I have a Nexus S model GT-I9023 which is broken and now Im trying to recover some photos. I searched for a whole lot of guides and I think Im doing it right but can't get it to work.
I acidentally dropped it into a bucket of water, I let it dry and the next day it worked and on for about a week. Then it suddenly stopped working and I couldn't boot my phone, it wouldn't go pass the startup text "Google" and the lock icon.
I have the android SDK installed including the Google USB drivers. I added the PATH to tools and platform-tools. In the terminal i type "cd C:\Program Files\Android\android-sdk\tools" and hit enter and afterwards type "adb devices". It starts the daemon up etc. but does not list any device.
Note: since I cannot boot up the phone and enable usb debuggin I boot the phone up in recovery mode which I think should work and is the same as enabling USB debuggin, if Im not wrong.
I suspect that maybe it's because of the recovery mode or because some drivers. I don't think my computer recognize the devices regularly but Im not sure what it really is.
Any help would be appreciated
bahagiga said:
Hi,
I have a Nexus S model GT-I9023 which is broken and now Im trying to recover some photos. I searched for a whole lot of guides and I think Im doing it right but can't get it to work.
I acidentally dropped it into a bucket of water, I let it dry and the next day it worked and on for about a week. Then it suddenly stopped working and I couldn't boot my phone, it wouldn't go pass the startup text "Google" and the lock icon.
I have the android SDK installed including the Google USB drivers. I added the PATH to tools and platform-tools. In the terminal i type "cd C:\Program Files\Android\android-sdk\tools" and hit enter and afterwards type "adb devices". It starts the daemon up etc. but does not list any device.
Note: since I cannot boot up the phone and enable usb debuggin I boot the phone up in recovery mode which I think should work and is the same as enabling USB debuggin, if Im not wrong.
I suspect that maybe it's because of the recovery mode or because some drivers. I don't think my computer recognize the devices regularly but Im not sure what it really is.
Any help would be appreciated
Click to expand...
Click to collapse
You don't need to boot in recovery, boot in bootloader only.
polobunny said:
You don't need to boot in recovery, boot in bootloader only.
Click to expand...
Click to collapse
I think I might have confused the terms bootloader and recovery mode, what I meant was I press the vol up button and the power button at the same time which then opens the bootloader I guess? anyways, still the same issue for me.
bahagiga said:
I think I might have confused the terms bootloader and recovery mode, what I meant was I press the vol up button and the power button at the same time which then opens the bootloader I guess? anyways, still the same issue for me.
Click to expand...
Click to collapse
Yes that's the bootloader.
Have you installed the ADB drivers? You don't need only the adb and fastboot executable, but also the drivers.
Under Windows, you can install the PDANet software which makes driver installation a breeze on most cases.
http://junefabrics.com/android/
polobunny said:
Yes that's the bootloader.
Have you installed the ADB drivers? You don't need only the adb and fastboot executable, but also the drivers.
Under Windows, you can install the PDANet software which makes driver installation a breeze on most cases.
link
Click to expand...
Click to collapse
Hmm, on the third step where it says "installing pdanet to your phone" it just like freeze and on my phone in the bottom it says "FASTBOOT STATUS - FAILInvalid Command"
what should I do??
bahagiga said:
Hi,
I have a Nexus S model GT-I9023 which is broken and now Im trying to recover some photos. I searched for a whole lot of guides and I think Im doing it right but can't get it to work.
I acidentally dropped it into a bucket of water, I let it dry and the next day it worked and on for about a week. Then it suddenly stopped working and I couldn't boot my phone, it wouldn't go pass the startup text "Google" and the lock icon.
I have the android SDK installed including the Google USB drivers. I added the PATH to tools and platform-tools. In the terminal i type "cd C:\Program Files\Android\android-sdk\tools" and hit enter and afterwards type "adb devices". It starts the daemon up etc. but does not list any device.
Note: since I cannot boot up the phone and enable usb debuggin I boot the phone up in recovery mode which I think should work and is the same as enabling USB debuggin, if Im not wrong.
I suspect that maybe it's because of the recovery mode or because some drivers. I don't think my computer recognize the devices regularly but Im not sure what it really is.
Any help would be appreciated
Click to expand...
Click to collapse
Can you boot into "recovery" and mount the sd from there?
Sent from my Nexus S 4G using xda premium
---------- Post added at 04:54 PM ---------- Previous post was at 04:50 PM ----------
If you can get to bootloader you should be able to get into recovery. And from there you should be able to mount your sd.
Sent from my Nexus S 4G using xda premium
Bkadleck said:
Can you boot into "recovery" and mount the sd from there?
Sent from my Nexus S 4G using xda premium
---------- Post added at 04:54 PM ---------- Previous post was at 04:50 PM ----------
If you can get to bootloader you should be able to get into recovery. And from there you should be able to mount your sd.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I tried but I dont think I can, when I try it just goes into that 'bootup screen, with the Google text and lock icon'. :/ Not sure what to do
Im still stuck and havent been able to get around this, any helpful information is appreciated. Thanks in advance
Hey guys, Im still stuck with this issue. Anyone who has some tips on what to do or has an idea of what it could be? I just formatted my PC yesterday Windows 7 32bit and everything should be up to date.
Kind regards,
baha
If there's anyone out there I would greatly appreciate your help! I have some pictures that are very valuable to me (pictures of my dog) and would really love to see if I could recover them.
I cannot start up my phone the "normal" way, I can only start up the Fastboot mode. I have the Samsung phone drivers installed along with the Google USB drivers. I have attached a picture that shows that there should be no problems with the drivers. I have tried to use the google usb drivers specifically but still the same. I have also attached a picture of the command prompt and as you can see nothing really happens. I have tried different tutorials and all kinds of ways trying to make it work but I have no clue what the problem is since I am not getting any other error message.
Any help is appreciated, please!
I typed fastboot devices in the cmd prompt and it actually listed a device serial number which matches then one stated on my phone in the fastbootmode. Any idea what to do or what this means?
Long story short, installed clockwork mod recovery in attempt to install a cyanogen nightly. I stupidly formatted everything including data and SYSTEM! Now I can only boot to recovery. When I plug the nexus into any PC it's not picked up as an unidentified piece of hardware on windows so I can't push another rom or adb sideline commands result in "waiting for device". Any suggestions? Should I attempt to RMA?
Reinstall drivers. Boot into the bootloader and flash the factory image.
El Daddy said:
Reinstall drivers. Boot into the bootloader and flash the factory image.
Click to expand...
Click to collapse
Thank you!! I never used the USB cable that actually came with the NEXUS until just now, the PC finally detected the phone as i was in the Bootloader and start automatically Download and Writing, rebooting itself and looks like it's booting up. Thanks again. Very quick response.
I accidentally formatted system as well, slip of the finger. I am unable to get my computer to recognize my device, "fastboot devices" lists nothing. Have tried flashing factory software, but it just says "waiting for device". Any suggestions???
Check USB drivers. Might not be working
Sent from my Nexus 5 using Tapatalk
wltnkyl said:
I accidentally formatted system as well, slip of the finger. I am unable to get my computer to recognize my device, "fastboot devices" lists nothing. Have tried flashing factory software, but it just says "waiting for device". Any suggestions???
Click to expand...
Click to collapse
If you are on windows 8 or 8.1 you have turn of driver signiture enforecment. http://sixcolumns.com/how-to-disable-and-bypass-driver-signature-enforcement-in-windows-8/
To make adb works when you are in recovery you need the naked usb drivers. Turn on sideload in the recovery and on a cmd type this: adb sideload path_to_your_rom_file.zip end hit enter.
bitdomo said:
If you are on windows 8 or 8.1 you have turn of driver signiture enforecment. http://sixcolumns.com/how-to-disable-and-bypass-driver-signature-enforcement-in-windows-8/
To make adb works when you are in recovery you need the naked usb drivers. Turn on sideload in the recovery and on a cmd type this: adb sideload path_to_your_rom_file.zip end hit enter.
Click to expand...
Click to collapse
Thank you so much!! Unfortunately I am only able to hit the THANKS button once. I thought for sure that it was done for!
I have bricked my phone before, but have always been able to find a workaround. This time, not so much.
Again, Thank You!!
wltnkyl said:
Thank you so much!! Unfortunately I am only able to hit the THANKS button once. I thought for sure that it was done for!
I have bricked my phone before, but have always been able to find a workaround. This time, not so much.
Again, Thank You!!
Click to expand...
Click to collapse
you can also try unlock bootloader, flash factory images. and bumm your phone works again.
install fastboot and etc... http://forum.xda-developers.com/showthread.php?t=2588979
guide to return stock http://forum.xda-developers.com/showthread.php?t=2513701
Oh and send me an e-mail: [email protected] then I will instruct you to downlaod teamviewer, so I could resolve your driver problems
You should give wag tool a try it completely brings you back to stock
Sent from my Nexus 5 using XDA Premium 4 mobile app
My device is a One Plus One. I've installed an ADB driver from here: adbdriver (some site I've searched up on google) (Is this even safe? I've never seen anyone use this link before or maybe it's new. It's not a virus is it?)
So once I've installed it, I've typed all commands such as adb while my device is turned on but then when it gets to where I have to press my powerbutton+volume down and then go into the recovery screen, I see "Cyanogen Recovery" or whatever but that's what it says. Suddenly on my computer, the ADB device disappears altogether and I cannot see my One Plus One storage anymore (it's connected and even If I unconnect and reconnect it's still the same). I believe I've unlocked my phone already before so is this why? I just want to make sure and type fastboot oem device-info but when I type that nothing comes up. I've been trying to solve this and I don't know what to do anymore... Is it because I've already unlocked my device (but even I'm not sure if it's still unlocked and that's why I'm trying to confirm it by typing "fastboot oem device-info" which doesn't even work. Help please!
xMTOOLO said:
My device is a One Plus One. I've installed an ADB driver from here: adbdriver (some site I've searched up on google) (Is this even safe? I've never seen anyone use this link before or maybe it's new. It's not a virus is it?)
So once I've installed it, I've typed all commands such as adb while my device is turned on but then when it gets to where I have to press my powerbutton+volume down and then go into the recovery screen, I see "Cyanogen Recovery" or whatever but that's what it says. Suddenly on my computer, the ADB device disappears altogether and I cannot see my One Plus One storage anymore (it's connected and even If I unconnect and reconnect it's still the same). I believe I've unlocked my phone already before so is this why? I just want to make sure and type fastboot oem device-info but when I type that nothing comes up. I've been trying to solve this and I don't know what to do anymore... Is it because I've already unlocked my device (but even I'm not sure if it's still unlocked and that's why I'm trying to confirm it by typing "fastboot oem device-info" which doesn't even work. Help please!
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. To get you the expert help you need, I'm going to move this thread to your specific device Q&A forum.
Good luck!
You need to boot into bootloader by pressing volume up + power.
Then you can use "fastboot devices" to see if your OPO is being recognised.
"fastboot oem device-info" only works when you boot to bootloader
ADB is not fastboot btw.
http://www.androidcentral.com/android-z-what-fastboot
ADB does only work when your phone is booted to the Android system and USB-Debugging is enabled
http://www.androidcentral.com/what-adb