I have always thought about this, but never got around to asking. Isn't it rather hard to brick a Droid X? With the SBF file, shouldn't you always be able to SBF back, unless the bootloader is corrupt? I would think this since the bootloader is not something that is overridden except with OTA software updates (?). Is this correct?
Thanks!
It's nearly impossible to truly brick the DX. (or almost any phone, for that matter) Motorola and Verizon are just tired of people doing stuff like trying to install a ROM without wiping data and cache and getting stuck bootlooping and then taking their phone in saying it broke out of nowhere because they're too dumb to spend 5 minutes searching Google to figure out how to fix it.
Thanks for your input! That seems to be the impression I am getting as well.
If you want to truly brick it, abort installation while flashing the radio. I know of two ways to do this for the droid x:
1.) During an OTA update, pull the battery halfway through or while it is flashing the radio. How you determine timing is completely on you
2.) Do as mentioned above except during an sbf instead of an OTA update.
These are pretty much the only ways to truly brick the DX
What makes you think losing power during an SBF will brick it? My cat knocked my phone off my desk while I was SBF'ing a few weeks ago and I had the battery cover already off because I was having freezing issues on the Liberty .3 GB ROM, battery popped out and it came unplugged from the computer *WHILE* SBF'ing, but all I did was start over and it was fine.
I can't speak to whether or not you can perma-brick it while flashing the radio. You couldn't just try it again?
Related
I know that there's probably tons of these, but here goes.
Last night, I tried installing 2.3.320, but ended up looping at the eye. I thought I had installed it wrong, so I tried to access bootstrap recovery to delete the data I hadn't cleared. I was surprised to only be able to access the stock bootloader, 30.04. Anyway, I decided to try using an SBF to restore, but I used the wrong one. Bootloader now loads with these messages, "Err:A5,70,70,00,1F" "MEM_MAP Blank" "Service Req'd".
I got my hands on the system only SBF for 2.3.320 that is floating around, but that still isn't fixing my problem.
Simply put, does anybody know of anything I can do now?
silversonic1 said:
I know that there's probably tons of these, but here goes.
Last night, I tried installing 2.3.320, but ended up looping at the eye. I thought I had installed it wrong, so I tried to access bootstrap recovery to delete the data I hadn't cleared. I was surprised to only be able to access the stock bootloader, 30.04. Anyway, I decided to try using an SBF to restore, but I used the wrong one. Bootloader now loads with these messages, "Err:A5,70,70,00,1F" "MEM_MAP Blank" "Service Req'd".
I got my hands on the system only SBF for 2.3.320 that is floating around, but that still isn't fixing my problem.
Simply put, does anybody know of anything I can do now?
Click to expand...
Click to collapse
Think you're boned. Shoulda read some of the thread at mydroid before taking this on. Most ppl are bricking, with it. You appear to fall into that category.
Go Back to TBH there maybe some help now.
But the 23.15 may also big the big bone.
ouch
This is awful. I'm a guide on another forum for androids and I'm telling people not to try the new update until there is a full sbf available. I'm so sorry. You are stuck..for now.
Well, Verizon's gonna let me swap, so I'll just have to wait until Tuesday and root the new phone.
I'm preparing to root my X and am trying to get a rescue plan in place prior to rooting. The one thing I can't find is a list of what SBF files can safely be used for a given bootloader revision. I posted this in a thread at another forum. Does what I'm asking for not make sense? Or am I completely missing something?
There should be some sort of sticky for SBF'ing the X. I realize that sbf links cannot be posted but it would sure be nice to know which files are needed to properly sbf a semi bricked phone, especially if using the wrong one will fully brick a phone.
What I've gleaned from this thread...
"No if you were stuck on the M that shows that you should already be updated, put your phone into flash mode and make sure (turn of your phone press the camera down volume and power button). It should say boot loader 30.04 if it shows 30.03 then dont use the link provided. If it is 30.04 go download the sbf from ncdubs link and run it using RSD 4.8 and that should be enough for the phone to get past the M logo. Dont it asap because you never know when that link will be dead. Man I was so scared yesterday because i thought my phone was bricked haha but that link that i found in another forum did the job."
"If you are on 2.3.20, use the 2.3.15 SBF.
If you are on 2.3.320, use the SBF's from TBH"
It would be nice to have a running list detailing which sbf file needs to be used for a given bootloader,
i.e. if bootloader is 30.03 use the 2.3.15 sbf or the x.x.xx sbf
if bootlader is 30.04 you can safely use the x.x.xx sbf
and so on.
Surely this won't be in violation of anyone's terms of service would it?
I'm not rooted yet but I'm trying to wade through multiple posts at multiple sites to put together a rescue package prior to rooting and can't find what I believe to be concise information anywhere.
Click to expand...
Click to collapse
http://www.mydroidworld.com/forums/...rikes-back-2-3-320-update-must-rooted-69.html
Post #682 - CZ from TBH is working on a way to restore soft bricked X's,and is making good headway!
bricked, verizon is overnighting one, should have a good clean one tomorrow.
SerialKilla said:
.....link deleted, as this forum won't allow me to post outside links..... yet...
Post #682 - CZ from TBH is working on a way to restore soft bricked X's,and is making good headway!
Click to expand...
Click to collapse
Thanks for the link, I'll be following the thread closely. Sorry to hear you're X is in a semi bricked state. At this point I'm quite wary of doing anything to the X but I believe I have a rescue in place. My phone shows to be 2.3.151 and I found VRZ_MB810_2.3.15_1FF_01.sbf so I believe I should be able to safely recover should I brick it. I rooted using Z4 and the bootstrap, then proceeded to freeze the bloat. I'll run like this until UD for the X comes out then depending on SBF requirement / availability will consider trying it out. UD2 is really sweet on the D1 and I've read it's even nicer on the X.
I must be in the minority because I kind of like blur. I did freeze all of the social networking stuff and installed gallery3d, I would continue to use the blur gallery if it synced with picasa.
edit: SerialKilla I see a new rescue sbf was released, did it work for you?
edthesped said:
Thanks for the link, I'll be following the thread closely. Sorry to hear you're X is in a semi bricked state. At this point I'm quite wary of doing anything to the X but I believe I have a rescue in place. My phone shows to be 2.3.151 and I found VRZ_MB810_2.3.15_1FF_01.sbf so I believe I should be able to safely recover should I brick it. I rooted using Z4 and the bootstrap, then proceeded to freeze the bloat. I'll run like this until UD for the X comes out then depending on SBF requirement / availability will consider trying it out. UD2 is really sweet on the D1 and I've read it's even nicer on the X.
I must be in the minority because I kind of like blur. I did freeze all of the social networking stuff and installed gallery3d, I would continue to use the blur gallery if it synced with picasa.
edit: SerialKilla I see a new rescue sbf was released, did it work for you?
Click to expand...
Click to collapse
I haven't seen the new .sbf yet...where did you see it? If it's just the sytem only fix, that won't work on mine - I need the full .sbf, or whatever it'll be that CZ and P3 are working on. P3 said to expect something in less than 36 hours, but I haven't seen anything as of yet. Too early yet I think - but I know they've had success in their progress, so fingers crossed!
SerialKilla said:
I haven't seen the new .sbf yet...where did you see it? If it's just the sytem only fix, that won't work on mine - I need the full .sbf, or whatever it'll be that CZ and P3 are working on. P3 said to expect something in less than 36 hours, but I haven't seen anything as of yet. Too early yet I think - but I know they've had success in their progress, so fingers crossed!
Click to expand...
Click to collapse
Sorry, it was the system only sbf, I d/l'ed it as a backup and judging by it's size it isn't a full system sbf. Hopefully you'll be rocking again by this time tomorrow.
I have one of those Legends that require a downgrade before you root, but I decided to chicken out and after I downgraded to 1.31 or whatever it was, I decided to debrand my Bell Legend and chicken out to get the worldwide Froyo OTA. Plus, it was getting late, I didn't want to accidentally screw up the rooting because I was tired.
Anyway, after I downgraded, I installed a system update that brought me to Eclair-update-1. I don't think that was a really good idea.
Because afterwards, when I tried installing the debranded RUU from the debrand thread, it resulted in an error and I have to keep what I have right now.
UNLESS YOU GUYS HELP.
What did I do wrong? I'm only still a kid. Hell, I thought I bricked my phone halfway through installing the first RUU because there was something wrong with the drivers, I ALMOST TEARED UP FFS.
Oh yeah, and wtf is up with this BS where you format the SD card to turn it into a Goldcard, and HTC Footprints just decides to move its crap into the SD card RIGHT AFTER I FORMAT IT. It's not important, but I was just wondering.
I might have been missing some details (it's late) so please post below and tell me what I'm missing.
Thanks in advance!
PS: Oh yeah, have I voided my warranty yet? Technically, I mean. I COULD still clean it up somehow, and make it seem like I didn't do anything to it, right?
PS2: OK, now I'm getting USB errors 171 and 170 when installing RUUs. I can't get out of the RUU I'm on. Oh crap.
PS3: I just got Error 140, BOOTLOADER Error. What did I do wrong here?
At least I'm at the phone's home screen now, no more unfamilar scary-ass HTC LOGO territory.
Basically the update to "2.1-update1" brought you back to where you were before the downgrade. Your phone is stock right now.
So first relax and get some sleep
Do the downgrade again. DO NOT UPDATE.
Continue the debranding/gold card procedure.
good luck
p.s. your warranty might technically be void when you install another ROM or debrand or root, mostly they don't care as long as you didnt drop it in water . There is always a way to bring it back to stock/unroot
Oh my goodness I love you. I just noticed (while I was tired, wow, that's strange) that the strange ROM number within the About Phone menu finally clicked with what I've been doing! NO UPDATE.
So I decided to call it a night after I try once more.
So I downgraded to w/e. It was fine.
And I tried the debranding RUU. Then I got a bootloader error. I guess I'll try to find out what that means when I wake up, I'm super sleepy. (Unless you guys can help me 'til then )
It was error 140 or something like that, but it booted me fine to my downgraded ROM, so I'm good for the time being.
Good night!
EPIC ACHIEVEMENT EDIT:
Alright, I rooted it. Sweat all over the place, but hey, don't blame me. The problem above is still experienced by many people all over the internet, unfortunately. Too bad I can't answer it.
Just a question before I flash my first ROM with ClockworkMod: What about fixes? How do I flash those? Super noobish, but yeah.
Okay so today i decide to root my phone. I heard alot about custom roms and other tweaks that make your phone do all this cool stuff. Well i try and download a custom rom, i did use the droid 2 bootstrap, and i believe i backed up on ROM Manager. after that i went and looked at roms and i downloaded Tanzanite ROM. at first i thought i was in a boot loop and i got scared because i rooted my phone last week and downloaded a custom rom wrong and it was in a boot loop. So when i thought this time it was in a boot loop, i hold X and Power button and get recovery options. i factory reset it then rebooted it, it then started up on Tanzanite ROM. I was quite happy with it, then when i try to look at my apps, they are all GONE ! There is no Market and i have no 3G coverage. I was upset and i dont know what to do. I am scared if i do something it will go into a bootloop or i will be stuck with this ROM forever. I NEED HELP ! PLEASE ! i cant afford another phone replacement. Please help me ! Please, experts, people who had this issue, somebody just please help. Thanks.
You're not stuck. There's always SBF.
SBF is your best friend. And a word of advice to you. ALWAYS find out what kind of recovery is out for your phone before you do ANYTHING like rooting or flashing. For Moto phones, SBF is your friend. HTC has RUU's.
Here is the guide to SBF your phone:
http://forum.xda-developers.com/showthread.php?t=770224
(Be sure to get the RSDlite 4.9 and the latest Moto drivers which you can find on Moto's website)
Here is the SBF file to download:
h t t p://www.mydroidworld.com/forums/droid-2-discussion/5323-tbh-mydroidworld-present-droid-2-2-3-20-triple-threat.html
This will get you back to 100% out of the box stock.
Good luck and let us know if you get it fixed. If you have any problems or questions, feel free to PM me.
I fixed the problem. Thanks guys but i would like to know, what is SBF and what does it do? Everytime i do a new ROM i am scared of the outcome. It bootlooped once and got a new one. I will always be scared when my phone re-boots. Alot of feedback i got, has mentioned SBF and i have yet to know what it does and yet to know what it means.
I could be wrong, but I think SBF stands for System Backup File. It basically is a file that came from Motorola. Motorola uses it to get the phone back to its out of the box state, meaning it returns the phone to the same state as when you got it.
You use it if you have no way to fix your phone. As long as you can get into bootloader mode, you should be able to use the SBF. It's actually pretty hard to 100% brick these phones.
Most phone has some sort of recovery utility like this. For example, HTC has RUU (ROM Update Utility) which will do the same thing as an SBF for Moto phones. I don't actually know what other brand phones have, because I've only ever rooted HTC and Moto phones.
Also, when you flash a ROM, you say you bootloop right? Be sure before you flash a new ROM to wipe data and cache in clockwork recovery. This should prevent bootloops.
close this plz
If you know what your doing with an sbf then it would work. Quit trying to get a free phone for no reason.
maxbakerman said:
ok so i have been wanting to sbf to froyo and install rooted GB, but my phone is a POS and will not sbf, i always get an error and ive tried all of the option, but noting works. (please don't help me with sbf'ing, i know what im doing) so im trying to find a way to "break" my phone so that I can send it into verizon and get another one for free (warranty). so i need to figure out a way to break it without voiding the warranty. ive already tried shorting it out with a 9 volt, but all its done is turned the phone off. anyone know of a way to make the phone inoperable or bad enough so that i can get a free replacement?
Click to expand...
Click to collapse
Well i hate to say this but personally I believe you need to try sbf'ing and following the troubleshooting with sbf. When I started sbf'ing i had errors galore. I learned that by reading other peopples follies and solutions led me to using older rds, updating rds, re downloading sbf file several times, and many other things. Now i have no problems mainly due to the sbf file being d/l 2x to get a fully functioning, no error one.
Just my 2cents
Night before last my Droid X was upgraded via OTA from Froyo 2.2.1 to Gingerbread 2.3.4 , at which I lost my Root. So I started searching YouTube for videos on taking my phone back to Froyo. And I found just what I was looking for. Return your Droid back to Froyo. So I followed the instructions to the letter, I downloaded - RDS Lite 4.9 - Motorola Helper_2.1.40_5.5.0 - VRZ_M810_2.3.34_IFF_01 . According to RSD Lite the flash was successful. Droid X reboots, and this is what I was left with.
Bootloader
30.04
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program'Transfer Mode:
USB
I have tried SBFing twice and RSD Lite sees the phone, goes thru the flash, reboots the phone but I get the same responce on the phone as stated above. Although in my computer, the Droid is not detected.
In your opinions, have I done an unrecoverable bricking to my Droid?
Go ahead, I can take it.
TIA
I used 4.5.621 SBF file, and was able to bring my phone back to the way it was before I got in a bind (Droid X SBF Files - Motorola SBF Files). It is alive with all of my Apps, so I'm not sure just what happened to it. But to whoever is responsible for the web site, I think P3 Thanks
Great job on getting back to .621.
Unfortunately, being on .621 makes it impossible to flash back to Froyo.
However, you can root and install custom roms.
Sent from my DROIDX using Tapatalk 2
yeah I know, but at this point I'm just happy to have my phone back in good working order. I had just bricked my Droid X2 @ 2 weeks ago, so now I don't have to face my wife with another $200.00 paper weight.
I have the same issue. Someone pointed me to this forum so I'll just include my text.
So I just got my first droid yesterday, it's a droidx from motorola. I initially factory reset it and cache cleared and it was working like a charm. Anyways, today I got the idea after reading over cyanogenmod following these instructions. Since I didn't have much on it I didn't backup. I remember vaguely updating the system previous to this, I think I was at 2.34. Anyways, I get done with flashing it- as far as I know it was successful- rdslite said it was complete. I try to do another factory reset, can't get into it. Just the bootloader comes up saying : Bootloader30.04 Err:A5,70,70,00,1F and a few things about to plug usb in and that it needs service...
I see something on cyanogen's page that I overlooked before:
WARNING: The 2.3.4 OTA release, the bootloader was patched to version 30.04. If an attempt is made to downgrade to an earlier version through the SBF method below, the bootloader will throw an error and the phone will not boot.
FLICK.
I tried the 1kds cd and it says it installed properly, I turn it on only to see same bootloader issue. I tried another rom and same thing. The last one I used was apparantly a 2.34 one and now my phone says code corrupt on the bootloader screen.
I need to find a way to charge the battery. I feel bad because it was a present to me from my girlfriends sister, and I don't want to see her and tell her I broke it already
But, can you guys help me with this? I don't really know where to go from here.
Sbf
Sbf is the only way. And from what I understand if you did the. 621, you won't be able to do previous releases.
I could be wrong.
When it comes yo moto flashing, donkey skip reading anything lol
Sent from my DROIDX using xda premium