Hello everyone, I got a problem again with my Robin, when I try to turn on the phone I do it with my charger since my power button and volume buttons are smashed, now since I cant use my power button I cant start the phone, and after a while it boots me intro TWRP, so my question is Is there a way to turn on my Robin without my power button on TWRP?
Your help is very aprecciated. :fingers-crossed:
I would think mounting it to a pc and issuing a reboot command would work. I never thought TWRP loaded automatically though.
philhachey said:
I would think mounting it to a pc and issuing a reboot command would work. I never thought TWRP loaded automatically though.
Click to expand...
Click to collapse
I already did that, and it didn't work :crying: it goes to fastboot mode, I cant choose anything and just stays in fastboot for a while then it goes back to TWRP.
Maybe your smashed buttons are getting pressed at boot simulating the fastboot and/or recovery.
Related
I apologize in advance if this a repeat post, I couldn't find any answers and only found one similar thread to this that was still not exactly my problem.
I have an unrevoked evo running 2.2 and I know at one point I was able to fastboot (it's been awhile since I've done anything). While trying tonight to flash a custom boot image, it simply vibrated 3 times and stayed black. The charging light (as it was connected to USB) turned off and my phone wouldn't turn back on normally until I took the battery out and put it back in. I tried this repeatedly with/without USB debugging on, without USB being plugged in and got the same response every time - 3 vibrations, black screen, and inability to turn back on until the battery is removed. When I press vol down + power though I am able to boot into recovery mode just fine. Vol up + power fastboot seems to be my only problem.
Any ideas as to why I can't fastboot but I can access recovery mode?
Thanks!
Volume up and power was removed with the froyo update. Just use vol down and power to get to bootloader and from there select fastboot. What boot.img are you trying to flash exactly? It sounds like you may be doing something wrong with flashing though fastboot or soething. Unless you are trying to use eng commands?
dkdude36 said:
Volume up and power was removed with the froyo update. Just use vol down and power to get to bootloader and from there select fastboot. What boot.img are you trying to flash exactly? It sounds like you may be doing something wrong with flashing though fastboot or soething. Unless you are trying to use eng commands?
Click to expand...
Click to collapse
LOL well I feel dumb. Didn't know this was changed. While that did help me get into fastboot now I'm getting an error "FAILED: remote not allowed" but that's another problem that I do see a few threads on so I guess this can be closed.
Thanks!
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.
yesterday i unlocked the bootloader, and used ADB and FASTBOOT to flash TWRP 3.0.2 and then rooted by flashing superSU v2.76
the phone was still S-on
i attempted to modify the buildprop file and used TWRP to mount system and copy the file over to /system/
i did have other things ticked as being mounted, like /data and one other partition that escapes me now.
anyway, i copied the buildprop back and used CHMOD755 but thought choosing 644 would be better so i choose CHMOD but entered 0644 as it was asking for 4 characters. after hitting boot system the phone just went black, trying to boot into bootloader mode now doesn't work, nothing happens. the only way i get any sign of life out of the phone now is by holding volume up and power. then the phone will boot for about 5 to 6 secs before going black screened again.
so i can't boot, cant enter recovery or bootloader.
usb debuggung was ticked previously but i'm not sure i even have a working rom now. ADB fails to find a device and trying
Code:
abd reboot bootloader
just brings
Code:
error: device '(null)' not found
am i totally screwed ? or is this something i can fix ???
help needed...
Connect to PC so you can hear connect/disconnect sound.
Press & hold power + volume up buttons to force reboot, once you hear the disconnect sound on PC, release both buttons and quickly press & hold volume down button. This will take you to hboot, select recovery and restore your backup or install ROM zip
ckpv5 said:
Connect to PC so you can hear connect/disconnect sound.
Press & hold power + volume up buttons to force reboot, once you hear the disconnect sound on PC, release both buttons and quickly press & hold volume down button. This will take you to hboot, select recovery and restore your backup or install ROM zip
Click to expand...
Click to collapse
connecting up to PC i don't get any "bing bong" sounds at all. if i try booting with volume up and power while connected to PC i still don't get the bing bong, quickly switching to holding volume down as you suggest doesn't stop the phone going back to black screen.
HEEEEELLLLP !!!!!
EDIT: additional info
the phone has been this way for a few hours now and twice in that time the phone has started booting up by itself (without me touching it), only to go back off again the same as every other time...
EDIT: after leaving the phone to go nuts all by itself and let the battery run down and recharging it, I was able to get back into bootloader mode and recovery to restore a backup.
I am now happily running GPe MM, and about to test out ElementalX
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.