[FIX] Stuck at S/W Upgrade, Running Windows 7 64bit - T-Mobile LG G2x

I posted this in another thread, but created this new one specifically for these users that are having this issue and can't solve it because they don't have access to an XP machine.
I solved my issue late last night. I am running Windows 7 64bit. I saw that a lot of the guys here used XP to run the KDZ flasher and that wasn't an option for me until I installed XP Mode.
XP Mode allows you to run a virtual XP machine inside Windows 7. I was able to run the KDZ flasher in there and successfully flashed the KDZ GB file to my phone.
You do need to flash stock recovery first. I tried unsuccessfully to flash the KDZ with CWM recovery installed. It would not work until I flashed stock recovery.
One other problem I ran into is, in XP Mode, you are "attaching" USB devices to the virtual XP session via a "stub USB driver." For some reason during the KDZ flashing process the USB modem driver for LG kept releasing from my session. What I did to counteract this was manual attach it each time it released. This was easy, but I had to stay on top of it until the flasher finished the job. I have two monitors so I had the "Devices and Printers" window open in Windows 7, and when I heard the ding indicating the USB driver had left the session, and saw the LG devices appear in the Devices and Printers window, I would just click attach on the USB pulldown in the XP session.
I know this sounds a little complex for some (and possibly vague), but once you get into the XP Mode session you will see what I'm talking about.
I hope this helps you guys still stuck on SW Update screen that don't have XP.

hey guys whats up
i lost my nerves for 2 days tr5ying everything to bring back to life my P990..
since im huge noob with android i messed up everything when i tried to update phone with cm7. anyway i can bring it back to life with rom for p999 and thats it...
all other techniques dont work. cant even boot phone or whatever.. tried smartflash but i dont get anything what should be automaticaly assigned.. like communication driver..com port etc. i wanted to try kdz but this file cant be downloaded..its forbidden on lg site and now it cant be downloaded on megaupload. can i download file from somewhere else? im really pissed off cuz im stuck like this. please help

http://forum.xda-developers.com/showthread.php?t=1056847
And if you have a P990, you're in the wrong forum (this forum is for the P999).

omerika.emir said:
hey guys whats up
i lost my nerves for 2 days tr5ying everything to bring back to life my P990..
since im huge noob with android i messed up everything when i tried to update phone with cm7. anyway i can bring it back to life with rom for p999 and thats it...
all other techniques dont work. cant even boot phone or whatever.. tried smartflash but i dont get anything what should be automaticaly assigned.. like communication driver..com port etc. i wanted to try kdz but this file cant be downloaded..its forbidden on lg site and now it cant be downloaded on megaupload. can i download file from somewhere else? im really pissed off cuz im stuck like this. please help
Click to expand...
Click to collapse
The Roms for the p999 and the p990 are not inter changeable. Different frame work.

jrfaulkin said:
I posted this in another thread, but created this new one specifically for these users that are having this issue and can't solve it because they don't have access to an XP machine.
I solved my issue late last night. I am running Windows 7 64bit. I saw that a lot of the guys here used XP to run the KDZ flasher and that wasn't an option for me until I installed XP Mode.
XP Mode allows you to run a virtual XP machine inside Windows 7. I was able to run the KDZ flasher in there and successfully flashed the KDZ GB file to my phone.
You do need to flash stock recovery first. I tried unsuccessfully to flash the KDZ with CWM recovery installed. It would not work until I flashed stock recovery.
One other problem I ran into is, in XP Mode, you are "attaching" USB devices to the virtual XP session via a "stub USB driver." For some reason during the KDZ flashing process the USB modem driver for LG kept releasing from my session. What I did to counteract this was manual attach it each time it released. This was easy, but I had to stay on top of it until the flasher finished the job. I have two monitors so I had the "Devices and Printers" window open in Windows 7, and when I heard the ding indicating the USB driver had left the session, and saw the LG devices appear in the Devices and Printers window, I would just click attach on the USB pulldown in the XP session.
I know this sounds a little complex for some (and possibly vague), but once you get into the XP Mode session you will see what I'm talking about.
I hope this helps you guys still stuck on SW Update screen that don't have XP.
Click to expand...
Click to collapse
I'm running Windows 7 Home premium 64 Bit and Virtual XP Mode is not compatible with this version of Windows 7... Is there another way around this issue...???

