Database Info

[Q] Need help with RUU 3.18

Hello,
I am new to oneXL forum and by the looks of all the thread it seems that having S-off and upgrading to latest Ruu 3.14 is needed for most of the custom ROM to flash, i have an unlocked boot-loader and rooted. I am currently with below configuration on my XL,
Evita pvt ship s-on rl
Hboot-1.09.0000
Radio-0.17a.32.09.24_2
openDSP-v25.1.0.32.0405
emmc-boot
I just wanted to know what are my limitations and what better it will do with S-Off and upgrade to RUU.
Thank you

may2118 said:
Hello,
I am new to oneXL forum and by the looks of all the thread it seems that having S-off and upgrading to latest Ruu 3.14 is needed for most of the custom ROM to flash, i have an unlocked boot-loader and rooted. I am currently with below configuration on my XL,
Evita pvt ship s-on rl
Hboot-1.09.0000
Radio-0.17a.32.09.24_2
openDSP-v25.1.0.32.0405
emmc-boot
I just wanted to know what are my limitations and what better it will do with S-Off and upgrade to RUU.
Thank you
Click to expand...
Click to collapse
I also need assistance. I don't have a windows pc, so I find it a bit difficult to run a .exe file lol. Is there any way to flash the ruu in recovery, or do the update with a linux pc? Basically, any way to bypass the while so does requirement...

darthvince said:
I also need assistance. I don't have a windows pc, so I find it a bit difficult to run a .exe file lol. Is there any way to flash the ruu in recovery, or do the update with a linux pc? Basically, any way to bypass the while so does requirement...
Click to expand...
Click to collapse
Search for how to run a vm through Linux via Virtual Box, there are several how-to that have been written on these very forums....

Crappyvate said:
Search for how to run a vm through Linux via Virtual Box, there are several how-to that have been written on these very forums....
Click to expand...
Click to collapse
Hi,
Can you tell me if i need to upgrade Hboot for supercid?, and can i s-off without supercid?

How about you do some searching, and some reading. The answers to your questions lie within these forums. Who knows, you might actually learn something. Basic XDA rules: search before posting.
Sent from my Evita

may2118 said:
Hi,
Can you tell me if i need to upgrade Hboot for supercid?, and can i s-off without supercid?
Click to expand...
Click to collapse
hboot has very little to do with most things. It does not need updating and downgrading for pretty much anything. Newer hboot does protect some partitions like radio and boot, but that really does not get in the way and is entirely overcome once you s-off.
People need to forget about hboot and what version it is, it is unlikely to ever really get in your way these days.
For you second question, why not refer to the s-off thread where the first post tells you what to do?
http://forum.xda-developers.com/showthread.php?p=38174259
---------- Post added at 03:39 AM ---------- Previous post was at 03:32 AM ----------
darthvince said:
Is there any way to flash the ruu in recovery, or do the update with a linux pc?
Click to expand...
Click to collapse
There is a few ways for the phone to accept OTA updates, eg with a vanilla stock ROM or via recovery mode.
You can also just install the full firmware.zip taken from 3.17/3.18 from rebootruu.
They are all far more risky then just supercid, soff and installing a RUU.
Surely you can get access to a Windows machine.

twistedddx said:
hboot has very little to do with most things. It does not need updating and downgrading for pretty much anything. Newer hboot does protect some partitions like radio and boot, but that really does not get in the way and is entirely overcome once you s-off.
People need to forget about hboot and what version it is, it is unlikely to ever really get in your way these days.
For you second question, why not refer to the s-off thread where the first post tells you what to do?
http://forum.xda-developers.com/showthread.php?p=38174259
---------- Post added at 03:39 AM ---------- Previous post was at 03:32 AM ----------
There is a few ways for the phone to accept OTA updates, eg with a vanilla stock ROM or via recovery mode.
You can also just install the full firmware.zip taken from 3.17/3.18 from rebootruu.
They are all far more risky then just supercid, soff and installing a RUU.
Surely you can get access to a Windows machine.
Click to expand...
Click to collapse
Thank you very much...i will start with Supercid and S-off....thanks again

timmaaa said:
How about you do some searching, and some reading. The answers to your questions lie within these forums. Who knows, you might actually learn something. Basic XDA rules: search before posting.
Sent from my Evita
Click to expand...
Click to collapse
I know, what you said is right and i have been reading...but it seems more i read..the more i get confused. I wanted to try one of the methods to do Supercid and S-off but before i proceed i wanted to reassure my self before. Thanks anyways!!!

