Related
As the title says, Kies no longer sees/detects my phone. Did the sammfiles/rooted update to my phone via odin and Kies wouldn't see the phone. Wiped the phone and forced an update via Kies with model number/serial number and afterward Kies still would not detect my phone. Any ideas?
Edited to remove the "task rom" comment. Got my devices mixed up
TomH54 said:
As the title says, Kies no longer sees/detects my phone. Was using task's "fat" on my phone before and Kies detected my phone. Did the sammfiles/rooted update to my phone via odin and Kies wouldn't see the phone. Wiped the phone and forced an update via Kies with model number/serial number and afterward Kies still would not detect my phone. Any ideas?
Click to expand...
Click to collapse
Have you tried to turn off debugging in the development section?
Yeah. Tried that. It's no biggie tho since I can still force updates if needed. Thanks for the reply.
Removing/Freezing/Uninstalling/Disabling etc... bloatware causes Kies not to work.
Installing CWM also causes Kies not to work. Because, in short, CWM replaced the factory recovery
I find that if I plug my USB cable into different ports on the front of my computer I get different results.. Might be worth a shot to try if you have more than 1 to choose from.
"Device Not Supported by Kies 2.0"
I've a similar problem. I ran Kies yesterday for the first time since the ICS update back in April and it began to update to a new version. After which it says, "This device is not supported by Kies 2.0"?! I've uninstalled and re-installed about 8 times today even the Samsung USB drivers and nothing! What's going on?
Any help would be appreciated.
Thanks
E-Nigma said:
I've a similar problem. I ran Kies yesterday for the first time since the ICS update back in April and it began to update to a new version. After which it says, "This device is not supported by Kies 2.0"?! I've uninstalled and re-installed about 8 times today even the Samsung USB drivers and nothing! What's going on?
Any help would be appreciated.
Thanks[/QUOTE
it wouldn't work while i was rooted with gingerbread. i returned to stock and it worked fine. after that i was able to root after update thanks to creepyncrawly from this thread http://forum.xda-developers.com/showthread.php?t=1746181 and it works fine now. if you go this route make sure to read the whole thread first. you have to get another kernal before wiping or you can brick your phone. im using siyah-v3.4.3-nonswap by ktoonsez and so far so good. not sure if you have to update to ucle5 for it to work but thats what i did. i havent had a chance to try other roms. hope this helps a little
Click to expand...
Click to collapse
For me. This is what worked. First go into device manager (on computer obviously)and remove the phone drivers currently installed.Next turn off usb debugging. Then plug your phone in to a different usb port. Let it do it's thing. Unplug, turn on usb debugging, plug back in.Let it do it's thing unplug. Reboot into cwm recovery, plug in. Let it do it's thing. Unplug. Turn off usb debugging. Boot up phone. Plug in. Profit. At least this is what fixed it for me.Good luck. Happy flashing.
Sent from my SGH-I777 using Tapatalk 2
Alrighty, two problems I ran into trying to get ICS up and running.
Problem number one is what I call the infinite Kies update loop where Kies will ask you to update, you do all the steps, and Kies AGAIN asks you to update to the same version you just supposedly did. The software has to be current in order for Kies to perform the update. Now, there are two ways to go about it:
You can either edit the KiesVersion.txt and just type in the current version to 'fake' Kies out
OR you can download the latest build HERE:
downloadcenter.samsung.com/content/SW/201110/20111024092325174/Kies_2.3.2.12064_9_7.exe
Doesnt matter if you have another version installed or not, the installer will guide you through the process and uninstall the previous version. Takes about 5 minutes to install the whole deal.
Problem number two is getting Kies to actually recognize your device instead of just 'connecting' forever.
The way to get around this is the following:
Shut down Kies
Unplug your phone, then ON YOUR PHONE, go to settings>Wireless and Network>USB Settings and enable mass storage (Ill fix the wording on this shortly as my phone is currently updating but its only one option). After doing so, it will tell you that USB Debugging needs to be disabled (I think it will do this automatically), hit the Continue box and then plug your phone in. YOU DO NOT need to tap the Connect phone button under the little Android guy that appears on your phone screen. Now, let Windows install the driver.
NOW, unplug your phone and go to Settings>Applications> and enable USB Debugging (its the last option in the applications menu) and let windows install the driver.
Now, launch Kies and it should only take about 30 seconds to connect.
Note that your phone MUST be in USB Debugging for Kies to upgrade the firmware (which is why the last thing we did was enable USB Debugging, your phone will already be in USB Debugging mode).
Hope this helps
littlewierdo said:
Alrighty, two problems I ran into trying to get ICS up and running.
Problem number one is what I call the infinite Kies update loop where Kies will ask you to update, you do all the steps, and Kies AGAIN asks you to update to the same version you just supposedly did. The software has to be current in order for Kies to perform the update. Now, there are two ways to go about it:
You can either edit the KiesVersion.txt and just type in the current version to 'fake' Kies out
OR you can download the latest build HERE:
downloadcenter.samsung.com/content/SW/201110/20111024092325174/Kies_2.3.2.12064_9_7.exe
Doesnt matter if you have another version installed or not, the installer will guide you through the process and uninstall the previous version. Takes about 5 minutes to install the whole deal.
Problem number two is getting Kies to actually recognize your device instead of just 'connecting' forever.
The way to get around this is the following:
Shut down Kies
Unplug your phone, then ON YOUR PHONE, go to settings>Wireless and Network>USB Settings and enable mass storage (Ill fix the wording on this shortly as my phone is currently updating but its only one option). After doing so, it will tell you that USB Debugging needs to be disabled (I think it will do this automatically), hit the Continue box and then plug your phone in. YOU DO NOT need to tap the Connect phone button under the little Android guy that appears on your phone screen. Now, let Windows install the driver.
NOW, unplug your phone and go to Settings>Applications> and enable USB Debugging (its the last option in the applications menu) and let windows install the driver.
Now, launch Kies and it should only take about 30 seconds to connect.
Note that your phone MUST be in USB Debugging for Kies to upgrade the firmware (which is why the last thing we did was enable USB Debugging, your phone will already be in USB Debugging mode).
Hope this helps
Click to expand...
Click to collapse
You are the man! Thanks for posting this!
littlewierdo said:
OR you can download the latest build HERE:
downloadcenter.samsung.com/content/SW/201110/20111024092325174/Kies_2.3.2.12064_9_7.exe
Doesnt matter if you have another version installed or not, the installer will guide you through the process and uninstall the previous version. Takes about 5 minutes to install the whole deal.
Click to expand...
Click to collapse
Didn't work. I get caught in an endless loop where it keeps asking me to uninstall the previous version.
What do you mean "edit the KiesVersion.txt"?
bigmout said:
Didn't work. I get caught in an endless loop where it keeps asking me to uninstall the previous version.
What do you mean "edit the KiesVersion.txt"?
Click to expand...
Click to collapse
Ok, what you need to do is copy and paste the download link into a new tab in your browser. This should automatically give you a download dialog box (no need to browse a website). Download the app, its 90 megabytes and when it is done downloading, run it. Follow the on screen prompts.
This DOES work, I know, I did it on three different machines, all running Vista, XP, and Win7.
Alternatively, you can browse to where Kies is installed (C:\Program Files\SAMSUNG\Kies) and look for a file called KiesVersion.txt. Open this in Notepad and you will see one line at the top. Copy and paste the version number REPLACING whatever version is showing:
2.3.2.12064_9
(So you should have just one line showing the version number above).
Save and exit.
Note, if you choose the KiesVersion.txt method, Kies will not update correctly which is why I strongly recommend doing the first method first.
littlewierdo said:
Alrighty, two problems I ran into trying to get ICS up and running.
Problem number one is what I call the infinite Kies update loop where Kies will ask you to update, you do all the steps, and Kies AGAIN asks you to update to the same version you just supposedly did. The software has to be current in order for Kies to perform the update. Now, there are two ways to go about it:
You can either edit the KiesVersion.txt and just type in the current version to 'fake' Kies out
OR you can download the latest build HERE:
downloadcenter.samsung.com/content/SW/201110/20111024092325174/Kies_2.3.2.12064_9_7.exe
Doesnt matter if you have another version installed or not, the installer will guide you through the process and uninstall the previous version. Takes about 5 minutes to install the whole deal.
Problem number two is getting Kies to actually recognize your device instead of just 'connecting' forever.
The way to get around this is the following:
Shut down Kies
Unplug your phone, then ON YOUR PHONE, go to settings>Wireless and Network>USB Settings and enable mass storage (Ill fix the wording on this shortly as my phone is currently updating but its only one option). After doing so, it will tell you that USB Debugging needs to be disabled (I think it will do this automatically), hit the Continue box and then plug your phone in. YOU DO NOT need to tap the Connect phone button under the little Android guy that appears on your phone screen. Now, let Windows install the driver.
NOW, unplug your phone and go to Settings>Applications> and enable USB Debugging (its the last option in the applications menu) and let windows install the driver.
Now, launch Kies and it should only take about 30 seconds to connect.
Note that your phone MUST be in USB Debugging for Kies to upgrade the firmware (which is why the last thing we did was enable USB Debugging, your phone will already be in USB Debugging mode).
Hope this helps
Click to expand...
Click to collapse
Thanks man. Your method worked for me!:good:
littlewierdo said:
Ok, what you need to do is copy and paste the download link into a new tab in your browser. This should automatically give you a download dialog box (no need to browse a website). Download the app, its 90 megabytes and when it is done downloading, run it. Follow the on screen prompts.
Click to expand...
Click to collapse
Yeah, I did all that. I downloaded the installer and clicked on it. It started installing, then asked me if I wanted to uninstall the old version of Kies. I said yes, and it started uninstalling.
And... that's as far as I can get. After that, it loops back and keeps asking me if I want to uninstall the old version of Kies.
littlewierdo said:
Alternatively, you can browse to where Kies is installed (C:\Program Files\SAMSUNG\Kies) and look for a file called KiesVersion.txt. Open this in Notepad and you will see one line at the top. Copy and paste the version number REPLACING whatever version is showing:
2.3.2.12064_9
(So you should have just one line showing the version number above).
Save and exit.
Note, if you choose the KiesVersion.txt method, Kies will not update correctly which is why I strongly recommend doing the first method first.
Click to expand...
Click to collapse
I'll try this -- thanks.
bigmout said:
Yeah, I did all that. I downloaded the installer and clicked on it. It started installing, then asked me if I wanted to uninstall the old version of Kies. I said yes, and it started uninstalling.
And... that's as far as I can get. After that, it loops back and keeps asking me if I want to uninstall the old version of Kies.
I'll try this -- thanks.
Click to expand...
Click to collapse
Maybe try uninstalling the version you have before you install the one I posted. Might be a version problem (my version that I had installed might be newer/older than yours).
Thx...i finally got it working
Sent from my SAMSUNG-SGH-I717 using xda premium
FINALLY!!!!!! Thank you so much! Downloading the newest version you posted finally got rid of the infinite updating issue plaguing me.
BTW I uninstalled the old version first before installing the new one since im seeing issues with replacing also
Sent from my Galaxy Nexus using Tapatalk 2
29% about 40 mins way to slow to download.
Edit: Received a timeout error damn!!!!!!!
Sent from my SAMSUNG-SGH-I717 using xda premium
Thank you for the debugging tip! This worked when I used it regularly. However, as soon as I went into download mode, it started the infinite connecting again! Any idea what is up with that?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
My phone still won't connect
Sent from my SAMSUNG-SGH-I717 using xda premium
whittakerh said:
Thank you for the debugging tip! This worked when I used it regularly. However, as soon as I went into download mode, it started the infinite connecting again! Any idea what is up with that?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
It has to do with the bizarre way Windows handles drivers.
EVERY phone state has to have a different 'driver' installed, although technically, it is using the same driver for each phone state..
The Note actually has five states, Download mode (this is the mode you would put your phone into to 'Odin' anything to it), Recovery mode (Clockwork recovery menu), Debugging mode (turn on USB Debugging) - also known as ADB mode, Mass Storage, and Wifi Direct (useful for connecting to your PC's files or public files on your phone using your PC - requires the PC to have wireless capability). Due to the way plug and play works, any device connected to your PC must put out a 'ping' to tell the OS what it is (a device name). Samsung has opted to really confuse everything by reporting a different device name for all these different states rather than doing what most devices do, a recovery mode and a mass storage mode (two states instead of the 5 Samsung is using).
Installing the samsung note driver via kies is sufficient to cover all the different states (windows just duplicates the driver for each new state it has not detected previously) but in order to cover every state the phone can possibly be in, you have to plug in the phone while the phone is in that state (ie. plugging it in with USB debugging on will install the drivers for ADB mode). One other note, just in case you are getting the brilliant idea to go ahead and -pre-install all of these different states, it has to be done for each USB port (each state) and Windows tends to remove unused drivers after a short period of time (if you havent put your phone in download mode and plugged in to your PC in awhile, chances are, Windows will have to reinstall the driver for this state again). This is why in the instructions I listed, I explain putting the phone into mass storage mode and then back into ADB mode - this forces windows to install the drivers for each state.
For those still having trouble with this, reboot your PC and try the instructions again. Pay very close attention to the system tray (the icons by your clock in the lower right corner - typically unless you moved your start menu).
MAKE SURE that windows FINISHES installing the driver for mass storage BEFORE you switch to ADB mode or you will have problems. BE PATIENT! Put your phone in mass storage and go get a coffee, do a cross word puzzle, take a shower, whatever. It takes anywhere between 30 seconds to 5 minutes to install the driver and if you interrupt the process, things become wonky until you reboot.
There will be an icon by the clock that is animated while the driver is installing (click it and it will tell you it is installing the driver). When it isnt animated, clicking it will tell you that windows finished installing the driver. DONT RELY ON THE ANIMATION! Click the icon and be sure it has installed.
Also, you cannot have Kies running while Windows is installing the driver. If you do, windows will correctly install the driver but Kies will never detect the phone. It is possible that shutting Kies down and restarting it (and repeating the steps I mentioned to get Kies to connect) may correct the issue but most likely, it will require a reboot and then you will have to run thru the steps I outlined again to get it to connect properly.
This is a combination of Windows and Samsung both. Windows could handle this so much better, Samsung could have reported the device as two possibilities instead of 5. But, what can I say, One company is Korean and one is American and they each like to do things their own way.
Thanks, OP - finally able to get the ICS update. This whole process was a complete cluster****. Samsung should work on that.
Edit: Guess I spoke too soon. Kies was able to recognize my Note and began the update process (i.e., asked me if I wanted to update, had to agree to whatever, etc.), but after it downloads the firmware and begins "preparing firmware upgrade components" to install the upgrade it loses the connection with the phone and restarts the whole process again. Kies doesn't say anything about losing the connection - the box that shows the status of the update just closes and Kies doesn't register any connected devices (though it starts the "connecting" process again a few seconds later. Any suggestions?
NickNaylor said:
Thanks, OP - finally able to get the ICS update. This whole process was a complete cluster****. Samsung should work on that.
Edit: Guess I spoke too soon. Kies was able to recognize my Note and began the update process (i.e., asked me if I wanted to update, had to agree to whatever, etc.), but after it downloads the firmware and begins "preparing firmware upgrade components" to install the upgrade it loses the connection with the phone and restarts the whole process again. Kies doesn't say anything about losing the connection - the box that shows the status of the update just closes and Kies doesn't register any connected devices (though it starts the "connecting" process again a few seconds later. Any suggestions?
Click to expand...
Click to collapse
Use the link I provided in the original post to download the updated version and stick it in a folder you can find.
Completely UNINSTALL Kies.
Unplug your Note from the PC.
Reboot your PC.
Reinstall Kies using the new version you downloaded.
After installing, reboot your PC.
After your PC has rebooted, go through the process of installing the Note drivers as I described in the original post (see below). Once you reach the step of putting the phone in USB debugging mode and have plugged it into your PC, wait until AFTER Windows has told you the drivers have been correctly installed. If Windows gives you an error that the drivers did NOT install correctly, reboot and try again. You need to pay attention to the icon in the system tray, click on it to see whether it is currently installing, whether it successfully installed, or whether it failed if you arent seeing the icon animation.
MAKE SURE to watch the icon near the clock, do NOT change the USB mode on the phone until AFTER windows has told you it has installed the driver for that mode.
AFTER you have enabled USB Debugging and plugged it into your PC, wait until AFTER Windows says that it successfully installed the driver, then, WITHOUT unplugging your phone, launch Kies and proceed to update your phone.
littlewierdo said:
Use the link I provided in the original post to download the updated version and stick it in a folder you can find.
Completely UNINSTALL Kies.
Unplug your Note from the PC.
Reboot your PC.
Reinstall Kies using the new version you downloaded.
Click to expand...
Click to collapse
Thanks for all of these suggestions. This makes complete sense but I'm still having a problem (Windows Vista 64):
- I uninstalled using Kies Uninstall tool
- I searched out and deleted all other Kies related files, including program data stored under the user profile
- I rebooted my PC
But... when I try to install Kies from the new .exe file, it goes back to the loop: uninstall / install / uninstall.
Is there something more that needs to be done to "uninstall Kies" completely? e.g. modify a registry?
PS about the "loop" it goes like this:
10 Pop up: Before you install the new version, you need to uninstall the old version of Kies
20 Me: OK
30 (it then uninstalls - allegedly)
40 Pop up: You will now install the new version.
50 Me: OK
60 goto 10
UPDATE (7/17):
I used a registry cleaning utility to wipe out Kies related keys in the registry. I was then able to install the new, downloaded version of Kies and successfully updated my phone. So... I assume the loop was caused by Kies not being able to properly uninstall itself. (Or... it could have just been me...)
There is a possibility of user account control getting in the way. Forgot to mention that before you run the installer, you need to right click on the exe and select the compatibility tab and then select 'run this program as administrator'. For whatever reason, some machines I have noticed that Windows doesnt always automatically detect when a program needs to be run as admin and it needs to in order to access everything it needs to.
Why arent people flashing ICS the way everyone else has been for months? Seems like its causing more problems than anything
Sent from my SAMSUNG-SGH-I717 using xda premium
Newer Version of Kies!
littlewierdo said:
Alrighty, two problems I ran into trying to get ICS up and running.
Problem number one is what I call the infinite Kies update loop where Kies will ask you to update, you do all the steps, and Kies AGAIN asks you to update to the same version you just supposedly did. The software has to be current in order for Kies to perform the update. Now, there are two ways to go about it:
You can either edit the KiesVersion.txt and just type in the current version to 'fake' Kies out
OR you can download the latest build HERE:
downloadcenter.samsung.com/content/SW/201110/20111024092325174/Kies_2.3.2.12064_9_7.exe
Doesnt matter if you have another version installed or not, the installer will guide you through the process and uninstall the previous version. Takes about 5 minutes to install the whole deal.
Problem number two is getting Kies to actually recognize your device instead of just 'connecting' forever.
The way to get around this is the following:
Shut down Kies
Unplug your phone, then ON YOUR PHONE, go to settings>Wireless and Network>USB Settings and enable mass storage (Ill fix the wording on this shortly as my phone is currently updating but its only one option). After doing so, it will tell you that USB Debugging needs to be disabled (I think it will do this automatically), hit the Continue box and then plug your phone in. YOU DO NOT need to tap the Connect phone button under the little Android guy that appears on your phone screen. Now, let Windows install the driver.
NOW, unplug your phone and go to Settings>Applications> and enable USB Debugging (its the last option in the applications menu) and let windows install the driver.
Now, launch Kies and it should only take about 30 seconds to connect.
Note that your phone MUST be in USB Debugging for Kies to upgrade the firmware (which is why the last thing we did was enable USB Debugging, your phone will already be in USB Debugging mode).
Hope this helps
Click to expand...
Click to collapse
This worked great to finally upgrade my Kies to Version 9.7, however there is a newer version 2.3.2.12064.10 available so when trying to update it once again goes into the loop. Any idea as to where to find this newer version?
Cubbump1 said:
This worked great to finally upgrade my Kies to Version 9.7, however there is a newer version 2.3.2.12064.10 available so when trying to update it once again goes into the loop. Any idea as to where to find this newer version?
Click to expand...
Click to collapse
I found this direct link at the German Samung website: downloadcenter.samsung.com/content/SW/201105/20110512115717796/Kies_2.3.2.12064_10_1.exe (Grrr...I am not allowed to post a working link since I am a new user. Sorry for that.).
Worked for me, but I had to remove the old version on my own before installing the latest version with this installer. Otherwise it got stuck in the infinite uninstall loop.
Hi, this is my first post here.
I have an unbranded international Galaxy S3 GT-I9300, Android 4.0.4
Kernel Version: 3.0.15-928452-user
[email protected] # 1
AP: I9300XXBLG8
CP: I9300XXLG8
CSC: I9300DBTBLG6
Long story, so I better put my questions first:
How can I flash a non-rooted device without using the USB port? SD-Card somehow?? Download mode is working at least...
and/or
How can I remove a Super SU system app from a apparently non-rooted device? (...which can not be rooted by using the USB port)
What happened:
I had rooted my device via this instuctions: http://forum.xda-developers.com/showthread.php?t=1695238
-> [03.07.2012] CF-Root 6.4 - SuperSU+CWM5.5+CWMManager.
I used heimdall 1.3.1 on Ubuntu 12.04 via 'sudo heimdall flash --recovery recovery.img --cache cache.img'
All worked fine.
When the latest OTA firmware showed up a couple of days age (45,76MB) I tried it and it failed at 29%.
I remebered I had deleted some bloatware and thought maybe bringing it back would make the OTA work. Because I coudn't find Samsung Video Hub at some point I thought it would be the easiest to just factory reset, then run OTA and reroot.
I made lots of backups with Titanium Backup ROOT and I rolled back the BusyBox changes. I also reverted some later installed App to a non-system App again but am not sure which one, it was not Super SU, maybe the terminal app.
I then made a factory reset from within Android, on reboot CWM appeared and I choose the single one 'yes, delete all data'
After rebooting I tried to apply the OTA, still stuck at 29%
I realized that there ist still Super SU left as a system app and thought that might be the reason. However I decided to first give Kies a try with the update.
Installing Kies and connecting the phone (via my gf's Xperia Ray cable) went fine and it showed me the update. Because of memory shortage I had to move some things around, time passes, my gf sit down on her office chair and somehow remaind hanging on the usb cable,
my phone fell down. At first there doesn;t seem to be any problem, but after trying to reconnect to Kies, it didn;t work. I found the USB cable not working anymore, which means that no mobile is charged if connected via that cable now.
However I could not establish a connection from my phone to a computer again since then (original usb cable, another usb cable).
Not to Ubuntu (not recognized in heimdall), neither to any of 2 different windows 7 computers.
I know there is a lot of connection problems out there for S3, I cleaned the connector, and tried lots of stuff like not giving google account credentials after wipe, try different usb-ports, restart computer. Windows always says "Unknow device" now. Ubuntu, also heimdall 1.3.2 just says nothing.
Thats why I guess that somehow there is a hardware problem with the USB connector on the phone now. Charging and MHL is working. It also recognizes USB OTG cable, but not the things that I attach to it, it worked flawless before. USB Debugging on/off -> no difference. Also the option to switch MTP/PTP under Preferences->Storge->USB is gone (was there before my first reset)
As a side note, also WLAN is not working as before anymore, I always have to use a static IP to get connected to my FritzBox.
Because the ruins of SuperSU are still in the system I can not update. However the phone is not rooted as all apps I have tried claim. Reinstalling Super SU did not bring root back. It is there, it thinks the device is rooted but it is not. But I also can not get rid of Super SU.
So now, I can't use normal OTA update, can't reroot or use my backups, bc Titanium requires root.
I am stuck. Is there any way out? Or at least a direction?
Thank you for taking the time.
Silvio
einSelbst said:
Hi, this is my first post here.
I have an unbranded international Galaxy S3 GT-I9300, Android 4.0.4
Kernel Version: 3.0.15-928452-user
[email protected] # 1
AP: I9300XXBLG8
CP: I9300XXLG8
CSC: I9300DBTBLG6
Long story, so I better put my questions first:
How can I flash a non-rooted device without using the USB port? SD-Card somehow?? Download mode is working at least...
and/or
How can I remove a Super SU system app from a apparently non-rooted device? (...which can not be rooted by using the USB port)
What happened:
I had rooted my device via this instuctions: http://forum.xda-developers.com/showthread.php?t=1695238
-> [03.07.2012] CF-Root 6.4 - SuperSU+CWM5.5+CWMManager.
I used heimdall 1.3.1 on Ubuntu 12.04 via 'sudo heimdall flash --recovery recovery.img --cache cache.img'
All worked fine.
When the latest OTA firmware showed up a couple of days age (45,76MB) I tried it and it failed at 29%.
I remebered I had deleted some bloatware and thought maybe bringing it back would make the OTA work. Because I coudn't find Samsung Video Hub at some point I thought it would be the easiest to just factory reset, then run OTA and reroot.
I made lots of backups with Titanium Backup ROOT and I rolled back the BusyBox changes. I also reverted some later installed App to a non-system App again but am not sure which one, it was not Super SU, maybe the terminal app.
I then made a factory reset from within Android, on reboot CWM appeared and I choose the single one 'yes, delete all data'
After rebooting I tried to apply the OTA, still stuck at 29%
I realized that there ist still Super SU left as a system app and thought that might be the reason. However I decided to first give Kies a try with the update.
Installing Kies and connecting the phone (via my gf's Xperia Ray cable) went fine and it showed me the update. Because of memory shortage I had to move some things around, time passes, my gf sit down on her office chair and somehow remaind hanging on the usb cable,
my phone fell down. At first there doesn;t seem to be any problem, but after trying to reconnect to Kies, it didn;t work. I found the USB cable not working anymore, which means that no mobile is charged if connected via that cable now.
However I could not establish a connection from my phone to a computer again since then (original usb cable, another usb cable).
Not to Ubuntu (not recognized in heimdall), neither to any of 2 different windows 7 computers.
I know there is a lot of connection problems out there for S3, I cleaned the connector, and tried lots of stuff like not giving google account credentials after wipe, try different usb-ports, restart computer. Windows always says "Unknow device" now. Ubuntu, also heimdall 1.3.2 just says nothing.
Thats why I guess that somehow there is a hardware problem with the USB connector on the phone now. Charging and MHL is working. It also recognizes USB OTG cable, but not the things that I attach to it, it worked flawless before. USB Debugging on/off -> no difference. Also the option to switch MTP/PTP under Preferences->Storge->USB is gone (was there before my first reset)
As a side note, also WLAN is not working as before anymore, I always have to use a static IP to get connected to my FritzBox.
Because the ruins of SuperSU are still in the system I can not update. However the phone is not rooted as all apps I have tried claim. Reinstalling Super SU did not bring root back. It is there, it thinks the device is rooted but it is not. But I also can not get rid of Super SU.
So now, I can't use normal OTA update, can't reroot or use my backups, bc Titanium requires root.
I am stuck. Is there any way out? Or at least a direction?
Thank you for taking the time.
Silvio
Click to expand...
Click to collapse
Hi. First of all you can have ota updates with kies even if you are rooted as long as you haveone of the official roms installed. Su does not disturb your ota updates through kies.You wont be able to have ota if you are rooted without kies.
R u sure you tried other usb cables and your connection failed? Try another one......You are saying you can charge....These cables have got a lot of thiny cables inside. Even if one is damaged you will have a problem.Try a new Samsung cable.
In the worst case if there is a hardware issue after the fall try kies wireless app so you connect to the pc without cable.
How do you connect to your FritzBox?
looks bad
Hi art,
thank you for your input!
art_arev said:
Hi. First of all you can have ota updates with kies even if you are rooted as long as you haveone of the official roms installed. Su does not disturb your ota updates through kies.You wont be able to have ota if you are rooted without kies. R u sure you tried other usb cables and your connection failed?
Click to expand...
Click to collapse
I tried with two different cables (Samsung, Lenovo) on 2 different computers. What makes me quite certain that there is an issue with the usb connector is, that USB OTG is not working anymore. No matter what I connect, the only thing it recognizes is the usb otg cable itself, but no stick/mouse/hub.
The cable which is broken now is the SE Xperia Ray cable from my gf's phone.
art_arev said:
In the worst case if there is a hardware issue after the fall try kies wireless app so you connect to the pc without cable. How do you connect to your FritzBox?
Click to expand...
Click to collapse
I tried it, it seems that the Kies Air App as well as Kies over WLAN (via Androids Preferences to connect to the Kies Desktop Application) does not support any firmware updating. I connect to the fritzbox via WLAN, it worked flawless before and I haven't changed anything.
It seems I have the following options:
1. find a way to reroot or flash the phone without using the usb connector (I read somewhere that it should be possible, but no further instructions were given)
2. find a way to remove the left overs from rooting (Super SU) -> that would at least open the possibility to apply OTAs
3. send it to samsung and hope they will repair it (problem is there are still traces of rooting on the phone)
4. try to repair the broken usb-connector myself
5. continue to try to somehow establish a connection via usb
Concerning option #1: I have unsuccesfully looked into the following options: unrevoked, UniversallAndroot, Z4root
All threads I read say it's not possible (e.g. http://forum.xda-developers.com/showthread.php?t=1870267&highlight=root+without+usb)
If I can't make any use of the leftovers of Super SU I think option 1+2 are dead ends.
I think I should try option 3 and if they deny, try option 4 or live with an unupdateable (?) unrooted phone (nah )
If there is SuperSU in system/app folder than it should work. Try to use build in options in SuperSU to reinstall. Also download and install busybox.
If root will be present and give you all needed partitions than you will be able to use Mobile Odin to flash stock firmware. But you also must remove binary counter information. This is imposible without root and/or working USB port.
There is a small chance that after flashing stock firmware USB port will be fully operational once again. I suppose it could be a software/driver issue, not hardware malfunction.
You can try to flash first with Everoot option enabled and after that check your USB connection. Of course you must transfer stock firmware to your phone. Do this via AirDroid or write it on external sd card on computer and put it into your phone. (copy this firmware to your internal sd card, it's better to flash from internal memory).
To resurrect your phone you need root or working USB.
i9.0.1.3k galaxy imperator
Thank you for keeping the hope alive SirKunon!
SirKunon said:
If there is SuperSU in system/app folder than it should work.
Click to expand...
Click to collapse
The App in system/app is called Superuser.apk (if that makes a difference), from inside the App I can see it is SuperSU v0.93.
There is an update available in the playstore which I can apply.
If I start any app which requires root (BusyBox, Titanium Backup, Root Explorer, Root Checker) I get the Superuser prompt to decide if I want to grant root access. Even if I choose "Yes" it never works.
Using the options inside SuperSU to reinstall fails (it does not close) as long as I don't have the update of SuperSU installed. If that is in place. It will close and left me with the former SuperSU version. Same for the option to "switch to another Superuser App" and "complete unroot".
If I try to remove the check from the box saying "activate Superuser" it tells me "Uninstallation failed"
SuperSU is there, Root access not. The only thing I can think of is do a factory reset once more (already did a couple) and try again.
It seems like there is a solution just behind the next door but I can't get through...
It's very strange, indeed.
Try hard reset service code:
*2767*3855# - hard reset
I don't have any other ideas. Service center will refuse fixing it if there are root traces. But you can try to find someone with jtag box to flash stock firmware or replace USB circuit on your own if you are sure that's faulty.
i9.0.1.3k galaxy imperator
Thanks for your help.
SirKunon said:
Try hard reset service code:
*2767*3855# - hard reset
Click to expand...
Click to collapse
Tried it, but situation remains unchanged, SuperSU is there, root access not, uninstall/reinstall it has no effect
OTA still hanging at 29%
no usb connection
no wireless connection unless I use a static ip
At least the phone is working as is...
Will probably send it to service center b/c I have nothing to loose. Maybe try to use my gf's insurance on beforehand.
If all fails, open the device or live with it, not sure.
einSelbst said:
Thanks for your help.
OTA still hanging at 29%
YES as it does .
Turn off signature verification via recovery may help.
Triangle Away
Mobile ODIN Pro and flash stock rom from external sd card
Then factory reset .
jje
Click to expand...
Click to collapse
hi jje,
JJEgan said:
Turn off signature verification via recovery may help.
Click to expand...
Click to collapse
but I don't have correctly working root access and only stock recovery.
Do you think it is still possible?
einSelbst said:
hi jje,
but I don't have correctly working root access and only stock recovery.
Do you think it is still possible?
Click to expand...
Click to collapse
No as we still have no way of flashing stock from phone without recovery .
it was just thinking aloud anyway .
What is required is a method to root from within the phone which we don't have .
jje
I've been pulling my hair out trying to make Kies work but nothing seems to help. Kies detects GT-I9300 but doesn't get past the 'Connecting' screen. I uninstalled Kies, removed the drivers, removed registry entries related to kies, temporary files, cache, everything and reinstalled the latest update, still it doesn't help. I've tried connecting with 'USB Debugging off' as well as 'USB Debugging On'. Nothing seems to work.
The last time Kies connected to my device was before I flashed Siyah Kernel, I haven't checked since then. Has it got anything to do with the kernel?
I'm running the latest Siyah Kernel
and Stock Rom: I9300XXDLJ5
I need it to connect to Kies so that I can update to I9300XXDLK1
Any solutions?
Update using Odin, its much more easier and less trouble,
Sent from my GT-I9300 with a BIG
Hello all, I have a GS3 international GT-I9300
I'll try to go through the story as fast as I can and give as much detail so you guys can understand how I got here.
Bought the phone unlocked, I was stock, I rooted and then I decided to install a new ROM. I went with Resurrection Remix, it was working great. I did this on a desktop back home. They released a new update to RR so I did a OTA update with "Update Me" apparently the thing flashed but it didn't, the phone still worked but NFC wasn't working as well as having lost root access and some other stuff wasn't working correctly, but I lived with it.
I moved to Florida (home is in NY) and I have a laptop with me, for some reason my laptop used to be able to transfer files to my S3, but it wasn't doing it any more after a while. So it would just charge it. I was in a hotel room last week trying to tether via USB but the PC wasnt having it, it could not locate the phone. This week I moved to a different hotel with internet and decided I would flash stock on my S3 to get rid of all these bugs and get root again, I tried flashing stock through recovery and it wasn't going, so I tried flashing RR again (this time downloaded from the site RR site) and it worked. Still no USB connection but I had root back. I looked around my PC and apparently the Samsung drives are not installing or something on my PC. I installed Kies, but nothing, I tried a stand alone driver install and nothing, so I just gave up and bought Mobile Odin pro from Gplay to try to flash again.
Mobile Odin for some reason (I blame it on myself) wasn't finding/flashing stock so again I decided to try and flash RR and see what would happen. It flashed RR and turned on fine. Then I just decided to look for an NFC fix on XDA. Once I found my NFC fix (http://forum.xda-developers.com/showpost.php?p=32029713&postcount=8367) I decided to just copy the files to the system folder, NFC still not working, rebooted and NFC still no working, so I figured I would try to flash the fix through mobile odin seeing as how I can't get my PC to pick up on the USB. I tried flashing but MO just kept bouncing it back and re-booting into RR. Tried again and no flash. So I decided to again try and flash stock. I tried going into Recovery, the phone shut off like it always does, came back on but stayed in the Galaxy S3 GT-I9300 logo and would not move. I shut it off again, tried turning it on again and still stuck on the galaxy logo. Now, if I leave the phone off and plug in the USB, it won't show the battery charging image, it will actually turn straight onto the galaxy logo again and stay there. I can get the phone into download mode, but like I said my pc won't recognize the drivers.
Now, here are my questions:
What happened?
Can this be fixed?
Am I an idiot?
If I can get the drivers installed on another PC as well as Odin (1.85), will the new PC "see" the S3 or are the drivers on the phone deleted as well? (if that sort of thing can happen, idk.)
I'm going to see if I can borrow a buddy's PC and download the drivers as well as odin to try and bring my S3 back to life, I just want to know, what happens if I can't get the other PC to pick it up ether because the drivers on the phone are deleted (if that's a thing) or what I can expect if it is connected.
What are the steps or guides to follow here? I just got it into Download mode and it says on the top of the screen:
ODIN MODE
Product name: GT-I9300
Custom Binary Download: Yes (2 counts)
Current Binary: Custom
System Status: Custom
sorry , i am sometime getting headache reading long english text so i just briefly look over.
your PC doesn't recognize your S3 ? is that correct ? hmmm , is it possible that your PC (Microsoft Windows I assume?) system is damaged due to something like virus or some reasons ? i have encountered that kinda problem before and be OK after i reinstalled the system.
If it's a soft brick, then it can defiantly be fixed. You might, however, lose your data along the process.
Be glad it's not hard bricked
It happened to me many times, USB error "unknown device" connected. Only fix for it was reinstalling Windows so better if you can use different PC or laptop. Install Kies and other USB drivers. Restart computer, download and run Odin v 3.0x. Flash your phone.
If this doesn't work then maybe your phone have a problem with USB port?
Sent from my GT-I9305 using xda app-developers app
djembey said:
It happened to me many times, USB error "unknown device" connected. Only fix for it was reinstalling Windows so better if you can use different PC or laptop. Install Kies and other USB drivers. Restart computer, download and run Odin v 3.0x. Flash your phone.
If this doesn't work then maybe your phone have a problem with USB port?
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Don't forget to delete kies as you only need the drivers
Sent from my GT-I9300 using Tapatalk 2
Thanks for the replies guys. I'll try to fix tit today, I didn't get a chance to do it last night. If anything I'll update you guys with what's going on.
Like I was saying, I'll try using a different PC to fix it. Now, if I can't get Odin to recognize the phone, what would be the next step?