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.
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 ...................
So a couple days ago I installed MIUI to my phone. Everything went great, it booted successfully and worked for 2 days or so, until i accidentally let the battery die (not sure if this is related to the problem or not). Since this day, it wont charge or turn on while connected to the wall. When it is connected to the wall, it starts the screen and show a big battery with a question mark inside. I tried a friends battery and it gets stuck at the M logo. The only thing i can access now is the stock recovery screen. Any ideas on how to solve this? Thanks
viiniq said:
So a couple days ago I installed MIUI to my phone. Everything went great, it booted successfully and worked for 2 days or so, until i accidentally let the battery die (not sure if this is related to the problem or not). Since this day, it wont charge or turn on while connected to the wall. When it is connected to the wall, it starts the screen and show a big battery with a question mark inside. I tried a friends battery and it gets stuck at the M logo. The only thing i can access now is the stock recovery screen. Any ideas on how to solve this? Thanks
Click to expand...
Click to collapse
1.Download RSD Lite
2.Download the stock .sbf file for your device
3.Use your friends battery and boot into bootloader by holding Power+Volume Down+Camera button
4.Open RSD Lite, choose the .sbf file you downloaded, connect your phone to pc with usb cable and flash it.
If your pc doesn't reckognize your phone, you'll have to download and install the latest motorola milestone 2 usb drivers.
Ok. So i tried to apply the sbf file, but as soon as the process starts, RSDLite says under the status area "Phone[0000]:Creating Image File." and it wont get thru this. Any ideas?
Maybe try sbf_flash on linux?
Will the sbf_flash work the same on the mac? Or should they work differently on mac and linux? I tried it earlier today and i got stuck at some part i cant remember...I'll recharge the battery with a universal charger that i found (cause it's saying its too low to program) and try it again tomorrow, so i just wanna be sure that i can do it on the mac...
Thanks
It should work same way. OS X version is just port from the linux version.
You have to run RSDlite as an administrator. Right click on RSD.exe or RSDlite.exe not shure what's the exe file named and Run as administrator.
br Zola
having the same problem
after flashed MIUI/CM7
the battery died then the phone cant boot to desktop
tried RSD Lite, flash failed lol
Tried to run RSD as administrator. Still stuck at the same point.
Tried sbf_flash, stuck at 'waiting for phone:'.
I'll try to download the sbf file again, just in case it is corrupted.
Any other ideas?
PS.: I'm running rsd on VMWare, could this be the problem??
Dunno how exactly works USB bridge in VMWare, but rsd on pure (not virtualised) system is worth a try. Also - are you sure, your battery is charged? I know, that if your phone can't boot, the battery will not charge via USB - you should use universal charger or somebody here recommended (and successfully repaired MS2 this way) put contacts directly on the battery to charge it little (just for RSD flash).
I charged it on a charger that you put the battery directly into the contacts. I'm sure that it is charged cause 1) the led display on the charger says so and 2) when i get to bootloader mode to apply sbf, it says 'Battery OK / OK to program' , and before i charged it, it would say: "battery too low, cant program", or something like that.
I'll try to get a windows pc and try to apply the sbf
Thank you guys.
I was trying to flash it with a sbf that was on a pendrive. All i did was transfer the file to the HD and flashed it via RSDLite, using VMWare.
Now my phone is working again.
Thank you very much to everyone that helped me
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 too have a focus that is stuck in a loop at the Samsung logo. I bought it like that thinking I might be able to resurrect it as another toy. I have had lots of experience with Samsung, HTC and Sony droid phones, this would be the first WP.
It is a I917R on Rogers, there is no hardware revision under battery. I am assuming it is V1.3 as I have only seen software for the that version posted. I do not know how the phone got to its present state. They just said it happened during normal use?
I can get to both download mode and factory reset. I have flashed the stock rogers files without errors, but I never get the screen connecting to pc. The phone just restarts after successfully flashing, only to reboot continuously. I have been able to install MAGLDR and flashed every v1.3 ROM i could download. All without errors, just the same outcome they all just keep displaying Samung logo and then reboot. Only thing I noticed is that when I flash MAGLDR and custom ROMs it takes the phone longer to reboot.
I never get the connect to pc if I hold camera and power, nor do I ever get that screen when I flash a ROM.
Not sure if situation is similar... I am puzzled?
Your situation is very similar with other folks' here, unfortunately. It's not clear what causes it and there's no solution as of yet. For some, re-flashing worked. For others, a new battery. Most are stuck on loop...
When you connect the phone to USB when in download mode, what do you get?
When I boot to download mode I can flash Rom with WP7. I get to the yellow triangle download mode and flashes ok, no errors. Just noticed that it never goes to connect to pc mode.
Same with when I format, no connect to pc mode.
Nothing I try seems to help.
blackangel21 said:
When I boot to download mode I can flash Rom with WP7. I get to the yellow triangle download mode and flashes ok, no errors. Just noticed that it never goes to connect to pc mode.
Same with when I format, no connect to pc mode.
Nothing I try seems to help.
Click to expand...
Click to collapse
I see. What messages do you get when you connect the phone to the PC via USB, in either mode?
No messages, just shows up as Samsung USB composite device, Samsung mobile modem and Samsung mobile modem diagnostic serial port in download mode.
In magldr it shows up add Microsoft USB sync.
The only thing I forgot to mention was that when I flash with WP7 it finished without error in 90 seconds, but on the phone it says it will take 10 minutes.
Not sure what more I can add...
You could try different downloaders. Please see this thread for 7.41 downloader, maybe that helps?
Tried both, same outcome... No errors, just keeps rebooting... No Connect to PC message.
Im having the same problem. And i can see many other people who are having the same issue also. So i think its time to dump those phones, not worth a penny. The one i have in here was actually working, i followed all the directions in order to flash it. And still the phone got stuck into that bootloop. Its ridiculous from what i can see. I think ive read once you put that SDmini in it the phone will use it for the OS. But the one i had was working actually without it, i could turn it off as many times as i wanted and nothing happened. But if i tried a factory reset data would stay and diagnosis mode wasnt working. So i decided to flash it. Big, huge mistake! Hope you have better luck than i did. Because im dumping this one....
Same problem here, ive checked a couple of threads and no solution so far