Here’s the four step process anyone can use to root their using One Click Root: Step 1) Download One Click Root Step 2) Connect your to your PC using your standard USB cord Step 3) Enable USB debugging on your device from the Developer Options menu Step 4) Run One Click Root the software will automatically complete all remaining steps!
Root galaxy s2 t989 android root APK 2019
Easy Step By Step manual, 100% working method. Free download top popular app for android root root galaxy s2 t989 with/without PC MAC IOS or windows 10, 8.1, 8, 7, XP computer .
Select android version for root galaxy s2 t989:
Root galaxy s2 t989 for android Gingerbread 2.3.3 - 2.3.7 2010 year
- Android version: android Gingerbread 2.3.3 - 2.3.7 2010 year
- Country: All
- How to Android root , see Instructions:Follow Tutorial
- Download Size: 2.38 MB
- Updated: 30 January 2019
- Last version APK file: 9.2
Get Android root APK
Root galaxy s2 t989 for android Ice Cream Sandwich 4.0.3 - 4.0.4 2011 year
- Android version: android Ice Cream Sandwich 4.0.3 - 4.0.4 2011 year
- Country: All
- How to Android root , see Instructions:Follow Tutorial
- Download Size: 4.59 MB
- Updated: 10 April 2019
- Last version APK file: 2.4
Get Android root APK
Root galaxy s2 t989 for android Jelly Bean 4.1.x 2012 year
- Android version: android Jelly Bean 4.1.x 2012 year
- Country: All
- How to Android root , see Instructions:Follow Tutorial
- Download Size: 4.53 MB
- Updated: 03 January 2019
- Last version APK file: 8.2
Get Android root APK
Root galaxy s2 t989 for android Jelly Bean 4.2.x 2012 year
- Android version: android Jelly Bean 4.2.x 2012 year
- Country: All
- How to Android root , see Instructions:Follow Tutorial
- Download Size: 8.07 MB
- Updated: 29 April 2019
- Last version APK file: 2.3
Get Android root APK
Root galaxy s2 t989 for android Jelly Bean 4.3 2013 year
- Android version: android Jelly Bean 4.3 2013 year
- Country: All
- How to Android root , see Instructions:Follow Tutorial
- Download Size: 2.72 MB
- Updated: 11 August 2018
- Last version APK file: 2
Get Android root APK
Root galaxy s2 t989 for android KitKat 4.4 2013 year
- Android version: android KitKat 4.4 2013 year
- Country: All
- How to Android root , see Instructions:Follow Tutorial
- Download Size: 3.65 MB
- Updated: 15 December 2018
- Last version APK file: 9.9
Get Android root APK
Root galaxy s2 t989 for android Lollipop 5.0 2014 year
- Android version: android Lollipop 5.0 2014 year
- Country: All
- How to Android root , see Instructions:Follow Tutorial
- Download Size: 2.51 MB
- Updated: 08 February 2019
- Last version APK file: 8.3
Get Android root APK
Root galaxy s2 t989 for android Lollipop 5.1 2015 year
- Android version: android Lollipop 5.1 2015 year
- Country: All
- How to Android root , see Instructions:Follow Tutorial
- Download Size: 2.01 MB
- Updated: 14 July 2018
- Last version APK file: 9.6
Get Android root APK
Root galaxy s2 t989 for android Marshmallow 6.0 2015 year
- Android version: android Marshmallow 6.0 2015 year
- Country: All
- How to Android root , see Instructions:Follow Tutorial
- Download Size: 5.61 MB
- Updated: 16 November 2018
- Last version APK file: 4.9
Get Android root APK
Root galaxy s2 t989 for android Nougat 7.0 2016 year
- Android version: android Nougat 7.0 2016 year
- Country: All
- How to Android root , see Instructions:Follow Tutorial
- Download Size: 8.3 MB
- Updated: 22 April 2019
- Last version APK file: 5.8
Get Android root APK
Root galaxy s2 t989 for android Nougat 7.1 2016 year
- Android version: android Nougat 7.1 2016 year
- Country: All
- How to Android root , see Instructions:Follow Tutorial
- Download Size: 5.81 MB
- Updated: 26 August 2018
- Last version APK file: 6.6
Get Android root APK
Root galaxy s2 t989 for android Oreo 8.0 2017 year
- Android version: android Oreo 8.0 2017 year
- Country: All
- How to Android root , see Instructions:Follow Tutorial
- Download Size: 3.5 MB
- Updated: 29 April 2019
- Last version APK file: 4.3
Get Android root APK
Root galaxy s2 t989 for android Oreo 8.1 2017 year
- Android version: android Oreo 8.1 2017 year
- Country: All
- How to Android root , see Instructions:Follow Tutorial
- Download Size: 5.61 MB
- Updated: 15 October 2018
- Last version APK file: 6.1
Get Android root APK
Root galaxy s2 t989 for android Pie 9.0 2018 year
- Android version: android Pie 9.0 2018 year
- Country: All
- How to Android root , see Instructions:Follow Tutorial
- Download Size: 8.85 MB
- Updated: 12 February 2019
- Last version APK file: 8.6
Get Android root APK
Root galaxy s2 t989 for android Q 10.0 2019 year
- Android version: android Q 10.0 2019 year
- Country: All
- How to Android root , see Instructions:Follow Tutorial
- Download Size: 3.1 MB
- Updated: 09 May 2019
- Last version APK file: 5.8
Get Android root APK
Root galaxy s2 t989 for android All - universal version
- Android version: android All - universal version
- Country: All
- How to Android root , see Instructions:Follow Tutorial
- Download Size: 2.65 MB
- Updated: 16 May 2019
- Last version APK file: 9.8
Get Android root APK
Download Android version Now!
How To easy access android root for products: root apps, root tool, root download, app root, root phone, root king, root device, root tablet, mobile root, root samsung, mobile rooter app, kingo root android, .
All rights reserved. Unauthorized reproduction, in whole or in part is strictly prohibited.
ALSO SEE RELATION:
Kernel for the sgh-t989 aka S2 aka hercules Jelly Bean 4.1.2 TW
These are the release notes for Linux version 3. Read them carefully,as they tell you what this is all about, explain how to install thekernel, and what to do if something goes wrong.
WHAT IS LINUX?
Linux is a clone of the operating system Unix, written from scratch byLinus Torvalds with assistance from a loosely-knit team of hackers acrossthe Net. It aims towards POSIX and Single UNIX Specification compliance.
It has all the features you would expect in a modern fully-fledged Unix,including true multitasking, virtual memory, shared libraries, demandloading, shared copy-on-write executables, proper memory management,and multistack networking including IPv4 and IPv6.
It is distributed under the GNU General Public License - see theaccompanying COPYING file for more details.
ON WHAT HARDWARE DOES IT RUN?
Although originally developed first for 32-bit x86-based PCs (386 or higher),today Linux also runs on (at least) the Compaq Alpha AXP, Sun SPARC andUltraSPARC, Motorola 68000, PowerPC, PowerPC64, ARM, Hitachi SuperH, Cell,IBM S/390, MIPS, HP PA-RISC, Intel IA-64, DEC VAX, AMD x86-64, AXIS CRIS,Xtensa, Tilera TILE, AVR32 and Renesas M32R architectures.
Linux is easily portable to most general-purpose 32- or 64-bit architecturesas long as they have a paged memory management unit (PMMU) and a port of theGNU C compiler (gcc) (part of The GNU Compiler Collection, GCC). Linux hasalso been ported to a number of architectures without a PMMU, althoughfunctionality is then obviously somewhat limited.Linux has also been ported to itself. You can now run the kernel as auserspace application - this is called UserMode Linux (UML).
DOCUMENTATION:
- There is a lot of documentation available both in electronic form onthe Internet and in books, both Linux-specific and pertaining togeneral UNIX questions. I'd recommend looking into the documentationsubdirectories on any Linux FTP site for the LDP (Linux DocumentationProject) books. This README is not meant to be documentation on thesystem: there are much better sources available.
- There are various README files in the Documentation/ subdirectory:these typically contain kernel-specific installation notes for somedrivers for example. See Documentation/00-INDEX for a list of whatis contained in each file. Please read the Changes file, as itcontains information about the problems, which may result by upgradingyour kernel.
- The Documentation/DocBook/ subdirectory contains several guides forkernel developers and users. These guides can be rendered in anumber of formats: PostScript (.ps), PDF, HTML, & man-pages, among others.After installation, 'make psdocs', 'make pdfdocs', 'make htmldocs',or 'make mandocs' will render the documentation in the requested format.
INSTALLING the kernel source:
- If you install the full sources, put the kernel tarball in adirectory where you have permissions (eg. your home directory) andunpack it:orbzip2 -dc linux-3.X.tar.bz2 | tar xvf -Replace 'XX' with the version number of the latest kernel.Do NOT use the /usr/src/linux area! This area has a (usuallyincomplete) set of kernel headers that are used by the library headerfiles. They should match the library, and not get messed up bywhatever the kernel-du-jour happens to be.
- You can also upgrade between 3.x releases by patching. Patches aredistributed in the traditional gzip and the newer bzip2 format. Toinstall by patching, get all the newer patch files, enter thetop level directory of the kernel source (linux-3.x) and execute:orbzip2 -dc ../patch-3.x.bz2 | patch -p1(repeat xx for all versions bigger than the version of your currentsource tree, in_order) and you should be ok. You may want to removethe backup files (xxx~ or xxx.orig), and make sure that there are nofailed patches (xxx# or xxx.rej). If there are, either you or me hasmade a mistake.Unlike patches for the 3.x kernels, patches for the 3.x.y kernels(also known as the -stable kernels) are not incremental but instead applydirectly to the base 3.x kernel. Please readDocumentation/applying-patches.txt for more information.Alternatively, the script patch-kernel can be used to automate thisprocess. It determines the current kernel version and applies anypatches found.The first argument in the command above is the location of thekernel source. Patches are applied from the current directory, butan alternative directory can be specified as the second argument.
- If you are upgrading between releases using the stable series patches(for example, patch-3.x.y), note that these 'dot-releases' arenot incremental and must be applied to the 3.x base tree. Forexample, if your base kernel is 3.0 and you want to apply the3.0.3 patch, you do not and indeed must not first apply the3.0.1 and 3.0.2 patches. Similarly, if you are running kernelversion 3.0.2 and want to jump to 3.0.3, you must firstreverse the 3.0.2 patch (that is, patch -R) before applyingthe 3.0.3 patch.You can read more on this in Documentation/applying-patches.txt
- Make sure you have no stale .o files and dependencies lying around:You should now have the sources correctly installed.
SOFTWARE REQUIREMENTS
Compiling and running the 3.x kernels requires up-to-dateversions of various software packages. ConsultDocumentation/Changes for the minimum version numbers requiredand how to get updates for these packages. Beware that usingexcessively old versions of these packages can cause indirecterrors that are very difficult to track down, so don't assume thatyou can just update packages when obvious problems arise duringbuild or operation.
BUILD directory for the kernel:
![Root Root](/uploads/1/2/4/3/124354619/394844181.jpg)
When compiling the kernel all output files will per default bestored together with the kernel source code.Using the option 'make O=output/dir' allow you to specify an alternateplace for the output files (including .config).Example:kernel source code: /usr/src/linux-3.Nbuild directory: /home/name/build/kernel
To configure and build the kernel use:cd /usr/src/linux-3.Nmake O=/home/name/build/kernel menuconfigmake O=/home/name/build/kernelsudo make O=/home/name/build/kernel modules_install install
Please note: If the 'O=output/dir' option is used then it must beused for all invocations of make.
CONFIGURING the kernel:
Do not skip this step even if you are only upgrading one minorversion. New configuration options are added in each release, andodd problems will turn up if the configuration files are not set upas expected. If you want to carry your existing configuration to anew version with minimal work, use 'make oldconfig', which willonly ask you for the answers to new questions.
- Alternate configuration commands are:'make config' Plain text interface.'make menuconfig' Text based color menus, radiolists & dialogs.'make nconfig' Enhanced text based color menus.'make xconfig' X windows (Qt) based configuration tool.'make gconfig' X windows (Gtk) based configuration tool.'make oldconfig' Default all questions based on the contents ofyour existing ./.config file and asking aboutnew config symbols.'make silentoldconfig'Like above, but avoids cluttering the screenwith questions already answered.Additionally updates the dependencies.'make defconfig' Create a ./.config file by using the defaultsymbol values from either arch/$ARCH/defconfigor arch/$ARCH/configs/${PLATFORM}_defconfig,depending on the architecture.'make ${PLATFORM}_defconfig'Create a ./.config file by using the defaultsymbol values fromarch/$ARCH/configs/${PLATFORM}_defconfig.Use 'make help' to get a list of all availableplatforms of your architecture.'make allyesconfig'Create a ./.config file by setting symbolvalues to 'y' as much as possible.'make allmodconfig'Create a ./.config file by setting symbolvalues to 'm' as much as possible.'make allnoconfig' Create a ./.config file by setting symbolvalues to 'n' as much as possible.'make randconfig' Create a ./.config file by setting symbolvalues to random values.You can find more information on using the Linux kernel config toolsin Documentation/kbuild/kconfig.txt.NOTES on 'make config':
- having unnecessary drivers will make the kernel bigger, and canunder some circumstances lead to problems: probing for anonexistent controller card may confuse your other controllers
- compiling the kernel with 'Processor type' set higher than 386will result in a kernel that does NOT work on a 386. Thekernel will detect this on bootup, and give up.
- A kernel with math-emulation compiled in will still use thecoprocessor if one is present: the math emulation will justnever get used in that case. The kernel will be slightly larger,but will work on different machines regardless of whether theyhave a math coprocessor or not.
- the 'kernel hacking' configuration details usually result in abigger or slower kernel (or both), and can even make the kernelless stable by configuring some routines to actively try tobreak bad code to find kernel problems (kmalloc()). Thus youshould probably answer 'n' to the questions for'development', 'experimental', or 'debugging' features.
COMPILING the kernel:
- Make sure you have at least gcc 3.2 available.For more information, refer to Documentation/Changes.Please note that you can still run a.out user programs with this kernel.
- Do a 'make' to create a compressed kernel image. It is alsopossible to do 'make install' if you have lilo installed to suit thekernel makefiles, but you may want to check your particular lilo setup first.To do the actual install you have to be root, but none of the normalbuild should require that. Don't take the name of root in vain.
- If you configured any of the parts of the kernel as `modules', youwill also have to do 'make modules_install'.
- Verbose kernel compile/build output:Normally the kernel build system runs in a fairly quiet mode (but nottotally silent). However, sometimes you or other kernel developers needto see compile, link, or other commands exactly as they are executed.For this, use 'verbose' build mode. This is done by inserting'V=1' in the 'make' command. E.g.:make V=1 allTo have the build system also tell the reason for the rebuild of eachtarget, use 'V=2'. The default is 'V=0'.
- Keep a backup kernel handy in case something goes wrong. This isespecially true for the development releases, since each new releasecontains new code which has not been debugged. Make sure you keep abackup of the modules corresponding to that kernel, as well. If youare installing a new kernel with the same version number as yourworking kernel, make a backup of your modules directory before youdo a 'make modules_install'.Alternatively, before compiling, use the kernel config option'LOCALVERSION' to append a unique suffix to the regular kernel version.LOCALVERSION can be set in the 'General Setup' menu.
- In order to boot your new kernel, you'll need to copy the kernelimage (e.g. .../linux/arch/i386/boot/bzImage after compilation)to the place where your regular bootable kernel is found.
- Booting a kernel directly from a floppy without the assistance of abootloader such as LILO, is no longer supported.If you boot Linux from the hard drive, chances are you use LILO whichuses the kernel image as specified in the file /etc/lilo.conf. Thekernel image file is usually /vmlinuz, /boot/vmlinuz, /bzImage or/boot/bzImage. To use the new kernel, save a copy of the old imageand copy the new image over the old one. Then, you MUST RERUN LILOto update the loading map!! If you don't, you won't be able to bootthe new kernel image.Reinstalling LILO is usually a matter of running /sbin/lilo.You may wish to edit /etc/lilo.conf to specify an entry for yourold kernel image (say, /vmlinux.old) in case the new one does notwork. See the LILO docs for more information.After reinstalling LILO, you should be all set. Shutdown the system,reboot, and enjoy!If you ever need to change the default root device, video mode,ramdisk size, etc. in the kernel image, use the 'rdev' program (oralternatively the LILO boot options when appropriate). No need torecompile the kernel to change these parameters.
- Reboot with the new kernel and enjoy.
IF SOMETHING GOES WRONG:
- If you have problems that seem to be due to kernel bugs, please checkthe file MAINTAINERS to see if there is a particular person associatedwith the part of the kernel that you are having trouble with. If thereisn't anyone listed there, then the second best thing is to mailthem to me ([email protected]), and possibly to any otherrelevant mailing-list or to the newsgroup.
- In all bug-reports, please tell what kernel you are talking about,how to duplicate the problem, and what your setup is (use your commonsense). If the problem is new, tell me so, and if the problem isold, please try to tell me when you first noticed it.
- If the bug results in a message likeunable to handle kernel paging request at address C0000010Oops: 0002EIP: 0010:XXXXXXXXeax: xxxxxxxx ebx: xxxxxxxx ecx: xxxxxxxx edx: xxxxxxxxesi: xxxxxxxx edi: xxxxxxxx ebp: xxxxxxxxds: xxxx es: xxxx fs: xxxx gs: xxxxPid: xx, process nr: xxxx xx xx xx xx xx xx xx xx xxor similar kernel debugging information on your screen or in yoursystem log, please duplicate it exactly. The dump may lookincomprehensible to you, but it does contain information that mayhelp debugging the problem. The text above the dump is alsoimportant: it tells something about why the kernel dumped code (inthe above example it's due to a bad kernel pointer). More informationon making sense of the dump is in Documentation/oops-tracing.txt
- If you compiled the kernel with CONFIG_KALLSYMS you can send the dumpas is, otherwise you will have to use the 'ksymoops' program to makesense of the dump (but compiling with CONFIG_KALLSYMS is usually preferred).This utility can be downloaded fromftp://ftp..kernel.org/pub/linux/utils/kernel/ksymoops/ .Alternately you can do the dump lookup by hand:
- In debugging dumps like the above, it helps enormously if you canlook up what the EIP value means. The hex value as such doesn't helpme or anybody else very much: it will depend on your particularkernel setup. What you should do is take the hex value from the EIPline (ignore the '0010:'), and look it up in the kernel namelist tosee which kernel function contains the offending address.To find out the kernel function name, you'll need to find the systembinary associated with the kernel that exhibited the symptom. This isthe file 'linux/vmlinux'. To extract the namelist and match it againstthe EIP from the kernel crash, do:This will give you a list of kernel addresses sorted in ascendingorder, from which it is simple to find the function that contains theoffending address. Note that the address given by the kerneldebugging messages will not necessarily match exactly with thefunction addresses (in fact, that is very unlikely), so you can'tjust 'grep' the list: the list will, however, give you the startingpoint of each kernel function, so by looking for the function thathas a starting address lower than the one you are searching for butis followed by a function with a higher address you will find the oneyou want. In fact, it may be a good idea to include a bit of'context' in your problem report, giving a few lines around theinteresting one.If you for some reason cannot do the above (you have a pre-compiledkernel image or similar), telling me as much about your setup aspossible will help. Please read the REPORTING-BUGS document for details.
- Alternately, you can use gdb on a running kernel. (read-only; i.e. youcannot change values or set break points.) To do this, first compile thekernel with -g; edit arch/i386/Makefile appropriately, then do a 'makeclean'. You'll also need to enable CONFIG_PROC_FS (via 'make config').After you've rebooted with the new kernel, do 'gdb vmlinux /proc/kcore'.You can now use all the usual gdb commands. The command to look up thepoint where your system crashed is 'l *0xXXXXXXXX'. (Replace the XXXeswith the EIP value.)gdb'ing a non-running kernel currently fails because gdb (wrongly)disregards the starting offset for which the kernel is compiled.