Database Develop

Phone randomly reboots after 20-30 seconds. Help?

Decided to rewrite this as the problem is different now, not as bad, but a lot weirder! I can't get my head round whats up
Description of Problem
Right, so simplistically, the phone boots up, and you can use it (sort of) for about 30 seconds, before it reboots. Whilst its on, you can open apps, but there is definite issues with menu's not opening and you cant set a wallpaper, but its almost fully working. Then without any warning it just reboots, and does the same thing again.
I'm just confused at how it can boot up and almost fully work before rebooting. Failing to boot at all or bootlooping at the start animation, I can understand that, but not this.
Video of the Problem
What Caused the Issue
Its been a week or so since it first died, so I cant fully remember exact things that happened (I appreciate this will not be helpful!)
I had converted the phone to a google edition version using the tutorial here: http://forum.xda-developers.com/showthread.php?t=2358781
Changed the MID and CID, flashed the bootloader, recovery and RUU and the whole thing worked great.
Then I got my Xperia Z, so wanted it back to stock to be sold. Problem is I locked the bootloader and went S-ON before flashing the stock bootloader because i'm an idiot! Then obviously it wouldn't boot due to locked bootloader and custom recovery, so I tried to flash stock RUU, failed naturally due to upgraded bootloader, so I unlocked the bootloader again, flashed stock, and now this happens
Things I've Tried
Factory Reset
Flashed Stock Roms (1.28 / 2.17 / 2.24 and google edition) via both flashable zip and CWM backups - flashing in fastboot doesnt work because of signature error
Revone to re S-OFF (On HBOOT 1.54 so get a -6 error)
Maybe some other things?
Does anyone have any ideas? Any help is appreciated at the moment, don't want to wait for S-OFF on 1.54 or a 2.24 RUU as that could mean a brick on my shelf for a while.

Can't you use revone to unlock? Or did you do s-on as well?
Edit: didn't mean to thank you there - this app is killing me..
Have you tried downgrading your firmware to give you the old 1.44 bootloader?
Sent from my HTC One using xda premium

redbull123 said:
Can't you use revone to unlock? Or did you do s-on as well?
Edit: didn't mean to thank you there - this app is killing me..
Have you tried downgrading your firmware to give you the old 1.44 bootloader?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
After hours of playing round I managed to get it to unlock the bootloader, so I should be fine, no idea what changed to make it work, but now it does. Out of interest for the future, how can you downgrade via fastboot with locked bootloader and S-ON?

dh2311 said:
Out of interest for the future, how can you downgrade via fastboot with locked bootloader and S-ON?
Click to expand...
Click to collapse
You can't downgrade when you're s-on.

iElvis said:
You can't downgrade when you're s-on.
Click to expand...
Click to collapse
Thats what I thought, hence why I got a bit concerned earlier. Phones not fixed yet, stuck in a bootloop but my internet is slow for downloading firmwares

If you're unlocked, you should be able to flash a new recovery, and from there a new rom. You've probably mucked up something with the OS, so hopefully a wipe and flash should do the trick.

dh2311 said:
After hours of playing round I managed to get it to unlock the bootloader, so I should be fine, no idea what changed to make it work, but now it does. Out of interest for the future, how can you downgrade via fastboot with locked bootloader and S-ON?
Click to expand...
Click to collapse
You can't - I thought you were s-off since I didn't read in your post that you went back to s-on, that's what I was asking..
Sent from my HTC One using xda premium

iElvis said:
If you're unlocked, you should be able to flash a new recovery, and from there a new rom. You've probably mucked up something with the OS, so hopefully a wipe and flash should do the trick.
Click to expand...
Click to collapse
The partition tables are ******, dont know why, sd card partition is unreadable and an ADB sideload still causes bootloops, this phone is really messed up and i dont know what i did
Usually I can figure the problem out. No idea now. Going to try and get the SD card back and restore an RUU from a CWM backup, then RUU it and should be fixed!
Luckily I have my trusty Xperia Z to use whilst I sort this out!

dh2311 said:
The partition tables are ******, dont know why, sd card partition is unreadable and an ADB sideload still causes bootloops, this phone is really messed up and i dont know what i did
Usually I can figure the problem out. No idea now. Going to try and get the SD card back and restore an RUU from a CWM backup, then RUU it and should be fixed!
Luckily I have my trusty Xperia Z to use whilst I sort this out!
Click to expand...
Click to collapse
Did you try formatting your sdcard partition from your computer? That sounds like the issue. Likely you corrupted something with all those changes. Remember revone is a hack, so it;s not 100% reliable.

iElvis said:
Did you try formatting your sdcard partition from your computer? That sounds like the issue. Likely you corrupted something with all those changes. Remember revone is a hack, so it;s not 100% reliable.
Click to expand...
Click to collapse
Genius! Dont know how i didnt think of that. Now i have an accessible SD card, just still bootlooping, itll work with the 1.28 backup and then the RUU will correct everything I've messed up

Okay, this needs a bump since this problem is weird now. The phone boots, with a number of roms, but after about 15 seconds, crashes and reboots every single time, no matter what ROM.
I have wiped system, data, cache everything, and it still does this!
Any ideas? an RUU is out of the question since i am on 2.17 and there is no RUU

dh2311 said:
Okay, this needs a bump since this problem is weird now. The phone boots, with a number of roms, but after about 15 seconds, crashes and reboots every single time, no matter what ROM.
I have wiped system, data, cache everything, and it still does this!
Any ideas? an RUU is out of the question since i am on 2.17 and there is no RUU
Click to expand...
Click to collapse
Sounds like a kernel or firmware conflict. Try flashing 2.24 and see if that helps.
Edit: n/m, just saw you're s-on. I think the problem is that you've got an incompatible mix of firmwares from trying to convert to GE. You need to get s-off again somehow.

iElvis said:
Sounds like a kernel or firmware conflict. Try flashing 2.24 and see if that helps.
Click to expand...
Click to collapse
Thats what I thought, tried 1.28, 2.17 and 2.24 with still no success. It doesnt make sense to me.Trying flashing CM10 as i saw someone else suggest
EDIT: same problem! :'(

dh2311 said:
Thats what I thought, tried 1.28, 2.17 and 2.24 with still no success. It doesnt make sense to me.Trying flashing CM10 as i saw someone else suggest
Click to expand...
Click to collapse
Are you flashing firmware or just roms?

iElvis said:
Are you flashing firmware or just roms?
Click to expand...
Click to collapse
I cant flash RUU's becuase of my firmware version (2.17) flashed 1.28 via a CWM backup and the other 2 via ARHD stock odexed roms, best I think i can get becuase theres no 2.17 or 2.24 RUU that I know of

