Related
This is just an updated version of deadnex's original guide, with a few things thrown in from various people who have found what works and what doesn't.
This guide has been used and tested as effective with the windows 7 rc 7100 build.
Step 1 - Go here http://www.microsoft.com/windows/windows-7/download.aspx and download Windows 7. You can get a key from the same place, so don't worry about not having a key.
In the event that the servers aren't offering the download {due to server issues} you can download a current version through a torrent site. I recommend mininova as it's the most legitimate of the bunch.
To get a key for windows 7 (32bit) (if you downloaded it through a torrent site), go to this address https://www.microsoft.com/betaexperience/productkeys/win7-32/enus/default.aspx
(64bit)
https://www.microsoft.com/betaexperience/productkeys/win7-64/enus/default.aspx
To clarify this part, you're setting up a usb flash drive or usb card reader and sd card to work as an installation drive for windows 7. I've followed these steps exactly, and found them to be completely accurate. They work, so do each step, and make sure to keep track of your steps so as not to miss one.
Thanks to deadnex for all of this information.
USB-install:
User feedback suggests that doing this next part should be done on a computer running windows vista. In winXP, your usb drive might not show up during the process.
edit (before step 1, create a folder on your main computer called windows7. Don't do this on your shift, and it's recommended to use c:\windows7\ to make the process easier. If you use another location to extract the files to, make sure to remember which directory it is, and adjust the steps of this tutorial to your own location.)
1 - Open the windows7 Iso file with winrar, and extract all the files into C:\WINDOWS7\ (or the folder you created as mentioned above)
2 - Open command prompt in administrator mode (start - all programs - accessories - (right click) Command Prompt and select run as administrator.
3 - Then type these commands without the - and press enter after each :
- CD\
- DISKPART
- LIST DISK
- SELECT DISK X ( X is the memory stick disk number you got from LIST DISK)
- CLEAN (CAUTION; THIS WILL ERASE ALL THE CONTENTS OF THE SELECTED DISK)
- CREATE PARTITION PRIMARY
- SELECT PARTITION 1
- ACTIVE
- FORMAT FS=FAT32 QUICK
- ASSIGN
- EXIT
- XCOPY C:\WINDOWS7\*.* /S /E /F U:\ (U:\ is the name of usb drive you are using for your install, if your drive has another letter, which is most likely, of course put in your own) (after *.* and after each letter preceded by / there's a space!)
OPTIONAL- Include an extra folder on your windows7 usb drive called drivers, and put all the drivers in there that you'll need to get windows 7 running smooth. Drivers are listed just a little further down on the page, so before completing the next step, go there and get the drivers.
WARNING- THIS WILL ERASE YOUR VISTA AND REPLACE IT WITH WINDOWS 7. THIS IS IT!!! Don't worry, win7 rc 7100 is far better anyway. Just to be safe though, backup your personal data before continuing to the next step.
[edit] With a little use and time, I've come to find that windows 7 has a great amount of compatibility issues with certain games. Although I've only had the chance to try a few, there seems to be a trend with win7 being unable to run a lot of older, but still 3d, games. Warcraft 3, and Dungeon Keeper 2, to be more specific. If you're not a gamer, it shouldn't matter, and Windows 7 is still the best choice for you. If you do like to play games, you might want to reconsider changing to windows 7. [edit]
Restart your computer, at startup push FN+F10, and choose your usb drive.
This will take you to the installer, select your language, timezone, and keyboard layout. Next.
In summary, you're going to select Custon (advanced) in the windows 7 installation process, and some card readers (sd to usb) don't work.
This will not affect your HTC SHIFT Vista recovery partition but it will remove Vista itself from your shift. Your settings from Vista will not be carried over to Windows 7.
_________________________________________________________________
DRIVER DOWNLOADS AND INSTALLATION.
Well, once you're through all that, you should be looking at your new windows 7 shift. Now's the fun part! Driver installation!
Go to this link, and download all of the drivers. (10 in total)
http://www.htc.com/www/SupportDownload.aspx?p_id=60&cat=1&dl_id=82
Putting these files on the same flash drive as your windows 7 install makes matters much easier for this time and next time should you need to try again. I also recommend copying and pasting the installation order from the htc site in a notepad or wordpad file and putting that in the same folder as your drivers. That way, when it's time to install your drivers, you can open that file, and use it as a reference to ensure you have the order correct. Chances are that your shift won't connect to the net, right after the win7 installation.
IMPORTANT IMPORTANT IMPORTANT
INSTALL EACH DRIVER IN THE ORDER THAT HTC HAS LISTED ON THEIR DRIVER DOWNLOADS PAGE. DO THIS OR FACE TOTAL DEATHKILL!!! actually, you'll just have driver issues, but that SUCKS!
After many people have responded, I wish to remind everyone. Install all the drivers. INSTALL ALL THE DRIVERS. Install all the drivers. Yes, I said that three times. Although your shift seems to work, when only installing a few, the fact is, drivers like the synaptics touchpad driver also control other parts of your shift, like the two face bottons above the touch pad. If you install one driver, and skip one in between, you mess up the order of installation that is so important, and then force yourself to need an entire wipe and reinstallation of win 7. So, one more time, INSTALL ALL THE DRIVERS FROM HTC.
One more important thing to know about the drivers is, DON'T LET WINDOWS RESET AFTER INSTALLING EACH DRIVER, select RESTART LATER AFTER INSTALLING EACH DRIVER. I REPEAT, INSTALL ALL DRIVERS (IN ORDER) BEFORE RESTARTING WINDOWS.
IMPORTANT When you've finished installing your drivers but still need to restart to take effect, go to your display settings (right click the desktop) and select a non aero theme. save settings after that. Windows 7 Basic is a non aero theme and it looks good. If you leave Aero enabled, your shift will blue screen of death crash when it boots into high res mode.
Windows 7 can not run Aero in high res on the shift. (for now, at least)
When you install the drivers – beware that you have to install them with Vista Compatibility mode enabled and run as Administrator. Right-click the driver setup file – click the Compatibility tab – select Windows Vista and mark “run this file as Administrator”
To save yourself a headache, copy and paste the following list into a wordpad file and place it in the same directory as your driver downloads. Putting this list in the same directory on your win7 flash card means that you can open it on your shift after installing win7 and use it as a reference when installing your drivers. Keep it all together.
EACH DRIVER IS 100% IMPORTANT AND NEEDED, DO NOT SKIP DRIVERS, EVEN IF THAT DEVICE SEEMS TO BE WORKING ALREADY. SKIPPING THE TOUCHPAD DRIVER MEANS THAT THE RESOLUTION AND COMM CENTER BUTTONS DON'T WORK. SKIPPING THE SOUND DRIVER MEANS THAT CERTAIN APPS WILL CAUSE THE SYSTEM TO BLUE SCREEN. SKIPPING THE VIDEO DRIVERS MEANS THAT CERTAIN APPS WILL CAUSE THE SYSTEM TO BLUE SCREEN.
DON'T SKIP DRIVERS.
Here's the order.
a. VISTA_INTEL Chipset Driver v8[1].3.0.1014
b. Intel VGA driver(7[1].14.10.1461)
c. VistaECDrvV1[1].0.1.10
d. TouchScreen(1[1].1.0.2)
e. Synaptics MicroPad(10[1].0.11.1)
f. Realtek Audio Driver R197(6[1].0.1.5653)
g. Vitakey _AC5023_Fingerprint AP v5[1].0.2.0 and Driver v7.10.1.0 *
h. Extension Kit USBLanDriver(3[1].8.3.7)
i. Shagctrl_1[1].2.6.122-control center
j. Marvell WiFi driver(8[1].114.123.139)
This next part was contributed by Thaihugo. Thank you a ton for this contribution Thaihugo .
To connect the Windows Mobile (your Shift's other OS) side to the PC side of your Shift, run USB Tools in the windows mobile side. If nothing happens, go to your settings (still in mobile)- Connections, then click on "USB to PC". Uncheck the "Enable advanced network functionality and wait at least 5 minutes to see if it connects (you must enable the port in USB tools first). Another note, some roms, for the wm side of shift, don't include the internet sharing app. If you can't find it, you've got a crap rom, and you should follow a guide which will allow you to put a real rom on it.
Make sure you are connected to the internet on win7 side (using wifi for example) to download WMDC (Windows Mobile Device Center).
If WMDC doesn't load, plug another pocket pc into the shift's usb port while running windows7 and it will download , or if you don't have another pocket pc lying around, download it manually from Microsoft.
Also, after this setup, the Snapvue side might turn off and not turn on again. In this case, reset under vista side using the HTC tools, and go to the power settings (long click or right click on the battery icon in the bottom right of your desktop). Disable all the "turn device off after x min" settings and make sure to click ok to make the changes effective.
Again, a big huge thanks to deadnex for originally posting the steps to this process. And thanks to everyone else who contributed to a better running shift via windows 7.
Caid.
444
You forgot to specify that drivers must be installed with Vista Compatibility mode enabled and run as Administrator
Everythnig works fine for me untill.. I boot from usb go to "install now". And then ...
"A required CD/DVD drive device driver is missing.If you have a driver floppy disk,CD,DVD or USB flash drive please insert it now.
Note: If the windows installation media is in the CD/DVD drive, you can safely remove it for this step"
I go to browse and then " No device drivers were found.Make sure that the installation media contains the correct drivers, and then click OK".
I'm completly lost help..
thanks for the reminder.
weird, list disk doesn't list my usb flash drive but lists all my other hard drives. what am i doing wrong?
You are probably under Windows XP. Try a vista computer or another computer for this operation.
Caid444, you can upgrade your guide with the following info:
To connect the Windows Mobile side to the PC, use the USB tools. If nothing happens, go to settings, Connections then click on "USB to PC". Uncheck the "Enable advanced network functionality and wait at least 5 minutes to see if it connects (you must enable the port in USB tools).
Make sure you are connected to internet on vista side (using wifi for example) to download WMDC.
If WMDC doesn't load, plug in another pocket pc using the USB port, or download it manually.
Also, after this setup, the Snapvue side might turn off and never turn on. In this case, reset under vista side using the HTC tools, and go to the power settings (long click on the battery icon). Disable all the "turn device off after x min".
Thanks for your description. It looks good. Only onr thing let me bluescreen
my Shift. Whenever I install Synaptics MicroPad(10[1].0.11.1) my Device ended with a bluescreen. I tried a newer Version from the website, but no way, same result. Does anybody understand why? Does someone found out same?
Greets
Androgyn
thaihugo said:
Caid444, you can upgrade your guide with the following info:
To connect the Windows Mobile side to the PC, use the USB tools. If nothing happens, go to settings, Connections then click on "USB to PC". Uncheck the "Enable advanced network functionality and wait at least 5 minutes to see if it connects (you must enable the port in USB tools).
Make sure you are connected to internet on vista side (using wifi for example) to download WMDC.
If WMDC doesn't load, plug in another pocket pc using the USB port, or download it manually.
Also, after this setup, the Snapvue side might turn off and never turn on. In this case, reset under vista side using the HTC tools, and go to the power settings (long click on the battery icon). Disable all the "turn device off after x min".
Click to expand...
Click to collapse
I've added this part, thanks again Thaihugo.
Caid
444
thaihugo said:
You are probably under Windows XP. Try a vista computer or another computer for this operation.
Click to expand...
Click to collapse
You're right. it's all good though, i used MBRWIZ to take care of that minor setback. I can boot Windows 7 thru a USB drive now. I'm still on the fence about it, i have Vista Ultimate on my Shift right now. From your experience will Win 7 be drastically better?
Greenarcher707™ said:
You're right. it's all good though, i used MBRWIZ to take care of that minor setback. I can boot Windows 7 thru a USB drive now. I'm still on the fence about it, i have Vista Ultimate on my Shift right now. From your experience will Win 7 be drastically better?
Click to expand...
Click to collapse
It's like driving a race car compared to vista.
apoparis said:
Everythnig works fine for me untill.. I boot from usb go to "install now". And then ...
"A required CD/DVD drive device driver is missing.If you have a driver floppy disk,CD,DVD or USB flash drive please insert it now.
Note: If the windows installation media is in the CD/DVD drive, you can safely remove it for this step"
I go to browse and then " No device drivers were found.Make sure that the installation media contains the correct drivers, and then click OK".
I'm completly lost help..
Click to expand...
Click to collapse
Please, is there anybody who can help me resolve my problem? I tried lots of times by nothing works..I'm reading all these positive comments about win7 and I can't wait to have them on my shift.. I can see the usb, I browse there to the folder I have the drivers but can't install them.
Thank you in advance
This is for those who've encountered problems.
Start the whole process over again. I didn't make the guide clear enough when I first posted this thread. It's clearer now. The symantec drivers are probably fine, you're probably crashing because windows aero is still enabled, and it is crashing your shift whenever it tries to switch to high res mode. Disable aero.
As for apop, you need to install via the second option, not the first. I got the same error when I selected the first install option when I booted into the windows 7 installer. This method will completely remove vista as the main os and put it in another folder. As a precaution, I recommend backing up personal documents that are stored in any windows sub directory. *word documents and the likes.
Anything outside of your windows directory, or on the main hard drive itself should remain after the install, but I only did this process once with extra stuff on the drive (it stayed).
Back it up, and do a fresh install.
Caid.
444
Thanks for your anser Caid. I just don't have an external DVD.. Is it impossible to go through 1st way? I have read that some people managed to do it this way..
You mean via a usb flash drive? That's how I did it. Follow the steps for the usb flash drive method, but when you boot it on your shift and you have the option to do a custom or express install, do the custom install.
Caid
thaihugo said:
It's like driving a race car compared to vista.
Click to expand...
Click to collapse
wow, that got me convinced. installing windows 7 right now. gonna probably stay up late ha ha
Caid444 said:
You mean via a usb flash drive? That's how I did it. Follow the steps for the usb flash drive method, but when you boot it on your shift and you have the option to do a custom or express install, do the custom install.
Caid
Click to expand...
Click to collapse
Yes, I'm using a usb card reader and sd card. I don't have two options (custom/express). Just one "install now"..
P.S. Thanks for your interest in my case.
ok
After you select "install now" there'll be a license agreement. After that there'll be a choice between two install options. You need to choose the second one.
Caid.
Can someone explain to me how to set up a cellular internet connection through windows 7? I've got the sim card inside, the phone recognizes it, but I don't know how to get it working through win7, I used control center to enable modem, but still no luck. This is really annoying.
Caid.
444
SnapView Turn's and WM7 too ... the screen goes off
Hi, I completed the W7 installation successfully. I even got to conect SnapView with W7 this time. I say this time because with the previous Wm7 guide I wasn't able to do it.
Anyway, now my screen is blank for WM and W7. In fact I have to press the on switch to get the W7 screen back. Once I have W7 working I need to reset Snapview throught the Shift Control Centre to get it going. Finally Snapview / WM comes on. However it lasts on for a few minutes and then the screen is off again. W7 will last for a few minutes more and the same will happen. I then need to press the sliding switch again. The W7 screen will turn on back to normal (the OS doesn't actually turn off but just the screen); however, WM doesn't turn on (in this case it's the screen and WM itself). I then need to repeat the resetting process again.
I did do this:
"
Also, after this setup, the Snapvue side might turn off and not turn on again. In this case, reset under vista side using the HTC tools, and go to the power settings (long click or right click on the battery icon in the bottom right of your desktop). Disable all the "turn device off after x min" settings and make sure to click ok to make the changes effective"
I did it at W7. Am I missing something? Any hints from the experts? Needless to say, everything was working fine with Vista.
Thanks
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
Hey guys,
For some reason, my Windows 7 32bit laptop is not recognizing the Galaxy tab at all when in download mode. I have installed kies (which incidentally also doesn't recognize the tab), and installed the individual drivers, but cannot get my computer to even see the Tab.
When the Tab is in normal mode (debugging turned off), I can mount the Tab as a drive and it has no problems.
Has anybody else run into this issue? The Tab is not showing up in the device manager at all. I do have root, and my end desire is to connect with Heimdall, and continue to get the error message "Failed to detect compatible device."
Any help would be greatly appreciated.
Seth
Download and install drivers for your tab. Samsung website should have them, if not they shouldn't be too hard to find.
drivers
Hi,
Already tried that. Kies doesn't recognize the device at all (with USB debugging active and not active both), and the Device Manager doesn't show anything either. When I plug the tab in, it recognizes that it is connected, but mounting the SD card as a drive doesn't do anything either.
The worst part about it is that I'm not sure that I can even revert to stock without being able to get Heimdall working. I've searched a ton, and it seems to be the key to just about everything. Any other ideas?
Seth
have you tried to install the drivers that come with Heimdall? I've had to force install those a couple times to get my Tab recognized in download mode.
Heimdall drivers
pvtjoker42,
Can you explain a little about what you mean? I am running Heimdall 1.1.1 have done the following:
1. Browse from the main folder to the "Drivers" folder and run zadig as an Administrator.
2. Click on "Options" and select "List all devices"
3. Click on the dropdown menu and search for anything that might be related to Samsung Galaxy Tab or Android of which there are none.
Is there a different way to force the install of the Heimdall drivers that I'm unaware of?
Thanks for your help,
Seth
when you drop down the list of devices what all is listed? I've had it show up as just a serial device before, with no mention of samsung/tab/galaxy etc..
Devices
Cisco VT Camera II (Interface 0)
Cisco Microphone (VT Camera II) (Interface 2)
USB Receiver (Interface 0)
USB Receiver (Interface 1)
USB-Serial Controller D
Fingerprint Sensor
Optical Drive Controller
TOSHIBA Web Camera (Interface 0)
USB Multimedia Audio Device (Interface 0)
USB Multimedia Audio Device (Interface 3)
Those same entries can be found in Device Manager>Universal Serial Bus controllers even on first boot if the Tab is not connected. Even after connecting the Tab, this list does not change.
Thanks again for your help!
Seth
have you tried uninstalling everything related to the tab? Kies, the specific drivers etc, then trying the Heimdall drivers?
So all the devices listed above are there when the Tab isn't even plugged in? Odd.. I would have suggested trying it for the USB-Serial Controller D, but if it's there without the Tab plugged in it sound like a different system device.
Don't suppose you have access to a different pc to try it on? see if it even notices the Tab being plugged in and tries to install drivers..
Yeah, I have other computers to try. Tried plugging it in yesterday to a different computer (same brand and model) with no change. Computer didn't recognize the device at all and/or try to install drivers.
Usually when an unknown device is plugged into a computer, the computer registers that it's there - the Device Manager shows an "Unknown Device" somewhere in the list, but this isn't the case with this device. Not sure what happened, but it appears as though I goofed up the USB somehow in the rooting process or the port itself went bad.
I'll try other computers and write back.
Thanks again,
Seth
I've tried three different computers with the same outcome. They do not register the device at all, and I cannot mount the SD card to the computer. I'm definitely at a bit of a loss at this point. Without USB, I'm not sure how else to make this happen. Ideas?
Seth
Just to double check with hemidall ur opening the drivers folder and running zadig.exe in there going to options>list all devices
Yes, that is correct. I'm opening the Heimdall 1.1.1 folder, opening the drivers folder, and running zadig. Nothing pops up at all and nothing shows up in the device manager.
I cannot mount the SD card to my computer, but the Tab recognizes it when I plug it into the computer's USB port. That's as far as I can get, however, as the computer does not see the Tab at all.
Have you tried 'fix permisions' in recovery mode - usually under the advanced option?
Sent from my GT-P1000 using XDA App
There is no "Fix permissions" in this recovery mode. Tried to fix permissions from cwr (which only went through 2 lines), but it doesn't seem to make any difference. Still force closes Gallery when I try to mount the SD card. Also force closes gallery when I try to open gallery.
This is very strange. It continues to tell me that there is an update available. I might go ahead and take it to see if it takes me back to stock. I would be okay with this as long as I had USB connectivity again and could root.
Any other thoughts?
Seth
P.S. Tried to take the update, but it gets about 1/3 of the way through the install and fails.
Any other ideas on how to flash without Heimdall?
Seth, what about trying Odin3 and its drivers?
Sent from my GT-P1000 using XDA App
I'll look around and find Odin3 and give it a shot. I'm concerned that because my computer doesn't recognize it as a connected USB device, that no program will see it either. That said, it's worth the shot and I appreciate the suggestion.
Do you know whether I can use the same files for Odin that I would use with Heimdall? Do they need to be packaged differently?
Thanks in advance,
Seth
If you have GSM based tab you can try flashing Team Overcome's Kratos ROM (I had no issues with download mode following their excellent ROM flashing instruction here http://p1000.teamovercome.net/?page_id=64 ) which involves download mode + using Odin, which displayed that it's connected to a tab through a serial port emulation. At least you can confirm if your tab's download mode is working. I'm using Win 7 Home Premium 64 btw.
I downloaded Odin 3, but without knowing if I am able to flash a package designed for Heimdall, I'm not sure what Odin 3 would tell me. Thoughts? Can I use Odin3 to transfer one of the Heimdall-specific ROMs to the Tab?
I had this same problem some weeks back. I had to use the drivers that came with Heimdall, and most importantly, in order to get it to recognize in download mode, I had to install them while in download mode and plugged in.
Hello folks,
I'm facing this "please insert a disk" issue when connecting my Note to computer via USB Debugging mode / Mass Storage Mode.
I'll let screenshots in the attachment explain itself. #1 shows the screenshot of devices menu when the phone is plugged into the computer in DEBUG mode; #2 shows the screen after I've clicked "connect USB storage" from the drop-down list of the phone; #3 shows what happens when I try to open one of the two "removable disks".
MTP mode works fine, as well as Kies connection. As I finally started exploring the potential of Android platform, I realized that MTP and Kies connection are the most useless connection options for me, and I'd rather leave it in debug mode all day. So has anybody experienced this issue, or had any suggestion on the solution?
As always, many thanks in advance, and many thanks button clicks afterward!
p.s.,
Desktop OS: Win7 Pro X64 SP1
Note: 2.3.6 Stock LB1 Open Germany Firmware, CF rooted LB1 kernel.
Also, I should have all the latest official device driver from Samsung, as I have the latest version of Kies installed (and I discovered a driver folder under Kies' installed location). I'm not so sure about adb driver, but I was able to find the Note to be listed under devices by typing "adb devices". So.. I don't know where could've gone wrong.
Help anyone?
This really sounds weird... I was facing problems of the Galaxy Note not being detected on several Windows7 32/64-Bit SP1 computers as well but this was gone after I installed SAMSUNG_USB_Driver_for_Mobile_Phones.
You are right - from all that i know all required drivers should be available when KIES is installed on your system. Whatis even more strange is that your device seems to be detected as two partitions are available and are displayed in Explorer...
So I would test the following:
- check if your device manager lists any unknown devices
- Uninstall KIES and try to find the SAMSUNG_USB_Driver_for_Mobile_Phones and install those
- check all available USB ports and see if this solves the problem
- try another USB cable
- make sure your (external) SD card is formatted with a Windows compatible file-system e.g. FAT32
Hope this is helpful and helps solving your problem.
Thanks for your reply!
My device manager basically listed all the drivers/devices associated with the phone:
My Device manager shows devices:
Samsung Android Composite ADB interface
Android UMS Composite USB device (x2)
SAMSUNG Android USB Modem
USB Mass Storage Device
USB Mass Storage Device (Android)
I've attached the screenshot when all the drivers being installed when the phone is firstly connected to the computer. Also in the device manager, everything shows "this device is working properly"
I then decided to test with another Note of my friend's (On the same computer). Her Note has no SD card in it, and is completely stock ROM non-rooted LA4 Open Germany firmware. The same thing happened.
One thing worth mentioning: Yesterday, this worked only for once. When I initially encountered this issue, I restarted my computer, and boom, my phone was connected in Debugging mode! However, once disconnected, and I tried to connect it to the computer again, this issue came back. And afterward, no matter how I restart my computer, the phone won't get connected.
I also tried all USB port (USB 2.0 and 3.0), three different cables (2 of them are Samsung OEMs) and failed to address the issue.
I'm nearly exhausted but I will never give up, as this is my only computer and my only phone (haha), and without solving this issue, I'm never gonna be able to view the phone as a USB storage and easily transfer the file from my computer to the phone.
I'm going to try the last thing that I haven't done from the list you posted:
- Uninstall KIES and try to find the SAMSUNG_USB_Driver_for_Mobile_Phones and install those
I believe that I can keep the driver folder in the Kies' folder, as I believe those are the newest Samsung driver, given that the Kies was the latest release version.
So far, I can only conclude that this issue is not related to specific phone but the Windows 7.
And thank you for your help btotaku!
If anyone has any insight into this issue, please help me. Thumbs up for you!
BTW, I was able to extract both SAMSUNG_USB_Driver_for_Mobile_Phones.exe from under Kies' installation path under Program Files x86 folder, and an uncompressed folder of all kinds of drivers for Samsung device, called "USB Drivers".
And looks like I was wrong. The newest version of SAMSUNG_USB_Driver_for_Mobile_Phones I had was 1.4.8. While the driver that came with the newest Kies was 1.4.103
I'll post back soon
Reinstal Windows on your PC bro.
Problem fixed.
is that your internal memory or the sd card?
Same thing happens either with SD card in the phone or not
avetny said:
Reinstal Windows on your PC bro.
Problem fixed.
Click to expand...
Click to collapse
That's the last thing I would do
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.