Related
This is for International hTC One XL/Evita - Hboot 2.14 & firmware 3.17 (Orange UK)
If you own AT&T One X please look elsewhere, this guide is not for your phone
There is an abundance of information scattered in these forums and not all root methods/exploits work universally due to variation in firmware builds and Hboots.
I had to read a lot of threads to figure out how to S-off my Orange UK One XL with Hboot 2.14 and firmware build 3.17.
I was only interested in attaining S-off but had to start with HTCDev bootloader unlocking which I didn't really want to do but none of the known root exploits worked on my firmware.
I am sharing this hoping it would help others avoid taking pills for headaches when pursuing this noble quest
AIM:
Provide a short guide to others with similar device and configuration on where to start and simple clear steps to follow with needed links.
PREREQUISITES:
1. latest htc drivers for your Windows PC/laptop if you have one of those. Check here.
2. a working adb environment preferably from latest Android SDK, if you don't have this already set up please check here.
3. "USB debugging" must be checked under Phone settings>Developer options
4. an original htc USB cable is strongly recommended.
5. phone charged at above 50%
6. basic knowledge of using command prompt (cmd) in Windows and adb commands.
STEPS:
So in my case the steps were:
[1] Unlock bootloader through htcdev.com
[2] Flash/install TWRP recovery
This is done manually. All-In-One Toolkit didn't work for me BTW.
1. download latest TWRP recovery for One XL/Evita from here
2. you can rename file for easier command prompt typing later, like TWRP5.img
3. place file recovery file in your adb/fastboot folder
4. connect phone in fastboot mode to PC, make sure it displays fastboot USB on phone before you proceed.
5. start command prompt from within fastboot folder by right clicking inside folder and choosing "open prompt here", type following command:
Code:
C:\yourFastbootFolder> fastboot flash recovery TWRP5.img
Not a bad idea to test your recovery by making a nandroid backup before proceeding to next step.
[3] Flash a custom rom (root)
All custom roms are rooted by definition. If you chose e.g. ViperXL like I did remember to flash boot.img extracted form same rom zip afterwards, otherwise bootloop!
You can of course flash a SuperSU zip instead to gain root but I don't see the point.
[4] SuperCID
This is the simplest way that I found accidentally during my endless searches, all credit goes to @beaups for this one and @Austempest for sharing :good:
1. connect phone to PC in Android mode (mode where you can use phone)
2. Run the following command from command prompt (CMD):
Code:
C:\>adb shell
To enter adb shell, then enter following commands after each other:
Code:
# su
# echo -ne "11111111" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
3. Reboot to bootloader and hopefully you'll see 11111111 as your CID ...... yes
[5] S-Off
Now that your are rooted with SuperCID you can just follow @beaups simple steps for S-Off found here Facepalm S-Off
That is it.... you broke your shackles :laugh:
I am not a dev and for sure not taking credit for other people's work, merely giving back and hoping this assists clarify stuff and save some time.
Cheers!
the one clicks would not work for you because you dont have an att one x so the supercid exploit doesnt work on our phones
all phones go through htcdev.com to unlock, att phones just need supercid first.
you should make a not in your guide that this guide wont work for at&t phones.
exad said:
the one clicks would not work for you because you dont have an att one x so the supercid exploit doesnt work on our phones
all phones go through htcdev.com to unlock, att phones just need supercid first.
you should make a note in your guide that this guide wont work for at&t phones.
Click to expand...
Click to collapse
Thanks for this important reminder, note added in red on top!
You mentioned one click is only for AT&T phones, I guess you mean All-In-One Toolkit by hason2000, you see even in the tool's thread it's not stated explicitly that tool works only for AT&T, while the respective threads for these exploit state that it's for AT&T One X not negating other international versions!
Most guides/tools are for North America and some Australia but very few for Europe which BTW only recently came on board with 4G/LTE.
So figuring out, especially for noobs, what is what with all these international variations for one device and huge amount of information, while searching doesn't always provide an answer is a tedious task and can end up miserably :crying:
I hope it's in order to add some info for European Evitas
guys kindly don't quote whole post(s), thanks
Only AT&T Phones are different in the case of unlocking/rooting because they can't use HTCDEV. Every other onexl is the same for unlocking/rooting.
Great guide, thanks you! it worked !
Now i'm stuck at the next step. ha :crying:
i cant get root, because my touchscreen not functional after flashed a custom rom. i had success until step 3, i cant proceed to step 4 as i cant use my touches when the rom loaded. i didnt have any back up. i already searched around to dgrade my touchscreen firmware, but it needs root. im stuck here, i can flash custom cwm recovery, install custom rom but cant touch screen. the default cm10.1 dont have android debugging enabled by default, i cant enable it cos i cant touch the screen. if i restore to stock ruu, i can touch screen n all works, but i had a problem sync google contacts.
The reason im getting my hands on custom rom is bcos my stock XL(Asian version) will neve sync google contacts properly, i tried to flash JB stock RUU, but its same. then, i started to tamper my fon with unlocking bootloader via htcdev, flash cwm(twrp mess on my sdcard storage). i had experience on older htc devices but its my 1st time on the htc one series. right now, im on evita s-on, unlocked bootloader, hboot 2.14, cwm recovery(twrp mess on my sdcard storage), not-super CID. I 'm left with a non-touchable cm10.1, i can flash any rom that supports s-on. tried to relock bootloader but i cant flash stock ICS ruu.flashing stock JB RUU is ok. my target now is to s-off n superCID.
i can :
flash RUU 3.17, running a stock RUU 3.17.
unlock bootloader
flash custom recovery(twrp mess with my internal storage)
i cant :
root my device on stock rom
touchscreen wont work on custom rom
any help will b greatly appreciated.
Do not make multiple posts about the same thing. It is strictly against XDA rules.
sorry, may i know how to delete it? i click on edit/delete but cant see any options to delete my post.
You cannot
Sent from my One X using xda app-developers app
sir how to back or normal cid help me
sir how to back or normal cid help me i have a one x its allredy super cid how get back normal cid
Fastboot oem writecid whateveryourcidwas
This will only work once with s-on after supercid but will work as many times as you want if s-off.
Sent from my One X using xda app-developers app
ignore this post. found a relevant thread
How to upgrade bootloader to 2.14
So what if you are not on HBoot 2.14?
EDIT:
Warning: It is not a good idea to upgrade only the bootloader if you intend to flash the latest CM10 builds! Avoiding RUU and unlocking again out of laziness will probably get you in trouble afterwards. RUU is definitely the safer way. You'll find a good collection of ROMs here
http://forum.xda-developers.com/showthread.php?t=2119610
and the tutorial for upgrading RUU on a previously modded phone here
http://forum.xda-developers.com/showthread.php?p=26260005
I found these threads which helped me SuperCID, S-Off and finally upgrade the HBoot of my already rooted evita.
First you need the superCID from this post:
http://forum.xda-developers.com/showthread.php?p=42351491
Next Step S-Off:
http://forum.xda-developers.com/showthread.php?t=2155069
Then RegawMOD the appropriate bootloader from this thread and flash:
http://forum.xda-developers.com/showthread.php?t=1786498
The procedure was easy once I had found the appropriate threads on XDA
You should not update hboot that way. It only updates one file and not all the firmware files. Ruu or flashing firmware.zip are the best ways.
Sent from my HTC One XL using xda app-developers app
New CM10 and derivates require HBoot 2.14
exad said:
You should not update hboot that way. It only updates one file and not all the firmware files. Ruu or flashing firmware.zip are the best ways.
Click to expand...
Click to collapse
I simply needed an updated bootloader in order to enable flashing the latest CM10 nightlies. This did the job.
ernstlustig said:
exad said:
You should not update hboot that way. It only updates one file and not all the firmware files. Ruu or flashing firmware.zip are the best ways.
I simply needed an updated bootloader in order to enable flashing the latest CM10 nightlies. This did the job.
Click to expand...
Click to collapse
That's exactly why you should not do it that way. You may get issues along the way as a result of the software not properly utilizing your hardware. This is why you're supposed to update hboot. What you did is more like tricking it into thinking you updated the firmware.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
ernstlustig said:
I simply needed an updated bootloader in order to enable flashing the latest CM10 nightlies. This did the job.
Click to expand...
Click to collapse
As exad said, CM 10 didnt want you to update just the hboot it wanted you to flash 3.18 RUU or equal to get updated firmware.
The requirement to install 3.18 RUU is listed as a requirement for CM. The hboot is what is checked but things like radio, adsp and wcnss are what actually needed to be updated, which you have not updated.
All you have successfully done is beaten the basic check for if you flashed the 3.18 RUU without actually doing what you were told to do.
How did you get s-off? i have a rogers version
salt204 said:
How did you get s-off? i have a rogers version
Click to expand...
Click to collapse
Links to XDA threads updated. (Sorry.) Please look again.
Has anyone tried successfully to write SuperCID into hboot 2.15 S-On devices?
as the instructions is for hboot 2.14, and I would like to S-Off the device with hboot 2.15 and it is S-On.
I have tried the hex with adb method, but it doesn't work.
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:
Hi everyone,
This is my very first post and I'll admit I am a NOOB.
As I've searched XDA and Google for my questions, I am really at a loss and thought I would pose my question(s) to the community.
I have a Rogers HTC One X(Evita) running CM 10.0, I am currently S-ON, with TWERP 2.3.1
I would like to install the latest CM but it would seem my HBOOT (1.11) needs to be upgraded.
My first question is if my CID is Roger001 is this similar to being SuperCID?
If so, which firmware is recommended? Which is the latest HBOOT I should upgrade to?
I guess this brings me to my next question, what exactly do I need to be able to upgrade my HBOOT?
I've seen a few walkthroughs but none mention Roger001 as CID and I'd rather not risk bricking my phone.
If you need any other information, please let me know.
Any assistance is greatly appreciated.
You definitely need to update your phone in order to flash the latest cm ROM. But, with your phone in its current state you'll brick it. You don't have SuperCID (11111111), you'll definitely need to get that first, then get s-off, then you can RUU up to the latest. Links to everything you need are in this thread.
Sent from my Evita
Thanks Tim.
I'll give that a whirl and let you know how it turns out.
Another silly question, what exactly is RUU?
Sent from my One X using xda app-developers app
RUU stands for ROM Update Utility. It basically takes your phone back to being completely stock, including recovery. The beauty of being s-off when you run an RUU is the s-off status survives the process, and so will your unlocked bootloader. So all you need to do when it's finished is flash TWRP again via fastboot, then flash your ROM via TWRP.
Sent from my Evita
Ahh
That makes perfect sense!
If I wanted to stay stock, I could?
Sent from my One X using xda app-developers app
Yeah there's nothing stopping you. Then if you change your mind it's as simple as following the steps I mentioned before.
Sent from my Evita
I haven't had a chance to try anything as of yet but I've been doing some reading, could I use the One X Att all-in-one kit 3.0.1 to obtain SuperCID as well S-Off?
I tried another apparently popular program yesterday but it didn't work, as my CID is still Roger001.
Thanks!
Sent from my One X using xda app-developers app
Yeah you might as well try anything you can to get it done.
Sent from my Evita
Yes!
timmaaa said:
Yeah you might as well try anything you can to get it done.
Sent from my Evita
Click to expand...
Click to collapse
Hey timmaa,
Just wanted to say thanks for the help!
I managed to get CID 11111111, as well as S-OFF.
I've just relocked and I am currently downloading the Rogers stock RUU, with that comes HBoot 2.14 and the latest CM!
Thanks again:good::laugh:
Spoke too soon.. :S
asarrecchia said:
Hey timmaa,
Just wanted to say thanks for the help!
I managed to get CID 11111111, as well as S-OFF.
I've just relocked and I am currently downloading the Rogers stock RUU, with that comes HBoot 2.14 and the latest CM!
Thanks again:good::laugh:
Click to expand...
Click to collapse
So, I flashed that latest Rogers RUU using ARUWizard, everything looked to be okay, as now I am now on H-Boot 2.14.
However, I cant boot into anything..
For some reason, when it tries to boot up it shows the CyanogenMod logo when loading but nothing.
Windows recognizes my phone and tries to install new drivers but fails.
I can boot into the bootloader but when I hit recover, the screen goes black and then after awhile a red ! with a phone beneath it shows up.
Any ideas anyone?
asarrecchia said:
So, I flashed that latest Rogers RUU using ARUWizard, everything looked to be okay, as now I am now on H-Boot 2.14.
However, I cant boot into anything..
For some reason, when it tries to boot up it shows the CyanogenMod logo when loading but nothing.
Windows recognizes my phone and tries to install new drivers but fails.
I can boot into the bootloader but when I hit recover, the screen goes black and then after awhile a red ! with a phone beneath it shows up.
Any ideas anyone?
Click to expand...
Click to collapse
Ok, firstly you didn't need to relock your bootloader to run the RUU because you have s-off. And what exactly is aruwizard? And how did you flash CM after you ran the RUU?
Sent from my Evita
timmaaa said:
Ok, firstly you didn't need to relock your bootloader to run the RUU because you have s-off. And what exactly is aruwizard? And how did you flash CM after you ran the RUU?
Sent from my Evita
Click to expand...
Click to collapse
I followed the steps from the link you gave me, under the RUU section, as there was a guide on how to install an RUU for Rogers HTC One X.
It said to relock the phone, so, I did.
ARWizard was part of the guide.
The weird thing is, I didn't flash CM, I flashed the Rogers RUU, so, I'm not even sure how CM10 is even on my phone.
I can get to the Bootloader but I can't launch TWERP and my windows PC now doesn't recognize my phone, it says installing drivers but never does. I had HTC Sync installed in hopes that it would help, it didn't.
Is my only option to do a Factory Reset in Hboot? I've read ill lose all my info on the SD card.
Thanks
Which RUU did you run? Something has gone wrong.
Sent from my Evita
timmaaa said:
Which RUU did you run? Something has gone wrong.
Sent from my Evita
Click to expand...
Click to collapse
I followed the steps in the below thread to help me flash the RUU
http://forum.xda-developers.com/showthread.php?t=1658929&nocache=1
I went to this site to get the Stock image:
http://forum.xda-developers.com/showthread.php?p=37227608
It's 3.17.631.2
OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23a.3 2.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl 6j.zip
I really do appreciate the help, by the way.
I'm not familiar with that method, but it seems to me that it doesn't do a full RUU. And evidently it hasn't because you still have cm on your phone. What hboot version does your phone list in bootloader now? You could just run the at&t 3.18 RUU which will do the whole job. You're s-off so it should be fine.
Sent from my Evita
timmaaa said:
I'm not familiar with that method, but it seems to me that it doesn't do a full RUU. And evidently it hasn't because you still have cm on your phone. What hboot version does your phone list in bootloader now? You could just run the at&t 3.18 RUU which will do the whole job. You're s-off so it should be fine.
Sent from my Evita
Click to expand...
Click to collapse
I am 2.14 HBOOT and S-off.
The problem is that while my Windows PC recognizes my phone, it doesnt load the drivers and therefore, I cant send any ADB commands.
I am not even able to go into TWERP.
How will I be able to run the AT&T if I cant push any ADB commands from my PC?
You don't need any adb commands to run an RUU, but you do need the pc to recognize the phone. I'd try uninstalling all drivers, then installing them again to see if it helps.
Sent from my Evita
Ota is not the same as aruwizard zip. Aru zip is exactly the same as Rom.zip you find inside ruu files, evita ones get the name pj83img.
Not sure why everyone thinks ota is ruu, nowhere is it refered to as being the same thing.
Maybe the firmware.zip in the ota managed to flash though hence your hboot and other firmware was upgraded.
If you follow the "or" method for flashing the zip it actually should work. The better correct answer is once s-off to download/install the latest ruu available that you want and ota up from there.
twistedddx said:
Ota is not the same as aruwizard zip. Aru zip is exactly the same as Rom.zip you find inside ruu files.
Not sure why everyone thinks ota is ruu, nowhere is it refered to as being the same thing.
Maybe the firmware.zip in the ota managed to flash though hence your hboot and other firmware was upgraded.
Click to expand...
Click to collapse
That's what I thought, but if he has used this aru zip, it's had the opposite effect. He now has the upgraded hboot but the previous ROM is still intact.
Sent from my Evita
timmaaa said:
That's what I thought, but if he has used this aru zip, it's had the opposite effect. He now has the upgraded hboot but the previous ROM is still intact.
Sent from my Evita
Click to expand...
Click to collapse
Thanks guys.
I'll try uninstalling the phone drivers and reinstall them, hopefully, it'll allow my PC to see my phone.
Worse case scenario, if my computer doesn't load the drivers for my phone, what are my options?
What if I select factory reset from HBOOT?
I have S4 Ville on firmware 3.14.531.17 and need to know if S-OFF is possible using whatever method available. Moonshine thread states that only 3.14.531.11 (T-MOB) is supported and haven't found any details in the Facepalm thread.
Anyone know for sure?
Bump
Sent from my One S using XDA Premium 4 mobile app
My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.
tivofool said:
My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.
Click to expand...
Click to collapse
Well gave this a shot and after 5 hours I am back on CM10.2 with S-ON and latest firmware still.
Thanks for the help though. Cheers.
Anyone else got any idea?
bump
Look for 3.14.531.11. It should be available somewhere. Lock the phone back and RUU it. Then you can unlock again and S-OFF with moonshine.
evrycard said:
Look for 3.14.531.11. It should be available somewhere. Lock the phone back and RUU it. Then you can unlock again and S-OFF with moonshine.
Click to expand...
Click to collapse
He probably cannot downgrade from *.17 to *.11.
I don't know what parts of the firmware moonshine needs. But you could try downgrade using a OTA or Nandroid.
Same here
I'm pretty much stuck with a One-S Bootloader unlocked with S-on.
I can't find a way to get S-Off. Just googling and throwing prayers in the sky someone develops a way.
pyrocide said:
Well gave this a shot and after 5 hours I am back on CM10.2 with S-ON and latest firmware still.
Thanks for the help though. Cheers.
Anyone else got any idea?
Click to expand...
Click to collapse
If that procedure took you 5 hours... Maybe s-off isn't for you.
Sent from my HTC One S using xda app-developers app
havikx said:
If that procedure took you 5 hours... Maybe s-off isn't for you.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
It took me 5 hours total to begin finding all req's and trying the above method, finding it not to work, redoing the RUU *.17 and getting BACK on CM10.2 and having a phone to make calls with. The method above took maybe 20-30 minutes of double checking and making sure i didn't miss something.
Maybe PM this guy. He posted that it moonshine worked on .17.
http://forum.xda-developers.com/showpost.php?p=45955250&postcount=1091
Ask if he ran moonshine on Linux.
tivofool said:
Maybe PM this guy. He posted that it moonshine worked on .17.
http://forum.xda-developers.com/showpost.php?p=45955250&postcount=1091
Ask if he ran moonshine on Linux.
Click to expand...
Click to collapse
PM'd him for more info. Thanks!
So I was having problems getting s-off as well, eventually I got it done, but it was definitely a big trial and error process.
What I ended up doing was:
1) Get the 3.14.531.11 RUU from http://www.androidruu.com/index.php?developer=Ville (make sure you get the TMOUS one) This link is also provided in the first post in the Android development section
2) I ended up using Moonshine S-Off (http://forum.xda-developers.com/showthread.php?t=2325590) but I needed to use it in conjunction with running it on Ubuntu. Luckily I had a spare hard drive lying around. If you don't, I believe you can run it through the CD as well as long your burn the Ubuntu.iso on a disc. Plug in your phone to the computer and let it do its magic
3) From there, if you wanted to, you can change to SuperCID. Since you have s-off by then, you can change it from the fastboot usb in the bootloader with the line fastboot oem writecid 11111111 (double check, i'm just writing off the top of my head)
4) Then install roms and etc through the usual custom recovery
Note. I tried the Maximus HD, yes it was nice, but it didn't allow me to utilize my phone as a hotspot, so I ended up using the Dark Jelly rom instead. So far it's been very nice. The hotspot works, but the tethering portion is still unavailable. Just my two cents.
I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise
tivofool said:
My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.
Click to expand...
Click to collapse
i can say that this worked for me as well. i didn't relock bootloader before installing the 3.14.531.11 ruu though. still worked for me. also installed moonshine on windows. ( guess i'm lucky )
bnd10706 said:
I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise
Click to expand...
Click to collapse
You saved me so much time. Thanks!
bnd10706 said:
I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise
Click to expand...
Click to collapse
I do not understand meet all the requirement and I run it step by step and still gets stuck in step 3 moonshine I need urgent help, thanks
pyrocide said:
I have S4 Ville on firmware 3.14.531.17 and need to know if S-OFF is possible using whatever method available. Moonshine thread states that only 3.14.531.11 (T-MOB) is supported and haven't found any details in the Facepalm thread.
Anyone know for sure?
Click to expand...
Click to collapse
Test... click here
http://forum.xda-developers.com/showthread.php?t=2569755
[Q]Hboot/Firmware update 2.15 to 2.16 et al.
Sorry wrong thread.
I hope I'm in the right place. I can't connect at all to the PC since I flashed the AOKP_jb_mr1_build4 ROM. The PC says can't find device driver.
Also, I would love to update to newer builds, requiring a newer hboot version I gather, but not quite sure as to how to go about that, and deal with s-on. I only want to do what has to be done to get the latest AOKP ROM builds. Any advice would be greatly appreciated...
I am using HTC one x, Evita, rooted, (not sure about supercid, I think so), s-on, hboot 1.14, and trwp 2.6+.
Even though I've had my phone a year, I'm still quite the noob when it comes to all this. Heavy forum reading...re-reading. I'm looking for any definitive help on getting me set up on the last steps here.
Sent from my One X using xda app-developers app
Newer builds do require an upgrade but it's not just the hboot that needs upgrading, it's the firmware as a whole which needs upgrading. The firmware does contain the hboot as a component and it is also usually identified by the hboot version number that it contains, I guess that's why there's a common misconception that it's just the hboot you need to upgrade.
Anyway, what you need to do is run the 3.18 RUU which will give you the 2.14 firmware modules. In order to run the RUU you'll first need s-off otherwise you'll end up with a brick. In order to get s-off you need to be sure you have SuperCID, without SuperCID the s-off process won't work. I know this all seems like a lot of work but it's a pretty easy process. Not having s-off at this stage is a stupid hindrance, without it you basically cannot flash any current ROM because they all require some kind of update (which itself requires s-off).
PS. You're not quite in the right place, in future please post questions in the Q&A section. I'll ask for this thread to be moved there.
Sent from my Evita
timmaaa said:
PS. You're not quite in the right place, in future please post questions in the Q&A section. I'll ask for this thread to be moved there.
Sent from my Evita
Click to expand...
Click to collapse
Done and title changed:good:
Thanks. Trying to find noob-proof instructions to accomplish all you mentioned. But I do appreciate being pointed in the right direction. Its good to know definitively what I need to do, now just gotta get down the how lol...
Sent from my One X using xda app-developers app
Ok, I'll make it a bit easier on you. The easiest way for you to get it done will be to follow these steps:
Flash a Sense 4 Android 4.1 ROM with root. It cannot be Sense 5 Android 4.2 though. You'll find plenty in our development section.
Determine whether you have SuperCID or not. Boot into bootloader and connect to your PC then issue this fastboot command:
Code:
fastboot oem readcid
If it shows up as 11111111 or 22222222 you have SuperCID and can continue to the s-off step. If it shows up as anything else you don't have SuperCID, in that case you van use this method to obtain SuperCID:
http://forum.xda-developers.com/showthread.php?t=2212737
Once you have SuperCID you can get s-off by following this guide:
http://forum.xda-developers.com/showthread.php?t=2155071
So now you should have s-off, which means you can run the 3.18 RUU. You'll find it here:
http://dl3.htc.com/application/RUU_..._10.130.32.34_release_signed_With_Partial.exe
All you need to do is connect your phone to your PC, run the RUU exe program and follow a few prompts. Make sure no other programs are running and make sure screen saver/hibernation is turned off. Also make sure HTC Sync is uninstalled (leave divers installed) because it gets in the way.
When the RUU is complete you will have a stock ROM and stock recovery on your phone (your bootloader will remain unlocked and you'll still have s-off though) so you'll need to flash TWRP recovery again. Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can flash any aosp ROM you want.
Sent from my Evita
Thanks...
Thanks for all the help. I was SuperCID, I achieved S-Off, i think. It says s-off on bootloader, but when I was entering the final 3 commands, the second one said error, I resubmitted it, and it went thru. Now it says S-Off. So is everything cool there?
I am a little concerned as to how terrible sounding running the RUU 3.18 can be. Am I cool to go now with no problems forseen?
Thanks for your responses btw. Very Helpful
Also, do I connect to PC in bootloader, or up and running rom, while running RUU?
If you are s-off running the ruu is entirely safe
Sent from my VENOMized HoxL
Everything went smooth today. I am running s-off, and hboot 2.14. Instructions worked perfectly. Thanks to everyone that helped me.
Sent from my One X using xda app-developers app
:thumbup:
Sent from my Evita