Database Info

[Q] Problem with SuperCID (sensation)

I S-offed my device via htcdev.com(as Revolutionary IO method didn't work for me). I flashed CWM 5.0.0.8.
To supercid my sensation, I followed the guide on this link :
http://forum.xda-developers.com/showthread.php?t=1192300
When I try to do the the SuperCID part of it, I get this:
C:\adb>fastboot oem writecid 11111111
... INFOvreg_set: request is duplicated id 14
INFO pyramid_init_sd, SD card power on ok
INFOsdcc_init_memory_device done
INFO[FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
INFO[JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 1.081s]
finished. total time: 1.082s
Yes, my phone is detected when I type "adb devices".
Yes, I'm rooted. When i downloaded root checker app from playstore and checked it.. it said "Rooted".
Please help. Thank you in advance.

vipulnj said:
I S-offed my device via htcdev.com(as Revolutionary IO method didn't work for me). I flashed CWM 5.0.0.8.
To supercid my sensation, I followed the guide on this link :
http://forum.xda-developers.com/showthread.php?t=1192300
When I try to do the the SuperCID part of it, I get this:
C:\adb>fastboot oem writecid 11111111
... INFOvreg_set: request is duplicated id 14
INFO pyramid_init_sd, SD card power on ok
INFOsdcc_init_memory_device done
INFO[FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
INFO[JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 1.081s]
finished. total time: 1.082s
Yes, my phone is detected when I type "adb devices".
Yes, I'm rooted. When i downloaded root checker app from playstore and checked it.. it said "Rooted".
Please help. Thank you in advance.
Click to expand...
Click to collapse
Using htcdev method to unlock your phone doesn't give you complete unlock solution it prevents fastboot commands that's why you are unable to supercid your device using fastboot command.
Using HTC unlocked bootloader you can still flash roms but you can only flash roms which are having stock kernel as option like ARHD. any other kernel will not be accepted by bootloader
Sent from my HTC Sensation XE with Beats Audio using xda premium

So what can i do next?
ganeshp said:
Using htcdev method to unlock your phone doesn't give you complete unlock solution it prevents fastboot commands that's why you are unable to supercid your device using fastboot command.
Using HTC unlocked bootloader you can still flash roms but you can only flash roms which are having stock kernel as option like ARHD. any other kernel will not be accepted by bootloader
Sent from my HTC Sensation XE with Beats Audio using xda premium
Click to expand...
Click to collapse
Thank you ganeshp. So what can i do next? Can I do something through the terminal emulator?

vipulnj said:
Thank you ganeshp. So what can i do next? Can I do something through the terminal emulator?
Click to expand...
Click to collapse
I got a method which can be done through adb shell or terminal emulator
But I haven't tried it myself but the comments are showing lot if success so try at your own risk and follow the steps carefully
Here is the link
h-t-t-p://www.simply-android.com/discussion/1600/how-to-super-cid-for-sensation/p1
(remove "-" between http)
Sent from my HTC Sensation XE with Beats Audio using xda premium

Link broken!
Yes Ganesh! Even I just was looking at the same. But the multiupload link is broken. Any idea how I can get to download this file? Please help! I think I am close to this.
Thanks a lot!

vipulnj said:
Yes Ganesh! Even I just was looking at the same. But the multiupload link is broken. Any idea how I can get to download this file? Please help! I think I am close to this.
Thanks a lot!
Click to expand...
Click to collapse
Yeah I came to know that too.
I'm just trying something and verifying it
I'll give you an update in few minutes
Edit1:
Can you first verify your CID and MID and post it here
type "fastboot getvar cid" and "fastboot getvar mid"
these commands will work as they are doing just reads
Edit2:
Can you give me small info?
Type
"dd if=/dev/block/mmcblk0p16 of=/sdcard/mmcblk0p16_bkp"
Without quotes on terminal emulator after typing su
(Be careful while using dd command its extremely low level command and its quite risky(may brick the device if typed wrongly)
so double check the command before pressing enter
Also this command will just read the block so it might pose no problem but be cautious just in case)
And send the mmcblk0p16_bkp (will be at sdcard root once you type the command) through private message to me/or post it here if its fine with you
Sent from my HTC Sensation XE with Beats Audio using xda premium

Exactly the same problem HELP! I want Sense 4 ORDROID and it just won't flash because the firmware won't flash because i cant supercid! The problem is the same! Because i used the HTCDEV method

Sorry can't help you in this case.
I've confirmed with devs .
No one for sure knows where/which partition the cid is stored.
So modifying the partition won't do and its pretty dangerous which might brick your device.
So we can't change cid without fastboot command.
I'll dig further and will let you know if I got any leads
---------- Post added at 10:35 PM ---------- Previous post was at 10:12 PM ----------
guys are you sure you are soff
i mean when you unlocked your boot loader using htcdev the bootloader reads unlocked ...but wont change s-on to s-off
so double check the s-off and if you are s-off then you guys have
a big chance to completely unlock your boot loader and also get supercid
so if you guys are soff then flash the latest firmware package again
then you'll get both soff and supercid
here is the firmware thread
firmware thread

"Revolutionary did not work for me...." = not s-off.
sent from HTC Pyramid using Tapatalk 2

stringer7 said:
"Revolutionary did not work for me...." = not s-off.
sent from HTC Pyramid using Tapatalk 2
Click to expand...
Click to collapse
yeah i know but i just want to here from them just to make sure
someone might try revolutionary to get the bootloader unlocked (or not )

You are clearly **unlocked** but still S-ON.
Use Revolutionary to S-OFF and then supercid devices.
Beta key is case sensitive so be sure to digit it correctly (usually this is the main reason why it doesn't work at first attempt).

kualmente said:
You are clearly **unlocked** but still S-ON.
Use Revolutionary to S-OFF and then supercid devices.
Beta key is case sensitive so be sure to digit it correctly (usually this is the main reason why it doesn't work at first attempt).
Click to expand...
Click to collapse
Revolutionary does not work because i have HBOOT 1.27.0000 and that is not surported. WOW! just checked i do indeed have s-on! how do i turn it off? Is there anyway to downgrade HBOOT?

Zd0s said:
Revolutionary does not work because i have HBOOT 1.27.0000 and that is not surported. WOW! just checked i do indeed have s-on! how do i turn it off?
Click to expand...
Click to collapse
You cannot. As you said actually Revolutionary doesn't support Hboot 1.27

Zd0s said:
Revolutionary does not work because i have HBOOT 1.27.0000 and that is not surported. WOW! just checked i do indeed have s-on! how do i turn it off? Is there anyway to downgrade HBOOT?
Click to expand...
Click to collapse
revolutionary does two things
1.unlock your bootloader completely (unlike HTCdev which unlocks partly)
2.S-off your device
Right now you are out of luck
but there 2 promising developments happening which might get s-off on hboot 1.27
here are the threads
be sure to follow them by subscribing to them (they might come with solution anytime)
1.http://forum.xda-developers.com/showthread.php?t=1573577
2.http://forum.xda-developers.com/showthread.php?t=1522351

Thanks everyone for your help! I will subcribe to those threads and wait patiently

Zd0s said:
Thanks everyone for your help! I will subcribe to those threads and wait patiently
Click to expand...
Click to collapse
There is actually a button to say thanks
Actually i've learned a lot too while finding answers to your questions

ganeshp said:
There is actually a button to say thanks
Actually i've learned a lot too while finding answers to your questions
Click to expand...
Click to collapse
Sorry forgot!
Done Now B)

ganeshp said:
Sorry can't help you in this case.
I've confirmed with devs .
No one for sure knows where/which partition the cid is stored.
So modifying the partition won't do and its pretty dangerous which might brick your device.
So we can't change cid without fastboot command.
I'll dig further and will let you know if I got any leads
---------- Post added at 10:35 PM ---------- Previous post was at 10:12 PM ----------
guys are you sure you are soff
i mean when you unlocked your boot loader using htcdev the bootloader reads unlocked ...but wont change s-on to s-off
so double check the s-off and if you are s-off then you guys have
a big chance to completely unlock your boot loader and also get supercid
so if you guys are soff then flash the latest firmware package again
then you'll get both soff and supercid
here is the firmware thread
firmware thread
Click to expand...
Click to collapse
Sorry, I was new to this actually. I only unlocked the bootloader. I was/am still S-ON.. Anyway to get to S-off? Or suppose I get an official OTA update from HTC (which I think I will get though I have unlocked my bootloader), will everything be back to how it was when I bought it?? So that I can start everything afresh with Revolutionary method. I am not going to htc dev method again!
Please help.
Thank you!

vipulnj said:
Sorry, I was new to this actually. I only unlocked the bootloader. I was/am still S-ON.. Anyway to get to S-off? Or suppose I get an official OTA update from HTC (which I think I will get though I have unlocked my bootloader), will everything be back to how it was when I bought it?? So that I can start everything afresh with Revolutionary method. I am not going to htc dev method again!
Please help.
Thank you!
Click to expand...
Click to collapse
1.you want get SOFF ->right now you are out of luck
just wait for 2 promising tools which claim to downgrade your HBOOT ...i've mentioned them in my previous posts and subscribe to them
2.If you want to flash a custom rom....then you still have a chance ...but only couple of roms though
(you did have custom recovery flashed right....CWM i guess)
if your option is 2 let me know ill guide you through further steps

Option 2!
ganeshp said:
1.you want get SOFF ->right now you are out of luck
just wait for 2 promising tools which claim to downgrade your HBOOT ...i've mentioned them in my previous posts and subscribe to them
2.If you want to flash a custom rom....then you still have a chance ...but only couple of roms though
(you did have custom recovery flashed right....CWM i guess)
if your option is 2 let me know ill guide you through further steps
Click to expand...
Click to collapse
Yeah, i do have Clock Work Mod 5.0.2.0 now.. Option 2 agreed!
What is the next step?
Thanks for help.

[HOWTO] [HTC One SV] Unbrand your phone to get the OTA updates

Bonjour everyone, here's a little guide on how to unbrand your phone in order to get the OTA updates notifications directly and be able to install them.
If you want to get S-OFF one day on your One SV, read this first. You need to change CID to SuperCID to do so, and it's not possible (for the moment) if you upgrade to JB
Basically this works as long as your phone model is sold unbranded somewhere in the world and that the people having such a phone got an OTA update.
For now, ther's no way to change CID if you're running JB and are S-ON. That means that this only work for One SV's running ICS who want to get the OTA updates.
As far as I know, it works on K2_U and K2_UL, since they both got an OTA update to JB.
The trick is simple, I didn't invent it and haven't been able to find its original founder, but thanks a lot to her or him !
I'm basically just a messenger here since I only tried out some stuff that worked with other phones, so thanks a lot to bkcokota, old.splatterhand and jmztaylor
Don't try it if you're worried, bricks happen, you'd be the only one responsible !
Here we go :
1. First you need to root your phone, here's how.
2. Change you CID using the same method than for the One S.
Personnaly, I changed it to "HTC__203", which is the CID unbranded HTC phones have in France (HTC-FRA).
For example, "HTC__001" is HTC-WWE, which stands for World Wide English.
You can change it to whatever CID you like : choose it well. I can only recommend to use HTC__203 since it's the only one I tried and that it worked, but do as you please !
3. Flash stock recovery back. You'll find it here or here. Flash it like you flashed CWM recovery (into fastboot, using fastboot flash recovery xxxxxx.img).
4. Relock your bootloader. It's possible that it's not necessary, but it can't hurt ("fastboot oem lock", when in fastboot usb)
5. Run a RUU that matches you unbranded CID to get an "unbranded" rom.
You'll find them here, for example. The "RUU_K2_UL_ICS_40_HTC_Europe_1.17.401.5_R....exe" one will work with HTC__203 and HTC__001 CIDs.
6. Go ask your phone if he can find any updates
WARNING : for the moment there's no way to change CID if you upgrade to JB since the newer HBOOT (v2.00) don't let you do it. That means that for now you won't be able to S-OFF if you upgrate to JB using this method. For now...

Nice one!
Only thing i would add for people to know:
if somebody want to get S-Off, they should change the CID to SuperCID 11111111 (or if you want 22222222,...).

old.splatterhand said:
Nice one!
Only thing i would add for people to know:
if somebody want to get S-Off, they should change the CID to SuperCID 11111111 (or if you want 22222222,...).
Click to expand...
Click to collapse
Done, sir.
It was only said at the bottom of the message at first, but now I put it at the beginning as well.
There's one thing that I'm trying to get though : according to a lot of people and forums, you don't get OTA when you have SuperCID... but some poeple say they do.
It probably changes depending on the type of HTC phone, but also depending on the OTA (some got the first ones, but not the latest...).

I got the ota notification with SuperCID, i think it depends on more things.
But there i'm not far enough into it.

I have had no success at all. My story:
Updated a branded phone to JB, rooted. Then I did a moonshine S-off and changed CID to HTC__001 (even tried 11111111).
I have downloaded a ICS RUU (couldn't find stock K2_UL so I thought that I would download ICS first and then do OTA to JB) but I am getting error 158. I have checked md5 sum and it matches (http://androidfiles.org/ruu/getdown...0.14_2_10.49.40.11L_release_301902_signed.exe). Any ideas?

If you're on jb and hboot 2.00, that's normal... and written in the first post.

There is information that it is impossible to change CID while on JB and with 2.0 hboot, but I guess that I have had success in changing to superCID (at least this is what I can read in bootloader and using fastboot oem readcid command.
So, as far as I understand newer hboot won't let me use older RUU as well, right?

Is there any chance to make this for the k2cl ( boost mobile ) version?

idr666 said:
Is there any chance to make this for the k2cl ( boost mobile ) version?
Click to expand...
Click to collapse
Can you be more specific, what you mean with "this".

old.splatterhand said:
Can you be more specific, what you mean with "this".
Click to expand...
Click to collapse
Sorry, I was wondering if there is a way to update this phone ( the k2cl ) to JB

idr666 said:
Sorry, I was wondering if there is a way to update this phone ( the k2cl ) to JB
Click to expand...
Click to collapse
Boost has no official jb, but i know that there is work for an custom jb rom for boost.

Oh, thank you for the info. Is there any link about this work in progress?

idr666 said:
Oh, thank you for the info. Is there any link about this work in progress?
Click to expand...
Click to collapse
Look here

szympro said:
There is information that it is impossible to change CID while on JB and with 2.0 hboot, but I guess that I have had success in changing to superCID (at least this is what I can read in bootloader and using fastboot oem readcid command.
So, as far as I understand newer hboot won't let me use older RUU as well, right?
Click to expand...
Click to collapse
old.splatterhand, you seem to know this and that about One SV. No chance for older RUU, right? I can't seem to find a clean WWE JB OTA update. I just want a clean, stock, not modified ROM from HTC and I thought RUU is the only way to go :crying: Any advices?

szympro said:
There is information that it is impossible to change CID while on JB and with 2.0 hboot,...
Click to expand...
Click to collapse
This was before moonshine was available. With S-Off i think it should be possible.
So, as far as I understand newer hboot won't let me use older RUU as well, right?
Click to expand...
Click to collapse
I think so.
szympro said:
old.splatterhand, you seem to know this and that about One SV. No chance for older RUU, right? I can't seem to find a clean WWE JB OTA update. I just want a clean, stock, not modified ROM from HTC and I thought RUU is the only way to go :crying: Any advices?
Click to expand...
Click to collapse
To get it a bit clearer.
At this point i'm not very up to date, thats why i didn't answer til now.
I think (but i'm not sure) you can flash the ruu, if you are on hboot 1.0.
And as you are S-Off you should be able to downgrade hboot. But this is a very risky point, you can easily brick your device. Here is, how you have to do:
rollon76 said:
To change hboot you will need a PL80IMG.zip on sdcard with android-info.txt and hboot.img inside it.
reboot to bootloader and flash.
Click to expand...
Click to collapse
The thing what makes it difficult, is to get the hboot.img (its inside ics ruu), cause the htc ruu's encrypted and i only have heard about tools for linux which can decrypt it.

Thanks to your reply I did some research and I have managed to do what I wanted. I have downgraded hboot first (by extracting and encrypting ICS RUU using linux), then I could run RUU and now I am stock ICS with S-off and superCID
Should I post some files from RUU? 1.0 hboot or stock recovery? You guys need something?
Thanks for your helping hand old.splatterhand!

szympro said:
Thanks to your reply I did some research and I have managed to do what I wanted. I have downgraded hboot first (by extracting and encrypting ICS RUU using linux), then I could run RUU and now I am stock ICS with S-off and superCID
Should I post some files from RUU? 1.0 hboot or stock recovery? You guys need something?
Thanks for your helping hand old.splatterhand!
Click to expand...
Click to collapse
Glad, it worked for you.
Yes, of course, everything is appreciated! You can use this thread, please post ruu name too. You can look at my posts there. Hboot, boot.img, recovery, radio, would be fine.

HERE have other ruu
https://www.dropbox.com/sh/1t2zswod7tc97az/5hbzEgTv80

szympro said:
I have downgraded hboot first (by extracting and encrypting ICS RUU using linux)
Click to expand...
Click to collapse
Wow, that's cool !
Did you use rollon's method and flashed PL80IMG.zip in bootloader mode ?
If yes, which android-info.txt did you use ?
If not, how did you do it ?
szympro said:
then I could run RUU and now I am stock ICS with S-off and superCID
Click to expand...
Click to collapse
Even cooler for you.
Did you get the ota update notification for JB then ?
Did you manage to apply it ?
Thanks and congratulations !

Hi everyone.
Just a quick message to confirm that rollon's method works.
To downgrade you need to be S-OFF, extract and decrypt (with ruuveal, using linux or a linux virtualbox runned in windows) hboot and androidinfo from ICS RUU, put them in a zip named PL80IMG.zip, put it on your sd card and boot into bootloader. Then you can run the ICS RUU normally and you'll be back to stock ICS, with a "*** LOCKED ***" bootloader (not relocked !), will be able to go back to S-ON using "fastboot oem writesecureflag 3" (thanks to JMZ)...
You'll then have a locked S-ON out of box phone running 100% stock ICS with original boot, recovery and all that... who'll get the 2 JB OTA's...
In case anyone's interested

Firmware Update Q&A [extra noob friendly]

WARNING*WARNING*WARNING
do this at your own risk! This is for s4 only!!
It has been brought to my attention that there might be a mid (model id) conflict
With flashing this and me along with others are trying to narrow down the issue. Thanks to @real187 for bring this to my attention.
I'm
S-off
Cid 11111111
MID PJ4011000
And had no problems flashing this firmware but others with same setup have reported soft brick.
OK I think @mkinney88 may have pin pointed where the soft brick may be coming from. If you s-off using facepalm, flash the firmware.zip and get soft bricked try this.
1. Get back to s-on (warning read directions several times before doing you CAN hard brick your phone) ~ http://forum.xda-developers.com/showthread.php?p=38267667
2. Get s-off with moonshine ~ http://forum.xda-developers.com/showthread.php?p=42613403
First off this is mostly ment for the T-Mobile branded phones but ill try and help all please let me know when asking questions if you have a T-Mobile or HTC branded phone (it has it right on the front of phone ).
I'm starting this thread to have a place for noobs and long time users to ask and answer questions. This is going to be as noob friendly as possible but please keep questions firmware related only. So lets get started.
i really dont know how to make it any clearer then @mkinney88 did in his rom OP. all credit goes to him these institutions.
By: Mkinney88 (UnKnown_ROMS)
--> Unlock your device
Step1. download and use this program to unlock your bootloader http://forum.xda-developers.com/show....php?t=1604677
Step2. SuperCID your phone so you can S-OFF and so you can also write the T-MOB010 CID if you are on a different carrier and want to run this ROM. You will need to be CID T-MOB010 if you want to run the firmware.zip Follow this to SuperCID http://forum.xda-developers.com/show...1#post26516911
Step3. After you have sucessfully unlocked your bootloader and SuperCID you can either S-OFF your phone or Not, it is up to you. I would recommend you achieve S-OFF so you can flash radios, kernels, and boot.img's. Follow this to achieve S-OFF http://forum.xda-developers.com/show....php?t=2155135
If everything went well you should be able to reboot into bootloader using the All In One Tool and in the top left your bootloader should say Unlocked, S-OFF, CID-1111111
--> Writing T-MOB010 CID
If you did everything right then your all set. Next you will want to run the fastboot command " fastboot oem writecid T-MOB010 " and reboot into bootloader again. Now in the top left it should say CID-T-MOB010. If you have made it this far you are doing great. Now we are going to run the firmware.zip package to ensure everything works without a problem.
--> Flashing the firmware.zip
Now if you are coming from STOCK OEM LOCKED T-MOBILE PHONE that already has Andorid 4.1.1 Jelly Bean on it then you do not need to do this step. You must be CID T-MOB010 to flash this or S-OFF CID 11111111 (I had no problem flashing firmware with s-off and Cid 11111111 but others have reported problems so if you don't want to chance it write your Cid to T-MOB010)
1. fastboot oem lock
2. fastboot erase cache
3. fastboot oem rebootRUU
4. fastboot flash zip firmware.zip, and you might get an error
5. fastboot flash zip firmware.zip again and it should pass and install a bunch of files should take about 2 minutes.
6. the phone does NOT reboot on its own so #7
7. fastboot reboot or fastboot reboot-bootloader
--> UNLOCKING BOOTLOADER AGAIN
Now we need to unlock the bootloader again so just do step 1 again but you will already have the Unlock_code.bin from the first time you unlocked you phone so no need to get another one from HTC but if for some funny reason it doesn't work you will need to just resubmit for a new one.
--> CUSTOM RECOVERY
After doing all the above steps you will need to install the custom recover. You will need to use TWRP 2.3.3 to insure no problems. Here is the link to download it http://techerrata.com/file/twrp2/vil....3.0-ville.img after you download it go to the DIR where you have the HTC One S All-In-One Toolkit v3.5 extracted. example: C:\Users\yourusername\Downloads\One_S_All-In-One_Kit_v3.5\One_S_All-In-One_Kit_v3.5\Data\Recoveries and in the Recoveries folder rename the downloaded twrp2.3.3.img to TWRPS4.img and replace the one that is in the folder and then proceed to install the recovery,
now youve followed that and now your stuck ether getting errors or phone is now acting all erratic? that's why you're here. go ahead ask any question you want about firmware noobish,dumb,anything as long as its firmware related. (sorry i cant tell you how to get the cute girl at the mall)
this is just a crude start ill add and refine as we get going.
please do don't ask firmware questions in development threads ask here.
If you want to see mkinney88's full guide go here paste bin

Downloads
FIRMWARE ZIP DOWNLOAD
https://drive.google.com/folderview?id=0B-BYnLh2sosKamRwaUJJS05oU3M&usp=sharing or http://db.tt/Wua8mDS2
Credit go's to mkinney88 for the firmware

Bricks
First off if you can get into bootloader then you don't have a hard brick.
If your phone is in the black screen of death there may be hope but we're still trying to figure that one out.
If your phone doesn't respond to any input from you (power, power+volume down) then congratulations you have a hard brick but don't through it in the junk drawer just yet, you can have it jtag repaired (they open phone plug into main board and flash everything)
Here's the link (you do have to pay for this)
http://forum.xda-developers.com/showthread.php?p=37136553

One more just in case

rc420head said:
I'm starting this thread to have a place for noobs and long time users to ask and answer questions. This is going to be as noob friendly as possible but please keep questions firmware related only. So lets get started.
i really dont know how to make it any clearer then @mkinney88 did in his rom OP. all credit goes to him these institutions.
By: Mkinney88 (UnKnown_ROMS)
--> Unlock your device
Step1. download and use this program to unlock your bootloader http://forum.xda-developers.com/show....php?t=1604677
Step2. SuperCID your phone so you can S-OFF and so you can also write the T-MOB010 CID if you are on a different carrier and want to run this ROM. You will need to be CID T-MOB010 if you want to run the firmware.zip Follow this to SuperCID http://forum.xda-developers.com/show...1#post26516911
Step3. After you have sucessfully unlocked your bootloader and SuperCID you can either S-OFF your phone or Not, it is up to you. I would recommend you achieve S-OFF so you can flash radios, kernels, and boot.img's. Follow this to achieve S-OFF http://forum.xda-developers.com/show....php?t=2155135
If everything went well you should be able to reboot into bootloader using the All In One Tool and in the top left your bootloader should say Unlocked, S-OFF, CID-1111111
--> Writing T-MOB010 CID
If you did everything right then your all set. Next you will want to run the fastboot command " fastboot oem writecid T-MOB010 " and reboot into bootloader again. Now in the top left it should say CID-T-MOB010. If you have made it this far you are doing great. Now we are going to run the firmware.zip package to ensure everything works without a problem.
--> Flashing the firmware.zip
Now if you are coming from STOCK OEM LOCKED T-MOBILE PHONE that already has Andorid 4.1.1 Jelly Bean on it then you do not need to do this step. You must be CID T-MOB010 to flash this or S-OFF CID 11111111
1. fastboot oem lock
2. fastboot erase cache
3. fastboot oem rebootRUU
4. fastboot flash zip firmware.zip, and you might get an error
5. fastboot flash zip firmware.zip again and it should pass and install a bunch of files should take about 2 minutes.
6. the phone does NOT reboot on its own so #7
7. fastboot reboot or fastboot reboot-bootloader
--> UNLOCKING BOOTLOADER AGAIN
Now we need to unlock the bootloader again so just do step 1 again but you will already have the Unlock_code.bin from the first time you unlocked you phone so no need to get another one from HTC but if for some funny reason it doesn't work you will need to just resubmit for a new one.
--> CUSTOM RECOVERY
After doing all the above steps you will need to install the custom recover. You will need to use TWRP 2.3.3 to insure no problems. Here is the link to download it http://techerrata.com/file/twrp2/vil....3.0-ville.img after you download it go to the DIR where you have the HTC One S All-In-One Toolkit v3.5 extracted. example: C:\Users\yourusername\Downloads\One_S_All-In-One_Kit_v3.5\One_S_All-In-One_Kit_v3.5\Data\Recoveries and in the Recoveries folder rename the downloaded twrp2.3.3.img to TWRPS4.img and replace the one that is in the folder and then proceed to install the recovery,
now youve followed that and now your stuck ether getting errors or phone is now acting all erratic? that's why you're here. go ahead ask any question you want about firmware noobish,dumb,anything as long as its firmware related. (sorry i cant tell you how to get the cute girl at the mall)
this is just a crude start ill add and refine as we get going.
please do don't ask firmware questions in development threads ask here.
If you want to see mkinney88's full guide go here paste bin
Click to expand...
Click to collapse
Don't flash the firmware on SuperCID which leads to brick, which can be recovered though

vatsaman said:
Don't flash the firmware on SuperCID which leads to brick, which can be recovered though
Click to expand...
Click to collapse
Bricks can't be recovered (unless you jtag) , you had a soft brick.
I had no problem doing this with s-off and Cid 11111111.
But I remember you from other threads and I have a few questions.
1. Is your phone t-mobile branded or htc? 2. When you first did the firmware update what was your hboot version?
-----------------------------------------
Friends don't let friends post without searching first!

I put a note of this in op just now, thanks for the warning, I'm trying to figure out why some can do this Cid 11111111 and some can't.
-----------------------------------------
Friends don't let friends post without searching first!

rc420head said:
Bricks can't be recovered (unless you jtag) , you had a soft brick.
I had no problem doing this with s-off and Cid 11111111.
But I remember you from other threads and I have a few questions.
1. Is your phone t-mobile branded or htc? 2. When you first did the firmware update what was your hboot version?
-----------------------------------------
Friends don't let friends post without searching first!
Click to expand...
Click to collapse
Yeah mine was a softbrick. If you stroll over, u can find many people in my queue. May be it is happening only for people who got S-OFF with the Facepalm way. I was on Hboot 1.14 and so a T Mob branded one.
Also you will see a warning in Facepalm thread that flashing firmware on SuperCID phones likey causes a brick.

vatsaman said:
Yeah mine was a softbrick. If you stroll over, u can find many people in my queue. May be it is happening only for people who got S-OFF with the Facepalm way. I was on Hboot 1.14 and so a T Mob branded one.
Also you will see a warning in Facepalm thread that flashing firmware on SuperCID phones likey causes a brick.
Click to expand...
Click to collapse
Something else is going on. I used facepalm, and Cid 11111111 to flash firmware twice now with no issues and started same as you hboot 1.14
-----------------------------------------
Friends don't let friends post without searching first!

thank you!

I'm on Stock JB 4.1.1 and my CID is BM___001, rooted, unlocked BL.
There is no RUU for this CID and only a JB OTA, The radio version and software version match with those of the phone.
my question is: Without S-OFF and SuperCID, Can I use the OTA.zip to be flashed for getting stock ROM? e.g if I am on CM 10.1 and I want to revert back to stock, can I use the OTA.zip?

khan.orak said:
I'm on Stock JB 4.1.1 and my CID is BM___001, rooted, unlocked BL.
There is no RUU for this CID and only a JB OTA, The radio version and software version match with those of the phone.
my question is: Without S-OFF and SuperCID, Can I use the OTA.zip to be flashed for getting stock ROM? e.g if I am on CM 10.1 and I want to revert back to stock, can I use the OTA.zip?
Click to expand...
Click to collapse
I'm not sure if I understand your question. So let me ask a few questions.
What hboot are you on?
What carrier are you using?
Are you wanting to try cm 10.1 and afraid for losing stock?
What is stock just HTC sense 4+ or is there carrier added stuff?

rc420head said:
I'm not sure if I understand your question. So let me ask a few questions.
Click to expand...
Click to collapse
ok I'll try to make it clearer.
What hboot are you on?
Click to expand...
Click to collapse
I'm on hboot 2.15.0000
What carrier are you using?
Click to expand...
Click to collapse
This phone is from Bell Mobility Canada, but I'm not using this carrier.
Are you wanting to try cm 10.1 and afraid for losing stock?
Click to expand...
Click to collapse
Exactly!! this is what I was asking. There isn't any RUU for stock JB 4.1.1, for the CID BM____001.
What is stock just HTC sense 4+ or is there carrier added stuff?
Click to expand...
Click to collapse
Stock sense is 4+ and is heavily bloated. It has got apps like DropBox, Let's Play Golf, Friend Stream, HTC Media Link HD, Polaris Office etc.

khan.orak said:
ok I'll try to make it clearer.
I'm on hboot 2.15.0000
This phone is from Bell Mobility Canada, but I'm not using this carrier.
Exactly!! this is what I was asking. There isn't any RUU for stock JB 4.1.1, for the CID BM____001.
Stock sense is 4+ and is heavily bloated. It has got apps like DropBox, Let's Play Golf, Friend Stream, HTC Media Link HD, Polaris Office etc.
Click to expand...
Click to collapse
OK since your on hboot 2.15 there's no need to upgrade firmware.
Since there is no RUU for stock the next best thing would to to make a back-up of stock using a custom recovery I would recommend twrp 2.3.3 (if you need help with this just ask that's what this thread is for)
Then I would copy the back up to your pc for safe keeping (you might even want to back it up on a cloud too I'd recommend goggle drive or Dropbox)

rc420head said:
OK since your on hboot 2.15 there's no need to upgrade firmware.
Since there is no RUU for stock the next best thing would to to make a back-up of stock using a custom recovery I would recommend twrp 2.3.3 (if you need help with this just ask that's what this thread is for)
Then I would copy the back up to your pc for safe keeping (you might even want to back it up on a cloud too I'd recommend goggle drive or Dropbox)
Click to expand...
Click to collapse
Thanks for the reply, really much appreciated.
I already have rooted the device and custom recovery TWRP 2.5. Though I am considering to downgrade it to 2.3.30. Now I made a backup of stock ROM. (System + Boot Partition)
So is this the only way I can get to stock?
I read somewhere that the following method could be used too(?)
S-OFF ---> Run an older RUU for Bell Mobility (probably ICS RUU) ---> Then update OTA.
Is this valid?

khan.orak said:
S-OFF ---> Run an older RUU for Bell Mobility (probably ICS RUU) ---> Then update OTA.
Is this valid?
Click to expand...
Click to collapse
Yes, if an older RUU is available for your CID just get S-OFF first then use it. Then you'll be able to update via OTA.
Sent from my HTC VLE_U using xda app-developers app

ardax said:
Yes, if an older RUU is available for your CID just get S-OFF first then use it. Then you'll be able to update via OTA.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Big thanks! :good:

vatsaman said:
Yeah mine was a softbrick. If you stroll over, u can find many people in my queue. May be it is happening only for people who got S-OFF with the Facepalm way. I was on Hboot 1.14 and so a T Mob branded one.
Also you will see a warning in Facepalm thread that flashing firmware on SuperCID phones likey causes a brick.
Click to expand...
Click to collapse
This is very interesting to me because I have a unbranded one s from a small spinoff of T-mo in Iowa. I got s-off with facepalm and SuperCID at the same time, then on hboot 1.13. Now recently I upgraded hboot to 2.15 with a euro RUU, soft bricked but was able to recover with only a firmware flash. (details are a bit fuzzy right now) I didn't relock the bootloader, but did install stock recovery. Ever after this stunt I've had tons of problems with radio disconnects. I first thought my problem was hardware, but I just got it back from a very good repair shop and the same thing. Although better on a different carrier, I suspect only because the better carrier has stronger signal. I'm ready to try a older RUU or euro firmware or just about anything, this phone only has service 10% of the time where it used to be 100% right now I'm running the latest Trickdroid 10.3.2 Changing the fast.dormancy=2 helped a tiny bit but it's something more fundamental than that I'm thinking... Sugg anyone??
Prolly should add I'm using the euro 1.15 radio. Thanks
Edit, looks like maybe my problems may only be build prop related, if I change to.til.radio.svn=19 to 5 I get an instant connection, but only G...
ro.ril.hsdpa.category=28
ro.ril.hsupa.category=7
ro.ril.fast.dormancy.rule=0
ro.ril.radio.svn=5
Sent from my HTC One S using xda app-developers app

ardax said:
Yes, if an older RUU is available for your CID just get S-OFF first then use it. Then you'll be able to update via OTA.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Yes this will also work (I was under the impression no ruu's were available)
khan.orak said:
Big thanks! :good:
Click to expand...
Click to collapse

forgiven90 said:
This is very interesting to me because I have a unbranded one s from a small spinoff of T-mo in Iowa. I got s-off with facepalm and SuperCID at the same time, then on hboot 1.13. Now recently I upgraded hboot to 2.15 with a euro RUU, soft bricked but was able to recover with only a firmware flash. (details are a bit fuzzy right now) I didn't relock the bootloader, but did install stock recovery. Ever after this stunt I've had tons of problems with radio disconnects. I first thought my problem was hardware, but I just got it back from a very good repair shop and the same thing. Although better on a different carrier, I suspect only because the better carrier has stronger signal. I'm ready to try a older RUU or euro firmware or just about anything, this phone only has service 10% of the time where it used to be 100% right now I'm running the latest Trickdroid 10.3.2 Changing the fast.dormancy=2 helped a tiny bit but it's something more fundamental than that I'm thinking... Sugg anyone??
Prolly should add I'm using the euro 1.15 radio. Thanks
Edit, looks like maybe my problems may only be build prop related, if I change to.til.radio.svn=19 to 5 I get an instant connection, but only G...
ro.ril.hsdpa.category=28
ro.ril.hsupa.category=7
ro.ril.fast.dormancy.rule=0
ro.ril.radio.svn=5
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Yeah disabling the fast dormancy solved all my problems. :good:

[Q] S-OFF F/W 3.14.531.17 (T-MOB) possible?

I have S4 Ville on firmware 3.14.531.17 and need to know if S-OFF is possible using whatever method available. Moonshine thread states that only 3.14.531.11 (T-MOB) is supported and haven't found any details in the Facepalm thread.
Anyone know for sure?

Bump
Sent from my One S using XDA Premium 4 mobile app

My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.

tivofool said:
My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.
Click to expand...
Click to collapse
Well gave this a shot and after 5 hours I am back on CM10.2 with S-ON and latest firmware still.
Thanks for the help though. Cheers.
Anyone else got any idea?

bump

Look for 3.14.531.11. It should be available somewhere. Lock the phone back and RUU it. Then you can unlock again and S-OFF with moonshine.

evrycard said:
Look for 3.14.531.11. It should be available somewhere. Lock the phone back and RUU it. Then you can unlock again and S-OFF with moonshine.
Click to expand...
Click to collapse
He probably cannot downgrade from *.17 to *.11.
I don't know what parts of the firmware moonshine needs. But you could try downgrade using a OTA or Nandroid.

Same here
I'm pretty much stuck with a One-S Bootloader unlocked with S-on.
I can't find a way to get S-Off. Just googling and throwing prayers in the sky someone develops a way.

pyrocide said:
Well gave this a shot and after 5 hours I am back on CM10.2 with S-ON and latest firmware still.
Thanks for the help though. Cheers.
Anyone else got any idea?
Click to expand...
Click to collapse
If that procedure took you 5 hours... Maybe s-off isn't for you.
Sent from my HTC One S using xda app-developers app

havikx said:
If that procedure took you 5 hours... Maybe s-off isn't for you.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
It took me 5 hours total to begin finding all req's and trying the above method, finding it not to work, redoing the RUU *.17 and getting BACK on CM10.2 and having a phone to make calls with. The method above took maybe 20-30 minutes of double checking and making sure i didn't miss something.

Maybe PM this guy. He posted that it moonshine worked on .17.
http://forum.xda-developers.com/showpost.php?p=45955250&postcount=1091
Ask if he ran moonshine on Linux.

tivofool said:
Maybe PM this guy. He posted that it moonshine worked on .17.
http://forum.xda-developers.com/showpost.php?p=45955250&postcount=1091
Ask if he ran moonshine on Linux.
Click to expand...
Click to collapse
PM'd him for more info. Thanks!

So I was having problems getting s-off as well, eventually I got it done, but it was definitely a big trial and error process.
What I ended up doing was:
1) Get the 3.14.531.11 RUU from http://www.androidruu.com/index.php?developer=Ville (make sure you get the TMOUS one) This link is also provided in the first post in the Android development section
2) I ended up using Moonshine S-Off (http://forum.xda-developers.com/showthread.php?t=2325590) but I needed to use it in conjunction with running it on Ubuntu. Luckily I had a spare hard drive lying around. If you don't, I believe you can run it through the CD as well as long your burn the Ubuntu.iso on a disc. Plug in your phone to the computer and let it do its magic
3) From there, if you wanted to, you can change to SuperCID. Since you have s-off by then, you can change it from the fastboot usb in the bootloader with the line fastboot oem writecid 11111111 (double check, i'm just writing off the top of my head)
4) Then install roms and etc through the usual custom recovery
Note. I tried the Maximus HD, yes it was nice, but it didn't allow me to utilize my phone as a hotspot, so I ended up using the Dark Jelly rom instead. So far it's been very nice. The hotspot works, but the tethering portion is still unavailable. Just my two cents.

I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise

tivofool said:
My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.
Click to expand...
Click to collapse
i can say that this worked for me as well. i didn't relock bootloader before installing the 3.14.531.11 ruu though. still worked for me. also installed moonshine on windows. ( guess i'm lucky )

bnd10706 said:
I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise
Click to expand...
Click to collapse
You saved me so much time. Thanks!

bnd10706 said:
I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise
Click to expand...
Click to collapse
I do not understand meet all the requirement and I run it step by step and still gets stuck in step 3 moonshine I need urgent help, thanks

pyrocide said:
I have S4 Ville on firmware 3.14.531.17 and need to know if S-OFF is possible using whatever method available. Moonshine thread states that only 3.14.531.11 (T-MOB) is supported and haven't found any details in the Facepalm thread.
Anyone know for sure?
Click to expand...
Click to collapse
Test... click here
http://forum.xda-developers.com/showthread.php?t=2569755

[Q]Hboot/Firmware update 2.15 to 2.16 et al.
Sorry wrong thread.

[Q] A quick Q about Evita.

Hi there guys,
Not sure if any of y'all remember way-back-when, but at one point my AT&T One X went into (what seemed like) a bricked state. For 8 months, I didn't touch it, charge it, yada-yada-yada. About 2 weeks ago I decided to give it a go so I charged it for a half hour and the mo'fo' decided to work. I updated my ViperXL ROM to 4.2.0 because I enjoyed it for its features. Now I'm left to ask the question, do I have to update HBOOT to flash a JB 4.3 ROM? I'm still unsure because I feel like I remembered seeing somewhere that your HBOOT has to be a newer version to run 4.3.
Thanks and regards, worldindo1.
NOTE: My current HBOOT version is reading "1.14.002".

Yes you do need to upgrade, it's written in the install instructions for the ROMs. It isn't just the hboot you need to update though, you need to run an RUU to make sure everything gets updated.
Sent from my Evita

timmaaa said:
Yes you do need to upgrade, it's written in the install instructions for the ROMs. It isn't just the hboot you need to update though, you need to run an RUU to make sure everything gets updated.
Sent from my Evita
Click to expand...
Click to collapse
Hey timmaaa,
So just relock bootloader, RUU file, and then unlock it again? Do you know of anyone who has just the firmware upgrade files from the RUU so I can do it from my Linux laptop? Thanks a ton, now I know I wouldn't have any problems or possibly brick my device haha.
Regards, worldindo1.

You need Windows to run an RUU properly, so you'll need to hit up friend to use their PC. You don't need to relock the bootloader as long as you get s-off first so I suggest getting s-off, it's pretty important because s-on + SuperCID + jb RUU = brick.
Sent from my Evita

timmaaa said:
You need Windows to run an RUU properly, so you'll need to hit up friend to use their PC. You don't need to relock the bootloader as long as you get s-off first so I suggest getting s-off, it's pretty important because s-on + SuperCID + jb RUU = brick.
Sent from my Evita
Click to expand...
Click to collapse
Howdy,
I am S-Off thankfully haha. I used XFactor back when it was still current. But I thought the main purpose of an RUU was to execute:
Code:
fastboot oem rebootRUU
fastboot flash zip (firmware).zip
Back when I had done some work with the HTC One V, we used unruu (for Linux) or on the Windows side, explored the RUU's %temp% folder to get the firmware files. Could I still issue those commands safely or have they changed how the RUU works? As well, since I'm S-Off, do I just issue all of the usual commands (minus the "fastboot oem lock") or ? Just making sure to do all of my homework before I jump in haha.
Regards, worldindo1.

Hang on, as far as I know Xfactor was a bootloader unlock exploit, that doesn't give you s-off. There's only one s-off method for our phone and that's the Facepalm method. Having an unlocked bootloader and having s-off are completely different. Can you please post your bootloader details?
Using unruu and pulling the RUU apart and flashing the firmware files is never how an RUU was supposed to be run, nor will it ever be. That's only doing a tiny portion of the job that actually running an RUU properly does. An RUU is an exe file which is meant to be run as an exe file, there is no other way to run it properly other than that. You connect your phone in fastboot mode and run the RUU in Windows and follow the prompts. Like I said though I really need to see your bootloader details (the first four lines) because I'm concerned you have s-off and bootloader unlock confused.
Sent from my Evita

timmaaa said:
Hang on, as far as I know Xfactor was a bootloader unlock exploit, that doesn't give you s-off. There's only one s-off method for our phone and that's the Facepalm method. Having an unlocked bootloader and having s-off are completely different. Can you please post your bootloader details?
Using unruu and pulling the RUU apart and flashing the firmware files is never how an RUU was supposed to be run, nor will it ever be. That's only doing a tiny portion of the job that actually running an RUU properly does. An RUU is an exe file which is meant to be run as an exe file, there is no other way to run it properly other than that. You connect your phone in fastboot mode and run the RUU in Windows and follow the prompts. Like I said though I really need to see your bootloader details (the first four lines) because I'm concerned you have s-off and bootloader unlock confused.
Sent from my Evita
Click to expand...
Click to collapse
Sorry about that my mind just drew a blank. I mixed up xfactor with facepalm haha. Yeah I'm s-off and bootunlocked.
Sent from Marianas Trench.