Database Develop

Droid Won't Boot. Stuck At M Logo

I am looking at a phone for a friend of mine. It's a original Droid. It will not boot to the OS, it just sits at the M logo for hours and hours. I have got it into recovery mode by powering on and holding up on the D pad. I then used RSD Lite to reflash VZW_A855_FRG01B_QSC6085BP_C_01.43.01P_SW_UPDATE_01 to it. It says it finished and passed, but still sits at the M logo. Any ideas?

::tap tap tap:: Is this thing on?

Guess not. Thanks for all the help. Sure am glad I own an iPhone.

can you try with another custom rom?

So i hope someone responds to this.
My og Droid is stuck at the M logo. i can get into bootloader and Clockworkmod revoery mode, but i cant actually boot into the OS.
So when i first got it a few days ago, i did a factory reset. I then rooted it, which worked, and then installed rom manager. i made a back up twice to be sure, then tried to flash to Kfazz's Jellybean ROM. It said success, but after that i was in a boot loop. I read on how to fix this, but adb wont find the device until it is in the OS, so i popped out the battery and restored from my backup, but now it just stays at the M logo. Any help would be greatly appreciated.
Thanks in advance

The M logo is the bootloader's logo. Since the droid has unlocked bootloader it is possible that something messed it up.
Can you restore the stock bootloader?

Erovia said:
The M logo is the bootloader's logo. Since the droid has unlocked bootloader it is possible that something messed it up.
Can you restore the stock bootloader?
Click to expand...
Click to collapse
Is it? I hit up on the d-pad and that says bootloader on it. You may be right as i am new to ths and will try that out after i eat. Thank you for the quick reply!
---------- Post added at 06:30 PM ---------- Previous post was at 06:22 PM ----------
BradlyeG said:
Is it? I hit up on the d-pad and that says bootloader on it. You may be right as i am new to ths and will try that out after i eat. Thank you for the quick reply!
Click to expand...
Click to collapse
So i tried it and im not actually sure how to reset the bootloader. Thanks again and any help is always apprecieated.

Go into recovery and wipe data, cache, and dalvik cache. Then try and boot it up. If that fails download a new rom wipe everything above again, then flash the new rom, the m logo is not the bootloader nothin u did had anything with the bootloader. I have this problem once in a when flashin a kernel or new rom
Sent from my Droid using xda premium

WillisD said:
Go into recovery and wipe data, cache, and dalvik cache. Then try and boot it up. If that fails download a new rom wipe everything above again, then flash the new rom, the m logo is not the bootloader nothin u did had anything with the bootloader. I have this problem once in a when flashin a kernel or new rom
Sent from my Droid using xda premium
Click to expand...
Click to collapse
Thank you so much for the info. Wiping all the above did not work, so i am going to flash to a new rom. Thanks again!!
---------- Post added at 09:20 PM ---------- Previous post was at 09:15 PM ----------
BradlyeG said:
Thank you so much for the info. Wiping all the above did not work, so i am going to flash to a new rom. Thanks again!!
Click to expand...
Click to collapse
Holy hedgehogs it freakin worked!!!!!!!!!!!!!!!!!!! At least i think. It got past the m logo and is doong some weird boot animation

just wipe everything before before flashing new rom cm7 is pretty stable, and there is steel droid thats still active
---------- Post added at 09:23 PM ---------- Previous post was at 09:20 PM ----------
if you made it to the boot animation then you should be good, just let me know

WillisD said:
just wipe everything before before flashing new rom cm7 is pretty stable, and there is steel droid thats still active
---------- Post added at 09:23 PM ---------- Previous post was at 09:20 PM ----------
if you made it to the boot animation then you should be good, just let me know
Click to expand...
Click to collapse
I actuLly used CM9, but i cant get the touch screen or touch buttons to work. I may just have to use a different build, or roll back to an ealier cm build.

[Q] Phone Stuck in Recovery - Tried installing ROM before installing Superuser

I am pretty new to ROOTing android phone. I wanted to upgrade my HTC incredible S to Jelly bean. I was successfully able to UNLOCK the phone. But in recovery menu, i have installed/flashed the Jelly bean (PACman-v19.3-VIVO-BLINDNDUMB.zip) OS before installing Superuser. Now the mobile is booting only in recovery mode everytime. Please help me on this. Is my phone gone for good?

I guess that you are probably s-on. Do the following steps. Format all partitions except the sd card using the recovery. I hope you installed a custom recovery like Cwm or 4ext after unlocking your bootloader. If you have, then flash the ROM again. Then reboot your phone into the bootloader and fastboot flash the boot.img.
Sent from my Incredible S using XDA
---------- Post added at 03:31 PM ---------- Previous post was at 03:29 PM ----------
Try following the instructions in this thread
http://forum.xda-developers.com/showthread.php?t=1337105
Sent from my Incredible S using XDA

