Phone randomly reboots after 20-30 seconds. Help? - One (M7) Q&A, Help & Troubleshooting

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

Related

[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

Stock Rom 4.2.2 update to 4.3 = brick

I put stock back on my phone "Guru_Reset_M7_2.24.771.3.zip" which I have done before without any problem.
Stock rom flashed fine, boots up fine and start reinstalling apps etc, OTA firmware starts downloading sense 5.5 etc
Install OTA update and then restart then phone just shows white background with htc logo then bootloops.
Tried going into recovery, restarting, power down, factory reset etc, doesn't work so I do fastboot oem relock to see if it helps.
So basically it's boot looping and now I have no idea how to fix it
EDIT: - I Wiped, reinstalled stock rom and tried again, SAME PROBLEM.
Anarchy89 said:
Hey guys I'll try and keep it short and sweet.
So here's what happened.
I installed android revolution HD 71.1 no problems, notice mobile signal is weak 1-2 bars I normally have 4-5 so I searched and someone said maybe firmware is not up to date.
So I wipe the rom and put stock back on there "Guru_Reset_M7_2.24.771.3.zip" which I have done before without any problem.
Stock rom flashed fine, boots up fine and start reinstalling apps etc, OTA firmware starts downloading sense 5.5 etc
Install OTA update and then restart then phone just shows white background with htc logo then bootloops.
Tried going into recovery, restarting, power down, factory reset etc, doesn't work so I do fastboot oem relock to see if it helps.
So basically it's boot looping and now I have no idea how to fix it, please help, it will be so appreciated
Click to expand...
Click to collapse
If you can flash and access custom recovery, adb push or adb sideload a custom rom..
thanks, I'm making progress, I unlocked the bootloader again and am reflashing the stock firmware...
I flashed stock firmware and stock recovery and downloaded and installed the OTA update and it's doing the same thing!! why?
Just bootlooping
Anarchy89 said:
I flashed stock firmware and stock recovery and downloaded and installed the OTA update and it's doing the same thing!! why?
Just bootlooping
Click to expand...
Click to collapse
Links to stock firmware and stock recovery?
Maybe something is wrong with the phone??
Your best start will be to flash a custom recovery and then flash a custom rom. What is the output of your fastboot getvar all ? (remove IMEI)
SaHiLzZ said:
Links to stock firmware and stock recovery?
Maybe something is wrong with the phone??
Your best start will be to flash a custom recovery and then flash a custom rom. What is the output of your fastboot getvar all ? (remove IMEI)
Click to expand...
Click to collapse
He is using this correct ?: http://www.htc1guru.com/dld/guru_reset_m7_2-24-771-3-zip/
He is having exactly the same problem as someone I was trying to help out who is having exactly the same issue and may join in this thread.
The guru reset puts them on 4.2.2 which works fine then they get a small OTA which installs fine, then a big update to 4.3 which installs, but upon restart for some reason gives a boot loop, doesn't get past the HTC quietly brilliant logo, im at a loss.
Seanie280672 said:
He is using this correct ?: http://www.htc1guru.com/dld/guru_reset_m7_2-24-771-3-zip/
He is having exactly the same problem as someone I was trying to help out who is having exactly the same issue and may join in this thread.
The guru reset puts them on 4.2.2 which works fine then they get a small OTA which installs fine, then a big update to 4.3 which installs, but upon restart for some reason gives a boot loop, doesn't get past the HTC quietly brilliant logo, im at a loss.
Click to expand...
Click to collapse
yes that's the exact one I am using
Seanie280672 said:
He is using this correct ?: http://www.htc1guru.com/dld/guru_reset_m7_2-24-771-3-zip/
He is having exactly the same problem as someone I was trying to help out who is having exactly the same issue and may join in this thread.
The guru reset puts them on 4.2.2 which works fine then they get a small OTA which installs fine, then a big update to 4.3 which installs, but upon restart for some reason gives a boot loop, doesn't get past the HTC quietly brilliant logo, im at a loss.
Click to expand...
Click to collapse
Oh ok.. Interesting.
S-OFF, and move to .401 base perhaps?
SaHiLzZ said:
Oh ok.. Interesting.
S-OFF, and move to .401 base perhaps?
Click to expand...
Click to collapse
I did suggest that, but, somehow he never got the sense 6 update but is on hboot 1.57 and cant s-off
SaHiLzZ said:
Oh ok.. Interesting.
S-OFF, and move to .401 base perhaps?
Click to expand...
Click to collapse
Sorry I don't understand.
Also couldn't I circumvent this hassle just by installing this ROM?
http://forum.xda-developers.com/showthread.php?t=2224752
Seanie280672 said:
I did suggest that, but, somehow he never got the sense 6 update but is on hboot 1.57 and cant s-off
Click to expand...
Click to collapse
ODD! 4.2/4.3 should be on 1.55 Hboot..
@OP.. whats your fastboot getvar all ?
C:\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.23.3263.28
(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: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3838mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae8bbb39
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.049s
couldn't I circumvent this hassle just by installing this ROM?
http://forum.xda-developers.com/showthread.php?t=2224752
Its strange that you too have HBOOT 1.57, did you get the sense 6 update ?
Seanie280672 said:
Its strange that you too have HBOOT 1.57, did you get the sense 6 update ?
Click to expand...
Click to collapse
nope
Anarchy89 said:
couldn't I circumvent this hassle just by installing this ROM?
http://forum.xda-developers.com/showthread.php?t=2224752
Click to expand...
Click to collapse
Yes... You have 1.57 HBOOT.. you should NOT be using 2.x.771.x files. It does NOT gel well.
You have to stick with custom roms, just use adb push or adb sideload..
Anarchy89 said:
nope
Click to expand...
Click to collapse
Well you could try flashing twrp 2.6.3.3 and then flash that ROM your interested in, but it could make things worse, you have a very strange problem, I would love to know why custom rom's work and the guru-reset file, but the OTA's pretty much kill your phone.
SaHiLzZ said:
Yes... You have 1.57 HBOOT.. you should NOT be using 2.x.771.x files. It does NOT gel well.
You have to stick with custom roms, just use adb push or adb sideload..
Click to expand...
Click to collapse
Okay, well I don't know a lot about all this stuff, for example I don't know what HBOOT is, S-OFF/ON etc, I just look for ROMs I'm interested in, optimizing my phone, I just read guides and 99% of the time I don't have a problem.
Do you think my problem would go away if I had HBOOT 1.55? Is it even possible to downgrade?
I'll just flash the ROM I mentioned...but doesn't that mean I won't be able to get OTA updates? (because of the nonstock recovery)
IDFK
Don't know why your HBOOT is 1:57 while your device is not OTA to Sense 6.0. Certainly you can't downgrage HBOOT to 1:55 without S-OFF. You should flash TWRP 2.6.3.3, then adb sileload a custom rom to install
I just wiped and put android revolution hd 71.1 on there and it seems fine now, the other stock rom I mentioned earlier I flashed and I kept getting errors "unfortunately updater has stopped working" every 3 minutes.
I had a go at S-OFF with rumrunner but it didn't work on two ROMs, someone said to try it on linux as it's more reliable, any suggestions for how I can easily S-OFF? thanks :good:

[SOLVED] [Q] HTC Stuck on Boot Screen, here's what I did

Hi everyone,
I've spent the last 6 hours attempting various fixes from forums and I just can't &^%$ing get this.
Here's what I did.
(1) Phone got stuck in a bootloop.
(2) I did a backup in TWRP version 2.6.
(3) Factory reset.
(4) Everything worked again, no bootloop.
(5) Tried to recover from the backup in TWRP, backup failed.
(6) Phone now stuck on the HTC One screen.. won't load a thing.
I really just want things back to normal, as in stock ROM.
Some info about the phone:
S-ON
TWRP ver 2.6
rooted
can access recovery
don't need anything on the phone
I'm looking for a solution to get this phone going again.. any solution. I'd prefer to be on stock ROM. I'd love some help on this. I'm here.
post your fastboot getvar all please
2dayquestion said:
Hi everyone,
I've spent the last 6 hours attempting various fixes from forums and I just can't &^%$ing get this.
Here's what I did.
(1) Phone got stuck in a bootloop.
(2) I did a backup in TWRP version 2.6.
(3) Factory reset.
(4) Everything worked again, no bootloop.
(5) Tried to recover from the backup in TWRP, backup failed.
(6) Phone now stuck on the HTC One screen.. won't load a thing.
I really just want things back to normal, as in stock ROM.
don't need anything on the phone
Click to expand...
Click to collapse
well if you don't need anything on the phone and you previously did a factory reset and the phone stopped boot-looping, why did you restored that faulty backup? just do a factory reset and you'll be good
alray said:
well if you don't need anything on the phone and you previously did a factory reset and the phone stopped boot-looping, why did you restored that faulty backup? just do a factory reset and you'll be good
Click to expand...
Click to collapse
The backup contained all of the original apps. Thought I could get it rolling again, but no go. Now the phone just won't boot. Stuck on the HTC one screen, even after another factory reset.
2dayquestion said:
The backup contained all of the original apps. Thought I could get it rolling again, but no go. Now the phone just won't boot. Stuck on the HTC one screen, even after another factory reset.
Click to expand...
Click to collapse
post the ouput of fastboot getvar all
Seanie280672 said:
post your fastboot getvar all please
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.0
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ---------------
(bootloader) imei: ----------------
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3855mV
(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
2dayquestion said:
The backup contained all of the original apps. Thought I could get it rolling again, but no go. Now the phone just won't boot. Stuck on the HTC one screen, even after another factory reset.
Click to expand...
Click to collapse
factory reset again
Install Titanium backup it will restore apps & data from nandroid backup
from HTC One
yatindroid said:
factory reset again
Install Titanium backup it will restore apps & data from nandroid backup
from HTC One
Click to expand...
Click to collapse
The factory reset isn't working. It still hangs. I did the initial backup through TWRP. Will Titanium backup be compatible with that backup?
Now the phone is currently locked, no OS.Should I flash another ROM?
http://www.htc1guru.com/dld/ruu_m7_..._10-38r-1157-04l_release_351317_signed_2-exe/
Looks like your RUU to return to fully stock
You could do with seeing if you can see this number anywhere in the bootloader 4.19.631.9 usually under os- however, radio's match
Seanie280672 said:
http://www.htc1guru.com/dld/ruu_m7_..._10-38r-1157-04l_release_351317_signed_2-exe/
Looks like your RUU to return to fully stock
You could do with seeing if you can see this number anywhere in the bootloader 4.19.631.9 usually under os- however, radio's match
Click to expand...
Click to collapse
The OS is set to 1.000.000. I used some **** utility that reset it. I started clicking things... lol
One thing I'm wondering is since this phone is S-ON, will I be able to even flash a ROM? Could that be the reason that the TWRP restore function isn't working? As far as I know... SON would prevent system files from being written.. correct me if I'm wrong
..downloading that file as I write this
Seanie280672 said:
http://www.htc1guru.com/dld/ruu_m7_..._10-38r-1157-04l_release_351317_signed_2-exe/
Looks like your RUU to return to fully stock
You could do with seeing if you can see this number anywhere in the bootloader 4.19.631.9 usually under os- however, radio's match
Click to expand...
Click to collapse
The phone is the HTC One m7 through Rogers. It was recently asking me for the latest OTA update. The ROM was stock, if that helps.
2dayquestion said:
The phone is the HTC One m7 through Rogers. It was recently asking me for the latest OTA update. The ROM was stock, if that helps.
Click to expand...
Click to collapse
looks like your RUU, like I said, its a Rogers RUU and contains the same radio, your version-main just threw me off a bit, leave your bootloader locked / relocked and plug into your computer in bootloader mode, then run the RUU on your computer, follow the instructions, make sure your battery is 50% or more before running.
regarding your other question, you can flash custom roms whilst s-on, you just have to make sure your bootloader is unlocked, s-on is not there to protect system files, its there to protect you from messing with the HBOOT and radio's etc which will brick the phone if done wrong, you cant brick by flashing rom's.
Seanie280672 said:
looks like your RUU, like I said, its a Rogers RUU and contains the same radio, your version-main just threw me off a bit, leave your bootloader locked / relocked and plug into your computer in bootloader mode, then run the RUU on your computer, follow the instructions, make sure your battery is 50% or more before running.
regarding your other question, you can flash custom roms whilst s-on, you just have to make sure your bootloader is unlocked, s-on is not there to protect system files, its there to protect you from messing with the HBOOT and radio's etc which will brick the phone if done wrong, you cant brick by flashing rom's.
Click to expand...
Click to collapse
Thanks a lot for that link. I found an RUU file about 7 hours ago, but it was in .zip format, not .exe like the link you provided me. This made it damn easy. I relocked the bootloader, installed, now it's all great. Thanks a lot. Can I thumbs up you, or do anything in return?
2dayquestion said:
Thanks a lot for that link. I found an RUU file about 7 hours ago, but it was in .zip format, not .exe like the link you provided me. This made it damn easy. I relocked the bootloader, installed, now it's all great. Thanks a lot. Can I thumbs up you, or do anything in return?
Click to expand...
Click to collapse
Just hit the thanks button a couple of times is plenty.
The Zip would of worked too, you just have to flash it in a special kinda way.
Glad its all working now, could you edit your title in your first post to SOLVED now please.
Seanie280672 said:
Just hit the thanks button a couple of times is plenty.
The Zip would of worked too, you just have to flash it in a special kinda way.
Glad its all working now, could you edit your title in your first post to SOLVED now please.
Click to expand...
Click to collapse
I'm guessing a side-load? I really like the install wizard, the RUU method is pretty ingenious. One quick question for you: It's asking me for a system update, OTA, that's not installing after I download it. I unlocked the bootloader through HTC dev using the binary they e-mail you. Would I have to unroot? Any tips on what I could do?
[edit: for some reason, OTA worked] thanks a lot for your help and especially for that magical link. cheers
2dayquestion said:
I'm guessing a side-load? I really like the install wizard, the RUU method is pretty ingenious. One quick question for you: It's asking me for a system update, OTA, that's not installing after I download it. I unlocked the bootloader through HTC dev using the binary they e-mail you. Would I have to unroot? Any tips on what I could do?
[edit: for some reason, OTA worked] thanks a lot for your help and especially for that magical link. cheers
Click to expand...
Click to collapse
No, you have to put your phone in fastbootRUU mode and then flash the zip from your computer using fastboot commands.
Glad the OTA worked in the end, but in future when installing OTA's just make sure your bootloader is locked / relocked first.
Seanie280672 said:
No, you have to put your phone in fastbootRUU mode and then flash the zip from your computer using fastboot commands.
Glad the OTA worked in the end, but in future when installing OTA's just make sure your bootloader is locked / relocked first.
Click to expand...
Click to collapse
That may have been the issue. Thanks for your time. Another 'thanks' is in order. Cheers

[Q] urgent help please

Hi, really need some help as i have no clue whats happening, installed Lollipop update on my htc one tonight, when it went to start up it got stuck at htc one screen, tried rebooting several times with no change, the phone was previously unlocked, rooted and had a custom rom installed, but i did the stock RUU, which relocked the phone and allowed me to do OTA back to Kitkat 4.4.3. I can get into the bootloader which shows *Tampered* (i know that one) but underneath its saying *Unlocked* ? please help
johnrc_uk said:
Hi, really need some help as i have no clue whats happening, installed Lollipop update on my htc one tonight, when it went to start up it got stuck at htc one screen, tried rebooting several times with no change, the phone was previously unlocked, rooted and had a custom rom installed, but i did the stock RUU, which relocked the phone and allowed me to do OTA back to Kitkat 4.4.3. I can get into the bootloader which shows *Tampered* (i know that one) but underneath its saying *Unlocked* ? please help
Click to expand...
Click to collapse
Very strange, can you link the RUU that you used to get back to stock ? never known an RUU to relock the bootloader for you.
Seanie280672 said:
Very strange, can you link the RUU that you used to get back to stock ? never known an RUU to relock the bootloader for you.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=23501681358543706
guru reset file, select stock radio and stock recovery during the flash, when the flash is finished and phone reboots, start updating., the guru reset will wipe everything so be sure to backup anything you want to keep first.
It was you who pointed me to it,
johnrc_uk said:
https://www.androidfilehost.com/?fid=23501681358543706
guru reset file, select stock radio and stock recovery during the flash, when the flash is finished and phone reboots, start updating., the guru reset will wipe everything so be sure to backup anything you want to keep first.
It was you who pointed me to it,
Click to expand...
Click to collapse
LOL, yeah that seems about right, and did it update ok after that ? before Lollipop ?
Sorry could you post your fastboot getvar all again please without imei and serial
Seanie280672 said:
LOL, yeah that seems about right, and did it update ok after that ? before Lollipop ?
Click to expand...
Click to collapse
yeah i did about 4 OTA updates back to 4.4.3 and phone worked perfect, so when i got the lollipop update i wouldnt think anthing would be different. now i cant get past the htc one screen :/
c:\fastboot>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3783mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
johnrc_uk said:
yeah i did about 4 OTA updates back to 4.4.3 and phone worked perfect, so when i got the lollipop update i wouldnt think anthing would be different. now i cant get past the htc one screen :/
Click to expand...
Click to collapse
I would say, try again, start again, its possible that the Lollipop update has got a bit corrupt along the way somewhere, maybe the download, thankfully your only soft bricked, you will need to get back to the bootloader, flash a custom recovery and then push that guru reset to your internal SDCard and flash it again, very strange that all of the KK updates worked fine but the LP one bricked you.
Before you do try that, have you tried a factory reset from the bootloader ?
Damn, hang on, the firmware part of the LP update seems to have worked fine, I can see thats all updated, you probably wont beable to use the guru reset again due to HBOOT conflicts.
Seanie280672 said:
I would say, try again, start again, its possible that the Lollipop update has got a bit corrupt along the way somewhere, maybe the download, thankfully your only soft bricked, you will need to get back to the bootloader, flash a custom recovery and then push that guru reset to your internal SDCard and flash it again, very strange that all of the KK updates worked fine but the LP one bricked you.
Before you do try that, have you tried a factory reset from the bootloader ?
Click to expand...
Click to collapse
havent tried a factory reset, should i try that first. and what steps would i take if that didnt work? would i have to root phone etc again first?
johnrc_uk said:
havent tried a factory reset, should i try that first. and what steps would i take if that didnt work? would i have to root phone etc again first?
Click to expand...
Click to collapse
try the factory reset first, if that doesnt work, as you have the newer firmware on your phone already, I would flash a custom recovery (TWRP 2.8.4.0) and then flash this rom, its basically stock Lollipop with future OTA ability.
https://www.androidfilehost.com/?fid=95916177934533366
Seanie280672 said:
try the factory reset first, if that doesnt work, as you have the newer firmware on your phone already, I would flash a custom recovery (TWRP 2.8.4.0) and then flash this rom, its basically stock Lollipop with future OTA ability.
https://www.androidfilehost.com/?fid=95916177934533366
Click to expand...
Click to collapse
tried factory reset...still hangs on htc one screen, still plays startup music.
johnrc_uk said:
tried factory reset...still hangs on htc one screen, still plays startup music.
Click to expand...
Click to collapse
This is very strange, im tempted to say try and relock the bootloader first and then try and boot, but im worried that if it still doesnt boot you may not be able to unlock the bootloader again, then you'll be right up the creek without a paddle.
Seanie280672 said:
This is very strange, im tempted to say try and relock the bootloader first and then try and boot, but im worried that if it still doesnt boot you may not be able to unlock the bootloader again, then you'll be right up the creek without a paddle.
Click to expand...
Click to collapse
ok no idea if this was me but i relocked bootloader, then did htcdev unlock again and flashed custom recovery. rebooted the phone and now its booted up and optimising android apps, what ever it did now seems to have got out of the boot loop.
johnrc_uk said:
ok no idea if this was me but i relocked bootloader, then did htcdev unlock again and flashed custom recovery. rebooted the phone and now its booted up and optimising android apps. weird!?!
Click to expand...
Click to collapse
:silly:, thats a new one on me, glad it working though, very weird.
Seanie280672 said:
:silly:, thats a new one on me, glad it working though, very weird.
Click to expand...
Click to collapse
Had a funny feeling id be on stock android after i did the factory reset lol..phone has booted up, and im on lollipop, rooted again but never mind!
johnrc_uk said:
Had a funny feeling id be on stock android after i did the factory reset lol..phone has booted up, and im on lollipop, rooted again but never mind!
Click to expand...
Click to collapse
Its still stock mate, just rooted and custom recovery, I cant live without root
Seanie280672 said:
Very strange, can you link the RUU that you used to get back to stock ? never known an RUU to relock the bootloader for you.
Click to expand...
Click to collapse
I have an almost similar problem.
I own the European model, unbranded.
Got the OTA tonight, after installing I got stuck ed on the HTC WHITE screen.
My device has never been rooted nor S- Off.
The boot screen reads as follow.
***LOCKED***
M7 SHIP S-ON RH
HBOOT- 1.57.000
RADIO -4T. 29.3210.00
OPEN dsp v32. 120.274.0909
OS-6.09.401.11
Emmc-boot 2048mb
Nov 12 2014.22:00:05,0
Neither Recovery nor factory reset worked
Can you provide me some advice.
Thanks
Henry Paris
Sent from my GT-N8010 using XDA Free mobile app

[Q] Error after Lollipop update

Hoping someone here might be able to help as nothing on the HTC website did.
My phone updated yesterday to Lollipop 5.0 (through EE in the UK)...well it it had a go, but failed. I'm left with just an exclamation mark of helpfulness. I've tried all of the basic recovery options but it just restarts a few times and goes back to said exclamation mark.
The error is..
DEVICE_CW_Install: Can't mount /cwprop
Then stuff about failing to mount the SD card (that it doesn't have).
Are there any tools that might help me sort this out? I don't particularly want to install something none standard on it but if that's all I can do to get it working, it would be ok.
Jxt. said:
is your bootloader is unlocked and are you on complete stock.
Click to expand...
Click to collapse
It's totally stock.
alfev said:
It's totally stock.
Click to expand...
Click to collapse
post your fastboot getvar all please without imei and serial number.
however if it is totally stock and the bootloader is locked, then id suggest you send it back under warranty.
Thanks for replying and trying to help. It's out of warranty this is just a last ditch attempt before getting a new one really. I have zero knowledge in this area but have installed the sdk and run that command...
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.16.61.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: sssh
(bootloader) imei: ssshh
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3778mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.088s
Seanie280672 said:
post your fastboot getvar all please without imei and serial number.
however if it is totally stock and the bootloader is locked, then id suggest you send it back under warranty.
Click to expand...
Click to collapse
Is it possible to unlock it, is there anything I can do with it, or is it a paper weight now?
alfev said:
Is it possible to unlock it, is there anything I can do with it, or is it a paper weight now?
Click to expand...
Click to collapse
If it's still under warranty, better send it back to service center since it is an OTA failure, not your fault.
eyeyousee said:
If it's still under warranty, better send it back to service center since it is an OTA failure, not your fault.
Click to expand...
Click to collapse
I would do but as I say, it's out of warranty so just making the best of it.
I'm downloading this at the moment RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe
No idea if that's a good idea but I can't be any worse off than I am at the moment.
alfev said:
I would do but as I say, it's out of warranty so just making the best of it.
I'm downloading this at the moment RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe
No idea if that's a good idea but I can't be any worse off than I am at the moment.
Click to expand...
Click to collapse
If that RUU fails, the best thing to do is to unlock your bootloader, you can find the unlocking instructions here search for it. Then install custom recovery, and then install custom rom.
Just post the results of your RUU setup.
eyeyousee said:
If that RUU fails, the best thing to do is to unlock your bootloader, you can find the unlocking instructions here search for it. Then install custom recovery, and then install custom rom.
Just post the results of your RUU setup.
Click to expand...
Click to collapse
The RUU update got to 1/5 checking header then crashed with "htc_fastboot.exe has stopped working." Then Error 171: USB connection error. Not sure if their is a problem with a driver or something.
alfev said:
The RUU update got to 1/5 checking header then crashed with "htc_fastboot.exe has stopped working." Then Error 171: USB connection error. Not sure if their is a problem with a driver or something.
Click to expand...
Click to collapse
171 is a USB error, means therres a problem with your drivers, sorry been a bit busy today, car problems, but that RUU is wrong for your phone anyway, that's a 401 RUU (4.19.401.2), you need a 61 RUU if one exists, you will need an RUU labelled as 6.16.61.8 or higher
Seanie280672 said:
171 is a USB error, means therres a problem with your drivers, sorry been a bit busy today, car problems, but that RUU is wrong for your phone anyway, that's a 401 RUU (4.19.401.2), you need a 61 RUU if one exists, you will need an RUU labelled as 6.16.61.8 or higher
Click to expand...
Click to collapse
I've sorted of veered off the RUU route and unlocked the phone. I've installed twrp... I'm winging it completely. Trying to get a ROM on it now... or something.
alfev said:
I've sorted of veered off the RUU route and unlocked the phone. I've installed twrp... I'm winging it completely. Trying to get a ROM on it now... or something.
Click to expand...
Click to collapse
you will have problems with Lollipop based roms, so use this one which matches your firmware: https://www.androidfilehost.com/?fid=95897840722644627
your best bet if you want it full stock is to get s-off using sunshine once you get a rom on it and convert it to a 401 WWE phone, which gets one of the fastest updates, sunshine however will cost you $25 via paypal.
I'm not familiar with M7 software numbers but, yes maximusHD custom roms are good to begin with.
Seanie280672 said:
you will have problems with Lollipop based roms, so use this one which matches your firmware: https://www.androidfilehost.com/?fid=95897840722644627
your best bet if you want it full stock is to get s-off using sunshine once you get a rom on it and convert it to a 401 WWE phone, which gets one of the fastest updates, sunshine however will cost you $25 via paypal.
Click to expand...
Click to collapse
Thanks,I will probably have a go at putting different rom's on at some point and was wondering what people thought the best option is for the M7.
I managed to get sorted using Guru_Reset_M7_2.24.401.8.zip. I had some problems uploading it to begin with, I think the usb issue stopped the ruu and abd working but not fastboot. I have a working phone now, which seems like a bonus after thinking the phone was maybe a goner. It's been a massive learning curve having known absolutely nothing about any of this stuff on Monday, I know how to put different rom's on now which is handy to know. The phone is still unlocked at the moment, I don't know what the cons of that are. Would this rom maybe update if I locked it again?
alfev said:
Thanks,I will probably have a go at putting different rom's on at some point and was wondering what people thought the best option is for the M7.
I managed to get sorted using Guru_Reset_M7_2.24.401.8.zip. I had some problems uploading it to begin with, I think the usb issue stopped the ruu and abd working but not fastboot. I have a working phone now, which seems like a bonus after thinking the phone was maybe a goner. It's been a massive learning curve having known absolutely nothing about any of this stuff on Monday, I know how to put different rom's on now which is handy to know. The phone is still unlocked at the moment, I don't know what the cons of that are. Would this rom maybe update if I locked it again?
Click to expand...
Click to collapse
no, don't try and update either, you'll stand a high chance of seriously bricking your phone, it will try and install 401 firmware which isn't for your phone, hence 2.24.401.8 like I said before, your firmware is 61. orange / EE.
the numbers work like this, 2.24.401.8 ( the 2 is android version) the 24 is part of the build number, the 401 is carrier / region (401 is WWE world wide English) yours is 61 orange / EE and you can only use these files same or above the one your currently on as your phone is s-on, and the last number 8 is build number, or alternatively you can flash any custom rom you like upto KitKat as your firmware on your phone is currently 6.xx.61.x
you are stuck with custom rom's only up to KitKat, the one I linked earlier is Maximus HD 50.0 which is as close to stock Kitkat as you will get for now, but still a custom rom. Lollipop rom's will play up as your on firmware 6xxxxxxx unless you s-off and convert your phone or unless you can get hold of the 7.xx.61.x firmware and manually upgrade your firmware, you need to have, or find someone who has the 7.xx.61.x OTA and grab the firmware.zip out of it and flash that in fastbootRUU mode.
I think I've been pretty lucky to get the thing up and running really could've gone badly but I didn't think I had anything to lose. With all of the different firmware and rom version that I wasn't aware of it sounds like there was actually a lot I could've lost with my wing it aproach.
This oldish Android version I'm on now seems to use a lot of battery, presumably connected to the additional "HTC Pocket Radiator" feature which it also turns on sporadically. It's not a big problem but I think I'll have a bash with the MaximusHD you suggested. Question though, Googling for a bit more info on MaximusHD 5.0 it appears to be Lollipop, am I right? If so, just to confirm, you're saying that I could have problems with Lollipop because of my firmware but this version of it should work ok with my current firmware? From googling I found a description of the rom that said "Firmware 7.15.401.1 is recommended to install". Sorry, just making sure because my luck is likely to run out soon.
EDIT
Also, if I do need to S-OFF, you mention Sunshine and you mention $25, this is a 3 year old phone with a slight crack in the screen so I'm not going to throw any money at it but I found Squabbi's tool kit which uses Revone for S-OFF, would this be no good?
Seanie280672 said:
(..)you need a 61 RUU if one exists, you will need an RUU labelled as 6.16.61.8 or higher
Click to expand...
Click to collapse
There is a 6.16.61.8 signed RUU available but unfortunately, its only available at ir-file.com and you need a paid account to download from that website.
http://www.ir-file.com/portal/index.php?dir=Firmware/HTC/HTC_Android/M7_UL/
Seanie280672 said:
no, don't try and update either, you'll stand a high chance of seriously bricking your phone, it will try and install 401 firmware which isn't for your phone, hence 2.24.401.8 like I said before, your firmware is 61. orange / EE.
Click to expand...
Click to collapse
Right the update will not work but there is no chance of bricking here, the ota install process will only stop before flashing anything since the Orange CID and .61 Firmware of the phone doesn't match the WWE CID and .401 base of the OTA
alfev said:
EDIT
Also, if I do need to S-OFF, you mention Sunshine and you mention $25, this is a 3 year old phone with a slight crack in the screen so I'm not going to throw any money at it but I found Squabbi's tool kit which uses Revone for S-OFF, would this be no good?
Click to expand...
Click to collapse
No, Revone is only for hboot 1.44 pre-June 2013 version. For hboot 1.57 and above, Sunshine is the only way.
alray said:
There is a 6.16.61.8 signed RUU available but unfortunately, its only available at ir-file.com and you need a paid account to download from that website.
http://www.ir-file.com/portal/index.php?dir=Firmware/HTC/HTC_Android/M7_UL/
Right the update will not work but there is no chance of bricking here, the ota install process will only stop before flashing anything since the Orange CID and .61 Firmware of the phone doesn't match the WWE CID and .401 base of the OTA
No, Revone is only for hboot 1.44 pre-June 2013 version. For hboot 1.57 and above, Sunshine is the only way.
Click to expand...
Click to collapse
Ok, MaximusHD was mentioned. 50.0 looks to be the latest version and that's the version posted above but that's Lollipop, would 40.0 be the right one for me?
I might be best just leaving it as is. I've successfully upgraded it from a paperweight to a phone, if I twist I might bust and end up back with a shiny paperweight again.
alfev said:
Ok, MaximusHD was mentioned. 50.0 looks to be the latest version and that's the version posted above but that's Lollipop, would 40.0 be the right one for me?
I might be best just leaving it as is. I've successfully upgraded it from a paperweight to a phone, if I twist I might bust and end up back with a shiny paperweight again.
Click to expand...
Click to collapse
sorry my bad, I thought 50 was a KitKat rom as its sense 6, use this one instead which is a KitKat 6xxxx as close to stock rom as possible: https://www.androidfilehost.com/?w=files&flid=22071 (Maximus HD 46.0)
custom rom based on 6.09.401.11
Seanie280672 said:
sorry my bad, I thought 50 was a Ki
Code:
tKat rom as its sense 6, use this one instead which is a KitKat 6xxxx as close to stock rom as possible: [url]https://www.androidfilehost.com/?w=files&flid=22071[/url] (Maximus HD 46.0)
custom rom based on 6.09.401.11
Click to expand...
Click to collapse
Excellent, thanks, I think I'll have a pop at that then.

Categories

Resources