So I was trying to flash a Sprint branded Q to the Vivo firmware.
I had problems getting the moto drivers for the Q to load properly. Downloaded them 3 times from the moto site and still nothing. Not even manually pointing them to where they should be stored on the harddrive allowed them to be found.
On the advice of a member: http://howardforums.com/showpost.php...&postcount=117 - I downloaded Microsofts Software Update hoping it would allow the Q to be recognized. No luck. Still didnt see it.
Finally I loaded MS Actisync and that mounted the phone but only as a generic mobile device. It did however let MSU see the phone. MSU didn't let me update the software because it was out of warranty but it saw the phone.
I gave running RSD lite 3.2 a shot at that point. Booted the phone up in flash mode (using the A + return key combo) and tried to load the Vivo firmware. Somewhere along the line it failed.
Since then when i turn the phone on it only reads: "msystems could not locate master" over the yellow Sprint startup screen and stays there until i take out the battery.
Several tries to flash it again with the Vivo, Alltel, and VZ firmware for the Q all fail.
The phone gets to the Initializing BP and after that something goes bad.
RSD reports the "Flashing code group 1" (sometimes get to group 2) gets executed somewhere in the 7-15% area before the error messages begin.
One of these two errors show up in RSD:
"Failed flashing process. Error eraing subscriber unit. device api error 0xe003003b command: ERASE. OR
"Failed flashing process. Phone [0000] Error checking the RAM downloader [0x9F] phone disconnected"
The first error message appears when the process takes the longest and seems to be going along okay. ~10-15 min and the phone stays on and reads Initializing BP and RSD can sometimes lock up.
When I get the second error message its usually early on in the attempt. Maybe 60-90 seconds in. And the phone shuts down on its own. Right before it does the phone reports that the ipl and mbm get written successfully (don't know what they are) and then turns off.
The battery was fully charged and since it uses the same type as my W385 i can keep charging the battery to retry the process but I am out of ideas on what more I can do. And the phone worked fine before all this.
Looks like it has been a while since you have posted it, but I was wondering if you had any luck?
If no, then I can give you one advise.
If you trying to flash any motorola phones from Sprint, always do upgrade flash using Sprint Upgrade monster flash and then flash it with Verizon monster. After that you can flash to any other monster's - cricket, US cellular etc.
Also, if you still have no luck, try to use downgrade version of RSD lite. 3.4 has always worked for me.
Cheers
Looks like it has been a while since you have posted it, but I was wondering if you had any luck?
If no, then I can give you one advise.
If you trying to flash any motorola phones from Sprint, always do upgrade flash using Sprint Upgrade monster flash and then flash it with Verizon monster. After that you can flash to any other monster's - cricket, US cellular etc.
Also, if you still have no luck, try to use downgrade version of RSD lite. 3.4 has always worked for me.
Cheers
Im trying your solution, hope it work... I wil post results
Failed Q flash bricked the phone
Reply With Quote
Originally Posted by johnconnor
Bookmarks