Keep us posted if you find anything Adrynalyne -- I'm intrigued as to whether or not it was Verizon or Samsung (or both) that screwed this one up.
everyone having computer connection issues, please post here.
- Thread starter gunnermike53
- Start date
Well, so far I've been doing my own investigation.
Stock DH12-DI01 = no issues
DJ05 = start of seeing issues
DL09 = still seeing issues
So far there is no rhyme or reason to what causes it...Ive seen it happen with Odin users, and rom flashers, and kernel flashers, on all versions of roms and kernels, EXCEPT bone stock DI01. Even stock updates cause it, as we have seen here.
Now this Verizon iso is on the DI01 rom, it just does not work. Now when we got the DJ05 leak, we stopped making kernels for DI01, due to the initramfs changes. I have checked the source between DI01 and DL09 kernel, wise, only a handful of files were changed, and they all refer to sound, or battery. So really,a DL09 kernel is very much like a DI01 kernel, code wise.
Thats why I think the problem may lie in the system rom, or the initramfs.
So far my attempts to eradicate the CD ROM iso code in the kernel has been met with resistance. If you remove the code (or infection) from the driver, then the ONLY thing your phone will show up as is a cd rom device...
If you remove the kernel CD ROM drivers from the source, the problem still remains.
So I am still working on it, but I am looking for a needle in the haystack right now.
Stock DH12-DI01 = no issues
DJ05 = start of seeing issues
DL09 = still seeing issues
So far there is no rhyme or reason to what causes it...Ive seen it happen with Odin users, and rom flashers, and kernel flashers, on all versions of roms and kernels, EXCEPT bone stock DI01. Even stock updates cause it, as we have seen here.
Now this Verizon iso is on the DI01 rom, it just does not work. Now when we got the DJ05 leak, we stopped making kernels for DI01, due to the initramfs changes. I have checked the source between DI01 and DL09 kernel, wise, only a handful of files were changed, and they all refer to sound, or battery. So really,a DL09 kernel is very much like a DI01 kernel, code wise.
Thats why I think the problem may lie in the system rom, or the initramfs.
So far my attempts to eradicate the CD ROM iso code in the kernel has been met with resistance. If you remove the code (or infection) from the driver, then the ONLY thing your phone will show up as is a cd rom device...
If you remove the kernel CD ROM drivers from the source, the problem still remains.
So I am still working on it, but I am looking for a needle in the haystack right now.
Before update was rooted with z4root, unrooted, then did a manual check for the new update, downloaded and installed it OTA. Rerooted using manual method from Android Central. This is what's been happening with my usb mounting since then:
Plugged into Linux and was able to mount, saw my files for a few seconds and then it immediately unmounted. Plugged it in using the Samsung factory cord and was able to mount successfully and have access to my files.
Tried it on Windows XP and was unable to mount - it gave me the option in the notification bar of my phone, but when I selected it there was no mounting that occurred in Windows. (I should also mention that I have auto play disabled in Windows, so I didn't see that pop up everyone else is talking about). Tried turning off usb debugging and then didn't even get the option to mount in the notification bar when connected and after about 30 seconds media sync started (I canceled it, but still didn't show any of my files). Tried to plug it back into Linux with usb debugging still unchecked and it didn't even register that it was plugged in on either the computer or the phone. Turned on usb debugging, plugged it back into Linux and it still didn't even register that it was plugged in. Rebooted phone (with usb debugging still on) and after reboot was able to mount to Linux again. Only factory cord will work though, any other cord will mount for a second and then just unmount automatically (even though you will still have to drag down your notification bar and select turn off usb connection).
This works for me for now, as my Linux computer is my main computer. I guess to transfer anything from any of my Windows laptops for now, I'll have to continue using SugarSync (which I used 10x more than mounting my phone anyway) or pull out the sd card and use my handy dandy card reader to get the job done. This bug is certainly a huge oversight on Verizon or Samsung's part!
Sent from my Galaxy Tab using Tapatalk
Plugged into Linux and was able to mount, saw my files for a few seconds and then it immediately unmounted. Plugged it in using the Samsung factory cord and was able to mount successfully and have access to my files.
Tried it on Windows XP and was unable to mount - it gave me the option in the notification bar of my phone, but when I selected it there was no mounting that occurred in Windows. (I should also mention that I have auto play disabled in Windows, so I didn't see that pop up everyone else is talking about). Tried turning off usb debugging and then didn't even get the option to mount in the notification bar when connected and after about 30 seconds media sync started (I canceled it, but still didn't show any of my files). Tried to plug it back into Linux with usb debugging still unchecked and it didn't even register that it was plugged in on either the computer or the phone. Turned on usb debugging, plugged it back into Linux and it still didn't even register that it was plugged in. Rebooted phone (with usb debugging still on) and after reboot was able to mount to Linux again. Only factory cord will work though, any other cord will mount for a second and then just unmount automatically (even though you will still have to drag down your notification bar and select turn off usb connection).
This works for me for now, as my Linux computer is my main computer. I guess to transfer anything from any of my Windows laptops for now, I'll have to continue using SugarSync (which I used 10x more than mounting my phone anyway) or pull out the sd card and use my handy dandy card reader to get the job done. This bug is certainly a huge oversight on Verizon or Samsung's part!
Sent from my Galaxy Tab using Tapatalk
I'm all stock and had this issue right after the OTA update. Just got off the phone with verizon and they don't know of any problems , Imagine that !!!!
This is exactly why they did it. vcast = revenue.
He's probably our best and only hope.
mike has the verizon media management thing been discussed, sorry if it has i have been working on one click root last couple days
Menu key, Settings, Applications, Development, select the check box next to USB Debugging (a message box will then pop up, press ok).
Sent from my Galaxy Tab using Tapatalk
I have found that if I turn my Mac off for about ten minutes and then I try again, my phone mounts and I can use isyncr to sync my playlists.
Sent from my SCH-I500 using Tapatalk
Sent from my SCH-I500 using Tapatalk
On step #4, you listed to "run toollauncher-bootstrap.exe."
When I plug in the phone, will it prompt me to run that? Or is that another file that I need to download and install?
Thanks
When I plug in the phone, will it prompt me to run that? Or is that another file that I need to download and install?
Thanks
Windows should pop up a dialog box asking you if you want to run it.
Thanks for the info Cory. I just wanted to make sure.
I read in another post that said you need to find ToolLauncer-Bootstrap.exe file in the folder that you installed Media Manager. That you should double click on the file.
I read in another post that said you need to find ToolLauncer-Bootstrap.exe file in the folder that you installed Media Manager. That you should double click on the file.
Do you think this will help with the media sync issues that I've been having? I've been getting a delayed write error when I try to sync my music and SF. Never had this problem with DL01. Only when I updated to DL09.
It's so weird, I haven't had any of this happen to me, thankfully. Media Sync runs, but doesn't prevent me from being able to mount and access my SD card as usual. If I wanted to use some special software to access my phone I would have bought an iPhone.
My two cents
Had the problem. Turned on USB debugging and turned it off. Connections to computer works but takes about 30 seconds for USB to connect. Downloaded the VZW media manager app to see if that made any difference. Never saw the "Bootstrap" file and nothing changed in terms of the connection. Still takes about 30 seconds.
Had the problem. Turned on USB debugging and turned it off. Connections to computer works but takes about 30 seconds for USB to connect. Downloaded the VZW media manager app to see if that made any difference. Never saw the "Bootstrap" file and nothing changed in terms of the connection. Still takes about 30 seconds.
it has, a rock in my shoe is more useful. for some it appears to work, but not for me.
hey man thats great info, but you are on the wrong thread.
post here please:http://forum.androidcentral.com/ver...ascinate-sd-card-will-not-mount-mac-dl09.htmlim sure folks there would love to hear about this. this one is for pc. the problems are a bit different on mac vs pc.
I can support Cory's suggestion from post #58 because I coincidentally tried the exact same method before I came to this thread (!!!). I am running stock DL09 via OTA, rooted using the 1-click method (2 attempts-- first one claimed success but had failed).
I had found initial success using 32-bit drivers on my 64-bit machine, but the system became unresponsive and I switched back to 64. I've done several phone restarts since then and everything seems to be fine, although the phone sometimes takes a couple seconds to mount to the computer and vice-versa. USB debugging must remain on.
I had found initial success using 32-bit drivers on my 64-bit machine, but the system became unresponsive and I switched back to 64. I've done several phone restarts since then and everything seems to be fine, although the phone sometimes takes a couple seconds to mount to the computer and vice-versa. USB debugging must remain on.
Similar threads
- Locked
- Locked
Facebook
Twitter
Instagram