[HTC One X] djeggy:
Hello,

Grab a drink and settle in, this ones lengthy!

My HTC one XL (UK, EE, Evita, CID: ORANG001) has been uber slow recently and I'd been wanting to have a tinker, remove bloatware for a while. So I set about investigating unlocking bootloader, rooting and flashing a funky ROM.

I first created a backup of phone using a couple of apps (to be safe, easy backup & Helium), then I copied all of the phone folders to my PC (to be safe), then I installed CWRom Manager and then from there installed CWM Recovery (6.0.2.8), unlocked the bootloader through HTCdev, no issues, booted back into CWM and made a backup.

Then I rooted my device using "BETA-SuperSU-v2.66-20160103015024" via the command line prompt, no issue there, took another backup in CWM Recovery.

Then I booted my phone, went into CWMRom manager, chose to flash a ROM "CM 10.0.0" and rebooted, phone got stuck at cyanogen mod screen and restarted x2 (realised I hadn't flashed the boot.img)

flashed the boot img via cmd line and phone booted into the initial set up screen (happy as a pig in dirt I was)...then I realised the touch screen wasn't working, bit of googling, found it a common problem, bit too late @ night to resolve, plus I couldn't find the correct file to replace the screen drivers, so I thought I would just revert.

I think (because I can't exactly remember this pattern of choices) that I chose the wipe/factory reset in CWM thinking that I would simply undo all that I'd done, re-do (as I quite enjoyed it) and select a different ROM, so when I booted into bootloader I think I then chose "clear data", the phone rebooted but got stuck at the white HTC quietly brilliant screen.

Realising there was no O/S, into Bootloader again and this time chose fastboot, went onto my PC but it wouldn't recognise the SD card in the phone and wanted me to format it. So I did so, I chose FAT32 and did a quick format.

Looking for a stock 4.2.2 ROM to return to I downloaded this "EVITA_UL_JB_50_S_TMO_DE_5.08.111.2_By_Turge", then flashed the boot img and it worked fine and got me my phone back to life, albeit T-Mobile and German bloatware.

I then tried to flash CM12.1 via CWM recovery, but it failed due to no file contexts and mounting issues (see attched pic) and at the end of it was status 7 error. I then maually mounted all points in CWM (/system /data /cache etc) and re-run, this time status error 0 message. Bit more googling led me to replacing the "META-INF" file from a working ROM (so I chose the ze German one) into the non-working CM12.1, and it worked. Phone booted, but it was back into the German ROM, not CM12.1. :confused:

So today, found my original nandroid backup from CWM recovery and restored to it. Phone back alive and working again. I downloaded CM11 (thinking it was better suited to my bootloader 2.18) but again, I get the mounting issues present with /system /data etc, BUT...when I tried to re-flash the german ROM, that worked. So it can flash something, just not everything. :(

So it can flash - but it seems that something just isn't right with my storage and I can't place it. I'm not sure of what commands to run to identify what partitions do and don't exist on the damn thing, so I could do with some help there. It feels like if I sort my storage issue out and get over that hurdle, I can flash a ROM. Do I need to re-create any -ext partitions?? I have downloaded an app, retrieved partition and usage info and have posted it also.

My current state as of writing;

Botloader unlocked

rooted with SuperSU

I have installed TWRP App, however I have NOT yet installed recovery, this is because it was asking me to confirm that /dev/block/mmcblk0p22 is the correct something - I just don't know how to confirm this and do not want to cause an irreversable change. I would prefer to resolve with CWM as I am used to using that now.

So many thanks if someone can help me.

Key info:

build number: 5.14.61.2 CL275436 release keys

I am aware of an update to firmware 5.18 (recommended for AT&T users) but I am a UK, EE user and no updates have been pushed to me. So I don't want to upgrade this yet either. I would rather remain at 5.14, get the thing working than risk bricking it with firmware while it's not 100% happy.

CWM recovery 6.0.2.8

Images of useful info I hope + disk usage - (Unable to post an external link to Drop box as I'm new, please PM me for images.)

C:\Android>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 2.18.0000

(bootloader) version-baseband: 1.34a.32.45.21

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main:

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno:

(bootloader) imei:

(bootloader) product: evita

(bootloader) platform: HBOOT-8960

(bootloader) modelid: PJ8311000

(bootloader) cidnum: ORANG001

(bootloader) battery-status: good

(bootloader) battery-voltage: 4101mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-c20bff6f

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.135s