[Q] Motorola XPRT stuck at Motorola Logo - Droid Pro General

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.

Related

[Q] Droid x stuck at M logo please help

I flashed to GB from stock, i went to try a fission rom, wiped data and flashed and now im stuck on M logo. Ive seen prior posts on this problem and followed instruction on loading the sbf file thru rsd lite. So i did that, it executes the whole flash process and reboots my phone and that execution goes to 100% and it tells me to power my phone up manually. Heres the problem when it rebooted my phone it got froze at logo again and i could do nothing but pull battery. So is there any thoughts or advice as to what maybe im doing wrong or another way to get my phone up and running? THANX
Also i cant boot into clockworkmod only android system recovery...is this maybe why its not working?
go into recovery and wipe data/factory reset. Then reboot.
jgraham4598 said:
go into recovery and wipe data/factory reset. Then reboot.
Click to expand...
Click to collapse
I did try that it was one of the first methods tried it didnt help...Thanks for the reply tho
Scitzo382 said:
I did try that it was one of the first methods tried it didnt help...Thanks for the reply tho
Click to expand...
Click to collapse
What version of bootloader are you on? What version of SBF are you using?
bigshotrob22 said:
What version of bootloader are you on? What version of SBF are you using?
Click to expand...
Click to collapse
Bootloader 30.04 and sbf SHADO_X6_ 2.3.34
Scitzo382 said:
Bootloader 30.04 and sbf SHADO_X6_ 2.3.34
Click to expand...
Click to collapse
I believe that's the system only. You need the full sbf file
Sent from my DROIDX using XDA App
I replied to your post in the other post... anyway, yes you need to try wiping (multiple times) and then if that doesn't work, SBF, you can find SBF downloads on site in my sig.
bigshotrob22 said:
I believe that's the system only. You need the full sbf file
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
o If you have already flashed 2.3.32, and/or have 30.04 bootloader: 2.3.34 SYSTEM ONLY SBF:
• DIRECT LINK TO SBF: http://www.megaupload.com/?d=OXK9Q1ZG
i was going by that in SystmeAdmin-X's noob to droid x post sice i had 30.04 i used system only....will it be safe to do the full 2.3.32
snwagner said:
I replied to your post in the other post... anyway, yes you need to try wiping (multiple times) and then if that doesn't work, SBF, you can find SBF downloads on site in my sig.
Click to expand...
Click to collapse
Yes im new to forums this my first posts i realized after the fact that i should started a new thread so did....thanx for the replies i have tried several wipes and tried sbf with rsd lite. i used 2.3.34 since i have 30.04 boot loader and i still got stuck at M logo...should i do full file 2.3.32 with 30.04 bootloader?
Scitzo382 said:
Yes im new to forums this my first posts i realized after the fact that i should started a new thread so did....thanx for the replies i have tried several wipes and tried sbf with rsd lite. i used 2.3.34 since i have 30.04 boot loader and i still got stuck at M logo...should i do full file 2.3.32 with 30.04 bootloader?
Click to expand...
Click to collapse
You need to full sbf in order for your phone to work. The system only wil not work if you came from GB.
Sent from my DROIDX using XDA App
bigshotrob22 said:
You need to full sbf in order for your phone to work. The system only wil not work if you came from GB.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
OK thank you i will try that right now and post results
Thanks a million times over to Bigshotrob22 and snwagner, The full file worked like a charm u guys are awesome thanks for the support i got my baby back
Scitzo382 said:
Thanks a million times over to Bigshotrob22 and snwagner, The full file worked like a charm u guys are awesome thanks for the support i got my baby back
Click to expand...
Click to collapse
No problem...For future reference if your on froyo and you do the system only sbf it will work. The reason why you had to do the full sbf is because GB changes the stock recovery and other files I can't remember off the top of my head.
Sent from my DROIDX using XDA App

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

Briked my phone?

I think i bricked my Droid X. i was running Rubix Focused and tryed to flash GingerAle 3.0 and now it just sits at the moto "M" logo. i can get into the recovery by pulling the battery but even after a wipe and a recovery it still just sits. did i brick it, and if so how can i fix it? please help, reletivly new to flashing roms.
P.S. I'll love you forever if i can fix it =)
now i think i really did it. I tried running a recovery image from a few days ago and now i cant get back into the recovery menu...
Sounds Like SBF Time
Sounds like SBF is going to be your friend here, if you don't know how, head to
http://forum.xda-developers.com/showpost.php?p=11118819&postcount=2
and look for "SBF: What is it, and what does it do?!?"
OK, so i SBFed the phone, got all the way through it, got to the phone is rebooting and it just sits at the Moto "M" again. did i SBF wrong or what?
EDIT: I can get into the stock recovery... sort of. i can get to the ! with the droid next to it but nothing happens when i push the search button.
hmm, I know GB doesnt use the search button to pass that, try using vol UP+DOWN at the same time. perhaps the stock recovery isn't modified from SBF?
Woot that worked. got into recovery. wiped data and tryed a reboot, got stuck at logo again. should i try flashing back to the Rubix focused i had before?
Edit: it now boots into <3e> recovery and i get the e: signature verification failed instillation aborted when i try to install Rubix or Gingerale.
You can't install a custom roms from stock recovery
Sent from my DROIDX using XDA Premium App
try doing a full wipe data/cache a couple of times. that usually works for me
Sent from my DROIDX using the XDA mobile application powered by Tapatalk
YAY
Fixed it!!! yay!! I had to flash the full SBF file, not just the system one. thanks for the help guys
thats ur best bet. full sbf
Sent from my DROIDX using the XDA mobile application powered by Tapatalk

