Back to Stock ICS for k2u & k2ul with S-Off
Hi there, as there are different news, we will get one more major update, there is a need to get back to the stock rom, cause otherwise the update will fail. Or maybe you want to sell your device or need to return for warranty, so you also need a stock phone.
And there is nothing more stock out there, than a RUU. But as we have no Jelly Bean RUU, we need to get the ICS RUU running to downgrade hboot first!
So we provide here an almost easy way to go to this condition and you only have to follow these steps, but do it careful, cause we need to downgrade hboot for that and this is very dangerous for your phone, if you are doing something wrong!
This guide is provided to you, with the help of Matlevo12, who made the files you need for downgrading hboot and tested the way. So give him a thanks for it!
This only works for "free" phones (unbranded) or if you have Supercid.
Credits:
- kmdm for his ruuveal
- Matlevo12 for creating and testing the "downgrade files"
- rollon76 & Jmz for suggestions
Click to expand...
Click to collapse
Notice:
- This guide is for european k2u & k2ul. Don't do this on other HTC One SV devices, this will brick your phone.
- Be careful and download the correct file, check the md5 sum to get sure, the download is not corrupted.
- Make a backup of important files, before you do this, they are lost afterwards!
- This will not reset your CID, if you have changed it to SuperCID. So if you have SuperCID, follow this guide to change it back before you doing this! Your phone must be unbranded then.
Click to expand...
Click to collapse
Don't do this, if you are not experienced enough for it. You will do this on your own risk and we are not responsible for bricked devices!!!
Requirements:
- a phone with S-Off -> yes, you need S-Off (if you don't have it, look here for ICS and there for JB to get it.)
- the correct file for downgrading hboot
- the correct RUU for your device
- some time and coffee and some knowledge about fastboot commands
Click to expand...
Click to collapse
Download:
(be sure to download the right files for your device!)
For k2u (without LTE):
- k2uhbootdowngrade(renametoPL80IMG.zipbeforeuse).zip --> for downgrading hboot
md5 sum: 8b4ad0f238c5857367d4e074450b2262
- ICS RUU for k2u
Click to expand...
Click to collapse
For k2ul (with LTE):
- k2ulhbootdowngrade(renametoPL80IMG.zipbeforeuse).zip --> for downgrading hboot
md5 sum: 44f4acc65d299d8aa5b0da533515e421
- ICS RUU for k2ul
Click to expand...
Click to collapse
How to:
To downgrade hboot:
1.) Download the fitting zip file for your device
2.) Rename the file to PL80IMG.zip
3.) Copy it to your sdcard (external not internal)
4.) Reboot into bootloader and hit volume up when prompted
Click to expand...
Click to collapse
You maybe need to go to Settings -> Power first and untick the Fast boot (scroll down, last point on the page) that you can boot into bootloader!
To boot into bootloader:
If your phone is off, you need to power on & hold vol- at the same time.
Now the hboot should be downgraded to hboot 1.0 and most tricky part is done.
To flash RUU:
5.) Reboot your phone and connect it to pc
6.) Run the downloaded RUU.exe (you maybe have to start it as administrator) and follow the steps provided by HTC
If the RUU won't flash, relock your bootloader with fastboot cmd:
Code:
fastboot oem lock
Click to expand...
Click to collapse
After the RUU was running through you have stock ICS boot.img, recovery and system files installed. You are still S-Off, but with a "*** LOCKED ***" bootloader.
If you wanna get S-On, follow now step 7.) & 8.).
If you wanna update, now you can restart your phone and search for updates. Install one by one (first will be the jb updates) until you don't get update offers anymore.
If you want to get your device S-On:
7.) Connect your phone to pc and boot into fastboot mode.
8.) Open fastboot command window on your pc and type the following command:
Code:
fastboot oem writesecureflag 3
Click to expand...
Click to collapse
Now you should be S-On.
Help
1.) Download the fitting zip file for your device---------------ok
2.) Rename the file to PL80IMG.zip-----------------------------ok
3.) Copy it to your sdcard (external not internal)-------------------------ok
4.) Reboot into bootloader and hit volume up when prompted--------------------ok
adn then? whould I do? I don't understand how it become downgraded to hboot 1.0.
thanks much.
Well, that's it. Nothing more to do.
help
https://www.dropbox.com/lightbox/home?select=IMAG0001.jpg
CID error
Can anyone help me?
It is normal to use just a little leg and can't flash rom.
How should I do now?
Thanks much.
When do you get that cid error ?
What cid are you ?
my CID is Orange1 or something similar, can I still use this method to be able to get myself an unbranded version of JB on the device?
Conan_troutman :
Well no, use the "unbrand your phone..." guide in the same section.
I think this only work for "free" phones or if you have supercid.
help
https://www.dropbox.com/lightbox/hom...t=IMAG0001.jpg
CID-HTC_621
can't into recovery:
hboot
cid incorrect！
update fail!
Press power to reboot
thanks very much
Painterok :
Your phone is branded, unbrand it first if you want to, or downgrade using files from your brand's ruu.
Why do you want to downgrade ?
Thanks much
Matlevo12 said:
Painterok :
Your phone is branded, unbrand it first if you want to, or downgrade using files from your brand's ruu.
Why do you want to downgrade ?
Click to expand...
Click to collapse
Thanks much again for reply.
At first, I must say that my English is not good enough, sorry.
Downgrade just for 2 way recording, because I need this function very much on the business. When 4.0.4, it's ok, but update to 4.1.2 it is unable to use.
Now, my phone can also be used, but not smooth.
How to unbrand it (sorry, Idon't understand what does branded mean) or what Ican do now?
Dear Matlevo12, Thanks very much.
S-off and RUU update went smooth but I no longer can enter Recovery menu. It shows an exclamation mark surounded by red triangle.
k2ul unbranded phone here and used RUU update file acording to my phone model.
Which S-off?
I upgraded to JB and want to bring ICS back. Old.splatterhand, you said we need S-off so which one do I need please?
Thanks a lot for sharing! :good:
As you are on JB you must use Moonshine S-off.
old.splatterhand said:
As you are on JB you must use Moonshine S-off.
Click to expand...
Click to collapse
Thank you! Hope it will work...
Hello all, sorry for bothering you again old.splatterhand, but before doing it I want to be sure I'm understanding things in the right way.
So after step 6, I will be done and should have ICS back, that's it? Thanks
toldmango said:
Hello all, sorry for bothering you again old.splatterhand, but before doing it I want to be sure I'm understanding things in the right way.
So after step 6, I will be done and should have ICS back, that's it? Thanks
Click to expand...
Click to collapse
Yes, it's pretty clear :
After the RUU was running through you have stock ICS boot.img, recovery and system files installed. You are still S-Off, but with a "*** LOCKED ***" bootloader.
If you wanna get S-On, follow now step 7.) & 8.).
Click to expand...
Click to collapse
Matlevo12 said:
Yes, it's pretty clear :
Click to expand...
Click to collapse
Alright then, thank you Matlevo12!
Pure JB Rom, Kernel, Recovery, etc.
I got the JB stock Rom, Kernel, Recovery, etc. Just got to place it on your external sdcard. Its completely fresh without touching it. Just like you gotit from the box. This is for k2_cl, it may work for others but not tested. Need atleast 1.02 gigs available on external sdcard. Once placed there just boot into custom recovery. I used TWRP and I recommend it. Not a fan of CWM. Once in recovery just click on restore then select the pure JB folder. It comes with MD5 files so be sure to check the verification box so when doing this it will confirm its integrity prior to proceeding further. After verification it will proceed on and wipe everything out as it restores. Then reboot. Keep in mind that this is a fresh 4.1.2 JB stock. You will lose root but you can easily get it back by downloading supersu on Google play. Voila. Will have to upload tonight then will share resource on here. Once available have at it. I don't request credit for it or anything. Just want it out there for people who messed there phone up or failed to get a copy for themselves.
There are already copies of this for k2_cl in old.splatterhand's thread in original android development
http://forum.xda-developers.com/sho...SV] Stock boot.img | recovery.img | radio.img
Related
DISCLAIMER. Do it at your own risk.. I am not responsible for bricks....bla bla bla, usual stuff.
If in doubt-STAY AWAY!
Q/A First.
Do I HAVE to flash this FW? - YES, if you want to flash ICS 4.0.3 based rom. If not, it just won't boot. Latest firmware works with previous (2.3.4,2.3.5,4.0.1) roms.
Do I NEED SuperCID? - YES, it will help in case you need to revert and if your CID is not on the update.zip list
Will I lose S-OFF? - NO
Can I use this FW with earlier builds? - YES
Will I lose fastboot commands like flash splash1? - Yes
Is it safe? Never 100% but no fails so far. Flash at your own risk
Can I revert to previous hboot, like 1.17? Yes, make sure you are superCID.
Any disadvantages? None so far
Any advantages? More optimised fw/drivers for ICS. Users report faster ROM operation.
Why does it say ***LOCKED*** in bootloader? Because hboot is locked (don't panic)
Can I go back to **REVOLUTIONARY**? Yes, flash 1.17 HBOOT at the bottom of OP.
HOW TO
0. Make sure you are S-OFF and superCID. Check HERE
1. Download zip from HERE Credits to rmk40, this is FW I used).
2. Do nandroid backup.
3. Copy/paste PG58xxxxx to the root of your microSD
4. Make sure MD5 match!!! MD5 checker I use HERE
4. Make sure MD5 match again!!!
4. And once again, make sure MD5 match.
5. Reboot into bootloader (if you don't know how to do it, don't do any of that at all)
6. microSD will be scanned and will ask you if you want to update, press +vol for YES
7. Follow onscreen instructions.
8. Now just pull sd card out if you don't have microSD reader or delete PG58xxxx if you do. PG58 will prevent you from going into recovery if phone sees it.
9. Reboot into bootloader-go to recovery
10. Put your SD card back in
11. Reboot or flash new rom
12. You are done. Just delete that PG58 file so it doesn't stop you getting into recovery again.
REVERT TO 1.17 HBOOT
ziggy1001 said:
Direct link with MD5
http://forum.xda-developers.com/showpost.php?p=20681060&postcount=22
Click to expand...
Click to collapse
Paste on root of SD card, make sure MD5 matches. Repeat update from bootloader (steps 1-12 from above) and you should be done.
If anyone has anything to add, feel free.
Remember, if you flash RUU, then process is slightly different and will most likely involve unlocking via HTCDEV (haven't really looked into it)
This is for all Sensation's, right?
aNYthing24 said:
This is for all Sensation's, right?
Click to expand...
Click to collapse
Indeed. Mike provided img files from both RUUs. I'm pretty sure it's safe to mix and match, since we ran 1.73 RUUs on normal Senny, but wouldn't recommend risking it just in case. But there is always a brave one ... LOL Who is it gonna be this time?
I've already followed the steps as in mike1986's thread and all went well, but what is the benefit of reverting to 1.17 HBOOT?
piplewis said:
I've already followed the steps as in mike1986's thread and all went well, but what is the benefit of reverting to 1.17 HBOOT?
Click to expand...
Click to collapse
Advanced fastboot commands
nice work on the thread mate, do you want to include a note that mikes files will update the radio too, just make sure everyone is clear on what is updates
Does it improve performance noticeably? I'm just a bit overwhelmed, sorry.
Hawke84 said:
nice work on the thread mate, do you want to include a note that mikes files will update the radio too, just make sure everyone is clear on what is updates
Click to expand...
Click to collapse
So there will be no possibility of downgrading the radio?...our i have to revert to 1.17 to flash older radios?
I have 10.56 and i m satisfied with it...
jjdoctor said:
So there will be no possibility of downgrading the radio?...our i have to revert to 1.17 to flash older radios?
I have 10.56 and i m satisfied with it...
Click to expand...
Click to collapse
You can still do it via PG58 update, but not via fatboot flash radio radio_image_name.img
I want to try this so bad, but I am scared as heck! What do we need to know before doing this? Such as, what do we risk other than an all out brick? Will we be able to go back to what we have now?
Matt
tinky1 said:
Find 1.17 HBOOT in PG58xxxx in THIS THREAD (provided by ziggy1001)
)
Click to expand...
Click to collapse
Direct link with MD5
http://forum.xda-developers.com/showpost.php?p=20681060&postcount=22
Looks like it worked for me. I am restoring a ROM right now. After that, ill revert back to the previous bootloader. So far, so good!
So now, where do you guys see the improvements?
Matt
I just tried to flash it but it have me CID error... I used supercid by this method
http://forum.xda-developers.com/showthread.php?t=1192630
What could be wrong?
jjdoctor said:
I just tried to flash it but it have me CID error... I used supercid by this method
http://forum.xda-developers.com/showthread.php?t=1192630
What could be wrong?
Click to expand...
Click to collapse
I am getting ready to flash it, but I did supercid by the method in the sticky-noted post near the top of the Sensation forums.
[Guide] to Installing S-off, Unlocking, ClockWork, Root, SuperCID & S-on
jjdoctor said:
I just tried to flash it but it have me CID error... I used supercid by this method
http://forum.xda-developers.com/showthread.php?t=1192630
What could be wrong?
Click to expand...
Click to collapse
Does your bootloader screen show **locked** in pink color ?
hsnmz said:
Does your bootloader screen show **locked** in pink color ?
Click to expand...
Click to collapse
Yes it shows Locked in pink... My hboot is now 1.20
My radio didn't upgrade... I still have 10.56....
I flashed it over Ultimite ROM... i thought it will erase my ROM but nothing changed....:-/
It flashed everything but showed cid error in last one... I don't know what was it....
So now i have to go back to 1.17, supercid using adb and fish 1.20 again?
I supercid using terminal emulator... I guess that didn't work...
jjdoctor said:
I supercid using terminal emulator... I guess that didn't work...
Click to expand...
Click to collapse
Wait, what?!
You tried to SuperCID via Terminal Emulator, while the phone was running? oO
What's wrong with following the instructions in the stickied guide and using adb?
Never in my life i used adb stuff... :-/
never tried to learn it either... But i guess i have to learn it now..
Now tell me what to do?
should i download hboot 1.17, flash it and then reflash 1.20 after supercid?
jjdoctor said:
Never in my life i used adb stuff... :-/
never tried to learn it either... But i guess i have to learn it now..
Now tell me what to do?
should i download hboot 1.17, flash it and then reflash 1.20 after supercid?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1192300 this is the thread I have followed time and time again with success step 4 is to do cid
is this firmware just relevent to ics roms or can it be used on 3.0/3.5 roms??????
i find it hard to restore my one s because there is no official RUU for my one s c2,i failed to s-off aswel to use older RUU that i have so i found out that you can still restore your rom to stock after using custom roms..this method is tested and working (but me reminded to always have nandroid back up and use it at your own risk)
1st step: download a OTA update,in my case i download ASIA WWE 3.17.707.102 (it is in a zip form): you can find yours here http://splanet.info
or you can obtain it form any other source
2nd step: once you have the zip file open it and extract the firmware.zip (put it beside the fastboot.exe or inside the folder where adb and fastboot is)
now before proceeding to next step you need to verify first your CID
To Get the CID of your phone: reboot the phone in bootloader/fastboot mode (adb reboot bootloader), and use fastboot getvar cid. Match this in the android-info.txt file found inside the firmware.zip file. If it doesn’t match, don’t go any further.
**************If you’re still here, I guess your CID matched.*******************
now we will need tools like notepadc++ and 7zip
3rd step: Now, in the OTA zip file, find the file updater-script in the directory META-INF/com/google/android. In this we’ll need to remove some code that doesn’t work with recoveries other than the default HTC ones. (extract the updater-script)
then Open the file with any decent text editor that preserves newlines (for windows, Notepad++ springs to mind, on Linux/Mac just use vi), and look for a textblock like this:
ifelse( is_ship_bootloader(getprop("ro.bootloader")) == "t" ,
assert(check_cid(getprop("ro.cid"), "00000000" , "11111111" ,
"22222222" , "33333333" , "44444444" , "55555555" , "66666666" ,
"77777777" , "88888888" , "99999999" , "HTC__044") == "t");
);
delete that line.. then save it. after that delete the update-script inside the OTA (located in META-INF/com/google/android.) after deleting copy the new updater-script that we have just edited to the same directory where you delete the old updater-script..
4th step: Next, reboot your phone into Clockworkdmod Recovery (or whatever recovery you have installed), make a nandroid backup of your phone, and copy the OTA zip file on the phone. As a safety measure, it’s recommended to make a backup of everything on the SD storage to your computer.
5th step: When the backups are completed, reboot your phone into bootloader/fastboot mode. It’s time to lock the bootloader again, so we can flash the firmware update. This can be done using the command fastboot oem lock. Your phone will reboot.
6th step: Reboot it once again, this time to OEM update mode: adb reboot oem-78
7th step: Flash the firmware update: fastboot flash zip firmware.zip. If this complains without getting you a green progressbar on the screen, try it again – the second time it usually sticks.(even if it fails the the 4th time around just try and try it)
Once this process completes, reboot the phone again in the new bootloader: fastboot reboot-bootloader.
Now you can unlock your bootloader again, using the Unlock_Code.bin file you got from htcdev.com: fastboot flash unlocktoken Unlock_Code.bin.
At this point, you’d sure as hell wish you’d made a backup, if you didn’t. Because now your phone is wiped, reset to factory default. Don’t say I didn’t warn you upfront.
8th step: After the reboot finishes, you can once again boot in booloader/fastboot mode, and flash your recovery anew. For Clockworkdmod Recovery, the command is fastboot flash recovery <filename.img> Now you can boot the phone in the recovery (select the option from the bootloader menu).
9th step: Once in the recovery, it’s time to restore your nandroid backup. You did make one, did you?
If you finished restoring the backup, or you can now flash the OTA zip on the phone, updating the ROM to the new version or stock version.
After this, you just need to reboot one more time, this time to the ROM itself. Let it finish upgrading all applications, and tadaa, your freshly upgraded phone.
This worked for me, might not work for you. No promises.
this tut i found is for the one x but i made a one s version (villec2) which works.. so have fun and restore your device to stock....
Hope This Helps...
if you like this feel free to like and thanks me
ps: sorry for really bad english
-- xander
Would it work as an update for phone which doesn't "see" the OTA update and cheating recovery by placing the OTA as update.zip on phone's memory doesn't work either?
xQrzy said:
Would it work as an update for phone which doesn't "see" the OTA update and cheating recovery by placing the OTA as update.zip on phone's memory doesn't work either?
Click to expand...
Click to collapse
hello mate,
ive tried before but it didnt work,you really have to do the stuff,but incase your one s is in different status it will be different..for mine im still s-on
and the ota rom will only work for the firmware .zip that is inside the ota which you will have to manually flash..
Hi xander1993,
I am sorry to bother you but your answer is not clear to me
You say you tried it but didn't work and just after that you write I have to do the stuff
So let's clarify my situation and then I will wait for your answer:
I am currently using TD6 because I could not update to JB using OTA. My HBOOT now is 2.11.
I did go back to stock 4.0.4 (by RUU, my CID is HTC__032) several times, tried OTA, but no result.
Then I tried (also several times) to download the OTA zip file from splanet, place it on phone and reboot to stock recovery - every time it was showing me first a pgone with green arrows shaping to a circle and one arrow inside the circle and after several seconds it was a phone with red triangle with an exclamation mark - at this stage I had to wait few minutes for reboot every time. No effect.
So my question is:
Will your guide help me to get just update from 4.0.4 to JB?
xQrzy said:
Hi xander1993,
I am sorry to bother you but your answer is not clear to me
You say you tried it but didn't work and just after that you write I have to do the stuff
So let's clarify my situation and then I will wait for your answer:
I am currently using TD6 because I could not update to JB using OTA. My HBOOT now is 2.11.
I did go back to stock 4.0.4 (by RUU, my CID is HTC__032) several times, tried OTA, but no result.
Then I tried (also several times) to download the OTA zip file from splanet, place it on phone and reboot to stock recovery - every time it was showing me first a pgone with green arrows shaping to a circle and one arrow inside the circle and after several seconds it was a phone with red triangle with an exclamation mark - at this stage I had to wait few minutes for reboot every time. No effect.
So my question is:
Will your guide help me to get just update from 4.0.4 to JB?
Click to expand...
Click to collapse
okay now i got your question my guide is about s-on devices restoring to jelly bean stockbecause s3 version havent got any RUU,all the RUU i found is ICS so i made this to restore back to stock,so in your situation you are still in ics? are you s-off? or s-on? and do you have the bootloader unlocked?
i can help you to update to jb with the OTA just find your OTA that matches your phones CID and MID,
after that you will need to have custom recovery like twrprecovery
then just follow my post above start 2nd step... i will wait for your reply...
As I mentioned above I am on TD6 now (TrickDroid 6), HOS S3, ICS base, S-ON (there is no S-OFF for S3 ), bootloader unlocked.
Hmm, what is MID? I haven't heard of it before..
I will follow your guide once I get an answer for this simple question
AW: (GUIDE) RESTORE JB HBOOT 3.06 TO STOCK AFTER CUSTOM ROM ONE S C2 (villec2) !!
I have a One s with cid vodap102 and Android 4.0.3 can i Flash on this way Android 4.1 Euro stock rom on my One s ?
Sent from my HTC One S using xda app-developers app
xantan said:
I have a One s with cid vodap102 and Android 4.0.3 can i Flash on this way Android 4.1 Euro stock rom on my One s ?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
u can try but most probably u cant
Make a backup before doing
AW: (GUIDE) RESTORE JB HBOOT 3.06 TO STOCK AFTER CUSTOM ROM ONE S C2 (villec2) !!
Im testing this
Sent from my HTC One S using xda app-developers app
Yes it will work because this method is also tricking the custom recovery so that ota can be installed
Sent from my HTC One S using xda app-developers app
Mid is the model of device so if yours is one s s3 don't worry about mid,
Sent from my HTC One S using xda app-developers app
Yes you can it update you to 4.1.1 just download the right ota for your device specifically the right ota for your cid
Sent from my HTC One S using xda app-developers app
I read the guide and I barely understood how it works, but my question would be this:
Im on CID BSTAR301 (yeah, Latinamerican fked up CID stuck on 4.0.3) and if I change some of the code of a RUU.zip file (with other updated CID), would it work on my device? Is there any way to cheat the RUU to make it work on others CID? I think this could be possible, it's just some editable files, I hope this could work because I don't wanna be stuck on 4.0.3 while others Villec2 are with official JB
krlwarrior said:
I read the guide and I barely understood how it works, but my question would be this:
Im on CID BSTAR301 (yeah, Latinamerican fked up CID stuck on 4.0.3) and if I change some of the code of a RUU.zip file (with other updated CID), would it work on my device? Is there any way to cheat the RUU to make it work on others CID? I think this could be possible, it's just some editable files, I hope this could work because I don't wanna be stuck on 4.0.3 while others Villec2 are with official JB
Click to expand...
Click to collapse
sorry i am bad in english...but the method up is working...ill help you..first download your OTA for your CID..then tell me when you got it
you can find yours here http://splanet.info/
The problem is that my CID is not in the list, BSTAR301... I want to use other RUU because there is no RUU for my CID Can we cheat on other RUU file?
krlwarrior said:
The problem is that my CID is not in the list, BSTAR301... I want to use other RUU because there is no RUU for my CID Can we cheat on other RUU file?
Click to expand...
Click to collapse
no you cant cheat the RUU but can cheat the OTA update,even if you dont have the the correct OTA it will install but first you need to be unlock via HTCDEV and you got to have twrp custom recovery
When trying to flash the firmware, mine says "remote: 44 hboot version check fail" I have hboot 3.01.0000 :| Any ideea why?
bubert said:
When trying to flash the firmware, mine says "remote: 44 hboot version check fail" I have hboot 3.01.0000 :| Any ideea why?
Click to expand...
Click to collapse
you are not htc dev unlocked?
HTC One S Arabic JB update
Hi,
I bought an HTC One S from Dubai(Arabic Region) and I am using it in India right now. I have not yet received the JB update for the phone.
I was able to find the OTA files for the JB Update to the One S for the Arabic Region here -
splanet.info/
My CID is HTC_J15 as given by the CID Getter app.
I booted into the bootloader and got the following information -
***Locked***
VilleC2 PVT SHIP S-ON RL
HBOOT-2.09.0001
RADIO-16.05.20.24_M
OpenDSP-v05.6.0.2226.00.0418
eMMC-boot
May 10 2012, 17:19:49
This was followed by the HBoot, FastBoot, Recovery. Factory Rset, SIMLock, Image CRC and Show BarCode options.
Can you guide me as to how I can install the JB update?
Please bear with me as I am a noob.
Thanks.
sshray said:
Hi,
I bought an HTC One S from Dubai(Arabic Region) and I am using it in India right now. I have not yet received the JB update for the phone.
I was able to find the OTA files for the JB Update to the One S for the Arabic Region here -
splanet.info/
My CID is HTC_J15 as given by the CID Getter app.
I booted into the bootloader and got the following information -
***Locked***
VilleC2 PVT SHIP S-ON RL
HBOOT-2.09.0001
RADIO-16.05.20.24_M
OpenDSP-v05.6.0.2226.00.0418
eMMC-boot
May 10 2012, 17:19:49
This was followed by the HBoot, FastBoot, Recovery. Factory Rset, SIMLock, Image CRC and Show BarCode options.
Can you guide me as to how I can install the JB update?
Please bear with me as I am a noob.
Thanks.
Click to expand...
Click to collapse
first thing first you need to have htc dev unlock boot loader http://www.htcdev.com/bootloader select "all other supported models" then follow the on screen instruction then after that go back here....
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
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:
Running an RUU is only simple for those who haven't been messing with their devices, and that usually isn't us. Since I just did this, I want to write down the steps because I was not able to find easy answers.
This assumes your device is rooted with a different ROM installed. If that is not the case, then you can just download and run the RUU for your device, end of instructions.
Downloading the correct RUU
The most complete list of RUUs for Ville is found on androidruu.com
T-Mobile: http://www.androidruu.com/getdownlo..._10.30.50.08L_release_309489_signed_ICS_2.exe
HTC Europe: http://www.androidruu.com/getdownlo...28_10.27.50.08L_release_301814_signed_2_4.exe
There are RUU updates listed for other service providers, but I can't tell if they are JellyBean hboot 2.15 or not. If someone knows, I'll update this post.
Preparing your device
Make your device s-off if it isn't already. Why?
You will not have to relock the bootloader to perform the RUU update.
You will not have to flash the boot image separately.
If for some reason you can't or won't go s-off, you can still do this, but will have many more steps to follow.
Instructions to make your device s-off are here for firmwares below 3.14: Facepalm S-Off for HTC Devices One S, One XL, Droid DNA
Or you can use the HTC All-In-One Toolkit which helps you through the process.
Use the HTC All-In-One Toolkit (link above) to change the CID to match the RUU.
You needed Super CID to gain s-off, but it won't help you install RUUs. Even if you are Super CID (11111111), you must change your CID to match the RUU you are installing (mine is TMobile: T-MOB010). I know, kinda defeats the purpose of being Super CID, but the RUU won't succeed otherwise. If you are s-off, it is a one click operation using the All-In-One Toolkit.
Backup your device
Use Titanium backup to backup all your user apps so you can restore them afterwards. (No, don't restore system apps please!)
Also back up your ROM by booting into recovery mode and selecting Backup.
If you are only updating the hboot but keeping the same ROM, you can just restore the backup afterwards. Not sure why anyone would need to update the hboot without installing a new ROM, but then you also have a backup in case things go wrong.
Run the RUU
If you are s-on you will have to relock the bootloader by rebooting into the fastboot mode, connecting your device to the computer and running the command "fastboot oem lock". You will also have to follow the process again to unlock your bootloader after doing the update. Tutorials for that are found elsewhere.
1. Leave bootloader unlocked, and leave s-off as is. No need to go back to s-on or relock bootloader.
2. Run the RUU and wait while it updates the phone (Incidentally, it didn't even wipe my sd partition data!)
3. While you are still in bootloader mode (before booting up), use the All-In-One tool to install the TWRP S4 recovery. Or, if you don't want to use the tool, you'll have to download a recovery and use "fastboot flash recovery" followed by the name of the recovery img file.
4. Reboot bootloader and enter recovery mode
5. Restore from backup or Mount USB from TWRP and copy over the ROM and gapps package, flash, wipe cache, and you are up and running.
If you are s-on you will need to extract the boot.img from the zip you are flashing and flash that image separately with "fastboot flash boot boot.img"
Note that device still has the unlocked bootloader and is still s-off! :victory:
My device before: hboot 1.09, unlocked bootloader, Super CID, s-off (In layman's terms, this is a device with an unlocked bootloader so it can accept other ROMs, set to accept any service provider's RUU update via SuperCID, and has had write permission to the boot sector removed via s-off).
My device after: hboot 2.15, unlocked bootloader, T-MOB010 CID, s-off
If possible, I will answer your comments or questions by updating this post and I'll refer you back to here.
Have you changed your CID?
mag13 said:
Have you changed your CID?
Click to expand...
Click to collapse
Please read again.
I was Super CID (11111111) but easily changed it to match TMobile (T-MOB010) with this tool for the update.
Click to expand...
Click to collapse
yooouuri said:
Please read again.
Click to expand...
Click to collapse
I am on Super CID and it does not work
mag13 said:
I am on Super CID and it does not work
Click to expand...
Click to collapse
You have to change your CID back to the one for your RUU.
Can I use this tutorial to rollback to 2.15 or whatever works for ViperS rom with sense 4 after I flashed MaximusHD and firmware?
Now my phone is like this:
Hboot 2.16
Radio 1.20.50 (worst radio ever)
S-OFF
CID 11111111
The rom's with sense 5 (I tried just maximus because the others are not compatible with the new firmware, the sdcard mount point for multi user) are killing my battery more than twice faster compared with ViperS. 2h Display vs 5h on Viper.
Thank you!
Can we use this as rollback from h-boot 2.16 ?
mag13 said:
I am on Super CID and it does not work
Click to expand...
Click to collapse
I didn't think it would. Glad you didn't brick your phone and I'll update the OP based on your experiment.
flow27 said:
Can we use this as rollback from h-boot 2.16 ?
Click to expand...
Click to collapse
arazvan2002 said:
Can I use this tutorial to rollback to 2.15 or whatever works for ViperS rom with sense 4
Click to expand...
Click to collapse
Upgrading your hboot is a one way street, as far as I know. Can't you change the radio to something else?
I flashed Viper ROM. All the things are ok, gsm, wifi, etc just I can't see the internal memory like I should. I can browse to it file es file explorer but I need a method to default mount the new (4.2.2) location of it. Where is mounted by the internal memory in 4.1 JB? I discovered a file vold.fstab. Maybe I can change something like that somewhere to be able to use 4.1 ROM's again.
Sorry for OFF topic.
Somebody asked it but i want a clear awnser.
Can i use it to roll back to 2.15 from 2.16?
yooouuri said:
Somebody asked it but i want a clear awnser.
Can i use it to roll back to 2.15 from 2.16?
Click to expand...
Click to collapse
Yes you can if youre s-off.
Sent from HTC One S using android 4.2.2 sense 5
Im s-off and changen my RUU back to the origonal.
Using 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
But i get the same error. Cant update because wrong "Update tool".
-------------------------------
Flashed orig_hboot_2.15.0000.zip
But im stuck on 1.20 Radio?
yooouuri said:
Im s-off and changen my RUU back to the origonal.
Using 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
But i get the same error. Cant update because wrong "Update tool".
-------------------------------
Flashed orig_hboot_2.15.0000.zip
But im stuck on 1.20 Radio?
Click to expand...
Click to collapse
Did you run the RUU.exe when your phone was in bootloader (fastboot USB mode)?
tivofool said:
Did you run the RUU.exe when your phone was in bootloader (fastboot USB mode)?
Click to expand...
Click to collapse
That's the right thing to do, yes?
kilo94 said:
That's the right thing to do, yes?
Click to expand...
Click to collapse
Yes
I have the same problem. I can't go back to stock. I haven't changed my CID yet but I see that has not worked for you.
Did you try with HTC__001 ?
dhigby said:
Running an RUU is only simple for those who haven't been messing with their devices, and that usually isn't us. Since I just did this, I want to write down the steps because I was not able to find easy answers.
This assumes your device is rooted with a different ROM installed. If that is not the case, then you can just download and run the RUU for your device, end of instructions.
Downloading the correct RUU
The most complete list of RUUs for Ville is found on androidruu.com
T-Mobile: http://www.androidruu.com/getdownlo..._10.30.50.08L_release_309489_signed_ICS_2.exe
HTC Europe: http://www.androidruu.com/getdownlo...28_10.27.50.08L_release_301814_signed_2_4.exe
There are RUU updates listed for other service providers, but I can't tell if they are JellyBean hboot 2.15 or not. If someone knows, I'll update this post.
Preparing your device
Make your device s-off if it isn't already. Why?
You will not have to relock the bootloader to perform the RUU update.
You will not have to flash the boot image separately.
If for some reason you can't or won't go s-off, you can still do this, but will have many more steps to follow.
Instructions to make your device s-off are here for firmwares below 3.14: Facepalm S-Off for HTC Devices One S, One XL, Droid DNA
Or you can use the HTC All-In-One Toolkit which helps you through the process.
Use the HTC All-In-One Toolkit (link above) to change the CID to match the RUU.
You needed Super CID to gain s-off, but it won't help you install RUUs. Even if you are Super CID (11111111), you must change your CID to match the RUU you are installing (mine is TMobile: T-MOB010). I know, kinda defeats the purpose of being Super CID, but the RUU won't succeed otherwise. If you are s-off, it is a one click operation using the All-In-One Toolkit.
Backup your device
Use Titanium backup to backup all your user apps so you can restore them afterwards. (No, don't restore system apps please!)
Also back up your ROM by booting into recovery mode and selecting Backup.
If you are only updating the hboot but keeping the same ROM, you can just restore the backup afterwards. Not sure why anyone would need to update the hboot without installing a new ROM, but then you also have a backup in case things go wrong.
Run the RUU
If you are s-on you will have to relock the bootloader by rebooting into the fastboot mode, connecting your device to the computer and running the command "fastboot oem lock". You will also have to follow the process again to unlock your bootloader after doing the update. Tutorials for that are found elsewhere.
1. Leave bootloader unlocked, and leave s-off as is. No need to go back to s-on or relock bootloader.
2. Run the RUU and wait while it updates the phone (Incidentally, it didn't even wipe my sd partition data!)
3. While you are still in bootloader mode (before booting up), use the All-In-One tool to install the TWRP S4 recovery. Or, if you don't want to use the tool, you'll have to download a recovery and use "fastboot flash recovery" followed by the name of the recovery img file.
4. Reboot bootloader and enter recovery mode
5. Restore from backup or Mount USB from TWRP and copy over the ROM and gapps package, flash, wipe cache, and you are up and running.
If you are s-on you will need to extract the boot.img from the zip you are flashing and flash that image separately with "fastboot flash boot boot.img"
Note that device still has the unlocked bootloader and is still s-off! :victory:
My device before: hboot 1.09, unlocked bootloader, Super CID, s-off (In layman's terms, this is a device with an unlocked bootloader so it can accept other ROMs, set to accept any service provider's RUU update via SuperCID, and has had write permission to the boot sector removed via s-off).
My device after: hboot 2.15, unlocked bootloader, T-MOB010 CID, s-off
If possible, I will answer your comments or questions by updating this post and I'll refer you back to here.
Click to expand...
Click to collapse
Hey I used your instructions and everything was perfect thank you. I used to upgarde and downgrade hboot even to restore the HTC one S
I got the RUU "Error: 159" again with both RUU from first post and testet with each common cid, but at the end I only got success with super cid and the TMO_US Ruu.
Now I am back on Hboot 2.15 and can flash again the newest custom-recovery, thank you very much.
I've heard about a flashabe standalone zip for the hboot 2.15 and found this:
Only for S4!
Boot into bootloader and enable fastboot.
Code:
fastboot oem rebootRUU
Wait for the black screen with white HTC symbol. (Like when you flash a RUU)
then enter:
Code:
fastboot flash zip modded_hboot_YOUR_NEEDED_HBOOT.zip
then if you want
Code:
fastboot oem boot
(Boot into your current ROM)
modded_ = The red text is removed and "tampered" is gone in bootloader.
Download:
modded_hboot_1.06.0000.zip - (397.1 KB)
modded_hboot_1.09.0000.zip - (400.6 KB)
modded_hboot_1.13.0000.zip - (399.0 KB)
modded_hboot_1.14.0002.zip - (405.3 KB)
modded_hboot_1.14.0004.zip - (373.2 KB)
modded_hboot_1.14.0005.zip - (373.6 KB)
modded_hboot_2.15.0000.zip - (400.9 KB)
modded_hboot_2.16.0000.zip - (398.6 KB)
Thx goes to: touch of jobo XDA Post Source
DISCLAIMER:this is not my work. i have tested it on my own device,but use it at your own risk. if it melts your phone into a lil pile of goo,its not my fault.
Greetings by Idijt