Database Info

[Q] S-Off not possible because of "Error 131" - doesn't matter which RUU

Hi guys,
I am new here, so maybe I missed something.
Anyway, I followed the tutorial step-by-step to unlock my HTC Desire S which I got today (so it has a 2.x bootloader) like stated here:
http://forum.xda-developers.com/showthread.php?t=1443636
But I can't seem to install any RUU cause of "Error 131", as told in the tutorial, I must use the RUU for my specific region.
So, my Region is Germany and my phone is from o2.
So first I used
RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed.exe
Click to expand...
Click to collapse
because Germany is in Europe. And the only GER RUU is from "TMO" which may mean "T-Mobile" I guess. But it didn't work.
Next I thought "**** that ****" and I tried to flash (after repeating all tutorial steps):
RUU_Saga_TMO_DE_1.30.111.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_178580_signed.exe
Click to expand...
Click to collapse
But it still shows up "Error 131"... so now I am depressed. Can anyone tell me what I am doing wrong?
Thank you very much

Samwan said:
Hi guys,
I am new here, so maybe I missed something.
Anyway, I followed the tutorial step-by-step to unlock my HTC Desire S which I got today (so it has a 2.x bootloader) like stated here:
http://forum.xda-developers.com/showthread.php?t=1443636
But I can't seem to install any RUU cause of "Error 131", as told in the tutorial, I must use the RUU for my specific region.
So, my Region is Germany and my phone is from o2.
So first I used
because Germany is in Europe. And the only GER RUU is from "TMO" which may mean "T-Mobile" I guess. But it didn't work.
Next I thought "**** that ****" and I tried to flash (after repeating all tutorial steps):
But it still shows up "Error 131"... so now I am depressed. Can anyone tell me what I am doing wrong?
Thank you very much
Click to expand...
Click to collapse
Hi there,
You need to flash the RUU that is supported by your phone's version.
Turn the phone into fastboot mode (voldown + power), click fastboot, wait till it shows fastboot usb.
Open console in PC and find the android tools, type:
<androidtool dir>\ fastboot getvar all
It should come up as: INFOversion etc.
What you need to look for is INFOversion-main and INFOcidnum
Go to http://forum.xda-developers.com/showthread.php?t=1002506
and download the RUU that matches!
If you've S-OFF'd the phone with Revolutionary, then RUU will have some problems with overwriting the bootloader, follow this guide to re S-ON.
http://forum.xda-developers.com/showthread.php?t=1187231

