Database Develop

[Q] Stuck at bootloader *Security warning* *SOLVED*

Hi
I think I made a huge mistake when relocking my bootloader, used the "fastboot oem relock" command before anything else. I was still on custom ROM (Google edition) When trying to update firmware it wouldnt let me flash it. It gets stuck on the sending image, it doesnt give a error report, it just keeps saying sending without anything happening. I then tried to unlock my bootloader again both with the old token, and also tried to get a new token from HTC Dev. Everytime it gets stuck on the "fastboot flash unlocktoken Unlock_code.bin" command. No error report, it just gets stuck at sending. Tried to leave it for up to 15 minutes without a luck.
I guess it got something do do with the bootloader version not match the recovery? My bootloader i sno locked, so cant get into recovery. I figured out that my only opition is to flash a stock RUU for my phone, but cant find anyone that works. Tried a few of them out there, both the executable desktop version and tried to flash to phone with adb commands. No luck, it just keep getting stuck. Anyone who can point me in the right direction?
This is my details from "fastboot getvar all"
C:\Android\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH34GW902611
(bootloader) imei: 354436055220667
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4295mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-f188f379dbbfee373cd551f7bc62b8435
getvar:all FAILED (unknown status code)
finished. total time: 0.057s
Thanks in advance!!

garman76 said:
Hi
I think I made a huge mistake when relocking my bootloader, used the "fastboot oem relock" command before anything else. I was still on custom ROM (Google edition) When trying to update firmware it wouldnt let me flash it. It gets stuck on the sending image, it doesnt give a error report, it just keeps saying sending without anything happening. I then tried to unlock my bootloader again both with the old token, and also tried to get a new token from HTC Dev. Everytime it gets stuck on the "fastboot flash unlocktoken Unlock_code.bin" command. No error report, it just gets stuck at sending. Tried to leave it for up to 15 minutes without a luck.
I guess it got something do do with the bootloader version not match the recovery? My bootloader i sno locked, so cant get into recovery. I figured out that my only opition is to flash a stock RUU for my phone, but cant find anyone that works. Tried a few of them out there, both the executable desktop version and tried to flash to phone with adb commands. No luck, it just keep getting stuck. Anyone who can point me in the right direction?
This is my details from "fastboot getvar all"
C:\Android\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH34GW902611
(bootloader) imei: 354436055220667
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4295mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-f188f379dbbfee373cd551f7bc62b8435
getvar:all FAILED (unknown status code)
finished. total time: 0.057s
Thanks in advance!!
Click to expand...
Click to collapse
does the bootloader say fastboot USB?
if you issue the command fastboot devices do you see the phone?
Unlocking should just work.
If you can't get it unlocked an RUU is your best bet.

gunnyman said:
does the bootloader say fastboot USB?
if you issue the command fastboot devices do you see the phone?
Unlocking should just work.
If you can't get it unlocked an RUU is your best bet.
Click to expand...
Click to collapse
My bootloader says fastboot usb in red. I can use the adb commands, and the device answears to the comands, but it's just keep getting stuck whatever I'm trying to push to the phone. recovery, RUU, unlock token, firmware.. nothing works, and it just freezes..
Need to reset phone with powerbutton for 15 seconds to get bootloader up again.
What RUU image would be my best shot based on my information?

garman76 said:
My bootloader says fastboot usb in red. I can use the adb commands, and the device answears to the comands, but it's just keep getting stuck whatever I'm trying to push to the phone. recovery, RUU, unlock token, firmware.. nothing works, and it just freezes..
Need to reset phone with powerbutton for 15 seconds to get bootloader up again.
What RUU image would be my best shot based on my information?
Click to expand...
Click to collapse
What does the security warning mean? It came when I relocked bootloader...

You get the security warning because you locked the phone while running a custom recovery. Hang on a few minutes and I will find the RUU you need
Edit :
There may not be one for your cid.
Try another cable, usb port, or computer to send the unlock token.

Thank you so very much!!
Found my old laptop running linux. Pushed the unlock token to the phone and there it went.
Unlocked again.
Knew I was missing something basic. Strange thing though, my adb drivers seemed to working fine, and has never given me a problem before.
Thanks a million.

