Related
ever since doing the ota and fota my phone was upgraded to 2.3.5 and the most recent radio version. However, I have had connection issues ever since.
My question is. I have downloaded RUU_Marvel_HTC_Europe_1.33.401.2_Radio_47.10.35.3029H_7.46.35.08_release_185724_signed.exe, located its temp files and found ROM.zip, inside which is the image file for the radio version which i found flawless. Can I thru fastboot flash radio.img and restore the phone back to an older radio version?
I tried to install the ROM.zip by following a guide to the letter, but hboot said it was incorrect file.
My phone is current s-on but unlocked thru htcdev, CWM recovery is installed, and has been rooted and is working.
thanks
I don't think you can flash the radio with s-on.
i had a suspicion that would be the case, so I've ordered an xtc clip
nckgarvey said:
i had a suspicion that would be the case, so I've ordered an xtc clip
Click to expand...
Click to collapse
too early, mate. you could have downgrade your device to 1.33.401.2 and then install the new hboot from htcdev again (the latest version does not include a new radio anymore) and re unlock your bootloader.
theq86 said:
too early, mate. you could have downgrade your device to 1.33.401.2 and then install the new hboot from htcdev again (the latest version does not include a new radio anymore) and re unlock your bootloader.
Click to expand...
Click to collapse
does this mean even if i s-off with xtc clip i can't downgrade
no, the clip will give you absolute freedom.
but if you only wanted to achieve the old radio there would have been a way to do so without the clip.
theq86 said:
no, the clip will give you absolute freedom.
but if you only wanted to achieve the old radio there would have been a way to do so without the clip.
Click to expand...
Click to collapse
thew, thats good to know, can anyone point me in the direction of a tutorial in how to do what i want, whilst i wait for the arrival of the clip.
Thanks given to you all
Follow that tutorial: http://forum.xda-developers.com/showthread.php?t=1445867
then you will be able to flash the official 1.33.401.2 RUU. (but you first have to lock the bootloader again with fastboot oem lock)
in 1.33.401.2 there is hboot 1.03.0000, the hboot will bypassing installation because it can not be downgraded. That means if your device was unlocked before, you can unlock it again.
theq86 said:
Follow that tutorial: http://forum.xda-developers.com/showthread.php?t=1445867
then you will be able to flash the official 1.33.401.2 RUU. (but you first have to lock the bootloader again with fastboot oem lock)
in 1.33.401.2 there is hboot 1.03.0000, the hboot will bypassing installation because it can not be downgraded. That means if your device was unlocked before, you can unlock it again.
Click to expand...
Click to collapse
So let me see if I got this right.
Relock boot loader using fast boot OEM lock
Follow changing version guide
Flash the from that I want
And then unlock again if I want root
exactly
booted phone into fastboot
entered fastboot oem lock - phone now relocked
start following guide for error 190 fix.
got to:
./data/local/tmp/zergRush
*zergRush will kill adb, start it again with*
but it didn't kill adb $ sign still remained, so moved onto next step
cat /dev/mtd/mtd0 > /sdcard/misc.img
and i get permission denied.
where am i going wrong
Problem solved, followed error 190 guide, skipped the parts regarding zergrush, completed flash in #prompt.
rebooted phone, let hboot do its work, then got a menu asking me what i wanted to update, or in my case would have been a downgrade.
Thanks given to theq86
Guys,
I'm trying to get my JB flasher tool to work with S-Off devices. (Mine is S-On so I can't test)
Can anyone with a S-off phone that's upgraded the FW let me know the procedure. There seems to be confusion about which commands work with a locked bootloader and S-off so don't speculate, only respond if you know it works.
Specific question:
If you have a CID of 11111111 does it need changing to a compatible CID from the androidinfo.txt? If so, how? Does the bootloader need to be unlocked?
Can the bootloader be unlocked without htcdev code? If yes, how?
Can all fastboot commands be run with S-off but a locked bootloader?
Thanks
DO NOT UNLOCK YOUR BOOTLOADER!!!!
You will have to add the Super CID to the android-info.txt before flashing but other than that it's the same process as S-ON users
EddyOS said:
DO NOT UNLOCK YOUR BOOTLOADER!!!!
You will have to add the Super CID to the android-info.txt before flashing but other than that it's the same process as S-ON users
Click to expand...
Click to collapse
As easy as that. Thanks:good:
PS So S-off will ignore the broken signature?
Also, if someone has already unlocked their bootloader (due to not realising the power of S-Off ), I assume it'll need to be relocked before installing the firmware.zip?
PS Can boot.img be flashed via fastboot if its locked on a S-off phone?
Also, can I replace the recovery.img with CWM in the zip, or even just remove it. Same goes for the boot.img
If you're S-OFF you basically have the same rights as someone with an unlocked bootloader plus more so you can flash CWM/boot etc. through fastboot without unlocking the bootloader. As you said, S-OFF ignores the signature. So long as it's a proper update.zip it should flash without issues (I should qualify this by saying I'm basing this on my HTC Sensation and what I could/couldn't do with S-OFF. If I had an S-OFF One X I could give you a 100% answer)
S-off HOX 044? how to do this? pls,help me
hoangps said:
S-off HOX 044? how to do this? pls,help me
Click to expand...
Click to collapse
you can't s-off for now...
Hello, just a quick question. I had my One rooted, s-off, and unlocked when my microphone went. So I relocked, s-on, and flashed an RUU via http://forum.xda-developers.com/showthread.php?t=2475216. Just making sure that before I pack it in the box, there is nothing else that could trip the people at Verizon that I had messed with my phone. I took the OTAs up to 4.3. I'm just paranoid about info not matching up such as the baseband version and build number etc. Thanks
Does the bootloader say locked or relocked? Locked is good relocked not so much. Other than that you should be fine. Ruu's wipe everything and install it all fresh, including the firmware (baseband, hboot, recovery, etc), so everything will match up.
In the bootloader I have "Locked" also s-on. I noticed though with the refurbished phone I received (not happy about having to get refurbished but thats besides the point) the CID number shows in the bootloader screen whereas on my original phone it is not displayed. Not sure if I even need to be this worried, but I'm just paranoid. Thanks
Are both phones on the same hboot version? I dont remember if it showed in older hboots or not. Either way i wouldn't worry, locked and s-on is all you need.
No they weren't. I'm just going to stop worrying too much about it. Thanks
If i send my phone back to verizon do i have to be on the original ROM? i understand that i need to lock my bootloader and have s-on, but what about the software itself?
It can be on stock rom/firmware of any version. Just no custom roms or anything.
Just to confirm, if I have a phone that is S-OFF, unlocked:
1. Do I need to lock the bootloader before flashing an RUU?
2. Does flashing an RUU revert the phone to S-ON?
3. Does anything special otherwise need to be done to the phone prior to flashing the RUU?
Thanks so much in advance.
I also have to return a phone to VZW due to a hardware issue (the autofocus issue finally too much for me to bear).
You only need to relock the bootloader if using a signed ruu. A decrypted ruu does not need it locked.
Flashing an ruu will not remove s-off or relock the bootloader. You can do it before or after, but i sugest after, that way if something goes wrong durring the ruu, you still have options.
Once you do the ruu you will be stock. So the only thing you would have to do is relock and go s-on.
Fantastically clear, Clumsco, thanks! Three quick additional questions
1. is there any advantage to flashing the signed RUU, and adding danger by locking the bootloader beforehand? In your links below your signature is a path to both decrypted and signed versions of the latest RUUs. So I thought to ask before going with one or the other. If there is no advantage then I guess the decrypted version would be the safer bet, right?
2. Is there a danger that locking after the RUU will result in a "relocked" versus the desired "Locked" status?
3. Will the RUU flash wipe my /sdcard area? If so I'll back everything up before embarking on this.
I VERY much appreciate the help. I ran rumrunner several months back and have forgotten a lot of the nuances. Thanks for the quick primer!
cmlusco said:
You only need to relock the bootloader if using a signed ruu. A decrypted ruu does not need it locked.
Flashing an ruu will not remove s-off or relock the bootloader. You can do it before or after, but i sugest after, that way if something goes wrong durring the ruu, you still have options.
Once you do the ruu you will be stock. So the only thing you would have to do is relock and go s-on.
Click to expand...
Click to collapse
There is no difference between a signed and decrypted ruu other than what their names suggest. Ones signed ones not, both do the exact same thing to the phone.
You can lock the bootloader first. As long as you still have s-off, you have a saftey net. As long as your s-off you can change it to say what ever you want it to say. Locked, relocked, or unlocked.
Yes the ruu will wipe everything.
You will want to back up your sd.
Do the ruu.
Take the ota to kitkat.
Lock the bootloader.
Go s-on.
Thanks, everything worked. For future knowledge, can you flash signed RUU's with an S-ON device?
cmlusco said:
There is no difference between a signed and decrypted ruu other than what their names suggest. Ones signed ones not, both do the exact same thing to the phone.
You can lock the bootloader first. As long as you still have s-off, you have a saftey net. As long as your s-off you can change it to say what ever you want it to say. Locked, relocked, or unlocked.
Yes the ruu will wipe everything.
You will want to back up your sd.
Do the ruu.
Take the ota to kitkat.
Lock the bootloader.
Go s-on.
Click to expand...
Click to collapse
Yes and no. You can flash a signed ruu if s-on, but not one that is an older version than currently on the phone. It has to be the same or a newer version. This is an issue if your on kitkat, as we do not currently have a kk ruu available.
cmlusco said:
Yes and no. You can flash a signed ruu if s-on, but not one that is an older version than currently on the phone. It has to be the same or a newer version. This is an issue if your on kitkat, as we do not currently have a kk ruu available.
Click to expand...
Click to collapse
I'm trying to learn here too, that is dependent on the hboot correct? So if you were to downgrade your hboot via the thread somewhere in the VZW HTC One forum, you should be able to flash any RUU right?
Technically yes, although as far as i know there is no way to do so while s-on and locked. In order to downgrade hboot you would need to have the bootloader unlocked. Since verizon does not let us use htcdev to unlock, it would be virtually imposible.
Your responses are clear and helpful. Thanks a bunch!
cmlusco said:
Technically yes, although as far as i know there is no way to do so while s-on and locked. In order to downgrade hboot you would need to have the bootloader unlocked. Since verizon does not let us use htcdev to unlock, it would be virtually imposible.
Click to expand...
Click to collapse
cmlusco said:
There is no difference between a signed and decrypted ruu other than what their names suggest. Ones signed ones not, both do the exact same thing to the phone.
You can lock the bootloader first. As long as you still have s-off, you have a saftey net. As long as your s-off you can change it to say what ever you want it to say. Locked, relocked, or unlocked.
Yes the ruu will wipe everything.
You will want to back up your sd.
Do the ruu.
Take the ota to kitkat.
Lock the bootloader.
Go s-on.
Click to expand...
Click to collapse
My phone is current S-Off and relocked, how can I change it to unlocked?
Thank you.
UPDATE: Nevermind, I got it here: http://forum.xda-developers.com/showthread.php?t=2470340
How do you do the above for warranty claim
I need to send the phone in for replacement / maintenance
it is unlocked US version running Verizon ROM on Verizon network
How do I unroot, lock the bootloader, and s-on?
I know they might not care, I still would like to restore everything to prevent any surprises or rejection
please list the steps. Thank you very much
ahgahg said:
How do you do the above for warranty claim
I need to send the phone in for replacement / maintenance
it is unlocked US version running Verizon ROM on Verizon network
How do I unroot, lock the bootloader, and s-on?
I know they might not care, I still would like to restore everything to prevent any surprises or rejection
please list the steps. Thank you very much
Click to expand...
Click to collapse
First thing to do is backup everything from your phone to your PC. Then run a RUU ( I guess that would be US unlocked, not Verizon). After RUU is flashed, go to download mode and issue a command "fastboot oem writesecureflag 3" (without quotes). That will restore your security flag back to s-on. Then use Sunshine to set bootloader status to LOCKED and s-off (really the easiest way to set it to LOCKED, not RELOCKED). Finally, run "fastboot oem writesecureflag 3" once again, and done. You are 100% stock. It's much faster and simpler than it looks from my description.
donkeykong1 said:
First thing to do is backup everything from your phone to your PC. Then run a RUU ( I guess that would be US unlocked, not Verizon). After RUU is flashed, go to download mode and issue a command "fastboot oem writesecureflag 3" (without quotes). That will restore your security flag back to s-on. Then use Sunshine to set bootloader status to LOCKED and s-off (really the easiest way to set it to LOCKED, not RELOCKED). Finally, run "fastboot oem writesecureflag 3" once again, and done. You are 100% stock. It's much faster and simpler than it looks from my description.
Click to expand...
Click to collapse
Does this remove the red text on the start up screen? One look at that and HTC knows the phone has been altered. On Samsung devices once Knox is tripped you get a message saying so and it's permanent. Just curious.
comstockload said:
Does this remove the red text on the start up screen? One look at that and HTC knows the phone has been altered. On Samsung devices once Knox is tripped you get a message saying so and it's permanent. Just curious.
Click to expand...
Click to collapse
Red text will be removed after you flash a RUU. HTC is much simpler than Samsung regarding that. Just to be on the safe side, check bootloader status after each step. It's a quick procedure, but you're safe
S-off should be ok just make sure its locked not unlocked.
https://www.xda-developers.com/htc-...gn=Feed:+xda-developers/ShsH+(xda-developers)
donkeykong1 said:
First thing to do is backup everything from your phone to your PC. Then run a RUU ( I guess that would be US unlocked, not Verizon). After RUU is flashed, go to download mode and issue a command "fastboot oem writesecureflag 3" (without quotes). That will restore your security flag back to s-on. Then use Sunshine to set bootloader status to LOCKED and s-off (really the easiest way to set it to LOCKED, not RELOCKED). Finally, run "fastboot oem writesecureflag 3" once again, and done. You are 100% stock. It's much faster and simpler than it looks from my description.
Click to expand...
Click to collapse
Did all that (installing the RUU) and received only "re-locked" since it already was S-ON. Sunshine now cannot be used, because the RUU was installed. What did I do wrong, then?
Matt.Murdock said:
Did all that (installing the RUU) and received only "re-locked" since it already was S-ON. Sunshine now cannot be used, because the RUU was installed. What did I do wrong, then?
Click to expand...
Click to collapse
You can use Sunshine. But, if I understood correctly, your phine was never s-off. If that's true, you need to unlock your bootloader again, use Sunshine to get s-off, and then follow my steps
donkeykong1 said:
You can use Sunshine. But, if I understood correctly, your phine was never s-off. If that's true, you need to unlock your bootloader again, use Sunshine to get s-off, and then follow my steps
Click to expand...
Click to collapse
I see, so the only way to have the phone LOCKED is to root it and use Sunshine?
Matt.Murdock said:
I see, so the only way to have the phone LOCKED is to root it and use Sunshine?
Click to expand...
Click to collapse
Tecnicaly, you only need to unlock the bootloader and use Sunshine. No need to root, but, in general, the answer is yes
rooting without s-off
donkeykong1 said:
Tecnicaly, you only need to unlock the bootloader and use Sunshine. No need to root, but, in general, the answer is yes
Click to expand...
Click to collapse
how do you even get a verizon htc 10 with oreo installed rooted in the first place if the HTCdev site is unable to unlock your bootloader, Sunshine is unable to unlock your bootloader or S-Off? There is nothing on the internet that has this "Solved" issue that I've read. However after reading your response, are you sure anyone can unlock bootloader and then use sunshine without root?
pearson_1974 said:
how do you even get a verizon htc 10 with oreo installed rooted in the first place if the HTCdev site is unable to unlock your bootloader, Sunshine is unable to unlock your bootloader or S-Off? There is nothing on the internet that has this "Solved" issue that I've read. However after reading your response, are you sure anyone can unlock bootloader and then use sunshine without root?
Click to expand...
Click to collapse
If you read the first post, you will see that OP is running an US unlocked with Verizon ROM. In that case my steps are correct. If you have Verizon phone, you can't even unlock bootloader, so this is of no use for you
donkeykong1 said:
First thing to do is backup everything from your phone to your PC. Then run a RUU ( I guess that would be US unlocked, not Verizon). After RUU is flashed, go to download mode and issue a command "fastboot oem writesecureflag 3" (without quotes). That will restore your security flag back to s-on. Then use Sunshine to set bootloader status to LOCKED and s-off (really the easiest way to set it to LOCKED, not RELOCKED). Finally, run "fastboot oem writesecureflag 3" once again, and done. You are 100% stock. It's much faster and simpler than it looks from my description.
Click to expand...
Click to collapse
Hi. Sunshine .Pay once Or pay every time you use.
osakajung said:
Hi. Sunshine .Pay once Or pay every time you use.
Click to expand...
Click to collapse
Once
pearson_1974 said:
how do you even get a verizon htc 10 with oreo installed rooted in the first place if the HTCdev site is unable to unlock your bootloader, Sunshine is unable to unlock your bootloader or S-Off? There is nothing on the internet that has this "Solved" issue that I've read. However after reading your response, are you sure anyone can unlock bootloader and then use sunshine without root?
Click to expand...
Click to collapse
Only way is to mail your phone to the sunshine team
donkeykong1 said:
Once
Click to expand...
Click to collapse
I pay on the first to s-off/unlock bootloader.
I flash other rom.
I set "fastboot oem writesecureflag 3" to s-on.
I download Sunshine to set s-off/Lock bootloader is not pay?
osakajung said:
I pay on the first to s-off/unlock bootloader.
I flash other rom.
I set "fastboot oem writesecureflag 3" to s-on.
I download Sunshine to set s-off/Lock bootloader is not pay?
Click to expand...
Click to collapse
No. Once you pay for Sunshine, it's free for you to use as many times sa you need, as long as you don't change your motherboard
donkeykong1 said:
No. Once you pay for Sunshine, it's free for you to use as many times sa you need, as long as you don't change your motherboard
Click to expand...
Click to collapse
Thank you
Can't seem to find any into on relocking the bootloader with S-on
other than HTC has disabled the oem lock in 7.0
So is there anyway I can downgrade to with a TWRP backup, flash a stock recovery file relock the bootloader and then run the latest RUU to update everything or do I need S-off to downgrade the bootloader to relock?
It's not for a warranty claim, I just want to use Android pay since it works with my bank now.
I'm assuming a ***RELOCKED*** flag would pass it's security check?
I don't have sunshine since I never went S-off.
Vonrottes said:
Can't seem to find any into on relocking the bootloader with S-on
other than HTC has disabled the oem lock in 7.0
So is there anyway I can downgrade to with a TWRP backup, flash a stock recovery file relock the bootloader and then run the latest RUU to update everything or do I need S-off to downgrade the bootloader to relock?
It's not for a warranty claim, I just want to use Android pay since it works with my bank now.
I'm assuming a ***RELOCKED*** flag would pass it's security check?
I don't have sunshine since I never went S-off.
Click to expand...
Click to collapse
You may want to look into flashing a custom kernel, like ElementalX. Hides the bootloader unlocked status from safetynet. You'd also need to have an untouched system partition as well for Android Pay to work.
You can simply relock the bootloader, no need to downgrade. But you will have to flash a RUU >= your current version. Done it several times, it works
The command world be "fastboot oem lock". Phone needs to be in download mode, obviously...
Relock flag passes safetynet, yes.
bopsch said:
You can simply relock the bootloader, no need to downgrade. But you will have to flash a RUU >= your current version. Done it several times, it works
The command world be "fastboot oem lock". Phone needs to be in download mode, obviously...
Relock flag passes safetynet, yes.
Click to expand...
Click to collapse
You sure?
I've tried it 3 times with a 2.41 RUU the command does what it should, but reboot still shows unlocked.
Vonrottes said:
You sure?
I've tried it 3 times with a 2.41 RUU the command does what it should, but reboot still shows unlocked.
Click to expand...
Click to collapse
Enable OEM unlocking option in developer options from settings. Then the command.
A breadcrumb for anybody on the same trail...
If your bootloader status is still "unlocked" even after flashing a stock RUU and passing a seemingly successful "fastboot oem lock", try removing your SD card and "fastboot oem lock" again. After a load of messing around this immediately allowed me to gain "Relocked".
I loved my HTC10 in it's heyday but I'm so over all these HTC quirks