Jump to content


Photo

motorola Q stuck at bootloader

- - - - -

  • Please log in to reply
6 replies to this topic

#1
kailm

kailm

    Newbie

  • Members
  • Pip
  • 3 posts
  • Devices:q
I left my motorola Q to charge.
When I checked few hours later it was at the bootloader flash
prompt.

motorola flash mode
bootloader version:
boot_c_03.05.00R_mpap

please connect usb cable.

I tried power cycling many times, removing battery, putting in a charged battery
from another Q. No go at all.

I believe there is a bug that fried the rom while charging? I have seen others
have same issue other threads/forums.

I also tried using motorola Q update software it finds the Q
and tries to update it.
but it errors out after doing
ipl write successfully
mbm write successfully, powers off, then repeat cycle.

  • 0

#2
kailm

kailm

    Newbie

  • Members
  • Pip
  • 3 posts
  • Devices:q
here is the flash error and flash debug file outputs from the software update


05:06:00, June 07, 2007
Line: 5080
ERROR: Phone[0000]: Error checking the RAM Downloader.
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0

05:06:00, June 07, 2007
Line: 6155
ERROR: Phone[0000]: Error jumping to RAM Downloader
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0

05:06:00, June 07, 2007
Line: 1662
ERROR: Phone[0000]: Error flashing subscriber unit. Device API Error: 0xE0030009 Address: 0x9CBFF800 Command: ADDR
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0

05:06:00, June 07, 2007
Line: 3551
ERROR: Phone[0000]: Flash failed.
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0

05:06:00, June 07, 2007
Line: 573
ERROR: Flash failure: Phone[0000]: Error checking the RAM Downloader. (Error Code: 9f),
Detailed Error Details: Direction of the Error=No Direction, Command Value=0, Code Group Number=No Codegroup
File: X:\test_dev_usb\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0

05:06:00, June 07, 2007
Line: 573
ERROR: Flash failure: Phone[0000]: Error flashing subscriber unit. Device API Error: 0xE0030009 Address: 0x9CBFF800 Command: ADDR (Error Code: e0030009),
Detailed Error Details: Direction of the Error=1000, Command Value=200000, Code Group Number=40
File: X:\test_dev_usb\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0

===================

05:05:22, June 07, 2007
Line: 371
Status: PST_DISP_PROG
File: X:\test_dev_usb\flash\code\flashdll\Progress.cpp

05:05:23, June 07, 2007
Line: 371
Status: PST_DISP_PROG
File: X:\test_dev_usb\flash\code\flashdll\Progress.cpp

05:05:24, June 07, 2007
Line: 5638
Status: Phone[0000]: Waiting for re-enumeration
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp

05:05:47, June 07, 2007
Line: 2733
Status: Phone[0000]: Erasing flash memory.
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp

05:05:47, June 07, 2007
Line: 1309
Status: Phone[0000]: Loading RAM Downloader for Bootloader.
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp

05:05:48, June 07, 2007
Line: 371
Status: PST_DISP_PROG
File: X:\test_dev_usb\flash\code\flashdll\Progress.cpp

05:05:55, June 07, 2007
Line: 2836
Status: Phone[0000]: Erase Complete.
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp

05:05:55, June 07, 2007
Line: 4532
Status: Phone[0000]: Flashing Code Group 32
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp

05:05:55, June 07, 2007
Line: 4572
Status: Phone[0000]: Code Group 32 flashed.
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp

05:05:55, June 07, 2007
Line: 4532
Status: Phone[0000]: Flashing Code Group 33
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp

05:05:55, June 07, 2007
Line: 626
Status: Phone is processing data, please wait.
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_Flash.cpp

05:05:57, June 07, 2007
Line: 4572
Status: Phone[0000]: Code Group 33 flashed.
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp

05:05:57, June 07, 2007
Line: 4532
Status: Phone[0000]: Flashing Code Group 34
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp

05:05:57, June 07, 2007
Line: 626
Status: Phone is processing data, please wait.
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_Flash.cpp

05:05:59, June 07, 2007
Line: 4572
Status: Phone[0000]: Code Group 34 flashed.
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp

05:05:59, June 07, 2007
Line: 4532
Status: Phone[0000]: Flashing Code Group 40
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp

05:06:00, June 07, 2007
Line: 5080
Status: PSTDisplay_Error
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp

05:06:00, June 07, 2007
Line: 1662
Status: PSTDisplay_Error
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp

05:06:00, June 07, 2007
Line: 6155
Status: PSTDisplay_Error
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp

05:06:00, June 07, 2007
Line: 1825
Status: Phone[0000]: BP Failed
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp

