I was interested if it is possible to downgrade from Kitkat with cyanogenmod installed on it to 4.1.2. I have Motorola Droid Razr HD and I just hate 4.4 (for some reason).
KK to JB
this might help http://forum.xda-developers.com/showthread.php?t=2789743
ncsuwolfs said:
this might help http://forum.xda-developers.com/showthread.php?t=2789743
Click to expand...
Click to collapse
Sadly I cant really use RSD Lite, since it doesn't detect my phone for some reason (probably because it's not OEM). Is there any other way of doing it without rsd lite?
just to make sure, did you have phone in fastboot with debugging enabled while having it connected to a pc running newest version of rsd lite on a usb port not usb 3.0?
ncsuwolfs said:
just to make sure, did you have phone in fastboot with debugging enabled while having it connected to a pc running newest version of rsd lite on a usb port not usb 3.0?
Click to expand...
Click to collapse
Yes, and everything is as it should be, except RSD Lite 6.1.6 (which is the latest version as far as I know) does not detect it. Bootloader unlocked, I have root access, everything is OK. But still it won't show up in the list.
Have you uninstalled all the drivers and everything? I'm going to assume you are Windows 7.
Also, ensure you are connected to a 2.0 usb port. You don't have 3.0 USB ports do you? If so, those don't work from what others have reported.
Also, have you tried several different cables? If you have the OEM cable that came with your phone, use that. If that doesn't work, the cable could be bad.
If it's not showing up when you connect with the phone booted up normally nor under fastboot mode, then that points to either a driver issue or a cable issue.
I had an issue where the driver was old, so I went into Device Manager and saw that it showed my phone (Motorola USB Phone) but it had an exclamation mark next to it which meant it had trouble with the drivers. I then uninstalled all the drivers and eventually, point it to the drivers in the Android SDK (Google USB drivers) and that fixed it.
iBolski said:
Have you uninstalled all the drivers and everything? I'm going to assume you are Windows 7.
Also, ensure you are connected to a 2.0 usb port. You don't have 3.0 USB ports do you? If so, those don't work from what others have reported.
Also, have you tried several different cables? If you have the OEM cable that came with your phone, use that. If that doesn't work, the cable could be bad.
If it's not showing up when you connect with the phone booted up normally nor under fastboot mode, then that points to either a driver issue or a cable issue.
I had an issue where the driver was old, so I went into Device Manager and saw that it showed my phone (Motorola USB Phone) but it had an exclamation mark next to it which meant it had trouble with the drivers. I then uninstalled all the drivers and eventually, point it to the drivers in the Android SDK (Google USB drivers) and that fixed it.
Click to expand...
Click to collapse
I have all the drivers that were necessary to flash, set up recovery, install CM11, so I don't think it's a driver issue. I'm using Windows 8.
I do have 1 USB 3.0 port, but for this operation I use 2.0.
And the cable, I am using a different cable, I don't have OEM anymore, so that might be a problem here.Thanks, I'm going to buy the cable from Motorola I guess and will post results here.
toka793 said:
I have all the drivers that were necessary to flash, set up recovery, install CM11, so I don't think it's a driver issue. I'm using Windows 8.
I do have 1 USB 3.0 port, but for this operation I use 2.0.
And the cable, I am using a different cable, I don't have OEM anymore, so that might be a problem here.Thanks, I'm going to buy the cable from Motorola I guess and will post results here.
Click to expand...
Click to collapse
That's the issue then. Windows 8, from what I've read, is very finicky with Android and ADB.
Go to this thread as it might help -> http://forum.xda-developers.com/showthread.php?t=1583801
otherwise, I would suggest either going to a Windows 7 machine or even a Unix machine. Worse comes to worse, you might be able to hook up a Virtual Machine (using either VMWare Player or Oracle's Virtual Box - both are free) and set up a Ubuntu Linux and try it that way since Linux doesn't need the SDK USB drivers. ADB and Fastboot will work right out of the box.
I actually have another PC set up with Ubuntu directly (not in a Virtual machine image) and it works just fine. I have a Windows 8 laptop, but that's my wife's so I don't hook up my phone to it. My other machine is a Windows 7 64-bit machine and it works just fine (and it has two Ubuntu virtual machines that work with my phone just as well).
So, now that I see you have a Windows 8 machine, it makes more sense.
iBolski said:
That's the issue then. Windows 8, from what I've read, is very finicky with Android and ADB.
Go to this thread as it might help -> http://forum.xda-developers.com/showthread.php?t=1583801
otherwise, I would suggest either going to a Windows 7 machine or even a Unix machine. Worse comes to worse, you might be able to hook up a Virtual Machine (using either VMWare Player or Oracle's Virtual Box - both are free) and set up a Ubuntu Linux and try it that way since Linux doesn't need the SDK USB drivers. ADB and Fastboot will work right out of the box.
I actually have another PC set up with Ubuntu directly (not in a Virtual machine image) and it works just fine. I have a Windows 8 laptop, but that's my wife's so I don't hook up my phone to it. My other machine is a Windows 7 64-bit machine and it works just fine (and it has two Ubuntu virtual machines that work with my phone just as well).
So, now that I see you have a Windows 8 machine, it makes more sense.
Click to expand...
Click to collapse
Oh okay, I'll try it on Windows 7 then.
iBolski said:
Go to this thread as it might help -> http://forum.xda-developers.com/showthread.php?t=1583801
Click to expand...
Click to collapse
Thanks for the link iBolski - I am in the unfortunate situation, that my laptop came with Win 8.1 and has just two USB 3.0 ports.
Hopefully some of the suggestions will get RSD to work, otherwise I may need to start my Linux learning adventure sooner than planned..
StefanGA said:
Thanks for the link iBolski - I am in the unfortunate situation, that my laptop came with Win 8.1 and has just two USB 3.0 ports.
Hopefully some of the suggestions will get RSD to work, otherwise I may need to start my Linux learning adventure sooner than planned..
Click to expand...
Click to collapse
The only isssue is, if all you have are 3.0 USB ports, then you are hosed as far as I know. Some have reported getting it to work on USB 3.0, but I have no idea how they did it.
A goggle search might help lead to some answers though.
iBolski said:
The only isssue is, if all you have are 3.0 USB ports, then you are hosed as far as I know. Some have reported getting it to work on USB 3.0, but I have no idea how they did it.
A goggle search might help lead to some answers though.
Click to expand...
Click to collapse
I will do some deeper research on google.. first pass didn't yield any viable information other than "it doesn't work"
Are you saying, that USB 3.0 may not even work under Linux?
I used to have the same problem... I solved by doing the following:
1- first go to window's device manager and check that windows is recognizing that there is a new hardware but it does not has the drivers for it
2- install morotola's drivers (if you haven't already)
3- look where the motorola's installer store the files in your machine
4- go to device manager, look for the unrecognized hardware, click properties and install the proper driver manually
sorry I can't give you more details cause I'm currently at work.
StefanGA said:
I will do some deeper research on google.. first pass didn't yield any viable information other than "it doesn't work"
Are you saying, that USB 3.0 may not even work under Linux?
Click to expand...
Click to collapse
I believe so, though I'm not 100% positive. But, from what I've read, USB 3.0 is incompatible with Android phones in general.
I have a computer with Windows 8 and 2 USB 3.0 ports, everytime I try RSD with one of the two 3.0 ports it doesn't work. Fortunately I have a USB 2.0 and it always work. I always use RSD 6.1.4 because for some weird reason this is the only version that detects my xt925. So it might not be the comp or windows 8, but the cable or drivers, as stated before. The latest drivers are on Motorola's website and they're updated to work with Windows 8.
Sent from my RAZR HD using XDA Free mobile app
Related
When I updated my OS from Windows 7 x64 Ultimate to Windows 8 Pro x64, I faced some serious issues related to USB connectivity.
I currently use MyPhoneExplorer as a windows interface for my phone management and it needs USB drivers properly working. Windows automatically detects the unknown device and downloads the related drivers if missing. But as you know it's a long shot and in this case it worked.
Windows managed to pull up some drivers so my USB debugging mode worked and connectivity was fine.
But if you want to connect the device in Download mode using ODIN for firmware upgradation, you're stuck. ODIN cann't detect any device connected to any port (though it's there connected to one of the USB ports actually)
So the final ultimate solution is (after so many other futile attempts ) : download the latest KIES from Samsung's official website.
Trust me on this, it may seem simple and straight but the amount of (futile) efforts I put behind all these is a lot, and I seriously don't want anyone to waste your time on this stupid issue. So that's it.
By the way this is my very first post to XDA. Been using the site for troubleshooting since years but never participated actively. Thanks to the team and all the developers for this great gateway of solutions. :good:
Onsite_Baba said:
When I updated my OS from Windows 7 x64 Ultimate to Windows 8 Pro x64, I faced some serious issues related to USB connectivity.
I currently use MyPhoneExplorer as a windows interface for my phone management and it needs USB drivers properly working. Windows automatically detects the unknown device and downloads the related drivers if missing. But as you know it's a long shot and in this case it worked.
Windows managed to pull up some drivers so my USB debugging mode worked and connectivity was fine.
But if you want to connect the device in Download mode using ODIN for firmware upgradation, you're stuck. ODIN cann't detect any device connected to any port (though it's there connected to one of the USB ports actually)
So the final ultimate solution is (after so many other futile attempts ) : download the latest KIES from Samsung's official website.
Trust me on this, it may seem simple and straight but the amount of (futile) efforts I put behind all these is a lot, and I seriously don't want anyone to waste your time on this stupid issue. So that's it.
By the way this is my very first post to XDA. Been using the site for troubleshooting since years but never participated actively. Thanks to the team and all the developers for this great gateway of solutions. :good:
Click to expand...
Click to collapse
hi try to run odin in compatible mode that should solve your problem could be odin is not compatible with windows 8
Hi, just received my Surface Pro yesterday and its amazing Anyways, I've been installing all my normal desktop applications as I would do with any other new PC. Today, I tried to install drivers for fastboot so I can flash custom kernels on my Xperia S. I managed to get the fastboot and ADB drivers installed correctly by disabling driver enforcement, but every time I connect my phone in fastboot mode to my Surface, Windows says the last USB device connected has malfunctioned.
I've read that other people are having problems with Windows 8 64bit and installing drivers, but I've managed to do that without problems
I've also read that you should plug your phone into a USB 2.0 port because it won't work with USB 3.0 ports yet but since the Surface Pro has only one USB 3.0 port, I haven't had the chance to try that.
I wonder if there is an adapter that changes USB 3 to USB 2? Maybe this could solve the problem?
Has anyone managed to get fastboot for any android phone working successfully on their Surface Pro?
Thanks in advance.
You could possibly try a USB 2.0 hub to degrade the USB 3 port to a USB 2 port.
netham45 said:
You could possibly try a USB 2.0 hub to degrade the USB 3 port to a USB 2 port.
Click to expand...
Click to collapse
Thanks for the reply, I've actually already tried that. It seems to me that Google need to update their SDK for USB 3.
ttiimm said:
Thanks for the reply, I've actually already tried that. It seems to me that Google need to update their SDK for USB 3.
Click to expand...
Click to collapse
I doubt that it is a USB 3.0 problem as I have USB 3.0 ports only on my laptop and have had fastboot working no problem, as well as adb for my nexus.
It sounds more like you are having driver problems and not usb port problems. I have not tried using fastboot yet on my win8 asus tablet but I should try that today.
goofball2k said:
I doubt that it is a USB 3.0 problem as I have USB 3.0 ports only on my laptop and have had fastboot working no problem, as well as adb for my nexus.
It sounds more like you are having driver problems and not usb port problems. I have not tried using fastboot yet on my win8 asus tablet but I should try that today.
Click to expand...
Click to collapse
Same thing on my Surface Pro. The problem lays in BOTH: the USB 3.0 driver and the Windows 8. There are tons of posts regarding not working many devices on USB 3.0 and Win8 (I'm not sure if it's only in x64 or x86 as well).
Anyway, I'm also stuck with not working fastboot (ADB works good). There is a tutorial how to install unsigned Intel driver but Microsoft's engineers geniuses didn't enabled USB keyboard in Startup Settings so I can't navigate and disable that specific option (I'm using 3rd party keyboard so I guess those morons punish me for that ).
Ok, I can't manage to get my SV work with my PC.
This problem persists only in fastboot mode.
Yellow triangle, unknown device as always. (In device manager it shows up as My HTC)
What i tried until this:
-3 different USB port (1 of them is 2.0)
-4 different drivers (including official HTC Win8 x64 drivers, Win7 x64 drivers by old.splatterhand, and 2 other drivers from random sites)
-Retail USB Cable and a random noname pink colored USB cable
-USB HUB
-HTC Sync and HTC Sync Manager installed
-Java installed
-Google SDK installed
-drivers and updates in android SDK installed
-of course I turned driver signature enforcement and antivirus off.
It's not the first case when i have this problem. I had some Xperia phones before SV, none of them was able to connect to my PC. Probably because of drivers. Or because of my PC? My previous PC with Win7 x64 worked like charm, but that was a Desktop PC.
Thanks in advance.
If you have already tried the drivers i provide, i can't give you others, sorry.
But if this problem happened, the first time after the update to 4.2.2, you can try to downgrade your hboot (when you are S-off!) and see if it could be solved by that.
old.splatterhand said:
If you have already tried the drivers i provide, i can't give you others, sorry.
But if this problem happened, the first time after the update to 4.2.2, you can try to downgrade your hboot (when you are S-off!) and see if it could be solved by that.
Click to expand...
Click to collapse
Didn't tried on 4.1.2.
Don't have root nor unlock.
that's why I want to get them work
But seems it won't. Np seems my notebook is not compatible with this. WIll try on another PC With XP. Thanks anyway
Report back, if you had success.
Hi,
I'm using this CM 11 http://forum.xda-developers.com/showthread.php?t=2922500 but I have strange problem with my laptop. It periodically looses driver information for my device. I don't know how but when I re-installed my OS Windows 7 (32bit) it found the proper driver. Later I've got a message that my USB device is not recognized and can't connect to my device. Does anyone else have the same problem and do you know a fix? I've tried a lot and different driver versions but without success. Logcat doesn't show anything last time but I will try later or when I loose drivers again (it seems I cannot use USB again).
BTW I don't have this problem with my desktop PC which has always connected USB cable to it. Also everything works fine with CM 10.1, MIUI or Sense ROMs but they are based on lower Android versions.
P.S. I was trying to connect with another USB cable. I've found my cable that I used to install drivers and USB is working again. This is really strange behaviour
Logcat from device terminal
Logcat when plug in or out my USB connector is attached.
Use this tool
http://forum.xda-developers.com/showthread.php?t=2588979
Afternoon all,
Have been out of the rom'ing scene for a while...
I have a number of devices (Galaxy Tab 2 10.1 and Nexus 7 2012, to be exact), that I want to flash a new ROM onto (the Tab's stuck in a boot loop, the N7's due for Dirty Unicorns Nougat Rom).
All pretty straight forward - I've done it in the past - BUT...
Can I get Windows 10 to even *see* new hardware's been connected, let alone recognize it?
Can I fook
To confirm, I plug the USB between the PC and the device, and all that shows this is connected is that the device realises it's being charged, no "ding ding" from Windows, no USB confirmation from the device...
Both devices have USB Debugging enabled.
Have tried different USB cables
Have tried different USB ports
Have tried - many! - different USB drivers, including that from both Asus and Google's own dev kit.
Have ADB installed, "adb devices" shows no devices (blank).
The thing that's really pi**ing me off is that this is such a basic thing to be stuck by, I really cant figure out what I'm missing!
Any help appreciated gents...
cy80rg said:
Afternoon all,
Have been out of the rom'ing scene for a while...
I have a number of devices (Galaxy Tab 2 10.1 and Nexus 7 2012, to be exact), that I want to flash a new ROM onto (the Tab's stuck in a boot loop, the N7's due for Dirty Unicorns Nougat Rom).
All pretty straight forward - I've done it in the past - BUT...
Can I get Windows 10 to even *see* new hardware's been connected, let alone recognize it?
Can I fook
To confirm, I plug the USB between the PC and the device, and all that shows this is connected is that the device realises it's being charged, no "ding ding" from Windows, no USB confirmation from the device...
Both devices have USB Debugging enabled.
Have tried different USB cables
Have tried different USB ports
Have tried - many! - different USB drivers, including that from both Asus and Google's own dev kit.
Have ADB installed, "adb devices" shows no devices (blank).
The thing that's really pi**ing me off is that this is such a basic thing to be stuck by, I really cant figure out what I'm missing!
Any help appreciated gents...
Click to expand...
Click to collapse
Windows 10 is very buggy. Download lobit Drive Booster to see if you are missing any driver for your pc. Your pc is probably missing some drivers for the motherborad or outdated. If this does not work, clean install windows 10. Let windows 10 install all the drivers for you while it is installing. Best method. Good internet connection required.
its damn easy,the problem lies in Windows,just boot into repairmodus/system recovery its the blue menu for troubleshooting,there u choose Startup Setting and there u choose number 7,thats for disabling the digital driver signature checking,after the reboot all is fine,boot note u must do it everytime new after reboot.
please next ask and post in right section,thanx.
Nvidia USB driver (ADB and Fastboot) is the only one that works for me
https://developer.nvidia.com/shield-open-source