[Q] S-OFF a GPE Phone - One (M7) Q&A, Help & Troubleshooting

I have a genuine Htc One Google Play Edition Phone.
Get Vars :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.06.1700.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3992mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
Phone was unlocked (fastboot oem unlock) and rooted 2 months ago.
Now I messed things up by trying to install the 4.4 OTA using TWRP. With the OTA, I get a nice blue-screen. I had a backup so the phone is booting correctly now.
I want to install a factory image. From what I can gather, this is not like a Nexus phone and I cannot simply use fastboot to get back to stock. I must use RUU. Now : for RUU to work, I need to be S-OFF.
I searched a lot and there does not seem to be a way to put a GPE to SOFF. I tried RumRunners but it fails saying I'm not rooted (which is wrong since I'm rooted) and I'm not running an unsecure kernel (which is true). - again, this is a factory GPE HTC One.. unlocked and rooted. That is all.
So, am I missing something? I'm running HBOOT 1.54. Can I get this phone to turn the security off?

Whatever you do, do NOT lock the boot loader. Can NOT unlock boot loader, otherwise.

deleted

SaHiLzZ said:
Whatever you do, do NOT lock the boot loader. Can NOT unlock boot loader, otherwise.
Click to expand...
Click to collapse
Yeah, I figured that much.
I was finally able to update to 4.4. I simply flashed the stock recovery and it worked.. BUT now my phone boot loops!

Restore your nandroid. Or issue fastboot erase cache and do a factory rest from bootloader.

"fastboot erase cache" is the first thing I did. That's the thing : all the recoveries I try boot loop. The only one working is the stock one! With the stock one I sis a factory reset. Still no go.

Related

[Q] [Help] Brick help needed [Solved!]

