Related
I'm on Paranoid ROM (last).
Bootloader 3.16.
I would like 3.19 or .18 in order to use Android 5.0 (CM 12).
Miqueas111 said:
I'm on Paranoid ROM (last).
Bootloader 3.16.
I would like 3.19 or .18 in order to use Android 5.0 (CM 12).
Click to expand...
Click to collapse
What exact variant do you have and have you achieved S-OFF yet ?
jball said:
What exact variant do you have and have you achieved S-OFF yet ?
Click to expand...
Click to collapse
I have the 3.16 bootloader, and I have no idea of S-OFF, so i guess I'm S-ON .
Miqueas111 said:
I have the 3.16 bootloader, and I have no idea of S-OFF, so i guess I'm S-ON .
Click to expand...
Click to collapse
Don't guess. Boot into bootloader, and it will say either s-on or s-off near the top.
By variant, jball is asking what carrier version or CID.
Flash the proper firmware package for your CID, if its in the collection:
http://forum.xda-developers.com/showthread.php?t=2696282
Or alternately return to stock ROM and stock recovery, than official OTA to update to hboot 3.17 then 3.19.
http://forum.xda-developers.com/showthread.php?t=2701376
redpoint73 said:
Don't guess. Boot into bootloader, and it will say either s-on or s-off near the top.
By variant, jball is asking what carrier version or CID.
Flash the proper firmware package for your CID, if its in the collection:
http://forum.xda-developers.com/showthread.php?t=2696282
Or alternately return to stock ROM and stock recovery, than official OTA to update to hboot 3.17 then 3.19.
http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
I'm having the same issue as the OP. Trying to get to Lollipop from the latest Paranoid Android ROM. Here's the output of fastboot getvar all in the spoiler. Can you please tell me exactly what to do, in what order, and what specific files to flash in order to get my phone updated to a 5.0 ROM? I've been trying to follow this post, but something's just not clicking for me. I've already bricked my phone to the point where flashing the RUU from HTCDev was the only thing that'd save it - two separate times. Believe I am s-off, with TWRP 2.7.0.1 installed, but on the AT&T Stock ROM 1.58.502.1. Checked for OTAs, and I'm apparently up to date...
Code:
C:\One_M8_All-In-One_Kit_v\data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.58.502.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA43NWM03051
(bootloader) imei: 358718050169510
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.020s
C:\One_M8_All-In-One_Kit_v\data>
@bassitone
How does anyone not know if they are S-OFF/S-ON ?
Did you buy your phone second hand ?
Do you know how to boot into hboot/bootlooader mode witch will inform you if your S-OFF or S-ON
Have you tried an up to date twrp cause the one your on is very old.
At&t is furthest from receiving OTA's in my opinion
jball said:
@bassitone
How does anyone not know if they are S-OFF/S-ON ?
Did you buy your phone second hand ?
Do you know how to boot into hboot/bootlooader mode witch will inform you if your S-OFF or S-ON
Have you tried an up to date twrp cause the one your on is very old.
At&t is furthest from receiving OTA's in my opinion
Click to expand...
Click to collapse
His fastboot getvar all output clearly states SECURITY - OFF ...... so he has an S-OFF device.
Mr Hofs said:
His fastboot getvar all output clearly states SECURITY - OFF ...... so he has an S-OFF device.
Click to expand...
Click to collapse
Right, yet he still states
"I believe I'm S-OFF"
jball said:
Right, yet he still states
"I believe I'm S-OFF"
Click to expand...
Click to collapse
Because I wasn't sure if something I did yesterday managed to undo my s-off status. First HTC device, and I went pretty far in restoring to stock
Thread cleaned.
Keep it CIVIL please.
bassitone said:
I'm having the same issue as the OP. Trying to get to Lollipop from the latest Paranoid Android ROM. Here's the output of fastboot getvar all in the spoiler. Can you please tell me exactly what to do, in what order, and what specific files to flash in order to get my phone updated to a 5.0 ROM? I've been trying to follow this post, but something's just not clicking for me. I've already bricked my phone to the point where flashing the RUU from HTCDev was the only thing that'd save it - two separate times. Believe I am s-off, with TWRP 2.7.0.1 installed, but on the AT&T Stock ROM 1.58.502.1. Checked for OTAs, and I'm apparently up to date...
Click to expand...
Click to collapse
I would suggest the following thread, which has explicit step-by-step instruction on how to update firmware:
http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
"3.28.1540 firmware only" file is what you want.
****ed up and didn't read things properly. I was trying to revert my phone to stock with an HTC RUU, that didn't work, and in haste and anger I set S-ON. On a device running CyanogenMod.
The threads I found on the subject weren't entirely helpful, so I'm here now, hoping I don't have to explain to HTC why I'm dumb. My device boots immediately to fastboot:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M8_UL_CA PVD SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1.14.21331931.LA02_2G
OpenDSP-v32.2.2-00542-M8974.0213
OS-2.12.1700.1
eMMC-boot 2048MB
Jun 16 2014,18:47:55.0
Here's the output of fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.12.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA45P
(bootloader) imei: 35871
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.131s
If anyone has advice, I'd appreciate it. Thanks!
Delete your IMEI and serial number. Those are personal data, which should never be posted on open forums.
Which RUU? Only an AT&T RUU will work unless you modify MID/CID by s-off.
An AT&T RUU should work.
redpoint73 said:
Delete your IMEI and serial number. Those are personal data, which should never be posted on open forums.
Which RUU? Only an AT&T RUU will work unless you modify MID/CID by s-off.
An AT&T RUU should work.
Click to expand...
Click to collapse
Thanks, I'll make sure to edit those out if I post again. A mod did that this time, hooray.
It was an AT&T RUU. At one point, I installed a stock GPE ROM and might have changed my MID, but don't quite remember. I remember that I changed my CID, but changed it back for the AT&T RUU. Judging by this thread, my MID is an "AT&T, unlocked, developer ID", so I guess it'll work.
If it helps, the specific RUU I used was named RUU_M8_UL_K44_SENSE60_ATT_SECURITY_Cingular_US_1.58.502.1_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_368350_signed_2. I downloaded it from HTC.
BaconSupreme said:
Thanks, I'll make sure to edit those out if I post again. A mod did that this time, hooray.
Click to expand...
Click to collapse
That's because I reported to the mods to delete the personal data.
BaconSupreme said:
It was an AT&T RUU. At one point, I installed a stock GPE ROM and might have changed my MID, but don't quite remember. I remember that I changed my CID, but changed it back for the AT&T RUU. Judging by this thread, my MID is an "AT&T, unlocked, developer ID", so I guess it'll work..
Click to expand...
Click to collapse
Your CID and MID are the correct one for AT&T.
BaconSupreme said:
If it helps, the specific RUU I used was named RUU_M8_UL_K44_SENSE60_ATT_SECURITY_Cingular_US_1.58.502.1_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_368350_signed_2. I downloaded it from HTC.
Click to expand...
Click to collapse
That RUU will fail, since it corresponds to hboot 3.16; and with s-on you can't run an RUU with a lower number hboot than is installed on the phone (3.18 in your case). Any other RUU except that one should work. You can find the other RUUs on my AT&T specific Index thread:
http://forum.xda-developers.com/showthread.php?t=2751432
Bad news first: the only RUU in that thread (the 4.4.4 one from HTC) that I could have used didn't work and gave me an unknown error (155). The other executable was the one I was already using and all the others require a microSD card, which I don't own.
Good news instead: This was fixed by... unlocking my bootloader again. Once I did that, my phone booted into CWM which was still installed and then booted into Cyanogenmod which was still there due to all the failed RUUs not doing anything. Hooray!
Thanks for the help, redpoint.
BaconSupreme said:
Bad news first: the only RUU in that thread (the 4.4.4 one from HTC) that I could have used didn't work and gave me an unknown error (155). The other executable was the one I was already using and all the others require a microSD card, which I don't own.
Click to expand...
Click to collapse
Actually, you discovered an error in my Index thread, as the "Official" 4.4.3 RUU link should go here:
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Instead of incorrectly sending you to the "bootable" RUU.
Not sure why the 4.4.4 RUU is giving your error 155 (wrong image).
BaconSupreme said:
Good news instead: This was fixed by... unlocking my bootloader again. Once I did that, my phone booted into CWM which was still installed and then booted into Cyanogenmod which was still there due to all the failed RUUs not doing anything. Hooray!
Click to expand...
Click to collapse
You actually never mentioned what the original issue with CWM was. Did it not boot?
I think relocking the bootloader wipes the phone. So maybe that was all that was needed to get CWM to boot.
redpoint73 said:
Actually, you discovered an error in my Index thread, as the "Official" 4.4.3 RUU link should go here:
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Instead of incorrectly sending you to the "bootable" RUU.
Not sure why the 4.4.4 RUU is giving your error 155 (wrong image).
You actually never mentioned what the original issue with CWM was. Did it not boot?
I think relocking the bootloader wipes the phone. So maybe that was all that was needed to get CWM to boot.
Click to expand...
Click to collapse
Yeah, I couldn't boot into CWM. Fastboot > HBoot > Recovery... poof, back into Fastboot.
Hey so I had converted my M8 to GPe but am now selling it so I'm putting it back to Sense. Everything's working except for the wifi which I had issues with in the past from not flashing the Telus firmware.zip again from a 4.4.4 OTA file. At this link http://d-h.st/BfV the OTA file is there but there's only two fake looking download buttons that Chrome says both are malicious. One downloads an .exe and the other gets outright blocked. Can anyone help me out with finding the OTA file for Telus?
Thanks, I'm selling the phone in a few hours and am freaking as the wifi doesn't currently work! :/
Bump I just need the firmware.zip for Telus, the official OTA Collection on this forum's links are busted for me at least.
Hendrycks said:
Bump I just need the firmware.zip for Telus, the official OTA Collection on this forum's links are busted for me at least.
Click to expand...
Click to collapse
the blue download now button is the one you need, its not fake, the ota will have the firmware you need.
Are you s-off ?
Seanie280672 said:
the blue download now button is the one you need, its not fake, the ota will have the firmware you need.
Are you s-off ?
Click to expand...
Click to collapse
Oh ok, and ya I am but I used a different firmware and now my phone's got the HTC silver logo with 4 triangles with exclamation points in each other. I can only see that screen or what looks like the bootloader but it says the following:
HBOOT-3.19.0.0000
RADIO-1.21.21331147A1.19_2G
OpenDSP-v46.2.2-00564-M8974_F0.0811
OS-3.28.1540 (3.28.1540.5) < ------this is all in red text
eMMC-boot 2048MB
Oct 2 2014,14:55:52.0
RUU <----- this is white text with an orange box around it
I'd love some help with recovering the phone to being usable again, I feel like a total dumbass :/ thanks in advance!
Hendrycks said:
Oh ok, and ya I am but I used a different firmware and now my phone's got the HTC silver logo with 4 triangles with exclamation points in each other. I can only see that screen or what looks like the bootloader but it says the following:
HBOOT-3.19.0.0000
RADIO-1.21.21331147A1.19_2G
OpenDSP-v46.2.2-00564-M8974_F0.0811
OS-3.28.1540 (3.28.1540.5) < ------this is all in red text
eMMC-boot 2048MB
Oct 2 2014,14:55:52.0
RUU <----- this is white text with an orange box around it
I'd love some help with recovering the phone to being usable again, I feel like a total dumbass :/ thanks in advance!
Click to expand...
Click to collapse
The orange RUU means your phone is stuck in RUU mode, meaning you've not completed the firmware flash, you cant use that OTA file for the firmware, first of all, its the wrong firmware for your phone, and an OTA firmware is not full firmware, its only an update to parts, and 2nd, your phone has developer edition 1540 firmware, you need the full firmware of 3.28.1540.5 full wipe package or the RUU.
RUU zip: https://www.androidfilehost.com/?fid=95897840722643418 flash it like firmware.
Seanie280672 said:
first of all, its the wrong firmware for your phone, and an OTA firmware is not full firmware, its only an update to parts.
Click to expand...
Click to collapse
Sometimes is a full package, sometimes its not. You're right, that sometimes if not all modules were updated (from the preceding OTA) typically its not a full package (only includes the parts that were updated).
Flashing firmware zips without knowing exactly what you are doing is really dangerous. I've seen folks flash a "partial" firmware, that didn't contain all the bootloader modules; only 2 of the 3, and the one that wasn't updated didn't correspond to the 2 that were. BRICK
Seanie280672 said:
The orange RUU means your phone is stuck in RUU mode, meaning you've not completed the firmware flash, you cant use that OTA file for the firmware, first of all, its the wrong firmware for your phone, and an OTA firmware is not full firmware, its only an update to parts, and 2nd, your phone has developer edition 1540 firmware, you need the full firmware of 3.28.1540.5 full wipe package or the RUU.
RUU zip: https://www.androidfilehost.com/?fid=95897840722643418 flash it like firmware.
Click to expand...
Click to collapse
I ran a stupid developer edition .exe and it failed but I just want it back to being Telus and leave it at that, can I flash the Telus firmware.zip in the OTA and be good to go?
EDIT: I can't get to any menus once the phone is plugged in to my comp so how can I flash the RUU like firmware?
Hendrycks said:
I ran a stupid developer edition .exe and it failed but I just want it back to being Telus and leave it at that, can I flash the Telus firmware.zip in the OTA and be good to go?
EDIT: I can't get to any menus once the phone is plugged in to my comp so how can I flash the RUU like firmware?
Click to expand...
Click to collapse
Did you change your CID and MID on your phone before flashing the dev edition firmware ?
Seanie280672 said:
Did you change your CID and MID on your phone before flashing the dev edition firmware ?
Click to expand...
Click to collapse
My MID is whatever it had to be to be a GPe and my CID is set to SuperCID. I didn't want it to be dev I just needed a firmware that I thought would work and messed up.
EDIT: What steps do I have to take to get it out of being stuck in RUU? I tried using ADB to flash the RUU like a firmware and it doesn't work. It says it's the max download size and that it can't load firmware.zip
Hendrycks said:
My MID is whatever it had to be to be a GPe and my CID is set to SuperCID. I didn't want it to be dev I just needed a firmware that I thought would work and messed up.
EDIT: What steps do I have to take to get it out of being stuck in RUU? I tried using ADB to flash the RUU like a firmware and it doesn't work. It says it's the max download size and that it can't load firmware.zip
Click to expand...
Click to collapse
if you are s-off, you needed to change your MID and CID to match the firmware you are flashing, if you are still s-off, then you can edit the dev ed firmware you have downloaded, edit the android-info.txt file, change the MID in that file to whatever yours is and add your CID to the text file to whatever yours is too, then save it.
As your phone is already in RUU mode, with it highlighted on the screen, unplug the USB lead, and then plug it back in, should go back to the black screen with silver HTC logo.
DO NOT GO S-ON EVER AT THIS POINT, you'll be flashing a modified firmware, modified with your CID and MID and s-on will lead to an instant brick
Thats if this even works at all :fingers-crossed: only thing I can think of to try as its too late to change your phones MID and CID.
Seanie280672 said:
if you are s-off, you needed to change your MID and CID to match the firmware you are flashing, if you are still s-off, then you can edit the dev ed firmware you have downloaded, edit the android-info.txt file, change the MID in that file to whatever yours is and add your CID to the text file to whatever yours is too, then save it.
As your phone is already in RUU mode, with it highlighted on the screen, unplug the USB lead, and then plug it back in, should go back to the black screen with silver HTC logo.
DO NOT GO S-ON EVER AT THIS POINT, you'll be flashing a modified firmware, modified with your CID and MID and s-on will lead to an instant brick
Thats if this even works at all :fingers-crossed: only thing I can think of to try as its too late to change your phones MID and CID.
Click to expand...
Click to collapse
If the RUU was an .exe how can I edit it?
Okay so progress!! I just reflashed a firmware from before and followed this video: https://www.youtube.com/watch?v=oGWNtRAkRqs
And now I'm back into fastboot USB and so I can do everything again! So what do I do to get this all fixed up and back to being Telus? Flash the Firmware.zip from the Telus OTA?
Hendrycks said:
Okay so progress!! I just reflashed a firmware from before and followed this video: https://www.youtube.com/watch?v=oGWNtRAkRqs
And now I'm back into fastboot USB and so I can do everything again! So what do I do to get this all fixed up and back to being Telus? Flash the Firmware.zip from the Telus OTA?
Click to expand...
Click to collapse
noooo, forget the OTA all together, you cant take the chance that its not a full firmware, if its not you'll have a brick.
which firmware "from before" did you flash ?
Change your cid and mid to match the dev edition RUU and then run the RUU.
Seanie280672 said:
noooo, forget the OTA all together, you cant take the chance that its not a full firmware, if its not you'll have a brick.
which firmware "from before" did you flash ?
Change your cid and mid to match the dev edition RUU and then run the RUU.
Click to expand...
Click to collapse
I used the "1.54.401.5-W_Splash.zip" linked on that video I linked. It's what I used trying to get my phone back to Sense from GPe before this Developer Edition crap all went down aha.
With that firmware my getvar all is now:
C:\Users\Andrew\Desktop\HTC Tools>fastboot g
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HIDDEN
(bootloader) imei: HIDDEN
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
does that tell you anything about what to do next?
EDIT: Thanks so much for the help so far btw, I'm definitely not going to try and just jump head first doing this anymore, I have an S6 Edge pre-ordered and I am not going through this again with it.
Hendrycks said:
I used the "1.54.401.5-W_Splash.zip" linked on that video I linked. It's what I used trying to get my phone back to Sense from GPe before this Developer Edition crap all went down aha.
With that firmware my getvar all is now:
C:\Users\Andrew\Desktop\HTC Tools>fastboot g
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HIDDEN
(bootloader) imei: HIDDEN
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
does that tell you anything about what to do next?
EDIT: Thanks so much for the help so far btw, I'm definitely not going to try and just jump head first doing this anymore, I have an S6 Edge pre-ordered and I am not going through this again with it.
Click to expand...
Click to collapse
ok well first of all, you need to change that modelID, I suggest as you flashed the 401 firmware, you may as well stay on that, its world wide english international firmware, however your modelID is for google play edition, you need to change that to WWE, so see here, and make sure you copy and paste the commands, because one slip up with this and you'll have a brick: http://forum.xda-developers.com/showthread.php?t=2708581 choose the one for HTC Europe MID, ignore the fastboot reboot command at the very end of that instruction set.
then change you cid to HTC__001 (thats 2 underscores, cid is always 8 characters)
post your fastboot getvar all again once done and we'll take it from there.
Seanie280672 said:
ok well first of all, you need to change that modelID, I suggest as you flashed the 401 firmware, you may as well stay on that, its world wide english international firmware, however your modelID is for google play edition, you need to change that to WWE, so see here, and make sure you copy and paste the commands, because one slip up with this and you'll have a brick: http://forum.xda-developers.com/showthread.php?t=2708581 choose the one for HTC Europe MID, ignore the fastboot reboot command at the very end of that instruction set.
then change you cid to HTC__001 (thats 2 underscores, cid is always 8 characters)
post your fastboot getvar all again once done and we'll take it from there.
Click to expand...
Click to collapse
Ok I can definitely do what that link says except that now my phone isn't shown when I do adb devices, I have to be in fastboot USB right?
Hendrycks said:
Ok I can definitely do what that link says except that now my phone isn't shown when I do adb devices, I have to be in fastboot USB right?
Click to expand...
Click to collapse
yes fastboot usb is correct, but you cant use adb commands in fastboot mode, you use fastboot commands, so type fastboot devices instead.
oh damn, hang on 1 sec.
Seanie280672 said:
yes fastboot usb is correct, but you cant use adb commands in fastboot mode, you use fastboot commands, so type fastboot devices instead.
oh damn, hang on 1 sec.
Click to expand...
Click to collapse
I got it but that link says to do adb at the top but then switches to saying to do fastboot? When I do fastboot devices it does show up though. Do I still follow those instructions?
Hendrycks said:
I got it but that link says to do adb at the top but then switches to saying to do fastboot? When I do fastboot devices it does show up though. Do I still follow those instructions?
Click to expand...
Click to collapse
no, bear with me 1 min, on my M7 there was an app to run in recovery to change the MID, much easier, however, im just wondering if you run those commands in recovery, or within a booted rom.
Seanie280672 said:
no, bear with me 1 min, on my M7 there was an app to run in recovery to change the MID, much easier, however, im just wondering if you run those commands in recovery, or within a booted rom.
Click to expand...
Click to collapse
Sounds good thanks
So I got all greedy and wanted Lollipop sooner than when my provider did an OTA.
I tried a bunch of roms and found that Cyanogen was able to work for my phone (a lot of others gave me that issue where the Wifi wouldn't work, I subsequently worked out this was a firmware issue).
In an effort to try and fix a number of bugs I've been attempting to get S-Off. I downloaded Sunshine but Sunshine told me my ROM wasn't close enough to stock for it. So I put another Rom on it, but then mysteriously I lost root access.
So I did a hard wipe.
And now I find myself unable to install any ROMs on it at all (I'm trying to find a stock Kitkat one that will hopefully run).
So I can't get S-Off. I'm not even sure if it's still rooted (though I do have Philz installed and that loads when I put it into recovery mode). And so I'm not even remotely sure what I should do.
Yay!
Bricked mine too!
RuminatorNZ said:
So I got all greedy and wanted Lollipop sooner than when my provider did an OTA.
I tried a bunch of roms and found that Cyanogen was able to work for my phone (a lot of others gave me that issue where the Wifi wouldn't work, I subsequently worked out this was a firmware issue).
In an effort to try and fix a number of bugs I've been attempting to get S-Off. I downloaded Sunshine but Sunshine told me my ROM wasn't close enough to stock for it. So I put another Rom on it, but then mysteriously I lost root access.
So I did a hard wipe.
And now I find myself unable to install any ROMs on it at all (I'm trying to find a stock Kitkat one that will hopefully run).
So I can't get S-Off. I'm not even sure if it's still rooted (though I do have Philz installed and that loads when I put it into recovery mode). And so I'm not even remotely sure what I should do.
Yay!
Click to expand...
Click to collapse
I just joined this forum, so I don't know if I should be posting here or on a new thread, so let me know I can delete this, move it if I'm out of line.
I'm in the same boat. Just softbricked my girlfriend's Samsung Galaxy S5 (SM-G900a)
Her phone was unlocked AT&T and it auto updated to 5.0 Lollipop update OTA about a week ago.
It's been running like **** so I thought I'd downgrade it to 4.2.2 via ODIN
ODIN (failed) trying to install
G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.gz
I read in one of these forums that downgrading wouldn't work but they found a work around
http://forum.xda-developers.com/showthread.php?t=2785363
Oh yeah and then my phone bricked so there is that, my GF is being really understanding but I'm hoping I can recover this!!!!
Edit: My problem was resolved here
http://forum.xda-developers.com/att...-2-bricked-t3093826/post60397413#post60397413
RuminatorNZ said:
So I got all greedy and wanted Lollipop sooner than when my provider did an OTA.
I tried a bunch of roms and found that Cyanogen was able to work for my phone (a lot of others gave me that issue where the Wifi wouldn't work, I subsequently worked out this was a firmware issue).
In an effort to try and fix a number of bugs I've been attempting to get S-Off. I downloaded Sunshine but Sunshine told me my ROM wasn't close enough to stock for it. So I put another Rom on it, but then mysteriously I lost root access.
So I did a hard wipe.
And now I find myself unable to install any ROMs on it at all (I'm trying to find a stock Kitkat one that will hopefully run).
So I can't get S-Off. I'm not even sure if it's still rooted (though I do have Philz installed and that loads when I put it into recovery mode). And so I'm not even remotely sure what I should do.
Yay!
Click to expand...
Click to collapse
your mistake is using CWM recovery, Sense custom roms require TWRP recovery, so you need to start by flashing the latest version of that.
once flashed, go in and do a full wipe. dont forget after wiping to reboot back into recovery for the changes to take effect, when you go to reboot it will say something like you have no OS installed, are you sure you want to reboot, just say yes, and select DO NOT INSTALL to SuperSU, the rom you falsh will be pre rooted.
TWRP latest version supports MTP, so when your in recovery main window, plug your phone into the computer and your sdcard and internal storage will open on your computer, just copy a rom to your sdcard, once copied, unplug your phone and install it.
use something like ARHD 41 or Maximus HD, they are close enough to stock for sunshine to work.
have a look here for a rom, dont download anything too modded or fancy as you'll be coming away from stock then http://forum.xda-developers.com/htc-one-m8/development
Seanie280672 said:
your mistake is using CWM recovery, Sense custom roms require TWRP recovery, so you need to start by flashing the latest version of that.
once flashed, go in and do a full wipe. dont forget after wiping to reboot back into recovery for the changes to take effect, when you go to reboot it will say something like you have no OS installed, are you sure you want to reboot, just say yes, and select DO NOT INSTALL to SuperSU, the rom you falsh will be pre rooted.
TWRP latest version supports MTP, so when your in recovery main window, plug your phone into the computer and your sdcard and internal storage will open on your computer, just copy a rom to your sdcard, once copied, unplug your phone and install it.
use something like ARHD 41 or Maximus HD, they are close enough to stock for sunshine to work.
have a look here for a rom, dont download anything too modded or fancy as you'll be coming away from stock then http://forum.xda-developers.com/htc-one-m8/development
Click to expand...
Click to collapse
Brilliant, thank you - I'll give this a whirl.
RuminatorNZ said:
Brilliant, thank you - I'll give this a whirl.
Click to expand...
Click to collapse
on a slightly different note, you dont need s-off to flash a firmware or RUU depending on your current firmware, can you post your fastboot getvar all without your imei and serial number please.
Seanie280672 said:
on a slightly different note, you dont need s-off to flash a firmware or RUU depending on your current firmware, can you post your fastboot getvar all without your imei and serial number please.
Click to expand...
Click to collapse
I sure can (thank you for your help):
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.16.2133156.UA15_2G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B11000
cidnum: HTC__039
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: ab0efa49
hbootpreupdate: 11
gencheckpt: 0
RuminatorNZ said:
I sure can (thank you for your help):
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.16.2133156.UA15_2G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B11000
cidnum: HTC__039
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: ab0efa49
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
your going to need s-off and convert your phone im sorry, doesnt seem to be anything about for your phone, firmware or RUU's.
You'll need to convert to get the latest firmware on your phone, unless you have it via an OTA or something like that ? convert to WWE 401 or Dev Edition 1540, currently your on 980 Austraillia Unbranded.
once you get s-off, convert is easy, all you need to do is change your CID number with a fastboot command, change your MID number, flash the firmware for Dev Ed or WWE, and then run the RUU.
Seanie280672 said:
on a slightly different note, you dont need s-off to flash a firmware or RUU depending on your current firmware, can you post your fastboot getvar all without your imei and serial number please.
Click to expand...
Click to collapse
I've got a sneaking suspicion that the ARHD and Maximus ROMS I'm finding won't mesh with the firmware I've got. I think.
Seanie280672 said:
your going to need s-off and convert your phone im sorry, doesnt seem to be anything about for your phone, firmware or RUU's.
You'll need to convert to get the latest firmware on your phone, unless you have it via an OTA or something like that ? convert to WWE 401 or Dev Edition 1540, currently your on 980 Austraillia Unbranded.
once you get s-off, convert is easy, all you need to do is change your CID number with a fastboot command, change your MID number, flash the firmware for Dev Ed or WWE, and then run the RUU.
Click to expand...
Click to collapse
yeah it's getting S-Off that struggling with.
RuminatorNZ said:
I've got a sneaking suspicion that the ARHD and Maximus ROMS I'm finding won't mesh with the firmware I've got. I think.
Click to expand...
Click to collapse
they should still install and run, your may have a few problems like wifi, but it should effect them installing and booting, try this one insted, its stock for your firmware version, https://www.androidfilehost.com/?fid=95916177934516545
You just need to make sure you flash with TWRP not CWM. http://dl.twrp.me/m8/
Seanie280672 said:
they should still install and run, your may have a few problems like wifi, but it should effect them installing and booting, try this one insted, its an older version of ARHD http://www.androidrevolution.org/do...oid_Revolution_HD-One_M8_34.6.zip&hash=3703c7
You just need to make sure you flash with TWRP not CWM. http://dl.twrp.me/m8/
Click to expand...
Click to collapse
Right, off I go to download these files on New Zealand's rubbish internet. I'll report back in many many hours
Thank you for all your help so far. Really appreciate it.
RuminatorNZ said:
Right, off I go to download these files on New Zealand's rubbish internet. I'll report back in many many hours
Thank you for all your help so far. Really appreciate it.
Click to expand...
Click to collapse
use this rom instead: https://www.androidfilehost.com/?fid=95916177934516545 its full stock rom, flash in TWRP still, and closest matching to your firmware, its KitKat not Lollipop.
Seanie280672 said:
they should still install and run, your may have a few problems like wifi, but it should effect them installing and booting, try this one insted, its stock for your firmware version, https://www.androidfilehost.com/?fid=95916177934516545
You just need to make sure you flash with TWRP not CWM. http://dl.twrp.me/m8/
Click to expand...
Click to collapse
Just keeping you updated, finished dowloading the above rom, flashed it and it seems to be working (mind you, my wifi still ain't working with that ROM, but I can live with that). Sunshine is now S-Off-ing as we speak so this is as much progress as I've made in 2 days!!
What should my next step be after getting S-Off?
RuminatorNZ said:
Just keeping you updated, finished dowloading the above rom, flashed it and it seems to be working (mind you, my wifi still ain't working with that ROM, but I can live with that). Sunshine is now S-Off-ing as we speak so this is as much progress as I've made in 2 days!!
What should my next step be after getting S-Off?
Click to expand...
Click to collapse
easiest thing for you to do is change your cid first, change it to WWE HTC__001 the command is fastboot oem write cid HTC__001 (thats 2 underscores, CID number is always 8 characters long)
so with your phone in the bootloader fastboot usb mode and plugged into the computer, run these3 commands
fastboot oem write cid HTC__001
fastboot erase cache
fastboot reboot-bootloader
next is to change you mid, so enter recovery and put this file on your SDcard http://forum.xda-developers.com/showthread.php?t=2779524
install it like you would with a rom, and follow the instructions on screen, when given the options to select mid to change to, select the one for WWE international.
when you have finished those 2 things, post your fastboot getvar all again please, should be a new and updated one, again without imei and serial number
Seanie280672 said:
easiest thing for you to do is change your cid first, change it to WWE HTC__001 the command is fastboot oem write cid HTC__001 (thats 2 underscores, CID number is always 8 characters long)
so with your phone in the bootloader fastboot usb mode and plugged into the computer, run these3 commands
fastboot oem write cid HTC__001
fastboot erase cache
fastboot reboot-bootloader
next is to change you mid, so enter recovery and put this file on your SDcard http://forum.xda-developers.com/showthread.php?t=2779524
install it like you would with a rom, and follow the instructions on screen, when given the options to select mid to change to, select the one for WWE international.
when you have finished those 2 things, post your fastboot getvar all again please, should be a new and updated one, again without imei and serial number
Click to expand...
Click to collapse
Is what you've suggested better than the Super-CID - 11111111 ?
RuminatorNZ said:
Is what you've suggested better than the Super-CID - 11111111 ?
Click to expand...
Click to collapse
I never bother with superCID, always seems to cause me more headaches than good.
the 2 best cid's to go for in my books are HTC__001 WWE (world wide engish) or BS_US001 Dev edition, they get the fastest updates.
Seanie280672 said:
I never bother with superCID, always seems to cause me more headaches than good.
the 2 best cid's to go for in my books are HTC__001 WWE (world wide engish) or BS_US001 Dev edition, they get the fastest updates.
Click to expand...
Click to collapse
Brilliant. I'll take your advice. You've got it all right so far.
See this guiy here did the same thing, but he is complaining that he's not got the next update yet, it because he hasnt changed his cid number, he needs to be on HTC__001, everytrhing else is done right, this is from the Australlian thread: http://forum.xda-developers.com/showpost.php?p=60272806&postcount=662
your fastboot getvar all should look like his when your done, only yours should say HTC__001 for the cid.
---------- Post added at 11:50 AM ---------- Previous post was at 11:42 AM ----------
RuminatorNZ said:
Brilliant. I'll take your advice. You've got it all right so far.
Click to expand...
Click to collapse
sorry my bad, no space between wite and cid so the command is fastboot oem writecid HTC__001
Seanie280672 said:
See this guiy here did the same thing, but he is complaining that he's not got the next update yet, it because he hasnt changed his cid number, he needs to be on HTC__001, everytrhing else is done right, this is from the Australlian thread: http://forum.xda-developers.com/showpost.php?p=60272806&postcount=662
your fastboot getvar all should look like his when your done, only yours should say HTC__001 for the cid.
---------- Post added at 11:50 AM ---------- Previous post was at 11:42 AM ----------
sorry my bad, no space between wite and cid so the command is fastboot oem writecid HTC__001
Click to expand...
Click to collapse
Righto, so far so good ... I think:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.24.21331147A1.09G
version-cpld: None
version-microp: None
version-main: 4.16.1540.8
version-misc: PVT SHIP S-OFF
serialno:
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B11000
cidnum: HTC__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 3aa067db
hbootpreupdate: 11
gencheckpt: 0
RuminatorNZ said:
Righto, so far so good ... I think:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.24.21331147A1.09G
version-cpld: None
version-microp: None
version-main: 4.16.1540.8
version-misc: PVT SHIP S-OFF
serialno:
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B11000
cidnum: HTC__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 3aa067db
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
just MID to change, just wondering, have you flashed some firmware ??? how did you get on this 4.16.1540.8 ??? this is dev edition firmware.
Hey everyone!
I just got HTC M8 from a friend, and figured out it is a demo unit. It comes with a demo app, which I am unable to get rid off. It was firstly rooted and mistakenly I removed the internal storage. After all the mayhem, researching for hours on this forum, I am finally able to get my device back running but still the demo app is there. I am unable to make any changes in developer options or through control center. I am new to all modding, HTC, Android and custom / stock roms.
I have few questions after reading a lot. After accidentally deleting the OS, and wiping internal memory - I was able to get it back, but now wants to run a custom ROM on it but not sure if I am able to do it with current status of my device.
Information about device:
HBoot: 3.16.000
S-ON
HTC__002
Unlocked Bootloader
TWRP installed (but throws error whenever I try flashing a zip file)
The question: Can I install a custom rom without getting S-OFF and if yes, which custom ROM can I use on my device? I understand there is some limitation to HBoot version, but I am unable to figure out how to update it to latest version. I would like to update my device from Android Kitkat to Marshmallow or some custom ROM which doesn't have a demo app.
P.S: A noob!
Update:
After reading lots of threads, I finally bought Sunshine license and activated S-OFF, now, I am with SuperCID 11111111 on my demo unit. Now, I want know about which Custom ROM I can run, and how can I update my Hboot to latest version?
You can use this ROM
https://forum.xda-developers.com/htc-one-m8/development/rom-resurrection-remix-v5-8-0-t3507210
Follow the directions there and you will be all right.
If you still need help contact me on :
[email protected]
HamzaSheikh said:
[*]HBoot: 3.16.000
[*]TWRP installed (but throws error whenever I try flashing a zip file)
Click to expand...
Click to collapse
Might help, if you tell us what error message TWRP gives you.
Hboot version is too old to flash most ROMs. Also, such an old hboot version, is not compatible with many TWRP versions (might be the reason zip won't flash in TWRP).
What TWRP version?
Do fastboot getvar all, and post the result (delete IMEI and serial number before posting).
I believe @ckpv5 knows some about how to get the demo versions working or modded. The demo versions pops up infrequently enough, I can't remember the exact details.
---------- Post added at 03:39 PM ---------- Previous post was at 03:38 PM ----------
Hero_elmehrik22 said:
You can use this ROM
https://forum.xda-developers.com/htc-one-m8/development/rom-resurrection-remix-v5-8-0-t3507210
Follow the directions there and you will be all right.
Click to expand...
Click to collapse
He says TWRP gives an error flashing zips. So how is he supposed to install that ROM?
Most likely, his Hboot version is too old to support that ROM.
Yes, Hboot version is too old. I had a long fight with getting it restored. I had to try every other TWRP version and suddenly TWRP 2.8.0.0 worked for me!
Here is the output from getvar all:
Hamzas-iMac:~ hamza$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: removed
(bootloader) imei: removed
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__002
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 098a72e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.203s
Click to expand...
Click to collapse
Problem I face:
- Current TWRP is old, I am unable to make most out of it. (v2.8.0.0)
- Hboot is like hanging in stone age, I need to update it - but I have a demo unit (it comes with annoying demo app!)
- I want to run Custom ROM or at least a newer Android version.
redpoint73 said:
Might help, if you tell us what error message TWRP gives you.
Hboot version is too old to flash most ROMs. Also, such an old hboot version, is not compatible with many TWRP versions (might be the reason zip won't flash in TWRP).
What TWRP version?
Do fastboot getvar all, and post the result (delete IMEI and serial number before posting).
I believe @ckpv5 knows some about how to get the demo versions working or modded. The demo versions pops up infrequently enough, I can't remember the exact details.
---------- Post added at 03:39 PM ---------- Previous post was at 03:38 PM ----------
He says TWRP gives an error flashing zips. So how is he supposed to install that ROM?
Most likely, his Hboot version is too old to support that ROM.
Click to expand...
Click to collapse
You should be able to disable the demo app, using the "alternative method" indicated in the following post: https://forum.xda-developers.com/showpost.php?p=59735868&postcount=10
You can update to a newer version using the RUU and instructions on the following post. You will need to relock the bootloader in order to RUU: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Be aware that RUU will wipe all data on the phone! Again, you will need to disable the demo app if you intend to stay on the Marshmallow "stock" ROM.
Updating to newer version (Marshmallow) by RUU, will also update the hboot, and other firmware (radio, WiFi, etc.). So after that you should be able to use the current version TWRP (3.1) and the current custom ROMs. Again, I'm not 100% knowledgeable on the demo model. But I don't see how the demo version CID (which is what triggers the demo app) would prevent you from doing the above. Especially if you disable the demo app, or flash a custom ROM (non-Sense) that doesn't have the demo app to begin with.
Thanks @redpoint73 for the help. Here is an update:
I finally able to get rid of demo app using SuperCID - means, now I have S-OFF device. I used Sunshine apk. Now I would like to update my device to latest Android (Marshmallow) - so should I follow the instructions on the thread you pointed me or is there something else I can try instead of locking the bootloader again?
redpoint73 said:
You should be able to disable the demo app, using the "alternative method" indicated in the following post: https://forum.xda-developers.com/showpost.php?p=59735868&postcount=10
You can update to a newer version using the RUU and instructions on the following post. You will need to relock the bootloader in order to RUU: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Be aware that RUU will wipe all data on the phone! Again, you will need to disable the demo app if you intend to stay on the Marshmallow "stock" ROM.
Updating to newer version (Marshmallow) by RUU, will also update the hboot, and other firmware (radio, WiFi, etc.). So after that you should be able to use the current version TWRP (3.1) and the current custom ROMs. Again, I'm not 100% knowledgeable on the demo model. But I don't see how the demo version CID (which is what triggers the demo app) would prevent you from doing the above. Especially if you disable the demo app, or flash a custom ROM (non-Sense) that doesn't have the demo app to begin with.
Click to expand...
Click to collapse
Meanwhile, I tried following the details on thread and got myself stuck on error:
FAILED (remote: 32 header error)
Whenever I try to flash the RUU, it gives this error!
redpoint73 said:
You should be able to disable the demo app, using the "alternative method" indicated in the following post: https://forum.xda-developers.com/showpost.php?p=59735868&postcount=10
You can update to a newer version using the RUU and instructions on the following post. You will need to relock the bootloader in order to RUU: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Be aware that RUU will wipe all data on the phone! Again, you will need to disable the demo app if you intend to stay on the Marshmallow "stock" ROM.
Updating to newer version (Marshmallow) by RUU, will also update the hboot, and other firmware (radio, WiFi, etc.). So after that you should be able to use the current version TWRP (3.1) and the current custom ROMs. Again, I'm not 100% knowledgeable on the demo model. But I don't see how the demo version CID (which is what triggers the demo app) would prevent you from doing the above. Especially if you disable the demo app, or flash a custom ROM (non-Sense) that doesn't have the demo app to begin with.
Click to expand...
Click to collapse
HamzaSheikh said:
Meanwhile, I tried following the details on thread and got myself stuck on error:
FAILED (remote: 32 header error)
Whenever I try to flash the RUU, it gives this error!
Click to expand...
Click to collapse
1. No need to relock bootloader as you already S-Off your device
2. You got error because you don't use htc_fastboot as in the instructions.
Lots of love man! I finally got it. It worked like a charm through HTC_fastboot.exe. I was on macOS earlier and tried flashing ruu.zip through it, but after your message. I tried on Windows with HTC fastboot and wow!
I did a small mess and eventually relocked my bootloader! No issues with that, I can re-unlock it!
Thanks @ckpv5 for the final tip, and lots of love for @redpoint73 for pointing me at right direction!
Latest Getvar All:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: removed
(bootloader) imei: removed
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Anything else I should be doing to make it work awesome and fast?
ckpv5 said:
1. No need to relock bootloader as you already S-Off your device
2. You got error because you don't use htc_fastboot as in the instructions.
Click to expand...
Click to collapse
HamzaSheikh said:
I did a small mess and eventually relocked my bootloader! No issues with that, I can re-unlock it!
Click to expand...
Click to collapse
Honest mistake. Relocking the bootloader is mandatory to run an RUU with s-on. So it's easy to miss the fact that the requirement (to relock the bootloader to RUU) is bypassed with s-off.
As you said, you can always unlock the bootloader again, if you want to install custom recovery, root, flash custom ROM, etc. Alternately, if you want to stay stock with no root, you can just leave it relocked.
HamzaSheikh said:
Thanks @ckpv5 for the final tip, and lots of love for @redpoint73 for pointing me at right direction!
Click to expand...
Click to collapse
You're very welcome. I wasn't sure if you wanted to pay for sunshine, so that is why I was suggesting some possible solutions with s-on. But glad to have pointed you in the right direction, regardless.
HamzaSheikh said:
Thanks [MENTION=830797]
Anything else I should be doing to make it work awesome and fast?
Click to expand...
Click to collapse
That is a very open-ended and subjective question. It's completely up to your preference, if you want to do any more mods. You can try custom ROMs, root, custom kernels, and much more. There really isn't much limit on what you can try.