Erocks said:
I'm running Windows 7 Home premium 64 Bit and Virtual XP Mode is not compatible with this version of Windows 7... Is there another way around this issue...???
Click to expand...
Click to collapse
VMware with XP on it/Google how to bypass limitation?
Found this to get Xp Mode on home edition idk if it works I just use VMware personally
http://m.tomshardware.com/news/windows-xp-mode-windows-7-win7,10213.html
Sent from my LG-P999

Related

I want my baby back!!!

Ok here's the story,
I had an older version of windows mobile, really buggy and kept freezing all the time. So I Figured let's upgrade to a newer version! YAY.... But that kinda failed miserably, and now my phone is stuck in bootloader.
I Tried the MTTY Stuff but that won't give an USB Port under ports.
I Tried flashing in bootloader mode but I kep getting Error 101 and 150, meaning wether it can't find the phone and if it can find it it tells me the rom version isn't right for me.
I'm really sure the rom version is right for me, and my windows Vista starts installing Mobile Device drivers as soon as I plug the phone in so that's connected and all.
Only it won't update. Took everything out too, no SD No sim .. nothing.
Anyone, please reanimate my phone
GWD said:
Ok here's the story,
I had an older version of windows mobile, really buggy and kept freezing all the time. So I Figured let's upgrade to a newer version! YAY.... But that kinda failed miserably, and now my phone is stuck in bootloader.
I Tried the MTTY Stuff but that won't give an USB Port under ports.
I Tried flashing in bootloader mode but I kep getting Error 101 and 150, meaning wether it can't find the phone and if it can find it it tells me the rom version isn't right for me.
I'm really sure the rom version is right for me, and my windows Vista starts installing Mobile Device drivers as soon as I plug the phone in so that's connected and all.
Only it won't update. Took everything out too, no SD No sim .. nothing.
Anyone, please reanimate my phone
Click to expand...
Click to collapse
"Windows Vista"..... uh huh
So it has been fixed, and yes I used windows Vista to do it... In your face vista uhuh guy!!!
I took the old windows XP drivers, deleted the vista one, installed the XP one, closed to device center, put it back on into boot mode.
Serial appeared, plugged in the USB and ran MTTY or something software. Selected USB that worked fine now
Typed the set 14 0 stuff pushed enter. shut down the program. and used the bootloader to install the latest and greatest Windows Mobile 6. All worked perfectly!!!!
So for the people with windows vista, just install the old windows XP drivers and you're ready to go, with out the loss of the latest technology
XP in Vista??
So, can you explain exactly how you installed the XP drivers into Vista... My Uni is pretty much the only reason I'm running a multi-boot system anymore!!
Any problems caused??
I tried to fight the Vista urge, but after having Ultimate installed on all the systems at work, I could fight no longer!!
GWD said:
So it has been fixed, and yes I used windows Vista to do it... In your face vista uhuh guy!!!
I took the old windows XP drivers, deleted the vista one, installed the XP one, closed to device center, put it back on into boot mode.
Serial appeared, plugged in the USB and ran MTTY or something software. Selected USB that worked fine now
Typed the set 14 0 stuff pushed enter. shut down the program. and used the bootloader to install the latest and greatest Windows Mobile 6. All worked perfectly!!!!
So for the people with windows vista, just install the old windows XP drivers and you're ready to go, with out the loss of the latest technology
Click to expand...
Click to collapse
i'll resist the urge to call you a "fool", but had you not put your foot in your mouth...i.e SEARCHED BEFORE WRITING...some one would have come to your help...
read this for upgrading in vista
http://forum.xda-developers.com/showthread.php?t=292631

