It just hangs on the Google screen with an unlock icon.
What now?
edit:
found this post. Following the steps.
http://forum.xda-developers.com/showthread.php?t=1773179
Related
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/
My N10 won't get past the lock screen. When I try to unlock the screen turns black and returns to the lock screen. I have tried rebooting and tried opening to Google Now or settings with no success. I am running rooted stock Android and haven't flashed anything in over a month. Any ideas?
nickrich1418 said:
My N10 won't get past the lock screen. When I try to unlock the screen turns black and returns to the lock screen. I have tried rebooting and tried opening to Google Now or settings with no success. I am running rooted stock Android and haven't flashed anything in over a month. Any ideas?
Click to expand...
Click to collapse
I fixed it. I cleared cache and fixed permissions in TWRP and it was good as new. I'm not sure what happend.
I am stuck in an installation loop that started while updating to KitKat.
I was happy with my LG G2 (T-mobile, D801G), but wanted to use root apps. So, I rooted and installed TWRP, but did not flash a custom rom.
Tuesday when I woke up there was a message saying I could download KitKat. After installing my last system update I lost root, so just had to unroot and re-root – took me about 15 minutes. So, I decided to go ahead and install KitKat.
It downloaded and began to install, but got stuck in a loop. The LG logo flashes for 5 seconds, the little droid pops up with his stomach spinning and the message “Installing system updates” but shows for only about ½-second. Then the screen goes black for 2 seconds and it starts again.
I can get it into the factory reset screen, but when I say yes-yes, it puts up the message :
Error: Boot certification verify
341120
341170
341220 Secure booting error!
341270 Cause: boot certification verify
341320
341370
(the nunbers are different each time, but always 6 numbers in increments of 50)
Then it sits in a black, but not quite off screen until I hold down the power button to turn it off. When I turn it back on, it shows the logo, then the droid showing the message ‘Erasing…’ for a full second, then switches to the ½-second ‘installing system updates’ loop.
It will go into download mode. When I connect it to the LG flash tool ‘Up Test’ it says all firmware is up-to-date.
I tried this: http://forum.xda-developers.com/showthread.php?t=2582142 but I couldn’t get Ubuntu 12.04 to install gdisk. Then I noticed that
ls /dev/sd*
returned the same values whether my phone was plugged in in download mode or unplugged completely. The values were
/dev/sda, /dev/sda1, /dev/sda2, /dev/sda3, /dev/sda4.
I tried the next step anyway
gdisk -l /dev/sdb
and got the error saying gdisk was not found, but I could install it with… etc. I tried to install it, but it wouldn’t work.
This is the second phone I’ve rooted – I had my HTC Sensation rooted for years, and flashed many ROMs. I hadn’t played much with the G2 because I liked it just the way it was – but had to have some rooted apps. I also have an HP Touchpad running Cyanogenmod. My experience with Linux is limited. So I’m just one step up from a noob.
Any advice would be appreciated! I bought a go phone so that I can take my time and fix my G2 right. :-/
So I was running CWM (Philz) I believe, and I had been running into issues while on rooted 4.2.2 D800 stock ROM. There were force closes and random reboots, etc. I've only installed xposed mods. I've also used android tuner to adjust some of the build.prop and kernel presets.
However, after my phone got stuck in what I thought was a boot loop, I finally got it up and running. What happened next was odd. I tried booting into recovery -> the "LG" splash screen showed up and it went into another infinite boot loop.
I'm assuming I somehow corrupted or lost my recovery. Any advice on what to do? I don't know if I should follow the original instructions for flashing a recovery here - http://forum.xda-developers.com/showthread.php?t=2633150.
Edit: Jesus christ my phone infuriates and confuses the hell out of me. After attempting to enter the recovery again, I am now stuck in a permanent boot loop. The last time I fixed it was by turning my phone off....and then *WAITING*.
What? That doesn't make sense you say? Of course it doesn't. But that's still what worked. I waited 12 hours, and then tried turning it on again. When I did, oh look, the AT&T screen!
CONFUSING. help please...
Double edit (Hard Mode): Going into download mode when I'm in this constant bootloop = nothing happens. That little icon that says "Download Mode" with the 5 blue circles just stays there, and my laptop ends up not recognizing anything. This happened the last time too, and all I was able to see on my laptop was "QHSUSB_BULK". I thought this meant that I would have to do a complete wiping process through Linux (found on another thread somewhere), but apparently waiting 12 hours also fixed the problem.
Hi, it is possible to hide message caution before logo Android one bootloader is unlock when phone start booting ?
Yes, do some searching on xda, there are 2 threads for replacing that annoying splash image.
You can replace the splash image, but delay on boot will remain.