PDA

View Full Version : bricked x because of 2.2 downgrade



00gt1
12-12-2010, 07:51 PM
So I got the message that 2.2.1 was available so I rebloated my phone and updated (still rooted). Everything went fine until I tried to reroot. Superuser was stuck on my phone even though it wasn't rooted so the new root would not take. A friend suggested I SBF it back to stock and then go from there. It seemed to make sense however aparently the sbf he used was not the current one, so not my phone is stuck in:


Bootloader mode
30.04
Err:A5,70,70,00,1F

MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Transfer Mode:
USB

I have quite literally tried about 5 different 2.2 .sbf files that I have found floating around here in the coinciding threads about this and every time, RSD claims that the flash passes... however the phone goes right back to that same bootloader screen and will not boot. Any suggestions? I am about on my wits end here and do not want to trade in my brand new phone for a "like new" replacement phone.

Thanks in advance for any help.

C Dippa
12-12-2010, 07:55 PM
You can't use a 2.2 sbf, since you are on 2.2.1. Check the first post in this thread...

http://www.droidxforums.com/forum/droid-x-hacks/11959-2-2-1-sbf.html
(http://www.droidxforums.com/forum/droid-x-roms/11959-2-2-1-sbf-3.html)

mpetruzz
12-12-2010, 07:56 PM
Try taking the battery out, holding down the home and power key and then put the batteru back in. Hold the buttons down till ou get the triangle. You can do a factory reset and that may get ou outta the loop.

Sent from my DROIDX using Droid X Forum App

00gt1
12-12-2010, 10:39 PM
Try taking the battery out, holding down the home and power key and then put the batteru back in. Hold the buttons down till ou get the triangle. You can do a factory reset and that may get ou outta the loop.

Sent from my DROIDX using Droid X Forum App

Thanks for the thought, but this does not work unfortunately, it was the first thing I tried

00gt1
12-12-2010, 10:42 PM
You can't use a 2.2 sbf, since you are on 2.2.1. Check the last post (post #24) in this thread...

http://www.droidxforums.com/forum/droid-x-roms/11959-2-2-1-sbf-3.html

Thanks i will try this right now and report back

jfederice
12-12-2010, 10:44 PM
im having the exact same problem. ive tried just about everything but im stuck on that same bootloader

Bootloader
30.04
Err:A5,70,70,00,1F

MEM_MAP Blank
Service Req'd
Battery OK
OK to program
Connect USB
Data Cable


if i figure it out please help me out. and same goes for if i figure it out ill hit u up

jfederice
12-12-2010, 10:51 PM
i was sent this link to system files but i have no idea how to install this maybe itll help you out if u can install it.

http://dl.dropbox.com/u/6765686/Blur_2.3.320_System_2.2.1.zip

00gt1
12-13-2010, 12:17 AM
SUCCESS!!!! The link from post #2 did the trick!! This was a huge learning experience on my part. Not only did I have to learn the work around for RSD not flashing properly from the file due to the blank characters, but I learned a ton about the background stuff that goes into a bootloader and the different software versions. A huge thanks to EVERYONE that helped and for the quick responces. If anyone else feels that they are in the same boat that I was in and can't figure it out from this thread or needs a re-up of the file that finally allowed me to get out of that bootloader lockdown, feel free to PM me and I will do my best to share what I can.

The breakdown of my situation:

Once the OTA update for 2.2.1 came around, I rebloated and downloaded it

I did not un-root my phone before hand and for some reason, after the update, Superuser was still on the phone even though it wasn't rooted

I tried a few things to get it off of there and had no success.

Thats when my friend and I decided to try to SBF it

I stupidly attempted to flash back to 2.2 from 2.2.1 (obviously not paying any attention to the numerous warnings posted all over the forum)

This did not work and bricked the phone.

Due to the fact that my error message contained:

Bootloader mode
30.04
Err:A5,70,70,00,1F

I needed to use a specific SBF file that was designed to work with bootloader 30.04. (each version has it's own specific SBF that you can flash to)

Once this file was so graciously pointed out to me by C Dippa, (and after I had tried numerous other ones), it was smooth sailing.

My RSD workaround:

My RSD kept erroring out saying it could not flash the phone:

I would get this:
Failed Flashing process. (0x7100)

The best way I can describe the workaround is to put your SBF in your root folder (C:/ or D:/ generally)
and rename it r.SBF

Technically you can pull up your error log from the RSD folder in program files and look for blank characters and so on but that seemed like too much work.

I am not a programmer but supposedly this has to do with something about blank memory references in the file name and by filling the voids with numbers the program recognizes the SBF

Anyway, see if it runs with r.SBF, if not keep editing the name with sequential numbers (r1.SBF, r12.SBF, r123.SBF) until the file runs.

My RSD ended up working with r123.SBF

This is your magic number for the program so make sure to remember the number for your future flashing needs.

Also, make sure you are using RSD version 4.8, not 4.7 and that your X drivers are all up to date from the Moto site.

Once RSD finished I was thrilled ( I have never been so happy to see a stock boot animation in my life) and everything works fine now.

(I did have to do a *228 in order to get out of roaming, but supposedly this is normal)

Once everything was back up and running, I ran Z4root which worked the first time and that is where I am at currently (still haven't debloated yet).

So that is my experience, start to finish, again, feel free to contact me if you feel I can be of any assistance with any step of the process, I am nowhere near as smart as the Rescue Squad here but I will do my best to help out however I can.

spodoc
12-13-2010, 12:50 AM
I'm stoked for you. I did the same thing before 2.2 sbf was out. I had 2.2 installed OTA and it ran fine. I messed up a black bar install, got stuck in some bootloop, so I flashed 2.1 sbf to "bring back to stock" since it came with 2.1. Like you, I was stuck. Forums like these helped out and I was able to find 2.2 sbf and be up and running again.

Congrats on your successful trip to sbf land :)

Abe21599
12-13-2010, 01:42 AM
im gonna sticky this for others to see.

00gt1
12-13-2010, 02:22 PM
Update:

Everything is working perfectly, I was able to freeze all of the bloat with titanium backup.

If the link to the file in post 2 goes down let me know and I will reup it for you in RS or dropbox. Thanks again for all of the help.

Sent from my DROIDX using Droid X Forum App

C Dippa
12-13-2010, 02:53 PM
No problem...glad you're back up and running!

Sent from my DROIDX

SimplySweetness
12-17-2010, 12:34 AM
#2 worked... sweet!

toxic binary
12-22-2010, 06:59 PM
Ok this worked thanks. But I'm trying to get Apex 1.3.1 rom working and that requires official 2.2.1 with 2.3.340... I'm screwed right?

Pensacola32526
12-28-2010, 02:10 PM
Got passed the Bootloader screen, now stuck on Droid and Eyeball logo cycling over and over. What do you suggest from here?

C Dippa
12-28-2010, 02:21 PM
Pull battery, put back in...hold down home and power button, press search at the exclamation point, factory reset, then reboot system

Abe21599
12-28-2010, 03:13 PM
Got passed the Bootloader screen, now stuck on Droid and Eyeball logo cycling over and over. What do you suggest from here?

http://www.droidxforums.com/forum/droid-x-rescue-squad/14548-bootloop-after-flashing-sbf-file.html

stim100986
12-30-2010, 07:57 AM
I have to say, I am beyond grateful for this site.

I completely screwed up and did a factory reset on my rooted phone, and all I got was black screens everywhere. I was able to see the notification screen, and could even answer a call, but that was about it.

I started reading through all of the posts (my lord, are there a lot) regarding rooted phones, bricked phones, etc. And, of course, I kept reading a post that had part of the information, or dealt with the previus software version, so I didn't sleep much last night. :-)

Now I have RDS and my CURRENT SDF file, and going to try to finish the job today! IF this works (and why wouldn't it!), I'm going to start contributing to society...

Pensacola32526
12-30-2010, 08:27 PM
So I got the message that 2.2.1 was available so I rebloated my phone and updated (still rooted). Everything went fine until I tried to reroot. Superuser was stuck on my phone even though it wasn't rooted so the new root would not take. A friend suggested I SBF it back to stock and then go from there. It seemed to make sense however aparently the sbf he used was not the current one, so not my phone is stuck in:


Bootloader mode
30.04
Err:A5,70,70,00,1F

MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Transfer Mode:
USB

I have quite literally tried about 5 different 2.2 .sbf files that I have found floating around here in the coinciding threads about this and every time, RSD claims that the flash passes... however the phone goes right back to that same bootloader screen and will not boot. Any suggestions? I am about on my wits end here and do not want to trade in my brand new phone for a "like new" replacement phone.

Thanks in advance for any help. 00gt1, I hear you. I had the same issue. Took several battery pulls, several SBF flashes via RSD with several different files(the gift, the holiday, 2.3.15, 2.3.340, etc.), then got passed the error codes and stuck on the M logo and it looped. So then I had that issue to fix. Fiixed that, now I don't get Bootloader error codes and am back to normal. It's very frustrating, I know. I even had Verizon send me a replacement phone(refurbished), which I then sent back because the home key was not level with the rest of the keys, not to mention my old phone was fixed and was brand new when I bought it 4 months ago. After several hours reading the forums(not just this one), and sitting in front of my computer squinting my eyes, it worked. Glad everything turned out alright for you.

00gt1
12-31-2010, 02:09 PM
Thanks Pensacola32526, There was no way I was going to give up my new X for a refurb one, that's why I wrote it all up here once I figured out a solution. I didn't want others to have to go through hours of searching and possible a refurb to get it fixed. Glad to hear this post is helping people!!

Abe21599
12-31-2010, 02:52 PM
I have to say, I am beyond grateful for this site.

I completely screwed up and did a factory reset on my rooted phone, and all I got was black screens everywhere. I was able to see the notification screen, and could even answer a call, but that was about it.

I started reading through all of the posts (my lord, are there a lot) regarding rooted phones, bricked phones, etc. And, of course, I kept reading a post that had part of the information, or dealt with the previus software version, so I didn't sleep much last night. :-)

Now I have RDS and my CURRENT SDF file, and going to try to finish the job today! IF this works (and why wouldn't it!), I'm going to start contributing to society...


Thanks Pensacola32526, There was no way I was going to give up my new X for a refurb one, that's why I wrote it all up here once I figured out a solution. I didn't want others to have to go through hours of searching and possible a refurb to get it fixed. Glad to hear this post is helping people!!

thats why i made it a sticky so other can learn :)

stackertwo13
01-01-2011, 03:07 PM
so i bricked my dorid x reflashed it from the directions i found on here now its stuck in bootloader gives a err:a5,70,70,00,1f any ideas

C Dippa
01-01-2011, 03:09 PM
I think you used the wrong sbf. What does the bootloader say, 30.04? And which sbf did you use?

Sent from my DROIDX

stackertwo13
01-01-2011, 03:16 PM
i used 2.3.15_1ff_01.sbf im trying to reflash it again how to i find out what sbf to use if its the wrong one

stackertwo13
01-01-2011, 03:18 PM
ok it didnt work bootloader says 30.04 err a5,70,70,00,1f
mem,map blank
service req'd
battery ok
ok to program
connect to usb data cable

1KDS
01-01-2011, 03:23 PM
C Dippa is right, you flashed the wrong SBF. You need to flash the full .320 sbf (http://www.mydroidworld.com/forums/droid-x-discussion/5633-droid-x-2-3-32-full-sbf.html) then patch to .340 (http://www.mydroidworld.com/forums/droid-x-discussion/5789-tbh-patches-2-3-340-system-baseband-2-3-340-kernel-bootloader.html)

stackertwo13
01-01-2011, 03:24 PM
ok so just do it the same way i did then

1KDS
01-01-2011, 03:30 PM
yeah, the .320 is a full sbf, flash it the same way you did the 2.3.15. The updates to .340 are a little different, you load those through bootstrap like a theme, there are directions in the patch link above

stackertwo13
01-01-2011, 03:34 PM
sweet thanks i have a slowww internet connection i normally use my droid but since thats down im suckin waiting 2 hrs for the down load but thanks ill let ya know if it works

Pensacola32526
01-01-2011, 03:35 PM
Stackertwo13, I hear you. I had the same issue. Took several battery pulls, several SBF flashes via RSD with several different files(the gift, the holiday, 2.3.15, 2.3.340, etc.), then got passed the error codes and stuck on the M logo and it looped. So then I had that issue to fix. Fiixed that, now I don't get Bootloader error codes and am back to normal. It's very frustrating, I know. I even had Verizon send me a replacement phone(refurbished), which I then sent back because the home key was not level with the rest of the keys, not to mention my old phone was fixed and was brand new when I bought it 4 months ago. After several hours reading the forums(not just this one), and sitting in front of my computer squinting my eyes, it worked. Good luck!

stackertwo13
01-01-2011, 03:55 PM
haha ya that sounds like me right now i sent in to get a new one yesterday mines comming monday but if i can fix it im gona fix it i love my x came from a blackberry and this is a world better

stackertwo13
01-01-2011, 07:02 PM
ok still waiting on my stuff to download but im not to sure how do i use bootstrap never done it

1KDS
01-01-2011, 07:04 PM
http://www.droidxforums.com/forum/droid-x-hacking-guides/13485-how-use-droid-x-bootstrap.html
Also you will need to re-root http://www.droidxforums.com/forum/droid-x-hacks/13259-z4root-download-links-get-your-root-here.html

stackertwo13
01-01-2011, 07:44 PM
so how do you bootstrap the patch

1KDS
01-01-2011, 07:54 PM
You will have to download them and get them on your sd card, then boot into clockwork recovery and select update.zip then reboot, repeat process with each patch. You use the volume rocker to move up and down and the camera button as enter.

Abe21599
01-01-2011, 08:35 PM
thread merged into the sticky

stackertwo13
01-02-2011, 12:19 PM
Heyyy its up n runnin thanks everyone

Sent from my DROIDX using Droid X Forum App

Slimjim1520
01-13-2011, 12:19 PM
OMFG THANK YOU I FOUND THIS AND IT WORKED.....
I do want to mention that I had trouble getting my droid x to come up in RSD lite 4.8. Drivers were installed and I can see the device in the device manager But not is RSD lite
i downgraded the RSD lite to4.7 and installed the patch. Everything showed up correctly and i used the SPF from the second post and BOOM everything WORKED!!!!.

Abe21599
01-13-2011, 01:37 PM
Glad you got it. Stickys do serve a purpose lol

(insert creative, witty tapatalk signature here)

Slimjim1520
01-13-2011, 03:25 PM
just an little back story to what happened to me. I had 2.1 and then i was rooted. Next I got the 2.2 OTA update without unrooting. well it broke but i didnt care cause i never needed it. Then updated to 2.2.1. Last night i needed root so i tried to reroot and could not for the life of me get it to work so i downgraded to 2.1 and expected to just upgrade to 2.2 then 2.2.1 (btw i used to have an iPhone...ANDROID ALOT BETTER....But i was used to do this with iPhone) then i came accross this error and about died when i found out that this was the brick message. I found this thread ran rsd lite and then rooted the phone. now i have a rooted 2.2.1 THANKS again