Database Develop

[Q] Stuck at bootloader - Wiped OS - S-ON

Ok, so I am one of those idiots that accidentally wiped his OS. I was stuck in a boot loop and got a little click happy when I was choosing what to wipe during the reset process.
Here is my question (as everything I need is downloading)...
I am stuck at bootloader/recovery...and have S-ON. Will I be able to flash back to a stock (or any) ROM?
M7_WLS PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-1.00.20.0913_3
OpenDSP-v31.120.274.0617
OS-3.04.651.2
eMMC-boot 2048MB
I upgraded to 4.3, rooted and was doing fine until I got the dreaded reboot loop (Boot to OS and work for about 10 sec before rebooting again). Decided to do a factory reset, and like I said, got a little over zealous.
So, what I have read (at least I think) is that unless I get S-OFF, I am screwed. But how do I get S-OFF if I can't boot into the OS?
Someone, please help...been working on this all day with no luck.

jac1599 said:
Ok, so I am one of those idiots that accidentally wiped his OS. I was stuck in a boot loop and got a little click happy when I was choosing what to wipe during the reset process.
Here is my question (as everything I need is downloading)...
I am stuck at bootloader/recovery...and have S-ON. Will I be able to flash back to a stock (or any) ROM?
M7_WLS PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-1.00.20.0913_3
OpenDSP-v31.120.274.0617
OS-3.04.651.2
eMMC-boot 2048MB
I upgraded to 4.3, rooted and was doing fine until I got the dreaded reboot loop (Boot to OS and work for about 10 sec before rebooting again). Decided to do a factory reset, and like I said, got a little over zealous.
So, what I have read (at least I think) is that unless I get S-OFF, I am screwed. But how do I get S-OFF if I can't boot into the OS?
Someone, please help...been working on this all day with no luck.
Click to expand...
Click to collapse
You can do an adb sideload of a stock rooted ROM based on 3.04.651.2. The only time you need S-OFF is if you are flashing a ROM that is based on a different firmware (Sense 5.5 based ROMS). You can do a google search for adb sideload steps... its pretty straight forward.

Look HERE
Use the guide(if you want to learn some stuff ) or run the 3.04 RUU

bigdaddy619 said:
Look HERE
Use the guide(if you want to learn some stuff ) or run the 3.04 RUU
Click to expand...
Click to collapse
Wow, thanks guys. I have literally been searching THIS forum for an hour and somehow the thread with the RUU I need never showed up...of course if I had just clicked on the actual forum it would have taken me right to it.
Thanks again.

the.emilio said:
You can do an adb sideload of a stock rooted ROM based on 3.04.651.2. The only time you need S-OFF is if you are flashing a ROM that is based on a different firmware (Sense 5.5 based ROMS). You can do a google search for adb sideload steps... its pretty straight forward.
Click to expand...
Click to collapse
Sideload won't work for some reason

adb push it takes about 10 minutes so be patient
Sent from my HTCONE using XDA Premium 4 mobile app

[Q] Have I now botched my M7 beyond repair?

