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 am very Noob in this, but I have questions that I am sure that are gonna help a lot of people.
I am going to buy a cheap e-reader/tablet, and I have seen that the two best options are Nook Tablet and Kindle Fire.
The difference between the prices is 50USD, and I accept them. But I want to permanent root my device, so, the question is:
If I permanent root the Nook Tablet, will I be able to access all the device memory? Because without rooting it is limited to 1GB.. Will I be able to put for example 4gb of video without MicroSD?
Because if I cant access all the storage, I will have to buy a 16gb microSD.. So the difference between the two devices will be about 80USD, which is quite a lot.
The other questions are: Can you really access the Android Market and download apps if you root the Nook Tablet?
What does that means that the bootloader in the Nook tablet is locked? Is the rooting going to be unstable for that?
Thank you very much.
All these questions have been answered to other threads. Please read or search for them.
xdahgary said:
All these questions have been answered to other threads. Please read or search for them.
Click to expand...
Click to collapse
I have been in a lot of forums, and I know perfectly that before you ask, you have to search for your questions. I have been about half hours looking for them, and I have found different answers, so I need the real one.
Some answers say that you can only access all the memory for the installed apps, but not for all the medias.. others say that you always need a MicroSD card.. so, tell me please, which of those threads is the truth?
skipped said:
Some answers say that you can only access all the memory for the installed apps, but not for all the medias.. others say that you always need a MicroSD card.. so, tell me please, which of those threads is the truth?
Click to expand...
Click to collapse
The first one. You install to the internal, and can make folders (I suggest putting them in data or media, and not anywhere in the main directory) anywhere. Downloads from other app stores and ebook stores save all over the place, but usually by default to an SD card. Just learn to use a file manager and expect to root it.
It's easier to get every other application/store/video to run on a rooted Nook Tablet (compared to a KF), but it'll be much easier to make custom roms for a Kindle Fire due to the bootloader. What this means is that: if you have a kindle, you will sit around fiddling with rooting and unrooting if you want their Instant Video to work, until a whole new rom (entire OS overhaul) is available. In comparison you can root a Nook Tablet, and put whatever you want on it and run it and most things will work (if they're tablet apps, and depending on what stores you use), but it will be much harder to load a new OS on it, if ever. For someone who wants to hack and mod a tablet, they will want to do it on a device that is supports it (KF). For someone that wants to read books, play games, watch videos, read comics, very easily right off the bat (with 10 min of work), the Nook Tablet is better (and has a few important higher specs).
And the suggestion to find the many threads that answer your question wasn't "go out there and find other forums with lots of conflicting answers" but *SCROLL DOWN.*
skipped said:
I am very Noob in this, but I have questions that I am sure that are gonna help a lot of people.
I am going to buy a cheap e-reader/tablet, and I have seen that the two best options are Nook Tablet and Kindle Fire.
The difference between the prices is 50USD, and I accept them. But I want to permanent root my device, so, the question is:
If I permanent root the Nook Tablet, will I be able to access all the device memory? Because without rooting it is limited to 1GB.. Will I be able to put for example 4gb of video without MicroSD?
Because if I cant access all the storage, I will have to buy a 16gb microSD.. So the difference between the two devices will be about 80USD, which is quite a lot.
The other questions are: Can you really access the Android Market and download apps if you root the Nook Tablet?
What does that means that the bootloader in the Nook tablet is locked? Is the rooting going to be unstable for that?
Thank you very much.
Click to expand...
Click to collapse
There are definitive answers, so I don't know that you've searched all that much. However, to answer some of your questions:
Yes, you can install the market once rooted, and the bootloader being locked means that the simplest solutions for installing new ROMs will not work. People are trying workarounds at the moment, but there is no ETA. This has no bearing on having the device rooted.
I think it is also important to mention that until a verified means of preventing OTA updates to the system is created, it is possible your device to become un-rooted after it updates itself.
So far, I have seen no sure-fire ways to prevent the NT from updating itself - only guesses. So your "permanent root" may not be so permanent for the time being.
1. Yes
2. Yes
3. Means custom roms can't be created as of yet. Give it time.
Why do so many people keep repeating "over the air updates may remove root..." Maybe it will, maybe it won't. You must accept an OTA update. If you are worried about root, don't accept the update until you know what it will do. Seems simple to me.
Is there even a patch for the zergrush expolit?
dkb218 said:
1. Yes
2. Yes
3. Means custom roms can't be created as of yet. Give it time.
Why do so many people keep repeating "over the air updates may remove root..." Maybe it will, maybe it won't. You must accept an OTA update. If you are worried about root, don't accept the update until you know what it will do. Seems simple to me.
Click to expand...
Click to collapse
For the KF at least, its coming in the form of silent updates. Once you're on wifi, the update is pushed down.
Honestly its a hazard of the game until we have different roms. If they plug the hole, they plug it. I'm holding out for the ROM solution, regardless of elegant/inelegant the solution proves to be.
Sent from my Motorola Atrix w/CM7.1 with xda premium
JoeM01 said:
For the KF at least, its coming in the form of silent updates. Once you're on wifi, the update is pushed down.
Honestly its a hazard of the game until we have different roms. If they plug the hole, they plug it. I'm holding out for the ROM solution, regardless of elegant/inelegant the solution proves to be.
Sent from my Motorola Atrix w/CM7.1 with xda premium
Click to expand...
Click to collapse
True enough. Often inelegant=most effective. Same when I first rooted my TF101. Used the ADB root. Which meant I had to self-teach ADB. Best thing that happened as not only I achieved root but learned something new that has helped with other devices.
dkb218 said:
1. Yes
2. Yes
3. Means custom roms can't be created as of yet. Give it time.
Why do so many people keep repeating "over the air updates may remove root..." Maybe it will, maybe it won't. You must accept an OTA update. If you are worried about root, don't accept the update until you know what it will do. Seems simple to me.
Click to expand...
Click to collapse
If the NT does OTA updates like the NC there is no prompt to accept the update, just a message that the update occurred. It is not the same as a phone.
Sent from my BNTV250 using Tapatalk
I had rooted my Nook Color and then was running CM7 off the SD card. Eventually, the screen had issues, so I returned it (still under warranty) and got the Nook Tablet. I'm pretty much liking it stock, but would like to root it. (Ideally, I'd like to run an OS off the SD card again, but I understand that's not available yet.) I'm a little lost with all the different threads and links floating around. I want to be sure I'm using the latest, and most problem-free, method.
Can someone point me to the latest, and easiest, rooting link? Indirect's, yes?
Thanks, Lori
loribuono said:
I had rooted my Nook Color and then was running CM7 off the SD card. Eventually, the screen had issues, so I returned it (still under warranty) and got the Nook Tablet. I'm pretty much liking it stock, but would like to root it. (Ideally, I'd like to run an OS off the SD card again, but I understand that's not available yet.) I'm a little lost with all the different threads and links floating around. I want to be sure I'm using the latest, and most problem-free, method.
Can someone point me to the latest, and easiest, rooting link? Indirect's, yes?
Thanks, Lori
Click to expand...
Click to collapse
use indirect's root if you still want to keep the B&N experience (apps, books, etc)
use snowball mod if you want an almost pure android tablet (B&N is basically removed)
i like snowball mod cause i don't really use B&N services and it gets rid of bloatware which is always nice...
There is a thread that was just created for Noobs...just read that thread, very informative.
Edit: core is for...sorry spell checker
Core noobs? What does that mean? Obviously, I know what noobs mean, but not sure what you're referring to. Do you have a link?
loribuono said:
Core noobs? What does that mean? Obviously, I know what noobs mean, but not sure what you're referring to. Do you have a link?
Click to expand...
Click to collapse
There is a sticky thread in this forum with FAQ's.
jesus people provide the link at least without it, its not helping...
they might be referring to this http://forum.xda-developers.com/showthread.php?t=1415812
also this http://forum.xda-developers.com/showthread.php?t=1363334
I'm sure he meant "for noobs"
and I think this is the thread:
http://forum.xda-developers.com/showthread.php?t=1415812
you beat me to it Doctorword..
ha! no biggie glad there was another person helping
Fixed it with spell checker....Noob means newbie or someone who is new to a particular thing.
---------- Post added at 06:10 PM ---------- Previous post was at 06:06 PM ----------
Doctorword said:
jesus people provide the link at least without it, its not helping...
they might be referring to this http://forum.xda-developers.com/showthread.php?t=1415812
also this http://forum.xda-developers.com/showthread.php?t=1363334
Click to expand...
Click to collapse
I don't like to hold hands for anyone. Yes we were all new to things but before you jump in the water you should learn how to swim. People get on these forums, see root files and jump in and when they are drowning or have drowned expect to get a quick fix which isn't fair to those who do their homework and research...just saying. If I'm posting from my phone or tablet, I don't go out of my way to provide links; hence the reason I say search.
If I post asking a question it's after I did all my homework and once I don't locate, I'll ask because no one knows all the anwers.
man, sometime i think it is more effort for us to copy and past a link than it is for noobs to just take the initiative to read... ><; Not to take it out on this one poster, but i have seen many people post a question like "hey everyone I am new, update me on whats going on"... instead of just reading.
First, let me say, "Thank you," for your video, which was very helpful.
In response to what you wrote, I do read. I read quite a bit. Perhaps you've forgotten what it's like to learn something in a language you don't speak. When you're new to this stuff, every single thing you read contains something you don't understand. And you look things up and look things up, until you've got 20 windows open on different topics, in the hope that you can piece it all together, and remember what you were looking up in the first place. If I've spent more than 45 minutes merely trying to "find" the information I need, which is no small task with a search feature that doesn't let you search phrases, and another couple of hours sifting through the confusing information, I don't think it's a stretch to then turn to those in the know, on a newbie forum, for help.
Again, I appreciate very much what you guys (and girls) do. But you post it up here for people to use.
I don't know about other newbies, but sometimes I feel like I'm going to be flogged if I don't word things the right way or perform the prerequisite quantity of searching beforehand. I do my best.
Again, thanks to those of you who have helped me out.
albertwertz said:
man, sometime i think it is more effort for us to copy and past a link than it is for noobs to just take the initiative to read... ><; Not to take it out on this one poster, but i have seen many people post a question like "hey everyone I am new, update me on whats going on"... instead of just reading.
Click to expand...
Click to collapse
I'm posting from my phone and providing a link would be a LOT of work, so excuse my lack of linking.
There was a new method posted up that allows you to keep root and update to 1.4.1. The problem is that 1.4.1 will not allow sideloading from the browser, and the author doesn't hold your hand through the whole process. Its nowhere near as nooblet friendly as Indirects root method.
The learning curve is STEEP, some of us are still working on it. The faq sticky is AWESOME and has a ton of link to helpful stuff, incuding my own ADB guide.
Thanks for the new info!
The_Joe said:
I'm posting from my phone and providing a link would be a LOT of work, so excuse my lack of linking.
There was a new method posted up that allows you to keep root and update to 1.4.1. The problem is that 1.4.1 will not allow sideloading from the browser, and the author doesn't hold your hand through the whole process. Its nowhere near as nooblet friendly as Indirects root method.
The learning curve is STEEP, some of us are still working on it. The faq sticky is AWESOME and has a ton of link to helpful stuff, incuding my own ADB guide.
Click to expand...
Click to collapse
It's been a while since I've worked on this, and I still can't find anyone with a similar problem on xda. Does anyone have a clue what's going on with this thing?
First, I got it working just fine with CM7 installed to the nook itself, not running from an sd card. That worked for a bit, then it started just shutting off with no obvious reason.
Also, if I make any changes, like uninstalling apps, it goes right back after a reboot - which happens whether I want it to or not. This applies to changes done with CWM as well, even installing a new rom.
On top of that, it won't boot from an sd card, so that sucks too.
Lastly (I think, it's tough to keep track of all these problems) abd doesn't recognize the device, and for that matter the operating system doesn't either. I've been using Ubuntu Lucid if that matters, but it didn't have issues detecting the device before.
I'm pretty novice, but I think this is a very complicated problem in need of expert advice. Any answers, tips, advice, or pointing in the right direction for any of my problems here would be awesome. Does anyone have any ideas?
Thanks.
Dude you say your a novice thats one... Two you are being critical of people who volunteer on this stuff. You can't be serious. You obviously have not read the support threads because you are not the only one with these problems and those that have them also did not read enough initially and failed to follow some step. Moreover, even if your problem were unique who do you think you are getting upset at anyone but yourself for taking the risk. Read the support thread for cm7 Mr. Ungrateful... flash back to stock and leave this forum alone until you 1. Learn what it means to be grateful. 2. Learn to follow instructions. The end
it is impossible to stump xda...
rickyshortcuts said:
Dude you say your a novice thats one... Two you are being critical of people who volunteer on this stuff. You can't be serious. You obviously have not read the support threads because you are not the only one with these problems and those that have them also did not read enough initially and failed to follow some step. Moreover, even if your problem were unique who do you think you are getting upset at anyone but yourself for taking the risk. Read the support thread for cm7 Mr. Ungrateful... flash back to stock and leave this forum alone until you 1. Learn what it means to be grateful. 2. Learn to follow instructions. The end
Click to expand...
Click to collapse
Thanks, that reminds me, I did follow all steps to the letter without a hitch to get CM7 going. It wasn't until after it was running for a few days that this happened. Also, in the aftermath while trying to solve the problem, I did everything I can think of to completely brick the nook so that I might be able to use some of the methods here to unbrick.
And just to defend my good name, I think it's a stretch to imagine I've been critical of anyone. To reference your other post on these forums, perhaps you might reconsider how to be helpful. Let me help you out with that.
because it is SERIOUSLY a hard brick, then you gotta get serious about your attack on this sick puppy. get a #6 torx and open it up and get directly at the internal sd card ( which sounds like you have trashed... )
hth
.
let us know when you got it open...
Dude!!!
rickyshortcuts said:
Dude you say your a novice thats one... Two you are being critical of people who volunteer on this stuff. You can't be serious. You obviously have not read the support threads because you are not the only one with these problems and those that have them also did not read enough initially and failed to follow some step. Moreover, even if your problem were unique who do you think you are getting upset at anyone but yourself for taking the risk. Read the support thread for cm7 Mr. Ungrateful... flash back to stock and leave this forum alone until you 1. Learn what it means to be grateful. 2. Learn to follow instructions. The end
Click to expand...
Click to collapse
One: This was a completely pointless flaming. Two: For being a novice he seems to be a bit more informed than you are. This is an issue, however not a common one. And from what I have read in these forums there is not as yet a fix. Three: I didn't read any ungratefulness, criticism, nor any hint of being upset. And Four: If you can't help out or give any useful advice then maybe you should "leave this forum alone" until you learn to be more civil.
chuckweiss2 said:
Thanks, that reminds me, I did follow all steps to the letter without a hitch to get CM7 going. It wasn't until after it was running for a few days that this happened. Also, in the aftermath while trying to solve the problem, I did everything I can think of to completely brick the nook so that I might be able to use some of the methods here to unbrick.
And just to defend my good name, I think it's a stretch to imagine I've been critical of anyone. To reference your other post on these forums, perhaps you might reconsider how to be helpful. Let me help you out with that.
Click to expand...
Click to collapse
Well put, and Props.....
I don't know if I can help out but I think I can point you in the right direction.
http://forum.xda-developers.com/showthread.php?t=1619615
This seems to be a hardware problem, but I don't think anyone is sure what is causing this.
Good luck with finding a fix.
went and found a XDA link for res-erecting bricked devices. it by @adamoutler and looks like a goodie !
ModeDetect USBID Detector
http://forum.xda-developers.com/showthread.php?t=1257434
hth
.
( you can tell that Adam is passionate about his tech. what do they feed those boys down in Louisiana beside crawdads ? )
Alright, so thanks to old_fart and DavDoc I've determined two of my problems, and I think there are four.
First, DavDoc's linked thread describes perfectly what's happening with problem one, what I'm calling the Groundhog Day Syndrome for no particular reason. Any changes to my nook go right back after it's powered off.
Second, I checked out old_fart's linked thread and I'm pretty sure even though I have a blank screen it's still on in one mode or another. The program doesn't work though because of problem #3 (to be explained) but it seems sensible because to power it back on I must first hold the power button for an extended period of time and release, then hold it again for the normal power-up.
Problem number three is that the nook is not recognized by either Ubuntu or Windows when plugged in anymore. Thus that program not working, and also adb. I may be able to determine that one from error logs as soon as I figure out what in the world the error logs are saying.
Fourth and hopefully final, it won't boot from sd. I'll figure that out too.
Thanks for the advice so far, this forum is definitely indispensable for people who like to learn from playing with technology.
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