Database Develop

[DEV][Solved]Need advanced help with HBOOT... Unique S-Off situation

Hey guys... Ok I am in a very unique situation. I was recently testing to get 4.2.2 ROMs to work on sprint with a kernel...
Well, it ended up not working, and a few things ended up getting jittery. So i relocked bootloader, did a fastboot oem rebootRUU, and went ahead and ruu'd the phone. Here is where it gets weird...
After the RUU finished succesfully, I went into bootloader, and it showed "RELOCKED S-OFF", and figured that cant be good, so i proceeded to do a fastboot oem writesecureflag 3, and re-relocked via RevONE. Bootloader now showed "LOCKED S-ON", so RUU'd again. Now, my CID is still unlocked which has nothing to do with hboot i know. Either way, I did the fastboot flash unlocktoken......, and got HTCDEV unlocked. I then proceed to unlock via RevONE with all successful. I even flashed the boot_unsecure.img (kernel) on the stock RUU rom.
Bootloader shows "UNLOCKED S-OFF"... But I am not S-Off, simply my flag shows it. I cannot flash a different hboot, nor can i flash a radio (and yes i tried flashing within rebootRUU). It gives me the stupid "remote - not allowed".
Would there be a way to DD the mmcblk? Does anyone on an ENG S-Off bootloader have the mmcblk partition number? Mine does not show the hboot label... cat /proc/emmc.
Anyone ideas? Moonshine does not work either.
Update... MMCBLK0P12 hboot
Solved
Lol that was easy... Just had to do a low level overwrite (DD) to an ENG hboot, so that i could then truely S-Off, and flash other hboots and radios... sheesh...

Tilde88 said:
Hey guys... Ok I am in a very unique situation. I was recently testing to get 4.2.2 ROMs to work on sprint with a kernel...
Well, it ended up not working, and a few things ended up getting jittery. So i relocked bootloader, did a fastboot oem rebootRUU, and went ahead and ruu'd the phone. Here is where it gets weird...
After the RUU finished succesfully, I went into bootloader, and it showed "RELOCKED S-OFF", and figured that cant be good, so i proceeded to do a fastboot oem writesecureflag 3, and re-relocked via RevONE. Bootloader now showed "LOCKED S-ON", so RUU'd again. Now, my CID is still unlocked which has nothing to do with hboot i know. Either way, I did the fastboot flash unlocktoken......, and got HTCDEV unlocked. I then proceed to unlock via RevONE with all successful. I even flashed the boot_unsecure.img (kernel) on the stock RUU rom.
Bootloader shows "UNLOCKED S-OFF"... But I am not S-Off, simply my flag shows it. I cannot flash a different hboot, nor can i flash a radio (and yes i tried flashing within rebootRUU). It gives me the stupid "remote - not allowed".
Would there be a way to DD the mmcblk? Does anyone on an ENG S-Off bootloader have the mmcblk partition number? Mine does not show the hboot label... cat /proc/emmc.
Anyone ideas? Moonshine does not work either.
Update... MMCBLK0P12 hboot
Solved
Lol that was easy... Just had to do a low level overwrite (DD) to an ENG hboot, so that i could then truely S-Off, and flash other hboots and radios... sheesh...
Click to expand...
Click to collapse
I thought once soff always soff I have ruu 2 times already after soff revone and was still able to flash the radio from the newest firmware. After every ruu it always said soff
Sent from my GT-P3113 using xda app-developers app

Just out of curisosity, could anyone explain why that happened? What made the security flag change?
Also, why did you say "this cannot be good" when you saw "RELOCKED S-OFF"? Were you S-OFF to begin with? You can lock the bootloader and still remain S-Off, correct?

karn101 said:
Just out of curisosity, could anyone explain why that happened? What made the security flag change?
Also, why did you say "this cannot be good" when you saw "RELOCKED S-OFF"? Were you S-OFF to begin with? You can lock the bootloader and still remain S-Off, correct?
Click to expand...
Click to collapse
Yes, but I figured that while it was relocked, it would overwrite the hboot to stock if I RUU'd, thus making the flag S-On. however, this needed to be manually done with fastboot apparently.
Tbh, I think this all started from a ROM flash, it was an international ROM, and I hadn't bothered to check to know the partition layouts were different. Kernel ended up flashing to recovery, and system almost went to radio, lol idk how it didn't brick.... but yea.

