Related
My HTC One M8 (Verizon) is seemingly bricked. My phone is rooted, S-Off, with the stock ROM. I have been trying to update to the latest OTA update by returning to stock. I had previously modified some entries in the Build.prop and Platform.xml. I knew those had to be default in order for the OTA to work. I had copied the original files and pasted them to my SD Card so that I could simply cut the modified versions, paste them to my SD Card, and cut the originals from my SD Card and put them in their corresponding system folders.
Upon a reboot something apparently went horribly wrong because all my phone does now is boot with the white screen and green HTC Logo, then the screen goes black. I have tried the typical Power Button + Volume Down but it won't enter the boot loader. The good news is that the USB port seems to still work for my windows computer recognizes a device connecting to it but it doesn't show up as an interactive device in windows explorer..if that makes sense.
Please Help!
SF-Echo18 said:
My HTC One M8 (Verizon) is seemingly bricked. My phone is rooted, S-Off, with the stock ROM. I have been trying to update to the latest OTA update by returning to stock. I had previously modified some entries in the Build.prop and Platform.xml. I knew those had to be default in order for the OTA to work. I had copied the original files and pasted them to my SD Card so that I could simply cut the modified versions, paste them to my SD Card, and cut the originals from my SD Card and put them in their corresponding system folders.
Upon a reboot something apparently went horribly wrong because all my phone does now is boot with the white screen and green HTC Logo, then the screen goes black. I have tried the typical Power Button + Volume Down but it won't enter the boot loader. The good news is that the USB port seems to still work for my windows computer recognizes a device connecting to it but it doesn't show up as an interactive device in windows explorer..if that makes sense.
Please Help!
Click to expand...
Click to collapse
When you connect it to the PC can you pick up the device with adb? If so, have you tried to run the command from adb to boot it into bootloader? adb devices ... if found, adb reboot bootloader
:fingers-crossed:
BerndM14 said:
When you connect it to the PC can you pick up the device with adb? If so, have you tried to run the command from adb to boot it into bootloader? adb devices ... if found, adb reboot bootloader
:fingers-crossed:
Click to expand...
Click to collapse
I'm not too familiar with ADB commands but I typed in "adb reboot recovery" and it said: "error: device not found" so even if my command was wrong it's still not detecting it. I also tried: "fastboot reboot bootloader" and it just says "waiting for device"
Also I feel like it's worth mentioning the phone is automatically rebooting every two minutes or so (haven't timed it exactly but it's a while). Still showing the green HTC Logo then the screen goes dim, then the screen turns off.
SF-Echo18 said:
I'm not too familiar with ADB commands but I typed in "adb reboot recovery" and it said: "error: device not found" so even if my command was wrong it's still not detecting it. I also tried: "fastboot reboot bootloader" and it just says "waiting on device for device"
Also I feel like it's worth mentioning the phone is automatically rebooting every two minutes or so (haven't timed it exactly but it's a while). Still showing the green HTC Logo then the screen goes dim, then the screen turns off.
Click to expand...
Click to collapse
Try holding volume UP + Power button, this simulates a "battery pull", just hold it in for a while it can take a while to "pull", when it's off try again booting into bootloader, volume DOWN + Power button.
BerndM14 said:
Try holding volume UP + Power button, this simulates a "battery pull", just hold it in for a while it can take a while to "pull", when it's off try again booting into bootloader, volume DOWN + Power button.
Click to expand...
Click to collapse
I held Volume Up + Power Button and it showed the white screen with the green HTC logo. I then released all buttons. Once the screen turned off I then held Volume Down + Power Button for two minutes straight and nothing happened.
Even though we haven't found a solution yet, I am appreciative of the help.
sounds like you never installed the htc drivers for your phone, hence your pc doesn't see the phone when you are doing ADB commands.
install the drivers for it, then try the ADB commands via your pc
and dont mess with the build prop or other system files unless you have a working back up and are 101% certain about what you are doing..
Just remember to change directory in command prompt to the folder where adb.exe is located.
I don't know why the device doesn't reboot into bootloader though when you hold volume down + power button, shouldn't have to hold it for 2minutes. Holding volume up + power button to simulate a "pull" should only take up to 20 seconds or so at most and pressing volume down + power will then immediately take you into bootloader mode, or at least it's supposed to.
Did you release the volume up / power combo when the screen went dead or before? Try holding it until the phone shuts off and then right away press volume down + power.
Sorry if I'm not answering right away though, busy eating, and will be here and away for the next hour or so while I get ready for work =o( once I leave for work I'll only be able to help some more after like 2 hours or so. Hopefully we can do something before then though =o)
wase4711 said:
sounds like you never installed the htc drivers for your phone, hence your pc doesn't see the phone when you are doing ADB commands.
install the drivers for it, then try the ADB commands via your pc
and dont mess with the build prop or other system files unless you have a working back up and are 101% certain about what you are doing..
Click to expand...
Click to collapse
You're right, I didn't install the drivers. I did so and ADB was able to recognize it and I was able to access the bootloader. Thank you everyone for your help. I won't be making the mistake again.
SF-Echo18 said:
You're right, I didn't install the drivers. I did so and ADB was able to recognize it and I was able to access the bootloader. Thank you everyone for your help. I won't be making the mistake again.
Click to expand...
Click to collapse
So you'll be able to fix it from here on then? I was just about to link this thread to you as well should you have gotten adb to work again, it's for the RUU for Verizon seeing as you said you're on Verizon.
But going by your response up there you might already know how to fix this issue further :good:
BerndM14 said:
So you'll be able to fix it from here on then? I was just about to link this thread to you as well should you have gotten adb to work again, it's for the RUU for Verizon seeing as you said you're on Verizon.
But going by your response up there you might already know how to fix this issue further :good:
Click to expand...
Click to collapse
Indeed I appreciate it, but I just finished installing the RUU ha. Hopefully this thread will be of use to someone in a similar circumstance in the future.
Share another method of getting into recovery mode on non-responsive blank screen
Hi,
I just want to share how I accessed recovery mode with the same build.prop issue but with S-ON (might work with S-Off too).
I found the solution from here:
http://forum.xda-developers.com/htc...ter-download-mode-t2853100/page2#post62490577
To get into recovery mode on a non-responsive blank screen, hold the power button and volume up button at the same time and then approximately after 10 seconds, switch from pressing the volume up to volume down button before the HTC logo white screen shows while still holding down the power button. After, a white boot screen will give an option to go into recovery mode.
I have just flash the custom 5.0.2 ROM using philz touch 6.48.4.
After I flashed the ROM, I reboot to the philz recovery and flashed back to cwm 6.0.4.8.
However, the device stuck on the LG logo screen.
I have try to enter Download mode/Emergence mode/Hard reset mode/Recovery, but all of them I cannot go into.
Please help! Thank you for your helping!!
pchuen said:
I have just flash the custom 5.0.2 ROM using philz touch 6.48.4.
After I flashed the ROM, I reboot to the philz recovery and flashed back to cwm 6.0.4.8.
However, the device stuck on the LG logo screen.
I have try to enter Download mode/Emergence mode/Hard reset mode/Recovery, but all of them I cannot go into.
Please help! Thank you for your helping!!
Click to expand...
Click to collapse
Your boot loader is broken. Gonna have to get to the down load mode and reinstall either the or the stock. You can probably flash the recovery with .IMG file with lg flashing tool. Nerdy blond's twrp is one of those files that you can use. You can even try installing it first with the adb shell command, you can get the instructions at the same place where you download.
http://forum.xda-developers.com/showthread.php?t=3144369
hawkwind212 said:
Your boot loader is broken. Gonna have to get to the down load mode and reinstall either the or the stock. You can probably flash the recovery with .IMG file with lg flashing tool. Nerdy blond's twrp is one of those files that you can use. You can even try installing it first with the adb shell command, you can get the instructions at the same place where you download.
http://forum.xda-developers.com/showthread.php?t=3144369
Click to expand...
Click to collapse
Thank you for replying.
I cannot do anythings since I cannot enter into download mode.
I pressed volume key + and - and insert the usb cable to computer. There is nothing happened, computer dose not show the devices attached and the phone stay in the LG logo screen.
Also, I cannot use adb commands to force the phone enters into download mode as it shows nothings under "List of devices".
Is there any methods I can go into the download mode???
Thank you!
pchuen said:
Thank you for replying.
I cannot do anythings since I cannot enter into download mode.
I pressed volume key + and - and insert the usb cable to computer. There is nothing happened, computer dose not show the devices attached and the phone stay in the LG logo screen.
Also, I cannot use adb commands to force the phone enters into download mode as it shows nothings under "List of devices".
Is there any methods I can go into the download mode???
Thank you!
Click to expand...
Click to collapse
If your phone shows LG start screen, it should go into Download mode. I had similar problem few days ago while I was testing some kernel patches, it just froze on the LG screen. Solution was to unplug it, remove it's battery, SIM & SD (you don't have to remove SIM & SD, I just work that way) , make sure it's off, return battery back, press Vol + & Vol - at the same time and plug-in the USB cable.
Before that, make sure you have installed LG Unified driver (can be obtained via LG's software from support site), because without that Windows won't recognise your device.
After that, once you make your phone usable with Freegee/whatever you use to install initial recovery, flash official TWRP, because others are too old - that Philz CWM is old but still working with Lollipop but not work good and is tends to lock itself into a bootloop if you use hardware keys to enter; that other one, from GPRO_recovery APK is not supported and not working well (for me since day one), so it should be replaced as soon as possible.
Also, I can suggest you to flash your phone from stock 4.1 (not KitKat), root, flash recovery via freegee and after reboot update to latest official TWRP via Flashify.
hawkwind212 said:
Your boot loader is broken. Gonna have to get to the down load mode and reinstall either the or the stock. You can probably flash the recovery with .IMG file with lg flashing tool. Nerdy blond's twrp is one of those files that you can use. You can even try installing it first with the adb shell command, you can get the instructions at the same place where you download.
http://forum.xda-developers.com/showthread.php?t=3144369
Click to expand...
Click to collapse
ShadySquirrel said:
If your phone shows LG start screen, it should go into Download mode. I had similar problem few days ago while I was testing some kernel patches, it just froze on the LG screen. Solution was to unplug it, remove it's battery, SIM & SD (you don't have to remove SIM & SD, I just work that way) , make sure it's off, return battery back, press Vol + & Vol - at the same time and plug-in the USB cable.
Before that, make sure you have installed LG Unified driver (can be obtained via LG's software from support site), because without that Windows won't recognise your device.
After that, once you make your phone usable with Freegee/whatever you use to install initial recovery, flash official TWRP, because others are too old - that Philz CWM is old but still working with Lollipop but not work good and is tends to lock itself into a bootloop if you use hardware keys to enter; that other one, from GPRO_recovery APK is not supported and not working well (for me since day one), so it should be replaced as soon as possible.
Also, I can suggest you to flash your phone from stock 4.1 (not KitKat), root, flash recovery via freegee and after reboot update to latest official TWRP via Flashify.
Click to expand...
Click to collapse
Thank you for your detail reply.
I have tried to reinstall the LG driver and try to enter download mode again.
The screen is still stuck on LG logo and I cannot find the device in hardware manager (cannot recognize it).
I cannot do anythings until it can recognize it.
(Is it the bootloader is broken? and can I fix it?)
Thank you very much and waiting for your reply soon.:good:
pchuen said:
Thank you for your detail reply.
I have tried to reinstall the LG driver and try to enter download mode again.
The screen is still stuck on LG logo and I cannot find the device in hardware manager (cannot recognize it).
I cannot do anythings until it can recognize it.
(Is it the bootloader is broken? and can I fix it?)
Thank you very much and waiting for your reply soon.:good:
Click to expand...
Click to collapse
Which version of Windows are you using? It should be displayed under Serial ports in Device manager (named something like LGE Serial device) and LGFlashTool should recognise it immediately. I can't make you a screenshot/check for real name because I'm running Linux right now and can't reboot.
Also, try with another cable/port, remove all other android drivers you may have (Samsung's, Google's...) and disable antivirus.
ShadySquirrel said:
Which version of Windows are you using? It should be displayed under Serial ports in Device manager (named something like LGE Serial device) and LGFlashTool should recognise it immediately. I can't make you a screenshot/check for real name because I'm running Linux right now and can't reboot.
Also, try with another cable/port, remove all other android drivers you may have (Samsung's, Google's...) and disable antivirus.
Click to expand...
Click to collapse
It does not work on Windows 7 and XP.
I did not find any LGE XXX under Serial ports part.
Thank you!
pchuen said:
It does not work on Windows 7 and XP.
I did not find any LGE XXX under Serial ports part.
Thank you!
Click to expand...
Click to collapse
Hm.... Phone shows that it have entered download mode? Black screen, centered gray message and "DOWNLOAD MODE" red text?
ShadySquirrel said:
Hm.... Phone shows that it have entered download mode? Black screen, centered gray message and "DOWNLOAD MODE" red text?
Click to expand...
Click to collapse
No... nothing happens, just showing LG logo...
pchuen said:
No... nothing happens, just showing LG logo...
Click to expand...
Click to collapse
OK, it doesn't enter download mode. So, step by step:
- remove battery and leave it for 15-30 seconds, return battery
- press Vol+ and Vol- at the same time and keep them pressed,
- plug USB cable in while keys are pressed
It should immediately put you into download mode, with no LG screen, just black screen with gray box and red text I've described to you.
ShadySquirrel said:
OK, it doesn't enter download mode. So, step by step:
- remove battery and leave it for 15-30 seconds,
- press Vol+ and Vol- at the same time and keep them pressed,
- plug USB cable in while keys are pressed
It should immediately put you into download mode, with no LG screen, just black screen with gray box and red text I've described to you.
Click to expand...
Click to collapse
I understand what download mode screen is.
I followed your methods, bur I still cannot enter it and the computer cannot recognize that.
Sorry for disturbing :crying:
pchuen said:
I understand what download mode screen is.
I followed your methods, bur I still cannot enter it and the computer cannot recognize that.
Sorry for disturbing :crying:
Click to expand...
Click to collapse
So, whatever you try to do, phone just shows LG logo, not even a message in an upper left corner?
I'm running out of ideas. I have exact same variant (E988) but only time it didn't want to enter download mode this way was when cable I was using was broken...
ShadySquirrel said:
So, whatever you try to do, phone just shows LG logo, not even a message in an upper left corner?
I'm running out of ideas. I have exact same variant (E988) but only time it didn't want to enter download mode this way was when cable I was using was broken...
Click to expand...
Click to collapse
I have changed the cable, but it is the same.
Quick background on situation.
I was running CM13 and I still have TWRP 3.0.2-0. I wanted to try out CM14 or some other variant. I went into TWRP Recovery Mode and Advanced WIPED everything except the Internal Storage and MicroSD (this is probably where I messed up?)
Then went to install and navigate to the new rom and gapps on my microsd card. Well TWRP does not see either. It lists both of them but with 0MB and unselectable. I tried two other card, no go (all FAT32). Tried OTG with 3 different thumb drives, same results. The OS is gone and all I get of course is the white ASUS boot screen loop. ADB doesn't see any devices as well (windows device manager see no new devices when I attached the cable or when I list devices).
The only thing I can boot into is TWRP and I have tried everything to access the SD/OTG without success.
So can I assume I have bricked this thing and must go onto the IntelSOC XFStik procedure? and if so, does having a working TWRP on there force me to deviate from the normal unbrick procedure I have see here and on youtube?
Or is it something really easy that I am missing? I am fairly novice (as noted by my current situation), so maybe it's an easy fix?
Any help is appreciated. Thanks.
@Endosmok
You have LP version twrp recovery? , not the mmbl twrp recovery installed ? which ends in 3.0.2.M1 ??
If you do have 3.0.2.0 for LP bootloader which early versions of CM13 used , then you can fastboot flash stock recovery for 4 20 40 196 in bootloader from here....
https://mega.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Thanks go to Shakalaca
To get into bootloader -- from Twrp , select reboot , select power off !
Count to ten after switching off.
Press power and vol + , release power when it vibes , release vol+ at asus screen.
Fastboot flash stock recovery for above LP .196 in bootloader , when flashed --- scroll via vol buttons to recovery and hit power. At the dead android , press power and vol+ together for 4 secs , release vol+
You should be in stock recovery now.
Scroll to `update over adb` and select .
adb sideload LP official firmware from asus for LP .196 or .198
If you need help to get thru this step , just ask:good:
Thanks for the response. I am not sure if I have the LP version. It was done back I think in April of last year... I looked around TWRP and I don't see anything except 3.0.2-0 listed.
So still a little confused. This is how i have been navigating so far....
Power button, volume up... I get to the dead robot. There I can see FASTBOOT MODE is in Red, product name, variant, IFWI, Serial #. The rest is either ? or unknown (bootloader version is unknown).
Then at the bottom i can see 'continue the fastboot process' in blue. With the volume rocker i can select, NORMAL BOOT, POWER OFF, RECOVERY MODE and RESTART BOOTLOADER. I have been select Recovery Mode to get into TWRP. Restart Bootloader gets me back to the dead robot. I would assume this is the bootloader. Normal Boot just gives me the white asus splash where it hangs. In TWRP i can see ADVANCED -> ADB Sideload, I can start and it shows starting adb sideload feature with the blue color scrolling. But still when I connect to the computer I get no connection and nothing is listed when i run adb devices.
My TWRP doesn't let me select either the OTG or MicroSD, they show 0MB but are listed. So no way for me to flash via TWRP. I figured if i can get the computer adb to recognize the phone I can try to sideload via there. But so far my device manager doesn't see a thing, not even an unknown device waiting for their proper drivers.
Where am i going wrong?
Endosmok said:
Thanks for the response. I am not sure if I have the LP version. It was done back I think in April of last year... I looked around TWRP and I don't see anything except 3.0.2-0 listed.
So still a little confused. This is how i have been navigating so far....
Power button, volume up... I get to the dead robot. There I can see FASTBOOT MODE is in Red, product name, variant, IFWI, Serial #. The rest is either ? or unknown (bootloader version is unknown).
Then at the bottom i can see 'continue the fastboot process' in blue. With the volume rocker i can select, NORMAL BOOT, POWER OFF, RECOVERY MODE and RESTART BOOTLOADER. I have been select Recovery Mode to get into TWRP. Restart Bootloader gets me back to the dead robot. I would assume this is the bootloader. Normal Boot just gives me the white asus splash where it hangs. In TWRP i can see ADVANCED -> ADB Sideload, I can start and it shows starting adb sideload feature with the blue color scrolling. But still when I connect to the computer I get no connection and nothing is listed when i run adb devices.
My TWRP doesn't let me select either the OTG or MicroSD, they show 0MB but are listed. So no way for me to flash via TWRP. I figured if i can get the computer adb to recognize the phone I can try to sideload via there. But so far my device manager doesn't see a thing, not even an unknown device waiting for their proper drivers.
Where am i going wrong?
Click to expand...
Click to collapse
You have LP bootloader .
Type in bootloader >
fastboot devices
If recognised, fastboot flash , follow my first reply above , adb wont be recognised until stock recovery is flashed and selected.
Please try to follow what as been already advised
It is V important to follow this from above , dont miss this step ;-
To get into bootloader -- from Twrp , select reboot , select power off !
timbernot said:
You have LP bootloader .
Type in bootloader >
fastboot devices
If recognised, fastboot flash , follow my first reply above , adb wont be recognised until stock recovery is flashed and selected.
Please try to follow what as been already advised
It is V important to follow this from above , dont miss this step ;-
To get into bootloader -- from Twrp , select reboot , select power off !
Click to expand...
Click to collapse
Ok... let me get this straight.... before I sound too dumb...
You want me to go into the bootloader from TWRP (using Reboot > Power Off), even though I get to TWRP via the bootloader (recovery mode) from a power on?
Also, how do I know if fastboot is enabled? Is it when I see FASTBOOT MODE in the color red on the bootloader screen with 'continue the fastboot process' at the bottom?
I've done step by step what you wrote and I get to the bootloader but fastboot devices shows nothing (I've tried different computers/cables as well). I have the computer connect to the phone w/ bootloader screen on with what i wrote about FASTBOOT MODE in red and contine the fastboot process. If that is not correct, let me know. I did hold down the Volume Up for a bit longer
I'm almost thinking I have a hardware issue with my phone. I did replace the mic with a new module prior. I never checked if the usb storage was functioning after. Though it charges via the usb (even connected to a computer it charges but not recognized as a device). I'll have to double check that as well.... not sure why the sd card is not recognized though either... never touched that area. Could be the reason why TWRP can't access either the micro sd or otg?
I do appreciate the help... and i have been reading other threads... just seem to be at a stand still for now... suggestions are always welcome.
update: tried adjust the cable on the mic module ... no dice... replaced with older mic module, no dice... don't think it's a hardware issue.
To get into fastboot mode, power off the phone. Press and hold the volume up button and press the volume button. Once the phone vibrates, let go of the power button, then the volume button. You should not be in fastboot mode. You can choose recovery, power off, etc. with the volume button when in fastboot mode.
Connect the phone to the computer. Do you see any Android devices in device manager? Do you see any unknow devices?
Did you open a command prompt window on your computer, connect the phone in fastboot mode, and type "fastboot devices" (without quotation marks) and press enter to see if the phone is recognized?
audit13 said:
To get into fastboot mode, power off the phone. Press and hold the volume up button and press the volume button. Once the phone vibrates, let go of the power button, then the volume button. You should not be in fastboot mode. You can choose recovery, power off, etc. with the volume button when in fastboot mode.
Connect the phone to the computer. Do you see any Android devices in device manager? Do you see any unknow devices?
Did you open a command prompt window on your computer, connect the phone in fastboot mode, and type "fastboot devices" (without quotation marks) and press enter to see if the phone is recognized?
Click to expand...
Click to collapse
So made some progress here. I think it was a hardware issue now... I put back the new mic module and reconnected the cable and now I can see my SD card and the computer sees it as well in adb and fastboot. That's the good news....
But ran into a new issue when trying to install any ROM from my micro sd card. I get ERROR 7 no matter what ROM I try to install. I have verified that they are the proper roms for my Z00A ZE551ML but still a no go.
What steps should I take next if I can now communicate but get error 7?
Thanks
Which recovery are you using to flash and which file are you trying to flash?
I am using TWRP 3.0.2.-0. Using the install from zip. I select any rom (Nougat Based so far I have tried). RR, Lineage, Octopus, all with the same error.
The phone is running a MM bootloader? What about MM or LP based ROMs?
I believe Timbernot said it was an LP based. I believe I installed about April last year and it was 3.0.2-0
Looks exactly like this
https://forum.xda-developers.com/zenfone-2-laser/development/recovery-twrp-3-0-0-0-recovery-t3319704
You probably need an MM bootloader for custom Nougat ROMs. Did you try any LP-based ROMs?
I have not tried any LP based yet. I will try in a bit and forward the results.
Thanks
Post removed. Let's keep things respectful here folks. :good:
And remember, to each their own.
Cheers,
Darth
Senior Moderator
I restored an lineage os update last night, then i restored a BOOT update that didnt belong to that rom and i`m in bootloop unable to enter recovery or enter bootload, my phone responds only to power button+ volume up ( it restarts), tried to connect fastboot and i get that device isnt found( its connected to usb ports, i installed htc sync manager for htc drivers)
What can i do to go into bootloader, because if i get there i flash twrp then restore the correct rom, but now its just bootloops in RR remix( it doesnt restart itself just loading loading )
Can i get some help with right drivers or something that i could use that command" adb reboot bootloader" and it wont answer with device not found
P.S I get the device in device manager but in adb just says "device not found"
P.S2 Close the thread, i let the phone fully discharge then Volume down + power and it entered fastboot and i was able to get to recovery, nvm
Callliope said:
my phone responds only to power button+ volume up ( it restarts)
Click to expand...
Click to collapse
I know you fixed the problem, but for future reference, in the above scenario, as long as you can force a reboot (power+vol up); the moment the screen goes black to reboot, just slide your finger to vol down (no need to hold power button any longer) and keep holding it; and the phone will go to bootloader.
Callliope said:
Can i get some help with right drivers or something that i could use that command" adb reboot bootloader" and it wont answer with device not found
P.S I get the device in device manager but in adb just says "device not found"
Click to expand...
Click to collapse
adb would never have worked in the condition your phone was in. The phone needs to be booted to OS or custom recovery for adb to work.
So my Note 10+ screen broke so that I can only see the top 15% and only touch the bottom 60%. I booted into TWRP to backup everything, and now I'm in a situation where I can't turn the thing off. I am unable to press the shutdown button, only the download mode and recovery mode buttons. I am also unable to press the ADB side load button to send a shutdown command. It will be quite some time before I am able to fix the screen, so I don't want the phone battery to be sitting dead and degrading for a month or more. I already tried draining the battery and then plugging it in to charge, but the phone automatically booted into TWRP.... hardware key combos only reboot, they won't shut down...
Does anybody have an idea how to power off my device? Or to reboot into system or gain ADB access without being able to use the touchscreen? Thanks for the help
TWRP should allow you to use adb commands already.
You can use fastboot continue
XDHx86 said:
TWRP should allow you to use adb commands already.
You can use fastboot continue
Click to expand...
Click to collapse
I am trying to use adb from another Android device to the broken device using an otg cable, but the ADB otg app does not recognize it. From my memory, when I had tried to use adb in TWRP I always had to go into advanced and press the ADB side load button, but maybe this is different with fastboot? Unfortunately I do not have access to a computer right now, or a mouse for that matter.
AllanRSS said:
I am trying to use adb from another Android device to the broken device using an otg cable, but the ADB otg app does not recognize it. From my memory, when I had tried to use adb in TWRP I always had to go into advanced and press the ADB side load button, but maybe this is different with fastboot? Unfortunately I do not have access to a computer right now, or a mouse for that matter.
Click to expand...
Click to collapse
What are you trying to do exactly?
A bit convoluted but ...
Volume down + Power - forced reboot, right after vibration with USB cable on switch to Volume Up + Power . maybe boot to recovery !?
Odin - Set get system Info on - force reboot ?
Bomn said:
A bit convoluted but ...
Volume down + Power - forced reboot, right after vibration with USB cable on switch to Volume Up + Power . maybe boot to recovery !?
Odin - Set get system Info on - force reboot ?
Click to expand...
Click to collapse
Thanks for the recommendation, but the problem is that I am stuck in recovery mode. I am able to boot into recovery and download modes, but not into the normal system mode. If I could boot into system mode I should be able to use the lower half of the screen to shutdown the device, or use adb.
AllanRSS said:
Thanks for the recommendation, but the problem is that I am stuck in recovery mode. I am able to boot into recovery and download modes, but not into the normal system mode. If I could boot into system mode I should be able to use the lower half of the screen to shutdown the device, or use adb.
Click to expand...
Click to collapse
Yes, I understood that, last opcional on recovery is shutdown?
Just press up and then power?
Bomn said:
Yes, I understood that, last opcional on recovery is shutdown?
Just press up and then power?
Click to expand...
Click to collapse
Unless you can't boot to the default recovery? That's why I suggested Odin.