Database Develop

[Q] help! Can't access bootloader

My phone was stuck when install apps, so I restarted it by holding power key. Then is hard brick... I can't access bootloader and I tried http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
After blank-flash.bat, it shows greet-device: error reading packet.
What can I do? Help, thanks:crying:

fwkimi said:
My phone was stuck when install apps, so I restarted it by holding power key. Then is hard brick... I can't access fastboot and I tried http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
After blank-flash.bat, it shows greet-device: error reading packet.
What can I do? Help, thanks:crying:
Click to expand...
Click to collapse
I doubt that you needed to use that fix. That fix is for the downgraded bootloader brick. I suspect you were only in soft brick. Was it bootlooping?
Hold power and volume down to enter bootloader. Do or did you have TWRP installed?
More information please.

Evolution_Tech said:
I doubt that you needed to use that fix. That fix is for the downgraded bootloader brick. I suspect you were only in soft brick. Was it bootlooping?
Hold power and volume down to enter bootloader. Do or did you have TWRP installed?
More information please.
Click to expand...
Click to collapse
Dear. there is nothing after hold power and volume down, can't reboot, enter bootloader and TWRP... There is nothing on screen even charging... Only black screen. It quite strange
It show new added hardware when the phone connect with PC.
I only root and install xposed. System is 5.1.1, international version.
It showed qhsubs_bulk before I install Qualcomm Drivers. So I think maybe there are similar issue. Thanks
View attachment 3397226
View attachment 3397227

fwkimi said:
Dear. there is nothing after hold power and volume down, can't reboot, enter bootloader and TWRP... There is nothing on screen even charging... Only black screen. It quite strange
It show new added hardware when the phone connect with PC.
I only root and install xposed. System is 5.1.1, international version.
View attachment 3397226
View attachment 3397227
Click to expand...
Click to collapse
Xposed bites another one. Lol

prdog1 said:
Xposed bites another one. Lol
Click to expand...
Click to collapse
oh no:crying: I install it on Nexus4, only reboot more times...

Leave on charger for a while. If battery all way down will not show charging and will not let into bootloader or recovery.

prdog1 said:
Leave on charger for a while. If battery all way down will not show charging and will not let into bootloader or recovery.
Click to expand...
Click to collapse
Ok, have a try.
The phone and charger are not very hot as charging. Will it impact HW issue? I'm lost:crying:

fwkimi said:
Ok, have a try.
The phone and charger are not very hot as charging. Will it impact HW issue? I'm lost:crying:
Click to expand...
Click to collapse
No. But if can't boot at all will have to RMA. N9 and N6 will show nothing if battery completely down. Has to have at least 10% (guessing) before will do anything once totally depleted.

prdog1 said:
No. But if can't boot at all will have to RMA. N9 and N6 will show nothing if battery completely down. Has to have at least 10% (guessing) before will do anything once totally depleted.
Click to expand...
Click to collapse
It's hardly to RMA in China:crying: I doubt it's HW issue...

fwkimi said:
It's hardly to RMA in China:crying: I doubt it's HW issue...
Click to expand...
Click to collapse
If unlocked and can get into bootloader there is a chance. If locked and won't boot not much hope.

prdog1 said:
If unlocked and can get into bootloader there is a chance. If locked and won't boot not much hope.
Click to expand...
Click to collapse
I unlocked it, but can't access bootloader... I need amend my title.

fwkimi said:
I unlocked it, but can't access bootloader... I need amend my title.
Click to expand...
Click to collapse
Leave on charger. Sounds like only hope.

prdog1 said:
Leave on charger. Sounds like only hope.
Click to expand...
Click to collapse
:crying: It seems only I hve this problem, is there anyone else? Or it's a HW issue and just happen on that time...

fwkimi said:
My phone was stuck when install apps, so I restarted it by holding power key. Then is hard brick... I can't access bootload and I tried http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
After blank-flash.bat, it shows greet-device: error reading packet.
What can I do? Help, thanks:crying:
Click to expand...
Click to collapse
Flash-all doesn`t on Windows, you have to flash the img`s seperately in fastboot. Just press volume up and down +power to get in fastboot mode.

gee2012 said:
Flash-all doesn`t on Windows, you have to flash the img`s seperately in fastboot. Just press volume up and down +power to get in fastboot mode.
Click to expand...
Click to collapse
FWIW: it doesn't work on Ubuntu either.

