Galaxy Tab S2 - ERROR: Failed to detect compatible download-mode device - Galaxy Tab S2 Q&A, Help & Troubleshooting

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...

Related

heimdall gives me 'failed to detect compatible device'

drivers installed fine but when I'm in heimdall and select the zimage, its give me an error 'failed to detect compatible device'. zimage is checked, connected the device (mounted and unmounted) and it doesn't recognize it. Any ideas on what the issue is?
SPH P100 sprint tab, win7 64b and winxp, stock, rooted with superoneclick.
Are you in download mode?
Also read having odin / heimdall drivers on same os might cause issues - havent tried myself.
yes, now I get a failed to access device error -12.
I take it you installed the samsung drivers first - i.e kies application. Then Yadig driver install.
If your on linux , then should be easier to get this working.
I use vista - and sometimes it does non work first time for some reason and after a couple attempts it works. vista for you.
got it thanks. for some reason I had to install the drivers again and went right into hiemdall and flashed fine. odd.

[Q] Can I use Heimdall with gtab 8.9?

I've managed to soft brick my Galaxy Tab 8.9 Wifi while installing CWM, see this thread
http://forum.xda-developers.com/showthread.php?t=1311924
So I should install stock ROM from Samsung, right? But I don't have access to any Windows machine so I can't run Odin. Can it be done with Heimdall? Anybody got experience with Heimdall on gtab 8.9?
Second question - exactly witch ROM should I choose? The thread mentioned above links to http://netfolder.in/folder.php?folder_id=VgnYQ90
and there's three choices for version 3.2. How do I know which one to choose?
not for the tab, sorry, but i have used both heimdall and odin on my captivate without an issue. seeing as it is a samsung device, it should be ok.
When I click on Detect Device button in Heimdall it just says 'Device deteced', nothing more and when I click on the Print PIT button it says
Initialising connection...
Detecting device...
ERROR: Failed to access the device. libusb error: -3
But that is perhaps expected for a soft bricked device in downloading mode?
Anything else I could do, besides flashing, to determine if this is going to work ok?
find a friend with a windows machine, might be your best bet
Well, the problem is that most of my friends also have Linux, or they run Windows in VirtualBox. And I tried running Odin in Windows in a VirtualBox and it doesn't work. Doesn't seem to detect the device.
install drivers
make sure your tab is in download mode then install drivers. If you are using it is in a folder named 'drivers' in the folder that you extracted heimdall to. It worked for me though on a windows machine

CAPTIVATE - Frozen on AT&T Boot, Unrecognized via USB, NO access to CWM - PLEASE HELP

