okay guys here's my issue. I was flashing over to liberty and I forgot to wipe everything so as liberty was going through its stuff through bootstrap I pulled the battery hoping to stop the process.
HOWEVER, I am not stuck at the "liberty" logo. I have tried to sbf and I am getting....
failed flashing process: Phone (0000): Phone did not re-enumerate after RAM-downloader was sent. (0x703E) phone was disconnected.
Can someone please help me?
I've seen people have sucess with SBF errors by renaming the SBF file, trying a diff comp, and if ya vista or win7 ya have to be running as Admin. Give any of those a try that ya can while I'm looking over google to see if I can find anything more directly relevant to the errors you are getting.
Luckily I still have my x sitting around. I'm using macbook pro with vmware running windows 7. I have sbfed successfully on my x using the same setup.
Sent from my DROIDX using Tapatalk
I should also note that I tried booting into recovery and wiping data and cache still didn't help.
I do have a backup of stock from that I made. However, I just don't think its possible for me to access that backup to restore?
Sent from my DROIDX using Tapatalk
I'm not sure then. I've looked over quite a few different articles were people have had this problem, and have had it solved, and everytime it was some type of comp issue that was causing it. Some people fixed by changing USB ports, some by reinstalling the Moto RSD software (Also, with RSD, make sure you are using version 4.8 or 4.9), or using a completely different computer or OS. Past that the only other thing I can suggest is make sure you have the correct SBF file, and maybe try re-downloading it incase it somehow got corrupted during the download.
EDIT: Which recovery are you using? The stock recovery, or Clockwork? If ya using stock, then as far as I am aware you don't have the ability to backup/restore.
-Gilgamesh- said:
I'm not sure then. I've looked over quite a few different articles were people have had this problem, and have had it solved, and everytime it was some type of comp issue that was causing it. Some people fixed by changing USB ports, some by reinstalling the Moto RSD software (Also, with RSD, make sure you are using version 4.8 or 4.9), or using a completely different computer or OS. Past that the only other thing I can suggest is make sure you have the correct SBF file, and maybe try re-downloading it incase it somehow got corrupted during the download.
EDIT: Which recovery are you using? The stock recovery, or Clockwork? If ya using stock, then as far as I am aware you don't have the ability to backup/restore.
Click to expand...
Click to collapse
I am using rsd 4.9. I tried everything you stated except a new computer.
I have droid 2 bootstrapper installed and clockwork. However, whenever I boot into recovery it keeps bringing me to the stock one so I can't restore. If I can figure out how to restore maybe I would be good?
Sent from my DROIDX using Tapatalk
Likely you got far enough into SBF to erase clockwork. Though you can try pulling you battery during boot while its on the moto logo, and if clockwork is still installed it will then boot directly to it.
Yupp nothing. Stuck at the liberty boot logo where it says "liberty"
Sent from my DROIDX using Tapatalk
I donno then. I would try a diff comp and see if that helps. Or maybe someone else will see this thread and have some other ideas. You may could also try posting directly in the SBF thread, maybe someone with more experance with it will see it there? Just a thought.
Thanks for the help.
If anyone else can help I am all ears!
Sent from my DROIDX using Tapatalk
Ok, the bad news...
The first thing Liberty does when installing is format the /system directory. I dont know at what point you pulled the battery but, while you did at one time have bootstrapper and clockwork mod installed, you no longer do. Your only option at this point is to SBF.
I have had, as have others, lots of issues with getting it to go through on Windows 7. It will get to a point where it tries to switch modes (unfortunately I don't recall the name of that mode right now), then it wont find the driver fast enough and fail. If you can get that driver installed when it tries to switch modes, it should work, and cause no problems in the future. The problem for you though, may be even greater given that Windows 7 is bad enough and being run in VMware probably will just compound those issues.
If at all possible, try from a windows XP machine.
OK so im not sure about the Liberty ROM however I have had to SBF when I tried installing Fission 2.4.3 on my D2G.
My process was turning the phone on boot mode. This is done but holding the +- Volume button and then hitting the power button.
Next I got RSDLite 4.9 and lastest drivers from motorola. Next is restart computer! This was important as RSD wasn't finding my phone until I did. Once I restarted ran RSD hooked up the phone in boot mode found the sbf file and hit start. Took about 15 min to finish.
Not sure if this helps.
Rsd is finding my phone no problem right away. I suppose I should try it on a different computer though, one that's running xp.
Sent from my DROIDX using Tapatalk
buryboi said:
Ok, the bad news...
The first thing Liberty does when installing is format the /system directory. I dont know at what point you pulled the battery but, while you did at one time have bootstrapper and clockwork mod installed, you no longer do. Your only option at this point is to SBF.
I have had, as have others, lots of issues with getting it to go through on Windows 7. It will get to a point where it tries to switch modes (unfortunately I don't recall the name of that mode right now), then it wont find the driver fast enough and fail. If you can get that driver installed when it tries to switch modes, it should work, and cause no problems in the future. The problem for you though, may be even greater given that Windows 7 is bad enough and being run in VMware probably will just compound those issues.
If at all possible, try from a windows XP machine.
Click to expand...
Click to collapse
Do you know what driver your talking about or where to find it?
Okay guys I tried doing it on Windows XP and I am still getting the same exact message it wont' re-enumerate.
I am scared beyond belief right now and don't know what to do. If someone can suggest something I would really appreciate it.
Not sure if this helps, but this is what "my device" info says while in rsd lite...
IMEI/ESN/MEID:
N / A
Technology:
N / A
Software Version:
N / A
Flex Version:
N / A
Bootloader Version:
v0x00D011
DRM Version:
N / A
AP Die ID:
14b0001391953a0a0000d8ff0100
BP Die ID:
0000000000000000cd6932890485
AP Public ID:
6df40c77da38d6f01bc27cc2f40c041ee4491ae2
BP Public ID:
040000000500000002000000ffff0000ed153289
If you are on Win7 64 then try the drivers in the attached zip file.
It is the BP passthrough mode that fails at the end of the flash because it needs to load a separate interface to flash the baseband radio partition.
That interface is a Motorola Flash device MDM6600 and not the S-Flash OMAP3460 device.
If you are having trouble with the drivers loading during the flash cycle re enumeration then you can try this trick to get them to load.
Turn off the phone and then power on holding the Volume Up + Power.
The phone will boot to the M Logo and just stay there like it is hung.
It is now in BP passthrough mode and will enumerate as a Motorola MDM6600 flash device and Windows will attempt to load those drivers when you connect the USB cable. Point the New Hardware Found wizard to the folder where you extracted the zip and it should load them. If not, you may have to manually force it to load them in the Have Disk dialog.
Now pull the battery and reboot the phone normally and try flashing in RSD Lite again. You will already have the BP passthrough interface drivers loaded now and it should re enumerate and complete the flash of the baseband(CG5) and reboot the phone at the end. Wait at least a minute after it reboots for all the post boot initializations to complete and RSD Lite should eventually say Pass and allow you to disconnect without the error warning about damaging the attached device.
If none of this works, get an XP box and it will all work without any issues 99% of the time.
Good luck!
Okay... So I downloaded the drivers, connected via USB and it did show up as what you said it would. However, I then ran the sbf and it says "The Motorola AP flash interface could not be found and kept failing.
What do I do?
Also, another thing it now says my battery is low. If I just plug it into the wall, will it charge or do I need to USB it? I can't tell if its charging or not
nickb2005 said:
Also, another thing it now says my battery is low. If I just plug it into the wall, will it charge or do I need to USB it? I can't tell if its charging or not
Click to expand...
Click to collapse
It won't charge in the bootloader until you have software on your phone you need to use another D1 or D2 to charge. Or use an external charger.
If windows isn't working there are ways to flash in linux that usually yield better results.
Sent from my DROID2 using XDA App
I recently put a custom rom on my wife's D2G. Long story short, she doesn't like it and wants her phone back to stock.
I followed the directions in the thread Reverting To Stock , downloaded all necessary files but I am running into a problem.
When I load the DROID2WE_X6_2.4.29_FULL.sbf file into RSD Lite 4.9 nothing shows in the file properties box and the start button is not highlighted. The phone is detected, as it says in RSD Lite but yet I can't select start.
Any suggestions would be great before my wife kills me.
Thanks
Try following http://droid.koumakan.jp/wiki/SBF — if something goes wrong, tell which step exactly it was.
I can load the SBF in to RSD Lite. I can select start. The phone is detected and in Boot Loader Mode.
The problem i run into is:
1. There is no info displayed when I load the SBF
2. RSD starts but does not finish. The following message is displayed:
Failed flashing process. Fialed flashing process. Phone[0000]: Error switching phone to BP Pass through mode (0x70BE); phone connected
Let me quote what you apparently have missed on the page I linked.
Note: Under certain circumstances (especially when using Windows Vista and Windows 7) there might be a problem with not all device drivers being installed correctly. In such case, the flashing process will abort, and your phone won't be able to boot normally. To get around this issue, once you get a Device driver could not be installed message from Windows, don't close RSDLite nor power off the phone. Start Motorola Driver Installer once again, and let it finish. Then if RSDLite didn't timeout yet, head to Device Manager, find the Unknown device, and in its properties' Driver tab click Update driver…. It should now install normally. If RSDLite timed out and you got an error from it, just repeat the SBF process. The driver should now be present, and the flashing process will finish normally.
Click to expand...
Click to collapse
His problem is more likely a corrupted DL of the SBF file.
RSD lite should not need a connection to the phone to be working to display the SBF info, only the Phone info.
I suggest you re download the SBF file
Problem could be also coming from the location where the sbf file is saved. RSDLite is quite picky on that too. Make sure you save in a directory with short name and no spaces in it - for example C:\temp\ You can rename sbf to something like droidwe.sbf from the original very long name.
You can also avoid the issue of RSD not finding the file by dragging the file into the right pane of RSD lite. Also make sure you have chosen to run as administrator on the properties tab of the swdl.exe.
Accidently updated my atrix 2 to 2.3.6. I then severely wanted root so I tried to flash back. I kept trying to install rsd lite but kept getting error 2738 when it was almost done installing. I googled for fastboot tools and found one on this forum. When i tried to flash an img, it apparently did not work even though I choose this fastboot tool because it said it was for atrix 2 and had atrix 2 img's with it. Now, my phone is stuck in fastboot mode and my computer can't recognize it.Any tips or help are greatly appreciated.
Did you take out the battery and see if it will reboot?
Sent from my DROID3 using XDA App
a lot of times, I did. Jim is doing his best to help me via pm but I have stumbled onto a small yet major issue. EDIT I have fixed this issue and found another. I have rsd lite working on my old, crappy laptop. However the usb port isn't giving my phone enough power to even turn on.It only turns on when charging through the wall.
Atrix 2 stuck in fastboot mode
I update my atrix 2 to 2.3.6. OTA when it was released. I then update my phone to Supercharged V5 update 2. I hated that my phone could not run most games other phones with similar specs can run. I decided to install the drivers for chainfire 3d, the phone then rebooted past the red moto logo onto a blank screen. Ever since that happened i've only been able to boot into fastboot mode. I tried using the modified .xml file, and replacing the boot.img, cdt, device_tree etc. I don't know what else to do, this happened yesterday. This is also a warning to be careful with chainfire3d after update to 2.3.6. I used it before on 2.3.5 and i had no problem with it.
Hi I accidently deleted my system 1 partition in BMM, then it failed on me and since then It wont boot, I still see the motorolla logo when I turn my phone on then it goes to a lit up gray screen forever. I tried finding the stock FXZ for AT&T but cannot find it, and RSDLite 6.0 wont recognize my device for some reason. Any help would be appreciated thank you
Good times
motopeekz said:
Hi I accidently deleted my system 1 partition in BMM, then it failed on me and since then It wont boot, I still see the motorolla logo when I turn my phone on then it goes to a lit up gray screen forever. I tried finding the stock FXZ for AT&T but cannot find it, and RSDLite 6.0 wont recognize my device for some reason. Any help would be appreciated thank you
Click to expand...
Click to collapse
Hey there, allow me to point you in the right direction that should hopefully get you back up and running. Here's the link to the working SBF site for the AT&T fxz: Droid Devs SBF, if you had AT&T ICS before bricking then download the InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml zip file.
As for what to use to actually flash it with, RSD lite is notorious for giving many issues when trying to return to stock so what I personally use is this fast-boot script. It was made long ago by @alteredlikeness specifically for ICS, that will do the same thing with much less hassle. Here's the thread post with instructions on how to use it and the script download itself: FXZ Script. That should do it as long as you can get your phone into fastboot mode AND ensure your battery is charged enough or it will get stuck during the process (or not start if too low). Best of luck!:good:
My phone stopped working after I installed Chain Fire 3D and rebooted. I realized it was boot looping but didn't panic. First I tried the traditional method that always used to work and that is rebooting into recovery mode and wiping everything (ClockWork Recovery). Then I tried repeating it multiple times to no avail. After, I tried loading my latest backup. I then tried wiping everything multiple times and now ClockWork Recovery disappeared (I have no idea why). When all of that failed I tried using RSD Lite, but although my computer recognized my phone RDS Lite wouldn't recognize my phone even after installing the drivers and .sbf files. Now the battery is dead and I can only use the phone when it is plugged into the wall. I can load the boot loader, but no use anymore because the battery is dead. I can still use the system recovery which seems to be my only option of fixing it.
Key things:
•Chain Fire 3D was most definitely the cause
•Only works when plugged into the wall
•Not willing to cough up money for a new battery when fix isnt guaranteed
•I tried multiple different .sbf files and RSD Lite Versions (Which is why my phone's battery is so low)
Thank You for taking the time to read this. After trying everything that I feel should have worked I am open to any and all suggestions that may help.
XDA Visitor said:
My phone stopped working after I installed Chain Fire 3D and rebooted. I realized it was boot looping but didn't panic. First I tried the traditional method that always used to work and that is rebooting into recovery mode and wiping everything (ClockWork Recovery). Then I tried repeating it multiple times to no avail. After, I tried loading my latest backup. I then tried wiping everything multiple times and now ClockWork Recovery disappeared (I have no idea why). When all of that failed I tried using RSD Lite, but although my computer recognized my phone RDS Lite wouldn't recognize my phone even after installing the drivers and .sbf files. Now the battery is dead and I can only use the phone when it is plugged into the wall. I can load the boot loader, but no use anymore because the battery is dead. I can still use the system recovery which seems to be my only option of fixing it.
Key things:
•Chain Fire 3D was most definitely the cause
•Only works when plugged into the wall
•Not willing to cough up money for a new battery when fix isnt guaranteed
•I tried multiple different .sbf files and RSD Lite Versions (Which is why my phone's battery is so low)
Thank You for taking the time to read this. After trying everything that I feel should have worked I am open to any and all suggestions that may help.
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist.
Please create an XDA account so you can post within your device's forums found here:
Motorola Droid 2
Your questions will go here:
Droid 2 Global General
Good luck and welcome to XDA!