Hi,
I am trying to install CM7 using Heimdall on my Galaxy tab P1000
But just after clicking Start i get ERROR: Failed to access device. libusb error: -12
In the Heimdal folder there's a README and a drivers folder.
Read the README. There's instructions.
Run the executable in the Drivers folder. From one of the menu's select all devices and you should see an option for samsung composite device. Click Install Driver.
If you're on Win7, there's instructions in the README to go through the device manager and change the drivers that your device is using to connect. Do this then try to flash it again. It should detect your device now.
Thanks that helps too much , installed CM 7 on my tab
Related
I follow the how to on android centrals forums, I've downloaded the usbdrivers and extracted properly. But windows vista gives me this error.
"WINDOWS FOUND DRIVER SOFTWARE FOR YOUR DEVICE BUT ENCOUNTERED AN ERROR WHILE ATTEMPTING TO INSTALL IT. ANDROID COMPOSITE ADB INTERFACE. THE DEVICE DOES NOT RECOGNIZE THE COMMAND."
All I'm trying to do is get GApps running
Sent from my Nexus One using XDA App
Try this thread: http://forum.xda-developers.com/showthread.php?t=882751
It comes with a script to run that will automatically install the adb/nook color drivers. The win7 one *should* work for vista.
Good-luck
where can i install CDC Serial & SAMSUNG_Android drives?
weiverpool said:
where can i install CDC Serial & SAMSUNG_Android drives?
Click to expand...
Click to collapse
You just need to install Samsung KIES dude.
i try to download kies already but kies doesn't work on my pc.(can't open the kies after installed).Is there any different version or.........
weiverpool said:
i try to download kies already but kies doesn't work on my pc.(can't open the kies after installed).Is there any different version or.........
Click to expand...
Click to collapse
Here is where I got it from http://www.samsungapps.com/about/onPc.as
If you're running Vista or Windows 7 and are unsure whether you have UAC switch on or not, right click the file you downloaded from the website and choose "Run as Administrator" from the drop down list and see if that makes a difference.
You can find the galaxy note drivers on the US Samsung site (and only this one). I unfortunately cannot post the direct link as this is my first post...
If, like me, your Galaxy Note is not recognized by your PC with a "driver not found" message, try to look in your device manager.
I had for some reason a Bluetooth device that was not correctly recognized (yellow "!"). I uninstalled the Bluetooth device (which I never used anyway) and suprisingly when I plugged my Galaxy Note back it was perfectly recognized this time.
Hope this helps!
get it from here
32bit
64bit
problem with the latest samsung kies
its all problem with the latest samsung kies. I think I was using Kies_2.3.2.12064_10_1.exe
With latest samung kies, the drivers are not getting installed properly.
Steps to correct this problem
1) Uninstall samsung kies
2) Reboot system
3) Install an old version of kies - I used Kies_2.1.1.11124_17_6
4) Connect your S2
5) Old kies will install the drivers properly for your s2
6) Now with the mobile connected, update kies from kies itself.
All works after that.
usb cdc mod hatası
*#0808# tuşuna bas ac ap mtp atp kaydet sn makina bukadar da arıza yap
path for driver installation
after installation, samsung_android drivers window opens .
now guide me to select the correct path which will install drivers correctly.
kindly do reply asap
patel_gsm82 said:
after installation, samsung_android drivers window opens .
now guide me to select the correct path which will install drivers correctly.
kindly do reply asap
Click to expand...
Click to collapse
http://developer.samsung.com/android/tools-sdks/Samsung-Andorid-USB-Driver-for-Windows
I'm running AOKP m6 with the default Glitch kernel v14. The problem I'm was having is no adb over USB.
My PC is running Windows 7 64-bit.
The problem lies in the device showing in Device Manager as "SGH-I897" instead of one of the more common identifiers (which obviously were used by other kernels and/or ROMs as other ones worked fine).
NOTE: unless you NEED adb over USB for something, it will probably just be easier for you to use adb over WIFI. The following isn't super-hard but if adb over WIFI works for you ... use it.
What I attempted to do to fix before doing the workaround (add "tested adb: FAIL" to each step below) ... try these, they may work in your case:
Updated to latest Android SDK, rebooted
"Uninstalled" device in Windows
Tried to "Update Driver Software" using Android SDK USB driver ... error: "Windows could not find driver software for your device"
Tried to "Update Driver Software" using Samsung Kies USB driver ... same error.
(over WIFI adb) ran `setprop persist.sys.usb.config mass_storage,adb` ... no luck, Mass Storage worked before and after, no adb
WORKAROUND:
Summary: you need to add your device string to the USB driver INF file. The following ATTEMPTS to be a full step-by-step to show those who haven't done this before what to do.
Go to your android-sdk folder (assuming you have installed the SDK -and- included the USB drivers ... if not ... that's your first step)
Open %ANDROID-SDK%\usb_driver\android_winusb.inf in your favorite text editor
add the following lines to BOTH sections [Google.NTx86] and [Google.NTamd64]
;Samsung Captivate with Glitch kernel
SGH-I897 = USB_Install, USB\VID_18D1&PID_4E22&REV_0231&MI_01
For OTHER phones with this same problem (skip if you are using a Captivate)
NOTE: For other phones or other ROMs ... try the steps I outline at the end of this post to see if they work BEFORE you hack the driver file. You may not have the same problem I've had here.
You will need to change the lines you add to the file above. To find the right string to add to your inf file:
find your Android device in Device Manager, it SHOULD have a yellow "disabled" triangle icon and is probably under "Other Devices".
right-click the entry for your phone and select "Properties"
go to the "Details" tab
change the "Property" from "Device Description" to "Hardware Ids"
right-click and "Copy" the first entry (should look similar to USB\VID_18D1&PID_4E22&REV_0231&MI_01)
Replace USB\VID_18D1&PID_4E22&REV_0231&MI_01 from my lines above with the value you copied in the previous step
Replace ;Samsung Captivate with Glitch kernel in my lines above with something that describes your device. KEEP the semi-colon at the front of the line.
find your Android device in Device Manager
right-click it and select "Uninstall"
(IF your computer tells you to reboot at this point ... yeah ... you gotta ... so just come back here when done and make sure you've done the "Uninstall" step)
in Device Manager, do "Action" > "Scan"
find your Android device again, this time likely under "Other devices"
right-click the device in Device Manager and select "Update Driver Software"
"Browse my computer for driver software"
click the "Browse" button and find %ANDROID-SDK%\usb_driver\
click "Next"
if it tells you it can't find a driver for your device, SOMETHING above went wrong OR this workaround can't solve your problem
if it tells you "Windows can't verify the publisher of this software" ... select ... "Install this driver software anyway"
you're basically done. Verify it worked by trying the command `adb devices`. Your device should now appear.
NOTES:
If you have this problem, both Recovery mode and normal mode will be unable to connect adb via USB
adb works over WiFi, but I have some scripts that are expecting a USB connection and don't behave well without USB connection for sensing when the device has rebooted
I had adb over USB running on the same phone using Doc's ICS, Stock 2.2 and Stock 2.3
adb recovery mode on my phone works with Corn kernel, so I really think this is an issue with Glitch kernel rather than AOKP
Hi mates,
i crashed my GT-P1000.
Installed CWM via Heimdall and tried to flash to Paranoid 2.20.
Now I cant install anything because of "Status 7".
The only package which was possible to install was MiUi.
No WiFi, no GSM, etc. - thats why I think i must have touched the radio-partition
I can control the tab via adb, but odin and all those tools dont recognize the Tab (Just Samsung Composite Device). So no flashing via Odin.
Anybody here can tell me how to get the radio partition back?
Thanks a lot and all the best!
Jan
There is no radio partition on MTD based ROM.
it is just /radio/
Which ROM did you flash, maybe can find out if it is BML or MTD.
But WiFi isn't radio dependent.
Remove your sim card in case you have the WiFi channel / middle eastern tab WiFi issue.
your best bet is still to restock
Sent from my GT-P1000 using xda app-developers app
WilhelmDerTell said:
I can control the tab via adb, but odin and all those tools dont recognize the Tab (Just Samsung Composite Device). So no flashing via Odin.
Click to expand...
Click to collapse
priyana said:
your best bet is still to restock
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
As Priyana said it is not related to radio partition... are you sure you have p1000 tab.
Error status 7 occur when flashing noncompatible ROM.
Sent from my GT-P1000
Its definetly P1000.
I used a howto to install CWM.
Technomancer’s Kernel with ClockworkMod Recovery 5 (cwm-5-p1.tar, 5 MB, md5sum: e67e61a27741069e43bf9f790bf35b10)
Heimdall Suite 1.3.2 (heimdall-suite-1.3.2-win32-.zip, 9.6 MB)
Instructions
1. Extract the contents of Heimdall Suite 1.3.2 to obtain a folder named Heimdall Suite. Drivers and the Heimdall Suite application are found inside the folder.
2. Connect the other end of the USB cable to the computer. Do not connect the tablet just yet.
3. Switch off your tablet.
4. Reboot the tablet into Download Mode. To do this, press and hold the Power and Volume Down buttons as you connect the other end of the USB cable to your tablet.
5. On your PC, double-click the zadig.exe file found in the Heimdall Suite folder. This tool allows you to easily install the USB drivers needed for Heimdall to be able to communicate with your tablet.
6. Select Options and choose List All Devices from the menu. You will see a drop-down list.
7. From the drop-down list, select either Samsung USB Composite Device or Gadget Serial and choose Install Driver. After this, Heimdall can now be safely used on your computer.
NOTE: A prompt may appear saying that the installer is unable to verify the publisher of the driver. If this happens, select “Install this driver anyway.”
8. After installation of the drivers, unplug your tablet from the USB cable.
9. Turn your tablet off.
10. Reboot the tablet into Download Mode again (as in step 4).
11. Untar Technomancer’s Kernel. You will be getting a file named zImage. Copy the zImage file into the Heimdall Suite folder. The file should be inside the same folder as heimdall.exe.
12. On your PC, open a command prompt. Change directory to where heimdall.exe is located.
13. Enter the following at the command prompt:
heimdall flash --kernel zImage
14. The command above instructs Heimdall to flash the kernel to your tablet. You will see a blue progress indicator displayed on your tablet’s screen.
15. After flashing of the kernel is done, your tablet will boot automatically.
Click to expand...
Click to collapse
Step 15 didnt work
The Tab didnt boot anymore.
So I asked a friend to have a look at it.
First there was the problem that the tab seemed not to know "who" it was.
"assert failed: getprop(“ro.product.device”)..."
We tried several ROMs.
The only one which worked was the MiUi. But nor I can enable WiFi neither it recognizes my SIM Card.
Even without the SIM I cant enable WiFi.
I dont know how to restock, without being able to install any ROM because of status 7.
So far thanks for your effort!
If you are REALLY sure you have the right version of a ROM for your type of Tab, you can do the following. ROM's which can be flashed from the Recovery are zips with files and folders. One of these files, META-INF/com/google/android/updater-script, checks first of all if the Tab is the right type. It seems this check can fail even though the Tab is OK. In this case you can just remove the first two lines with the assert statement. Be careful, because the ROM doesn't have the type sanity check anymore! It should flash now.
The best way to do this is not to unzip the zip into a folder, edit the file, and rezip the folder, but to open the zip, edit the file, and update the zip. You'll have to use an editor that respects UNIX end-of-lines (line feed), and not replaces them with DOS end-of-lines (carriage return/line feed). Notepad++ will do that, but there are others as well.
Sorry, it might have been a bit incomprehensible.
The problem isnt "assert failed: getprop(“ro.product.device”)..." anymore.
Ive got the problem that i cant install anything because of "status 7".
Restock to overcome method.
Follow my signature. Even a p1000l/n will become p1000 assert wise.
Sent from my GT-P1000 using xda app-developers app
Its done
I dont know why Odin didnt recognize the Tab before, but with these tools it does.
Thanks a lot Priyana, you absolutely made my day!!
pls close this thread
Need help can't connect with Odin because of zadig driver replacement.
I just replace driver of my Galaxy S with zadig.exe refer from wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd
Now, I want to connect with Odin but don't know how to rollback to sscdbus on my phone:crying:
solved: by Heimdall with darkyrom 10.2
gostyx said:
Need help can't connect with Odin because of zadig driver replacement.
I just replace driver of my Galaxy S with zadig.exe refer from wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd
Now, I want to connect with Odin but don't know how to rollback to sscdbus on my phone:crying:
solved: by Heimdall with darkyrom 10.2
Click to expand...
Click to collapse
You can fix this by removing the driver installed by zadig from the Control Panel.
Disconnect your device from the computer and do the following:
1. Open command prompt
2. type "set devmgr_show_nonpresent_devices=1". This will allow Device Manager to show installed devices even if they are not connected.
3. type "devmgmt.msc" . This will open up Device Manager
4. Click View > Show Hidden Devices
5. Check under libusbk or libusb0 (depending on what you did in zadig)
6. Right click and uninstall your device (if the device was in Download Mode when you replaced the driver e.g. for heimdall, then look for MSM****)
7. Close Device Manager.
Reconnect your device; Windows should automatically detect the "new" device and install proper drivers for it.