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.
Related
Guys,
First of all, hello to all! So, I followed a tutorial to install Froyo on my Defy. Now I'm stuck with my phone trying to boot as soon as i put the battery on, but it never makes it past the "M". I can get into recovery. I wiped data, cache and tried to install the "update.zip" but it aborts saying "signature verification failed." I have the boot file (that was the next step) to install using RSDlite 4.9 but the phone is not even recognized any of my USB ports. Any ideas? Thanks to all in advanced.
press volumn up buton and power button on boot , once you saw the backlit is on , release the button , you will see the rsd litle showing your usb .
dont worry . i think it is your first time to use RSD only
yea i been through that ( doesnt work on vista )
you need to install rsd lite and 2.51 UK Firmware ( no usa )
google it and you will find it or on this forum
install usb driver from motorola webiste
install rsd lite
put uk firmware in ... C drive/ program files / motorola / rsd lite
install driver
If your phone is stuck on " M " then pull battery out
turn on and quicky press power + vol up ( i think ) before M even appear
wait till it say your boot loader and your battery
plug phone in
start rsd lite
on ... look up your uk firmware that you you recently put in rsd lite folder
then you should see your phone connected on the 1 slot
then hit start or something and wait it out .
Thanks guys! But I've been messing around with this thing for so long, I drained the battery. I had to run it up to the local phone store to get it charged. I'll pick it up in a couple of hours and give your advice a try.
Hey guys! it worked! I'm up and running. Now, anyone has a link to bypass this Welcome to Motoblur screen. Is there a Custom Froyo or Gingerbread Rom out there without Motoblur?
Alright... I'm up and running, but no camera!!! Heck, it was a learning experience. I guess I'll go back to 2.1 now. LOL
So the Chinese ROM was rooted. I installed Clockworkmod and restored from the backup i had made of the original 2.1 OS. I'm back to a rebooting phone not making it past the "M" I went back to RSDlite and realized the boot file said 2.2 only. Can anyone assist me finding the right one to go back to original. I haven't been able to find a thread about reverting back to original.
The more I read, the smarter I get seems like the only thing I'm missing here is the SBF file for my original T-Mobile OS. I'm looking at the motorola website, but I can't find it. Can anyone point me to it? Thanks all! Oh yeah, this is the first android phone i mess with so my apologies.
There is no us sbf file. You have to flash a uk version and restore 3g with the posted fix. You can find the links to available sbf files on this forum. They are not available thru moto's site.
Sent from my ME525 using Tapatalk
Just to make sure I got it right. After using clockworkmod to restore to my factory backup, I need to use the UK sbf to be able to boot to it. Correct?
I found the sbf for Central Europe with no Motoblur. Does anyone know of any issues with it?
well the only way to fix this if you previously backed up your rom/files with recovery ( good thing i did this ). If not then you have to live with what you got.
I backed up my original firmware using clockworkmod. I flashed to the Chinese 2.2 but my camera didn't work. Since the camera is important to me, the Chinese Froyo was a deal breaker. I installed clockworkmod again and "recovered" from my original backup but now my defy won't boot. Did I miss a step?
Your data from the backup may cause issues when rolling backwards. Install an eclair sbf, then restore. That worked for me.
On another note there is a fix for the camera. Check the forums.
Sent from my ME525 using Tapatalk
Bricked Defy and not recognized by my USB
I also bricked my phone when going back to stock from cm7. My phone is able to go into boot loader. But it is not recognized by my desktop PC/RSDlite. I tried in linux with SBF_Flash. I tried with my laptop also. no luck . anyone please help me!
arulshoponline said:
I also bricked my phone when going back to stock from cm7. My phone is able to go into boot loader. But it is not recognized by my desktop PC/RSDlite. I tried in linux with SBF_Flash. I tried with my laptop also. no luck . anyone please help me!
Click to expand...
Click to collapse
Just try and install the Motorola Drivers in your desktop and open RSDLite and press 'show devices' button. It will surely show the details of your phone.
Then point RSDLite to the stock SBF and flash away.
kvigneshkrish said:
Just try and install the Motorola Drivers in your desktop and open RSDLite and press 'show devices' button. It will surely show the details of your phone.
Then point RSDLite to the stock SBF and flash away.
Click to expand...
Click to collapse
Thanks! Vignesh. But i have drivers installed. Tried uninstalling and reinstalling drivers. But did not help
Edit:
I missed to mention. My defy did not connect to desktop even before bricking.
arulshoponline said:
Thanks! Vignesh. But i have drivers installed. Tried uninstalling and reinstalling drivers. But did not help
Edit:
I missed to mention. My defy did not connect to desktop even before bricking.
Click to expand...
Click to collapse
If you hear the USB plugged in sound in your Pc, it's a messed up driver installation. If you don't hear the sound, it can be a bad cable, or a faulty microusb port (assuming that your pc usb works fine). Try once in a different pc and with a different microusb cable.
nsm1234 said:
If you hear the USB plugged in sound in your Pc, it's a messed up driver installation. If you don't hear the sound, it can be a bad cable, or a faulty microusb port (assuming that your pc usb works fine). Try once in a different pc and with a different microusb cable.
Click to expand...
Click to collapse
I do not hear any sound from desktop/laptop.
I think I stuck in boot loop. When I try to power on the phone, it just shows CM7 boot logo for few seconds then restarts again shows the boot logo... this happens continually. When I try to enter into recovery, it does not go to CWM recovery instead it goes to stock recovery. I am still able to enter into boot loader. In boot loader, it says battery OK connect USB to program. When I connect USB, it is recognized by phone and says transfer mode: USB. But my PC does not shows up the phone.
I tried re-installing drivers and RSDlite many times but no luck. But I have nandroid backup of CM7. Is there any possibilities to enter into CWM recovery?
Any help is appreciated.
Edit:
I tried even different USB cables and PCs also.
I have bootloader 30.04 after using liberty 1.5 I wanted to try out Rubix Focused. Everything was going well till my I tried to flash the watermarkd theme. Went through all the steps rebooted using Koush bootstrapper rocovery and when it restarted stuck at splash screen. After searching around I found out I could get into bootloader menu and reflash. My phone said low batteery cannot program. After cutting a USB in half and jump starting my battery I was able to get it into bootloader and it said battery ok, okay to program. Connect data cable. Make a long story short RSD lite will not recognize my phone I was using 4.9 and was later recommended to use 4.8 as a lot of people had trouble with 4.9 Any advice on this and how I can bring my phone back to life? I can get into boostrap recovery on the Android Recovery system which we all know is kinda useless for the purpose. Am I going to have to SBF Flash my phone? What if it wont recognize the phone after using 4.8 What are my options?! I need to get my phone up and running asap and i've been working on this for like 3 days now. Can anyone give me detailed instructions that could help me restore my phone? I did make a nandroid backup too, I just cant get to the bootstrap recovery for some reason. Only bootloader or Android Recovery. Please Help!!
Make sure you have the latest drivers installed. What OS are you using? If using Windows 7 you have to run as administrator(by holding shift + right click then click run as administrator . Also I had to rename my sbf file to C:/abc.sbf my computer would only recognize the sbf on the root of my C drive.
Alrighty, so my droid X will not stay in the bootloader long enough for me to flash it.
When it is in the bootloader, it will automatically boot up after a short period of time to the OS. The red motorolla boot image will come up while in bootloader mode.
What should I do?
Oh, and when I run the adb devices command in the command prompt... it says the device is always offline.
I'm trying to flash with this
VRZ_MB810_2.3.34_1FF_01.sbf
Nevermind... fixed the problem.
Thanks.
ok i got this problem too, how did you fix it?
I kept tinkering with the motorola drivers and changed USB ports, etc. I had to take out the battery and screw around with it a ton before it would start flashing. It just worked somehow... So stay persistent and keep at it, you'll eventually get it to flash back. Try using RSDlite 5.0 instead of 4.8 and uninstall / reinstall the Motorola drivers.
I used rsd 4.9. Also, make sure your sbf is on the root of your C: drive. I had to use my laptop because it wasn't working on my pc for some reason. Try a different computer. It'll prob work
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 ...................
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