Hi all. I am trying to get AsteroidOS on my SW3, but every time I try to unlock the bootloader through ADB, I get "< Waiting For Device >" and it doesn't stop. I have googled everything and nothing came up. Any suggestions?
Related
Hey guys, Im at a loss here. I have an unlocked (via Sony website) Verizon XP R800x on firmware 2.3.4 with the Doomlord Kernel installed. Last night I decided to go to CM9 and I backed up the phone with Clockworkmod. I then reached the step where I needed to go to the command line and type “fastboot flash boot boot.img”. I got the message "waiting for device"
An hour later, nothing had changed and I found out it simply locked up so I decided to try again and found out that my phone wont bootup. No power lights, nothing. All it will do is very briefly vibrate sometime within 10 seconds of me holding the power button. And it will only do that when the controller is slid out. It won't do a thing when its closed. The battery was fully charged so I'm sure that's not it. Nothing I do makes my PC detect this phone now. Flashtool wont detect it when I try to go back to stock. I even threw a dart and tried to do a FOTA unbrick I read about. Didn't work either, phone isn't detected. Does anyone have another idea? Thanks!
Have you tried to install the drivers manually?
C:Flashtool/drivers/Flashtool-drivers.exe
saiyan23 said:
Hey guys, Im at a loss here. I have an unlocked (via Sony website) Verizon XP R800x on firmware 2.3.4 with the Doomlord Kernel installed. Last night I decided to go to CM9 and I backed up the phone with Clockworkmod. I then reached the step where I needed to go to the command line and type “fastboot flash boot boot.img”. I got the message "waiting for device"
An hour later, nothing had changed and I found out it simply locked up so I decided to try again and found out that my phone wont bootup. No power lights, nothing. All it will do is very briefly vibrate sometime within 10 seconds of me holding the power button. And it will only do that when the controller is slid out. It won't do a thing when its closed. The battery was fully charged so I'm sure that's not it. Nothing I do makes my PC detect this phone now. Flashtool wont detect it when I try to go back to stock. I even threw a dart and tried to do a FOTA unbrick I read about. Didn't work either, phone isn't detected. Does anyone have another idea? Thanks!
Click to expand...
Click to collapse
Hi
Same thing happ ened to me. you have to remove the battery and reflash the phone to 2.3.4 using the flash tool. the phone was in fast boot with the blue light on when you entered the code by doing so it must have deleted something thats what happened to me .DO this and it will work make sure the battery is removed when you plug in the USB cable. if you find a way to run the command and put the phone in FXP boot screen let me know cause im stuck on step 22.
saiyan23 said:
Hey guys, Im at a loss here. I have an unlocked (via Sony website) Verizon XP R800x on firmware 2.3.4 with the Doomlord Kernel installed. Last night I decided to go to CM9 and I backed up the phone with Clockworkmod. I then reached the step where I needed to go to the command line and type “fastboot flash boot boot.img”. I got the message "waiting for device"
An hour later, nothing had changed and I found out it simply locked up so I decided to try again and found out that my phone wont bootup. No power lights, nothing. All it will do is very briefly vibrate sometime within 10 seconds of me holding the power button. And it will only do that when the controller is slid out. It won't do a thing when its closed. The battery was fully charged so I'm sure that's not it. Nothing I do makes my PC detect this phone now. Flashtool wont detect it when I try to go back to stock. I even threw a dart and tried to do a FOTA unbrick I read about. Didn't work either, phone isn't detected. Does anyone have another idea? Thanks!
Click to expand...
Click to collapse
Correct command should have been "fastboot -i 0xfce flash boot boot.img" did you missed the vendor id part? its 0xfce for xperia play.
If you can enter in fast bootmode try "fastboot -i 0xfce flash boot boot.img" now
If you cant still get your phone up and flashtools isnt working for you either ,even after a manual driver installation, then your trim area is damaged
And if, Unfortunately, your TRIM Area is Damaged then this post might help you
http://forum.xda-developers.com/showthread.php?t=1252038
OK here's the quick version of what happened.
Last night, before leaving work, I was playing a game (dice w/buddies) and when I was finished I put the phone to sleep. Picked it up after my 45 min drive home and the screen wouldn't turn on at all. Pulled the battery and as soon as I put it back in the phone vibrated and started the boot process. I didn't even hit the power button. I let it do it's thing and just watched. The screen was all kinds of jacked!! Vertical banding and discoloration to say the least. Well it took about 10 min to boot but when it did the touchscreen was unresponsive. After about 10 min of batt pulls to reboot and check the screen, I called VZW for a replacement.. (They overnighted one and it will be here this morning) So after that call, I just put the phone down and fed my daughter and did a few things around the house. Went back about 2 hrs later and pulled the battery and rebooted the phone to find that the screen now works! BUT the power button does not. It won't wake the phone up,put it to sleep, nothing. It's dead. So I thought I would unroot/relock and take it back to stock so I can send it back. Here is the problem with that; with the power button broken, fastboot won't recognize the phone. I can get into the bootloader via rom toolbox lite (JRummy app) and that works fine. But whether I try it thru adb or WugFresh's toolkit, as soon as the phone hits "Checking fastboot status", it fails. When you go to the device manager in Win7 and try to update the drivers, it fails. It comes up as something like INTF7 or something like that.
So how can I return to stock without a working power button? Even if I was to get it back to stock somehow, I can't relock it as I would have to hit the power button to accept the warning. Is there any other way?
I heard there was some issues with adb on 4.2. You might want to try updating your adb on your comp and then retry fastboot. There was a post on here about what steps to take to troubleshoot adb.
eqjunkie829 said:
I heard there was some issues with adb on 4.2. You might want to try updating your adb on your comp and then retry fastboot. There was a post on here about what steps to take to troubleshoot adb.
Click to expand...
Click to collapse
SDK was updated last night to the newest version. I don't think it's an adb/sdk issue. They are not connecting (I think) because the power botton is broken and the phone turns on as soon as the battery is put in. It's almost like it thinks the power button is being held in.
Once you get it to reboot into fastboot mode, it doesn't do anything. None of the buttons work then. Volume or power. And all adb says is "waiting for device."
cubsfan187 said:
SDK was updated last night to the newest version. I don't think it's an adb/sdk issue. They are not connecting (I think) because the power botton is broken and the phone turns on as soon as the battery is put in. It's almost like it thinks the power button is being held in.
Once you get it to reboot into fastboot mode, it doesn't do anything. None of the buttons work then. Volume or power. And all adb says is "waiting for device."
Click to expand...
Click to collapse
ADB doesn't work in the bootloader (fastboot mode). It will work in a custom recovery, or once boot into Android though.
When in the bootloader the only commands that will work will be fastboot commands, and they should be all you need to get back to stock and lock your bootloader up.
cupfulloflol said:
ADB doesn't work in the bootloader (fastboot mode). It will work in a custom recovery, or once boot into Android though.
When in the bootloader the only commands that will work will be fastboot commands, and they should be all you need to get back to stock and lock your bootloader up.
Click to expand...
Click to collapse
The fastboot commands don't work. Once you get into bootloader mode, nothing works. The volume keys,power key, nothing. When you type in a fastboot command it sits at "waiting for device" and never does anything. If you look in device manager (Win7) is shows a strange INFT2 (or something like that) driver that needs to be installed. I have searched for hours and found nothing on that. Even the toolkits stall at fastboot commands.
cubsfan187 said:
The fastboot commands don't work. Once you get into bootloader mode, nothing works. The volume keys,power key, nothing. When you type in a fastboot command it sits at "waiting for device" and never does anything. If you look in device manager (Win7) is shows a strange INFT2 (or something like that) driver that needs to be installed. I have searched for hours and found nothing on that. Even the toolkits stall at fastboot commands.
Click to expand...
Click to collapse
This sounds like a driver issue with your PC. I recommend that you start fresh. Uninstalling the current drivers, and installing new ones. http://forum.xda-developers.com/showthread.php?t=1379875 <-- I recommend the Naked Driver. http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735 <-- guide there on how to install them.
If you used fastboot on this PC successfully in the past, you could also just do some tinkering to figure out why, but this may take more work to diagnose than actually just nuking the current setup and setting up new ones.
cubsfan187 said:
When you go to the device manager in Win7 and try to update the drivers, it fails. It comes up as something like INTF7 or something like that.
cupfulloflol said:
This sounds like a driver issue with your PC. I recommend that you start fresh. Uninstalling the current drivers, and installing new ones. http://forum.xda-developers.com/showthread.php?t=1379875 <-- I recommend the Naked Driver. http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735 <-- guide there on how to install them.
If you used fastboot on this PC successfully in the past, you could also just do some tinkering to figure out why, but this may take more work to diagnose than actually just nuking the current setup and setting up new ones.
Click to expand...
Click to collapse
I already tried to mess with the drivers. They won't update while in fastboot mode. It comes up as INTF7 (or whatever it was) and they cannot be found. As long as I can lock the bootloader I will send it back rooted and maybe even on a close-to-stock rom. That's probably the best I can do.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
cubsfan187 said:
I already tried to mess with the drivers. They won't update while in fastboot mode. It comes up as INTF7 (or whatever it was) and they cannot be found. As long as I can lock the bootloader I will send it back rooted and maybe even on a close-to-stock rom. That's probably the best I can do.
Click to expand...
Click to collapse
You can get back to stock as long as you are at least rooted. You can do this, which will allow you to do it all as long as the device can boot into Android.
cupfulloflol said:
You can get back to stock as long as you are at least rooted. You can do this, which will allow you to do it all as long as the device can boot into Android.
Click to expand...
Click to collapse
This is exactly what I am gonna try after getting the new phone set up. :good:
Hi all,
Trying to unlock the bootloader. I'm a bit of a noob regarding bootloader. I got it as far as rebooting into bootloader using command prompt. But as soon as the phone gets there it seems to hang. I will no longer get a response via command prompt (just telling me its waiting for device) and the device itself gets unresponsive. The hold 10 seconds to power down thing doesn't work either. I have to physically remove the battery for it to turn off.
Can anyone help me along? Cause I'd really like to root my phone.
Thank you
Roflmao. Guessing you haven't read any threads regarding root
WeeDoggy said:
Hi all,
Trying to unlock the bootloader. I'm a bit of a noob regarding bootloader. I got it as far as rebooting into bootloader using command prompt. But as soon as the phone gets there it seems to hang. I will no longer get a response via command prompt (just telling me its waiting for device) and the device itself gets unresponsive. The hold 10 seconds to power down thing doesn't work either. I have to physically remove the battery for it to turn off.
Can anyone help me along? Cause I'd really like to root my phone.
Thank you
Click to expand...
Click to collapse
Sadly unless you have the h815 version you are NOT going to get any further than what you are getting (at least at this point in time). The ONLY version of the G4 that has root right now is the h815 and that is simply because LG released the bootloader unlock via their page.
It is being worked on but you have to remember that this is a very new device and this is going to take some time, so just relax and play the waiting game with the rest of us in the mean time.
Yeah I have read the thread about rooting and I in fact do have the h815. That's why I am trying to root it and that's why I am busy trying to unlock the bootloader with the LG unlock tool. I said I'm a noob, not a dumbass regarding unlocking a bootloader cause before I had a samsung and I never needed to unlock that.
So once again my question stands why is my device getting unresponsive once it is succesfully been rebooted into bootloader via command prompt?
Thank you
WeeDoggy said:
Hi all,
Trying to unlock the bootloader. I'm a bit of a noob regarding bootloader. I got it as far as rebooting into bootloader using command prompt. But as soon as the phone gets there it seems to hang. I will no longer get a response via command prompt (just telling me its waiting for device) and the device itself gets unresponsive. The hold 10 seconds to power down thing doesn't work either. I have to physically remove the battery for it to turn off.
Can anyone help me along? Cause I'd really like to root my phone.
Thank you
Click to expand...
Click to collapse
Have you enabled the OEM Bootloader In Dev Options? Who is your provider as some of them will force lock the bootloader and not allow it to be unlocked unless you take it to a phone shop but you will void both LG's and Their Warranty and any support from them
Also when you are on bootloader screen with few lines with very litle fonts, try to make sure that in your Windows devices manager, your phone is corectly listed.
For some reason it did happend to me that drivers for the phone in bootloader mode wasn't properly installed.
bleuxeon said:
Also when you are on bootloader screen with few lines with very litle fonts, try to make sure that in your Windows devices manager, your phone is corectly listed.
For some reason it did happend to me that drivers for the phone in bootloader mode wasn't properly installed.
Click to expand...
Click to collapse
When I go into bootloader my PC does make that sound where it's like I disconnected a USB device. But as far as I can tell there's nothing unusual going in Windows device manager. Which drivers have you installed? I installed the pc drivers via my phone. And I saw adb drivers in there when it got installed. I thought that would suffice.
But it also freezes up. I can't close the phone anymore even with the 10-second power hold. It just locks up
Im having the exact same problem did everything right but as soon as i enter bootloading mode my pc just doesnt reconize it anymore or something
WeeDoggy said:
Hi all,
Trying to unlock the bootloader. I'm a bit of a noob regarding bootloader. I got it as far as rebooting into bootloader using command prompt. But as soon as the phone gets there it seems to hang. I will no longer get a response via command prompt (just telling me its waiting for device) and the device itself gets unresponsive. The hold 10 seconds to power down thing doesn't work either. I have to physically remove the battery for it to turn off.
Can anyone help me along? Cause I'd really like to root my phone.
Thank you
Click to expand...
Click to collapse
I had exactly the same problem with the same model. When the device is in fastboot mode and not responding open up devices and printers. For me it was now showing as android instead of G4 and the USB disconnect sound means you dont have to correct drivers even if you installed the LG drivers.
For me the fix was going to windows updater and allow it to update drivers. Now right click the android device and trouble run it. It updated the drivers for me
and I was able to run the command to get the device-id.
Hope it helps
Legion377 said:
I had exactly the same problem with the same model. When the device is in fastboot mode and not responding open up devices and printers. For me it was now showing as android instead of G4 and the USB disconnect sound means you dont have to correct drivers even if you installed the LG drivers.
For me the fix was going to windows updater and allow it to update drivers. Now right click the android device and trouble run it. It updated the drivers for me
and I was able to run the command to get the device-id.
Hope it helps
Click to expand...
Click to collapse
I have the same problem, what do you mean by "windows updater"? do you mean "windows update"?
And what is "trouble run it"?
Thanks in advance.
I was flashing a rom via twrp and the rom errored out. I tried reflashing but each time the rom didn't install fully. I wiped, rebooted and hoped for the best. Now, I'm stuck at the opening Huawei screen. Fastboot does not work. My computer recognizes the watch and shows HUAWEI WATCH under Universal Serial Bus devices in Device Manager. I've tried sending commands via command prompt but it just shows < waiting for device >. Any ideas on how to fix? I greatly appreciate any help. Thank you!
Ignore - I figured it out. I installed the Android SDK universal Google USB driver and I was able to get into fastboot. I then just flashed back to stock everything.
tfpHumorBlog said:
I was flashing a rom via twrp and the rom errored out. I tried reflashing but each time the rom didn't install fully. I wiped, rebooted and hoped for the best. Now, I'm stuck at the opening Huawei screen. Fastboot does not work. My computer recognizes the watch and shows HUAWEI WATCH under Universal Serial Bus devices in Device Manager. I've tried sending commands via command prompt but it just shows < waiting for device >. Any ideas on how to fix? I greatly appreciate any help. Thank you!
Click to expand...
Click to collapse
Lots of posts and solutions about this, here is one.
http://forum.xda-developers.com/huawei-watch/help/bricked-updating-to-android-wear-2-0-t3436336
Bro I got the same problem. My watch got stuck on Huawei Logo. Can you help me out? How can I go to fastboot. Cause holding the home button is not working
JOHN BALAGSO said:
Bro I got the same problem. My watch got stuck on Huawei Logo. Can you help me out? How can I go to fastboot. Cause holding the home button is not working
Click to expand...
Click to collapse
If the button does not work, you probably have a defective unit. Get an RMA and return it.
Pkt_Lnt said:
If the button does not work, you probably have a defective unit. Get an RMA and return it.
Click to expand...
Click to collapse
Well the button is working but not going to bootloader. Sometimes it works but couldnt restart the watch so cant go to bootloader. Is there a way to go to bootloader directly using computer?
JOHN BALAGSO said:
Well the button is working but not going to bootloader. Sometimes it works but couldnt restart the watch so cant go to bootloader. Is there a way to go to bootloader directly using computer?
Click to expand...
Click to collapse
Code:
adb reboot bootloader
Do you have the ADB program installed and drivers loaded?
https://developer.android.com/studio/command-line/adb.html
Pkt_Lnt said:
Code:
adb reboot bootloader
Do you have the ADB program installed and drivers loaded?
https://developer.android.com/studio/command-line/adb.html
Click to expand...
Click to collapse
Yes I have, but I cant do adb cause cant get my watch to get past the huawei logo
Hi everyone,
Hoping to find an answer to this issue. I was downgrading my firmware from oreo to naugat via duk fullOTA ROM flasher method. My bootloader was unlocked. Process went well till 99% after that phone went off and now its not switching on. Battery was almost 90% at that time. I have tried every possible method during last few days. When it's connected to a PC, there is a clicking sound in the PC and in device manager it is shown as SER_USB. If I try to execute any command via adb method, it shows waiting for device. I even dismantled the whole device, disconnected every wire and reconnected them again.
Is there any possibility of reviving it or it's time to move on.
Thanks
sunnyshaan0414 said:
Hi everyone,
Hoping to find an answer to this issue. I was downgrading my firmware from oreo to naugat via duk fullOTA ROM flasher method. My bootloader was unlocked. Process went well till 99% after that phone went off and now its not switching on. Battery was almost 90% at that time. I have tried every possible method during last few days. When it's connected to a PC, there is a clicking sound in the PC and in device manager it is shown as SER_USB. If I try to execute any command via adb method, it shows waiting for device. I even dismantled the whole device, disconnected every wire and reconnected them again.
Is there any possibility of reviving it or it's time to move on.
Thanks
Click to expand...
Click to collapse
move on