Database Users

rom installed not rebooting stuck on unlocked screen

hey anything please i wiped everything and installed zip"rom" from sd and installed secussful and then i clicked reboot and it just stays on the motorola screen with unlocked in the corner and is stuck there what am i not doing or doing wrong its rooted and unlocked

INSTALL BACKUP!
Or 1. Try pull battery. Or 2. Install again. Or 3. Fastboot.
Atrix - "CM7"

clod007 said:
INSTALL BACKUP!
Or 1. Try pull battery. Or 2. Install again. Or 3. Fastboot.
Atrix - "CM7"
Click to expand...
Click to collapse
i made a back up with titanium and android recovery....
i pulled the battery installed it 2 or 3 times and same thing
what exactly do i type in my cmd prompt on fastboot

If you have a copy of the old ROM, why not reinstall?
For fastboot, sorry, but looking for a tutorial.
Atrix - "CM7"

clod007 said:
If you have a copy of the old ROM, why not reinstall?
For fastboot, sorry, but looking for a tutorial.
Atrix - "CM7"
Click to expand...
Click to collapse
i dont know how to reinstall it but i made back ups of everything

Enter in Android recovery mod
Backup
Chose restore
Atrix - "CM7"

Sometimes certain roms do not properly either clean up the cache and dalvik-cache before and\or after installation which can cause that exact issue. It boots to the Dual-Core screen without doing anything else or restarting after some random amount of time. Hook up fastboot, connect to the device
in command prompt, type this
first confirm that fastboot can communicate between the phone and the pc by using this command below which should show a device connected and list it's serial number
fastboot devices
#--if fastboot sees your phone then just simply type
fastboot -w
#--that wipes the partitions that can cause you to get stuck at the initial boot screen logo, after it finishes, just type
fastboot reboot
I've gotta out of a few situations where phone wouldnt boot until I either did this "fastboot -w" or in clockworkmod recovery, cleared the data and cache, hope that helps, try this method before jumping to any extreme solutions that could make the phone a hat weight

android-DEP said:
Sometimes certain roms do not properly either clean up the cache and dalvik-cache before and\or after installation which can cause that exact issue. It boots to the Dual-Core screen without doing anything else or restarting after some random amount of time. Hook up fastboot, connect to the device
in command prompt, type this
first confirm that fastboot can communicate between the phone and the pc by using this command below which should show a device connected and list it's serial number
fastboot devices
#--if fastboot sees your phone then just simply type
fastboot -w
#--that wipes the partitions that can cause you to get stuck at the initial boot screen logo, after it finishes, just type
fastboot reboot
I've gotta out of a few situations where phone wouldnt boot until I either did this "fastboot -w" or in clockworkmod recovery, cleared the data and cache, hope that helps, try this method before jumping to any extreme solutions that could make the phone a hat weight
Click to expand...
Click to collapse
ok it rebooted and went off the screen now its in a boot loop and flashes the motorola sign then shuts down and keeps going

ok, so the issue was partly the cache not being wiped prior the rom being installed and something went wrong with the installation of the kernel. That happens if the boot.img didnt properly extract and write to partition or its just incompatible with the rom\device.
Visit faux123's thread with kernels for ATT froyo, GB, CM7 & CM9
download the kernel that's compatible for your rom(froyo, gb, cm7 or cm9). Once you download the zip, go in there and pull out the "boot.img" file and put it into the same folder you have fastboot.exe in and boot into fastboot again.
quickly check connectivity with "fastboot devices" to verify and if that checks out, use this command.
"fastboot flash boot boot.img"
it takes like 3 seconds or something to complete so its an easy fix, after its done just do the "fastboot reboot" command.
i had this same exact issue last week plus my recovery was being erased along with this problem so i keep boot.img & recovery.img just sitting inside the fastboot folder just in case
atrix reboot project - it has every single file thats for the atrix and copies of systems, roms, tools, recovery files, mods, tweaks

Try this:
Pull battery
Replace battery while holding volume down until you see fastboot
Tap volume down to until you see android recovery, then press volume up to enter recovery
First try wiping cache/dalvik, if that doesn't work restore nandroid backup, if that doesn't work reflash rom

[Q] Need help! Did OTA update to 5.0, stuck in bootloop!

