Hello, I was just wondering the best way to root the AT&T Samsung Note SGH-I717. I have looked up many ways but every time I scroll down to the comments I read everyone is having problems. I would just like the best and most proven way to root the phone. I use the phone with straight talk, it is an unlocked att phone, will rooting the phone affect anything with Straight Talk? I am new to rooting so please be detailed and give me links to get everything I need. Thank You so much.
zeus1911 said:
Hello, I was just wondering the best way to root the AT&T Samsung Note SGH-I717. I have looked up many ways but every time I scroll down to the comments I read everyone is having problems. I would just like the best and most proven way to root the phone. I use the phone with straight talk, it is an unlocked att phone, will rooting the phone affect anything with Straight Talk? I am new to rooting so please be detailed and give me links to get everything I need. Thank You so much.
Click to expand...
Click to collapse
so here is the deal, here are 2 methods with very subtle differences. you didn't say what your phone was running now, so here are my suggestions.......
READ, READ, READ
I know you are new here, and I was once too. I went through all of this and was very nervous about the process. (no real reason to be)
I spent a good 2 weeks reading so I would feel confident about what I was doing. I would read through these and figure which is better for you or which you feel more confident in using. they would both work fine depending on your situation or what you phone is running. because these threads are older, you may run into an issue as to where the download files are not active anymore. that is where a recent Google search could come into play. you say you have read the comments for different methods have had negative results. problem is you don't know whether that person followed the directions correctly or whether they were just in a hurry and missed something.
that's why I posted both these threads. compare to what you have read. I have a habit of going to the back of the threads and read forward. this tells me what the most recent problems may have been and if there is a solution. though the files may or may not be active, you can always get the file. its the PROCESS which is correct. compare them.
as I said........... READ, READ, READ
it puts you in the situation to help yourself first
take your time, do as the process suggests. I even rehearsed it several times. due to my lack of experience, I wanted to be as prepared as possible in case something went wrong.
http://forum.xda-developers.com/showthread.php?t=1504218
http://forum.xda-developers.com/showthread.php?t=1518962
both of these threads are from very reputable members of the community. as all threads will suggest......they are NOT responsible for what you do. make sure you are ready. watch Youtube tutorals, compare processes, have your files loaded and where you have easy access, read and rehearse.
take your time
whatever you need to do to feel confident. if something goes wrong....KNOW what you are going to do next. if you don't know where you went wrong in process or deviated from it, then others cant help.
good luck and I hope I have helped
edit.......
just saw this...this is at the back of Da G 's thread. suggested by AGOATTAMER. he is the man when it comes to having old links to process. this IS the one I used, that I couldn't find.
http://rootgalaxynote.com/galaxy-no...y-note-sgh-i717-icsgingerbreadeasiest-method/
Thanl You Very Much. I am running 4.1.2 jelllybean.
Sent from my SAMSUNG-SGH-I717 using XDA Free mobile app
Related
I wanted to contribute something to the development but I'm a dumby when it comes to code. For a living I coordinate techs and developers with end users, basically I'm a tech-speak translator. I've notice that around these parts there are a ton of questions that could be easier resolved by following some guidelines. So this guide isn't about how to root or rom specifically, it's tips to avoid common mistakes and make it easier to provide you with help if something does go wrong. Think of it like when you call your cable help line and they ask you "is it plugged in" if you checked to make sure it was plugged in before you called you'll get to a solution a lot quicker.
I ask that any devs who can add to this do because knowing what us regular users can do to make your job (unpaid job that is) easier benefits us all.
Back up
This is super important but a lot of us are in such a rush to play with the goodies that we skip it. Always always keep a current back up of your sd card on your pc/mac. You can create a folder called "mytouchbak" or whatever you want and just copy and paste all the files over there.
Also nandroid backup. You should keep at least 2 nandroid backups. If you're just now rooting make a nandroid back up before you do anything. Then once you have a good stable rom running make another nandroid back up. This way you can either return to a default build, or to your working rom build.
These things are important because usually if you screw something up it's usually quicker and easier to just start from the beginning rather than have someone try to figure out what tiny step out of the many involved you may have done wrong, then figure out how to fix it.
Try twice
This relates to "back up." If something seems broken start from the beginning and try it again. Most likely you missed a step, forgot a symbol in something you typed, or sometimes something just didn't quite go right. By rooting you are doing things that weren't meant to be done and sometimes some numbers just got crossed somewhere. Before you proclaim that things are broken just try it again. You would be suprised by the number of times things work the second time through.
Read the whole thread
We have all done it. You follow the instructions perfectly and something doesn't work so you run to the forum and immediately write a post saying "help, i can't get it to work" on page 80 of a thread when several other people experienced the same problem, already asked the question and a solution was posted on page 20. I know it's sometimes a pain to skim 80 pages of posts but those 80 pages are probably caused by other people not reading the thread before posting. A good tip for this is if there is something specific that isn't working like wi-fi tether, just open the search toolbar in your browser, type "tether" and then go to each page hitting search. That way you don't have to read every post but if anyone has mentioned anything about tethering it will point you right to it and you only have to read those posts.
Have a computer ready
This is one that most of us already do but the one time you forget things always go bad. Don't ever rely on remembering the instructions you read on your phones browser when working on rooting and romming. If you have a computer in front of you you can read the forums and follow the instructions word for word which gives you a better chance of success.
Read everything first
Before you start read everything from start to finish at least once. Sometimes devs skip steps that they assume we know and then mention them later. It's because a lot of things seem like something everyone should know, but we don't. In the same vein if you can find multiple tutorials read them all first. This will give you several view points on doing the same thing and will in general make the whole process make more sense to you and clue you in on things one tutorial may have skipped past.
The other benefit is sometimes a step is listed, and then right after it it will say something like "and don't do that until you do this." such as with our current rooting loop method. If you read all the steps first before starting you won't be caught off guard by things like this.
Asking for help
When you get stuck, you can't find any answers AFTER READING AND SEARCHING THE FORUM for your issue then definitely ask away. How you ask relates to how easily it is for someone to help you.
Avoid making general statements when possible, detail is a must. Instead of saying "I rooted, then did A2SD, then restarted" give the steps you took to root and A2SD by either referencing the method such as "I rooted as per the steps laid out in (link to instructions or name of method) or lay out the exact steps line for line as to what you did. If you assume you rooted right and what went wrong was you missed a step in the rooting process how is anyone supposed to tell you what step you missed.
Also format it to be easy to read. Development trains your mind to be very organized and structured. Basically don't format your post like this guide I'm writing, in large blocks of paragraph text. Instead put each command on a new line for instance:
"I did this
adb shell
adb push update.zip /sd
reboot into recovery....."
this makes it a lot easier to provide you with help.
Slow down, Find a good time
Don't rush through the process. That's how steps are missed, commands are mistyped and phones get bricked. I've done roots at 2am and couldn't for the life of me get it to work, I put it away and tried again in the morning and things went great. So don't mess with rooting and romming when you're exhausted, in a hurry, high, in the midst of an argument with your girlfriend, or any sort of other distractions.
That's all I have for now, I hope it helps. If anyone has anything to add please do.
great guide, most of us probably follow these general rules without really thinking about it and sometimes that is overlooked when a new guy comes in to try to do something.
tubaking182 said:
great guide, most of us probably follow these general rules without really thinking about it and sometimes that is overlooked when a new guy comes in to try to do something.
Click to expand...
Click to collapse
Thank you. I notice that happen a lot in my job where someone with no experience in the particular tech get's lost because the things we take for granted as common knowledge really aren't for someone new to the idea. Especially with the android devices becoming insanely popular theres a huge influx of new users looking at the goodies that come with root. install a custom rom or two and everything above becomes second nature.
skullkandy said:
Slow down, Find a good time
Don't rush through the process. That's how steps are missed, commands are mistyped and phones get bricked. I've done roots at 2am and couldn't for the life of me get it to work, I put it away and tried again in the morning and things went great. So don't mess with rooting and romming when you're exhausted, in a hurry, high, in the midst of an argument with your girlfriend, or any sort of other distractions.
Click to expand...
Click to collapse
So that's why I was having problems.
this tut is NOW IN SLIDE BIBLE! just send people there any chance you get with noobs, and we'll let them search
Aweome idea for a post! Thanks!
Sent from my T-Mobile myTouch 3G Slide using XDA App
Thanks for all the positive feedback guys. And especially thank you for getting this posted into the slide bible. I hope this cuts down on some of the repeat questions and makes it easier for some of the new folks to not be so overwhelmed when rooting for the first time.
@Bigshow281 : I have screwed up several rootings by being a little bit too foggy to be messing with something that requires precise typing and following instructions correctly.
I freely admit that I'm a Newbie when it comes to rooting; this post is to ask if anyone can please recommend a good source of reading matter to help me get started rooting my Streak?
AidanBell said:
I freely admit that I'm a Newbie when it comes to rooting; this post is to ask if anyone can please recommend a good source of reading matter to help me get started rooting my Streak?
Click to expand...
Click to collapse
There are several threads and even a sticky you'd have to be blind or flat lazy to miss to not have seen it with ALL the info you need
Please note the word "Newbie". I have indeed found many threads and pages, all of which dive into the subject as if it's second nature. I don't even know what a "Sticky" IS! I'm an intelligent person, PC literate, perfectly capable of rooting a phone, I'm sure. But I have utterly no experience of doing so. I'm sure there are many people in my position, and I'm simply looking for a user-friendly starting point. Thanks.
AidanBell said:
Please note the word "Newbie". I have indeed found many threads and pages, all of which dive into the subject as if it's second nature. I don't even know what a "Sticky" IS! I'm an intelligent person, PC literate, perfectly capable of rooting a phone, I'm sure. But I have utterly no experience of doing so. I'm sure there are many people in my position, and I'm simply looking for a user-friendly starting point. Thanks.
Click to expand...
Click to collapse
Hey - I was lost when I first started to flash my first rom. I found a number of different sources which all helped in their own little way. I'll gladly talk you through each step. Have you rooted your phone yet? There is an excellent video on (youtube.com/watch?v=60z9YBv9Ksw) youtube to help you along - visit the unlockr's how to's also (//theunlockr.com/category/howto/android_how_tos/dell-streak-how-tos/)
Many thanks thecelticchimp. I'm gonna check the links you've kindly given and if there's enough there to give me a basic grounding then I'll bite the bullet and do the deed this evening.
read the top 5 or 6 threads
http://forum.xda-developers.com/forumdisplay.php?f=698
thecelticchimp said:
Hey - I was lost when I first started to flash my first rom. I found a number of different sources which all helped in their own little way. I'll gladly talk you through each step. Have you rooted your phone yet? There is an excellent video on (youtube.com/watch?v=60z9YBv9Ksw) youtube to help you along - visit the unlockr's how to's also (//theunlockr.com/category/howto/android_how_tos/dell-streak-how-tos/)
Click to expand...
Click to collapse
Oh dear, foiled at the first hurdle! My phone's build number is 15609. Theunlockr.com sends me to
http://android.modaco.com/topic/316229-19aug-streak-21-downloads-how-tos-rom-superboot-recovery/
where I can't find any reference to that build number, therefore can't find the necessary Superboot files.
Help? ... !
Your first problem is trying to use Superboot. You don't need to, and it's not recommended to use it in any event. All you need to know is how to use Fastboot properly.
The second problem is that you're trying to do this cold. For a bit of an assist, try looking in the apparently little known Wiki on the site here. There is a flashing guide for the Dell Streak there and one very critical piece of advice on it that is a must read, though duplicated on some of the threads.
I am going to recommend that you spend some time reading up before attempting to flash the Streak, or you will very likely end up with a nice, shiny, and very expensive paperweight.
OK, for the moment I'm going to be content with a factory reset and no root.
I think if one of you experts out there fancies a little project it would be to write exactly what the sarcastic "No spoonfeeding here" signature doesn't want; a "Rooting for beginners" guide.
I'm told I don't need to use Superboot, but I thought Superboot WAS rooting. Truth be told all I wanted to do was to be able to uninstall unwanted pre-loaded software on my Streak, not much more than that.
Despite kind people's encouraging words that rooting is now very straightforward, Strephon's timely warning reminds me that it isn't. I think I'll take the easy way out and wait until someone IS prepared to spoon feed me!
Sticky posts are set up so that they never disappear from page 1 of the forum you are reading. They are also so that critical information, such as how to root the streak without bricking it, is easy to find. Rooting the Streak is quite easy; far easier than other devices. Yet it's still possible to brick it if you do not read up on what you're supposed to be doing.
If you were truly a noob I'd have given you a link. However, you have been with the site a while, and thus you should by now know the rules, especially rule 1: search before you post. Thus, no spoonfeeding for you. Use the search engine and the stickies. That is why we have them.
Duly ticked off! Many thanks for the help and advice, I'll start reading...
Cheers,
Aidan
I am a new Xperia Ultra owner and whilst not planning to do any flashing just yet I thought tonight I'd take a quick look at threads discussing steps that would be involved in doing this.
Let me qualify what I'm about to say by stating that I appreciate people on this site who develop tools which allow us to hack our devices so we can make better use of our phones. They are incredibly skilled, gifted and generous with their time. I would love to be able to spend the time learning how to do this but I simply don't have the time. So please don't take what I am about to say as a criticism but more as an observation, considering the effort contributors put into this it would indeed be incredibly foolish of me to criticise anyone here.
I can probably safely say that none of the contributors are also trained technical writers and a fair number do not have English as their first language. Its my first and only language and I often have difficulty getting the meaning across succinctly not to mind getting the spelling right . And I know even for large software houses support documentation is not a priority.
I want to approach hacking my phone with confidence this time round. In the past I've reflashed several phones for myself and friends and simply followed steps and not really understanding completely what the hell I was doing. Lordmanhattan I know I sent you an email regarding a contradiction on your thread. And you very kindly got back to me very quickly.....amazing, thank you. And then there is the "TA partition", WTH is that? I did very briefly google this to find a quick answer but no joy....grrrr (also looked in the XDA Wiki acronyms) I'm sure if I looked hard enough I'd find it. It's mentioned everywhere but nobody seems to be offering an explanation what it is or what it does or why it's important or what it stands for !!!!
Very often I find threads on here describing how to do something hard to follow and this is often for the following reasons:
It could be that there is more than one way to achieve something so its a case of different people offering varied procedures, this can be confusing
A process may be described but then to the newbie the author seems to miss out on a step that to the experienced is obvious
The level of English used leads the reader to scratching their head wondering ...did he/she mean this or that
Threads not being updated or corrected even after feedback
Okay I won't go on.
So I have decided my time might be well spent doing some background research before delving into messing about with my Xperia Z Ultra and saving you guys from having to deal with daft questions from me.
Now does this mean I have to spend time reading through threads and trying to piece it all together to find the best way through and possibly getting the wrong end of the stick or reading superseded posts?
OR
Are there a couple of sites that will get me up to speed understanding the terminology, hardware, memory management, etc for my phone?
I have a feeling it's going to be a bit of both......your suggestions please
Oh, I stumbled across XDA University but got the impression it wasn't being maintained???
Some of the pages I visited....
A New User’s Guide to Android.......unfortunately none of the images for this page loaded
Video guides .................................had flash presentations which didn't load
Ferg8080 said:
I am a new Xperia Ultra owner...
Click to expand...
Click to collapse
A good and detailed post, and it's not just the dev's and support that could take note. Some of the people that ask questions really need to read your post and think about what they are trying to say, get help with -- we aren't mind readers either.
I always try and help anew user by using as few TLA as possible in a reply to them. I also try to do the steps as #'d lists with as many steps as possible.
I do think LordManhattan's guide needs a little love as a few things are a little out of date - but it is as comprehensive guide as you could get, and most vagaries are covered in the thread.
TA = trim area, where your unique DRM keys are stored, and god only knows what else.
Thanks for your well written post! First I want to say - like Blueether just did, that we are not mind readers, so we can't possible know people's skill level or what they want to do. That's why I've started to ask them straight up what they want to do and where in the process they are. That way it'll be easier for me to help the other person, and hopefully write a short but complete step by step guide. It won't happen that often, but if I got some time to spare, why not.
My guide is a little out of date now, and I have planned to update it for quite some time, but things are moving so god damn quick around here that even I will get outdated if I take a short break. I recently sent my Ultra in for repairs, and 12 days later when I got it back and ready to get back in the game, a new firmware had been released with a new rooting method. I knew everything one day, and nothing on the other. It's really hard to balance real life and being kept updated at all times. Don't forget that you must be sure about what you know and write when you make a guide, because you don't want to brick people's devices. One slipup and the consequences might be ugly.
There are (of course) one or four ways of doing things around here, and you'll probably get different ways of doing things if you ask me or blueether about rooting or flashing custom ROMs. I guess it's just the way it is. New methods also pop up once in awhile, so some people will adopt these new methods while some other people will stick with the old school method, thus making things a little more complicated for new people who are looking for reliable information.
The TA partition is, like blueether already said, your device's unique DRM keys which makes X-Reality (and other minor things, I guess) work. It's important to make a backup of this partition since you'll lose it when you unlock the bootloader. Why would you unlock the bootloader? You have to unlock it if you want to flash custom ROMs, or if you want to make rooting easier. The problem is that you need to be rooted to back it up, so you'll have to spend some time reading and researching before you start.
Just keep your Ultra stock for now, and just casually read and soak up stuff from different threads around here. Walk around like you do in a new city and check out the locals and see what they do and say. You'll pick up a few things here and there and things will start rolling from there.
Sent from my C6806_GPe using Tapatalk
blueether said:
A good and detailed post, and it's not just the dev's and support that could take note. Some of the people that ask questions really need to read your post and think about what they are trying to say, get help with -- we aren't mind readers either.
Click to expand...
Click to collapse
LordManhattan said:
a new firmware had been released with a new rooting method. I knew everything one day, and nothing on the other. It's really hard to balance real life and being kept updated at all times. Don't forget that you must be sure about what you know and write when you make a guide, because you don't want to brick people's devices. One slipup and the consequences might be ugly.
some other people will stick with the old school method, thus making things a little more complicated for new people who are looking for reliable information.
Just keep your Ultra stock for now, and just casually read and soak up stuff from different threads around here.
Click to expand...
Click to collapse
Yes you can see some people just rush in with questions without giving serious thought to what they want to achieve. I think its people who don't often understand the process properly, haven't thought it through and are following what seems like a straightforward step by step process. Understanding what you are doing requires patience and TIME.
XDA I think is an unrivalled repository of amazing contributions from amazing people on a technology that is constantly evolving. Its also a jungle. One doesn't go into the jungle unprepared
Thanks for the fantastic advice guys and I will heed but I can't promise I might come out with some corkers
One last thing, how on earth do you find the time to lead a normal life? You obviously love what you are doing. It might be easy to assume everyone who contributes here is in IT. I imagine there are plumbers, electricians, mechanics, office workers, retired folk.....
Sooo, Ill start off by saying that I've unlocked, hacked, rooted, jailbroke pretty much every phone since it became available over the years. Im a careless tinkerer and have always stumbled across well written how to's to do everything I've need in forums like this and have great luck.
Well awhile ago, shortly after I got my AT&T M8, I decided to try and turn it into Google Play Edition. Somewhere along the way while in the process of doing S-OFF, something went wrong. I kept getting errors and couldn't get anything to flash. So I gave up and got the LG G3 and put the M8 aside for a bit. Well now I want to use it again, and along the way of "tinkering", I've managed to wipe TWRP, relocked the bootloader, have no OS and still S-OFF. I can boot into recovery or boot to the HTC screen so its not completely gone yet from what Ive researched.
Would anyone be willing to help me out in getting this thing back to stock Sense or point me in the right direction? I want it completely stock, without root or custom recovery. I'd rather a good step by step, if someone would be willing. I can't seem to piece together all of the information i need to do this myself. Thanks!
Have you tried this. http://forum.xda-developers.com/showthread.php?p=55094112
StupidN00b said:
Im a careless tinkerer and have always stumbled across well written how to's to do everything I've need in forums like this and have great luck.
Click to expand...
Click to collapse
Just RUU as suggested in the previous response.
I suggest leaving your phones stock, unless you are willing to put in the time to read, research, and obtain some real knowledge.
Step-by-step guides and toolkits are dangerous things. As you see, they just get you into trouble without giving you the knowledge or tools to get out of that jam.
I'm surprised you've modded as many phones as you say, and haven't gotten any real knowledge to this point. Either you are very humble; or your story is a testament to the fact that such step-by-step guides shouldn't be posted in the first place.
redpoint73 said:
Just RUU as suggested in the previous response.
I suggest leaving your phones stock, unless you are willing to put in the time to read, research, and obtain some real knowledge.
Step-by-step guides and toolkits are dangerous things. As you see, they just get you into trouble without giving you the knowledge or tools to get out of that jam.
I'm surprised you've modded as many phones as you say, and haven't gotten any real knowledge to this point. Either you are very humble; or your story is a testament to the fact that such step-by-step guides shouldn't be posted in the first place.
Click to expand...
Click to collapse
Thank you for your response but unfortunately I find it extremely arrogant and asinine. The fact is that I have put in a lot of time and knowledge to understand what I am doing. I may not have a conventional degree in coding as you might but I am able to successfully mod my phones by browsing forums like this where you can find an abundance of knowledge, especially step-by-step guides, as you are so against. If you are so against step by step guides then maybe you can be the voice about banning them from this forum. Do you see how I am a new member? I am one of the few that actually search the forums instead of posting another thread asking the same questions. Ive used tools and information from this site for a very long time without having to post one single thing until a few days ago. And this is the response I get? I was even humble enough in my screen name to call myself stupid because, with this specific issue, I knew it had to be something stupid that i was missing. You shouldn't tell people that step by step guides are dangerous things. All it takes is some balls and some command lines and you can accomplish many things. Have I messed up my phones and others before? Yes, but i had never run into a situation I haven't been able to get myself out of. To me, tinkering around, as a hobby, is fun. Like now, as I watch Sunday NFL Countdown, I am about to dust off my Nexus 5 and flash Lollipop on it. Guess what I am going to use? A STEP BY STEP GUIDE!!!! If I mess it up, then Im sure I wouldn't be the first to do so and Im sure Ill find a solution on great forums like this. Besides, my rooted/unlocked OnePlus One is my main phone. I wanted to play around with the M8 again to see if I would miss the smaller screen but I don't. So, thank you for just repeating the first response then proceeding to insult me because you think i don't have the skills needed to mod my devices. I will continue to do so however I please, just as many others will. Either contribute to threads or ignore them. No need for the insults. You've also insulted many other members who have posted tools and step by step guides on this specific site.
nuwayman said:
Have you tried this. http://forum.xda-developers.com/showthread.php?p=55094112
Click to expand...
Click to collapse
I actually did RUU but it ended up that I had a corrupt RUU file. I redownloaded it and put it on the MicroSD card and it worked like a charm. Thank you for your quick response.
StupidN00b said:
Thank you for your response but unfortunately I find it extremely arrogant and asinine.
So, thank you for just repeating the first response then proceeding to insult me
Click to expand...
Click to collapse
Quite frankly, incorrect on both points. You don't understand what an insult is, and there is nothing insulting in my post. If you read my post carefully, you will see there is no actual personal attack or insults.
redpoint73 said:
Just RUU as suggested in the previous response.
Click to expand...
Click to collapse
Contrary to what you suggest, backing up the previous suggestion is added value; as it adds credibility and consensus to the previous solution.
redpoint73 said:
I suggest leaving your phones stock, unless you are willing to put in the time to read, research, and obtain some real knowledge.
Click to expand...
Click to collapse
Its just a suggestion, and note that its conditional. Therefore, if you meet the latter part of the statement, the first part doesn't apply to you.
redpoint73 said:
Step-by-step guides and toolkits are dangerous things. As you see, they just get you into trouble without giving you the knowledge or tools to get out of that jam.
Click to expand...
Click to collapse
I stand by this statement. I've seen dozens dozens of instances where such tools just arm people with enough "knowledge" to get them into trouble, and don't equip them with any tools to get them out. Its then left to folks like me to even start to get these folks on the right track.
I'll step back a bit from my statement that these tools "shouldn't be posted in the first place". I'll agree that step-by-step guides and toolkits might be useful if combined with the proper research, learning and understanding. But in and of themselves, they can easily lead newcomers astray.
redpoint73 said:
I'm surprised you've modded as many phones as you say, and haven't gotten any real knowledge to this point. Either you are very humble; or your story is a testament to the fact that such step-by-step guides shouldn't be posted in the first place.
Click to expand...
Click to collapse
I already gave you the benefit of the doubt here, but you chose to react defensively and in my opinion, unreasonably.
In any case, as far as your knowledge and background, we can only go by what you've stated; and you clearly stated yourself as a "careless tinkerer" and "stumbled" upon solutions. Now in your later post you say "I have put in a lot of time and knowledge to understand what I am doing". So if you provide conflicting information as to your background, nobody can be blamed for making an incorrect assumption regarding your knowledge.
Greetings people here, nice to meet you guys but aside that I could use some assistance. All knowledge/experience I have with rooting have come from here and it has helped me quite a bit in the past with my old phone (Samsung Galaxy Light). Rooting that thing was simple and I have recently made the jump to a Galaxy S5 (SM-G900T3) and being the idiot I am I upgraded to the newest version (G900T3UVS1FOL1). I have looked around and around the internet for info on this firmware as well as my model of phone but I have found few pieces of information that include both. Fear has been keeping me from doing too much as this is the most expensive phone I have ever gotten and having very little funds I want to be sure of everything. I understand risks come with rooting and such but covering all the bases can't bee too bad right?
From what I gather there is no way around using Odin to do something that will let me root this thing. While I haven't used the program before I trust there are enough tutorials online involving the program that I can figure my way around that thing. What troubles me is that I see many files/tutorials for different versions (FOG, FOF, FOJ, ect...) not to mention numbers past those things. Also the staggering times I see someone mention SM-g900t and ONLY that one with the occasional person ask if it is similar to sm-g900t3. Long post yeah but I am concerned and as far as I'm aware more info for these kinds of questions leads to faster results and better times for those trying to help.
I would post links to images to show more info but my account is new so...yeah, sorry about that. Aside that thanks for taking the time to read my rather long post and thanks again for all that offer any assistance.
Ennen said:
Greetings people here, nice to meet you guys but aside that I could use some assistance. All knowledge/experience I have with rooting have come from here and it has helped me quite a bit in the past with my old phone (Samsung Galaxy Light). Rooting that thing was simple and I have recently made the jump to a Galaxy S5 (SM-G900T3) and being the idiot I am I upgraded to the newest version (G900T3UVS1FOL1). I have looked around and around the internet for info on this firmware as well as my model of phone but I have found few pieces of information that include both. Fear has been keeping me from doing too much as this is the most expensive phone I have ever gotten and having very little funds I want to be sure of everything. I understand risks come with rooting and such but covering all the bases can't bee too bad right?
From what I gather there is no way around using Odin to do something that will let me root this thing. While I haven't used the program before I trust there are enough tutorials online involving the program that I can figure my way around that thing. What troubles me is that I see many files/tutorials for different versions (FOG, FOF, FOJ, ect...) not to mention numbers past those things. Also the staggering times I see someone mention SM-g900t and ONLY that one with the occasional person ask if it is similar to sm-g900t3. Long post yeah but I am concerned and as far as I'm aware more info for these kinds of questions leads to faster results and better times for those trying to help.
I would post links to images to show more info but my account is new so...yeah, sorry about that. Aside that thanks for taking the time to read my rather long post and thanks again for all that offer any assistance.
Click to expand...
Click to collapse
I might suggest you read: http://forum.xda-developers.com/tmo.../compilation-s5-g900t-stock-firmware-t3042400. Just find the info for your phone. For the most part, using Odin is easy. If you used Heimdall to root your previous phone, you might want to use a different computer because the two programs can conflict with each other.