[Q] Need Help, HTC One XL Australia, recovery wont load SD Card

[Q] Need Help, HTC One XL Australia, recovery wont load SD Card - AT&T, Rogers HTC One X, Telstra One XL

HTC One XL stuck in boot loop, recovery will no load System, or SD Card, so i cannot retrieve my restores. have fastboot usb capabilities still, Does anyone know how to resolve this problem?

More information required. Please state your bootloader details, current ROM and kernel, current recovery, and a detailed description of the effects that lead to this situation.
Sent from my Evita

HBOOT 2.15.0000 --- S-Off & Unlocked
Radio 1.31a.32.45.16_2
ROM Viper xl
Recovery TWRP 2.5
I flashed oxp_elitekernel_130413, which i now realize was wrong, which led to the boot loop, So i tried to flash back to previous Kernal but it cam up with error device not found.
So i tried to access recovery and it just kept bootlooping. So i then flashed recovery again, now i have recovery but sd and system won't load.

You need to update your recovery, TWRP 2.5 is full of bugs. Get 2.6 or above from here and flash it using fastboot. Out of interest, how exactly did you try to flash back to your original kernel? You said you got a "device not found" message which doesn't seem right.
I'm not sure where you found that oxp_elitekernel but it certainly wasn't from within our device forum. You need to make sure you don't stray into other forums, nothing outside of our forum is compatible with our device, you're actually very lucky you didn't brick your phone. Our device forum main page is here:
http://forum.xda-developers.com/one-x-att
Bookmark that page and make sure you stay within it.
Sent from my Evita

I think i have bricked it....lol. Nothing is loading.

I flashed in fastboot cmd prompt. Because the sdcard isn't loading anymore it can't write or read the phone. so i don't care if i have to format the whole dam thing, i just dont know how to do it, without risking what little access i have left.

All Good, i worked it out in the end
Thanks to all who gave me feedback but i ended up figuring it out. If anyone has that problem in the future, all you have to do is format system and sdcard, (yeah i know you loose everything, but thats better than losing the whole phone.) then mount sdcard in TWRP, and place on the zip files for your roms, un-mount the partitions, then install the zips. If your S-ON, i guess you would flash boot image (unless S-ON stops you from wiping those partitions, in which case your screwed.) . But if you're S-OFF Just install and your back.

S-on doesn't stop you from wiping any partitions. Good to see you worked it out though. You might benefit from reading the Evita FAQ and How-To Guide For Beginners threads in my signature.
Sent from my Evita

I am not really a beginner, started hacking my phones 3.5 years ago. Been in love with it ever since, I was at the end of three nights with no sleep, and I wasn't thinking very clearly, and so I failed to notice that I had strayed into just the one x+ forum, and flashed the wrong kernal, very nearly bricking it in the process. Rookie mistake, one I'm not likely to repeat. Scared the crap outa me...lol.
Thanks for your help once again bud.
Sent from my HTC One XL using xda app-developers app

All good, no offence intended.
Sent from my Evita

Oh I know, was explaining more out of my own embarrassment then anything else..lol
Sent from my HTC One XL using xda app-developers app

Related

Noob Question About S-On, S-Off, and HTC's unlock

I used HTC's official unlock and my phone is unlocked, but has S-On. Is there a benefit to S-Off now that mine is unlocked? What is the difference between how the unlocks are? Sorry if i'm not making much sense, I'm new to this place and Android in general... I just got my sensation last week.

Welcome to Sensation
Don't worry, everyone's a noob at some point, I'm pretty much still a noob myself but as far as I understand it:
To this point you have unlocked your bootloader which simply allows the phone to boot with third-party software installed. In your phone there is a form of security check and the level of security is determined by whether you are S-ON or S-OFF. It's a flag at the radio level of your phone that checks images before they are allowed to be written to the system memory. So when you gain S-OFF, you gain unrestricted access to the NAND flash memory on your device, also known as root. With S-ON you can get temporary root but it's not guaranteed, with S-OFF you can get permanent root no matter what you flash.
Essentially gaining S-OFF permits superuser access to the phone, giving you control over all aspects of software and hardware.
If you like your phone the way it comes to you, all filled up with bloatware and stuck using only the latest version of Android that your carrier releases OTA, with a boring/crappy splash screen and boot animation (and so on and so forth ) then you have no real reason to get S-OFF.
If however you have seen some of the shiny ROMs put together by the devs here at XDA, or have a sweet custom splash screen you'd love to see every time you boot up the phone, or just like the idea of having complete control over YOUR phone and flashing what-the-hell-ever ROM/firmware/radio/other stuff you damn well please, then you should definitely consider rooting.
The disclaimer to all this is that if you aren't careful and don't thoroughly research what you're doing BEFORE you do it, you could brick your phone and give yourself some serious grief. The fact you're even asking this now is a point in your favour, there are far too many 'help me' posts on here from people who did something without bothering to try and understand it first. Knowledge is power and there's buckets of knowledge on this forum and others.
I'd suggest reading here and here at the very least.
Hope that helps

s-off means you may do anything with your phone,
you will lose warrenty at s-off gain it at s-on
as the other guy said if u want a nice toutch to your rom s-off it and install, if u want it still legal dont

Thanks for the info. I've been considering using an ICS OTA file on my HTC Sensation 4G, but the guides i've seen only mention S-OFF and nothing about the unlocked S-ON. I just can't wait for the official release!
On the other hand though, I also want to remove bloatware from this phone and found a script for such... but i can't seem to get any temp root method working. I'm not ready to jump off the deep end yet, but i'm tired of the unnecessary stuff.

