EDIT: Well this is awkward. After posting this thread I found the solution. If anyone in the future has the same problems as me, just flash one of these
http://forum.xda-developers.com/showthread.php?t=2406330
Apparently that was all that was needed.
Hello xda community,
First off, I apologize. I know questions like these get asked hundreds of times but after spending 3 days straight of digging through forum threads and making very little progress I've decided to just ask.
So I tried installing a custom rom on my HTC One. I did exactly what I usually do when flashing a new rom on my nexus 7. I had an unlocked device with the latest twrp recovery. I did an advanced wipe (which included internal storage), then I did an adb sideload to flash the rom. I must have done something wrong because the flashing didn't work and ever since then I've been trying to get back to stock rom.
I've tried running both the 3.04.651.2 RUU and the 4.06.651.4 RUU posted by O.M.J and neither worked. I've tried flashing the Guru Reset M7 Sprint 3.04.651.2 rom found on htc1guru. Twrp said the flashing was successful yet when I booted up the device it would get to the lockscreen and when I tried to unlock it, it would just show the HTC logo. After that it would endlessly reboot itself over and over. I've tried flashing the Android Revolution HD 31.6 rom and I got the same problems as when I tried to flash the htc1guru stock rom.
I can get into both the bootloader and twrp recovery without any problems so I figure not all hope is lost. Below is info about my phone. As you can see the version-main number is missing, though I don't know how important that is.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: X
(bootloader) imei: X
(bootloader) meid: X
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4315mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.037s
I'm not sure if it's significant, but I did manage to flash that custom rom today. It's the Slim-m7spr-4.4.2.build.5 rom. I booted up the phone just fine (this is probably the only successful thing I've done so far).
Anyway, like I said I'm trying to get back to stock and I would appreciate any and all help. Thanks guys.
Related
So I woke up today and decided I wanted to get a custom ROM on my HTC One. This sounded all good. I unlocked the bootloader and rooted the rom. All was fine until I tried to flash a custom rom. I had the ViperOne ROM ready to go but it would install and then get stuck on the loading. I presumed I would just have to wipe everything and then re-install the zip. This is where I messed up. I wiped the MicroSD in which the zip was originally on.
So now I am left with a device that has no OS. Basically a paperweight. From looking around I have found some topics that say that I just need to flash a RUU back onto the phone but something always fails and never works out.
As of right now, ADB is NOT working and the only way I can access the phone is through fastboot.
Here is my getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.63.980.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: --------------------
(bootloader) imei: -----------------------
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__039
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-fd1bd949
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.050s
From the info above I went and downloaded "RUU Zip M7 Google Edition 4.4 3.58.1700.5" from htc1guru though when I went to install it, it failed. Putting me back at square 1.
Please help!!
Thanks in advance
DarkShock124 said:
So I woke up today and decided I wanted to get a custom ROM on my HTC One. This sounded all good. I unlocked the bootloader and rooted the rom. All was fine until I tried to flash a custom rom. I had the ViperOne ROM ready to go but it would install and then get stuck on the loading. I presumed I would just have to wipe everything and then re-install the zip. This is where I messed up. I wiped the MicroSD in which the zip was originally on.
So now I am left with a device that has no OS. Basically a paperweight. From looking around I have found some topics that say that I just need to flash a RUU back onto the phone but something always fails and never works out.
As of right now, ADB is NOT working and the only way I can access the phone is through fastboot.
Here is my getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.63.980.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: --------------------
(bootloader) imei: -----------------------
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__039
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-fd1bd949
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.050s
From the info above I went and downloaded "RUU Zip M7 Google Edition 4.4 3.58.1700.5" from htc1guru though when I went to install it, it failed. Putting me back at square 1.
Please help!!
Thanks in advance
Click to expand...
Click to collapse
You will need to buy a USB OTG cable, which costs about $5. This is a microUSB to full USB cable. On a FAT32-formatted USB, transfer the ViperOne zip to the USB storage. Then, in TWRP recovery, choose the /usb otg directory. Then, flash the ViperOne zip from TWRP.
FYI, you cannot flash a Google Play RUU if you're S-ON. The phone needs to be S-OFF for that
raghav kapur said:
You will need to buy a USB OTG cable, which costs about $5. This is a microUSB to full USB cable. On a FAT32-formatted USB, transfer the ViperOne zip to the USB storage. Then, in TWRP recovery, choose the /usb otg directory. Then, flash the ViperOne zip from TWRP.
FYI, you cannot flash a Google Play RUU if you're S-ON. The phone needs to be S-OFF for that
Click to expand...
Click to collapse
Ok so i got the cable and flashed the ROM, now it is getting to the boot and just rebooting into TWRP.
The only error I got during the installation was the "set_metadata_recursive: some changes failed"
What version of twrp?
sent from my mobile device
SaHiLzZ said:
What version of twrp?
sent from my mobile device
Click to expand...
Click to collapse
Yeah that was the problem. The version was old and it was reported to have those issues. I flashed the newest version of the recovery and the installation went fine and I have my phone back now.
Thanks anyway
This was my first time messing with my phones ROM, I am completely new to this, and I bricked my phone. Here is what happened.
I rooted my phone using the guide from htconeroot.com
Everything worked fine.
Then I followed a guide from htconeroot to install android 4.4 kitkat ROM
That is when my phone got stuck in bootloader. I could run recovery with clockworkmod but when i went to the back up file in my sdcard the folder was empty. I tried factory reset and erasing cache to no avail. I finally found a guide by qbking77 called "how to unroot/unbrick the htc one to stock" and have been attempting various RUU versions trying to get it to take. I always get ERROR 155 The ROM Update Utility cannot update your Android phone. After running the RUU I can no longer run recovery with clockworkmod.
I have spent all weekend trying to educate myself and get this fixed but I am lost.
Here is my getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0515
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: 0000000000000
(bootloader) imei:00000000000000000
(bootloader) meid: 0000000000000000
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3808mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thank you in advance for any advice.
Well the first thing I noticed is you have an m7 wls, this is the spirint version of the HTC one, completely different to the normal version, so stop flashing things before you really do brick your phone, if you can get into the bootloader then your not bricked, yet, if you continue to try and flash wrong things you stand a high chance of messing up your blocks and partitions. Get yourself over to the m7 spirint forums for help.from here, just search for it above in the find your device box.
Seanie280672 said:
Well the first thing I noticed is you have an m7 wls, this is the spirint version of the HTC one, completely different to the normal version, so stop flashing things before you really do brick your phone, if you can get into the bootloader then your not bricked, yet, if you continue to try and flash wrong things you stand a high chance of messing up your blocks and partitions. Get yourself over to the m7 spirint forums for help.from here, just search for it above in the find your device box.
Click to expand...
Click to collapse
Didn't realize they had separate forum for the different service providers. ty.
Kunigaz said:
Didn't realize they had separate forum for the different service providers. ty.
Click to expand...
Click to collapse
Your welcome, not a different service provider, a different phone, it's not a gsm phone.
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:
I'm new to the HTC One and I almost didn't know what I was doing, so I messed up really bad.
What did I do:
My friend wanted to try cm11 in his phone, so I unlocked the bootloader, installed cmw 6.0.2.8 and then the cm11 rom. It all went fine, but he realized that a lot of data he had wasn't recovered by Google's backups. so I thought that installing a rom with htc sense we could recover the majority of contacts and other things that he had. So I downloaded and installed this rom:
HTML:
http://forum.xda-developers.com/showthread.php?t=2626050
and installed it (wrong rom). When the installation finished, the phone rebooted into bootloader with the 'Active cmdline overflow' error.
I tried different solutions but nothing worked for me.
So, here goes the phone's info: (I got it in RUU mode, I hope it doesn't matter)
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA**********
(bootloader) imei: 35*************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG309
(bootloader) battery-status: good
(bootloader) battery-voltage: 3866mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-d2906a15
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I flashed recovery a few times, always erasing cache, but I still can't enter recovery.
I hope someone can help me.
Frinalal said:
I'm new to the HTC One and I almost didn't know what I was doing, so I messed up really bad.
What did I do:
My friend wanted to try cm11 in his phone, so I unlocked the bootloader, installed cmw 6.0.2.8 and then the cm11 rom. It all went fine, but he realized that a lot of data he had wasn't recovered by Google's backups. so I thought that installing a rom with htc sense we could recover the majority of contacts and other things that he had. So I downloaded and installed this rom:
HTML:
http://forum.xda-developers.com/showthread.php?t=2626050
and installed it (wrong rom). When the installation finished, the phone rebooted into bootloader with the 'Active cmdline overflow' error.
I tried different solutions but nothing worked for me.
So, here goes the phone's info: (I got it in RUU mode, I hope it doesn't matter)
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA**********
(bootloader) imei: 35*************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG309
(bootloader) battery-status: good
(bootloader) battery-voltage: 3866mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-d2906a15
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I flashed recovery a few times, always erasing cache, but I still can't enter recovery.
I hope someone can help me.
Click to expand...
Click to collapse
this fix is touch and go with your current hboot, give it a try, if it works then :fingers-crossed: if not then its :crying: as your s-on
http://forum.xda-developers.com/showthread.php?t=2739126
Seanie280672 said:
this fix is touch and go with your current hboot, give it a try, if it works then :fingers-crossed: if not then its :crying: as your s-on
Click to expand...
Click to collapse
Yes, I alredy tried it, but after installing the noBCB recovery, I still cant access it.
I also searched for nand backups for my CID, but there aren't any. (I don't know if that would even help at all)
Frinalal said:
Yes, I alredy tried it, but after installing the noBCB recovery, I still cant access it.
I also searched for nand backups for my CID, but there aren't any. (I don't know if that would even help at all)
Click to expand...
Click to collapse
nope, nothing will work until you fix that error.
if you carry on reading through that thread you will see that people experiencing that problem have had to downgrade their HBOOT in order to get it to work, unfortunately you need to be s-off to do that, I think one user had success using a certain version of cwm recovery, here you go, try this:
http://forum.xda-developers.com/showpost.php?p=53634257&postcount=90
Seanie280672 said:
nope, nothing will work until you fix that error.
if you carry on reading through that thread you will see that people experiencing that problem have had to downgrade their HBOOT in order to get it to work, unfortunately you need to be s-off to do that, I think one user had success using a certain version of cwm recovery, here you go, try this:
Click to expand...
Click to collapse
Thanks for helping. I tried it and it still doesn't work. I'll keep searching around the forums to see if I can do anything.
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