Related
Hey Guys,
I need some help! I used RSD lite 4.8 and the new sbf (2.3.15) and I get all the way to the end and then it fails....Here is the error log:
Failed flashing process. Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE0030009 Address: 0x18F000 Command ADDR (0xE0231009); phone connected.
Any ideas?
I am using the OTA 2.2 update and was rooted using BigDX theme.
I have tried the sbf 2x, and both times, would up in the same spot...
When the phone reboots, I have all my contacts and apps...
The reason I wanted to use the sbf is gmail keeps force closing so I'm not getting my emails over push...
So you didnt do a nandroid backup before you installed themes/roms?
I know this is a stupid question so sorry in advance- did you enable USB debugging on your phone? If so- have you tried it in different modes? Media Sync or USB mass storage?
I have heard reports of having to be in a different mode.
And you are sure it was the new sbf...
VRZ_MB810_2.3.15_1FF_01
Not the system sbf...
SHADO_X6_2.3.13_SYSTEM-ONLY
thepolishguy said:
I know this is a stupid question so sorry in advance- did you enable USB debugging on your phone? If so- have you tried it in different modes? Media Sync or USB mass storage?
I have heard reports of having to be in a different mode.
And you are sure it was the new sbf...
VRZ_MB810_2.3.15_1FF_01
Not the system sbf...
SHADO_X6_2.3.13_SYSTEM-ONLY
Click to expand...
Click to collapse
To SysadmNJ,
Yes I did a nandroid backup, so I have a place to go back to...but gmail was still force closed... So that is why I wanted to do the SBF.
Polishguy,
yes I have USB debugging enabled, and had thrown the phone in PC mode so it was detected. I'm stumped as to why it is failing at the end. Yes, I grabbed the SBF from rootz wiki. Would like to have a full SBF work so I can get the gmail service working again.
did you place the patch in rsd lite folder?
mob87 said:
did you place the patch in rsd lite folder?
Click to expand...
Click to collapse
Yes, the patched pst_flash.ini file?
Is there a new one for RSD 4.8?
Just trying to figure out what else might be going wrong...
there isnt a new one just wanted to make sure. maybe you got a bad download of the sbf.
mob87 said:
there isnt a new one just wanted to make sure. maybe you got a bad download of the sbf.
Click to expand...
Click to collapse
Tried the original that was hosted here before it got pulled by the mods, and also grabbed the one from rootz wiki as well. Got the same result with both. I will try putting the phone in charge only mode as well as media sync mode later and retry the sbf.
If anyone has done this successfully, can you please list the steps you took?
Thanks
SysAdmin-X said:
Tried the original that was hosted here before it got pulled by the mods, and also grabbed the one from rootz wiki as well. Got the same result with both. I will try putting the phone in charge only mode as well as media sync mode later and retry the sbf.
If anyone has done this successfully, can you please list the steps you took?
Thanks
Click to expand...
Click to collapse
You are suppose to be in bootloader when you flash the sbf.
mob87 said:
You are suppose to be in bootloader when you flash the sbf.
Click to expand...
Click to collapse
Ok. Will give this a try. I read you could do it with the phone on or off.... That it would put the phone into bootloader...which it looks like it did.
I will try putting it into bootloader prior to running the sbf.
EDIT:
I put the phone into bootloader mode, and have run the sbf 2 more times...still with the same error. Just wind up with different values on the error codes....
Yes holding the volume down, camera, and power button for a few seconds will make the screen flash then release the buttons and you will be in bootloader mode.
Sent from my DROIDX using XDA App
Try a different USB port or even a different PC.
Have tried the above suggestions.... I noticced each time it would make it slightly farther (or so it seemed) that there were device druvers being installed along the way.
Anyone have the driver p package they used if they got the sbf to work?
I'm using the 4.7 drivers
Sent from my DROIDX using XDA App
I recently got the same error message, I asked a few developers and P3 told me its the radio that is not being changed. he said it is not a problem unless you are not happy with the radio. This was about a week agao and i have been flashing Rom's/Themes all week and my phone is running great. I wouldn't worry much about it.
Just an FYI I am on the leak and used the first sbf.
FSRBIKER said:
I recently got the same error message, I asked a few developers and P3 told me its the radio that is not being changed. he said it is not a problem unless you are not happy with the radio. This was about a week agao and i have been flashing Rom's/Themes all week and my phone is running great. I wouldn't worry much about it.
Just an FYI I am on the leak and used the first sbf.
Click to expand...
Click to collapse
Hm...interesting. So the radio doesn't really matter unless its already messed up... I guess I should have thought of that...
ON ur x, it does look like everything else is back to stock tho?
did you do a battery pull ; and/or clear data/cache and do a factory reset after the process seemingly completes (never mind the error) - coz I got some error when I tried flashing using sbf - but I was on the 1st leak - and used the original (2.1) sbf - rsdlite said 100% - but error - mentioned somethin abt bootloader - I did a battery pull - phone went into loop of death - I cleared data/cache and also did a factory reset by going into recovery - and my phone was as good as new... just a thought..
EDIT: Actually, all your questions seem to be answered in the other thread in this very forum by name " Droid X Full SBF Release" posted by catalystsupreme2 - read through all the posts - esp. abt the radio etc which someone here also mentioned in this thread
chiaroscuro7 said:
did you do a battery pull ; and/or clear data/cache and do a factory reset after the process seemingly completes (never mind the error) - coz I got some error when I tried flashing using sbf - but I was on the 1st leak - and used the original (2.1) sbf - rsdlite said 100% - but error - mentioned somethin abt bootloader - I did a battery pull - phone went into loop of death - I cleared data/cache and also did a factory reset by going into recovery - and my phone was as good as new... just a thought..
EDIT: Actually, all your questions seem to be answered in the other thread in this very forum by name " Droid X Full SBF Release" posted by catalystsupreme2 - read through all the posts - esp. abt the radio etc which someone here also mentioned in this thread
Click to expand...
Click to collapse
I read through this, and I haven't done the battery pull, or clear..... trying to avoid it if possible...but will if needed.
As for the answer about the BP, it didn't seem like the post really answered the question per say...just gave an explanation about it overall
thank you for the help
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 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?
A month go I installed the leaked Gingerbread. everything has been fine until I decided to get back to Froyo for the OTA. Rooted this morning through Gingerbreak. Still OK. Made a back up through Bootstrapper. Booted into recovery and installed .zip from sd card. Used Maderstock zip. it made it through almost the entire process then when it got to update Radio it aborted. I cleared all the cache and data and all...still nothing. Hit reboot and now it is stuck in bootloop at the droid logo. The font with the circles under the "r" Can not hold home and power to get into recovery. can not turn on phone at all. only get charge screen when plugged in (and yes I was 90-100% charged when attempting this) and red moto logo goes black when attempting recovery boot.
I assume I need to SBF through RSD Lite. Problem is- It wont recognize my device. (yes I have downloaded the Moto drivers.)
At this point I am totally stumped. Noob here, but with LOTS of research and reading over the last weeks.
Help?
check out how to sbf using a linux virtual machine. You can just boot it up within windows. As far as I know, you will not need the drivers for this to work.
Try this. Hopefully it helps.
http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html
After weeks of reading forums and posts, I have successfully SBFd my phone back to stock Froyo. I wish I could remember everyones names from every post I read, and thank them personally, but a BIG THANK YOU to the Android community and to anyone that has offered their time and service to helping out. THANK YOU ALL! My experience as little as it might be might now be valuable to others as well.
Let us know what you did fix your situation.
Sent from my DROIDX using XDA App
Fixing a bricked Droid X
beeper10 said:
Let us know what you did fix your situation.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Many thanks to all those that have spent countless hours helping users like myself find solutions to Droid X problems. At one point in this process I basically bricked (maybe soft briked is the term) my phone. I could do nothing but get a bootload screen. No moto logo, no droid eye, NOTHING.
Long story short, and to help anyone that needs it, here is my solution.
Download FULL SBF file from file share somewhere (VRZ_MB810_2.3.34_1FF_01.sbf)
Download RSD Lite 4.8
Download Moto Drivers
Power Off Droid X- Make sure it is fully charged when attempting any SBF Flashing.
Power on into Bootload mode. I held Power and Volume rocker simultaneously until a quick flash then Bootload appeared. (version 30.4)
Open RSD Lite as an administrator. (hold shift and right click. use "run as") In my case Windows 7 -64bit
Plug phone into computer via USB
Locate device in RSD. Click the little box that has "..." in it and select the SBF file you previously downloaded.
Start.
Let it work its entire process and Voila you will have stock Froyo back on your phone in no time.
I then went in under settings and received the OTA for Gingerbread. My phone works like a champ now.
The steps are clear as day in my head, and I will be able to troubleshoot many of you through the steps. The further from today it gets it might get foggier, so ask away if you are having problems.
It seems like everything had to be VERY specific to work just right.
Good luck and happy Bricking! :/
It happened to more people than you think. I DLed RSD 4.9, 4.8 didnt work for some reason. That was like a month ago, I'm on froyo now, rooted with Liberty. Now I have to SBF again to get the official GB...lol!
My story the same just different thread, (soft bricked) lol my phone, all i got was the bootloader, on win7 64bit as well, only thing different was ive my win7 tuned up to my preferences so i didnt have to ask or run as anything. The steps used in this thread were identical however and many many hours of reading done as well. Just putting this info up here to let you know that you can get your dead bootloading phone back so even though it feels like you have a bowl of something nasty in your stomach as you stare at your DX with nothing but a bootload screen on it and seemingly no other options, read thoroughly, pay attention, be specific and youll have your DX running like a champ in no time. THANK YOU Devs/Community
As the title asks...
Has anyone been able to SBF back to 2.2.2 Froyo from the OTA update? If so, please advise all details. Thanks.
Much of the software conveniences I use, are better working in 2.2.2 especially screen lockers, unlockers, blockers, and Wireless Tethering.
W/ 2.3.5, I change the hotspot info to that of Wireless-Tether's and use it, but that's annoying...
Feels like two different setups.
i tried once... didn't go so well, ended with warranty replacement.
downloaded sbf that indicated it was for cell south(cspire) from here. everything appeared to go just fine. until the phone rebooted. gave me a message that said something like MEM_BLANK or something similar. i will admit that i am not very proficient with motorola's yet, and may have done something wrong, but i followed the steps that i found posted here on xda. if you find any more information i would love to hear it.
I had the same issue come up with no success as well. This happened when I tried flashing Liberty3 after doing full wipes and installing the Droid 2 bootstrapper. After the flash, I kept getting stuck on the bootloader with some error codes. At that point, I tried flashing the sbf using rsd lite and sbf_flash on ubuntu, but those ended up giving me more error codes with the MEM_BLANK and SERVICE REQ'D outputs. Meh, guess I'll just have to stick with stock rooted.
Rocheforte said:
I had the same issue come up with no success as well. This happened when I tried flashing Liberty3 after doing full wipes and installing the Droid 2 bootstrapper. After the flash, I kept getting stuck on the bootloader with some error codes. At that point, I tried flashing the sbf using rsd lite and sbf_flash on ubuntu, but those ended up giving me more error codes with the MEM_BLANK and SERVICE REQ'D outputs. Meh, guess I'll just have to stick with stock rooted.
Click to expand...
Click to collapse
exactly. i came to the same conclusion. makes me wonder why the motorola roms aren't more like the htc roms where they are not carrier specific.
edit: did you manage to get past the MEM_BLANK and SERVICE REQ'D errors on your own? and if so, how?
No success, anytime I tried to sbf it would output a slightly different error with MEM_BLANK and Service Req'd. I eventually just replaced it, but now I'm likely going to return this one because it won't update to 2.3 and wifi doesn't work.
Rocheforte said:
No success, anytime I tried to sbf it would output a slightly different error with MEM_BLANK and Service Req'd. I eventually just replaced it, but now I'm likely going to return this one because it won't update to 2.3 and wifi doesn't work.
Click to expand...
Click to collapse
did u install the bootstrapper? it changes the logwrapper file, however changing it back and removing the bootstrapper all together still yeilds the same problem. update fails after about 1 minute.
here is a strange morsel of info, when i was trying. (before warranty replc) even tho the update would fail, it did change the system info on the phone, it would indicate that .602 was installed on the phone even tho it had failed.
ngholson said:
did u install the bootstrapper? it changes the logwrapper file, however changing it back and removing the bootstrapper all together still yeilds the same problem. update fails after about 1 minute.
here is a strange morsel of info, when i was trying. (before warranty replc) even tho the update would fail, it did change the system info on the phone, it would indicate that .602 was installed on the phone even tho it had failed.
Click to expand...
Click to collapse
Yeah, I had used the Droid 2 bootstrapper at that point. Has anyone tried using the Verizon Droid X sbf's since apparently they are supposed to be very similar to the Milestone X's?
Sent from my Milestone X using xda premium