[HTC One X] frontinsomething:
Hi Guys,

I have a big problem! I forgot to flash the boot.img of "Jelly Bam 7.2.1" - it all ended in total chaos. I will try to describe everything I did, feel free to ask any further on points that seem to be more relevant than I thought.

To let you know: I have knowledge of flashing / custom roms and all that good jazz in general (with other phones before), but I am a total noob concerning all the One X specific stuff...

1.) rooted my One X. No problems so far, stock rom working fine after doing so, HBoot says "UNLOCKED" at the top, so no problems here.

2.) downloaded the custom ROM (JellyBam, endeavoru, 7.2.1), checked MD5, so no problems with the download - copied it to my phone

3.) went into recovery without fastboot, just the way via hboot and did the following in that order: "wipe data/factory reset", "wipe cache partition", formatted "/cache", formatted "/system", formatted "/data", "wipe dalvik cache", flashed the zip "jelly-bam-blabla.zip"

4.) tried to boot, which obviously did not work, because I forgot flashing the boot.img.... but in concrete: the phone first showed the normal "HTC"-Screen, then the JellyBam loading screen came on the screen, then the "Android Welcome Screen" showed up. after 0,5 seconds a pop-up came up saying "Unfortunately, System UI has stopped." and some 0,5 seconds after another pop-up places itself right over the other one. it says "Unfortunately, the process com.android.phone has stopped."... I tried to hit "OK" but it always came up again within 0,5 seconds or shorter.

5.) I went into hboot from there, because my first idea was, that the problem could have been me having forgotten the "fix permissions" after flashing the rom... so i did all the cache / formatting stuff again, flashed the zip again and then fixed permissions.

6.) tried to boot, exactly the same situation as described in "4"

7.) the boot.img-stuff came in my mind. slapped myself in the face several times. the "you should always fastboot flash your recovery if you want to flash anything on your phone"-advise also came in my mind. hurt my face for some more seconds.

8.) went into hboot again, then "fastboot", connected to my MBP and firstly tried to fastboot flash cwm-recovery. but the terminal said that my HOX is too low on battery life...

9.) the part I actually can't remember correctly. tried different advises on how to load the battery without having a rom up and running (from xda devs mainly) - which all did not work but somehow resulted in my HOX not even letting me boot up normally anymore. a (re)boot just kicks me directly into cwm recovery.

10) my battery went totally empty. and now the scary part i really do not understand begins: I connected my HOX via the usb cable to a power adapter. the orange light first started blinking, then it stood on for about 3 hours - I did not touch it. after these about 3 hours the device automatically booted into cwm recovery. i went into hboot which resulted in the normal error messages while connected via usb to a power adapter or a computer, so i unplugged the cable and rebooted recovery. again went in hboot, which now tells me I am too low on battery to flash anything. Because the orange light is only on in cwm recovery I thought that the phone charges there (I also read that, but the people said it would be veeery slow), so I tried to keep it in recovery. the problem is: it automatically shuts down after 20-30 minutes... I tried to avoid that as long as possible, always just hitting volume down once every 20 minutes - but even after doing that for about 6 hours, hboot still told me my battery is too low...

I really do not know what to do. I am never able to stay at home for longer than these 6 hours, so I do not know how I might get the battery high enough in order to flash the boot img or the zip in cwm again...

Please help me you genius people out there!

P.S.: The nerd video at registration is nicely done. I really like it. And I hope I did not overlook a thread that could solve my problem...