So, I've exhausted just about every bit of time looking, searching, and trying everything to get my Droid 2 back working again. I'll explain everything I've tried plus the current error messages I'm getting and see if someone else can help.
Before we start, yes, I do have the current moto drivers (plus old drivers too). Yes, I've uninstalled, reinstalled the drivers and RSDLite a million times, and yes, I've rebooted after installing everything to make sure that wasn't the problem.
Right now, I've flashed the bootloader back to d2.35. But I can flash back to d2.37.
Using RSDLite, every time I flash it doesn't make it past the BP pass through mode. Right as soon as it gets to it, the computer disconnects the phone, and on the phone is says:
SW update...
Complete
And when it reboots it is still at the bootloader screen. I load into recovery, and it tells me that:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
Once I wipe cache/factory reset, I reboot and it still goes to bootloader screen.
So, I load into recovery again, and this time it gives me the error:
E: Can't open /cache/recovery/command
I've used RSDLite 4.7+patch and flashed, same thing.
I've used RSDLite 4.8/4.9/5.6 and so on, everytime, same thing.
I've burned the Linux iso to disc, booted that up, and flashed that way, same results.
I think that pretty much sums everything up. I've searched every forum, I've googled everything about the phone known to man. Usually I just silently lurk the forums since I've never encountered a problem flashing any other phone, but this one has me stumped. Thanks ahead for any information.
What is the name of the sbf you're trying to flash?
Sent from my EncounterICS droid 2
VRZ_A955_2.3.20_1FF_01.sbf
size unpacked: 455,586,301
packed: 253,561,045
Ok and what were you trying to flash when it broke?
EDIT: that is the correct sbf but you might want to check the md5
Sent from my EncounterICS droid 2
Yea, check the md5. Also, try to manually mount it in the linux terminal.
I'll check the md5 tonight, didnt think about that. And what was i trying to flash..? And mount it in a linux terminal?
Sent from my SCH-I400 using XDA App
The only md5's I can find of the file to verify it with say that it's incorrect. I'm trying several different downloads now to see if I can find one that matches. Anyone have a working sbf that I can check my md5 with theirs just to make sure?
http://wiki.cyanogenmod.com/wiki/Motorola_Droid_2:_Full_Update_Guide
That's where my SBF's come from whenever I need to go stock. Never had a problem with it before.
MD5 checks out now, flashed on Windows XP, still fails at BP pass through, and tried again on Windows 7, still fails at BP pass through. I honestly have no idea what's going on with it. I know the phone disconnects right as soon as it hits BP pass through mode. Then, it reboots the phone saying it's complete, then I pull battery, then wipe/erase, and still goes to bootloader. On the screen it shows:
WinXP:
Failed flashing process. Failed flashing process. Phone[0000]: Error switching phone to BP Pass through mode [0x70BE]: phone disconnected
Win7:
Failed flashing process. Failed flashing process. Phone[0000]: Error switching phone to BP Pass through mode [0x70BE]: phone connected
Is there any config settings that need to be specified? Or is the phone just a complete paper weight now?
I'm not sure exactly. I've never used RSDLite. I've only ever flashed on Linux.
Are you able to wipe Dalvik cache just to be sure? Also, just as a fail safe, if you have an SD card in there take it out.
Here's what I found:
Computer engineer here. Registered so I could post this and hopefully help a few of you guys out
I was running into the same problem, with Win7 x64, RSD Lite 4.6, latest drivers. Did some investigation into the error log and looks like I found a bug in their programming. Go into the directory you installed RSD Lite (for Win7 x64 the default is C:\Program Files (x86)\Motorola\RSD Lite\) and look for a file that starts with "FlashErrorLog". Open it, and if you see something like this:
Code:
Line: 865
ERROR: \\?\c:\SPRecovery_ESE81.sbfwtƒyoþÿÿÿ‚qawñrawðiµ was not found.
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashFileIO.cpp
then you are experiencing this same bug that I had (looks like adr3nalin3 had this problem too). For those fellow programmers out there, looks like they are copying the filename into uninitialized memory and not explicitly adding the NULL terminator, meaning it's pure luck whether the filename is recognized or not. Since the uninitialized memory produces random results, this explains why people have had it work after restarting their computer, trying several times, using a different computer, etc. Hopefully if you follow my instructions below, you will be able to make it work right away.
So the work around for this problem is to rename the file so that the real filename overwrites all the unwanted junk characters at the end. These junk characters are random, and they are likely to change each time you open RSD Lite.
Here are step by step instructions:
Go to the folder where you installed RSD Lite
Delete any files that start with "FlashErrorLog"
Right click on "SDL.exe" and click "Run As Administrator"
Move your recovery file to the root C:\ directory
Rename the recovery file to something short, like "r.sbf", so that you will have space left for the filename to overwrite the junk characters
Try flashing the file with RSD Lite - it will most likely fail, don't worry (if it works then good job, you are lucky )
In the RSD Lite folder, open the newly created FlashErrorLog... file
Count the number of junk characters after the real filename - for example if you have this error:
Code:
ERROR: \\?\c:\r.sbfqawñraï was not found.
then the junk characters are "qawñraï" and there are 7 of them, so we are going to add 7 extra letters to the real filename
Rename the file to add the same number of letters/numbers as junk characters in the log file. In this case, we need to add 7, so change the filename to something like "r1234567.sbf" - make sure you add the characters BEFORE the file extension (".sbf"), not after!
Point RSD Lite to the renamed file, click Start, and it should work!
Note that some of the junk characters can't be displayed in the log, so there might actually be 8 of them when you can only see 7, etc. Just repeat the process from step 6, adding 1 character at a time (don't remove any), and it should work after a few tries.
Note that just making the filename really long won't work, you need to be precise so that you only overwrite the extra stuff, nothing more and nothing less.
Click to expand...
Click to collapse
I hope that works for ya. Different phone, but same idea.
How do you wipe dalvik without clockwork recovery mod?
Sent from my SCH-I400 using XDA App
Try this tool
http://www.droidforums.net/forum/droid-2-hacks/161849-tool-ezsbf.html
It works 100% of the time for me. As long as you can get to the bootloader screen (by pressing the up button on the hardware keyboard while powering up), it will work. Please try it and let me know how it works for you. You will need a blank CD
Sent from my DROID2 using XDA App
I already tried that. It didnt work for me. Still get the same error messages as i stated in OP and after i wipe data it still boots to the bootloader.
Sent from my SCH-I400 using XDA App
ripdarkness said:
MD5 checks out now, flashed on Windows XP, still fails at BP pass through, and tried again on Windows 7, still fails at BP pass through. I honestly have no idea what's going on with it. I know the phone disconnects right as soon as it hits BP pass through mode. Then, it reboots the phone saying it's complete, then I pull battery, then wipe/erase, and still goes to bootloader. On the screen it shows:
WinXP:
Failed flashing process. Failed flashing process. Phone[0000]: Error switching phone to BP Pass through mode [0x70BE]: phone disconnected
Win7:
Failed flashing process. Failed flashing process. Phone[0000]: Error switching phone to BP Pass through mode [0x70BE]: phone connected
Is there any config settings that need to be specified? Or is the phone just a complete paper weight now?
Click to expand...
Click to collapse
read
http://droid.koumakan.jp/wiki/SBF
it's for the 2 global but should still work
also try deleting rsd lite error log
program files/motorola/rsdlite/ flasherrorlog11_15_24_45.log
yours will be different
Yeah, I don't know what it is. I think it's pretty much bricked. Nothings worked, and nothings even remotely came close to fixing it. I've tried everything. The only thing I notice is as soon as it hits BP pass through, the phone gets disconnected, and it doesn't reconnect till the phone reboots after saying:
SW update...
Complete.
And then it reboots into bootloader. So whatever it is, it's something to do with that.
Related
OK, so I have a D2 that someone gave me. It was completely stock (not rooted), but had all of their stuff on it still so I decided to do a factory restore through the android menus. The process started and the phone got stuck at the "M" logo, I left it for a few hours, and never budged.
I can NOT get into recovery, holding "X" and power on battery or connected to USB does nothing, have tried about 50 or 60 times now.
I can get to the bootloader and flash a new sbf (tried 2.3.20, 2.2.20, and downgrading the bootloader to d2.35) aside from the d2.37 bootloader I don't know of any other sbf's to try untill the GB one leaks, and who knows when that will be. I am using RSD lite 4.9 on win 7 x64, and 2.3.20 does not error out, also it identifies the phone as "s flash omap..." something instead of A955 or droid.
Sorry for the lengthy post, any help would be appreciated.
Edit: I tried flashing the 2.3.20 sbf from an ubuntu live CD with no joy. I just don't understand, i'm not getting any errors with ADB, it completes just fine, so recovery should be there for me to go into. The better part of 2 days trying to figure this out now.
Just a quick question, is recovery included in 2.3.20 full sbf?
Try it on a different computer. That worked for me. S flash is OK. As long as it says connected, you're good. You need to sbf. As long as you can get into Bootloader (2. 37)you can sbf.
Sent from my DROID2 using XDA App
That was the next thing I was going to try, need to get an OS on my old laptop to try, I have been busy so I should get to that sometime before the weekend. Dug out an old OG Droid that had the same issue that I could never figure out too, and got a custom recovery flashed, but no success on the full SBF or restoring a backup. Hopefully it is just this PC that is not playing nicely.
Thanks for the suggestion.
You can't get into recovery after you SBF? Is that what you mean?
wrichards2009 said:
You can't get into recovery after you SBF? Is that what you mean?
Click to expand...
Click to collapse
Exactly, it's like recovery is not there. Powering up while holding X does nothing, all I get is the "M" logo. I've let it sit and eat a whole battery just sitting on the "M". I will try to flash on another computer or two tonight and post my results.
Well I finally had time to try on another computer, and no luck. Used a freshly downloaded SBF, moto drivers and RSD Lite 4.8. Also I hadn't thought to check the logs before, and the FlashErrorLog has 4 errors, ERROR: AP Die ID, BP Die ID, AP Public ID and BP Public ID.
Everything went same as before, RSD completes with no errors. (well almost completes when I use my Motorola branded cord, stops at rebooting phone, and with my wifes LG branded cord, it reboots into the bootloader automatically, strange)
If anyone else has any ideas, I'm just at a complete loss here, willing to try something drastic at this point.
Having a similar problem, so hope you don't mind me piggybacking on your thread. I'm running 2.3.3 rooted on my D2, and I cannot boot into recovery either, but also can't get SBF to recognize my device on any computer. Any ideas?
How to get into Clockwork Mod
Is there a way to enter Clockwork MOD recovery on a rooted phone Manually? I am away from a computer, phone seems to be bricked need to get into recovery MANUALLY ...................
Tried to install several roms but every time it says it can't verify the info so I decided to do SBF.
Plugged in phone PC downloaded motoflash driver even though I have latest moto usb driver and shows up as this in RDS lite
Code:
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x00C106
DRM Version: N / A
Phone Type: Engineering (1D1D3410D773020000003C060000)
It goes through a few things and then gets to flashing but says FAILED phone is not compatible with multi-interface super-file. (0x703B)
I verified the SBF was the correct one, wasn't corrupt and was the correct md5 and tried a couple times with the same result.
What do?
I have this same issue. Can anyone tell us what that error means?
Depending on whether your sbfing froyo or gingerbread you need the most recent sbf of the two
Sent from my MB860 using XDA Premium App
Same problem.
I am having the same issue. I think I may have actually completely bricked my phone. I didn't think it was possible.
I was attempting to use ROM Manager to flash to MIUI. It then went into a boot loop. However, it does not even hit the eye. Just the 'M' screen.
When I try to boot into recovery, I get Andy with the triangle exclamation point, but the search button does not bring up recovery.
Most of the time my XP PC tells me that it does not recognize the hardware. When it does and I try SBF using RSDLite (4.8 and 4.9), I get the same as above and the log have hundreds of these entries:
[0x0000137c] E(08) [1000] CPSTSerialTIHelper:rocessPingCommand - Failed to get DIEID ACK
I have Moto Driver updater 5.2 with the latest droid drivers.
I tried using SBF_Flash for the MAC, and It gets stuck on "Waiting for phone..."
My guess is that the component that communicates from the phone is corrupted. Any thoughts or suggestions?
Thanks
First, to get into stock recovery you have to use the volume rocker once you get to andy, not the search ket (atleast seach hasn't worked for me, and you need to press both at once)
Second, you need to go into bootloader (idk if you have, but I didn't see it mentioned)
Third, make sure you have the correct SBF file (I use the triplethreat full sbf, which redoes kernel and system)
Fourth, I haven't seen a phone bricked yet, and I've been doin this for a bit of time, that was more in the early days of android.
Sent from my ApeX-ed, Overclocked, and Automated Droid 2.
I fixed my issues. It turns out that both my PC and My cables were having issues. I used a new machine with a fresh Moto cable, and was able to flash. Took 2 attempts, though.
Good luck
Great!! Glad it worked!
Sent from my ApeX-ed, Overclocked, and Automated Droid 2.
Hey there!
My beloved Droid R2D2 seems to be ailing in the form of being bricked. Nothing happened to it, it just decided that today (really three days ago) was a good day to get stuck in Bootloader on infinite loop. The battery is fully charged, whenever I turn on the phone it goes to:
Bootloader
D2.37
Battery OK
OK to Program
Connect USB
Data Cable
I can get into both Recovery and Bootloader the normal way (I've tried wiping my cache and setting it back to factory settings already) but can't seem to get to anything else.
I tried SBFing it using RSDLite v5.6 with the most recent drivers installed and the SBF file from the lovely droid developers site (specifically the 2.3.4 version). It gets to 100%, the phone restarts, but then I'm presented with the message:
Error switching phone to BP Pass through mode (0x70BE); phone connected
and a big FAIL in the Result box.
I've been looking all over for solutions so I wouldn't have to post this, but it seems everyone else has errors or corrupted codes with their bootloader, whereas mine seems to think it's okay.
I absolutely adore this phone and am by no means ready to give it up (they've even stopped producing them so any new phone would have to be a plain old regular Droid2...), so any help would be unbelievably appreciated!
http://droid.koumakan.jp/wiki/SBF
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. RSDLite shows the following error message:
Error switching phone to BP Pass through mode
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.
Once the flashing process is complete, RSDLite will tell you to “power the phone up manually”. In most cases you won't be able to do this straight as instructed: the phone will be bootlooping. Take the battery out, and then place it back in. Press the lock/power button: the phone should boot normally.
Close RSDLite. Disregard the warning about flashing not being completed since your phone has already booted into Android.
In case you still get bootloops after pulling the battery, refer to Android Recovery.
Click to expand...
Click to collapse
if you still no luck, to ezSBF
http://www.droidforums.net/forum/droid-2-hacks/161849-tool-ezsbf.html
Ah! ezSBF worked! This is both wonderful and unfortunate (I ordered a droid 4 to replace my phone deciding it really was dead so now I have to figure out whether to switch to the 4 or send it back for a few more months in the hopes that its price goes down a bit more...) but mostly really good to see old R2 alive and well again. Thanks!
ezsbf has helped a lot of people
Sent from my MB870 using xda premium
so i have a questions. i got mine rooted and deleted something i shouldnt have deleted. so i sbf back to stock. its says that the flash was successful but my r2d2 keeps bootlooping. any ideas
Which sbf did you flash?
Sent from my DROID2 using Tapatalk 2
did you try wiping cache or data?
delete this
jwagman1 said:
delete this
Click to expand...
Click to collapse
you decide to to read the thread? like 4 posts up
I'm attempting to repair a bricked DX. Bootloader is 30.04. It apparently had the 621 update, and of course, that's the only SBF that flashes.
However, in RSD Lite, across several versions, it fails at "Switching to BP Pass through" I've tried on windows 8, as well as a VM for windows 7. Moto device manager has been left in charge of the drivers. I've even tried XP 32-bit in virtualbox
sbf_flash on linux doesn't touch the BP to my knowledge, so even though it says it successfullyl flashes, I go right back to bootloader.
In recovery, trying to flash the 621 Verizon Blur zip fails after "updating BP", with a status 0 error message for "cannot open /tmp/sideload/package.zip" or something to that effect. Recovery is stock.
Yup, I've tried flashing from 621 to 604 with no luck. Can't flash the 604-to-621 package because it's stock recovery and I'm right back at the bootloader anyways. Yes I've factory reset after flashing sbf/recovery, etc, with no luck
Sooooooo, is this thing hard bricked?
tonglebeak said:
I'm attempting to repair a bricked DX. Bootloader is 30.04. It apparently had the 621 update, and of course, that's the only SBF that flashes.
However, in RSD Lite, across several versions, it fails at "Switching to BP Pass through" I've tried on windows 8, as well as a VM for windows 7. Moto device manager has been left in charge of the drivers. I've even tried XP 32-bit in virtualbox
sbf_flash on linux doesn't touch the BP to my knowledge, so even though it says it successfullyl flashes, I go right back to bootloader.
In recovery, trying to flash the 621 Verizon Blur zip fails after "updating BP", with a status 0 error message for "cannot open /tmp/sideload/package.zip" or something to that effect. Recovery is stock.
Yup, I've tried flashing from 621 to 604 with no luck. Can't flash the 604-to-621 package because it's stock recovery and I'm right back at the bootloader anyways. Yes I've factory reset after flashing sbf/recovery, etc, with no luck
Sooooooo, is this thing hard bricked?
Click to expand...
Click to collapse
It's been a while, but I remember having problems getting the process to work in Windows 7. I had to find an old Windows XP machine and it worked for me.
It may be worth trying to find a physical XP machine.
try the 621 ezSBF
DX (MB810) ezSBF & Root 2.3.4/4.5.621
Sent from my Amazon Kindle Fire using Tapatalk 2
sd_shadow said:
try the 621 ezSBF
DX (MB810) ezSBF & Root 2.3.4/4.5.621
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
When sbf_flash had no visible effects on my gentoo machine, I ran this iso in a VM and it still did not work. I'm thinking this is a hardware issue at this point. Updating BP fails from recovery's zip, and rsd lite fails at bp-passthrough mode no matter what I do, so it really looks like a hardware problem to me. I'm not sure what a physical xp machine will do that a vm couldn't.
usually the "Switching to BP Pass through" error, is a windows driver error, not a phone hardware failure
but it can be a hardware failure
also which version of rsd lite tried 6.1.4
one way to check driver, right after you see Switching to BP Pass through, open windows device manager and look for
an unknown device or a yellow triangle in of a device, fix a bad/missing driver can be a little tricky
Start Motorola Driver Installer once again, and let it finish. Then ... head to Device Manager, find the Unknown device, and in its properties' Driver tab click Update driver…. It should now install normally.
or
burn the ezSBF iso file to a cd or usb, and boot pc from ezSBF boot disc, vm is not the same thing as the real thing, vm does not always work
In recovery, trying to flash the 621 Verizon Blur zip fails after "updating BP", with a status 0 error message for "cannot open /tmp/sideload/package.zip"
Click to expand...
Click to collapse
moto updates only update, unlike some other android devices, the update only works if the older software is installed, and verified completely stock
sd_shadow said:
usually the "Switching to BP Pass through" error, is a windows driver error, not a phone hardware failure
but it can be a hardware failure
also which version of rsd lite tried 6.1.4
one way to check driver, right after you see Switching to BP Pass through, open windows device manager and look for
an unknown device or a yellow triangle in of a device, fix a bad/missing driver can be a little tricky
Start Motorola Driver Installer once again, and let it finish. Then ... head to Device Manager, find the Unknown device, and in its properties' Driver tab click Update driver…. It should now install normally.
or
burn the ezSBF iso file to a cd or usb, and boot pc from ezSBF boot disc, vm is not the same thing as the real thing, vm does not always work
moto updates only update, unlike some other android devices, the update only works if the older software is installed, and verified completely stock
Click to expand...
Click to collapse
I've tried 4.7, 4.8, 5.7...regarding the device manager thing, I have never had to worry about an unknown device in dev manager. It always showed
"Motorola Flash Interface." during the bp passthrough. I've even gone as far as changing the driver to "Motorola BP Flash", etc during and before the flash with no change in results.
With the .zip update, it gets past the "verifying system" portion. It verifies, patches boot files, patches system files, then when it hits updating BP, it fails. If I decide to play with this again I will take a picture of the recovery screen.
Is there a cwm sbf available so I can at least get adb
tonglebeak said:
Is there a cwm sbf available so I can at least get adb
Click to expand...
Click to collapse
no there is not, because of the locked bootloader, the only way to access CWM is with a bootstrap app, which creates a boot hijack.
linxi
help you
Download mode, but cant dl anything from pc to phone now even using odin.
Phone just stuck in boot loop.
Got as far as loading twrp onto it via odin and then when tried search for file just blank folders, nothing in them.
So worried totally bricked it. everyone says get into safe mode, but when try to all it goes to is twrp.
HELPPP!!!!
If you can get into TWRP and aree able to do a complete wipe. It will return your OS to factory settings and fix the boot loop. Other wise try the emergency recovery on Smart switch.
You will need your model information as well as the phone serial number.
Oh,
even phone storage showing "0" in twrp and try wipe just fails.
Cosmic Blue said:
If you can get into TWRP and aree able to do a complete wipe. It will return your OS to factory settings and fix the boot loop. Other wise try the emergency recovery on Smart switch.
You will need your model information as well as the phone serial number.
Click to expand...
Click to collapse
Hi,
Thanks for the reply.
TWRP, tried wipe and few other options on twrp and all says failed.(as does odin now)
The weird thing is was all going fine till went to look for the zip files put onto phone before loading twrp which video said too, but when went to folder that SHOULD show all phones system/pic/video forlders and the 2 zip files I put on phone, it is all gone, folder and all folders showing empty. even internal memory showing as empty.
Magisk-v13 rooting instructions video was what I used.
Have just dl smart switch.
All this because fast charge wasn't working and battery drain fast. Guess thats why seller never sent me the quick charger kit and usb and just a wireless charger with old 0.7mah old samsung charger. 6-7H to charge.
Got another fastcharger but didnt work with the phone.
Just reading about smartswitch and seems can only use if can run from my s7 edge phone. but cant get back into phone.??
Dl it to pc and just tried to run it and yep, saying
app failed to start because its side by side config is incorrect???? Please see app event log to use the command line sxstrace.exe tool for more detail.
Sorry,
Now just more confused
Right,
Out of desperation I found a file, which to a useless tech head like me seemed to ring a bell being a md5 file and can with my odin download, so loaded it up and after 4 tries of
to catch the bootloop with pressing start and holding down and releasing the buttons on phone while starting odin with the file it worked and dl file onto phone, phone restarted after few minutes and then worried for a minute when just flashed the samsung logo, but RESULT. Loaded up, only to ask for pass code, put mine in and said wrong so tried the trick to get into bottloader system reset screen and reset to factory setting AND ALL Good again, just fresh start again.
So for anyone and future info/help the file that saved my AR*E was
cf-auto-root-hero2lte-hero2lte-smg935f.tar
So if need do a search guys or if ok can post a link to one on here if OK ?
imbloodyskintagain said:
Dl it to pc and just tried to run it and yep, saying
app failed to start because its side by side config is incorrect???? Please see app event log to use the command line sxstrace.exe tool for more detail.
Click to expand...
Click to collapse
Updating for future reference/help anyone gets same issue with smartswitch(windows 10)
Google came up with answer,
needed to dl and run.
2008 Microsoft Visual C++ Redistributable package(x86)
This fixed the smartswitch exe file not starting issue.