Boot Loop after unlocked bootloader

As the title says, After I unlocked the bootloader, and flashed a 2.3.4 rom, My Atrix sometimes will go up to the blur phase of the boot and then it will restart, but most of the time will just do a boot loop on the Red Moto Logo at boot, I can go into fastboot and recovery no problem...
Thanks on any help...
same thing
i get the same thing every now and then but i can get fastboot and recovery so im good i guess.
Did you wipe before you installed your ROM?
Do a fastboot -w then reinstall your ROM.
also do a factory reset and make sure your on the newest recovery
quicklyspent said:
Did you wipe before you installed your ROM?
Do a fastboot -w then reinstall your ROM.
Click to expand...
Click to collapse
Did the fastboot -w and reinstalled the ROM and it is doing the bootloop the same, first boot goes up to the blur phase and reboots, and afterwards just does the boot loop up to the motorola dual core red logo.
TechnoNeto said:
also do a factory reset and make sure your on the newest recovery
Click to expand...
Click to collapse
I have the latest recovery, thanks...
Flash back to stock and follow my guide
Sent from my MB860 using XDA Premium App
TechnoNeto said:
Flash back to stock and follow my guide
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Where can I find your guide, and should I SBF 1.83 or what..
It's in general under video how to go... Sorry I'm on my phone
Sent from my MB860 using XDA Premium App
http://forum.xda-developers.com/showthread.php?t=1179506
Sent from my MB860 using XDA Premium App
Did you make sure to use tenfar's CWM instead of ROM Manager's? My 2.3.4 install also bootlooped, and that ended up being the issue.
Sent from my ATRIX running CherryBlur 1.3.
I'm still having issues, I have the latest Recovery, and I have tried to flash through Recovery and still get the boot loops...
Just Flashed via RSD the SBF 1.2.6 and still have the reboots, I think that my phone it's bricked, I can go into RSD, Fastboot, Recovery, everywere, I can flash anything, but when it boots, it does a bootloop everytime... I
If someone has an answer please help...
poorg said:
Just Flashed via RSD the SBF 1.2.6 and still have the reboots, I think that my phone it's bricked, I can go into RSD, Fastboot, Recovery, everywere, I can flash anything, but when it boots, it does a bootloop everytime... I
If someone has an answer please help...
Click to expand...
Click to collapse
Take out the battery for 30 sec and then put it back press vol up while you turn on.... can you please post what it show up in your screen after this?
Sent from my MB860 using XDA App
mramirezusa said:
Take out the battery for 30 sec and then put it back press vol up while you turn on.... can you please post what it show up in your screen after this?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Starting RSD protocol support....
poorg said:
Starting RSD protocol support....
Click to expand...
Click to collapse
Ok I will post a guide and follow up give 1 minute
Sent from my MB860 using XDA App
mramirezusa said:
Ok I will post a guide and follow up give 1 minute
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Thanks for the help, really appreciate this...
poorg said:
Thanks for the help, really appreciate this...
Click to expand...
Click to collapse
Ok maybe is time for clean starp up, DEEP CLEAN, I did this script for a friend and it help:
Need Windows PC and UNLOCKED BOOTLOADER (when I said unlocked bootloader need to be that everytime you boot you saw "unlocked" tag at the left top corner)
1. Download and extract/unzip the following file in a new folder (example C:\atrix):
http://www.filesonic.com/file/15073...signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
2. You will end after extracted/unzip the file with something like this:
1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf
3. Download this file "CLEAN_2.3.4_ATT.zip" and extract/unzip to the same location (example C:\atrix)
http://forum.xda-developers.com/attachment.php?attachmentid=673330&d=1312203457
5. Run the script "clean" and follow exactly all the instrucctions!
6. This will install a Pristine Official ATT GB 2.3.4/4.5.91
Done!
Hope it help
mramirezusa said:
Ok maybe is time for clean starp up, DEEP CLEAN, I did this script for a friend and it help:
Need Windows PC and UNLOCKED BOOTLOADER (when I said unlocked bootloader need to be that everytime you boot you saw "unlocked" tag at the left top corner)
1. Download and extract/unzip the following file in a new folder (example C:\atrix):
http://www.filesonic.com/file/15073...signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
2. You will end after extracted/unzip the file with something like this:
1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf
3. Download this file "CLEAN_2.3.4_ATT.zip" and extract/unzip to the same location (example C:\atrix)
http://forum.xda-developers.com/attachment.php?attachmentid=673330&d=1312203457
5. Run the script "clean" and follow exactly all the instrucctions!
6. This will install a Pristine Official ATT GB 2.3.4/4.5.91
Done!
Hope it help
Click to expand...
Click to collapse
Ok, but mine does not say unlocked right now, I did Unlock the bootloader but after I flashed the 1.2.6 SBF it does not say it!!!!
I noticed you posted that you actually have unlocked bootloader just make sure that when you turn on the phone it said in the left top corner "unlocked", if it is not that case just follow intructions on this post:
http://forum.xda-developers.com/showpost.php?p=15930466&postcount=1
download the script and select option 1 from the main menu and then option 3 and complete all the steps
so you can re unlocked the bootloader
then follow the instrucionts that I posted before here
mramirezusa Thank You.... As you stated, everything went smoothly and my phone it's perfect again, something I noticed, when it boots, it's does not say unlocked anymore shoul'd I do the procedure with the the script that you sent posted above...

