Database Develop

[Q] Bricked Sprint HTC One M7 - Stuck in boot loop

Hello,
About a month back I destroyed my old HTC One. I unlocked the phone and flashed a new rom for the International version instead of the Sprint version. Ever since, no matter what rom I use, the phone is stuck in a boot loop. I cannot set it back to factory with the RUU because my version is more recent and I do not have S-OFF. I've since bought a new phone, but I'm looking to attempt to get the old one working. This has been a learning experience.
M7_WLS PVT SHIP S-ON RH
HBOOT - 1.55.0000
OpenDSP-v31.120.274.0617
OS-3.04.651.2
eMMC-boot 2048MB
Sep 18 2013,15:46:04.0
Any insight on what I can do to fix this would be greatly appreciated.
Thanks,
SJJ

sjjonesjr1 said:
Hello,
About a month back I destroyed my old HTC One. I unlocked the phone and flashed a new rom for the International version instead of the Sprint version. Ever since, no matter what rom I use, the phone is stuck in a boot loop. I cannot set it back to factory with the RUU because my version is more recent and I do not have S-OFF. I've since bought a new phone, but I'm looking to attempt to get the old one working. This has been a learning experience.
M7_WLS PVT SHIP S-ON RH
HBOOT - 1.55.0000
OpenDSP-v31.120.274.0617
OS-3.04.651.2
eMMC-boot 2048MB
Sep 18 2013,15:46:04.0
Any insight on what I can do to fix this would be greatly appreciated.
Thanks,
SJJ
Click to expand...
Click to collapse
Did you read this: http://forum.xda-developers.com/showthread.php?t=2503646 ?

I downgraded firmware and everything works
tdhite said:
Did you read this: http://forum.xda-developers.com/showthread.php?t=2503646 ?
Click to expand...
Click to collapse
I had the same problem before. I can't even restore ruu rom .. but as soon as I downgrade the firmware from 3.05.651.6 to 3.04.651.2 . everything works without a bootloop. been working on this problem for two days .. hope this will help others.
sprint htc one
hboot 155

Hello I have a problem,
I have htc one m7 locked for sprint (hboot 1.57.000, android 4.4 ) I already root it then i tried to turn s-off with rumrunner it was not possible cuz my kernel was stock ( I think...) so i tried to install custom kernel (Bulletproof-m7wl-1.2.zip) i then i stuck in bootloop ( htc logo). Now I can enter in recovery (teamwin) but i don't know what to do next.