cam30era said:
FWIW: it doesn't work on Ubuntu either.
Click to expand...
Click to collapse
Oke, it works on Linux according to users

gee2012 said:
Oke, it works on Linux according to users
Click to expand...
Click to collapse
Hmm. Must be me. Thanks. Anyway, I prefer to do it manually. Just like the transmission in my car.

gee2012 said:
Flash-all doesn`t on Windows, you have to flash the img`s seperately in fastboot. Just press volume up and down +power to get in fastboot mode.
Click to expand...
Click to collapse
Sorry, I can't access bootloader. Nothing shows when power+volumn+ or power +volumn-. I think it maybe bricked

hi,
I seem to have the same problem as OP, I have no access to fastboot, either by console or button combination.
I also tried the solution provided by opssemnik but when I try to use blank-flash I get the error "sdl-transfer-image:send-image:sdl-open-multi:target error" when flashing singleimage.bin.
I have Lollipop 5.1.1. Any ideas? My phone seems a goner now...

none
DO you have SDK manager installed on your computer and your phone's manufacturer Drivers? If not install SDK Manager here.
http://developer.android.com/sdk/index.html#top Scroll down to the bottom of the page and select SDK tools only, you will see the link for windows.
After you've installed this and the drivers from the manufacturer go into SDK you just installed and install "Google USB Driver".
From there open a command prompt, plug your phone into the computer and type "adb reboot bootloader" without the quotation marks and that will get you into bootloader. you can also type "adb reboot recovery" without the quotes.
ANother way is to go to Titanium backup, hit menu, scroll down to reboot to recovery. One of those should work.

OP3T - Black (broken) screen. How to recovery data (debug not enabled)

