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.

[Q] One S Dev Phone with root issues

So I bought a One S from craigslist about 2 weeks ago. The guy said it was a dev phone. At the top on the case is a tag of numbers and letters printed on the phone. When I first boot the phone it has a HTC splash screen along with the text
"This build is for development purposes only. Do not distribute outside of HTC without HTC's permission. Failure to comply may lead to legal action."
Booting into the bootloader I get this:
*** LOCKED ***
VLE XC SHIP S-OFF RH
CID-11111111
HBOOT-0.90.0000
RADIO-0.14.31.22_2
OpenDSP-v10.1.0.31.0221
eMMC-boot
Feb 21 2012,14:27:31
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
CLEAR STORAGE
SIMLOCK
IMAGE CRC
SHOW BARCODE
Also it came with CWM 5.8.1.5 already installed. I tried to use Hasoon's tool to install a more recent CWM but it wouldn't work.
I tried to unlock the bootloader using the htcdev site and token and that didn't work.
I was able to flash it with the UTB ROM using the existing CWM and it works but I cannot gain root access even though supersu is installed and I add apps to its list.
Any ideas on how to get root access?

Looking at your HBOOT version it seems like the device is on early software. You're already S-OFF, so you can try flashing the official TMO release ROM and follow the guides on XDA to root.

hammondnav said:
Looking at your HBOOT version it seems like the device is on early software. You're already S-OFF, so you can try flashing the official TMO release ROM and follow the guides on XDA to root.
Click to expand...
Click to collapse
I don't see the official release. There is a thread here that says T-Mobile USA Complete Rom but there's no link to the actual ROM.

I thought reselling of these phones can land u into trouble ?
I mean the development phones

what about busybox? there's an app to install that if you don't have it
Sent from my Kindle Fire using xda premium

dude thats awesome
post us some pictures of the phone and the HBOOT menu
If you are S-OFF and supercid, the possibilities are endless... flash an ruu, that should bring you upto date with the latest firmware and software..

azzledazzle said:
dude thats awesome
post us some pictures of the phone and the HBOOT menu
If you are S-OFF and supercid, the possibilities are endless... flash an ruu, that should bring you upto date with the latest firmware and software..
Click to expand...
Click to collapse
it wont let me post my photo album because i am still new so i am pm'ing you the link. what are some things i can do with this phone? i'm still a noob but a quick learner. so far i've only flashed a couple of roms. currently using black dragon's. still haven't gotten root access though.

dannyy2200 said:
it wont let me post my photo album because i am still new so i am pm'ing you the link. what are some things i can do with this phone? i'm still a noob but a quick learner. so far i've only flashed a couple of roms. currently using black dragon's. still haven't gotten root access though.
Click to expand...
Click to collapse
You could talk to the devs in the development section (as soon as you have your 10 posts) und help them to get s-off with providing informations maybe.

yeah man that would be a great idea, PM some and see if you can help them as for getting the bootloader unlocked, Unless HTCdev isnt working, there isnt much else yet.
why does it not work ? what errors does it give ?

hmm seems that I'm lacking some knowledge ^^
Is there any necessesity for unlocking the bootlaoder if the device already has s-off? Thouht that s-off would mean no security and full system access.

S-OFF means the NAND partition is writeable, When its S-ON this partition is locked (Security ON ), so with S-OFF we can customise even further, Flashing Radio.IMGs and lots more,
With unlocked bootloader we can do things like install a recovery and flash Root.
the perfect scenario would to have S-OFF AND Unlocked Bootloader.

azzledazzle said:
S-OFF means the NAND partition is writeable, When its S-ON this partition is locked (Security ON ), so with S-OFF we can customise even further, Flashing Radio.IMGs and lots more,
With unlocked bootloader we can do things like install a recovery and flash Root.
the perfect scenario would to have S-OFF AND Unlocked Bootloader.
Click to expand...
Click to collapse
Ah alright, I thought S-OFF would already allow to flash root.

nope usually when using an S-OFF tool, such as revolutionary, It will unlock bootloader at the same time..
surely theres someone out there can can do something really awesome with this developer phone !!

azzledazzle said:
yeah man that would be a great idea, PM some and see if you can help them as for getting the bootloader unlocked, Unless HTCdev isnt working, there isnt much else yet.
why does it not work ? what errors does it give ?
Click to expand...
Click to collapse
well it doesn't give me any errors, and says unlock successful, and just acts as if it went ahead and unlocked, but when i boot into the loader it still says locked. weird.

hmmmm..
maybe theres a command you can use in adb ? Im not sure..
I know the command to relock is ''fastboot oem lock'' maybe ''fastboot oem unlock'' might do something lol.
i have no idea as with most things in my life

[Q] Can't s-off my desire S !!!

