[HTC One S] mortek:
Hey all,

I've been trying to cope with a strange situation:

I've had my unbranded international S-on S4 HOS for about 6 months now - stock & rooted.

Everything was fine, except for some random reboots now and then - which didn't really bother me since they were a rare occurrence.

About two weeks ago, at the end of a long day, my battery was drained and my phone was powered off, so, due to the lack of a normal car charger, I plugged it into the car stereo's usb host for it to charge - which is something I have done several times in the past.

After I let it charge for a couple of minutes before I hit the power button to get it booted, it went into a boot loop where it couldn't get past the first splash screen with the green HTC logo.

I was able to get into bootloader but not in recovery, so I did a factory reset from there. Again it went into the same boot loop. I then flashed a custom recovery using the All-in-One Toolkit only to discover that I have rendered the sdcard unmountable and therefore unreadable.

After reading several relevant threads and posts here, I relocked the bootloader and used an executable RUU to get the phone back to stock.

It booted up normally and everything was working fine again!

Until last night. Again my battery drained, and again it got into the same boot loop - although this time I used the normal wall charger and left it to charge for 30 minutes before I hit the power button.

Unfortunately, since this time around I don't have access to a Windows machine in order to do the RUU procedure, I flashed the latest CM 10.1 nightly through the latest TWRP recovery after flashing the latest AOSP-required firmware and flashing the boot.img - all that using a Mac.

It again got into a boot loop and after several reboots it finally booted!

Though, the ROM's performance was extremely sluggy so I decided to go into recovery to wipe and reflash in order to fix it and also in order to check if it would get into a bootloop again by just rebooting it.

Not only did it get into a bootloop but I was not able to get in the recovery at all!

I then successfully repushed the recovery through fastboot, wiped and reflashed CM 10.1 nightly, it once again got in a bootloop and it once again booted after several reboots!

Although, I wasn't satisfied with this temporary solution - knowing this would just last until the next time my phone reboots - and I decided to try a different firmware/kernel/ROM combo so I tried to reboot into recovery only to get into that bootloop again - without being able to go into recovery!

I reflashed the TWRP 2.3.3 recovery and flashed the ViperOneS 2.1 ROM. It once again got into a bootloop but this time it never managed to boot. I tried several recovery versions but I never got it to boot. I then tried the Android_Sense_Best_Stock_v3.0_By_BehradGH ROM combined with the ElementalX-S-4.3 kernel but this one never made it past the first HTC splash screen.

I am now stuck with a bricked phone and no access to the RUU - temporary - solution.

What do you reckon? Has anyone dealt with such a situation before? Could it be a bad NAND? Any thoughts?

Sorry for the long post but I wanted to give as much info as possible.

P.S. I've always flashed the corresponding boot.img after and/or before every ROM.