Database Info

Stuck at boot animation

Regardless of which ROM I flash
I never get past the boot animation, whether it is AOKP or Jelly Bam or anything
I flashed boot image
installed from TWRP
It installs fine
...never gets past the loading screen.

ccamwilkins said:
---i flash boot after i installed ROM, and everything works now---
Regardless of which ROM I flash
I never get past the boot animation, whether it is AOKP or Jelly Bam or anything
I flashed boot image
installed from TWRP
It installs fine
...never gets past the loading screen.
Click to expand...
Click to collapse
So you used fastboot to flash the boot.img prior to flashing each ROM? And you used the boot.img that came with the particular ROM you are flashing?

Yes, from the cmd prompt i would type fastboot flash boot boot.img (all from correct folder)
I even saw progress that it's done in the HTC FASTBOOT screen.
And to get the correct boot.img, i would extract the .zip of the rom and use that boot.img
i FINALLY got it past boot animation by flashbooting boot.img AFTER i installed the ROM
But now, THREE different ROMs don't function correctly. (the home button doesn't work, and Android Keyboard AOSP messes up every 5 seconds)

ccamwilkins said:
Yes, from the cmd prompt i would type fastboot flash boot boot.img (all from correct folder)
I even saw progress that it's done in the HTC FASTBOOT screen.
And to get the correct boot.img, i would extract the .zip of the rom and use that boot.img
i FINALLY got it past boot animation by flashbooting boot.img AFTER i installed the ROM
But now, THREE different ROMs don't function correctly. (the home button doesn't work, and Android Keyboard AOSP messes up every 5 seconds)
Click to expand...
Click to collapse
What ROM are you using?

trying to flash: Evita Vanilla RootBox
http://forum.xda-developers.com/showthread.php?t=1988554

I'm really fine with any JB rom if you have any other suggestions.
I just wanted a smooth one.

ccamwilkins said:
I'm really fine with any JB rom if you have any other suggestions.
I just wanted a smooth one.
Click to expand...
Click to collapse
I was actually going to try that one out but currently I am using CM10. Btw you don't have to unzip the folder to get the boot img out. You can just open it, copy, and paste it in your adb folder.
As for your issues, make sure in TWRP you wipe Cache, Dalvik, System, and Factory Reset. You have to do all 4. Do it two or three times to make sure. Also, after you flash, wipe cache and dalvik again.

Butters619 said:
I was actually going to try that one out but currently I am using CM10. Btw you don't have to unzip the folder to get the boot img out. You can just open it, copy, and paste it in your adb folder.
As for your issues, make sure in TWRP you wipe Cache, Dalvik, System, and Factory Reset. You have to do all 4. Do it two or three times to make sure. Also, after you flash, wipe cache and dalvik again.
Click to expand...
Click to collapse
My opinion is Dirty Rom is the best AOSP ROM at the moment, Very stable, never a hiccup, and speed with Rohan's

[Q] Stuck at boot animation

So today I both flashed King Kang and tried to load a custom boot animation. I rebooted multiple times between the two, and once after I loaded the custom animation. The second time I booted with the custom animation, it gets to the animation and then just sits there with the animation.
TL;DR: Worked when I flashed the rom, and once after new boot animation, didn't work after second reboot.
EDIT: Screw it, I just factory reset.

If your hboot version is 1.14 you have to flash the boot.img from the ROM before you reboot.
Fastboot flash boot boot.img
Sent from my One X using xda app-developers app

Sensation dead?

Hey guys!
My Sensation recently died on me, or should I say it won't boot ANY ROM available here. It just enters bootloop and cuts off on first glimpse of the boot animation (or sometimes after fresh ext4 format it just hangs on the splash screen - white bg with HTC). I have installed 4EXT recovery because I thought it was due to CWM Recovery. I had ViperS installed andd I got occasional random reboots followed by bootloops. After pulling the battery out the ROM booted fine until today. Now I can't boot any ROM, flashing goes OK, I tried restoring my factory ROM, but that just bootloops and cuts off at the beats logo, too.
What to do? Is there any fix?