I need some major help
My N7 2012 was stock, never rooted. I had only installed OTA updates. Yesterday, the OTA update for Lollipop appeared, and I installed it.
It worked fine for about an hour, until it suddenly rebooted. After that, it will now only boot into the launcher (Nova Launcher) for about 15 seconds, then *bam* crash, reboot. Rinse and repeat.
I've tried booting into safe mode via long-pressing on the Shutdown menu, but it apparently crashes before it can reboot, because it just boots back to Nova Launcher.
I've also tried getting it into fastboot, and I can issue fastboot commands. However, I've never unlocked the bootloader. And when I try to unlock it now, I get the screen that says "This will void your warranty are you sure?" But when I select Yes, fastboot's console says "Failed", and it remains locked.
If I go into Recovery, it just says "No commmand"
I need some help from the geniuses on this forum. To me it seems like an app running at startup is causing the crash, so if I could just get it to Safe Mode, I could figure it out and uninstall it. Hell, I'd be fine w/ a total wipe at this point. Just something to get it working again!
Thanks in advance!

Try using wugfresh's nexus toolkit to fix your issue, preferably to full wipe and reinstall lollipop again.

Didn't work
bubba949 said:
Try using wugfresh's nexus toolkit to fix your issue, preferably to full wipe and reinstall lollipop again.
Click to expand...
Click to collapse
I tried using the Nexus toolkit, using Flash to Stock/Unroot in Bootloop mode, and it didn't work. A few sections succeeded, but most of the sections said "FAILED". Even after performing this, it still wants to boot to my normal desktop, so I know it's not re-flashing a thing.
I wish I knew more about this. I can get into fastboot by going to Power+VOL- but because it won't stay on the desktop, adb commands are a no-go. Is there something in the Advanced section of the Nexus Toolkit that will let me do a reflash? I'm afraid of just poking and trying things for fear of truly bricking it.
Thanks.

Sorry just re-read your last reply didn't realise you can't do adb commands, if you get to a point when you can then below may help...
I had a similiar issue caused differently what i did was to go to this link
http://forum.xda-developers.com/showthread.php?t=1907796
Downloaded the bootloader from JWR66V the guy mentions in his thread he mentions the same issue that i had which is when i tried to flash a stock or custom rom i kept getting messages about invalidstate on bootloader then the system and userdata images would fail when i tried to install...
In the end i downloaded the stock JWR66Y rom, replaced the bootloader image with the one mentioned above, i had to flash the seperate parts of the rom as the Nexus Root Toolkit wouldn't accept the MD5 after i replaced the bootloader so make sure the recovery, the modified bootloader, system and userdata are in your SDK tools folder then i did the following in cmd...
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot erase cache
Fastboot reboot
And voila it booted up and then upgraded its self and is now stock running 5.0 but its working for 2days it wasn't lol

alastria1 said:
It worked fine for about an hour, until it suddenly rebooted. After that, it will now only boot into the launcher (Nova Launcher) for about 15 seconds, then *bam* crash, reboot. Rinse and repeat.
I've tried booting into safe mode via long-pressing on the Shutdown menu, but it apparently crashes before it can reboot, because it just boots back to Nova Launcher.
Click to expand...
Click to collapse
You can try booting into Safe Mode directly from powered off state. From a reference guide here in help
bftb0 said:
[size=+1]Safe Mode Boot[/size]
From a cold start boot (press & release Power button), wait 2 seconds after the B&W Google (bootloader) splash screen appears, then press and hold Vol-Down button until the normal OS boot is fully completed (lock screen or home screen appears)
Click to expand...
Click to collapse
Sounds like something is draining the RAM. Try using the stock launcher as default.

Still crashed
dtg7 said:
You can try booting into Safe Mode directly from powered off state. From a reference guide here in help
Sounds like something is draining the RAM. Try using the stock launcher as default.
Click to expand...
Click to collapse
I didn't know that. I tried it, and I was able to boot it into safe mode doing this ... and then it crashed in 15 seconds and rebooted...
At this point, I'm considering just emailing Google, since its their update that did this.

