Related
UPDATE: Apparently it is only possible to change the CID with S-ON if your current CID is SuperCID.
*issue closed*
I had used Revolutionary to de-brand my phone. First S-OFF, then SuperCID, then a stock unbranded ROM, then back to S-ON.
I wasn't getting the OTA to 2.3.4 here in The Netherlands, so I changed my CID to HTC__E11, which is the CID for an unbranded Sensation in The Netherlands. Lo and behold, I got the OTA immediately.
Interesting to note, I was able to change the CID using "fastboot oem writecid HTC__E11" with S-ON. Someone else was able to do exactly the same thing so it's confirmed to work.
Now that I have upgraded to 2.3.4 and have my CID set to HTC__E11, this no longer works for me. However I'm wondering if it *does* work for people still on 2.3.3, or if it only worked for me because I was already SuperCID. I wonder if others who are still on 2.3.3 are able to use "fastboot oem writecid 11111111" with S-ON (i.e. without using Revolutionary).
So, using adb tools on a stock ROM:
NOTE: If you test this you do so at your own risk.
0. download and unzip adb tools to a folder. make sure HTC Sync is not running (uninstall, or just exit/kill the application).
1. open command prompt and "cd" your adb folder
2. ensure your phone is switched on (regular home screen) and connect it by USB in charging mode (ensure usb debugging is on settings).
3. enter the command "adb devices". This is to confirm your phone is connected. (It should come back with list of devices attached and your serial number)
4. enter the command "adb reboot-bootloader". (nothing further required device WILL reboot in bootloader)
5. enter the command "fastboot oem writecid 11111111"
6. enter the command "fastboot reboot-bootloader (Wait for it to reboot the bootloader)
7. enter the command "fastboot getvar cid" [it should confirm your CID is 11111111]
8. enter the command "fastboot reboot"
9. you should now be able to flash any stock ROM you like.
NOTE: Please DO NOT change your CID to HTC__E11 unless you are in The Netherlands. HTC__E11 is the CID for an unbranded Sensation in The Netherlands. If you are in a different country, check for the appropriate CID here: http://forum.xda-developers.com/showthread.php?t=1195475&page=3.
I've already de-branded my phone, but I wonder if others are able to using "fastboot oem writecid 11111111" without using Revolutionary.
Click to expand...
Click to collapse
Yes, I have. In fact I believe that method is in one of the tutorials here.
Here is a link that describes it: http://forum.xda-developers.com/showthread.php?t=1192300
kmdub said:
Yes, I have. In fact I believe that method is in one of the tutorials here.
Here is a link that describes it: http://forum.xda-developers.com/showthread.php?t=1192300
Click to expand...
Click to collapse
No, that tutorial uses Revolutionary first to go from S-ON to S-OFF before changing the CID. I was able to change my CID with S-ON.
so I'm changing my cid to 11111111?
not HTC__E11?
zahashingo123 said:
so I'm changing my cid to 11111111?
not HTC__E11?
Click to expand...
Click to collapse
11111111 is the SuperCID. HTC__E11 is the CID for unbranded Sensations in The Netherlands. If you don't use the SuperCID, you may want to refer to http://forum.xda-developers.com/showthread.php?t=1195475&page=3 for a list of CIDs.
I changed to the SuperCID using Revolutionary to first get S-OFF. Then I set S-ON. But even with S-ON, I was still able to change my CID (I changed it to HTC__E11 in order to receive the OTA to 2.3.4.).
So what I'm wondering is if people with 2.3.3 and S-ON are able to change their CID to the SuperCID 11111111, without first using Revolutionary to change to S-OFF.
Ok, I must have misunderstood your question. It seems as if you have clarified your question since your original post. I just thought you were asking if one could write the CID without Revolutionary. My bad. FYI, I have not tried what you are asking.
I changed to the SuperCID using Revolutionary to first get S-OFF. Then I set S-ON.
Click to expand...
Click to collapse
A statement like this, though, I don't really understand. Two questions come to mind: 1) How did you set S-ON? and 2) Were you able to confirm that you wrote a new CID with S-ON, or did you just not get an error message?
kmdub said:
Ok, I must have misunderstood your question. It seems as if you have clarified your question since your original post. I just thought you were asking if one could write the CID without Revolutionary. My bad. FYI, I have not tried what you are asking.
A statement like this, though, I don't really understand. Two questions come to mind: 1) How did you set S-ON? and 2) Were you able to confirm that you wrote a new CID with S-ON, or did you just not get an error message?
Click to expand...
Click to collapse
I set S-ON using the instructions on how to set S-ON here http://forum.xda-developers.com/showthread.php?t=1192300 and I confirmed it during reboot, the text "S-ON" was back on the boot screen.
I wrote the new CID with S-ON, then confirmed it by rebooting and running the command "fastboot getvar cid", which gave me the phone's CID, which indeed was the new CID I'd written. In addition, with the new CID (unbranded Dutch, instead of SuperCID), I immediately got the OTA to 2.3.4.
Someone need to test this with a stock phone!
Or try to set secureflag to 1 maybe its not really changed ...
xtcislove said:
Someone need to test this with a stock phone!
Click to expand...
Click to collapse
That's exactly what I'm asking people to do.
xtcislove said:
Or try to set secureflag to 1 maybe its not really changed ...
Click to expand...
Click to collapse
What's your problem, can't you read? I wrote already, the phone reports "S-ON" in the boot screen, and after a reboot, it still reports the new CID, and after setting the new CID, I got the Netherlands OTA immediately.
I tried it with stock s-on phone and it doesn't work.
Code:
C:\AndroidSDK\tools>fastboot oem writecid 11111111
...
(bootloader) pyramid_init_sd, SD card already power on
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 0.172s]
finished. total time: 0.172s
It still reports same cid.
supendal said:
I tried it with stock s-on phone and it doesn't work.
It still reports same cid.
Click to expand...
Click to collapse
Thanks for testing this - just to confirm, you tested with 2.3.3 and not 2.3.4, right?
If so, then it seems to imply that you can change the CID even with S-ON but only if you currently have SuperCID.
Then I have no idea. I would not think one could write a new CID with S-ON, regardless of the ROM. However, you have tried it and claim it works, so someone with more knowledge will have to explain why...lol
I notice in the tutorial it says "secureflag 3," which at least gives you S-ON displayed, and perhaps does set the security back on. I wonder what 0,1,and 2 do, though. Is it 0,1,2, or 3 on stock phone with S-ON?
sowen222 said:
Thanks for testing this - just to confirm, you tested with 2.3.3 and not 2.3.4, right?
Click to expand...
Click to collapse
Yes, tested on stock s-on phone and stock 2.3.3 rom. 2.3.4 Ota update is still not available here.
well i do also have s-on and managed to change cid to HTC__E11 with adb and also like the OP can't seem to change it back to what it was (stock sensation with 1.50...rom) does the cid mathers in terms of warranty and ota updates??? (i'm in the netherlands)
regards
edit:well OTA updates do work on my side but still no luck changing the CID again.
nobody here that can decifer this one??
I have a sendation xe with hboot 1.18 and s-on.
I used the commands to change CID from HTC__038 to HTC__001.
I still don't receive the OTA update on my phone though.
The phone was bought from Hong Kong but from using the CID Getter app it shows CID at the top as HTC__001 now but when you scroll through the data there are still reference to it being an indian phone.
I am looking to change it to stock Euro gingerbread with CID 001 so that I can receive the OTA ICS update.
I can't use revolutionary to change to S-OFF as always fails. I can't install the RUU for euro GB as it gives an error when I try to run it.
Not having any joy asking people for help so far either.
I have a sensation thats giving me two CID numbers.
If i use fastboot commands i get 11111111.
If i use CID getter i get VODAP001.
Phone is s-off, rooted and unlocked.
How can i get these the same?
The phone is downloading an ICS update but not installing it.
I've seen the same thing, your correct CID is the one you got through adb. CID getter for some reason throws up CID information stored elsewhere so you generally end up getting the CID the phone came with.
Given that you are SuperCID, why won't ICS install? What error(s) are you seeing?
goatee84 said:
I've seen the same thing, your correct CID is the one you got through adb. CID getter for some reason throws up CID information stored elsewhere so you generally end up getting the CID the phone came with.
Given that you are SuperCID, why won't ICS install? What error(s) are you seeing?
Click to expand...
Click to collapse
More accurately... Your correct CID is the one you get through:
Code:
fastboot getvar cid
If I use adb shell command:
Code:
getprop ro.cid
Then I get my original CID "T-MOB010"...
To the OP:
Go to your directory where adb and fastboot are, and type the following:
Code:
adb reboot bootloader
wait for bootloader to boot
Code:
fastboot oem writecid VODAP001
wait for it to flash
Code:
fastboot reboot-bootloader
wait for bootloader to boot
Code:
fastboot getvar cid
verify that the output is "VODAP001"
Code:
fastboot reboot
wait for device to reboot and you should be able to install your update if you're on an unaltered stock ROM...
Thanks for the replies.
It is the rom that came on the phone but i have removed some of the app's that Vodaphone pre-install, will this affect the up date?
Part of the error message was a problem with flickr which i did remove.
I would like a T-mobile ICS stock rom that is rooted as that is my provider, any suggestions?
I tried updating to 3.32 firmware but was getting boot loops, so downgraded again.
If you apply SuperCID, your phone has 2 CIDs:
the actual CID, which is 11111111
and the backup CID, which is a backup of the
cid the phone was before(shipped).
The backup CID is stored in the misc partition,
and i havent tried yet, but there are following fastboot cmds:
fastboot oem erasebcid
fastboot oem readbcid
fastboot oem writebcid
I think theyre the appropriate cmds for handling the bcid.
After deleting the backup CID the only CID left is the (main) CID.
BTT: If you want to apply a ICS RUU, I think you have to change your CID back
to stock, because the RUU checks for a T-Mob phone, which your phone isnt if
you have SuperCID ;D
After the RUU, you can SuperCID again.
Edit:
Have not read the first time:
If you want to install a T-Mobile RUU on a Vodaphone Device,
you have to set one of the following CIDs, matching the RUU best:
TMA: T-MOB102
TMCZ: T-MOB004
TMD: T-MOB101
TMH: T-MOB007
TMHR: T-MOB006
TMMK: T-MOBL11
TMNL: T-MOB003
TMSK: T-MOB008
TMUK: T-MOB005
TMUS: T-MOB010
Greetz
criestr
ann-dr01d said:
Thanks for the replies.
It is the rom that came on the phone but i have removed some of the app's that Vodaphone pre-install, will this affect the up date?
Part of the error message was a problem with flickr which i did remove.
I would like a T-mobile ICS stock rom that is rooted as that is my provider, any suggestions?
I tried updating to 3.32 firmware but was getting boot loops, so downgraded again.
Click to expand...
Click to collapse
Your stock ROM must be unaltered... Restore those apps if you still have them.
Please help me, I'm desperate.
- I want to install MaximusHD ROM.
- I have HBOOT 2.15.
- I unlocked bootloader via HTCDev.
- I have CM10.1 running on my phone.
I tried this method to get Supercid, because, as far as I know, you need to have Supercid before getting S-OFF. (Please correct me if I'm wrong)
This: http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
I haven't even tried using the facepalm method because I can't get supercid.
After I followed all the steps correctly, I run command "fastboot oem readcid" and still get the T-MOB010 CID.
I repeated the whole process 3 times, making perfectly sure I didn't make any mistake and still, can't get supercid 11111111.
I tried using moonshine method too, but when I run distiller.exe at the end it says read and try again or something. So I just cant get S-OFF or supercid.
Please tell me how can I get MaximusHD Rom working on my phone! Please! :/
Is there anyone who can help me S-off my HTC device?
Sent from my One S using xda app-developers app
rolo143 said:
Is there anyone who can help me S-off my HTC device?
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Im in the same boat, Ive found my partition is write protected and cant find any other method to do it, I have tried both moonshine (my device isnt supported) and facepalm (protected partition) methods. Ive given up and stuck with MagioRom, which is like MaximusRom, but not so stable currently, but saying that the last RC5 of Magio is stable for me so far.
rolo143 said:
Please help me, I'm desperate.
- I want to install MaximusHD ROM.
- I have HBOOT 2.15.
- I unlocked bootloader via HTCDev.
- I have CM10.1 running on my phone.
I tried this method to get Supercid, because, as far as I know, you need to have Supercid before getting S-OFF. (Please correct me if I'm wrong)
This: http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
I haven't even tried using the facepalm method because I can't get supercid.
After I followed all the steps correctly, I run command "fastboot oem readcid" and still get the T-MOB010 CID.
I repeated the whole process 3 times, making perfectly sure I didn't make any mistake and still, can't get supercid 11111111.
I tried using moonshine method too, but when I run distiller.exe at the end it says read and try again or something. So I just cant get S-OFF or supercid.
Please tell me how can I get MaximusHD Rom working on my phone! Please! :/
Click to expand...
Click to collapse
Hi,
can you provide a log (or screenshots) of all the commands you enter and the files you push / pull?
Have you tried Moonshine S-OFF?
I can't. I didn't take screenshots, but believe me, I follow exactly the steps in the above mentioned thread to get supercid. But it just didn't stick. I keep getting T-MOB010 cid.
I think there's nothing I can do because my phone isn't supported by moonshine (I think) and my hboot is 2.15
Anyway I want to try MagioROM. Is it stable now or will it give me constant reboots?
Sent from my One S using xda app-developers app
Try to install official RUU to your phone. Before that you need reblocked your bootloader. After installation unlocked bootloader again and try get S-OFF.
Sent from my HTC One S using XDA Premium 4 mobile app
Malexion said:
Try to install official RUU to your phone. Before that you need reblocked your bootloader. After installation unlocked bootloader again and try get S-OFF.
Click to expand...
Click to collapse
+1 on Malexion's suggestion.
Being on HBOOT 2.15 is not enough. For Moonshine to work, you need to be on one of the supported firmwares listed at the top of the Moonshine OP:
3.14.531.11 (T-MOB)
3.16.666.9 (BM)
3.16.111.10 (TMO_DE)
3.16.661.4 (Telus)
Click to expand...
Click to collapse
If you have an RUU available for your carrier that's on one of those, it can be done..
I'm on T-Mobile US, and had accepted the OTA JB update to 3.14.531.17 before deciding to go for S-OFF. That little OTA update from .11 to .17 apparently includes some cute write protection that doesn't allow for SuperCID (among other things). As with you then, Facepalm was out of the question for me.
So I turned to Moonshine, which worked after jumping through the right hoops:
Downloaded supported RUU
Verified that RUU matched my carrier, HBOOT and baseband
Locked bootloader
Flashed RUU (in my case, I was going back to 3.14.531.11 (T-MOB))
Unlocked bootloader (you'll need to get a new unlock key from htcdev)
Ran Moonshine
Moonshine worked on the first try for me, but from reading the posts, it's clearly not as easy for everyone (especially on Windows for whatever reason).
Hopefully that helps, but happy to provide more info if you have questions.
Good luck!
---------- Post added at 10:23 PM ---------- Previous post was at 10:17 PM ----------
rolo143 said:
I tried this method to get Supercid, because, as far as I know, you need to have Supercid before getting S-OFF. (Please correct me if I'm wrong)
Click to expand...
Click to collapse
Also, forgot to mention that Moonshine does not require SuperCID. I never had it and still don't. (If Moonshine S-OFF works for you, it's easy to get SuperCID if you really need it -- which I don't, so I haven't bothered yet).
T-Mobile
I'm also on T-Mobile and I wish I saw your post before I "upgraded" from .11 to .17. Quick question for you, because I just got this phone and don't know a whole lot about it. I've heard that HTC and/or Google released a jelly bean update that was horrible on the battery, and had to follow up with an update.
Is the .11 update the battery draining bad update? Is the battery drain problem something that can be fixed via a rom, rather than the update?
I guess that was more than one question, but any answers would be much appreciated. Also, if you could comment on your battery life since moving down to .11....
Yes, the .11 OTA was the first JB rollout for this phone, and the .17 OTA was released soon after to correct the battery drain issue.
I was only on the older .11 firmware for a few days before I flashed a new ROM, but it seemed pretty brutal. I'm still new to flashing ROMs, though, and I've read that it can take a new ROM a little time to optimize battery life... Not sure if that also applies to RUUs.
But it was bad enough that I would recommend only flashing the .11 firmware if you intend to switch to another ROM.
Anyhow, I flashed AOSPA 3+ a few days later and love it. A stable port, fast and fun to play with the hybrid engine. Battery life on PA has been good so far, seems on par or better than the .17 firmware in my case.
Hope that helps!
---------- Post added at 02:08 AM ---------- Previous post was at 01:50 AM ----------
Clarification: I would only bother with the older firmware as an interim step to (a) getting Moonshine S-OFF before flashing a new ROM, or (b) going back to stock and eventually the later .17 version via OTA.
(If you ever go back to stock, be *very* careful to read up on proper procedure before ever allowing a carrier OTA once you've played around with your phone... There are one or two cases where a carrier OTA is an instant brick scenario if you don't take the proper precautions).
When I type on cmd command:
"fastboot getvar all"
this is what appears:
Code:
version: 0.5
version-bootloader: 2.15.0000
version-baseband: 1.13.50.05.31
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: HT242W420470
imei: 359902047827302
product: vle
platform: HBOOT-8960
modelid: PJ4011000
cidnum: T-MOB010
battery-status: good
battery-voltage: 3964mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-64bedd38
hbootpreupdate: 11
gencheckpt: 0
Now, from here... Can someone please tell me how to find my corresponding RUU file? How can I install it? Do I need S-OFF for that? Please help... I don't really understand how can I achieve S-OFF in my HTC One S and I read a LOT of guides already.... Just don't know what can I do so I can install MaximusHD Rom and stick with it.
@rolo143: I'll pull together my exact steps for you when I'm in front of my computer again... In the meantime, to stay safe I would remove your serial number and imei from your last post.
Flashing the RUU so you can run Moonshine S-OFF
1: VERIFY ADB/FASTBOOT ENVIRONMENT & HTC DRIVERS ARE WORKING
Boot phone into fastboot mode (boot into bootloader, select "fastboot" from hboot menu).
Connect to PC (phone will now show "fastboot USB" highlighted), open command prompt and enter:
fastboot devices
It should return "[serial number] fastboot" if it's working properly.
You've already entered fastboot getvar all to get the info you need to get the correct RUU.
Click to expand...
Click to collapse
2: MAKE A NANDROID BACKUP
Use your custom recovery (TWRP or ClockworkMod) to make a backup of your device.
Put a copy of your nandroid onto your PC for safe keeping.
Click to expand...
Click to collapse
3: DOWNLOAD THE APPROPRIATE RUU
I got my RUU from this xda thread:
Since you're not S-OFF and SuperCID, you have to use an RUU that matches your carrier, hboot and baseband (radio).
Based upon your fastboot getvar all results...
Your carrier: T-MOB010 (cid) = TMUS (T-Mobile US carrier) ... I used this cid list to double-check this.
Your current hboot: 2.15, which will work with the JB 3.14.531.11 RUU you're going to flash, so you're good there.
Your current radio: 1.13.50.05.31.
I downloaded the matching RUU (you'll be using the same that I did):
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release... (truncated rest of filename).
Happily, this RUU is one of the four firmware versions supported by Moonshine S-OFF.
Click to expand...
Click to collapse
4. LOCK BOOTLOADER
Put phone into bootloader mode, connect to PC, open command prompt and enter:
fastboot devices
If it shows your serial number again, then enter:
fastboot oem lock
Your bootloader will now be locked and the phone may reboot back into bootloader. Leave the phone connected to the PC.
Click to expand...
Click to collapse
5. RUN THE RUU
Leave phone in fastboot mode (if it rebooted to bootloader you may need to select "fastboot" again). You should see "Fastboot USB" highlighted on the phone.
On your PC, run the RUU (.exe) that you downloaded. Give it a few minutes after you run it, as it took mine a while to actually look like it was doing anything.
Once it finally loads, you'll get a window that gives you a series of instructions. Follow them and then let it do it's thing.
Do NOT unplug your phone from the PC (I wouldn't touch the thing, frankly) until it reboots the phone automatically.
Once your phone reboots to system, it'll be running 3.14.531.11 Jellybean!
Click to expand...
Click to collapse
5. MOONSHINE S-OFF
Revisit the Moonshine S-OFF thread and follow the instructions very deliberately. Now that you're on a supported firmware, it should work.
---- EDIT ---- After you successfully run the RUU, you'll need to unlock your bootloader again before running Moonshine. You won't be able to use your old unlock .bin file, so you'll need to request a new one via htcdev. If you want to brush up on that, follow the unlock instructions on this xda tutorial thread.
Good luck!
Click to expand...
Click to collapse
Good post
When I did moonshine, I eventually put mint linux on a laptop just to get it to work. Where there is a will there is a way.
Thanks... I've learned a ton over the last few months from everyone being so supportive here. Want to give back a little where I can.
I tried and tried to set up Ubuntu Linux, but I simply could not get it to play nicely with my MacBook Pro. For my new Android obsession, I'm running Windows through Parallels, and I didn't want to use that for Moonshine since they don't officially support VMs. But the Ubuntu install on my particular hardware just kept throwing up too many roadblocks. Thankfully, I was able to pretty carefully manage my HTC driver setup on the Mac and in the VM, and once I figured out the right combo, my adb/fastboot connections have been rock solid. So I took a deep breath and gave Moonshine a go through Parallels, and it took on the first try. Go figure, after all of my toying around with Linux.
super cid
hi
my one s ville is for TIM Italya operator
when i want to perform super cid ,my cid is TIM--401
I change it to 11111111 but it doesnt work and my cid again is TIM--401
WHAT should i do for super cid my phone????
2k10GT said:
Flashing the RUU so you can run Moonshine S-OFF
Click to expand...
Click to collapse
Great post and thank you for the effort to write the detailed instructions. I was able to successfully do the moonshine s-off
rolo143 said:
Please help me, I'm desperate.
- I want to install MaximusHD ROM.
- I have HBOOT 2.15.
- I unlocked bootloader via HTCDev.
- I have CM10.1 running on my phone.
I tried this method to get Supercid, because, as far as I know, you need to have Supercid before getting S-OFF. (Please correct me if I'm wrong)
This: http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
I haven't even tried using the facepalm method because I can't get supercid.
After I followed all the steps correctly, I run command "fastboot oem readcid" and still get the T-MOB010 CID.
I repeated the whole process 3 times, making perfectly sure I didn't make any mistake and still, can't get supercid 11111111.
I tried using moonshine method too, but when I run distiller.exe at the end it says read and try again or something. So I just cant get S-OFF or supercid.
Please tell me how can I get MaximusHD Rom working on my phone! Please! :/
Click to expand...
Click to collapse
If it works in windows moonshine I did this tutorial but in spanish to help all who have problems to make the soff
http://www.taringa.net/posts/celulares/17401702/Como-hacer-soff-en-HTC-one-s-3-14-531-17RD.html
2k10GT said:
Flashing the RUU so you can run Moonshine S-OFF
Click to expand...
Click to collapse
Thanks for that concise summary. It helped me when I finally decided to get around to get S-OFF on my phone (flashing boot.img with every ROM switch/update/downgrade/etc. got tiresome).
Hello everybody!
I am can't get SuperCID in my HTC One S. In this time i have in phone root, unlock from htcdev and it's all. Trying with adb command receive T-MOB010 Cid, Moonshine after 3'd reboot stopping in '.........' in Fastboot. This '.......' points I am wait for 30 min and after disconnecting phone it still writing in comp screen. RUU from TMOB supported by Moonshine is installed to phone. What I wrong doing. *wall*. Help me, please!
> tried this method to get Supercid, because, as far as I know, you need to have Supercid before getting S-OFF. (Please correct me if I'm wrong)
Wait. You do not have to have SuperCID to get S-OFF.
Try moonshine. Some of us couldn't get S-OFF any other way. Also, I had to use an Ubuntu Live CD - Windows didn't work for me no matter what I tried. It kept getting stuck at "..........."
When I used the Ubuntu live CD it went right through.
UPDATE 30/11/2013:
This thread describes my efforts in updating my unlocked One S to a hboot higher than 2.13. The phone had an H3G CID but non of the RUU's (see thread) worked. For me the solution was to Super CID and S-OFF the phone. Iḿ now on hboot 2.16.
END UPDATE
After more than two years of using Android (Legend, Desire S) phones and rooting them, I now have to register to be able to ask a question on this great forum.
Yesterday I obtained a One S. It is a UK model (not sim-locked to a carrier). I unlocked the bootloader almost immediatly with the intention of running a 4.3 or 4.4 based ROM (cyanogenmod or codename lungo). Here are some of the getvar details:
Code:
version: 0.5
version-bootloader: 2.13.0000
version-baseband: 1.11.50.05.28
version-misc: PVT SHIP S-ON
cidnum: H3G__001
boot-mode: FASTBOOT
Both cyanogen 4.4 and lungo ended in a bootloop and I figured it had to do with the hboot version. Self assured as I was I did not do a nandroid backup in twrp when flashing cyanogen and lungo and I ended up looking for a rom that would boot. I was succesful with MagioRom_ONE_S_RC6. From that I intended to use a RUU to update my hboot. I tried several (including both the H3G's) from this resource. All ended up in errors (131, 132, 155, 170 and probably some more). After reading some threads I relocked the bootloader and flashed stock recovery. All to no avail, no RUU will install. After reading a bit more I concluded that SuperCID was my best option of getting my brand new One S to a higher hboot version. I decided to go with this tutorial, but I ended up in another frustration: adb is not working for me in both windows (7) and linux (ubuntu). I reinstall the drivers (under windows) and tried some other things, but nothing works.
This is where I am now. I hope someone is willing to help. I tried to be as complete in describing the things I tried and the information I have, but I'd be happy to provide any additional info.
Getting custom roms on the legend and desire s was a lot easier.
First I do not own a UK version One S, I have the TMOUS but these are some tips that I used to help get my phone back from a non booting state.
Couple things,
Make absolutely sure this is a Ville not a VilleC2 (aka S3 One S)
Are you at all able to boot the phone to a recovery program (TWRP/CWM etc)?
Ensure that you have followed these instructions to get adb and fastboot to work. Use the Unlock section. Its best to make sure you can fastboot or at least adb before doing anything with the phone.
If you can get to fastboot (Power and Vol Down button), connect your phone and run the command "fastboot devices" post output - keep in mind command shell has to be at the adb directory most of the time C:\adb or something similar.
Make sure you have the latest driver installed and to remove (completely uninstall it) HTC Sync or Sync Manager. Not needed if you don't keep the stock ROM on your phone IMO. If you are unsure, remove all HTC software and just reinstall the driver.
Make sure you are running the right RUU for your specific device. What carrier was this phone for when it was purchased? Assuming it is H3G this is the latest RUU available for that particular OneS. You will have to run either the same version F/W or later RUU, you cannot go backwards.
Once we get the phone back to stock rom. Then start over by unlocking bootloader and getting S-OFF THEN start to flash roms.
In order to run CM11 Beta you need to have l a certain recovery installed + a few other things. I think it would be best if you can get back on CM10.1.3 Stable first then attempt to go to CM11.
TL;DR
Verify carrier and version of phone
Lock Bootloader if not already done
Download and run carrier specific RUU while in fastboot mode (power +vol down)
Unlock Bootloader
S-OFF
Flash rom
@pyrocide
Thanks for the reply. I've been working through your post. First I wanna point out that the phone is in a working state know running the MagioRom and I can boot into TWRP recovery.
Here is the output for fastboot devices:
Code:
SH24PW402945 fastboot
I'm sure it is an s4. It is says Z520e and 1.5 ghz on the box. I got the phone from ebay, so I'm not 100% which carrier it was on, but there was a T-Mobile sim still in the phone :silly:. The CID reads H3G though and the phone is not locked to a carrier/network since my giffgaff sim works fine.
I got adb to work. Thanks for that :good:.
I relocked the bootloader with fastboot oem lock (it know says 'relocked'). Running the suggested RUU ends in an error 155 during the veryfiying signature step.
And you ran the RUU while you were in fastboot usb mode?
based on Google
"ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again."
So the RUU is wrong, we need to find out specifically what version of OneS it is.
run this command while in fasboot usb mode
Code:
fastboot getvar all
post modelid: XXXXXXXXXX
The output of that:
Code:
modelid: PJ4010000
http://androidforums.appforerunner....ed-problem-restoring-ruu-error-131-151-a.html
Guy had the same problem and same modelid
Used this RUU and was able to go back to stock.
Hopefully this works.
Thanks for the help. Appreciate it.
That RUU ended in an 131 error, unfortunately.
H2Oxide said:
Thanks for the help. Appreciate it.
That RUU ended in an 131 error, unfortunately.
Click to expand...
Click to collapse
At this point i would suggest doing all Euro RUUs. That should have worked considering the modelid is the same for that guy and it worked. Sorry man but I don't know what else to suggest other than to do each RUU. If none of them work then something is definitely wrong.
pyrocide said:
At this point i would suggest doing all Euro RUUs. That should have worked considering the modelid is the same for that guy and it worked. Sorry man but I don't know what else to suggest other than to do each RUU. If none of them work then something is definitely wrong.
Click to expand...
Click to collapse
Would I need to reflash a/the stock recovery to make for a successful RUU flash?
The list of the RUU's I tried. Non worked... Really frustrating.
Code:
RUU_Ville_U_BM_1.70.666.1_R_Radio_0.16.31501S.06_3_10.20.31501S.09L_release_255222_signed.exe
RUU_Ville_U_BM_1.84.666.9_Radio_0.17.31501S.10_2_10.27.31501S.10L_release_265369_signed.exe
RUU_Ville_U_H3G_UK_1.53.771.4_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251870_signed.exe
RUU_Ville_U_H3G_UK_1.78.771.5_Radio_0.16.31501S.19_2_10.23.31501S.10L_release_258982_signed.exe
RUU_Ville_U_HTC_Europe_1.09.401.1_R_Radio_0.14.3059.14_2_release_243825_signed.exe
RUU_Ville_U_HTC_Europe_1.47.401.1_Radio_0.15.31501S.13_3_10.08.31501S.04L_release_250115_signed.exe
RUU_Ville_U_HTC_Europe_1.53.401.2_Radio_0.15.31501S.19_10.12.31501S.06L_release_251412_signed.exe
RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed.exe
RUU_Ville_U_ICS_40_S_BM_2.40.666.1_Radio_1.09ts.50.02.04_10.08g.50.04L_release_280275_signed.exe
RUU_Ville_U_ICS_40_S_HTC_Europe_2.21.401.10_Radio_1.06s.50.02.27_2_10.08.50.04L__release_271119_signed.exe
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5.exe
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed.exe
RUU_Ville_U_ICS_40_S_TMOUS_2.35.531.7_Radio_1.08ts.50.02.16_10.08e.50.04L_release_279577_signed.exe
RUU_Ville_U_ICS_40_S_Vodafone_UK_2.38.161.6_Radio_1.08es.50.02.21_10.09c.50.04L_release_280400_signed.exe
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2.exe
RUU_Ville_U_O2_UK_1.78.206.4_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258707_signed.exe
RUU_Ville_U_TMO_DE_1.77.111.5_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_259421_signed.exe
RUU_Ville_U_TMOUS_1.53.531.16_Radio_0.16.31501S.02_10.18.31501S.08L_release_262073_signed.exe
RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S.16_2_10.22.31501S.10L_release_263233_signed.exe
RUU_Ville_U_Vodafone_UK_1.53.161.3_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251482_signed.exe
RUU_Ville_U_Vodafone_UK_1.78.161.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258386_signed.exe
H2Oxide said:
Would I need to reflash a/the stock recovery to make for a successful RUU flash?
Click to expand...
Click to collapse
No, running the RUU erases custom recovery & flashes stock recovery.
Did all of the downloads MD5 checkout correctly?
Also, just to make sure we are ruling everything out. Did you run the RUU by double clicking or right clicking and Run as Administrator? If you just did it by double clicking rerun the one I posted that fixed the other guys issue by using Run as Administrator. Again be sure to be in fastboot usb mode and that "fastboot devices" command shows your device in the output. Make sure you use a usb 2.0 port in case of compatibility issues and the cable that came with the phone if possible.
pyrocide said:
No, running the RUU erases custom recovery & flashes stock recovery.
Did all of the downloads MD5 checkout correctly?
Also, just to make sure we are ruling everything out. Did you run the RUU by double clicking or right clicking and Run as Administrator? If you just did it by double clicking rerun the one I posted that fixed the other guys issue by using Run as Administrator. Again be sure to be in fastboot usb mode and that "fastboot devices" command shows your device in the output. Make sure you use a usb 2.0 port in case of compatibility issues and the cable that came with the phone if possible.
Click to expand...
Click to collapse
I used another laptop. Running the suggested RUU again resulted in the same 131 error. I ran as admin and did an md5 check. I'd say the other RUU's will also result in an error again...
H2Oxide said:
I used another laptop. Running the suggested RUU again resulted in the same 131 error. I ran as admin and did an md5 check. I'd say the other RUU's will also result in an error again...
Click to expand...
Click to collapse
Did some digging.
Error 155 - usually wrong recovery.img /wrong boot.img
Error 140 - wrong bootloader / bootloader unlocked
Error 131 - wrong RUU for your device
So, if one is giving you the 155 error then try with the stock recovery and do the RUU.
The phone does say relocked in bootloader right? Try doing fastboot oem lock again and run the RUU that gave you the 155 error.
Wow, that still didn't work.
So I flashed stock recovery and relocked the bootloader. Then I tried three RUU's, both the H3G RUU's and the HTC Europe RUU mentoined before. The H3G's ended up in a 155 error, the HTC Europe in a 131.
So, still no succes. This is getting annoying, right... ? Any other suggestions besides flushing the One S down the toilet?
Regards.
H2Oxide said:
Wow, that still didn't work.
So I flashed stock recovery and relocked the bootloader. Then I tried three RUU's, both the H3G RUU's and the HTC Europe RUU mentoined before. The H3G's ended up in a 155 error, the HTC Europe in a 131.
So, still no succes. This is getting annoying, right... ? Any other suggestions besides flushing the One S down the toilet?
Regards.
Click to expand...
Click to collapse
Im at a loss man. At this point I would email HTC with the getvar all info and see what they say and which RUU they give you to try. If nothing else itll help narrow down exactly what model phone it is.
pyrocide said:
Im at a loss man. At this point I would email HTC with the getvar all info and see what they say and which RUU they give you to try. If nothing else itll help narrow down exactly what model phone it is.
Click to expand...
Click to collapse
Just a thought. Since the 155 error could point to both a wrong recovery.img or a wrong boot.img, I could try flashing another (stock) boot.img. Maybe the custom rom's boot.img is in the way. So what boot.img would I need?
So I did that. I extracted the boot.img from de H3G RUU and flashed it. I also extracted the recovery and flashed that. I then tried different scenario's with the H3G, the HTC Europe and the O2 UK RUU's. Non worked. The H3G ended up in 155, the others in 131.
Anyone else any ideas on this besides emailing HTC?
H2Oxide said:
Just a thought. Since the 155 error could point to both a wrong recovery.img or a wrong boot.img, I could try flashing another (stock) boot.img. Maybe the custom rom's boot.img is in the way. So what boot.img would I need?
Click to expand...
Click to collapse
You could try to decompile the 155 error exe and fastboot flash boot boot.img but I am very nervous that might screw something up. I still suggest contacting HTC directly to have their input on what exactly RUU is needed and if you do have the right one, why it is not working.
Code:
<T133845><DEBUG><OUT>FAILED (remote: 44 hboot version check fail)</OUT>
Got the line above out the RUU log files. This is the 155 error RUU.
This raises two question:
Is it possible to get the expected hboot version number out the decompiled RUU (decompiled = the stuff placed in user/temp)?
Is it possible to down/upgrade hboot with any of the hboot versions posted here or would I run the risk of softbricking my One S then?
Don't flash any of that hboots. You will brick.
Just try to s-off, follow facepalm method in dev forum.
After that you can flash any ruu.
Sent from my HTC One S using Tapatalk
So I am a little (a lot) scared to touch my new phone.
I recently acquired an AT&T One X, and it is currently rooted, and running CleanROM 6.5.0. I don't have the history of the device, so I am not sure how its previous owner got it to here, and what the safest steps would be to get it back to pure stock.
I am not worried about resetting the tamper indication or warranty issues. I just would like to get back to the stock AT&T software, and then I can go from there getting it where I want it.
The phone has TWRP Recovery, but had no recovery images. I have made a recovery for where it is at currently.
Bootloader currently shows:
*** LOCKED ***
EVITA PVT SHIP S-ON RL
CID- 11111111
HBOOT-2.15.0000
RADIO -0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Aug 14 2013, 16:02:22 -1
I would say my skill level with phones is "moderate". I at least know enough to not mess with something if I am not 100% sure.
So, from what I am seeing, the phone is S-on, and bootloader is locked, and I have superCID, so I should be able to just flash the proper RUU?
Or, is there anything else I need to do first?
Absolutely do not run an RUU while s-on, SuperCID + s-on + RUU = bricked phone. Where did you read that you can run an RUU with that combination? It's completely untrue. You can't run any RUU anyway, there are no RUUs after your current firmware version and you can't RUU backwards while s-on.
May I ask why you want to return it to a stock at&t ROM though? There is really no benefit of doing so, it's seriously a step backwards because at&t intentionally break some features and leave others out on their ROMs. What is your end goal for this device? I'll help you get there in the most efficient and safe way.
PS. Questions go in the q&a section, please make sure you post in the right section in future.
Sent from my Evita.
timmaaa said:
Absolutely do not run an RUU while s-on, SuperCID + s-on + RUU = bricked phone. Where did you read that you can run an RUU with that combination? It's completely untrue. You can't run any RUU anyway, there are no RUUs after your current firmware version and you can't RUU backwards while s-on.
May I ask why you want to return it to a stock at&t ROM though? There is really no benefit of doing so, it's seriously a step backwards because at&t intentionally break some features and leave others out on their ROMs. What is your end goal for this device? I'll help you get there in the most efficient and safe way.
PS. Questions go in the q&a section, please make sure you post in the right section in future.
Sent from my Evita.
Click to expand...
Click to collapse
Thanks for the heads up! I have been through so many posts in the last couple hours, I probably got confused about where I needed to be to safely RUU.
I don't necessarily want to be on a stock ROM, as much as I just want to return the phone to stock, and start over myself. I don't like the idea of having a customized device, and not knowing how it got there.
BUT, where I would to end up, is with CleanROM 7.0, or something similar. I am just looking for a stock(ish), rooted JB ROM, with sense 5.0.
I don't trust my skills enough to like messing with kernels and such, so I am just looking for a good JB ROM to run.
Thanks for the help! And sorry for the wrong forum.
Your thread is now in the Q&A section:good:
floodx4 said:
Thanks for the heads up! I have been through so many posts in the last couple hours, I probably got confused about where I needed to be to safely RUU.
I don't necessarily want to be on a stock ROM, as much as I just want to return the phone to stock, and start over myself. I don't like the idea of having a customized device, and not knowing how it got there.
BUT, where I would to end up, is with CleanROM 7.0, or something similar. I am just looking for a stock(ish), rooted JB ROM, with sense 5.0.
I don't trust my skills enough to like messing with kernels and such, so I am just looking for a good JB ROM to run.
Thanks for the help! And sorry for the wrong forum.
Click to expand...
Click to collapse
I admire the fact that you want to get it there yourself, the learning aspect of unlocking a device is very important in my eyes. The first thing you need to do is get s-off so you can safely run an RUU without bricking your device. I'll give you a quick run down of the entire process first though.
1. Get s-off.
2. Run the 3.18 RUU.
3. Change CID from SuperCID to original CID.
4. Use the 3.18 root method to gain SuperCID again.
5. Unlock your bootloader at htcdev.
6. Install TWRP recovery.
7. Upgrade to the 2.15 firmware package.
8. Flash Cleanrom 7.x.
So, first you'll need s-off. The easiest way is probably to use the Rumrunner method, you'll find it here:
Http://Rumrunner.us
Even before doing that though you'll need to setup an adb/fastboot environment on your PC. Adb.exe and fastboot.exe are programs you install on Windows in order to communicate with your phone via the usb cable and command prompt. In order for these to work you'll also need HTC drivers installed.
This thread is the easiest way to install adb/fastboot:
http://forum.xda-developers.com/showthread.php?p=42407269
This is where you can find the latest HTC drivers:
http://forum.xda-developers.com/showthread.php?t=2535581
Once you have those both installed you should test out the communication. Connect your phone in fastboot mode (boot into bootloader and connect device, it'll say fastboot usb on the phone), open a command prompt from within your fastboot folder (navigate to where fastboot is located on your PC, shift + right click anywhere in that folder, select open command prompt here), and issue this command:
Code:
fastboot devices
It should now return your device serial number, if it does you can go ahead and attempt Rumrunner s-off. If it doesn't return the serial you have a problem with communication.
Sent from my Evita.
How do I know what the original CID should be?
The above post by me lists how to go about the entire process, which isn't completely necessary but I've outlined it because you said you want to start from the beginning. There is a shorter way to do this, if you'd like to go for that just let me know and I'll outline though too. Your steps there look ok but I'd make a slight change.
Sent from my Evita.
floodx4 please be sure to click timmaaa thanks button.
That's how we show appreciation on XDA
Dang.......
Went through the Rumrunner process, everything seemed to go as it should, but I am still S-on.
Also, tried to unlock through HTC DEV, and I get nothing after flash the unlock token. (phone never gives me the "accept" screen.
Communication is good through fastboot, but something doesn't seem right.
Any ideas, or should I just leave well enough alone and live with 4.1?
Oh, that's my fault, I forgot you need an unlocked bootloader for Rumrunner to work. Sometimes it can take several attempts at flashing the unlock token for it to work, so keep trying that.
Sent from my Evita.
Man.....not sure what the previous owner did here, but....
I tried flashing the unlock token several times....all seemed to go through, but no "accept" screen on the phone.
Finally, I sent the fastboot oem lock command, and it "somewhat" acted like it relocked it. (I did get a FAILED message in there somewhere).
Resent the flash token command, and viola! I got the "accept" screen. Accepted the warning....and.....still locked
Went through Rumrunner again, just to see, and same result. I get the success message, but still have a locked bootloader, and still have s-on.
Back to the drawing board.......
EDIT: Went back through the process again, and noticed that when I send the fastboot oem lock command, the status changes to ***RELOCKED***, and after I flash the token, and accept the warning, the phone resets back to factory.....but bootloader still shows locked.
2nd EDIT: I think I may be on to something here!
Could the phone have one of the tools installed that "spoof" the hboot screen?
Here is what I get from a getvar all:
C:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 0.24p.32.09.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.20.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT255W302399
(bootloader) imei: 3xxxx6
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4052mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-de589c6eef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.083s
Could I be s-off and unlocked, and just not seeing it?
Yeah, the previous owner has spoofed the hboot, so even though the phone shows locked after you flash the token I believe it's unlocked. Test the theory by trying to install a custom recovery.
Download the modified version of TWRP 2.6.3.0 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now disconnect your phone and select recovery from the bootloader screen on your phone. Hopefully it boots into TWRP recovery, this proves that your bootloader is in fact unlocked.
Sent from my Evita.
timmaaa said:
Yeah, the previous owner has spoofed the hboot, so even though the phone shows locked after you flash the token I believe it's unlocked. Test the theory by trying to install a custom recovery.
<snip>
Click to expand...
Click to collapse
OK, we are getting somewhere!
I have the TWRP recovery. (I believe I already may have had this same recovery, but It did flash successfully via the commands, so I think I'm good)
So....now what? Can I "un-spoof" the hboot to be sure? Or just be satisfied with the above experiment? And if so, does this put me at Step #2 "Flash the 3.18 RUU"?
Yeah I believe you're good to go, I'd like to be doubly sure first though. You can change your CID as many times as you like if you have s-off, but with s-on you can't do that. So I'd suggest trying to change it and this will confirm your security status. The command is:
Code:
fastboot oem writecid 22222222
Hopefully that'll work, confirm by giving this command:
Code:
fastboot oem readcid
Hopefully you'll see eight two's. Once you've confirmed that works you can change it back, and you'll be good to go with the 3.18 RUU. The RUU will install the official 2.14 hboot so the locked/unlocked/relocked flags at the top of your bootloader screen will be normal again.
PS. You might want to edit the IMEI out of your post above, you should never post that publicly.
Sent from my Evita.
Cool, writecid worked.
And speaking of that, Step 3, Change CID to original......what would the original CID be?
I wouldn't worry about that step, the point of that was to use the 3.18 root method.as a learning tool, it's completely unnecessary for you, but to be honest it's more trouble than it's worth. Right now I think you're learning quite a lot so you can run the 3.18 RUU, skip step 3 and 4, you've already unlocked your bootloader so skip step 5, you'll need to install TWRP recovery again after the RUU so do step 6, then you can continue on with steps 7 and 8.
Sent from my Evita.
timmaaa said:
I wouldn't worry about that step, the point of that was to use the 3.18 root method.as a learning tool, it's completely unnecessary for you, but to be honest it's more trouble than it's worth. Right now I think you're learning quite a lot so you can run the 3.18 RUU, skip step 3 and 4, you've already unlocked your bootloader so skip step 5, you'll need to install TWRP recovery again after the RUU so do step 6, then you can continue on with steps 7 and 8.
Sent from my Evita.
Click to expand...
Click to collapse
Awesome.
Just to be sure here....do I want my bootloader locked or unlocked when I flash the RUU?
You're s-off so you can leave the bootloader unlocked. Here's a link for the RUU.
http://dl3.htc.com/application/RUU_..._10.130.32.34_release_signed_With_Partial.exe
Sent from my Evita.
I cant hit the thanks button enough!
CleanRom 7 installed and working great, and best of all, I know where it came from.
Now its time to take this thing for a test drive.......
Oohhhh yeah! That's what I'm talkin bout!
Great news, and once again I admire you for actually wanting to put in the effort and do some learning along the way. Most people want to take the shortest road possible, and they're inevitably the ones who have no idea what to do when something goes wrong.
If you do ever need help in the future just let me know.
Sent from my Evita.