Tilde88 said:
Yes, but I figured that while it was relocked, it would overwrite the hboot to stock if I RUU'd, thus making the flag S-On. however, this needed to be manually done with fastboot apparently.
Tbh, I think this all started from a ROM flash, it was an international ROM, and I hadn't bothered to check to know the partition layouts were different. Kernel ended up flashing to recovery, and system almost went to radio, lol idk how it didn't brick.... but yea.
Click to expand...
Click to collapse
Oh, so you were more concerned that it said relocked than S-OFF. S-OFF was bolded so I thought you were saying "Uh oh" to the S-Off.

[Q] I have S-ON... why?!

OK, so I unlocked my HTC one bootloader with the 'legit' method (as it came with android 4.2.2) via the HTC site.
I have TWRP, tried a bunch of custom roms and a couple of different kernels.
Well, I decided that I liked a previous kernel and went back to re-flash it again. It wouldn't work. When doing it the phone would just reboot every time, or simply freeze on trying to do it.
After a while, I noticed that S-OFF was S-ON again :S
I haven't made an intentional attempt of switching it back again.
Not sure even how it happened!
Any ideas how to get S-OFF again? And maybe any ideas why it may have reverted on it's own accord?
Thanks,
Mark.

I don't think it was ever S-Off; the HTCDev site unlock keeps security on. And as to my knowledge Android Jelly Bean 4.2.2 has HBoot 1.54. Someone double check me on that... But yeah, you can't S-Off now with HBoot 1.54; only 1.44 is supported. If your HBoot is 1.44, then just do it through Revone; Google "Revone S-Off" and you will find the XDA thread on how to do it.

yorkies88888 said:
I don't think it was ever S-Off; the HTCDev site unlock keeps security on. And as to my knowledge Android Jelly Bean 4.2.2 has HBoot 1.54. Someone double check me on that... But yeah, you can't S-Off now with HBoot 1.54; only 1.44 is supported. If your HBoot is 1.44, then just do it through Revone; Google "Revone S-Off" and you will find the XDA thread on how to do it.
Click to expand...
Click to collapse
OK, that's fair enough, I probably was under the false assumption that I had S-OFF and didn't.
Having said that, I was also under the assumption that to flash a kernel, S-OFF was required?
Am I wrong on that? I have definitely managed to flash a couple of them already, and now they won't do so. Any thoughts on what could be causing that, if this isn't the issue?
Thanks,
Mark.

Nope, with the One, we can flash the kernel in recovery with s-on.
Only in some device like One X/S/V we can't do this without s-off.
However, from htcdev you will only unlock the bootloader, you will stay with s-on

Guich said:
Nope, with the One, we can flash the kernel in recovery with s-on.
Only in some device like One X/S/V we can't do this without s-off.
However, from htcdev you will only unlock the bootloader, you will stay with s-on
Click to expand...
Click to collapse
OK, thanks for the consise info.
Based on this though, can you think of any reason that I wouldn't be able to flash a kernel?
It was working fine, and now it isn't.
I've tried elementalx and bulletproof.
I can set them both up through the aroma installer, but when it actually comes to flashing, as I already stated, the script starts and my phone either freezes or reboots.
Kinda annoying

You can flash any kernel with s-on.
I flashed they before achived the s-off
So, aroma will freeze?
Try the faux and report the log here

cacoe said:
OK, thanks for the consise info.
Based on this though, can you think of any reason that I wouldn't be able to flash a kernel?
It was working fine, and now it isn't.
I've tried elementalx and bulletproof.
I can set them both up through the aroma installer, but when it actually comes to flashing, as I already stated, the script starts and my phone either freezes or reboots.
Kinda annoying
Click to expand...
Click to collapse
This is an aroma bug. Came with an update to the aroma installer, not kernel related. Current fix is to retry process until it works.
AT&T HTC M7ul
Baad Newz's InsertCoin 3.4-2
Flar2's Bulletproof 6.2

Guich said:
You can flash any kernel with s-on.
I flashed they before achived the s-off
So, aroma will freeze?
Try the faux and report the log here
Click to expand...
Click to collapse
Faux123 worked great! Presumebly because it doesn't use an aroma script. Thanks a load, it actually has more features than the other ROMs that I had tried