05:06:00, June 07, 2007
Line: 1825
Status: Phone[0000]: AP-OS Failed
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp

05:06:00, June 07, 2007
Line: 3551
Status: PSTDisplay_Error
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp

05:06:00, June 07, 2007
Line: 371
Status: PST_DISP_PROG
File: X:\test_dev_usb\flash\code\flashdll\Progress.cpp

  • 0

#3
motogeek

motogeek

    Newbie

  • Members
  • Pip
  • 2 posts
  • Devices:moto q
Sounds like you bricked it. I hope it is under warranty. Maybe take it to your service provider to see if they can help. :)

  • 0

#4
cholman97

cholman97

    Newbie

  • Members
  • Pip
  • 2 posts

Sounds like you bricked it. I hope it is under warranty. Maybe take it to your service provider to see if they can help. ;)



There has to be a better way... I work for a cellular provider and have seen a few come in that are stuck in the bootloader mode. Yes you will get a replacement phone, YES it is refurbished, YES I think that policy sucks too. I have spent hours of my life looking for an answer to this problem and have not found one creadible answer. Standard hard reset, press and hold center action button while holding red power button, does not work. Motoroloa nor Microsoft seem interested in providing a ROM replacement. IMHO there has to be a better answer than take it in for a replacement.

anyone? anyone? Buler?

  • 0

#5
kailm

kailm

    Newbie

  • Members
  • Pip
  • 3 posts
  • Devices:q

There has to be a better way... I work for a cellular provider and have seen a few come in that are stuck in the bootloader mode. Yes you will get a replacement phone, YES it is refurbished, YES I think that policy sucks too. I have spent hours of my life looking for an answer to this problem and have not found one creadible answer. Standard hard reset, press and hold center action button while holding red power button, does not work. Motoroloa nor Microsoft seem interested in providing a ROM replacement. IMHO there has to be a better answer than take it in for a replacement.

anyone? anyone? Buler?


Its been awhile since i posted that above. Anyway update to those in this situation.
So the phone was definitely bricked. I got it replaced from the sprint store they charged me $40.
Other way was to send the phone back to motorola and get another (warranty). I didnt want to play the waiting game
and be without a phone. So $20 for shipping vs $40 to get it now was good.

I do believe the rom got fried. I left it charging on the charger, only think i can say is probably some electric surge
came through wall then the charger fried the phone. I know it sucks but stuff happens, use surge protector even with
your phones ppl ;)

I dont think they can provide rom replacement as the chip is on theboard and impossible to take off. You need a new board
hence a new phone.

  • 0

#6
Wavelabs

Wavelabs

    Newbie

  • Members
  • Pip
  • 8 posts
  • Location:New York City
  • Interests:Indycar Racing<br />Champcar Racing<br />Formula-1 Racing<br />Trance Music<br />Females, Females, Females.<br />Lamborghini Marcielago LP640<br />Liveforspeed.com<br />trackmanianations.com
  • Devices:MOTO-Q9H Global - AT&T
Same thing happend to me, I was installing a small plugin called SRS WOW plugin.
and it totally fried my phone, bricked the hell out of it.

Lucky when I went to AT&T they where nice enough to give me a brand new phone, because all their
refurbished phones , they where out of. they said too many customers came in that week with Briked phones,
So they gave me a new one.

So there is another Word of Advice, be very careful what you install.
Motorola contacted AT&T back and said that a program
I installed wrote code in the main System OS or Hardware I don't remember and crapped it out.

Thats what AT&T told me when they called me about a week later about it.
as I still had a ticket number they forgot to close out.....lol

Edited by Wavelabs, 14 February 2008 - 11:17 AM.

  • 0
1 - If at first you don't succeed, distroy all evidence that you tried.
2 - I had a life, now I have a modem and a computer.
3 - In life always pass it forward.

#7
gmanvbva

gmanvbva

    Newbie

  • Members
  • Pip
  • 1 posts
I have had this happen twice now. Both times were while charging during the night.

On occasion the phone will not charge correctly during the night. It seemed that if I left the phone on the charger while trying to reboot (or power on), it had a chance of bricking and going to the autoloader screen. Both times were with different chargers and batteries. The first phone that did this worked on and off (bootloader screen, then worked fine, repeated) over the last few days before it finally died.

Now, if the phone does not charge properly in the evening I unplug it before powering on. It might not be the real reason, but I haven't had one brick on me since.

Edit: On both of these occasions, nothing was recently installed.

Edited by gmanvbva, 28 May 2008 - 05:59 PM.

  • 0




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users