Thank you
InsertDumbNick said:
I guess that you are probably s-on. Do the following steps. Format all partitions except the sd card using the recovery. I hope you installed a custom recovery like Cwm or 4ext after unlocking your bootloader. If you have, then flash the ROM again. Then reboot your phone into the bootloader and fastboot flash the boot.img.
Sent from my Incredible S using XDA
---------- Post added at 03:31 PM ---------- Previous post was at 03:29 PM ----------
Try following the instructions in this thread
http://forum.xda-developers.com/showthread.php?t=1337105
Sent from my Incredible S using XDA
Click to expand...
Click to collapse
Thanks a lot for the help. Successfully installed Jelly bean. Phone up an running. Really appreciate the help provoided

[Q] need help in slimkat rom

hi guys,
I did installed cwm recovery ,unlocked bootloader and tried to flash slimkat rom and got stuck with bootloop with error "process system isn't responding do you want to close".i did reflashed couple of times i have done complete wipe including data.fixed permisions in recovery after all that i am still not able to boot the rom.please help me in solving this

harishke said:
hi guys,
I did installed cwm recovery ,unlocked bootloader and tried to flash slimkat rom and got stuck with bootloop with error "process system isn't responding do you want to close".i did reflashed couple of times i have done complete wipe including data.fixed permisions in recovery after all that i am still not able to boot the rom.please help me in solving this
Click to expand...
Click to collapse
what i normally do using philz recovery
1) wipe data ( complete wipe to install a new rom)
2) flash slimkat rom
3) flash slim gapps
4) as im having as c6902, i need to flash modules of c6902, hence, flash the modules provided in the monx thread in Xperia Z1 android development
5) flash superuser zip to gain root access later on
6) reboot

Hey
[/COLOR]
harishke said:
hi guys,
I did installed cwm recovery ,unlocked bootloader and tried to flash slimkat rom and got stuck with bootloop with error "process system isn't responding do you want to close".i did reflashed couple of times i have done complete wipe including data.fixed permisions in recovery after all that i am still not able to boot the rom.please help me in solving this
Click to expand...
Click to collapse
you have to download this file: https://drive.google.com/file/d/0B_3SvSLy59OXUTUweFJpWjYwd1E/edit?usp=sharing
then flash it.

Exact problem. Give This zip a try. Also can you explain what is This file do???
---------- Post added at 04:57 PM ---------- Previous post was at 04:24 PM ----------
stoan123 said:
[/COLOR]
you have to download this file: https://drive.google.com/file/d/0B_3SvSLy59OXUTUweFJpWjYwd1E/edit?usp=sharing
then flash it.
Click to expand...
Click to collapse
Working. thanks bro
Sent from my z1 on slimkat rc2

a
jobangill99 said:
Exact problem. Give This zip a try. Also can you explain what is This file do???
---------- Post added at 04:57 PM ---------- Previous post was at 04:24 PM ----------
Working. thanks bro
Sent from my z1 on slimkat rc2
Click to expand...
Click to collapse
there're diferent between c6903 and c6902. i think that is modem
you can read more detail from thread

thanks a ton guys finally it worked by flashing modem and was able to use the rom:good:

How to easly install a custom rom on my Note 3

I need help on how to install a custom rom, i have been at it, and i cant seem to get this done at all.
http://forum.xda-developers.com/showthread.php?t=2595085 (Dynamic Rom)
There is the link of the rom i want to install on my stock Galaxy Note 3 4.3.
I Have Rom Manager on my phone and i have safestrap when i put the phone in recovery mode, i dont get any of these options like to install rom etc..

Dasin said:
I need help on how to install a custom rom, i have been at it, and i cant seem to get this done at all.
http://forum.xda-developers.com/showthread.php?t=2595085 (Dynamic Rom)
There is the link of the rom i want to install on my stock Galaxy Note 3 4.3.
I Have Rom Manager on my phone and i have safestrap when i put the phone in recovery mode, i dont get any of these options like to install rom etc..
Click to expand...
Click to collapse
did you install the safestrap recovery from inside the app

jerrycoffman45 said:
did you install the safestrap recovery from inside the app
Click to expand...
Click to collapse
No i just downloaded safestrap from a online source and then transferred it to my Phone and then i just installed it from there

Dasin said:
No i just downloaded safestrap from a online source and then transferred it to my Phone and then i just installed it from there
Click to expand...
Click to collapse
click on the app on your phone then click install recovery also make sure you have the right version of safestrap for 4.3 it is 3.71

jerrycoffman45 said:
click on the app on your phone then click install recovery also make sure you have the right version of safestrap for 4.3 it is 3.71
Click to expand...
Click to collapse
im on version 3.2, do i need to downgrade? if not
when i go to boot into recovery mode it just goes into a boot loop, n then boot into 4.3 and im back at square one

Dasin said:
im on version 3.2, do i need to downgrade?
Click to expand...
Click to collapse
yes 3.72 is for kitkat

jerrycoffman45 said:
yes 3.72 is for kitkat
Click to expand...
Click to collapse
When I try and boot into clockwork recovery mod, this is the image I get on the screen once the phone reboots into recovery mode

