Database Users

can somebody help? stuck on boot logo

i install the paranoid android rom on my nexus 7 and now its stuck on the bootanimation of the paranoidandroid rom i didn't wipe the data but i did wipe the caches so if somebody can tell how to get out of it i will appreciate the help I'm new to this thank you

Hold on the power button (I believe) to turn it off and go back to recovery and re-wipe and reflash. It happened to me once. Or wait till the battery dies.

Hold down the volume up (might be down, can't remember) and power button down at the google screen. Then the screen should go black, quickly hold down all three keys (up, down, and power) and it should bring you to recovery mode. :good:

Nxxx said:
Hold down the volume up (might be down, can't remember) and power button down at the google screen. Then the screen should go black, quickly hold down all three keys (up, down, and power) and it should bring you to recovery mode. :good:
Click to expand...
Click to collapse
Hi. Have the same problem. When trying getting into recovery mode, nexus stuck on google logo. Please help. I don't know what to do.

Ran into the same thing and now fixed
I had the same problem and finally figured out (I think) that it was because I was installing the ROM and the gapps at the same time. I installed just the ROM and then booted. Then rebooted to recovery and installed the gapps.
1. Hook it up to the computer.
2. Shut it off. Hold power. Then hold Power and Down till at the bootloader screen.
3. Flash recovery "fastboot flash recovery recov_filename.img". I used the zip from thread 1837401 on these boards to get fastboot and clockwork recovery.
Sometimes have to do this 2x if won't run through. If it sits doing nothing, go down in the menu and reboot bootload and then rerun the command before touching anything on the GN7.
4. Go into recovery, flash PA and reboot. After got in and running, reboot and install gapps.
5. Enjoy the awesomeness!

LOL you have to wipe the data. use tib to get your stuff back. Wiping the cache is a meaningless gesture if you haven't wiped the data. If you had followed the instructions in the rom thread, there would be no problem for you.
Sent from my Nexus 7 using xda premium

dude i do this on the nexus 7 toolkit and all it does is close the toolkit, i cant get off the x loading screen, can you help please? running jellybean4.2.1
only1skeemer said:
I had the same problem and finally figured out (I think) that it was because I was installing the ROM and the gapps at the same time. I installed just the ROM and then booted. Then rebooted to recovery and installed the gapps.
1. Hook it up to the computer.
2. Shut it off. Hold power. Then hold Power and Down till at the bootloader screen.
3. Flash recovery "fastboot flash recovery recov_filename.img". I used the zip from thread 1837401 on these boards to get fastboot and clockwork recovery.
Sometimes have to do this 2x if won't run through. If it sits doing nothing, go down in the menu and reboot bootload and then rerun the command before touching anything on the GN7.
4. Go into recovery, flash PA and reboot. After got in and running, reboot and install gapps.
5. Enjoy the awesomeness!
Click to expand...
Click to collapse

[Q] Cyanogenmod 10.1(or 10.2) stuck in bootloop? D:

So about a few hours ago I saw that I could download the new 10.2 cyanogenmod. I wanted it because it was Android 4.3, so I downloaded it. I tried watching flash movies and stuff, and the browsers and stuff kept crashing, and the internet didn't work completely. So, I downloaded 10.1 again, and installed it. It rebooted to the teamwin thing, and then rebooted again. A few minutes after, I was curious as to why it was still loading. Waited a long time, and it still was on the CM boot logo thing. Im using the Nexus 7 toolkit (its called something else, but im not sure what. The icon is a red toolbox with 3 tools in it), and can't reboot into recovery or flash stock back on it. How can I get it out of bootloop? I really need help! D:

Press all the three buttons , power , volume up and volume down together and boot into bootloader. From boot loader use volume buttons to go onto recovery , do a clean wipe there and reflash a ROM. Another alternative is to use adb and type
Code:
adb reboot recovery
then wipe clean and reflash ROM.

Red Devil said:
Press all the three buttons , power , volume up and volume down together and boot into bootloader. From boot loader use volume buttons to go onto recovery , do a clean wipe there and reflash a ROM. Another alternative is to use adb and type
Code:
adb reboot recovery
then wipe clean and reflash ROM.
Click to expand...
Click to collapse
You Probably forgot to do one or some of these steps before flashing, I had the same problem today trying to flash 10.2:
http://forum.xda-developers.com/showthread.php?t=2179330

Atrix HD Stuck on Animation
Red Devil said:
Press all the three buttons , power , volume up and volume down together and boot into bootloader. From boot loader use volume buttons to go onto recovery , do a clean wipe there and reflash a ROM. Another alternative is to use adb and type
Code:
adb reboot recovery
then wipe clean and reflash ROM.
Click to expand...
Click to collapse
Hi Red Devil,
I just tried to install CM 10.1.3 on my Motorola Atrix HD.
I forgot to wipe data and cache before installing the ROM, and now it is stuck in the boot animation.
When I press the power and volume keys down together, it takes my phone to a black screen, and when I press them again on the black screen it gives me a brief menu that says
"Normal power up"
"Recovery"
"AP Fastboot"
"Factory"
and another one I can't recall.
This screen times out in about 3 seconds. and regardless of which item from the menu I select, it still shows my boot logo, then the CM animation. I cant boot into fastboot or recovery, and I can't find anything good online to help me.
Help! What do I do?

Nexus 4 - Received 4.4 OTA - Stuck on Nexus Splash screen...

As the title suggests, after installing Kit Kat (OTA) and waiting for the device to finish the process, my Nexus 4 is now stuck on the Nexus splash screen. Have let it sit for 20+ minutes now and it will not go any further.
Some assistance is welcome
Thank you

By the way, the phone is completely stock; no root/locked boot loader...and the OTA was pushed to me, not sidel oaded.

Same problem...

Reboot into recovery and wipe cache. (Hold VOL - and Power), in Recovery, (hold Power first then VOL +) to enable the menu.
Be careful with the factory reset option, which in this case will wipe your entire device.
You can also use the adb sideload feature to sideload the OTA package manaully that might fix it. You can download them here with insrtuctions on how to flash: http://forum.xda-developers.com/showthread.php?t=2145848. You might need adb drivers to have your device recognize, http://developer.android.com/sdk/win-usb.html

eksasol said:
Reboot into recovery and wipe cache. (Hold VOL - and Power), in Recovery, (hold Power first then VOL +) to enable the menu.
Be careful with the factory reset option, which in this case will wipe your entire device.
You can also use the adb sideload feature to sideload the OTA package manaully that might fix it. You can download them here with insrtuctions on how to flash: http://forum.xda-developers.com/showthread.php?t=2145848. You might need adb drivers to have your device recognize, http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
Clearing Cache did not work...Will have to try other options.

same problem too
I have the same problem too... but now it´s even worse because (after touching all the recovery menu) my N4 gets stuck in the Google screen, and it cannot conect to my PC (but it does charge the phone when connected to the computer)
Any help please!!??? I´m completely lost
thank you

luiiinho said:
I have the same problem too... but now it´s even worse because (after touching all the recovery menu) my N4 gets stuck in the Google screen, and it cannot conect to my PC (but it does charge the phone when connected to the computer)
Any help please!!??? I´m completely lost
thank you
Click to expand...
Click to collapse
Download the OTA package and follow the Scenario #1 steps from here to flash the OTA manually: http://forum.xda-developers.com/showthread.php?t=2145848
If after that and wiping data in recovery the phone won't work, then you need to do a factory reset in recovery (you will lose all your data).
After factory reset, if it still don't work you need to manually flash the factory image. See the guide links in my signature.

Same case, nothing works

Problems after resetting.

So I wiped cache and so on now the thing is hanging at the Motorola screen and that's it.
I tried to get a sbf but all who should be compatible are down so that I pretty much am freaked.
Is there a way to get at least now a clean rom on it maybe something new 4.4.2 without SDCard or is that also a nogo?
----
So if your phone won'T boot and you just have a white light or nothing at all. You probably have less battery power to sbf flash something.
I used the Jumper cable method from Sorensiim.
That worked like a charm.
If you are looking for sbf files. Here are some.
----
So now I rooted that thing and tried to install bootmenu. Iused the adb method with ./install.sh permission denied after the copy procedure was complete ((data/bootmenu chmod etc.). I tried 2ndinit with the problem that the program hangs after the download. So what is it now that freakin thing wants me to do?
----
Got Bootmenu installed now the Defy has a Bootloop. For a short time before it loops the white led blinks. No volume up or volume down work.
----

Hanging at M logo on re-boot
Having rooted the phone . . .
1. Switch on and await blue LED
2. Press volume down to enter Android Boot Menu (v 1.1.8-jordan)
3. Recovery
4. Custom Recovery > Cyanogen Defy Recovery (v5.0.3.1-jordan)
5. Wipe Data / Factory Reset
6. Wipe Cache Partition
7. Advanced > Wipe Dalvik Cache
8. Install zip from SD card
9. Toggle signature verification to Disabled
10. Toggle script asserts to Disabled
11. Choose zip from SD card
12. Apply zip from SD card
13. Reboot
14. Hangs at M logo
Tried with and without step 10.
The zip files tried are the only two ‘nightlies’ on the XDA website, as I have been unable to find the last ‘stable’ version.
Can anyone help please?

OP2 soft bricked, can't access recovery, not recognized by laptop

Hey,
Very strange query but here goes. Rooted phone a while back and installed CM13 along with recovery. Was trying to update TWRP{ by downloading .img from their website, went to flashing, selected the file and hit recovery. Said it was succesful so attempted to reboot. Plugged in to charge and was charging but when I tried to switch it on, it was stuck in Cyanogen Bootloop (blue alien stayed on the screen for 10+ minutes). Tried rebooting to recovery by hitting power + volume down and instead of booting to TWRP, it takes me to a Cyanogen recovery screen where I see the following options:
Cyanogen Recovery.
- Reboot system now
- Apply update
- - -apply from ADB
- - -choose from emulated
- Factory reset
- - -system reset
- - -full factory reset
- - -wipe cache
- Advanced
- - -reboot recovery
- - -reboot to bootloader
- - -Wipe system partition
- - -view recovery logs
Here's what I tried as troubleshooting. Tried to do a system reset, factory reset and wiped cache and tried to restart my phone but no luck. Still stuck in boot loop with CM logo. Tried to reboot to bootloader but the screen is stuck with the 1+ logo for about 5 mins so gave up on that.
Basically, right now I can't access anything on the phone, can't find any way to reinstall a ROM and when I plug it into my Macbook, it is not recognised. So I'm screwed sideways. I had TWRP recovery set up so I have no clue how this happened but can anyone please help me with this.

If data isn't at risk try the Qualcomm recovery tool one the oneplus forum it's by nammand bhal (definitely butchered the name) but all data is lost and resets the phone to out of box conditions locked bootloader and Oos 2.2.1 so this is often a last measure (tool is Windows but may have Mac variant and the file is quite big)
My suggestion is to try to boot to bootloader again and flash TWRP
hmm mac book I don't have much experience with those
If you have a Windows pc you can use adb or on Mac if it has it. Also when it come to being found by a computer in recovery it should but again don't have a mac

CM13 replaced your TWRP recovery with Cyanogen Recovery.
Try to boot into fastboot by holding volume up+ power buttons. If successfull, flash TWRP Recovery, boot into it, wipe everything and do a clean install of the ROM.
Macbook won't detect your device unless it is booted up, in recovery or in fastboot mode.
Doesn't it detect while you are in CM Recovery??
Try selecting Apply Update and Update from ADB. It should detect the device atleast now. If yes, try sideloading.

AJay27 said:
CM13 replaced your TWRP recovery with Cyanogen Recovery.
Try to boot into fastboot by holding volume up+ power buttons. If successfull, flash TWRP Recovery, boot into it, wipe everything and do a clean install of the ROM.
Macbook won't detect your device unless it is booted up, in recovery or in fastboot mode.
Doesn't it detect while you are in CM Recovery??
Try selecting Apply Update and Update from ADB. It should detect the device atleast now. If yes, try sideloading.
Click to expand...
Click to collapse
I knew I would regret getting that macbook at some point
Borrowed a friend's PC and was able to flash TWRP recovery. Was then able to boot into it and do a clean install. Ended up installing Oxygen OS this time. Do you know why this issue occurred so I can research how to prevent it next time.

justicesourglide said:
I knew I would regret getting that macbook at some point
Borrowed a friend's PC and was able to flash TWRP recovery. Was then able to boot into it and do a clean install. Ended up installing Oxygen OS this time. Do you know why this issue occurred so I can research how to prevent it next time.
Click to expand...
Click to collapse
Actually I don't think the issue was with the Macbook since I have unlocked, flashed custom recoveries and sideloaded ROMs on several devices including OP2, OP3, Nexus 5, etc on mine. It might have been some accidental flashing error, which unfortunately ended up bricking your device.