hi,
first , I dont speak english, so I'm trying little bit and I will use google transalte a lot of time (speak french if somebody do it !)
I can't do mu desire s in s-off, cause the version of hboot is : 2.00.0002
I've tried this solution http://forum.xda-developers.com/showthread.php?t=1443636 but when i'm trying to install rom I have a message error 155 and bad ID (not seems regions !), and I've try to do it with htc supetools and no result !
My phone is root , and unlocked bootloader, an i install 4extrecovery
but since 3 day I'm trying to do it S-off and I can't
is there somebody to help me please ?
Thanks

octopus82 said:
hi,
first , I dont speak english, so I'm trying little bit and I will use google transalte a lot of time (speak french if somebody do it !)
I can't do mu desire s in s-off, cause the version of hboot is : 2.00.0002
I've tried this solution http://forum.xda-developers.com/showthread.php?t=1443636 but when i'm trying to install rom I have a message error 155 and bad ID (not seems regions !), and I've try to do it with htc supetools and no result !
My phone is root , and unlocked bootloader, an i install 4extrecovery
but since 3 day I'm trying to do it S-off and I can't
is there somebody to help me please ?
Thanks
Click to expand...
Click to collapse
Try this one: http://forum.xda-developers.com/showthread.php?t=1604255 >>> This will downgrade your hboot to 0.98.XXXX, read through replies they simplify the steps further.
Then follow this guide: http://www.youtube.com/watch?v=kvg0i8in96M >>> to S-OFF your phone via revolutionary.
It helped me S-OFF my phone. I have same problem like you days ago, i was S-ON, hboot unlocked, rooted and hboot 2.00.0002. Now I'm S-OFF and permanently rooted. Hope this helps!

If I'm not mistaken (and most likely I'm not), you can't downgrade a phone without locking the bootloader first. So you need to lock the bootloader and flash RUU - and you're not using the correct guide for it. You need to do some steps that aren't in the guide.

Jack_R1 said:
If I'm not mistaken (and most likely I'm not), you can't downgrade a phone without locking the bootloader first. So you need to lock the bootloader and flash RUU - and you're not using the correct guide for it. You need to do some steps that aren't in the guide.
Click to expand...
Click to collapse
Correct, but that's after you change your misc version, which is in the guide. Locking the bootloader is part of the steps, so no worries there, RUU's are also there, I think there's one from his region so no problem. Take it from me, I started from S-ON, rooted (temp i think), boot unlocked and hboot 2.00.0002 and the guide is noob fail-safe, given you researched enough to know what you're doing, and you just do what it tells you. You'll do the deed right.

Sorry, I was replying to the OP, but you posted before me so it looks like I'm replying to you instead. I meant the guide he mentioned in his OP, not your guide.

bods11 said:
Try this one: http://forum.xda-developers.com/showthread.php?t=1604255 >>> This will downgrade your hboot to 0.98.XXXX, read through replies they simplify the steps further.
Click to expand...
Click to collapse
Thank's
I tried this, but the last step does not work with me, I can not bring the command line because cmd does not detect my phone when it is in bootloader, or maybe I'm wrong to maneuver?
Code:
then type in command prompt.
- fastboot oem lock
P.S: the bootloader is unlock with htcdev.com

bods11 said:
RUU's are also there, I think there's one from his region so no problem.
Click to expand...
Click to collapse
What do you mean by "region": is the region where I live, or that or the phone was for its manufacture? if this is the second time how to recognize the region because I have not bought new?
thank's

