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:
Related
The phone is a brand new HTC One. After unlocking the bootloader, flashing TWRP 2.6.3.3, rooting it, and flashing a rom (tried insert coin and Sinless), the phone gets past the HTC logo, past the Google logo (Google edition rom), shows setup for a second, and reboots. It would do this until the battery dies. I can get into recovery fine, and do anything other than boot the rom. I've tried multiple roms, multiple recoveries, etc. What should I do? Thanks for any help!
Can you issue fastboot erase cache in bootloader and do a wipe data in recovery before booting?
SaHiLzZ said:
Can you issue fastboot erase cache in bootloader and do a wipe data in recovery before booting?
Click to expand...
Click to collapse
Did both. We wiped the phone completely as well and did it from scratch and it has the exact problem.
Can you post your fastboot getvar all output? Remove Imei
SaHiLzZ said:
Can you post your fastboot getvar all output? Remove Imei
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT3B5W907210
(bootloader) imei:
(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: 3951mV
(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.069s
You need to be S-Off to run any google edition roms. Listed on the first post of both sinless and arhd GE thread.
SaHiLzZ said:
You need to be S-Off to run any google edition roms. Listed on the first post of both sinless and arhd GE thread.
Click to expand...
Click to collapse
So do you think it will work if we use a Sense rom?
Also can you get S-Off in my situation? How so?
I'm new to this. Thanks for your help. I really appreciate it.
Better question: can we expect run Rumrunner without a functional OS?
You should be on sense based rom for Soff, or ATT nandroid or backup. Reinstall ATT RUU if one available, or adb push a rom in recovery
SaHiLzZ said:
You should be on sense based rom for Soff, or ATT nandroid or backup. Reinstall ATT RUU if one available, or adb push a rom in recovery
Click to expand...
Click to collapse
Feeling really dumb for not trying a Sense rom. One just worked. Thanks for your help!
Hello guys. I'm having troubles getting my One back to stock. It is bootloader unlocked.
First the getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SERIALNO
(bootloader) imei: 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: 3883mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I tried everything i could find to go back to stock. I tried restoring a nandroid backup and then updating, i tried flashing RUU for my devices but that gives me an error everytime. I locked the bootloader and updating but that didn't do anything. I tried Stock ROM – Guru Reset but after OTA update to 4.4.2 the phone doesn't boot anymore.
Must be something i'm missing, there is allot of information about the One M7. Maybe there is a official rom that i could flash and go from there. Just want to have a stock rom with KK.
Thanks in advance.
kollarik said:
Hello guys. I'm having troubles getting my One back to stock. It is bootloader unlocked.
First the getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SERIALNO
(bootloader) imei: 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: 3883mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I tried everything i could find to go back to stock. I tried restoring a nandroid backup and then updating, i tried flashing RUU for my devices but that gives me an error everytime. I locked the bootloader and updating but that didn't do anything. I tried Stock ROM – Guru Reset but after OTA update to 4.4.2 the phone doesn't boot anymore.
Must be something i'm missing, there is allot of information about the One M7. Maybe there is a official rom that i could flash and go from there. Just want to have a stock rom with KK.
Thanks in advance.
Click to expand...
Click to collapse
you cant use the guru-reset file because the version is too low for your HBOOT, the updates are failing causing a boot loop because they are trying to downgrade your HBOOT, not possible with s-on.
the RUU is also a lower version than you are currently running, and as you are s-on, you cant downgrade.
the only way you can get back to stock now is too unlock your bootloader, flash twrp recovery 2.6.3.3 and download stock odexed 5.11.401.10 rom from here: http://android-revolution-hd.blogspot.co.uk/p/android-revolution-hd-mirror-site-var.html
flash it through recovery, after its installed and your phone is set back up, if you want to be fully stock, download the recovery from the same page and flash that.
U can used firewater to get S-OFF and then used RUU.zip to return to stock
Link: http://firewater-soff.com/instructions/
I will try the solution Seanie280672 recomended. I can't get S-OFF for my device.
kollarik said:
I will try the solution Seanie280672 recomended. I can't get S-OFF for my device.
Click to expand...
Click to collapse
s-off is very hard with 1,57 hboot, some people are having success, most arnt still.
Yep. I'm one of those that get this: whelp, this sucks, firewater can not work on your device no amount of reflashing, retrying, or ruuing will fix...
BTW, thank you for your qiuck reply.
kollarik said:
Yep. I'm one of those that get this: whelp, this sucks, firewater can not work on your device no amount of reflashing, retrying, or ruuing will fix...
BTW, thank you for your qiuck reply.
Click to expand...
Click to collapse
Yup, I used to get that message too, I got s-off in the end with a java card by taking my phone to these guys, they also have a mail in service if your in the EU and can live without your phone for a few days:
http://www.fonefunshop.co.uk/Unlocking/htc_s-off_service.htm
Well if i can get it stock i will leave it like that. I had so much headache in last 2 days with this phone. :laugh:
Worked like a charm. Seanie280672 thank you! You saved me.:highfive:
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
I rooted my M7 and put CyanogenMod on it. Now I need to sell it and am struggling getting it back to factory.
First I tried the method from here: http://forum.xda-developers.com/showthread.php?t=2658910
I relocked the bootloader (though it does say "tampered" and "relocked"...but my buyer won't care). When I did that, it wouldn't allow me to boot back into CyanogenMod any more...which is fine, cause I want to restore to factory anyway. I then ran the EXE file in the zip from that thread and It gets hung up at 4% (verifying headers). I have HBoot 1.57.0000 so I figured that should work.
I let it sit for about an hour and it never progressed so I just unplugged the USB and held the pwr button on the phone until it turned off. I tried again with the same result. One thing to note, on the screen where it says "Current information about your Android phone -> Image Version is blank. When I click the Update button, it says it's going to replace it with version xxx (forget the number but at least that's showing).
After that failed a few times, I googled for another resource and found this: http://htc-one.wonderhowto.com/how-...actory-settings-for-warranty-repairs-0149204/
because I couldn't boot the phone I couldn't do the first step so I tried d/ling the two sprint RUUs and running the exe's in those zips. I get the same result for the current version (blank) but it doesn't hang at 4% (verifying headers), it hangs at "Sending....." when it's "Updating the ROM image on your phone"
I'm stuck here. any ideas of what I should be trying to get this thing back to factory?
BurritoSmithJohnson said:
I rooted my M7 and put CyanogenMod on it. Now I need to sell it and am struggling getting it back to factory.
First I tried the method from here: http://forum.xda-developers.com/showthread.php?t=2658910
I relocked the bootloader (though it does say "tampered" and "relocked"...but my buyer won't care). When I did that, it wouldn't allow me to boot back into CyanogenMod any more...which is fine, cause I want to restore to factory anyway. I then ran the EXE file in the zip from that thread and It gets hung up at 4% (verifying headers). I have HBoot 1.57.0000 so I figured that should work.
I let it sit for about an hour and it never progressed so I just unplugged the USB and held the pwr button on the phone until it turned off. I tried again with the same result. One thing to note, on the screen where it says "Current information about your Android phone -> Image Version is blank. When I click the Update button, it says it's going to replace it with version xxx (forget the number but at least that's showing).
After that failed a few times, I googled for another resource and found this: http://htc-one.wonderhowto.com/how-...actory-settings-for-warranty-repairs-0149204/
because I couldn't boot the phone I couldn't do the first step so I tried d/ling the two sprint RUUs and running the exe's in those zips. I get the same result for the current version (blank) but it doesn't hang at 4% (verifying headers), it hangs at "Sending....." when it's "Updating the ROM image on your phone"
I'm stuck here. any ideas of what I should be trying to get this thing back to factory?
Click to expand...
Click to collapse
post your "fastboot getvar all" except your imei/meid/serialno
@alray here you go
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0904_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
...
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e1af350
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.046s
BurritoSmithJohnson said:
@alray here you go
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0904_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
...
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e1af350
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.046s
Click to expand...
Click to collapse
4.06.651.4 RUU is for hboot 1.56 and yours is 1.57 so you can't use that one with S-ON
try the 5.03.651.3 RUU from here: http://forum.xda-developers.com/showthread.php?t=2503646
or the 5.05.651.2 RUU should be better but im not sure if this one can be flashed with s-on, better to ask there.
alray said:
4.06.651.4 RUU is for hboot 1.56 and yours is 1.57 so you can't use that one with S-ON
try the 5.03.651.3 RUU from here: http://forum.xda-developers.com/showthread.php?t=2503646
or the 5.05.651.2 RUU should be better but im not sure if this one can be flashed with s-on, better to ask there.
Click to expand...
Click to collapse
this got me there, thanks. How do I give you an upvote or whatever for your assistance?
BurritoSmithJohnson said:
this got me there, thanks. How do I give you an upvote or whatever for your assistance?
Click to expand...
Click to collapse
So your phone is ok now?
If you want to thanks someone on xda, just click the "thanks" button below his avatar.
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