CAPTIVATE - Frozen on AT&T Boot, Unrecognized via USB, NO access to CWM - PLEASE HELP
HI - I've been fighting this captivate for over 48 hours. Being very familiar with all this, and not doing this for the first time either, the fact that I can't get this resolved drives me insane as I have never been so mentally exhausted in being incapable of resolving a problem, thus seeking professional guidance from the Gods on mobile technology!
HERE IS THE SPIEL:
Device: Samsung Captivate i897 (Device is rooted)
Software: AOKP build.38
Kernel: IcyGlitch v14
CWM: Installed v.5-----
The Problem
Device stuck at AT&T Logo - Not Looping (just stuck)
Windows XP Professional SP3 (x86) with all recommended USB drivers will not detect device. Device Manager displays the phone as unknown, regardless of drivers & upon inputting it into a USB (2.0) windows displays a message "USB Device is not recognized".
Windows 7 Ultimate SP1 (x64) brings up identical message as that of Windows XP with all proper & recommended drivers with the phone recognized as "unknown"
Device boots into download mode via holding Vol.+/- and plugin in USB cable. Both Heimdall & Odin can't recognized the device when it's in UNKNOWN state by windows. Although all drivers are installed.
Purchased new Micro USB cable - NOTHING - that's testing all USB ports on all my systems.
The Story:
The device was working flawlessly being able to mount as mass storage on both my Windows 7 Ultimate SP1 (x64) & Windows XP Professional SP3 (x86) until i've upgraded to AOKP build #38. The upgrade was successful (2 months ago). 2 days ago, i decided to upgrade to AOKP build #40. The device was not recognized as mass storage but rather "Unknown Device" or "USB Device not Recognized" - although the phone was in full working condition (USB Debugging was enabled). After some reading, I realized that the AOKP build #38 has a bug where there was a problem with mounting & the camera was not functioning since it had no access to external_sd (a problem that was very irritating since the update, but i had no time to look into it until recently). I followed a similar tutorial (http://forum.xda-developers.com/showthread.php?t=1545801) which required the editing of the vold.fstab file with Root Explorer, resolving the issue of external_sd becoming accessible on the phone with camera working, however unable to mount and copy the new AOKP Build 40 ROM through Windows to flash via CWM.
At this point I booted into CWM via holding volume +/- & power button. Wiped everything, and loaded a backup I've done a # of months ago where everything was working perfectly. There was an error when it was "...loading data image" which is normal, so I did it again and the error persisted. On the second attempt, it again re-sent me primary CWM menu where i was intending to now load another backup. I accidentally clicked the restart button, having already cleaned the devlick cache, etc, including user data which brought me this NIGHTMARE of problems.
I will be forever grateful the the kind soul which will help me resolve this, as I am at a phase of taking this samsung captivate and throwing it against a wall.
I assume you can still access recovery? Try putting CM9 on the external SD with a card reader, and flashing that...
EDIT: Just saw you can't access CWM... Try recovery again... all three until ATT comes up, immediately let off power... Try multiple times... Leave the battery out, hold all three, have someone else insert it, and let off power at ATT... When going into download mode, leave the battery out, hook it up, hold boths vols, and insert the battery...
The Unknown device issue....
Uninstall your drivers... Here are drivers to manually install, they are 64bit... so try right clicking the Unknown device in device manager and doing a manual driver update...
OP,
See this thread... Captivate Connection Issues...
Sent from my SAMSUNG-SGH-I777 using xda premium
B-Naughty: Thank you. I have tried this & that no luck. Even loaded Linux Mint 13, however heimdall is being a !*&#@ in loading the firmware...Perhaps if you would know any (proper) packages for a Samsung Captivate i897 via heimdall id be grateful. I used heimdall-suite-1.3.2 command line & frontend. Will try again tomorrow. Although still haven't figured out whether or not it read the phone in Linux (it's a different world for me)
4-2ndtwin: My friend, thank you for the detailed link. I have been doing this for over 48 hours ... nothing. I'll give it another shot via Linux, if not i'll try Ubuntu. Truly am just confused out of my mind, never had this before.
PS: The phone's data is wiped & it's stuck at AT&T when loaded via power button. Booting into DOWNLOAD MODE isn't a problem. All combination to load into recovery, did not work. I mean...there must be a way! There always is...Any further ideas or should i simply through it out and buy a Galaxy SIII?
I897UCKK4 Stock, Wipe, with option to install Bootloaders, Param,and Repartition-Heimdall One-Click
And try all of your USB cords, I don't know what you bought, but a bad one, or a lot of times an aftermarket one won't work...
Edit:
I saw you can get into download mode. So my original post doesn't help much.
Have you tried installing the Andoid SDK and downloading the nexus drivers from there? Perhaps your device now thinks it is a nexus. It might be worth a shot.
^
+ 1
Yes... I second this ^
Sent from my SAMSUNG-SGH-I777 using xda premium
This happened to me and I just reflash the boot loader and reinstalled the same from to keep my data
Decrapitated Samsung
Thank you all for the support.
At this point I've installed SDK Manager w/Google USB revision 6, latest Java, all proper drivers...nothing. Tried all usbs on all systems.
Q: If the phone goes into download mode, is it not in a default state and must be detected? I have a samsung galaxy tab 10.1, detects immediately. Samsung YPS3 mp3 player detects immediately - Samsung Captivate however, nothing...
I set up a clean Windows 7 Ultimate x64bit (all june 2012 updates + .Net 4.0). Installed all usb drivers...same thing, UNKNOWN DEVICE - so the usb cable works...but now when you go and manually upgrade driver via device manager, it says that the best driver for the unknown device is already installed.
Anyone want's a free captivate lol...
At this point...I dont even know what to ask...since i've tried everything. I'll try to revisit Ubuntu & Linux later this evenings and report status!
Thanks for the I897UCKK4 Stock, Wipe, with option to install Bootloaders, Param,and Repartition-Heimdall One-Click link, i can't use it since the phone isn't detected by the application
I would say you need to uninstall any/all drivers for your captivate. This includes heimdall installed drivers. Make sure to uninstall the drivers for the "unknown" device also.
kScorpion said:
Thank you all for the support.
At this point I've installed SDK Manager w/Google USB revision 6, latest Java, all proper drivers...nothing. Tried all usbs on all systems.
Q: If the phone goes into download mode, is it not in a default state and must be detected? I have a samsung galaxy tab 10.1, detects immediately. Samsung YPS3 mp3 player detects immediately - Samsung Captivate however, nothing...
I set up a clean Windows 7 Ultimate x64bit (all june 2012 updates + .Net 4.0). Installed all usb drivers...same thing, UNKNOWN DEVICE - so the usb cable works...but now when you go and manually upgrade driver via device manager, it says that the best driver for the unknown device is already installed.
Anyone want's a free captivate lol...
At this point...I dont even know what to ask...since i've tried everything. I'll try to revisit Ubuntu & Linux later this evenings and report status!
Thanks for the I897UCKK4 Stock, Wipe, with option to install Bootloaders, Param,and Repartition-Heimdall One-Click link, i can't use it since the phone isn't detected by the application
Click to expand...
Click to collapse
Seems as though you have a hardware problem with the phone, or a s/w problem so messed up you're down to Unbrickable Mod
---------- Post added at 08:35 PM ---------- Previous post was at 08:34 PM ----------
Red_81 said:
I would say you need to uninstall any/all drivers for your captivate. This includes heimdall installed drivers. Make sure to uninstall the drivers for the "unknown" device also.
Click to expand...
Click to collapse
He had a fresh Windows install and install drivers...
Unbrickable MOD - wont be able to do this my self, would need an electric to look into it. I mean the phone isn't bricked, it accesses download mode i just have to get it to connect via usb to be read as a "samsung composite device" to flash the bootloader. As now, it would be stuck at the AT&T screen without giving access to CWM.
I have installed Ubuntu 12.04 - set up java 7 - loaded Heimdall One-Click stock rom provided above via java...tried all USB's phone not detected via DOWNLOAD MODE. Phone not detected at all!
This is just insane...If it's in DOWNLOAD MODE, it should be accessible, not the contrary. Ubuntu doesn't need usb drivers, should be plug&play...Both XP & Win7Ultimate at least recognized the phone as an unknown device. On Ubuntu it does nothing at all, as if it never was plugged in.
The microusb slot on the phone is not damaged / cable is stock, also have another one from Staples. The system w/XP is reading all devices on a plug&play basis and read the captivate before flawlessly. Same applies to the Asus P43 laptop, which read the device without hesitation on Win7 Ultimate x64. The Ubuntu is now on the laptop...tried connecting the Galaxy Tab 10.1 (Samsung) it recognized it immediately...with full access to files etc.
Last plea for Ideas...before i'll send this captivate to hell, to where the journey isn't captivating at all!
It sounds like you have a bad flash. You need jtag to fix this issue. Contact mobiletechvideos and Josh should be able to repair it for you. I think at this point you've tried every other option.
Sent from my SAMSUNG-SGH-I897 using xda premium
kScorpion said:
Thank you all for the support.
At this point I've installed SDK Manager w/Google USB revision 6, latest Java, all proper drivers...nothing. Tried all usbs on all systems.
Q: If the phone goes into download mode, is it not in a default state and must be detected? I have a samsung galaxy tab 10.1, detects immediately. Samsung YPS3 mp3 player detects immediately - Samsung Captivate however, nothing...
I set up a clean Windows 7 Ultimate x64bit (all june 2012 updates + .Net 4.0). Installed all usb drivers...same thing, UNKNOWN DEVICE - so the usb cable works...but now when you go and manually upgrade driver via device manager, it says that the best driver for the unknown device is already installed.
Anyone want's a free captivate lol...
At this point...I dont even know what to ask...since i've tried everything. I'll try to revisit Ubuntu & Linux later this evenings and report status!
Thanks for the I897UCKK4 Stock, Wipe, with option to install Bootloaders, Param,and Repartition-Heimdall One-Click link, i can't use it since the phone isn't detected by the application
Click to expand...
Click to collapse
did u try reverting back to stock using ODIN 1 Click Stock Firmware Installer? there's a tutorial on youtube by mobiletechvideos original post by connexion2005.
Samsung Captivate (ODIN 1 Click Stock Firmware Installer)
youtube.com/watch?v=UDtxnH4lFuk
I would like to have that free captivate thou :good:
Same Problem
i have the same prob and if i try to recovery mode (i.e. by pressing volume buttons and power button simultaneously)
i get following type of errors
"E:failed to mount /cache (Invalid argument)
E:Can't mount/cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log"
kindly sugeest some way out
I have done everything possible to get it connected and recognized by the PC & all is failing. I have tried to "manually" install the Samsung composite Device driver via "have disk method in Device Manager.
In XP:
I load device manager and than do the following:
Click Universal Serial Bus Controllers
Right click "unknown device" which is the captivate
Select Update Driver
Select Install from a list or specific location (Advanced)
Select Don't Search. I will choose the driver to install. (Click Next)
Select "Have Disk" with the (show compatible devices) checked
Browse to the directory of extracted 32bit Windows XP Drivers: SGH-i897_Captivate_USB_Drivers_5_02_0_2
Select "ssadadb2.inf" & click open
And than i get the msg saying:The specified location does not contain information about your hardware
...WTF... I mean really...
Windows 7 Ultimate:
Same procedure as above until you select have disk, pick a proper x64 driver provided by XDA - also tried the Universal_Naked_Driver_Beta_0.6 ...there was progress that got me very excited - the Phone was detected as: Samsung Android Composite Device. Was I happy...until i clicked next and got this msg:Samsung Android USB Composite Device - This device cannot start. (Code10)...
There must be a solution: I had the phone bricked when i first tried to change from stock rom, managed to load it in download mode, and it was detected fine on all systems via USB with the same accessories, worked like a charm...so when this happened i wasn't concerned, as i thought id follow standard procedure, accept it did not work.
Anyone?
Let's try this since you seem to be stuck in a boot loop.
Code:
adb wait-for-device reboot recovery
Make sure your phone is plugged in and reboot it. If your machine recognizes the phone at any point in the boot process it will kick it into recovery.
Once there you can try to restore the backup again.
If this doesn't work, you will most likely need JTAG service. Because of the bad image flash your device might not "think" it is a Captivate any longer and that's why the drivers aren't working.
Red_81 :Thank You. Would you please be more specific & put into a 1,2,3...process?
1. Power off device
2. Plug in to computer
3. Open a command prompt
4. Navigate to adb.exe (android sdk or inside my kk4 root utility)
5. Enter command above
6. Boot up phone.
7. Hopefully go into recovery
Sent from my SGH-I777 using xda premium
Thank you. I've been endlessly fighting the achievement of the PC systems to detect the captivate & no results. Thank you all for you help...when i have time i'll JTAG this device, or probably not even going to bother and pick up a SGIII. By the way Red_81:http://forum.xda-developers.com/showthread.php?t=1680048 is an amazing app, if only my phone was detected as it's recognized as unknown device, so there isn't much it can do. Although i highly recommend it to anyone else whose phone is detected.

Firmware upgrade encountered an error

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!

Problems Loading Recovery and Getting to Lineage, Using Heimdall Zadig

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

Categories

Resources