Downgrading from DJ05/DL09 on fascinate

[gunnermike53]

It's been a LONG time since the last time I played with Open Suse, but I have a little Linux storage/print server I set up, and found Ubuntu to be the most user friendly and have the most driver support of all the distros I tried out - (Ubuntu, Fedora, Debian).



Connect the phone and the following in a command prompt:

adb shell
dmesg > /sdcard/dmesg.txt

It'll write out a text file to your SD card with what appears to be a bunch of logs.

everything i read led me to ubuntu, however a couple of the sites mentioned that open suse works a little better with laptops, more power options and more wifi drivers and support. i dont have my heart set on open suse, if i dont like i will get ubuntu.

i tryed the command in adb and got nothing. it sees my phone, i get the bash-4.1# i type the commands, it does someting, and then goes back to bash-4.1#, but no .txt file named dmesg. i suck at life.

 

[JaeKar99]

I've flashed modems from DI01 to DJ05 to DL09 and several combination thereof and never had a problem. It is strange that the issue pops up for some going to DJ05, for some going to DI01 and for some not at all.

Just to compare, the Samsung Win7 64 drivers I'm using are version 5.2.0.4, dated 5/12/2010

I do remember initially not being able to get Win7 to recognize the phone at all, and had to initially root the phone (way back when) on my wife's notebook. Then at some point, I tried to reinstall the drivers on my computer and everything started working.

I stripped out everything but (Samsung USB driver for mobile phones 1.3.450.0) 5/27/2010.

 

[DroidXcon]

Sorry guys, i thought i had something there

 

[gunnermike53]

something has happened to the phone, i dont think it has anything to do with the computer. i restarted my phone connected to my win 7 x64 partition. as usuall i can see the sd card. then i restart and install open suse on another partition. when i plug the phone in it pops right up with 16 gb file system. i disconect, restart the phone, and reconnect to the pc..... nothing. i still have to restart plugged in to the computer for the computer to recognize the phone. i can plug my phone into any computer i want all day long and it is just fine. i restart my phone not plugged into anything and it starts all over. it seems if the phone starts up connected to a computer it will connect just fin. if it doesnt then well it doesnt.

 

[DroidXcon]

something has happened to the phone, i dont think it has anything to do with the computer. i restarted my phone connected to my win 7 x64 partition. as usuall i can see the sd card. then i restart and install open suse on another partition. when i plug the phone in it pops right up with 16 gb file system. i disconect, restart the phone, and reconnect to the pc..... nothing. i still have to restart plugged in to the computer for the computer to recognize the phone. i can plug my phone into any computer i want all day long and it is just fine. i restart my phone not plugged into anything and it starts all over. it seems if the phone starts up connected to a computer it will connect just fin. if it doesnt then well it doesnt.

kind of like it is using random addresses vs an asigned one in the phone

 

[gunnermike53]

kind of like it is using random addresses vs an asigned one in the phone

kinda i geuss. its really starting to annoy me. its not that i have to restart connected to the computer, i dont mind that so much. but i am trying to play around with adb and nothing is working like it should, just like trying to get that dmesg. i cant tell if i am doing something wrong or if this connection issue is causing the adb issue, like its another symptom. no one seems to eager to answer the adb questions i have put out there, so i am left scratching myhead and making posts like my famous "dang it!!!" posts.

 

[gunnermike53]

It's been a LONG time since the last time I played with Open Suse, but I have a little Linux storage/print server I set up, and found Ubuntu to be the most user friendly and have the most driver support of all the distros I tried out - (Ubuntu, Fedora, Debian).



Connect the phone and the following in a command prompt:

adb shell
dmesg > /sdcard/dmesg.txt

It'll write out a text file to your SD card with what appears to be a bunch of logs.

GOT IT!!!!! dont know if anyone has mentioned this but dont mount the sdcard when using adb. just decided to try some basic trouble shooting, run the command with the card mounted and when that didnt work i unmounted and tryed it again.

 

[Chris3D]

GOT IT!!!!! dont know if anyone has mentioned this but dont mount the sdcard when using adb. just decided to try some basic trouble shooting, run the command with the card mounted and when that didnt work i unmounted and tryed it again.

Ahhh, yea, if the card is mounted in Windows, the phone can't access it...

Which makes me wonder - might the problem be a mount issue? Maybe the card being inaccessible when connected (when the problem is active) is because Android has it mounted and is refusing to unmount it and turn over control to the host OS.

To try it out, reboot the phone untethered so the problem arrises, connect it to the computer and try to open whatever comes up in Windows, you say it shows up as a CD drive - try to open it. See if the option in the notification tray appears letting you mount the SD card to copy files.