They'll probably tell you to wipe cache partition. And by the way,
alastria1 said:
If I go into Recovery, it just says "No commmand"
Click to expand...
Click to collapse
that is a normal operation, it's supposed to say that. What you need to do to get the actual recovery menu is, with screen saying No Command, hold the power button, then click the volume Up button, them let go of power.
This will get you the recovery options, where you should scroll down to wipe Cache partition (last one I think) and select it by hitting power. Reboot into Android and see if that helped.
If not in the same recovery menu there's an option to wipe everything, factory reset. that might cure your device but it will wipe your data.
There is an adb command to pull your sdcard data off your device, but I've never tried it in stock recovery. it might work, but of course it will probably require you had turned On USB debugging.
adb pull /storage/sdcard0/ yourcomputerfolder
yourcomputerfolder being a location on your laptop, like a folder on the desktop.
try this command when in recovery, I don't think it works in bootloader. also, if it works it will only backup your regular files, not your installed apps.
if not then just do the wipe from recovery.
good luck.

Still a no go...
So, I got into the recovery menu, and did a full factory reset. After it rebooted, it went right back to Nova Launcher (with my usual wallpaper on there), and crashed as before. Getting into safe mode confirmed that it no apps were wiped. Factory reset didn't reset a thing.
Its almost like the flash memory is stuck on read-only mode. No matter what I do, nothing changes the contents of memory.

That is weird. And I suppose you can't do what 'wakers' suggested and flash the individual partitions since it probably requires an unlocked bootloader, which you already tried to unlock unsuccessfully. I'd say you were up sh-- creek without a paddle, but... Google searching, maybe there's still a tiny bit of hope:
See this discussion: http://android.stackexchange.com/qu...p-after-lollipop-flash-no-adb-and-no-fastboot
to summarize the suggestions:
- try holding the power button for over ten seconds to kind of reset... something
- try sending the command: fastboot oem lock
yes I know you never unlocked but try it anyway, it might go thru where unlock failed.
speaking of fastboot oem unlock, I know it failed but maybe you can just keep sending the command a few times, one of them might go thru.
I'd add another suggestion: carefully remove the back and carefully unplug the battery and let it sit for a while. then put it back together and try booting up.
may the force be with you.

Finally resolved
Thanks to the posters for the help. I contacted Google customer support and they're overnighting a refurb replacement for free.

Nexus 6p stuck at fastboot

Hi guys,
I had bootloop issues so tried couple of methods to solve it but could not.
I was able to connect it to my PC and in command window i tried fastboot erase recovery, fastboot erase system, fastboot erase cache. but this did not work and now after i press power button and volume button and select recovery mode, it gets stuck there itself. Also i cannot find my device when i type adb devices in command window.
Please help me :crying:

surajvibhute18 said:
Hi guys,
I had bootloop issues so tried couple of methods to solve it but could not.
I was able to connect it to my PC and in command window i tried fastboot erase recovery, fastboot erase system, fastboot erase cache. but this did not work and now after i press power button and volume button and select recovery mode, it gets stuck there itself. Also i cannot find my device when i type adb devices in command window.
Please help me :crying:
Click to expand...
Click to collapse
Try typing fastboot devices instead and in bootloader mode try flashing the stock angler images such as system, boot, etc.

DEVILOPS 007 said:
Try typing fastboot devices instead and in bootloader mode try flashing the stock angler images such as system, boot, etc.
Click to expand...
Click to collapse
Can you tell me how can i know which file is to downloaded? N2G48B or which. I am not aware which is compatible with my nexus. How do i find out

Help Wiping (or Unlocking) With a Broken Screen

The screen on my Stock unrooted & locked Nexus 6P is completely non-functional (shattered, not displaying anything, likely not responding to touch) and I'd like to wipe it before disposing of it.
I'm able to blindly navigate to the bootloader but I'm having trouble unlocking for the purposes of
Code:
fastboot erase system -w
.
Process
Boot into bootloader then issue the unlock command:
Code:
fastboot flashing unlock
Because I can't see the screen, I'm assuming pressing up or down will select 'Yes' and power will confirm it.
Either way (up+pwr or down+pwr or just pwr) the phone restarts and I let it sit for a while.
I reboot into the bootloader but the unlocked variable returns no.
I figured the closest analog would be to reflash via
Code:
fastboot -w update "image.zip"
, which will wipe userdata and cache - is that sufficient?