[Q] Can't update firmware, Unlocked/Tampered S-ON

I want to be able to flash the latest CM10.1 for my AT&T HTC One X. Details about the phone-
Unlocked with HTCDev. Hboot 1.14.0002. Have latest TWRP flashed. Says TAMPERED, UNLOCKED, and S-ON.
I tried a RUU to update the Hboot, but that didn't work.
How can I update the firmware so I can run latest ROMs like CM10.1? I've looked at similar questions, but the answers were for the International Version of the HTC One X.
Any help or suggestions are appreciated.

seth50k said:
I want to be able to flash the latest CM10.1 for my AT&T HTC One X. Details about the phone-
Unlocked with HTCDev. Hboot 1.14.0002. Have latest TWRP flashed. Says TAMPERED, UNLOCKED, and S-ON.
I tried a RUU to update the Hboot, but that didn't work.
How can I update the firmware so I can run latest ROMs like CM10.1? I've looked at similar questions, but the answers were for the International Version of the HTC One X.
Any help or suggestions are appreciated.
Click to expand...
Click to collapse
S-off
Run 3.18 ruu (no need to relock with s-off)
Relash recovery
Flash cm10
Sent from my HTC One XL using xda premium

31ken31 said:
S-off
Run 3.18 ruu (no need to relock with s-off)
Relash recovery
Flash cm10
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Ok, so here's the 2nd question. Somehow I managed to wipe whatever ROM I had on here (CleanROM I think), so it doesn't boot to anything. I've tried flashing CleanROM 6 and 3.20.401.1 Odexed, both error out in TWRP.
I'm assuming I've managed to softbrick it?

seth50k said:
Ok, so here's the 2nd question. Somehow I managed to wipe whatever ROM I had on here (CleanROM I think), so it doesn't boot to anything. I've tried flashing CleanROM 6 and 3.20.401.1 Odexed, both error out in TWRP.
I'm assuming I've managed to softbrick it?
Click to expand...
Click to collapse
Not sure 3.20.401.1 is but what did you do? You didn't do factory reset from bootloader did you?

RollTribe said:
Not sure 3.20.401.1 is but what did you do? You didn't do factory reset from bootloader did you?
Click to expand...
Click to collapse
I might have. What I was trying to do is clean out the phone to sell it, then get it updated, etc. I know in TWRP I ran probably every type of wipe, and I may have run Factory reset from the bootloader. It was a while ago and I set it aside, and now i've come back to it trying to get this phone sorted out.

seth50k said:
I might have. What I was trying to do is clean out the phone to sell it, then get it updated, etc. I know in TWRP I ran probably every type of wipe, and I may have run Factory reset from the bootloader. It was a while ago and I set it aside, and now i've come back to it trying to get this phone sorted out.
Click to expand...
Click to collapse
If you did, then you're not gonna be able to so anything with ROMs. Run an ruu, reunlock, and report back.

RollTribe said:
If you did, then you're not gonna be able to so anything with ROMs. Run an ruu, reunlock, and report back.
Click to expand...
Click to collapse
I've tried running RUU, it gets about halfway and fails. Do I need to flash the stock recovery and relock first, then run a RUU?

U need to relock the bootloader
Use command prompt
"Fastboot oem lock" from fastboot then run the ruu.... I recommend getting s-off as well is very easy and fast and it will save u a lot of troubles in the future plus u will not have to lock the bootloader to flash an ruu
Sent from my HTC One X using xda premium

If you ruu with s-on and supercid you brick.
Be careful with your advice breeze. You'll cause him a brick.
Sent from my One X using xda app-developers app

breezedragon said:
U need to relock the bootloader
Use command prompt
"Fastboot oem lock" from fastboot then run the ruu.... I recommend getting s-off as well is very easy and fast and it will save u a lot of troubles in the future plus u will not have to lock the bootloader to flash an ruu
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yeah, but you need a ROM working to even do the s-off process. So getting a ROM loaded is my main priority at this point. I can get into Bootloader/Fastboot, and I can still get to TWRP. Flashing a ROM from TWRP isn't working, and neither is running the latest RUU from fastboot. I get ERROR 159 when I try to run the latest RUU. So do I need to fastboot oemlock, then try again?
Perhaps running the RUU that was previously on it would work? 2.20, is what firmware was on it last.