dh2311 said:
I cant flash RUU's becuase of my firmware version (2.17) flashed 1.28 via a CWM backup and the other 2 via ARHD stock odexed roms, best I think i can get becuase theres no 2.17 or 2.24 RUU that I know of
Click to expand...
Click to collapse
I don't mean RUUs, I mean one of the custom firmware packages that you flash in fastboot. But you need to be s-off to do that. You did something like this when you converted to GE.
This is one of the risks of going s-off, unfortunately. It lets you do stuff to your phone that can really screw it up.

iElvis said:
I don't mean RUUs, I mean one of the custom firmware packages that you flash in fastboot. But you need to be s-off to do that. You did something like this when you converted to GE.
This is one of the risks of going s-off, unfortunately. It lets you do stuff to your phone that can really screw it up.
Click to expand...
Click to collapse
Going back to S-ON was my mistake, if this phone was still S-OFF I'd have been able to fix it. But i still cant explain why it bootloops? All I did was change the MID and CID, which are now back to stock (HTC_001) and (PN07100) but it still has the Google edition bootloader, surely if that was the issue then it wouldnt boot past the bootloader, so where does the issue lie?

dh2311 said:
Going back to S-ON was my mistake, if this phone was still S-OFF I'd have been able to fix it. But i still cant explain why it bootloops? All I did was change the MID and CID, which are now back to stock (HTC_001) and (PN07100) but it still has the Google edition bootloader, surely if that was the issue then it wouldnt boot past the bootloader, so where does the issue lie?
Click to expand...
Click to collapse
It could be any number of things. You changed a lot going to GE, and with S-on, the phone is now doing all its usual security checks. Something somewhere got bollixed up. It could be the GE firmware is conflicting with your CID or MID.
One way or another, you've got to get back to s-off.

iElvis said:
It could be any number of things. You changed a lot going to GE, and with S-on, the phone is now doing all its usual security checks. Something somewhere got bollixed up. It could be the GE firmware is conflicting with your CID or MID.
One way or another, you've got to get back to s-off.
Click to expand...
Click to collapse
Thats the solution. Or a 2.24 RUU from HTC could also do it. But revone requires a booting phone, which mine cant do, doesnt work out of recovery unfortunately. and moonshine is only for older versions. Tempted to just put this phone on a shelf and wait for an RUU. Carry on using my Xperia Z

Dont know if this will be of any help for sorting the issue, but this is all the hboot info from getvar all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.17.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: <removed for safety>
(bootloader) imei: <removed for safety>
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN071000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3821mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-21fde4b846
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Definitely cant seem to get this to work, upon booting i get lots of force closes like the messaging app and contacts storage. That a clue for anyone?
Or if anyone knows how to S-Off without a working F/W that would be a help but I doubt it can be done

[Q] I've fallen and I can't get up!

I've successfully played with custom roms for years, but I managed to completely corrupt my Sprint HTC One M7 and I'm having a hard time figuring out how to get it back to being a working phone.
It's rooted and unlocked. I think a bad download of a recovery or rom corrupted either the storage or firmware or both.
When I first rooted it, I did have some problems. However, I was able to recover and successfully ran the Revolution ROM for about a month. I wanted to try the Viper ROM and that action (not the ROM itself, of course) put the device into its current bricked state.
I can still flash different recoveries. I can install new ROMs. I've even attempted to flash stock recoveries and run a factory reset to completely reset the phone's partitions. However the phone is unusable. I even have a OTG cable to grab ROMS from a USB stick. TWRP doesn't recognize the internal storage of the phone, but it does recognize the USB stick on the OTG cable. ClockWork can see all of the storage on the phone.
I have tried relocking and running RUUs, but I think I am doing it incorrectly because my phone is still S-ON and if that is the case, you have to find the right version of RUU that is an upgrade rather than a downgrade of the phone. The RUUs always error out. Perhaps someone will be able to provide a correct link as I have screen pictures and Model ID info I can include.
Behavior: As I try to show in the pictures I've attached, I can install customer ROMS or alleged stock ROMS onto the phone. When the process completes, I am presented with the stock lock screen for the M7. When I swipe the screen I am presented with a white HTC screen that is similar to the boot screen, but note there is no other writing. This is not the boot screen. Rather, it is all you get.
If you are tethered to a PC, you can see the storage on your list of drives.
However, after about 90 seconds, the phone auto reboots, and you are in a loop.
The phone is 13 months old, so I don't think I can just relock it and walk into a Sprint store and ask for a replacement.
Moreover, I think this is fixable, I just don't know how quite yet.
Thanks for those pros out there who can help me get out of this mess of my own making.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.651.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4242mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.035s

It's not bricked.....
Go Here and follow the instructions exactly===============>http://forum.xda-developers.com/showthread.php?t=2250904

There is no RUU for 4.06.651.9.
This guide will get you fixed up use either the 4.06.651.9 or 5.03.651.3 s-on firmware
http://forum.xda-developers.com/showthread.php?t=2503646

twisteddan said:
It's not bricked.....
Go Here and follow the instructions exactly===============>http://forum.xda-developers.com/showthread.php?t=2250904
Click to expand...
Click to collapse
That RUU won't work it's super old

BD619 said:
That RUU won't work it's super old
Click to expand...
Click to collapse
Oh ok.....Sorry about that.

twisteddan said:
Oh ok.....Sorry about that.
Click to expand...
Click to collapse
No harm no foul
Since he/she is s-on they need to run an RUU equal to or newer then their main version

