Hey all
I believe based on model number, that I have an M7 HTC One. It was working just fine, and got some OTA update and the phone rebooted. From that point on, I get the ATT logo and noise (at max volume).. black screen and about 90 seconds, and reboots and starts over again.
I found the commands to get into the boot menu and chose the restore function after looking for all other options, and not only did it not help, it didn't make a difference!
Any suggestions? I see a TON of RUU images, utilities, and 1,000 other things that might help force out a new image onto the phone, but I am not familiar with what are the right choices or what might work? I did search through the forums first, looked at options, but didn't see what I was looking for or don't know enough to know what I am looking at.
Suggestions?
Boot menu system info says:
****LOCKED******
M7_UL PVT SHIP S-ON RH
HBOOT - 1.57.0000
RadIO-4M.27.3218.14
OpenDSP-v32.120.274.0909
OS-5.12.502.2
eMMC-boot 2048mb
Apr 22 2014, 01:10:58.0
All of the various HBOOT menu options.. chose fastboot, recovery, facory reset.. nothing helps..
Handaar said:
Hey all
I believe based on model number, that I have an M7 HTC One. It was working just fine, and got some OTA update and the phone rebooted. From that point on, I get the ATT logo and noise (at max volume).. black screen and about 90 seconds, and reboots and starts over again.
I found the commands to get into the boot menu and chose the restore function after looking for all other options, and not only did it not help, it didn't make a difference!
Any suggestions? I see a TON of RUU images, utilities, and 1,000 other things that might help force out a new image onto the phone, but I am not familiar with what are the right choices or what might work? I did search through the forums first, looked at options, but didn't see what I was looking for or don't know enough to know what I am looking at.
Suggestions?
Boot menu system info says:
****LOCKED******
M7_UL PVT SHIP S-ON RH
HBOOT - 1.57.0000
RadIO-4M.27.3218.14
OpenDSP-v32.120.274.0909
OS-5.12.502.2
eMMC-boot 2048mb
Apr 22 2014, 01:10:58.0
All of the various HBOOT menu options.. chose fastboot, recovery, facory reset.. nothing helps..
Click to expand...
Click to collapse
your s-on and locked bootloader use the AT&T RUU here >> http://dl3.htc.com/application/RUU_...06_10.46.1718.01L_release_424933_signed_2.exe
Thank you and I will check that. I just ran it once, and while the phone seemed to respond to the flash, it still loops on boot. The utility then crashed out, but I will try it again. Thank you!
Yeah.. the installer recognized the phone the first sitting in fastboot USB mode, but now doing the same thing the installer fails out saying no phone detected even though I get the USB connection chime noise from my PC, and I can see the fastboot flip to fastboot USB showing it is connected.
This may be a completely bricked phone.
Related
Carrier: Sprint
Phone: 32GB HTC One
M7_WLS PVT SHIP S-ON RH
HBOOT-1.44.0000
OpenDSP-v31.120.274.0617
eMMC-boot
Jul 5 2013, 17:19:22:-1
Unlocked
TWRP Recovery 2.5.0.0
I unlocked my phone and successfully flashed ViperROM 1.1.0 onto it. Unhappy with the ROM, I went to try Paranoid (4.3) and I screwed something up along the way. Now my phone boots up, the carrier information is gone so I get no signal what so ever, wifi doesn't work and the phone restarts at random. I tried to use fastboot to lock the bootloader and go back to stock, but I keep getting a "12 signature verify fail" when I try to flash with the factory RUU for my phone. If you can point me in the direction of a relevant thread or post helpful information in here, I'd be very grateful.
Edit:
I guess I was just using the wrong SPRINT RUU for my phone. It's all good now, reverted to stock and now I'm on Official Android 4.3
HTC ONE Stuck on Bootloader Screen...HELP PLE
Im really frinking out my phone is stuck on Bootloader screen i root everything was good and for some stupid reason i decided to updated it to 4.3 and after i run it and it restart i just keep going back to bootloader screen try recovery but it will just got back to same screen when you plug into the computer it does detect ti just fine but i don't know what to do this is what is on my screen. i try RUU but is say i have the wrong version (31.1)
and the phone is like completely wipe out. some HELP ME PLEASE , I don't have insurance nor warranty and the phone is like 1 month old
***tampered***
***Relocked***
M7_WIL PVT SHI P S-ON RH
HBOOT-1.44.0000
OpenDSP-v31.120.274.0617
eMMC-boot
Hello --
My US T-Mobile HTC One received the Kit-Kat update today (first day of upgrade). It is stuck on the white "HTC One" screen and cannot go past it. Phone is (was?) stock T-Mob Android rooted. I went back to the stock recovery to ensure the update happened properly. That whole process of rooting, using custom recovery, etc went pretty smoothly. Now it is just stuck on that boot screen. T-Mobile logo appears very briefly looks corrupt/scrambled. I can issue ADB commands so I know it is talking to the device, however the device says "offline" and I cannot get it go "online". I tried other USB cables, kill-server, start-server and nothing is bringing it back online. Screen has now been on over an hour (I cannot get it to turn off completely in the boot screen). I figured being it is talking still to the device (although offline) maybe all is not lost.Anyone with any advice on how to get this up and running before I have to return this to T-Mobile and pay hefty probably for this.
If anyone can help, maybe the below will be helpful:
M7_VL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.03
OpenDSP-v32.120.274.0909
OS-3.24.531.3
eMMC-boot 2048MB
Oct 4 2013, 17:31:32.0
I upgraded ADB, and now instead of OFFLINE it says UNAUTHORIZED (although I have used ADB before on this same computer/device and it was fine -- consistently have used other ROMs before, etc)
LAChris67 said:
If anyone can help, maybe the below will be helpful:
M7_VL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.03
OpenDSP-v32.120.274.0909
OS-3.24.531.3
eMMC-boot 2048MB
Oct 4 2013, 17:31:32.0
I upgraded ADB, and now instead of OFFLINE it says UNAUTHORIZED (although I have used ADB before on this same computer/device and it was fine -- consistently have used other ROMs before, etc)
Click to expand...
Click to collapse
Did you figure out how to solve the problem?
Can you get into the bootloader and wipe the device?
adzenith said:
Did you figure out how to solve the problem?
Click to expand...
Click to collapse
I used Guru Reset from http://www.htc1guru.com/downloads/stock-rom-downloads/, then used a USB OTG cable and a mouse to get the first update, then got the second update, then reflashed TWRP, then rooted.
If I did it again I think I'd go the RUU route to save me from having to use the mouse and do two updates.
adzenith said:
Did you figure out how to solve the problem?
Click to expand...
Click to collapse
Thanks for asking. After a couple of hours of panic and then reading on here, (if I remember correctly) I kept powering it until it gave me the option to fastboot (vol-down, power -- but I had to keep trying it because it would not take or boot properly consistently). I was able to flash RUU onto it, somehow lost all the data on the memory card (maybe this is normal?) and then was able to take the update. Not sure what happened there, but once I did the RUU, it was able to take the boot and update and re-boot itself to complete the install. For me, it seems like something was wrong with recovery. I flashed the stock one, but perhaps I loaded the wrong one (although I had been booting/rooted practically since I had the device a year ago).
Hi all,
I have bought an unlocked HTC one (m7), it seems in good working order but when i tried to sell it on, they told me there is no recovery mode, and the it says RElocked.
So when i tried to go into recovery nothing works, I just get a red triangle inside a phone picture. noting works when i press power and Volume up either,
could someone please advise in child like details how i can get this phone back to normal so i can sell it please.
here are the phone details:
*** RELOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.000
RADIO-4A.25.3263.21
OpenDSP-V32.120.274.0909
OS-4.19.401.11
eMMC-boot 2048mb
THANKYOU
The recovery sounds fine, the only way to get it back to locked rather than relocked is to s-off (security off the phone) which might be doable via firewater http://firewater-soff.com/
You need to do some research on the hoops to go through to s-off/unlock/relock etc. plenty of threads about it. Not child like instructions but hopefully send you in the right direction.
Hello,
I seemed to have bricked/boot lopped my Sprint HTC One. I was trying to flash a zip to turn of system write protection, before i noticed it was an obsolete zip. Since then when trying to boot normally all I get is the white screen with the HTC logo. I can get into the bootloader and TWRP recovery, but my computer will not mount it as a mass storage device so i cant copy anything to it. I have tried adb sideload but adb doesnt ee my device. Fastboot seems to be the only thing half working. I have tried fastbooting a new stock boot image and a 1.29 RUU image and erasing, still no luck. I have tried locking it and doing all this and unlocked. I get further unlocked. I have scoured this forum and google for solutions but nothing has seemed to work. I dont know if its because of the recent update or not.
Here is what shows up on the bootloader screen:
*** TAMPERED ***
*** UNLOCKED ***
M7_WLS_ PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-1.01.20.0515
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
May 15 2014, 16:31:22.0
filgto2000 said:
Hello,
I seemed to have bricked/boot lopped my Sprint HTC One. I was trying to flash a zip to turn of system write protection, before i noticed it was an obsolete zip. Since then when trying to boot normally all I get is the white screen with the HTC logo. I can get into the bootloader and TWRP recovery, but my computer will not mount it as a mass storage device so i cant copy anything to it. I have tried adb sideload but adb doesnt ee my device. Fastboot seems to be the only thing half working. I have tried fastbooting a new stock boot image and a 1.29 RUU image and erasing, still no luck. I have tried locking it and doing all this and unlocked. I get further unlocked. I have scoured this forum and google for solutions but nothing has seemed to work. I dont know if its because of the recent update or not.
Here is what shows up on the bootloader screen:
*** TAMPERED ***
*** UNLOCKED ***
M7_WLS_ PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-1.01.20.0515
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
May 15 2014, 16:31:22.0
Click to expand...
Click to collapse
Sweet baby jesus, I dont know how but i got ADB sideload to work and installed ViperOne. Thank god,
Hello! Usually I am able to do research and fix my own problems that I have had with my HTC but this time it seems to be different.
I have a T-Mobile HTC One that has Insertcoin 3.0.3 installed with Kangaroo Kernel v100.
The phone is rooted and unlocked and the bootloader reads as follows:
***Unlocked***
M7_UL PVT SHIP S-OFF RH
CID-TMOBO010
HBOOT-1.57.0000
RADIO-4T.27.3218.14
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
May 9 2014,15:57:530
Before going to work last night I was checking facebook when all of the sudden my phone froze. Naturally I just held down the power button and waited it to boot back up. While I was distracted by the tv I glanced back down to my phone and realized it was just a black screen. I tried to re-reboot and same thing happened. (The phone starts and displays the HTC screen but does not get to the boot animation)
Next I tried to boot into recovery but once I enter the bootloader and select an option my phone freezes and I have to power it down. Same thing happends to all of the options... Fastboot, recovery, factory reset, ect.
Another strange thing is that the phone flashes a red light opposed to a solid red light when I plug it in to charge. The phone is completely cool and it is not overheating.
I'd really like to be able to fix the phone or at least be able to re-lock it so I can send it to T-Mobile for repairs if needed.
The phone has been working fine the whole day before the incident.
P.S. I just realized the bootloader displays the OS as empty?