As the title says I can't seem to flash any custom roms. I always get stuck at the boot animation. I have unlocked boot loader, installed twrp recovery, and rooted. I'm pretty sure I follow the few custom roms installation instructions correctly. but I always get stuck on the boot screen animation. What am i doing wrong? this is incredibly frustrating This is my first nexus device but not my first time installing custom roms on android. I have the wifi version nexus 9 on latest stock android as of this time.
phillip zanders said:
As the title says I can't seem to flash any custom roms. I always get stuck at the boot animation. I have unlocked boot loader, installed twrp recovery, and rooted. I'm pretty sure I follow the few custom roms installation instructions correctly. but I always get stuck on the boot screen animation. What am i doing wrong? this is incredibly frustrating This is my first nexus device but not my first time installing custom roms on android. I have the wifi version nexus 9 on latest stock android as of this time.
Click to expand...
Click to collapse
Whenever that happens to me I let it sit on boot animation for a couple minutes, then hold power until it reboots again. It usually boots system then.
Thanks for responding ill give that a try after.
Related
Whenever I try install a custom rom, my streak never gets past the loading screen after the dell logo. I've tried streakdroid and longhorn both get stuck on a loading screen. How can I get my streak running a custom rom? :/ I've followed all the instructions and I'm not sure what I'm doing wrong.
of course first boot usually takes time to initialized itself... subsequent boot usually only take around 30 - 45 seconds only...
Yes I am aware first boot takes longer, but as I said in my first post, it freezes. It starts the loading process again.
It's seems you flash a custom rom that need mod kernel. To flash mod kernel you have to unlock boot loader.
It happen to me once, stuck at SONY logo.
Try to flash with stock rom, it will be fine (i hope).
frisman said:
It's seems you flash a custom rom that need mod kernel. To flash mod kernel you have to unlock boot loader.
It happen to me once, stuck at SONY logo.
Try to flash with stock rom, it will be fine (i hope).
Click to expand...
Click to collapse
All of the custom ROMs have the correct Kernels built into the ROM.
Did you perforn BOTH factory resets after flashing?
tenorntex said:
All of the custom ROMs have the correct Kernels built into the ROM.
Did you perforn BOTH factory resets after flashing?
Click to expand...
Click to collapse
What other factory reset it there besides the one in clockwork recovery? And how do I do it?
the menu in white text...
1. factory reset
2. software upgrade via update.pkg on sd card
3. screen calibration
4. power off
select 1
though when you do that, all data would be erased....
Beauie said:
What other factory reset it there besides the one in clockwork recovery? And how do I do it?
Click to expand...
Click to collapse
That is your first mistake. You should be using streakmod.
Sent using Longhorn 2.8, ICS Longhorn 1.4.2, and Longhorn Betas
Ok so I searched the forums before this just to let you know.
I wasn't thinking and the wrong kernel got installed as the title says. So, I got into a bootloop (expected). It hits the fan after my next step :'(
I go to bootloader, then to recovery, start up TWRP, then screen goes blank and goes back to the htc bootscreen.
The odd thing is, it now has that disclaimer on the bottom for normal boot sequence.
I have attempted flashing other recoveries, erasing my cache, fastbooting roms, and fastbooting kernels. I assume my choices are limited with S-On since most of the fastboot commands return "remote:not allowed".
Do I have to wait for a RUU?
Thank you for your time in advance
UPDATE:
Finally got Clockworkmod to boot (after reflashing it at least 5 times), sideloaded a ROM, and presto it seems to be alive. Still have that disclaimer on the bootscreen, oh well :/
IF YOU FOUND THIS BY SEARCHING
1. Fast boot flash recovery "recovery file" (I used clockwork non touch)
2. Fast boot erase cache MUST!!!
3. Boot recovery
4. Sideload Rom via adb
seamarshall said:
Finally got Clockworkmod to boot (after reflashing it at least 5 times), sideloaded a ROM, and presto it seems to be alive. Still have that disclaimer on the bootscreen, oh well :/
Click to expand...
Click to collapse
Glad to hear you got it working again. Anytime you install a custom ROM though, you will see the disclaimer on the bootscreen. It isn't a big deal software wise though, it just looks ugly. I'd consider that a minor inconvenience for using a better ROM without the bloat.
So I was just in a boot loop on my stock ROM that was rooted and I was trying to install a custom ROM but got stuck in a boot loop. So I followed a bunch of things and ended up getting stuck at my carrier logo loading screen. So I found another thing that said to go into recovery (which I did using clockworkmod) and install a new custom ROM (which I did, and that ROM being cyanogenmod). So I installed this new ROM and now I'm back into the boot loop but this time it loops through the cyanogenmod loading screen, the HTC turning on screen, and a plain black off screen. HELP MEE!!!
I suggest using 4ext recovery
If you want any other Rom than stock-based, you need to lower your hboot to 1.5 or lower
You can only change hboot if you are s off
If you are s on, install 4ext recovery and make sure smartflash is enabled.
you need to be sure and wipe all partitions except your sd card.
If it still bootloops, you need to get the boot.IMG from the Rom, and flash it in fastboot USB mode.
Sent from my PG86100 using xda app-developers app
Just got my S4 in the mail today and the first thing I did was go looking for a Rom.
I rooted with towelroot and then installed Safestrap. My first flash was Slimkat but all it did was boot to a black screen. I went back to recovery and did a factory reset. Still black screen.
I re-booted to recovery and installed Google Play Edition. That got stuck on the boot logo for about 5 minutes. Went back to recovery and did a factory resit, still stuck on boot logo.
Next I installed Hyperdrive. stuck in bootloop for 15 minutes before I gave up and Odin'ed back to stock. any suggestion why I'm failing at installing custom roms?
swing4thefence said:
Just got my S4 in the mail today and the first thing I did was go looking for a Rom.
I rooted with towelroot and then installed Safestrap. My first flash was Slimkat but all it did was boot to a black screen. I went back to recovery and did a factory reset. Still black screen.
I re-booted to recovery and installed Google Play Edition. That got stuck on the boot logo for about 5 minutes. Went back to recovery and did a factory resit, still stuck on boot logo.
Next I installed Hyperdrive. stuck in bootloop for 15 minutes before I gave up and Odin'ed back to stock. any suggestion why I'm failing at installing custom roms?
Click to expand...
Click to collapse
Are you installing to the stock slot?
Yes. I have gotten the impression that you can ONLY install to the stock slot.
swing4thefence said:
Just got my S4 in the mail today and the first thing I did was go looking for a Rom.
I rooted with towelroot and then installed Safestrap. My first flash was Slimkat but all it did was boot to a black screen. I went back to recovery and did a factory reset. Still black screen.
I re-booted to recovery and installed Google Play Edition. That got stuck on the boot logo for about 5 minutes. Went back to recovery and did a factory resit, still stuck on boot logo.
Next I installed Hyperdrive. stuck in bootloop for 15 minutes before I gave up and Odin'ed back to stock. any suggestion why I'm failing at installing custom roms?
Click to expand...
Click to collapse
Assuming you are using Safestrap correctly.... check your downloads.
Also, slimkat is not compatible with your phone unless you are on mdk which I doubt. There is a process by which you can get the GPE ROM to run on our device if you aren't on mdk but I suspect all you did was flash the zip. We can't use AOSP Roms and if your going by the list of Roms in this thread http://forum.xda-developers.com/showthread.php?t=2297370 you will find most of them to be incompatible. There is no reason that Hyperdrive would get stuck in a bootloop unless there were something wrong with the install or your download.
liljoe727 said:
Assuming you are using Safestrap correctly.... check your downloads.
Also, slimkat is not compatible with your phone unless you are on mdk which I doubt. There is a process by which you can get the GPE ROM to run on our device if you aren't on mdk but I suspect all you did was flash the zip. We can't use AOSP Roms and if your going by the list of Roms in this thread http://forum.xda-developers.com/showthread.php?t=2297370 you will find most of them to be incompatible. There is no reason that Hyperdrive would get stuck in a bootloop unless there were something wrong with the install or your download.
Click to expand...
Click to collapse
Your right. I "Just flashed" I Odined back to stock and tried again, this time following the isntructions for flashing Hyperdrive and it's working fine. Imagine that! All i had to do was read the instructions.
swing4thefence said:
Your right. I "Just flashed" I Odined back to stock and tried again, this time following the isntructions for flashing Hyperdrive and it's working fine. Imagine that! All i had to do was read the instructions.
Click to expand...
Click to collapse
That usually helps ; )
I am on Aosp 6.0.1 all of a sudden it rebooted and stuck at boot animation. no matter what i do it will not get past that thing.I have this problem from long time in many roms after using 10-15 days this problem arises.
flash Fastboot Rom
You may have to do a reflash of the ROM, i'm assuming you have a custom recovery installed? You can try flashing over top of your existing installation.
goofball2k said:
You may have to do a reflash of the ROM, i'm assuming you have a custom recovery installed? You can try flashing over top of your existing installation.
Click to expand...
Click to collapse
Happened with me. Try booting in twrp and reboot to system