That is the stock recovery to get to safestrap recovery just hit the reboot into recovery button in the app
Sent from my SAMSUNG-SM-N900A using Tapatalk
---------- Post added at 09:35 PM ---------- Previous post was at 09:34 PM ----------
And safestrap uses a modified twrp recovery
Sent from my SAMSUNG-SM-N900A using Tapatalk

jerrycoffman45 said:
That is the stock recovery to get to safestrap recovery just hit the reboot into recovery button in the app
Sent from my SAMSUNG-SM-N900A using Tapatalk
---------- Post added at 09:35 PM ---------- Previous post was at 09:34 PM ----------
And safestrap uses a modified twrp recovery
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
I just did that and i get the same options, shown in the picture above, it wont let me get into that mode.

I don't know what to tell you maybe uninstall the recovery from within safestrap then uninstall safestrap reboot and try again I would also try re downloading the app maybe a bad download
Sent from my SAMSUNG-SM-N900A using Tapatalk
---------- Post added at 09:56 PM ---------- Previous post was at 09:55 PM ----------
Also you are already rooted right
Sent from my SAMSUNG-SM-N900A using Tapatalk

Dasin said:
When I try and boot into clockwork recovery mod, this is the image I get on the screen once the phone reboots into recovery mode
Click to expand...
Click to collapse
I have seen you mention ROM Manager and Clockwork recovery. Neither of these are compatible with the AT&T Note 3. PM & I will help out.

jerrycoffman45 said:
I don't know what to tell you maybe uninstall the recovery from within safestrap then uninstall safestrap reboot and try again I would also try re downloading the app maybe a bad download
Sent from my SAMSUNG-SM-N900A using Tapatalk
---------- Post added at 09:56 PM ---------- Previous post was at 09:55 PM ----------
Also you are already rooted right
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
When i boot up the phone, it says the process system has not running wait or ok, when i push ok or wait. after about 40 seconds the phone just freezes up.

Flashing Dead Android Doll Error After Root Attempt (XT1060 - VZW)

I tried to root my phone from the methods provided from here: http://forum.xda-developers.com/moto-x/general/root-moto-x-att-xt1058-5-1-lpa23-12-21-1-t3164125
I downloaded the necessary files for my specific device. Everything went fine in the flashing process. I booted my phone to check if it was the correct build version, and it was right (LPA23.12-39.7).
I proceeded to the next process, which was running the BLBROKE and RUN_Root file to root my phone. After the RUN_Root process finished ~15 minutes, my phone bootlooped. I tried to re-flash the LPA23.12-39.7 software, but it bootlooped again.
So I performed a hard reset. AFter the hard reset, it bootlooped again and this error showed up: https://drive.google.com/file/d/0BzXaUzs8MoBWSWRWbnh2TG9VTVU/view
I can get to fastboot and Qualcomm Emergency Mode, but anything I have done so far will come back that flashing dead android doll. Any help please? Thanks.

try flashing stock rom, chose the one you were using before brick.
here is guide:
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
firmware link:
https://yadi.sk/d/MCliEyCPfj7ZZ/MOTO.X1/XT1060

buddy means u downgrade your phone from build no. LPAS23.12-39.7-1 ??

ftan299 said:
I tried to root my phone from the methods provided from here: http://forum.xda-developers.com/moto-x/general/root-moto-x-att-xt1058-5-1-lpa23-12-21-1-t3164125
I downloaded the necessary files for my specific device. Everything went fine in the flashing process. I booted my phone to check if it was the correct build version, and it was right (LPA23.12-39.7).
I proceeded to the next process, which was running the BLBROKE and RUN_Root file to root my phone. After the RUN_Root process finished ~15 minutes, my phone bootlooped. I tried to re-flash the LPA23.12-39.7 software, but it bootlooped again.
So I performed a hard reset. AFter the hard reset, it bootlooped again and this error showed up: https://drive.google.com/file/d/0BzXaUzs8MoBWSWRWbnh2TG9VTVU/view
I can get to fastboot and Qualcomm Emergency Mode, but anything I have done so far will come back that flashing dead android doll. Any help please? Thanks.
Click to expand...
Click to collapse
Hello
I encounter exactly the same problem "flashing dead droid no command" after try to root with that method
I tryed to flash the stock rom but I could not down grade to that!
what have you found?? what did you do buddy plz tell me
---------- Post added at 04:04 PM ---------- Previous post was at 03:59 PM ----------
if anybody else should know what should I do to getaway that flashing dead droid plz tell me?
I try to flash the stock rom but I couldnt cuz of downgrade security problem!

Mohsen_zz said:
Hello
I encounter exactly the same problem "flashing dead droid no command" after try to root with that method
I tryed to flash the stock rom but I could not down grade to that!
what have you found?? what did you do buddy plz tell me
---------- Post added at 04:04 PM ---------- Previous post was at 03:59 PM ----------
if anybody else should know what should I do to getaway that flashing dead droid plz tell me?
I try to flash the stock rom but I couldnt cuz of downgrade security problem!
Click to expand...
Click to collapse
I've found this post really helpful
So after I did this first step (flash stock firmware via fastboot) I was able to overcome bootloop issue and install root
Hope this helps!