Well, I spent the last week or so having all sorts of creative fun with my new Captivate. Unfortunately, I was having the random shutdown issue, so I decided to remove SRE, SU, etc, using ODIN to restore my phone back to stock and get it exchanged for a new one.
I came home with my new phone today and proceeded to start the customization process all over. Before I did anything serious, I connected my new Captivate to my desktop, to both charge the battery and to sync with outlook using Kies.
With a full battery and my contacts loaded, I moved on the rooting and installing SRE. I then installed a bunch of apps, including ADW, ShopSavvy, and a bunch of games.
I then tried to get on the Market to download a few more apps. I forgot to 'emulate' T-Mobile to get around the AT&T censorship, so I fired up MarketAccess. I got an error message saying that MarketAccess couldn't get SU privs. That made no sense, since the phone was rooted, and SRE installed SuperUser. I downloaded the latest copy of Superuser and installed that. The SU problem was now fixed. (Turns out there was a glitch in the SRE I used. Designgears quickly fixed the zip file, but I was already using the glitchy one.)
Anyway, after loading a slew of apps/games, I plugged the phone back into the desktop to charge the battery some more. I got two error messages, one on the phone, and one on the desktop.
The phone complained that it was not on an 'idle' screen, since ADW was running. Since I had set ADW to be the default launcher, I used TitaniumBackup to temporarily uninstall ADW. (I couldn't figure out how to stop ADW and set TW back to the default.)
The desktop is more or a serious problem. I am now getting an info bubble saying that the USB DEVICE IS NOT RECOGNIZED.
The correct USB drivers are installed. I've used them to ODIN my previous phone back to stock. And they were working fine before I added SRE, ADW, etc.
I've uninstalled and reinstalled the drivers. Didn't help.
I tried USB Debugging, on and off. Didn't help.
I tried the age-old trick of unplugging the desktop and leaving it unplugged for 30 minutes. Didn't help.
So, here are my questions:
1) Does anyone know how to correct the DEVICE NOT RECOGNIZED error?
2) If not, is there anyway for me to restore the phone to stock without USB connectivity?
The phone still functions fine, just no USB. I was able to download the new SRE (with SuperUser fixed) using Dolphin browser. I then used My Files to rename and move the zip file to the root directory, and was able to install it fine. Is this same approach possible to restore to stock?
Thanks in advance...
Uninstall the usb drivers. Not sure what there called when kies installs it
fivebraids said:
Well, I spent the last week or so having all sorts of creative fun with my new Captivate. Unfortunately, I was having the random shutdown issue, so I decided to remove SRE, SU, etc, using ODIN to restore my phone back to stock and get it exchanged for a new one.
I came home with my new phone today and proceeded to start the customization process all over. Before I did anything serious, I connected my new Captivate to my desktop, to both charge the battery and to sync with outlook using Kies.
With a full battery and my contacts loaded, I moved on the rooting and installing SRE. I then installed a bunch of apps, including ADW, ShopSavvy, and a bunch of games.
I then tried to get on the Market to download a few more apps. I forgot to 'emulate' T-Mobile to get around the AT&T censorship, so I fired up MarketAccess. I got an error message saying that MarketAccess couldn't get SU privs. That made no sense, since the phone was rooted, and SRE installed SuperUser. I downloaded the latest copy of Superuser and installed that. The SU problem was now fixed. (Turns out there was a glitch in the SRE I used. Designgears quickly fixed the zip file, but I was already using the glitchy one.)
Anyway, after loading a slew of apps/games, I plugged the phone back into the desktop to charge the battery some more. I got two error messages, one on the phone, and one on the desktop.
The phone complained that it was not on an 'idle' screen, since ADW was running. Since I had set ADW to be the default launcher, I used TitaniumBackup to temporarily uninstall ADW. (I couldn't figure out how to stop ADW and set TW back to the default.)
The desktop is more or a serious problem. I am now getting an info bubble saying that the USB DEVICE IS NOT RECOGNIZED.
The correct USB drivers are installed. I've used them to ODIN my previous phone back to stock. And they were working fine before I added SRE, ADW, etc.
I've uninstalled and reinstalled the drivers. Didn't help.
I tried USB Debugging, on and off. Didn't help.
I tried the age-old trick of unplugging the desktop and leaving it unplugged for 30 minutes. Didn't help.
So, here are my questions:
1) Does anyone know how to correct the DEVICE NOT RECOGNIZED error?
2) If not, is there anyway for me to restore the phone to stock without USB connectivity?
The phone still functions fine, just no USB. I was able to download the new SRE (with SuperUser fixed) using Dolphin browser. I then used My Files to rename and move the zip file to the root directory, and was able to install it fine. Is this same approach possible to restore to stock?
Thanks in advance...
Click to expand...
Click to collapse
I had a similar problem and it turn out that Kies hosed up all my drivers...The only way I got it fix was by totally removing any trace of Kies and then uninstalled all my samsung drivers and usb drivers and then rebooted my pc. Then I reinstalled the samsung drivers and win 7 did the rest...
Well, I haven't uninstalled Kies yet. Although I have uninstalled and reinstalled the drivers from the ODIN thread. No difference.
I even uninstalled the ODIN referred drivers and tried the drivers directly from the Samsung site. Still no difference.
I'll go ahead and try uninstalling Kies and then the ODIN drivers, reinstall the ODIN drivers and see if that helps.
I've also ordered a new cable, since I've read a few threads on other forums where the problem was bad cables. I was going to go to AT&T and get a new cable, but they want $24.99. I just ordered a pair from Amazon at $3.99 each, with free shipping!!
Thanks...off to try ridding myself of Kies...
Well, deleting Kies (and associated drivers) didn't help!
After deleting Kies, I tried both the ODIN referenced drivers, as well as those from the Samsung site. Still not working!
I guess I'll wait on a new cable and see if that helps...
Okay, I think I'm in BIG TROUBLE here!!!
New cables arrived today, but they made no difference at all! Still getting the USB Device Not Recognized message. Doesn't matter if I plug the cable in while the phone is on and select any of the connection options (Kies, Mass Storage, etc.). It gives me the same message when I have Odin running and plug the phone in while holding the volume keys.
To further add to the problem, I tried installing the Odin referenced USB drivers on my wife's laptop which has never seen this phone or Kies. SAME PROBLEM!
I'm thinking there might actually be something wrong with the physical port on the phone. But this highlights my actual problem...
How can I return the phone (for the second time) when this phone has been rooted and is running SRE 1.2.1a ?!?!?
Apparently, there's no way for me to restore this thing to stock without USB.
Any ideas/suggestions?
Relax dude--I just got a captivate a few weeks ago, and have it working on tmobile.
For the drivers, when you plug your phone in, you're getting some errors. I know you uninstalled the drivers, but to double-check, open up device manager and see if there are any ! marks for the phone. Right-click and uninstall the entries. Also, you might try using a different USB port. I can only get my phone to connect using one of the 6 usb ports i've tried. Finally, and I don't know if these are the drivers for Odin, but I downloaded these drivers: SGH-i897_Captivate_USB_Drivers_5_02_0_2
When the phone connects, you might want to go to device manager, find the device(s), righ-click and and select 'update driver'. then, in the driver update window, pick 'manual' or 'let me specify location' and navigate to the unzipped SGH-i897_Captivate_USB_Drivers_5_02_0_2 file. Then, it should work.
Like I said, I have no idea if those are the drivers for odin...but I'm about to find out
I'd like to relax, but I think I'm dealing with a phone with a bad usb port...and since I've rooted, SRE'ed, etc., I won't be able to return it.
Anyway...
The driver you're using is the 'direct from Samsung' version, not the one for Odin.
Regardless, I've been through the exercise you propose...both with the Samsung and Odin drivers. When you attempt to manually install drivers, you need to point the installer to the ".inf" setup information file to use. The Samsung driver has three: SSADADB2.inf, SSADBUS.inf, and SSADMDM2.inf.
I get the following message when trying to use any of these three setup files:
The specified location does not contain information about your hardware.
Oh, and I've tried several different USB ports on the computer...both on my external hub and directly into the back of the machine.
Thanks for the suggestions, but still not working...
I'm really thinking I have a bad port on the phone...especially since trying the connection on my wife's laptop produces the exact same error.
Dam...
Still trying to find a way to restore the phone to stock without a USB connection...
i also have this "DEVICE NOT RECOGNIZED" on my sony x1.
Drivers
I was having trouble using the USB drivers from Samsung the one's you were using SGH-i897_Captivate_USB_Drivers_5_02_0_2. The computer didn't recognize the phone. If you havn't tryed these already give these a try. Well since I am new I can't post the url. Put these words together (forum.xda-developers com archive index.php t-730638)
superdog404 said:
I was having trouble using the USB drivers from Samsung the one's you were using SGH-i897_Captivate_USB_Drivers_5_02_0_2. The computer didn't recognize the phone. If you havn't tryed these already give these a try. Well since I am new I can't post the url. Put these words together (forum.xda-developers com archive index.php t-730638)
Click to expand...
Click to collapse
Not sure different USB drivers would help, but I went to the thread you show and tried to download the 32bit drivers. This is what I get:
{"error": "Invalid access attempt for this token"}
Oh well, thanks anyway.
I'm still thinking that the problem is hardware on the phone. I've tried four different cables, and three different computers. All show same problem of DEVICE NOT RECOGNIZED.
Still trying to figure out how to restore to stock without USB connection for ODIN so I can exchange for a new phone...
What are your USB settings on the device? Do you have debug mode enabled or maybe you've set the device to connect to kies right away which is producing errors on your PC. What versions of windows have you been trying to connect to? This sounds like a windows problem more than anything else.
No modifications, same error
I didn't make any modifications to my new AT&T Captivate, and I too am getting USB Device not recognized under any of the following conditions:
- drivers installed, no Kies
- drivers installed after Kies
- Kies installed after drivers
No response to any USB connection mode (Kies, mass storage, media player, PC INternet).
Only way to exchange files is to physically remove the SD card and plug it into my PC. Windows XP Professional.
By the way, which of the three drivers is the correct one: ssadadb2.inf, ssadbus.inf, or ssadmdm2.inf? Pardon my ignorance as to how this is supposed to work.
mukherji said:
I didn't make any modifications to my new AT&T Captivate, and I too am getting USB Device not recognized under any of the following conditions:
- drivers installed, no Kies
- drivers installed after Kies
- Kies installed after drivers
No response to any USB connection mode (Kies, mass storage, media player, PC INternet).
Only way to exchange files is to physically remove the SD card and plug it into my PC. Windows XP Professional.
By the way, which of the three drivers is the correct one: ssadadb2.inf, ssadbus.inf, or ssadmdm2.inf? Pardon my ignorance as to how this is supposed to work.
Click to expand...
Click to collapse
You should return your phone if it's new if you can't get your computer to recognize it when you have the correct settings and drivers.
Choose, mass storage. I use the drivers from ODIN, I also have to ones from Samsung's site but they are for Windows 7 64bit. Before you plug any Captivate into a PC for the first time you need to first change the settings to USB Mass storage or Kies will attemp to download drivers. Once you get your phone to mass storage windows should find the drivers. I am not sure, I am running Windows 7, I have an old desktop that runs XP, I could plug my phone in and check for you.
FiveBraids
Settings--developement-- check debugging mode, this will allow you to open a command shell. Using SDK and ADB commands.
Download SDK online.
http://developer.android.com/sdk/index.html
Follow the installation instructions. This will allow you to use the command ADB download to get your phone into download mode. Kies screws my drivers so I don't use it.
Rhiannon224 said:
You should return your phone if it's new if you can't get your computer to recognize it when you have the correct settings and drivers.
Choose, mass storage. I use the drivers from ODIN, I also have to ones from Samsung's site but they are for Windows 7 64bit. Before you plug any Captivate into a PC for the first time you need to first change the settings to USB Mass storage or Kies will attemp to download drivers. Once you get your phone to mass storage windows should find the drivers. I am not sure, I am running Windows 7, I have an old desktop that runs XP, I could plug my phone in and check for you.
FiveBraids
Settings--developement-- check debugging mode, this will allow you to open a command shell. Using SDK and ADB commands.
Download SDK online.
http://developer.android.com/sdk/index.html
Follow the installation instructions. This will allow you to use the command ADB download to get your phone into download mode. Kies screws my drivers so I don't use it.
Click to expand...
Click to collapse
The 2 folders I found that have the drivers are /program files/android/, .... and /program files/samsung. Delete these subfolders that have drivers in them.
Download this : http://www.megaupload.com/?d=N4GC49JL and unzip. In the folders inside (i386 and amd) there are uninstallers. Run whichever version is appropriate for you. If you have no drivers or it doesn't say to reboot, the main folder has a setup program. Run that to install the proper drivers. When you plug in to usb, it will now find these drivers.
Also, for me, ONLY the REAR usb ports work properly with this. Top, front, and ext hub ALL give issues.....
JayPhill89 said:
What are your USB settings on the device? Do you have debug mode enabled or maybe you've set the device to connect to kies right away which is producing errors on your PC. What versions of windows have you been trying to connect to? This sounds like a windows problem more than anything else.
Click to expand...
Click to collapse
USB is set to Ask on connection
Debug off or on makes no difference
All tests have been done on XP machines (3 different ones)
I'm all but positive this is hardware...
Thanks for trying to help!
Rhiannon224 said:
<snip>
FiveBraids
Settings--developement-- check debugging mode, this will allow you to open a command shell. Using SDK and ADB commands.
Download SDK online.
http://developer.android.com/sdk/index.html
Follow the installation instructions. This will allow you to use the command ADB download to get your phone into download mode. Kies screws my drivers so I don't use it.
Click to expand...
Click to collapse
I haven't tried ADB, but I'm not understanding how ADB would be able to connect when the connection to the computer is failing at the driver level. I guess I can give it a try tomorrow.
Thanks for trying to help!
What would REALLY help me is for someone to post a backup taken of a completely stock (ODIN'ed) phone using ROM manager. I'm thinking I could load that on the phone and then be able to return it for a new phone!
Any volunteers...please?
techmik67 said:
The 2 folders I found that have the drivers are /program files/android/, .... and /program files/samsung. Delete these subfolders that have drivers in them.
Download this : http://www.megaupload.com/?d=N4GC49JL and unzip. In the folders inside (i386 and amd) there are uninstallers. Run whichever version is appropriate for you. If you have no drivers or it doesn't say to reboot, the main folder has a setup program. Run that to install the proper drivers. When you plug in to usb, it will now find these drivers.
Also, for me, ONLY the REAR usb ports work properly with this. Top, front, and ext hub ALL give issues.....
Click to expand...
Click to collapse
Big thanks!
Just got my first Android device a couple hours ago (went from ATT Bold to Captivate), and could not get the phone to mount to my PC.... followed your instructions here and BAM! Perfect-o! I have now rooted....
OK, not sure where to go next... was thinking about just getting a new ROM flashed since I am totally stock at this point.... the fun begins!!!
jaxf250 said:
Big thanks!
Just got my first Android device a couple hours ago (went from ATT Bold to Captivate), and could not get the phone to mount to my PC.... followed your instructions here and BAM! Perfect-o! I have now rooted....
OK, not sure where to go next... was thinking about just getting a new ROM flashed since I am totally stock at this point.... the fun begins!!!
Click to expand...
Click to collapse
Great!! Glad it all worked for you. My next advice is, before adding anything READ A LOT!!! =) Decide what you want from the descriptions and issues you will see in the threads....
Happy modding!!
I didn't see, I just skimmed through bit did you try to put the phone in download mode and see if windows sees that (different drivers come in to play in download mode and none of the touch wiz stuff is running)? it would test the idea of a bad port.
then you can still always install linux and use adw from there, linux and macs don't need drivers. if that doesn't work, put insurance on the phone if you haven't already then drop it in the sink and get another one.
also I think although I don't know but I think adw may have something to do with it. and incorrectly uninstalling it. first put the phone in download mode then you can work from there on ways to fix that.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Ok, I've given up trying to get this to work. I'm 100% convinced this is a hardware problem with the phone!
I had another thread going, looking for a way to restore this phone (remove SRE, SU, etc.) without usb/ODIN so I could return it to AT&T. I've figured out how to restore it to stock and will be heading to AT&T in the morning.
Thanks to everyone for their patience and assistance!
i use linux on my home pc and i have not seen a thread or qestion answered about flashing odin from linux so i tried it myself, forgive me if it has been covered before.
i was able to successfully flash with odin using windeows running inside a vm. my vm software is sun virtual box.
before you do this read the instructions for running odin in widows as i dont go into odin specific detail here.
1. created virtual machine.
2. installed windows XP sp2 on virtual machine
3. installed the newwest version of .net framework(i read that helps but it may have been in reference to kies)
4. dowloaded odin and the proper windows drivers and .pit file and jh2
5. shut down the virtual machine
6. put phone into download mode
7. plugged phone into usb port
8. went into virtual box without the VM running and select
machine>settings>usb
9. clicked the add device icon on the right and clicked on samsung_android[0400]
10. started virtual machine
11. started odin and added the proper .pit file and .tar file
12. pulled batery from phone and put into download mode again and connected the usb and selected devices from the top of the window, selected "samsung_android [0400]"
at this point odin should see the device. if not you may need to reselect the phone in the vm window, do this quickly as there seems to be a time window to start the conection.
simply click start!
this may work in vmware and other vm type software for mac and linux as long as you can mount usb devices to the vm as soon as they are hooked up. if it can be done by com port and not device that may be even better.
i have only done this with virtual box 3.2 running widows XP inside mint 9
if it fails i am not responsible for damage to your device. and in the event it doesn't work go find a friend with windows and run it the proper way! windows machines aren't hard to find!
this worked for my iphone with itunes but was trickier as the driver changes halfway through and that is why i thought this would work.
wine does not work, i have not been able to use wine with software for any device that need drivers when running in widows. so please dont ask!
Not running Linux except for my G1 theme dev,but thanks for the info.
Sent from my SAMSUNG-SGH-I897 using XDA App
I can verify VirtualBox works great for this. Qemu didn't, afaict none of the host USB access options work as documented.
Vmware also works perfectly.
Sent from my GT-I9000 using XDA App
Wouldn't Wine work as well? I haven't tried yet from Wine, but I might now that I read this.
I can never get the USB to attach using VBox, everytime I try to attach the device to my client, I get an error message.
ponack said:
Wouldn't Wine work as well? I haven't tried yet from Wine, but I might now that I read this.
Click to expand...
Click to collapse
wine will not work. it doesn't support USB plugging
Wine is a set of libraries and a loader providing a windows-compatible environment for applications, so in general windows drivers do not work with it. There are patches for USB driver support, but installing drivers is a tedious manual task and results are not consistently very good. VBox is known to work and is fairly easy to set up.
Sent from my SAMSUNG-SGH-I897 using XDA App
Unhelpful said:
Wine is a set of libraries and a loader providing a windows-compatible environment for applications, so in general windows drivers do not work with it. There are patches for USB driver support, but installing drivers is a tedious manual task and results are not consistently very good. VBox is known to work and is fairly easy to set up.
Click to expand...
Click to collapse
Yeah, I figured that out after I posted - I was like wait, there's drivers that need to be installed. Oops.
Unhelpful said:
Wine is a set of libraries and a loader providing a windows-compatible environment for applications, so in general windows drivers do not work with it. There are patches for USB driver support, but installing drivers is a tedious manual task and results are not consistently very good. VBox is known to work and is fairly easy to set up.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Couldn't have said it better, I have tried wine with lots of software but never got the usb end of things to work. Odin does open under wine but I have no idea how to tell it to see the phone as it would see a windows driver that sees the phone.if that makes sense.
There are things I can try but if feel I'd be wasting my time as I don't know enough to be sure I'm on the right path.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
TimF said:
I can never get the USB to attach using VBox, everytime I try to attach the device to my client, I get an error message.
Click to expand...
Click to collapse
I'm not sure if I'm on the right track here. To use usb you need to add the device to a list of mountable devices to the vm. With the virtual machine off go settings> devices> usb. The phone should be hooked up and in download mode to ensure that it is seen to the vm exactly as it will be during the odin flash. Once it is on the list it should work. If this is what you are doing I'm not sure I can help, maybe the devs will have more insight.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Dani897 said:
I'm not sure if I'm on the right track here. To use usb you need to add the device to a list of mountable devices to the vm. With the virtual machine off go settings> devices> usb. The phone should be hooked up and in download mode to ensure that it is seen to the vm exactly as it will be during the odin flash. Once it is on the list it should work. If this is what you are doing I'm not sure I can help, maybe the devs will have more insight.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Click to expand...
Click to collapse
So if you do a "lsusb" form the linux box when your phone is in "download" mode do you see the phone?
I can only get it to show up in "recovery" mode... there for I'm having a bit of a problem getting the VM to see it is not seen in linux...
pietro_spina said:
So if you do a "lsusb" form the linux box when your phone is in "download" mode do you see the phone?
I can only get it to show up in "recovery" mode... there for I'm having a bit of a problem getting the VM to see it is not seen in linux...
Click to expand...
Click to collapse
well I can see it in download mode now... It was just the stupid front ports on my computer. Seems to prefer the back ones...
so now a device is visible in my windows VM but it is called "Gadget Serial"
When it is in "recovery" windows VM can see it as Samsung etc.. and Odin can connect... But obviously odin needs it to be in "download" not "recovery" for it to work.
I've problems trying it...
In normal mode all works and VM detects correctly...
But when I put the phone in Download Mode, "lsusb" freezes...
any ideas?
Maybe I'm missing the point of this thread, by why would you go to all the trouble of hacking around to try to make buggy Odin work under Linux instead of just using Heimdall, which is supported natively under Linux?
Gromlakh said:
Maybe I'm missing the point of this thread, by why would you go to all the trouble of hacking around to try to make buggy Odin work under Linux instead of just using Heimdall, which is supported natively under Linux?
Click to expand...
Click to collapse
I swear, I was just about to ask the same thing.
Seems pointless and convoluted to muck around in VMs when there is a native solution.
Gromlakh said:
Maybe I'm missing the point of this thread, by why would you go to all the trouble of hacking around to try to make buggy Odin work under Linux instead of just using Heimdall, which is supported natively under Linux?
Click to expand...
Click to collapse
mystichobo said:
I swear, I was just about to ask the same thing.
Seems pointless and convoluted to muck around in VMs when there is a native solution.
Click to expand...
Click to collapse
this thread was risen from the dead.....
for no reason as you have mentioned. look at the date of the OP, and realize that heimdall wasnt always available
Ok, I have a N7000 with stock gb and KK2 kernel and I want to load the Paranoid Android ICS rom. First I see that I must route my phone, so I tried following the instructions at:
http://www.android.gs/how-to-root-samsung-galaxy-note-n7000/
These instructions make it sound darn simple, but perhaps I am really dumb? Ok, so first I downloaded the latest kies as well as "CF-Root-SGN_ZS_MUL_KK1-v5.0-CWM5.rar"
After installing kies, I got it to connect to my note although not without heart ache. Eventually I found that it would only work if I first disabled USB debugging. But that wasn't enough. Then I had to reboot the phone. (Without that step it wouldn't work). It wasn't clear to me if I even needed to make it connect to kies. The instructions didn't say I needed to. Ok, so then I start "not-rooted-yet.bat" which displays this:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
(3) enable "UNKNOWN SOURCES"
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
(7) !!! PUT A CF-ROOT zImage FILE IN THE zImage FOLDER !!!
I can only easily do items 2-5. It's hard for me to imagine that I should just ignore the other 3 items.
Instruction #1 confused me. How do I accomplish that? It seems that the adb drivers come with the android sdk but the instructions don't say anything about installing that. That seems like a big deal and if it was required it seems that it would surely be mentioned?
Plus I found this post which also indicates that the sdk is not required.
> victorlht88:
> no u don't need the android sdk to root.
> just install kies, plug your phone with usb debugging enabled
> and let it install the drivers.
> restart your comp and plug your phone in (download mode),
> downgrade the firmware (if need be) with odin and simply
> root using cf root.
> its not that tough.
However those instructions seem about as clear as mud, since if I plug in my phone with usb debugging enabled, kies just hung forever saying "connecting".
Do the adb drivers get installed just by installing kies or do you somehow have to coerce kies to do this?
And then there is step 6. But I don't get any prompt of any kind when I plug in the phone to the pc.
And then there is step 7. I don't know what this means, but my guess is that I have to copy the zimage\zimage file to somewhere on the phone. However where exactly? There is no zImage folder on my phone! Plus even if there was, I couldn't copy anything to it after checking "USB debugging" (mass storage mode) I can no longer see my phone in explorer. What happens when I plug the phone in is that the phone says "USB connected" and then two new drives appear on my PC. However if I try to click on either of those I see "No disk drive. Insert a disk and try again". I even tried rebooting my pc, but then I get even more than two new drives showing up briefly, but they always give the same error message as before.
... yet I know that thousands of people have routed their phones ... so I am left pretty mystified. If anyone can clarify these instructions it would help me greatly, and maybe others as well.
Thanks
~Paul
Follow dr. Ketans thread in the development section.
And once on download mode with usb connected, CLOSE KIES. Otherwise odin will not work.
Sent from my GT-N7000 using xda app-developers app
Hi, your guide is taken from here. I think there is a missing step, which is to download the InitialCFRootFlasher.zip from the end of post #2, and you need to follow the instruction step "1.2. If you are not rooted yet: Using the zergRush exploit".
Btw, adb drivers are included when you install Kies in your PC. Once Kies is installed, you have to close it. Make sure your phone is in USB debugging mode before starting the procedure.
praetorius said:
Follow dr. Ketans thread in the development section.
Click to expand...
Click to collapse
Ok, those instructions seemed more clear. Different script as well although perhaps not significantly so? In any case it worked. I'm not rooted! Thanks all
~Paul
you said your kernel is kk2, then why did you use CF Root KK1?
Cf root kernel for KK1 and KK2 is same.
This How-To is best viewed in a web browser as many of the forum readers strip out the formatting.
The obligatory warning:
"I take no responsibility for what happens to your device if you follow this guide. Flashing with Odin carries risk no matter the platform/OS used. This procedure has worked multiple times with 100% success in the test environment detailed below. It should work for any device, but I can't confirm, so feedback please if it works for your device."
- 3DSammy
Test Environment:
This method has been successfully used to flash stock Samsung firmware to a Samsung Tab S 10.5 (SM-T800) tablet. The SM-T800 Knox counter was "0 0x0000" before the Odin flash and remained as "0 0x0000" after the Virtualbox Odin flash of the Samsung stock 4.4.2 firmware and subsequently a Samsung stock 5.0.2 bootloader.
Distro: Ubuntu 14.04
Virtualbox: v4.3.10_Ubuntu r93012 along with extension pack (scroll down)
Windows Virtual machines: XP with all updates applied and Win7 with all updates applied except IE 11 cumulative update
Odin: v3.10
ADB, Fastboot and drivers: 15 second ABD Driver install (maybe the best solution for MS-XP)
KIES3: Samsung KIES3 and download link
Samsung stock 4.4.2 firmware *(XAC - Canadian): T800XXU1ANF8_T800XAC1ANF5_HOME.tar.md5
Samsung stock 5.0.2 bootloader
Tablet model: SM-T800NTSAXAC (Tab S 10.5)
*Samsung device firmware
Configuring a MS-Windows Virtualbox VM to use with KIES3 and ODIN:
1) Install/Upgrade to the latest Virtualbox for your Linux Distro and make sure you have a matching extension pack
2) Install a Microsoft XP or higher OS from an ISO image or your DVD player via Virtualbox. ISO's can be downloaded but unless you have a valid license key it can only be used for 30 days, which may be all you need.
Note: make sure to configure the memory and disk space to match the minimum requirements for the Windows version, KIES3 and Odin
3) Install the extension pack in the new Windows VM
4) Apply all available Windows Updates in the new VM. This can take a very long time depending on the Windows DVD/ISO you started with.
5) Take a VM snapshot as you do not want to waste the set up time again..
6) For the VM to have access to the PC's USB devices your user account must join the "vboxusers" user group. You need root access
for this step. In a terminal session:
> echo $USER # This will display your user id if you are unsure
> FOOUSER # For example
> sudo usermod -G vboxusers -a FOOUSER # "FOOUSER" should be your user ID as this is only an example
7) Reboot Linux (that is what I did but a log out may work as well)
8) Connect your POWERED ON Samsung Device to the PC
9) Start Virtualbox access the new Window VM's settings and click on USB to get the USB filter list
Check both "Enable USB Controller" and "Enable USB 2.0 (EHCI) Controller"
Press ALT+INS and a pop-up list of all connected USB devices should display.
Select the one starting with "SAMSUNG_Android".
Click OK
Disconnect your Samsung device and power it off
Reboot your Samsung device into Download mode (button combination is specific to your model)
Connect the device to your PC
Open the Virtualbox USB pop-up again
Press ALT+INS and a pop-up list of all connected USB devices should display.
Select the one starting with "SAMSUNG Gadget Serial".
Click OK
Disconnect your Samsung device from the PC and reboot the device (button combination is specific to your model)
NOTES:
I never modified any of the internal USB filter values leaving them exactly like Virtualbox added them to the filter list
The USB filter list should look like the screen shot attached to the bottom of this post
You can ignore any scary warnings on your device when invoking "Download mode" as no device connection or downloads are occurring.
Both USB filters are required as the "SAMSUG_Android" works with KIES3 while "SAMSUNG Gadget Serial" works with Odin.
10) Start the Windows VM and log in
11) ADB, Fastboot and drivers:
At this point you can attempt to let Windows recognize and install the necessary drivers or you can download and install them yourself. See 15 second ADB installer.
NOTES:
Despite installing the drivers manually on Windows 7 the VM recognized and downloaded and installed the drivers a second time when I attached my SM-T800. The driver discovery, download and install took way longer than I expected but eventually completed.
With the XP VM I manually installed the necessary drivers with the 15 second ADB installer script
12) Download and install KIES3 and Odin per their web page instructions. The downloads can be done within the VM. XP may need Internet Explorer upgraded as some web sites no longer support old versions of IE. Upgrading in XP can be a major hassle. Alternately (recommended) download the KIES3 and Odin software outside of the VM and set up a Virtualbox share or use a network share that is attached to the VM. I found that you could not install the executable directly from the share but could after you copied the install file into a Window's directory such as "Downloads".
13) KIES3 validation:
Start the Windows VM and log on
Start KIES3
Connect your booted Samsung device to your computer
After a while (up to a couple minutes) the KIES3 should connect to the device
Check that the device information is accurate (e.g. Internal storage used value)
Attempt a backup but the first time un-check the item for backup up your apps as that can take a very long while for a validation test.
NOTE:
App backups will skip some of the apps, I have no idea why. This is not a fail condition. KIES3 highlights that condition.
Check if the backed up data is accurate, I like to check wallpaper, pictures, music ... etc.
14) Odin validation:
Start the Windows VM and log on
Start Odin (run as administrator)
Power off your device and disconnect from the PC
Reboot your Samsung device into the bootloader and start Download mode (button combination is specific to your model)
Connect your download ready Samsung device to your computer
After a while (up to a couple minutes) the Odin log should show that your device is connected
NOTE: At this point you can use Odin normally.
WARNING: Odin is powerful and can brick your device so read the Odin instructions carefully
As I do not own any Apple products, I could not test this Odin solution on a Mac but maybe someone can see if these instructions can be tailored to Virtualbox on a Mac. Steps 6 and 9 are the only steps unique to KIES3 and Odin use of a VM and are likely similar across both Linux and MAC in regards to Virtualbox's VMs.
Here is an article describing how to use cross-platform JODIN3 as an alternate to Windows and Odin. You may find it a viable alternative to the solution described above..
I hope this helps someone and if you have issues/successes please post in this thread.
Screen shots:
USB filter pop-up settings and required Samsung device (SM-T800) USB filters
Odin after successfully flashing the Samsung 4.4.2 stock firmware to a Tab S 10.5 SM-T800 tablet
Odin after successfully flashing the Samsung 5.0.2 stock bootloader to a Tab S 10.5 SM-T800 tablet
Sent from my SM-T580 using XDA Labs
This is a message for everyone who has been troubled with Odin and VirtualBox. It worked for me that way, but took some time and errors. Finally I found out that the connection in the VM can be established by first opening Odin and then connect the mobile phone in download mode to the VM which requires a click on "devices". Puhhh, took some time, but finally after a week I found that out.