Unmodded V3m is like an angry girlfriend

[achilles381]

My phone is unresponsive and stubborn.

I went for a road trip Saturday, and on my way home I discovered my V3m wasn't working properly. Apparently it didn't like the fact that I dragged it up to Dairyland for a day, maybe I should buy it flowers?

When I first found it, the outer screen was on, but blank, and the main screen only showed the "Verizon Wireless" image. The keypad was lit, but unresponsive, so I removed the battery. When I turned the phone on again, I still got the same result. I have since tried charging it, left the battery out overnight, talked to the robots who work at Verizon stores and kiosks, taking it apart, reassembling it, cursing at it, and throwing it on the floor. None of those have worked so far.

I learned from here how to press * and # and the power button, and it will show the Bootloader USB Init screen. MPT 5.0 claimed it didn't support my phone. MPT 4.5 claimed it couldn't locate my phone. BitPim says my phone's modem status is "active: false" and "available: false".

The closest thread I could find to my symptoms with a search was this:

http://www.howardforums.com/showthre...&highlight=v3m

But my phone was not exposed to moisture. Lots of other threads deal with modified phones, mine is as it came from Verizon many moons ago.

So for the sake of my man-phone relationship, is there anyway to bring the love back? I would love to make phone calls again, or at least recover my contacts, and maybe that movie I took of my step mother's cat being a jerk.

Thanks in advance!

[hyelton]

one thing its either dead or not. it needs to be flashed but everything on it will be LOST

[achilles381]

one thing its either dead or not. it needs to be flashed but everything on it will be LOST

I was hoping for a third option, rather than dead or not, how about purgatory?

You mean I'll lose my precious movies of angry kitty?

After paging through many threads ending with unanswered questions, I found I needed the right usb driver which I found on Motorola's support site. Now at least RSD Lite can communicate with my phone, but...

I've been trying to flash it with the NEWC_01.09.02 I found here:

http://www.humpa.com/vzw/

But it fails with the "error flashing subscriber unit" error every time right around 95%.

In the past 8 hours I have learned more than I ever needed to know about fixing a Motorola V3m.

A few more flash tries and I start shopping for a fresh phone.

[achilles381]

Model - Flash MSM6500

Port No. 1

Port Type USB

IMEI / ESN / MEID - N/A

Satus - Failed Flashing Process. Failed Flashing process. Phone[0000]: Error flashing subscriber unit. Device API Error: 0xE0030009 Address: 0x135C000 Command: ADDR (0XE0231009); phone connected.

Progess: Executed:100%

Result - FAIL

Fail indeed....

[achilles381]

Well seeing as this thread will eventually be buried in the binary abyss of the internet...

I will say for future people who search and find this lonely thread, that I was unable to rescue my slim silver folding sidekick of almost two years.

Services for the old phone will be held at a non-denominational location, and the phone will be buried in my junk drawer, joining its brother Moto, cousins LG and Nokia who came before it.

[UrbanBounca]

Have you tried putting your handset into bootloader mode, and flashing it with the original VZW firmware with RSD Lite? RSD Lite can be found by a simple Google search.

[achilles381]

Have you tried putting your handset into bootloader mode, and flashing it with the original VZW firmware with RSD Lite? RSD Lite can be found by a simple Google search.

I stated above that I was using RSD Lite to try and jolt my Moto out of its self-induced coma.

The problem with just saying "google RSD Lite" is that noobs like me who search find that in every thread, and still have no idea how to use it. So for the next person who searches, I will make your life easier by posting this:

http://wiki.howardforums.com/index.p..._with_RSD_lite

RSD Lite would not recognize my phone unless it was in bootloader mode. As stated above, I tried the original firmware. Then I tried an updated firmware, and finally a "monster". None of those took, the latter two never got past 50% progress.

So I gave up and bought a fruity touch screen phone.