I want to root and know how, but I first need the drivers installed. I found the drivers from samsung's site from here: http://www.samsung.com/us/support/downloads/SGH-I777ZKAATT
But most people say that I need to install through kies. Does anybody know if installing the drivers from samsung's site is different than installing through kies? Thanks in advance
Related
i can connect my sgs2 vie kies and i can backup my contacts, add media files, and transfer files via windows explorer.
however i get the screenshot below when looking at the firmware section.
does this mean that my country doesnt have available firmware yet or that i need install drivers before it searches for updates?
TIA
Perhaps this is region specific.
I have seen once that problem reported elsewhere, but unfortunately without resolution: Kies not showing latest firmware.
Are you running latest version of Kies BTW?
yes I'm running latest kies version.this afternoon kies changed status to 's latest firmware installed'
hoping that's a prelude to getting 2.3.4
Sent from my GT-I9100 using Tapatalk
First of all - if this has been asked before, please forgive me. I tried searching, but it's not even 6.30 am yet and my brain isn't completely on yet.
What I was wondering about is if rooting the S3 will stop OTA updates for the phone, and if the OTA will keep coming I would very much like to know what the easiest route to rooting this is. I cannot be bothered to keep manually flashing my phone like I did with my S2...
Cheers!
If all you do is root, you will still get OTA updates but if you install a custom recovery the OTA updates will not install.
Sent from my Nexus 7 using Tapatalk 2
You would still be able to update through kies with custom recovery. Its basically what i do, root + CWM, when i see the OTA, i go to my pc and update through kies.
Thanks, guys Now I just need to find out how come Odin won't connect properly. Hopefully, the phone just needs a charge...
Is it actually possible to root without changing the loader? If so, could someone point me in the right direction? It seems the ones I've found will install CWM :S
OT
one does not simply
root a n00b
Just flash the kernel via Odin. It will not void your warranty if you use Triangle Away.
The only reason why Odin does not detect is because the drivers are not installed properly in your PC
Hi guys. I have a Samsung Galaxy s3 GT-i9300 running 4.1.1 Baseband 19300XXDLIB.
I have been trying and trying and trying for the last few days to root my mobile. I take care following all of the steps and I have tried every type of root program and files I think are available but even though they download to the phone and reboot into their custom recovery, then install the files needed to root, none of them have worked!!
It's strange because the phone is just unrootable it seems. I have tried several versions of Odin. I've tried what should be 1 click rooters but nothing works! The most recent files I have used to download to my phone via Odin were CF-Auto-Root-m0-gti9300, CF-Root-SGS3-v6.4, SuperOneClickv2.2-ShortFuse, SuperOneClickv2.3.1-ShortFuse and SuperOneClickv2.3.3-ShortFuse all of which have been recommended to me and I have strictly followed YouTube videos and written guides. I don't think I am doing anything wrong yet I still have no root access. The last root I tried installed a CWM app (I know it stands for Clock Work Mod but not sure what I am supposed to do with it) but not SuperSU which is supposed to come with it.
Please can someone help? I'm tearing my hair out here!
I should probably point out I am not using the stock ROM as I did manage to brick my phone at one point and had to install another firmware, although I would like to go back to my original firmware yet I am not sure what it was...is it possible to figure out what the stock firmware should be? The phone is unbranded from the UK.
Many thanks
I should probably point out I am not using the stock ROM as I did manage to brick my phone at one point and had to install another firmware, although I would like to go back to my original firmware yet I am not sure what it was...is it possible to figure out what the stock firmware should be? The phone is unbranded from the UK.
No you can only guess .
TO ROOT .
Factory reset the phone and install CF root 6.4 via Odin .
But its really pointless rooting when you don't have a clue as to why or what .
BASICS .
http://forum.xda-developers.com/showthread.php?t=1927113
jje
May also be because your computer hasn't been installed with the samsung drivers yet? Kies i think it's called..
Have you tried downloading supersu from the play store? And be sure to not try superuser but supersu.
I had the same thing with cf-autoroot. supersu wasn't there and I didn't have root. Tried several times, never worked. After that I tried rooting with the old cf-root that also installs cwm recovery. Recovery was there but no supersu and the phone didn't get root. Tried that several times too but that didn't help either, although that is how I rooted my phone successfully right after I had bought it. Went back to cf-autoroot, same result, no root. But as soon as I downloaded the app supersu manually and updated the binarys as it tells you to at first start, I had root.
Zelmer said:
May also be because your computer hasn't been installed with the samsung drivers yet? Kies i think it's called..
Click to expand...
Click to collapse
Kies is not required (and its junkie bloatware that doesn't properly clean itself up on uninstall anyway)
Windows can pull the drivers from WU.
You Sir, are a legend! Thank you very much, you have sorted my problem I had SuperUser instead of SuperSU like you stated. Who would've thought it'd be so easy to fix?
shamez23 said:
Have you tried downloading supersu from the play store? And be sure to not try superuser but supersu.
I had the same thing with cf-autoroot. supersu wasn't there and I didn't have root. Tried several times, never worked. After that I tried rooting with the old cf-root that also installs cwm recovery. Recovery was there but no supersu and the phone didn't get root. Tried that several times too but that didn't help either, although that is how I rooted my phone successfully right after I had bought it. Went back to cf-autoroot, same result, no root. But as soon as I downloaded the app supersu manually and updated the binarys as it tells you to at first start, I had root.
Click to expand...
Click to collapse
You should probably not just imagine that just because someone has a problem that they don't have a clue what they are doing. I have done this numerous amounts of times with several phones, my Samsung was just slightly more difficult since I had made an easy mistake by not taking note of my original firmware and by not realizing that I needed SuperSU and not SuperUser (which I'm sure is a common and easy mistake).
Try next time not to put a fellow site member down.
JJEgan said:
I should probably point out I am not using the stock ROM as I did manage to brick my phone at one point and had to install another firmware, although I would like to go back to my original firmware yet I am not sure what it was...is it possible to figure out what the stock firmware should be? The phone is unbranded from the UK.
No you can only guess .
TO ROOT .
Factory reset the phone and install CF root 6.4 via Odin .
But its really pointless rooting when you don't have a clue as to why or what .
BASICS .
http://forum.xda-developers.com/showthread.php?t=1927113
jje
Click to expand...
Click to collapse
I did actually install Kies but thanks for the help anyway
Zelmer said:
May also be because your computer hasn't been installed with the samsung drivers yet? Kies i think it's called..
Click to expand...
Click to collapse
Alright, I am just posting this for anyone unable to find and locate the solution posted by Agrajag27. I didn't find this post right away because I was searching by the build number after I did the first OTA update successfully and then got an error message; unable to update while trying to install the second OTA provided by Verizon. In summary, Agrajag27 wrote this as the solution to those experiencing issues installing the second OTA update:
1. Go to Samsung Kies website (sorry, unable to post the link for the website)
2. Download Kies3 (not Kies) for PC and install
3. Open Kies3 on PC and ignore the suggestion of installing Smart-something or other(I can't remember exactly what it suggested either during the process?)
4. Connect your phone via cable to the PC and Kies will see it and tell you there's an update. Install the update.
Thank you (a million times) Agrajag27 for finding a rather simple solution to this OTA issue!
cimbus said:
Alright, I am just posting this for anyone unable to find and locate the solution posted by Agrajag27. I didn't find this post right away because I was searching by the build number after I did the first OTA update successfully and then got an error message; unable to update while trying to install the second OTA provided by Verizon. In summary, Agrajag27 wrote this as the solution to those experiencing issues installing the second OTA update:
1. Go to Samsung Kies website (sorry, unable to post the link for the website)
2. Download Kies3 (not Kies) for PC and install
3. Open Kies3 on PC and ignore the suggestion of installing Smart-something or other(I can't remember exactly what it suggested either during the process?)
4. Connect your phone via cable to the PC and Kies will see it and tell you there's an update. Install the update.
Thank you (a million times) Agrajag27 for finding a rather simple solution to this OTA issue!
Click to expand...
Click to collapse
Can someone do me a kindness and please post a reply in this thread when its discovered how to root Lollipop on the Verizon SCHI-545? Thanks. I need root!
You want root, but took the OTA? It wouldn't be surprising if there is never a way to root it. There's a method of upgrading to OC1 without losing root or the ability to downgrade. There's not much incentive for others to look for a root method, because anyone who wanted root had the ability to keep it when they upgraded and new root methods require more and more effort as previous exploits are closed off. Here are general rules to live by:
1) If you're rooted or modified in any way, taking an OTA may brick your phone.
2) Wait until those who know better figure out safe ways of upgrading while retaining root, and there's a widespread indication of success, before even thinking about upgrading.
3) Learn patience. You don't need to upgrade within the first few days of a new release.
I have a Verizon Samsung Galaxy S4 that was rooted on the 4.3 build with the saferoot method (I think, it's been awhile). I had since installed Xposed framework and installer, etc. I unrooted with the supersu unroot method. Now I can't connect my phone via USB in either Ubuntu or Windows 7 (it shows unknown device). Another S4 shows up and installs drivers just fine on my computer, and my phone isn't recognized by other computers running windows. Basically, no matter what I've done with ADB and Windows drivers, my phone will not talk with my PC and I cannot connect to Odin. I've factory reset my phone, and I just want to be able to communicate via USB. At this point I'm torn between whether or not it is hardware or software, but I'm going to do whatever I can with the software before I look at new hardware.
I'm looking at taking some of the firmware I've found on XDA and installing that through the stock recovery with the SD card. `SCH-I545_VZW_1_20131023084910_v4vth34m5z_fac.zip` is the package I have.
My question: is this okay to just push this `.zip` via stock recovery? Is there anything else I need to do, like install other packages, etc?
You can try to install this, then I would FDR again and then flash the actual full Odin file! That should do the trick!!
Also if you haven't tried, our the phone into download mode before connecting to the computer...and use Windows 7
Sent from my SCH-I545 using Tapatalk
Okay, I tried to install several firmware versions, but since I don't have a custom recovery it still checks for a signature and they all failed. OTA update also failed, but I don't know why. I ordered a new usb board for the phone. If that doesn't fix it, I'm not sure what will. I'll update when it gets in.