Cwm recovery issues

Hey guys, i have a few weeks experience flashing and all that leet stuff, but it seems i have a problem! I started to modify my ATRIX on 2.3.4, i unlocked sim, rooted, unlocked bootloader, and flashed custom recovery. I played around with a few roms, then i decided to update my fw to 2.3.6, well before i could do that i had to undo all mods so i ended up flashing a stock 2.3.4 fw and upgraded OTA. Im pretty sure that was my mistake... i may have needed an unlocked 2.3.6 sbf.. i re-rooted, and flashed cwm with rom manager, now when i go to boot in recovery mode i get failed to boot 2 starting rsd protocol. Everything is fine i just need to know where i messed up and how to get cwm running again. P.S. ive also been having an issue with my camera! I open the cam app and i get black screen, factory reset does NOT fix! Ive seen post's saying that the module is bad if that does not work BUT, when using flashlight app the flash lights up for a sec and then shuts off. When i switch to front camera it will stop responding, i'll click wait and after a min it will show image and i can take a pic(only with front cam). If i could get both issues solved i would be very grateful! If any other info is needed ill be sure to respond asap! Thank you in advanced for reading and assisting with my issues!
Sent from my MB860 using XDA
Get the cwm recovery img & flash with Fastboot and that should fix your recovery.
Sent from my MB860 using Tapatalk 2
Thanks for a reply but I did that as well and ended up getting an error. "Failed to process command flash:recovery error(0x180002)". I tried this method at first, received that error then tried to flash cwm through rom manager and recieved failed to boot2 starting rsd protocol.
Sent from my MB860 using XDA
Try unlocking bootloader again just to make sure ... Maybe that factory firmware closed hole on you when flashed.. Then flash cwm image ....
xRawwRRRRx said:
Thanks for a reply but I did that as well and ended up getting an error. "Failed to process command flash:recovery error(0x180002)". I tried this method at first, received that error then tried to flash cwm through rom manager and recieved failed to boot2 starting rsd protocol.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
XRange said:
Try unlocking bootloader again just to make sure ... Maybe that factory firmware closed hole on you when flashed.. Then flash cwm image ....
Click to expand...
Click to collapse
+1. You'll always need to re-flash pudding BL after using an .sbf.
ghost_og said:
+1. You'll always need to re-flash pudding BL after using an .sbf.
Click to expand...
Click to collapse
Would you happen to have the file? 2.3.6
Sent from my MB860 using XDA
xRawwRRRRx said:
Would you happen to have the file? 2.3.6
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Think what you seek lies here in Puddling thread..
http://forum.xda-developers.com/showthread.php?t=1136261
XRange said:
Think what you seek lies here in Puddling thread..
http://forum.xda-developers.com/showthread.php?t=1136261
Click to expand...
Click to collapse
adding to this: the automatic unlocker should work for you too. I had to re-unlock my phone after Motorola upgraded it when it was out for repairs. Worked like a charm.
(IF you're on AT&T)
ghost_og said:
adding to this: the automatic unlocker should work for you too. I had to re-unlock my phone after Motorola upgraded it when it was out for repairs. Worked like a charm.
(IF you're on AT&T)
Click to expand...
Click to collapse
Thank you soo much! I had to "re-unlock" bootloader! Now i have my custom recovery! One more thing have you or any other reader out there figured out a solution to my camera problem?
Sent from my MB860 using XDA
Try one custom roms see if that fixes camera, if not you might have carry phone for bad camera...

Categories

Resources