Related
Well.. it seems to me that there has been an unusually high amount of people who are now getting the USB device not recognized error when plugging their phone into their computer. Myself included. I'm stuck on dj05 because of it.
Can everyone that's having this problem post what they've flashed and how? Or any other problems their having? Make sure to post what OS you are using, x64 or x86, stock cord or not, Samsung drivers version, etc. Maybe we can find a common theme between everyone having the problem, and figure out a way to fix it. Thanks!
Sent from my SCH-I500 using XDA App
I will asap when I get home to my computer. Thanks for the thread as I have asked myself, but still no luck.
Sent from my SCH-I500 using XDA App
Same problem. I was running DL30 with the Blackhole Rom. Just stopped working yesterday. Tried flashing stock, then DL05. Can't root, ADB doesn't see it, nothing. Can't mount either. Win7 64 keeps saying its a CD drive and tries to install the verizon drivers. Did that, still tries.
I thought considering I started the thread, I should probably post my configuration as well. I had no problems with USB until I flashed kaosinate. I'm sure this didn't have anything's to do with it but oh well. I also flashed the lasted kaosinate kernal. After that, I installed superclean with adryn.'s test kernal. Still nothing. If you look around, there are definitely quite a few reports of the phone being recognized as a CD drive. Adrynalyne reccomends flashing one of his new test kernals which has been reported by some to fix the problem. He says that he still has to reboot with the phone plugged in to have it recognized, however.
I an running windows 7 pro x64 with the lastest Samsung drivers. I only get the USB error when plugging the phone in while its In downlaod mode. Otherwise it is recognized as a CD drive. I guess this is what we get for flashing non stock firmware, Roms, etc. If anyone has any suggestions, feel free to post them.
Sent from my SCH-I500 using XDA App
Randomly came back...flashed stock DI01, then DI05, then DI09, then back to DI05. Working now...it must have finally wiped some bad code or something...
OK, so I went to root the thing...when the root rebooted, it didn't work. I had to disconnect and reconnect the USB cable to get it to recognize again.
Did you use Odin? Where did you get the files from?
Sent from my SCH-I500
Running Windows 7 64bit
running super clean 3.2nv
I finally got it to recognize. But it will not recognize when i boot into download so i can flash with odin...
So I'm needing to sbf and I'm currently on liberty 1.5 Moto drivers (specifically MTP USB) refuse to install (I currently have 4.9 installed) and RSDLite (ver. 4.9) refuses to even show my phone when I force it into bootloader mode. I'm really needing to go back to stock and I've been stuck playing this game for hours. Everything I see about MTP USb drivers are user error. I've gone through the install uninstall game, changing usb debugging etc and I'm running out of options on what to do next...
Try using rsd lite v4.8 http://www.megaupload.com/?d=72ILNCSN
Latest usb drivrs http://www.motorola.com/consumers/v/index.jsp?vgnextoid=bda09ec8009a0210VgnVCM1000008806b00aRCRD
Make sure to reboot your pc after updating drivers
Sent from my DROIDX using XDA App
anybody know where to get the SBF 2.2.1 ver 2.3.340?
http://droidmodderx.wordpress.com/how-to-sbf-your-droid-x-full-2-3-340/
Sent from my DROIDX using XDA App
running liberty gb v .1.after install I lost clockwork recovery and no matter what I do I cannot get it installed. I upgraded to gb for netflix but I can't even get that to work. I cannot sbf because I'm on the nTelos network and there are currently no sbf files out. Can't anyone help?
Sent from my DROIDX using XDA App
Liberty GB (all versions) come with Clockwork Mod, you might have either had a bad install or a bad downloaded file. I wasn't aware that the SBF files were network-specific, are you positive you can't use the regular Verizon ones on the web? Also, you've installed the donate Liberty Toolbox, right?
Have you gone into the normal bootloader (hold home button down while turning on) and wiped data + cache at least 3 times after installing Liberty GB to see if you can then get Clockwork Mod working? What happens if you try to reboot bootstrap from within Liberty Toolbox? Another thing to try is, install the Droid 2 Bootloader from the market, it's like $2 to buy. The Droid X one does NOT work with GB for the Droid X, you have to use the Droid 2 one.
The droid x one does work as long as USB debugging is unchecked
I have liberty toolbox donate and droid x bootstrapper , I've tried getting into stock and cw recovery. Both just lead to a blank screen that stays until you battery pull. It doesn't matter if I try to go into recovery through liberty toolbox or holding down any combination of buttons. Always the same result. I do have usb debugging disabled. And as far as all my research has led me to believe, sbf files are carrier specific. So using a vzw file would set my phone up as a verizon droid x rather than ntelos. If there is a way to change that after sbfing please let me know, as I haven't been able to come across any info on that yet.
Sent from my Droid X using Tapatalk
Since you have the donate toolbox, have you tried upgrading to .5 Liberty (make sure to use the one WITH the .595 kernel)?
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
I have C Spire's Milestone X (2.3.5), tried to flash Cyanogen's nightly and failed.
Couldn't use the C Spire SHADO_X6_3.2.6_SHADOW_BP_C_02.06.00R_AP_BP_Flex_21_signed_secure_cell_south_1ff_P3_USERBLD.sbf.zip (recovery errors), so I used the Alltel one.
Great, now my phone thinks it's with Verizon wireless.
*228.. "Welcome to Verizon wireless...."
Help?
I would find the stock sbf for ur milestone x and reflash.
I had to use ur milestone x sbf to get by 621.
Sent from my DROIDX using xda premium running ics 4.0.4 after taking the 621 update.
I can't downgrade from 2.3.5 which I'm assuming is what the .sbf I posted is.
I get bootloader errors. I even tried installing the 2.3.5 OTA patch but it doesn't work either. I get recovery errors.
Hence, my orig reply to flash ur latest sbf. That will get you back to a good starting point with all operational. Then test again. I always have my current sbf before root and flash.....preventative measures rule
Sent from my DROIDX using xda premium
Can't find one. I can't boot into CWM now either.. it just boots into reg. recovery. -sigh-
Looking around at your 2.3.5 milestone x device.
I notice alot of people bricking using your sbf file.
Sounds like there are issues from it and you cant install the update because of it.
First if you tried to update and it still failed, well my resolution.
Boot up in linux maybe ubuntu live to be safe
hook up your phone power on holding home+Vol down+power
should say usb at the bottom
Then run terminal
chmod +x sbf_flash
sbf_flash "your original sbf file to put to your carriers stock rom"
Unplug usb and reboot phone.
Why dont you try looking here for your original or current stock sbf file
Code:
http://sites.google.com/site/motosbf/milestone-x-sbf-files