I also couldn't wait for the official ICS release so I s-off, rooted, super CID, and flashed an ICS firmware and went to android revolution. Honestly, it's one of the best decisions Ive ever made. If you think your stock phone is running good right now, you'll be amazed when you flash it, it will run absolutely faster I tell you.
Though there are alot of risks doing all of that, it might brick your phone completely. So be very careful, read and understand everything if you're going to do all of those stuff.
Sent from revolutionized HTC Sensation ICS

HTC sensation stuck at boot
Hey Guys Noob here,
I need help big time. I gone and mess with something I shouldn't have. I'm a first time android/touch screen user so bear with me.
I was trying to S-off my phone (alrady rooted- after several tries) but I downloaded the juopunutbear zip file on my phone. I mistakenly loaded it via the CWM recovery and now the screen is stuck on that juopunutbear image.
I have tried to flash my rom because I thought it was just a boot loop, but nothing happened. I NEED some advice please don't tell me I bricked it. :crying:

man+droid said:
Hey Guys Noob here,
I need help big time. I gone and mess with something I shouldn't have. I'm a first time android/touch screen user so bear with me.
I was trying to S-off my phone (alrady rooted- after several tries) but I downloaded the juopunutbear zip file on my phone. I mistakenly loaded it via the CWM recovery and now the screen is stuck on that juopunutbear image.
I have tried to flash my rom because I thought it was just a boot loop, but nothing happened. I NEED some advice please don't tell me I bricked it. :crying:
Click to expand...
Click to collapse
if you can boot into bootloader then you are not bricked
secondly what do you mean by juopunutbear.zip and from where?
edit:you said that you are already rooted
which means that you have unlocked bootloader from htcdev site am i right?

Yes it was already unlock from HTC dev, but I was trying to get S- off using the wire trick method. In reading the Jounutbear guide thread it directed u to a link which has the zip file which I should have run on my pc but I had mistakenly installed it from my sd card and now it isn't going furthuer than that screen. I now can't using the Jbear exe bcuz it not recogining it.
I don't really want to keep adding my nonsense to the thread how can I PM someone for help.

man+droid said:
Yes it was already unlock from HTC dev, but I was trying to get S- off using the wire trick method. In reading the Jounutbear guide thread it directed u to a link which has the zip file which I should have run on my pc but I had mistakenly installed it from my sd card and now it isn't going furthuer than that screen. I now can't using the Jbear exe bcuz it not recogining it.
I don't really want to keep adding my nonsense to the thread how can I PM someone for help.
Click to expand...
Click to collapse
do this
install 4ext recovery
enable smartflash from it
flash the rom
http://forum.xda-developers.com/showthread.php?t=1631861

I did all that but the phone keeps booting up with the Juoputnutbear image that point to the phone. It looks similar to when I was just rooting the phone but it just no picking up nothing but that.

man+droid said:
I did all that but the phone keeps booting up with the Juoputnutbear image that point to the phone. It looks similar to when I was just rooting the phone but it just no picking up nothing but that.
Click to expand...
Click to collapse
that's weird
did you perform a full wipe(from recovery) before flashing the rom?
also as long as you are on S-ON use 4ext recovery to flash the rom
and before flashing the rom enable smartflash from 4ext
if you have done all the above then use a ruu.exe to return to stock condition
http://forum.xda-developers.com/showthread.php?t=1672425

Well that thread seems to be a mouth full remember I'm a noob. But I will try and read that again to get what it really says. It seems though that it was a complex instruction how to get back to the stock rom? Isn't there a file for that I can download. I get to doing that RUU thing to see if it works tho

man+droid said:
Well that thread seems to be a mouth full remember I'm a noob. But I will try and read that again to get what it really says. It seems though that it was a complex instruction how to get back to the stock rom? Isn't there a file for that I can download. I get to doing that RUU thing to see if it works tho
Click to expand...
Click to collapse
i saw your post in the other thread
you managed to install 4ext
now try to flash a custom rom
before flashing the rom enable smartflash from 4ext

Hey guys good news
I finally got the phone to power on. I saw this thread that highlead my pro http://forum.xda-developers.com/showthread.php?t=2284273 but I was really got the details from another forum. I don't know if I'm allowed to post it so I won't, but I'll sum it up.
All I need to do was flash the boot image on my current rom (get this from the zip file) and also flash the recovery image from a backup I had and presto.
But I'll go and follow you guys instruction about enabling the 4ext smart flash from now on. What I want to know though is for some custom roms (eg cyanogenmod 10.1) do I needs to be S-off to install it?
If so I'm still gonna try and S-off this here thingy. Givethanks y'all

man+droid said:
Hey guys good news
I finally got the phone to power on. I saw this thread that highlead my pro http://forum.xda-developers.com/showthread.php?t=2284273 but I was really got the details from another forum. I don't know if I'm allowed to post it so I won't, but I'll sum it up.
All I need to do was flash the boot image on my current rom (get this from the zip file) and also flash the recovery image from a backup I had and presto.
But I'll go and follow you guys instruction about enabling the 4ext smart flash from now on. What I want to know though is for some custom roms (eg cyanogenmod 10.1) do I needs to be S-off to install it?
If so I'm still gonna try and S-off this here thingy. Givethanks y'all
Click to expand...
Click to collapse
any ICS/JB rom you can install via enabling smartflash in 4EXT before flashing the ROM

ganeshp said:
any ICS/JB rom you can install via enabling smartflash in 4EXT before flashing the ROM
Click to expand...
Click to collapse
Hey thanx for the heads up. So I'm finally s-off using the J-bear method but where unlocked use to be I'm now seeing the juopunutbear there so I got back into android but it was the old CWM that was on it how do I get back the 4ext and would that be a prob if that J name remains there tho?