seth50k said:
Yeah, but you need a ROM working to even do the s-off process. So getting a ROM loaded is my main priority at this point. I can get into Bootloader/Fastboot, and I can still get to TWRP. Flashing a ROM from TWRP isn't working, and neither is running the latest RUU from fastboot. I get ERROR 159 when I try to run the latest RUU. So do I need to fastboot oemlock, then try again?
Perhaps running the RUU that was previously on it would work? 2.20, is what firmware was on it last.
Click to expand...
Click to collapse
Yeah, you have to run the same/later ruu if you're not S-Off. And you'll have to relock and you can flash stock recovery to be safe (but I think it flashes for you).
---------- Post added at 02:12 PM ---------- Previous post was at 02:11 PM ----------
exad said:
If you ruu with s-on and supercid you brick.
Be careful with your advice breeze. You'll cause him a brick.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
That's not necessarily true, I've ruu'ed with s-on and SuperCID and was fine. It is risky, though.

Unlock, flash a sense rooted rom, soff and then ruu up to 3.18
Sent from my One X using xda app-developers app

RollTribe said:
Yeah, you have to run the same/later ruu if you're not S-Off. And you'll have to relock and you can flash stock recovery to be safe (but I think it flashes for you).
---------- Post added at 02:12 PM ---------- Previous post was at 02:11 PM ----------
That's not necessarily true, I've ruu'ed with s-on and SuperCID and was fine. It is risky, though.
Click to expand...
Click to collapse
I'm able to run the 2.20 RUU so far after relocking, it's about 3/4 of the way done. After this i'll try the latest RUU, then go from there to re-unlock, then S-OFF, THEN reflash TWRP?

seth50k said:
I'm able to run the 2.20 RUU so far after relocking, it's about 3/4 of the way done. After this i'll try the latest RUU, then go from there to re-unlock, then S-OFF, THEN reflash TWRP?
Click to expand...
Click to collapse
Yup, you can swap the last two if you want

RollTribe said:
Yup, you can swap the last two if you want
Click to expand...
Click to collapse
Well shoot...got so close. 2.20 RUU worked, then I did the latest RUU, which completed fine, but now the phone won't turn on, and won't even show a red LED charging indicator. WTF...

seth50k said:
Well shoot...got so close. 2.20 RUU worked, then I did the latest RUU, which completed fine, but now the phone won't turn on, and won't even show a red LED charging indicator. WTF...
Click to expand...
Click to collapse
Yep, looks like it's bricked. http://forum.xda-developers.com/showthread.php?t=2181929

seth50k said:
Well shoot...got so close. 2.20 RUU worked, then I did the latest RUU, which completed fine, but now the phone won't turn on, and won't even show a red LED charging indicator. WTF...
Click to expand...
Click to collapse
Yeah, you have to s-off before running latest ruu. Damn sorry if I was unclear man.

RollTribe said:
Yeah, you have to s-off before running latest ruu. Damn sorry if I was unclear man.
Click to expand...
Click to collapse
It's alright, just a little surprised given the fact that HTC allows you to unlock and such, but their own RUU bricks the phone if in such a state.
I think it might be under warranty still, might try that route. Thanks for the help.

Sorry about your phone. It's Jtagg or new phone.
---------- Post added at 02:34 PM ---------- Previous post was at 02:34 PM ----------
seth50k said:
It's alright, just a little surprised given the fact that HTC allows you to unlock and such, but their own RUU bricks the phone if in such a state.
I think it might be under warranty still, might try that route. Thanks for the help.
Click to expand...
Click to collapse
They state on their site that after unlocking the bootloader, RUU/OTA could brick you.
If you plan to try warranty with HTC, do not mention that you unlocked. They will charge you 200 straight up no matter what you say.