5ageman said:
Hey guys!
My Sensation recently died on me, or should I say it won't boot ANY ROM available here. It just enters bootloop and cuts off on first glimpse of the boot animation (or sometimes after fresh ext4 format it just hangs on the splash screen - white bg with HTC). I have installed 4EXT recovery because I thought it was due to CWM Recovery. I had ViperS installed andd I got occasional random reboots followed by bootloops. After pulling the battery out the ROM booted fine until today. Now I can't boot any ROM, flashing goes OK, I tried restoring my factory ROM, but that just bootloops and cuts off at the beats logo, too.
What to do? Is there any fix?
Click to expand...
Click to collapse
S-ON or S-OFF?

rzr86 said:
S-ON or S-OFF?
Click to expand...
Click to collapse
It's all in my sig, I only have 1.27 now. S-OFF, rooted, unlocked. Flashed many ROMs and they worked fine, even now every ROM installs without any error but they all get stuck in bootloop

5ageman said:
It's all in my sig, I only have 1.27 now. S-OFF, rooted, unlocked. Flashed many ROMs and they worked fine, even now every ROM installs without any error but they all get stuck in bootloop
Click to expand...
Click to collapse
i am really blind
ok.i assume you have now 4ext
if yes then:
format all partitons except sdcard
flash the rom
otherwise flash the boot.img of the rom manually
see here how
http://forum.xda-developers.com/showthread.php?t=1631861 (only extra 1 step)

rzr86 said:
i am really blind
ok.i assume you have now 4ext
if yes then:
format all partitons except sdcard
flash the rom
otherwise flash the boot.img of the rom manually
see here how
http://forum.xda-developers.com/showthread.php?t=1631861 (only extra 1 step)
Click to expand...
Click to collapse
It happens
I tried both, 4EXT wipe and flashing the boot.img, but that didn't help
Now, this is weird! I thought after countless tries to try again, just before I give up, and try restoring my CWMR backup of the stock factory ROM I had and after one bootloop the phone started booting and now works normally :silly: even after couple of restarts.
Thanks for trying to help, but now I'm afraid to flash anything else on it. Could it be my hardware is not right?

Really frustrated, phone keeps booting to recovery after failing to boot to rom

Hi all, I've been trying for the past 8 hours(you can imagine how frustrated i am right now) to install HatkaXL(http://forum.xda-developers.com/showthread.php?t=2075783) for so long now and I have literally no idea where to go. I was only just trying to switch from cleanrom to Hatka. And I've ended up with absolutely no progress since 8 hours have passed. Actually, i've probably lost progress because i accidentally wiped my data without backing up. Here's what i've done so far:
i'm under AT&T, hboot-1.14, any other info i'll be glad to share. it's rooted and currently unlocked of course.
1. Used fastboot flash boot boot.img to no avail
2. Re-locked bootloader, ran an RUU(i made sure it was compatible), unlocked it and tried to flash HatkaXL froma fresh start
3. Wiped data, cache, etc. then flashed the rom(which still didnt work)
4. flashed TWRP, rebooted, went into TWRP, wiped data, cache, etc. and then flashed HatkaXL
What the problem is that my one x won't go past the HTC screen with all that red developmental font. It'll boot and then go to the screen, stay there for about 10 seconds and then turn off. Then it'll start up again 10 seconds later to boot back to TWRP.
At one point, i encountered a boot loop where it actually went past the red developmental font screen and to the HTCtm Beats Audio and then it just restarted from there. However, now that issue disappeared and it's just booting to recovery after shutting down.
Now that's where I was thinking that maybe since it's booting directly to TWRP that would mean that I would have to go into cmd and 'fastboot flash boot boot.img' right? I did exactly that, one, twice, three times, even with fastboot erase cache.
i can't even remeber everything i did because i'm so tired since i've been up through the night reading throug threads, trying to fix this damn thing.
I would really really appreciate it if anyone could help me out here because i've never been this lost when it came to technology lol.

