Hey Guys:
Ive got a Samsung exhibit 2 4g and I want to root it. Except when I connect usb, it always says cannot install driver. I've gone to device manager and it has two listings saying "SAMSUNG Android USB Composite Device" with exclamation marks next to it. Ive factory reset the phone and I have usb debugging on to. It also wont list for adb devices. Ive burnt about 6 hours for this and nothing.
Any help would be appreciated.
Bump... ANy help? Still cant get it!
bozaira said:
Bump... ANy help? Still cant get it!
Click to expand...
Click to collapse
did you install necessary stuff on PC? (e.g. http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/)
p107r0 said:
did you install necessary stuff on PC? (e.g. http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/)
Click to expand...
Click to collapse
Yeah I tried that... and probably every possible thing. I guess me and adb+Windows 7 64 bit dont go together . I still like the phone and I think I'll try this on Windows XP hopefully it will work. I'll keep you posted.
Do you know any other way of rooting the Exhibit 2 without adb. Cant even get it on XP
any solution yet??
bozaira said:
Do you know any other way of rooting the Exhibit 2 without adb. Cant even get it on XP
Click to expand...
Click to collapse
Me too facing the similar issue.. my exhibit-2 is unlocked, so i was wondering if that could be the issue.. but seems it is not.
Share with me if u managed to get some solution.
Basically I have no rom on my phone, I have tried sideloading and everything and it could not work. However, I noticed under devices that instead of saying HTC it says android phone and I am unable to access it. I have tried going into properties, however it refuses to let me uninstall or or update drivers. Does anyone know anyway for my phone to recognize it as a HTC and not just an android phone? Maybe then I can bump a rom or sideload it onto my phone. Also when I sideload it shows HTC XXXXXXXXXX when i typ in cmd adb devices. In CWM it says sideload started. When I go to adb sideload derp.zip it gives me a massive wall of text and my phone doesn't show any files being transferred and says its still waiting for them to start transfer.
Any ideas?
Worst case scenario you think I could take it to T-Mobile and ask them to do a factory reset on it?
derpyherpes said:
Basically I have no rom on my phone, I have tried sideloading and everything and it could not work. However, I noticed under devices that instead of saying HTC it says android phone and I am unable to access it. I have tried going into properties, however it refuses to let me uninstall or or update drivers. Does anyone know anyway for my phone to recognize it as a HTC and not just an android phone? Maybe then I can bump a rom or sideload it onto my phone. Also when I sideload it shows HTC XXXXXXXXXX when i typ in cmd adb devices. In CWM it says sideload started. When I go to adb sideload derp.zip it gives me a massive wall of text and my phone doesn't show any files being transferred and says its still waiting for them to start transfer.
Any ideas?
Worst case scenario you think I could take it to T-Mobile and ask them to do a factory reset on it?
Click to expand...
Click to collapse
That used to happen to me with another phone I had and what I would do to solve it was uninstall the "android phone" driver (with the device connected at all times), then scan for hardware changes and it would reinstall the driver correctly.
I haven't experienced this issue with this phone but worked in the past with other HTC phones, hope it helps
Sent from my Nexus 7 using Tapatalk 2
megabiteg said:
That used to happen to me with another phone I had and what I would do to solve it was uninstall the "android phone" driver (with the device connected at all times), then scan for hardware changes and it would reinstall the driver correctly.
I haven't experienced this issue with this phone but worked in the past with other HTC phones, hope it helps
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Also, you may need to regedit uninstall. Search and delete all "android" references in your registry. Reboot. Install generic android drivers.
But definitely try the simpler method first!
Tried both of the solutions and neither one worked I am at my wit's end lol
Anythign else I can try?
derpyherpes said:
Tried both of the solutions and neither one worked I am at my wit's end lol
Anythign else I can try?
Click to expand...
Click to collapse
Assume you've also tried installing generic HTC drivers?
Hey everyone. I'm in a very big issue right now. I've searched far and wide on the internet to try to find a solution to this, but to no avail. I was recently messing around in TWRP on my Kindle Fire HD 7", when all of a sudden I went to reboot it and then just a blank red screen. So obviously I have bricked it. I know how to run the recovery program to get it unbricked, no issue. I have bricked my Kindle before in the past and was able to easily fix it by running the Kindle restore recovery program. So now when I went to my PC to try and unbrick it, I get this message "One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it." So clearly the drivers aren't working. I went into the devices manager and located it under Universal Serial Bus Controllers as "Unknown Device." When I attempt to update the drivers, there is no Amazon option. I have tried uninstall and reinstalling the drivers countless times. I tried as many different driver sources as I possible could come across and nothing is working. I have used three different computers so far, and none are working. I do have a fastboot cable, which is what I'm using to do this. I can get my Kindle into fastboot but that still doesn't change the fact that the drivers aren't working. I have made a YouTube video about this. I will post the link to my video that I made so anyone can better understand this. I am desperate at this point, and I appreciate any help I can get.
EDIT: I can't post the link at this time since i'm "new and probably a spambot," so feel free to PM me and I'll provide the link.
I'm so sorry man the only advice I can give you is to try to flash a custom ROM over fastboot but that probably won't work you might be able to find a program that let's your computer find your device without it powered on or bricked. Sorry man also they are like 50 bucks on utube if worst comes to worst.
Do you think it has anything to do with something being broken internally? Because I have never had an issue with it not being recognized in fastboot.
Sent from my SM-G900V using XDA Free mobile app
I don't think so the same happened to me and I just flashed a custom ROM after a factory reset and that worked also did you enable adb before this happened? Because if you didn't, your going to have to toy with twrp until you can find a custom ROM you might have previously downloaded.
Yes, I always have adb enabled. But I can't even get into twrp. It's fully bricked, it just boots up to a blank red screen.
Sent from my SM-G900V using XDA Free mobile app
Ummmmm you could try sending it to amazon or a service on eBay that's kind of your last resort but still try to look for a fix I'll be looking around for a fix
So... now that I think with hindsight, I did something pretty stupid, and I'm going to need some help, since I have no idea what to do.
I have a Nexus 9 tablet, and I never liked it. The OS is just so slow and laggy, and it overheats, and it has many other problems. Quite a couple of times, I installed custom ROM's and so on, and I never had a problem. Let me explain what I did now.
Around a month ago, while looking on the internet, I heard this thing that if I install the original software, but with no encryption, it would work better. It sounded cool at the time, so I downloaded the Nexus Root Toolkit, and did it.
Everything went well. But then I heard about a custom ROM that was apparently working even better, Dirty Unicorns, so using the same toolkit, I installed it. For the first time, my Nexus 9 actually worked the way it is supposed to work, but the custom ROM still had its problems, it crashed from time to time. I was thinking about possibly returning or selling the tablet, so that's why using the Toolkit, I reinstalled the original software. But, if I went all the steps, and also locked the OEM, my device then showed a flag saying that it was a development device, while booting up. So, after messing around with the settings of the Toolkit a little, I decided to reinstall the software, but leave the bootloader unlocked.
But after some time, I reinstalled my Windows, and I also reinstalled the Toolkit. But that's when I started to have problems. My tablet wouldn't connect to my laptop anymore. I used the toolkit and uninstalled drivers, reinstalling others quite a couple of times, and that's where I think that I messed something up. I managed to eventually connect my tablet, and I rooted it, after rooting it, I connected it again. But adb wasn't working for some reason. A little annoyed, I simply copy pasted the zip file of CM13 into my tablet's internal storage, and I rebooted it to the recovery, TWRP. But the recovery failed to flash it, saying something about an Error 7.
Now that I think about it, I was stupid, since after that, I performed a complete factory reset, resetting my TWRP backup too. I tried to connect it again, nothing. It didn't connect at all. I plug it in, my computer doesn't even recognize that something is plugged in. No Nexus 9, no Android Device, no anything. I booted it in fastboot mode, and it worked, my computer recognized it, and after I downloaded a ROM zip file again, I tried to connect the tablet back and flash it manually, but nothing. It didn't recognize anything anymore.
I tried to reinstall the drivers countless times. I deleted what I had, reinstalled it, nothing. I uninstalled and reinstalled the Toolkit. But strangely, now, even if I know that I installed the Google USB drivers, and the ADB drivers, as I even installed Android SDK, if I use USB Deview, it doesn't show me any of them. I can't see any Google or ADB drivers, although I tried installing them multiple times. So now, I'm stuck with a tablet with TWRP and no OS, which I can't connect to my PC, and I can't use ADB or fastboot.
Is it something from my laptop? I can't check to see if it will connect to another PC right now, so I don't know for sure. Is there any way to delete all the traces from my (failed) attempts at reinstalling the drivers, and to install them again properly? Or is it something from the tablet itself? I don't have an OS, so I can't enable USB debugging.
So, shortly, I have no idea what's happening. And I'm quite obviously a noob in all of these. Can anyone help me? Please?
If you boot into the bootloader and from a command prompt type fastboot devices you don't get anything?
Sent from my Nexus 9 using XDA-Developers mobile app
I still couldn't get ADB to work, but I managed to work out fastboot. It may be something from my USB cable, it works perfectly.
I flashed the original software back, and I'll go to check my cable, although I feel kinda stupid that I didn't think about that in the first place.
Thanks for the help anyway.
If fastboot is working and bootloader is unlocked, you can still install a factory image.
Depending of your device download for wifi Version:
https://dl.google.com/dl/android/aosp/volantis-mob30p-factory-2cb57a1b.tgz
If you habe the LTE variant:
https://dl.google.com/dl/android/aosp/volantisg-mob30p-factory-ae9ce05a.tgz
Extract the files and put them into the same directory link fastboot and execute the flash-all.bat
WARNING: Any data will be erased!!! Also TWRP
Now it should boot up with stock firmware.
If you want your device decrypted install twrp. format the internal storage and flash the pure nexus rom which i can highly recommend and is decrypted by default. Dont forget do flash gapps
my issue is same
what if someone USB- debug is not enabled , is there any possibility to do that , i have a device nexus 9 , rooted it it went into bootloop then i factory reset it , and now my adb is not communicating , if there is any options?
rohanzakie said:
what if someone USB- debug is not enabled , is there any possibility to do that , i have a device nexus 9 , rooted it it went into bootloop then i factory reset it , and now my adb is not communicating , if there is any options?
Click to expand...
Click to collapse
Use fastboot, not adb.
what if fastboot isn't working, either?
uberSkeptic said:
what if fastboot isn't working, either?
Click to expand...
Click to collapse
Is the tablet in fastboot mode?
madbat99 said:
Is the tablet in fastboot mode?
Click to expand...
Click to collapse
Yup. I can boot into the bootloader, and from there (or from TWRP) into fastboot, but no computer I've connected it to (and I've tried many) will recognize it. Doesn't show up in Device Manger or lsusb, doesn't show up from either "adb devices" or "fastboot list devices" (the latter just hangs there saying "Waiting for any device"). The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
uberSkeptic said:
Yup. I can boot into the bootloader, and from there (or from TWRP) into fastboot, but no computer I've connected it to (and I've tried many) will recognize it. Doesn't show up in Device Manger or lsusb, doesn't show up from either "adb devices" or "fastboot list devices" (the latter just hangs there saying "Waiting for any device"). The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
Click to expand...
Click to collapse
Hi, uberSkeptic...
Just a quick thought... Have you tried a different USB cable?
Rgrds,
Ged.
Edit & Additional...
The command is not fastboot list devices... it's fastboot devices
One last point... Ensure your Nexus 9 is definitely booted into fastboot mode and not just HBOOT (the bootloader). Take a look at the two screenshots below - your Nexus 9 should look like the screenshot on the right, the one with my green explanatory text.
Apologies for the poor image quality; there's no way of taking a screenshot in the bootloader, so I had to take photographs instead.
Hope this helps and good luck.
Thanks for the advice and going so far as to photograph the hboot/fastboot screens, but unfortunately I have indeed tried multiple USB cables, including the OEM's and I've definitely successfully gotten the tablet into fastboot but it doesn't show on the computer with either fastboot command (devices or devices list).
uberSkeptic said:
Thanks for the advice and going so far as to photograph the hboot/fastboot screens, but unfortunately I have indeed tried multiple USB cables, including the OEM's and I've definitely successfully gotten the tablet into fastboot but it doesn't show on the computer with either fastboot command (devices or devices list).
Click to expand...
Click to collapse
I'm out of ideas then.
One of my first thoughts was possible Windows driver problems, but as you mentioned you'd tried it on several different computers, that didn't seem to be a likely cause of the problem - I mean, you'd expect at least one of 'em to work! Maybe somebody else can help with a solution.
GedBlake said:
I'm out of ideas then.
One of my first thoughts was possible Windows driver problems, but as you mentioned you'd tried it on several different computers, that didn't seem to be a likely cause of the problem - I mean, you'd expect at least one of 'em to work! Maybe somebody else can help with a solution.
Click to expand...
Click to collapse
Sadly, me too. I even tried using a flash drive with a micro-USB connector on it, which I used to use to do nandroid backups, but now TWRP doesn't even "notice" that the USB drive is there (or any USB drive connected via an OTG cable).
Too bad, too - the tablet is otherwise in great condition and even has a custom-painted backplate (long story).
Thanks for trying to help, though!
uberSkeptic said:
...The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
Click to expand...
Click to collapse
Mmm...
uberSkeptic said:
...I even tried using a flash drive with a micro-USB connector on it, which I used to use to do nandroid backups, but now TWRP doesn't even "notice" that the USB drive is there (or any USB drive connected via an OTG cable).
Click to expand...
Click to collapse
Mmm... (scratches head, raises eyebrow quizzically)...
If I was Hercule Poirot and this was a murder case, and with all the suspects gathered in one room, prior to revealing a brilliant deduction... I'd be casting very dark glances in the direction of your Nexus 9's USB port right now as the likely culprit here.
Think about it. Different computers. Different USB cables. An OTG cable... And none of them work. What's the one thing they all have in common?
Answer: The USB port on the Nexus 9 itself, and where you've replaced the USB daughter-board.
Maybe, possibly, that replacement don't go so well. Maybe there's some unknown problem with it. I can't comment too much on this, 'cos it outside the scope of my knowledge - I'm a software guy; circuit boards and dismantling devices to fix 'em isn't something I'm comfortable with. I always think I'm going to damage something or rip a wire out somewhere, so I bow to your superior knowledge in this area, as I may be talking complete cobblers here. It certainly wouldn't be the first time.
Anyway... Sorry I wasn't able to help find a working solution for you. If anything occurs to me that might help, I'll be sure to let you know.
Rgrds,
Ged.
I would be suspect if the replacement as well if it weren't for the fact that I did it only AFTER the other symptoms/problems appeared. Hence the replacement (which is known good because the battery charges no problem). There cables and everything inside the tablet tests just fine... It feels like the firmware for USB is somehow corrupt or something.
Thanks for all the advice, though. ?
So I can't believe I didn't think of this before, but when I run "dmesg" from the terminal app included w/ TWRP, I see that there a TON of errors, mostly referencing problems accessing the recovery image. I could screenshot it, if anyone at all might be able to tell me a little more specifically what the dmesg log is trying to tell me...
Hi guys,
I have been searching for hours but I can't seem to find how to fix my problem.
I have a new Z5 Compact that I was trying to flash with the stock firmware but I somehow managed to brick it. I don't think I had the drivers installed properly when I tried to flash with flashtool but since flashtool didn't even detect my phone or appear to begin flashing it I don't know how I bricked it. Anyway after trying for hours to fix it on my own I can't seem to find the information that I need. I have installed the drivers properly as far as I can tell by allowing unsigned drivers on windows 10 but whenever I boot to flash mode the phone isn't detected. Nothing even comes up in Device Manager so there are no options to update drivers or anything. I just hold the volume down button, plug in the usb, the LED briefly flashes red before holding on green and then nothing happens. Neither Flashtool or PC Companion detect the phone and I have tried this on 2 different laptops running Windows 7 and Windows 10. If anyone has any instructions on how to get this to work on Ubuntu I'm willing to try that too as I also have Ubuntu installed but I am really at a loss for what else I can try.
Any help would be greatly appreciated.
Thank you
tokococo said:
Hi guys,
I have been searching for hours but I can't seem to find how to fix my problem.
I have a new Z5 Compact that I was trying to flash with the stock firmware but I somehow managed to brick it. I don't think I had the drivers installed properly when I tried to flash with flashtool but since flashtool didn't even detect my phone or appear to begin flashing it I don't know how I bricked it. Anyway after trying for hours to fix it on my own I can't seem to find the information that I need. I have installed the drivers properly as far as I can tell by allowing unsigned drivers on windows 10 but whenever I boot to flash mode the phone isn't detected. Nothing even comes up in Device Manager so there are no options to update drivers or anything. I just hold the volume down button, plug in the usb, the LED briefly flashes red before holding on green and then nothing happens. Neither Flashtool or PC Companion detect the phone and I have tried this on 2 different laptops running Windows 7 and Windows 10. If anyone has any instructions on how to get this to work on Ubuntu I'm willing to try that too as I also have Ubuntu installed but I am really at a loss for what else I can try.
Any help would be greatly appreciated.
Thank you
Click to expand...
Click to collapse
sounds dumb but have you tried a different port and different cable? i ran into the same problem and found out one of the ports on my laptop doesnt work for data. flashtool is a major pain, it took me three pcs to find one that it worked with and then it took a good 5 tries and reboots to have a successful flash. flashing twrp and then xpower would be easier imo.
civicsr2cool said:
sounds dumb but have you tried a different port and different cable? i ran into the same problem and found out one of the ports on my laptop doesnt work for data. flashtool is a major pain, it took me three pcs to find one that it worked with and then it took a good 5 tries and reboots to have a successful flash. flashing twrp and then xpower would be easier imo.
Click to expand...
Click to collapse
Yeah, I have tried 7 ports and 3 cables across two different pcs. There's a desktop I can try on but I'll wait until tomorrow. It's really frustrating. I just wanted to root so that I could batch install my apps from Titanium but now I have got a brick. In the time that I have spent trying to fix it I could have selected and installed all the apps individually.
tokococo said:
Yeah, I have tried 7 ports and 3 cables across two different pcs. There's a desktop I can try on but I'll wait until tomorrow. It's really frustrating. I just wanted to root so that I could batch install my apps from Titanium but now I have got a brick. In the time that I have spent trying to fix it I could have selected and installed all the apps individually.
Click to expand...
Click to collapse
keep trying, it'll work after you figure out whats wrong with your install, flashtool is real finnicky. If your already soft bricked and only want root id suggest fastboot twrp 3.0.2 then flash xpower 3.0 and be done with it. the only real reason to use flashtool is to flash a new image onto the phone because you cant take an ota.
civicsr2cool said:
keep trying, it'll work after you figure out whats wrong with your install, flashtool is real finnicky. If your already soft bricked and only want root id suggest fastboot twrp 3.0.2 then flash xpower 3.0 and be done with it. the only real reason to use flashtool is to flash a new image onto the phone because you cant take an ota.
Click to expand...
Click to collapse
Thanks for your help. So I can do that without unlocking the boot loader?
tokococo said:
Thanks for your help. So I can do that without unlocking the boot loader?
Click to expand...
Click to collapse
bootloader has to be unlocked before doing any of this.
civicsr2cool said:
bootloader has to be unlocked before doing any of this.
Click to expand...
Click to collapse
Oh, you mean to do that once I have fixed my current issue.
Hmm, I seem to be having a smiliar issue, except instead of flashmode, mine isn't detected in fastboot mode, tried a crap load of drivers and usb ports etc..
EDIT: Got it fixed after following this guide
http://forum.xda-developers.com/z5-compact/general/unlock-bootloader-z5-compact-t3236237
RaunoT said:
Hmm, I seem to be having a smiliar issue, except instead of flashmode, mine isn't detected in fastboot mode, tried a crap load of drivers and usb ports etc..
EDIT: Got it fixed after following this guide
http://forum.xda-developers.com/z5-compact/general/unlock-bootloader-z5-compact-t3236237
Click to expand...
Click to collapse
I tried following that guide but when I try to install the driver it just says "The INF file you selected does not support this method if installation". You didn't happen to have that problem and find a workaround did you?
Just an update on what I have tried if anyone has any suggestions...
I tried inserting a SIM in case that would make any difference. I have also tried it on a desktop pc as well as the two laptops now which is windows 7, 8.1 and 10. The Windows 8.1 attempt was a clean install and I used the advanced boot method to enable the installation of unsigned drivers. I had high hopes for that but it didn't work. What I find curious is there is no activity when I plug the phone in, in flash mode. If I plug it in, in fastboot mode it searches for drivers and the device appears in device manager but with flash mode I get nothing. I'm beginning to think that perhaps the device itself has a faulty flash mode.
tokococo said:
I tried following that guide but when I try to install the driver it just says "The INF file you selected does not support this method if installation". You didn't happen to have that problem and find a workaround did you?
Click to expand...
Click to collapse
Sadly no :/
I managed to flash a Z5 Compact with the same model number without any issues on the same computer that won't detect my handset so I'm pretty sure that it's an issue specific to this handset. Thanks everyone for their suggestions.