Like the OP of this thread
https://forum.xda-developers.com/tab-s2/help/trying-to-install-lineage-galaxy-tab-s2-t3769081
I am using the install instructions below, to (eventually) get to Lineage 15.1 on my Galaxy tab S2 8.0
https://wiki.lineageos.org/devices/gts210vewifi/install
Unfortunately, the drivers don't seem to load. I get an error, long before I get to load TWRP.
I've attached the list of devices I see in Zadig, and I'm using "Gadget Serial Control" .
I have MS Visual 2012 C++ and Minimal ADB and Fastboot on my laptop, though I'm not sure I actually need ADB and Fastboot, when using Heimdall.
I've also attached the log file.
Can anyone offer any guidance, on how to troubleshoot/proceed? Just received my device and eager to enjoy it.
Thanks very much!
NBUK
After looking around, I found Odin, and was able to get TWRP on my tablet. I was also able to load Lineage OS 15.1. \
All good now. Thanks for your support
NBUK
Related
There should be a [NOOB] tag for forum posts...
I'm a long time windows mobile user, rather than jump into windows phone I'm making the switch to Android.
I bought my captivate on eBay, it shipped unlocked with a clean gingerbread rom. Not sure which. After reading through a number of threads and articles I was able to:
Setup ADB - Win7 x64
ADB to download mode, Odin 1-click back to stock
Flash CWM, again via ADB to recovery, and then flash the latest MIUI
3br does not seem to be working for me. At first I was able to get to recovery with Vol up + Home + plug into USB. I can no longer get to recovery or download mode at all. MIUI, has the reboot to Download/Recovery mode options, but neither work and just boot back to the OS. When plugged into my computer, the device drivers are not recognized. So it no longer works with ADB. I haven't been able to get the drivers re-installed. When I attempt to ADB, it says "Error: No device connected" (or along that wording). I tried installing the USB drivers straight from Samsung and the galaxy S x64 drivers posted online. Not having any luck.
I can't seem to find my answer searching the threads and web...maybe I'm not using the right terms (I avoided making a new post as long as I could). Everything else works fine otherwise, the phone isn't bricked...but where's the recovery? Any ideas?
I'm assuming if I can get into download mode, then I can Odin-1-click to stock and everything is peachy again? I'm not quite understanding the 3BR fix guides...I thought since I could get to recovery with other methods when I got the phone, that I was fine, but maybe that's my problem.
The combo is all 3 buttons for recovery and both volumes and plug in a usb fire download. Sometimes odin one click will disable the combo.
As for adb not working miui is an aosp (android open source project) build not based on samsung firmware so you need the google drivers installed for it to work.
studacris said:
The combo is all 3 buttons for recovery and both volumes and plug in a usb fire download. Sometimes odin one click will disable the combo.
As for adb not working miui is an aosp (android open source project) build not based on samsung firmware so you need the google drivers installed for it to work.
Click to expand...
Click to collapse
It must have gotten disabled somehow then...
By Google drivers, you mean the USB package you can select from the Android SDK Manager? I didn't mention this but I think I tried those as well. But I'll remove everything I've installed, restart and try re-installing fresh to double-check.
Thanks for the suggestion, that worked with the drivers from the sdk. So if I end up flashing a touchwiz based rom, will I have to go back to the samsung drivers?
That's correct
I have latest Motorola drivers and Android SDK installed, so my PC itself should be up to date. However, whenever I select "install zip from sideload" my device is not recognized. It shows up as XT925 in my Device Manager with a yellow exclamation point. None of the ADB commands work because it says no device is found, and "adb devices" gives me a blank list. I have tried disabling, re-enabling, and uninstalling drivers (Of the "XT925" device in Device Manager) and rebooting into CWM and selecting the sideload option again, but when my PC is trying to download/install the XT925 drivers, it never finds proper drivers and I'm back to where I was. Trying to find drivers through the Device Manager leaves me with no results. Anything I can do to get my device recognized? When powered on or in fastboot mode, I have no issues executing any command or with device recognition. Thanks in advance!
By the way, the issue has persisted through Stock ROM flash in RSD Lite, HoloBlur-X PurePerformance ROM, and Carbon ROM v1.8
I have the same issue as well. I dont think we have a fix. I have heard universal adb driver might fix it, you might want to try it and see. It didnt work for me though.
Ahh, I see, so its a known issue. I guess I'll try those universal ADB drivers, not expecting anything though... Thanks
Edit: Wow! I installed the universal ADB drivers a few minutes ago and ADB is totally useable in CWM sideload mode! I can sideload files, send commands to reboot, etc etc. I dropped a thanks to you ai6908, thank you very much
I grabbed and installed them from here: http://www.droid-life.com/2013/04/08/koush-releases-universal-adb-driver-for-windows/
Being able to sideload ROMs is going to save me a lot of headaches later on...
Neighbor808 said:
Ahh, I see, so its a known issue. I guess I'll try those universal ADB drivers, not expecting anything though... Thanks
Edit: Wow! I installed the universal ADB drivers a few minutes ago and ADB is totally useable in CWM sideload mode! I can sideload files, send commands to reboot, etc etc. I dropped a thanks to you ai6908, thank you very much
I grabbed and installed them from here: http://www.droid-life.com/2013/04/08/koush-releases-universal-adb-driver-for-windows/
Being able to sideload ROMs is going to save me a lot of headaches later on...
Click to expand...
Click to collapse
You can also update to unofficial cwm 6.0.3.2. I find it faster and everything works
Sent from my PACman Atrix HD
I updated to 6.0.3.2 a few minutes ago, everything is going smooth, thanks guys
I was trying to flash Corn Kernel with Odin and it kept failing in download mode. So, after two hours or so, I had to pull the plug. It then went to the. ...../!\..... screen saying, "firmware upgrade encountered an error, please select recovery in kies and try again." However, kies hangs on connecting, and now I'm stuck with a paperweight.(
Ps, I have tried to use SDK and ADB, but to no avail. ADB comes back with no devices found.
Help!!!!
justgene53 said:
I was trying to flash Corn Kernel with Odin and it kept failing in download mode. So, after two hours or so, I had to pull the plug. It then went to the. ...../!\..... screen saying, "firmware upgrade encountered an error, please select recovery in kies and try again." However, kies hangs on connecting, and now I'm stuck with a paperweight.(
Ps, I have tried to use SDK and ADB, but to no avail. ADB comes back with no devices found.
Help!!!!
Click to expand...
Click to collapse
IIRC, Kies can cause a conflict with the drivers when trying to use other methods. You may need to un-install Kies and then reinstall the drivers before adb will work.
The ......../!\........ screen will function as a download mode, from here. I have had my phone in this condition before and was able to use heimdall to flash a rom.
dawgdoc said:
IIRC, Kies can cause a conflict with the drivers when trying to use other methods. You may need to un-install Kies and then reinstall the drivers before adb will work.
The ......../!\........ screen will function as a download mode, from here. I have had my phone in this condition before and was able to use heimdall to flash a rom.
Click to expand...
Click to collapse
Thank you for your reply, however, attempting to use download and open the setup in the captivate drivers results in an error.
It specifically says, SAMSUNG Android USB Modem Software was not installed successfully
(9). All I can do is click OK. I tried again, but no luck.
justgene53 said:
Thank you for your reply, however, attempting to use download and open the setup in the captivate drivers results in an error.
It specifically says, SAMSUNG Android USB Modem Software was not installed successfully
(9). All I can do is click OK. I tried again, but no luck.
Click to expand...
Click to collapse
I'm very fuzzy about driver issues with Windows. It has been years since I last dual booted my laptop and had the ability to use Odin. Linux handles drivers differently, Odin and Kies do not work on Linux, therefore I have been using Heimdall in place of Odin and the only "issue" I have is that it is simpler to always use the same usb port on the laptop.
Ima newbie, what's Linux? I keep hearing that word thrown around.
justgene53 said:
Ima newbie, what's Linux? I keep hearing that word thrown around.
Click to expand...
Click to collapse
It's a computer operating system based on Unix. Development began on it in the early '90s. Android uses the Linux kernel at the very core. The kernel is the interface between software and hardware.
Linux is used in lieu of Windows or Mac OS. Like Android, it is very open to user customizations.
Heimdall is the open source equivalent of Odin. It works on Linux, Windows, or Mac.
Ohmg I had no idea what you meant when you said" dual booted" now I realize that Linux is not another computer COMPANY completely, it's just a kernel! Ha, I'll have to add that to my list of ways of how Windows is similar to android.
I'm jumping right on that verry soon.
Also, I've tried to use a program that claims that 13 of my drivers were outdated, however, I updated that, however that did not fix the issue. As I said, the download posted didn't work so I have ran into another wall.
Gah!
dawgdoc said:
It's a computer operating system based on Unix. Development began on it in the early '90s. Android uses the Linux kernel at the very core. The kernel is the interface between software and hardware.
Linux is used in lieu of Windows or Mac OS. Like Android, it is very open to user customizations.
Heimdall is the open source equivalent of Odin. It works on Linux, Windows, or Mac.
Click to expand...
Click to collapse
Thanks alot for your help because i would still b scratching my head about Linux and the triangle screen error.
Eventually, i tried it on my more recent laptop and used a more recent version on Odin, and boom! it worked flawlessly.
Now ready to install omnirom and eventually, Linux! :good:
justgene53 said:
Thanks alot for your help because i would still b scratching my head about Linux and the triangle screen error.
Eventually, i tried it on my more recent laptop and used a more recent version on Odin, and boom! it worked flawlessly.
Now ready to install omnirom and eventually, Linux! :good:
Click to expand...
Click to collapse
Glad to hear you have it working. Drive on!
Hello,
after checking the device list of lineage, I have bought a Samsung Galaxy Tab S2 tablet.
For installation I have read the lineage instruction, downloaded the required SW for Win and started on a Win 10 device. With zadiag I have somehow selected the wrong usb port (?) and now my keyboard is not working anymore. So I changed to Linux (debian stretch) and was also not successful.
Following the instructions - Heimdall (1.4.0 and 1.4.1) always comes back with:
ERROR: Failed to detect compatible download-mode device
Also adb was not recognizing the tablet and the frontend (heimdall 1.4.0) - of course - gave me the same feedback.
Any idea or link that heimdall will detect the tablet?
Thanks
Martin
PS and if you have an idea how I can fix my win pc - that would be great also
martinforum said:
Hello,
after checking the device list of lineage, I have bought a Samsung Galaxy Tab S2 tablet.
For installation I have read the lineage instruction, downloaded the required SW for Win and started on a Win 10 device. With zadiag I have somehow selected the wrong usb port (?) and now my keyboard is not working anymore. So I changed to Linux (debian stretch) and was also not successful.
Following the instructions - Heimdall (1.4.0 and 1.4.1) always comes back with:
ERROR: Failed to detect compatible download-mode device
Also adb was not recognizing the tablet and the frontend (heimdall 1.4.0) - of course - gave me the same feedback.
Any idea or link that heimdall will detect the tablet?
Thanks
Martin
PS and if you have an idea how I can fix my win pc - that would be great also
Click to expand...
Click to collapse
You need heimdall 1.4.2
Deltadroid said:
You need heimdall 1.4.2
Click to expand...
Click to collapse
ok - found heimdall 1.4.2 only for win but my win is broken... so first fix win and then test 1.4.2
martinforum said:
ok - found heimdall 1.4.2 only for win but my win is broken... so first fix win and then test 1.4.2
Click to expand...
Click to collapse
My guide here, walks you through the Linux method and links to a working .deb file of heimdall.
Your other option, see my post here, another user has posted instructions on using Odin, which works in Windows. (I have not tested or used this method)
That helps a lot - thank you, i will try the linux way first
Finally this weekend I found the time to test the linux way.
To make a long story short- it was working.
Thank you!
What I did:
With Mint I was successful installing TWRP.
Afterwards with adb I could follow the standard approach.
Only su is not working but I will find out why...
I recently had these issues with Windows not having the correct drivers even after installing the oneplus drivers
Since I could not easily find these solutions I thought I should share them here so that it may be easier to find for anyone who needs it
The first problem is OnePlus 6T not showing in MSM Tool and showing in device manager as QUSB_BULK_CID:xxxx_SN:xxxxxxxx
The solution I found here https://forum.xda-developers.com/t/guide-unlock-verizon-oneplus-8-5g-uw-in2019-bootloader.4409377/
is this :
Enter EDL mode with adb reboot edl or by powering the phone off and holding both volume up and down while connecting it to a PC
Next Open device manager and if you see "QUSB_BULK_CID:xxxx_SN:xxxxxxxx"
try to update the driver, it will not find one but choose the option to search Windows Update
It should open your settings to the Windows update page
You can open this manually and you should see the option to View Optional Updates
select “Qualcomm Incorporated - Ports - 3/25/2016 12:00:00 AM - 2.1.2.2” and install it.
This should install the correct driver, replacing “QUSB_BULK_CID:xxxx_SN:xxxxxxxx” with "Qualcomm HS-USB QDLoader 9008" in device manager
After this I thought I had solved my problems but then the OP6T was not showing in fastboot
I eventually found my solution here https://forum.xda-developers.com/t/...ng-up-in-fastboot-mode-windows-10-11.4194491/
The issue is because of OnePlus having unsigned drivers and windows refusing to use them unless you disable driver signature enforcement
I recommend following the linked guide for this problem as the solution is identical for the 6T as well as the 8T, I couldn't write it any better and I wouldn't want to just copy their guide
But it essentially is as simple as disable driver signature enforcement and install the correct drivers with device manager so your device will show in fastboot
FireRattus said:
I recently had these issues with Windows not having the correct drivers even after installing the oneplus drivers
Since I could not easily find these solutions I thought I should share them here so that it may be easier to find for anyone who needs it
The first problem is OnePlus 6T not showing in MSM Tool and showing in device manager as QUSB_BULK_CID:xxxx_SN:xxxxxxxx
The solution I found here https://forum.xda-developers.com/t/guide-unlock-verizon-oneplus-8-5g-uw-in2019-bootloader.4409377/
is this :
Enter EDL mode with adb reboot edl or by powering the phone off and holding both volume up and down while connecting it to a PC
Next Open device manager and if you see "QUSB_BULK_CID:xxxx_SN:xxxxxxxx"
try to update the driver, it will not find one but choose the option to search Windows Update
It should open your settings to the Windows update page
You can open this manually and you should see the option to View Optional Updates
select “Qualcomm Incorporated - Ports - 3/25/2016 12:00:00 AM - 2.1.2.2” and install it.
This should install the correct driver, replacing “QUSB_BULK_CID:xxxx_SN:xxxxxxxx” with "Qualcomm HS-USB QDLoader 9008" in device manager
After this I thought I had solved my problems but then the OP6T was not showing in fastboot
I eventually found my solution here https://forum.xda-developers.com/t/...ng-up-in-fastboot-mode-windows-10-11.4194491/
The issue is because of OnePlus having unsigned drivers and windows refusing to use them unless you disable driver signature enforcement
I recommend following the linked guide for this problem as the solution is identical for the 6T as well as the 8T, I couldn't write it any better and I wouldn't want to just copy their guide
But it essentially is as simple as disable driver signature enforcement and install the correct drivers with device manager so your device will show in fastboot
Click to expand...
Click to collapse
Per chance, would you know if this would also apply to the OnePlus One on Linux? I recently tried to gain root access but no matter what I did, I could not get the device to show up in fastboot or as an ADB device, for that matter. I tried both USB 2.0 ports and 3.0 ports, to no avail. It's obviously not my daily driver (based on release dates, etc.) so it's not a big deal but at the same time, I don't want to root my daily driver as it has enough trouble on stock OS as it is (Google Pixel 6 Pro). I don't need to go rooting it and introducing a whole new world of hurt, thus, the desire to root my recently resuscitated OnePlus One (I got it stuck in a boot loop one or maybe even two years ago but it wasn't my daily driver then, either and just kind of a tinker device, one of a couple at that. So rather than put in the minimal amount of effort to fix it, I just tossed in a drawer until a future need demanded that I give it the time and attention necessary, which happened to occur the other night. All went super smoothly until I hit this particular roadblock alluded to above while trying to gain root using Bacon Root Toolkit. Admittedly, I haven't tried going the old-fashioned route of gaining root but mostly because I couldn't get my computer to recognize that the device was connected to it, so that was no more an option than was going the easy route with BRT.)
Edited to mention that I successfully got it out of the boot loop by flashing cm12 and that booted up no problem. I also have TWRP installed, which actually may need updating as it was the version originally installed however many years ago prior to getting it stuck in the boot loop and subsequently getting the junk drawer treatment for 1-2 years but to my knowledge that would not cause the device to not be recognized as a fastboot/ADB device...
QneEyedJack said:
Per chance, would you know if this would also apply to the OnePlus One on Linux? I recently tried to gain root access but no matter what I did, I could not get the device to show up in fastboot or as an ADB device, for that matter. I tried both USB 2.0 ports and 3.0 ports, to no avail.
Click to expand...
Click to collapse
I am not exactly sure about this but I recommend you try what is suggested here if you haven't https://technastic.com/oneplus-usb-drivers-windows-mac-linux/
sudo apt-get install android-tools-adb android-tools-fastboot
QneEyedJack said:
Edited to mention that I successfully got it out of the boot loop by flashing cm12 and that booted up no problem. I also have TWRP installed, which actually may need updating as it was the version originally installed however many years ago prior to getting it stuck in the boot loop and subsequently getting the junk drawer treatment for 1-2 years but to my knowledge that would not cause the device to not be recognized as a fastboot/ADB device...
Click to expand...
Click to collapse
to my knowledge the recovery you have installed should not effect your device being recognized in fastboot mode
You should probably update your recovery to the latest official twrp imo