Hi all,
I have a particularly tricky case here. A OnePlus 3T with a broken screen (its black, can't tell if its registering taps) which I need to recovery data (photos) from. Normally I'd just use ADB but of course usb-debugging isn't enabled. I've tried rebooting into recovery... hold the power button and vol-down until the phone vibrates, keep holding for a few seconds. Then wait. Then vol down twice and power again to hopefully select English but the when I try
Code:
adb devices
nothing comes up on the list.
I'm wondering if anyone has any ideas how I can recover data/photos from this device.
One again the facts are:
-OnePlus 3T
-screen is broken, black, doesn't display anything
-usb-debugging is NOT enabled
-i can see the device in fastboot mode (boot w/ vol-up+power)
Thanks!

willjeffery said:
Hi all,
I have a particularly tricky case here. A OnePlus 3T with a broken screen (its black, can't tell if its registering taps) which I need to recovery data (photos) from. Normally I'd just use ADB but of course usb-debugging isn't enabled. I've tried rebooting into recovery... hold the power button and vol-down until the phone vibrates, keep holding for a few seconds. Then wait. Then vol down twice and power again to hopefully select English but the when I try
Code:
adb devices
nothing comes up on the list.
I'm wondering if anyone has any ideas how I can recover data/photos from this device.
One again the facts are:
-OnePlus 3T
-screen is broken, black, doesn't display anything
-usb-debugging is NOT enabled
-i can see the device in fastboot mode (boot w/ vol-up+power)
Thanks!
Click to expand...
Click to collapse
Replace the screen and recover your data?
Anyways,this ain't OP3T forums,this is OPO forums.

Anyways,this ain't OP3T forums,this is OPO forums.
Click to expand...
Click to collapse
Oh whoops. Been a while since I posted on here. I'll post on there an have a mod delete this thread.
Also yes, that's an option but the repair place can't guarantee that the device won't be formatted during the repair... how that would happen is beyond me.

willjeffery said:
Oh whoops. Been a while since I posted on here. I'll post on there an have a mod delete this thread.
Also yes, that's an option but the repair place can't guarantee that the device won't be formatted during the repair... how that would happen is beyond me.
Click to expand...
Click to collapse
I don't see any need to format device after replacing broken screen? Is your device still on warranty?

Mr.Ak said:
I don't see any need to format device after replacing broken screen? Is your device still on warranty?
Click to expand...
Click to collapse
My thoughts exactly. My only guess is that the repair place would just swap out the device for a refurb. Also, its not my device, belongs to a friend who asked for advice. I believe its out of warranty. The phone was dropped away so likely wouldn't be covered, anyway.

willjeffery said:
My thoughts exactly. My only guess is that the repair place would just swap out the device for a refurb. Also, its not my device, belongs to a friend who asked for advice. I believe its out of warranty. The phone was dropped away so likely wouldn't be covered, anyway.
Click to expand...
Click to collapse
Why not replace it yourself? It is much easy and cheap way.

YouTube is your best friend for DIY replacements!
Sizzled with Bacon ?

I'm having a similar problem. Did you fixed your phone? I'm unemployed and i don't have money to buy a replacement screen.

Boot fastboot
Install TWRP via fastboot command with "fastboot flash recovery recovery.img" -make sure to designate file location of recovery image in terminal
boot into recovery from fastboot with "fastboot reboot recovery"
MTP should be enabled by default
If the device is encrypted, you will not be able to access the files without entering encryption key in TWRP.
In that case, a repair of the screen will be necessary to obtain access to the files
If the phone is not bootloader unlock, it would require a FULL DATA WIPE in order to do so, which would not be beneficial in your case.

ADB Works, Fastboot still "waiting for any device"

I have been blundering my way though the internet to get my ROG Phone 2 rooted. I have unlocked the bootloader, I have a modified boot image from magisk, I have the ADB connection set up through USB and it works fantastically. I honestly don't know how I got it work, it involved many different driver update attempts and then figuring out I hadn't put the phone into USB debugging, but now fastboot doesn't work.
ADB will list the device, but fastboot cannot see it. I have tried rebooting the phone into the bootloader, but there is no connection on either. Not sure why I thought that would work, but I tried. I really don't understand enough about fastboot to get any farther on my own.
I have the tencent version and I was pretty certain I have the CN android 9.0 on it, but I am no longer certain of that. I am running windows 10.
This is my build number: PKQ1.190414.001.WW_Phone-16.0622.1906.19-0
I honestly don't know, but does that WW mean my tencent phone is running the WW firmware?

RichDoe252 said:
I have been blundering my way though the internet to get my ROG Phone 2 rooted. I have unlocked the bootloader, I have a modified boot image from magisk, I have the ADB connection set up through USB and it works fantastically. I honestly don't know how I got it work, it involved many different driver update attempts and then figuring out I hadn't put the phone into USB debugging, but now fastboot doesn't work.
ADB will list the device, but fastboot cannot see it. I have tried rebooting the phone into the bootloader, but there is no connection on either. Not sure why I thought that would work, but I tried. I really don't understand enough about fastboot to get any farther on my own.
I have the tencent version and I was pretty certain I have the CN android 9.0 on it, but I am no longer certain of that. I am running windows 10.
This is my build number: PKQ1.190414.001.WW_Phone-16.0622.1906.19-0
I honestly don't know, but does that WW mean my tencent phone is running the WW firmware?
Click to expand...
Click to collapse
Fun fact, I just got Fastboot access from my computer by using the side USB port and rebooting into the bootloader from ADB. Still not to sure about the version bit. I think I'm just going to give it whirl and brick my device, maybe.

RichDoe252 said:
I have been blundering my way though the internet to get my ROG Phone 2 rooted. I have unlocked the bootloader, I have a modified boot image from magisk, I have the ADB connection set up through USB and it works fantastically. I honestly don't know how I got it work, it involved many different driver update attempts and then figuring out I hadn't put the phone into USB debugging, but now fastboot doesn't work.
ADB will list the device, but fastboot cannot see it. I have tried rebooting the phone into the bootloader, but there is no connection on either. Not sure why I thought that would work, but I tried. I really don't understand enough about fastboot to get any farther on my own.
I have the tencent version and I was pretty certain I have the CN android 9.0 on it, but I am no longer certain of that. I am running windows 10.
This is my build number: PKQ1.190414.001.WW_Phone-16.0622.1906.19-0
I honestly don't know, but does that WW mean my tencent phone is running the WW firmware?
Click to expand...
Click to collapse
1. You are running a WW rom, but that doesn't necessarily mean your fingerprint is matched. To update you need to have both WW rom and WW fingerprint. You can check if your fingerprint is CN or WW using device info hw from playstore under 'system'
2. In order to root you need to have a matching root boot img for your current rom ie root img for 1906.19, just checking that your know this?
3. Have you managed to get the phone recognised using the cmd 'fastboot devices'? Also are you using the side port?
4.when you say bootloader, have you definitely got the phone in fastboot mode - hold vol up and power button until you see the screen with some options. That screen is fastboot mode, you don't need to select any further options. Once in that mode, connect to pc, open adb and run the fastboot devices cmd. Once your device is recognised, report back here for further steps

superbrick.
reg66 said:
1. You are running a WW rom, but that doesn't necessarily mean your fingerprint is matched. To update you need to have both WW rom and WW fingerprint. You can check if your fingerprint is CN or WW using device info hw from playstore under 'system'
2. In order to root you need to have a matching root boot img for your current rom ie root img for 1906.19, just checking that your know this?
3. Have you managed to get the phone recognised using the cmd 'fastboot devices'? Also are you using the side port?
4.when you say bootloader, have you definitely got the phone in fastboot mode - hold vol up and power button until you see the screen with some options. That screen is fastboot mode, you don't need to select any further options. Once in that mode, connect to pc, open adb and run the fastboot devices cmd. Once your device is recognised, report back here for further steps
Click to expand...
Click to collapse
Thanks for the reply! I did indeed get fastboot to work over USB. Fastboot devices reported back the serial number and everything. I did not know that the build need to match on both the boot and the rom, but that does make sense and I probably should have realized that before I went ahead and copied the rooted boot.img I had over. Then my phone couldn't boot up proper, and got stuck in fastboot. Then I went ahead and copied all of the contents of the same rom over and now it is literally just a black screen. Won't turn on any more. I think I super bricked it.
Sorry I didn't see your post earlier and I know I am not father into the deep end, but is there a way out from where I am.

RichDoe252 said:
Thanks for the reply! I did indeed get fastboot to work over USB. Fastboot devices reported back the serial number and everything. I did not know that the build need to match on both the boot and the rom, but that does make sense and I probably should have realized that before I went ahead and copied the rooted boot.img I had over. Then my phone couldn't boot up proper, and got stuck in fastboot. Then I went ahead and copied all of the contents of the same rom over and now it is literally just a black screen. Won't turn on any more. I think I super bricked it.
Sorry I didn't see your post earlier and I know I am not father into the deep end, but is there a way out from where I am.
Click to expand...
Click to collapse
Oh jeepers dude. So just a black screen... Can you at least boot into fastboot?

reg66 said:
Oh jeepers dude. So just a black screen... Can you at least boot into fastboot?
Click to expand...
Click to collapse
Nope. The only response I can get out of it now is when I plug it into the fastboot port, the computer recognizes that something was plugged in. I don't even get a device on a device manager.

RichDoe252 said:
Nope. The only response I can get out of it now is when I plug it into the fastboot port, the computer recognizes that something was plugged in. I don't even get a device on a device manager.
Click to expand...
Click to collapse
Try holding the power button for around 20 secs until it shuts down. Then try vol up and power together and see if you get back to fastboot. If that doesn't work try vol up vol down and power buttons all together. Then try again to put it in fastboot mode using vol up and power. Let us know what happens /if you can reach fastboot mode

reg66 said:
Try holding the power button for around 20 secs until it shuts down. Then try vol up and power together and see if you get back to fastboot. If that doesn't work try vol up vol down and power buttons all together. Then try again to put it in fastboot mode using vol up and power. Let us know what happens /if you can reach fastboot mode
Click to expand...
Click to collapse
Unfortunately, nothing. Holding power for 20 seconds showed nothing, and like wise for volume up and power. Battery was fully charged too. Had it plugged in for most of today while I was trying to get fastboot to work.

RichDoe252 said:
Unfortunately, nothing. Holding power for 20 seconds showed nothing, and like wise for volume up and power. Battery was fully charged too. Had it plugged in for most of today while I was trying to get fastboot to work.
Click to expand...
Click to collapse
Is there any sort of illumination to the black screen ie do you think the phone is on but the screen is black or do think the phone is completely off?
Holding power button for a while should switch it off after a while. Try holding for longer than 20 secs, then try booting into fastboot mode
---------- Post added at 04:00 AM ---------- Previous post was at 03:44 AM ----------
Well dude, it's 4 am here. Gotta get some sleep dude. Will check here when I wake. Good luck in the mean time

Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results

reg66 said:
Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results
Click to expand...
Click to collapse
Bro get to sleep! Such a good Samaritan

TikiThePug said:
Bro get to sleep! Such a good Samaritan
Click to expand...
Click to collapse
LOL! I would if I could, just can't sleep yet. Hopefully soon tho!

RichDoe252 said:
Unfortunately, nothing. Holding power for 20 seconds showed nothing, and like wise for volume up and power. Battery was fully charged too. Had it plugged in for most of today while I was trying to get fastboot to work.
Click to expand...
Click to collapse
Try a USB 2.0 port? Surprisingly this works for some phones even though it's compatible with 3.0.

reg66 said:
Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results
Click to expand...
Click to collapse
Well, It's been untouched for a day now, and it still will not react to input. No response from long hold on the power button. I will try again in the morning. Is it possible that I somehow wrote into the BIOS of the phone? Android does use a BIOS, right?

RichDoe252 said:
Well, It's been untouched for a day now, and it still will not react to input. No response from long hold on the power button. I will try again in the morning. Is it possible that I somehow wrote into the BIOS of the phone? Android does use a BIOS, right?
Click to expand...
Click to collapse
Android itself does not have a BIOS, since Android is an OS and BIOS is more similar to firmware. But yes, the phone does have firmware, and it could be that the mismatch in firmware versions (from which you tried to flash), has caused the bootloader to "not know what to do now" when trying to start the phone up.
One thing which comes with all phones with a Qualcomm chipset is something called Qualcomm Crashdump Mode. You can try to see if you can get your phone in EDL (emergency download) mode and restore the correct firmware in that way:
https://www.the***********.com/rog-phone-2-unbrick-guide (URL gets censored for some reason; it should be "the custom droid" with no spaces)
Also, if you continue to have driver issues with connecting the phone to your PC, are you able to test another PC or even a Mac if you have access to one? I find Windows can be a giant pain for getting ADB and fastboot to work properly at times.
Good luck and let us know how it goes.

reg66 said:
Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results
Click to expand...
Click to collapse
Ok, so here's where I am: I have left the phone unplugged for a long time now. Really had no effect. I just downloaded QPST and I can actually get my computer to see the phone. However, I am still not quite sure how to USE QPST and not make things worse. So this is my plan: I am going to look through the forums here for info on how to use QPST to get my phone working again. Not really sure what that will look like, but fastboot would be a good start. From there, it sounds like I have to get the original firmware back on it, and then go about the process of rooting once again.
Still leaves me with the issue that started me down the path of rooting this phone, but at least it will not longer be bricked.

RichDoe252 said:
Ok, so here's where I am: I have left the phone unplugged for a long time now. Really had no effect. I just downloaded QPST and I can actually get my computer to see the phone. However, I am still not quite sure how to USE QPST and not make things worse. So this is my plan: I am going to look through the forums here for info on how to use QPST to get my phone working again. Not really sure what that will look like, but fastboot would be a good start. From there, it sounds like I have to get the original firmware back on it, and then go about the process of rooting once again.
Still leaves me with the issue that started me down the path of rooting this phone, but at least it will not longer be bricked.
Click to expand...
Click to collapse
You may not HAVE to flash complete firmware, it is quite likely that the boot.img is causing the problem as you flashed an incompatible version. Below you'll flash the correct version which HOPEFULLY will fix your phone, provided you can get into fastboot mode now.
Haven't read back through all the thread so i can't recall all the details of where you're at. As far as i can tell you're still running WW 16.0622.1906.19-0, correct? Can you get the device to now boot into fastboot mode? (from a powered off state, press and hold vol up and power at the same time. You should then be presented with some options, DON'T select any option. With that menu screen open is fastboot mode.
1. Download and install ADB Fastboot from here to C: drive of your pc/laptop.
2. With your phone in fastboot mode (as detailed above) connect it to pc/laptop using the side port of the phone.
3. Navigate to C:\Program Files (x86)\Minimal ADB and Fastboot folder and double click the cmd-here.exe, this will open a cmd window.
4. Type 'fastboot devices' to check that it's recognised, there should be a serial/key shown after entering that cmd.
5. Provided the serial/key is shown in fastboot mode, download the following boot.img (which is for WW 1906.19) from here.
6. Copy that boot img to the same folder you have open for ADB (C:\Program Files (x86)\Minimal ADB and Fastboot)
7. In the cmd window type 'fastboot flash boot boot.img'.
Now, that boot img is the STOCK boot img for your rom version. Don't worry about rooting for now (if i recall correctly, your phone won't boot to system), let's just try to get the phone booting first. Providing there are no errors when flashing the boot img, on the phone fastboot menu, scroll through and choose 'restart'.
Let me know if the device boots to system now... Good luck
I'll pm you my email address so you'll be able to get hold of me if you get stuck at any stage...
EDIT: was forgetting you tried so many times to get into fastboot mode, without success.
---------- Post added at 08:59 PM ---------- Previous post was at 08:17 PM ----------
Dude, is your phone screen still black but switched on? When you tap the screen does it vibrate. I'm thinking you might already be in edl mode (which could be a good thing). Let us know
Check your pm's dude for further info. I can't post links to the site required so have sent via pm

TikiThePug said:
Android itself does not have a BIOS, since Android is an OS and BIOS is more similar to firmware. But yes, the phone does have firmware, and it could be that the mismatch in firmware versions (from which you tried to flash), has caused the bootloader to "not know what to do now" when trying to start the phone up.
One thing which comes with all phones with a Qualcomm chipset is something called Qualcomm Crashdump Mode. You can try to see if you can get your phone in EDL (emergency download) mode and restore the correct firmware in that way:
https://www.the***********.com/rog-phone-2-unbrick-guide (URL gets censored for some reason; it should be "the custom droid" with no spaces)
Also, if you continue to have driver issues with connecting the phone to your PC, are you able to test another PC or even a Mac if you have access to one? I find Windows can be a giant pain for getting ADB and fastboot to work properly at times.
Good luck and let us know how it goes.
Click to expand...
Click to collapse
Just dropping you a quick note to say thanks for thanks! LOL. Yeah, your post earlier seems like the best place to go. Have used Miflash Tool a few times on Xiaomi devices, it's pretty good and straight forward. Should be a LOT easier than using QPST and having to change EMMC to UFS.
Can't remember where i saw it now, but i'm sure i read that if the phone screen is black (but switched on) and vibrates, then it's likely to be in EDL mode already. Which will hopefully be good news for @RichDoe252. Before that (having never been in that situation), i wasn't aware that an all black screen could mean EDL mode is active. Fingers crossed for Rich it'll all work out just fine.
@RichDoe252 If all goes successfully using the QPST file download (and using the Miflash Tool the guide mentions in the pm i sent you) and flashing, DON'T ROOT JUST YET!!!! LOL. Let us know how it goes and then we can look into, and point you in the right direction, for getting you rooted and up to date on latest A9 or A10 whichever you'd prefer

Well I must say Rich, I'm surprised you haven't been back here yet to give any updates on progress!! Sent you a couple of emails through pm... Man, if it was my fairly expensive phone that was in the poo pan, I'd be all over trying to fix it lol

reg66 said:
Well I must say Rich, I'm surprised you haven't been back here yet to give any updates on progress!! Sent you a couple of emails through pm... Man, if it was my fairly expensive phone that was in the poo pan, I'd be all over trying to fix it lol
Click to expand...
Click to collapse
First off, you are a freaking saint. I really do appreciate all the help you have been offering up, and I am sorry I have not been very quick with a response. As my phone currently stands, I get 0% response from anything I do to it. No vibrate, nothing. No indication it even is plugged in. I had it connected to my PC with QPST installed, and it was able to pick up that the phone was there, and then immediately tried to download something to it. Not sure what, not sure why, but that kinda typifiies my interaction with this whole process so far. If you haven't guessed, I'm kinda in over my head.
Back to the problem: QPST started some opperation to download something to it. Wouldn't let me do anything else, said the phone was in "download mode". Either way it stopped at 30% and didn't progress for 30 minutes, so I tried to unplug it and plug it back in. Same interaction. Unable to do anything to the phone, no reaction from the phone what so ever. This was, by the way, plugged into the fastboot side port.
I saw that you PM'ed me, and now I can't find the email notification or the PMs on the site. Forgive me for being unfortunately new at this. I will get back to you bud, and thank you again.

Htc One m7 display not turning on

My device turns on but the display doesn't (I'm pretty sure the display isn't damaged since the display turned on twice after this problem started)
I need HELP urgently since that is the only phone I've got
Device details:
it runs on Lineage OS 17.1
Rooted (Magisk)
Twrp installed
I've tried entering recovery mode but it doesn't work
Tried recallibrating the battery but that doesn't work either
The phone turns on and I can see it in adb devices when connected to PC
I also tried to reset the device using adb but I guess I've disabled Root access over adb (in developer options)

try rebooting to recovery from adb

kouseralamin said:
try rebooting to recovery from adb
Click to expand...
Click to collapse
*thank you for replying*
tried doing so.. the phone boots into twrp recovery mode but the display doesn't turn on

Usmaan66 said:
tried doing so.. the phone boots into twrp recovery mode but the display doesn't turn on
Click to expand...
Click to collapse
And what happens when you start the bootloader mode (Fastboot) via ADB or press and hold the power button and volume down ?

Usmaan66 said:
*thank you for replying*
tried doing so.. the phone boots into twrp recovery mode but the display doesn't turn on
Click to expand...
Click to collapse
How can you know that the phone boots into twrp recovery mode if the the screen doesn't turn on?
In addition, if you can share a photo of your phone screen while in TWRP or in fastboot or anything that shows on the screen; that would be easier for me to understand the situation.

kouseralamin said:
How can you know that the phone boots into twrp recovery mode if the the screen doesn't turn on?
In addition, if you can share a photo of your phone screen while in TWRP or in fastboot or anything that shows on the screen; that would be easier for me to understand the situation.
Click to expand...
Click to collapse
i got to know that it is in recovery mode by typing adb devcies in cmd and it shows my device id and it shows 'recovery' beside the id
and now the device isn't entering recovery mode by this command 'adb reboot recovery'

kouseralamin said:
How can you know that the phone boots into twrp recovery mode if the the screen doesn't turn on?
In addition, if you can share a photo of your phone screen while in TWRP or in fastboot or anything that shows on the screen; that would be easier for me to understand the situation.
Click to expand...
Click to collapse
I'm sorry i cant click the picture since i dont have any other phone
(I'm replying through my PC and it doesn't have a webcam)

FBK2904 said:
And what happens when you start the bootloader mode (Fastboot) via ADB or press and hold the power button and volume down ?
Click to expand...
Click to collapse
it enters fastboot mode but there isnt any change in the display

Usmaan66 said:
it enters fastboot mode but there isnt any change in the display
Click to expand...
Click to collapse
Bad for you ... I think your HTC-One-M7 display is in Android heaven now:crying::angel:
3 options:
- change display (if that was it).
- Buy a new HTC-One-M7 (the cheeper way).
- Buy a different mobile phone model (if you want).
Greetz,
Frank

Usmaan66 said:
it enters fastboot mode but there isnt any change in the display
Click to expand...
Click to collapse
Seems a hardware issue.

Drop it from the height of approximately 34000 meters like You're on K2.
Then land on the earth again. In case if you find your phone again it will be like a box pack brand new.

Screen
Hi! I have the same problem sometimes: phone boots, but touchscreen doesn`t work. Same: Lineage 17.1 + magisk canary + TWRP. No GAPPs.
For solve it I doing next: immediately after boot when bootanimation finished - unlock the phone.
After this touchscreen keep working.

Fastboot - waiting for any device

I'm a newbie at this but managed to stumble through installing CM 14.1 on my LG G2.
Phone: LG G2 VS980
CyanogenMod version: 14.1-20161207-unofficial-phoenix-vs980
Kernel version 3.4.0-crdroid-g0f70b4b
TWRP v2.8.6.3 (I don't know how this version got installed, I started out with a 2.7 version and upgraded to a later version but this is the version I see after I got CM installed).
Latest version of ADB and Fastboot from the platform-tools download.
I'm trying to make the phone automatically turn on when plugged into a charger using the " fastboot oem off-mode-charge 0" command .
ADB commands work fine.
If I issue the command "adb reboot bootloader" when the device is booted in CM I get rebooted into a black screen with the following:
"Firmware Update Do not unplug the USB connection until the process is complete." There is a progress bar that remains at 0%.
Any fastboot command I issue returns "waiting for any device". I have to hold down the phone power button for several seconds to exit this screen and then the phone reboots normally.
If I issue the "adb reboot bootloader" command when the phone is in TWRP or I select Reboot - Bootloader from TWRP the phone just reboots into CM.
What am I doing wrong?
Thanks

I'm not too familiar with this phone, but all that I know is that it is in download mode, which is not the same as a bootloader. As a lot of android phones aren't the same as each other, I am not aware of how to boot into a bootloader of this phone.
I will say though, if it is anything like a Samsung phone, then it probably does not have a bootloader and the only way to interface with this mode is through the LG Flash tool found here: https://lgflash.com/LGUP/
Don't take my word for it, but it is possible that this is the case. Again, I don't have any idea how the phone works or anything, but this is possibly the solution.

NTGDeveloper said:
I'm not too familiar with this phone, but all that I know is that it is in download mode, which is not the same as a bootloader. As a lot of android phones aren't the same as each other, I am not aware of how to boot into a bootloader of this phone.
I will say though, if it is anything like a Samsung phone, then it probably does not have a bootloader and the only way to interface with this mode is through the LG Flash tool found here: https://lgflash.com/LGUP/
Don't take my word for it, but it is possible that this is the case. Again, I don't have any idea how the phone works or anything, but this is possibly the solution.
Click to expand...
Click to collapse
I believe I'm in download mode when I'm seeing the black Firmware Update screen. I'm not trying to flash a ROM at this point so I don't think the LGUP program will be helpful.
If there is a another way to get my phone to turn on when power is applied to the USB cord I'm open to it.

RKCRLR said:
If there is a another way to get my phone to turn on when power is applied to the USB cord I'm open to it.
Click to expand...
Click to collapse
Perhaps by modifying whatever starts when it's charging.
Charging animation for example...

The meaning and purpose of Download mode, Bootloader mode and Fastboot mode are same.

Any fastboot command I issue returns "waiting for any device".
Click to expand...
Click to collapse
1st thing of all things in order to run Fastboot commands is you have to run command
Code:
fastboot devices
what establishes the USB connection. As long as the connection isn't established Fastboot throws message "waiting for any device".
BTW:
Booting into device's bootloader ( FYI: each device has a bootloader ) requires in addition to the well-known Fastboot driver the Android USB Driver got installed, too. This driver is OEM ( brand/model ) specific, you have it to obtain from OEM - mostly offered on their website.

jwoegerbauer said:
The meaning and purpose of Download mode, Bootloader mode and Fastboot mode are same.
Click to expand...
Click to collapse
Not the same really - and LGs aren't Samsungs, or whatever either...
One maybe could try emptying LAF partition ("nuking"). Some more drastic ways also suggest it for boot as well. But IDK, is it worth the trouble really? And even if one could get into the fastboot, that command might not work after all...

jwoegerbauer said:
The meaning and purpose of Download mode, Bootloader mode and Fastboot mode are same.
Click to expand...
Click to collapse
The way I get into download mode is to hold the volume up button and plug in the USB cable with the phone off. When I do this I briefly see a screen that says Download with a blue hashmarked bar below it. It then goes to a screen that says "Firmware Update Do not unplug the USB connection until the process is complete." with zero percent progress.
Should I be able to issue fastboot commands when the phone is at that screen?

RKCRLR said:
Should I be able to issue fastboot commands when the phone is at that screen?
Click to expand...
Click to collapse
Nope.

CXZa said:
Not the same really - and LGs aren't Samsungs, or whatever either...
One maybe could try emptying LAF partition ("nuking"). Some more drastic ways also suggest it for boot as well. But IDK, is it worth the trouble really? And even if one could get into the fastboot, that command might not work after all...
Click to expand...
Click to collapse
I'm trying to repurpose the phone as a dedicated Android Auto "server" and would like to be able to leave it connected to my car. It would be really useful to have the phone turn off when there is no USB poser and turn on when there is USB power.
If I make a backup of the Boot and System partitions within TWRP would that allow me to restore my LAF if I nuke the LAF and something goes awry?

RKCRLR said:
to have the phone turn off
If I make a backup of the Boot and System partitions within TWRP would that allow me to restore my LAF if I nuke the LAF and something goes awry?
Click to expand...
Click to collapse
>to have the phone turn off
Could it be there some app for such? IDK, maybe...
>If I make a backup
Nope again, The LAF has a partition of it's own. To backup use lglaf.py or LGUP having the dump option enabled or extract it from kdz if available.

CXZa said:
>to have the phone turn off
Could it be there some app for such? IDK, maybe...
>If I make a backup
Nope again, The LAF has a partition of it's own. To backup use lglaf.py or LGUP having the dump option enabled or extract it from kdz if available.
Click to expand...
Click to collapse
This is probably a bridge too far for my skill level.
Is there a work around like putting it into a deep sleep that will let the battery to last for days or weeks but wake up when the USB has power?

RKCRLR said:
This is probably a bridge too far for my skill level.
Is there a work around like putting it into a deep sleep that will let the battery to last for days or weeks but wake up when the USB has power?
Click to expand...
Click to collapse
There's probably a way to do this via root and there will probably be some app that lets you do this. Other than that, you'll have to dig around and see what you can find.

Thread cleaned and moved to Verizon LG G2 section