My friends purchased a Droid Pro with CM9 already loaded onto it. He asked for my help because he was experiencing bugs and wanted to go back to a stock ROM.
I installed the Motorola drivers.
I put the phone into clockwordmod recovery and cleared all the caches and battery stats.
I then restarted into the Bootloader and started up a current version of RSD lite on my Win7x64 installation.
Next I got the SBF file loaded up in RSD lite and started flashing.
As it was nearing completion I picked up the phone to "catch the boot" and in the process bumped the USB cable just enough to terminate the connection and the process failed.
Now I can't get passed the Bootloader which says Code Corrupt.
I have spent hours upon hours scouring the internet trying different fixes to fix this problem.
Now when I try to flash it again with RSD lite it gets stuck when switching the phone to PB pass through and FAILS with the error 0x70be because it can't find the driver for MDM6600 and my system labels it as an unknown device.
I have since installed WinXPx84 on my system and tried the SBF process over and over in different ways hoping that it will take.
Any insight is greatly appreciated.
Thank you,
PEZ
PEZ Dispenser said:
My friends purchased a Droid Pro with CM9 already loaded onto it. He asked for my help because he was experiencing bugs and wanted to go back to a stock ROM.
I installed the Motorola drivers.
I put the phone into clockwordmod recovery and cleared all the caches and battery stats.
I then restarted into the Bootloader and started up a current version of RSD lite on my Win7x64 installation.
Next I got the SBF file loaded up in RSD lite and started flashing.
As it was nearing completion I picked up the phone to "catch the boot" and in the process bumped the USB cable just enough to terminate the connection and the process failed.
Now I can't get passed the Bootloader which says Code Corrupt.
I have spent hours upon hours scouring the internet trying different fixes to fix this problem.
Now when I try to flash it again with RSD lite it gets stuck when switching the phone to PB pass through and FAILS with the error 0x70be because it can't find the driver for MDM6600 and my system labels it as an unknown device.
I have since installed WinXPx84 on my system and tried the SBF process over and over in different ways hoping that it will take.
Any insight is greatly appreciated.
Thank you,
PEZ
Click to expand...
Click to collapse
Woah woah woah. Windows x84?
Sent from my Nexus 7 using xda app-developers app
BlackFire27 said:
Woah woah woah. Windows x84?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
x84 is just another way of saying 32 bit
I think it is x86. Back on topic. So, try downloading another sbf that is from before 4.7.8 Try sbfing that
Sent from my Amazon Kindle Fire using Tapatalk HD
Vlasp said:
I think it is x86. Back on topic. So, try downloading another sbf that is from before 4.7.8 Try sbfing that
Sent from my Amazon Kindle Fire using Tapatalk HD
Click to expand...
Click to collapse
Ah, my bad, yes x86. Like I said I've spent hours and hours on this and missed some sleep.
I will look into and try other SBFs however I have been having trouble locating good links considering the age of the device. Know of any resources?
What do you mean by 4.7.8? I can't find any information on that. The SBF files that I have tried flashing are 2.26.20 and another one I found for the Droid Pro that is just labeled 3087.sbf
PEZ Dispenser said:
Ah, my bad, yes x86. Like I said I've spent hours and hours on this and missed some sleep.
I will look into and try other SBFs however I have been having trouble locating good links considering the age of the device. Know of any resources?
What do you mean by 4.7.8? I can't find any information on that. The SBF files that I have tried flashing are 2.26.20 and another one I found for the Droid Pro that is just labeled 3087.sbf
Click to expand...
Click to collapse
my bad 4.7.3. Try that one by searching on google.
Sent from my Amazon Kindle Fire using Tapatalk HD
Vlasp said:
I think it is x86. Back on topic. So, try downloading another sbf that is from before 4.7.8 Try sbfing that
Sent from my Amazon Kindle Fire using Tapatalk HD
Click to expand...
Click to collapse
ah, I see, 4.7.8 is the blur version. Downloading 4.6.8 now. Hopefully that works.
Have I permanently bricked a phone for the first time?
Ok, so now I have tried 4.6.8, 4.7.3, 4.7.8 and probably also a couple others by now with no luck.
All of them get error switching phone to PB pass through mode (0x07BE). My system cannot find the driver for MDM 6600 and my systems will only see it as an unknown device after RSD light trys to do the PB mode switch. I have tried installing the driver pack after the PB switch, which doesn't work. Extracting the drivers to a location that I then direct device manager to and that doesn't work.
Any other ideas on how to get this good hardware back and going again?
I will try the process on a completely different computer tomorrow, maybe the OS switch wasn't enough and there is a conflict with my machine. I doubt it though because I have used this machine to work on my D3.
PEZ Dispenser said:
Ok, so now I have tried 4.6.8, 4.7.3, 4.7.8 and probably also a couple others by now with no luck.
All of them get error switching phone to PB pass through mode (0x07BE). My system cannot find the driver for MDM 6600 and my systems will only see it as an unknown device after RSD light trys to do the PB mode switch. I have tried installing the driver pack after the PB switch, which doesn't work. Extracting the drivers to a location that I then direct device manager to and that doesn't work.
Any other ideas on how to get this good hardware back and going again?
I will try the process on a completely different computer tomorrow, maybe the OS switch wasn't enough and there is a conflict with my machine. I doubt it though because I have used this machine to work on my D3.
Click to expand...
Click to collapse
now lets go 1 step back on rsd lite and downgrade to the second latest version. and install the Motorola bootloader drivers or normal drivers with that. quick question. can you boot past the error screen into the recovery? It is R and Q and Power button. when the M screen is present.
Sent from my Amazon Kindle Fire using Tapatalk HD
Vlasp said:
now lets go 1 step back on rsd lite and downgrade to the second latest version. and install the Motorola bootloader drivers or normal drivers with that. quick question. can you boot past the error screen into the recovery? It is R and Q and Power button. when the M screen is present.
Sent from my Amazon Kindle Fire using Tapatalk HD
Click to expand...
Click to collapse
I'm using RSD lite 6.1.5, so you say I should try 6.1.4 or another older version?
What is the difference between Motorola bootloader drivers and normal drivers?
I thought it was R and M and the Power button to get into recovery. Anyway, I tried R and Q which does not work either. Doesn't look like I can get into recovery. Can I flash a recovery system onto it with RSD lite and then fix it from there?
Thank you Vlasp for taking the time to help me out with this.
PEZ Dispenser said:
I'm using RSD lite 6.1.5, so you say I should try 6.1.4 or another older version?
What is the difference between Motorola bootloader drivers and normal drivers?
I thought it was R and M and the Power button to get into recovery. Anyway, I tried R and Q which does not work either. Doesn't look like I can get into recovery. Can I flash a recovery system onto it with RSD lite and then fix it from there?
Thank you Vlasp for taking the time to help me out with this.
Click to expand...
Click to collapse
I am getting all of my facts mixed up. It is R and M, and there are no bootloader drivers. and regarding the rsdlite, try the 6.1.4 or something.
Sent from my Amazon Kindle Fire using Tapatalk HD
You can flash the bootloader update, and then try flashing again... 4.04 or something like that... I cant check as my phone got stolen last week, but I think it may solve your problem
donlloreda said:
You can flash the bootloader update, and then try flashing again... 4.04 or something like that... I cant check as my phone got stolen last week, but I think it may solve your problem
Click to expand...
Click to collapse
I haven't been able to find any information on this or any other bootloader update. Can you maybe point me in the right direction?
try turning off firewall and flash it again
Sent from my Motorola MB612 using xda app-developers app
Hot-dog007 said:
try turning off firewall and flash it again
Sent from my Motorola MB612 using xda app-developers app
Click to expand...
Click to collapse
I'm not sure how that is supposed to help and the firewall was already disabled anyway.
When RSD lite finishes flashing and wants to switch the phone to PB pass through mode the system sees my phone as an unknown device and won't install the correct driver correctly. I do have the option to select which driver to install and can find Motorola from the menu but then I am faced with about 10 different options on what specific device driver to install. One of them is Motorola PB interface, one of them is Motorola Flash interface, etc etc. I've tried the PB interface driver and it seems like it installs but it still shows up as an unknown device on my system and the flashing fails.
try sbf_flash using linux
Related
So just so I could see how the whole process worked I decided to SBF. Well, it seems to have failed. It gets to a point in the flash process where it says "Switching phone to BP pass through". It fails on this step at 99% then says FAIL on the process. So now the only way to turn it off is to pull the battery. As soon as I put the battery back in it goes to the bootloader screen and says "Code Corrupt" but down on the other part it says "OK to Program"
anyone know anything I can try? Different computer perhaps?
can you get into recovery mode?
dekend said:
can you get into recovery mode?
Click to expand...
Click to collapse
Nope, only to the bootloader.
what OS are you using? 32bit?
Have you tried another comp yet?
possible driver corruption.
I'm assuming you've tried to reflash it again. In the past back flashing Moto flip phones I've had RSD Lite fail like that also. Just took flashing it again until it finally took and was good to go. Heck I remember I was flashing a v3c to Telus software and the darn power went out in the middle of it. Took me about 10 flashes after that to get it to take as something got corrupted because the power went out in the middle of the flash. Kinda why I always flash with my laptop nowdays....lol.
dekend said:
what OS are you using? 32bit?
Have you tried another comp yet?
possible driver corruption.
Click to expand...
Click to collapse
I was using 64bit Windows 7, but I was using it in VMware. I've got 32bit XP up and running on a new machine now (not virtual) and I'm about to try with that.
Never had a problem flashing with VMs before but that may be the problem. Who knows.
mrnosox said:
I was using 64bit Windows 7, but I was using it in VMware. I've got 32bit XP up and running on a new machine now (not virtual) and I'm about to try with that.
Never had a problem flashing with VMs before but that may be the problem. Who knows.
Click to expand...
Click to collapse
VM is definitely the problem -- I had the same issue with my D1. I think it's not loading the drivers correctly when the USB mode switches between ADB Flash interface and whetever comes next. I was able to re-SBF it using native XP 32-bit, so hopefully you can, too.
The same exact thing happened to me. Turned out the problem was that i was using an old version of RSD Lite. You NEED 4.7 for it to flash correctly. I was using 4.6. As soon as I updated, I plugged in via usb while in "Code Corrupt" bootloader and reflashed. Worked fine after that.
Sent from my DROIDX using XDA App
btdownloads7 said:
VM is definitely the problem -- I had the same issue with my D1. I think it's not loading the drivers correctly when the USB mode switches between ADB Flash interface and whetever comes next. I was able to re-SBF it using native XP 32-bit, so hopefully you can, too.
Click to expand...
Click to collapse
Yep, I loaded XP on my MBP in a bootcamp parition and it flashed the first time. It's Alive!
mrnosox said:
Yep, I loaded XP on my MBP in a bootcamp parition and it flashed the first time. It's Alive!
Click to expand...
Click to collapse
Nice, glad to hear you got it back going again.
I have a question...ok my phone is rooted used easy root....ok then I download boot strap now I want go back top stock what I have to do
Sent from my DROIDX using XDA App
If you still want to use some sort of virtual software on your mac, I recommend Parallels. I have the 5.0 version and running XP on the newer generation MBP.
SBF works like a charm. I don't use Boot Camp simply because I want access to both OS's at the same time.
If you can setup a Linux box, I'd use sbf_flash. Sooooo much easier.
i am tryint to flash the updated sbf for the atrix and the start button on RSD is greyed out. it does the same thing with the older retail version as well. is there something wrong with the drivers or something?
graemegb said:
i am tryint to flash the updated sbf for the atrix and the start button on RSD is greyed out. it does the same thing with the older retail version as well. is there something wrong with the drivers or something?
Click to expand...
Click to collapse
Make sure you put the. Sbf in the rsd lite folder, I had the same problem.
Sent from my MB860 using Tapatalk
like in the install folder?
ok, i got the start button to work, but now i get an error. "Failed flashing process. failed flashing process. (0x7100); phone connected"
You have the phone in rsd mode? I had a problem where my main laptop wouldn't flash it for some reason but when I used another I had it worked.
Sent from my MB860 using Tapatalk
Clienterror said:
You have the phone in rsd mode? I had a problem where my main laptop wouldn't flash it for some reason but when I used another I had it worked.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
yeah its in rsd mode. maybe if i bood in to windows with driver signing disabled?
i have the same error flashing the stock sbf and not the first leaked sbf
just found this guide. and it worked! http://groups.google.com/group/shadowmodbr/browse_thread/thread/e0a19659f5fb7683?pli=1
Ok so i was planning to flash my defy with the leaked 2.3.4 gingerbread but when it came time to connect it to the rsdlite, it wasn't detected. The drivers installed fine.
I followed this tutorial:
http://forum.xda-developers.com/showthread.php?p=14976942#post14976942
Things checked:
Bootloader was on when connected
Battery full
I tried multiple methods:
Running RSDLITE with safemode
running rsdlite admin access
installing rsdlite 4.9
installing rsdlite 5.3.1
installing motorola drivers 5.1
installing motorola drivers 5.2
So now i can't flash the shadow4.5.1-134fixed.sbf.
Doing this step:
4. Select “shadow4.5.1-134nandroid” and choose “System Only”
I can't load into my phone to access ClockworkMod Recovery to revert that.
So now when i boot up my phone it is stuck at the motorola symbol.
What i can do:
access bootloader
access recovery module
Pull out battery.
Reinsert battery while holding volume up key.
Phone should say ok to program.
Sent from my MB525 using XDA App
Red should detect then
Sent from my MB525 using XDA App
Tried that and RSDLITE still doesn't detect. I tried installing RSDLITE on a different laptop but same issue.
i have a feeling its because of the 64bit windows 7. Has anyone got it to work on other flavours of windows?
I'm having the same issue.. tried the pulling battery out and back in with volume up with no luck..
any solution?
i'm having the same problem
thanks
Any solution?
I have the same problem. Any help is appreciated. Thanks!
arulshoponline said:
Any solution?
I have the same problem. Any help is appreciated. Thanks!
Click to expand...
Click to collapse
just go to boot loader then connect phone to PC... RSd will detect it...
Sent from my MB526 using xda premium
nogoodusername said:
just go to boot loader then connect phone to PC... RSd will detect it...
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Thanks for your reply. I was also trying to connect USB when phone is on boot loader. Even computer itself does not recognize the phone.
try using another version of rsd
Sent from my MB526 using xda premium
Yeah my solution was that i installed windows XP on the same laptop, installed the same version of rsd lite and it was detected. I don't think you have to do something that strenuous but you could try installing a different version of rsd lite. I think the latest one is 5.6 and it works in detecting my phone on windows 7 x64.
munky88 said:
Yeah my solution was that i installed windows XP on the same laptop, installed the same version of rsd lite and it was detected. I don't think you have to do something that strenuous but you could try installing a different version of rsd lite. I think the latest one is 5.6 and it works in detecting my phone on windows 7 x64.
Click to expand...
Click to collapse
Thanks for replies. I tried RSD lite 5.6
4.9
4.8
4.6
on windows7 x64. But no luck.
Not only RSD lite, even computer also does not detect the phone. I tried in my laptop also which is running windows7 x64. I will try it in XP also tomorrow.
---------- Post added at 10:17 PM ---------- Previous post was at 10:12 PM ----------
I tried re-installing driver 5.5.0 also.
Check if you have any belkin router software installed. I remember reading on some topic that, the USB monitor of that software was interfering with rsd lite
Sent from my MB526 using XDA
shadenight said:
Check if you have any belkin router software installed. I remember reading on some topic that, the USB monitor of that software was interfering with rsd lite
Sent from my MB526 using XDA
Click to expand...
Click to collapse
Yes, I also read that thread and checked for it. I do not have belkin router software installed.
Sorry to missed this post.
I have the very same problem.
I tried each and every probe googled.
No luck.
Finally I have to install a brand new x86 Windows 7 Ultimate (I think not particularly ultimate, any would do e.g. home, home premium...etc).
To me it is the x86 that hinders me from recognizing the phone.
Sorry, it should be rsdlite not working along with x64 but seemless with x86.
Hope this helps !
kneepain said:
Sorry to missed this post.
I have the very same problem.
I tried each and every probe googled.
No luck.
Finally I have to install a brand new x86 Windows 7 Ultimate (I think not particularly ultimate, any would do e.g. home, home premium...etc).
To me it is the x86 that hinders me from recognizing the phone.
Sorry, it should be rsdlite not working along with x64 but seemless with x86.
Hope this helps !
Click to expand...
Click to collapse
Thanks for the reply. I found this is due to hardware issue. I sent it to service they replaced the board (with Defy+ board). Now it is working good with 2.3.6 defy+ stock ROM. Upgraded to Defy+!
arulshoponline said:
Thanks for the reply. I found this is due to hardware issue. I sent it to service they replaced the board (with Defy+ board). Now it is working good with 2.3.6 defy+ stock ROM. Upgraded to Defy+!
Click to expand...
Click to collapse
arulshoponline, I am suffering with this prob for soo long.. all the forums have been of very little help to me.
First, I rooted my phone and then installed the cyanogen 7.2 mod instead of 7.1 by mistake. Everything was going as instructed by various tutorials.. Then when the device rebooted, it was stuck on the screen showing android & cyanogen mod logo with an arrow going round and round(in blue). It kept repeating itself. Thinking my phone froze, I removed the battery. Upon reboot, it Got stuck at the "Google" image which replaced the original Motorola symbol after the update. Ever since I cannot get RSD Lite to recognize the device even after installing Motorola Helper drivers as well as the phone drivers. I am frustrated and seriously thinking of just getting a professionals help.
Any suggestions anyone?? The SBF file i used is JRDNEM_U3_3.4.3-11_BLUR_SIGN_SIGNED_USAJRDNEMARAB1B8RTGB03A.0R_PDS03C_USAJRDNFRYORTGB_P010_A007_HWp3_Service1FF.sbf
is this the wrong one?
arulshoponline - Where did you give your phone for service? Did you give it to Moto itself? or some local repair store?
P.S I was initiallly running Froyo 2.2.1 and wanted to upgrade to Gingerbread 2.3.4 when all this happened I am running on Win XP, currently with RSD 5.3. I have tried 4.9 and 5.0 so far.
akira.nev said:
arulshoponline, I am suffering with this prob for soo long.. all the forums have been of very little help to me.
First, I rooted my phone and then installed the cyanogen 7.2 mod instead of 7.1 by mistake. Everything was going as instructed by various tutorials.. Then when the device rebooted, it was stuck on the screen showing android & cyanogen mod logo with an arrow going round and round(in blue). It kept repeating itself. Thinking my phone froze, I removed the battery. Upon reboot, it Got stuck at the "Google" image which replaced the original Motorola symbol after the update. Ever since I cannot get RSD Lite to recognize the device even after installing Motorola Helper drivers as well as the phone drivers. I am frustrated and seriously thinking of just getting a professionals help.
Any suggestions anyone?? The SBF file i used is JRDNEM_U3_3.4.3-11_BLUR_SIGN_SIGNED_USAJRDNEMARAB1B8RTGB03A.0R_PDS03C_USAJRDNFRYORTGB_P010_A007_HWp3_Service1FF.sbf
is this the wrong one?
arulshoponline - Where did you give your phone for service? Did you give it to Moto itself? or some local repair store?
P.S I was initiallly running Froyo 2.2.1 and wanted to upgrade to Gingerbread 2.3.4 when all this happened I am running on Win XP, currently with RSD 5.3. I have tried 4.9 and 5.0 so far.
Click to expand...
Click to collapse
Sorry for you akira.nev. I also really felt bad when mine went wrong. I gave it to Moto service they also said RSD & computer do not detect the phone and advised to change the board. It cost me 2000INR.
Did your phone get connected with the computer thru USB before flashing cm7?Did you try to flash with RSD from another computer? Do you hear any sound when you plug in your device?
P.S Use the latest RSD. It works seamless in my laptop with Windows7 x64 home basic.
McGuver. Hack works
Sent from my MB525 using Xparent Cyan Tapatalk 2
First of all, I already found a lot of helpful info on this forum. Thanks for that!
But now it seems I am really stuck.... I searched through the forum, but still couldnt find any solution to my problem.
After succesfully flashing a custom rom, I wanted to try a different one.
At first i was stuck on the bootlogo. After reading some tips here I was able to get into recovery mode.
Then i guess I flashed a wrong SBF.....
Now i cant turn on my phone, no matter what i try, my screen stays all black. RSD Lite doesnt see my phone.
When connected to my pc, the white LED does come on, but thats all what happens.....
Any one got an idea? Or can I just throw away my Defy+?
Reply
Make sure your in bootloader mode first.
Pull out battery.
Reinsert battery while holding volume up key (thanks to drwario)
OR
Try the latest version of RSDlite. I think its 5.6. If it still doesn't work, try different versions of RSDlite.
OR
Install latest drivers from Moto website.
OR
Try another laptop/PC.
hotdog125 said:
Make sure your in bootloader mode first.
Pull out battery.
Reinsert battery while holding volume up key (thanks to drwario)
OR
Try the latest version of RSDlite. I think its 5.6. If it still doesn't work, try different versions of RSDlite.
OR
Install latest drivers from Moto website.
OR
Try another laptop/PC.
Click to expand...
Click to collapse
Thank you for your reply,
I tried all of that, without any results.....
I now have RSD 5.7, have the latest moto drivers. other pc didnt help either.
Any other ideas? Starting to get pretty desperate here....
Thanks again
reply
BoyBelanda said:
Thank you for your reply,
I tried all of that, without any results.....
I now have RSD 5.7, have the latest moto drivers. other pc didnt help either.
Any other ideas? Starting to get pretty desperate here....
Thanks again
Click to expand...
Click to collapse
Sometimes a 64-bit windows installation causes problems with RSDlite. Try a 32-bit PC.
If not working, I'm afraid you might (just might) have to get your board replaced. Take it to the service center and ask them.
EDIT: Check this link for help - http://androidforums.com/droid-x-all-things-root/209019-rsdlite-windows-7x64-problems-solutions.html
you should change your phone i had defy and defy + and the bootloader is completely locked dont try!
hotdog125 said:
Sometimes a 64-bit windows installation causes problems with RSDlite. Try a 32-bit PC.
If not working, I'm afraid you might (just might) have to get your board replaced. Take it to the service center and ask them.
Click to expand...
Click to collapse
Ok, only have 64bit systems here.....
Get my board replaced? uhmmmm.... sounds exspensive, maybe even more exspensive than a new phone.
alvin182 said:
you should change your phone i had defy and defy + and the bootloader is completely locked dont try!
Click to expand...
Click to collapse
Dont try what? This defy+ is my back up phone, I have an sony experia go as my daily phone. But have some problems with that one aswell....
reply
BoyBelanda said:
Ok, only have 64bit systems here.....
Get my board replaced? uhmmmm.... sounds exspensive, maybe even more exspensive than a new phone.
Click to expand...
Click to collapse
Try a 32-bit PC, wherever available... Worth a shot.
hotdog125 said:
Try a 32-bit PC, wherever available... Worth a shot.
Click to expand...
Click to collapse
So, I tried 32bit pc..... Phone is still not recognized in RSD
White led does come on, but thats all!
Frustrating! But thanks for your help.....
BoyBelanda said:
So, I tried 32bit pc..... Phone is still not recognized in RSD
White led does come on, but thats all!
Frustrating! But thanks for your help.....
Click to expand...
Click to collapse
got the smae problem !
dont know what to do 2
tuneon said:
got the smae problem !
dont know what to do 2
Click to expand...
Click to collapse
same problem here...!!! i tried a couple of sbf files then it resulted in this...any help
reply
As I said before, you might have to take it to the service center to have the board changed
Bricked defy 525 please help!!!
I rooted my defy 525 and flashed cm10.1 and everything was coo but the aosp keyboard kept popping up and I wasn't able to do anything couldn't even enter my wifi password because of it so I rebooted my phone to recovery so I could wipe everything to try a different custom and now it just boots baccthe motto logo and wont do anything else! I have tried the remove battery thingy and bootload through using rsd but still nothing please help me!
Just get a universal charger. Charge your battery to 100%. Reboot, get in to boot loader. Flash an appropriate Sbf. That's it. Don't try macgiver hack.
Sent from my Amazon Kindle Fire using XDA Premium HD app
---------- Post added at 02:04 AM ---------- Previous post was at 02:00 AM ----------
And your motherboard is OK. The white light only means that your battery is empty.
Sent from my Amazon Kindle Fire using XDA Premium HD app
That should work. There were a couple of cases where the motherboard was damaged
THANK YOU
juanvenegasa said:
just get a universal charger. Charge your battery to 100%. Reboot, get in to boot loader. Flash an appropriate sbf. That's it. Don't try macgiver hack.
Sent from my amazon kindle fire using xda premium hd app
---------- post added at 02:04 am ---------- previous post was at 02:00 am ----------
and your motherboard is ok. The white light only means that your battery is empty.
Sent from my amazon kindle fire using xda premium hd app
Click to expand...
Click to collapse
i appreciate it bro!
Did it work? BTW. The only way to kill or damage a defy is by using de macgyver hack, because the over volt. After using the hack you can get your battery unrecognized by the android system, so never use it. The price of a universal charger is like 2 dollars and they are good for any mobile with an empty battery.
Sent from my Amazon Kindle Fire using XDA Premium HD app
Same Problem
BoyBelanda said:
First of all, I already found a lot of helpful info on this forum. Thanks for that!
But now it seems I am really stuck.... I searched through the forum, but still couldnt find any solution to my problem.
After succesfully flashing a custom rom, I wanted to try a different one.
At first i was stuck on the bootlogo. After reading some tips here I was able to get into recovery mode.
Then i guess I flashed a wrong SBF.....
Now i cant turn on my phone, no matter what i try, my screen stays all black. RSD Lite doesnt see my phone.
When connected to my pc, the white LED does come on, but thats all what happens.....
Any one got an idea? Or can I just throw away my Defy+?
Click to expand...
Click to collapse
Facing Same Problem !! None of the solutions suggested in the thread is working !!
Please help anyone ?
anandrathi13 said:
Facing Same Problem !! None of the solutions suggested in the thread is working !!
Please help anyone ?
Click to expand...
Click to collapse
Get latest RSDLite and Moto drivers. They are version 6.1 I think.
hotdog125 said:
Get latest RSDLite and Moto drivers. They are version 6.1 I think.
Click to expand...
Click to collapse
Didnt work for me.... Already got the lastest of everything, still without any positive results
So basically I'm trying to get my phone to work. I tried flashing and I wiped my data/factory reset my phone. And I attempted to flash a custom rom. However my signature failed. I realized that I needed CWM but I cannot install anyway because my recovery is e3 and the signature fails. I tried resetting back to stock by using RSDLite/SBF to get back to normal. However my device will not read on my computer. I've attempted to make sure my drivers are correct, and that my cables/usb ports are working fine. I'm basically in a dilemma and I'm not sure what else I can really do. Is there another workaround? I'd love it if someone can help a brother out!
I think the reason it isn't reading in my computer is because it is Windows 8 if that helps.
Eatthisnx4 said:
So basically I'm trying to get my phone to work. I tried flashing and I wiped my data/factory reset my phone. And I attempted to flash a custom rom. However my signature failed. I realized that I needed CWM but I cannot install anyway because my recovery is e3 and the signature fails. I tried resetting back to stock by using RSDLite/SBF to get back to normal. However my device will not read on my computer. I've attempted to make sure my drivers are correct, and that my cables/usb ports are working fine. I'm basically in a dilemma and I'm not sure what else I can really do. Is there another workaround? I'd love it if someone can help a brother out!
I think the reason it isn't reading in my computer is because it is Windows 8 if that helps.
Click to expand...
Click to collapse
You need to download and install the Motorola drivers to connect the phone to RSD to SBF it. Just search for Motorola drivers on Google.
Then you can install the D2 Bootstrap, boot into recovery, and install your ROM.
Forgot to add: Root using Framaroot before installing Bootstrap.
VitaTaf said:
You need to download and install the Motorola drivers to connect the phone to RSD to SBF it. Just search for Motorola drivers on Google.
Then you can install the D2 Bootstrap, boot into recovery, and install your ROM.
Forgot to add: Root using Framaroot before installing Bootstrap.
Click to expand...
Click to collapse
I've done that already. And they are "installed" but it doesn't seem to appear as anything other than unspecified :/
Eatthisnx4 said:
I've done that already. And they are "installed" but it doesn't seem to appear as anything other than unspecified :/
Click to expand...
Click to collapse
Can you verify root using Root Checker? If you are on the stock Gingerbread ROM, z4root will not root your device.
VitaTaf said:
Can you verify root using Root Checker? If you are on the stock Gingerbread ROM, z4root will not root your device.
Click to expand...
Click to collapse
The problem with that is I wiped/deleted everything off my phone, as I cannot even access anything besides recovery/bootloader.
Eatthisnx4 said:
The problem with that is I wiped/deleted everything off my phone, as I cannot even access anything besides recovery/bootloader.
Click to expand...
Click to collapse
Can you try flashing this: http://goo.im/devs/wizard0f0s/Hijacked_Bootmenu/CM7
After that, press the volume down key when/if the blue LED lights up (after reboot on the red M logo). You should be able to access an updated recovery from there.
That would be a good idea. however I get the signature verification failure thing. :/
Eatthisnx4 said:
That would be a good idea. however I get the signature verification failure thing. :/
Click to expand...
Click to collapse
Unfortunately, the only option is to do an SBF. If using Windows doesn't work, you might want to try using Ubuntu.
By the way, I am using Windows 8 too and I do not have any problems with RSD Lite.
VitaTaf said:
Unfortunately, the only option is to do an SBF. If using Windows doesn't work, you might want to try using Ubuntu.
By the way, I am using Windows 8 too and I do not have any problems with RSD Lite.
Click to expand...
Click to collapse
I'm gonna attempt to use a different computer to fix my problem. Wish me luck man.
Thanks for your input.
Eatthisnx4 said:
I'm gonna attempt to use a different computer to fix my problem. Wish me luck man.
Thanks for your input.
Click to expand...
Click to collapse
No problem, good luck on fixing your problem.
Troubles with RSD lite try
DX (MB810) ezSBF & Root 2.3.4/4.5.621
Sent from my XT862 using Tapatalk
sd_shadow said:
Troubles with RSD lite try
DX (MB810) ezSBF & Root 2.3.4/4.5.621
Sent from my XT862 using Tapatalk
Click to expand...
Click to collapse
Good idea. The problem is I cannot get my computer to recognize my device properly. :/ But Once I find a way to do it I will use that way!
Eatthisnx4 said:
Good idea. The problem is I cannot get my computer to recognize my device properly. :/ But Once I find a way to do it I will use that way!
Click to expand...
Click to collapse
ezSBF doesn't need drivers installed, so if it's a drivers issue try ezSBF
---------- Post added at 12:02 PM ---------- Previous post was at 11:41 AM ----------
just need
1. windows, linux, or mac computer
2. blank cd-r, dvd-r, or flash drive (thumb, stick, sd card...)