Before starting with everything, turn on USB Debugging (settings>developer options) and turn off Fast boot (settings>Power) in your phone.
You installed HTC sync in your PC right? If not, first download and install HTC Sync (from here www(dot)htc(dot)com/sea/help/htc-desire-s/#download), you need the drivers from HTC sync, so your pc can recognize your phone.
Make sure you rebooted to bootloader. Then enter:
- fastboot oem lock >>> this is to "relocked" your phone so you can proceed to installation of the RUU.
First and foremost, is your phone branded? If yes, then choose the right RUU for you. If no, you can use the unbranded RUU. Or you can search the forum for your specific region, I think Europe RUU is ok. "Region" is your area, where you live and use your phone. Im from south east asia, so i used asia RUU. Also take note of Post #5 of the first guide, he has summarized everything and i believe he's in the same region as you. Read through everything before starting.

bods11 said:
Before starting with everything, turn on USB Debugging (settings>developer options) and turn off Fast boot (settings>Power) in your phone.
You installed HTC sync in your PC right? If not, first download and install HTC Sync (from here www(dot)htc(dot)com/sea/help/htc-desire-s/#download), you need the drivers from HTC sync, so your pc can recognize your phone.
Make sure you rebooted to bootloader. Then enter:
- fastboot oem lock >>> this is to "relocked" your phone so you can proceed to installation of the RUU.
First and foremost, is your phone branded? If yes, then choose the right RUU for you. If no, you can use the unbranded RUU. Or you can search the forum for your specific region, I think Europe RUU is ok. "Region" is your area, where you live and use your phone. Im from south east asia, so i used asia RUU. Also take note of Post #5 of the first guide, he has summarized everything and i believe he's in the same region as you. Read through everything before starting.
Click to expand...
Click to collapse
I relocked bootloader, maked a gold card, tried to install rom with fastboot usb and normaly, then the message error turn to ERROR [131]: ERROR CUSTOMER ID, before it was ERROR [155]: ERROR IMAGE
what can t do now ?
thanks

You flashed the wrong ROM for your CID, and the goldcard isn't correct.

Jack_R1 said:
You flashed the wrong ROM for your CID, and the goldcard isn't correct.
Click to expand...
Click to collapse
GOD IS GREAT GOD IS GREAT GOD IS GREAT
Thursday night is that I try to put it into s-off and to change the rom and the problem was the wrong way to do a Goldcard (I did it with goldcardtool)
here is the good way to do a goldcard
http://androidforums.com/desire-s-all-things-root/500543-guide-how-create-goldcard.html
I found it through dan fish in this topic
http://forum.xda-developers.com/showthread.php?p=27529821
Thank you so much dan fish and everybody who who tried to help me !

and now it's S-off with revolutionnary !

[Q] AT&T HTC ONE XL custom rom & recovery installed on locked phone

Hello everyone.
I am new to this part of the forum for i just received a somewhat non working AT&T HTC ONE XL from a friend.
I presume he did not read much into his issue at the time and messed up this phone one way or the other.
Basically the phone works, just not as a phone.
So i will take my time to explain the whole situation with as much detail as possible.
I am personally familiar with rooting, setting up recovery and installing custom roms on android phones (just not on this model yet).
The phone details in its current state are:
- android version 4.0.4
- htc sense version 4.0
- software number cleanrom 4.5 beta2
- htc extension version htcextension_403_1_ga_20
- kernel 3.0.8-01564-gdc95f45
- baseband 0.16.32.09.01_3_10.79.32.08L
As soon as i received the phone, i contacted at&t to ask for an unlocking code, they gladly oblige.
I insert the new SIM card (non AT&T) and the phone asks me to insert the code. After correctly inserting it, the phone accepts the code and proceeds to reboot. After the reboot i get the phone locked screen again and asks me for the code one more time.
At this point i start searching online for the official firmware from htc for this specific model and find the 4.2.2 version and proceed to install it according to their requirements and steps (in manual mode from a desktop pc since the rom installed doesn't have the update feature).
The process gets locked at a point and cannot proceed further.
Phone boots normally again and i decide to do a factory reset. This i when i notice a teamwin custom recovery was installed which is what is blocking the official rom installation.
So at this point i am open for ideas.
I'm positive the issue is not very hard to solve but i also know that i am missing the original recovery. I can only guess no official updates were installed so the phone was running the original 4.0.4 version.
Meanwhile i will be scouting this forum on how this phone exactly works for i understood that there were two forms of recoveries for it (one full and one partial).
I still don't know the recovery version, if it's good, how to access it (different combinations of volume and power pressing didn't work for me).
Finally your opinion on how to make the phone unlocking code work, as in would i need to go back to official, or would a custom different rom work as a solution.
Wish you guys a good day and awaiting your feedback.
Cheers.

Need more info. Boot into bootloader by holding down both the volume down rocker and the power button. After the power button is held for a few seconds, you should see the capacitive buttons flash a few times, and the phone will reboot. Let go of the power button, but DO NOT let go of the volume down rocker until the while hboot screen comes up. When you see the hboot screen, tell us what it says.
In particular, we need to know if it says s-off or s-on, if it says CID 11111111, and hboot version. Also, if it says LOCKED, UNLOCKED, or RELOCKED.
Official RUU will not run if the bootloader is UNLOCKED (needs to be RELOCKED or LOCKED). But be aware, if the phone is superCID and s-on, running a Jellybean RUU or OTA will brick the phone. Which is one of the reasons we need the bootloader info.
RUU does not need to have stock recovery to run, only OTA does. My guess is your bootloader is unlocked, or its the wrong RUU. Any error message when the RUU fails (if so, what does it say)?

Hi, thank you for your quick reply.
I'm going to write down all that is written in the recovery for i still don't understand what locked or unlocked means, s-on or s-off.
anyway, here goes:
tampered
unlocked
evita pvt ship s-on rl
hboot-1.09.0000
radio-0.16.32.09.01_3
opendsp-v25.1.0.32.0405
emmc-boot
i can't find anything related to cid and i'm still not used to this recovery just yet. wouldn't want to press anything just yet.
i hope i gave enough info and i guess it doesn't look too good just yet.
thank you again for your help.

you should remind me to reduce the use of "just yet".
i'm doing some more reading about superCID and S-on or S-off.
I understand there's a utility from this thread that could determine the supercid status.
http://forum.xda-developers.com/showthread.php?t=1672284
again i'd like to point out i have no clue what has been done to this phone so i am trying to handle it with as much care as possible in order not to brick it.
in case superCID is 1111111 and naturally i don't have the original CID, where would that leave me?
As i am understanding slowly how this phone works, if the previous user managed to install a custom rom and a custom recovery on it, would only make sense to assume the superCID has been modified? (i'll be running the tool shortly unless someone jumps and says NOOOOOOOOO don't do it!!!)
I also noticed the teamwin recovery installed is 2.1.8.1
next is understanding what s-on and s-off are all about.
i have a feeling my chances of reverting to stock firmware are slimming. this is quite a complicated phone, nice challenge.
i'm going to point out again what my main problem is: i can't unlock the sim using the code provided by at&t since as soon as the phone reboots it asks me again. so i don't mind whichever route to take, whether custom or stock, as long as i can unlock the sim the simple way.
cheers.

srasiroslayer said:
At this point i start searching online for the official firmware from htc for this specific model and find the 4.2.2 version and proceed to install it according to their requirements and steps (in manual mode from a desktop pc since the rom installed doesn't have the update feature).
The process gets locked at a point and cannot proceed further.
Phone boots normally again and i decide to do a factory reset. This i when i notice a teamwin custom recovery was installed which is what is blocking the official rom installation.
Click to expand...
Click to collapse
This is not correct (the text I've bold faced above). OTA requires stock recovery, but RUU does not.
What stopped the RUU from working, is that you bootloader is unlocked (as indicated by the "unlocked" text in hboot). But in your case, you are lucky, since if you were trying to run the 3.18 Jellybean RUU, if it had gotten past the bootloader lock check, it would have bricked the phone (known bug) if you have SuperCID (which is pretty likely).
To reiterate: DO NOT try to relock the bootloader and run the 3.18 RUU, as with S-on and SuperCID, this will brick your phone.
If you have a working adb/fastboot environment, you can easily check CID with the command: fastboot getvar all
---------- Post added at 10:26 AM ---------- Previous post was at 10:23 AM ----------
srasiroslayer said:
i have a feeling my chances of reverting to stock firmware are slimming.
Click to expand...
Click to collapse
That is far form the truth. Getting back to stock is not that hard.
But if you only want to SIM unlock, I'm not sure that going stock will necessarily help you. You are on CleanROM now, which is pretty close to stock, and I don't think there have been many issues getting SIM unlock on CleanROM.

redpoint73 said:
This is not correct (the text I've bold faced above). OTA requires stock recovery, but RUU does not.
What stopped the RUU from working, is that you bootloader is unlocked (as indicated by the "unlocked" text in hboot). But in your case, you are lucky, since if you were trying to run the 3.18 Jellybean RUU, if it had gotten past the bootloader lock check, it would have bricked the phone (known bug) if you have SuperCID (which is pretty likely).
To reiterate: DO NOT try to relock the bootloader and run the 3.18 RUU, as with S-on and SuperCID, this will brick your phone.
If you have a working adb/fastboot environment, you can easily check CID with the command: fastboot getvar all
---------- Post added at 10:26 AM ---------- Previous post was at 10:23 AM ----------
That is far form the truth. Getting back to stock is not that hard.
But if you only want to SIM unlock, I'm not sure that going stock will necessarily help you. You are on CleanROM now, which is pretty close to stock, and I don't think there have been many issues getting SIM unlock on CleanROM.
Click to expand...
Click to collapse
Wunderbar,
Thank you again for clarifying things up.
I've been taking this time to read more about this phone on this thread:
- http://forum.xda-developers.com/showthread.php?t=1671237
So i am starting to understand how it works.
i have to admit that i should consider myself lucky for if the phone had a locked bootloader, it would've been bricked.
i've been reading a bit about superCID and i don't have a working linux environment (other than virutal) running right now.
but i'll figure out how to check if it's superCID or not (more likely yes).
now that i've figured out one way or the other that the simlock has nothing to do with the firmwares or recovery........... what could cause it?
again i just want it to work and then i'll take the time to play with the custom roms.
I have the correct unlocking code from AT&T since it wouldn't have accepted it to reboot the phone if it was wrong.
so what could be messing it up?
Cheers

srasiroslayer said:
Wunderbar,
i've been reading a bit about superCID and i don't have a working linux environment (other than virutal) running right now.
but i'll figure out how to check if it's superCID or not (more likely yes).
Click to expand...
Click to collapse
You don't need a Linux environment to get fastboot/adb working. And you will need them if you want to get s-off or change the CID (which would be the solutions to your problem of running the RUU).
To get fastboot/adb going, I'd suggest you start here: http://forum.xda-developers.com/showthread.php?t=1754018
There are some apps what will read the phone's state including CID. Others here have mentioned the name of one (or more) such app, but I can't recall, and I don't use it. I'm used to using fastboot.
srasiroslayer said:
now that i've figured out one way or the other that the simlock has nothing to do with the firmwares or recovery........... what could cause it?
again i just want it to work and then i'll take the time to play with the custom roms.
I have the correct unlocking code from AT&T since it wouldn't have accepted it to reboot the phone if it was wrong.
so what could be messing it up?
Click to expand...
Click to collapse
Not sure. Going back to stock might help. Its all I can think of. But don't be disappointed if it still doesn't work.

Alright,
So i figured out my CIDnum is 1111111111 using fastboot.
I understand there's a tool that can revert that.
I should also switch to s-off next.
Then at the end lock the bootloader using the adb commands.
Am i on the right track?
At this point i'll try running the RUU and cross my fingers.
My question is, shouldn't i have the original CID number?
and another off topic point, i have no clue what s-on or s-off are.
i'll get into that reading mode again in a bit.
Thank you again, i feel i'm on the right track now and confident.
Cheers
P.S.: do you need me to post the "fastboot getvar all" results? or only thing missing to be sure of was the CID?

Hang on, you're s-on and SuperCID, don't run the RUU or you'll brick your phone. You need to do some reading and research all this before you try these things.
Sent from my Evita

Guys I am Vivek Rajput, from India. I have AT&T HTC oneX. Anything related to internet is not working except whatsapp. Every app is showing network error msg. Showing some data here which i got after reading here. Assume me complete novice about software/cellphones.
***LOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.320911_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012,14:36:28
Click to expand...
Click to collapse

Have you checked your APNs?
Sent from my Evita

srasiroslayer said:
Alright,
So i figured out my CIDnum is 1111111111 using fastboot.
I understand there's a tool that can revert that.
I should also switch to s-off next.
Then at the end lock the bootloader using the adb commands.
Am i on the right track?
At this point i'll try running the RUU and cross my fingers.
Click to expand...
Click to collapse
If you are going to s-off, you DO NOT want to change the CID. SuperCID (11111111) is needed to s-off.
As mentioned, make sure you s-off before RUU, or you will brick.
Once you are s-off, it shouldn't matter whether you lock the bootloader or not. S-off means all security checks are bypassed, including the check for bootloader lock.
srasiroslayer said:
and another off topic point, i have no clue what s-on or s-off are.
Click to expand...
Click to collapse
s-off, as mentioned above means all security checks are off. There are good and bad points to this.
The good, is that you will be safe of the SuperCID + RUU brick condition. Custom ROMs will also be easier to flash, if you are interested in doing that (do not need to flash boot.img separately).
The bad of s-off, is that because all security checks are off, there are no safety checks to prevent you from flashing the wrong things. You have to be very careful you don't flash something that is not intended for the device, as it may brick the phone.
Are you are okay with that, then proceed with s-off. If not, the alternate solution is to change the CID back to the proper AT&T CID (cws__001). This will also prevent the SuperCID + RUU brick condition. But may make the phone harder to s-off in the future, if you later choose that route.

It looks like then that the s-off route is the one to take, since i will definitely in the future be interested in flashing custom roms.
And it looks relatively easy as per:
http://forum.xda-developers.com/showthread.php?t=2155071
After doing some reading, it also looks safe to achieve s-off on custom roms such as my case.
I'm still reading if s-off will work on my bootloader version or if there are any specific versions to run it at. (so far no mention so good)
I'm guessing i will run s-off today and if everything works out as it should will post my results here.
Only then will i proceed to run the RUU which i downloaded from htc for the at&t model specifically (no chance i could go wrong with that).
Thank you for all the help, i honestly don't think i would've found my way around easily without guidance.
Cheers

Yes, the s-off method is easy, and it should work on any hboot version.
Good luck.

Could just having S-off fix my sim locked issue?
In any case new questions arise in my head such as since my model number is PJ8310000 and that with s-off i will be installing PJ8312000-OneX.zip, will that affect running the RUU later on?

srasiroslayer said:
Could just having S-off fix my sim locked issue?
Click to expand...
Click to collapse
I doubt it. SIM lock and s-off are not related, to my knowledge.
srasiroslayer said:
In any case new questions arise in my head such as since my model number is PJ8310000 and that with s-off i will be installing PJ8312000-OneX.zip, will that affect running the RUU later on?
Click to expand...
Click to collapse
Once you are s-off, all security and safety checks are off by definition. As long as you are running an RUU meant for EVITA, you will be safe, and it should run properly.

Looks like i got the 99 error thing.
at first i had the error 92 and all was working good but after the final reboot didn't get s-off
the second try i'm getting error 99.
I'm going to read more into it.
I'm still s-on so.......

So here are the current updates.
As i mentioned in the previous post, running it the first time resulted in error 92 which is normal, followed instructions and didn't get s-off.
second time i had error 99. still no s-off.
I turn off the device and power it back on, run the script all over again with a real good attention and precision (i usually don't f*ck things up).
This time i get the error 92 again and still no success at the end. (did this over 4 times now and no s-off).
would i be logical for me to assume that once the rom is booted it's messed up somewhere? hence the last part of the script not working and also hence sim unlock not working?
what's a good custom rom that would i could install using recovery and not brick my phone?
maybe just installing one would solve all my issues.
Cheers

What ROM are you attempting s-off on?
PS. Asking for a suggested/best/favourite ROM isn't allowed here.
Sent from my Evita

timmaaa said:
What ROM are you attempting s-off on?
PS. Asking for a suggested/best/favourite ROM isn't allowed here.
Sent from my Evita
Click to expand...
Click to collapse
Hi,
I'm trying it on CleanROM 4.5 beta2.
And by best rom in my case was asking one that would be compatible with my situation, as in hboot 1.0.9, teamwin 2.1.8.1 recovery, supercid, unlocked, s-on.
Cheers.

(help) ruu firmware

Hi
I can't find stock rom for my htc u11
Ocndugl0401 model.
Someone knows where to download?
Thank you

yossim66 said:
Hi
I can't find stock rom for my htc u11
Ocndugl0401 model.
Someone knows where to download?
Thank you
Click to expand...
Click to collapse
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit?usp=sharing
Sent from my HTC U11 using Tapatalk

speeddemon1891 said:
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit?usp=sharing
Click to expand...
Click to collapse
Hi
I saw that page before but didn't find htc_0401
Thank you

You mix up software version (401) with CID.
You can check your CID with "Simple CID Getter" on the Play Store.

kurtschmeichel said:
You mix up software version (401) with CID.
You can check your CID with "Simple CID Getter" on the Play Store.
Click to expand...
Click to collapse
You right, i get cid_060.
I download the ruu.
Thank you

https://androidfilehost.com/?
---------- Post added at 08:14 AM ---------- Previous post was at 08:13 AM ----------
Hi this is linked for all ruu frimwork
Sorry
This link
https://androidfilehost.com/?a=show&w=files&flid=183767
There are any ota and ruu and frimwork

This thread may help.
https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048/page99

mehrdad_esmaeeli said:
https://androidfilehost.com/?
---------- Post added at 08:14 AM ---------- Previous post was at 08:13 AM ----------
Hi this is linked for all ruu frimwork
Sorry
This link
https://androidfilehost.com/?a=show&w=files&flid=183767
There are any ota and ruu and frimwork
Click to expand...
Click to collapse
همش غیر فعاله

Hi everyone
Customer brought a phone to me to repair as they have bricked it with a custom rom, then deleted the system & recovery, then did the absolute unthinkable and relocked the bootloader i was told,
The os version is still there however when the device is booted with the power button a message appears with the device is corrupt and cannot be trusted and will not boot,
I cannot find a working stock HTC signed ruu.exe for this model & have downloaded the correct packages for the model and cid but it returns 9ruu security error zip from usb command, system also shows as modified in bootloader aswell.
This is what i am working with
Fastboot oem readmid returned 2PZC10000
Fastboot oem readcid returned htc_039
I cannot go supercid 11111111 with fastboot oem writecid11111111 as it return as not allowed
hTc download mode
***relocked***
***production***
htc_ocnuhl PVT S-ON
LK-1.0.0.0000
Radio-8998-002772TOV-1712061121
OpenDSP-V11.6.00347.CB8998_0711
OS-2.33.710.9
Dec 8 2017,21:29:54 (1002308)
i cannot boot to any recovery
I cannot obtain the identifier tokken as it displays killswitch enabled on the 3 options and i cannot flash the original unlock_code.bin that was provided on the thumb drive with the phone and also return not allowed on production build also
I have tried the following commands trying to flash the OTA's and also the firmware
Fastboot flash all <zip>
Fastboot flash <zip>
Fastboot flash zip <zip>
Fastboot update <zip>
All fail with some error
and also used htc_fastboot, minimal adb and fastboot 1.7msi & also power shell im using windows 8 also but no matter what i do cannot get anything to flash to the customers phone i downloaded the OTA's & firmware from the google spreadsheet i dont know what im doing wrong and the only RUU.exe i do have for htc_ocnuhl returns an error with incorrect model id please use the correct update utility,
What should i do tell him his phone is kaput or ?? Ive been at this 3 days now ive been working on phones for 10 years nothing takes 3 days !!!!!!
Any help would be greatly appreciated

Matty1993 said:
Hi everyone
Customer brought a phone to me to repair as they have bricked it with a custom rom, then deleted the system & recovery, then did the absolute unthinkable and relocked the bootloader i was told,
The os version is still there however when the device is booted with the power button a message appears with the device is corrupt and cannot be trusted and will not boot,
I cannot find a working stock HTC signed ruu.exe for this model & have downloaded the correct packages for the model and cid but it returns 9ruu security error zip from usb command, system also shows as modified in bootloader aswell.
This is what i am working with
Fastboot oem readmid returned 2PZC10000
Fastboot oem readcid returned htc_039
I cannot go supercid 11111111 with fastboot oem writecid11111111 as it return as not allowed
hTc download mode
***relocked***
***production***
htc_ocnuhl PVT S-ON
LK-1.0.0.0000
Radio-8998-002772TOV-1712061121
OpenDSP-V11.6.00347.CB8998_0711
OS-2.33.710.9
Dec 8 2017,21:29:54 (1002308)
i cannot boot to any recovery
I cannot obtain the identifier tokken as it displays killswitch enabled on the 3 options and i cannot flash the original unlock_code.bin that was provided on the thumb drive with the phone and also return not allowed on production build also
I have tried the following commands trying to flash the OTA's and also the firmware
Fastboot flash all <zip>
Fastboot flash <zip>
Fastboot flash zip <zip>
Fastboot update <zip>
All fail with some error
and also used htc_fastboot, minimal adb and fastboot 1.7msi & also power shell im using windows 8 also but no matter what i do cannot get anything to flash to the customers phone i downloaded the OTA's & firmware from the google spreadsheet i dont know what im doing wrong and the only RUU.exe i do have for htc_ocnuhl returns an error with incorrect model id please use the correct update utility,
What should i do tell him his phone is kaput or ?? Ive been at this 3 days now ive been working on phones for 10 years nothing takes 3 days !!!!!!
Any help would be greatly appreciated
Click to expand...
Click to collapse
Hi everyone so customer didn't want the phone in the end as it couldn't be repaired so didnt bother returning to pick it up so like I do with all things I tinker and I've spent a long long time trying to fix the OS and I have finally done it yayyy scored myself a free U11,
So I dont know how it managed to work, because I had main version 2.33.710.9, and the package that actually worked to repair it and flashed was main version 1.11.710.5 or something like that, my bootloader was re locked and S-ON and nothing I tried would work phone had no recovery and would not boot all i would get is your device is corrupt, couldn't unlock the bootloader again all I would get is a message to state the 3 killswitches are active and to disable them but couldn't without a functional OS.
The 1.11.710.5 file I tried over the course since last post with normal fastboot didn't work, then I tried a series of htc_fastboot didnt work, I even used the fastboot binaries provided by HTCdev that didnt work, I tried every command I could rack up in my brain but still the body thing wouldnt flash I fixed roughly 6 RUU flash errors I was facing but the only one I couldn't get past was Ruu security fail zip from USB command, this told me it was something system wise, but had reinstalled everything including drivers gave all fastboots elevated privileges tried a million diff computers and cords ( lucky I run a phone shop hehehe )
Now something has completely slipped my mind I had a HTC 10 batch tool on my computer and had completely forgotten it had it's own terminal interafce, (which is a fully sik purple might I say) all I did was place the file into the path that the batch took was installed to which was com I do believe and then opened the batch tool up & typed " htc_fastboot oem rebootRUU" after i had put the device into download mode and connected device,
Device rebooted to RUU, all I did was type htc_fastboot flash zip <file_name> and it flashed all 28 zips from the 1.11.710.5 device rebooted and was now met with the HTC logo and phone booted straight up like nothing ever happened, once I had gotten the FRP lock removed (only took 5 minutes) not very good HTC lol I then went to the setting menu to software Info only to find out that the firmware was still 2.33.710.9 but the firmware file was specifically 1.11.710.5 as i had gotten it from the google spread sheet here on xda developers,
So there you have it everyone I hope this helps you repair your devices it seems it's all in the terminal used to flash the device as long as the file is also signed though I can't be 100% on that as I'm not sure the zip i used was signed either but anyway phone is working great and now it gets to be used and abused as a dev phone for myself

Matty1993 said:
Hi everyone so customer didn't want the phone in the end as it couldn't be repaired so didnt bother returning to pick it up so like I do with all things I tinker and I've spent a long long time trying to fix the OS and I have finally done it yayyy scored myself a free U11,
So I dont know how it managed to work, because I had main version 2.33.710.9, and the package that actually worked to repair it and flashed was main version 1.11.710.5 or something like that, my bootloader was re locked and S-ON and nothing I tried would work phone had no recovery and would not boot all i would get is your device is corrupt, couldn't unlock the bootloader again all I would get is a message to state the 3 killswitches are active and to disable them but couldn't without a functional OS.
The 1.11.710.5 file I tried over the course since last post with normal fastboot didn't work, then I tried a series of htc_fastboot didnt work, I even used the fastboot binaries provided by HTCdev that didnt work, I tried every command I could rack up in my brain but still the body thing wouldnt flash I fixed roughly 6 RUU flash errors I was facing but the only one I couldn't get past was Ruu security fail zip from USB command, this told me it was something system wise, but had reinstalled everything including drivers gave all fastboots elevated privileges tried a million diff computers and cords ( lucky I run a phone shop hehehe )
Now something has completely slipped my mind I had a HTC 10 batch tool on my computer and had completely forgotten it had it's own terminal interafce, (which is a fully sik purple might I say) all I did was place the file into the path that the batch took was installed to which was com I do believe and then opened the batch tool up & typed " htc_fastboot oem rebootRUU" after i had put the device into download mode and connected device,
Device rebooted to RUU, all I did was type htc_fastboot flash zip <file_name> and it flashed all 28 zips from the 1.11.710.5 device rebooted and was now met with the HTC logo and phone booted straight up like nothing ever happened, once I had gotten the FRP lock removed (only took 5 minutes) not very good HTC lol I then went to the setting menu to software Info only to find out that the firmware was still 2.33.710.9 but the firmware file was specifically 1.11.710.5 as i had gotten it from the google spread sheet here on xda developers,
So there you have it everyone I hope this helps you repair your devices it seems it's all in the terminal used to flash the device as long as the file is also signed though I can't be 100% on that as I'm not sure the zip i used was signed either but anyway phone is working great and now it gets to be used and abused as a dev phone for myself
Click to expand...
Click to collapse
Congrats on getting the phone revived. I tried all what you had mentioned in your earlier post except what you mentioned about the "HTC 10 Batch Tool". Never heard of it until now. Well too bad for my phone as I sent it out to HTC Repair and it is in their hands now (3 weeks and counting). Yep, my mistake was relocking the phone when I wanted to receive the OTA update (phone was rooted but I didn't flash any custom ROM). Thanks for the post.

mauiblue said:
Congrats on getting the phone revived. I tried all what you had mentioned in your earlier post except what you mentioned about the "HTC 10 Batch Tool". Never heard of it until now. Well too bad for my phone as I sent it out to HTC Repair and it is in their hands now (3 weeks and counting). Yep, my mistake was relocking the phone when I wanted to receive the OTA update (phone was rooted but I didn't flash any custom ROM). Thanks for the post.
Click to expand...
Click to collapse
Hey mate yeah I spent weeks on end trying everything it seems the HTC 10 batchtool was the saviour here on xda somewhere as that's where I got it from the batch tool has it's own terminal built into it and it must still hold official HTC code in it somewhere to allow the package to be flashed,
Least you know for next time if it happens again to avoid that hefty repair bill by HTC

Matty1993 said:
Hey mate yeah I spent weeks on end trying everything it seems the HTC 10 batchtool was the saviour here on xda somewhere as that's where I got it from the batch tool has it's own terminal built into it and it must still hold official HTC code in it somewhere to allow the package to be flashed,
Least you know for next time if it happens again to avoid that hefty repair bill by HTC
Click to expand...
Click to collapse
That's the story of my life, a day late and a dollar short. All the best.

Matty1993 said:
So I dont know how it managed to work, because I had main version 2.33.710.9, and the package that actually worked to repair it and flashed was main version 1.11.710.5
Click to expand...
Click to collapse
@Matty1993
How did you flash Nougat RUU on phone with Oreo firmware? I always get error beacuse of version.

wojownikhaha said:
@Matty1993
How did you flash Nougat RUU on phone with Oreo firmware? I always get error beacuse of version.
Click to expand...
Click to collapse
When you use Sunshine.apk you can set S-Off and flash Nougat

wojownikhaha said:
@Matty1993
How did you flash Nougat RUU on phone with Oreo firmware? I always get error beacuse of version.
Click to expand...
Click to collapse
https://forum.xda-developers.com/u11/how-to/guide-downgrade-htc-u11-oreo-to-nougat-t3754481

miffymiffy said:
https://forum.xda-developers.com/u11/how-to/guide-downgrade-htc-u11-oreo-to-nougat-t3754481
Click to expand...
Click to collapse
I read this topic, but this metod requires working TWRP partition I got only (relocked) bootloader and download mode, so have to try Chimera Tool or something like that.

snoopyhaeckers said:
When you use Sunshine.apk you can set S-Off and flash Nougat
Click to expand...
Click to collapse
I was still S-ON and had Relocked BL OEM unlock was OFF due to no working OS ( was corrupt) no recovery, only download, bootloader and RUU mode,
the HTC fastboot batch tool allows rollback of the bootloader without paying $25 for sunshine off to do it, ive just seen this now to lol only took 3 months to reply
I actually made a post on how to fix any flash errors like that a while ago its in the HTC U11 forums 1.5k veiws and counting

Matty1993 said:
I was still S-ON and had Relocked BL OEM unlock was OFF due to no working OS ( was corrupt) no recovery, only download, bootloader and RUU mode,
the HTC fastboot batch tool allows rollback of the bootloader without paying $25 for sunshine off to do it, ive just seen this now to lol only took 3 months to reply
I actually made a post on how to fix any flash errors like that a while ago its in the HTC U11 forums 1.5k veiws and counting
Click to expand...
Click to collapse
Sorry man I doesn't have a htc 10 at I have at the moment u 11
Sent from my HTC U11 using XDA Labs

where do I download zip version of signed HTC ruu firmware?