Related
This is for all the people out there who currently have the most up to date version of the stock HTC One XL (Telstra) software/ firmware 3.17.xx and wish to be able to install CM10.1 and other ROMS alike.
I found it very hard to find all the information out there to be able to do this and now that it is finally done I feel the need to share this valuable information to all who are possibly having the same drama.
Here it is!
Step 1 - HTC Dev Unlock
This is easy! go to the HTC website and unlock your phone via their steps, It's simple and you can't stuff it up.
***MAKE SURE YOU KEEP ALL FILES FROM THIS, AS YOU'LL BE NEEDING IT LATER ON***
***THIS WILL RESET YOUR PHONE SO MAKE SURE YOU CONTACTS AND ANYTHING ELSE YOU WANT IS BACKED UP***
***MAKE SURE YOU REMEMBER THE LAST STEP USING THE FILE HTC SEND YOU, AS YOU WILL NEED TO BE DOING THIS AGAIN LATER ON***
Step 2 - SuperCID
Firstly do this http://forum.xda-developers.com/showthread.php?p=41482419
Once done, go here: http://forum.xda-developers.com/showthread.php?t=2155069& and follow exactly!
Step 3 - S-OFF
Click here and follow exactly!
For steps 5 and 6 I reccomend combing those two lines of code into a .bat file and the same with step 7.
Step 4 - Downgrade Touch Screen
You can't go wrong if you follow this think exactly!
http://forum.xda-developers.com/showthread.php?t=2159863
Step 5 - Flash Custom Recovery
I reccomend CWM
Step 6 - Install ROM!
Ok! So you've done all the steps below and you're now ready for the best part!
1. Go to http://get.cm/?device=evita and download the latest CM10.1 nightly.
2. Locate 4.2.2 Gapps via a quick Google search.
3. Fully wipe your device from Recovery if you are not coming from CM10.1 already.
4. Reboot into recovery and install ROM and then Gaaps.
That's if and you're now done! You phone is now like every other Android phone out there and you can now install any ROM via the custom recovery! Without having to flash the boot.img seperatly.
If you want to go even further and get rid of the red text on boot about your phone being tampered, go here: http://forum.xda-developers.com/showthread.php?t=2156368&highlight=supercid
***I HAVEN'T DONE THIS AND I DON'T KNOW IF IT WORKS***
Would like to thank Darbness for his efforts in figuring most of this out and all the other XDA posters who made this possible! Without you guys I'd be stuffed :silly:
Feeling nice? Make a BTC donation to 1ABS6U1rX7ZC9DnN4bkt5zCEt2KcKGXFn9
Any testing done on AT&T One X?
Sorry only tested on the Telstra version (being the model I have). I've had CleanROM 6 R6 on my model which was built for AT&T and that seem to work except for tethering and major battery pwnage and that to me suggests that this -may- work.
I can only suggest that you try it and let me know how you go. It would he interesting to find out!
Good luck!
Sent from my One XL using xda app-developers app
Glad to help.
software number: 3.17.841.9
Eios said:
This is for all the people out there who currently have the most up to date version of the stock HTC One XL (Telstra) software/ firmware 3.17.xx and wish to be able to install CM10.1 and other ROMS alike.
I found it very hard to find all the information out there to be able to do this and now that it is finally done I feel the need to share this valuable information to all who are possibly having the same drama.
Here it is!
Step 1 - HTC Dev Unlock
This is easy! go to the HTC website and unlock your phone via their steps, It's simple and you can't stuff it up.
***MAKE SURE YOU KEEP ALL FILES FROM THIS, AS YOU'LL BE NEEDING IT LATER ON***
***THIS WILL RESET YOUR PHONE SO MAKE SURE YOU CONTACTS AND ANYTHING ELSE YOU WANT IS BACKED UP***
***MAKE SURE YOU REMEMBER THE LAST STEP USING THE FILE HTC SEND YOU, AS YOU WILL NEED TO BE DOING THIS AGAIN LATER ON***
Step 2 - SuperCID
Firstly do this http://forum.xda-developers.com/showthread.php?p=41482419
Once done, go here: http://forum.xda-developers.com/showthread.php?t=2155069& and follow exactly!
Step 3 - S-OFF
Click here and follow exactly!
For steps 5 and 6 I reccomend combing those two lines of code into a .bat file and the same with step 7.
Step 4 - Downgrade Touch Screen
You can't go wrong if you follow this think exactly!
http://forum.xda-developers.com/showthread.php?t=2159863
Step 5 - Flash Custom Recovery
I reccomend CWM
Step 6 - Install ROM!
Ok! So you've done all the steps below and you're now ready for the best part!
1. Go to http://get.cm/?device=evita and download the latest CM10.1 nightly.
2. Locate 4.2.2 Gapps via a quick Google search.
3. Fully wipe your device from Recovery if you are not coming from CM10.1 already.
4. Reboot into recovery and install ROM and then Gaaps.
That's if and you're now done! You phone is now like every other Android phone out there and you can now install any ROM via the custom recovery! Without having to flash the boot.img seperatly.
If you want to go even further and get rid of the red text on boot about your phone being tampered, go here: http://forum.xda-developers.com/showthread.php?t=2156368&highlight=supercid
***I HAVEN'T DONE THIS AND I DON'T KNOW IF IT WORKS***
Would like to thank Darbness for his efforts in figuring most of this out and all the other XDA posters who made this possible! Without you guys I'd be stuffed :silly:
Feeling nice? Make a BTC donation to 1ABS6U1rX7ZC9DnN4bkt5zCEt2KcKGXFn9
Click to expand...
Click to collapse
Hi All,
Was wondering if these steps are still valid for software number: 3.17.841.9 with Android 4.1.1 (One XL Telstra)?
For instance, do we still have to downgrade the touchscreen?
Also, when the phone is reset (wiped) from recovery, wouldn't this also wipe the images that I've downloaded?
Would I still be able to use the stock telstra image unstill Step 6 (after step 4 or 5 is complete)?
Thank you...
Cheers
Android_Sycamore said:
Hi All,
Was wondering if these steps are still valid for software number: 3.17.841.9 with Android 4.1.1 (One XL Telstra)?
Click to expand...
Click to collapse
Yep, should still work. If the downgrading hboot part doesn't work, you can also use jet tool to downgrade hboot then just RUU after S-OFF
Android_Sycamore said:
For instance, do we still have to downgrade the touchscreen?
Click to expand...
Click to collapse
Not for cm10.1 on 3.4 beta kernel. And not for sense Roms. Just remember that it is a beta kernel and there are some weird glitches and a few reported bricks so if you have no plan if your phone happens to brick, you may want to avoid it until it's stable. The chances of bricking are extremely slim, but it has happened.
Android_Sycamore said:
Also, when the phone is reset (wiped) from recovery, wouldn't this also wipe the images that I've downloaded?
Click to expand...
Click to collapse
So long as you don't select SD Card when wiping, it won't touch your SD Card.
Android_Sycamore said:
Would I still be able to use the stock telstra image unstill Step 6 (after step 4 or 5 is complete)?
Click to expand...
Click to collapse
After flashing custom recovery, your stock rom may not boot unless you flash su in recovery.
Root?
Eios said:
This is for all the people out there who currently have the most up to date version of the stock HTC One XL (Telstra) software/ firmware 3.17.xx and wish to be able to install CM10.1 and other ROMS alike.
I found it very hard to find all the information out there to be able to do this and now that it is finally done I feel the need to share this valuable information to all who are possibly having the same drama.
Here it is!
Step 1 - HTC Dev Unlock
This is easy! go to the HTC website and unlock your phone via their steps, It's simple and you can't stuff it up.
***MAKE SURE YOU KEEP ALL FILES FROM THIS, AS YOU'LL BE NEEDING IT LATER ON***
***THIS WILL RESET YOUR PHONE SO MAKE SURE YOU CONTACTS AND ANYTHING ELSE YOU WANT IS BACKED UP***
***MAKE SURE YOU REMEMBER THE LAST STEP USING THE FILE HTC SEND YOU, AS YOU WILL NEED TO BE DOING THIS AGAIN LATER ON***
Step 2 - SuperCID
Firstly do this http://forum.xda-developers.com/showthread.php?p=41482419
Once done, go here: http://forum.xda-developers.com/showthread.php?t=2155069& and follow exactly!
Click to expand...
Click to collapse
Hi Guys,
I started with following this guide. Went through the HTC DEV process without a hassle (cancelled and backed everything up just before flashing the unlock token - Phew!)
Then I get to the first part of step 2 for the SuperCID and it seems to require root.
Austempest said:
Apparently the 3.17.841.9 update placed a write protection on the CID partition, so the only way to gain SuperCID, then S-OFF to install an AOKP Rom is to downgrade.
This will only work if you stay within the same HBOOT versions. 3.17.841.9 and 3.17.841.2 are both on HBOOT 2.14. Both root and SU is needed.
Click to expand...
Click to collapse
I've found a few other guides that did the Custom recovery ROM immediately after the HTC Dev. http://forum.xda-developers.com/showthread.php?t=2326329
This thread suggests that it should then be possible to flash SuperSU to gain root. I'd guess I can't skip a step to flash a Custom ROM directly due to the issues with the 3.17.841.9 update.
Is this the right way to go?
Edit: It worked. Then followed the rest of the steps for SuperCID and S-OFF. If we don't have to downgrade the touchscreen as per exad's post above, then I'm good to go! Woot!
Looking at the CyanogenMod page for the OneXL it has the following:
HTC One XL
CM Support: 10, 10.1
Notes:
The CM 10.1 builds require you to be updated to the newest 3.17/3.18 RUU (for the updated firmware and the 2.14 hboot). You also must downgrade your touchscreen firmware, see here: http://forum.xda-developers.com/showpost.php?p=38304611&postcount=1
Click to expand...
Click to collapse
My phone is a Telstra HTC One XL (Evita). Current software is Android 4.1.1 Software Number 3.17.841.9
Cheers,
Aaron
You no longer need to downgrade your touchscreen firmware to run the latest aosp builds. If you want to run older builds you will need to though.
Sent from my Evita
Maybe out of wack :S
Hey all,
I hope this guide has helped some people, I know that with the HTC One XL doing everything can be a bit of a pain.
This guide was written up after I had done everything so some steps maybe out of wack. eg... Gaining Root before SuperCID.
I'll update this as best as possible and if anyone ever has any input to this to make things simpler then please just let me know.
Feeling nice? Make a BTC donation to 1ABS6U1rX7ZC9DnN4bkt5zCEt2KcKGXFn9
Why do you have two links for S-off? One being for the dna DROID.
Sent from my HTC One XL using xda app-developers app
Update to come.
exad said:
Why do you have two links for S-off? One being for the dna DROID.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Hmm good pointing out! Over the next few days I'll go through this whole guide and update as appropriate!
Feeling nice? Make a BTC donation to 1ABS6U1rX7ZC9DnN4bkt5zCEt2KcKGXFn9
Hi I had a simple confusion. Firstly the details of my phone are below
Super cid
vit Pvt ship S-OFF rl
Hboot 2.14.0000
Radio 0.23a. 32.09.29
OpeDSP - v31.1.0.45.0815
Emmc-boot
My first question is should I follow tesltra method or the AT&T rooting method since in a few threads I got the impression that I should be using the AT&T method but according to this thread I should be following this method.
Secondly I am by default S-OFF and super cid so do I need to unlock my bootloader to root?
Thanks
Sent from my HTC One XL using xda app-developers app
swagatk said:
Hi I had a simple confusion. Firstly the details of my phone are below
Super cid
vit Pvt ship S-OFF rl
Hboot 2.14.0000
Radio 0.23a. 32.09.29
OpeDSP - v31.1.0.45.0815
Emmc-boot
My first question is should I follow tesltra method or the AT&T rooting method since in a few threads I got the impression that I should be using the AT&T method but according to this thread I should be following this method.
Secondly I am by default S-OFF and super cid so do I need to unlock my bootloader to root?
Thanks
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Is your phone Telstra or at&t?
Sent from my Evita
Re: swagatk
swagatk said:
Hi I had a simple confusion. Firstly the details of my phone are below
Super cid
vit Pvt ship S-OFF rl
Hboot 2.14.0000
Radio 0.23a. 32.09.29
OpeDSP - v31.1.0.45.0815
Emmc-boot
My first question is should I follow tesltra method or the AT&T rooting method since in a few threads I got the impression that I should be using the AT&T method but according to this thread I should be following this method.
Secondly I am by default S-OFF and super cid so do I need to unlock my bootloader to root?
Thanks
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Hey mate,
If you're Telstra I would suggest this method, my phone is Telstra and thus this guide has been written up for those users. If you're AT&T this may work for you, however there maybe some weird bugs to go with... Or it may work 100% and honestly I wouldn't know.
I would highly suggest unlocking your bootloader and flashing a custom recovery onto your phone. Having this has saved my ass heaps of times when I've been stuffing around with new settings from custom ROMS.
Feeling nice? Make a BTC donation to 1ABS6U1rX7ZC9DnN4bkt5zCEt2KcKGXFn9
timmaaa said:
Is your phone Telstra or at&t?
Sent from my Evita
Click to expand...
Click to collapse
None. I have an unbranded phone and it's not locked with any network, which is the reason for the confusion
Sent from my HTC One XL using xda app-developers app
If it's unbranded, you can just go to htcdev and unlock your bootloader, then flash TWRP 2.6 recovery, then flash the ROM of your choice.
Sent from my Evita
Well, it's my first post on here, i've been reading about rooting/custom roms etc. for a few months now and i couldn't seem to find a nice method to root my htc one xl. I just read here that all i need to do is to to unlock the bootloader, is that correct ? can i directly flash a recovery and a custom rom after that ? (i'd like to try cyanogenmod 11)
thanks in advance, and by the way i love this forum it's very enlightning.
Yes. Unlock your bootloader, then you can install TWRP recovery, then you can install a custom ROM. You might need a firmware upgrade first though, what are your bootloader details?
Sent from my Evita.
timmaaa said:
Yes. Unlock your bootloader, then you can install TWRP recovery, then you can install a custom ROM. You might need a firmware upgrade first though, what are your bootloader details?
Sent from my Evita.
Click to expand...
Click to collapse
It says :
Locked
EVITA PVT SHIP S-ON RL
HBoot 2.15.0000
radio-1.31a.32.45.16_2
Opendsp-v33.1.0.45.1128
Jul 18 2013, 13:16:10:-1
Ok, that's fine. As long as the phone isn't an at&t model you can just go ahead and unlock at htcdev.
Sent from my Evita.
I have a European One S (S4) with Hboot 2.15. Unlocked via htcdev. I cant figure out how to get s-off. Writing supercid doesnt work.. How to fix it?
S1pk3 said:
I have a European One S (S4) with Hboot 2.15. Unlocked via htcdev. I cant figure out how to get s-off. Writing supercid doesnt work.. How to fix it?
Click to expand...
Click to collapse
Moonshine
http://forum.xda-developers.com/showthread.php?t=2325590
If you aren't on the supported firmware it won't work. So, if that doesn't work for you then I would just leave it S-on. It isn't hard to fastboot flash a boot.img before flashing a rom in recovery.
Ok, thanks for your reply. I want to flash cm 10.2. That should be possible without s-off?
Sent from my HTC One S using xda app-developers app
S1pk3 said:
Ok, thanks for your reply. I want to flash cm 10.2. That should be possible without s-off?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Yeah. It is just recommended that you are s-off.
As the guy said before you need to flash boot.img (the kernel) afterwards.
Sent from my One S using xda app-developers app
Will give it a try. Thanks.
Sent from my HTC One S using xda app-developers app
Stuck while flashing firmware in htc one s
I got stuck while installing htc one s with maximus hd..
http://forum.xda-developers.com/showthread.php?t=2445392&highlight=sense+5
I did till fastboot flash recovery TWRP2.6.1.0.img ...but aftr fast boot reboot it dint take memory...without that i cant copy ROM to memory...i did unlock bootloader not s off.... i got an error99 while flashing firmware.. icant on the device now....please help me...
tivofool said:
Moonshine
http://forum.xda-developers.com/showthread.php?t=2325590
If you aren't on the supported firmware it won't work. So, if that doesn't work for you then I would just leave it S-on. It isn't hard to fastboot flash a boot.img before flashing a rom in recovery.
Click to expand...
Click to collapse
I just noticed this thread.
I also have a similar problem. I cannot achieve s-off with my (S4) htc one s , running the exact same hboot as op.
To upgrade to jb 4.2.2 sense 5 which we should be getting for which we now won't despite them making the update.
Will we be able to upgrade to this new patch with s-on using the flash boot?
sylvantino said:
I just noticed this thread.
I also have a similar problem. I cannot achieve s-off with my (S4) htc one s , running the exact same hboot as op.
To upgrade to jb 4.2.2 sense 5 which we should be getting for which we now won't despite them making the update.
Will we be able to upgrade to this new patch with s-on using the flash boot?
Click to expand...
Click to collapse
Maximus HD --- No you need S-off for this. The firmware updates your Hboot, Radio, and you flash a different recovery and finally Rom
You might check out other Rom's that have Sense 5 4.2.2 features. They do not require S-off like Maximus does.
Hi thanks for your reply.
Do you know of any such roms that don't require the s-off?
I installed odyssey, its got no google playstore..suddenly my computer no longer recognizes my sd card / phone.
I tried adb push, managed to get a stock orang001 tmobile uk package to the root folder, but when i turn off the mount, it says its bad..which is a little odd.
Seems thought I got odyssey installed / flashed etc, its so bare as its practically useless to me unless i have google, plus its got weird glitches on boot up, taking forever, always booting into the developers screen etc.
sylvantino said:
Hi thanks for your reply.
Do you know of any such roms that don't require the s-off?
I installed odyssey, its got no google playstore..suddenly my computer no longer recognizes my sd card / phone.
I tried adb push, managed to get a stock orang001 tmobile uk package to the root folder, but when i turn off the mount, it says its bad..which is a little odd.
Seems thought I got odyssey installed / flashed etc, its so bare as its practically useless to me unless i have google, plus its got weird glitches on boot up, taking forever, always booting into the developers screen etc.
Click to expand...
Click to collapse
With Odyssey you have to flash slim gapps after you install the rom.
Your Sd card (partition) may be corrupted, the way to fix that is to put the stock recovery back on your phone then go to bootloader and "clear storage"
All of the other Roms don't require S-off, MagioRom is being actively developed with the sense 5 and 4.2.2.
tivofool said:
With Odyssey you have to flash slim gapps after you install the rom.
Your Sd card (partition) may be corrupted, the way to fix that is to put the stock recovery back on your phone then go to bootloader and "clear storage"
All of the other Roms don't require S-off, MagioRom is being actively developed with the sense 5 and 4.2.2.
Click to expand...
Click to collapse
thanks for the information. i read through magiorom thread. trying to download now.seems a flaky webhost
tivofool said:
Moonshine
http://forum.xda-developers.com/showthread.php?t=2325590
If you aren't on the supported firmware it won't work. So, if that doesn't work for you then I would just leave it S-on. It isn't hard to fastboot flash a boot.img before flashing a rom in recovery.
Click to expand...
Click to collapse
Hi would moonshine work for hboot 2.16 ?
cyberusman said:
Hi would moonshine work for hboot 2.16 ?
Click to expand...
Click to collapse
No, it is hard enough to get it to work on the supported firmware. (I would love to be proven wrong, for the handful of people that need this)
tivofool said:
No, it is hard enough to get it to work on the supported firmware. (I would love to be proven wrong, for the handful of people that need this)
Click to expand...
Click to collapse
Well i have hboot 2.16 and i need to s-off i get this error when trying to flash the ruu its error 99 unknown fail i get it twice
tivofool said:
Maximus HD --- No you need S-off for this. The firmware updates your Hboot, Radio, and you flash a different recovery and finally Rom
You might check out other Rom's that have Sense 5 4.2.2 features. They do not require S-off like Maximus does.
Click to expand...
Click to collapse
I was able to load Maximus HD ROM with S-On but only issue I had was wireless.
santo_2k said:
I was able to load Maximus HD ROM with S-On but only issue I had was wireless.
Click to expand...
Click to collapse
Please tell me how did you manage to install MaximusHD ROM without S-off!
I'm a little scared since I read they have a lot of problems while installing this ROM.
I'm using CM10.1 right now, but I would like to have sense 5 on my HTC One S.
I have unlocked boot loader and TWRP recovery.
I read there are other ROMS with sense 5 like MagioRom, which doesn't require S-Off (As far as I know)
Is there a great difference between MagioRom and MaxiumusHD? All I want is Sense 5 on my phone without all the terrible of S-offing!!
Sent from my One S using xda app-developers app
rolo143 said:
Please tell me how did you manage to install MaximusHD ROM without S-off!
I'm a little scared since I read they have a lot of problems while installing this ROM.
I'm using CM10.1 right now, but I would like to have sense 5 on my HTC One S.
I have unlocked boot loader and TWRP recovery.
I read there are other ROMS with sense 5 like MagioRom, which doesn't require S-Off (As far as I know)
Is there a great difference between MagioRom and MaxiumusHD? All I want is Sense 5 on my phone without all the terrible of S-offing!!
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
I tried Maximus with CWM, did i using sideload and them flash the boot.img file. but it was a disaster as my device didn't connect to wifi and had some call drops then I tried flashing twrp and then sideloaded magicrom 4.0 and flas boot.img, it looks lot better now but only issue right now is my phone keeps on rebooting and am still waiting for a stable rom to be released.
I read MagioRom comments and they say with that ROM phone reboots a lot. So I think the only way is with MaximusHD. The WiFi problem I think it can be fixed. I don't know about the call drops, but many have this ROM as daily use so I guess it's ok. I will try S-off with moonshine method, then try install Maximus. Hope my phone survives.
Sent from my One S using xda app-developers app
Hi guys
I'd like to know if it's possible to root my phone and get S-OFF because I want to run MaximusHD on my One S.
So the 'specs' are the following
*** LOCKED ***
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.15.50.05.29
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012, 17:10:57:-1
Android 4.1.1
Sense 4+
3.16.401.9
SDK 4.63
HTCExtension_Sense45_2
If it is possible what tutorial should I follow? And is SuperCID necessary voor MaximusHD?
Thanks!
From here, your options are:
-Get an unlock code from htcdev and unlock the bootloader. This will let you flash the Maximus ROM. You are still S-ON at this point so you need to flash the boot.img file that came with the ROM after flashing the ROM using a custom recovery like TWRP
-Get SuperCID and use Facepalm to get S-OFF. From here you can just flash the ROM. Done.
-Use Moonshine to get S-OFF. This may work... your stock software is not one of the officially supported versions...
I think s-off is really needed, why?
Upgrading hboot can normally be done with s-on, but going back is the real problem then you need s-off.
Supercid is not needed. S-off is. (sometimes supercid is needed temporarily to get s-off)
The .9 firmware is problematic for s-off with facepalm. .8 will work. (you maybe can reruu to .8)
Or Try moonshine, check 4 compatiblity first.
Verstuurd van mijn HTC One S met Tapatalk
I am having the same problem when trying to get S-OFF. I have succesfully rooted and installed the Super CID. But when entereing the following command during the Facepalm S-OFF process, it fails:
Code:
c:\Development\android\UNLOCK>adb shell su -c "/data/local/tmp/soffbin3"
Segmentation fault
My software version is also .9. So maybe just this partition part is locked with this software version.
I have already tried installing RUU .8, but it failed the first time. Will do it again the other day.
It is possible considering I had the same Hboot and specs as you did.
To get S-OFF, I first ran the 3.14.531.11 RUU (I have T-Mobile) [Note: make sure to lock the bootloader before you run the RUU - fastboot oem lock] The RUU can be found http://www.androidruu.com/index.php?developer=Ville <- that thread. Considering you might be using a different network and what not, just make sure the supported RUU for moonshine is the one you run for you phone.
After that I ran moonshine S-OFF. I tried with Windows 8, I kept getting stuck on the process. What I ended up doing was partitioning a spare Harddrive and installing Ubuntu on it (partitioning is part of the installation). You can maybe run it from the disk as well, but I have not tried it. Moonshine worked the first run for me and got S-OFF.
With the MaximusHD you need SuperCID as well, with S-OFF, you can just use the command fastboot writecid 11111111 when you got the fastboot usb.
Flash rom, follow the instructions for the firmware. Reflash the firmware if you have troubles with the internal SD.
My two cents, I tried Maximus, it's is nice, however I like using my phone has a wireless hotspot for my tablet, and it doesn't allow me that function. I used Dark Jelly instead and haven't had that problem. However tethering and bluetooth is causing me some troubles. Just throwing it out there. Hope this helps.
I have maximushd and I have no issues using my phone as a Wi-Fi hotspot. Didn't even have to install any separate apps for it
Sent from my HTC One S using xda app-developers app
rgrpark said:
I have maximushd and I have no issues using my phone as a Wi-Fi hotspot. Didn't even have to install any separate apps for it
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Weird, I might try reflashing MaximusHD then, it had a very nice look to it. Quick question, what network are you running on?
myl0h said:
Weird, I might try reflashing MaximusHD then, it had a very nice look to it. Quick question, what network are you running on?
Click to expand...
Click to collapse
I'm on the $30 t mobile Wal-Mart plan
Sent from my HTC One S using xda app-developers app
rgrpark said:
I'm on the $30 t mobile Wal-Mart plan
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Thanks, I'm running T-Mobile too, guess I have a mini project to do when I go home then.
Hi guys,
so happy to be a part of this community!
My HTC One S is unlocked, rooted and S-ON:
CID: T-MOB102
HBOOT: 2.15
I'm currently using MaximusHD 10.0 (though I couldn't make the firmware upgrade because I'm not S-OFF).
I'm creating this thread because none of the currently opened ones covers my case. I wanted to S-OFF earlier and tried Facepalm but could not get superCID (as far as I know this is because of the write protection), so this method didn't work for me. Moonshine I think will not work also, because I'm not using a stock ROM. ( From the Moonshine instructions: 8. Use the matching Stock RUU, some stock based ROMs may work, but we cannot test them all.)
Before flashing MaximusHD 10.0 I've made a backup of my original 4.1.1 ROM that came with the device with the custom recovery (TWRP 2.4.3.0 as far as I can remember). Unfortunately when I try restoring from backup my device is in a bootloop.
Can you please advise how to obtain S-OFF so that I can enjoy the MaximusHD?
Please accept my apologies if this is not the right place for this thread.
Did you try this?
http://forum.xda-developers.com/showthread.php?t=2511027
Sent from HTC One S using android 4.2.2 sense 5
tominozh said:
Did you try this?
http://forum.xda-developers.com/showthread.php?t=2511027
Sent from HTC One S using android 4.2.2 sense 5
Click to expand...
Click to collapse
No, unfortunately I could not find stock RUU for TMOBA devices
If you need stock ruu go to www.htc.com and select your device and download the file for this file to work you need your bootloader to be lock stock or relocked. and just run the ruu and it shold work..
so you dont have any problems enter fastboot and make sure it says fastboot usb and than run ruu and it should put your phone to stock. I just did this with my phone.
Are you refering to the downloads at htcdev because I couldn't find anything else?
Hi guys,
I am on an old JellyBAM ROM (7.7.0), based on CyanogenMod 10.1.0 (Android 4.2.2). I want to try KitKat roms (4.4.2) such as latest CM 11 nightlies etc. So I want to know what all I need to do to get my phone ready to install 4.4 roms.
Some background:
I unlocked my bootloader using HTC Dev Token ID method, installed CWM recovery, and flashed my current and past roms that way - it has been around a year since I made any updates to my phone. So I think some of my firmware is not current enough to support 4.4 roms.
I am S-ON.
My main concern is that I have hboot 1.08. All the guides I see talk about either hboot 2.15 or 2.16.
Recovery: CWM v5.8.3.1
Phone is carrier-free Ville S4 processor. Currently service provider is Koodo - a division of Telus (in Canada).
CID: ROGER001
Radio: 0.16.31501S.02
From the reading that I did, what I understood is:
First I should S-OFF (to make things easier for any future playing around). I was thinking of using the Firewater S-OFF Tool (from http://www.androidpolice.com/2014/0...f-tool-will-unlock-any-htc-device-in-moments/)
I need to update my hboot. This is the step I am most worried about, as I have never flashed a RUU before, and that's what most guides say to do. This thread says to just run the JellyBean RUU [http://forum.xda-developers.com/showthread.php?t=2524306]. Would you say that's a pretty safe bet, or is that outdated advice/information?
Once I go S-OFF and update hboot to 2.15, can I just flash CWM (or TWRP) recovery, and flash CM 11 nightlies?
Thanks a lot!
arjundas86 said:
Hi guys,
I am on an old JellyBAM ROM (7.7.0), based on CyanogenMod 10.1.0 (Android 4.2.2). I want to try KitKat roms (4.4.2) such as latest CM 11 nightlies etc. So I want to know what all I need to do to get my phone ready to install 4.4 roms.
Some background:
I unlocked my bootloader using HTC Dev Token ID method, installed CWM recovery, and flashed my current and past roms that way - it has been around a year since I made any updates to my phone. So I think some of my firmware is not current enough to support 4.4 roms.
I am S-ON.
My main concern is that I have hboot 1.08. All the guides I see talk about either hboot 2.15 or 2.16.
Recovery: CWM v5.8.3.1
Phone is carrier-free Ville S4 processor.
Radio: 0.16.31501S.02
From the reading that I did, what I understood is:
First I should S-OFF (to make things easier for any future playing around). I was thinking of using the Firewater S-OFF Tool (from http://www.androidpolice.com/2014/0...f-tool-will-unlock-any-htc-device-in-moments/)
I need to update my hboot. This is the step I am most worried about, as I have never flashed a RUU before, and that's what most guides say to do. This thread says to just run the JellyBean RUU [http://forum.xda-developers.com/showthread.php?t=2524306]. Would you say that's a pretty safe bet, or is that outdated advice/information?
Once I go S-OFF and update hboot to 2.15, can I just flash CWM (or TWRP) recovery, and flash CM 11 nightlies?
Thanks a lot!
Click to expand...
Click to collapse
Whats your CID?
You don't need to be S-OFF if theres a matching RUU for you BUT you cant install lower HBoot versions while you're S-ON. Flashing a custom recovery is also possible while you're S-ON
LS.xD said:
Whats your CID?
You don't need to be S-OFF if theres a matching RUU for you BUT you cant install lower HBoot versions while you're S-ON. Flashing a custom recovery is also possible while you're S-ON
Click to expand...
Click to collapse
I am not sure - I have never checked it before.
I ran CID Getter app, and it's supposed to show me CID in red at the top, but it shows nothing. Some of the app comments say that if the CID is not shown, it means I am SuperCID. I'm not sure about that.
I'm at work, but when I get home, I'll run the fastboot command to find out the CID. I didn't do anything intentionally to get SuperCID, so is it likely that I might be SuperCID? How would I know?
arjundas86 said:
I am not sure - I have never checked it before.
I ran CID Getter app, and it's supposed to show me CID in red at the top, but it shows nothing. Some of the app comments say that if the CID is not shown, it means I am SuperCID. I'm not sure about that.
I'm at work, but when I get home, I'll run the fastboot command to find out the CID. I didn't do anything intentionally to get SuperCID, so is it likely that I might be SuperCID? How would I know?
Click to expand...
Click to collapse
SuperCID = 11111111
Other CIDs are listed here: HTC CID LIST
You can easiliy read the CID with WinDroid Toolkit 2.0
LS.xD said:
SuperCID = 11111111
Other CIDs are listed here: HTC CID LIST
You can easiliy read the CID with WinDroid Toolkit 2.0
Click to expand...
Click to collapse
Thanks for the toolkit.
cid: ROGER001
Btw, what's the purpose of going SuperCID?
Also, I don't want to install lower hboot. I am on hboot 1.08 and I think I need to install hboot 2.15. Right?
I guess S-OFF isn't absolutely necessary, but would be nice to have. Would you recommend using the S-OFF command from the toolkit you linked?
I Don't know which s-off Method is Best for your cid. Have you found matching RUU with hboot 2.15?
With superCID you can switch to other CIDs e.g. for unbranding your device Also it's needed for "Facepalm S-OFF" (Was the only working method for me)
Sent from my loved HTC One S using (most time buggy) Tapatalk
LS.xD said:
I Don't know which s-off Method is Best for your cid. Have you found matching RUU with hboot 2.15?
Sent from my loved HTC One S using (most time buggy) Tapatalk
Click to expand...
Click to collapse
I have seen a few options for RUU, but not sure which one I should use. I don't quite understand the relationships between phone parameters and which RUU to get.
The guide that I linked to in my first post, that I was thinking of using says the following one: (but they don't know what my CID is)
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.5 0.05.31_10.30.50.08L_release_309489_signed_ICS_2.exe
Androidruu.com has several other RUUs. I guess since my CID says Rogers, I should use one of the Rogers ones?
RUU_Ville_U_Rogers_WWE_1.70.631.1_Radio_0.16.31501S.02_10.18.31501S.08L_release_254139_signed.exe - 2013-01-29
or
RUU_Ville_U_Rogers_WWE_1.84.631.9_Radio_0.17.31501S.10_2_10.27.31501S.10L_release_265373_signed.exe - 2013-04-29
But my current provider is Koodo, which is a subdivision of Telus. So should I use one of the Telus RUUs?
RUU_Ville_U_TELUS_WWE_1.70.661.1_Radio_0.16.31501S.02_10.18.31501S.08L_release_254554_signed.exe - 2013-01-29
or
RUU_Ville_U_TELUS_WWE_1.84.661.9_Radio_0.17.31501S.10_2_10.27.31501S.10L_release_265367_signed.exe - 2013-04-29
I would appreciate any insights into what would be the applicable RUU?
Thanks.
arjundas86 said:
I have seen a few options for RUU, but not sure which one I should use. I don't quite understand the relationships between phone parameters and which RUU to get.
The guide that I linked to in my first post, that I was thinking of using says the following one: (but they don't know what my CID is)
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.5 0.05.31_10.30.50.08L_release_309489_signed_ICS_2.exe
Androidruu.com has several other RUUs. I guess since my CID says Rogers, I should use one of the Rogers ones?
RUU_Ville_U_Rogers_WWE_1.70.631.1_Radio_0.16.31501S.02_10.18.31501S.08L_release_254139_signed.exe - 2013-01-29
or
RUU_Ville_U_Rogers_WWE_1.84.631.9_Radio_0.17.31501S.10_2_10.27.31501S.10L_release_265373_signed.exe - 2013-04-29
But my current provider is Koodo, which is a subdivision of Telus. So should I use one of the Telus RUUs?
RUU_Ville_U_TELUS_WWE_1.70.661.1_Radio_0.16.31501S.02_10.18.31501S.08L_release_254554_signed.exe - 2013-01-29
or
RUU_Ville_U_TELUS_WWE_1.84.661.9_Radio_0.17.31501S.10_2_10.27.31501S.10L_release_265367_signed.exe - 2013-04-29
I would appreciate any insights into what would be the applicable RUU?
Thanks.
Click to expand...
Click to collapse
As long as you are S-ON you can only flash matching RUUs (Rogers). You will need to gain S-OFF to reach HBoot 2.15 as it seems.
LS.xD said:
As long as you are S-ON you can only flash matching RUUs (Rogers). You will need to gain S-OFF to reach HBoot 2.15 as it seems.
Click to expand...
Click to collapse
Okay. It seems that the best path forward for me is to S-OFF using the Firewater tool (since my device is HTCDEV unlocked/rooted, and having S-OFF means I won't need to unlock bootloader again after running RUU).
Then I'll run the newest Rogers RUU from AndroidRUU.
At this point, I should be on hboot 2.15 and still bootloader unlocked, right?
If I'm right about all that, then I should just have to install a custom recovery and be able to flash the 4.4 ROM I want. Correct?
arjundas86 said:
Okay. It seems that the best path forward for me is to S-OFF using the Firewater tool (since my device is HTCDEV unlocked/rooted, and having S-OFF means I won't need to unlock bootloader again after running RUU).
Then I'll run the newest Rogers RUU from AndroidRUU.
At this point, I should be on hboot 2.15 and still bootloader unlocked, right?
If I'm right about all that, then I should just have to install a custom recovery and be able to flash the 4.4 ROM I want. Correct?
Click to expand...
Click to collapse
Newest Rogers RUU ist HBoot 1.84 as it seems. Once you're S-OFF and have superCID you need to change your CID to unbranded (HTC__001) and flash e.g. unbranded RUU with HBoot 2.15.
LS.xD said:
Newest Rogers RUU ist HBoot 1.84 as it seems. Once you're S-OFF and have superCID you need to change your CID to unbranded (HTC__001) and flash e.g. unbranded RUU with HBoot 2.15.
Click to expand...
Click to collapse
Hmm... I see. Things are getting clearer, but still a little confused about SuperCID stuff.
Will running Tmobile US RUU work? That's the one from the guide I read in my first post. He suggests that RUU to get hboot 2.15.
Once I get S-OFF, then I should get SuperCID. I thought with SuperCID (i.e. 11111111), I can run any RUU. Or should I still manually set CID to HTC__001 before running Tmobile US RUU?
arjundas86 said:
Hmm... I see. Things are getting clearer, but still a little confused about SuperCID stuff.
Will running Tmobile US RUU work? That's the one from the guide I read in my first post. He suggests that RUU to get hboot 2.15.
Once I get S-OFF, then I should get SuperCID. I thought with SuperCID (i.e. 11111111), I can run any RUU. Or should I still manually set CID to HTC__001 before running Tmobile US RUU?
Click to expand...
Click to collapse
To run a RUU NOT MATCHING your stock CID you need S-OFF // SuperCID. You cant install TMobile RUU at first :/
I would act like this:
Run latest Rogers RUU --> READ FACEPALM GUIDE CAREFULLY. There is how to gain SuperCID and then S-OFF. Once done you can change CID to whatever you want and run a (unbranded) RUU with HBoot 2.15.
But that is just what i thought about it. I suggest to let someone else CONFIRM the way suggested by me first.
Have you tried anything yet? If NO. then STOP. Don't do anything and don't upgrade your firmware/hboot yet. It could happen you won't need this. I am on hboot 1.06 and I'm running fine any ROM including KitKat ones. That requirement for a higher firmware is coming from an old issue that was before with earlier Android versions (from the versions that used 3.4.x kernel and up), making SOME phones to misbehave (reboots or other issues). It could be that your phone handles it right and in that case you won't need to upgrade if you don't want to.
WHY? You should not only upgrade your firmware but also to S-Off. It is not required but it makes your life easier. And these procedures bear some risks even if they were successful for others. And why should you risk anything unless it's mandatory? The point is you have a hboot lower than 1.09. There are not to many left and people are tempted to forget, but hboot lower than 1.09 means you're like an S-Off. You can flash radios and kernels from recovery as on any other S-Off device. Only thing you can't do is to remove those red letters from the boot splash screen...that is you can't flash another firmware. But hopefully you might not need it.
OK. All these being said, I would suggest you to first try to see if the ROM works OK on your phone like it is and only if it doesn't you should think about S-Off, upgrading firmware and things like this.
Now, what you have to do is download the ROM you would like...any ROM, and before flashing it follow my guide HERE to change the updater script in the ROM's ZIP to allow flashing the ROM on lower hboots. It is very easy, I do this usually in 1 min, I would suggest to use method 2 that's much easier than to follow all detailed steps in method 1. If you have any questions or unclear things ask but I think it's easy enough.
If after this you cannot boot the ROM or have it working, then you can think of upgrading firmware
@Rapier
thank you for the provided help as usual
Are there any advantages by unsing HBoot 1.06?? I'm on 2.15 // S-OFF // SuperCID // No red letters // "tampered" removed
LS.xD said:
...Are there any advantages by unsing HBoot 1.06?? I'm on 2.15 // S-OFF // SuperCID // No red letters // "tampered" removed
Click to expand...
Click to collapse
For you? NO. You're better than me
The story is like this. I bought the phone in 2012. At that time, the highest hboot was 1.14 I believe (don't remember exactly) and there was no S-Off method available (they appeared later). There was something else tho. The lower hboots (1.09 and lower) permitted to write in the kernel partition or radio partition like an S-Off device. HTC then covered this in the higher hboots. So even if there was no S-Off method, there was a downgrade method that was used to downgrade the hboot from whatever you had to 1.09 or below. I downgraded mine to 1.06...don't ask why I didn't choose 1.09, I thought that was the RUU I considered to be fine for me at that time.
Now being on hboot 1.06 I can do anything except I cannot flash firmwares directly. So I cannot flash a new hboot with red letters removed for example. But I don't care about this...I can flash radios or kernels or splash screens like any S-Off user. The procedure for getting latest firmware and S-Off seems a little bit risky and I've read about alot of issues or problems from people who failed or tried countless times to reach that. So I've asked myself why should I do that if I don't need it?
Then it came the rumor and there were some brick cases of devices that were having some Android 4.3 ROMs and were not on latest firmware (in the meantime 2.13 and 2.15 hboots arise and also the S-Off method). It proved to be not the firmware fault after all. But CM team has included a check in the updater script of the ROM ZIP, to validate if the hboot was 2.13 or 2.15...if not, the flash won't happen. It's a simple assert command present there at the beginning of the script that do the check. As CM team was the pioneer in having the newest Android version ROMs available, everybody based initially their ROMs/builds on CM...so the check in the script was automatically carried over to all the ROMs out there. And it's still here.
As I've tested and I could run fine those ROM's (by removing the check before flash), I noticed that this requirement does not apply to everyone. Some could run fine the ROMs even if they're not on the "latest" firmware.
So that's why I am on 1.06...cause I don't know why should I go through some risky procedures when I don't need to.
Rapier said:
Have you tried anything yet? If NO. then STOP. Don't do anything and don't upgrade your firmware/hboot yet. It could happen you won't need this. I am on hboot 1.06 and I'm running fine any ROM including KitKat ones. That requirement for a higher firmware is coming from an old issue that was before with earlier Android versions (from the versions that used 3.4.x kernel and up), making SOME phones to misbehave (reboots or other issues). It could be that your phone handles it right and in that case you won't need to upgrade if you don't want to.
OK. All these being said, I would suggest you to first try to see if the ROM works OK on your phone like it is and only if it doesn't you should think about S-Off, upgrading firmware and things like this.
Now, what you have to do is download the ROM you would like...any ROM, and before flashing it follow my guide HERE to change the updater script in the ROM's ZIP to allow flashing the ROM on lower hboots. It is very easy, I do this usually in 1 min, I would suggest to use method 2 that's much easier than to follow all detailed steps in method 1. If you have any questions or unclear things ask but I think it's easy enough.
If after this you cannot boot the ROM or have it working, then you can think of upgrading firmware
Click to expand...
Click to collapse
I did read in more than one thread that you MUST have hboot 2.15 to install KitKat roms. Also, on CyanogenMod website, it says:
Firmware compatibility:
CM 10.1-11.0: HBOOT 2.13.0000, 2.15.0000, 2.15.4444.But no, I haven't done anything yet. So first of all, I'll make a nandroid backup and then just try factory reset, wipe cache/dalvik, and flash a CM 11 ROM, and see if it works. I'll post here whether it worked or not, I won't have time to do this until the weekend though.
Thanks, btw.
Rapier said:
WHY? You should not only upgrade your firmware but also to S-Off. It is not required but it makes your life easier. And these procedures bear some risks even if they were successful for others. And why should you risk anything unless it's mandatory? The point is you have a hboot lower than 1.09. There are not to many left and people are tempted to forget, but hboot lower than 1.09 means you're like an S-Off. You can flash radios and kernels from recovery as on any other S-Off device. Only thing you can't do is to remove those red letters from the boot splash screen...that is you can't flash another firmware. But hopefully you might not need it.
Click to expand...
Click to collapse
I don't get what you're saying. It is still worth getting S-OFF, or it is not?
arjundas86 said:
I did read in more than one thread that you MUST have hboot 2.15 to install KitKat roms. Also, on CyanogenMod website, it says:
Firmware compatibility:
CM 10.1-11.0: HBOOT 2.13.0000, 2.15.0000, 2.15.4444.But no, I haven't done anything yet. So first of all, I'll make a nandroid backup and then just try factory reset, wipe cache/dalvik, and flash a CM 11 ROM, and see if it works. I'll post here whether it worked or not, I won't have time to do this until the weekend though.
Thanks, btw.
I don't get what you're saying. It is still worth getting S-OFF, or it is not?
Click to expand...
Click to collapse
I beg to differ answering first:
Just try if you can install your preferred rom, AFTER you edited the "updatescript" as suggested by @Rapier.
IN CASE you have problems with the new rom you should get S-OFF + upgrading HBoot to 2.15+
LS.xD said:
I beg to differ answering first:
Just try if you can install your preferred rom, AFTER you edited the "updatescript" as suggested by @Rapier.
Just IN CASE you have problems with the new rom you should get S-OFF + upgrading HBoot to 2.15+
Click to expand...
Click to collapse
Yes, you're right. That's what I meant. I will delete the updater-script lines that Rapier mentioned before trying to install CM11.
If it doesn't work, at least I can restore to my backup, without risk of bricking.
Then I can try the hboot update and s-off if required.
Thanks.
arjundas86 said:
I did read in more than one thread that you MUST have hboot 2.15 to install KitKat roms. Also, on CyanogenMod website, it says:
Firmware compatibility:
CM 10.1-11.0: HBOOT 2.13.0000, 2.15.0000, 2.15.4444....
Click to expand...
Click to collapse
Yes, they say so. Then I'm the living proof that this requirement is not true...sorry for that. I've explained above to LS.xD where this requirement came from. The point is that you might have the ROM working even if you're on 1.08 and in this case you won't need to upgrade if you don't want
arjundas86 said:
...I don't get what you're saying. It is still worth getting S-OFF, or it is not?
Click to expand...
Click to collapse
It's depending on what you want. If you want to get rid of that red warning, to have the latest hboot and to have less trouble when flashing ROMs then yes, it worth it. If you just want to upgrade your firmware to 2.15 (to match the ROM requirements) but do not want to make the S-Off, you will have to flash the kernel separately in fastboot mode, after each ROM flash. Also you won't be able to flash a radio. That's why I said that if you are going to upgrade the firmware you should get S-Off as well
BUT, if you're NOT going to upgrade your firmware and you'll be lucky to have the ROM working, you won't need to S-Off since your current hboot is lower than 1.09 and allows you to flash radios and kernels directly from recovery.
And at this point, as you said, it worth a try like you are now and only if it's not working like this you should upgrade and do S-Off. I guess is much easier and less risky to remove 4 lines from that script and flash the ROM to see if it's working, than to go through the firmware upgrade & S-Off procedures
Rapier said:
Yes, they say so. Then I'm the living proof that this requirement is not true...sorry for that. I've explained above to LS.xD where this requirement came from. The point is that you might have the ROM working even if you're on 1.08 and in this case you won't need to upgrade if you don't wantIt's depending on what you want. If you want to get rid of that red warning, to have the latest hboot and to have less trouble when flashing ROMs then yes, it worth it. If you just want to upgrade your firmware to 2.15 (to match the ROM requirements) but do not want to make the S-Off, you will have to flash the kernel separately in fastboot mode, after each ROM flash. Also you won't be able to flash a radio. That's why I said that if you are going to upgrade the firmware you should get S-Off as well
Click to expand...
Click to collapse
Hey Rapier,
I'm having trouble doing getting the zip signed.
I tried the zip signer you had in your guide, as well as a bunch of other zip signing programs, but none of them seem to do the job. I keep getting Error: Status 7.
Not getting bootloops or anything like that, so I was able to restore to my backup. No harm done.