M8 stuck on boot screen, detected by ADB but not following commands - One (M8) Q&A, Help & Troubleshooting

I am on Wolla 5.0 and elementalx 6 something but I don't think these caused the stuck as the phone had been working fine.
Right before the phone was stuck, I updated an app called Lucky Patcher; I then restarted the phone and it's been stuck.
Under Devices manager My HTC shows this device is working properly.
M8 was detected by Adb. But when I typed commands such as "fastboot reboot bootloader" or "fastboot reboot recovery" ADB shows and stuck at "Waiting for device".
it has been like this for two hours.
Please help.

Whileitlasted said:
I am on Wolla 5.0 and elementalx 6 something but I don't think these caused the stuck as the phone had been working fine.
Right before the phone was stuck, I updated an app called Lucky Patcher; I then restarted the phone and it's been stuck.
Under Devices manager My HTC shows this device is working properly.
M8 was detected by Adb. But when I typed commands such as "fastboot reboot bootloader" or "fastboot reboot recovery" ADB shows and stuck at "Waiting for device".
it has been like this for two hours.
Please help.
Click to expand...
Click to collapse
That's what you get for using Lucky Patcher I guess. Get rid of it and stop ripping developers off.
Okay........................ the problem is you are using fastboot commands while booted to system would be my guess.
Try this:
adb reboot bootloader
You can only use fastboot commands while booted into bootloader. While booted into system (into your ROM or recovery) you can only use adb commands

xunholyx said:
That's what you get for using Lucky Patcher I guess. Get rid of it and stop ripping developers off.
Okay........................ the problem is you are using fastboot commands while booted to system would be my guess.
Try this:
adb reboot bootloader
You can only use fastboot commands while booted into bootloader. While booted into system (into your ROM or recovery) you can only use adb commands
Click to expand...
Click to collapse
Hi, I already tried the adb commands (reboot, reboot recovery, reboot bootloader) along with the fastboot ones; the adb ones didn't even show "waiting for device", instead a new command line was show, i.e. as if it was not aware of the adb commands.
I let the battery ran out (nothing I could do about it anyway) and after a full charge, the phone is now working with god knows why/how. The app is also working fine and no further issues happen. I will keep an eye on it and see how it goes.
Although phone is working, I am still very curious with what exactly happened...

Related

[HOW TO] Root only STOCK/No Custom Recovery