BD619 said:
No harm no foul
Since he/she is s-on they need to run an RUU equal to or newer then their main version
Click to expand...
Click to collapse
The question is, does such an RUU exist?
If it does not, is there a stock or custom ROM Zip that, while not packaged in an RUU, might work? Although if that were the case, the ROM's I've already tried to use might actually work.
Or, should I attempt to S-Off the phone (something I've never done before) in order to try an RUU to work?
Thanks for your initial answers. Sounds like I don't have enough to move forward quite yet.

BD619 said:
No harm no foul
Since he/she is s-on they need to run an RUU equal to or newer then their main version
Click to expand...
Click to collapse
I googled the version number 4.06.651.9 and came up with this:
http://forum.xda-developers.com/showthread.php?t=2687690
What do you think?

bethesdaadk said:
I googled the version number 4.06.651.9 and came up with this:
http://forum.xda-developers.com/showthread.php?t=2687690
What do you think?
Click to expand...
Click to collapse
This is not an RUU,it's firmware, the the guide I linked to will get you fixed up.
I'm actually surprised you were able to run ARHD for so long without issues, it's most likely the cause of the problems.
Edit: I noticed I did not include the 4.06.651.9 firmware in the rescue guide...it's now added.

BD619 said:
This is not an RUU,it's firmware, the the guide I linked to will get you fixed up.
I'm actually surprised you were able to run ARHD for so long without issues, it's most likely the cause of the problems.
Edit: I noticed I did not include the 4.06.651.9 firmware in the rescue guide...it's now added.
Click to expand...
Click to collapse
I have downloaded two firmwares from your guide. the 4.06.651.9 and the 5.03.651.3
The biggest problem I am currently having is downloading the TWRP recovery without an error. I'm even using download manager on one of my laptops and it sticks at 99%. This is probably how I got into trouble in the first place. I'm attempting 2.7.1.0
Is there a solid version of TWRP earlier that should try and download instead?

bethesdaadk said:
I have downloaded two firmwares from your guide. the 4.06.651.9 and the 5.03.651.3
The biggest problem I am currently having is downloading the TWRP recovery without an error. I'm even using download manager on one of my laptops and it sticks at 99%. This is probably how I got into trouble in the first place. I'm attempting 2.7.1.0
Is there a solid version of TWRP earlier that should try and download instead?
Click to expand...
Click to collapse
I use this one http://forum.xda-developers.com/showthread.php?t=2651035

BD619 said:
I use this one http://forum.xda-developers.com/showthread.php?t=2651035
Click to expand...
Click to collapse
I've tried to parse out your directions to make sure I do this correctly. Can you please check to make sure I'm understanding you correctly?
First step is to flash the firmware:
I've downloaded 4.06.651.9 s-on firmware per your suggestion becuase that's the current version of my phone.
Then I need to rename it to just plain firmware.zip
Then on the phone:
Boot to bootloader and lock the bootloader by typing:
fastboot oem lock
in my ADB/Fastboot dos session.
Then use these commands:
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Fastboot reboot-bootloader
which will flash the firmware.
Then: If you get this error after the second command (most likely will)
failed 90 hboot pre-update! please flush image again immediately
press the UP Arrow on your keyboard and press enter to issue the command again. Essentially, you are flashing the firmware a second time.
Then, unlock the bootloader again
fastboot flash unlocktoken Unlock_code.bin
Here's the part where I'm a little uncertain. You state:
8a. If you are using the 4.06.651.4 s-on firmware I would suggest you push this Stock Rooted Odexed Rom to your device or it may not boot.
8b. After flashing the 4.06.651.4 rom you will most likely need to flash the latest radio because the 4.06 firmware does not have a radio included find it HERE
Since I am flashing the 4.06.651.9 s-on firmware and not the 4.06.651.4 s-on firmware, do I need to used that suggested Rom? Or can I use any other standard Rom?
Also, earlier in the guide, you state:
If you are already on 4.06.651.4 or 4.06.651.9 you will have to flash the 3.05.651.6 s-off firmware first...reason being is the 4.06 s-off firmware does not have the latest radio included
Do I need to worry about that since I'm flashing the s-on firmware and not the s-off firmware?
Thanks for your help on this. If I were this careful the first time around, maybe I wouldn't have gotten to this point. Luckily, my old Evo4G is in good condition so I've put it into service while I try and fix the HTC One.

bethesdaadk said:
I have downloaded two firmwares from your guide. the 4.06.651.9 and the 5.03.651.3
The biggest problem I am currently having is downloading the TWRP recovery without an error. I'm even using download manager on one of my laptops and it sticks at 99%. This is probably how I got into trouble in the first place. I'm attempting 2.7.1.0
Is there a solid version of TWRP earlier that should try and download instead?
Click to expand...
Click to collapse
tdhite's 2.7.0.9 worked fine for me?

Since I am flashing the 4.06.651.9 s-on firmware and not the 4.06.651.4 s-on firmware, do I need to used that suggested Rom? Or can I use any other standard Rom?
Click to expand...
Click to collapse
I would use this rom just to get you up and running and you can then make a backup of the stock rom.
If you are already on 4.06.651.4 or 4.06.651.9 you will have to flash the 3.05.651.6 s-off firmware first...reason being is the 4.06 s-off firmware does not have the latest radio included
Click to expand...
Click to collapse
This only applies to folks that are s-off.

BD619 said:
I would use this rom just to get you up and running and you can then make a backup of the stock rom.
This only applies to folks that are s-off.
Click to expand...
Click to collapse
I will try and do this tomorrow and will let you know it goes.
Interestingly enough, I just saw someone with an HTCONE M7 tonight running Sense 6. I was floored at how different and sleek it looked. I hope that once I have a working phone again, I'll be able to get all the way to Sense 6.
But until then, I have to get this one working.
Thanks.

bethesdaadk said:
I will try and do this tomorrow and will let you know it goes.
Interestingly enough, I just saw someone with an HTCONE M7 tonight running Sense 6. I was floored at how different and sleek it looked. I hope that once I have a working phone again, I'll be able to get all the way to Sense 6.
But until then, I have to get this one working.
Thanks.
Click to expand...
Click to collapse
Well the 5.03.651.3 firmware and rom are sense 6

BD619 said:
Well the 5.03.651.3 firmware and rom are sense 6
Click to expand...
Click to collapse
Ok. So I am reporting back. It's a good news / bad news kind of situation.
I relocked the device.
Flashed the 4.06.651.9_firmware
It took two times exactly as predicted and was successful.
I had a little trouble re-unlocking it again, because I needed to resubmit the device of a new unlock.bin. The process changed the token. I suppose that makes sense.
I then flashed TWRP. On a positive note, TWRP allowed me to mount selections that were previously un-mountable.
However, when I put the unit into ADB Sideload mode and then attempted to adb side load from my PC, adb still did not recognize the device. Fastboot does, but adb doesn't.
However, since I had an OTG cable, I merely used that to have TWRP install the stock ROM you suggested.
It finished. I rebooted.
And it's still un-usable. Boots with the nice Sprint screen. One difference, I get an error about htcdialer freezing. I get the stock lock screen. I unlock to a white HTC screen.
The device shows up in device manager as my HTC but I don't see it as a listed drive anymore.
And the device reboots after about 2 minutes.
So, like I said, some success, but it still isn't usable.
Suggestions?

bethesdaadk said:
Ok. So I am reporting back. It's a good news / bad news kind of situation.
I relocked the device.
Flashed the 4.06.651.9_firmware
It took two times exactly as predicted and was successful.
I had a little trouble re-unlocking it again, because I needed to resubmit the device of a new unlock.bin. The process changed the token. I suppose that makes sense.
I then flashed TWRP. On a positive note, TWRP allowed me to mount selections that were previously un-mountable.
However, when I put the unit into ADB Sideload mode and then attempted to adb side load from my PC, adb still did not recognize the device. Fastboot does, but adb doesn't.
However, since I had an OTG cable, I merely used that to have TWRP install the stock ROM you suggested.
It finished. I rebooted.
And it's still un-usable. Boots with the nice Sprint screen. One difference, I get an error about htcdialer freezing. I get the stock lock screen. I unlock to a white HTC screen.
The device shows up in device manager as my HTC but I don't see it as a listed drive anymore.
And the device reboots after about 2 minutes.
So, like I said, some success, but it still isn't usable.
Suggestions?
Click to expand...
Click to collapse
Did you remember to flash the radio?

BD619 said:
Did you remember to flash the radio?
Click to expand...
Click to collapse
I did not flash the radio. I may have been confused, but I thought I didn't need to because I was S-On, not S-Off. At this point, it doesn't matter though, so I'll try it.
Do I need to go through the same steps as flashing the firmware?
Relock.
rebootRUU
Or can I just fastboot flash the radio?
Thanks.

bethesdaadk said:
I did not flash the radio. I may have been confused, but I thought I didn't need to because I was S-On, not S-Off. At this point, it doesn't matter though, so I'll try it.
Do I need to go through the same steps as flashing the firmware?
Relock.
rebootRUU
Or can I just fastboot flash the radio?
Thanks.
Click to expand...
Click to collapse
Nope just flash the radio from recovery

[Q] HTC One M7 BOOTLOADER SAYS LOCKED

HELP NEEDED
My HTC one m7 is stuck at locked bootloader...no matter what I do it remains locked....the rom is the stock 4.1 jb...it is s-ON...so far I have tried this:
Tried unlocking from HTC DEV
Tried Towelroot
when I unlock using htc dev the splash screen appears...after pressing yes, it reboots and resets everything but no unlocked bootloader....towelroot also doesn't work....
adb also not working...
previously it was s-OFF and I had installed viperONE....

Faisal0000 said:
HELP NEEDED
My HTC one m7 is stuck at locked bootloader...no matter what I do it remains locked....the rom is the stock 4.1 jb...it is s-ON...so far I have tried this:
Tried unlocking from HTC DEV
Tried Towelroot
when I unlock using htc dev the splash screen appears...after pressing yes, it reboots and resets everything but no unlocked bootloader....towelroot also doesn't work....
adb also not working...
previously it was s-OFF and I had installed viperONE....
Click to expand...
Click to collapse
Is USB Debugging enabled?
Is Fast boot in Power disabled?

Faisal0000 said:
HELP NEEDED
My HTC one m7 is stuck at locked bootloader...no matter what I do it remains locked....the rom is the stock 4.1 jb...it is s-ON...so far I have tried this:
Tried unlocking from HTC DEV
Tried Towelroot
when I unlock using htc dev the splash screen appears...after pressing yes, it reboots and resets everything but no unlocked bootloader....towelroot also doesn't work....
adb also not working...
previously it was s-OFF and I had installed viperONE....
Click to expand...
Click to collapse
was the device converted to GPE at any point when it was s-off. Or is it GPE originally?
Have you tried
Code:
fastboot oem unlock
Also the output from
Code:
fastboot getvar all
would be helpful, please edit out your serial and imei before posting :good:
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

majmoz said:
Is USB Debugging enabled?
Is Fast boot in Power disabled?
Click to expand...
Click to collapse
yes usb debugging is enabled...and fastboot is disabled...

Danny201281 said:
was the device converted to GPE at any point when it was s-off. Or is it GPE originally?
Have you tried
Code:
fastboot oem unlock
Also the output from
Code:
fastboot getvar all
would be helpful, please edit out your serial and imei before posting :good:
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
the device was originally sense...it wasn't converted to gpe...
fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 3773mV
(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

fastboot oem unlock doesnt work...

Faisal0000 said:
fastboot oem unlock doesnt work...
Click to expand...
Click to collapse
Ok I notice you have a very new radio compared to you hboot version. This unlocking problem normally happens when an s-off device is set back to s-on while something is still customized in the firmware. Could be anything even as little as a custom boot splash. Normally happens after botched gpe conversion. That's why I asked about that
What reason did you go back to s-on. Is it possible you had custom firmware at the time?
I only know of one case where the bootloader was ever unlocked again and they had to use Sunshine app. Which unlocked the bootloader and returned s-off. Obviously this is a good option If the phone is booting.
Although normally the device has been on the latest firmware with no ruu available. Not the case for your device, you could try flashing the 3.62.401.1.zip firmware from here.
http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/ with below instructions.
Rename the 3.62.401.1.zip to firmware.zip and put it in your fastboot folder.
Reboot the phone to the bootloader and Connect fastbootusb. Now open your Fastboot command line and type
Code:
fastboot erase cache
Code:
fastboot oem lock
you can skip this if already locked
Code:
fastboot reboot-bootloader
Code:
fastboot oem rebootRUU
< --- case sensitive.
The phone will reboot to a black screen with a Silver HTC LOGO. This is RUU mode. Now we're going to flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash will be short. It's just a preupdate preparing the hboot for the new firmware. So we need to do the same command again.
Code:
fastboot flash zip firmware.zip
The second flash will take a little longer and this time it will flash the full firmware. The progress bar on the phone screen will not reach 100% this is normal as long as the command window has completed its output the flash is done.
Code:
fastboot reboot-bootloader
Make sure fastboot usb is connected and run the ruu.exe on your pc
http://www.htc1guru.com/2014/03/android-ruu-europe/ This will return you to complete stock 4.19.401.9. After which you should get a new unlock code from HTC dev and try unlock again.
Good luck :good:
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
Ok I notice you have a very new radio compared to you hboot version. This unlocking problem normally happens when an s-off device is set back to s-on while something is still customized in the firmware. Could be anything even as little as a custom boot splash. Normally happens after botched gpe conversion. That's why I asked about that
What reason did you go back to s-on. Is it possible you had custom firmware at the time?
I only know of one case where the bootloader was ever unlocked again and they had to use Sunshine app. Which unlocked the bootloader and returned s-off. Obviously this is a good option If the phone is booting.
Although normally the device has been on the latest firmware with no ruu available. Not the case for your device, you could try flashing the 3.62.401.1.zip firmware from here.
http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/
Then flash this ruu. http://www.htc1guru.com/2014/03/android-ruu-europe/ This will return you to complete stock 4.19.401.9. After which you should get a new unlock code from HTC dev and try unlock again.
Good luck :good:
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
First of all thanks...
P.S the bootloader is locked and I cant flash the RUU...
neither do I have a custom recovery and root...so i cant install a guru reset...
the phone is booting and working fine but no root...
if I get root by towelroot I could use flashify to flash recovery without unlocking the bootloader and then restore it to stock...but the problem is that tr is not working...tried all versions...it worked before...
I did it s-ON to return it to stock so I could sale it...I was using viperone with elemental X kernel...I foolishly cleared everything also the system and... didnt notice...after that I flashed the stock recovery and gave the command for s-ON and then locked the bootloader...but the phone didnt boot...I didint knew what happened so I sent it for repair in a local shop...I dont know what they did but when I got it back it was LOCKED not RELOCKED....I dont what RUU did they flash because whenever I insert a sim card it says network locked...it happens with every sim card and whatever code I insert it says succesfully unlocked from network and rebooting...but still remains network locked...I was trying to unlock bootloader to flash the correct RUU to get the phone back in order but to no avail...now I've checked every local shop but they're out of options....so XDA is my only hope now....

Faisal0000 said:
First of all thanks...
P.S the bootloader is locked and I cant flash the RUU...
neither do I have a custom recovery and root...so i cant install a guru reset...
the phone is booting and working fine but no root...
if I get root by towelroot I could use flashify to flash recovery without unlocking the bootloader and then restore it to stock...but the problem is that tr is not working...tried all versions...it worked before...
I did it s-ON to return it to stock so I could sale it...I was using viperone with elemental X kernel...I foolishly cleared everything also the system and... didnt notice...after that I flashed the stock recovery and gave the command for s-ON and then locked the bootloader...but the phone didnt boot...I didint knew what happened so I sent it for repair in a local shop...I dont know what they did but when I got it back it was LOCKED not RELOCKED....I dont what RUU did they flash because whenever I insert a sim card it says network locked...it happens with every sim card and whatever code I insert it says succesfully unlocked from network and rebooting...but still remains network locked...I was trying to unlock bootloader to flash the correct RUU to get the phone back in order but to no avail...now I've checked every local shop but they're out of options....so XDA is my only hope now....
Click to expand...
Click to collapse
If the phone is s-on the bootloader must be LOCKED or RELOCKED to run an ruu or flash firmware
you can only flash Unlocked while s-off. So it should work. If it fails post the error :good:
I've edited my previous post to include instructions for flashing
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
If the phone is s-on the bootloader must be LOCKED or RELOCKED to run an ruu or flash firmware
you can only flash Unlocked while s-off. So it should work. If it fails post the error :good:
I've edited my previous post to include instructions for flashing
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
Thanks a lot man....but it was showing some error and so I got a new htc one, this thread is useless now so if anyone can delete it plz delete it...
Sent from my HTC One using XDA Free mobile app

[Q] Updating from REALLY OLD firmware.

A couple years ago, I unlocked/TWRPed/rooted/ROMed my phone - but I haven't touched it since. As a result, I haven't updated my firmware in a LONG time. I've been reading all afternoon, but I could use a little bit of help. Here's what I'm thinking my steps will be:
nandroid backup - I can't seem to get the phone mounted as a drive on my Mac, and HTC Sync Manager keeps crashing, but I'll figure out some way to pull the backup off...
S-OFF my phone - would you recommend Rumrunner? Any particular guide?
Using fastboot and this guy's advice, flash a bunch of firmwares onto my phone. Question: which firmwares do I need, and did how you know? I have to match my CID and MID, but how do I find all the firmware downloads that I've skipped? I don't suppose everyone flashes new versions of firmware the moment they're released, but I'm not sure how people "catch up"...
Flash the most recent TWRP and version of my custom ROM
I'd love to get some answers to the above questions, and to hear any advice you might have! Thanks, community - you rock! Here's some relevant information:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.15
(bootloader) version-misc: PVT SHIP S-ON
...
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4201mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT

mynnx said:
A couple years ago, I unlocked/TWRPed/rooted/ROMed my phone - but I haven't touched it since. As a result, I haven't updated my firmware in a LONG time. I've been reading all afternoon, but I could use a little bit of help. Here's what I'm thinking my steps will be:
nandroid backup - I can't seem to get the phone mounted as a drive on my Mac, and HTC Sync Manager keeps crashing, but I'll figure out some way to pull the backup off...
S-OFF my phone - would you recommend Rumrunner? Any particular guide?
Using fastboot and this guy's advice, flash a bunch of firmwares onto my phone. Question: which firmwares do I need, and did how you know? I have to match my CID and MID, but how do I find all the firmware downloads that I've skipped? I don't suppose everyone flashes new versions of firmware the moment they're released, but I'm not sure how people "catch up"...
Flash the most recent TWRP and version of my custom ROM
I'd love to get some answers to the above questions, and to hear any advice you might have! Thanks, community - you rock! Here's some relevant information:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.15
(bootloader) version-misc: PVT SHIP S-ON
...
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4201mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Click to expand...
Click to collapse
OK well your on the right track rumrunner should work for you to gain s-off. And that should be your first priority. Although rumrunner was developed for hboot 1.54 and 1.55 so if you run into issues you may need to flash the first 2 updates and a stock rom for it to work.
Once you have s-off which firmware to use depends largely on your situation. Your device is currently running At&t firmware. Are you still using the device on the At&t network? If not then it would probably be better to convert to Dev Edition or HTC Unbranded firmware.
Also with s-off it can be much easier to update the device using RUUs rather than just flashing firmware.zips.
Sent from my SM-T230 using Tapatalk

I was told that I shouldn't skip firmware updates. Is that true?
I'm on hboot 1.44, so I don't anticipate any problems with S-OFFing, right?

mynnx said:
I was told that I shouldn't skip firmware updates. Is that true?
I'm on hboot 1.44, so I don't anticipate any problems with S-OFFing, right?
Click to expand...
Click to collapse
That's right skipping firmware updates can brick your phone. Unless your using an RUU. RUUs contain a full firmware package so these can be used to skip a version but usually you need to be close to the RUU version for them to flash. Firmware updates however only include the updated part of the firmware. Skipping firmware updates can leave you with firmware incompatibility forcing the device into QHSUB USB DLOAD mode.
Try rumrunner with your current setup and see what happens. If it fails then make sure you have your backups safe. And relock your bootloader and flash this ruu. http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
This will update your device to hboot 1.55 with a Jellybean 4.3 stock rom perfect for rumrunner. It will wipe your internal storage though so make sure you've got everything you want to keep backup.
Instructions....
Boot device to the bootloader and connect fastboot usb. In the command window type
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
The bootloader should now read ***RELOCKED***
Make sure that it is in fastbootusb mode. Then launch the ruu.exe on your pc. Follow the instructions to update the phone. Once that's done unlock the bootloader and try rumrunner again. :good:
Sent from my SM-T230 using Tapatalk

Danny - thanks!
I don't have access to a PC, so I need a .zip to flash - is that the most recent RUU?
Can you (or anyone else) hook me up with the list of .zip RUUs that I need to flash to get to the most current version of my firmware?
Also, I shouldn't need to re-lock with S-OFF, right?

mynnx said:
Danny - thanks!
I don't have access to a PC, so I need a .zip to flash - is that the most recent RUU?
Can you (or anyone else) hook me up with the list of .zip RUUs that I need to flash to get to the most current version of my firmware?
Click to expand...
Click to collapse
Are you still on at&t ?
Also, I shouldn't need to re-lock with S-OFF, right?
Click to expand...
Click to collapse
right

mynnx said:
Danny - thanks!
I don't have access to a PC, so I need a .zip to flash - is that the most recent RUU?
Can you (or anyone else) hook me up with the list of .zip RUUs that I need to flash to get to the most current version of my firmware?
Also, I shouldn't need to re-lock with S-OFF, right?
Click to expand...
Click to collapse
It's not the most recent ruu no, but if you flash anything newer you will then need to use sunshine to s-off and it will cost you $25.
Any firmware or RUU will require access to a pc with fastboot. You can't flash firmware from recovery like a Rom. It has to be flashed in RUU mode.
You don't need to relock if your s-off but I think you will need to first update the device to hboot 1.55 before rumrunner will work. You can do that with this RUU then gain s-off then the sky's the limit
Sent from my M7 Running ARHD 92.x

Danny201281 said:
It's not the most recent ruu no, but if you flash anything newer you will then need to use sunshine to s-off and it will cost you $25.
Any firmware or RUU will require access to a pc with fastboot. You can't flash firmware from recovery like a Rom. It has to be flashed in RUU mode.
You don't need to relock if your s-off but I think you will need to first update the device to hboot 1.55 before rumrunner will work. You can do that with this RUU then gain s-off then the sky's the limit
Sent from my M7 Running ARHD 92.x
Click to expand...
Click to collapse
I should have been more specific - I don't have access to a Windows PC, so I can't run the .exe RUUs, but I can totally fastboot them on as .zip's.
Can you explain the need to use Sunshine with newer RUUs? And why/how it's necessary to update hboot to use rumrunner?

mynnx said:
I should have been more specific - I don't have access to a Windows PC, so I can't run the .exe RUUs, but I can totally fastboot them on as .zip's.
Can you explain the need to use Sunshine with newer RUUs? And why/how it's necessary to update hboot to use rumrunner?
Click to expand...
Click to collapse
There are different methods for gaining s-off depending on your hboot version.
First we had Revone and Moonshine. Which was developed for hboot 1.44 then HTC released a patched firmware to prevent it from working. [You currently have the patched firmware. So these are not an option.]
Then there is Rumrunner. Which was developed for hboot 1.54 and updated for 1.55 and 1.56. Then again HTC released patched firmware to prevent Rumrunner from working with hboot 1.56. But it still should work with 1.54 and 1.55. [Since the suggested RUU should update your device to 1.55. So rumrunner should then work with the device.]
Then came Firewater. Which was developed for 1.56 and 1.57. But for reasons of his own the dev discontinued support of Firewater. [Subsequently it no longer works at all.]
Then came Sunshine App developed for hboot 1.57 and above. Very simple to use, but the devs decided to charge a license for for it so you have to pay $25 to use it. [While controversial the s-off devs have worked hard for us over the years. So why shouldn't they.]
So you see you basically have 2 choices to s-off. rumrunner (free to use only works with hboot 1.54 and 1.55).
Sunshine App ( in theory should work with any hboot version. But costs $25)
I'm not sure if that ruu is available in zip format I'll see what I can find and post the links here :good: you may need to manually update firmware and flash a stock Rom to use rumrunner. Or if you can spare the 25 bills just use sunshine for a one click solution :good:
Sent from my M7 Running ARHD 92.x

alray said:
Are you still on at&t ?
right
Click to expand...
Click to collapse
Yeah, I'm still on AT&T.

mynnx said:
Yeah, I'm still on AT&T.
Click to expand...
Click to collapse
OK try this one. http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_50_cingular_3-10-502-2-zip/ ATT RUU zip. I don't know if it's been modified in any way though. If it has it will fail to flash because it's not signed. And your s-on. If it's signed it should flash just fine if you relock the bootloader.
Sent from my SM-T230 using Tapatalk

Danny201281 said:
There are different methods for gaining s-off depending on your hboot version.
First we had Revone and Moonshine. Which was developed for hboot 1.44 then HTC released a patched firmware to prevent it from working. [You currently have the patched firmware. So these are not an option.]
Then there is Rumrunner. Which was developed for hboot 1.54 and updated for 1.55 and 1.56. Then again HTC released patched firmware to prevent Rumrunner from working with hboot 1.56. But it still should work with 1.54 and 1.55. [Since the suggested RUU should update your device to 1.55. So rumrunner should then work with the device.]
Then came Firewater. Which was developed for 1.56 and 1.57. But for reasons of his own the dev discontinued support of Firewater. [Subsequently it no longer works at all.]
Then came Sunshine App developed for hboot 1.57 and above. Very simple to use, but the devs decided to charge a license for for it so you have to pay $25 to use it. [While controversial the s-off devs have worked hard for us over the years. So why shouldn't they.]
So you see you basically have 2 choices to s-off. rumrunner (free to use only works with hboot 1.54 and 1.55).
Sunshine App ( in theory should work with any hboot version. But costs $25)
I'm not sure if that ruu is available in zip format I'll see what I can find and post the links here :good: you may need to manually update firmware and flash a stock Rom to use rumrunner. Or if you can spare the 25 bills just use sunshine for a one click solution :good:
Sent from my M7 Running ARHD 92.x
Click to expand...
Click to collapse
Correct me if I'm wrong; I want to make sure I'm understanding you correctly:
hboot 1.44 with my firmware version isn't possible to S-OFF
Flashing RUUs will update my version of hboot, and the RUU you suggested is S-OFFable by rumrunner
I can't normally flash RUUs without S-OFF, but the RUU you suggested matches my CID and MID so it will work
Once I'm at hboot 1.55 after flashing that RUU, and S-OFFed after rumrunner, I should be able to flash more recent RUUs without losing my S-OFF
Why / how might I need to flash firmware manually and flash a stock ROM to use rumrunner?

mynnx said:
Correct me if I'm wrong; I want to make sure I'm understanding you correctly:
hboot 1.44 with my firmware version isn't possible to S-OFF <----- Correct because you have the latest 1.44 firmware as indicated by .15 on the end of your OS Version
Flashing RUUs will update my version of hboot, and the RUU you suggested is S-OFFable by rumrunner <----- Correct the Ruu will update your firmware hboot and rom completely stock. Rumrunner should work with this combination.
I can't normally flash RUUs without S-OFF, but the RUU you suggested matches my CID and MID so it will work. You can flash ruu's with s-on but the ruu must match your CiD, MiD You must relock the bootloader and the ruu must be unmodified and carry a HTC signiture. .exe ruu's are all HTC signed, Ruu zips can be modified so are not all guaranteed to work with s-on
Once I'm at hboot 1.55 after flashing that RUU, and S-OFFed after rumrunner, I should be able to flash more recent RUUs without losing my S-OFF <----- Correct, although you can update your firmware and flash the latest ruu with s-on but you will then have to pay for sunshine to get s-off so it's better to do it for free with rumrunner on the way. And No flashing RUUS will not affect s-off. The only way to go back to s-on requires a specific fastboot command.
Click to expand...
Click to collapse
Answers in bold red in above quote
Why / how might I need to flash firmware manually and flash a stock ROM to use rumrunner?
Click to expand...
Click to collapse
As your still on the att network you do have another option. You could flash this rom http://www.htc1guru.com/dld/guru_reset_m7_1-26-502-15-zip/
This is a guru reset rom that matches your current firmware. You can return your software to stock by flashing it in a custom recovery like a normal rom. It comes with some option of which you should choose
Stock radio = Yes
Stock recovery = Yes
Root = No
Once it's installed you'll have full stock rom and recovery, because your on the att network you will be able to accept OTA updates. Take the first to updates to hboot 1.55 then use Rumrunner then you could either manually flash the rest of the updates or just continue to take OTA's until your on the latest firmware and rom. Once that's done you can flash TWRP and any lollipop custom roms you like :good:
Edit:- Also forgot to mention with this method there is no need to relock the bootloader :good:
Sent from my SM-T230 using Tapatalk

Softbrick Going From CM12.1 to Stock

Hey everyone. I read a lot of posts and tutorials on here (love it) and I've done what I can to try and fix my issue, but I've hit a wall. Even a nudge in the right direction would be amazing. I am working with an AT&T HTC One M7 variant (CWS 001). Here are some relevant settings as to where I am now (below them is the progress of why they are what they are):
HBOOT 1.56
S-ON
Bootloader unlocked
TWRP v2.8.7.0 installed
SuperSU BETA 2.94
Android 4.1.2
Software 1.26.502.15
I recently flashed CM12.1 onto my HTC One M7. Prior to doing so, I did an
Code:
adb backup
(which I now assume I should have done a backup through TWRP?). I wanted to go back to official Android, so I did an
Code:
adb restore
to no avail. This worked for me in the past, so either I'm not sure whether it was wrong to begin with, or something went wrong in general. Either way, that's moot point.
Since that failed, I settled on the method laid out at http://www.htc1guru.com/downloads/stock-rom-downloads/ to restore to stock... Believing that it would restore to stock ROM, remove custom recovery and root, and I would be able to take OTA updates and start fresh-ish.
Long story short, I followed the video and ended up with software version "1.26.502.12" as expected... No touch controls, used a mouse to receive OTA update via WiFi. Somewhere along the process of installing the update, I got a message that it failed, was not able to capture the error, and the device rebooted. As a result of that failure, the software was updated to "1.26.502.15" but the WiFi is now broken... Of course meaning no OTA update. Since the touch controls do not work, I can't use the USB internet pass-through, so my device is relegated to mobile data.
I attempted to relock the bootloader (after affirming that the recovery looked to be stock) and run an RUU to update the phone (also unrooted at this point). I started with the official ROM listed on the HTC website, but I get a 155 error (which, as far as I've been able to find, should not be getting as the bootloader was relocked). I tried an RUU from htc1guru for 1.26.502.15, resulting in the same error. So all I can tell is that something is causing any RUU to fail (would there be logs somewhere?)
At this point I went "eff it, I should be able to get back to CM12.1 at least." So I unlocked the bootloader, installed TWRP v2.8.7.0, and initially installed SuperSU BETA 2.94. TWRP fails each time trying to flash CM12.1 now, however. It now also fails to flash the Guru reset from above.
And that now brings me to today... Basically at a complete loss as to next steps. Clearly I've bungled the whole thing and either taken a misstep or (more likely) a bunch of missteps. My device is successfully rooted, as I was able to download Flashify via the Play Store, open it, and see that it was granted permissions. I'm thinking that my next step might be to try flashing a stock recovery from http://forum.xda-developers.com/showthread.php?t=2545227 via Flashify and seeing if that works.
If it doesn't... Man, I could really use the help! Otherwise, I'm using a Lumia 635 indefinitely...

scirto said:
Hey everyone. I read a lot of posts and tutorials on here (love it) and I've done what I can to try and fix my issue, but I've hit a wall. Even a nudge in the right direction would be amazing. I am working with an AT&T HTC One M7 variant (CWS 001). Here are some relevant settings as to where I am now (below them is the progress of why they are what they are):
HBOOT 1.56
S-ON
Bootloader unlocked
TWRP v2.8.7.0 installed
SuperSU BETA 2.94
Android 4.1.2
Software 1.26.502.15
I recently flashed CM12.1 onto my HTC One M7. Prior to doing so, I did an
Code:
adb backup
(which I now assume I should have done a backup through TWRP?). I wanted to go back to official Android, so I did an
Code:
adb restore
to no avail. This worked for me in the past, so either I'm not sure whether it was wrong to begin with, or something went wrong in general. Either way, that's moot point.
Since that failed, I settled on the method laid out at http://www.htc1guru.com/downloads/stock-rom-downloads/ to restore to stock... Believing that it would restore to stock ROM, remove custom recovery and root, and I would be able to take OTA updates and start fresh-ish.
Long story short, I followed the video and ended up with software version "1.26.502.12" as expected... No touch controls, used a mouse to receive OTA update via WiFi. Somewhere along the process of installing the update, I got a message that it failed, was not able to capture the error, and the device rebooted. As a result of that failure, the software was updated to "1.26.502.15" but the WiFi is now broken... Of course meaning no OTA update. Since the touch controls do not work, I can't use the USB internet pass-through, so my device is relegated to mobile data.
I attempted to relock the bootloader (after affirming that the recovery looked to be stock) and run an RUU to update the phone (also unrooted at this point). I started with the official ROM listed on the HTC website, but I get a 155 error (which, as far as I've been able to find, should not be getting as the bootloader was relocked). I tried an RUU from htc1guru for 1.26.502.15, resulting in the same error. So all I can tell is that something is causing any RUU to fail (would there be logs somewhere?)
At this point I went "eff it, I should be able to get back to CM12.1 at least." So I unlocked the bootloader, installed TWRP v2.8.7.0, and initially installed SuperSU BETA 2.94. TWRP fails each time trying to flash CM12.1 now, however. It now also fails to flash the Guru reset from above.
And that now brings me to today... Basically at a complete loss as to next steps. Clearly I've bungled the whole thing and either taken a misstep or (more likely) a bunch of missteps. My device is successfully rooted, as I was able to download Flashify via the Play Store, open it, and see that it was granted permissions. I'm thinking that my next step might be to try flashing a stock recovery from http://forum.xda-developers.com/showthread.php?t=2545227 via Flashify and seeing if that works.
If it doesn't... Man, I could really use the help! Otherwise, I'm using a Lumia 635 indefinitely...
Click to expand...
Click to collapse
Ignore my last paragraph. I completely misread what that file was providing (stock recovery, duh, of course that's what it's providing. Not what I need).

Also, if this helps:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT344W907896
(bootloader) imei: 354439054277373
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3849mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

scirto said:
Also, if this helps:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT344W907896
(bootloader) imei: 354439054277373
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3849mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Hey, just picked up your post in the Unbrick thread. So basically your problem started when you tried to take OTA updates with a Stock rom older than your current firmware.
You can't downgrade firmware while s-on. So when the OTA tried to flash the firmware it failed
The simplest way to get you back to a working stock device will be to use an ruu. You can use this one here http://www.htc1guru.com/dld/ruu_m7_...9_10-26-1718-01l_release_356565_signed_2-exe/
Download it and put it on your pc desktop. Then reboot your device to the bootloader and connect fastboot usb. Because your s-on we need to relock the bootloader or the flash will fail so enter these commands.
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Once the bootloader reboots check it's relocked and in fastboot usb mode then launch the ruu .exe from your desktop. Follow the instructions on your pc. When the flash is complete your device should be back to stock and boot right up.
Then you can take OTA updates safely before unlocking your bootloader again :good:
Sent from my M7 ARHD 84-Kitkat

Danny201281 said:
Hey, just picked up your post in the Unbrick thread. So basically your problem started when you tried to take OTA updates with a Stock rom older than your current firmware.
You can't downgrade firmware while s-on. So when the OTA tried to flash the firmware it failed
The simplest way to get you back to a working stock device will be to use an ruu. You can use this one here http://www.htc1guru.com/dld/ruu_m7_...9_10-26-1718-01l_release_356565_signed_2-exe/
Download it and put it on your pc desktop. Then reboot your device to the bootloader and connect fastboot usb. Because your s-on we need to relock the bootloader or the flash will fail so enter these commands.
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Once the bootloader reboots check it's relocked and in fastboot usb mode then launch the ruu .exe from your desktop. Follow the instructions on your pc. When the flash is complete your device should be back to stock and boot right up.
Then you can take OTA updates safely before unlocking your bootloader again :good:
Sent from my M7 ARHD 84-Kitkat
Click to expand...
Click to collapse
First off, just want to say thanks for the response! I'll give it a shot with a different RUU, but I do want to mention that I have tried this process (albeit different RUU) and it failed.
So I first tried with the most recent RUU officially provided by HTC. It failed, which led me research to discover that I needed to relock the bootloader (received error code 155). So I relocked the bootloader, tried the same RUU again but received the same error code. So I have tried this with no success so far, but I will try again with the RUU you linked.
Also, I think I found where the logs get dumped from the RUU process so I will link my progress with the output in the event it does fail. Right now, before I try it, I will mention that I am now running software 1.26.502.10 (restored from a nandroid backup), stock recovery, but I am rooted. Does the RUU remove the root, or will it leave it and then I need to unroot to OTA update?
Anyways, more to come shortly...
EDIT: I will also note that my last attempt with an RUU was with my phone starting on the home screen. Not sure if starting in bootloader/fastboot is better or worse or makes no difference? I'll try that too

scirto said:
First off, just want to say thanks for the response! I'll give it a shot with a different RUU, but I do want to mention that I have tried this process (albeit different RUU) and it failed.
So I first tried with the most recent RUU officially provided by HTC. It failed, which led me research to discover that I needed to relock the bootloader (received error code 155). So I relocked the bootloader, tried the same RUU again but received the same error code. So I have tried this with no success so far, but I will try again with the RUU you linked.
Also, I think I found where the logs get dumped from the RUU process so I will link my progress with the output in the event it does fail. Right now, before I try it, I will mention that I am now running software 1.26.502.10 (restored from a nandroid backup), stock recovery, but I am rooted. Does the RUU remove the root, or will it leave it and then I need to unroot to OTA update?
Anyways, more to come shortly...
Click to expand...
Click to collapse
The problem is because your s-on. The way firmware is flashed is very strict with s-on.
You must Relock the bootloader.
You can only use firmware or ruu's that match your MiD and CiD. And they must be signed by HTC.
You can only flash a signed ruu or firmware that is the same as your current version or one update above.
So you see the earlier ruu will fail because it's to old and classed as a downgrade. There for can't be flashed with s-on even while relocked.
The latest ruu is lollipop 7.x.502.xx. So to flash it your device must be on at least 6.x.502.xx. Or the flash will fail. As your device is on 4.x.502.x you need the ruu I linked in my earlier instructions or a 5.x.502.xx which to the best of my knowledge does not exist :good: It should work as long ad you Relock your bootloader. Let me know how it goes
Sent from my SM-T230 using Tapatalk

deleted

Danny201281 said:
The problem is because your s-on. The way firmware is flashed is very strict with s-on.
You must Relock the bootloader.
You can only use firmware or ruu's that match your MiD and CiD. And they must be signed by HTC.
You can only flash a signed ruu or firmware that is the same as your current version or one update above.
So you see the earlier ruu will fail because it's to old and classed as a downgrade. There for can't be flashed with s-on even while relocked.
The latest ruu is lollipop 7.x.502.xx. So to flash it your device must be on at least 6.x.502.xx. Or the flash will fail. As your device is on 4.x.502.x you need the ruu I linked in my earlier instructions or a 5.x.502.xx which to the best of my knowledge does not exist :good: It should work as long ad you Relock your bootloader. Let me know how it goes
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
That all makes sense to me and why I was getting two failed RUU's before... One was too old, one was too new. As I type this, I just got a message saying that the ROM update was successful so let's see how it goes from here... Other than that, it had appeared I was following steps for the RUU's perfectly, hence my confusion!
Touch screen ability is back (I knew the old version I was on would cause issues, as warned by htc1guru) and I'm walking through the device setup now... Will update when I get to the OTA process.
Suffice to say, looking good so far and at the very least grateful to be on a DIFFERENT step than I was before!

scirto said:
That all makes sense to me and why I was getting two failed RUU's before... One was too old, one was too new. As I type this, I just got a message saying that the ROM update was successful so let's see how it goes from here... Other than that, it had appeared I was following steps for the RUU's perfectly, hence my confusion!
Touch screen ability is back (I knew the old version I was on would cause issues, as warned by htc1guru) and I'm walking through the device setup now... Will update when I get to the OTA process.
Suffice to say, looking good so far and at the very least grateful to be on a DIFFERENT step than I was before!
Click to expand...
Click to collapse
Good to know. Glad you got it sorted. At least you can start a fresh if nothing else. :good:
Sent from my M7 ARHD 84-Kitkat

Danny201281 said:
Good to know. Glad you got it sorted. At least you can start a fresh if nothing else. :good:
Sent from my M7 ARHD 84-Kitkat
Click to expand...
Click to collapse
Exactly... Might be the software developer in me, but I feel a huge sense of relief as long as I start to see something different happening. OTA is downloading, no root is detected, so the process should complete successfully. Major kudos to you, my friend.

So I was able to accept the OTA update to get up to 4.4.2 and software 5.something.something and am currently updating further... At this point, I think I'm comfortable in saying this issue is resolved. Thanks for the help!!!

scirto said:
So I was able to accept the OTA update to get up to 4.4.2 and software 5.something.something and am currently updating further... At this point, I think I'm comfortable in saying this issue is resolved. Thanks for the help!!!
Click to expand...
Click to collapse
Your Welcome. Enjoy
Sent from my SM-T230 using Tapatalk