Now before you tell me to reinstall my drivers, I have countless times. I'm 90% sure its an issue with the phone itself. When I connect the phone without debug mode it connects. If I have the phone in debug mode and I connect, the phone does get recognized, but not as a storage device but as a driver installer with a driver installer exe, when ran, it almost instantly disconnects the phone. The phone says connected as an installer, and no matter if I try to install this driver or the actual official driver it will not connect.
I had however connected in S/W upgrade mode and flashed, but it didn't fix the problem. I also tried flashing ICS u-boot and xloader then flashing but I can't for the life of me fix this. The phone is a locked bootloader w/ jb 20h. This problem arose when I flashed JB xloader and u-boot then I flashed the ICS one. I feel as if I permanently ruined a part on the phone, because there are countless other problems that go along with this like crashing etc.
Fixed thanks to Kuma
http://forum.xda-developers.com/showthread.php?t=2612356
Related
I am trying to flash from the bootloader to recover from an installation error on my Fuze. I've entered into the tricolor bootloader screen by holding down Vol.down and reset. Now, when I plug the phone into the computer, the computer recognize the phone as a Qaulcomm CDMA Technologies MSM, and is trying to install a driver for it (which it cannot find.) When I run the Custom_RUU, it does not find my Fuze and is showing a ERROR[260]: Connection.
What am I doing wrong? Do I need to find a driver for Qualcomm first? I searched, and it seemed that when you enter bootloader to flash, it is suppose to say USB at the bottom. Mine says Serial. Does that matter?
If more information is needed to troubleshoot:
SPL is SPL-1.90.OliNex
Phone is unlocked by using Olinex's unlocker
Rom was EnergyRom 3.0 Phoenix 51909
Problem was caused because I tried to install Studio Kuma Traditional Chinese Fonts on it. That program works flawlessly on a WM6.1. Of course, Energy 3.0 are WM6.5, hence causing the problem.
Any assistance is very appreciated.
Try sd card flashing
You have connect your device to your USB port and let it find the drivers. In order for it to download the drivers, you must have Activesync or Windows Mobile Device Center.
Once you have one of those downloaded, launch it and connect the device while it is running normally. Opt to connect via Activesync on your phone. You don't have to have these running in the future but you need it to find the drivers and install them. Leave the Activesync connection intact while you run the Flash program.
Once the phone reboots in bootloader mode, the PC will probably download some more drivers. The Flasher will probably time out while the drivers are being downloaded and installed. Keep trying.
Once the bootloader drivers are downloaded and installed, try to run the Flasher program again. Sometimes you'll need a reboot if something is hung up.
You SHOULD be able to reboot, put the phone in bootloader mode (Down + Power + Reset) and it should change "SERIAL" into "USB". Once it displays "USB" you are good to go. Load up the Flasher program and it should go all the way through without the assistance of ActiveSync or Mobile Device Center.
I always flash in bootloader mode, I just know the initial pairing is rough.
Well, I flashed from sd card, and the phone is working now. Thanks for everyone's replies.
Hi,
So I just purchased a Samsung Galaxy S II, and I've been trying a few different ROM's found on this site. The last thing I did was actually revert back to a stock Samsung Kernel and firmware. This worked fine, but it unrooted my device, which I knew would happen, but now I'm not able to root it again because when I put the device into download mode, ODIN, or better yet, my computer won't detect the device.
I have all the drivers installed, and I also deleted them all, and Kies, and started from scratch again after searching XDA for similar issues.
I don't believe this to be a driver issue, since I was able to root my device, and swap roms before I went back to the official kernel and firmware. I'm with Bell in Canada, so the versions I went back to were not the official Bell versions, since Samsung has not made them available.
I have a Mac, but I've been using Windows 7 and Odin under VMWare. I can connect my device to either OSX, or Windows 7 when the device is not in download mode, and everything works fine, and Odin detects the device (Not that that does any good of course)
When I connect the device under download mode, the Mac detects the device and asks me if I want to connect it to my Mac, or to Windows (As it should) but no matter which one I select, neither OS acknowledges the device after that point, where as when I'm not in Download mode, both OS's detect the device fine.
After all my troubleshooting with my computer based off of what I found online here, The only conclusion I have left is that there is something missing on the device that allows it to be found under download mode, but that aspect of all this is beyond my current skill level.
Anyone have any ideas?
Are you pressing the Volume Up button to continue in Download mode? Besides, Virtual machine isn't recommended I think.
Yes, Once the Custom ROM warning comes up, I press the Volume up button to continue.
That wasn't even necessary on the Stock Bell ROM. The warning didn't come up at all.
VM has been working fine up until now, so I don't think that's the problem, but I have been thinking of trying this on my old laptop that runs on windows if nothing else pans out.
Scott56 said:
Yes, Once the Custom ROM warning comes up, I press the Volume up button to continue.
That wasn't even necessary on the Stock Bell ROM. The warning didn't come up at all.
VM has been working fine up until now, so I don't think that's the problem, but I have been thinking of trying this on my old laptop that runs on windows if nothing else pans out.
Click to expand...
Click to collapse
Have you found anyway to Make Odin recognize to phone in download mode?? Im still struggling with that. my phone is on stock kernel and not rooted yet, ODIN finds it fine when the phone is on and USB Debugging is on, but once I put the phone on download mode it wont recognize it, I dont know why..
Could it be because of the ''SAMSUNG Mobile MTP Device'' driver failed to install correctly??
all other drivers are installed correctly.. I have tried to get the driver mentioned above to install correctly but it fails every time, with USB debugging on and off, i have wiped the phone and installed Kies and the drivers several times, Im clueless right.. anyone have any idea please help??
I myself am also suffering from this problem. However, USB seems to function fine while the phone is booted up or in recovery (For ADB). I'm wondering if necessary files may have become corrupted or deleted in reference to USB drivers (phone side mind you) that are used in download mode.
edit: It's also recognized in recovery mode.
Even if it can't be fixed I'd still like to understand why.
-Simply D
was looking for help on this and saw this thread, same problem too..
Connects to Odin and Kies fine when switched on "normally", can use USB mass storage mode Etc.
comes up with a USB device has malfunctioned message on PC when I connect USB cable when switched on and in download mode
EDIT:- just to add, if I try upgrading firmware via Kies it gets to the point where it switches the phone to download mode to upgrade it and has the same issue even with an official upgrade
Figuring download mode is outside the normal boot procedure, I hoped on an off chance that pulling my battery and sim for a few minutes would reset it. It did indeed. Download mode is now functional again, just to be certain I tested it right before pulling the battery to make sure it was still broken. And multiple flashes and reboots afterwards seem to confirm that it has returned to normal.
Anyone else who solves it with this method, please report back.
-Simply D
SimplyD said:
Figuring download mode is outside the normal boot procedure, I hoped on an off chance that pulling my battery and sim for a few minutes would reset it. It did indeed. Download mode is now functional again, just to be certain I tested it right before pulling the battery to make sure it was still broken. And multiple flashes and reboots afterwards seem to confirm that it has returned to normal.
Anyone else who solves it with this method, please report back.
-Simply D
Click to expand...
Click to collapse
Tried this and it didn't work for me :/ going to give it another try later, thanks for the suggestion either way
I've flashed a few different roms (trying to get around this), and i can't get flashtool (latest version, just downloaded yesterday) to recognize that my phone is in debugging mode. it flashes fine, no issues, then i disconnect, restart the phone, turn on USB debugging and allow non-market apps.
then i reconnect, and flashtool always says debugging is off, when the phone says debugging is on. i turn off the phone, and reconnect while it's booting, and i get the same result. i can flash all i want, but i can't get flashtool to root the phone, or install xrecovery.
i've searched, and can't find a solution. any ideas?
- Trying Open Flashtool with the phone connected.
- Uninstall flashtool and install an old version of the program
- if does not work, change the cable (I've had a similar problem, I bought a new cable...)
Same issue found my solution
Hey I had the exact same issue but I found a solution.
My device is SE x10i 2.3.3 Generic
What I did was accidental.
I tried the old method of routing gingerbread which was too downgrade using "X10_aZuZu_Kernel_Downgrade_Generic.ftf"
but wat I also did was extract the load & kernal from the original ftf that I used to flash my phone with in the first place and put them into their own bundle so I could restore them.
After Flashing with the aZuZu downgrade
I disconnected the phone and turned it on it was stuck at the load screen where it says Sony Ericsson so I connected it again and my pc started downloading drivers.
But I installed the SEMC USB driver in the first place so I was wounder wth was goin on.
It turns out that in order for this to run smoothly you must make sure ALL DRIVERS are installed I personnally thought there was only one driver lol.
So you need to download the SEMC MASS STORAGE driver and 2 others (can't remember the names) perhaps the easiest way would be to just install the latest pc companion not sure but anyways this worked for me.
hope this helps
Having strange PC connectivity issues(Windows 7). I plug my phone into my computer, I sometimes get that pop-up thing that says "Charge Only, Media Sync, etc..." - Sometimes I don't get a pop-up. Neither my phone nor computer recognizes it's been plugged in. Even though it still charges. But when I do get that pop-up, no matter which setting I choose, it stays on Charge Only mode. I first noticed then when using SnowJB, so I tried other ROMs and still have this issue. Things I've done:
I've reinstalled the drivers from the LG webpage.
I've LGNPST back to stock(No root, locked bootloader)
I've tried running the Root exploit thing, but it can't find my phone even though my phone says USB debugging is on
Tried using a different USB cable.
Pretty much, the only time my PC recognizes my phone is whenever it's in download mode using LGNPST. So I don't think it's a hardware issue since it works then. So for now, I'm stuck on an unrooted phone
Android Version - 4.0.4
Baseband - APQ8064/MDM9x15M
Kernel Version - 3.0.21
Build Number - IMM76L
Software Version - E97010o
Any ideas on what to do? If I go to AT&T, will they be able to tell that it's been rooted before?
So,
I'm trying to flash my Z5C with latest LP but when I try to enter Flash Mode to do it the phone enters Safe Mode. Now some people say it might be driver related and yes, one of the Z5C drivers I tried installing says this:
Sony Net (03/19/2015 6.0.6000.16511) Not needed (No device for update present)
Now even if it is a driver issue, shouldn't I be able to enter flash mode by simply pressing Vol Down + Power Button? I still enter Safe Mode. Can I not enter Flash Mode any other way than the Vol Down + USB?
I bought this phone a week or so ago and have not fiddled with anything apart from turning USB Debugging and Unknown Sources on. Other than that I have not done anything, not even OTA as it instantly goes to MM. This phone is stock firmware from factory.
Now when I tried connecting to Flashtools by entering Safe Mode (which I thought was flash mode but with a diff name) Flashtools either says Debugging is off or it goes as far as saying "Root Access Denied" (Note: it's not an error, just another message) and stops. The popup which says to plug in the phone doesn't dissapear either. So that's where I'm stuck and it's due to me not being able to enter Flash Mode on the phone.
So question is, what am I doing wrong?
PS. I will try this all over again on my W7 desktop as I've only tried with my W10 laptop and I know there are different driver settings. Yes I did enable "No Driver Signature"-mode on W10 prior to installing them but nothing changes.
Thankful for any help as I don't want stock, cause it's not very optimized and also phone can get a bit hot whereas they fix a lot of issues with these updates.
[EDIT]
Btw, can't find Sony PC Companion on the official site. Instead it's replaced by Xperia Companion. Inferior in tools but I assume they have the same drivers for phones included?
Anthraxiousness said:
So,
I'm trying to flash my Z5C with latest LP but when I try to enter Flash Mode to do it the phone enters Safe Mode. Now some people say it might be driver related and yes, one of the Z5C drivers I tried installing says this:
Sony Net (03/19/2015 6.0.6000.16511) Not needed (No device for update present)
Now even if it is a driver issue, shouldn't I be able to enter flash mode by simply pressing Vol Down + Power Button? I still enter Safe Mode. Can I not enter Flash Mode any other way than the Vol Down + USB?
I bought this phone a week or so ago and have not fiddled with anything apart from turning USB Debugging and Unknown Sources on. Other than that I have not done anything, not even OTA as it instantly goes to MM. This phone is stock firmware from factory.
Now when I tried connecting to Flashtools by entering Safe Mode (which I thought was flash mode but with a diff name) Flashtools either says Debugging is off or it goes as far as saying "Root Access Denied" (Note: it's not an error, just another message) and stops. The popup which says to plug in the phone doesn't dissapear either. So that's where I'm stuck and it's due to me not being able to enter Flash Mode on the phone.
So question is, what am I doing wrong?
PS. I will try this all over again on my W7 desktop as I've only tried with my W10 laptop and I know there are different driver settings. Yes I did enable "No Driver Signature"-mode on W10 prior to installing them but nothing changes.
Thankful for any help as I don't want stock, cause it's not very optimized and also phone can get a bit hot whereas they fix a lot of issues with these updates.
[EDIT]
Btw, can't find Sony PC Companion on the official site. Instead it's replaced by Xperia Companion. Inferior in tools but I assume they have the same drivers for phones included?
Click to expand...
Click to collapse
USB is the only way. I had to use 4 different PCs before finding one flash tool liked BTW. And you are kind of wrong about they fix issues with these updates. They really just create more. I'm on.200 LP and probably never going MM until aosp can deliver because MM is so messed up.
Did you get this sorted?
I can't boot into flash mode either, and I am stuck on a boot loop. Phone trying to setup and processes stopping.
civicsr2cool said:
USB is the only way. I had to use 4 different PCs before finding one flash tool liked BTW. And you are kind of wrong about they fix issues with these updates. They really just create more. I'm on.200 LP and probably never going MM until aosp can deliver because MM is so messed up.
Click to expand...
Click to collapse
Thank you for the suggestion to try different PCs. I only have the one at home but I tried a different USB port and Flashtool is working now. Bizarre.