diin1993 said:
Hello I have a problem,
I have htc one m7 locked for sprint (hboot 1.57.000, android 4.4 ) I already root it then i tried to turn s-off with rumrunner it was not possible cuz my kernel was stock ( I think...) so i tried to install custom kernel (Bulletproof-m7wl-1.2.zip) i then i stuck in bootloop ( htc logo). Now I can enter in recovery (teamwin) but i don't know what to do next.
Click to expand...
Click to collapse
You bootlooped because you loaded an incompatible kernel. Use *only* m7spr/m7wls kernels.
With that said -- just download a ROM you want (again -- stock with M7SPR or M7WLS (they're the same thing, just different ROMs call them by various names -- not going to explain that here).
Then, load your recovery (hopefully my TWRP 2.8.0.3 because it will work for you); "adb push" the rom file to /sdcard (i.e.: adb push <path_to_the_zip>.zip /sdcard) -- yes, that will work in recoveries.
Then install the ROM in your recovery. You should be fine with the caveat that if the kernel you loaded messed up your partitions (by writing it to the entirely incorrect disk partition), you'll have to RUU back to stock.

One/M7 stuck after TMOB upgrade to Kit-Kat

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).

[Q] Help not sure what I did

So lets start out with I was using Beanstalk and really enjoyed it till my internet was malfunctioning. So I was checking out how to do a PLR update and noticed that the version I had didn't support it. So in turn I decided to look for a rom that had the Sense, so I chose the Viper rom. I went through the the CWM to load it and it wouldn't work (multiply tries.) I then tried using an older version of TWRP, I think 2.6, and it was working but then it would fail at status 7. I did some research and there were a few posts that mentioned to use the newest version. So I downloaded it, it gets as far as installing the rom and I still get the status 7 failure. So then the phone would only boot into the bootloader, so I reinstalled TWRP, it worked but wont load the rom. I reinstall the rom and I get as far as the bootloader again and need to reinstall TWRP. Now my phone is locked in the bootloader, it says at the top:
TAMPERED
RELOCKED
M7_WLS PVT SHIP S-ON RH
HBOOT-1.44.000
OpenDSP-v26.120.274.0202
eMMC-boot
May 8 2013,16:30:08:-1
Yes I do know that when I did the previous rom it will always say tampered but I don't know why it is relocked and S-ON. It should have been unlocked and s-off. So I am not sure what I need to do. I was wondering if anyone could help. By the way I was using the One In All Kit v3.1 program off my computer to help me with all of my roms flashing.

Tsvallette said:
TAMPERED
RELOCKED
M7_WLW PVT SHIP S-ON RH
HBOOT-1.44.000
OpenDSP-v26.120.274.0202
eMMC-boot
May 8 2013,16:30:08:-1
Yes I do know that when I did the previous rom it will always say tampered but I don't know why it is relocked and S-ON. It should have been unlocked and s-off. So I am not sure what I need to do. I was wondering if anyone could help. By the way I was using the One In All Kit v3.1 program off my computer to help me with all of my roms flashing.
Click to expand...
Click to collapse
your phone is M7_WLV variant which means its not a gsm variant (M7_UL or M7_U) so you must use recoveries and roms specifically for your phone variant, M7_WLV
bootloader doesnt lock back by itself, so you probably did by mistake, same for s-on/s-off.
learn how to use adb and fastboot and get rid of this toolkit. always better to use adb and fastboot directly from the terminal
then
unlock bootloader
flash the correct recovery for your phone variant
flash a compatible rom for your phone variant
here is the coorect forum for your phone: http://forum.xda-developers.com/verizon-htc-one

I have a Sprint HTC One... And currently I am loading / downloading SDK and all of its components. I do appreciate in info. It seems as though that the programs that I am trying to use are older and outdated. The version of SDK that I had could have been one of the reasons why I am having issues connecting between the computer and my phone.

Tsvallette said:
I have a Sprint HTC One... And currently I am loading / downloading SDK and all of its components. I do appreciate in info. It seems as though that the programs that I am trying to use are older and outdated. The version of SDK that I had could have been one of the reasons why I am having issues connecting between the computer and my phone.
Click to expand...
Click to collapse
you don't need full sdk
Just need adb mini tool that's enough for all process
from HTC One

[Q] unable to repair partitions

For some weeks I have problems with my HTC One. At this point, I can run the setup of a custom ROM but It seems not to write to the system partition. I'm stuck at this moment.
[History]
I bought a HTC one, Used it for a year and wanted to install some applications who needed root access. Like my previous phones, I rooted it but the only difference is that I didn't installed a custom ROM. No need for that at this moment.
After some weeks there was a OTA update from HTC with Sense 6.0 or something. I was not able to install this update because at the restart it came in recovery mode and not in a predefined HTC state (I assume).
To get rid of the annoying "There is an update" message, I downloaded a custom ROM and installed it. So far, so good. After a while the phone run flat on the battery and after that moment I was not able to charge the phone again while android is started. The phone appears to be in USB host mode and is not able to charge. Only way was to charge the phone completly off. I asked a colleague who said that I had the wrong kernel.
I tried to install another ROM and there something went wrong. I assume that I formatted the data and the system partition and there was a moment that the phone run out of battery during installing a custom ROM. My colleague had my phone for several weeks and tried something. Didn't succeed in that. He tried RUU my phone but that failed because I'm S-ON
[And now]
I have access to the fastboot menu via the bootloader and I'm able to go into recovery (Clockworks 6.0.4.8). I had twrp but than I was not able to ADB my device
I was able to repair my data partition and pushed viperROM to my phone. I run the installation, at the end I got a message like "unfortunally, setup has stopped". I rebooted my phone and nothing. No Android.
So back to square one. now I've two options (imo)
* repair data partition / repair system partion and try again
* S-off my device and run RUU
I need help for both options, because I found a way to repair my data partition but not a way to repair system. And for option 2, I'm not able to use revone, firewater or so because there is no android on my phone.
can someone help me out with giving me instructions in the right direction or maybe a third option to go.
Phone:
**** TAMPERED ****
**** UNLOCKED ****
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4A.25.3263.21
openDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Feb 26 2014,12:32:09

Soft Bricked when resetting to stock

Hey all. Been browsing the forum to try to figure this out on my own, but I honestly don't understand this stuff enough to decipher what I need to do next (my experience is with x64-based PC systems).
So let's start off with the background as to what happened. Went back to using my Sprint HTC One as my Samsung S6 Edge decided to go for a dip in some water (yeah, I know). Anyway, I hadn't used the One in almost 2 years so as you can imagine, it was extremely out of date. I had forgotten that I had rooted the device and was running Cyanogenmod on it as well (with TWRP), so I attempted to reset everything to stock (stock ROM and recovery) in order to get OTA software and firmware updates.
After browsing the forum a bit, I decided to use the GuruReset with Aroma installer to reset everything to stock (running the tool through the TWRP recovery on the device itself). It seemed like it worked just fine, but upon reboot, it now just sits at the bootloader and none of the options really do anything (just reboots it back to the bootloader again). I will list a readout of what I see on my screen and hopefully you guys can help out a fellow nerd (and admitted Android noob) figure out this issue.
Btw, I have already attempted to use the HTC One Toolkit v3.3.0 (EoL) to no avail (whenever I try to use one of the options in the toolkit, the program crashes). Running Windows 10 on my PC.
---------------------------------------------------------------------------------------------------------
***TAMPERED***
***UNLOCKED***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.57.0000
OpenDSP-v32.120.274.0909
OS-5.05.651.2
eMMC-boot 2048MB
Sep 24 2014, 16:58:42.0

Nothing?
530+ views and no one has any ideas to throw around?

Have you tried pushing a custom rom on it and flashing it trough TWRP , that may work

Corbarum said:
Have you tried pushing a custom rom on it and flashing it trough TWRP , that may work
Click to expand...
Click to collapse
That's basically what I did to cause the problem in the first place. Had TWRP installed with Cyanogenmod from a couple years ago. Went to reset it to stock ROM and stock recovery. Now it just sits at the bootloader without doing anything. Doesn't even seem like there's a recovery on it at all.... Basically, the flash to stock failed from what I can tell and now there's nothing on it to load.

Try reFlashing TWRP on it, and look for the original rom
I still have no idea why you want the original recovery. but well, your choice
Also the thing is you might have just deleted the whole recovery , from what I know when you flash a custom recovery you overwrite the original recovery, so when you removed it completely
sorry , I am a newbie as well , I barely managed to fix my own m7 but now it works fine with cyanogenmod 13

DComm said:
Now it just sits at the bootloader without doing anything. Doesn't even seem like there's a recovery on it at all.... Basically, the flash to stock failed from what I can tell and now there's nothing on it to load.
Click to expand...
Click to collapse
Can you please post the output of "fastboot getvar all" (remove your imei, meid and serialno before posting)
What version of Guru reset rom did you flashed exactly (link) ?
I think it would be better to flash a RUU and have everything back to stock (wating for your getvar)
Btw twrp got overwritten by the stock recovery when flashing the Guru reset rom, that why twrp isn't there anymore.