alright. i will have to set up a dual boot tonight. i think i have vista 32 bit somewhere. what do you think about my theory?
Downgrading from DJ05/DL09 on fascinate
- Thread starter Chris3D
- Start date
alright. i will have to set up a dual boot tonight. i think i have vista 32 bit somewhere. what do you think about my theory?
alright. i will have to set up a dual boot tonight. i think i have vista 32 bit somewhere. what do you think about my theory?
Lol the dang it one, lol i think it actually has some merrit
I have access to both types of systems but I did not load DI01 in the one part flash back on the phone... I am hoping I can stay with DJ05, regardless of the "Update"... I can do everything with my phone as it stands now.
Now if there is some special magic pixie dust event that happens with the update and I have to go back to DI01 to get it - I will use the process described in this thread - I hope.
Keep us informed of your success gunnermike53!
Now if there is some special magic pixie dust event that happens with the update and I have to go back to DI01 to get it - I will use the process described in this thread - I hope.
Keep us informed of your success gunnermike53!
Problem is even if he doesnt get it running through this flash doesnt mean this will happen for other people, we need to find the common denomitor and so far its 64bit
Doesn't happen all the time then, I'm running Win7 x64 and even though I only did the Odin package once, it didn't cause it to lose usb connectivity.
Someone on XDA seemed to suggest he flashed with the all-in-one package and ran into the problem, flashed again with the all-in-one and the problem went away.
I suppose for the people with the problem, it's worth trying to reflash it... can't make things any worse. Well, I guess there's always the chance it can, but it might be worth a try.
i flashed a second time. restored to nandroid. reflashed again.
just finished installing win7 x86 on a partition on my laptop. im gonna download all the stuff and give it a try.
no go!!!!!!! i did the all in one and have the same results. what the heck is bootstrap doing on there? isnt that for droid x? why is it on my samsung cd rom?
gonna try flashing three parts. will let you know.
gonna try flashing three parts. will let you know.
It's a shot in the dark, but there's also an all-in-one DJ05 package here: http://forum.xda-developers.com/showthread.php?t=885262
It doesn't include quite as much as in the DI01 package (it's missing the boot.bin, moveinand.bin, param.lfs, and sbl.bin), but includes everything else.
Maybe you could try flashing that to upgrade everything to DJ05 and then use the separate parts to downgrade back to DJ01. Like I said, it's a shot in the dark.
Sorry I can't help more than this, I can't test any of these or any other ideas myself because I don't have the problem, and I'm not going any closer to these all-in-one packages than I already have (flashing the modem from DI01).
ok. so i through on win 7 x86 on a partition. installed drivers. did the all in one with the same results. then i tried with the three part method and the result is:
dang it!!!!! dang it!!!!! dang it!!!!!eeeeeeeeeeeeerrrrrrrrrrr!!!!!!!! stupid dumb @#*&^@# dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dumb crappy $%@&##!!!!!!!!!!!!!! dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!
dang it!!!!! dang it!!!!! dang it!!!!!
eeeeeeeeeeeeerrrrrrrrrrr!!!!!!!! stupid dumb @#*&^@# dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dumb crappy $%@&##!!!!!!!!!!!!!! dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!dang it!!!!!Here's a question: What version of Odin are you using? Maybe the problem isn't in Windows or with the drivers, but with Odin itself.
I find it hard to believe its a corruption problem. Corrupt things tend not to work - at all, not just sporadically. The reboot workaround shows that everything does, indeed, work, just not all the time. And with some having used the all-in-one package and not having problems at all, the problem itself is sporadic. You ruled out the version of Windows (at least 32/64), what about Odin?
I find it hard to believe its a corruption problem. Corrupt things tend not to work - at all, not just sporadically. The reboot workaround shows that everything does, indeed, work, just not all the time. And with some having used the all-in-one package and not having problems at all, the problem itself is sporadic. You ruled out the version of Windows (at least 32/64), what about Odin?
i am using 1.3. what is the latest?
we havent ruled out x64 yet. i had the problem and THEN tryed on an x86 system. we need a guinee pug.., i mean volunteer who has never used the all in on to try it on an x86 system, see what happens and then on an x64 system. just because mine didnt start working doesnt mean i would have gotten the problem if i had started on x86. am i making any sence??
i aggree with you, we are missing something. good thought on the odin version.
Ok so i was able to replicate the problem, i used my sisters phone to flash DI01.... then by accident i decided to flash superdark, but forgot it was DJ05 based, so after it was flashed i decided to flash the modem. and bam no USB support So i have officially knocked out the 64bit theory and the full package theory..... So it looks like flashing DJ05 modem individually can cause this problem in some fascinates...ill spend the night looking for a solution
Edit: ok i got the phone USB working again,,,While connected in USB debugging. download and install.
October 27th drivers from this site.
https://forums.androidcentral.com/e...t%2Fdownloads%2FSCH-I500RKAVZW&token=DsW9nPQa
Wait about approx 5 minutes while the drivers configure themselves after installed. thats how long it took for me ,
I dont know if this will work for you , but it worked for my sisters fascinate after completely not recognizing the phone at all
Last edited:
no go. dang it!! i was hoping. did you restart her phone and try plugging it in again?
no i plugged it in wasnt getting any response no matter what i did, so i just kept playing with drivers and that one took try the other two on that site. it just worked after a couple mins like i said
it will work fine until i restart my phone. then it shows up as a cd rom. so i have to restart my phone plugged in, once it restarts i mount the card and it works fine until the next phone restat, when i have to do it all over again.
I am wondering if DriodXcon had pared it down to the flashing of the modem for DJ05 - that created the issue for him and he could back out of using (newer/other)drivers.
I think he is onto something. I had to uninstall the drivers from my Win7/64 system, and reinstall twice before I could get Odin to work properly. Had to go in and strip out the Samsung drivers for my wife's phone and the supporting software.
Not suggesting any course of action. I just know that the other drivers and software were confusing the connection with my phone with my wife's.
I think he is onto something. I had to uninstall the drivers from my Win7/64 system, and reinstall twice before I could get Odin to work properly. Had to go in and strip out the Samsung drivers for my wife's phone and the supporting software.
Not suggesting any course of action. I just know that the other drivers and software were confusing the connection with my phone with my wife's.
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.
im gonna try open suse. ive been wanting to play around linux. this is as good as an excuse as any. i will just format over the 7 x86 partition.
adrynalyne asked for dmesg from those having the problem, does any one know how to do that?
adrynalyne asked for dmesg from those having the problem, does any one know how to do that?
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.
Similar threads
Facebook
Twitter
Instagram