Related
My vibrant is stuck on the vibrant logo after I tried to use the one click unroot program. The only solution I found after two days searching on the net, is to use odin. The first problem is that my phone is locked, so I can't use the vol up+down+power button combo to get into recovery or download mode.
Now comes the issue, I want to use adb to reboot the phone, but adb can't see my device. After installing the samsung USB Drivers, I see that the adb drivers are not installed (The drivers for this device are not installed. (Code 28)), and even when I try to manually install them from the SDK drivers (I checked the "include subfolders) it says that it can't find them.
I have windows 7 x64
Anyone have suggestions to how to install the adb drivers and make the adb see my device?
Can you get into download mode? Have you tried to Odin back to stock? If you want to set up ADB type ADB for dummies in search and you should find everything you need.
Here is the link from the sticky thread for help with drivers:
http://forum.xda-developers.com/showthread.php?t=728929
I just figured out a neat trick to get phone to work even if it's stuck on the vibrant screen.
Just connect it to the usb, wait until the grey battery picture appears.
After 5 seconds, take the battery out and put it right back, (leave usb in) and wait again. Do it once more, until you see that the battery picture turns green. After that take the battery out and unplug the usb, and turn the phone on.
It should work now.
The thing is that, next time you turn the phone off and on, it would be stuck again, so do something to fix it like odin.
That how it worked for me.
And about the adb driver problem, I just pointed manually the driver update to the "USB Drivers" that TGA_Gunnman posted here (I can't post link. just search usb drivers here in the forum) and after that adb worked like a charm, rebooted instantly to download mode - it's crucial for those like me that have hardware locked phones.
The thing is, that all the other posts say to point it to the sdk drivers, but that dosen't work.
Good luck to all others.
installing the samsung drivers and installing adb are two different things. the samsung drivers should install normal by double clicking the driver package (you may have to still tell windows where to look). installing adb is simply downloading the sdk, however, if you want adb to work everywhere (instead of just the sdk/tools folder) you need to put the sdk/tools folder in your path.
then 'adb devices' should show your device in win powershell, but will only work if you are in the sdk/tools folder or have added it to your environment variables.
i know that it's a bit silly to create an entire thread for one guy's problem, but i am stuck and probably going to give up hope when it comes to rooting my s5 neo (again, g903f), which is running android 5.1.1.
several days worth of research have yielded nothing. i can connect to my device using mtp, and i have usb 2 and 3 ports. lsusb and adb are working for me; i have set udev rules and "adb devices" returns my phone's serial number and its status. usb debugging is enabled as is the oem unlock (though whenever i try to disable developer tools and put them on again, the gui messes itself up and it won't let me turn them off, even if i refuse to put in my device's password). that's the only success i've had.
fastboot isn't working; "fastboot devices" shows nothing and it hangs at "< waiting for device>" with other commands, such as "fastboot oem unlock". adb won't work in download mode, either - though this is expected. rebooting into download mode via adb doesn't fix my problem, nor does using "sudo" or the root account.
odin3 won't work either despite the window opening with wine; the device never shows up in download mode. heimdall also doesn't seem to detect my device - although it might just be down to my ignorance.
the usual root tools, such as srsroot and kingo don't seem to do any good, though neither worked under wine, which helps to diagnose the problem. i have no access to windows, even through vmware.
i feel like everything i do only brings me one step closer to a brick wall, which i'm hitting all the time. it's like i've been chosen to experience this. if any of you guys can help me to get this phone rooted, i'd probably scream out of sheer ecstasy. and no, "try getting a girlfriend" who has windows isn't an answer.
[insert wojak here]
Hi!
It seems a driver issue
have you used already this tool in your pc successfully or is just a problem with your S5?
Reyse said:
Hi!
It seems a driver issue
have you used already this tool in your pc successfully or is just a problem with your S5?
Click to expand...
Click to collapse
i don't think that drivers are an issue; i have linux. do i need to use kies to install them under wine? it didn't work with wine 1.8 and kies3; i'm trying wine 1.9 right now.
thefailure said:
i don't think that drivers are an issue; i have linux. do i need to use kies to install them under wine? it didn't work with wine 1.8 and kies3; i'm trying wine 1.9 right now.
Click to expand...
Click to collapse
Did you debug (adb, fastboot) another phone already or is this your first one?
as i've posted on another forum here:
i know that it's a bit silly to create an entire thread for one guy's problem, but i am stuck and probably going to give up hope when it comes to rooting my s5 neo (again, g903f), which is running android 5.1.1.
several days worth of research have yielded nothing. i can connect to my device using mtp, and i have usb 2 and 3 ports. lsusb and adb are working for me; i have set udev rules and "adb devices" returns my phone's serial number and its status. usb debugging is enabled as is the oem unlock (though whenever i try to disable developer tools and put them on again, the gui messes itself up and it won't let me turn them off, even if i refuse to put in my device's password). that's the only success i've had.
fastboot isn't working; "fastboot devices" shows nothing and it hangs at "< waiting for device>" with other commands, such as "fastboot oem unlock". adb won't work in download mode, either - though this is expected. rebooting into download mode via adb doesn't fix my problem, nor does using "sudo" or the root account.
odin3 won't work either despite the window opening with wine; the device never shows up in download mode. heimdall also doesn't seem to detect my device - although it might just be down to my ignorance.
the usual root tools, such as srsroot and kingo don't seem to do any good, though neither worked under wine, which helps to diagnose the problem. i have no access to windows, even through vmware.
i feel like everything i do only brings me one step closer to a brick wall, which i'm hitting all the time. it's like i've been chosen to experience this. if any of you guys can help me to get this phone rooted, i'd probably scream out of sheer ecstasy. and no, "try getting a girlfriend" who has windows isn't an answer.
[insert wojak here]
Click to expand...
Click to collapse
new things: i know that usb support in wine is nonexistent, thus i need to know how to get wine to see my device if i need to use odin (with kies for the drivers). adb works only intermittently; it sometimes doesn't see my device. i'm not sure if i can use mac osx in a vm, either.
can i get samsung drivers for linux at all? or am i hopelessly screwed? all i wanna do is root, get twrp, get xposed and then work from there.
Hi!
I answered your previous thread, but now I understand your problem
I see you are trying with vmware
would you use virtualbox?
I'm very sorry if this problem has been raised and solved before or if this is the wrong place to ask this. My phone is currently on the b08 build and I was able to flash twrp 3.0.2-2 using this guide http://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 ([GUIDE] [A2017G] Install TWRP, Unlock BL, Flash Custom ROM) which has been very helpful but I just could not get past the 15th step when unlocking the bootloader. Whenever I type in "fastboot oem unlock", all I get is < waiting for any device > and nothing else. When i tried typing "fastboot devices" I get blank as well. I've tried using different usb ports, redoing all the steps for bootloader unlock part while my phone's in twrp, killing adb.exe while the < waiting for my device > line appeared but I couldn't get past the < waiting for any device > issue. This is actually the first time I've ever attempted a bootloader unlock on any device and I'm still a complete noob when it comes to this stuff so any help will be greatly appreciated!
ileikpi said:
I'm very sorry if this problem has been raised and solved before or if this is the wrong place to ask this. My phone is currently on the b08 build and I was able to flash twrp 3.0.2-2 using this guide http://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 ([GUIDE] [A2017G] Install TWRP, Unlock BL, Flash Custom ROM) which has been very helpful but I just could not get past the 15th step when unlocking the bootloader. Whenever I type in "fastboot oem unlock", all I get is < waiting for any device > and nothing else. When i tried typing "fastboot devices" I get blank as well. I've tried using different usb ports, redoing all the steps for bootloader unlock part while my phone's in twrp, killing adb.exe while the < waiting for my device > line appeared but I couldn't get past the < waiting for any device > issue. This is actually the first time I've ever attempted a bootloader unlock on any device and I'm still a complete noob when it comes to this stuff so any help will be greatly appreciated!
Click to expand...
Click to collapse
either you are not in bootloader mode on the phone or you need to fix your drivers.
This problem for me was that my phone was coming up as "android" instead of QUSB_BULK. So I used Zadig to show me all the drivers, right clicked on "Android", deleted that and the old QUSB_BULK driver, connected my phone again and then let Zadig install the missing driver again. This made my phone be seen as QUSB_BULK again and then unlocking bootloader worked for me.
I got stuck at that step as well, had to do a hard reboot, attempts at reinstalling the drivers only seemed to make it worse!
JP_93 said:
This problem for me was that my phone was coming up as "android" instead of QUSB_BULK. So I used Zadig to show me all the drivers, right clicked on "Android", deleted that and the old QUSB_BULK driver, connected my phone again and then let Zadig install the missing driver again. This made my phone be seen as QUSB_BULK again and then unlocking bootloader worked for me.
Click to expand...
Click to collapse
Thank you very much for replying to me on both threads. My phone also shows up as "Android" instead of QUSB_BULK in device manager when I reboot it into bootloader but I'm a bit confused about how you deleted "Android" and the old QUSB_BULK driver. Did you uninstall/disable "Android" in device manager or is there a way to do it in Zadig?
I tried uninstalling "Android" in device manager when in bootloader but I have no idea how to remove the old QUSB_BULK driver. I then unplugged my phone and plugged it back in but the driver Zadig installed still made it appear as "Android". Sorry, I'm still really new to all this!
ileikpi said:
Thank you very much for replying to me on both threads. My phone also shows up as "Android" instead of QUSB_BULK in device manager when I reboot it into bootloader but I'm a bit confused about how you deleted "Android" and the old QUSB_BULK driver. Did you uninstall/disable "Android" in device manager or is there a way to do it in Zadig?
I tried uninstalling "Android" in device manager when in bootloader but I have no idea how to remove the old QUSB_BULK driver. I then unplugged my phone and plugged it back in but the driver Zadig installed still made it appear as "Android". Sorry, I'm still really new to all this!
Click to expand...
Click to collapse
Sorry I don't have access to a pc atm but I'm sure I right clicked "Android" while using Zadig and it lets yoy uninstall the driver. Once that was done I unplugged my phone and plugged it back in and used Zadig to reinstall the driver for the axon. Then it showed up as QUSB_BULK again.
JP_93 said:
Sorry I don't have access to a pc atm but I'm sure I right clicked "Android" while using Zadig and it lets yoy uninstall the driver. Once that was done I unplugged my phone and plugged it back in and used Zadig to reinstall the driver for the axon. Then it showed up as QUSB_BULK again.
Click to expand...
Click to collapse
Zadig doesn't let me right click to uninstall drivers T-T. I tried reflashing twrp and redoing everything in the guide to make sure I didn't miss anything but I'm still stuck at < waiting for any device >. Unlocked bootloader seems so close yet so far... Thank you very much for your help thus far tho!
if you just connect the phone in MTP mode and you do "adb devices" is your phone showing?
Bucci83 said:
if you just connect the phone in MTP mode and you do "adb devices" is your phone showing?
Click to expand...
Click to collapse
Yep it does.
lafester said:
either you are not in bootloader mode on the phone or you need to fix your drivers.
Click to expand...
Click to collapse
I'm pretty sure I'm in bootloader. At this point I'm pretty sure my drivers are the issue but how do I fix them? When in bootloader mode, my phone just shows up as "Android" and Zadig did not help there. As I said, typing fastboot devices also show nothing. I'm probably the dumbest or the unluckiest person in here to be stuck at the same damn point for days...
ileikpi said:
I'm pretty sure I'm in bootloader. At this point I'm pretty sure my drivers are the issue but how do I fix them? When in bootloader mode, my phone just shows up as "Android" and Zadig did not help there. As I said, typing fastboot devices also show nothing. I'm probably the dumbest or the unluckiest person in here to be stuck at the same damn point for days...
Click to expand...
Click to collapse
have you tried re-installing the ZTE USB drivers?
I had some issues with the Zadig because it installed the Qualcomm drivers, but they weren't working correctly, I ended up downloading some other Qualcomm drivers and that did the trick...
Bucci83 said:
have you tried re-installing the ZTE USB drivers?
I had some issues with the Zadig because it installed the Qualcomm drivers, but they weren't working correctly, I ended up downloading some other Qualcomm drivers and that did the trick...
Click to expand...
Click to collapse
Ok I'll try that when I get home.
Sorry but may I ask if you remember what your phone was called in device manager when you rebooted it into bootloader? Was it "Android", some Qualcomm code (ie. QUSB_BULK), or ADB something? In @JP_93 and my cases, our phones were simply labelled as "Android" in device manager.
Unlocked using a different PC
Ok guys, I managed to unlock my phone using a friend's computer with no problems. The drivers in my own pc were definitely messed up and uninstalling and reinstalling them didn't work.
Thank you very much to everyone for your help and sorry if I blew this out of proportion!
Glad you got it to work!
Hello, a few weeks ago i got my OP 6t. Due to my positive experience from my previous phones (LG G3 and G5) and what i heard from OP i tried to flash twrp and planned to install magisk. I followed the instructions here on xda to unlock the bootloader, it got recognized as device in adb and i could reboot it into the bootloader, but then it didnt recognized it in fastboot, it looks like im missing some sort of drivers, because when im in fastboot in the win 10 device manager its called "android" with a yellow triangle, i tried multiple guides already, but i had no success. Its the unbranded version with 8 gigs and 128 gig. I can provide more info if needed. Help would be very appreciated.
Did you follow funkwizard's guide in the guides/news/discussion forum? It's stickied at the top.
Anyhow, if you followed the guide, he provides this link (https://drive.google.com/file/d/1L7EZGx5mgeQYXO19Vsp9FWu9GXhF45Qs/view?usp=drivesdk) for the OP6T drivers that need it be installed.
He then provides this link (https://drive.google.com/file/d/1-uWQn-oHu_ROuDVCzIyrExoRbsSBYTtU/view?usp=drivesdk) to update your ADB/fastboot to the latest version.
Complete both of those steps and your phone SHOULD be recognized in fastboot. Good luck.
I have read his complete thread and im still stuck with the same problem. I deinstalled all phone related driver and only installed the one from the thread, opened the command prompt via admin and under device manager is still the yellow triangle beside the android device. I tried to install the driver manually via the google universal driver, but windows never found any compatible drivers.
And just to be certain, do you have USB Debugging enabled in developer options?
Pain-N-Panic said:
And just to be certain, do you have USB Debugging enabled in developer options?
Click to expand...
Click to collapse
Yupp, but i have to say that i had to tap it four to five times until the confirmation window popped up.
I had this problem few hours ago, and this is W10 fault. For me solution was that:
instal drivers from guide,
enter fastboot mode,
remove phone from device manager and unistal drivers,
replug phone,
let windows find drivers automaticly when in fastboot mode.
And that's it, fasboot comands works now.
Bartuc666 said:
I had this problem few hours ago, and this is W10 fault. For me solution was that:
instal drivers from guide,
enter fastboot mode,
remove phone from device manager and unistal drivers,
replug phone,
let windows find drivers automaticly when in fastboot mode.
And that's it, fasboot comands works now.
Click to expand...
Click to collapse
Thanks for the try, but still no change.
lubal21 said:
Thanks for the try, but still no change.
Click to expand...
Click to collapse
forget all the other tips, install the Google USB drivers with the batch file by entering Y on every question. select install driver in the device manager by selecting manually install. in the list presented select on the left Google Inc and on the right the fastboot driver. finish setup and fastboot should work now
lubal21 said:
Hello, a few weeks ago i got my OP 6t. Due to my positive experience from my previous phones (LG G3 and G5) and what i heard from OP i tried to flash twrp and planned to install magisk. I followed the instructions here on xda to unlock the bootloader, it got recognized as device in adb and i could reboot it into the bootloader, but then it didnt recognized it in fastboot, it looks like im missing some sort of drivers, because when im in fastboot in the win 10 device manager its called "android" with a yellow triangle, i tried multiple guides already, but i had no success. Its the unbranded version with 8 gigs and 128 gig. I can provide more info if needed. Help would be very appreciated.
Click to expand...
Click to collapse
Probably this shall help:
How to Fix OnePlus Device not showing in Fastboot Mode
In this detailed guide, we will show you the steps to fix the OnePlus Device not showing in the Fastboot Mode on Windows 10 PC.
www.droidwin.com