Database Users

Stuck on loading screen?

hi guys
yesterday i flashed my radio + rom on my DHD for the first time (revolution 3.0) , everything went smooth - until this morning... noticed a 10 +- sec delay on each action i do on the phone, was really slow - so i decided to restart it (power button -> restart), since then - it won't get past the loading screen where it says "DHD" in a green font, and "quietly brilliant" under it - i've tried removing the battery but no luck - it's just stuck on that screen.
i can get into the bootloader menu but nothing else.
any help?
thank you

Try to restore an older build via CWM and flash your desired ROM again.
Did you wipe correctly? Coming from an older build and just updating to a newer one a full wipe is mostly not necessary but advised if any problems occure.
I allways wipe cache and dalvik before updating.
Rgds

[Q] Cyanogen Mod - Help - Zte Blade stuck at Green Andoid Image at startup-Won't Boot

Hi, first time modding and I've come up with a problem.
Baisically what's wrong now:
Phone is stuck at large green android logo when I turn on the phone.
Can't boot into Cyanogen
Can't get Clockworkmod to open
Phone only turns off with a battery pull
How I got the phone to this point:
Followed the instructions at wiki.cyanogen
(Backed up with titanium backup pro)
The first time I installed the mod I got stuck in a boot loop. But I fixed this by deleting data and cache in Clockworkmod and going through the steps again.
The phone and it's new mod seemed to work. I installed the google apps.zip, via CLockwork, still fine.
Then I tried to reinstall apps from Titainium Backup.
Some of these went well, but I started to get 'com.google.process.gapps' stopped working force close notifications.
I rebooted to see if that would make them stop.
But I got stuck in a boot loop of the Cyanogen animated logo, where it would boot, show me the unlock screen, I would unlock it, get another 'com.google.process.gapps' message and the phone would then freeze and reboot. The sequence then continued.
I tried battery pulling and tried to boot into Clockwork by holding down Menu Up and Power. But not after a while it just shows the green android logo. HELP.

I didn't read all!
So...
this problem is easy fix!
I spent 3 Hours with my blade to get my Blade II to work!
you have same problem which some other has posted somewhere here...
search on google or on Modaco: ZTE Blade TPT GEN1 or GEN2...
follow instructions!
now Blade II needs to work!

http://android.modaco.com/topic/343587-guide-de-bricking-a-zte-blade/

Dx massive bootloop problem

So my phone is stuck in a boot loop. It was rooted and running MIUI but wasn't booting into CWM recovery. I decided to SBF to .602 and start from scratch. Ever since I SBF'd the DX is stuck looping the Droid Eye logo animation.
I've tried two GB and two Froyo kernels but no matter what I use it is still looping the logo animation.
Anyone know the cause of this loop and anything I can do to fix it?

I'd do a fresh SBF just to be safe and then reboot into stock recovery by holding the home button while you turn on the phone and wipe data and cache from there. Afterwards, reboot and everything should be fixed.

I've been SBFing! I've tried SBFing to two GB kernels, and two Froyo kernels. No matter which kernel I've SBF'd the phone won't get past looping the logo animation.

choonami said:
I've been SBFing! I've tried SBFing to two GB kernels, and two Froyo kernels. No matter which kernel I've SBF'd the phone won't get past looping the logo animation.
Click to expand...
Click to collapse
Enter recovery by holding home and power, then press both volume buttons and continue to wipe data/factory reset.
Sent from my DROIDX using XDA App

Wow... Something so simple has stopped my phone from working all day! I've tried everything BUT regular data wipe.
Thanks for the help.

[Q] Round And Round The AOKP Goes...

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.

[Q] Problem: Phone stuck at ROM Booting animation.

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: