Stuck at M - Droid X General

Hello I get stuck at the M logo after I restart my phone. I flashed it to cricket and installed Rumm rx but now I get stuck at the M logo almost every time I reboot. After I remove the battery many times I can finally boot into my phone with no issues..any help would be great..thanks
Sent from my DROIDX using XDA App

Kinda sounds like you need to sbf and start over.

canyoufindben said:
Kinda sounds like you need to sbf and start over.
Click to expand...
Click to collapse
Is that hard to do? What does that do?
Sent from my DROIDX using XDA App

canyoufindben said:
Kinda sounds like you need to sbf and start over.
Click to expand...
Click to collapse
I did the SBF but it still hangs on the M logo until I take out the battery a few times.
Im also running boot loader 30.3 and sbf 2.3.15

Related

Help for a friend...

A friend of mine is trying to flash Liberty rom. When it finishes installing and reboots, he gets stuck in a boot loop. Any suggestions?
DozeBeatS said:
A friend of mine is trying to flash Liberty rom. When it finishes installing and reboots, he gets stuck in a boot loop. Any suggestions?
Click to expand...
Click to collapse
Boot into stock recovery and do a factory reset
Sent from my DROIDX using XDA App
what were you on before???? The more info u post the better we'll be able to help
bigshotrob22 said:
Boot into stock recovery and do a factory reset
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Do this. It will work

Bricked? SBF from GB .576 to Froyo .340. HELP!!!!

So I tried to SBF back to 2.3.340 like I done before and now I get stocked on the red M logo. When I try to go into recovery I only get to the exclamation point and pressing the search button doesn't do anything!!
What can I do?
Help please. I don't see an answer on the forums
Thanks
UPDATE: I had the system-only SBF. Found the SBF full and it worked.
Now try to figure how to install the zip files because my phone is not letting me
Venc said:
So I tried to SBF back to 2.3.340 like I done before and now I get stocked on the red M logo. When I try to go into recovery I only get to the exclamation point and pressing the search button doesn't do anything!!
What can I do?
Help please. I don't see an answer on the forums
Thanks
Click to expand...
Click to collapse
It sounds like you did the "system only" sbf.. Make sure it's the full sbf
Sent from my DROIDX using XDA App
bigshotrob22 said:
It sounds like you did the "system only" sbf.. Make sure it's the full sbf
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Hey,
Is it even out? I don't see it online
EDIT: I think I found the full SBF. I'll try it. Thanks
UPDATE: bigshotrob22 you are awesome!! Thank you it worked!!! Now I have to cancel my order for the replacement LOL
That happened to me. I SBF'd back to .340 and still had the Red M logo from the Gingerbread .595.
I was unable to get into recovery at all. I eneded up not having the phone for the day and did the SBF again when I got home, you can still access the bootloader, just not recovery (or atleast I was able to) to do the SBF back to .340.
You said you have done the SBF before..my issue with was I did not go into the factory recovery FIRST and wipe all data. I have since done three SBF's and wipe data (in stock recovery, not BOOT STRAP) first. I wiped data, DID NOT REBOOT device. Powered off, and went straight into the bootloader to SBF.
That seems to work for me now.
If it is the samething that happened to me...the wipe did not completely do its job. I make it a habit to wipe 3-4 times before doing anything.
try pushing the volume button up& down at the same time instead of search
Sent from my DROIDX using XDA App

[Q] Possible brick? Maybe sbf save?

So here's the story. Bought a used Droid X from a guy at work. Phone was fine. Never rooted or anything related to root. So I decided to root it. Used ZergRush method I believe. Installed Bootstrap Recovery. Wife used Rom Toolbox to change several notification icons, boot animation and boot logo. Everything was great for awhile, but she got tired of it always booting into recovery. So I was going to un-root and return to stock. Ran the same ZergRush Un-root app. Then removed Bootstrap and all other root apps. Then found out wife accepted an OTA before I un-rooted. Well, at this point the phone still worked, and was un-rooted, but still rebooted into recovery, still had custom boot animation and logo as well. So she then reset phone to factory defaults. After that is when we had problems. Basically it wouldn't load past the boot logo. I just pulled the phone out from its hiding spot after a month or so to try and tackle it again. But now I think the battery is shot because it won't turn on period, whether plugged in or not, and the battery looks like its swollen. Has a huge bulge in the middle.
My question is, do you think the phone is able to work again? Cuz if not, I'm not buying a new battery.
Yeah it sounds like a bad battery now but before would it would just boot to the red m? If so an sbf would probably do the trick
Sent from my ADR6425LVW using Tapatalk 2
Ya before it would boot to the M and stay there, until I pulled the battery. So hopefully new battery and sbf and it will work?
Well yeah an sbf should do you just fine
Just be sure once you do the sbf you boot into stock recovery (vol down+home+power then vol up+down together when you see the !) And do a factory reset or you'll just have another headache
Sent from my ADR6425LVW using Tapatalk 2
Alright cool. Looks like I'll be finding a battery and having a whirl at this. Thanks for the replies
So i sbf'd the shadow 2.3.4 using rsd and it said it was completed and to manually boot the phone. So i did and it still stays at red m logo. Only difference is its now the red m where as before the sbf it was the pink Android my wife installed. So some progress I guess.
Any ideas? Try a different sbf file maybe?
Sent from my R800x using XDA
EDIT: Nvm, tried a different sbf and it works fine now.
I know you say it would boot into the M but could you get it to boot into recovery?
Don't remember if i tried actually lol. Its plain now, no root or bootstrap, but it works
Sent from my R800x using XDA
Kasper DG said:
Its plain now, no root or bootstrap, but it works
Click to expand...
Click to collapse
Strange how DroidX phones eventually become stock and unrooted :^)
Sent from my unrooted DroidX using Tapatalk
Nate2 said:
Strange how DroidX phones eventually become stock and unrooted :^)
Sent from my unrooted DroidX using Tapatalk
Click to expand...
Click to collapse
Very strange indeed. Almost like I got the sbf to work or something
Sent from my R800x using XDA

[Q] Motorola XPRT stuck at Motorola Logo

Motorola XPRT stuck at Motorola Logo.
I'm trying to flash it with this firmwares:
1FF-p3_kronos_cdma_kronos-user-2.2.2-KRNS-X4-1.1.10-110916-release-keys-Sprint-US.sbf
1FF-p3_kronos_cdma_kronos-user-2.3.5-4.5.1-KNS-29-BST-15-18-release-keys-signed-Boost-US.sbf
If I use RSDLite, I get error (with any firmware):
and Code Corrupt in bootloader.
When I use sbf_flash on linux,
1FF-p3_kronos_cdma_kronos-user-2.2.2-KRNS-X4-1.1.10-110916-release-keys-Sprint-US.sbf - bootloader error(Mem Map Blank)
1FF-p3_kronos_cdma_kronos-user-2.3.5-4.5.1-KNS-29-BST-15-18-release-keys-signed-Boost-US.sbf - stuck at Motorola Logo.
Any suggestions?
Simple but always good to check. Make sure the sbf checksums are correct to ensure they were downloaded correctly.
Sent from my MB612 using xda app-developers app
Checksums of my files:
CRC32
1FF-p3_kronos_cdma_kronos-user-2.2.2-KRNS-X4-1.1.10-110916-release-keys-Sprint-US.sbf 7A4A4AF2
1FF-p3_kronos_cdma_kronos-user-2.3.5-4.5.1-KNS-29-BST-15-18-release-keys-signed-Boost-US.sbf 74A272C6
MD5
517739312695ec87e0668c50987dccdd *1FF-p3_kronos_cdma_kronos-user-2.2.2-KRNS-X4-1.1.10-110916-release-keys-Sprint-US.sbf
315d553a44a058ef6b662fa59280020e *1FF-p3_kronos_cdma_kronos-user-2.3.5-4.5.1-KNS-29-BST-15-18-release-keys-signed-Boost-US.sbf
SHA1
34197f6aee01746a4993017f9763166fa2e68bf0 *1FF-p3_kronos_cdma_kronos-user-2.2.2-KRNS-X4-1.1.10-110916-release-keys-Sprint-US.sbf
6b7657609e29323c38ee68401977b1618c855582 *1FF-p3_kronos_cdma_kronos-user-2.3.5-4.5.1-KNS-29-BST-15-18-release-keys-signed-Boost-US.sbf
Where i can find correct checksums for comparison?
Hmm. I thought I saw them on the download pages. When I get home today I will check the checksum of my boost sbf. Just to compare. I don't have the sprint one though.
Sent from my MB612 using xda app-developers app
I have the same problem, please help me!
After falshing, Turn off your mobile. press R + M + Power key. you will get into motorola recovery. Do a data wipe/factory reset and reboot again... It always bootloop whenever i flash the sbf also. It should fix it.
just flash bootloader BL_0402_cdma_kronous_HS_generic_signed_Consumer_replacer.sbf
https://docs.google.com/file/d/0BwQkFb0zEZ3iRUMwLTFtdXJSX28/edit?usp=sharing
it always helps
rongsang said:
After falshing, Turn off your mobile. press R + M + Power key. you will get into motorola recovery. Do a data wipe/factory reset and reboot again... It always bootloop whenever i flash the sbf also. It should fix it.
Click to expand...
Click to collapse
nonono666 said:
just flash bootloader BL_0402_cdma_kronous_HS_generic_signed_Consumer_replacer.sbf
https://docs.google.com/file/d/0BwQkFb0zEZ3iRUMwLTFtdXJSX28/edit?usp=sharing
it always helps
Click to expand...
Click to collapse
I've been doing it all, but in result i get after few minutes logo M error in bootloader
Bootloader
04.02
Err:1B,00,02,00,00
Battery OK
OK to Programm
Connect USB
Data Cable
Click to expand...
Click to collapse
Janushkevich said:
I've been doing it all, but in result i get after few minutes logo M error in bootloader
Click to expand...
Click to collapse
You cannot flash 2.2.2 after you have flashed 2.3.5.
After flashing 2.3.5 get into recovery and do a data/factory reset.
Sent from my MB612 using xda app-developers app
http://www.mediafire.com/?077aa2bbe3kxg63
1FF-p3_kronos_cdma_kronos-user-2.3.5-4.5.1-110-KNS-46-49-test-keys-signed-Sprint-US.sbf
yes, always do full wipe from recovery
then get root and flash rongsangs cm7
Janushkevich said:
I have the same problem, please help me!
Click to expand...
Click to collapse
today i had a bootloop
but when i insert microsd back, it worked
I had the same boot load error. You have to use 2.3.5 since you have already flashed to it once, you cannot back up to froyo.
Is your phone a boost or sprint?
Sprint can be flashed with either the sprint sbf or the boost sbf, But Boost can only be used with the boost mobile.
Reflash 2.3.5 and do a full wipe on the phone and it should fix the problem.

Is my sister's phone officially dead?

She told me today that the phone wouldn't boot after most of her apps stopped working. Normally, I would factory reset since her phone isn't rooted, but it didn't work. I then tried to flash the latest firmware with RSDlite. After flashing, the phone stays on the motorola logo. Its suprising that my phone works just fine after one flash. I've tried flashing her phone to stock for three time already and no success. Is her phone offically dead or am I doing something wrong?
ozeyguy said:
She told me today that the phone wouldn't boot after most of her apps stopped working. Normally, I would factory reset since her phone isn't rooted, but it didn't work. I then tried to flash the latest firmware with RSDlite. After flashing, the phone stays on the motorola logo. Its suprising that my phone works just fine after one flash. I've tried flashing her phone to stock for three time already and no success. Is her phone offically dead or am I doing something wrong?
Click to expand...
Click to collapse
no errors RSD Lite nor on phone?
Sent from my KFFOWI using XDA Labs
sd_shadow said:
no errors RSD Lite nor on phone?
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
Everything was a go. I flashed the "VZW_XT907_4.4.2-KDA20.62-15.1_CFC_1FF.xml" firmware, and it still gets stuck on the splash screen.
ozeyguy said:
Everything was a go. I flashed the "VZW_XT907_4.4.2-KDA20.62-15.1_CFC_1FF.xml" firmware, and it still gets stuck on the splash screen.
Click to expand...
Click to collapse
Could try house of moto, but it could be hardware failure
Sent from my KFFOWI using XDA Labs
sd_shadow said:
Could try house of moto, but it could be hardware failure
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
Tried the House of Moto. Can still go to recovery but won't go past the splash screen.

Categories

Resources