in an earlier thread of mine i said that, quote unquote, "a friend of mine helped me download a custom kernel, but that failed and caused a bootloop. we then tried flashing various other custom roms and eventually they booted up, just to reveal the unsuccessful decryption error". once i managed to solve this i went back to MIUI for a bit and then decided to open the bootloader on another computer, not my main one. i went back to my main computer and i couldn't even connect the phone via fastboot to flash the recovery: it just made the windows 10 usb disconnecting sound and showed, on my phone, "press any key to exit fastboot" or something like that. i went back to that other computer and tried flashing TWRP (it worked, but asked for a non-existent password once again) and then flashed orangefox, which worked. now i'm back on my main computer and i wanted to flash AEX, but i still couldn't connect to the computer. i tried switching ports/cables, what should i do? i do not wanna keep using MIUI, that is just one of the ****tiest ROMs ever.
still lightyears ahead of emui
somehow its common problem on windows 10, try connect using usb hub
if it still happen, try to google it, there's other solution for it, but using usb hub is the best solution imo
Related
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
Ok, so this was my first attempt at trying to root and flash a device, and somewhere along the way, I screwed up. I installed TWRP on my Galaxy Tab 10.1 WiFi only tablet (GT-P7510 32GB) via Odin, and rooted the device with the SuperUser and everything was gravy. Then, I tried to flash CM onto the device, and something went wrong. Bad install file or something along those lines.
OK, I'll just wipe it off and try again, went into TWRP "Wipe", and did all of the wipes. Which is where I went wrong. I did ALL of the wipes. So now the only thing still on the tablet is TWRP. Luckily I can still boot into that, but that's it.
So, this is where the real problem comes in. I need to be able to load the ZIP onto the device root so I can use TWRP to install it, but for the life of me I cannot get my Windows 7 Laptop to recognize the device. I have installed, uninstalled, and reinstalled the Samsung drivers at least 4 times, being extra patient to reset both the computer and tablet after each attempt, i've tried turning the computer on with it already plugged in, i've tried waiting to plug it in until after the computer is fully booted, everything.
The USB port on the computer recognizes other USB flash drives just fine, i'm using the OEM cable, and everything worked fine to connect the tablet with Odin before I did that wipe, so we can rule out the cable being bad.
I've been reading a lot of forum posts both on XDA and elsewhere and I've seen people talking about needing to uncheck the USB debugging in Settings, but obviously I can't get there, because there's no OS. This must have been unchecked before the wipe though, because it connected fine then.
Help
Interesting addendum.
I actually CAN access the device with Odin. It will allow me to reflash the TWRP .tar file onto the device. Not sure if that's helpful at all though.
Figured it out, questions answered
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.
I have flashed my device probably 50 times at this point trying different ROMS. Yesterday I decided to give stock another shot, but now I'm stuck. I had to flash the stock recovery to update to Marshmallow after restoring my Lollipop backup. I'm not happy with it, but I cannot reflash TWRP. When I boot to bootloader the fastboot drivers no longer work. Windows device manager says it's an unknown device and the device descriptor failed. I can't even manually force it to install the driver for the device by picking it, because it says that the driver isn't for that device. I even tried resetting my crappy Windows tablet so that it would have nothing previously installed and then installed HiSuite, but the same problem there as on my desktop. I have also tried generic "universal" android drivers and sketchy Huawei drivers from a "how to unlock your bootloader" tutorial. I have unplugged it and replugged it several times, using various different USB ports (I have 10 of them, so no shortage there).
I can't flash recovery through fastboot because that isn't an option. When in normal mode the computer sees the device just fine as a MTP device and an ADB device, but when I try to run ADB commands they don't see the device either. At this point I am really trying to find any way I can root the phone, regardless of how sketchy, so I can use Flashify to restore TWRP and go back to CM13 or an AOSP. Does anybody know a working method to root besides flashing through fastboot? Thanks.
Darrian said:
I have flashed my device probably 50 times at this point trying different ROMS. Yesterday I decided to give stock another shot, but now I'm stuck. I had to flash the stock recovery to update to Marshmallow after restoring my Lollipop backup. I'm not happy with it, but I cannot reflash TWRP. When I boot to bootloader the fastboot drivers no longer work. Windows device manager says it's an unknown device and the device descriptor failed. I can't even manually force it to install the driver for the device by picking it, because it says that the driver isn't for that device. I even tried resetting my crappy Windows tablet so that it would have nothing previously installed and then installed HiSuite, but the same problem there as on my desktop. I have also tried generic "universal" android drivers and sketchy Huawei drivers from a "how to unlock your bootloader" tutorial. I have unplugged it and replugged it several times, using various different USB ports (I have 10 of them, so no shortage there).
I can't flash recovery through fastboot because that isn't an option. When in normal mode the computer sees the device just fine as a MTP device and an ADB device, but when I try to run ADB commands they don't see the device either. At this point I am really trying to find any way I can root the phone, regardless of how sketchy, so I can use Flashify to restore TWRP and go back to CM13 or an AOSP. Does anybody know a working method to root besides flashing through fastboot? Thanks.
Click to expand...
Click to collapse
There is none. The only safe way to root is to flash TWRP in fastboot. Right now, you can try to force update through update.app
Thanks for the reply, but:
1. I'm not looking for a safe method, just any method. I've tried the obvious suspects already (towelroot, kingroot, kingoroot)
2. I don't need to force an update, I am on the latest firmware now. If anything I may have to attempt to force a downgrade to open up vulnerabilities, but if I go back to lollipop then I will likely have issues flashing cm13.
Darrian said:
Thanks for the reply, but:
1. I'm not looking for a safe method, just any method. I've tried the obvious suspects already (towelroot, kingroot, kingoroot)
2. I don't need to force an update, I am on the latest firmware now. If anything I may have to attempt to force a downgrade to open up vulnerabilities, but if I go back to lollipop then I will likely have issues flashing cm13.
Click to expand...
Click to collapse
Oh. But like I said, there is none.
I have come to the same conclusion, but I'm still hoping if somebody has rooted it in another way that they will see this thread and share their method. Otherwise I may end up stuck on unrooted stock, which will kinda suck.
Darrian said:
I have come to the same conclusion, but I'm still hoping if somebody has rooted it in another way that they will see this thread and share their method. Otherwise I may end up stuck on unrooted stock, which will kinda suck.
Click to expand...
Click to collapse
Have you tried changing the drivers.?
Yes
So, I did not figure out how to root it without fastboot, but I did solve my problem. I dug out the cable that came with the phone, and using that cable my computer finally recognized it as an Android device when in fastboot mode. I don't know why it only works with that cable, but there it is, so I will have to make sure that cable never gets broken or lost.
Darrian said:
So, I did not figure out how to root it without fastboot, but I did solve my problem. I dug out the cable that came with the phone, and using that cable my computer finally recognized it as an Android device when in fastboot mode. I don't know why it only works with that cable, but there it is, so I will have to make sure that cable never gets broken or lost.
Click to expand...
Click to collapse
Glad you fixed it. :highfive:
So after updating the phone to miui 11, the file transfer mtp using USB was not working...
Tried everything, installing drivers, changing pc, cable. lit every possible thing...
Finally decided to flash an older version of rom.
it was successful, but still, usb file transfer was not working.
So, thought to install custom rom, and for that, i installed twrp, and by mistake, i cleaned everything including the system.
now, my phone got dead. but still, fastboot bootloader mode was working, So, I tried a different bunch of commands that I found over internet. but nothing worked.
So, again I flashed the stock rom using mi tool, and it broke the last working thing also(fastboot screen).. and my phone stuck in a loop. it just vibrates and turns on-off without any indication on-screen(no Mi logo, no charging light, nothing)...
at last, tried EDL mode, but still no luck, i tried different version of stock rom using EDL mode also. nothing working....
Need help to fix this phone.