anchemis said:
If you've S-OFF'd the phone with Revolutionary, then RUU will have some problems with overwriting the bootloader, follow this guide to re S-ON.
http://forum.xda-developers.com/showthread.php?t=1187231
Click to expand...
Click to collapse
Very helpful reply buddy.
But i don't think the last line applies to him. He said he just got the phone, and it had the v2.xxx hboot to begin with, so he went looking to downgrade. If he had acheived S-off, he wouldn't be asking how to S-off in the first place.
@OP : You should try using a Goldcard when faced with a difficult choice of Region-specific RUUs. Try making one (Use Search function) and then re-running the European RUU. (You may also have to check your Misc_version to ensure compatibility, or you may hit a roadblock again.

Hi,
I just wanted to confirm for further searches / use that what has been stated inside the first answer is fully working.
I got my Desire S downgraded, S-OFFed and was able to flash MIUI, so it's finding it's way to my girlfriend as birthday present soon thank you for helping.

Do I need a new mobile?

Do I need a new mobile? A question that I often imagine in the last days... What's the situation?
Here are the base informations of my HTC One S:
Original CID: O2___102
Actual CID: 11111111
Boootloader informations:
VLE PVT SHIP S-ON RL
HBOOT-2.13.0000
RADIO-1.11.50.05.28
OpenDSP-v31.1.0.45.0815
eMMC-boot
Nov 20 2012, 15, 15:44:01:-1
The story
What happens. Because of the license mess with CyanogenMod I've tried different ROM's but all in all there where always a reason to change the ROM. After all I want to give Carbon a try but for this you have to upgrade the firmware and so the mess starts.
In fact o2 Germany is not able to deliver a proper RUU I've changed the CID to SuperCID (11111111) and tried to install the RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4. This and all my other installations of different RUU's breaks with a signature error. Next step was to change the CID to HTC__102 but this didn't help anything.
Now I was thinking to go back to the root and install the first custom ROM I've used. So I want to give ViperROM a try. With this it was not able to get the WiFi up and running. Next step was to give TrickDroid 10 and ZenROM a chance. There was no problem with the installation and both of them where running. The problems here are that both of them are far away from a daily driver.
Today I saw that there are again official CyanogenMod nightlies and so I've thought to install the base ROM of so many custom ROM's. This installation breaks with the error message: "failed : getprop("ro.bootloader") == 2.15.000" So It seems that the newest bootloader is a basic requirement. The problem is now that I'm unable to get the newest hboot because of the RUU signature problem.
I don't know what to do anymore. RUU update does not working. S-OFF does not working. The firmware upgrade is not working. Do I have to use the One S as a paperweight?
So .. I'm really grateful and happy about every hint, every tip or solution.
Thanks a lot
Christian

Why is S-OFF not working and why did you changed your CID back to stock? You have to get S-OFF and SuperCID so follow this guide. Report back at which step you fail

Uwe303 said:
Why is S-OFF not working and why did you changed your CID back to stock? You have to get S-OFF and SuperCID so follow this guide. Report back at which step you fail
Click to expand...
Click to collapse
Good morning,
sorry for my late response. I was so frustrated that I went off yesterday evening.
I've tried different things with the CID:
changed the O2___102 to 11111111
changed the 11111111 to HTC__102
rollback to 11111111
The reason was that I had found the RUU instructions which stated that there could be potential problems with RUU installations and SuperCID.
Based on this thread the S-Off always stops at step 5. I get an error message that says: "FAILED (remote: 99 unknown fail)". I've already tried the different things. Switch off the phone, switch off the computer, useing the original HTC USB cable and so on. Nothing worked here.
Thanks a lot
Christian

Try updating the HTC drivers on your PC then try again. There's a thread somewhere around the One S forums.

After the soff, supercid is not needed anymore.
Have you tried o2 ruus from a different country?
Btw is the ruu erroring because of your MID? Whats yours? Pj4010000?
Sometimes if a ruu errors, directly retrying sometimes works.
Verstuurd van mijn HTC One S met Tapatalk

YES! It's again up and running
After some days of troubleshooting my One S ist up and running again
First was the tip of djsubtronic. I've checked the drivers on my PC. But I've already installed the latest one. Then I've made a clean, fresh new installation on my notebook. But nothing changed.
Then I've tried some other RUU's. But there where always the same error. So... after all I was already looking for a new mobile device and then I've made ​​a final attempt.
Cleaned storage from bootloader
Reset from bootloader
Installed TWRP recovery (2.5.0.0)
Format the sdcard from Windows
Nothing left on the sdcard
System reset from TWRP
System wipe from TWRP
Followed step by step and extreme exactly the instructions of the firmware update thread
The second try to manual update the hboot then was succsessful
After that I was able to install the latest CyanogenMod nightly
Thanks a lot for every tip. They took me to re-read everything again and then start again from scratch. After all I'm already S-On. I'm happy that my phone is running again, I just do not quite trust myself to tackle the topic...
Thanks again...
Christian

Nice to hear you have your phone up and running again.
I want to ask something.
I too, don't have JB RUU for my carrier of the device.
So will S-off and subsequently changing CID to something which has an RUU help? Will that RUU work?
My basic purpose is to go fully stock.
Sent from my Nexus 7 using Tapatalk HD

khan.orak said:
Nice to hear you have your phone up and running again.
I want to ask something.
I too, don't have JB RUU for my carrier of the device.
So will S-off and subsequently changing CID to something which has an RUU help? Will that RUU work?
My basic purpose is to go fully stock.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Hi, if I understand this correct than yes. If you change the CID to a "non branded" CID. (SuperCID - 111111 or HTC - HTC__102) you should be able to install other RUU's for your device. I don't know why this didn't work for me but for normal this should work.
Christian

chmarx said:
Hi, if I understand this correct than yes. If you change the CID to a "non branded" CID. (SuperCID - 111111 or HTC - HTC__102) you should be able to install other RUU's for your device. I don't know why this didn't work for me but for normal this should work.
Christian
Click to expand...
Click to collapse
From what i have read and understood, yours must be a problem of MID. This is another requirement in addition to CID.
Sent from my Nexus 7 using Tapatalk HD

[q] problem with s-off

So yea... Have a sensation tied to "3" UK provider. So i thought i just take it, unlock it, put 4eXT into it, flash something else and done... Well... NOT... It didn't worked out. Just later i imagined that it needs s-off too which requires "Juopunutbear" which requires stock rooted rom in the phone which is working... so now i am not able to flash anything which works because i tried to do this already with a device not being prepared and when i am trying to put in to it an original RUU it does not work too because probably i can't downgrade without s-off and it says that i am "upgrading" from 3.32 to 1.34 and after an attempt and failure it gives the advice to find a proper update suite or smth.
only one ruu i found found for my CID was RUU Pyramid H3G UK 1.34.771.1 R Radio 10.43a.9007.00U 10.51.9007.27 M3 release 197065 signed.exe
what do i do now?
any advice apriciated!

check the guide "flashing roms with SOn" by asskickar in sensation general section ..and follow the steps carefully and flash the rom (particularly check step #2 and step #3 ..if those two failed check extra step #1)

cant unlock at&t htc one x bootloader

Hi everybody first of all excelent website...
I never had problems but when happens I look all over ethe Google or sea developers but this time I realy can't seem to get it done.
Moving from Samsung galaxy to HTC one x I can't unlock bootloader in order to flash a recovery and a Rom
I have try several tut but nnothing dosent change CID to unlock trought htcdev or the one click method or all one kit
And yes I search in all xda I like I say I don't get it right
Can someone help me, my info is:
Hboot 2.14
Android 4.1.1
Firmware version 3.18
At&t HTC one x
Thanks to everybody

Darkpikasso said:
Hi everybody first of all excelent website...
I never had problems but when happens I look all over ethe Google or sea developers but this time I realy can't seem to get it done.
Moving from Samsung galaxy to HTC one x I can't unlock bootloader in order to flash a recovery and a Rom
I have try several tut but nnothing dosent change CID to unlock trought htcdev or the one click method or all one kit
And yes I search in all xda I like I say I don't get it right
Can someone help me, my info is:
Hboot 2.14
Android 4.1.1
Firmware version 3.18
At&t HTC one x
Thanks to everybody
Click to expand...
Click to collapse
There is a thread HTC one x noobs u check that I hvnt searched enough unlocking is a simple process and it's all over the xda
Here is the url
http://forum.xda-developers.com/showthread.php?t=2567916
Or just search root method for 3.18 HTC one x
Sent from my HTC One X using XDA Premium 4 mobile app

It's an at&t phone, the at&t CID is blocked by htcdev so you need to get SuperCID before being able to unlock the bootloader. Click the Everything Evita link in my signature and bookmark that thread, it's a resource thread that contains everything you'll ever need. Once you're in that thread navigate to the root section and find the 3.18 root method, this is the only method that'll work with your current firmware. Follow the instructions in that thread and then you can unlock your bootloader.
Once you have an unlocked bootloader you can install TWRP recovery which will allow you to root your stock ROM or install custom ROMs. If you need instructions on this click the How-To Guide For Beginners link in my signature, it's a thread I put together detailing some basic operations. If you have any questions feel free to ask in my Noob Friendly Q&A + General Help thread.
Sent from my One X using Tapatalk

You need to use the correct root method that corresponds to your firmware version in order to change your CID. Trying other methods you randomly Google around for is not going to work.
Use my Index thread, look under "ROOT" and find the method that matches your firmware number (3.18).
http://forum.xda-developers.com/showthread.php?t=1671237
There is not one-click method that works for firmware 3.18. Trying methods that don't match your firmware number is a waste of time.
Also, when asking for help, you need to be absolutely specific as to what you have tried, and what you haven't (including the result such as error messages, etc). If you don't give us specifics, it makes it even harder for us to help you.
Hasoon2000's all-in-one toolkit should work on 3.18. But if this is the one you tried, you haven't told us what happens when you try to use it.

To make it easier, here's the link to the 3.18 root method:
http://forum.xda-developers.com/showthread.php?t=2285086
You'll still want to bookmark the Everything Evita thread linked in my signature.
Sent from my One X using Tapatalk

Thank you everybody
When I try the all in one kit gave the error of waiting for the device, updated the adv drivers and still dosent show the CID change
In htcdev give me the MID not allowed error
In most cases, all in one method, Jose method, motoXchopper method dosent seems to work what I'm going to try is to uninstall all the drivers for HTC one x and install again

Darkpikasso said:
In most cases, all in one method, Jose method, motoXchopper method dosent seems to work what I'm going to try is to uninstall all the drivers for HTC one x and install again
Click to expand...
Click to collapse
What the heck is "Jose method"? Again, I think your are fumbling around with methods that aren't even intended for your device or firmware version.
Do you have a working adb environment? What is the response if you use the command:
adb devices

ruffain said:
There is a thread HTC one x noobs u check that I hvnt searched enough unlocking is a simple process and it's all over the xda
Here is the url
http://forum.xda-developers.com/showthread.php?t=2567916
Or just search root method for 3.18 HTC one x
Sent from my HTC One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Come on, you of all people shouldn't be giving attitude to this guy telling him he hasn't searched enough. You've asked me multiple questions that could have been answered if you had searched for the answer, including how to unlock your bootloader, that's kinda like the pot calling the kettle black.
It's easy for you to say unlocking the bootloader is an easy process once you've done it. The fact is that it isn't that simple for someone who is unaware that there are different methods for different firmware versions.
Sent from my One X using Tapatalk

redpoint73 said:
What the heck is "Jose method"? Again, I think your are fumbling around with methods that aren't even intended for your device or firmware version.
Do you have a working adb environment? What is the response if you use the command:
adb devices
Click to expand...
Click to collapse
Thank you for all the responses
The error that gives me still is the same mid not allowed
Still having problems, but someone told me that it is first to root and then change the CID to superCID 1111111 and then run a all in one program to unlock
Is it thruth?

You've been told quite a few times now that you can't unlock your bootloader until you have SuperCID. You need to use the 3.18 root method that I linked you to a few posts ago. Forget about the toolkits, just go to that thread and follow the instructions.
Sent from my Evita

Darkpikasso said:
Thank you for all the responses
The error that gives me still is the same mid not allowed
Still having problems, but someone told me that it is first to root and then change the CID to superCID 1111111 and then run a all in one program to unlock
Is it thruth?
Click to expand...
Click to collapse
Ok I had the same issue several months ago. I have AT&t One x as well. I noticed I could unlock the bootloader and S-OFF when my phone was carrier unlocked. I used the roadrunner method I believe (it's been awhile). I am certain Timaaaa knows what he is saying, but if you can't find a solution, that may be your other answer as well. Worked for me.

Roadrunner? I don't think such a method exists for this device. You can't get s-off without root, you can't get root without an unlocked bootloader, you can get an unlocked bootloader without SuperCID, the only way to get SuperCID on his firmware is to use the 3.18 root method. Hence the reason that's been stated over and over again in this thread. It's the only solution. Carrier unlocking has absolutely nothing to do with the bootloader unlock / root process.
Sent from my Evita

timmaaa said:
You've been told quite a few times now that you can't unlock your bootloader until you have SuperCID. You need to use the 3.18 root method that I linked you to a few posts ago. Forget about the toolkits, just go to that thread and follow the instructions.
Sent from my Evita
Click to expand...
Click to collapse
Got it, first root and then unlock
Keep you update and thanks a lot for the help

No, SuperCID, unlock, custom recovery, root.
Sent from my Evita

timmaaa said:
No, SuperCID, unlock, custom recovery, root.
Sent from my Evita
Click to expand...
Click to collapse
Thanks everybody for the help but I can't get superCID
The htc dosent let him write and all the exploits to change it ether dosent find the device or dosent allow to write the commands
I really don't know what is the problem
I already install new drivers uninstall the ones from Samsung that I had and nothing
Not even my phone has the option to put it in charge only it has various opcitions but none of them are charge only

What do you mean by "all the exploits"? Which exploits have you tried? Did you try the 3.18 root method I gave you the link to?
Sent from my Evita

lemonfugu said:
Ok I had the same issue several months ago. I have AT&t One x as well. I noticed I could unlock the bootloader and S-OFF when my phone was carrier unlocked. I used the roadrunner method I believe (it's been awhile). I am certain Timaaaa knows what he is saying, but if you can't find a solution, that may be your other answer as well. Worked for me.
Click to expand...
Click to collapse
I got it....
I uninstall the drivers and install again there's were got the connection and unlocked but it says TEMPERED
Is that ok? Later in the afternoon I'm going to install custom recovery s-off and root

Yeah that's totally normal. I'd suggest you have a look at my How-To Guide For Beginners thread (link in my signature), it has some good instructions on your next steps.
Sent from my Evita

timmaaa said:
Roadrunner? I don't think such a method exists for this device.
Click to expand...
Click to collapse
Probably is referring to the Rumrunner s-off method. And yes, carrier (SIM) unlock has nothing to do with bootloader unlock and/or s-off. Probably just a coincidence that that person was able to bootloader unlock after doing SIM unlock.

Thank you very much for the help now I have it everydone unlock, custom recovery, root and s-off.
I was having problems with faceoff to s-off but nothing big
I already have install viperxl with beastmode kernel
Sent from my HTC One X using xda app-developers app

[Completed] [Q] A little help upgrading hboot - HOX

So I'm a first time flasher and i've done my thorough reading and research.
I have an at&t HTC one X, but i'm using it in India.
I was flashing it to CM11 Snapshot, for which i have unlocked bootloader from HTCdev, i already had S-Off and CID-11111111 (no idea why... and can someone explain what is supercid btw ?)
Also installed twrp and its inbuilt supersu. I verified full root access with root checker.
Right when i was ready to finally flash the CM11, i get an error message saying that i have hboot 1.14 and that i need a higher one (1.19 i think... dont remember)
Ive checked for the solution, it seems that i need to install the 3.18 RUU to update hboot to 2.14. However, its not available on the following link, So i guess i shud get the next available RUU, which is 5.18.
(http://forum.xda-developers.com/showthread.php?t=2119610)
I also read that i cant root 5.18, unless im already rooted. So i dont have to worry about this right ? (http://forum.xda-developers.com/showthread.php?t=1952038&page=58)
2 questions here,
Will it matter if i get 5.18 instead of 3.18 ? Plus, the 5.18 ruu is an exe file, not zip... is the flashing procedure different ?
I dont want to update the entire RUU, i just want to update my hboot. Is it possible ? If yes, how ?
I read that rooting is different for 3.18 than my current 2.20 firmware. I dont understand that either :/
( http://forum.xda-developers.com/showthread.php?t=1671237 )
And i need to toggle my bootlock ?
( http://forum.cyanogenmod.org/topic/74576-only-support-214-hboot/ )
Thats probably a lot of questions. But im really trying to understand this right. Basically what i wanna know is, what exactly do i do next to simply update my hboot safely, and then cm11.

zain910128 said:
So I'm a first time flasher and i've done my thorough reading and research.
I have an at&t HTC one X, but i'm using it in India.
I was flashing it to CM11 Snapshot, for which i have unlocked bootloader from HTCdev, i already had S-Off and CID-11111111 (no idea why... and can someone explain what is supercid btw ?)
Also installed twrp and its inbuilt supersu. I verified full root access with root checker.
Right when i was ready to finally flash the CM11, i get an error message saying that i have hboot 1.14 and that i need a higher one (1.19 i think... dont remember)
Ive checked for the solution, it seems that i need to install the 3.18 RUU to update hboot to 2.14. However, its not available on the following link, So i guess i shud get the next available RUU, which is 5.18.
(http://forum.xda-developers.com/showthread.php?t=2119610)
I also read that i cant root 5.18, unless im already rooted. So i dont have to worry about this right ? (http://forum.xda-developers.com/showthread.php?t=1952038&page=58)
2 questions here,
Will it matter if i get 5.18 instead of 3.18 ? Plus, the 5.18 ruu is an exe file, not zip... is the flashing procedure different ?
I dont want to update the entire RUU, i just want to update my hboot. Is it possible ? If yes, how ?
I read that rooting is different for 3.18 than my current 2.20 firmware. I dont understand that either :/
( http://forum.xda-developers.com/showthread.php?t=1671237 )
And i need to toggle my bootlock ?
( http://forum.cyanogenmod.org/topic/74576-only-support-214-hboot/ )
Thats probably a lot of questions. But im really trying to understand this right. Basically what i wanna know is, what exactly do i do next to simply update my hboot safely, and then cm11.
Click to expand...
Click to collapse
First of all, I'm not familiar with your device.
As you found already the specific forum for your device, please ask in the AT&T, Rogers HTC One X, Telstra One XL > One X Q&A, Help & Troubleshooting > [Q&A]{Evita/One XL} Noob Friendly Q&A + General Help - Ask Any Question! thread.
There you will surely get quick and proper help.

Thread closed and thank you.