A tale of Tilts, Macs, and Roms . . .

So, I tried to use Parallels (running windows XP) on my Intel Imac to flash a Kaiser Rom onto my AT&T Tilt. I'm currently stuck on the bootloader. I think I did find a solution, but I need to wait 10 minutes til I can download another Rapidshare file. In the meantime . . .
I think I did everything right. HardSPL worked fine, but then, when I tried to flash Dutty's Dual v4 ROM, it stopped at 6% and told me there was a communication error. I tried it a few more times, tried Dutty's Touchflo Rom (that got to 4%) . . . still no luck. Same error. In between each try, I reset using the stylus and sometimes the stylus while holding down power and camera.
Am I doing something wrong, or was my mistake trying to do this via parellels?
Current screen says:
KAIS1*0 MFG
SPL-1.0.OliPof
CPLD-8
USB
Thanks, guys.
I can confirm that if you install xp via boot camp then you can flash fine on a mac. I haven't tried going through an emulator such as parallels though. It should work fine though as long as parallels has taken over the usb ports.
Yeah, the USB connection wasn't the problem. And, unfortunately, I don't have extra XP licenses lying around to bootcamp. my mac.
Anyone have any idea? I'll give you a cookie . . .
By the way
It is error 262 that I'm getting . . .
I went through bootcamp boot as well, I rather assumed that I was going to need direct access to the hardware rather than the pass through of parallels...
btw you can set up parallels to boot a bootcamp partition... so you can use the direct boot and parallels from the same installation.
drewcopeland said:
It is error 262 that I'm getting . . .
Click to expand...
Click to collapse
I might have to look into that. My "solution" didn't work. I'm going to try to find the original ROM somewhere . . .
zenrandom said:
I went through bootcamp boot as well, I rather assumed that I was going to need direct access to the hardware rather than the pass through of parallels...
btw you can set up parallels to boot a bootcamp partition... so you can use the direct boot and parallels from the same installation.
Click to expand...
Click to collapse
I am using Fusion instead of Parallels but this is what I do. I only have 1 copy of xp installed via bootcamp but I can also access it through Fusion.
I also have fusion on my MacBook Pro, and it failed when tried to flash. So I bootcamp and started XP and it flashed flowlessly
If you own original XP CD (like me) you can always call microsoft to activate, and since it is installed in 1 PC then fine (you'll have 1 license for parallel & another for Bootcamp)
drewcopeland said:
So, I tried to use Parallels (running windows XP) on my Intel Imac to flash a Kaiser Rom onto my AT&T Tilt. I'm currently stuck on the bootloader. I think I did find a solution, but I need to wait 10 minutes til I can download another Rapidshare file.
Click to expand...
Click to collapse
Which version of parallels do you have? In version 5160 the usb flashing works fine, in 5582 it is broken, as is in version 5584. They had an special build 5582.5 which allowed me to flash my phone correctly and according to parallels, the "next" version will include those usb fixes.
I'm using the latest version 5584 and when I need to flash my phone, first i shut down windows vm, install parallels 5160 over the current version and then boot up windows. I ignore the installation of parallels tools and just flash my phone. Then shut down windows again, re-install parallels 5584 and all is fine again.
Hope this helps you...
that does. Do you mean the most recent update will work?
edit: never mind. the most recent is 5583. I'll try to find 5160
drewcopeland said:
Yeah, the USB connection wasn't the problem. And, unfortunately, I don't have extra XP licenses lying around to bootcamp. my mac.
Anyone have any idea? I'll give you a cookie . . .
Click to expand...
Click to collapse
If you have a valid license for parallels, then you have a valid license to use bootcamp...
That said, I have flashed through parallels and vmware fusion TONS of times (about to do it again, in fact). So long as you've routed the "HIGH GENERIC RNDIS" device to the virtual machine it should work fine.

windows 7 and windows mobile device center

Hi
Just for the fellas having problems when upgrading to a custom or signed ROM on the HTC FUZE on a computer with windows 7 and windows mobile device center.
you MUST be online at the time of installing a new rom
so the windows update downloads the " qualcomm cdma technologies msm" driver that recognizes your FUZE when windows mobile " is not present ".
I don't think I was connected when I did mine.
And that was flashing the Energy rom onto my Fuze.
I can't remember 100%, but I'm ~80% sure I wasn't. Maybe I just got lucky?
EDIT: Though that wasn't the first time I'd flashed. Maybe that was the differentiating factor.
alfmetal said:
Hi
Just for the fellas having problems when upgrading to a custom or signed ROM on the HTC FUZE on a computer with windows 7 and windows mobile device center.
you MUST be online at the time of installing a new rom
so the windows update downloads the " qualcomm cdma technologies msm" driver that recognizes your FUZE when windows mobile " is not present ".
Click to expand...
Click to collapse
i'm guessing this is the first time you're flashing for W7, the phone goes to bootloader mode and requires drivers that can be gained from Windows Update... after the first time, if you flash again using the same USB port, you'll be fine... using another USB port requires installing drivers again but you'll have the drivers saved in the windows folder
Is there some trick to get customruu.exe working?
Also i have problem syncing, i can only get it working if i disable fast data syncing.
I'm running latest energyrom and win7 ultimate x64 rtm
BigJayDogg3 said:
I don't think I was connected when I did mine.
And that was flashing the Energy rom onto my Fuze.
I can't remember 100%, but I'm ~80% sure I wasn't. Maybe I just got lucky?
EDIT: Though that wasn't the first time I'd flashed. Maybe that was the differentiating factor.
Click to expand...
Click to collapse
yeah, i think thats the difference, i was using a tmobile MDA with WM 5 like 2 years ago, and used to install custom roms but back in the time i had dsl so i never had a problem doing it.
so, BTW, how fast is the Energy rom?
the one i have looks nice but i feel is very slow
paperWastage said:
i'm guessing this is the first time you're flashing for W7, the phone goes to bootloader mode and requires drivers that can be gained from Windows Update... after the first time, if you flash again using the same USB port, you'll be fine... using another USB port requires installing drivers again but you'll have the drivers saved in the windows folder
Click to expand...
Click to collapse
i wonder if there is an offline mode to do this?, without an internet connection.
Daniehabazin said:
Is there some trick to get customruu.exe working?
Also i have problem syncing, i can only get it working if i disable fast data syncing.
I'm running latest energyrom and win7 ultimate x64 rtm
Click to expand...
Click to collapse
not that i know, but i have win7 32 bits version, so maybe its has something to do with the 64 version
It could be that there are no 64bit drivers for the phone available. I use Win7 x32 and it is a hassle getting it first sync'd up. What I normally do is just put the phone in bootloader mode before plugging in the USB cable. That way it only downloads the drivers it needs the first time.
Usually takes me a few resets of the PC and a couple Mobile Device Center restarts to get it to start ticking. Perhaps try downloading the latest Mobile Device Center, even if yours is the latest... just install over the existing installation. That's worked for me a few times.
Is it your first time flashing? Is it a newer Fuze? Because the latest Fuze's have a newer bootloader that is 1.95 (vs 1.90). I haven't found a way around it yet unless perhaps flash an official AT&T rom that has the 1.90 bootloader that may downgrade it... then HardSPL.
Just to add, windows 7 64bit here and haven't noticed one difference or problem with anything.
player911 said:
It could be that there are no 64bit drivers for the phone available. I use Win7 x32 and it is a hassle getting it first sync'd up. What I normally do is just put the phone in bootloader mode before plugging in the USB cable. That way it only downloads the drivers it needs the first time.
Usually takes me a few resets of the PC and a couple Mobile Device Center restarts to get it to start ticking. Perhaps try downloading the latest Mobile Device Center, even if yours is the latest... just install over the existing installation. That's worked for me a few times.
Is it your first time flashing? Is it a newer Fuze? Because the latest Fuze's have a newer bootloader that is 1.95 (vs 1.90). I haven't found a way around it yet unless perhaps flash an official AT&T rom that has the 1.90 bootloader that may downgrade it... then HardSPL.
Click to expand...
Click to collapse
Nah, had my raphael a long time, have flashed a couple of roms before, i'll try to put it in bootloader mode and let it install the driver, i'll keep searching for a customruu that works for 7 x64, Thanks for the reply
i got syncing working, uninstalled the driver for the mobile remote adapter, and let it download a new one from windows uppdate, and now it works, stange since it's the same driver as before...
I was having the same problem with windows 7 x64 and the fuze... found my solution elsewhere so i thought i'd post it here in case someone checks here first like me... I needed to install Windows Mobile Device Center to get the driver to work correctly with an active sync connection =)
I have W7 ultimate x64 and I can't flash either. But I don't mind. I just put the .nbh on the memory card, start up customRUU and it puts my phone in boot loader itself then installs the ROM off th ememory card.
even there's already a WMDC on win7, I tried to download it again from brothersoft, then it's update the driver..... done!
btw I'm using win7 x86, so I haven't tried on x64...
img707.imageshack.us/img707/3830/51947559.jpg
I can't post a pic or link...

[Kies] Crash on Win 7 x64 - Virtual PC work-around

So I had the dreaded Win 7 x64 crash. I uninstalled IE 9. No go. Used that DLL fix (which I can't remember where I found it). Still crashed. So here's how I got around the problem.
Note:
I'm just sharing what I found since none of the solutions I googled up worked for me (maybe I'm the only one). For those who wonder why anyone would bother with stock Froyo, I'm sure there are reasons. I just wanted to do some testing of the upgrade exactly as it came from Samsung. There's probably an Odin flashable package somewhere which may be bit-for-bit identical, but I didn't bother looking. I'm hoping this will work if another update comes down the pike (Ha!) and Kies is still broken.
Here's what worked for me. It may brick your phone so understand that before you start.
Step 1:
Load up Virtual PC.
In Virtual PC:
Install the Samsung drivers
Install Kies Mini
Install Samsung PC Studio (for Gadget Serial driver)
Step 2 - back to the phone:
Flash stock. I flashed one-click JF6, but use the right stock firmware for your phone (build 1010 and later phones should use something like this)
Step 3:
At this point you may want to make sure the Gadget Serial driver is loaded and working (if you one-click flashed JF6 skip to step 4), so put the phone into download mode and plug it into the PC.
In Virtual PC:
USB Menu->Gadget Serial Attach
Insure that driver is working. If it isn't then the update won't work because Kies Mini will not be able to communicate with the phone after it goes into download mode. If it works then skip to step 5. If not then do step 4.
Step 4:
Have CWM update.zip on you sdcard root directory
Reinstall packages
Reinstall packages again
Install zip from sdcard
Install sbl_CWM_update.zip (attached to this post)
Do the step 3 check. If that fails then the Gadget Serial driver isn't recognizing you phone and this isn't going to work unless you can fix it.
Step 5:
Reboot the phone, turn on USB debugging then plug it in to the PC.
In Virtual PC:
Start Kies Mini
USB->Samsung_Android Attach
Start the upgrade
Wait 12 years or so until the phone goes into download mode
USB->Gadget Serial Attach
The install should continue automatically. If it doesn't there is an upgrade button which should be enabled when driver is loaded and the phone is detected.
Wait for the install to finish, at which point to phone should boot into Froyo.
Done.
thanks
cool, i had tried all of the other ways of forcing kies to recognize my computer... but it always ended with the same crash, nice little white box where the program should be. so im trying this out but its taking forever to get xp virtual machine up and running. i will post again with my final results
ok now for my story
i have had flashed multiple versions of cognition on my phone and have become very familiar with the process. i do love cog 3.04 but the problem is that the swype that is loaded on the rom is a 60 day trial version and it ran out. so i wanted to try out the stock froyo and see what improvents i wanted so i could cook my own rom.
i went and got kies mini on the release date for froyo and it was crashing everytime i used it, giving me this lovely white box on my windows 7 x64 ultimate computer. i tried multiple work arounds and have never thought of virtual machine so thank you for that.
i want and ran my odin one click reflashed to jf6, then decided to see if kies recognized my phone. it imediately was recognized and started to update in the virtual machine.
it is currently downloading to my phone and i will repost again if my phone either becomes soft bricked or if the update goes through
Please help me find the Gadget Serial Driver for My Samsung Vibrant
I've been trying to Update my Samsung Vibrant from version KA2 to version KB5 using Samsung Kies mini to no avail. I am running Windows XP SP3.
I know, this is a developer site but I have a feeling I won't be able to develop at all because I when I try to update to (Official) Froyo (Provided through Kies mini), I get stuck in download mode with the yellow sign forever. Luckily I can restore by taking the battery out and rebooting my phone. This is problem is due to not having a Gadget Serial Driver installed. Now note, I have all the other USB drivers installed properly. They all show up in Device Manager, however the darn Gadget Serial Driver is MIA and Windows only notices that is missing the driver when the phone enters Download Mode. I have searched xda developers for this issue and I have seen a number of posts where other people have had the same issue and maybe a couple of people solved it by installing PC Studio. I have Googled up and down the internet, went to Samsung's website and even spoke to a Samsung Representative for a link to Samsung PC Studio. However all of the links I found were either dead, contained fake software or were just shady.
Samsung's site no longer contains an actual download link to PC Studio or New PC Studio (I don't know the difference). Can someone please help me get this Gadget Serial Driver or the PC Studio software which may solve this driver issue? Please don't point me to any "Samsung USB Drivers For Mobile Phones" links because I've downloaded that driver and it has solved nothing. Thanks in advance and sorry for sounding like a complete n00b.
privetKalla said:
I've been trying to Update my Samsung Vibrant from version KA2 to version KB5 using Samsung Kies mini to no avail. I am running Windows XP SP3.
I know, this is a developer site but I have a feeling I won't be able to develop at all because I when I try to update to (Official) Froyo (Provided through Kies mini), I get stuck in download mode with the yellow sign forever. Luckily I can restore by taking the battery out and rebooting my phone. This is problem is due to not having a Gadget Serial Driver installed. Now note, I have all the other USB drivers installed properly. They all show up in Device Manager, however the darn Gadget Serial Driver is MIA and Windows only notices that is missing the driver when the phone enters Download Mode. I have searched xda developers for this issue and I have seen a number of posts where other people have had the same issue and maybe a couple of people solved it by installing PC Studio. I have Googled up and down the internet, went to Samsung's website and even spoke to a Samsung Representative for a link to Samsung PC Studio. However all of the links I found were either dead, contained fake software or were just shady.
Samsung's site no longer contains an actual download link to PC Studio or New PC Studio (I don't know the difference). Can someone please help me get this Gadget Serial Driver or the PC Studio software which may solve this driver issue? Please don't point me to any "Samsung USB Drivers For Mobile Phones" links because I've downloaded that driver and it has solved nothing. Thanks in advance and sorry for sounding like a complete n00b.
Click to expand...
Click to collapse
This is for the flight II but the software has the PC Studio download. Good Luck!
http://www.samsung.com/us/support/downloads/SGH-A927ZAAATT
privetKalla said:
I've been trying to Update my Samsung Vibrant from version KA2 to version KB5 using Samsung Kies mini to no avail. I am running Windows XP SP3.
I know, this is a developer site but I have a feeling I won't be able to develop at all because I when I try to update to (Official) Froyo (Provided through Kies mini), I get stuck in download mode with the yellow sign forever.
Click to expand...
Click to collapse
Thanks man. That made my day. I needed that.
You can also get the Heimdall suite and open the drivers folder and run Zandig. Then connect your phone in download mode it should show gadget serial in the device window click install and it should complete and you're good to go, this is how I did it after 3 days trying to get my phone to stop showing the device malfunction error which is due to another problem on my main xp machine, a sony which I can't get usb 2.0 drivers for from sony or anywhere else to work correctly even though all 8 ports are 2.0 according to support, my manual, and previous xp install and that's after installing xp 4 times to get the graphics driver to install right so I could then install the right ati driver which everyone online with this model sony seems to have to do, but back on topic. I hopped on my windows server 2k3 machine which had correctly working usb 2.0 drivers ran zandig with my cappy in dl mode and BAM finally working gadget serial driver, just make sure you have zandig.exe open, and connect your phone in DL mode or you'll just install the equivalent of the standard samsung drivers which you prolly already have, I haven't been able to test this on a win7 machine but from what I've read the heimdall driver should work on them and worked great on both xp and server 2k3 on my home server machine.
Sent from my SAMSUNG-SGH-I897 using XDA App
Jsmokey said:
You can also get the Heimdall suite and open the drivers folder and run Zandig. Then connect your phone in download mode it should show gadget serial in the device window click install and it should complete and you're good to go, this is how I did it after 3 days trying to get my phone to stop showing the device malfunction error which is due to another problem on my main xp machine, a sony which I can't get usb 2.0 drivers for from sony or anywhere else to work correctly even though all 8 ports are 2.0 according to support, my manual, and previous xp install and that's after installing xp 4 times to get the graphics driver to install right so I could then install the right ati driver which everyone online with this model sony seems to have to do, but back on topic. I hopped on my windows server 2k3 machine which had correctly working usb 2.0 drivers ran zandig with my cappy in dl mode and BAM finally working gadget serial driver, just make sure you have zandig.exe open, and connect your phone in DL mode or you'll just install the equivalent of the standard samsung drivers which you prolly already have, I haven't been able to test this on a win7 machine but from what I've read the heimdall driver should work on them and worked great on both xp and server 2k3 on my home server machine.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Best first post I've seen in quite some time. Thanks for that.
boborone said:
Best first post I've seen in quite some time. Thanks for that.
Click to expand...
Click to collapse
Thanks I appreciate that I just wanna give back as much as I've received from the forums here its a great place to start. If anyone runs into any problem with this let me know and I'll see if I can reproduce and come up with something.
Sent from my SAMSUNG-SGH-I897 using XDA App