RollTribe said:
That's not necessarily true, I've ruu'ed with s-on and SuperCID and was fine. It is risky, though.
Click to expand...
Click to collapse
But was it the 3.18? It applies specifically for the AT&T 3.18 (and for some 3.17 JB RUUs on other carriers, and reported by some folks on this forum).
If you were able to run the 3.18 RUU successfully with SuperCID and S-on, I believe this is the first I've heard of it.
---------- Post added at 12:37 PM ---------- Previous post was at 12:33 PM ----------
seth50k said:
It's alright, just a little surprised given the fact that HTC allows you to unlock and such, but their own RUU bricks the phone if in such a state.
Click to expand...
Click to collapse
SuperCID as implemented on the AT&T One X is a mod/hack, and therefore not explicitly "allowed" by HTC. They can't really be held responsible for the effects of it.
SuperCID shouldn't be "expected" to brick under these conditions (worked fine with pre-JB RUUs), and nobody here has really been able to explain exactly why the phone bricks from SuperCID. But unfortunately, it does.

[Q]~[HELP] SuperCID, Unlocked, Rooted, and S-OFF, how to restore to stock AT&T ROM?

[Q]~[HELP] SuperCID, Unlocked, Rooted, and S-OFF, how to restore to stock AT&T ROM?
Hi, geeks,
For my AT&T HTC One X, I have followed you guys all the way to here now: with SuperCID, Bootloader Unlocked (via HTC Dev), Rooted of course, and S-OFF (with touchscreen firmware down-graded).
Now I want to go back to AT&T stock ROM to use the ISIS wallet. Could you please tell me how? I am worried that my phone get bricked!
Thank you so much!

You can just flash a stock at&t ROM which you'll find in our Android Development section. Or you can run the 3.18 RUU. This will also flash stock recovery, hboot, radio, and other firmware modules. The ROM is probably the better and easier option.
Sent from my Evita

Thank you, timmaaa. Do I need to lock the bootloader and so on? I saw it somewhere but can't find the link now.
timmaaa said:
You can just flash a stock at&t ROM which you'll find in our Android Development section. Or you can run the 3.18 RUU. This will also flash stock recovery, hboot, radio, and other firmware modules. The ROM is probably the better and easier option.
Sent from my Evita
Click to expand...
Click to collapse

To run the RUU? No, because you're s-off you don't need to do any of that, just run the RUU through Windows.
Sent from my Evita

timmaaa said:
To run the RUU? No, because you're s-off you don't need to do any of that, just run the RUU through Windows.
Sent from my Evita
Click to expand...
Click to collapse
I'm doing the same thing, but to attempt to trade in my phone. I assume that after running the RUU I should relock the bootloader. I want to get rid of the red text.
*EDIT* nevermind. didn't realize that the RUU clears out the *TAMPERED* flag and gets rid of the red text. should be all good now.

One more question, timmaaa: after flashing RUU, the recovery partition will be replaced with the stock recovery, and the S-OFF and boot loader will be kept as it is (based on what I learned from other posts of you). What if I need to flash CM again? I am confused because not many people are doing what I am. Thanks!
timmaaa said:
To run the RUU? No, because you're s-off you don't need to do any of that, just run the RUU through Windows.
Sent from my Evita
Click to expand...
Click to collapse

Yes, the RUU will install the stock recovery. Your phone will still be s-off and will still have an unlocked bootloader. All you need to do is install TWRP recovery again and then you can flash any ROM you like. Full instructions on how to install a recovery can be found in my How-To Guide For Beginners thread, link in my signature.
Sent from my Evita

Hi, timmaaa, I got a RUU error 155 when flashing RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial.exe.
Seems I need to re-lock the bootloader, which I am reluctant to do. Do I miss anything?
timmaaa said:
Yes, the RUU will install the stock recovery. Your phone will still be s-off and will still have an unlocked bootloader. All you need to do is install TWRP recovery again and then you can flash any ROM you like. Full instructions on how to install a recovery can be found in my How-To Guide For Beginners thread, link in my signature.
Sent from my Evita
Click to expand...
Click to collapse

You don't need to relock if you're s-off. Are you using a 2.0 or 3.0 usb port? Are you using a HTC cable? Are you in fastboot mode? Have you uninstalled HTC Sync Manager?
Sent from my Evita

Hi, timmaaa, I am using USB2.0 on windows XP, with a regular cable, not in fastboot mode, and haven't uninstalled HTC Sync Manager.
I will try flash in fastboot mode again.
timmaaa said:
You don't need to relock if you're s-off. Are you using a 2.0 or 3.0 usb port? Are you using a HTC cable? Are you in fastboot mode? Have you uninstalled HTC Sync Manager?
Sent from my Evita
Click to expand...
Click to collapse

