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.
I had non rooted Kitkat 4.4.4 installed on N10. I received update intimation to Lollipop hence downloaded the update. While installing, message regarding error came followed with message "No command" . Now nothing is done further. Even tablet is not getting power off. Periodically screen displaying Google is coming followed with message "No command" I just checked. I can enter in to download and recovery. I now downloaded also Lollipop update for manual updating.
While connecting to PC, it starts searching for driver and after sometime message flashed "Driver not installed successfully" might be due to non detection of MTP. In such case if I try to maually install then ADB also is not recognising the connected device.
Can you suggest how best I can revive N10?
Regards,
Contnuing further, my main problen now is how to make my device visible in computer. I tried to install universal driver/ pda net driver etc. but no success. I feel unless this is done, I can not even use recovery options.
Kindly guide me. I keeps on wasting time on futile excercises.
Regards,
I got the same error last night - went straight for the wugs tool kit - problem is now solved
trriley5 said:
I got the same error last night - went straight for the wugs tool kit - problem is now solved
Click to expand...
Click to collapse
What did you do with the tool kit? Use it to install drivers or what? I've tried it and it does nothing for me except give suggestions on how to install drivers.
I've got ADB &SDK installed on my PC that works with my HTC One M8, so I imagine the drivers should work with my Nexus 10, don't you think?
Sent from my HTC6525LVW using XDA Free mobile app
I Have this problem also. I forgot that I had unlocked the Nexus 10, and let the OTA update install. It failed. I cannot get WUGs to talk to the tablet. If I let it boot I get "No Command"
If I go into Download Mode??? "Power + Sound Up" I get Start and an Robot laying down, says Downloading... but WUGs is never able to talk to it.
Atul Kaji said:
I had non rooted Kitkat 4.4.4 installed on N10. I received update intimation to Lollipop hence downloaded the update. While installing, message regarding error came followed with message "No command" . Now nothing is done further. Even tablet is not getting power off. Periodically screen displaying Google is coming followed with message "No command" I just checked. I can enter in to download and recovery. I now downloaded also Lollipop update for manual updating.
While connecting to PC, it starts searching for driver and after sometime message flashed "Driver not installed successfully" might be due to non detection of MTP. In such case if I try to maually install then ADB also is not recognising the connected device.
Can you suggest how best I can revive N10?
Regards,
Click to expand...
Click to collapse
please refer to my post from another thread regarding the fix for your nexus 10, I also encountered the same problem with you guys.. Below is the link. Thank you. :good:
http://forum.xda-developers.com/showpost.php?p=57001773&postcount=134
Thanks. Problem is solved now. Your guide is perfect.
Regards,
Hello I got this device (MS345) last week and today I was going to unlock bootloader, everything was going ok, i put the MS34510f_00 kdz and it got me an error (couldn't connect to server i think it was) but when I tried to reboot the phone it just gave me this lines that says "Secure booting error! Error Code: 1003" I can't get my phone booted normally or going to download mode or try recovery, when i try to do a factory reset I select the yes option but then it gives me the same security error, what can I do? please help me
It happened to me the same thing I had to use the warranty I did not find any solution
trixi3 said:
Hello I got this device (MS345) last week and today I was going to unlock bootloader, everything was going ok, i put the MS34510f_00 kdz and it got me an error (couldn't connect to server i think it was) but when I tried to reboot the phone it just gave me this lines that says "Secure booting error! Error Code: 1003" I can't get my phone booted normally or going to download mode or try recovery, when i try to do a factory reset I select the yes option but then it gives me the same security error, what can I do? please help me
Click to expand...
Click to collapse
When this occured with me i just reinstalled de stock rom with lg flash tool and this put me automatically into download mode when i connected my phone in pc
Hello everyone, so the story goes like this, my phone got the display shadered and so I went to change it, they changed the display but now when I turn it on it goes directly to the eRecovery Mode, there the option to erase the fragments doesn't appear, I can select between:
* Download latest version and recovery, which when I selected gives me a message saying "Getting package info failed"
* Reboot
* Shutdown
There's anyway to upload a new configuration to the phone from a PC? Or do you have any recommendation or advice for this issue?
Thanks in advance .
Hello,
download Firmware Finder, write model and brand info (for me FIG-LX1C432) t the search bar, select ONLY FullOta-MF firmware, check with your IMEI and use update throught DNS (eRecovery method)
Sorry for my english
https://www.google.com/amp/s/forum....upgrade-to-android-pie-throught-t3884054/amp/
sebbcv said:
Hello everyone, so the story goes like this, my phone got the display shadered and so I went to change it, they changed the display but now when I turn it on it goes directly to the eRecovery Mode, there the option to erase the fragments doesn't appear, I can select between:
* Download latest version and recovery, which when I selected gives me a message saying "Getting package info failed"
* Reboot
* Shutdown
There's anyway to upload a new configuration to the phone from a PC? Or do you have any recommendation or advice for this issue?
Thanks in advance .
Click to expand...
Click to collapse
Hello. I am not sure about your problem but I can suggest you do something, Reflash the img files.
https://openkirin.net/support/ Go there and you will see some guides
http://prntscr.com/nho9xr here is the order, you can give it a shot mate. hope this will help.