Database Info

A Downgrade for 2.3.3 <maybe>

sorry it was a fail but will keep working

S-ON will not allow them to be flashed. Not even with a goldcard

HOW CAN WE DOWNGRADE THE BOOTLOADER. i can get teh RUUs to go but quits when it detects the bootloader.

malibu_23 said:
HOW CAN WE DOWNGRADE THE BOOTLOADER. i can get teh RUUs to go but quits when it detects the bootloader.
Click to expand...
Click to collapse
If Nand can be unlocked (S-OFF) then the bootloader can be downgraded but that's the initial hurdle is finding a way since the bootloader is encrypted

S-off after htcdev-bootloader-unlock?

First of all: I tried to find some useful info on the web to solve the problem... But if u guys got some useful links -» give it to me
Okay. My Ds is on hboot 2... Bootloader is unlocked with htcdev... And s-on...
I am sick of always flashing boot.IMG after flashing a Rom with 4ext... So my question is: is there a way to get s-off to "easily" install Roms without downgrading hboot..?
Sent from my HTC Desire S using XDA

Check this out:
forum.xda-developers.com/newreply.php?do=newreply&p=23771478

Saipro said:
Check this out:
forum.xda-developers.com/newreply.php?do=newreply&p=23771478
Click to expand...
Click to collapse
doesn't really help me, sry...

@rizmdee
Your only option is to downgrade to a older hboot, here a two threads
http://forum.xda-developers.com/showthread.php?t=1399331
http://forum.xda-developers.com/showthread.php?t=1443636
Once downgraded you can s-off with revolutionary, have a look here in section 1.

foX2delta said:
@rizmdee
Your only option is to downgrade to a older hboot, here a two threads
http://forum.xda-developers.com/showthread.php?t=1399331
http://forum.xda-developers.com/showthread.php?t=1443636
Once downgraded you can s-off with revolutionary, have a look here in section 1.
Click to expand...
Click to collapse
how to >without< unlocking with htc dev.... my device is allready unlocked, so i don't really think it will work...?

It will work too. You've got same hboot 2.xxx and are ever s-on with the same firmware . Don't forget to relock your bootloader using fastboot before flashing RUU.
fastboot oem lock
The only difference is that HTC now know you've unlocked your bootloader and can void your warranty if something goes wrong.
Sent from my Desire S using xda

@rizmdee
Just do it already and stop shooting things down. I understand that you are already unlocked, but if you took the time you would see that people that have unlocked have used it, you will only need to "fastboot oem lock" to install the RUU, READ and it will all be clear.
Also if you want to get into the details, then yeah if you are unlocked and have rooted or have a rooted rom, I assume you are, then just jump to changing your misc version cause you already have root #, no need for temp root, but for you I suggest you just follow it cause you will confuse yourself, .
Also just make a goldcard for the hell of it, casue I am unsure if you have a unbraded phone.

@foX2delta:
I tried it before I unlocked with htc-dev and it didn't work... so I#m not really sure
and does it work, if I got allrdy flashed custom rom (primo-s 1.3)? And if not: can i re-unlock with "fastboot oem unlock" ?
EDIT: my device ain't branded... deviceinfo-app says htc-europe...
Thanks a lot pplz... ill try and post again...

foX2delta said:
@rizmdee
Just do it already and stop shooting things down. I understand that you are already unlocked, but if you took the time you would see that people that have unlocked have used it, you will only need to "fastboot oem lock" to install the RUU, READ and it will all be clear.
Also if you want to get into the details, then yeah if you are unlocked and have rooted or have a rooted rom, I assume you are, then just jump to changing your misc version cause you already have root #, no need for temp root, but for you I suggest you just follow it cause you will confuse yourself, .
Also just make a goldcard for the hell of it, casue I am unsure if you have a unbraded phone.
Click to expand...
Click to collapse
misc_version worked...
oem lock worked...
BUT: now im in my bootloader and can't "oem unlock" -> command error!
*** RELOCKED ***
*** SECURITY WARNING ***
my device doesn't boot... PLZ HELP

@rizmdee
Run the 0.98 RUU now.

0.98 ruu? not 1.28 or 1.47?
EDIT: ah sry... doesnt work... error 131

@rizmdee
Yes 1.28 or 1.47
Yip, I told you, MAKE goldcard, remember?
Run the fastboot command "fastboot getvar all" remove yout imei from your post.
You will now have to make a coldcard on your PC (not sure if you can use another phone)
Check here, kashoulis post 11 and you can also check here

but the device is not branded... crappy...
ok ill take a look...
what does getvar all do?
crap: -> cidnum: O2___102

so i cant unlock my bootloader again?

