Related
ok, trying to install one-click root on my Epic, i have up-to-date drivers installed, USB debugging is checked, my computer gives me the option to mount and it reads my device. when I go to the run.bat command screen, I keep getting the message 'cannot locate device, unplug USB, re-plug and press enter.' when I do that I get 'aborting script, phone still not connected' message. can anyone point me in the right direction or tell me what I'm missing, any help would be greatly appreciated.
VB561 said:
ok, trying to install one-click root on my Epic, i have up-to-date drivers installed, USB debugging is checked, my computer gives me the option to mount and it reads my device. when I go to the run.bat command screen, I keep getting the message 'cannot locate device, unplug USB, re-plug and press enter.' when I do that I get 'aborting script, phone still not connected' message. can anyone point me in the right direction or tell me what I'm missing, any help would be greatly appreciated.
Click to expand...
Click to collapse
Try to do a battery pull on the phone and try that. If that does not work, do a battery pull and reset your computer and see if that helps.
Not sure what OS you are running but the best thing is to do on Win XP.
dito33
Can you tell us the complete verbage of the error? I ran into a problem because I did not LITTERALLY UNZIP the rar file before running it. Kept saying the phone was not connected..but when I looked closer it was failing because the bat file was trying to run a piece of the program and for some reason it was failing on it. COMPLETELY AND LITTERALLY unzipped the rar to my computer and then ran it (making sure the phone was connected and in usb debug mode) and was rooted in a matter of minutes. hope this helped a little... good luck
Sent from my SPH-D700 using XDA App
Try plugging the Epic into a mobo usb port.
VB561 said:
ok, trying to install one-click root on my Epic, i have up-to-date drivers installed, USB debugging is checked, my computer gives me the option to mount and it reads my device. when I go to the run.bat command screen, I keep getting the message 'cannot locate device, unplug USB, re-plug and press enter.' when I do that I get 'aborting script, phone still not connected' message. can anyone point me in the right direction or tell me what I'm missing, any help would be greatly appreciated.
Click to expand...
Click to collapse
Your computer gives you an option to mount? If you have ADB debug enabled you should see something pop up in your device manager, but I'm not so sure you should get any kind of mounting pop-up.
Make sure you have all of the correct drivers installed for your OS, and try it again running each command seperately from the batch file. Then post here which command is coming back unsuccsessful so I can pinpoint the problem better.
Sent from my soon to be 1.6ghz Epic 4G
thanks very much for the responses guys, the battery pull (along with restarting my computer about 4 times) finally got it to do its thing. don't know why it had to be such a pain but i'm just glad i got it to work. again, thank you all kindly for input.
Sent from my rooted SPH-D700 using the internets
I am having the same problem now for an hour or so. Tried everything I can think of , tried the all in one clockwork , used a different cable....i can hear my computer make that sound when I plug the phone in , and also when I unplug it. Just trying to get clockwork on here , ive read and read and read all the threads I can find. Got good drivers , windows xp. Rebooted laptop and phone at least 20 times ...dont know what else to try
Sent from my SPH-D700 using Tapatalk
Look in your device manager on your pc while your phone is connected with usb debugging and make sure there is no question mark next to Android ADB device. It needs to recognize this driver for it to connect.
HI
Hi i had that same issue an i went to the samsung official website becaue my phone can't connect to my pc i couldn't see my sd card pop up so the guy say my phone was defective so im thinking you have the same issue as me but samsung is fixing my phone now for free an free shipping i hope you still have warranty on your epic an they flashing a new rom an software on it for me they say to fix gps an wifi issues i had too
Got it to work, it was a driver issue apparently. Downloaded drivers again, completely removed old drivers. Reboot PC, make sure phone isnt connected yet. After reboot, install drivers, reboot again. I also had my phone turned off this whole time. When PC came back up , turn phone back on, connect using one of the main USB ports, not one in the front or anything. You should see windows detect and install the software. Then I ran the all in one clockwork , and here I am now fully rooted, syndicate rom , so much better than stock...hope you get it working! I definitely almost gave up a few times
Sent from my SPH-D700 using XDA App
just quickly, i get my phone in fastboot mode, connected it to pc, nothing pops up to install drivers, and when i try to flash cm7 to it it hangs on "waiting for device" so im pretty sure i just gotta install the drivers, i have the driver files but i do not know where to place them or how to install them. anybody help?
ok, sorry for double posting here but i need my question answered and nobody is saying anything. i thought that it would be better to double post than to make a thread exactly the same... so anyone know what directory the drivers go in? on windows XP. thanks.
Well I finally rooted my sidekick and went to backup the stock rom via rom manager and it rebooted and never got past t mobile sidekick boot screen so I downloaded odin the pit file and the tar but when I put my phone into download mode i cant get it to recognize the sidekick when I plug it in it just says unknown device and i have the driver down loaded any help please
Windows can be picky about drivers sometimes.
I recommend uninstalling the driver, opening regedit, and manually deleting any remaining registry keys associated with the Samsung drivers. (This will take you some time.)
After that, reinstall the driver and try again.
I think you may need to google some of what I said here to get it done. But, you can do it if you take some initiative.
well i tried deleting kies and reinstalling it whitch i thought it was the driver if im wrong or theres a more direct driver can someone tell me when i plug my sidekick in i get usb device not recognized message
uncapj said:
well i tried deleting kies and reinstalling it whitch i thought it was the driver if im wrong or theres a more direct driver can someone tell me when i plug my sidekick in i get usb device not recognized message
Click to expand...
Click to collapse
Ok. Give me some information.
I need to know what you installed as a driver. I need to know what Odin you are using. I also need to know where you got your information; what threads did you search for and read?
Is Windows complaining when you plug the device in or is the Odin program just not seeing your device?
When we do get your device back, also consider the risk/reward here. These customs aren't really offering the earth shattering things you might be hoping for. We're geeks and we are splitting hairs when we talk about improvements. The truth is, the final official KJ2 is a reliable and stable OS on its own. (If it wasn't, developers would be basing their work on older versions.) It's just something to think about...
Anyhow, get some more info out here and we'll help you Odin back to stock. After that, it's up to you.
well i got a drive from softpedia as well as kies and i searched various forums and topics im using windows xp sp3 and odin 3 as well as got the pit and tar files from lins on this site i
windows is the one that wines when i plug the phone in it says unknown device and no drivers for device found
You should have downloaded a Samsung USB driver for Mobile Phones. At one point, we were using Vibrant drivers to access the phone. Did you get real Samsung drivers for this phone?
You do NOT want to use Vibrant drivers.
Also, let's not rule out a hardware problem.
If you are rough with your phone's USB port, you can bend/break a pin in there. You could have a bad port.
If your phone isn't working like a USB pin drive on any (and every) computer you try, you may have a problem.
You should also check your cable and the physical port on your computer.
i got the kies from the samsung web site it was under the sidekick model nuber and showed a picture of my phone also i believe the softpedia driver was probably the vibrant driver
FYI, Kies only works if can get booted. We won't be using it until we can get a proper recovery of some kind.
What is happening? Is it just sitting there and vibrating over and over? Or does it appear to be rebooting?
Does it keep showing the t-mo logo flashing on and off the screen? Or is it just sitting there vibrating?
If you seeing the logo and the device is rebooting, you must use the Odin tool. If it is just hung up in the boot process, you can use Android Commander to get into clockworkmod.
I'm going to upload you some files. I'll private message you a link to download them.
We'll close out our public discussion here.
Howdy folks!
I am working my way through a minor (?) technical difficulty.
Would appeciate any suggestions you folks can off this newbie along the way.
Earlier today, I made an absent-minded mistake. Tried to go to my stock Froyo kernel without undoing my voodoo/lagfix/ext/watchamacallit setup. Whoops. Bootloop. No recovery mode available.
So, I attempted to use the procedure described in [ROM] [2.3.6] Heimdall One-click Back-To-Stock UCLB3 here:
http://forum.xda-developers.com/showthread.php?t=1524081
I’m in Windows 7.
I right-clicked on the Heimdall one-click program (Stock_SGH_I997_UCLB3_Repartition-One-Click), but there was no option to run as administrator. So I just double clicked it and it opened it (deviated from instructions on the first step...oh oh).
With the Heimdall one-click program now open, I put my phone in download mode and it indicated connected (perhaps in retrospect I connected too early)
I followed instruction on the PC program to install drivers, which it did (I already had Samsung drivers installed that I used successfully for SOC root program and for EFS Pro, I’m not sure what it was installing).
The pc program told me it needed to reboot. The phone screen said something about “dont’t shut off...”. I wasn’t sure what to do at that point, so I granted the pc permission to reboot.
PC rebooted, phone remains attached the whole time
Upon reboot, the Heimdall one-click program did not start up again.
So I double-clicked it and started it again.
The phone remained attached, but was not recognized as connected by the pc one-click program.
So I pushed 3 buttons on the phone to get it to turn off, then removed the batteries.
.
Then started pc Heimdal one-click program again. Then put my phone in download mode which it did successfully.
Then ran the flash and go the message “The FACTORYFS upload failed!”
(This occurred run without the checkbox about bootloaders)
At that point I checked the checkbox about bootloaders, and it came up with some scarey warning so I didn’t flash (probably should have).
I once again deenergized the phone (three-buttons, remove battery during the brief period it’s deenergized). Shut down pc heimdall one-click program.
Then started pc heimdall program.
Tried to put phone into download mode and received the following inauspicous message:
“Firmware upgrade encounted an issue. Please select recovery mode in Kies and try again”
Deenergized phone again. Shutdown pc program. Powered PC off. Restarted pc. Restarted Heimdall one click.
Tried to put the phone in download mode again and got the same error message.
I don’t know anything about selcting recover mode, not sure how to follow that instruction (any ideas?).
What I did next was search for the error message. It apparently has not been reported in the Infuse section, but I found two threads with this message discussed in the Galaxy S2 section.
“help” is the title of the first
http://forum.xda-developers.com/showthread.php?t=1189473
“Firmare upgrade encountered an issue - Am i done for?” is the title of the 2nd:
http://forum.xda-developers.com/showthread.php?t=1386232
There may be some more out there...
What I gathered was that I needed to remove my drivers.
I did remove the Sansung USG drivers in my control panel. I think these are the one’s I already had installed prior to me SOC root.
Rebooted.
Reinstalled drivers (filename SGH-i997_Infuse4G_USB_Drivers_5_2_0_2)
Restarted Heimdall one-click.
Put phone in download mode.
The same error message indicating that my phone has “issues”
Uninstalled my Samsung USB driver again.
Went back and looked at my control panel, there is another program. Keis. Uninstalled that. Rebooted.
Reinstalled SGH-i997_Infuse4G_USB_Drivers_5_2_0_2 driver
Reinstalled Kies_Mini_For_Captivate_11011_4.exe
Rebooted
Started the Heimdall one-click program.
Put phone in download.
Get the same error message on the phone (firmware upgraded encountered an issue...).
PC at this time thinks the phone is “connected”. So I clicked flash.
It proceeds to the next screen for driver installation.
I selected options / all / Samsung usb / Replace
PC Error message: Driver installation failed.
From those other threads, I’m pretty sure if I get my drivers straightened out I’ll be all right.
I don't know what I did wrong with the drivers... if anyone has a link with concise instructions for uninstalling/reinstalling the required drivers, maybe that would help me see if I've done something wrong.
Any other suggestions?
My java version is Version 6 Update 25
I have made a couple of change to this, a post I did for someone else today. You have done an excellent job of trying to resolve this- I hope this will be helpful.
There are a couple of things to point out:
Get Kies off your computer - it is a source of problems. Also means delete from recycle bin if there.
Download the Infuse drivers from bigjoe's ISET here: http://d-h.st/sKF
Thanks to bigjoe for an amazing page of resources !!
Be sure you have the latest version of Java here: http://www.java.com/en/download/index.jsp
Follow qkster's instructions he provides here:http://forum.xda-developers.com/showthread.php?t=1524081
Post 1 gets you back to stock- Post 2 gets root back.
Big thanks to qkster for doing this - saved many phones for countless number of users !! Me alone over a million times and counting
A video- no academy award nomination, but can be helpful : http://www.youtube.com/watch?v=sHyY7WHx4zc
Video is returning to Gingerbread.
You are willing to learn - therefore there will be many who are willing to help.
Take your time- do it right once and it will be easy next time !!
Heimdall uses it's own driver.
Once you install heimdall on one USB port of your pc, reserve that 1 port for going back. Also good to use that same USB cord.
The first part where it failed was because of bad connection. You just needed to change USB cord or change the port.
Read the heimdall thread and the how to thread a few times...
You could also use the froyo heimdall i put together for ucke3..see my sig link
Thanks very much for the replies.
Updated java.
Uninstalled Kies and Samsung driver (SGH-i997_Infuse4G_USB_Drivers_5_2_0_2)
Rebooted.
Reinstalled Samsung driver from bigjoe's link (same file).
I think it asked me to reboot.
Started the PC Heimdall program.
Attempted to put phone in download mode, it says "Firmware upgrade encountered an issue....".
So phone is not recognizing PC.
But PC recognizes the phone as connected.
Press flash. It goes to next page... I list all drivers, there is nothing Samsung in there.
Disconnected phone. Shut down program. Removed drivers/rebooted / reinstalled Samsung driver
Started Heimdall.
Attempted download mode, same error message "Firmware upgrade encountered an issue..."
Tried flash anyway, the next screen list of devices still has no Samsung.
Oddly when I go back to the first pc screen and try plug/unplug the phone, the PC recognizes phone as connected/disconnected. But it doesn't recognize it on the 2nd page where it tries to install the driver. And the phone has never successfully entered download mode since the first one or two tries...I get this "Firmware upgrade encountered an issue with yellow triangle screen every time since.
All above was on a single USB. I then tried on two other USB's same result. I may try another PC tomorrow night after work.
And will review the qkster's thread again as well as the video link posted by Pony Express.
Will report those results...
For now my head hurts . Time to call it a day.
Thanks for all your help.
I definitely appreciate it.
post deleted by op
meaning of this error message?
deleted
I see there is one other current thread in this forum on similar issue
"stuck on screen with (phone)---!----(Computer) "
http://forum.xda-developers.com/show...rch+this+forum
I noticed one thing we had in common is we both had Kies installed at some time early in our process (now removed).
I have some questions about the meaning of this screen that appears on my phone when I attempt to get to download mode:
"Firmware upgrade encounted an issue. Please select recovery mode in Kies and try again"
The screen has a yellow warning triangle on it
Is that a common screen to see on your phone during this process ?
Does it represent download mode? (I don't think so, since I saw a different screen on my phone the first time I connected... but maybe that had something to do with Kies?)
Is there any point in even trying to flash/download drivers when I see that message?
If the opportunity presents itself, is it advisable to attempt flash with "download bootloaders checked" when this error message is present?
(* If these questions are answered by the video, then I apologize in advance. I don't have the opportunity to watch that video here from my work computer, but I am eager to get a head start so I can hit the ground running when I get home after work tonight).
electricpete1 said:
I see there is one other current thread in this forum on similar issue
"stuck on screen with (phone)---!----(Computer) "
http://forum.xda-developers.com/show...rch+this+forum
I noticed one thing we had in common is we both had Kies installed at some time early in our process (now removed).
I have some questions about the meaning of this screen that appears on my phone when I attempt to get to download mode:
"Firmware upgrade encounted an issue. Please select recovery mode in Kies and try again"
The screen has a yellow warning triangle on it
Is that a common screen to see on your phone during this process ?
Does it represent download mode? (I don't think so, since I saw a different screen on my phone the first time I connected... but maybe that had something to do with Kies?)
Is there any point in even trying to flash/download drivers when I see that message?
If the opportunity presents itself, is it advisable to attempt flash with "download bootloaders checked" when this error message is present?
(* If these questions are answered by the video, then I apologize in advance. I don't have the opportunity to watch that video here from my work computer, but I am eager to get a head start so I can hit the ground running when I get home after work tonight).
Click to expand...
Click to collapse
For the moment don't check the bootloaders. You will only need them for ICS and JB to get rid of rainbows in the recovery. A bootloader flash is practically the only thing that can brick our phone.
Is that "firmware upgrade.." screen the one with the pc!phone? It has been a long time since I soft bricked so I don't recall if it said that somewhere.
If heimdall is giving you issues, try Odin and see how it goes there.
Sent from my sweet & buttery Infuse
electricpete1 said:
I see there is one other current thread in this forum on similar issue
"stuck on screen with (phone)---!----(Computer) "
http://forum.xda-developers.com/show...rch+this+forum
I noticed one thing we had in common is we both had Kies installed at some time early in our process (now removed).
I have some questions about the meaning of this screen that appears on my phone when I attempt to get to download mode:
"Firmware upgrade encounted an issue. Please select recovery mode in Kies and try again"
The screen has a yellow warning triangle on it
Is that a common screen to see on your phone during this process ?
Does it represent download mode? (I don't think so, since I saw a different screen on my phone the first time I connected... but maybe that had something to do with Kies?)
Is there any point in even trying to flash/download drivers when I see that message?
If the opportunity presents itself, is it advisable to attempt flash with "download bootloaders checked" when this error message is present?
(* If these questions are answered by the video, then I apologize in advance. I don't have the opportunity to watch that video here from my work computer, but I am eager to get a head start so I can hit the ground running when I get home after work tonight).
Click to expand...
Click to collapse
Yes...that's represents download mode...just another form...heimdall should still work
Sent from my SGH-I997 using Tapatalk 2
Thanks to everyone. That is very helpful.
I have some more questions. I'm not trying to be nit-picky, but just want to make sure I understand exactly what is being said.
qkster wrote:
Heimdall uses it's own driver.
Click to expand...
Click to collapse
Does that mean we don't need the Samsung driver SGH-i997_Infuse4G_USB_Drivers_5_2_0_2 driver ?
Any guess whether it works better with or without it? I will definitely try without it, but if anyone knows a preferred configuration, that would be helpful so I can focus on changing other things.
qkster's how to:
2. If you have not used Heimdall, you will need to set up the driver for device recognition
Click to expand...
Click to collapse
As a clarification. I'm not sure precisely what that means. All I'm doing is starting the program, letting it load drivers on first screen, connecting the phone in download mode (with error screen), pushing flash which will hopefully get me to the 2nd screen where I select options/all/Samsung/Replace to set up the driver. Is this statement intended to say anything different?
qkster's how to:
6. If it did not work, you will have to put it back into DOWNLOAD mode and reflash a second time, with the FLASH BOOTLOADER box checked.
Click to expand...
Click to collapse
I take it that in my situation (with error message and no evidence of success in previous flashing, and going to GB) this is really only a last resort after all other options exhausted as per andros' suggestion above?
By the way, I'm going to keep trying to install the UCLB3 GB (vs Froyo), as long as the chance of success is the same on both.
qkster's how to
4. Click on the FLASH button. (In my opinion: I recommend that you do this in a safe environment. Do not disturb your phone will flashing this firmware. Turn off Antivirus. Do not run any other programs, upload/download/youtube/burning DVD etc)
Click to expand...
Click to collapse
I'm a little nervous about turning off my security program (a/v, firewall etc) since I haven't done that in years.
Have there been problems attributed to doing this with security enabled, or is it just a general suggestion to avoid interruptions from unexpected scans or pop-ups etc? (my security runs peacefully in background and never interrupts me unless I ask it)
If it's really necessary to disable security program, I'd feel better about keeping my internet disconnected for the duration that the anti-virus is off. Is there any problem created if the internet connection remains disconnected for the duration of this process?
electricpete1 said:
Thanks to everyone. That is very helpful.
I have some more questions. I'm not trying to be nit-picky, but just want to make sure I understand exactly what is being said.
Does that mean we don't need the Samsung driver SGH-i997_Infuse4G_USB_Drivers_5_2_0_2 driver ?
Any guess whether it works better with or without it? I will definitely try without it, but if anyone knows a preferred configuration, that would be helpful so I can focus on changing other things.
As a clarification. I'm not sure precisely what that means. All I'm doing is starting the program, letting it load drivers on first screen, connecting the phone in download mode (with error screen), pushing flash which will hopefully get me to the 2nd screen where I select options/all/Samsung/Replace to set up the driver. Is this statement intended to say anything different?
I take it that in my situation (with error message and no evidence of success in previous flashing, and going to GB) this is really only a last resort after all other options exhausted as per andros' suggestion above?
By the way, I'm going to keep trying to install the UCLB3 GB (vs Froyo), as long as the chance of success is the same on both.
Click to expand...
Click to collapse
Drivers: when you launch heimdall it will install its own custom drivers for whatever usb port its pluged into...so if you plug it into one of your ports in the front and run heimdal only the port the phone is currently plugged into will be effected by the new driver. the driver is only used when in download mode...so dont uninstall your current drivers
selecting device: i think you got it (if my memory is correct...) just launch and run heimdall with device connected in dl mode...when you get to installing drivers just go to options and choose list all...i cant remember the exact name the infuse shows up as though
Bootloaders: just flash the first time without it checked...if it doesnt go through then check it and flash again
Antivirus: i have never turned off my anti virus when using heimdall on any of my computers (one computer uses norton 360 premier, the other one uses avast free) i never had it conflict with the process...so just leave it on for now...and only turn it off if you are having problems...if your worried about viruses then disconnect from the internet when you turn off your anti virus -i dont think the heimdall relies on internet at all...well maybe for the drivers...so just dont turn anything off until after you get the drivers
EDIT: i have a frseh install of windows 7 on my dev computer that i havent used heimdal on yet...so ill run it and clarify the driver section...i dual boot both linux and windows...currently im near the end of a repo sync so as soon as that finishes ill boot into windows and run heimdal...in less then a half hour hopefully...
Thanks mg2195.
Very good info.
I have tried my Windows 7 PC and another windows Vista PC.
On both pc's I tried with drivers pre-installed on the pc and without. Reboots in between.
I also used two different cables and tried all usb ports that were available.
In all cases but one, the anti-virus/firewall was on and pc connected to internet
In one case I tried with anti-virus off and pc diconnected from internet.
In all cases (except for the first one or two at the beginning of this thread), here's what happens:
I start Heimdall, it takes me to the first Heimdall screen, which shows "device status" red/disconnected as expected.
I try to put phone in download. Get the error message screen on the phone (see subject line). The "device status" shown on the pc changes from red/disconnected to green/connected (as expected).
I Click flash.
It asks to run the program, I say ok, it takes me to the second Heimdall screen, where I select Options/List-all.
There is no samsung driver choice.
I close the selection window (click x in upper right hand corner), it takes me back to the first Heimdall screen.
Device status still shows green/connected on the first Heimdall screen.
If I press flash again, the experience at the second screen repeats without showing Samsung driver.
Before I go to the next configuration (next usb port or cord or whatever), I remove the phone and close out the Heimdall program.
The bootloader option is available to be checked in the first Heimdall screen, but I have not done it
I’m not sure if I explained before that I have not had a successful driver installation in that second Heimdall screen (since the first one or two attempts). Does this change fact change your suggestion about checking the flash bootloaders box?
electricpete1 said:
Thanks mg2195.
Very good info.
I have tried my Windows 7 PC and another windows Vista PC.
On both pc's I tried with drivers pre-installed on the pc and without. Reboots in between.
I also used two different cables and tried all usb ports that were available.
In all cases (except for the first one or two at the beginning of this thread), here's what happens:
I start Heimdall.
Try to put phone in download. Get the error message screen.
Click flash in the first Heimdall screen.
It asks to run the program, I say ok, it takes me to the second Heimdall screen, where I select Options/List-all.
There is no samsung driver choice.
I close the selection window (click x in upper right hand corner), it takes me back to the first Heimdall screen.
The bootloader option is available to be checked in the first Heimdall screen, but I have not done it.
I’m not sure if I explained before that I have not had a successful driver installation in that second Heimdall screen (since the first one or two attempts). In this circumstance, do you still think it’s ok to check bootloaders?
Click to expand...
Click to collapse
you should probably wait until you get the heimdal drivers installed...im still wating for my reposync to finish...for some reason the download slowed down to 200kb/s,,,so it could take a while...
but for the drivers do this
1) On the menu bar (Device,Options,Help) Click Options --> List All Devices
2) Under USB Device select “Samsung USB Composite Device”
if its not locating it then try differnt ports/cables...if still no then run as admin...rightclick or shift+rightclick...if still not showing up...maybe bad usb port on the phone?
Quick response... thanks again!
Bad usb on phone is certainly possible, but I've never had a problem with it before.
I can believe the pc usb port might be finicky. Because historically on my Windows 7 PC, every once in awhile when I insert a flash drive memory stick, it does not get recognized. I will see if I can try a 3rd computer.
Regarding "run as administator":
When I right-click on the file, I don't see any option for "run as administrator" in either my Windows 7 pc or my Windows Vista pc.
So I have just been double-clicking the file. I think the Windows Vista asked me if I trusted the program and I said yes. Windows 7 just launches it.
Maybe there's some setting I need to change somewhere in order to get this "run as administator" ....I will google that... tomorrow. Right now, my pillow awaits.
electricpete1 said:
Quick response... thanks again!
Bad usb on phone is certainly possible, but I've never had a problem with it before.
I can believe the pc usb port might be finicky. Because historically on my Windows 7 PC, every once in awhile when I insert a flash drive memory stick, it does not get recognized. I will see if I can try a 3rd computer.
Regarding "run as administator":
When I right-click on the file, I don't see any option for "run as administrator" in either my Windows 7 pc or my Windows Vista pc.
So I have just been double-clicking the file. I think the Windows Vista asked me if I trusted the program and I said yes. Windows 7 just launches it.
Maybe there's some setting I need to change somewhere in order to get this "run as administator" ....I will google that when I get a chance.
Click to expand...
Click to collapse
Did you try holding shift while right clicking?
Sent from my SGH-I997 using Tapatalk 2
electricpete1 said:
I take it that in my situation (with error message and no evidence of success in previous flashing, and going to GB) this is really only a last resort after all other options exhausted as per andros' suggestion above?
Click to expand...
Click to collapse
Thanks for pointing out the imprecise grammar, Pete.
I corrected the op.
Recheck step 6 and 7.
To get heimdall to install its drivers, Zadig, you need the initial Samsung Android drivers. so when you pull down the zadig menu, Samsung Adroid device should show up.
Then reboot the PC.
Then try connect in dl mode again.
You had it at some point...
Thanks all.
That is now very clear qkster. (Actually it was reasonably clear before and I was pretty sure I knew what you meant, but just wanted to double check in case I was misunderstanding something)
I've had some trouble running as administrator, apparenlty others don't
Here's my difficulties and how I resolved it (I think):
DIFFICULTIES IN RUN-AS-ADMINISTRATOR.
If I right-click on an executable file (anything.exe), I get option to run as administrator. Great.
If I right click on a jar file (like the one I'm trying to run), no such option. Sad.
Same thing with short-cuts.
If I right-click on shortcut to exe, I can choose compatibility tab and select run as administrator. Great.
If I right-click on shortcut to jar, there is no compatibility tab. Sad.
HOW I RESOLVED RUN-AS-ADMINISTRATOR (I think)
I found some instructions for specifically for running jar as administrator here:
http://stackoverflow.com/questions/...r-with-administrators-privileges-on-windows-7
Specifically, click start, type cmd in the window just above start, right-click on the cmd result, and click "run as administrator.
That takes you to an elevated command prompt with the word administrator in the window heading.
Navigate to the directory and type
java -jar myfile.jar
where myfile is your file name (I renamed it to shorter name to make it easier).
RESULT:
I was able to launch Heimdal from the elevated command prompt.
Unfortunately, results have been the same thus far when using Heimdall launched from elevated command prompt as the previously reported results.
QUESTION: is there any way to check the program truly has admin priveleges?... it didn't ask any permission when launching Heimdall from the elevated command prompt.. the only permission asked was when launched cmd from the windows start menu screen.
I will repeat a few of yesterdays trials.
If those are unsuccessful, I think next step is trying GTG's package with ODIN.
QUESTION: Is there any way to clear any settings loaded into the USB ports by the Heimdall so they don't interfere with ODIN?
For Odin, just install the drivers you see at the iset page or kies drivers.
If you had a pc, one user when you log on, it is auto assume admin.
You can also go to control panel, users, look at privileges
So after trying to find a straightforward guide for installing the USB drivers for my OPO, almost every link says to use the OnePlus One toolkit, so I followed the 'manage drivers' section of the toolkit but for some reason, whenever I come to use my phone with my PC, the drivers seem to wipe themselves out! After I've done the initial driver installation, everything works fine, but after a day or 2, when when I plug my phone in, it will show 'unknown device' or it will show 'A0001' but with an exclamation mark next to it in the device manager and my phone isn't recognized. I'm using windows 7 x64 and the original red OPO cable.
I must be doing something wrong with these drivers, does anyone have a guide for deleting old drivers and reinstalling drivers for the OPO?
Edit: Ive reinstalled them again using the toolkit guide but I dont know if they will keep again, either way, im flashing blisspop now, maybe its an issue with 5.0 stock rom or something?
donk165 said:
So after trying to find a straightforward guide for installing the USB drivers for my OPO, almost every link says to use the OnePlus One toolkit, so I followed the 'manage drivers' section of the toolkit but for some reason, whenever I come to use my phone with my PC, the drivers seem to wipe themselves out! After I've done the initial driver installation, everything works fine, but after a day or 2, when when I plug my phone in, it will show 'unknown device' or it will show 'A0001' but with an exclamation mark next to it in the device manager and my phone isn't recognized. I'm using windows 7 x64 and the original red OPO cable.
I must be doing something wrong with these drivers, does anyone have a guide for deleting old drivers and reinstalling drivers for the OPO?
Edit: Ive reinstalled them again using the toolkit guide but I dont know if they will keep again, either way, im flashing blisspop now, maybe its an issue with 5.0 stock rom or something?
Click to expand...
Click to collapse
I had similar issue with lollipop ROMs, didn't find any solution except flashing fastboot images of CMOS12 or simply downgrading to CM11S.
Mr hOaX said:
I had similar issue with lollipop ROMs, didn't find any solution except flashing fastboot images of CMOS12 or simply downgrading to CM11S.
Click to expand...
Click to collapse
Fair enough, well i'm thinking I may move back to CM11S if things don't work out on Blisspop. If I turn off USB debugging and then switch to camera (PTP) mode and then back to MTP mode, my phone then connects fine. I wanted it to connect so I could copy my Titanium backup files off the phone and onto the PC. In the end, my mate told me about Airdroid and I managed to download them through that as a ZIP file. For some reason, the titanium backup folder isn't visible from your computer, I tried copying it to the DCIM folder and it just gave me a 1kb file. I also tried a new folder called backups and it was empty when I looked on my PC, but the files were visible when using Airdroid and also when I used a file browser on my phone.
Weird stuff!
Just wanted to bump this and see if anyone has a solution or even just an explanation.
Whenever I plug my OPO into my PC (with the original cable), the device, A0001 is found but is shown in Device Manager with an exclamation point. If I then right click on it and chose uninstall, and then reconnect the phone, it will connect and work fine for MTP/PTP modes. If I put USB debugging on, the MTP doesn't always work after. But no matter what, if I shutdown my PC, and then come to connect the phone the next day etc, I have to do the uninstall of the driver then reconnect for MTP to work. Pretty frustrating!
Anyone know why the phone isn't remembered by my PC correctly? I'm on Windows 7 x64 if that means anything.
I'm moving back to stock ROM soon so I'll see then if its something to do with the unlocked bootloader or using a custom ROM. I'll report back if I have any luck
Bumping this again, its still the same on 6.0. I don't fancy moving back to stock ROM, I like CM over Cyanogen OS, but this problem is really frustrating. Every single time I connect the phone to the PC, it will come up as A0001 but with an exclamation mark next to it in Device Manager, if I right click and uninstall the driver, then reconnect the phone, it works fine then. But if I restart my PC, it does the same thing where it cant find the right driver for the phone.
Is there anything I can try to fix this?