I was trying to flash a ROM earlier today and didn't realize that I was S-on... This threw me into a Boot loop, I thought no problem i'll just wipe and flash a rom that doesn't need s-off. found one and it booted but I got force close errors all over the place. Then I decided I should just bring it back to stock.. which I was somewhat able to using GURU RUU. I have the phone able to boot 100% into the OS but due to a Firmware difference (that he mentions in his video...) My touch screen isn't functioning. My current state is able to boot into stock rom with no error but no touch screen, I can Load bootloader, fastboot, and recover (I have TWRP but CWM works as well). I have fastboot operations but no adb functionality with the one exception that I can run sideload in twrp and cwm. Not sure if it is a pc issue or a phone issue, although I have tried reinstalling drivers both with and with out sync installed. What is my next move? Do i get a OTG USB cable and do an OTA using a mouse? Or do I do something else? wanted to check with you guys before I jump out of the frying pan and into the fire... seems like i have been making one mistake after another on my own accord. thanks for you time and help. Here is a copy of my fastboot getvar all (with my imei censored of course)
Code:
getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT3C5W902089
(bootloader) imei: XXXXXXXXXXXXXXXX
(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-a85199f7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.109s
Use otg cable +USB mouse to control the phone
sent from my mobile device
update
I have my otg cable and im able to use the usb mouse with it but I am unable to check for the at&t software update... i click on it and it puls up for a second and then goes away... any ideas?
Idea
I read somewhere that I can flash firmware with s-on as long as i re-lock the bootloader and the mid and cid match on the firmware that i flash to it... this would be done in the ruu flash boot? does that sound right and would this allow me to either get the ota update or flash the correct ruu OR would it possible get my adb functionality back to my bootloader so i can s-off and flash a stock ruu?
medicsizzle said:
I was trying to flash a ROM earlier today and didn't realize that I was S-on... This threw me into a Boot loop, I thought no problem i'll just wipe and flash a rom that doesn't need s-off. found one and it booted but I got force close errors all over the place. Then I decided I should just bring it back to stock.. which I was somewhat able to using GURU RUU. I have the phone able to boot 100% into the OS but due to a Firmware difference (that he mentions in his video...) My touch screen isn't functioning. My current state is able to boot into stock rom with no error but no touch screen, I can Load bootloader, fastboot, and recover (I have TWRP but CWM works as well). I have fastboot operations but no adb functionality with the one exception that I can run sideload in twrp and cwm. Not sure if it is a pc issue or a phone issue, although I have tried reinstalling drivers both with and with out sync installed. What is my next move? Do i get a OTG USB cable and do an OTA using a mouse? Or do I do something else? wanted to check with you guys before I jump out of the frying pan and into the fire... seems like i have been making one mistake after another on my own accord. thanks for you time and help. Here is a copy of my fastboot getvar all (with my imei censored of course)
Code:
getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT3C5W902089
(bootloader) imei: XXXXXXXXXXXXXXXX
(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-a85199f7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.109s
Click to expand...
Click to collapse
You need to flash your touch drivers.
You are in a bit of pickle, as you can't flash anything. Can you run this RUU? http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
SaHiLzZ said:
You are in a bit of pickle, as you can't flash anything. Can you run this RUU? http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
Click to expand...
Click to collapse
I can try but I am stuck in S-on would this be an issue? and I can flash from cwm and twrp would a stock nandroid help?
What GURU Reset file did you use? If it is same as nandroid for ATT, then it wont help.
You will need to lock the bootloader and run the RUU file I linked. If RUU doesn't like something on your phone (CID/MID/MAIN-ver mismatch) it will fail before flashing. If it starts flashing you should have a working device at the end.
SaHiLzZ said:
What GURU Reset file did you use? If it is same as nandroid for ATT, then it wont help.
You will need to lock the bootloader and run the RUU file I linked. If RUU doesn't like something on your phone (CID/MID/MAIN-ver mismatch) it will fail before flashing. If it starts flashing you should have a working device at the end.
Click to expand...
Click to collapse
You are the BEST! Thank you so much.. I have been racking my head trying to get this fixed... I am up and running again! My process
1. I had my phone unlocked bootloader, s-on, and twrp recovery
2. booted into trwp, and adb pushed the Guru stock installer
3. installed the zip, selecting to wipe data, no super user, and then I put the stock recovery and radios on
4. rebooted into bootloader and locked my bootloader
5. rebooted phone
6. ran the RUU that you provided me. (Thanks again)
7. phone booted up 100% working!!!!
8. Gave credit where credit was due!

[Q] HTC M7 Half-way Bricked - need help

Hi Guys,
Here is the status:
Tampered, unlocked, rooted, S-On, ElementalX kernell, TWRP.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.5
(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__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 3947mV
(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
I have tried to run a OTA , it failed, did some weird stuff to the rom and now the HTC doesnt get recognized when booted up.
I have the ElementalX kernel and it doesnt work with SunShine so cant get S-Off, so cant run RUU.
I havent found flashable stock kernel?
Please, if you are able to advise on a step by step way of of getting out of this mess, id be really happy. Optionally you can live assist and i would be willing to compensate you for your time.
Thanks again
Gabriel
xxxx-g-xxxx said:
Hi Guys,
Here is the status:
Tampered, unlocked, rooted, S-On, ElementalX kernell, TWRP.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.5
(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__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 3947mV
(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
I have tried to run a OTA , it failed, did some weird stuff to the rom and now the HTC doesnt get recognized when booted up.
I have the ElementalX kernel and it doesnt work with SunShine so cant get S-Off, so cant run RUU.
I havent found flashable stock kernel?
Please, if you are able to advise on a step by step way of of getting out of this mess, id be really happy. Optionally you can live assist and i would be willing to compensate you for your time.
Thanks again
Gabriel
Click to expand...
Click to collapse
Try to relash your rom completely. There is a stock odexed zip for 6.09.401.5 available on arhd Web site. Stock recovery for that version is also available
Tried the stock recovery and it resulted into a red triangle with a excalamtion mark. I then tried to install ARHD 82 and that resulted in it being frozen at the boot screen. Then flashed the newest firmware as it seems ARHD requires it. After the firmware ARHD still didnt work, so i got my stock rom from 6.09.401.5 working with 6.09.401.10 firmware and tried to apply the 6.09.401.10 OTA, that resulted in the red triangle again.
Right now im at the original status with a working older stock rom, but i feel that i kinda dont have anywhere to move. Seems that the firmware contained stock kernel (if im not mistaken) so i may as well try sunshine to get S-OFF, but im not sure if it helps with the RUU. When i tried RUU before i got stuck at the checking headers.
xxxx-g-xxxx said:
Tried the stock recovery and it resulted into a red triangle with a excalamtion mark. I then tried to install ARHD 82 and that resulted in it being frozen at the boot screen. Then flashed the newest firmware as it seems ARHD requires it. After the firmware ARHD still didnt work, so i got my stock rom from 6.09.401.5 working with 6.09.401.10 firmware and tried to apply the 6.09.401.10 OTA, that resulted in the red triangle again.
Right now im at the original status with a working older stock rom, but i feel that i kinda dont have anywhere to move. Seems that the firmware contained stock kernel (if im not mistaken) so i may as well try sunshine to get S-OFF, but im not sure if it helps with the RUU. When i tried RUU before i got stuck at the checking headers.
Click to expand...
Click to collapse
Stock recovery is the red triangle .. the RUU won't work without s-off your firmware is to new to downgrade.
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then sideload ARHD 81 to your phone
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
Sunshine should work after ARHD is running

[SOLVED] at&t m7 relocked, s-on, tempered, security warning

To begin with, I'm not a very smart man. Some would call me an idiot. I started clicking things and I'm afraid I screwed up my phone
My AT&T M7 was bootloader unlocked, S-OFF, TWRP installed, Custom ROM (PA), and rooted. I wanted to sell it so I got a SIM Unlock code from AT&T. I went to input the unlock code and it wouldn't work. Apparently you have to be on stock hboot (which I wasn't since I did the google play edition conversion a long time ago) and on a stock ROM (which I also wasn't). So I tried to restore through an RUU.exe and it wouldn't work. RUU.zip didn't work either. So I restored my CID to CWS__001 and that didn't work (I had super CID before). I restored back to stock hboot 1.44 easily. Then I guess I somehow started just clicking random combinations of things inside of HTC One Toolkit and managed to relock my device and s-on so that I could try to restore a stock RUU. I must have done that incorrectly though because now I have no ROM installed, no recovery installed, and I'm S-ON with a message that says "security warning". I'm unable to flash a ROM since I don't have a recovery.
I went to HTC Dev to get an unlock code, which I did, but fastboot bootloader unlock says successful and does nothing. Additionally, I am unable to flash a recovery because I am S-ON.
Help! Any way to get S-OFF trough fastboot only without a ROM installed? Any way to force flash a recovery? Any way to force flash a ROM? Any way to get RUU to not spit out error 158? HELP!!!
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4T.27.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HTxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(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: 4233mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
ajr901 said:
To begin with, I'm not a very smart man. Some would call me an idiot. I started clicking things and I'm afraid I screwed up my phone
My AT&T M7 was bootloader unlocked, S-OFF, TWRP installed, Custom ROM (PA), and rooted. I wanted to sell it so I got a SIM Unlock code from AT&T. I went to input the unlock code and it wouldn't work. Apparently you have to be on stock hboot (which I wasn't since I did the google play edition conversion a long time ago) and on a stock ROM (which I also wasn't). So I tried to restore through an RUU.exe and it wouldn't work. RUU.zip didn't work either. So I restored my CID to CWS__001 and that didn't work (I had super CID before). I restored back to stock hboot 1.44 easily. Then I guess I somehow started just clicking random combinations of things inside of HTC One Toolkit and managed to relock my device and s-on so that I could try to restore a stock RUU. I must have done that incorrectly though because now I have no ROM installed, no recovery installed, and I'm S-ON with a message that says "security warning". I'm unable to flash a ROM since I don't have a recovery.
I went to HTC Dev to get an unlock code, which I did, but fastboot bootloader unlock says successful and does nothing. Additionally, I am unable to flash a recovery because I am S-ON.
Help! Any way to get S-OFF trough fastboot only without a ROM installed? Any way to force flash a recovery? Any way to force flash a ROM? Any way to get RUU to not spit out error 158? HELP!!!
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4T.27.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HTxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(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: 4233mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Click to expand...
Click to collapse
Try a different RUU like this one: http://www.htc1guru.com/dld/ruu_m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3_radio_4a-19-3263-13_10-38j-1157-04_release_334235_signed_2-exe/ In the future, don't use toolkits it is easy to lose track of what is really happening to your phone with them. It is better to stick with the raw commands of fastboot and adb. Use this tool to install them and most sites will give you the appropriate commands to perform the various tasks.
Try a different RUU like this one: http://www.htc1guru.com/dld/ruu_m7_u..._signed_2-exe/ In the future, don't use toolkits it is easy to lose track of what is really happening to your phone with them. It is better to stick with the raw commands of fastboot and adb. Use this tool to install them and most sites will give you the appropriate commands to perform the various tasks.
Click to expand...
Click to collapse
Holy **** you are the man! That worked! How did you know that was going to work?!?!
Thank you soooooo much! I love you. I owe you one.

[Q] Stuck in boot loop after HTC1GURU reset

I wanted to GPE my HTC One m7. Having HBoot 1.57 made things a bit hard. I tried Moonshine, Revone, Firewater and Rumrunner, with no luck.
I decided I would pay for SunShine, but I needed a working system first. The various versions of the aforementioned tools were tested on a variety of roms and versions, which probably made this a real mess.
I ended up using this guide to get back to stock rom with stock recovery. (Apparently I am too noob to post links :-/ Here was a link to HTC1Guru "Reset to Stock for S-On")
It works. However, after applying the hotfix for a new system update, and rebooting, dowloading and installing the new update (4.4.3), I get stuck in a boot loop. My bootloader is unlocked, and I can flash a recovery. Booting up recovery while in this boot loop state gives me the phone with a red triangle warning sign on it.
My phone is S-On, HBoot 1.57, bought in Europe, using the *.*.401.* ROMs.
I've tried installing the stock 4.2.2 ROM twice and then applying update, no success. Any ideas on what I can do to get back to a stock phone, not in a boot loop?
Thanks in advance.
Sklirg said:
I wanted to GPE my HTC One m7. Having HBoot 1.57 made things a bit hard. I tried Moonshine, Revone, Firewater and Rumrunner, with no luck.
I decided I would pay for SunShine, but I needed a working system first. The various versions of the aforementioned tools were tested on a variety of roms and versions, which probably made this a real mess.
I ended up using this guide to get back to stock rom with stock recovery. (Apparently I am too noob to post links :-/ Here was a link to HTC1Guru "Reset to Stock for S-On")
It works. However, after applying the hotfix for a new system update, and rebooting, dowloading and installing the new update (4.4.3), I get stuck in a boot loop. My bootloader is unlocked, and I can flash a recovery. Booting up recovery while in this boot loop state gives me the phone with a red triangle warning sign on it.
My phone is S-On, HBoot 1.57, bought in Europe, using the *.*.401.* ROMs.
I've tried installing the stock 4.2.2 ROM twice and then applying update, no success. Any ideas on what I can do to get back to a stock phone, not in a boot loop?
Thanks in advance.
Click to expand...
Click to collapse
The reason it's bootlooping is because the updates that you are downloading are trying to update your hboot, but because you are already on the latest hboot they are failing.
Could you post your fastboot getvar all please without the imei and serial numbers please.
Seanie280672 said:
The reason it's bootlooping is because the updates that you are downloading are trying to update your hboot, but because you are already on the latest hboot they are failing.
Click to expand...
Click to collapse
That makes sense.
Seanie280672 said:
Could you post your fastboot getvar all please without the imei and serial numbers please.
Click to expand...
Click to collapse
Of course!
Code:
λ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
*snip*
(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: 3956mV
(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.077s
Thanks
Sklirg said:
That makes sense.
Of course!
Code:
λ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
*snip*
(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: 3956mV
(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.077s
Thanks
Click to expand...
Click to collapse
Ok, first thing is first, you will need twrp 2.6.3.3 recovery on your phone, once that's done, push or sideload the Rom linked below, it's full stock Rom 6.09.401.12 so just one above yours, then flash it like any other Rom.
http://www.androidrevolution.org/downloader/download.php?file=One_6.09.401.12_odexed.zip
Seanie280672 said:
Ok, first thing is first, you will need twrp 2.6.3.3 recovery on your phone, once that's done, push or sideload the Rom linked below, it's full stock Rom 6.09.401.12 so just one above yours, then flash it like any other Rom.
Click to expand...
Click to collapse
Thank you! This worked wonders.
Sklirg said:
Thank you! This worked wonders.
Click to expand...
Click to collapse
Your welcome, that's what we're here for :good:

[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

Categories

Resources