@rizmdee
Yip, see the CID O2__102, means your phone is O2 branded.
I think, not sure though, you can try this RUU. I think, judging by its size/data its a 0.98 hboot (O2_UK_1.31.206.1), but I am pretty sure.
SO give that one a try, if that fails you WILL have to make a goldcard.

foX2delta said:
@rizmdee
Yip, see the CID O2__102, means your phone is O2 branded.
I think, not sure though, you can try this RUU. I think, judging by its size/data its a 0.98 hboot (O2_UK_1.31.206.1), but I am pretty sure.
SO give that one a try, if that fails you WILL have to make a goldcard.
Click to expand...
Click to collapse
Okay i used to "fastboot flash unlocktoken Unlock_code.bin again and now my device is *** UNLOCKED *** again... holy crap i thought i won't get it !
okay... the next time ill try it -> GOLDCARD FIRST!!! thanks a lot foX2delta...
it's just like: holy crap I wanna be s-off xD

I am still sure the above mentioned RUU will downgrade you.

first i need to calm down, my friend
but I still want an s-off-device so I'll try it out next time and post the results

I tried the RUU mentioned above several months ago, and it indeed works for O2-branded DS, which the OP obviously has.

Jack_R1 said:
I tried the RUU mentioned above several months ago, and it indeed works for O2-branded DS, which the OP obviously has.
Click to expand...
Click to collapse
so now u got s-off with that ruu?

Unable to re-unlock bootloader--HELP!

So I am ATT One X and was on Magnolia rom 1.82. I tried to upgrade to the latest RUU by re-locking the bootloader. Because I used the Rogers CID before to Unlock, I had to change the CID to SuperCID before upgrading.
After I changed from Rogers CID to SuperCID, relocked, upgraded to 1.85 RUU, I attempted to re-unlock via HTC-DEV. I went through all the steps and successfully received and unlock code and successfully flashed it.
HOWEVER!!!! The bootloader still says RELOCKED and I can't flash stuff.
I tried changing the CID back to ROGER001 and running the original unlock key but that failed to i went through HTCDEV with that CID and got the unlock code, successfully flashed it, but still had the RELOCKED bootloader.
Did I mess something up???? Please tell me i didn't....Any help is appreciated

b3nman said:
So I am ATT One X and was on Magnolia rom 1.82. I tried to upgrade to the latest RUU by re-locking the bootloader. Because I used the Rogers CID before to Unlock, I had to change the CID to SuperCID before upgrading.
After I changed from Rogers CID to SuperCID, relocked, upgraded to 1.85 RUU, I attempted to re-unlock via HTC-DEV. I went through all the steps and successfully received and unlock code and successfully flashed it.
HOWEVER!!!! The bootloader still says RELOCKED and I can't flash stuff.
I tried changing the CID back to ROGER001 and running the original unlock key but that failed to i went through HTCDEV with that CID and got the unlock code, successfully flashed it, but still had the RELOCKED bootloader.
Did I mess something up???? Please tell me i didn't....Any help is appreciated
Click to expand...
Click to collapse
Check for errors in the command prompt when you try to unlock. What does it say?

dimgl said:
Check for errors in the command prompt when you try to unlock. What does it say?
Click to expand...
Click to collapse
none whatsoever everything goes flawlessly. just when i reboot into the bootloader it says RELOCKED at the top.

Do you think its because i unlocked with the Rogers CID and then Re-unlocked with the Super CID?

