Related
I have no clue what happened but I installed the newest Revolution HD rom and then my phone went and died and got stuck in bootloop but then I managed to get it to bootloader somehow (dont know how, it was magic I'm guessing)
I have it plugged in and it's in fastboot but I have literally no skill or anything when it comes to this stuff. I've tried for weeks to figure out what to do and tried understanding what's up but I actually feel even more confused than before.
I need somebody who's patient enough to explain to me in dot points, yes like a toddler, what to do from here step by step and how to get my htc one working again.
zackalphabet said:
I have no clue what happened but I installed the newest Revolution HD rom and then my phone went and died and got stuck in bootloop but then I managed to get it to bootloader somehow (dont know how, it was magic I'm guessing)
I have it plugged in and it's in fastboot but I have literally no skill or anything when it comes to this stuff. I've tried for weeks to figure out what to do and tried understanding what's up but I actually feel even more confused than before.
I need somebody who's patient enough to explain to me in dot points, yes like a toddler, what to do from here step by step and how to get my htc one working again.
Click to expand...
Click to collapse
Hey, hi
i am here to help you
are you ready??
Just let me know,
1. Are you sOFF?
2. Is your bootlader unlocked?
prunzzz said:
Hey, hi
i am here to help you
are you ready??
Just let me know,
1. Are you sOFF?
2. Is your bootlader unlocked?
Click to expand...
Click to collapse
YAY! thanks so much!
It's S-On and it says UNLOCKED at the top of the screen highlighted in pink so I suspect yes.
zackalphabet said:
YAY! thanks so much!
It's S-On and it says UNLOCKED at the top of the screen highlighted in pink so I suspect yes.
Click to expand...
Click to collapse
Let's just try to get your phone up and running, okay.
in bootloader/FASTBOOT USB: open a command prompt on your pc, go to your adb folder and type:
fastboot getvar all and copy/paste the output here (remove IMEI and s/n)
then
fastboot erase cache
and try to enter recovery (which one are you using by the way? including version number pls)
nkk71 said:
Let's just try to get your phone up and running, okay.
in bootloader/FASTBOOT USB: open a command prompt on your pc, go to your adb folder and type:
fastboot getvar all and copy/paste the output here (remove IMEI and s/n)
then
fastboot erase cache
and try to enter recovery (which one are you using by the way? including version number pls)
Click to expand...
Click to collapse
dont know what version number it is, it's CWMR.
did all that and it's just stuck on "waiting for device"
zackalphabet said:
dont know what version number it is, it's CWMR.
did all that and it's just stuck on "waiting for device"
Click to expand...
Click to collapse
does the screen show FASTBOOT USB in red; see attached
nkk71 said:
does the screen show FASTBOOT USB in red; see attached
Click to expand...
Click to collapse
yes it does.
zackalphabet said:
yes it does.
Click to expand...
Click to collapse
reboot PC and phone, if it still doesn't work, you may need to update HTC drivers; was it working properly before?
latest drivers:
HTCDriver_4.8.0.002.exe 15.1 MB
https://mega.co.nz/#!TAcGAJ7L!YdWM4AIji95b1ow8kVgagggOx5Yh7csRN5G0KJaCo6w
uninstall everything in control panel/programs that starts with HTC, then install these while you phone is NOT connected
nkk71 said:
reboot PC and phone, if it still doesn't work, you may need to update HTC drivers; was it working properly before?
latest drivers:
HTCDriver_4.8.0.002.exe 15.1 MB
uninstall everything in control panel/programs that starts with HTC, then install these while you phone is NOT connected
Click to expand...
Click to collapse
done and done!
zackalphabet said:
done and done!
Click to expand...
Click to collapse
fastboot devices
it should show your phones serial number, if OK, go to previous post and do the two commands
nkk71 said:
fastboot devices
it should show your phones serial number, if OK, go to previous post and do the two commands
Click to expand...
Click to collapse
it shows nothing. I dont think it's reading my device at all
zackalphabet said:
it shows nothing. I dont think it's reading my device at all
Click to expand...
Click to collapse
open Device Manager on your PC and check what you have
nkk71 said:
open Device Manager on your PC and check what you have
Click to expand...
Click to collapse
It says Unknown USB Device (Device Failed Enumeration)
zackalphabet said:
It says Unknown USB Device (Device Failed Enumeration)
Click to expand...
Click to collapse
what version of Windows are you on? I hope Win 7; Windows 8 and 8.1 sometimes have "issues", there are solutions (I think) but you'll have to look for them.
Try manually selecting a driver, if it's Win 7 or anything like it select "Update Driver" -> "Browse..." -> "Let me choose " -> "Android USB Devices" and select the "My HTC Version: xxxxx" the latest one.
nkk71 said:
what version of Windows are you on? I hope Win 7; Windows 8 and 8.1 sometimes have "issues", there are solutions (I think) but you'll have to look for them.
Try manually selecting a driver, if it's Win 7 or anything like it select "Update Driver" -> "Browse..." -> "Let me choose " -> "Android USB Devices" and select the "My HTC Version: xxxxx" the latest one.
Click to expand...
Click to collapse
I did that and it comes up with this:
zackalphabet said:
I did that and it comes up with this:
Click to expand...
Click to collapse
try uninstalling the driver (in device manager), reboot, and plug in phone again, see if you get the driver working.
nkk71 said:
try uninstalling the driver (in device manager), reboot, and plug in phone again, see if you get the driver working.
Click to expand...
Click to collapse
so I switched to my desktop and tried all of that again and now it seems to be reading it just fine.
after doing getvar all this came up:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.980.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 3712mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.069s
zackalphabet said:
so I switched to my desktop and tried all of that again and now it seems to be reading it just fine.
after doing getvar all this came up:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.980.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 3712mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.069s
Click to expand...
Click to collapse
So now your problem is solved, right?
Sent from my HTC One using xda premium
I just installed GPe 4.4 and I'm stuck in boot hell too. It gets to select language and then it restarts.
BobFaggot said:
I just installed GPe 4.4 and I'm stuck in boot hell too. It gets to select language and then it restarts.
Click to expand...
Click to collapse
Same things happening to me. It shows the lockscreen and keeps restarting, whenever I go into my custom recovery it says "entering recovery..." and it goes back into bootloop Did you by any chance get yours fixed?
Hello,
My phone is not rooted. It was still on factory setting, with no custom roms. I've been keeping up w/ the updates and i don't recall anything "special" happening before it was bricked yesterday night.
I tried accessing the fastboot screen (vol down + power button), and tried recovering, rebooting, and factory resetting, and they all sent it back to a freezing boot screen.
Using Hasoon2000's HTC One All-In-One Toolkit, I tried to boot it into bootloader, after a couple of hours, I saw a black screen w/ a red triangle in the middle, and after that, it just went back to being frozen at the Htc boot screen.
I have no idea what to do, any suggestions would help.
Thank You
-George Kayogre
Edit: Some specs in HBOOT:
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
George Kayogre said:
Hello,
My phone is not rooted. It was still on factory setting, with no custom roms. I've been keeping up w/ the updates and i don't recall anything "special" happening before it was bricked yesterday night.
I tried accessing the fastboot screen (vol down + power button), and tried recovering, rebooting, and factory resetting, and they all sent it back to a freezing boot screen.
Using Hasoon2000's HTC One All-In-One Toolkit, I tried to boot it into bootloader, after a couple of hours, I saw a black screen w/ a red triangle in the middle, and after that, it just went back to being frozen at the Htc boot screen.
I have no idea what to do, any suggestions would help.
Thank You
-George Kayogre
Edit: Some specs in HBOOT:
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
Click to expand...
Click to collapse
Since, it is completely stock and you didn't change anything, it might be a hardware issue. I would return it to HTC or your carrier for repair. The black screen with the red triangle is the stock recovery screen. The other thing you might try is run a RUU if available. Can you post a fastboot getvar all with the imei and serialno removed?
George Kayogre said:
Hello,
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
Click to expand...
Click to collapse
don't make duplicate posts
I answered you here >> http://forum.xda-developers.com/htc-one/help/htc-one-soft-bricked-idea-to-t2851592
clsA said:
don't make duplicate posts
I answered you here >> http://forum.xda-developers.com/htc-one/help/htc-one-soft-bricked-idea-to-t2851592
Click to expand...
Click to collapse
Sorry about the other thread, i was instructed to make another one in the correct section, but then a mod also moved my old post to this section...making it 2...
Anyway, I'm unable to get my device recognized, all it shows is "waiting for device" for ever.
majmoz said:
Since, it is completely stock and you didn't change anything, it might be a hardware issue. I would return it to HTC or your carrier for repair. The black screen with the red triangle is the stock recovery screen. The other thing you might try is run a RUU if available. Can you post a fastboot getvar all with the imei and serialno removed?
Click to expand...
Click to collapse
I'm trying to get the fastboot getvar from Hasoon's program, but it's returning an "error: device not found".
George Kayogre said:
Sorry about the other thread, i was instructed to make another one in the correct section, but then a mod also moved my old post to this section...making it 2...
Anyway, I'm unable to get my device recognized, all it shows is "waiting for device" for ever.
I'm trying to get the fastboot getvar from Hasoon's program, but it's returning an "error: device not found".
Click to expand...
Click to collapse
first of all, if you are not returning your device to your carrier or htc like majmoz suggested above and you want to troubleshoot it yourself, you will need to get rid of that toolkit and learn how to use ADB and FASTBOOT from a command window. Toolkits aren't the best thing when troubleshooting. They often comes with outdated stuff.
Install your HTC drivers correctly on your computer
download and install the Android SDK or Minimal ADB and FASTBOOT
do the commands cIsA told you on your other thread and post the results. The output of "fastboot getval all" could also be useful
alray said:
first of all, if you are not returning your device to your carrier or htc like majmoz suggested above and you want to troubleshoot it yourself, you will need to get rid of that toolkit and learn how to use ADB and FASTBOOT from a command window. Toolkits aren't the best thing when troubleshooting. They often comes with outdated stuff.
Install your HTC drivers correctly on your computer
download and install the Android SDK or Minimal ADB and FASTBOOT
do the commands cIsA told you on your other thread and post the results. The output of "fastboot getval all" could also be useful
Click to expand...
Click to collapse
Tried that, but still can't get my pc to recognize the device in bootloader, althought HTC sync does pop up every time i connect it.
When i type "fastboot devices" in the command prompt, nothing happens, then "fastboot clear cache" just shows "waiting for device".
I have downloaded the latest drivers, currently updating HTC Sync, hoping it'd affect something
George Kayogre said:
Tried that, but still can't get my pc to recognize the device in bootloader, althought HTC sync does pop up every time i connect it.
When i type "fastboot devices" in the command prompt, nothing happens, then "fastboot clear cache" just shows "waiting for device".
I have downloaded the latest drivers, currently updating HTC Sync, hoping it'd affect something
Click to expand...
Click to collapse
uninstall htc sync and try again
alray said:
uninstall htc sync and try again
Click to expand...
Click to collapse
Tried w/ and w/o HTC sync, ensured drivers were installed...and "fastboot devices" still has no effect.
George Kayogre said:
Tried w/ and w/o HTC sync, ensured drivers were installed...and "fastboot devices" still has no effect.
Click to expand...
Click to collapse
try another usb cable, another usb port. If the drivers are correctly installed, and the usb port/cable are ok and you still can't use fastboot commands from bootloader, it might be an hardware issue.
alray said:
try another usb cable, another usb port. If the drivers are correctly installed, and the usb port/cable are ok and you still can't use fastboot commands from bootloader, it might be an hardware issue.
Click to expand...
Click to collapse
Finally got my device to be recognized, all I did was plug in my phone, boot in into bootloader...again and again...till it was recognized
majmoz said:
Since, it is completely stock and you didn't change anything, it might be a hardware issue. I would return it to HTC or your carrier for repair. The black screen with the red triangle is the stock recovery screen. The other thing you might try is run a RUU if available. Can you post a fastboot getvar all with the imei and serialno removed?
Click to expand...
Click to collapse
This is what "fastboot getvar all" returned:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.401.110
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *erased*
(bootloader) imei: *erased*
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4078mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
clsA said:
Unzip this to your desktop and open a command window from it's folder (right click - command prompt here)
plug in your phone to the pc boot to the bootloader with power + volume down
type fastboot devices
your phone serial number should be listed
now type fastboot erase cache
it should say something about formatting cache
now fastboot reboot
hopefully your phone will boot back up
Click to expand...
Click to collapse
I did run these commands, they were performed successfully, but my phone is still getting frozen on the boot screen
George Kayogre said:
Finally got my device to be recognized, all I did was plug in my phone, boot in into bootloader...again and again...till it was recognized
This is what "fastboot getvar all" returned:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.401.110
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *erased*
(bootloader) imei: *erased*
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4078mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I did run these commands, they were performed successfully, but my phone is still getting frozen on the boot screen
Click to expand...
Click to collapse
have you tried to perform a factory reset from the bootloader?
alray said:
have you tried to perform a factory reset from the bootloader?
Click to expand...
Click to collapse
Yep, that was the first thing i tried to do, but i was still stuck w/ the same problem.
George Kayogre said:
Yep, that was the first thing i tried to do, but i was still stuck w/ the same problem.
Click to expand...
Click to collapse
if your phone is still under warranty, send it for repair because the next actions will void the warranty:
You'll probably have to unlock the bootloader, flash a custom recovery and flash a rom.
Not sure why this happened on a 100% stock phone. Normally, users get in this situation when flashing custom roms
alray said:
if your phone is still under warranty, send it for repair because the next actions will void the warranty:
You'll probably have to unlock the bootloader, flash a custom recovery and flash a rom.
Not sure why this happened on a 100% stock phone. Normally, users get in this situation when flashing custom roms
Click to expand...
Click to collapse
Here's something new: after unlocking my phone, and having confirmed that i wanted all my "personal data erased", it just booted up normally and it worked, but then, while using it, t=it simply crashed...and got stuck in the bootloop again, which kinda points in the arrow of hardware issue again. I'm gonna try installing a rom (after i figure out how) and see where that leads me.
Update: Flashed CM11, phone still on boot loop, sending to repair soon.
Everyone, thanks for the help anyway, I really appreciate it.
Hello guys,
I have a weird problem that happened not to my phone but a friend of mine... I'll try to make the details as good as possible but it may be different since I did not own the phone, but as I said, a friend did.
She says it was Sense6.0 4.4.2 and that one day the phone booted, showed the HTC logo like 3 times (between bootloop) and it went down (power off), so she charged it for like 1 days but it didn't turn the display on... Now, it had pattern lock so getting adb to work was a complete PITA but we figured that the phone wasn't dead when we tried to call her and she swept the screen to answer and she did, so, after a lot of pain, we managed to unlock it blindly and accept the recogniztion so we could have adb...
Now, we rebooted into fastboot, unlocked bootloader (which wiped the system to factory reset) and installed a custom kernel/recovery (via fastboot)
The phone has 1.57 HBOOT and I understand firewater works, but here is the major problem: I don't have access to Wireless because I cant see a damn thing so were screwed there... 3G connection doesn't work at all and I go and ping and it says failed...
ALTHOUGH I tried rumrunner (before I knew HBOOT was 1.57) and somehow it rebooted and the screen turned on so I figured the screen wasnt dead, but as soon as it finished booting, the screen went off again forever...
The phone has CID: HTC__332 (Latin American variant) so I cant find a suitable RUU so I can flash without S-OFF
I am really screwed but maybe anyone here with some experience can shed a light here and save an M7
PD: I have working adb and fastboot but just through command line
Poesini said:
Hello guys,
I have a weird problem that happened not to my phone but a friend of mine... I'll try to make the details as good as possible but it may be different since I did not own the phone, but as I said, a friend did.
She says it was Sense6.0 4.4.2 and that one day the phone booted, showed the HTC logo like 3 times (between bootloop) and it went down (power off), so she charged it for like 1 days but it didn't turn the display on... Now, it had pattern lock so getting adb to work was a complete PITA but we figured that the phone wasn't dead when we tried to call her and she swept the screen to answer and she did, so, after a lot of pain, we managed to unlock it blindly and accept the recogniztion so we could have adb...
Now, we rebooted into fastboot, unlocked bootloader (which wiped the system to factory reset) and installed a custom kernel/recovery (via fastboot)
The phone has 1.57 HBOOT and I understand firewater works, but here is the major problem: I don't have access to Wireless because I cant see a damn thing so were screwed there... 3G connection doesn't work at all and I go and ping and it says failed...
ALTHOUGH I tried rumrunner (before I knew HBOOT was 1.57) and somehow it rebooted and the screen turned on so I figured the screen wasnt dead, but as soon as it finished booting, the screen went off again forever...
The phone has CID: HTC__332 (Latin American variant) so I cant find a suitable RUU so I can flash without S-OFF
I am really screwed but maybe anyone here with some experience can shed a light here and save an M7
PD: I have working adb and fastboot but just through command line
Click to expand...
Click to collapse
So does the screen come on when the phone is booted to the bootloader and recovery?
Can you post fastboot getvar all?
Code:
fastboot getvar all
Post the output here but remove imei and serial numbers before posting.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
So does the screen come on when the phone is booted to the bootloader and recovery?
Can you post fastboot getvar all?
Code:
fastboot getvar all
Post the output here but remove imei and serial numbers before posting.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
No, the screen never turn on... It did only when trying the first time rumrunner but not anymore (But so, I know the screen isn't dead)
Here is the getvar all
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.15.599.101
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__332
(bootloader) battery-status: good
(bootloader) battery-voltage: 3854mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Poesini said:
No, the screen never turn on... It did only when trying the first time rumrunner but not anymore (But so, I know the screen isn't dead)
Here is the getvar all
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.15.599.101
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__332
(bootloader) battery-status: good
(bootloader) battery-voltage: 3854mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Click to expand...
Click to collapse
It does sound like a dead LCD to me. Weird how it came on once while running rumrunner though. Try powering off the device then hold a it under a bright light hold power on + volume down for 90+ seconds. Maybe a fault with proximity sensor.
There is no ruu you can use while s-on and I can't even find a firmware you can try to flash. So if that doesn't work I don't know what else to try
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
It does sound like a dead LCD to me. Weird how it came on once while running rumrunner though. Try powering off the device then hold a it under a bright light hold power on + volume down for 90+ seconds. Maybe a fault with proximity sensor.
There is no ruu you can use while s-on and I can't even find a firmware you can try to flash. So if that doesn't work I don't know what else to try
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
Holding the device under a bright light seems to power on the device SOMETIMES with the HTC logo visible and then it gets past that (with a little backlight movement meanwhile -dimmer- or -brighter-) and then back to desktop with no light
Is there any way to disable the proximity sensor or maybe flash a custom ROM via adb commands to flash it into recovery inside OS (TWRP 2.8.1.0 right now) or something?
Poesini said:
Holding the device under a bright light seems to power on the device SOMETIMES with the HTC logo visible and then it gets past that (with a little backlight movement meanwhile -dimmer- or -brighter-) and then back to desktop with no light
Is there any way to disable the proximity sensor or maybe flash a custom ROM via adb commands to flash it into recovery inside OS (TWRP 2.8.1.0 right now) or something?
Click to expand...
Click to collapse
Well that's promising. You can push a Rom with adb but you need the recovery menu to install it which may prove difficult if you can't see it.
To push the Rom put it in your fastboot folder and rename it rom.zip. connect the usb with the phone for adb and type in the command window
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push completes.
You may be better to use TWRP 2.6.3.3 to avoid install problems. Remember to
Code:
fastboot erase cache
when you flash a new recovery.
And keep using the bright light power on trick. May be give the sensors a clean (top left of the phone).
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
Well that's promising. You can push a Rom with adb but you need the recovery menu to install it which may prove difficult if you can't see it.
To push the Rom put it in your fastboot folder and rename it rom.zip. connect the usb with the phone for adb and type in the command window
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push completes.
You may be better to use TWRP 2.6.3.3 to avoid install problems. Remember to
Code:
fastboot erase cache
when you flash a new recovery.
And keep using the bright light power on trick. May be give the sensors a clean (top left of the phone).
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
I know my ways to push files via ADB, but I am saying like SuperSU does when it asks if you want to update it via TWRP option where it reboots directly to recovery and flashes a zip without you doing anything
I could push many files via ADB, but I couldn't flash them correctly (and I don't want to screw this phone) without seeing the screen
Poesini said:
I know my ways to push files via ADB, but I am saying like SuperSU does when it asks if you want to update it via TWRP option where it reboots directly to recovery and flashes a zip without you doing anything
I could push many files via ADB, but I couldn't flash them correctly (and I don't want to screw this phone) without seeing the screen
Click to expand...
Click to collapse
Flash twrp 2.6.3.3 newer versions of twrp can be temperamental and probably why your having trouble flashing roms
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
---------- Post added at 07:26 PM ---------- Previous post was at 07:07 PM ----------
Try the bright light trick again but this time power off the device. Hold the sensors close to the light
Hold volume up and down +power for 60 secs the phone will bootloop while your holding the buttons. Hopefully that will be enough to reset the sensor. :fingers-crossed:
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Dear XDA-Developers Forum,
I require your help fixing my HTC One M7.
When I tried to use an RUU to set it back to stock firmware the RUU.exe returned error 155. Maybe I did something wrong. I have some experience flashing different phones but I'm not a pro like most people here..
Anyway, the phone hung at the black screen with the HTC logo. At some point I managed to reconnect to the bootloader and Fastboot commands were still available. I tried using Fastboot to verify I had the correct RUU which to all appearance was the case. After trying to reboot to system the phone is stuck in a loop. It displays the CM logo from the ROM it had previously installed.
From here, I'm stuck. Power button does not work, combinations to go into bootloader don't work. The only thing that does work is holding power and vol+ and vol- at the same time. This makes the phone reboot (showing white HTC screen with green logo). After a few seconds I am however stuck with the CM logo.
Is there a way to fix this?
Some additional info on my device:
HBoot 1.55
Bootloader unlocked
S-ON (although that's strange cause I had it turned off before)
CM 10.2 installed
TWRP 2.8.5.0
I hope someone has a solution. Of course all drivers and software are up to date and I have backup of my relevent data. I fear that I will need to get a replacement since extensive Google-Search would not yield a solution so far. It could be I'm just not educated enough to understand.
Best regards
Nick
Little Update
Without any chance of turning the device off and re-entering bootloader or recovery I waited until the battery finally died.
I plugged it into the wall charger. I was then finally able to start to the bootloader. It looked very usual. The security alert had disappeared and it was in HBoot mode.
I went on and selected factory reset guessing this to be the easiest and quite likely solution to the bootloop. TWRP started but showed a number of mounting errors and did not finish the operation. After auto-restart I'm back at the bootloop from the start.
Waiting for the battery to die again...
Any suggestions what I should do next?
DNK83 said:
Without any chance of turning the device off and re-entering bootloader or recovery I waited until the battery finally died.
I plugged it into the wall charger. I was then finally able to start to the bootloader. It looked very usual. The security alert had disappeared and it was in HBoot mode.
I went on and selected factory reset guessing this to be the easiest and quite likely solution to the bootloop. TWRP started but showed a number of mounting errors and did not finish the operation. After auto-restart I'm back at the bootloop from the start.
Waiting for the battery to die again...
Any suggestions what I should do next?
Click to expand...
Click to collapse
Error 155 means your using the wrong RUU
You don't need to keep waiting for the battery to die, hold down the volume down button and the power button together, keep them held down, the captive lights on the bottom will flash about 15 times, when the phone goes off, let go of the power button only, the phone should now boot to the bootloader.
post your fastboot getvar all without imei and serial number please, anyone here needs more info about your phone before we can help and this will tell us all everything we need to know.
Hello,
thanks for your reply.
I have tried holding the power button and vol- together. Even after more than 30 seconds the phone does not react and keeps on showing the CM logo.
Sorry, for not providing more information. I would've posted the getvar info before but was not able to connect through fastboot.
Will do once the battery is charged enough for the next try.
After the battery dying and charging a little bit I was able to go into fastboot mode. The loader screen was showing "fastboot usb". Trying to obtain the variables yields:
C:\fastboot>fastboot getvar (all)
getvarall) FAILED (remote: unknown command)
finished. total time: 0.016s
DNK83 said:
After the battery dying and charging a little bit I was able to go into fastboot mode. The loader screen was showing "fastboot usb". Trying to obtain the variables yields:
C:\fastboot>fastboot getvar (all)
getvarall) FAILED (remote: unknown command)
finished. total time: 0.016s
Click to expand...
Click to collapse
take the brackets off the all () the command is fastboot getvar all
DNK83 said:
After the battery dying and charging a little bit I was able to go into fastboot mode. The loader screen was showing "fastboot usb". Trying to obtain the variables yields:
C:\fastboot>fastboot getvar (all)
getvarall) FAILED (remote: unknown command)
finished. total time: 0.016s
Click to expand...
Click to collapse
Why the brackets () in "fastboot getvar (all)" ? The command is "fastboot getvar all" without the quotes.
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.206.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3684mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
alray said:
Why the brackets () in "fastboot getvar (all)" ? The command is "fastboot getvar all" without the quotes.
Click to expand...
Click to collapse
The brackets are added because I'm tired and kinda angry.
DNK83 said:
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.206.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3684mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Click to expand...
Click to collapse
first of all I recommend you flash twrp 2.8.6.0 from here, it will make life easier for you: https://dl.twrp.me/m7/twrp-2.8.6.0-m7.img.html
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
then enter twrp, and create a very simple backup, just something like boot or cache.
now plug your phone into the computer, it should open on your computer as this version of twrp supports MTP, navigate to the TWRP backup folder on your phone and delete the backup file from the folder (just the backup file itself, none of the folders) it will be in TWRP/BACKUP/PHONE SERIAL NUMBER/DATE AND OTHER DIGITS/ delete the file in here and replace with the files in this zip (make sure you extract the zip first): https://www.androidfilehost.com/?fid=95897840722646676
now unplug your phone and restore the backup.
The installation of TWRP worked fine. Trying to make the simple backup yields a bunch of failed attempts to mount.
DNK83 said:
The installation of TWRP worked fine. Trying to make the simple backup yields a bunch of failed attempts to mount.
Click to expand...
Click to collapse
in that case, select wipe, and then format data button, type yes to confirm, when done, select reboot to recovery for change to take effect, it will say no OS installed, just ignore it, it will also ask you if you would like to install super SU, select do not install, when the phone boots back to recovery, try backup again.
Okay.
I formatted the card and was able to do the backup. I was neither notified of a missing OS nor asked if I wanted to Install Super SU. Reboot to Recovery worked normal.
Plugging the phone into my computer does not yield a connection that I could use to copy files.
DNK83 said:
Okay.
I formatted the card and was able to do the backup. I was neither notified of a missing OS nor asked if I wanted to Install Super SU. Reboot to Recovery worked normal.
Plugging the phone into my computer does not yield a connection that I could use to copy files.
Click to expand...
Click to collapse
make sure you are on the recovery main screen when you plug the phone into your computer, no sub menu's.
If it still doesn't appear on your computer, double check your device manager to make sure its showing in there correctly.
A "Google Nexus ADB Interface" is listed. Is that what we're looking for?
Btw: many thanks for the help so far. It's becoming quite exciting right now.
DNK83 said:
A "Google Nexus ADB Interface" is listed. Is that what we're looking for?
Btw: many thanks for the help so far. It's becoming quite exciting right now.
Click to expand...
Click to collapse
Strange, it should look like this pict below, I'm using a HTC One M8, with the latest TWRP, but its the same thing as yours, as I previously had the M7.
try uninstall, that driver and then manually install the correct driver.
check Question 2 here on how to manually force the driver: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
I have tried re-installing the HTC driver. So far no results. Did you want me to remove this ADB thing from the device manager? I am rebooting quickly to see if Win7 is the problem.
DNK83 said:
I have tried re-installing the HTC driver. So far no results. Did you want me to remove this ADB thing from the device manager? I am rebooting quickly to see if Win7 is the problem.
Click to expand...
Click to collapse
yes, just right click that other driver and uninstall it, then reboot.
I just download HTC sync manager and install that for my drivers, then just uninstall HTC sync, you will see the driver package which comes with sync manager just above it, leave that one alone, never had a problem with it.
The hardware detection ran when I plugged the phone in. The device is again listed as "Google Nexus ADB Device"
I have a package installed named "Minimal ADB and Fastboot Version 1.2". This is probably the reason why my phone is listed this way right now...uninstall?
DNK83 said:
The hardware detection ran when I plugged the phone in. The device is again listed as "Google Nexus ADB Device"
I have a package installed named "Minimal ADB and Fastboot Version 1.2". This is probably the reason why my phone is listed this way right now...uninstall?
Click to expand...
Click to collapse
strange, ive never seen it appear like that.
ive attached my adb and fastboot files below if you want to use those, maybe yours came with the google nexus driver.
Hi guys,
I really need help with my phone, i have an HTC One M7 802w dual sim and i soft bricked by trying to install an stock ruu which i though was the correct one for my phone.
I ended up being stuck in this screen an HTC Grey screen with exclamation marks in all four corners. I tried entering bootloader mode holding the phone in bright light by pressing the power button + vol down, but i had no success.
My computer can still see the device when try the fastboot devices command and can still flash a stock ruu i think but i can't find the correct one for my phone.
Can you guys please help! It almost brand new i only had it for 3 weeks now and i can't do anything but look at it
Here is my phones info:
(bootloader) version: 0.5
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-main: 2.39.1402.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0771000
(bootloader) battery-status: good
(bootloader) battery-voltage: 3675mV
(bootloader) partition-layout: Generic
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) hbootpreupdate: 11
all: Done!
finished. total time: 44.035s
Thank you in advance! I really hope that you guys can help me!
mrrrdude said:
Hi guys,
I really need help with my phone, i have an HTC One M7 802w dual sim and i soft bricked by trying to install an stock ruu which i though was the correct one for my phone.
I ended up being stuck in this screen an HTC Grey screen with exclamation marks in all four corners. I tried entering bootloader mode holding the phone in bright light by pressing the power button + vol down, but i had no success.
My computer can still see the device when try the fastboot devices command and can still flash a stock ruu i think but i can't find the correct one for my phone.
Can you guys please help! It almost brand new i only had it for 3 weeks now and i can't do anything but look at it
Here is my phones info:
(bootloader) version: 0.5
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-main: 2.39.1402.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0771000
(bootloader) battery-status: good
(bootloader) battery-voltage: 3675mV
(bootloader) partition-layout: Generic
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) hbootpreupdate: 11
all: Done!
finished. total time: 44.035s
Thank you in advance! I really hope that you guys can help me!
Click to expand...
Click to collapse
This is your RUU according to your version main http://d-h.st/7GA
flash it like this:
1. Download the file and rename the file to RUU.zip
2. Place it in adb/fastboot folder
3. Reboot phone to fastbootUSB mode
4. as you are S-On you need to relock bootloader
fastboot oem lock
fastboot erase cache
fastboot reboot-bootloader
5. fastboot oem rebootRUU
6. fastboot flash zip RUU.zip (pre HBOOT update, please flush again)
7. fastboot flash zip RUU.zip (yes twice)
now make sure at the end it says successful and OKAY
8. fastboot reboot-bootloader
9. fastboot reboot.
Seanie280672 said:
This is your RUU according to your version main http://d-h.st/7GA
flash it like this:
1. Download the file and rename the file to RUU.zip
2. Place it in adb/fastboot folder
3. Reboot phone to fastbootUSB mode
4. as you are S-On you need to relock bootloader
fastboot oem lock
fastboot erase cache
fastboot reboot-bootloader
5. fastboot oem rebootRUU
6. fastboot flash zip RUU.zip (pre HBOOT update, please flush again)
7. fastboot flash zip RUU.zip (yes twice)
now make sure at the end it says successful and OKAY
8. fastboot reboot-bootloader
9. fastboot reboot.
Click to expand...
Click to collapse
Thank you very much! i'll download the file and try! be back with a reply! hope it workes! thank you again!!!!!!
mrrrdude said:
Thank you very much! i'll download the file and try! be back with a reply! hope it workes! thank you again!!!!!!
Click to expand...
Click to collapse
IT WORKES!!!! My PHone is back to normal!! THANK YOU VERY MUCH!
I'm curious about something, can you please tell me what do you look for to see which is the proper RUU for any HTC?
mrrrdude said:
IT WORKES!!!! My PHone is back to normal!! THANK YOU VERY MUCH!
I'm curious about something, can you please tell me what do you look for to see which is the proper RUU for any HTC?
Click to expand...
Click to collapse
THIS: (bootloader) version-main: 2.39.1402.1
bit more tricky though if this isn't present, I then base it on CID, MID, Baseband version, HBOOT version etc, whatever I can.
it helps that you have a dual sim kind of, everything for your phone is here: http://forum.xda-developers.com/showthread.php?t=2617159
scroll down the page till you see 3. HTC One 802w (x.xx.1402.x) in blue, and then from there look up your full version main, if your VM is an OTA, then you have a big problem trying to recovery your phone, if theres an RUU then its easy.
Now your back up and running, make yourself a nandroid backup before messing with your phone, then copy the nandroid to somewhere safe on your computer, ive seen so many people wipe there entire phone by accident, including the nandroid and then being stuck, or get s-off for it, s-off is the difference between fixing your phone in the future if it ever goes down again, or having a nice new paper weight.
Seanie280672 said:
THIS: (bootloader) version-main: 2.39.1402.1
bit more tricky though if this isn't present, I then base it on CID, MID, Baseband version, HBOOT version etc, whatever I can.
it helps that you have a dual sim kind of, everything for your phone is here: http://forum.xda-developers.com/showthread.php?t=2617159
scroll down the page till you see 3. HTC One 802w (x.xx.1402.x) in blue, and then from there look up your full version main, if your VM is an OTA, then you have a big problem trying to recovery your phone, if theres an RUU then its easy.
Now your back up and running, make yourself a nandroid backup before messing with your phone, then copy the nandroid to somewhere safe on your computer, ive seen so many people wipe there entire phone by accident, including the nandroid and then being stuck, or get s-off for it, s-off is the difference between fixing your phone in the future if it ever goes down again, or having a nice new paper weight.
Click to expand...
Click to collapse
Thank you very much for your help! I'll do that from now one! i have allot to learn about flashing.