Don't worry....just download and install Nexus toolkit or do it manually by downloading Adb fastboot minimal <10mb size.
First, install driver for flashing firmware.
Reboot to bootloader,
Connect to pc,it will make sound if connected.
Now,put system.img to adb minial folder.
Right click and open cmd in adb minimal folder.
Type adb fastboot flash system system.img
Then,in the middle disconnect from pc.since,it will corrupt your system file.Do this for 2-3 times,that is flashing system.img and disconnecting in the middle to insure that system file have corrupted.
Then,at last flash system.img till end to complete.
Voila...you will have a factory reset phone.
I did this trick before selling my galaxy s5 broken display phone.
When buyer put display in front of me,it was factory reset.

Phylum said:
The screen on my Stock unrooted & locked Nexus 6P is completely non-functional (shattered, not displaying anything, likely not responding to touch) and I'd like to wipe it before disposing of it.
I'm able to blindly navigate to the bootloader but I'm having trouble unlocking for the purposes of
Code:
fastboot erase system -w
.
Process
Boot into bootloader then issue the unlock command:
Code:
fastboot flashing unlock
Because I can't see the screen, I'm assuming pressing up or down will select 'Yes' and power will confirm it.
Either way (up+pwr or down+pwr or just pwr) the phone restarts and I let it sit for a while.
I reboot into the bootloader but the unlocked variable returns no.
I figured the closest analog would be to reflash via
Code:
fastboot -w update "image.zip"
, which will wipe userdata and cache - is that sufficient?
Click to expand...
Click to collapse
Run a drill bit through the upper 1/4 of the screen and through the motherboard then dispose.

hawkswind1 said:
Run a drill bit through the upper 1/4 of the screen and through the motherboard then dispose.
Click to expand...
Click to collapse
Lol sounds good to me!
zameer hassan said:
Don't worry....just download and install Nexus toolkit or do it manually by downloading Adb fastboot minimal <10mb size.
First, install driver for flashing firmware.
Reboot to bootloader,
Connect to pc,it will make sound if connected.
Now,put system.img to adb minial folder.
Right click and open cmd in adb minimal folder.
Type adb fastboot flash system system.img
Then,in the middle disconnect from pc.since,it will corrupt your system file.Do this for 2-3 times,that is flashing system.img and disconnecting in the middle to insure that system file have corrupted.
Then,at last flash system.img till end to complete.
Voila...you will have a factory reset phone.
I did this trick before selling my galaxy s5 broken display phone.
When buyer put display in front of me,it was factory reset.
Click to expand...
Click to collapse
Excellent excellent excellent advice - much appreciated.

You need to have USB debugging enabled btw to unlock your phone and issue those fastboot commands.

Stuck in Fastboot Reboot Loop. Fastboot Reason: reboot mode set to fastboot

Last week i received a notification the 8.1 Oreo update was available for my Moto g4 Plus.
Downloaded the package and hit the install button. My moto restarted in order to perform the installation.
However, since i had TWRP installed and thus bootloader unlocked, the phone restarted in recovery mode.
Downloaded a TWRP 8.1 rom and installed it without a problem.
Unfotunately everytime I restart my Moto it starts up in fastboot mode.
Bootloader log shows: Fastboot Reason: reboot mode set to fastboot
From bootloader I can start the Android OS, but i wan't to get rid of this reboot mode
I tried tools like "Android Multi Tool" and "Free ReiBoot for Android" but this reboot mode can not be cleared.
Anyone encountered this problem and how did you fix it.
Thanks in advance

Try this:
Reboot your device to the bootloader.
Connect your device to your computer and open an ADB terminal on your computer.
In the ADB terminal, type 'fastboot devices' without quotes. Press Enter - your device should respond with its serial number.
If so, then type 'fastboot oem fb_mode_clear' without quotes. Press Enter, then reboot your device.
That fb_mode_clear command seems to clear a flag that keeps your device booting into fastboot (usually for OTA updates).

I have Tried that option as i found it as one of the possible solutions for this issue.
the clear_fb unfortunately does not remove the fastboot mode on my moto.

mbodewes said:
I have Tried that option as i found it as one of the possible solutions for this issue.
the clear_fb unfortunately does not remove the fastboot mode on my moto.
Click to expand...
Click to collapse
Alright, though this is for solving TWRP bootloops, might be useful for you https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325

echo92 said:
Alright, though this is for solving TWRP bootloops, might be useful for you https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
Click to expand...
Click to collapse
echo92. Thanks. Works like a charm. Issue fixed.