aaronDroid80 said:
I'm doing the same thing, but to attempt to trade in my phone. I assume that after running the RUU I should relock the bootloader. I want to get rid of the red text.
*EDIT* nevermind. didn't realize that the RUU clears out the *TAMPERED* flag and gets rid of the red text. should be all good now.
Click to expand...
Click to collapse
You need to make sure the person you are trading with understands the phone is s-off and bootloader unlocked, and what that means.
---------- Post added at 01:57 PM ---------- Previous post was at 01:54 PM ----------
BBS678 said:
One more question, timmaaa: after flashing RUU, the recovery partition will be replaced with the stock recovery, and the S-OFF and boot loader will be kept as it is (based on what I learned from other posts of you). What if I need to flash CM again? I am confused because not many people are doing what I am. Thanks!
Click to expand...
Click to collapse
If you think you might still want to flash custom ROMs, you need to ask yourself why you want to return to stock in the first place.
Going back to stock if you are s-off, custom recovery, etc. is a step backward, not forward. Aside from getting on the correct hboot, firmware, etc. (or selling/trading your phone like the guy above), there is no benefit to going through all the hassle to running the RUU to get back to stock. Just flash a stock rooted ROM as timmaaa originally mentioned.
EDIT: Missed the part in the OP where it mentioned ISIS. See my response below (#13).

An update (for the forum): In fastboot mode, I have flashed Stock RUU successfully, without locking boot loader. After this, even in stock ROM, ISIS still doesn't work. I think it's caused by the SuperCID and S-OFF.
Timmaaa, do you know how I can SAFELY get SuperCID and S-OFF fixed? Thank you!
BBS678 said:
Hi, timmaaa, I am using USB2.0 on windows XP, with a regular cable, not in fastboot mode, and haven't uninstalled HTC Sync Manager.
I will try flash in fastboot mode again.
Click to expand...
Click to collapse

BBS678 said:
An update (for the forum): In fastboot mode, I have flashed Stock RUU successfully, without locking boot loader. After this, even in stock ROM, ISIS still doesn't work. I think it's caused by the SuperCID and S-OFF.
Timmaaa, do you know how I can SAFELY get SuperCID and S-OFF fixed? Thank you!
Click to expand...
Click to collapse
Reading around, root seems to be the only mod that interferes with ISIS. Its unlikely that s-off would interfere with ISIS. SuperCID? Its possible. Changing from SuperCID is very easy with fastboot. Just search for the command.
Also, be aware that you need a ISIS compatible SIM ("secure element SIM") available from your carrier.
http://www.att.com/shop/apps/isis-mobile-wallet.html#fbid=xHuv6S8moS4

Could be. HTC One X is not available on att.com now, so your link can't explain at this moment.
From here, https://www.paywithisis.com/get-started.html, it says AT&T HTC One X is compatible.
In addition, I do have a ISIS compatible SIM card from AT&T. The reason I suspect it is due to CID is that it is “heard" from this forum that ISIS doesn't work if you put an AT&T SIM card in the T-mobile version of GN3 (unlocked).
redpoint73 said:
Reading around, root seems to be the only mod that interferes with ISIS. Its unlikely that s-off would interfere with ISIS. SuperCID? I suppose its possible, but my gut says no. Especially in light of the following:
I'm thinking it more the issue that the AT&T One X is not a "ISIS ready phone": http://www.att.com/shop/apps/isis-mobile-wallet.html#fbid=xHuv6S8moS4
Also, be aware that you need a ISIS compatible SIM ("secure element SIM") available from your carrier.
Click to expand...
Click to collapse

BBS678 said:
Could be. HTC One X is not available on att.com now, so your link can't explain at this moment.
From here, https://www.paywithisis.com/get-started.html, it says AT&T HTC One X is compatible.
Click to expand...
Click to collapse
Yes, I later realized that One X is not available at all anymore from AT&T (and that it is supposed to be ISIS ready), and revised my above response accordingly.
BBS678 said:
In addition, I do have a ISIS compatible SIM card from AT&T. The reason I suspect it is due to CID is that it is “heard" from this forum that ISIS doesn't work if you put an AT&T SIM card in the T-mobile version of GN3 (unlocked).
Click to expand...
Click to collapse
It could also be that they are looking at the phone model number. So SuperCID is a possibility, but not certain.
Its easy to change from SuperCID with a simple fastboot command. Just search this forum for the proper syntax.
---------- Post added at 02:43 PM ---------- Previous post was at 02:32 PM ----------
Here is the command to change from CID:
fastboot oem writecid CWS__001
(note that CWS__001 has two underscores)

Thank you! I learned from this forum that changing S-OFF to S-ON is very risky, and currently S-OFF relies on a SuperCID, so I think it's also risky to change the CID back. Have you ever tried? I need more opinions on this before I take the risk.

BBS678 said:
Thank you! I learned from this forum that changing S-OFF to S-ON is very risky, and currently S-OFF relies on a SuperCID, so I think it's also risky to change the CID back. Have you ever tried? I need more opinions on this before I take the risk.
Click to expand...
Click to collapse
I honestly doubt s-off is blocking ISIS. S-off is exclusively an HTC invention, and I doubt ISIS would care about such a thing. I would recommend to leave s-off alone.
I wouldn't say its "risky" to change CID. As long as you still have s-off, I don't see any reason to still have SuperCID. But even so, you can still use the correct exploit to change back to SuperCID.

Hi, timmaaa, could you please shed some lights on this (change back to stock CID) please? Thanks!

here is my other post about ISIS: http://forum.xda-developers.com/showthread.php?p=49822333
redpoint73 said:
I honestly doubt s-off is blocking ISIS. S-off is exclusively an HTC invention, and I doubt ISIS would care about such a thing. I would recommend to leave s-off alone.
I wouldn't say its "risky" to change CID. As long as you still have s-off, I don't see any reason to still have SuperCID. But even so, you can still use the correct exploit to change back to SuperCID.
Click to expand...
Click to collapse

Everything that @redpoint73 has said is correct. There's pretty much no risk involved in changing your CID back to stock, having s-off does not rely on SuperCID. You can try changing your CID using the command that redpoint gave before.
There's pretty much no risk involved with going from s-off to s-on either. I don't know where you read that but I believe you're misunderstanding the information. Personally I wouldn't go back to s-on though because I don't believe that is affecting your ability to run ISIS. Plus getting s-off again can be tricky sometimes.
Sent from my Evita

Cannot access Recovery

Hey guys,
My phone died from the dreaded "qhsusb_dload" issue, and since I cannot afford the replacement phone I really want, I bought another AT&T One X.
I had my previous one since March of last year and I have gotten everything done with no issues, including S-OFF, upgrading Firmware to 3.17 to use JB 4.2.2 and trying various Radios and Kernels, so I do have experience.
With this phone, completely stock, I unlocked the Bootloader, and at the top it shows TAMPERED and UNLOCKED. I now have two issues:
1. I cannot get into the Recovery. I flashed it manually from "Fastboot USB", as well as with EZ Toolkit Advanced (Evita) and WinDroidXL Tookit and it showed it was successful with each method, yet when I try to access it, I get the boot screen with the HTC logo for about 3 seconds then it just powers off completely.
I researched and tried TWRP 2.6 as well as CWM from WinDoidXL toolkit. I have also ran the "fastboot erase cache" command after installing the Recovery yet I still have the problem. I installed gapps to accomplish the same thing but I don't wanna use it just yet.
I am asking for help as I am afraid of bricking this phone as well. When it powers off after failing to access the Recovery, it stays off for a while, and Device Manager even shows "qhsusb_dload" I have to hold the power button for a long time (and multiple times in some instances) before it powers on and boots into the OS.
Please help me get this working as I am afraid to try it again with the fear of having it bricked.
I do not have root access (I need recovery to flash t he Super User zip file first, correct?) and my HBoot is 2.14 (can't remember what it was on my last phone). Do any of those play a part in the problem i'm having?
Thanks so much in advance

Does the phone boot up into the OS? What are your bootloader details?
Sent from my Evita

Hello again, timmaaa.
timmaaa said:
Does the phone boot up into the OS? What are your bootloader details?
Click to expand...
Click to collapse
badbwoydes said:
When it powers off after failing to access the Recovery, it stays off for a while, and Device Manager even shows "qhsusb_dload" I have to hold the power button for a long time (and multiple times in some instances) before it powers on and boots into the OS.
Click to expand...
Click to collapse
My phone works fine with stock ATT 4.1.1 that it came with, it's just the Recovery that won't launch, even though it appears to install fine when I flash it with fastboot.
My Bootloader shows:
TAMPERED
UNLOCKED
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012, 18:37:14-1
Thanks

Are you checking the md5 after downloading the recovery?
Sent from my Evita

timmaaa said:
Are you checking the md5 after downloading the recovery?
Sent from my Evita
Click to expand...
Click to collapse
No, but I have tried 2 different versions from here, the one I had on my previous Evita, and I have also used the ones embedded in the WinDroidXL and EZToolkit Advanced (Evita).
I've seen others saying their phone ends up booting normally after selecting Recovery from the Bootloader but mine just powers off when I select it and I can't find a previous thread with this issue.

It's possible your partitions are a bit funky. Running the 3.18 RUU might help.
Sent from my Evita
---------- Post added at 12:32 PM ---------- Previous post was at 12:31 PM ----------
We need to check your CID first.
Sent from my Evita

timmaaa said:
It's possible your partitions are a bit funky. Running the 3.18 RUU might help.
Sent from my Evita
---------- Post added at 12:32 PM ---------- Previous post was at 12:31 PM ----------
We need to check your CID first.
Sent from my Evita
Click to expand...
Click to collapse
Would this be what you're referring to? http://forum.xda-developers.com/showthread.php?t=2390405
And if so, I can try S-OFF even though I don't have root access?
My CID is all 1's
My HBOOT wouldn't cause this prob?

You can disregard all that. I ran the install for TWRP 2.6.3.0 from the EZToolkit Advanced (Evita) then cleared the cache with the automated option in the same Toolkit, which I have tried like 10 times a few hours ago and now it's working... I swear all I did differently was leave the phone idle and plugged in for a while.
I'd still like to get the S-OFF done at this time. When I run "fastboot getvar cid" it returns "cid: 11111111" which means I have SuperCID and I can go through with S-OFF?
Finally, I cannot find a S-OFF guide for HBOOT 2.14 and ATT Firmware 3.18. This is for my HBOOT but not my Firmware http://forum.xda-developers.com/showthread.php?p=42631876
I found this http://forum.xda-developers.com/showthread.php?t=2485865 which states it's for 3.18 Firmware but shows nothing for my HBOOT.
I also found this http://forum.xda-developers.com/showthread.php?t=2540232

S-off isn't specific to firmware, it works on all. Anyway, try Facepalm s-off.
http://forum.xda-developers.com/showthread.php?t=2155071
Sent from my Evita

timmaaa said:
S-off isn't specific to firmware, it works on all. Anyway, try Facepalm s-off.
http://forum.xda-developers.com/showthread.php?t=2155071
Sent from my Evita
Click to expand...
Click to collapse
You have no idea how terrified I am right now, modding a phone that is basically the same as the one that got bricked a few days ago.
Thank you for your assistance. I will indeed go with Facepalm as that's the one I used in the past

Back to Stock ATT? Which RUU?

Hey, I want to reset my HOX back to full AT&T stock settings. I'm just not sure which RUU to use. If someone could point me in the right direction, i'll be very grateful.
Thanks in advance.

Hangampalli said:
Hey, I want to reset my HOX back to full AT&T stock settings. I'm just not sure which RUU to use. If someone could point me in the right direction, i'll be very grateful.
Thanks in advance.
Click to expand...
Click to collapse
I guess you don't need to RUU it, previous one would work perfectly.
Sent from my One XL CyanogenMod 11 M9

azirgi said:
I guess you don't need to RUU it, previous one would work perfectly.
Sent from my One XL CyanogenMod 11 M9
Click to expand...
Click to collapse
Previous what??

azirgi said:
I guess you don't need to RUU it, previous one would work perfectly.
Sent from my One XL CyanogenMod 11 M9
Click to expand...
Click to collapse
Huh? He does need an RUU.
Transmitted via Bacon
---------- Post added at 08:20 AM ---------- Previous post was at 08:19 AM ----------
Hangampalli said:
Hey, I want to reset my HOX back to full AT&T stock settings. I'm just not sure which RUU to use. If someone could point me in the right direction, i'll be very grateful.
Thanks in advance.
Click to expand...
Click to collapse
What are your bootloader details please? We need to check something first.
Transmitted via Bacon

timmaaa said:
Huh? He does need an RUU.
Transmitted via Bacon
---------- Post added at 08:20 AM ---------- Previous post was at 08:19 AM ----------
What are your bootloader details please? We need to check something first.
Transmitted via Bacon
Click to expand...
Click to collapse
I'm S-OFF, SuperCID, and HBoot 2.15. I've also attached an image.

Hangampalli said:
I'm S-OFF, SuperCID, and HBoot 2.15. I've also attached an image.
Click to expand...
Click to collapse
Ok, you're good to go. You can run any RUU you like but if you want to run an at&t RUU these are the most recent:
3.18 RUU
5.18 RUU
Transmitted via Bacon

timmaaa said:
Ok, you're good to go. You can run any RUU you like but if you want to run an at&t RUU these are the most recent:
3.18 RUU
5.18 RUU
Transmitted via Bacon
Click to expand...
Click to collapse
This is probably a stupid question, but what are the differences between the two?
And thank you very much btw.

Hangampalli said:
This is probably a stupid question, but what are the differences between the two?
And thank you very much btw.
Click to expand...
Click to collapse
The 3.18 RUU is Android 4.1.2 and the 5.18 RUU is Android 4.2.2, keeping in mind that if you take the device back to fully stock, including stock CID, s-on, and locked bootloader, if it's on the Android 4.2.2 firmware the bootloader won't be able to be unlocked again because no exploit exists for that firmware. If you leave it s-off you can easily change the CID back to SuperCID and unlock the bootloader again though. But if you're selling it, it's not the best idea to give an s-off device to the average person.
Transmitted via Bacon

timmaaa said:
The 3.18 RUU is Android 4.1.2 and the 5.18 RUU is Android 4.2.2, keeping in mind that if you take the device back to fully stock, including stock CID, s-on, and locked bootloader, if it's on the Android 4.2.2 firmware the bootloader won't be able to be unlocked again because no exploit exists for that firmware. If you leave it s-off you can easily change the CID back to SuperCID and unlock the bootloader again though. But if you're selling it, it's not the best idea to give an s-off device to the average person.
Transmitted via Bacon
Click to expand...
Click to collapse
Thx Timma, i was looking for it. I have a HOX AT&T and i couldnt find the RUU. But after read this, i dont want to flash stock rom.

timmaaa said:
The 3.18 RUU is Android 4.1.2 and the 5.18 RUU is Android 4.2.2, keeping in mind that if you take the device back to fully stock, including stock CID, s-on, and locked bootloader, if it's on the Android 4.2.2 firmware the bootloader won't be able to be unlocked again because no exploit exists for that firmware. If you leave it s-off you can easily change the CID back to SuperCID and unlock the bootloader again though. But if you're selling it, it's not the best idea to give an s-off device to the average person.
Transmitted via Bacon
Click to expand...
Click to collapse
Hi timmaaa,
Im currently soff, supercid - if I were to use the 5.18 ruu to test an app in the play store, you're saying I'd have to get supercid again and unlock bootloader thru htcdev? Would i use the same supercid trick i used a couple years ago or is there an updated method? And lastly, would this cause any problems with going back to cm11 with the new hboot 2.18?
Thank you in advance!

buradd said:
Hi timmaaa,
Im currently soff, supercid - if I were to use the 5.18 ruu to test an app in the play store, you're saying I'd have to get supercid again and unlock bootloader thru htcdev? Would i use the same supercid trick i used a couple years ago or is there an updated method? And lastly, would this cause any problems with going back to cm11 with the new hboot 2.18?
Thank you in advance!
Click to expand...
Click to collapse
No, because you can leave the bootloader unlocked, leave it SuperCID, leave it s-off, when running the RUU. All you do is run the RUU without changing anything. The post of mine you quoted is only relevant to someone who wants to go back to stock. The 2.18 hboot is compatible with CM ROMs.
Transmitted via Bacon

how do you like the oneplus one in comparison to the htc one xl? sorry offtopic!

The OPO is light years better than the Evita. Light years.
Transmitted via Bacon

timmaaa said:
The OPO is light years better than the Evita. Light years.
Transmitted via Bacon
Click to expand...
Click to collapse
Do you happen to have an invite? I'd love to purchase one right now!