man+droid said:
Hey thanx for the heads up. So I'm finally s-off using the J-bear method but where unlocked use to be I'm now seeing the juopunutbear there so I got back into android but it was the old CWM that was on it how do I get back the 4ext and would that be a prob if that J name remains there tho?
Click to expand...
Click to collapse
no you are fine now
there is no problem with juopunutbear because now you have patched hboot which is unlocked
you are fine also with cwm recovery
but if you still want 4ext do only step 2 from here
http://forum.xda-developers.com/showthread.php?t=1631861

man+droid said:
I did all that but the phone keeps booting up with the Juoputnutbear image that point to the phone. It looks similar to when I was just rooting the phone but it just no picking up nothing but that.
Click to expand...
Click to collapse
might be a bad dl. Download it again and reflash or try a different rom.

[Q] Need some help badly, I just messed up my phone

OK i will admit I am over my head on this one. Frustration kicked in and I think I just lost all the data on my phone (pics and videos and everything which is the worst part). Here's the story.
I was originally on Team Venom 4.2 and was having random reboots.
I tried fixing by updating the Radio to ATT 3.18: http://d-h.st/DcT in this thread: http://forum.xda-developers.com/showthread.php?t=1694012 I flashed WITh the RIL (under the line that says do not flash these with newer roms) yeah I know.
flashed 3.18 again without RIL (above the 'do not flash' line
flashed att 2.0 radio
so now my radio still isnt working, tries to prepare sim card and will not work.
now I am trying to flash a new ROM to rewrite everything. tried to install android revolution HD. http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
flashed the android revolution boot.img file and attempted to flash the android revolution rom and would not flash, rebooted twrp after 30%
messed around in twrp a bit and hit factory reset. thought that would do a reboot of the android install. looks like i just formatted my sd card AND deleted android operating system. i cannot reboot into system 'no android os installed' and under twrp file manager i have NOTHING LEFT in my sd card. except the twrp folder. the phone has not been rebooted since.
DID I JUST LOSE EVERYTHING?
i am seriously interested in getting the pictures and data off the sd partition somehow. that is my main concern, i will deal with reinstalling android afterward.
any help will be rewarded, thank you in advance.

beppomarx said:
OK i will admit I am over my head on this one. Frustration kicked in and I think I just lost all the data on my phone (pics and videos and everything which is the worst part). Here's the story.
I was originally on Team Venom 4.2 and was having random reboots.
I tried fixing by updating the Radio to ATT 3.18: http://d-h.st/DcT in this thread: http://forum.xda-developers.com/showthread.php?t=1694012 I flashed WITh the RIL (under the line that says do not flash these with newer roms) yeah I know.
flashed 3.18 again without RIL (above the 'do not flash' line
flashed att 2.0 radio
so now my radio still isnt working, tries to prepare sim card and will not work.
now I am trying to flash a new ROM to rewrite everything. tried to install android revolution HD. http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
flashed the android revolution boot.img file and attempted to flash the android revolution rom and would not flash, rebooted twrp after 30%
messed around in twrp a bit and hit factory reset. thought that would do a reboot of the android install. looks like i just formatted my sd card AND deleted android operating system. i cannot reboot into system 'no android os installed' and under twrp file manager i have NOTHING LEFT in my sd card. except the twrp folder. the phone has not been rebooted since.
DID I JUST LOSE EVERYTHING?
i am seriously interested in getting the pictures and data off the sd partition somehow. that is my main concern, i will deal with reinstalling android afterward.
any help will be rewarded, thank you in advance.
Click to expand...
Click to collapse
Ok, first, you're all over the place. Why did you install a radio+RIL when it explicitly tells you not to? It's actions like this that get people like you into a lot of trouble and destroys phones.
Secondly, there is no Android Revolution HD for this device. I believe you have the HTC One XL / at&t One X (Evita) judging from your post, but like I said there's no ARHD ROM for the Evita, only for the HTC One X (Endeavoru). This leads me to believe that you're jumping between the two device forums, very bad idea, none of the stuff from the Endeavoru forum is compatible with our phone.
You're lucky the ROM install stopped otherwise you would have bricked your phone. Long story short, you have no OS because the ROM install didn't complete, you have a corrupt boot partition because you flashed the ARHD boot.img which isn't compatible. In future do not stray outside our device forum for any reason at all. Here's our forum main page, bookmark it:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Next. Performing a factory reset in TWRP recovery does not wipe user data (images/music etc). I'm not sure what you've done but the factory reset in recovery wasn't it. A factory reset performed in the bootloader does however corrupt the sd card, so never do a factory reset from the bootloader.
You might have a chance at saving some of your data using a data recovery tool in Windows. You'll need to mount usb storage in TWRP for Windows to access the sd. Do not under any circumstances do any writing to the sd card before you attempt to save your data.
In conclusion, you've made numerous mistakes with your device. You need to slow down a bit and educate yourself a bit better, a lack of knowledge when it comes to modifying devices is a very dangerous thing.
Please post the first five lines of your bootloader.
Sent from my Evita.

i could have sworn i got the android revolution rom from the att one x forum but i suppose not....
ok guys thanks so much so far i will pick up again after work today.
bootloader says:
TAMPERED
UNLOCKED
EVITA PVT SHIP S-ON RL
HBOOT-1.09.000
RADIO-0.19as.32.09.11_2
OpenDSP-v34.1.0.45.1219
eMMC-boot
Apr 2 2012,21:08:24
I'm 99.9% i was s-off before this all...

There isn't and never has been an Android Revolution ROM in this forum. It's kinda easy to make the mistake, the forums are named similarly.
I'm 99.9% sure you weren't s-off before all this. A phone can't change the security status without you doing it manually. It just can't happen. Did you actually go through either the Facepalm or Rumrunner s-off processes?
Well, you definitely have the Evita (HTC One XL / at&t One X) so make sure you stay within the forum I linked to earlier.
Good luck with attempting to recover your data, I hope you get at least some of it back.
Sent from my Evita.

Ok so as far as mounting my sd card in twrp, there's something up with my screen touch input I think... I am not able to click that particular box in the 'mount' menu. It seems like that part of the screen was not clickable when installing roms and such but once I get into android everything works perfectly.
Is there a way to rotate the screen in twrp?
Also by looking at my bootloader info once I get my sd card mounted and recovered best as I can, what is my best plan of action? Re-lock and flash a stock att ruu and begin from scratch or what? Or just try and load a correct radio and rom? I'm not a complete newbie I know I made a foolish mistake but I have done this quite a few times playing on the inspire, cha-cha, my kids nabi 2 tablets and on this att one x. This is the first time I have gotten really stuck in probably 35 flashes. Just this time I might be over my head...

To be honest I've never tried rotating the screen while in recovery, so I'm not sure about that. Exactly which recovery type (CWM/TWRP) and version number are you using?
I think your best plan of action would be to run an RUU, this will bring everything back to the way it should be. You're lucky in the sense that you're still on quite an early firmware version, so you should have a couple of RUU options. One thing to be careful of though, absolutely do not run a jb RUU if you have SuperCID, it will brick your device. SuperCID + s-on + jb RUU = brick. We should check your CID just in case, connect your phone in fastboot mode and issue this command:
Code:
fastboot oem readcid
Sent from my Evita.

beppomarx said:
i could have sworn i got the android revolution rom from the att one x forum but i suppose not....
Click to expand...
Click to collapse
There is absolutely no ARHD ROM for EVITA. You've made a grave error, and as timmaaa mentioned, you are lucky your phone isn't a paperweight now.
EVDEAVORU is partitioned completely differently from EVITA, so all bets are pretty much off on whether your data is still intact or not. The ROM itself may have overwritten your data. Also, if you happened to do a factory reset in hboot instead of TWRP (as you mentioned) this will corrupt the SD card on modded EVITAs (known issue, and somewhat common error).
Your best bet is to get the phone back up and running using timmaaa instructions. Then see if the files are still on the SD. If the data files aren't easily visible, you can also try data recovery programs to see if they can be salvaged (sometimes corrupted files get dumped to a temp folder, or otherwise recoverable).
But I wouldn't hold my breath on recovering the files. This is what always puzzles me (why folks never back their data, then freak out when its gone of damaged). If your data is important to you, its important enough to back up. And there are so many easy methods to do so (with built-in cloud backup apps and whatnot) yet so many folks neglect to do that. And all you are left with is regret when things do south. Its pretty much a no-brainer to backup anything important to you when modding the phone. I'm puzzling why so many folks never do it.

So since I have the 1.09.000 hboot i am going to download and install this:
1.85.502.3
File Timestamp: 25/05/12
Publically Seen: 06/06/12
Android: 4.0.3
Kernel: 3.0.8-01155-gca24d1e
hboot: 1.09.0000
radio: 0.17.32.09.12_10.86.32.08
adsp: 28.1.0.32.0504
wcnss: 1031120A
tp_syn3202: 3.0_PR1100755
tz: 001.031.511
sbl1: 001.031.503
sbl2: 001.031.501
sbl3: 001.031.502
OTA: OTA_Evita_UL_Cingular_US_1.85.502.3_R2_NEW_NFCPHON ESTORAGE-1.73.502.1_release_263287jkmeqj8u75z409z9.zip
RUU: RUU_Evita_UL_Cingular_US_1.85.502.3_R2_Radio_0.17. 32.09.12_10.86.32.08L_release_262092_signed.exe (Download)
Source: evita-ics-crc-3.0.8-271616b.zip
is this my best bet? I am going to try and check my CID status right now just need to download the android SDK and get that going...
**EDIT**
my CID is 11111111. is that superCID?
**EDIT**
looking for a way to remove superCID. If i just go S-off am i OK to run a RUU or should I keep looking to change my CID back?
**EDIT**
just downloaded WinDrid HTC One XL Toolkit and seems to be up and running fine. my plan so far is to S-off and run the RUU I posted above but I will wait for someone to chime in before I do anything else.. I feel like I am on the edge here and don't want to brick it... I can't find any way so far to return my CID but from what I read if I am S-off it should keep me safe.

S-off won't work unless you're able to boot into a ROM. I'd forget about using a toolkit for now, it completely bypasses some much needed learning, and doesn't always work anyway. I believe all you need to do is relock your bootloader and then run the RUU.
Sent from my Evita.

Ok I will look into how to re-lock that after work today. Can anyone else confirm this? Not that I don't trust you but wording it like 'I believe this will work' makes me ask again...

I'm 99.99% sure it's only the jb and above RUU that you need to worry about while s-on and SuperCID.
Sent from my Evita.

timmaaa said:
I'm 99.99% sure it's only the jb and above RUU that you need to worry about while s-on and SuperCID.
Click to expand...
Click to collapse
ICS RUUs are free of the S-on and SuperCID bug. Plenty of folks have flashed that RUU (such as 2.20) with SuperCID with no issue.

so I am going to relock the bootloader, it's as simple as 'fastboot oem lock'? that's it? before doing so should i bother s-off first? here's my plan of action:
s-off
relock bootloader
run 2.20.502.7 ruu
unlock bootloader again
install twrp
load custom rom
that should work correct?

If you s-off first, I believe you do not need to relock the bootloader to run the RUU. Just s-off, then run the RUU.

As I've previously mentioned, you won't be able to get s-off unless your phone will boot a ROM. The above process looks right.
Sent from my Evita.

got back to stock just fine, now to work my way back to modded. You guys are the best thank you a million.

Please hit the thanks button on any post that you've found helpful on XDA.
Sent from my Evita.

Remember also to either s-off or change cid back to normal, it will assist in the future if you get in a jam like this.
Although s-off and flashing a rom for a different phone(like you did) may have ended up much worse as some of the checks that likely saved you will be disabled.
At very least do not OTA/RUU update to Jellybean while you are s-on and supercid!

[Q] Can't achieve S-OFF or re-flash recovery. Am I bricked?

Background:
My wife migrated from the (US AT&T) One X to the One on day one. Her One X has been sitting in her bedside drawer for almost a year. (She wanted to keep it as a backup.) Her One recently suffered irreparable physical damage; need to get her up and running on the One X.
Before the One X's temporary retirement, we:
Gained SuperCID
Unlocked Bootloader
Flashed custom recovery
Flashed a (Android 4.1 based) AOKP nightly
Did not achieve S-OFF
When the One X came back out of retirement, it had some major stability issues. Coming from the Nexus world, and (admittedly) not doing thorough enough research, I thought I could quickly re-ROM her phone and have her up and running.
Long-story short, I've somehow seemed to corrupt the recovery partition and the boot partition. And I'm not sure where to go next...
I can access the bootloader and fastboot. In fact, the bootloader is immediately loaded on boot.
I cannot achieve S-OFF. Every method I've seen requires some combination of fastboot and adb commands. I can do the fastboot portion, but without a working Android partition, I cannot perform the adb commands.
Every attempt to flash a custom recover via fastboot fails:
FAILED (remote: 12 signature verify fail)
From the research I've done, it seems like I need S-OFF to flash a recovery and ROM, but I need a ROM to achieve S-OFF.
Is that the case? Is there anything else I can try?

Run the 2.20 RUU, it's the only option you have, it should fix your partitions. Do not run the 3.18 RUU while s-on though or you'll brick.
How did the phone end up with borked partitions?
Sent from my Evita<br>

timmaaa said:
Run the 2.20 RUU, it's the only option you have, it should fix your partitions.
Click to expand...
Click to collapse
Found and downloaded 2.20 RUU; was nervous as hell running this with S-ON. The process never errored out, and the application never hung, I never saw a progress bar on the HOX either. (RUU quoted ~10 minutes. I waited 40.) I hard-bounced the phone and tried again... Success!
Thanks for the recommendation!
timmaaa said:
How did the phone end up with borked partitions?
Click to expand...
Click to collapse
I pushed the stock T-Mobile ROM to the phone from the older recovery that was already on the HOX, then rebooted. It hung at boot; was never able to boot back into Android. I was still able to access the bootloader and fastboot, so I tried pushing TWRP to the HOX using the WinDroid Toolkit. After that, I wasn't able to access Android or TWRP, and the phone booted directly to the bootloader.
The biggest mistakes: cockiness and lack of research. (Statement of frustration: this S-ON/S-OFF nonsense is for the birds!)

I'd strongly suggest you get s-off now, and discontinue your use of toolkits in favour of manual fastboot commands.
Sent from my Evita

timmaaa said:
I'd strongly suggest you get s-off now, and discontinue your use of toolkits in favour of manual fastboot commands.
Click to expand...
Click to collapse
Noted. Thanks...
The whole situation was frustrating because it was self-inflicted and I knew better than rush into trying to re-ROMing on hardware I wasn't familiar with.
I usually don't use toolkits; was just on a system that hadn't been prepped with adb yet. I re-learned a valuable lesson: take the time to set that up!
What's most frustrating is that I did try to use adb (after hosing the filesystem). I just kept running into issues with S-ON while trying to push boot.img's and recoverys. Coming from my Nexus world, I'm not accustomed to that.

Cool cool. It might be worth taking a quick look at my Evita FAQ and How-To Guide For Beginners threads in my signature. I'm not insinuating that you're a beginner, but they contain some vital information specific to this device which you might find useful.
Sent from my Evita

timmaaa said:
It might be worth taking a quick look at my Evita FAQ and How-To Guide For Beginners threads in my signature. I'm not insinuating that you're a beginner, but they contain some vital information specific to this device which you might find useful.
Click to expand...
Click to collapse
Yeah... that -- among many, many others threads -- was one of the threads I checked out after killing it.
I was so convinced that S-ON was my problem that I spent most of my time trying to get S-OFF and repair my recovery via fastboot. Had I been able to let go of that notion, I might have gotten somewhere without having to ask for help.
I only-ever mess with the wife's hardware when there's a problem, so I'm not incredibly familiar with it. I'll definitely re-review your guide before I take on any other tasks!
Thanks again!

Unable to do OTA from 1.09

I have a AT&T One X rooted
HBOOT-1.09.0000
RADIO-0.17.32.09.12
I am attempting to do the OTA's or RUU to bring it up to current because I realized since I had not touched it since first purchased and rooted so none of the OTA's went through. I never gave myself time allowed to figure out how to send them.
Well now I'm trying and I have gotten myself in to a hot mess.
I first tried using the FUU Upgrades provided by Flashalot but it said "wrong update" and I could not find a reason. I backed up a couple and tried 2.14. Well eventually it just stayed at the fastboot "HTC" screen for nearly an hour and appeared locked up. So I pulled it and rebooted. It would not let me get past the boot up screen until I cleared cache's and went back to my stock rom (cmod 10).
Now it will not mount "SD Card" when connected USB and in TWRP. I am also unable to download any files to it via browser or launched phone because it says no SD Card installed.
I attempted to send any of the OTA's via fastboot and it hangs (giving it hours...overnight even). I did writecid 11111111 before sending some with same results.
Any suggestions?
Thanks

stampy101 said:
I have a AT&T One X rooted
HBOOT-1.09.0000
RADIO-0.17.32.09.12
I am attempting to do the OTA's or RUU to bring it up to current because I realized since I had not touched it since first purchased and rooted so none of the OTA's went through. I never gave myself time allowed to figure out how to send them.
Well now I'm trying and I have gotten myself in to a hot mess.
I first tried using the FUU Upgrades provided by Flashalot but it said "wrong update" and I could not find a reason. I backed up a couple and tried 2.14. Well eventually it just stayed at the fastboot "HTC" screen for nearly an hour and appeared locked up. So I pulled it and rebooted. It would not let me get past the boot up screen until I cleared cache's and went back to my stock rom (cmod 10).
Now it will not mount "SD Card" when connected USB and in TWRP. I am also unable to download any files to it via browser or launched phone because it says no SD Card installed.
I attempted to send any of the OTA's via fastboot and it hangs (giving it hours...overnight even). I did writecid 11111111 before sending some with same results.
Any suggestions?
Thanks
Click to expand...
Click to collapse
First question is do you have s-off?
Second question is did you perform a factory reset from the bootloader at some point? I ask this because it looks like your sd card is corrupt, and that's what happens when you perform a factory reset from the bootloader on a modified Evita. Either way I believe you need to wipe your sd card with TWRP before it'll become usable again. If it still isn't usable after a wipe, try mounting it to your PC again so you can format it with Windows.
My last question is what is your end goal? Are you wanting to run a stock ROM and that's why you're wanting to install OTA updates? The rule of thumb for modified phones is to never install OTA updates on them. If you're just looking to update to the latest/latest needed firmware, you can just flash a firmware package or run an RUU. You must have s-off to do this though.
Another thing I should mention is that you don't use fastboot to install OTA updates. It seems like you're not exactly sure about what you're doing, which can be a very dangerous thing when messing with a modified device. I think you need to do a bit more research before continuing ahead. Tell me exactly what your end goal is though and I'll provide as much information as I can.
Sent from my Evita

FUBAR?
timmaaa said:
First question is do you have s-off?
Second question is did you perform a factory reset from the bootloader at some point? I ask this because it looks like your sd card is corrupt, and that's what happens when you perform a factory reset from the bootloader on a modified Evita. Either way I believe you need to wipe your sd card with TWRP before it'll become usable again. If it still isn't usable after a wipe, try mounting it to your PC again so you can format it with Windows.
My last question is what is your end goal? Are you wanting to run a stock ROM and that's why you're wanting to install OTA updates? The rule of thumb for modified phones is to never install OTA updates on them. If you're just looking to update to the latest/latest needed firmware, you can just flash a firmware package or run an RUU. You must have s-off to do this though.
Another thing I should mention is that you don't use fastboot to install OTA updates. It seems like you're not exactly sure about what you're doing, which can be a very dangerous thing when messing with a modified device. I think you need to do a bit more research before continuing ahead. Tell me exactly what your end goal is though and I'll provide as much information as I can.
Sent from my Evita
Click to expand...
Click to collapse
OK So it sounds like I've probably corrupted my memory from what you are saying. Any going back?
1. S-Off. I'm going with no. It was 2 years ago when I rooted it and installed CM10. I do not recall doing this but just flashing CM.
1a. Attempting to do it now just shows error 99 unknown error...
2. Yes. I do believe that I had hit the factory reset. Attempting to do the wipe in TWRP shows "success" but it also shows it could not mount E:\
2a. Still will not let me turn on USB storage. It just spins for a while and ends up giving up when the display is changed.
3. End goal...I could care less about root. I've always used modded ROM's and prefer them. I only did "OTA" when the RUU would not take. I became a bull in a china shop and started banging with a hammer...Was dumb but I think I had already corrupted the memory by hitting factory reset. (I'll be honest I never meant to hit that).
I've rooted and installed many a custom ROM's, but I prefer the simple methods of following one of the many awesome easy setups on here. I'm not completely useless...
I would like to get it back to the SD card working and be able to update the firmware and a moderately functioning ROM.
Thank you for any help. I really do appreciate it.

stampy101 said:
OK So it sounds like I've probably corrupted my memory from what you are saying. Any going back?
1. S-Off. I'm going with no. It was 2 years ago when I rooted it and installed CM10. I do not recall doing this but just flashing CM.
1a. Attempting to do it now just shows error 99 unknown error...
2. Yes. I do believe that I had hit the factory reset. Attempting to do the wipe in TWRP shows "success" but it also shows it could not mount E:\
2a. Still will not let me turn on USB storage. It just spins for a while and ends up giving up when the display is changed.
3. End goal...I could care less about root. I've always used modded ROM's and prefer them. I only did "OTA" when the RUU would not take. I became a bull in a china shop and started banging with a hammer...Was dumb but I think I had already corrupted the memory by hitting factory reset. (I'll be honest I never meant to hit that).
I've rooted and installed many a custom ROM's, but I prefer the simple methods of following one of the many awesome easy setups on here. I'm not completely useless...
I would like to get it back to the SD card working and be able to update the firmware and a moderately functioning ROM.
Thank you for any help. I really do appreciate it.
Click to expand...
Click to collapse
There's no point in attempting s-off at the moment because s-off requires that a working OS is installed. You can tell whether you're s-off by looking at your bootloader, it'll say s-on or s-off in the first line under the unlocked and tampered banners.
Your problem with your sd might be that the version of TWRP you have installed is too old, only the newer versions are able to fix a corrupt sd card. 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 try wiping and mounting the sd card again. Once we have that sorted out we can move onto getting your firmware updated.
Sent from my Evita

OK! Looks like we are getting somewhere! It is now mounted.

Now you can copy files across to flash. You'll need to get s-off now so you can update your firmware. You'll need a bootable OS installed to do that, I'd suggest installing Kickdroid and then you can attempt getting s-off via the Rumrunner method.
Sent from my Evita

You are awesome! Thank you so very much for your help. Up and running.

How far have you gotten?
Sent from my Evita

S-Off and firmware updated and running with different ROM's. I'm golden man. Unless you can think of something I should consider?

As long as you're on the 2.15 firmware or higher, you are indeed golden. I was just curious.
Sent from my Evita

Hey there, I just noticed you made a donation to me with this thread as the reference. I just wanted to thank you, that's very generous of you. Donations aren't expected in return for my assistance but are greatly appreciated. Anyway, thanks again and have a great day.

Is this soft brick?

Hi, I was having issues so i ran a RUU by suggestion and reset my device. afterwards I unlocked, flashed twrp 2.6.3 (2.7+ doesn't work, just boot loop) and then i upgraded to hboot 2.14 so i could install the roms i wanted. since upgrading to 2.14 i was getting new errors so i tried to wipe the device and restart and now I did that all the files are missing.
I cannot mount anything or boot, so i can't install via recovery or sideload at all, because it can't mount to anything. I can't restore or do anything else because it can't mount the cache, data etc.
I tried running the RUU again but now i am getting error 117 and it can't detect the phone, and since it has no OS installed it doesn't go far enough to register with the RUU application, or so i believe.. the phone does work fine, can access fastboot and recovery, i just can't mount or install anything else.
I am currently
Unlocked
S-OFF
HBOOT 2.14 (TextRemoval)
TWRP 2.6.3.0 (Anything higher doesn't work, will just show htc logo(20s), then go to black screen(15s or so) and bootloop
CID:111111111111
Some suggestions would be great. I've run out of ideas and spent the whole day trying different things to fix it.

When you say "so I tried to wipe the device" what exactly do you mean? Did you perform a factory reset from the bootloader? If so, you've corrupted your sd card and that's why you can't mount it. Use TWRP to wipe the sd card and then mount it to Windows and format it. You may need to flash TWRP 2.6 specifically to accomplish this. Once that's done you should be able to copy a ROM across.
You mentioned upgrading to hboot 2.14, and I see you flashed the modified one with the removed red text. That isn't the correct way to do it, you're supposed to run the 3.18 RUU so you get the full firmware. Having just the hboot upgraded is pretty pointless. Plus, those modified hboots have caused problems for a few people so I'd suggest just dealing with the red text for five seconds on boot. Basically what you need to do is run the 3.18 RUU to bring your hboot and firmware back onto line.
Which RUU did you run in the first place? And specifically which ROM build did you try to flash? This information will also help to diagnose why you were boot looping to begin with.
It's probably worth reading the Evita FAQ thread and the How-To Guide For Beginners thread, both links are in my signature, and both threads contain some essential information.
Sent from my Evita

On twrp 2.7,aren't we supposed to delete the .twrp .twrp in twrp folder by using a file explorer? I remember reading that in pandasas twrp o.p
Sent from my Desire HD using Tapatalk

I didn't need to do that, but yes, if you experience problems that's the first thing to do. Reading the OP is essential, and reading the last few pages of a thread is strongly recommended.
Sent from my Evita

timmaaa said:
When you say "so I tried to wipe the device" what exactly do you mean? Did you perform a factory reset from the bootloader? If so, you've corrupted your sd card and that's why you can't mount it. Use TWRP to wipe the sd card and then mount it to Windows and format it. You may need to flash TWRP 2.6 specifically to accomplish this. Once that's done you should be able to copy a ROM across.
You mentioned upgrading to hboot 2.14, and I see you flashed the modified one with the removed red text. That isn't the correct way to do it, you're supposed to run the 3.18 RUU so you get the full firmware. Having just the hboot upgraded is pretty pointless. Plus, those modified hboots have caused problems for a few people so I'd suggest just dealing with the red text for five seconds on boot. Basically what you need to do is run the 3.18 RUU to bring your hboot and firmware back onto line.
Which RUU did you run in the first place? And specifically which ROM build did you try to flash? This information will also help to diagnose why you were boot looping to begin with.
It's probably worth reading the Evita FAQ thread and the How-To Guide For Beginners thread, both links are in my signature, and both threads contain some essential information.
Sent from my Evita
Click to expand...
Click to collapse
Firstly, thanks for your help timmaaa.
The RUU i used was:
RUU_Evita_UL_Telstra_WWE_1.89.841.9_Radio_0.18c.32 .09.01_10.93a.32.20L_release_266699_signed.exe
I simply went to the RUU list and picked the most recent one of my carrier.
I installed it and it worked and booted, however the touch screen did not work. This confused me more because the reason I did a RUU was because the 3 softkeys were no longer working prior, and I was trying to fix it.
I was then having issues flashing roms because of the hboot, so I upgraded the hboot to 2.14 to solve this, using the method and 2.14 Textremoval file in the thread here: http://forum.xda-developers.com/showthread.php?t=2156686
After installing the hboot fine, I then went back to install candykat (to be honest all i want is a working phone, any rom works for me) and then was met with the error that it could not mount E:cache. Now i was also having issues where the bottom buttons in the Recovery menu would not respond (not the softkeys under the screen) and so i tried fixing permissions to this. Either way I got it working again - but was just other strange thing.
I just formatted the phone after mounting it in twrp 2.6.3.0 so now its ready to continue. Not sure what RUU or rom or what to go with next.

You have s-off so you don't need to worry about sticking to RUU's from your carrier, you can run any Evita RUU you like. My advice is to run the 3.18 RUU from at&t, that one will give you the firmware you require for aosp ROMs. Stay away from those modified hboots, just deal with having a red text. Make sure you flash the appropriate recovery for whatever ROM you want to flash, keeping in mind that most (maybe all?) current aosp ROMs require either the unofficial TWRP 2.7.0.8 by @pandasa123, found in our Android Development Section, or the official TWRP 2.7.1.0 from here.
Sent from my Evita

timmaaa said:
You have s-off so you don't need to worry about sticking to RUU's from your carrier, you can run any Evita RUU you like. My advice is to run the 3.18 RUU from at&t, that one will give you the firmware you require for aosp ROMs. Stay away from those modified hboots, just deal with having a red text. Make sure you flash the appropriate recovery for whatever ROM you want to flash, keeping in mind that most (maybe all?) current aosp ROMs require either the unofficial TWRP 2.7.0.8 by @pandasa123, found in our Android Development Section, or the official TWRP 2.7.1.0 from here.
Sent from my Evita
Click to expand...
Click to collapse
How can i flash the RUU without being able to boot?
When installing a RUU it says to turn the phone on and connect it via usb.
I get an error that there is no usb connection. I have tried just having the phone on and sit at the htc screen, going into bootloader, going into fastboot, recovery, mount in recovery. None of these methods connect with the RUU application. Is this normal? I can't remember how i did the RUU the first time around - but I did have access to the OS so i probably ran the RUU with the phone on and idle at homescreen the first time around.

xlmama said:
How can i flash the RUU without being able to boot?
When installing a RUU it says to turn the phone on and connect it via usb.
I get an error that there is no usb connection. I have tried just having the phone on and sit at the htc screen, going into bootloader, going into fastboot, recovery, mount in recovery. None of these methods connect with the RUU application. Is this normal? I can't remember how i did the RUU the first time around - but I did have access to the OS so i probably ran the RUU with the phone on and idle at homescreen the first time around.
Click to expand...
Click to collapse
You don't need the phone to be able to boot to run an RUU. Just boot the phone into the bootloader and start the RUU. The "not having a usb connection" problem can be caused by countless things; incorrect usb port (must be 2.0), incorrect usb cable (original HTC cable is recommended), drivers aren't setup properly. Those are the main offenders.
Sent from my Evita

timmaaa said:
You don't need the phone to be able to boot to run an RUU. Just boot the phone into the bootloader and start the RUU. The "not having a usb connection" problem can be caused by countless things; incorrect usb port (must be 2.0), incorrect usb cable (original HTC cable is recommended), drivers aren't setup properly. Those are the main offenders.
Sent from my Evita
Click to expand...
Click to collapse
I was able to get the RUU working and the 3.18 at&t is now installed and working. However I'm now back to my old issue of the 3 capacitive buttons at the bottom not working.
Is there anything software related to fix this or is it likely a hardware failure? When i tap any of the 3 keys, at best it will activate a touch at the lowest portion of the screen on that particular y axis. Example: I press the home key; instead of going back to the homescreen it does nothing, and at most sends a touch command just above at the bottom of the actual touch screen area.
Also, if you think it is a hardware issue, would it be the digitizer? I see they are $30 or so on ebay and figured i could fix up the phone. Everything else works fine except the damn cap. keys
http://www.ebay.com.au/itm/Genuine-...gitizer-front-panel-replacement-/261100897324

During any of your adventures with flashing on this phone, did the cap buttons begin working again at all? My thought is definitely that it's a hardware issue. The digitizer would be the culprit, but, do not attempt to separate the digitizer from the LCD, it will result in one or both of the items being destroyed. You'll need to buy the LCD + digitizer as a set.
Sent from my Evita

timmaaa said:
During any of your adventures with flashing on this phone, did the cap buttons begin working again at all? My thought is definitely that it's a hardware issue. The digitizer would be the culprit, but, do not attempt to separate the digitizer from the LCD, it will result in one or both of the items being destroyed. You'll need to buy the LCD + digitizer as a set.
Sent from my Evita
Click to expand...
Click to collapse
At most the cap. buttons will light up / flash when the phone does a particular action, but no actual response or input of the cap. buttons registers. I'm going to order the digitizer from the link above and hope for the best. It doesn't clearly say it, but I'm assuming it does come with the digi + screen in one.

I think you're wasting your money, that looks like it's only the digitizer. You can't separate them without destroying at least one.
Sent from my Evita

timmaaa said:
I think you're wasting your money, that looks like it's only the digitizer. You can't separate them without destroying at least one.
Sent from my Evita
Click to expand...
Click to collapse
Hmm, thats a bummer.
On another note. I just picked up the phone and unlocked it and it started vibrating like crazy, opened up the message (sms) app and started inputing random keys on the onscreen keyboard. Definitly something malfunctional with the screen. Bottom cap keys not working and random bouts of the screen randomly inputing.

The vibe crazy thing sounds like what happened to me on an inspire. Flashed wrong firmware
Sent from my HTC One X using Tapatalk

Database Info

welcome