Database Develop

[Q] Boot looping Phone

Ok i have a one and it keeps boot looping i ran an ruu and nothing changed, i can get in to boot loader but that's about it, the phone hasn't been rooted and its bootloader is locked idk what to do, please help

Hypeonline said:
Ok i have a one and it keeps boot looping i ran an ruu and nothing changed, i can get in to boot loader but that's about it, the phone hasn't been rooted and its bootloader is locked idk what to do, please help
Click to expand...
Click to collapse
Could you take a picture of the hboot screen? If you can't, write all the text here. Also do you know of anything that may have contributed to the boot loop?

I dont have much info on this phone myself i got my hands on it in boot loop, ive been screwing with it for the last few days heres the pics of the hboot

fastboot getvar all gave me this info, i removed the imei/serialno
C:\Users\Mandatedace>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 1.00.20.1108
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.651.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: not blank
(bootloader) imei: not blank
(bootloader) meid: 99000146974578
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3759mV
(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.053s

Hypeonline said:
fastboot getvar all gave me this info, i removed the imei/serialno
C:\Users\Mandatedace>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 1.00.20.1108
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.651.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: not blank
(bootloader) imei: not blank
(bootloader) meid: 99000146974578
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3759mV
(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.053s
Click to expand...
Click to collapse
did you use the ruu for 4.06.651.4(if there is one) and do you have stock recovery installed? you can't downgrade because you're s-on you have to use the ruu I posted. you can find it in development section OMJ has it posted there, you'll need 10 posts to access that section

Ok so that ruu will more than likey resolve my problem?

Hypeonline said:
Ok so that ruu will more than likey resolve my problem?
Click to expand...
Click to collapse
yep it should.

Ok getting it stated right now will post results

no dice the phone still boot loops got the update all finished and its looping as i type

Hypeonline said:
no dice the phone still boot loops got the update all finished and its looping as i type
Click to expand...
Click to collapse
boy, I don't know buddy, if the ruu installed properly, should have fixed you up, you have stock recvovery?

Aldo101t said:
boy, I don't know buddy, if the ruu installed properly, should have fixed you up, you have stock recvovery?
Click to expand...
Click to collapse
This phone is stock as i far as i know, Im working blind when it comes to this thing, could this phone really be a gsm phone that was flashed with the cdma stuff, could that possibly be teh problem, like i said im not sure on whats been done with the phone before i got it

Hypeonline said:
This phone is stock as i far as i know, Im working blind when it comes to this thing, could this phone really be a gsm phone that was flashed with the cdma stuff, could that possibly be teh problem, like i said im not sure on whats been done with the phone before i got it
Click to expand...
Click to collapse
boy. anything is possible, I don't know at this point, sorry

dang well thanks for the help, i may just look for an att ruu or is there away to manualy put the update on the phone?

Hypeonline said:
dang well thanks for the help, i may just look for an att ruu or is there away to manualy put the update on the phone?
Click to expand...
Click to collapse
I don't know I wouldn't just start flashing ruu's until you know what exactly is going on there, I know that's not much help, but maybe someone else will chime in here.

Oh dose it matter that this is the M7 one

fastboot erase data dosent work i get an err in fastboot, i cant do a factory wipe, nor check smartsd, is there a way to flash using fastboot not with the ruu tool, if i could wipe this phone it would be so much help, or something i need some help, using fastboot oem unlock results in an error i used the fastboot erase cache command, it goes thru and finishes up, any idea will help please somebody

Is there anything else i can try like using fastboot or something, i need some help asap

Hypeonline said:
Is there anything else i can try like using fastboot or something, i need some help asap
Click to expand...
Click to collapse
You can try flashing the newest RUU. Instructions are in the thread. Other than that, I don't really know :/. If the phone wasn't modded you can take it to Sprint and say that the phone started bootlooping after an update and try and get a replacement.

I keep getting suck at 4% on the ruu

Hypeonline said:
I keep getting suck at 4% on the ruu
Click to expand...
Click to collapse
Could you post what's happening in Command Prompt? We might be able to see what's going on then.
Usually if an RUU fails, it's time to get a replacement though :/

HTC One m7 stuck on black screen

After upgrade to 4.4 my phone started to reboot randomly and display "Process com.htc.dialer isn't responding", so i flashed hboot 1.44 and installed new ruu now phone after boot is stuck on black screen and i can see only top bar with icons.
Phone is S-OFF
UNLOCKED
not rooted
below getvar all:
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:--------------------
(bootloader) imei: -----------------------
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4238mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.344s
Any help would be great.
Okay so i flashed it again with same ruu now it load lock screen and aftter unlock it only shows white htc logo and after couple minutes reboot, after one reboot it goes back to being stuck on black screen.

ol3k1990 said:
After upgrade to 4.4 my phone started to reboot randomly and display "Process com.htc.dialer isn't responding", so i flashed hboot 1.44 and installed new ruu now phone after boot is stuck on black screen and i can see only top bar with icons.
Phone is S-OFF
UNLOCKED
not rooted
below getvar all:
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:--------------------
(bootloader) imei: -----------------------
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4238mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.344s
Any help would be great.
Okay so i flashed it again with same ruu now it load lock screen and aftter unlock it only shows white htc logo and after couple minutes reboot, after one reboot it goes back to being stuck on black screen.
Click to expand...
Click to collapse
download 4.19.401.9 no wipe firmware from here and flash it in fastboot RUU mode: https://docs.google.com/spreadsheets/d/1LQDLpVZYyUpXPgC2sh1BvAS9Oo8B-fTiZU_JhpIH-fU/pubhtml
Code:
fastboot oem rebootRUU
fastboot flash zip (name of firmware).zip
fastboot flash zip (name of firmware).zip - [B]yes twice[/B]
[B][I]if successful at the end then[/I][/B]
fastboot reboot-bootloader
[B][I]if failed, report back here before doing anything else.[/I][/B]
now with your phone in fastboot USB mode still, download and run this RUU
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/

Seanie280672 said:
download 4.19.401.9 no wipe firmware from here and flash it in fastboot RUU mode:
Code:
fastboot oem rebootRUU
fastboot flash zip (name of firmware).zip
fastboot flash zip (name of firmware).zip - [B]yes twice[/B]
[B][I]if successful at the end then[/I][/B]
fastboot reboot-bootloader
[B][I]if failed, report back here before doing anything else.[/I][/B]
now with your phone in fastboot USB mode still, download and run this RUU
Click to expand...
Click to collapse
Hi, thanks for replaying
I did everyting above and after installing new ruu now is still rebooting the only difference it isstuck on white htc screen after lock screen and the Process com.htc.htcdialer error is showing again.

ol3k1990 said:
I did everyting above and after installing new ruu now is still rebooting the only difference it isstuck on white htc screen after lock screen and the Process com.htc.htcdialer error is showing again.
Click to expand...
Click to collapse
can you post a new fastboot getvar all please ?

Seanie280672 said:
can you post a new fastboot getvar all please ?
Click to expand...
Click to collapse
My new getvar all:
< waiting for device >
(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: 4.19.401.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ----------------
(bootloader) imei: ------------------
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4264mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(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.284s

ol3k1990 said:
My new getvar all:
< waiting for device >
(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: 4.19.401.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: REMOVE THIS
(bootloader) imei: REMOVE THIS
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4264mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(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.284s
Click to expand...
Click to collapse
remove your imei and serial number please like ive done in the quote.
well the firmware flash went fine, if you notice you are now on HBOOT 1.56 and also have a version main, did the RUU flash ok ?

Seanie280672 said:
remove your imei and serial number please like ive done in the quote.
well the firmware flash went fine, if you notice you are now on HBOOT 1.56 and also have a version main, did the RUU flash ok ?
Click to expand...
Click to collapse
It went perfectly fine

ol3k1990 said:
It went perfectly fine
Click to expand...
Click to collapse
I would have to say it sounds like you have some sort of hardware problem going on there, maybe a bad nand.
you could try flashing twrp recovery and then doing a full format (format data) then try all of the above again, see if that works, if it still fails then id say it was down to hardware.

Seanie280672 said:
I would have to say it sounds like you have some sort of hardware problem going on there, maybe a bad nand.
you could try flashing twrp recovery and then doing a full format (format data) then try all of the above again, see if that works, if it still fails then id say it was down to hardware.
Click to expand...
Click to collapse
Thanks for replaying again ,
The phone is still under guarantee so if that wont help i will try to get it back to locked and s-off and then send it for service.

ol3k1990 said:
Thanks for replaying again ,
The phone is still under guarantee so if that wont help i will try to get it back to locked and s-off and then send it for service.
Click to expand...
Click to collapse
yes you can do that, but you will have to flash an earlier firmware and ruu before going s-on, with the later ones, like the one you have on there now, going s-on brings back the tampered flag.

Seanie280672 said:
yes you can do that, but you will have to flash an earlier firmware and ruu before going s-on, with the later ones, like the one you have on there now, going s-on brings back the tampered flag.
Click to expand...
Click to collapse
So it should be alright if i flash hboot 1.44 and install the ruu i used earlier.

ol3k1990 said:
So it should be alright if i flash hboot 1.44 and install the ruu i used earlier.
Click to expand...
Click to collapse
which ruu did you use earlier ?

Seanie280672 said:
which ruu did you use earlier ?
Click to expand...
Click to collapse
Cant post links yet but full name is
RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed

ol3k1990 said:
Cant post links yet but full name is
RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed
Click to expand...
Click to collapse
yup that will be perfect, downgrade your hboot to 1.44, run the ruu.zip, make sure your firmware is downgraded to, it should be and then remove tampered flag from the bootloader if its still there, then lock the bootloader and s-on.

Seanie280672 said:
yup that will be perfect, downgrade your hboot to 1.44, run the ruu.zip, make sure your firmware is downgraded to, it should be and then remove tampered flag from the bootloader if its still there, then lock the bootloader and s-on.
Click to expand...
Click to collapse
Thanks for help

HTC supports Rooting so warranty may still be ok. Depending on your provider honoring it is another thing but I'm sure you can go directly to HTC if your provider has a problem with it.

bornthor said:
HTC supports Rooting so warranty may still be ok. Depending on your provider honoring it is another thing but I'm sure you can go directly to HTC if your provider has a problem with it.
Click to expand...
Click to collapse
HTC will refuse to repair, and make you pay for repairs if you have TAMPERED or UNLOCKED or RELOCKED flags on your bootloader, they will shift all fault and blame onto you.

Seanie280672 said:
HTC will refuse to repair, and make you pay for repairs if you have TAMPERED or UNLOCKED or RELOCKED flags on your bootloader, they will shift all fault and blame onto you.
Click to expand...
Click to collapse
I guess if you have experienced this and or have been told this personally then you know. I'm looking at the htcdev site that says "not all claims... May be covered under warranty." it's worth a try if you can't resurrect it.

[Q] Stock HTC m7 wont boot up and both recovery and hard rest wont work

Hi Guys,
I have been reading around the forum but cant seem to find the answer to my problem. Or the suggestions are going over my head, so hope you can help.
I have a stock htc one m7 that is unrooted but it is sim unlocked. Went to bed with the phone working and then woke up with it stuck on the htc boot screen.
Things I have tried:
- get into HBOOT (which i can), then try recovery. This just reboots the phone to the white htc screen or screen just goes off.
- try and hard reset from hboot, but this does the same and either turns the screen black or reboots.
Both times i have left the phone for a while to see if it is up to anything but nothing happens.
I read about clearing the cache, but I could not get my head around the guides I read, so is there an idiots guide (I usually pretty good with tech stuff but not done much to do with phones etc)
Or any other suggestions. I use my phone for work so would be nice to get it working again without wiping it but most of the stuff should be back up anyway.
Thanks
Tom

From what I have tried I guess I should now try and flash the RRU?
The phone is on UKs EE network, as it is not rooted do I need to flash it with their branded rom or not? If so where can I get that from.
Thanks

Tommy_G5 said:
From what I have tried I guess I should now try and flash the RRU?
The phone is on UKs EE network, as it is not rooted do I need to flash it with their branded rom or not? If so where can I get that from.
Thanks
Click to expand...
Click to collapse
Do you have an sdk installed on your pc for adb/fastboot? If so can you post the output of
Code:
fastboot getvar all
Please remove your imei and serial number before posting :good:

Danny201281 said:
Do you have an sdk installed on your pc for adb/fastboot? If so can you post the output of
Code:
fastboot getvar all
Please remove your imei and serial number before posting :good:
Click to expand...
Click to collapse
Just downloading sdk now but I used another program i found on my travels. Is this all the info you need?
C:\toolkit>fastboot getvar all
(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: XXXXXXXXX
(bootloader) imei: XXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4017mV
(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.052s
If you need other info ill post it when sdk is downloaded and installed
Thanks for your help!

Tommy_G5 said:
Just downloading sdk now but I used another program i found on my travels. Is this all the info you need?
C:\toolkit>fastboot getvar all
(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: XXXXXXXXX
(bootloader) imei: XXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4017mV
(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.052s
If you need other info ill post it when sdk is downloaded and installed
Thanks for your help!
Click to expand...
Click to collapse
Yep that's what we wanted, unfortunately there's no ruu for your phone
If you've got warranty on the device I would send it in for repair.
If you don't have warranty you gonna need to unlock the bootloader to do anything with it. If your gonna do it go here www.htcdev.com register an account and go to the Unlock My Bootloader section of the site and follow the instructions to unlock :good:

Ok. I will do that.
So once the bootloader is unlocked, what is my solution? installing a different Ruu? Or installing a different Rom (or are they the same thing)
Thanks
Tom

Tommy_G5 said:
Ok. I will do that.
So once the bootloader is unlocked, what is my solution? installing a different Ruu? Or installing a different Rom (or are they the same thing)
Thanks
Tom
Click to expand...
Click to collapse
Once your Unlocked you can flash a Custom or Unbranded Stock Rom. To be able to use RUU's you will need to go s-off. As your on hboot 1.57 the only way to s-off is Sunshine app. But this costs $25 to use. So I would just go with flashing a Custom Recovery and ROM for the time being. :good:

Unlocking the bootloader void warranty. If you have none, then proceed. In my opinion, your phone has suffered hardware failure and will not be recoverable, hence warranty.

Thanks
Thanks for the help guys. Turns out its still under warranty which is good news. I know with other custom roms you can use adb to retrive info off the device.
Any chance I can do the same, as most of the stuff is backed up except some photos ( last couple of months worth).
If not Ill get over it but just in case.
Thanks for your help so far.
Tom

[Q] Relocked bootloader while using custom software, hboot won't detect power button

So, here's the thing, I already posted on a thread but it seems it's actually full of people asking and the guys answering there are stumped with our problems so I came here.
My bootloader is locked because I (stupidly ) relocked it while trying to install a newer firmware via RUU so then it just locked me out and couldn't do anything until I installed the RUU update of the same version I was running.
It's working but not as intended.
I tried unlocking the bootloader again after installing the RUU but no luck, the token works but it just won't detect my power button when I try to accept but the button works perfectly while running the system.
Here's my getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4M.32.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.23.502.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: X
(bootloader) imei: X
(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: 4297mV
(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.072s

adkz25 said:
So, here's the thing, I already posted on a thread but it seems it's actually full of people asking and the guys answering there are stumped with our problems so I came here.
Click to expand...
Click to collapse
Actually they guy there, me, was really busy in the past days and wasn't able to answer everyone. You can't imagine how much PM and Quote I had in the last week And yes I agree with you, its really hard to troubleshoot in that thread since there's so many discussions going on at the same time.
My bootloader is locked because I (stupidly ) relocked it while trying to install a newer firmware via RUU so then it just locked me out and couldn't do anything until I installed the RUU update of the same version I was running.
It's working but not as intended.
I tried unlocking the bootloader again after installing the RUU but no luck, the token works but it just won't detect my power button when I try to accept but the button works perfectly while running the system.
Here's my getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4M.32.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.23.502.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: X
(bootloader) imei: X
(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: 4297mV
(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.072s
Click to expand...
Click to collapse
Its a pretty uncommon problem. When flashing a RUU, all partitions (except some partitions that are unique to each devices) are flashed back to stock, even the bootloader which make me believe its not a corrupt bootloader problem. So if after flashing a RUU, your phone still have some problems, its most likely an hardware problem... If the RUU flashed fine there is nothing more you can do on the software side.... THe only thing I can think is to use Sunshine S-OFF to unlock your bootloader but unfortunately it cost 25$ to use Sunshine but at least it will bypass that "power button not working only in bootloader" problem

Yeah, I figured you were real busy. )^:
I really don't mind paying for Sunshine to get S-Off but when I tried running it to get temp root it just says it failed and closes. Is there any way for me to get it working?

adkz25 said:
Yeah, I figured you were real busy. )^:
I really don't mind paying for Sunshine to get S-Off but when I tried running it to get temp root it just says it failed and closes. Is there any way for me to get it working?
Click to expand...
Click to collapse
I would try the same method they are using in the Verizon HTC One forum, get temp root using kingRoot then launch sunshine
http://forum.xda-developers.com/ver...root-root-method-bl-unlock-5-0-x-ota-t3122099

Yay! It worked. I'm S-Off and unlocked right now so I might try to install TWRP and stuff.
KingRoot worked like a charm, I didn't even need to re-run it and try to get some prompt, it just... worked and gave me temp root.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4M.32.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.23.502.4
(bootloader) version-misc: PVT SHIP S-OFF
.
Anyway, I still have a little doubt (unrelated to this issue but you seem to know your way around). Everything I posted in this and that thread went down because I tried to install this ROM and it said I needed some firmware flashed.
What I'm trying to get to is:
Do I really need to flash that firmware?
Is it flashed via TWRP?
Are those GPE roms worth it?
Anyways, thank you for helping me out.

adkz25 said:
Yay! It worked. I'm S-Off and unlocked right now so I might try to install TWRP and stuff.
KingRoot worked like a charm, I didn't even need to re-run it and try to get some prompt, it just... worked and gave me temp root.
.
Anyway, I still have a little doubt (unrelated to this issue but you seem to know your way around). Everything I posted in this and that thread went down because I tried to install this ROM and it said I needed some firmware flashed.
What I'm trying to get to is:
Do I really need to flash that firmware?
Is it flashed via TWRP?
Are those GPE roms worth it?
Anyways, thank you for helping me out.
Click to expand...
Click to collapse
Glad it worked!
Firmware files are flashed with fastboot in ruu mode:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip "file name".zip
fastboot flash zip "file name".zip
fastboot reboot-bootloader
Then go in recovery and flash the rom
Better to flash the latest firmware without stock recovery so you don't overwrite twrp recovery with the stock recovery.
Note that this firmware is the latest GPE firmware and that if you want to go back to stock rom using a ruu you'll have to reflash a hboot 1.57 or 1.61 firmware before running a 7.xx.xxx.xx Sense ruu.
GPE roms is perfect if you want something closer to a nexus experience, otherwise stay with a Sense rom.
Sent from my HTC One using XDA Labs

No ROM, No Recovery, Relocked, Tampered, Security Warning

I've been searching around for a solution to fix my device with all of my attempts failing. I have a HTC One M7 from Telus (Newfoundland, Canada) which is about 3 years old. It's in great condition and has been well taken care of. I had been using CM 12.1 and TWRP right up until a few days ago. My intentions were to bring my phone back to factory settings without any root capabilities as the newest update for Pokémon Go requires you to have an un-rooted device. Obviously my efforts to go back to factory settings were in vain as now my phone is basically one step away from being bricked. I can load up the bootloader just fine and acheive fastboot without any problems although anything beyond there fails everytime (ie. enter recovery mode).
I'm able to do stuff with it using ADB tools via my pc so not all hope is lost just yet. Could anyone provide step by step instructions on how to get the phone back to an untampered state as well as links to the files i'll need to do so? I have yet to find any ROM's for a TELUS M7 as well as the default recovery tools. I keep seeing links to utilities which apparently are a basic one-click-fix though none of them have worked thusfar (my most recent one is called "RUU_M7_UL_K44_SENSE55_MR_TELUS_WWE_4.19.661.8_R_Radio_4T.24.3218.09_10.26.1718.01L_release_351500_signed_2.exe" which seems to work right up until it gets to the HEADER portion where it doesn't move past 5%)
I've since bought a new phone which is an extreme pain to use as, in my opinion, it's a huge downgrade from what i've been using (LG-K121)
Any and all help is muchly appreciated [:=

kayohbe said:
I've been searching around for a solution to fix my device with all of my attempts failing. I have a HTC One M7 from Telus (Newfoundland, Canada) which is about 3 years old. It's in great condition and has been well taken care of. I had been using CM 12.1 and TWRP right up until a few days ago. My intentions were to bring my phone back to factory settings without any root capabilities as the newest update for Pokémon Go requires you to have an un-rooted device. Obviously my efforts to go back to factory settings were in vain as now my phone is basically one step away from being bricked. I can load up the bootloader just fine and acheive fastboot without any problems although anything beyond there fails everytime (ie. enter recovery mode).
I'm able to do stuff with it using ADB tools via my pc so not all hope is lost just yet. Could anyone provide step by step instructions on how to get the phone back to an untampered state as well as links to the files i'll need to do so? I have yet to find any ROM's for a TELUS M7 as well as the default recovery tools. I keep seeing links to utilities which apparently are a basic one-click-fix though none of them have worked thusfar (my most recent one is called "RUU_M7_UL_K44_SENSE55_MR_TELUS_WWE_4.19.661.8_R_Radio_4T.24.3218.09_10.26.1718.01L_release_351500_signed_2.exe" which seems to work right up until it gets to the HEADER portion where it doesn't move past 5%)
I've since bought a new phone which is an extreme pain to use as, in my opinion, it's a huge downgrade from what i've been using (LG-K121)
Any and all help is muchly appreciated [:=
Click to expand...
Click to collapse
Please, post the output of "fastboot getvar all" (don't post your imei and serialno).
Sent from my HTC One using XDA Labs

fastboot getvar all
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4266mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-eff4f609
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.127s

I recognize this is my own mistake as a result of being short sighted and not careful enough with my actions. Also, i'm willing to take any amount of time necessary to learn whatever skills may be required to resolve this issue (how to utilize certain tools properly, specific programming languages etc.)

kayohbe said:
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4266mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-eff4f609
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.127s
Click to expand...
Click to collapse
When a phone is S-ON you can only flash a RUU that is same or newer version than your actual version. Unfortunately your version-main is blank (this is bug caused by an old twrp version) so we can't exactly know the version it was running. The 1.61 hboot version and CID/MID suggest a 7.17.661.?? version. The newest RUU version available is 7.17.661.7
Try to flash it (from this thread: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944)
Use instruction provided at post #1 of that thread to flash the RUU ****make sure to use the fastboot version provided in that thread***.
If your phone was running a newer bersion than that (i.e 7.17.661.52) the RUU won't flash and we'll have to try something else.
Btw did you already relocked your bootloader? If no make sure to reflash the stock recovery over twrp before re-locking.

alray said:
When a phone is S-ON you can only flash a RUU that is same or newer version than your actual version. Unfortunately your version-main is blank (this is bug caused by an old twrp version) so we can't exactly know the version it was running. The 1.61 hboot version and CID/MID suggest a 7.17.661.?? version. The newest RUU version available is 7.17.661.7
Try to flash it (from this thread: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944)
Use instruction provided at post #1 of that thread to flash the RUU ****make sure to use the fastboot version provided in that thread***.
If your phone was running a newer bersion than that (i.e 7.17.661.52) the RUU won't flash and we'll have to try something else.
Btw did you already relocked your bootloader? If no make sure to reflash the stock recovery over twrp before re-locking.
Click to expand...
Click to collapse
Alrighty, just to reiterate before I get into it, you suggested I choose the 7.17.661.7 version correct?

kayohbe said:
Alrighty, just to reiterate before I get into it, you suggested I choose the 7.17.661.7 version correct?
Click to expand...
Click to collapse
Yep try this version first and if it's not working we'll try something else. You'll have to relock your bootloader before flashing the ruu, male sure to flash the stock recovery (linked above) before relocking.
Sent from my HTC One using XDA Labs

alray said:
Yep try this version first and if it's not working we'll try something else. You'll have to relock your bootloader before flashing the ruu, male sure to flash the stock recovery (linked above) before relocking.
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
My Bootloader has already been Relocked, should I be doing something else to get a working recovery on there before I begin flashing the RUU?

kayohbe said:
My Bootloader has already been Relocked, should I be doing something else to get a working recovery on there before I begin flashing the RUU?
Click to expand...
Click to collapse
No its to late, try the RUU.

Seems good [:=
Just finished the process & everything seems to be working just fine - i'm in the middle of the "optimizing apps 189 of 251" (das a lotta bloat lol) stage right now.
Any suggestions on what should be done next?
Also - thank you so friggen much for your help & I apologize for being so noob in these matters

kayohbe said:
Just finished the process & everything seems to be working just fine - i'm in the middle of the "optimizing apps 189 of 251" (das a lotta bloat lol) stage right now.
Any suggestions on what should be done next?
Also - thank you so friggen much for your help & I apologize for being so noob in these matters
Click to expand...
Click to collapse
no problem. Update your phone to the latest version before unlocking and rooting. The latest one is .52

One final question - is there a default recovery on there now that everything is set up and running properly or will I need to dig up a factory recovery, achieve S-OFF & flash it on there?

kayohbe said:
One final question - is there a default recovery on there now that everything is set up and running properly or will I need to dig up a factory recovery, achieve S-OFF & flash it on there?
Click to expand...
Click to collapse
When flashing a RUU, the stock recovery is installed on the phone. The stock recovery is very limited, it can be used to install ota updates, clear cache and factory reset. If you want to make a backup of your whole phone you'll need to unlock your bootloader and flash a custom recovery (preferably TWRP).

alray said:
When flashing a RUU, the stock recovery is installed on the phone. The stock recovery is very limited, it can be used to install ota updates, clear cache and factory reset. If you want to make a backup of your whole phone you'll need to unlock your bootloader and flash a custom recovery (preferably TWRP).
Click to expand...
Click to collapse
My only issue with going back to custom ROM's (which I waaay prefer over stock as stock ROM's are super limited in so many ways) is I will be prevented from playing Pokémon Go as Niantic have recently disallowed such operating systems from running their app altogether. I don't care for using apps which would be considered 'cheating' or 'exploiting' but with a custom ROM i'd be completely forced to stop playing it no matter how I choose to do so (yes it's silly that i'm basing my decision around that one simple game which isn't even all that great as far as Pokémon games go but it's what I do to pass time during my work breaks 6 nights a week).
Until a fail-safe workaround is made for this tiny issue, i'm stuck with Official 5.0.2 (blek!) and Sense - at the very least I can use a custom Launcher but that's about all I can do.

kayohbe said:
My only issue with going back to custom ROM's (which I waaay prefer over stock as stock ROM's are super limited in so many ways) is I will be prevented from playing Pokémon Go as Niantic have recently disallowed such operating systems from running their app altogether. I don't care for using apps which would be considered 'cheating' or 'exploiting' but with a custom ROM i'd be completely forced to stop playing it no matter how I choose to do so (yes it's silly that i'm basing my decision around that one simple game which isn't even all that great as far as Pokémon games go but it's what I do to pass time during my work breaks 6 nights a week).
Until a fail-safe workaround is made for this tiny issue, i'm stuck with Official 5.0.2 (blek!) and Sense - at the very least I can use a custom Launcher but that's about all I can do.
Click to expand...
Click to collapse
I played the game for 2-3 days at launch and it was easy to spoof a fake gps location to cheat. To do that I also had to hide the fact the I was using "mock location" from the developer options using an Xposed module or the game would detect it. I guess its also really easy to hide the fact the you are using a custom rom/root from pokémon go using the same method... Not tried but im sure it can be done.

I assume it was easy prior to the current update - they've cracked down on 'spoof players' about a week or so ago

Help for HTC - M7
Dear Sir
my phone stuck @HTC logo. not booting icant install new OS.
still S-On please help me to solve mobile software issue.
ready for the payment. if your solution success.
=-============================================
(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.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3AVW904592
(bootloader) imei: 359405054090020
(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: 3952mV
(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
i dont know whether i downloded file corect or not
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed
need step by step instruction

1191 said:
Dear Sir
my phone stuck @HTC logo. not booting icant install new OS.
still S-On please help me to solve mobile software issue.
ready for the payment. if your solution success.
=-============================================
(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.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3AVW904592
(bootloader) imei: 359405054090020
(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: 3952mV
(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
i dont know whether i downloded file corect or not
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed
need step by step instruction
Click to expand...
Click to collapse
Yes you've download the right file.
Instructions how to flash: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
(see post #1)