And I thought this would be a simple update from T-mobile Stock Rom to GPe Rom. The good news is I have another idential virgin HTC T-mobile M7 (bought two), and could happily make backups from that one if doing so would help here.
I have a T-mobile HTC One M7.
Here's what I did:
-installed twrp sucessfully
-unlocked bootloader sucessfully
-installed this rom vita twerp: http://forum.xda-developers.com/showthread.php?t=2341395
Then the problems, which I no doubt made worse with my efforts to fix them:
-experienced a bootloop after the ROM was sucessfully loaded
-tried to fix said bootloop by flashing the Guru Reset file ( http://www.htc1guru.com/downloads/stock-rom-downloads/ ) corresponding to my model, namely http://www.htc1guru.com/dld/guru_reset_m7_1-27-531-11-zip/ .
-Realized too late that this file wouldn't work with the touchscreen on my M7 because the firmware was newer than the rom. So now the touchscreen is completely non responsive.
That would be fine, except somehow in the process I broke both twep recovery (I can't load into recovery anymore), and the usb connection to my PC. (The bootloader screen says "fastboot usb" when the cable is connected, as I gather it should. But I can't find the device via adb.
Interestingly to me, I *can* still write from PC to my internal storage when I do a regular boot. So USB debugging is still enabled (indeed I can't disable it, because of the crippled touchscreen problem).
Here is my current info in the bootloader, line by line:
***TAMPERED***
***UNLOCKED***
M7_UL PUT SHIP S-ON RH
HBOOT-1.55.0000
RADIO 4A.17.3250.20
Open DSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Oct 14 2013, 17:31:32.0
I am now lost, after 4+ hours of work. Right after flashing a nook HD+ to CM 11 with no issues...maybe gave me a false sense of confidence?
Anyway, would *very much* appreciate any guidance you all can offer. TIA!

polphi said:
And I thought this would be a simple update from T-mobile Stock Rom to GPe Rom. The good news is I have another idential virgin HTC T-mobile M7 (bought two), and could happily make backups from that one if doing so would help here.
I have a T-mobile HTC One M7.
Here's what I did:
-installed twrp sucessfully
-unlocked bootloader sucessfully
-installed this rom vita twerp: http://forum.xda-developers.com/showthread.php?t=2341395
Then the problems, which I no doubt made worse with my efforts to fix them:
-experienced a bootloop after the ROM was sucessfully loaded
-tried to fix said bootloop by flashing the Guru Reset file ( http://www.htc1guru.com/downloads/stock-rom-downloads/ ) corresponding to my model, namely http://www.htc1guru.com/dld/guru_reset_m7_1-27-531-11-zip/ .
-Realized too late that this file wouldn't work with the touchscreen on my M7 because the firmware was newer than the rom. So now the touchscreen is completely non responsive.
That would be fine, except somehow in the process I broke both twep recovery (I can't load into recovery anymore), and the usb connection to my PC. (The bootloader screen says "fastboot usb" when the cable is connected, as I gather it should. But I can't find the device via adb.
Interestingly to me, I *can* still write from PC to my internal storage when I do a regular boot. So USB debugging is still enabled (indeed I can't disable it, because of the crippled touchscreen problem).
Here is my current info in the bootloader, line by line:
***TAMPERED***
***UNLOCKED***
M7_UL PUT SHIP S-ON RH
HBOOT-1.55.0000
RADIO 4A.17.3250.20
Open DSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Oct 14 2013, 17:31:32.0
I am now lost, after 4+ hours of work. Right after flashing a nook HD+ to CM 11 with no issues...maybe gave me a false sense of confidence?
Anyway, would *very much* appreciate any guidance you all can offer. TIA!
Click to expand...
Click to collapse
Looks like your OS is gone. Did you try and reflash twrp?
---------- Post added at 08:25 AM ---------- Previous post was at 07:55 AM ----------
24.531
polphi said:
And I thought this would be a simple update from T-mobile Stock Rom to GPe Rom. The good news is I have another idential virgin HTC T-mobile M7 (bought two), and could happily make backups from that one if doing so would help here.
I have a T-mobile HTC One M7.
Here's what I did:
-installed twrp sucessfully
-unlocked bootloader sucessfully
-installed this rom vita twerp: http://forum.xda-developers.com/showthread.php?t=2341395
Then the problems, which I no doubt made worse with my efforts to fix them:
-experienced a bootloop after the ROM was sucessfully loaded
-tried to fix said bootloop by flashing the Guru Reset file ( http://www.htc1guru.com/downloads/stock-rom-downloads/ ) corresponding to my model, namely http://www.htc1guru.com/dld/guru_reset_m7_1-27-531-11-zip/ .
-Realized too late that this file wouldn't work with the touchscreen on my M7 because the firmware was newer than the rom. So now the touchscreen is completely non responsive.
That would be fine, except somehow in the process I broke both twep recovery (I can't load into recovery anymore), and the usb connection to my PC. (The bootloader screen says "fastboot usb" when the cable is connected, as I gather it should. But I can't find the device via adb.
Interestingly to me, I *can* still write from PC to my internal storage when I do a regular boot. So USB debugging is still enabled (indeed I can't disable it, because of the crippled touchscreen problem).
Here is my current info in the bootloader, line by line:
***TAMPERED***
***UNLOCKED***
M7_UL PUT SHIP S-ON RH
HBOOT-1.55.0000
RADIO 4A.17.3250.20
Open DSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Oct 14 2013, 17:31:32.0
I am now lost, after 4+ hours of work. Right after flashing a nook HD+ to CM 11 with no issues...maybe gave me a false sense of confidence?
Anyway, would *very much* appreciate any guidance you all can offer. TIA!
Click to expand...
Click to collapse
Try running this 3.24.531.3 ruu, instructions on page.
http://forum.xda-developers.com/showthread.php?t=2375223

Thanks very much folks. Somehow, I was able to reflash twrp. From there, I realized that one mistake I made was overlooking that I needed s-off activated before flashing the ROM. (I think that was the beginning of my difficulties.)
Before reflashing twrp, I tried the RUU suggestion (TY!), but that needed bootloader turned back on, which in turn needed s-off...quite a procedure.
Anyway, With s-off done (thanks to the very persistent rumrunner_HTC_0.5.0.zip !), a second flash attempt of the rom at http://forum.xda-developers.com/showthread.php?t=2341395 worked seemingly perfectly. I now just trying to figure out whether I can get wifi calling working reliably (should be able to in theory, and at least one poster in that thread says he's done so).
Getting the HTC one properly modded is not a simple process relative to my prior experiences. I'm grateful for the help!

All of that work in the beginning was not needed. All you had to do was unlock bootloader, S-Off, change CID to 11111111, and run the GPE RUU from HTC. That's it. I had an ATT version that saw every different incarnation of software and it was that easy every time. Went from ATT to GPE, to T-Mobile, to Dev Edition and back without a problem. Well, red triangles of death be damned, but it never slowed me down, and the only time I got those was when I mis-matched the recovery img, or tried an update with a HBoot higher that 1.44, those are the only thinga to watch for. Make sure your ducks are in a row and update away. Stock recovery and lower Hboot worked awesome. I probably should put together a master file of everything I have for DL because I have it all and would make life so easy if someone hasn't done it already.

[Q] Bootloop and other problems

Hey guys,
So first sorry for my bad English but I’m from Germany And also I’m a total amateur with Android and roots and all that stuff.
Now back 2 topic.
So I bought my HTC One (M7) almost a year ago. I rooted it, unlocked it and also got S-Off. Yesterday I tried to get it back to stock so I could finally get some OTA-Updates. When I first entered the bootloader (if that’s the name of the white screen) everything seemed normal. But after I left my One got stuck in a Bootloop. I thing I know the cause for that but I will come back to that later.
My big problem is that while I’m in the bootloader my PC cant connect with the One. The device-manager says something like “cant start the device (code 10)”. So I cant use RUUs and the likes to get it back to stock. I tried all kinds of drivers and all USB-Slots I got. Nothings changes.
Another problem is, that my Phone is back to S-On, though I have no clue what I could have done to do that. And that brings me back to the Bootloop. After I wiped all my Data I could start my phone and had no Bootloop, everything worked just fine (though no APPs where left of course). But I got the message I should Install SuperSU. The second I did that I was back in the loop. So I think S-On and SuperSU is not a good combination. But since I cant connect the One via Fastboot I also have no clue how to S-Off it again.
If I just could connect the Phone with my PC via fastboot I would probably be able to get stock back. Does anyone know what the problem might be?
I don’t know if it helps but the bootloader says:
Tampered
Unlocked
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v31.120.274.0617
OS-2.24.401.1
eMMC-boot 2048MB
And I also use Windows 8.1

Change computer
Windows 7
from HTC One

Try on other PC. If you get it to connect to fastboot, keep that PC and run the ruu.
Sent from my HTC One using XDA Premium 4 mobile app

ATT HTC One M7 (I believe) - stuck in boot loop.

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.

Starts on Fastboot

Hi there
Hadn't used the phone for awhile so charged it up but whenever it starts it goes straight to Fastboot. No other screen appears.
I have gone in to HBOOT and done a factory reset and still the same.
It is in original state [no root etc].
The Fastboot page says
Software status modified
LOCKED
Security Warning
A11_UL PVT Ship S_ON
HBOOT-3.19.0.0000
Radio-01.02.010.U10251_37.08.40820
OS-1.10.61.7
eMMC-boot 1024MB
Nov 14 2015,01:20:53.0
Any help appreciated

Charles Collins said:
Hi there
Hadn't used the phone for awhile so charged it up but whenever it starts it goes straight to Fastboot. No other screen appears.
I have gone in to HBOOT and done a factory reset and still the same.
It is in original state [no root etc].
The Fastboot page says
Software status modified
LOCKED
Security Warning
A11_UL PVT Ship S_ON
HBOOT-3.19.0.0000
Radio-01.02.010.U10251_37.08.40820
OS-1.10.61.7
eMMC-boot 1024MB
Nov 14 2015,01:20:53.0
Any help appreciated
Click to expand...
Click to collapse
Seeing your Hboot info I'd say that at some point the bootloader was unlocked
Software status modified
LOCKED
Security Warning
Click to expand...
Click to collapse
And the phone probably had root but lets put that a side and take a look at your problem.
The only reason I can think of for the phone to go directly into fastboot is because the system partition is wiped, formated or the data is corrupted.
Your best choice at this point would be to try this out http://forum.xda-developers.com/desire-510/htc-desire-510-64-bit-eu--international-version/android-4-4-3-stock-os-debloated-64bit-t3361689. The guide is written by me so if you have any trouble or questions feel free to ask

Cheers, I'll take a look later.
Honestly, haven't done anything to the phone, though I can see why you might think I have. It has hardly been used and was sitting in a draw for some time. I've rooted other phones including the original HTC DESIRE but have moved onto Nexus phones and used a toolkit to root them.
Sent from my LG-H815 using XDA Free mobile app

Mistake!!