Taken FROM http://rootzwiki.com/topic/11732-galaxy-nexus-root-procedure-broken-adb-method-dont-use/
With the big change of YOU WILL BOOT LOOP WAIT FOR ADB TO RESPOND and push all the commands then pull the battery and disconnect your USB cable and reboot normal you should have perm root!
**As always RootzWiki nor myself are responsible if something goes wrong. Root your phone at your own risk with the understanding it will void your warranty and there is always a chance of something going wrong.**
*This method WILL WIPE YOUR DATA*
First download Galaxy Nexus FYA Root Package and extract it to c:\gnexroot (for the purposes of this guide)
Also if you wipe and format remember to re-enable Debug mode before restarting processes listed above.
Method
1. First, navigate to C:\gnexroot and install the Samsung drivers (Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0.exe)
1. If those drivers dont work download pdanet from here http://forum.xda-dev....php?p=19709279 and let pdanet install the drivers for you. Worked for some of us.
2. With the phone turned OFF, hold VOLUME UP + VOLUME DOWN and power the phone on. This will put you in bootloader mode.
3. Navigate again to C:\gnexroot, and hold SHIFT on your keyboard, and right click in the white space. Then, click 'Open command window here'
4. In the command prompt, type:
fastboot oem unlock
You will be prompted to confirm that you wish to unlock the bootloader. You do, of course.
5. Once the bootloader has been unlocked, it's time to boot up the device using the insecure boot.img (ro.secure=0 set in the ramdisk). This essentially means you have permanent root for the duration of this boot session. In order to boot up using that boot image, simply type:
fastboot boot boot.img
Don't expect to see anything wildly different during the boot process - it will boot as normal.
6. Once the phone has booted, in the command prompt window, type the following commands, pressing enter after each line:
adb root
adb remount
adb push su /system/bin
adb push Superuser.apk /system/app
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
adb reboot
Again I did NOT write these steps nor did I take credit for this procedure. My goal was to have all this information easy to access here so people don't brick their new device
Edit:
If you get stuck at the google logo and cannot push adb commands, pull the battery and usb cable then reinsert and reboot. If this doesn't work Reboot into recovery and wipe everything and start over.
12/17/2011
If you do a factory restore remember to boot at least once after and re-enable debug mode.
anyone had the issue of not being able to unlock the bootloader?
i ran the command "fastboot oem unlock" and it just sticks at the response: <waiting for device>
but nothing shows on my phone.
aldouse said:
anyone had the issue of not being able to unlock the bootloader?
i ran the command "fastboot oem unlock" and it just sticks at the response: <waiting for device>
but nothing shows on my phone.
Click to expand...
Click to collapse
I would guess your computer is not recognizing the device. Try installing the drivers and connecting the phone to the computer while it is in normal mode not the bootloader. It should install the drivers correctly that way and your computer will then recognize it when you boot into the bootloader and the commands should work.
yea... you are right... it was the samsung drivers not fully loading. re-installed the drivers then doing a windows update showed that there's a new set of samsung drivers on the windows update that needed to be installed. that did the trick.
The superboot method worked just fine for me.
Sent from my Galaxy Nexus using Tapatalk
SomeGuyDude said:
The superboot method worked just fine for me.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
same though I had a bootloop but it did root itself.
Sent from my Galaxy Nexus using Tapatalk
aldouse said:
anyone had the issue of not being able to unlock the bootloader?
i ran the command "fastboot oem unlock" and it just sticks at the response: <waiting for device>
but nothing shows on my phone.
Click to expand...
Click to collapse
You must be in recovery mode. Turn the phone off, press volume up and down as well as power. Keep it there until you're in recovery and then unlock.
Sent from my Galaxy Nexus using Tapatalk
innov8ion said:
You must be in recovery mode. Turn the phone off, press volume up and down as well as power. Keep it there until you're in recovery and then unlock.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Its not recovery mode, but fastboot mode. If you are in recovery fastboot won't be recognized. Looks like he got it fixed by checking his drivers.
can you also use this method for a Verizon Galaxy Nexus???
http://forum.xda-developers.com/showthread.php?t=1392310
is there any difference?
Superboot method actually does the same thing as this method from what I read just one is automatic and one is manual.
Being I didn't see anyone else rooting from Verizon I took the time to figure out a manual method so i can verify each step and figure out issues if I ran in to any. With Superboot its either it works or it doesn't there is no playing with procedures.
This should work for other carriers to, I can only verify it for Verizon though.
I get past <adb reboot bootloader> just fine but then when I do a <fastboot oem unlock> it just says "waiting for device" forever. everything is installed but under my drivers it says;
"Android 1.0" drivers not installed.
plz someone help, ive searched all over the net but only found help for HTC phones and 2007 old posts.
edit: I am in "Fastboot mode"
Update the Samsung ADB driver under device manager while you are sitting in the bootloader. I'm bootlooping after pushing the boot.img
got it working, "Note: 1" under this guide fixed it.
http://forum.xda-developers.com/showthread.php?t=1392310
thanks again XDA!!
GOod. Mine is still bootlooping back to the Google screen with a lock on it.
Booted into recovery, formatted. At least i can boot up now.
fatsix said:
GOod. Mine is still bootlooping back to the Google screen with a lock on it.
Booted into recovery, formatted. At least i can boot up now.
Click to expand...
Click to collapse
Sounds like you didn't successfully unlock your bootloader. Have you resolved this?
Done and rooted. Pushing APK's now.
I would recommend doing a full wipe first. I think something got corrupted during the forced wipe when unlocking.
After wiping, I started over. Unlocked and flashed the boot.img. Got a full normal reboot. Flashed it a second time, and it stayed at the google screen and i could connect to it with ADB. Pushed all the commands and rebooted. Works great.
Thank you.
I assume you need to have adb installed before doing this? Or do the command prompts perform from windows?
Sent from my SCH-I500 using Tapatalk
I had it previously installed. If you download the zip. its already in there, just run it right from the directory you unzip it from.
I would like to return my phone to stock. Locked, unrooted, and available for OTAs. Is there a way to do this yet?
craighwk said:
I would like to return my phone to stock. Locked, unrooted, and available for OTAs. Is there a way to do this yet?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1394051
After you complete that Run:
fastboot oem unlock
From the main instructions and simply relock it.