[SOLVED] CID change and repairs

There is no ruu for my phone (02___001) so now I have s off I was going to run a stock ruu and update to the latest firmware. If I send the phone back for repair and change my cid to HTC_001 would HTC know I have changed my cid even if I s on?

Anyone help me at all?

stovie_steve said:
Anyone help me at all?
Click to expand...
Click to collapse
Two things:
1- I dont know if they keep a record of IMEI (or s/n) <--> carrier, but I think they have to and do.
2- the CID is stored in several partitions, not only the one you change with fastboot writecid.
HOWEVER, it really depends on how far they're going to dig into this, if they are going to check their IMEI database or check the different partitions on the phone, just to "prove you wrong", I guess they could.
But then again, would it be worth all that hassle for them?
I dont have any experience with repair centers or how far they would go to prove that you changed something on your phone, and it's really quite country (and HTC people) dependent; for some they have no problem with an unlocked or relocked phone, and other even have a problem with S-Off (though they can't prove the phone didn't ship that way in the first place)
Better have someone from your region (O2 so UK?) post their experience(s)

Ah that's ok
So you reckon it would be better to be completely stock with stock CID and leave it s-off as it could ha e shipped that way anyway even for a carrier branded phone?

stovie_steve said:
Ah that's ok
So you reckon it would be better to be completely stock with stock CID and leave it s-off as it could ha e shipped that way anyway even for a carrier branded phone?
Click to expand...
Click to collapse
I honestly cannot say mate, have ZERO experience with this, just what I've read from other people; can't remember which countries, but some have sent their phone in for repair (eg for the purple camera issue) with tampered, unlocked etc and got either a repair or a brand new phone, others sent it completely stock, only with S-Off and were refused service (and the service center can't even prove it didn't ship that way, nor did they try).
Sorry can't help you out, or give any good advice about that.
I can help get you back to stock, or at least as close to stock as possible (you can check some of the other guys I've helped out in the Q&A section), but that's about as far as I can go.
Cheers & good luck
EDIT: one guy I helped (I think from Canada) got it 100% stock and S-On, and the a**holes still gave him a hard time, don't know what happened in the end, hope they fixed it for him.

nkk71 said:
I honestly cannot say mate, have ZERO experience with this, just what I've read from other people; can't remember which countries, but some have sent their phone in for repair (eg for the purple camera issue) with tampered, unlocked etc and got either a repair or a brand new phone, others sent it completely stock, only with S-Off and were refused service (and the service center can't even prove it didn't ship that way, nor did they try).
Sorry can't help you out, or give any good advice about that.
I can help get you back to stock, or at least as close to stock as possible (you can check some of the other guys I've helped out in the Q&A section), but that's about as far as I can go.
Cheers & good luck
EDIT: one guy I helped (I think from Canada) got it 100% stock and S-On, and the a**holes still gave him a hard time, don't know what happened in the end, hope they fixed it for him.
Click to expand...
Click to collapse
If you could help me yes that would be great mate
The steps I took to get where I am are as follows:
1. I was running a stock 02 UK Rom (2.24.206.7) and achieved s off using rumrunner
2. I downgraded hboot to 1.44 and installed a stock ruu for cid HTC__001
3. I flashed cwm recovery and nandroid restored my phone to o2 backup 1.29.206.1 and flashed a stock recovery before locking the bootloader using adb shell command and then installing the updates (my cid was also changed back to 02___001 to do this). I note also that I'm not sure that the recovery was completely stock, as I had to manually reboot the phone a few times to allow the ota to install.
4. I upgraded my phone via various OTA's until the latest 3.62.206.1 firmware
5. Satisfied that the OTA had flashed the latest stock hboot, stock recovery and stock Rom I did fastboot oem writesecureflag 3. I got success and when I reboot it said tamper detected - rebooting. The bootloader is now locked, s on and tampered
What steps would you add/take away or change?
I can unlock again using htcdev and start again I guess
Would you advise maybe re running rumrunner once I'm back to version 2.24.206.7 and run all the commands again (lock, remove tampered) and then s on?
The reason I ran the ota from an earlier nandroid was because I thought I would restore everything to stock by ota
If you help me achieve this I will gladly buy you a beer lol!

stovie_steve said:
If you could help me yes that would be great mate
The steps I took to get where I am are as follows:
1. I was running a stock 02 UK Rom (2.24.206.7) and achieved s off using rumrunner
2. I downgraded hboot to 1.44 and installed a stock ruu for cid HTC__001
3. I flashed cwm recovery and nandroid restored my phone to o2 backup 1.29.206.1 and flashed a stock recovery before locking the bootloader using adb shell command and then installing the updates (my cid was also changed back to 02___001 to do this). I note also that I'm not sure that the recovery was completely stock, as I had to manually reboot the phone a few times to allow the ota to install.
4. I upgraded my phone via various OTA's until the latest 3.62.206.1 firmware
5. Satisfied that the OTA had flashed the latest stock hboot, stock recovery and stock Rom I did fastboot oem writesecureflag 3. I got success and when I reboot it said tamper detected - rebooting. The bootloader is now locked, s on and tampered
What steps would you add/take away or change?
I can unlock again using htcdev and start again I guess
Would you advise maybe re running rumrunner once I'm back to version 2.24.206.7 and run all the commands again (lock, remove tampered) and then s on?
The reason I ran the ota from an earlier nandroid was because I thought I would restore everything to stock by ota
If you help me achieve this I will gladly buy you a beer lol!
Click to expand...
Click to collapse
1- Well the steps you took sound very good (I personally, would have skipped all the OTAs), but can you elaborate on "when I reboot it said tamper detected - rebooting", do you mean that you had removed TAMPERED and it suddenly came back by itself???
2- For you to be able to fix this, you will need S-Off, I just checked rumrunner, and there's only a 3.62.401.1 package around, hopefully it will work, otherwise you will need: "If you mainver is not listed, please contact [email protected] with firmware version AND a link to the corresponding RUU and/or firmware ota package." (http://forum.xda-developers.com/showthread.php?t=2487888)
3- I guess you're going to have to unlock again, and try rumrunner 3.62.401.1 package and hope it works without the hassle of having to send in you firmware.
4- Beer won't be necessary, I'm actually enjoying a scotch at the moment ; maybe when I'm in London next time Otherwise hitting the thanks button, is more than enough!
So I guess, go ahead an unlock and try to get S-Off, post back with results. I'll keep an :cyclops: on the thread and help as much I can.

nkk71 said:
1- Well the steps you took sound very good (I personally, would have skipped all the OTAs), but can you elaborate on "when I reboot it said tamper detected - rebooting", do you mean that you had removed TAMPERED and it suddenly came back by itself???
2- For you to be able to fix this, you will need S-Off, I just checked rumrunner, and there's only a 3.62.401.1 package around, hopefully it will work, otherwise you will need: "If you mainver is not listed, please contact [email protected] with firmware version AND a link to the corresponding RUU and/or firmware ota package." (http://forum.xda-developers.com/showthread.php?t=2487888)
3- I guess you're going to have to unlock again, and try rumrunner 3.62.401.1 package and hope it works without the hassle of having to send in you firmware.
4- Beer won't be necessary, I'm actually enjoying a scotch at the moment ; maybe when I'm in London next time Otherwise hitting the thanks button, is more than enough!
So I guess, go ahead an unlock and try to get S-Off, post back with results. I'll keep an :cyclops: on the thread and help as much I can.
Click to expand...
Click to collapse
Yes the phone said on booting up the Rom - "tamper detected - rebooting" and then my bootloader said tampered
I had to do the ota as I didn't have the stock recovery for version 1.29.206.7 as I knew the ota would flash an official recovery
I guess I could 're-run s off rumrunner when I'm on 2.24.206.7 (the 2.24.401.7 version works for this) and reset all the flags and then s on again?
You think that could work?

stovie_steve said:
Yes the phone said on booting up the Rom - "tamper detected - rebooting" and then my bootloader said tampered
Click to expand...
Click to collapse
Hmmm, interesting (only saw 1 other post like that, I think), did that happen after the last OTA which updated hboot to 1.55; wondering if they "patched" something in 1.55.
stovie_steve said:
I had to do the ota as I didn't have the stock recovery for version 1.29.206.7 as I knew the ota would flash an official recovery
Click to expand...
Click to collapse
The first OTA would have been enough, you didn't need to go all the way to 3.62; you had to manually reboot the first OTA yourself because stock recovery wasn't 100% correct, but after the OTA was successfully installed, you could have stopped at that.
stovie_steve said:
I guess I could 're-run s off rumrunner when I'm on 2.24.206.7 (the 2.24.401.7 version works for this) and reset all the flags and then s on again?
You think that could work?
Click to expand...
Click to collapse
Problem is you are already on 3.62 and downgrading isn't possible with S-On, so you're going to have to unlock and try a rumrunner package that get's you s-off. If the 3.62.401 rumrunner works or the 2.24.206.7 or whichever one works to get you S-Off it doesn't matter, but you do need to get S-Off (IMHO).

nkk71 said:
Hmmm, interesting (only saw 1 other post like that, I think), did that happen after the last OTA which updated hboot to 1.55; wondering if they "patched" something in 1.55.
The first OTA would have been enough, you didn't need to go all the way to 3.62; you had to manually reboot the first OTA yourself because stock recovery wasn't 100% correct, but after the OTA was successfully installed, you could have stopped at that.
Problem is you are already on 3.62 and downgrading isn't possible with S-On, so you're going to have to unlock and try a rumrunner package that get's you s-off. If the 3.62.401 rumrunner works or the 2.24.206.7 or whichever one works to get you S-Off it doesn't matter, but you do need to get S-Off (IMHO).
Click to expand...
Click to collapse
I'm going to unlock via HTC dev, install guru reset via recovery and s off again. Then 're run the nandroid backup ota til 2.24.206.7, n 're run rumrunner

stovie_steve said:
I'm going to unlock via HTC dev, install guru reset via recovery and s off again. Then 're run the nandroid backup ota til 2.24.206.7, n 're run rumrunner
Click to expand...
Click to collapse
Okidoke, good luck :fingers-crossed:.
I'm two hours ahead of you... okay that sounds bad :silly:, what I mean is there's a two hour difference between us, but I'll keep checking your thread for a while longer (an hour or two). if you post something and I don't get back to you tonight, I'll definitely check again tomorrow.

nkk71 said:
Okidoke, good luck :fingers-crossed:.
I'm two hours ahead of you... okay that sounds bad :silly:, what I mean is there's a two hour difference between us, but I'll keep checking your thread for a while longer (an hour or two). if you post something and I don't get back to you tonight, I'll definitely check again tomorrow.
Click to expand...
Click to collapse
No problem!
Right these are the steps I'm going to do
1. Unlock bootloader via HTC dev
2. Install guru reset for 2.24.401.8
3. Run rumrunner and get s off
4. Downgrade hboot to 1.44
5. Restore nandroid backup for my 02 version 1.28.206.7
6. Upgrade via OTA to 2.24.206.7 (mostly to fix the stock recovery to match)
7. Go s-on to see what happens
8. If s-on fails in any way then redo the HTC dev unlock, 're run rumrunner and get s off again using the same version of rumrunner
9. Reset tampered flag and lock bootloader via adb shell
10. Retry s-on again
11. Upgrade to latest hboot without having to do writesecureflag 3 again
Thoughts on this method? I'm just wondering if people tried going s on in hboot 1.55 caused this tampered message to appear or if I s on first and then update will it appear then after? I do t know. I'd like to hear your thoughts tho

stovie_steve said:
No problem!
Right these are the steps I'm going to do
1. Unlock bootloader via HTC dev
2. Install guru reset for 2.24.401.8
3. Run rumrunner and get s off
4. Downgrade hboot to 1.44
5. Restore nandroid backup for my 02 version 1.28.206.7
6. Upgrade via OTA to 2.24.206.7 (mostly to fix the stock recovery to match)
7. Go s-on to see what happens
8. If s-on fails in any way then redo the HTC dev unlock, 're run rumrunner and get s off again using the same version of rumrunner
9. Reset tampered flag and lock bootloader via adb shell
10. Retry s-on again
11. Upgrade to latest hboot without having to do writesecureflag 3 again
Thoughts on this method? I'm just wondering if people tried going s on in hboot 1.55 caused this tampered message to appear or if I s on first and then update will it appear then after? I do t know. I'd like to hear your thoughts tho
Click to expand...
Click to collapse
Ok, my thoughts, in a nutshell
1. Unlock bootloader via HTC dev <- YES
2----- try rumrunner 3.62
2. Install guru reset for 2.24.401.8
3. Run rumrunner and get s off <- Ok, try, if it fails use above rumrunner 3.62
Once S-Off:
--- remove tampered: revone or http://forum.xda-developers.com/showthread.php?t=2477792
5. Restore nandroid backup for my 02 version 1.28.206.7
--- set phone to LOCKED, using revone (or http://forum.xda-developers.com/showthread.php?t=2475914)
------- you will need to have SU privileges which you can get using revone or flashing SuperSU; if you do flash SuperSU, uninstall it after getting LOCKED
6. Upgrade via OTA to 2.24.206.7 (mostly to fix the stock recovery to match) <- Yep
11. Upgrade to latest hboot without having to do writesecureflag 3 again
Once you have your bootloader "LOCKED", no TAMPERED, no red text on bootup, do "fastboot oem writesecureflag 3"
reboot three times and see if everything sticks, and don't take any other OTAs.
Hit me with a thanks if this was useful

So you think I shouldn't upgrade to the latest OTA once I get s on?

stovie_steve said:
So you think I shouldn't upgrade to the latest OTA once I get s on?
Click to expand...
Click to collapse
Since you're sending it in for repair, why would you want to?
But anyway, as long as the above steps work to get S-Off (again and again, if necessary), you can try and see if you dont get that "tamper detected" thing again. If it doesnt show up again you're all good to go.
(and I would be curious if we could find out where that comes from. the "tamper detected" hmmm )

nkk71 said:
Since you're sending it in for repair, why would you want to?
But anyway, as long as the above steps work to get S-Off (again and again, if necessary), you can try and see if you dont get that "tamper detected" thing again. If it doesnt show up again you're all good to go.
(and I would be curious if we could find out where that comes from. the "tamper detected" hmmm )
Click to expand...
Click to collapse
Ok so I'll do the HTC dev unlock and install the guru reset by recovery and s off again. The rumrunner for 3.62.401 does not work with my rpm version
After that I'll downgrade the hboot to 1.44, install an android 4.1.2 RUU and then flash my nandroid backup. I'll reset the tamper and lock bootloader after flashing stock recovery
Then I'll upgrade to 2.24.206.7 and try s on. If it fails. I'll run the rumrunner for version 2.24.401.8 which def works with that Rom version as confirmed by others. Then I'll do the reset flags again and try s on. Try few reboots then send in for repair once satisfied
Sound like a plan? I hope so lol

stovie_steve said:
Ok so I'll do the HTC dev unlock and install the guru reset by recovery and s off again. The rumrunner for 3.62.401 does not work with my rpm version
After that I'll downgrade the hboot to 1.44, install an android 4.1.2 RUU and then flash my nandroid backup. I'll reset the tamper and lock bootloader after flashing stock recovery
Then I'll upgrade to 2.24.206.7 and try s on. If it fails. I'll run the rumrunner for version 2.24.401.8 which def works with that Rom version as confirmed by others. Then I'll do the reset flags again and try s on. Try few reboots then send in for repair once satisfied
Sound like a plan? I hope so lol
Click to expand...
Click to collapse
N I need to downgrade the hboot otherwise my touch screen won't work with the nandroid backup. Then again I don't necessarily have to run the ruu either

stovie_steve said:
Ok so I'll do the HTC dev unlock and install the guru reset by recovery and s off again. The rumrunner for 3.62.401 does not work with my rpm version
After that I'll downgrade the hboot to 1.44, install an android 4.1.2 RUU and then flash my nandroid backup. I'll reset the tamper and lock bootloader after flashing stock recovery
Then I'll upgrade to 2.24.206.7 and try s on. If it fails. I'll run the rumrunner for version 2.24.401.8 which def works with that Rom version as confirmed by others. Then I'll do the reset flags again and try s on. Try few reboots then send in for repair once satisfied
Sound like a plan? I hope so lol
Click to expand...
Click to collapse
Yep, sounds good, except I would unlock using HTCdev then immediately try the 3.62 rumrunner to get S-Off, if it works GREAT and you're pretty much sure to be able to "easily" get S-Off on any version.
If it doesn't S-Off then try the Guru Reset.
BTW, as soon as you unlock, do a nandroid and "adb pull" it to your PC! just in case.

nkk71 said:
Yep, sounds good, except I would unlock using HTCdev then immediately try the 3.62 rumrunner to get S-Off, if it works GREAT and you're pretty much sure to be able to "easily" get S-Off on any version.
If it doesn't S-Off then try the Guru Reset.
BTW, as soon as you unlock, do a nandroid and "adb pull" it to your PC! just in case.
Click to expand...
Click to collapse
And how to I keep hold of the 3.62.206.1 recovery before I do a nandroid backup?

stovie_steve said:
N I need to downgrade the hboot otherwise my touch screen won't work with the nandroid backup. Then again I don't necessarily have to run the ruu either
Click to expand...
Click to collapse
the touchscreen drivers were part of the 2.xx firmware package, not hboot, so if you don't use a full RUU, it will break the touchscreen drivers, but you can use an OTG cable + mouse.
stovie_steve said:
And how to I keep hold of the 3.62.206.1 recovery before I do a nandroid backup?
Click to expand...
Click to collapse
Unfortunately you can't (anymore), but this one should be close enough: http://d-h.st/users/guich/?fld_id=25920#files, or the best thing is to get a hold of the OTA 3.62.206.1 file and extract it from it.
Anyway, in my humble opinion, first things first: unlock using HTCdev and see if you can get rumrunner to S-Off on 3.62.

[Q] PLEASE help me return to stock URGENT

2.24.980.2
s-off
CID-OPTUS001
HBOOT1.54.0000
returned to stock back up - android 4.2.2 (after using viperone rc2)
recovery - latest twrp
how the heck can i remove *Tampered* and *Unlocked* and restore the stock recovery? can i downgrade hboot because every method i have found has said "does not work with hboot 1.54+"
i need to return my phone under warranty because the speakers are making terrible crackling sounds and the phone doesnt vibrate anymore. . . i am so damn carful with my phones always have an otterbox on them and never dropped it ever so its ticking me off a bit.
any help would be greatly appreciated

jande425 said:
2.24.980.2
s-off
CID-OPTUS001
HBOOT1.54.0000
returned to stock back up - android 4.2.2 (after using viperone rc2)
recovery - latest twrp
how the heck can i remove *Tampered* and *Unlocked* and restore the stock recovery? can i downgrade hboot because every method i have found has said "does not work with hboot 1.54+"
i need to return my phone under warranty because the speakers are making terrible crackling sounds and the phone doesnt vibrate anymore. . . i am so damn carful with my phones always have an otterbox on them and never dropped it ever so its ticking me off a bit.
any help would be greatly appreciated
Click to expand...
Click to collapse
since you are s-off just download a ruu and flash it s-off allows you to run any ruu

jande425 said:
2.24.980.2
s-off
CID-OPTUS001
HBOOT1.54.0000
returned to stock back up - android 4.2.2 (after using viperone rc2)
recovery - latest twrp
how the heck can i remove *Tampered* and *Unlocked* and restore the stock recovery? can i downgrade hboot because every method i have found has said "does not work with hboot 1.54+"
i need to return my phone under warranty because the speakers are making terrible crackling sounds and the phone doesnt vibrate anymore. . . i am so damn carful with my phones always have an otterbox on them and never dropped it ever so its ticking me off a bit.
any help would be greatly appreciated
Click to expand...
Click to collapse
Have you checked my guide http://forum.xda-developers.com/showthread.php?t=2541082

nkk71 said:
Have you checked my guide http://forum.xda-developers.com/showthread.php?t=2541082
Click to expand...
Click to collapse
Fails every time i try to flash the zip it goes through a couple steps then says failed. . . . :/

jerrycoffman45 said:
since you are s-off just download a ruu and flash it s-off allows you to run any ruu
Click to expand...
Click to collapse
will a ruu remove the tampered and unlocked ??

jande425 said:
will a ruu remove the tampered and unlocked ??
Click to expand...
Click to collapse
will removed tampered but not unocked

jerrycoffman45 said:
will removed tampered but not unocked
Click to expand...
Click to collapse
fu** sake i cant even flash the correct RUU

i downgraded my hboot to 1.44 and got super cid
but i still cant remove unlocked and tampered

alright if anyone happens to see this this is where i am at now
i have removed tampered and unlocked (replaced with locked) but i can not for the life of me figure out how to restore the stock recovery without having the device saying "unlocked"
i have the guru tool which can remove tampered and lock and unlock boot loader but i want the stock recovery on my phone so i an return for warranty purposes the only way i can use the guru tool is through cwm. . when i lock the bootloader i cant change the recovery . . . what in the damn hell do i do hahaha
currently hboot 1.44
s off

jande425 said:
alright if anyone happens to see this this is where i am at now
i have removed tampered and unlocked (replaced with locked) but i can not for the life of me figure out how to restore the stock recovery without having the device saying "unlocked"
i have the guru tool which can remove tampered and lock and unlock boot loader but i want the stock recovery on my phone so i an return for warranty purposes the only way i can use the guru tool is through cwm. . when i lock the bootloader i cant change the recovery . . . what in the damn hell do i do hahaha
currently hboot 1.44
s off
Click to expand...
Click to collapse
check my thread, replied to you there

[Q] Boot loop after RUU

So my problem is the further, I had a fully working HTC first with the latest Hboot update previously moonshined with the old one. So I had S-off, root, JMZ's custom kernel and an unlocked bootloader but then after a while I've done alot of flashes, zip installs tweaks and modifications that created pesky problems that wouldn't go away with a simple wipe in CWM. That's okay though I could just do a complete restore with the RUU. And i did, no I didn't re-lock the bootloader because I had S-off anyways. Everything came out great. But then I went ahead and the problems started to happen.. After unlocking the bootloader I had an eternal bootloop that wouldn't go away, but did a simple re-lock and booted up just fine.
My question is what the hell am I doing wrong? does it have to do with the version of RUU im using?

abrahammmmmmm_ said:
So my problem is the further, I had a fully working HTC first with the latest Hboot update previously moonshined with the old one. So I had S-off, root, JMZ's custom kernel and an unlocked bootloader but then after a while I've done alot of flashes, zip installs tweaks and modifications that created pesky problems that wouldn't go away with a simple wipe in CWM. That's okay though I could just do a complete restore with the RUU. And i did, no I didn't re-lock the bootloader because I had S-off anyways. Everything came out great. But then I went ahead and the problems started to happen.. After unlocking the bootloader I had an eternal bootloop that wouldn't go away, but did a simple re-lock and booted up just fine.
My question is what the hell am I doing wrong? does it have to do with the version of RUU im using?
Click to expand...
Click to collapse
You got to turn S-ON after you RUU a previously S-OFF'd device.

Kendosis said:
You got to turn S-ON after you RUU a previously S-OFF'd device.
Click to expand...
Click to collapse
Wow, well I was completely unaware of that. Sorry for the noob question but how would i go about in doing that?

abrahammmmmmm_ said:
Wow, well I was completely unaware of that. Sorry for the noob question but how would i go about in doing that?
Click to expand...
Click to collapse
http://androidforums.com/internatio...-return-100-stock-revone-moonshine-s-off.html

Kendosis said:
http://androidforums.com/internatio...-return-100-stock-revone-moonshine-s-off.html
Click to expand...
Click to collapse
Thanks! One question: what's the stock cid number for the RUU the first has? I now have S-on but when I tried to run the RUU again to see if everything was working I got error 131 which shows when there's a CID mismatch. The CID I used was cws__001. I have the first with a t-mobile simcard by the way if that changes anything

abrahammmmmmm_ said:
Thanks! One question: what's the stock cid number for the RUU the first has? I now have S-on but when I tried to run the RUU again to see if everything was working I got error 131 which shows when there's a CID mismatch. The CID I used was cws__001. I have the first with a t-mobile simcard by the way if that changes anything
Click to expand...
Click to collapse
Try a different version of the ruu, there's two iirc. Try version 1.08.502.1 if that doesn't work try the next version.

Kendosis said:
Try a different version of the ruu, there's two iirc. Try version 1.08.502.1 if that doesn't work try the next version.
Click to expand...
Click to collapse
I tried both and it's a no go. Pretty sure it has to do with me changing the cid number on without knowing to the one I said earlier. But I guess if I would ever want to run the ruu I'd have to s-off it first and do it the long way then but at least I can successfully unlock the boot loader now with no problems, or at least I think. (Haven't tried it yet)
Edit:
Problem solved I unlocked the bootloader once more moonshined and set a supercid on the phone