Then open up My Files, Root Explorer or even just the gallery and see if you still have access to the SD card from the phone. The more I think about it, the more it seems like a mount problem - it could be mistakenly mounting some other file system, and Windows just happens to see it as a CD drive.

 

[gunnermike53]

Ahhh, yea, if the card is mounted in Windows, the phone can't access it...

Which makes me wonder - might the problem be a mount issue? Maybe the card being inaccessible when connected (when the problem is active) is because Android has it mounted and is refusing to unmount it and turn over control to the host OS.

To try it out, reboot the phone untethered so the problem arrises, connect it to the computer and try to open whatever comes up in Windows, you say it shows up as a CD drive - try to open it. See if the option in the notification tray appears letting you mount the SD card to copy files.

Then open up My Files, Root Explorer or even just the gallery and see if you still have access to the SD card from the phone. The more I think about it, the more it seems like a mount problem - it could be mistakenly mounting some other file system, and Windows just happens to see it as a CD drive.

yeah, ben there done that. the phone shows up as a cd rom. you open it and it has the phone drivers and bootstrap. the phone cant access the sd card cause it thinks its mounted. whats up with bootstrap???

 

[Chris3D]

yeah, ben there done that. the phone shows up as a cd rom. you open it and it has the phone drivers and bootstrap. the phone cant access the sd card cause it thinks its mounted. whats up with bootstrap???

Ok, well, it's a clue. If whatever shows up in Windows has drivers and bootstrap (in other words, files that aren't on your SD card), the phone is sharing the wrong volume or partition.

It might think it's sharing the SD card, and therefore preventing the phone from accessing it, but it's actually sharing something else.

 

[DroidXcon]

Ok guys so i have been flashing back and forth from DI01 and DJ05 all night, using my phone not my sisters....When i flash DJ05 i can access the phone and the SD card only when in debugging mode.

when i flash DI01 i can not access anything at all except for the drivers and bootstrap, when i open boot strap odin opens up so i guess thats what that is

Im at a loss...

 

[gunnermike53]

Ok guys so i have been flashing back and forth from DI01 and DJ05 all night, using my phone not my sisters....When i flash DJ05 i can access the phone and the SD card only when in debugging mode.

when i flash DI01 i can not access anything at all except for the drivers and bootstrap, when i open boot strap odin opens up so i guess thats what that is

Im at a loss...

aw, you broke your phone for us. thanks xcon. personlaly i would have continued with my sisters, or better yet with my sister in laws, i dont like her anyway she is a selfish brat. oh well i can always dream.

if you plug your phone into your pc with debugging on and restart you phone you should be able to access your sdcard. also everyone should make sure you send adrylyne your dmesg.txt.

 

[gunnermike53]

Ok, well, it's a clue. If whatever shows up in Windows has drivers and bootstrap (in other words, files that aren't on your SD card), the phone is sharing the wrong volume or partition.

It might think it's sharing the SD card, and therefore preventing the phone from accessing it, but it's actually sharing something else.

yeah, that a good thought about sharing the wrong volume. that sounds right. i just wish i knew what to do about it. lol

 

[abowlofsoda]

aw, you broke your phone for us. thanks xcon. personlaly i would have continued with my sisters, or better yet with my sister in laws, i dont like her anyway she is a selfish brat. oh well i can always dream.

if you plug your phone into your pc with debugging on and restart you phone you should be able to access your sdcard. also everyone should make sure you send adrylyne your dmesg.txt.

How do I make a dmesg.txt from Windows? lol

 

[DroidXcon]

Ok to add to the strangeness, i plugged in my phone at work via usb debugging and nothing,,,,,i shut off usb debugging , mounted and there it is. This is just wacky now lol

 

[gunnermike53]

How do I make a dmesg.txt from Windows? lol

check out the "phone shows up as cd rom" thread. the last two of three thread give you the commands. you need to have adb installed.

 

[DroidXcon]

check out the "phone shows up as cd rom" thread. the last two of three thread give you the commands. you need to have adb installed.

and if you are having trouble with getting adb working download this
and just put the commands directly in

Android Terminal Emulator - Android app on AppBrain

 

[gunnermike53]

and if you are having trouble with getting adb working download this
and just put the commands directly in

Android Terminal Emulator - Android app on AppBrain

oooooo. neato!!

wait a minute. you mean you dint acutally have to install adb, you can just run that emulator?!?!?!?!?!

 

[DroidXcon]

oooooo. neato!!

wait a minute. you mean you dint acutally have to install adb, you can just run that emulator?!?!?!?!?!

yeah, just run the commands without starting them with adb shell

 

[gunnermike53]

yeah, just run the commands without starting them with adb shell

you mean i didnt have to go through all that crap to install adb and i dont even need it!?!?! can this do all the stuff adb can?