Happy to help.
Now UNLESS you're doing an RUU install there is NO reason to lock the Bootloader.
Leave it alone

gunnyman said:
Happy to help.
Now UNLESS you're doing an RUU install there is NO reason to lock the Bootloader.
Leave it alone
Click to expand...
Click to collapse
No need to update firmware to flash Android Revolution Google edition?

garman76 said:
No need to update firmware to flash Android Revolution Google edition?
Click to expand...
Click to collapse
No and even if you did you'd want S-off and supercid bootloader lock wouldn't matter

[Q][SOLVED]One keeps rebooting/white HTC logo at welcome screen

Hi guys,
So I tried to restore to stock to send it in warranty to fix that darn camera tint issue.
I was on ARHD 31.6 (based on 4.3 and Sense 5.5 international. I managed to restore my CID and MID without issues, then I relocked and put S-ON.
Now I get boot loops avery 2 minutes after starting fine in my old rom backup and every rom I tried installs fine but after boot I get the screen and when I unlock it the screen gets stuck to a white screen with HTC logo on it (welcome screen?) which is weird since power button responds but nothing else works, it just stays in the white HTC logo screen and then reboots after 1-2 minutes or so.
On top of that I get TAMPERED in the boot loader which was not there before. I managed to unlock it again but I cannot get it to stay on as long as to get S-OFF with rumrunner to then modify MID\CID and run a RUU to restore it.
Anyone has any ideea how I can make this fonctional enough to be sent to HTC?

I think that my mistake was to enable back S-On. So does anyone has any idea on how to fix this? Have I managed to make myself a 600$ beautiful paperweight?

santarulz said:
Hi guys,
So I tried to restore to stock to send it in warranty to fix that darn camera tint issue.
I was on ARHD 31.6 (based on 4.3 and Sense 5.5 international. I managed to restore my CID and MID without issues, then I relocked and put S-ON.
Now I get boot loops avery 2 minutes after starting fine in my old rom backup and every rom I tried installs fine but after boot I get the screen and when I unlock it the screen gets stuck to a white screen with HTC logo on it (welcome screen?) which is weird since power button responds but nothing else works, it just stays in the white HTC logo screen and then reboots after 1-2 minutes or so.
On top of that I get TAMPERED in the boot loader which was not there before. I managed to unlock it again but I cannot get it to stay on as long as to get S-OFF with rumrunner to then modify MID\CID and run a RUU to restore it.
Anyone has any ideea how I can make this fonctional enough to be sent to HTC?
Click to expand...
Click to collapse
1- how stable is bootloader?
2- can you post a "fastboot getvar all" (remove IMEI and s/n)
3- what recovery are you on (name and version number please, not "latest")
4- what ROM are you on

1- stable, works fine, no reboots there
2- fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(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: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4279mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
3- I am using TWRP 2.6.3.1 and I tried also 2.6.3.3 while I was testing KitKat roms which also had the same behavior as first post
4- I was using ARHD 31.6 when I decided to go back to stock and that is the backup I have (rooted with debug on) but that one does not have the white page with HTC logo after screen unlock but still reboots after around 2 minutes like the other roms.

nkk71 said:
1- how stable is bootloader?
2- can you post a "fastboot getvar all" (remove IMEI and s/n)
3- what recovery are you on (name and version number please, not "latest")
4- what ROM are you on
Click to expand...
Click to collapse
I also do not have access to a RUU since I am with Bell in Canada and they are the worst of them all...
That would have simplified things I think...

santarulz said:
I also do not have access to a RUU since I am with Bell in Canada and they are the worst of them all...
That would have simplified things I think...
Click to expand...
Click to collapse
why not try a Guru Reset: http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-1-zip/
UNSELECT "stock recovery", if it's still randomly rebooting, we may need to check partitions for corruption (let's hope not)
flash it through the recovery you have like any custom rom, and hope it holds; report back and we'll take it from there...
---------- Post added at 08:28 PM ---------- Previous post was at 08:26 PM ----------
santarulz said:
1- stable, works fine, no reboots there
2- fastboot getvar all:
(bootloader) version-baseband: N/A
Click to expand...
Click to collapse
EDIT: is the above correct "N/A" on radio??? (or did you remove it)

nkk71 said:
EDIT: is the above correct "N/A" on radio??? (or did you remove it)
Click to expand...
Click to collapse
Dlding now guru reset.
I have not removed the radio, that is what it says. Could that cause it?

santarulz said:
Dlding now guru reset.
I have not removed the radio, that is what it says. Could that cause it?
Click to expand...
Click to collapse
maybe, in the Guru Reset, there is "stock radio", select it!! but unselect "stock recovery" you don't need that!
and then do a getvar again

nkk71 said:
maybe, in the Guru Reset, there is "stock radio", select it!! but unselect "stock recovery" you don't need that!
and then do a getvar again
Click to expand...
Click to collapse
Ok, so that did the trick!
c:\adb>fastboot getvar all
(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.24.401.1
(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: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4138mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
First try it got stuck for like an hour at 0%. I restarted it and tried again but did not selected any baseband (or stock recovery) to see if selecting those was making the aroma installer to get stuck. It went all that way like that but it was also bootlooping and showing the white screen. Then I installed it again with selecting baseband and it worked fine and rom is functional again. No bootloops and not more stuck white screen.
I wonder when the radio got wiped. I used the ENGHboot trick to modify cid\mid then run that su echo command to put LOCKED back then fastboot writesecureflag 3 to put S-ON. Weird but I learned something more today I guess
Thank you @nkk71. You saved me a lot of headaches

santarulz said:
Ok, so that did the trick!
c:\adb>fastboot getvar all
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
First try it got stuck for like an hour at 0%. I restarted it and tried again but did not selected any baseband (or stock recovery) to see if selecting those was making the aroma installer to get stuck. It went all that way like that but it was also bootlooping and showing the white screen. Then I installed it again with selecting baseband and it worked fine and rom is functional again. No bootloops and not more stuck white screen.
I wonder when the radio got wiped. I used the ENGHboot trick to modify cid\mid then run that su echo command to put LOCKED back then fastboot writesecureflag 3 to put S-ON. Weird but I learned something more today I guess
Thank you @nkk71. You saved me a lot of headaches
Click to expand...
Click to collapse
:good::good: glad all good now
"First try it got stuck for like an hour at 0%" -> i've noticed that a few times myself when flashing stuff, but if i wipe cache and dalvik before (in recovery) before beginning the install, it goes smoothly. (but then again aroma has been known to freeze sometimes)
So if all is good now, could i kindly ask you to edit main thread title to include [SOLVED], thanks

nkk71 said:
:good::good: glad all good now
"First try it got stuck for like an hour at 0%" -> i've noticed that a few times myself when flashing stuff, but if i wipe cache and dalvik before (in recovery) before beginning the install, it goes smoothly. (but then again aroma has been known to freeze sometimes)
So if all is good now, could i kindly ask you to edit main thread title to include [SOLVED], thanks
Click to expand...
Click to collapse
[SOLVED] added.
Thanks again!

[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 :/

Getting my phone back to 100% Stock

II see there are a lot of scenarious and ways to get your phone back to stock depending on the specific situation with your phone. well here's my phone. I'll be upgrading to an S5 here soon and plan on handing my phone down to my mom. I'd like to get it back to stock so when I bring to sprint there shouldn't be any issues getting it trasnfered over.
I am currently'
running the latest version of viper
It says S-ON on bootloader
HBOOT 1.57.0000
At the top it says tampered and unlocked
The recovery I am using is TWRP V2.8.1.0
Someone walk me through to this to get this thing to a point whre it looks like it has never been modified or send me to the appropriate guide. Thanks!

gravatrax1 said:
II see there are a lot of scenarious and ways to get your phone back to stock depending on the specific situation with your phone. well here's my phone. I'll be upgrading to an S5 here soon and plan on handing my phone down to my mom. I'd like to get it back to stock so when I bring to sprint there shouldn't be any issues getting it trasnfered over.
I am currently'
running the latest version of viper
It says S-ON on bootloader
HBOOT 1.57.0000
At the top it says tampered and unlocked
The recovery I am using is TWRP V2.8.1.0
Someone walk me through to this to get this thing to a point whre it looks like it has never been modified or send me to the appropriate guide. Thanks!
Click to expand...
Click to collapse
can you post the output of "fastboot getvar all" ? Remove your IMEI/MEID/SERIALNO before posting.

alray said:
can you post the output of "fastboot getvar all" ? Remove your IMEI/MEID/SERIALNO before posting.
Click to expand...
Click to collapse
Just stays stuck on "waiting for device" :/

gravatrax1 said:
Just stays stuck on "waiting for device" :/
Click to expand...
Click to collapse
Check your drivers in Windows device manager with the phone plugged in booted up and also in the boot loader, this is something your going to need to get working in order to get back to stock.

Seanie280672 said:
Check your drivers in Windows device manager with the phone plugged in booted up and also in the boot loader, this is something your going to need to get working in order to get back to stock.
Click to expand...
Click to collapse
When booted (into the OS) It shows a My Android Device in device manager, No errors of any kind. While on the bootloader it simply shows a "unknown device" in the USB tree. While in TWRP it shows the same thing as when booted into the OS.

gravatrax1 said:
When booted (into the OS) It shows a My Android Device in device manager, No errors of any kind. While on the bootloader it simply shows a "unknown device" in the USB tree. While in TWRP it shows the same thing as when booted into the OS.
Click to expand...
Click to collapse
You need to force the driver when in the boot loader then, just right click and select update driver, choose let me pick myself NOT let Windows search, it will fail, and from there go manual all the way till the driver is installed.
It should say myhtc in device e manager when booted and in recovery by the way, you can get the lastest drivers by downloading and installing HTC sync manager from HTC site, just be sure to uninstall HTC sync after the install from add remove programs, you should see HTC driver package just above it, leave that alone.

can u help me too
C:\adb>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.13.707.106
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxxxxx
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 3845mV
(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.049s
cant s-off tried all ways ..

navjot2785 said:
C:\adb>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.13.707.106
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxxxxx
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 3845mV
(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.049s
cant s-off tried all ways ..
Click to expand...
Click to collapse
There is only one method with a hboot 1.57 and it is Sunshine but it will cost $25.

i dnt have that much money .. any other way

navjot2785 said:
i dnt have that much money .. any other way
Click to expand...
Click to collapse
Unfortunately not!!!

any other way to revert back to stock 100% .so i can upgrade my firmware

navjot2785 said:
any other way to revert back to stock 100% .so i can upgrade my firmware
Click to expand...
Click to collapse
you can flash the same firmware that's on the phone now or higher
it has nothing to do with stock. If you want stock just flash a stock odex rom or find a nandroid of your carrier

i did had nandbackup of my rom .. am on s-on .. if i restore backup with twrp and change my recovery to stock and re lock my bootloader .. will my future updates will update my firmware to 7xxxxxxxxxx.. coz to update firmware rte now i need to be on s-off nd i cant s-off ..cant pay 25$

My mom is going to be the one using the phone. IS there any basically stock ROMS floating around out there? I just want to give the appearance when its booted up its stock. My only other concern is can the device be activated if its rooted and with a custom rom? Even the viper rom still maintains the auto activate feature it seems. I just want it to be stable for her so I don't have to constantly explains how to do things. As far as warranty goes she won't be maintain the equipment protection on the device so whatever happens to it is on her. I'm half tempted to see if there is something they might due about the cracked camera lense on it...I've had two htc ones so far and they haven't cost me anything to replace other htan the monthly insurance plan.

htc one m7 gpe stuck in bootloop

Hi all,
So I woke up this morning and power on my phone to find it stuck in some sort of boot loop. It loads to the home screen which seems like it might work but 30 seconds later it reboots on its own.
The phone is stock, unrooted and the bootloader is locked (and S-ON).
I already did a factory reset (wipe cache + data) but didn't work.
I'm trying to unlock the bootloader to flash a recovery and a new rom but I'm not able to do that.
I followed all the steps to unlock the bootloader as reported in HTCdev, but after I typed the last command
fastboot flash unlocktoken Unlock_code.bin
the "splash" screen didn't appear on my phone so I wasn't able to complete the unlock.
Can anyone help me with unlocking the bootloader?? Or did anyone know another method to unbrick my phone that is stuck in a bootloop??
Thank you in advance,
Mattia.

raffoaddicted said:
Hi all,
So I woke up this morning and power on my phone to find it stuck in some sort of boot loop. It loads to the home screen which seems like it might work but 30 seconds later it reboots on its own.
The phone is stock, unrooted and the bootloader is locked (and S-ON).
I already did a factory reset (wipe cache + data) but didn't work.
I'm trying to unlock the bootloader to flash a recovery and a new rom but I'm not able to do that.
I followed all the steps to unlock the bootloader as reported in HTCdev, but after I typed the last command
fastboot flash unlocktoken Unlock_code.bin
the "splash" screen didn't appear on my phone so I wasn't able to complete the unlock.
Can anyone help me with unlocking the bootloader?? Or did anyone know another method to unbrick my phone that is stuck in a bootloop??
Thank you in advance,
Mattia.
Click to expand...
Click to collapse
The bootloader unlock issue is well known on the gpe bootloaders and unfortunately, they never fixed it. Sunshine S-OFF willl be the only way to unlock (and s-off). Otherwise you could try a RUU if there is one for your phone (need to know you "fastboot getvar all").

alray said:
The bootloader unlock issue is well known on the gpe bootloaders and unfortunately, they never fixed it. Sunshine S-OFF willl be the only way to unlock (and s-off). Otherwise you could try a RUU if there is one for your phone (need to know you "fastboot getvar all").
Click to expand...
Click to collapse
Hi, thank you for your reply!
fastboot getvar all gives
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.27.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.09.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4291mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e02a9046
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
Thanks,
Mattia

raffoaddicted said:
Hi, thank you for your reply!
fastboot getvar all gives
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.27.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.09.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4291mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e02a9046
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
Thanks,
Mattia
Click to expand...
Click to collapse
This one should work
https://www.androidfilehost.com/?fid=24369303960689828

Hi,
I apologize for not answering sooner!
Btw, thank you for the file, but now... How am I supposed to preceed?
My problems are also that:
1) fastboot recognizes my phone, but adb does not. I'm confident that I actived usb debugging but i'm not totally sure of that... so I think that it's why adb doesn't find my phone.
2) as soon as try to do ''apply from storage" or "apply from sd card" in the recovery of my phone... it reboots with ''invalid operation, check cid failed".
Thank you so much, and sorry to bother you again, but i'm a novice.
Cheers,
mattia

raffoaddicted said:
Hi,
I apologize for not answering sooner!
Btw, thank you for the file, but now... How am I supposed to preceed?
My problems are also that:
1) fastboot recognizes my phone, but adb does not. I'm confident that I actived usb debugging but i'm not totally sure of that... so I think that it's why adb doesn't find my phone.
2) as soon as try to do ''apply from storage" or "apply from sd card" in the recovery of my phone... it reboots with ''invalid operation, check cid failed".
Thank you so much, and sorry to bother you again, but i'm a novice.
Cheers,
mattia
Click to expand...
Click to collapse
1)abd is only accessible from a custom recovery or from a booted OS. fastboot is the only thing you need to flash a ruu.
fastboot oem rebootRUU
fastboot flash zip "filename".zip
fastboot flash zip "filename".zip
fastboot reboot
If your bootloader is unlocked, you must relock it first using "fastboot oem lock"

alray said:
1)abd is only accessible from a custom recovery or from a booted OS. fastboot is the only thing you need to flash a ruu.
fastboot oem rebootRUU
fastboot flash zip "filename".zip
fastboot flash zip "filename".zip
fastboot reboot
If your bootloader is unlocked, you must relock it first using "fastboot oem lock"
Click to expand...
Click to collapse
ok!
Thank you!!