It sounds like you were on the right track, I am lost why it failed for you?
Can you install cleanrom again? eg is it just HatkaXl that is not working? Perhaps your download is bad or the ROM is simply broken and you need to report it to the dev?
When you were flashing the boot.img did it say success? Did you triple check you are extracting the correct boot.img to the correct folder?
Just to be clear to install ROM's I often do:
1)wipe data and system
2)install ROM
3)fastboot flash boot boot.img

twistedddx said:
It sounds like you were on the right track, I am lost why it failed for you?
Can you install cleanrom again? eg is it just HatkaXl that is not working? Perhaps your download is bad or the ROM is simply broken and you need to report it to the dev?
When you were flashing the boot.img did it say success? Did you triple check you are extracting the correct boot.img to the correct folder?
Just to be clear to install ROM's I often do:
1)wipe data and system
2)install ROM
3)fastboot flash boot boot.img
Click to expand...
Click to collapse
Thanks for the response. Yep, every time i flash the boot.img, it's always a success. i also mae sure it's the correct one.
sending 'boot' (6156 KB)...
OKAY [ 0.933s]
writing 'boot'...
OKAY [ 1.475s]
finished. total time: 2.413s
Click to expand...
Click to collapse
I just tried to install cleanrom 5.1 again and it's not working either. Actually, it's stuck at the red developmental font screen this time so atleast it's not immediately rebooting to go to TWRP.
UPDATE: It's working! CleanROM! Thank you so much man! I'll be back to ask you another question. Gotta go real quick.

Correct me if I'm wrong but clean Rom 5.1 flashes the boot img for you I didn't see you flashing the boot.img the other times successfully so yes it won't get past that HTC screen

