Originally Posted by Zabbi

Funny you mention the issues with 2.4 wiping your SD and the mount issue. I just recovered from something similar with both of those things happening simultaneously. Happened when I flashed Elemental 6.5, running current Viper... Not too sure what the issue was exactly, couldn't boot, recovery couldn't mount SD. Fixed with a fastboot flash of the boot.img from Bulletproof... my SD was empty at the end if it all though.

Not too sure if it was an issue I had with the settings I had on the kernel from install, ie. too much overclock/undervolt... or if it was an issue with the recovery. Almost tempted to try TWRP 2.3.3.0 flashing with the higher kernel settings.

Sent from my HTC One X using xda premium

The HTC One X, One S, and EVO LTE are all somewhat prone to blowing away their internal sdcards. We don't experience these issues with other devices so I feel confident that it's not an issue with TWRP.

Any real reason to switch from 2.3.3.0?

Sent from my One X using xda app-developers app

Originally Posted by Desertman123

Any real reason to switch from 2.3.3.0?

Sent from my One X using xda app-developers app

2.5 is shiny and new!

Sent from my HTC One X using xda app-developers app

Hey, the screen timeout feature started back with 2.4.2 right?
I was backing up a nightly all boxes checked... left the room, came back, screens off, unlocked it. It seemed like the backup had stopped and it resumed when I unlocked the screen. I hit the screen again when it dimmed so it would continue. The complete compressed backup took about 200 seconds. Is it possible that the timeout stymied the operation?
If so could this be an if-then programming situation that a longer than the timeout operation would bypass the screen timeout until it's finished.

What's the lowest version I can use with the new touch screen firmware?

my blazing fast hatka xl!

Originally Posted by twisteddroid

What's the lowest version I can use with the new touch screen firmware?

my blazing fast hatka xl!

CHANGELOG for 2.3.1.1:
-Updated kernel to fix touchscreen issues

if you didn't want to read the OP

Originally Posted by DvineLord

CHANGELOG for 2.3.1.1:
-Updated kernel to fix touchscreen issues

if you didn't want to read the OP

Sorry I just reading and I got confused I wanted to go back to 2.3.3.1 but I did the 3.18 ruu for what reason I'm not sure of now. Anyway I read somewhere that I had to go to a newer version to be compatible with the new firmware

my blazing fast hatka xl!

Originally Posted by twisteddroid

Sorry I just reading and I got confused I wanted to go back to 2.3.3.1 but I did the 3.18 ruu for what reason I'm not sure of now. Anyway I read somewhere that I had to go to a newer version to be compatible with the new firmware

my blazing fast hatka xl!

As of now, I see most users sticking to 2.3.3.0 because of issues when flashing kernels and ROMs, specifically CM. 2.3.3.0 is what I've been using ever since I rooted my HOXL and I haven't had a single issue with it.

Originally Posted by Scozzar

As of now, I see most users sticking to 2.3.3.0 because of issues when flashing kernels and ROMs, specifically CM. 2.3.3.0 is what I've been using ever since I rooted my HOXL and I haven't had a single issue with it.

my blazing fast hatka xl!

Thanks. I been using 2.3.3.1 since the day I rooted but the other day I ran the 3.18 ruu so I put 2.5 on because I wasn't sure if the other would work. I'm flashed back to 2.3.3.1 now and all is good

Request for testing

---

Note: I have obtained permission from Dees_Troy to post this here.
Caution: Advanced users only. I will not take responsibility for damaged devices.

I put some work into updating and unifying the TWRP device trees for evita, jewel, fireball, and ville. Before I make a pull-request to TeamWin, I need the below recovery image tested. Everything should work just as well as in the official TWRP 2.5.0.0. If there are any regressions, please report them!

A couple changes worth noting:

1. Can backup encrypted data partitions of AOSP based ROMs (see notes below for CyanogenMod example)
2. sdcard is now called Internal Storage (path: /sdcard)

evita image: unofficial_twrp_2.5.0.0x1-evita.img
Update x1: (hopefully) adds USB OTG support

CyanogenMod Encryption notes

 

Pre-requisites:

1. CyanogenMod for evita build 20130516 or newer

Encryption procedure:

1. Make a full backup in TWRP
2. Restore your backup - This seemingly odd step will ensure a footer is allocated at the end of your data partition for encryption data.
3. Install a CM build equal to or newer than 20130516 and wipe Dalvik cache
4. Reboot and let phone battery charge to 100%
5. Turn on Airplane mode
6. Settings > Security > Encrypt phone
   Be patient, your screen may go black for a couple minutes without indication of anything occurring before a reboot occurs and encryption progress is displayed.

Reverting encryption:

1. Make a full backup in TWRP (you will need to enter your encryption PIN upon entering recovery)
2. Reboot to TWRP, but instead of entering your encryption pin, just hit cancel
3. Wipe your data partition
4. Restore your backup