Froyo OTA bricked phone?

[n0m0n]

Sounds like the right files. I tweeted to P3, Birdmann and a couple others that you have this file, I am sure one of them will contact you soon. I see you are on MDW as well so you can contact P3 via PM.

You would need to dl the OTA but not install it. It should be stored on the cache folder not the sd card. You will them need to copy it to your sd card and then transfer it to your computer before returning your phone. You will need to use Root Explorer or adb to do this.

There are 267 files.
Is that right?
I downloaded via root explorer copied all the files from within the cache folder to a folder I created on my SDCard.
Moved that folder to my PC.

267???
Shouldn't there be 1 file?

Now I am clueless to most of this and hobble when rooting or making some of these changes as you guys fly so bare with me on the elementary question PLEASE.

Do I do anything to make them 1 file?
Am I wrong to think that this is a SBF file or what?

Thanks

OK they are on my PC and waiting for contact.

Thanks

 

[la2texas]

Soooo

Man I'm so mad - wish I woulda read this thread first. So I had a rooted 2.1 X, installed update - was running fine (although slowwwww and buggy). I hated it - 2.1 was so responsive, quick - like a phone should be - 2.2 locked up, quit responding, etc... . Knowing the little bit I know (enough to tear stuff up) - I found the 2.1 sbf - followed some instructions and are now getting the 30.03 Bootloader:
Err:A5,70,70,00,1F

.....

MEM_MAP Blank

Wondering what I should do now? Just chill and wait for a 2.2 sbf? Or maybe try the leaked 2.2? If I go to a verizon store with this phone to get it fixed claiming "the update did it" - are they going to freak out and jack with my wifes parents contract?

 

[chinton]

I had this same thing happen. I went to the Verizon store and told them what happened. The guy took one look at the phone and told me I was going to need a new one. He walked.over to the counter and put me in for a replacement. I received it the next day.

In conversation he told me that they were expecting a few bricks due to the update. Apparently they had similar issues when the droid 1 cam out.

 

[Kentech0023]

I was running stock 2.1 and once I upgraded to 2.2 the same thing is happening to me except it happens randomly and so far I've had to pull it twice in less than 24 hours of having 2.2.

 

[la2texas]

I had this same thing happen. I went to the Verizon store and told them what happened. The guy took one look at the phone and told me I was going to need a new one. He walked.over to the counter and put me in for a replacement. I received it the next day.

In conversation he told me that they were expecting a few bricks due to the update. Apparently they had similar issues when the droid 1 cam out.

So yours was rooted and had the same message on the screen after update (Err:A5,70....etc..)? Did you tell them you rooted it, or just that the update did this to your phone?

 

[chinton]

double post. see condensed below

 

[chinton]

I condensed my first post and not sure if my reply went so here it is again.

1.I was unrooted.
2.Upgraded phone
3.Locked up during phone call
4.Batt pull
5.Stuck at m and thought it was bricked
6.Read froums to flash to 2.1 and then bricked it for real
7.Called Verizon and got passed to motorola.
8.talked to level 1 tech and was escalated to level 2
9.Sat on hold for level 2 tech and gave up after 30min of waiting
10.Went to Verizon store and told them what happened. (2-9)
11.New replacement ordered

Sent from my DROIDX using Tapatalk

 

[la2texas]

Thanks man. Im going to head up there shortly - the store I got it from was walmart (only ones who had an x in stock in my town) - they probably wont know much about the process anyway so.

 

[chkmate]

Sorry if this isn't related. Brand new X out of the box. Programed it, ran backup assistant and then grabbed official 2.2 update from Verizon. Downloaded fine, restarted and finished unpacking files. After a very long time I felt a vibration and could hear the eye loading up, still on /\/\ screen. Gave it another 10 minutes and popped battery. Started right up running Froyo smooth. But every time I restart I have to pop batt. or it will stick on /\/\.

FYI, when first unpacked the /\/\ was very dim, not bright. They are sending me a new one once again. Gonna take it to Verizon when I get it and let them do it so there are no other questions.

 

[la2texas]

I condensed my first post and not sure if my reply went so here it is again.

1.I was unrooted.
2.Upgraded phone
3.Locked up during phone call
4.Batt pull
5.Stuck at m and thought it was bricked
6.Read froums to flash to 2.1 and then bricked it for real
7.Called Verizon and got passed to motorola.
8.talked to level 1 tech and was escalated to level 2
9.Sat on hold for level 2 tech and gave up after 30min of waiting
10.Went to Verizon store and told them what happened. (2-9)
11.New replacement ordered

Sent from my DROIDX using Tapatalk

Walmart didnt have any to replace with, and wouldnt order another saying I will just have to wait until one comes in (ha). Took out sd, went to verizon and told them the update did this to my phone (left the Err:A5 screen) - they took it to the back for about an hour trying to flash it, gave it back to me with 29.01 bootloader (instead of 30.03) - with it still not fixed. They ordered another one to come to the house by next tues/wed. Funny thing is they gave this one back - wonder if I have to ship it back when the other comes?

 

[rmcomer]

Yes, once you get the replacement phone, you send back your original phone in the same package with the included FedEx return label. You have 10 days from receipt of phone to send your's back.

 

[la2texas]

Question

While I have this bricked phone, I would like to mess around with it. Can anyone point me to how to get into the low level programming of it? I am a 3'rd year computer science student and would really like to get my hands on some x. This would look wonderful on my resume im sure :>.

 

[skydivewags]

It happens part of the problem here is the CPU is getting pretty darn hot during this UPDATE as with anything electronic if it gets too hot bad things happen. It is not Verizon Or moto's fault if the CPU was already warmer then normal when the update took place. The stores should have a very minimal supply of X on hand I agree with you on that point.

You are exactly correct. I have a Droid X that is stock, and updated today (yesterday), and it came up with the M screen, and nothing else. Pulled the battery many times, waited up to 20min, still nothing. Went to Verizon store, and the guy started a Google search to figure out the problem, didn't get it. After it sat for a while another guy came over and pressed the start button, and it started up. I was happy to have a working phone again, but not feeling very confident for the long term.

He had the SD card out, and I wanted it back in, so decided to pull the battery an put it in. Damn! back where I started. Did many battery pulls, tried to get to the "triangle" screen, and that was actually there also, but only showed the M.

I spent an hour with a Verizon rep that said they have been getting a lot of calls with the same issue. We got nowhere.

Then after reading this, and putting things together, I realized I usually had the phone in my pocket, or hand, so it stayed warm.

I put it in the freezer for about 5 minuets, and It booted!!!!!!!dancedroid

I have had it not boot again after that, and did the same thing, and it worked. This is obviously a chip that is being pushed beyond it's capability. I now need a cooling system for my Droid X. Will call Verizon back and get a new phone on it's way, but for now, it works....

 

[djjsin]

just so you all know the outcome. I ended up calling verizon, and they sent me a replacement phone for my dad. Funny thing is...his account is a corporate account. He's not authorized to do anything on it. While i was pretending to be him, they asked me all these security questions. I told them i didnt know anything about how the company set the stuff up, all i know is that they updated my phone and now it doesnt work so i wanted a new one.

Got a new one sent out without problems

 

[la2texas]

Mine is also on its way, will be here tomorrow or wed.