Today, I decided to install AOKP on my Droid X. This was my procedure:
started on EncounterICS X build 4
went into cwm5
made a nandroid
wiped data/cache
installed AOKP
When I tried to boot up, it showed the M logo for 15 seconds, then just showed a black screen. So I tried this:
used Linux ISO to flash Milestone X sbf
tried to install CWM with ROM Manager (didn't do anything)
installed D2 Bootstrap and flashed CWM 2.5
installed AOKP
The first time the phone booted up, it showed a black screen. I pulled the battery and tried again. Now, it shows the AOKP boot animation over and over. Every ten seconds or so, it freezes for maybe five seconds, then keeps going.
EDIT: I fixed it by wiping data.
Related
Hi,
I followed the huge guide to root Telus Desire HD, and clockwork mod latest version, then I flashed CM7 RC4, now im stuck in a reboot loop.
All I see is the spinning blue arrow around the android for 3-4 seconds then reboot.
if I pull out the battery and try again, I get HTC logo , then same spinning blue arrow (cyanogenmod bootup screen looks like)...
where to go from here?
okay I figured out the hold volume down to get to a menu.
trying this now:
http://forum.cyanogenmod.com/topic/16884-wont-boot-after-cm7-flash/
EDIT: Done. Fixed by wiping data, cache, and dalvik-cache
I originally was trying to flash CM7 using a SD bootable version of CWM 3.0.2.8 and it wouldn't boot at all. So, after a bit of searching, came to find out my refurbished Nook was one of the "new" ones with the partition change and was told that custom ROMs won't work on it yet.
I then got a CWM flashable 1.2 stock ROM and flashed it back to stock. Now, it won't boot past the N screen. I tried holding the power and N button to get into recovery to restore it, but that process freezes up half way through.
Next, I tried the 8 times boot interrupt (which is only 4 on my Nook btw) and it too freezes up part way through while "Clearing Data".
Any ideas on where to go next?
Nevermind, problem fixed. Whew, I went from having a Nook that wouldn't even power on this morning to a fully restored one.
Turns out I needed to have the power adapter plugged in while doing the 8 boot interrupt process.
Currently having an issue with my Droid R2D2 (rooted), I was installing a new battery mod for my phone, restarted the status bar and all worked out fine. I went to do a reboot to make sure it all worked out and BOOM, phone became stuck at Moto Logo for the past 20 mins when I tried to restart it.
I can't seem to get Bootloader to load up even with the phone plugged into the computer itself, but it will go into recovery mode after holding the X button on keyboard, but search key wont bring up any luck either.
I can't seem to find my back-ups either before I installed the battery logo, ROM Manager would back-up my stock R2D2 ROM but it wouldn't appear on the list of possible recoveries before the phone went into deep sleep.
Only thing that I've found to fix this is to just SBF_Flash back to stock and start over.
Hello everybody.
I am a Defy Red Lense user with a recently flashed PA 2.14 build (coming from 2.00 version of same ROM). At first 3-4 boots everything was ok, till I made some changes on phone config (namely enabling 16 bit transparency as recommended by it's maker, and then some small changes in Paranoid Android Settings) and asked me to reboot. Ok so I went to reboot and as usual, it booted me into bootmenu, and I chose "boot" and "2ndinit" as usual. After a odd bootloop (where the phone wouldn't go through the blue, then green LED sequence and would then reboot, show Moto logo boot animation, rinse and repeat, etc) that I ended by pressing vol - and entering, again, into bootmenu, I chose again boot and 2ndinit and then something really weird happened:
After almost half an hour i'm still stuck at the very ROM booting animation (the Paranoid Android one, no the Moto logo), just like the guys that tried that new kernel that were reporting 15+ min first boot times. As a clarification, my first boot with just flashed 2.14 took, at most, 5 minutes. And there is another odd vehaviour, concerning the PA boot animation: it gets randomly stuck for a few secs and continues as usual, with no looping from 0 just like the normal loopboot.
So here comes the questions:
- What is really happening? is it really booting or the phone is just stuck in ROM bootanimation? How long should I wait to consider shutting it down?
- Is there some way to get out of it/shutting it down without damaging the device? Can I just pull the battery off without bricking the device?
Looking fowardd for some theories behind this issue :good:
Well, seems like it was OK to unmount the battery while on ROM booting animation, since I haven't had mayor problems after doing so and rebooting. Now the phone works just fine.
Tho im still curious the reason behind this pseudo-bootloop. Thanks for reading anyways :good:
I tried (clean) flashing a droid concepts build over on droid-hive a little while ago and everything went ok when flashing. I tapped reboot system in twrp and the screen went black and didn't boot. I can't get it to boot consistently either into the os or into fastboot. It'll occasionally let me into recovery and I tried restoring a backup and also just rebooting from recovery and it won't boot at all. When it is plugged up, it'll show the charging icon when I tap the power button like it does when the screen is off. I've tried everything I can think of. Any help would be appreciated. Thanks.
Edit - I finally got it into fastboot and I flashed the stock google image. Its working now.
Sent from my Galaxy Nexus using Tapatalk 4 Beta