I was flashing the full sbf 2.3.340 file to my phone (first time)
so i could get ginerbread on my dx
but when flashing it excutes everything fine but when flashing process is ending it gives me a fail saying internal error idk what to my phone still says sw update in progress... even though rsd gives me a fail can i unplug my phone and restart the process or no?
jf4888 said:
I was flashing the full sbf 2.3.340 file to my phone (first time)
so i could get ginerbread on my dx
but when flashing it excutes everything fine but when flashing process is ending it gives me a fail saying internal error idk what to my phone still says sw update in progress... even though rsd gives me a fail can i unplug my phone and restart the process or no?
Click to expand...
Click to collapse
YES...After it fails with the FULL sbf do the SYSTEM ONLY sbf and you should be working again. I had to do it that way a few times.
Also for me I had to find a copy of 4.8, the 4.7 rsd lite would not work for me. Good luck!
Sent from my DROIDX using XDA App
drum747 said:
Also for me I had to find a copy of 4.8, the 4.7 rsd lite would not work for me. Good luck!
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
You can find a lot of the "old" files on my server: http://rdp.yagoolio.info/downloads
Related
i guess im going to call verizon with a bs reason i need a new phone. I have tried to update off nan from when i first rooted downloads but wont install dont understand sbfing and zip files wont load need serious help
What exactly is your phone doing right now? Is it stuck on the boot logo or what?
Its operational, I just flashed back to first nan and reloaded fission cause nothing I did the 928 back to stock ect worked, even tried updating without signing into google, unrooted and all that just frustrated it won't work
Sent from my DROIDX using XDA App
Ok, so you are up and running then. The only thing i was going to suggest is flashing SBF to get you back to Stock Android 2.2 and starting the process over again. I had a similar problem and wiped everything clean IOT get what i wanted. SBF'ing is simpler then you think, all you need is 2 files (rsdlite_4.8 and VRZ MB810_2.3.15 sbf). There's lots of articles here on it and I used them when I thought I bricked my phone. I started all over and was able to receive my 2.2.1 update.....finally!!
have you done the ota update? if so use 2.3.32.sbf you can get it by google and search droid x 2.3.32 sbf and its the first result. and dl rdlite 4.8. very easy to flash. several guides on here as stated.
I got it my drivers are up to date but won't find my phone.. And I'm leary all I got to do is that file and update?
Sent from my DROIDX using XDA App
Try running rsdlite as the administrator. (Right click rsdlite)
Now won't find it and I got a toshiba, only a little bit over a year old
Sent from my DROIDX using XDA App
EDIT - finally got rsd lite to recognize but first attempt failed trying again... pray
EDIT #2 - YEs, rebooted with 2.3.320 now to find 2.3.340 n flash it
I tried to flash Fizzion rom and then all it would do is get stuck at the M. . Then i couldn't get clockwork recovery to come up.. I tried to sbf and it keeps failing at the very end of a long ass process.. I used sbf on this phone once before and had no problems.. Now it doesn't do anything but go to the bootloader. .It's a friends phone so im kinda freaking out..
What version were you on and what sbf versiln did you try to flash?
Sent from my DROIDX using XDA App
2.3.15 trying to use 2.3.15 sbf
Can you boot into stock recovery? (Home and power, at triangle push search button once)
If you can, try to wipe data and cache.
Sent from my DROIDX using XDA App
I wish i could boot into stock recovery.. doesn't do anything but go to the bootloader.
boredmug said:
I tried to flash Fizzion rom and then all it would do is get stuck at the M. . Then i couldn't get clockwork recovery to come up.. I tried to sbf and it keeps failing at the very end of a long ass process.. I used sbf on this phone once before and had no problems.. Now it doesn't do anything but go to the bootloader. .It's a friends phone so im kinda freaking out..
Click to expand...
Click to collapse
Some friend you are.... Lol.
Sent from my DROIDX using XDA App
lol.. well now it boots up.. I said it failed the sbf flash but it booted into stock 2.2. . wtf?
boredmug said:
I tried to flash Fizzion rom and then all it would do is get stuck at the M. . Then i couldn't get clockwork recovery to come up.. I tried to sbf and it keeps failing at the very end of a long ass process.. I used sbf on this phone once before and had no problems.. Now it doesn't do anything but go to the bootloader. .It's a friends phone so im kinda freaking out..
Click to expand...
Click to collapse
Sometimes it will say it failed at the end, but it just isn't overwriting bp-passthroug. This isnt an essential file if you are already on the same version as the sbf you are using. These are radio files I believe... So if this part fails...oh well. As long as it is writing the system files, that is what you should be concerned about for the most part.
Please help...very similar situation I am in as was boredmug. I Flashed the Fission Rom...then it got stuck on the "M" boot animation...I did some research and used RSD Lite 4.8 to flash 2.3.15 sbf from bootloader... It started working fine and then right at the end of the process my bootloader said "Battery low...Unable to program". I know my battery was fully charged..
Could I just need a new battery maybe?? hopefully???
jeraspie28 said:
Please help...very similar situation I am in as was boredmug. I Flashed the Fission Rom...then it got stuck on the "M" boot animation...I did some research and used RSD Lite 4.8 to flash 2.3.15 sbf from bootloader... It started working fine and then right at the end of the process my bootloader said "Battery low...Unable to program". I know my battery was fully charged..
Could I just need a new battery maybe?? hopefully???
Click to expand...
Click to collapse
I had this happen to me before. You will need to charge your battery before you continue. I hope you did not fry out your battery as this has also happened to me. Give it a full charge as well.
There is a full 340 SBF that you can use with RSD Lite as well as a zip, maderstcok for 340. With the maderstcok update ( which works just as well as flashing with RSD Lite ) it doesn't matter which bootloader you have as long as you are on 2.3.15. It will update all files so you are on the latest version of Android.
Make sure you guys are wiping data/cache as well before SBF or installing new ROMS.
When I plug the phone into USB port and the led is green and the bootloader still says "Battery low, Cannot program." Would it help to get another battery?
It also says "NEW_MAP Blank" above the battery low message. Does that have something to do with it?
Sent from my Ginger Tazz using XDA App
jeraspie28 said:
When I plug the phone into USB port and the led is green and the bootloader still says "Battery low, Cannot program." Would it help to get another battery?
It also says "NEW_MAP Blank" above the battery low message. Does that have something to do with it?
Sent from my Ginger Tazz using XDA App
Click to expand...
Click to collapse
USB port charging is not enough to charge the phone properly. You will need to charge the phone with the wall charger while the phone is off or take it to a Verizon store so they can charge it for you. Usually the batteries from VZW come with less then half a charge. They can also test your battery to make sure it's still good.
I finally solved the problem by "rigging" up the battery to another USB cable wires. Crazy, but it worked. I'm all good now.. Thanks.
http://www.droidforums.net/forum/te...ons/99781-droid-not-booting-odd-behavior.html
Jeremy
hi i was using the sbf 1.2.6 file from http://bandbinnovations.com/xda/OLYF..._1g_1FF.sbf.g. site, i flashed in rsd mode and it went through ecxeuction 100%, then went through flashing the different files, but then as it was flashing the files at about 86% it said flashing failed "because of switching device to bp pass mode failed". and now iam stuck at the red M screen, what can i do now?. i have tried about 4 different sbf files but they have never done this. . can someone help. what do i do now?
Did you check the MD5 hash? Also did you give the .SBF a shorter file name? This solved all my problems personally.
Moved to general.
bongd said:
Did you check the MD5 hash? Also did you give the .SBF a shorter file name? This solved all my problems personally.
Click to expand...
Click to collapse
what is the MD5 hash, and yes i did renamed the.sbf.gz to atrix.sbf. dont know what to do?
Hi
Rename the file to smtng shorter
Make sure the the battery is full and you might wanna use a PC and not a laptop ( my laptop was part of the problem when I tried to flash an sbf to a soft brick phone)
If it doesn't work for you pm me and ill send you a complete way to do it
Sent from my MB860 using XDA App
See if you can access RDS protocol by holding Vol. Up at boot. Then retry.
RPK925 said:
what is the MD5 hash, and yes i did renamed the.sbf.gz to atrix.sbf. dont know what to do?
Click to expand...
Click to collapse
You have to extract the file, not rename it.
Yeah first need to extract the .Gz file and then rename the long sbf file to smtng shorter
Sent from my MB860 using XDA App
AmitMa said:
You have to extract the file, not rename it.
Click to expand...
Click to collapse
i downloaded it on my sd card then extracted it to the root if my c:\ drive, and renamed it ryan.sbf.
I
RPK925 said:
hi i was using the sbf 1.2.6 file from http://bandbinnovations.com/xda/OLYF..._1g_1FF.sbf.g. site, i flashed in rsd mode and it went through ecxeuction 100%, then went through flashing the different files, but then as it was flashing the files at about 86% it said flashing failed "because of switching device to bp pass mode failed". and now iam stuck at the red M screen, what can i do now?. i have tried about 4 different sbf files but they have never done this. . can someone help. what do i do now?
Click to expand...
Click to collapse
Wow! Today I woke up ready to call.att.warranty, and powered up mt Atrix and I went to the M screen and I thought it would stay there because of the failed SBF flash the night before, and then to my surprise it then popped up the" rethink possible" att logo. And I thought I was dreaming. It started up like normal, and im now rooted on 1.2.6. I have now idea how it happened, but im glad it did. Does anyone have anyidea what happens or have ever heard of this before? It was bricked on the M screen all last night, and now im back to stock. Very strange.
Sent from my MB860 using XDA Premium App
nosit1 said:
See if you can access RDS protocol by holding Vol. Up at boot. Then retry.
Click to expand...
Click to collapse
Actually last night for about a hour a could not get to the.RSD protocol screen. Then I tried powering up pushing both the vol up and down button at the same time and that worked, for me. I have no idea why it worked when I pushed both but it did.
Sent from my MB860 using XDA Premium App
hi The Atrix has been my first official Android phone, i had a HTC TILT 2, which i flashed to 2.3. But this Atrix is very confusing. The first thing i haven't been able to flash any sbf file since i have gotten the phone. I wanted to go back to stock because my webtop hack wasn't working through adb or gingerblur bloatware.zip in cwm. So extracted the SBF to the root of my c: drive,unzipped, renamed SBF, waited for connection, then it extracts 100%then fails and gives and error but it never restarted. But last night i ran rsd with the sbf from this link http://bandbinnovations.com/xda/OLYF..._1g_1FF.sbf.g[/url], and ran the sbf properly, but after it executed 100%, then started running the phone commands, but while running commands it stopped @86% and gave a error "switching device to bp pass error", i tried to flash this same file a second time but each time it stopped and gave the same error at 86%, and RDS completely stopped. so i unplugged the usb from my computer, and it was stuck at the M logo screen(all night). So i freaked out and thought it was bricked, because no sbf i have tried has worked for me, and my battery was getting low flashing SBF so many times. and almost called att warranty this morning. But this morning i turned my Atrix on and boom it was back to stock 1.2.6?Dont know how i did it,or how do it again properly, but glad im back to stock. But that was extremly confusing and frustrating!
Nice! What are the odds you and someone else have the same story and posted at the same time with the same login name? Musta been excited to post this story.
Clienterror said:
Nice! What are the odds you and someone else have the same story and posted at the same time with the same login name? Musta been excited to post this story.
Click to expand...
Click to collapse
Gotta raise post count somehow! Lol
Sent from WinBorg 4G using XDA Premium App
CaelanT said:
Gotta raise post count somehow! Lol
Ya that's it man. Sorry if I kinda in a hurry to get my phone working again. And I don't know how delete the other post or how I did it 2 times.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
which VERSION of RSD were you used?
RSD 5.0 or RSD 5.3.1 is OK for flash AT&T 1.26 or 1.5.7 or 1.8.3 SBF.
I flashed my ATT Atrix with RSD 5.0 many times, there's no issue every time.
jenhore said:
which VERSION of RSD were you used?u
RSD 5.0 or RSD 5.3.1 is OK for flash AT&T 1.26 or 1.5.7 or 1.8.3 SBF.
I flashed my ATT Atrix with RSD 5.0 many times, there's no issue every time.
Click to expand...
Click to collapse
I was using RSD 5.0 and trying to flash 1.2.6. On att. I don't know if its my computer or what, but I have tries it on 4 different sbf files on 3 computers. It finally went back to stock but I don't know how because it was bricked the night before.
Sent from my MB860 using XDA Premium App
Background:
I've rooted then unrooted my Droid X in the past. Today I tried to install the OTA Gingerbread update. After the download and the reboot the Droid X booted into Clockwork Recovery (as has been normal recently). After selecting reboot, the phone reboots and tells me the update has failed.
I attempted to SBF using this guide: droidforums dot net/forum/droid-x-hacks/99958-rooolers-guide-root-backup-roms-2-2-ota.html#3.
The file I used was: VRZ_MB810_2.3.15_1FF_01.sbf.
Now:
I have the following on my screen (black).
Bootloader
30.04
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Connect USB
Data Cable
I searched and found that I needed to use a 2.3.34 SBF, so I found this: SHADO_X6_2.3.34_SYSTEM-ONLY.sbf.
After SBFing with the new SBF I have the same result.
I'm stuck, I'm short on time, any help would be appreciated.
Thanks!
pvliii said:
Background:
I've rooted then unrooted my Droid X in the past. Today I tried to install the OTA Gingerbread update. After the download and the reboot the Droid X booted into Clockwork Recovery (as has been normal recently). After selecting reboot, the phone reboots and tells me the update has failed.
I attempted to SBF using this guide: droidforums dot net/forum/droid-x-hacks/99958-rooolers-guide-root-backup-roms-2-2-ota.html#3.
The file I used was: VRZ_MB810_2.3.15_1FF_01.sbf.
Now:
I have the following on my screen (black).
Bootloader
30.04
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Connect USB
Data Cable
I searched and found that I needed to use a 2.3.34 SBF, so I found this: SHADO_X6_2.3.34_SYSTEM-ONLY.sbf.
After SBFing with the new SBF I have the same result.
I'm stuck, I'm short on time, any help would be appreciated.
Thanks!
Click to expand...
Click to collapse
You need the full sbf.
Sent from my DROIDX using XDA App
You needed to use VRZ_MB810_2.3.34_1FF_01.zip. you can try that, if it doesn't work you might have completely bricked it.
Sent from my DROIDX using XDA App
Same thing happened to me this morning, but different ERR numbers. Verizon & Motorola were no help. Took it to the Verizon store, they forced Froyo 2.2 back on the phone. Its working now, but keeps trying to update. I am waiting until I get home to back up everything, then I will wipe the phone and let it update on its own. Seems to be a bootloader issue with either Bootstrap or rooting.
Sent from my DROIDX using XDA App
If I'm on GB my phone ALWAYS gives me a "code corrupt" after running the 2.3.340 full SBF. A system SBF afterwards always fixes the issue. Weirdly, I can't just do the system SBF. Its like I have to brick the phone with the full SBF and then repair it with the system SBF.
ashish8 said:
You needed to use VRZ_MB810_2.3.34_1FF_01.zip. you can try that, if it doesn't work you might have completely bricked it.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I'm running VRZ_MB810_2.3.34_1FF_01.sbf now. I'll post back with my results.
Thanks everyone for the input so far.
After flashing with VRZ_MB810_2.3.34_1FF_01.sbf it looks like we're back in business. Everything looks the way it was before I started all this.
I'll try updating to GB now and report back.
ashish8 said:
If I'm on GB my phone ALWAYS gives me a "code corrupt" after running the 2.3.340 full SBF. A system SBF afterwards always fixes the issue. Weirdly, I can't just do the system SBF. Its like I have to brick the phone with the full SBF and then repair it with the system SBF.
Click to expand...
Click to collapse
You should probably download the file again