[Q] Download mode un-recognized

Windows 7 (x64)
Just got a Samsung infuse and i've had nothing but issues since the start. For starters. Im trying to go back to stock and start over. Ive tried odin and heimdall. ive tried at least 5 different driver packages. NOTHING will recognize the device. Ive tried different cables. different ports. Even different computers.
When I install any driver to it windows gives me code 10.
im about to throw this phone out the window
Are you using odin3.3?
Sent from my SAMSUNG-SGH-I997 using XDA App
You need to download Kies Mini inorder to obtain the drivers for your device 1st of all. Once the Drivers install it will recognize your phone that is plugged in as Samsung. The rest of the Software does completely nothing other than give us drivers, Once your finished with the drivers reopen Odin set all the options as needed Put your phone into Download Mode and you should see a Port # show up as either 3, or some other number as long as theirs a Port # then you can flash the Rom.
Ok so i FINALLY got the drivers correct. however, ODIN now hangs on 'setting up connection"
now what?
Ok. so i set compatibility in windows to vista sp2 lol now it works?
celljunkie707 said:
Ok. so i set compatibility in windows to vista sp2 lol now it works?
Click to expand...
Click to collapse
Previously, were you running it as Administrator? I believe that is required on Win7, but not on Vista (which I am running).
yea... i was running on admin every attempt. weird.
now im just trying to figure out why CWM wont see my external sd card.

Categories

Resources