I think some users reported having to attempt BL unlock multiple times on 1.85 before it worked. Pretty sure I read that on one of the bootloader unlock threads in Development (can't remember if it was the one-click SuperCID thread, or the "original" hex editor method thread).
Mine worked the first try on 1.85. I used the same bin file that unlocked 1.73.

redpoint73 said:
I think some users reported having to attempt BL unlock multiple times on 1.85 before it worked. Pretty sure I read that on one of the bootloader unlock threads in Development (can't remember if it was the one-click SuperCID thread, or the "original" hex editor method thread).
Mine worked the first try on 1.85. I used the same bin file that unlocked 1.73.
Click to expand...
Click to collapse
Thats the thing. I changed the CID from when i originally Unlocked it. Has anyone successfully done this?

SOLVED
I figured it out.
When you select power off or reset from the Power Menu, OR use the adb reboot command from command line, it doesn't really completely power off. So you have to actually hold the power button until it completely powers down and THEN start the bootloader for the the unlocked change to take effect. At least thats what happened with me. Your mileage may vary....

Make sure when you boot up to turn on usb debugging you also turn off fast boot (settings/power) its not the fast boot we're used to but its HTCs way of not completely powering off the phone to give a faster boot time. I personally had to run the unlock twice to get the bootloader to say unlocked instead of relocked.
Hope this helps.
Sent from my HTC One X using xda premium

Dear god, this thread should be a sticky. After 30 tries, I disable fastboot, power off completely using the power button and when I booted to the bootloader, it was unlocked.

Stuck at Hboot 2.00.0002 trying to s-on for warranty

Hi Guys,
I have S-on'd my device. Currently i'm stuck.
I have HBoot 2.00.0002
I can lock or unlock via HTCdev
But i cannot load any RUUs, All fail on custom ID error.
Tried changing versions makes no difference?
Help
thanks
p.s. anything i can do to give you more info?

yes, search and read there are 1000+ threads with the same problems.
If your bootloader is unlocked you need to locked it before flashing a RUU.
fastboot oem lock
Click to expand...
Click to collapse
post here your CID number and will try to recommend a RUU, or create a goldcard and you can flash any RUU

Thanks for the reply, Obviously i have read many many threads on this and spent over a day working on this before i posted asking for help.....
I have already locked bootloader and still all RUUs i have tried fail.
My CID number is 02______01

http://dl.xda-developers.com/attach...9420c269863/4fda5f8c/1/0/5/6/9/2/8/Cidnum.txt
Try to find your Cid in that link. Where are you from? Is your phone branded?
Eventually post your main version.
No matter what with a gold card you can flash any ruu with no problems.

supercid says 11111111 on 2.20 but cant unlock bootloader

i updated to 2.20 ruu and thank god i already had supercid set to 11111111.but now when i try to unlock bootloader from htcdev,it doesn't stick.please help

saketh91 said:
i updated to 2.20 ruu and thank god i already had supercid set to 11111111.but now when i try to unlock bootloader from htcdev,it doesn't stick.please help
Click to expand...
Click to collapse
very simple to fix. The fact that you got to the "ready to unlock?" screen means the unlock token works.
go into settings on the phone go to power. Turn OFF fastboot.
Power off the phone completely.
Boot to bootloader
send the unlock.bin again
this time it will stick.

saketh91 said:
i updated to 2.20 ruu and thank god i already had supercid set to 11111111.but now when i try to unlock bootloader from htcdev,it doesn't stick.please help
Click to expand...
Click to collapse
Sometimes the phone can get confused about its locked state.
To fix:
-Force reboot the phone. Hold the power button for 10+ seconds until bottom lights flash and then stop.
-Boot in to bootloader
Now force the phone to lock even if you think it is locked already.
-fastboot oem lock
-fastboot flash unlocktoken Unlock_code.bin
Sending "fastboot oem lock" tends to get the phone back on the right track so it doesn't just keep rebooting in to a relocked state.

get into bootloader manually volume down + power.

Wow, so I've been under the impression that if I updated to 2.20 via the RUU that I couldn't do anything. I know my supercid is definitely 11111111. I can still unlock the bootloader if this is the situation? Root wouldn't happen though right?

Ethere said:
Wow, so I've been under the impression that if I updated to 2.20 via the RUU that I couldn't do anything. I know my supercid is definitely 11111111. I can still unlock the bootloader if this is the situation? Root wouldn't happen though right?
Click to expand...
Click to collapse
yes root will happen.
unlock bootloader. Install twrp recovery. Flash the root package found here http://forum.xda-developers.com/showthread.php?t=1673935

Thanks so much gunny. One quick question. I got the bootloader unlocked without a problem. Now, twrp recovery...can I just do that through GooManager, or should I do it another way?

Ethere said:
Thanks so much gunny. One quick question. I got the bootloader unlocked without a problem. Now, twrp recovery...can I just do that through GooManager, or should I do it another way?
Click to expand...
Click to collapse
I think you may have to use fastboot flash recovery recovery.img because of the new limitations of the new HBOOT. It might be only for boot.imgs though

That worked rohan32 Thanks so much to both of you. Now I have an unlocked bootloader and TWRP installed. Going for root now. Thank you thank you thank you! You guys have saved me from wanting another phone!
[EDIT]Rooted as well. Again, thank you both so much!

thanks everyone i solved my problem.dint except quick replies from you guys.

Ethere said:
Wow, so I've been under the impression that if I updated to 2.20 via the RUU that I couldn't do anything. I know my supercid is definitely 11111111. I can still unlock the bootloader if this is the situation? Root wouldn't happen though right?
Click to expand...
Click to collapse
If you stay away from the AT&T cid you will be fine.
In theory things could change but at the moment so long as you have super cid prior to RUU flashing you will be fine.

OK I just got my AT&T HOX today and from what I've read hear there is no way to root it? Since I have 2.20.502.7 710RD but if I use super cid I can flash roms?

Without root you can't get super Cid

Please update the title and add "Resolved"
Sent from my HTC One XL using xda premium