I just had a lot of trouble trying to root my galaxy tab. Instructions from a couple different sources said you have to set up Kies first and get that working.
== IN MY EXPERIENCE ==
It turns out, all you have to use Kies for is to get the drivers, and pay no attention to the fact that you cant do anything with Kies. Kies kept telling me my device wasnt supported and it wasnt in the right mode and such. Finally I just skipped that step and went and turned USB Debugging back on and gave SuperOneClickRoot a shot and it worked!
I dont know if this was a maverick move, so follow at your own risk.
Related
I'm having some problems upgrading my wife's phone. I went to the website with the upgrade instructions, downloaded Kies mini, and installed all of the drivers for the phone. I put the phone in usb debugging mode and plugged it in, but Kies doesn't see the phone. I tried messing around with some settings (i don't remember what I did) and it worked one time. And the one time it did work, it said something like unsupported device and the upgrade phone button was greyed out. I've tried searching everywhere for an answer to no avail. I don't know what I'm doing wrong
Did you use the USB port on the back of the PC?
No, I used one of the ports on the front
What sort of configuration was the phone running before you tried the update. Any customization? Rooted?
no customizations, unrooted
Make sure in the USB setting it of set to Kies (Fireware Update). This is under settings/applications
Sent from my SAMSUNG-SGH-I897 using XDA App
I did that. when I did switch it to kies, it said I had to turn off debugging mode. After i switched it to kies mode, i turned debugging back on. Should I not have done that?
the_KEV said:
I went to the website with the upgrade instructions, downloaded Kies mini, and installed all of the drivers for the phone. I put the phone in usb debugging mode and plugged it in, but Kies doesn't see the phone.
Click to expand...
Click to collapse
May I ask why did you put the phone in debugging mode? You don't need to. You should do what Viper 714 suggested. Have you ever used Kies before this attempt at updating the firmware?
Feel free to PM me and I'd be happy to assist you.
clemmie said:
May I ask why did you put the phone in debugging mode? You don't need to. You should do what Viper 714 suggested. Have you ever used Kies before this attempt at updating the firmware?
Feel free to PM me and I'd be happy to assist you.
Click to expand...
Click to collapse
I have never used kies before this. I didn't think I needed it. The instructions says debugging mode should be enabled.
Captivate Froyo update crash and how to solve
Note my device is an ATT Samsung Captivate S SGHi897
Kies would crash on the update indicating a conflict AMINIFUS.EXE from the AMINIFUSREQLEV component. Also sometimes, kies would not present the upgrade screen althought KIES sees the device memory/drives.
Here's what fixed it for me.
On the device - go to settings / development turn ON USB debuging and turn ON Allow mock locations.
With KIES running - the Capivate USB screen may not appear when you connect your USB cable. But the upgrade screen KIES will appear and start your upgrade.
IF you have a external SD card - remove prior to the update. I was able to update with my external SD card installed but when the device rebooted the device screen would go to black AFTER the ATT and Capivate splash screens and appear to hang. I removed my external card - rebooted the Capivate and the device was able to work this the initial Froyo set up screens - then the external was fine.
Samsung is aware of this problem and fix is not widely known. I person I spoke with at Samsung only discovered this fix on his previous call.
Good luck everyone. Froyo is finally OH and lastly = ATT will be rolling out an over the air update for those who do not want to go through KIEs.
You should definitely remove your SIM and external SD before flashing any new firmware, as a matter of Due Diligence.
I'd give it a try first with it disabled.
Oh yeah I forgot to mention that when the phone is not in debugging mode, the phone says it's connected to kies, but kies says no phone is connected
clemmie said:
You should definitely remove your SIM and external SD before flashing any new firmware, as a matter of Due Diligence.
I'd give it a try first with it disabled.
Click to expand...
Click to collapse
OK I'll try again when my wife gets home with the phone. would it be a good Idea to uninstall everything and start from the beginning?
I did it with usb debugging on. The important part id make sure your in Touchwiz. Otherwise keis will not see the phone.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
shinji257 said:
I did it with usb debugging on. The important part id make sure your in Touchwiz. Otherwise keis will not see the phone.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Click to expand...
Click to collapse
did kies automatically see it or did you have do anything after you plugged in your phone?
I suggest using the full KIES application itself opposed to KIESmini.
If you do a quick google search (or even search the forums here) for KIES you will soon come across a download link for the full KIES application.
KIESmini has been known to have issues with 64bit operating systems. So check into that as well.
I run Win7 64bit and I could not get KIESmini to work. It would crash (stopped responding error) every time the device was connected. So I downloaded the full KIES application and the problem was solved... Everything updated fine.
clemmie said:
May I ask why did you put the phone in debugging mode? You don't need to. You should do what Viper 714 suggested. Have you ever used Kies before this attempt at updating the firmware?
Feel free to PM me and I'd be happy to assist you.
Click to expand...
Click to collapse
I had the same problems. Not only do you need to turn on debugging but also allow mock locations.
RaptorOne3 said:
I suggest using the actual KIES program itself opposed to KIESmini.
If you do a quick google search (or even search the forums here) for KIES you will soon come across a download link for the actual KIES application.
KIESmini has been known to have issues with 64bit operating systems. So check into that as well.
Good luck..
Click to expand...
Click to collapse
Unless you modify the built in Access database for Kies, it will not recognize the i897 as a supported device.
Back when I used to check for updates with Kies Mini frequently I always had trouble getting the phone to talk to Kies Mini. What I found worked the best is as follows:
1. Restart the PC
2. Restart the Phone
3. Disable Bluetooth on the phone if it is enabled
4. Put the phone in "Kies (Firmware update)" mode in Settings | Applications | USB Settings
5. Plug the phone into a USB port on the computer that is not on a root hub shared by any other devices (especially a keyboard or mouse).
6. Launch Kies Mini
Step 5 is very important because the phone must negotiate a USB 2.0 connection. I found that steps 1 & 2 were almost always necessary, without a clean boot on both devices, I frequently had problems. Step 3 seemed to help, though sometimes I could get the phone to connect to Kies Mini with Bluetooth enabled. I was able to get it to connect in either Kies "Firmware Update" mode, or USB debug mode. The documentation may specify USB debug mode because Bluetooth has to be disabled for USB debug mode.
I think I got it!! I uninstalled everything. Then I just did what everyone said. Used the back of the PC, made sure the phone what kies mode, with debugging, and mock locations, removed sim card and sd card...but then kies kept crashing. Then I found another post somewhere that said to uninstall IE9. I did that and now its finally working! Thanks yall for your help.
anyway I can add solved to the title?
Before I start this short tutorial let me say I'm no expert, but I am quite tech savvy (I work in IT and have done so for over 20 years).
I've been having major problems rooting my Galaxy Tab after it came back from Samsung following a Newbie mistake I made....
I have figured out how to root it after much searching and so decided to post this in the hope it might help someone else. Because I'm a new user I can't post links but the things you need are easy to find with Google if you follow my instructions below.
First some background....
When I first rooted my Galaxy Tab everything went perfectly, using SuperOneClick and following directions I found on one of the many forums.
Then after doing much reading I decided to jump into flashing a custom rom.
That too went perfectly.
Then I made a silly mistake and bricked my phone :-(
Fortunately Samsung here in Thailand fixed it whilst I waited in 45 minutes under warranty
So I had a virgin phone again and needed to root it again but this time everytime I tried nothing would happen... SuperOneClick would just sit there saying waiting for device.
This is what I did to fix the problem and gain root access to my Galaxy Tab once more.
1) Forget the instructions that start off with syncing to Kies
2) Go to Control Panel - Add Remove Programs - look for the Samsung USB drivers - Uninstall them.
3) locate and download these Samsung USB Drivers by searching google - Samsung_P1000_USB_Drivers.rar.html
4) Open the archive and find the setup file, run that to install the drivers.
5) Search Google for this page on Lifehacker - the-always-up+to+date-guide-to-rooting-any-android-phone - and follow their instructions for rooting with SuperOneClick. You will note they make no mention of connecting with Kies and disconnecting then reconnecting then..... blah blah blah.
They just say to connect in USB Debugging mode and run SuperOneClick.
This method worked for me first time after trying and failing with various versions of SuperOneClick, 2 versions of Kies, uninstalling and reinstalling....
Hopefully it will work for someone else that is having problems with the 'Waiting for device' message.
Good luck!
Sean
I just wanted to relay my experience for anyone who might run across the same problem. There are so many solutions (some good, some bad) that I thought I'd try and help someone else out that was in one of these situations. Keep in mind, the solutions are all here at XDA, I just had to dig and try a few things.
This Captivate was on a Ginger Clone rom (2.2) from about a year ago and I wanted to go to Cyanogenmod. I personally run Cyanogenmod7 (181), and was trying to replicate that.
[Boot-Loop]
I Attempted to clear caches and go straight to Cyanogenmod. This may have been an inexperienced guess that I might be able to do this, but I know a few other folks that manage to do this. I ended up in a boot loop
[Getting to Download mode]
Can be frustrating, but seems to be if you have the usb unplugged, battery out, sim out, put the sim in, battery in, usb in (phone will turn on, so you have to move fairly quickly) and then hit the up and down volume buttons it will go into download mode.
[Go back to Factory]
I tried using the Odin 1 click solution. I believe there are more than 1 versions of this, but it would just get stuck at "Do not turn off target". I decided to try something else. The Java based Hemidal 1.3 aka "SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click.jar" seems like it is very well written and very easy. It has you update a driver in the mix and it works fantastically.
[Now I'm at Stock 2.2, rooted]
Need to turn on USB debugging, and I was expecting to be able to put
on the rom manager by copying over a file, naming it update.zip but it won't run due to some signing restriction.
[Unable to run any scripts or update.zip]
http://forum.xda-developers.com/showthread.php?t=833423
Basically, you need to turn off signing
[Went off the tracks, bricked the phone]
I decided I would try and apply the Cyanogenmod rom a different way. I went to their wiki and tried to use their Hemidal 1.1.1 update suite and script. I ended up with a brick. I didn't panic, I used the below url and it worked to get me back into download mode. I then used the previously successful Hemidal one click to fix it.
http://www.traemcneely.com/2011/05/...e-possibly-vibrant-kernel-error-black-screen/
I went back to the 3e recovery installer, ran that script, it worked and let me run unsigned code, I installed rom manager via update.zip, and from rom manager I was able to apply Cyanodenmod 7-v181 and then the Google apps and I was happy. Took about 2 1/2 hours to go through all that. Kind-of a pain... happy now.
Rich
Wish I had your kind of luck
I have a Captivate that isn't "bricked" per say but when I plug it into my computer when it's in download mode I only ever get "unknown device". Forcing a driver install causes a code 10 which makes it unusable as well. I have tried 4 different cables and 3 different computers now and tried all of the USB ports on each of the computers I tried at and always get unknown device even with the correct drivers installed. The 3 button trick doesn't work to put it in download mode but using a jig does. I have tried every operating system combo as well heimdall in OSX and Linux says no device connected, and in Windows 7 32 bit and 64 bit I get the unknown device error, also tried Windows XP and get the same error. I have tried 4 different usb cables now as well in each situation with the same unkown device/no device connected error (2 motorola cables, 1 samsung oem cable, and one no-name cable). I was going to gift this to my Dad because he's been missing Android since he gave his HD2 away and went back to a Blackberry.
HI, This is my first android so bear with me!! I purchased a galaxy s4 active last October. Since then I dropped it and it has a small crack in the glass in the corner so Samsung wont help me. My phone worked fine after the drop and later took the update, however, aftyer some time I connected it to the computer and an ap i had on my computer ( I think it was part of an antivirus app) said my device needed a new driver and asked to install it at which I said ok. Whatever happened my phone doesnt work. I can start it up but I only get a message that says: Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. I have done this time and time again to no avail. Kies says it doesnt recognize my device firmware. I have the update software on my pc and odin and I've tried to reinstall it on the phone with this notice on and in download mode. Either way it fails. Please help if you can, I'm stuck,aggravated, etc....etc.. Thank you MUCH for your time, Herbie :crying:
hbaer said:
HI, This is my first android so bear with me!! I purchased a galaxy s4 active last October. Since then I dropped it and it has a small crack in the glass in the corner so Samsung wont help me. My phone worked fine after the drop and later took the update, however, aftyer some time I connected it to the computer and an ap i had on my computer ( I think it was part of an antivirus app) said my device needed a new driver and asked to install it at which I said ok. Whatever happened my phone doesnt work. I can start it up but I only get a message that says: Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. I have done this time and time again to no avail. Kies says it doesnt recognize my device firmware. I have the update software on my pc and odin and I've tried to reinstall it on the phone with this notice on and in download mode. Either way it fails. Please help if you can, I'm stuck,aggravated, etc....etc.. Thank you MUCH for your time, Herbie :crying:
Click to expand...
Click to collapse
Ok Sir in new in here but there are certain things i have already understand.
1. Your phone is the intl national versión or regular a&t version (SGH-I537)
2. Wich Android version were You runing before it brake down?
3. Have you tried to push volume down + power? That gets you to Odin mode.
4. If yours is attending version please check this http://forum.xda-developers.com/showthread.php?t=2625033
That's the whole 4.3 package if your noon look for Odin 3.09 it's way more understandable on where you have to put each package.
5. If your phone is intl version please check samobile
For your phone software and make sure you have downloaded the drivers for your phone.
You can look for them in Samsung.com
alphabeast said:
Ok Sir in new in here but there are certain things i have already understand.
1. Your phone is the intl national versión or regular a&t version (SGH-I537)
2. Wich Android version were You runing before it brake down?
3. Have you tried to push volume down + power? That gets you to Odin mode.
4. If yours is attending version please check this http://forum.xda-developers.com/showthread.php?t=2625033
That's the whole 4.3 package if your noon look for Odin 3.09 it's way more understandable on where you have to put each package.
5. If your phone is intl version please check samobile
For your phone software and make sure you have downloaded the drivers for your phone.
You can look for them in Samsung.com
Click to expand...
Click to collapse
My phone is regular at&t version SGH1537 and I updated it to 4.3 OTA before it broke down. As I stated I have the update ( 4.3 ) on my computer and Odin, so of course I tried the download mode but odin said the process failed and my phone is stuck. It wont start up any further than this message!!! :crying:
hbaer said:
My phone is regular at&t version SGH1537 and I updated it to 4.3 OTA before it broke down. As I stated I have the update ( 4.3 ) on my computer and Odin, so of course I tried the download mode but odin said the process failed and my phone is stuck. It wont start up any further than this message!!! :crying:
Click to expand...
Click to collapse
Try reinstalling the drivers for the i537 (as mentioned before they're on Samsung's site). Also make sure you're using the USB cable that came with the phone. For some reason, not all USB cables will work properly. As long as you can get into Download mode there is no reason you shouldn't be able to Odin back to stock. Make sure the Odin files you downloaded aren't corrupted by checking the MD5. Just keep trying Odin on different computers, with different cables, and different USB ports until it works. It sucks, but for some reason Odin is super picky about what it needs to work properly.
Devo7v said:
Try reinstalling the drivers for the i537 (as mentioned before they're on Samsung's site). Also make sure you're using the USB cable that came with the phone. For some reason, not all USB cables will work properly. As long as you can get into Download mode there is no reason you shouldn't be able to Odin back to stock. Make sure the Odin files you downloaded aren't corrupted by checking the MD5. Just keep trying Odin on different computers, with different cables, and different USB ports until it works. It sucks, but for some reason Odin is super picky about what it needs to work properly.
Click to expand...
Click to collapse
Awesome, thank you so much! I will try everything you said. I will let you know how its turned out. Thanks again Herbie
Hello folks.
Had a go at rooting Samsung i9000. It's quite old, and clearly clogged up to the hilt with the apps very laggy and frequently crashing. I quite fancied getting rid of the bloatwear too and the bloody annoying splash screen at start up!
Needless to say, it's all gone belly up. I've tried a couple of things using the guides here, but I don't want to keep pushing my luck in case I completely brick the device.
I'm running an i9000 in the UK on the o2 (Well, giffgaff) network. It was running Gingerbread, 2.3.5 I think. As it stands, I can get into the download option, but nothing else. I had used Odin 3, but have since read that the highest level is 1.83, which I now have. This might have caused the initial problem, but it's "soft" bricked. I've tried to flash over a stock rom again, but I keep getting failure notices. I can't get past the "Can't open the serial (COM) port" error message on Odin. I've downloaded the drivers and they have successfully installed.
One thing I don't think I did beforehand was to enable USB debugging.
I also tried the guide on here which uses the pit method, and curiously enough, it went through without the COM port error. The only thing that did, however, was to remove the "Phone + PC" logo. I am still able to get into download though.
Help! I am due to get a new phone very shortly, but it would be very useful to get the phone working again in the meantime! Any help very much appreciated.
If Kies is running in background it will fail, Go into Kies, Tools -> Preferences, unselect "Run Samsung Kies automatically when a device is connected", save the change, close out of Kies, and then restart ODIN. Try flashing now.
Try uninstalling Kies and then reboot and install the Samsung Drivers. Try then.
PFFFFFFFFFFFFFFFFTTT, sent from my i9000