[HTC One X+] mrg209:
similar issue, yet to find a solution

Hi all,

I'm having a very similar issue to the one here. I have the HTC One X+ on AT&T. I had never rooted this phone. I got the OTA update in January, which seemed to go pretty smoothly. The phone was slow for a few days until I got all the apps updated and then was starting to be normal again. Every now and then it would hang and then I'd force restart and it would stick on the bootscreen until I restarted again. One day, however, it did this and then never exited the bootscreen. Got into the bootloader menu and did factory reset in hboot mode, which did nothing. Then I find out it wouldn't do anything because the settings of the phone were set to Fastboot and that needs to be unchecked for factory reset to work. But I can't get into the phone to change that, so I started looking through many many forums here at XDA and trying solutions to problems that were as close to mine as I could find. ...most people have this problem when first attempting the update or when putting on a custom rom, or using a different HTC phone.

So, I've learned quite a bit about flashing roms and the architecture of my phone, but not enough to fix this or to know where I may have may things worse. Here is a summary of what I attempted (all with battery >50% and HTC Sync has been installed on my computer--although the computer never recognizes the device and says driver install failed every phone reboot):

First was to get adb and fastboot and clear the cache

Then I ran the RUU: RUU_EVITARE_UL_JB_50_S_Cingular_US_2.15.502.1_Radio_2.21.5517.15_18.27.11.35L_release_341689_signed_0220

It claimed it updated my phone from 2.15.502 to 2.15.502 and then hung on the bootscreen. (it did CHANGE the bootscreen logo to a simple HTC)

Older RUUs return an error that they are not the right RUU for my phone.

Next, I attempted to directly flash the recovery_signed and boot.img from the zipped roms that were in the TEMP folder after initializing the RUU (according to one forum thread), but this method required a system.img to exist and it does not.

I flashed TWRP recovery (v2.6.3.0) and can access that just fine. The entire phone is wiped. There is no OS. I cannot mount the SD card.

Most recently, I attempted to sideload the zipped ROM from the RUU (http://xdaforums.com/showthread.php?t=2317986). It failed (unable to find partition size..unable to mount anything), so I used adb push to put the rom onto the SD card. Install from TWRP also failed. Unable to find/mount anything. That's where I am now.

*** UNLOCKED ***

EVITARE_UL PVT SHIP S-ON RL

HBOOT-1.73.0000

CPLD-None

MICROP-None

RADIO-SSD:2.21.5517.15

eMMC-bootmode: disabled

CPU-bootmode: disabled

HW Secure boot: enabled

MODEM TYPE : MDM9215M

Sep 30 2013, 17:16:15

(bootloader) version: 0.5a

(bootloader) version-bootloader: 1.73.0000

(bootloader) version-baseband: SSD:2.21.5517.15

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 2.15.502.1

(bootloader) serialno: ***********

(bootloader) imei: ***************

(bootloader) product: evitare_ul

(bootloader) platform: HBOOT-T30S

(bootloader) modelid: PM6310000

(bootloader) cidnum: CWS__001

(bootloader) battery-status: good

(bootloader) battery-voltage: 4160mV

(bootloader) devpower: 93

(bootloader) partition-layout: None

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: None

(bootloader) hbootpreupdate: 2

(bootloader) gencheckpt: 0

Thanks.