a box of kittens said:
Correct me if I'm wrong but clean Rom 5.1 flashes the boot img for you I didn't see you flashing the boot.img the other times successfully so yes it won't get past that HTC screen
Click to expand...
Click to collapse
I also noticed this. Op, a few things to remember when flashing boot.img.
The boot.img needs to be extracted from the rom you are flashing.
The phone must be in bootloader, plugged in to pc and in fastboot usb mode. (the phone will say fastboot usb.
The boot.img must be in the folder with the fast boot and adb programs.
I have more than just a feeling you were doing something wrong
Sent from my One X using xda app-developers app

Thanks for the responses guys, you guys are saving me lots of stress and time.
a box of kittens said:
Correct me if I'm wrong but clean Rom 5.1 flashes the boot img for you I didn't see you flashing the boot.img the other times successfully so yes it won't get past that HTC screen
Click to expand...
Click to collapse
You are correct that clean rom 5.1 flashes it for you, which is through its AROMA installer. However, HatkaXL also uses the AROMA installer, and there's a line in the installation screen where it says "flashing boot.img." - both ROMs have that line. Interestingly, it worked when I followed twistedddx's order so I'm going to try that again.
exad said:
I also noticed this. Op, a few things to remember when flashing boot.img.
The boot.img needs to be extracted from the rom you are flashing.
The phone must be in bootloader, plugged in to pc and in fastboot usb mode. (the phone will say fastboot usb.
The boot.img must be in the folder with the fast boot and adb programs.
I have more than just a feeling you were doing something wrong
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Yup, I have those in the same folder correctly. I always extract the boot.img from the rom zip into the folder with both fastboot and adb(how else would I able to have fastbooted in the first place?), always made sure the phone was in bootloader, plugged in, and in fastboot usb.
edit: I wiped, then installed hatkaXL, then fastboot flash boot boot.img, and now it starts, it gets past the red developmental screen, INTO the HTC Onetm beats audio screen, turns off and then restarts again through the whole process. it's jst looping now.
edit2: Flashed ViperXL, that's working. I guess HatkaXL just isn't for my phone.. sigh. I hope this thread helps anyone else.

devfrost said:
Thanks for the responses guys, you guys are saving me lots of stress and time.
You are correct that clean rom 5.1 flashes it for you, which is through its AROMA installer. However, HatkaXL also uses the AROMA installer, and there's a line in the installation screen where it says "flashing boot.img." - both ROMs have that line. Interestingly, it worked when I followed twistedddx's order so I'm going to try that again.
Yup, I have those in the same folder correctly. I always extract the boot.img from the rom zip into the folder with both fastboot and adb(how else would I able to have fastbooted in the first place?), always made sure the phone was in bootloader, plugged in, and in fastboot usb.
edit: I wiped, then installed hatkaXL, then fastboot flash boot boot.img, and now it starts, it gets past the red developmental screen, INTO the HTC Onetm beats audio screen, turns off and then restarts again through the whole process. it's jst looping now.
edit2: Flashed ViperXL, that's working. I guess HatkaXL just isn't for my phone.. sigh. I hope this thread helps anyone else.
Click to expand...
Click to collapse
Could be a kernel issue.. Try flashing stock kernel after flashing rom?... That's all I can think of. Also, I don't know if you do but I always wipe cache, dalvik, system, and then factory reset in twrp and I've never had any issues with any roms.
Sent from my One X using xda app-developers app

[Q] Weird Problem. Only one rom boots.

Hi Guys,
Well my pico is stuck in the weirdest issue. It only and only boots up when i flash miui rom. On every other rom, i get boot loops or just stuck at boot screen.
I've tried cwm, twrp and currently am on Philz recovery. Nothing seems to work.
Have tried flashing the stock rom (goes in boot loop), CM 10 (stuck at boot screen, never-ending circle cyanogenmod), revolution and the sense 4 roms. (all stuck at boot screen)
I have tried with ext3 and ext4 partitions. ALso tried without partitions. Wierdly only and only miui rom boots up. I am trying the latest version of miui and its unusable. Very buggy atleast on my pico.
Now if it boots in miui why does it not boot other roms. I always do a complete wipe before each install.
Also, i know the RUU can be used. I have just one query, if i lock the bootloader with cmd "fastboot oem lock", can i also unlock it in the same manner?
Kindly help stuck on pico since weeks.

Pratzgh1 said:
Hi Guys,
Well my pico is stuck in the weirdest issue. It only and only boots up when i flash miui rom. On every other rom, i get boot loops or just stuck at boot screen.
I've tried cwm, twrp and currently am on Philz recovery. Nothing seems to work.
Have tried flashing the stock rom (goes in boot loop), CM 10 (stuck at boot screen, never-ending circle cyanogenmod), revolution and the sense 4 roms. (all stuck at boot screen)
I have tried with ext3 and ext4 partitions. ALso tried without partitions. Wierdly only and only miui rom boots up. I am trying the latest version of miui and its unusable. Very buggy atleast on my pico.
Now if it boots in miui why does it not boot other roms. I always do a complete wipe before each install.
Also, i know the RUU can be used. I have just one query, if i lock the bootloader with cmd "fastboot oem lock", can i also unlock it in the same manner?
Kindly help stuck on pico since weeks.
Click to expand...
Click to collapse
Try using superwipe to wipe the partitions and also try downloading any other ROM except those you have tried or latest builds of that as well, maybe that could help.
Talking about RUU, don't install that unless you know what you're doing. "fastboot oem lock" locks your bootloader and if you have rooted your phone(That's obvious ) then you might know that there is a different command for unlocking the bootloader that works on fastboot !! :good:

vaibhav121 said:
Try using superwipe to wipe the partitions and also try downloading any other ROM except those you have tried or latest builds of that as well, maybe that could help.
Talking about RUU, don't install that unless you know what you're doing. "fastboot oem lock" locks your bootloader and if you have rooted your phone(That's obvious ) then you might know that there is a different command for unlocking the bootloader that works on fastboot !! :good:
Click to expand...
Click to collapse
Hey Vaibhav. Thanks for the reply. I'll download and check other roms. I have used the super wipe before installing all the roms. Will update soon regarding the same. Even tried various SD cards, still same issue mann. Donno what's wrong exactly!

Pratzgh1 said:
Hey Vaibhav. Thanks for the reply. I'll download and check other roms. I have used the super wipe before installing all the roms. Will update soon regarding the same. Even tried various SD cards, still same issue mann. Donno what's wrong exactly!
Click to expand...
Click to collapse
Then it's the burnt NAND issue.