cant enter recovery

ive installed a rom and it wont boot (FC's loop), i tried to enter recovery (-vol and power when phone is off) but it keeps trying to boot, ive flashed loads of roms and entered recovery a fair few times so i dont know why i cant do it now!
Do you have the Android SDK or any other adb tool installed on your PC? If you do, try plugging the phone in to the USB port on the PC and open a command prompt.
Type this:
Code:
adb reboot recovery
Not sure if that will work if the phone doesn't boot into Android though. You might have to time it just right, to find a point when the phone responds to adb commands but before it reboots.
How far does the phone get before it reboots? Do you just get the splash screen, the bootanimation, or what exactly happens?
Actually, you might have more luck with using fastboot from a command prompt:
Code:
fastboot reboot-bootloader

DESPERATE need help!! one x recovery failure??

so i had just htc dev unocked my one x, now i was using hasoons tool, and when i tried to flash a recovery in fastboot with commands, everything in the prompt said okay.. flashed successful and so on, and the bar on the top right hand side of my phone flickered as if to load, but didint. now when i go to recovery mode, it gives me the splash screen with some red letter **** about distrabution, then reboots. ive tried flashing every possible recovery for the one x, including stock, and seems to do nothing, help??
pic is the screen rite b4 reboot (thats what i get when i reboot into recovery)
EDIT:: now im stuck at the screen in the picture, will not boot into anything else, will not be recognized by adb. PLEASE HELP!!!!
EDIT EDIT: i can power off, and get back into fast boot with volume off, but im almost asuming i just have no recovery..... and it will NOT! boot into the phone no matter what, only booting into that screen... what the **** do i do lol this is kind of a panic now
Have you tried reflashing stock recovery? Also shouldn't you be in the AT&T One X forum unless of course you have the international version of the One X.
I have tried the stock recovery, but now its in fastboot and won't get recognized by adb on my pc as it did. It just boot loops now at that screen and won't get recognized. And this isn't at. &t
ixi_devo_ixi said:
I have tried the stock recovery, but now its in fastboot and won't get recognized by adb on my pc as it did. It just boot loops now at that screen and won't get recognized. And this isn't at. &t
Click to expand...
Click to collapse
You're suppose to flash stock recovery in fastboot.
I know, I tried when it was getting recognized, now I can't even pick it up with adb
so its telling me to flash the stock RUU, but i cant use adb commands it wont recognize in fastboot, the computer dings when i plug it in, but adb devices comes up with nothing, i tried every usb port on my pc and everything
ixi_devo_ixi said:
so its telling me to flash the stock RUU, but i cant use adb commands it wont recognize in fastboot, the computer dings when i plug it in, but adb devices comes up with nothing, i tried every usb port on my pc and everything
Click to expand...
Click to collapse
First of all ADB only works in RECOVERY mode not directly in bootloader. So do the following steps & instal custom rom (Any1 u like).
1. You need recovery.img in your fastboot directory
2. Go into bootloader and connect phone
3. Then use: "fastboot boot recovery.img" (thus booting your image from pc and not the installed recovery).
4. When in recovery, you can use the adb commands.
5. You can try with "adb devices" which should show you serial of phone.
6. command: adb push rom_rom.zip /sdcard
credits to broncogr for finding that adb works if you use fastboot boot command and to Jotha for helping me out!

Tied everything to root swift, cant get past initial fastboot stage

hi all, sorry if this has beeen posted before but its bugging me as i spent literally 4-5 hours lastnight trying to sort it, i havee rooted 4-5 android phones in the past but im just having no luck with this one
i installed adb / fastboot minimal, enabled what needed to be enabled in developer options on the swift, booted the swift into fastboot mode, then when i run adb on my computer, the first command works 'fastboot oem unlock' but after that its constantly saying 'waiting for devices' whenever i try the next phase of commands ie. fastboot -i 0x2970 oem unlock-go etc it just wont detect the device at all in windows on adb, is there any suggestions anyone could throw out there before i end up sending it back and getting an alternative android phone thats easier to root? the only thing i can think off is its a usb driver issue? but i installed the gloogle usb drivers and it picks up the phone for file transfer etc so im not sure if this is the issue. many thanks!
yodjone1 said:
hi all, sorry if this has beeen posted before but its bugging me as i spent literally 4-5 hours lastnight trying to sort it, i havee rooted 4-5 android phones in the past but im just having no luck with this one
i installed adb / fastboot minimal, enabled what needed to be enabled in developer options on the swift, booted the swift into fastboot mode, then when i run adb on my computer, the first command works 'fastboot oem unlock' but after that its constantly saying 'waiting for devices' whenever i try the next phase of commands ie. fastboot -i 0x2970 oem unlock-go etc it just wont detect the device at all in windows on adb, is there any suggestions anyone could throw out there before i end up sending it back and getting an alternative android phone thats easier to root? the only thing i can think off is its a usb driver issue? but i installed the gloogle usb drivers and it picks up the phone for file transfer etc so im not sure if this is the issue. many thanks!
Click to expand...
Click to collapse
Hi,
I had the same issue. When that happens, do commands without the -i 0x2970 bit. So for example:
fastboot -i 0x2970 erase recovery
becomes:
fastboot erase recovery
Hope this helps
-Jev
I tried this but it still says 'waiting for any device' My initial command worked for fastboot oem unlock, but then I just couldnt do the following commands, and as a result whenever i tried to install a custom recovery / rom it gave me the error along the lines of 'unable to verify....'
edit: when i missed out the -i part, then said its already unlocked. however i still am not able to install supersu or the recovery as it still gives me the error 'signature verification failed'
yodjone1 said:
I tried this but it still says 'waiting for any device' My initial command worked for fastboot oem unlock, but then I just couldnt do the following commands, and as a result whenever i tried to install a custom recovery / rom it gave me the error along the lines of 'unable to verify....'
edit: when i missed out the -i part, then said its already unlocked. however i still am not able to install supersu or the recovery as it still gives me the error 'signature verification failed'
Click to expand...
Click to collapse
Hi,
OK, what recovery are you trying to install? I would recommend TWRP 3.0.2 by Beroid (in the development section) because it's easy to use and it works. Get the image and put it in your adb folder is. Make sure you are in fastboot. Then run commands
- fastboot erase recovery
- fastboot flash recovery (name of file).img
Disconnect the device from your computer. Then remove the battery. Then replace the battery and press VOLUME DOWN and POWER to rebbot in to recovery mode to verify the installation.
You should now be in the recovery. You can flash custom roms and supersu within this new recovery.
Hope this helps
-Jev

XL Bricked

Hi people,
I unlocked, rooted, and flashed Liquid on my XL tonight. Everything seemed to be going fine when I rebooted again and got a bootloop. TWRP is not loading, what I am getting is the Android on it's back menu and here's where I'm lost. I'm getting the error in the screenshots when I try to sideload the factory image from ADB. My cords are good, drivers are updated, and I have ADB and Fastboot set to Large Address Aware. I don't want to admit that I have a paperweight now. Any ideas? Thanks in Advance
elektrosoundwave said:
Hi people,
I unlocked, rooted, and flashed Liquid on my XL tonight. Everything seemed to be going fine when I rebooted again and got a bootloop. TWRP is not loading, what I am getting is the Android on it's back menu and here's where I'm lost. I'm getting the error in the screenshots when I try to sideload the factory image from ADB. My cords are good, drivers are updated, and I have ADB and Fastboot set to Large Address Aware. I don't want to admit that I have a paperweight now. Any ideas? Thanks in Advance
Click to expand...
Click to collapse
Can you reboot to download mode (fastboot)? Hold the power button and vol down buttons together.
If you can get into the bootloader, use fastboot to flash the factory image instead of using adb. Or try issuing 'adb reboot-bootloader' command to reboot to bootloader
koivth said:
Can you reboot to download mode (fastboot)? Hold the power button and vol down buttons together.
If you can get into the bootloader, use fastboot to flash the factory image instead of using adb. Or try issuing 'adb reboot-bootloader' command to reboot to bootloader
Click to expand...
Click to collapse
Both volume buttons? I've only done the power and down volume. I will try both of these when I get home tonight, or when I wake up. I stayed up until 6am working on this and did not get much sleep. I'm also going to uninstall and reinstall the Pixel driver. I don't remember off the top of my head if I installed it before or after I upgraded my laptop to Windows 10.
elektrosoundwave said:
Both volume buttons? I've only done the power and down volume. I will try both of these when I get home tonight, or when I wake up. I stayed up until 6am working on this and did not get much sleep. I'm also going to uninstall and reinstall the Pixel driver. I don't remember off the top of my head if I installed it before or after I upgraded my laptop to Windows 10.
Click to expand...
Click to collapse
Sorry for being unclear. To get into the bootloader (where you can use the fastboot command to re-flash the factory image), you hold the Power Button and Volume Down buttons together (not volume up button). This is what your screen should look like if you successfully get to the bootloader: https://www.xda-developers.com/files/2016/10/CvqcEDHUsAA_EY4.jpg
If you see that screen, you're sitting good. Download the latest factory image (https://developers.google.com/android/images#marlin) and run the flash-all.bat (for windows) script to reflash your phone. You will have to have fastboot drivers installed on your computer for that to work.
If your device is recognized by adb (if you type 'adb devices' and it shows your device as the output) but you are having trouble getting to the bootloader, you can type in 'adb reboot-bootloader' to reboot your device into fastboot mode where you can flash the factory image. Hopefully that helps push you in the right direction. Your phone isn't bricked/lost forever if adb or fastboot recognizes your device and you can save it!
koivth said:
Sorry for being unclear. To get into the bootloader (where you can use the fastboot command to re-flash the factory image), you hold the Power Button and Volume Down buttons together (not volume up button). This is what your screen should look like if you successfully get to the bootloader: https://www.xda-developers.com/files/2016/10/CvqcEDHUsAA_EY4.jpg
If you see that screen, you're sitting good. Download the latest factory image (https://developers.google.com/android/images#marlin) and run the flash-all.bat (for windows) script to reflash your phone. You will have to have fastboot drivers installed on your computer for that to work.
If your device is recognized by adb (if you type 'adb devices' and it shows your device as the output) but you are having trouble getting to the bootloader, you can type in 'adb reboot-bootloader' to reboot your device into fastboot mode where you can flash the factory image. Hopefully that helps push you in the right direction. Your phone isn't bricked/lost forever if adb or fastboot recognizes your device and you can save it!
Click to expand...
Click to collapse
That's where that first screenshot came from. I will try the reboot bootloader tonight. They sort of recognize my phone, but I can't get them to flash anything. This isn't my first rodeo with borked phones, but I don't think I've had this much trouble since I placed the wrong boot animation on my Droid 4 many years ago.
:victory: :highfive: It's flashing right now. You don't know how much I appreciate it.
Hi, thought I would jump in on this thread. I have the same issue, and I can get to the fastboot screen and device is recognised by adb with "fastboot devices". When I try to flash-all I get the message that the device must be unlocked. Any idea why mine in different? I just have stock recovery, maybe that is it. The device also will not boot into recovery, it just bootloops
obsidianlycanthrope said:
Hi, thought I would jump in on this thread. I have the same issue, and I can get to the fastboot screen and device is recognised by adb with "fastboot devices". When I try to flash-all I get the message that the device must be unlocked. Any idea why mine in different? I just have stock recovery, maybe that is it. The device also will not boot into recovery, it just bootloops
Click to expand...
Click to collapse
Is your bootloader unlocked?
obsidianlycanthrope said:
Hi, thought I would jump in on this thread. I have the same issue, and I can get to the fastboot screen and device is recognised by adb with "fastboot devices". When I try to flash-all I get the message that the device must be unlocked. Any idea why mine in different? I just have stock recovery, maybe that is it. The device also will not boot into recovery, it just bootloops
Click to expand...
Click to collapse
Before you can flash the factory image, you have to unlock the bootloader by issuing this command first: 'fastboot flashing unlock'

Categories

Resources