Does a DPro sbf exist or at least is somebody working on it?
Sent from my DROID PRO using XDA App
I wish one did.
Bricked my Pro yesterday
pman219 said:
I wish one did.
Bricked my Pro yesterday
Click to expand...
Click to collapse
Please share how you bricked it so we can avoid doing the same. Did you try to put a custom recovery that wasn't made specifically for the Pro?
jayhammy said:
Please share how you bricked it so we can avoid doing the same. Did you try to put a custom recovery that wasn't made specifically for the Pro?
Click to expand...
Click to collapse
It was rather dumb on my part.
I've been working with ninjamorph to develop a status bar mod and I accidentally swapped drawable files with a different ROM.
That was all it took
Well hopefully we get some dev love
Sent from my DROID PRO using XDA App
Guys any luck unbricking your Droid Pro?
It seems like I have bricked mine aswell trying to replace the bloat ware to receive the ota update. Now it just goes on a endless boot loop. Any help will be appreciated.
Thanks
I have a bricked / endless looped Droid Pro as well. I suppose all we can do is wait until a method is found to flash a rom from the recovery mode...
Check the development section for the Droid pro. We have an SBF.
Sent from my SAMSUNG-SGH-I897 using XDA App
It appears the sbf given to us was for the wrong phone so wait for now. Were trying to get the correct version.
Sent from my SAMSUNG-SGH-I897 using XDA App
Newb question. What is SBF and what is it used for?
Thank you mistarose!
My phone is back.
Thanks [email protected]!
Keyword is "Droid Pro SBF".
raphael888 said:
My phone is back.
Thanks [email protected]!
Keyword is "Droid Pro SBF".
Click to expand...
Click to collapse
Raphael888,
So, exactly what did you do to fix your droid pro? I have gone to the pilotrose forum and downloaded the sbf files and havent had any luck flashing them with RSD lite 4.9.
Thank you!
xCalvaryx said:
Raphael888,
So, exactly what did you do to fix your droid pro? I have gone to the pilotrose forum and downloaded the sbf files and havent had any luck flashing them with RSD lite 4.9.
Thank you!
Click to expand...
Click to collapse
My Steps is as follows.
1. Use Windows 32-bit OS like XP or Server 2003.
2. Install Motorola usb driver which I use is version 4.8 and then reboot.
3. Install RSD lite 4.9 and then reboot.
4. Boot Droid Pro into recovery mode then connect it to you pc/laptop. In the meantime, Windows will ask for device drivers for you phone, just choose the default option to finish.
5. Open RSD lite 4.9, no need to change any configuration except clear "delete image file on exit".
6. In RSD lite, make sure droid pro is found and then click '...' button to load the SBF file. Click start to begin re-image.
7. In the RSD lite re-imaging progress, you may again be asked by Windows for device driver like step 4. Repeat what you did in step 4 and let RSD lite finish its work.
8. If Droid Pro boots successfully, the phone is totally cured. If it boots into recovery mode again, close RSD lite and then repeat from step 4 again.
If you need more detailed info about RSD lite, the following link is very useful.
http://www.droidforums.net/forum/droid-labs/73579-using-rsd-lite-flash-sbf-file-correctly.html
thanks a lot for your tips
Related
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
Welcome to my thread on bootloop fixes for flashing new ROM's through CWM.
I have seen many cases where people will get stuck in a bootloop from flashing a newer 2.3.4 ROM with CWM, and this has also happened to me. Please be aware I made this guide for AT&T Atrix 4G's. I am unaware if this works for international devices.
Click to expand...
Click to collapse
DISCLAIMER:
I AM NOT RESPONSIBLE FOR ANYTHING THAT MAY GO WRONG WHILE FOLLOWING MY INSTRUCTIONS. YOU SHOULD ALREADY KNOW THERE IS ALWAYS A RISK OF BRICKING YOUR DEVICE WHILE FLASHING.
DO NOT DO THIS IF YOU ARE COMING FROM A 2.3.4 STOCK AT&T OTA UPDATE ROM.
THIS WILL WIPE ALL DATA EXCEPT INTERNAL MEMORY AND THE SD CARD, AND MAKE YOUR PHONE LIKE NEW.
ALSO, BE AWARE THIS IS FOR AT&T, NOT INTERNATIONAL.
Click to expand...
Click to collapse
WHY?:
In almost every bootloop case, it is because the CWM version installed on your atrix is older then what the ROM maker made it for. For example, if you were like me and flashed the HKTW ROM right when it came out with Tenfar's first unlocked CWM recovery, then tried to flash a new ROM such as Kenneth's 2.3.4 AT&T, then you would be stuck in a bootloop. So again, you always need the latest CWM.
Click to expand...
Click to collapse
SOLUTION?:
WINDOWS ONLY:
Prerequisites:
1.2.6 SBF file (the password to extract the file is "atrixbl")
RSD Lite 5.0
Drivers: 32 bit OR 64 bit
INSTUCTIONS:
1. Make sure your phone is turned off
2. Take out your microSD card and SIM card for the flashing process
3. While turning the phone on, hold the Volume Up button until it acknowledges RSD
4. Your device will say “Starting RSD protocol support”
5. Run “RSD Lite” on your computer
6. Press the “. . .” button next to the box labeled “Filename”
7. Load up the SBF file (The SBF file is located inside of the .gz file, you must extract it out before loading it into RSD Lite)
(Use WinRAR or 7-Zip to extract the .gz file on your computer)
8. Plug your device into your computer
9. RSD Lite should recognize your device and say “Model: NS Flash Olympus” and “Connected…”
10. Press the “Start” button
11. Be patient while the phone reboots. It will take a long time.
12. OTA update from 1.2.6, all the way to 1.8.3
Download "Rom Manager" from the android market.
13. Click the first option "Flash ClockworkMod Recovery"
14. Select Motorola Atrix 4G.
15. Now you're all set and back in the game. You are safe to flash any new ROMs with this OFFICIAL CWM. And Rom Manager will let you know when a new CWM version is available.
Click to expand...
Click to collapse
IF ANYTHING IS INCORRECT, PLEASE LET ME KNOW. ALSO, IF THESE METHODS DO NOT WORK, LET ME KNOW AND I WILL UPDATE THE GUIDE. WHAT I HAVE POSTED HERE IS BASED ON WHAT WORKED FOR ME, AND EVERYONE I HAVE HELPED.
Click to expand...
Click to collapse
If you would like to donate to me, I will put a link below. What I do with donations is find ROM developers, and see their current work progress, and donate to them. So anything you donate to me, gets donated to future ROM making.
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=8Q3MSD9KW2GD6
Click to expand...
Click to collapse
Thank you for everyone who has given us ROMs, hacks, mods, you name it. This device is nothing without you guys!
Click to expand...
Click to collapse
Reserved
Sent from my MB860 using XDA Premium App
jbrussee said:
Does this not effect anyone?
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
People who are on the ota DO NOT flash back to 1.83 or prior op make this clear please although most will know some noobs wont lol
edit my fault you did, maybe a little bigger? if not its ok at least you have it
Yeah, I made sure I said that.
Sent from my MB860 using XDA Premium App
hi im posting this so I can post in the development section.
LMAO Techno. You got punked on two consecutive threads. Why do you have to be so rude and arrogant? Oh and please follow your own advice.....read before posting any comment.
Sent from my MB860 using XDA App
logantyler said:
hi im posting this so I can post in the development section.
Click to expand...
Click to collapse
+1 This place is way to aggressive with new users.
bootloop
Hi All,
I wanted to add my solution for having my phone stuck in a bootloop and then soft bricking it. My phone did not unlock successfully
1. Download a working version of 1.83
2. Download RSD Lite for your computer
3. When starting phone enter recovery by holding the volume down and pressing the power button, when the recovery option at the top shows up, use the volume down to get to RSD Mode. Volume Up selects.
4. Launch RSD Lite
5. Plug phone into computer using USB and RSD Lite should recognize phone.
6. Select the 1.83 file. Then run it
7. This may take some time, but it will boot your phone back to stock settings.
8. Read directions more carefully next time when you install a custom rom.
Hope this helps someone!
Thanks for more input!
Sent from my Motorola Atrix 4G MB860 using XDA Premium App
Hello, I installed GingerBlur and Now want to upgrade to Gingerbread. I am having some issues with doing an OTA upgrade. I aslo no longer have a PC which I used to root and flash before. Any help would be greatly appreciated.
I believe your instructions are only for AT&T users (judging by the files and OTA numbers).
If so, you should state that so some new International user doesn't try this and hard brick.
Zero-k, thank you for informing me of this.
Sent from my Motorola Atrix 4G MB860 using XDA Premium App
I was trying to flash a custom rom onto my sisters droid x. I'm not new to androids and have pretty good knowledge but coming from a atrix it was a bit different. Anyway I flashed the rom and the phone got stuck on the moto sign. So I tried loading back to stock via rsdlite. It finished and phone rebooted. Then got stuck again on the moto sign. Don't know where to go from here. Any help would be greatly appreciated. She needs her phone asap for work soon. Thanks.
Try SBFing again using RSD Lite, or use the Linux live cd--which is much easier.
Be sure you are using the correct SBF, also. Should say version .602.
Sent from my DROIDX using XDA App
thx got it to work via rsdlite. now running newest cm7. had a panic attack.
stevehkim said:
thx got it to work via rsdlite. now running newest cm7. had a panic attack.
Click to expand...
Click to collapse
Hey man - been there done that The SBF_FLASH utility you can download and use in LINUX (you can boot with the Ubuntu Live CD like the guy above suggested) is MUCH better. It "just works". Never had it error and RSDLITE failed so many times my battery went dead (before). I don't even bother with it now I just go straight to sbf_flash.
always remember to wipe wipe wipe... thats y u got stuck at the moto after rsd...
Sent from my DROIDX using the XDA mobile application powered by Tapatalk
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
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...)