First off, I'm completely new to this and wish to root my new sgs2, and I've done some reading on the forum about this but got some questions (or want to confirm what I think I know) before I actually go ahead with the process. I apologize if it's something others have already asked, but I would really hate for anything to happen to what has become my new baby...
I mainly just want root access on my phone as I've come across several apps and what not that required root access.
My phone's status right now:
Android version: 2.3.3
Baseband: I9100XXKG1
Kernel Version: 2.6.35.7-I9100ZSKG2-CL361136 [email protected] #6
Build: GINGERBREAD.ZSKG2
I found (http://forum.xda-developers.com/showthread.php?t=1103399) about CF-Root. It seems like a lot of people recommend this method to root, so I thought I may try it out. Before I do though, I wanted to know:
- Just rooting my phone will not prevent me from receiving any new updates to my phone via Kies, right? (E.g. a new firmware or version comes out in the future...)
- What do I need to do if I wish to unroot in the future?
- For this method, this should be the one I should download and use right? (it's the closest one I found matching my current kernel): CF-Root-SGS2_ZS_OZS_KG2-v4.1-CWM4.zip
Again, sorry for asking what may be pretty simple questions, but I really appreciate everyone's help!
Hi,
You can follow this (http://knowmydroid.com/guide/root-samsung-galaxy-s-2) step by step guide to root your SGS2.
1) Yes, rooting your phone means you cannot use KIES anymore. Its highly not recommended
2) Download any official firmware from SamFirmware.com and flash via ODIN
3) You can flash the KH3 version of CF-Root as well.
Orangetato said:
First off, I'm completely new to this and wish to root my new sgs2, and I've done some reading on the forum about this but got some questions (or want to confirm what I think I know) before I actually go ahead with the process. I apologize if it's something others have already asked, but I would really hate for anything to happen to what has become my new baby...
I mainly just want root access on my phone as I've come across several apps and what not that required root access.
My phone's status right now:
Android version: 2.3.3
Baseband: I9100XXKG1
Kernel Version: 2.6.35.7-I9100ZSKG2-CL361136 [email protected] #6
Build: GINGERBREAD.ZSKG2
I found (http://forum.xda-developers.com/showthread.php?t=1103399) about CF-Root. It seems like a lot of people recommend this method to root, so I thought I may try it out. Before I do though, I wanted to know:
- Just rooting my phone will not prevent me from receiving any new updates to my phone via Kies, right? (E.g. a new firmware or version comes out in the future...)
- What do I need to do if I wish to unroot in the future?
- For this method, this should be the one I should download and use right? (it's the closest one I found matching my current kernel): CF-Root-SGS2_ZS_OZS_KG2-v4.1-CWM4.zip
Again, sorry for asking what may be pretty simple questions, but I really appreciate everyone's help!
Click to expand...
Click to collapse
Hello,
you will still receive updates via KIES.
Unroot is possible with SuperOneclick. I have not tried so far. Every new firmware overwrites root. So if you root with ODIN and flash the rooted Firmware to the original one, KIES will allow to upgrade.
You could also use ODIA's insecure original kernels and use the ones provided from INTRATECH to have the original back on.
Never tried CF myself.
This phone is practically impossible not to root! Read everything thoroughly and take the dive, see you on the other side
Sent from my GT-I9100 using xda premium
Thanks~
Thanks for all the help! I did take the plunge ... and have no regrets!
I used CF's way, and have flashed back to my original stock kernel afterwards (courtesy of INTRATECH). Everything seems to be happy so far.
And now.. time to have some real fun with the phone
Thanks again everyone!
I also recently rooted with the CF-Root method. Congrats from a fellow HK/Taiwan phone user.
Check out this thread if you are interested in an XXKH3 rom with Chinese input: http://www.mobile01.com/topicdetail.php?f=568&t=2188818&last=30718996 (Note: I have not tried these myself.)
Hello all,
To begin here are the current specs of my At&t Samsung Galaxy S2:
Model Number: SAMSUNG-SGH-I777
Android Version: 2.3.6 (yes, i have done OTA update from 2.3.4)
Baseband Version: I777UCKK6
Kernel version: 2.6.35.7
Build number: GINGERBREAD.UCKK6
So now onto the reason for this post, I have spent several hours...several months uptil now trying to fully understand the rooting process for the At&t Samsung Galaxy S2 and I have a few questions around the entire process that i would like to get some concrete input on.
My objective behind rooting is only to get SuperUser access and be able to remove all of the at&t/samsung apps i dont need or use, and to use apps like titanium backup to backup all my stuff...i dont plan to ever install anything custom on my sgs2 as the stock rom is sufficient enough for what i do on the phone (at the moment).
with that said:
1) is it possible to keep everything stock and just but just enable the SuperUser access, if so, can some1 point me in the direction of what all i need to achieve this?
2) (if #1 is achieved and ) if i just root the phone by keeping everything stock, is there a posibility that my flash counter on sgs2 will get incremented? ( i am aware that there is a method to undo/reset the flash counter back to 0 ("NO"), but i would like to avoid incrementing it to begin with).
thanks for your input!
FI
Hit my return to stock thread - includes a prerooted system image with stock kernel for UCKK6.
Prerooted system images don't trigger the custom binary count.
http://forum.xda-developers.com/showthread.php?t=1286432
Entropy512 said:
Hit my return to stock thread - includes a prerooted system image with stock kernel for UCKK6.
Prerooted system images don't trigger the custom binary count.
Click to expand...
Click to collapse
thanks, i have studied ur post in detail actually, and then for some odd reason, i drifted off onto other threads where i got a bit concerned about the binary flash counter...
Edit: re-visiting your post, i know that it was the thread by creepyncrawly that got me in the concerned stage
Hi, I recently got an international Galaxy S3 - my first Android phone. It's an unlocked Spain model (not tied to any carrier), and I upgraded it from 4.0.4 to 4.1.1 as soon as I took it out of the box. I've been rooted through Chainfire's ExynosAbuse since it was released. I've never used Kies; the only update I've had was done OTA.
I wasn't planning on messing around with ROMs for quite a while, but I considered installing a 4.1.2 ROM after seeing the Premium Suite announcement. I figured I'd wait however long it took for Samsung to release 4.1.2 to Spanish phones... but reading that the XXELLA upgrade fixes the sudden death issue - something which I've been quite worried about - I kind of want to just install it, assuming there's no adverse effects. And if the eMMC bug causes damage to the chip over time, I would like to install the hotfix as quickly as possible... (I do have the affected chip and FW rev)
I have been reading up quite a bit in the GT-I9300 sections here, and I think I've got an okay picture of how stuff goes, but I do want to make sure before I do anything with my expensive phone! There is an overwhelming amount of information and it's hard to keep track of everything. Anyway, here's what I was wondering...
- What's the best and safest way to flash the 4.1.2 ROM? It seems like I can use Odin, Mobile Odin, Heimdall or a recovery... but I assume I would need to flash the latter through one of the other three? I use Linux, so I would prefer to use Heimdall over Odin (if it's not more risky). Is a recovery required for custom ROMs, or is it just for convenience? Is it safer than the other methods?
I should also mention that if I used Mobile Odin, I would have to use the lite version as paid Play apps aren't available where I live and I don't have a credit/debit card anyhow.
- Would doing this get me the same result as installing it through Kies or OTA if it was officially released for Spain? (eg. the properly updated kernel/bootloader/modem/whatever else...) Including the famous eMMC fix...
- Are there any adverse effects to installing a ROM belonging to a different country? I think I'd probably end up going for the UK version.
- Would I keep my installed apps, settings, etc like I did with the 4.1.1 OTA update?
- I may end up installing a custom kernel later on (possibly Perseus or something of the like); is there anything I should take into account for this, like what method I use to flash it? And would I lose my data through doing this?
I hope I haven't asked anything too dumb, lol. Thanks very much!
Treeki said:
- What's the best and safest way to flash the 4.1.2 ROM?
>> follow the instructions for the firmware
? I use Linux, so I would prefer to use Heimdall over Odin
Use hEIMDALL
. Is a recovery required for custom ROMs,
Yes
Is it safer than the other methods?
No
- Are there any adverse effects to installing a ROM belonging to a different country? I think I'd probably end up going for the UK version.
Possible need to flash modem or CSC for your region / network
- I may end up installing a custom kernel later on (possibly Perseus or something of the like); is there anything I should take into account for this, like what method I use to flash it?
Follow the kernels instructions .
BASICS .
http://forum.xda-developers.com/showthread.php?t=1927113
jje
Click to expand...
Click to collapse
[Q&A] Samsung Galaxy Mega 2 SM-G750A AT&T Root. Plus Hotspot unlocked for Cricket or
Q&A for Samsung Galaxy Mega 2 SM-G750A AT&T Root. Plus Hotspot unlocked for Cricket or other
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Samsung Galaxy Mega 2 SM-G750A AT&T Root. Plus Hotspot unlocked for Cricket or other. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Mega 2 as well.
KingRoot did work for me. I am looking for a custom ROM now, but there is like NO support from anywhere for this device. I hope we can get a developer onboard and get something built for these devices.
have a thread on android forums for this as well, you can do a search for Mega 2 and its the only thread on the mega 2 forum, screenname on there is Matt Cajon as well.
Maybe we can make something happen
Custom Recovery?
Any luck with a working custom recovery?
running backup before running the app.
Thank you shockazulu for your post on the mega2 root.
I'm new to this and have been looking and searching for the best way to do it and most have refurred the king root app.I do have a questions .
Do I still need to do a backup of the phone before running the app.?
Is this a preferment root as I noted your phone reverting back to it's original state?
Noticed there is a newer version of the king root app now 4.5 and would it be better to run that app ?
Thanks Again and I'm sure I'll have another question before I get into doing this !
Chris
I manage to root the galaxy mega 2 on the newer baseband G750AUCU3AOFA. Since for some reason you can't root it on that build. but with the modem flash it worked
Matt Cajon said:
KingRoot did work for me. I am looking for a custom ROM now, but there is like NO support from anywhere for this device. I hope we can get a developer onboard and get something built for these devices.
have a thread on android forums for this as well, you can do a search for Mega 2 and its the only thread on the mega 2 forum, screenname on there is Matt Cajon as well.
Maybe we can make something happen
Click to expand...
Click to collapse
The problem with the att version of the mega 2 is that the bootloader is locked. So there is no way to use a custom bootloader like Clockwork. Without a custom bootloader we can't load/flash roms.
But what we can do is........
We can use a program called Flashfire. Flashfire is a way to flash things on our phone without having to use the bootloader.
We can also use exposed launcher and wanam exposed. This is the tools we can use to make customise our stock rom.
One of us could customize a rom and create a step by step for how they created it. If it is a stable setup then instead of others flashing that custom ROM, they would fallow the steps to create the same custom ROM.
whats with the vague answer ...
if you rooted it on OFA how did you do it?!?!
WHAT MODEM?! please elaborate I need to know asap..
Any of you had luck on installing a custom recovery for it? i am trying to help another forum member who have this S750A .
I recently ported a custom TWRP for my device which is a SM-J105B. Found out that TWRP was easier to port/works better on it than CWM for instance. Maybe this is the case for you guys device, i want to help out.
i know this is a 1 year old post but if any were successful please share the knowledge cheers from Brasil!
Pindroid is trying to help me i have a samsung galaxy mega 2 sm-g750a also it said "unlocked" on the ad when i got it but anyways we are looking for the original 4.4.4 kitkat firmware and can't seem to find it anywhere but the one we did find that has repair in its title has never worked as far as flashing with it goes. I have lollipop right now and it works fine but it hasn't solved the problem im having with my IMEI so we are trying a downgrade to see if that helps. Anyways thanks for any help
I have a sm- g750a on 5.1.1 too ,tried kingo root ,kingoroot, with a no go ,roots but then just bootloops then I gotta reflash 5.1.1 firmware via Odin ...I've looked and looked just the run around on how to root this device,I really wanna root this phone love the screen and it's my go to phone for work ,if anyone could figure this out that would be awesome
I get the same thing...Boot looping after root..Firmware is 5.1.1..Anyone have thoughts?Thanks.
Surgeman said:
I get the same thing...Boot looping after root..Firmware is 5.1.1..Anyone have thoughts?Thanks.
Click to expand...
Click to collapse
Thoughts on how to root or how to fix the bootloop?
Piridroid said:
Thoughts on how to root or how to fix the bootloop?
Click to expand...
Click to collapse
The root is no problem..It's the boot loop is the biggest problem.And factory wiping it doesn't fix the issue.
Surgeman said:
The root is no problem..It's the boot loop is the biggest problem.And factory wiping it doesn't fix the issue.
Click to expand...
Click to collapse
As mrodriguezangel said on page 1:
"I have a sm- g750a on 5.1.1 too ,tried kingo root ,kingoroot, with a no go ,roots but then just bootloops THEN I GOTTA REFLASH 5.1.1 FIRMWARE VIA ODIN .."
Did you manage to root Mega 2 5.1.1 without issues? To remove the bootloop you will have to reflash your stock firmware via ODIN software.
According to the official AT&T page (is yours at&t?) :
https://www.att.com/devicehowto/tut..._KB425949?make=Samsung&model=GalaxyMega2G750A
Latest Kitkat is July 7, 2015
Android version: 4.4.4
Baseband version: G750AUCU3AOFA
Kernel Version: 3.4.39-2550495 [email protected]#1
Build number: KTU84P.G750AUCU3AOFA
Latest Lollipop is September 2, 2015
Android version: 5.1.1
Baseband version: G750AUCU3BOH4
Kernel Version: 3.4.39-5559233 [email protected]#1
Build number: LMY47X.G750AUCU3BOH4
Googled "G750AUCU3BOH4" and found http://www.mediafire.com/file/hd72qrsaeoob9tl/G750AUCU3BOH4+5.1.1.rar , try to know more about it, but should work ok.
How did you root?
Piridroid said:
As mrodriguezangel said on page 1:
"I have a sm- g750a on 5.1.1 too ,tried kingo root ,kingoroot, with a no go ,roots but then just bootloops THEN I GOTTA REFLASH 5.1.1 FIRMWARE VIA ODIN .."
Did you manage to root Mega 2 5.1.1 without issues? To remove the bootloop you will have to reflash your stock firmware via ODIN software.
According to the official AT&T page (is yours at&t?) :
https://www.att.com/devicehowto/tut..._KB425949?make=Samsung&model=GalaxyMega2G750A
Latest Kitkat is July 7, 2015
Android version: 4.4.4
Baseband version: G750AUCU3AOFA
Kernel Version: 3.4.39-2550495 [email protected]#1
Build number: KTU84P.G750AUCU3AOFA
Latest Lollipop is September 2, 2015
Android version: 5.1.1
Baseband version: G750AUCU3BOH4
Kernel Version: 3.4.39-5559233 [email protected]#1
Build number: LMY47X.G750AUCU3BOH4
Googled "G750AUCU3BOH4" and found http://www.mediafire.com/file/hd72qrsaeoob9tl/G750AUCU3BOH4+5.1.1.rar , try to know more about it, but should work ok.
How did you root?
Click to expand...
Click to collapse
I have rooted it 2 different ways...Kingo and Super SU..Once rebooted it will boot loop over and over.It has something to do with the Knox itself.I've been working on a way to disable it but it's enterprise and it doesn't have an option under security.And yes it's SG-M750A AT&T Mega 2.
Surgeman said:
I have rooted it 2 different ways...Kingo and Super SU..Once rebooted it will boot loop over and over.It has something to do with the Knox itself.I've been working on a way to disable it but it's enterprise and it doesn't have an option under security.And yes it's SG-M750A AT&T Mega 2.
Click to expand...
Click to collapse
mmm Ok. How did you root with SuperSU ? CF-auto? recovery? supersu-me ?
Is there an option called "Unlock by OEM" under "Developer Options"? Enable it.
Another thing, according to this tutorial for the SG-M750F:
https://androidmtk.com/root-samsung-galaxy-mega-2-sm-g750f
This F version which should be similar is only rootable with a specific firmware. Maybe thats the case for the A version aswell.
Also, next time you have root, before you reboot you should make a backup of your EFS and Modem folders. You can do that via ADB, EFS tools or using some apks for instance.
Check dlo2000 post on first page, he had kitkat installed, rooted with Kingo and let the the phone OTA update to lollipop... somehow his IMEI number got corrupted and now he cannot use his phone to make calls. Thats why backing up your EFS partition is important, your IMEI is there.
So from what i understood, you did know stock firmware flash would remove bootloops, but you currently dont know how to root without creating a bootloop, is that correct? cheers
---------- Post added at 01:48 AM ---------- Previous post was at 01:37 AM ----------
Surgeman said:
I have rooted it 2 different ways...Kingo and Super SU..Once rebooted it will boot loop over and over.It has something to do with the Knox itself.I've been working on a way to disable it but it's enterprise and it doesn't have an option under security.And yes it's SG-M750A AT&T Mega 2.
Click to expand...
Click to collapse
Enterprise... maybe it has extra security turned on, idk.
How do you know it has to do with KNOX, did it show some knox message? Chainfire's supersu sometimes asks to let it disable knox. Which version of supersu did you use?
Piridroid said:
mmm Ok. How did you root with SuperSU ? CF-auto? recovery? supersu-me ?
Is there an option called "Unlock by OEM" under "Developer Options"? Enable it.
Another thing, according to this tutorial for the SG-M750F:
https://androidmtk.com/root-samsung-galaxy-mega-2-sm-g750f
This F version which should be similar is only rootable with a specific firmware. Maybe thats the case for the A version aswell.
Also, next time you have root, before you reboot you should make a backup of your EFS and Modem folders. You can do that via ADB, EFS tools or using some apks for instance.
Check dlo2000 post on first page, he had kitkat installed, rooted with Kingo and let the the phone OTA update to lollipop... somehow his IMEI number got corrupted and now he cannot use his phone to make calls. Thats why backing up your EFS partition is important, your IMEI is there.
So from what i understood, you did know stock firmware flash would remove bootloops, but you currently dont know how to root without creating a bootloop, is that correct? cheers
---------- Post added at 01:48 AM ---------- Previous post was at 01:37 AM ----------
Enterprise... maybe it has extra security turned on, idk.
How do you know it has to do with KNOX, did it show some knox message? Chainfire's supersu sometimes asks to let it disable knox. Which version of supersu did you use?
Click to expand...
Click to collapse
I used Kingo the first time,and even used Super SU me to remove Kingo...AT&T devices doesn't require any unlock for cricket because AT&T owns them lock stock and barrel.You're getting the same service just bottle necked on the 4G end of it at 8 mbs and it's unlimited.I have been reading through other post in some other forums,and the SE for Android pops up about security settings and ask to reboot to restore them.Once you do..the boot loop begins.I have searched the error out also...and it pertains to knox.I have even tried to remove knox before rebooting..No go..still boot loops...Myself and another user have the same issue,and we've been trying to figure a work around and nothing yet.Some other information I have read that with the Lollipop update it adds the enterprise knox that may cause issues.But it doesn't hurt to try...Oh I forgot to mention...I made a efs backup before I started the journey but good looking out..Thanks..
Surgeman said:
I used Kingo the first time,and even used Super SU me to remove Kingo...AT&T devices doesn't require any unlock for cricket because AT&T owns them lock stock and barrel.You're getting the same service just bottle necked on the 4G end of it at 8 mbs and it's unlimited.I have been reading through other post in some other forums,and the SE for Android pops up about security settings and ask to reboot to restore them.Once you do..the boot loop begins.I have searched the error out also...and it pertains to knox.I have even tried to remove knox before rebooting..No go..still boot loops...Myself and another user have the same issue,and we've been trying to figure a work around and nothing yet.Some other information I have read that with the Lollipop update it adds the enterprise knox that may cause issues.But it doesn't hurt to try...Oh I forgot to mention...I made a efs backup before I started the journey but good looking out..Thanks..
Click to expand...
Click to collapse
OK, so it was supersu-me and the issue has to do with SElinux right.
dude i own a Galaxy J1 mini and i was the "first person" to root the B/F/M/Y versions (custom recovery method, based on an obscure version created for the H version) , this device is also a 5.1.1 android, SElinux activated from factory. The website which provided the root for the H version vanished a couple of weeks after they annouced it... lucky to find it, i just had to read easy tutorials here in XDA to learn how to properly port the TWRP for my specific model B and later on for the other J1 mini variants on ppl demand.
What i find out from my experience is, if i was going to wait for some expert to find how to root it, i would still be waiting... keep trying!
I would personally as a noob, try to find out how to disable KNOX or SElinux . There are probably commands which can be run as root user to disable them, for instance "selinux set permissive" (i know it exists, something like that, maybe). There are apps which claim to do those stuff, just search playstore for "knox" or "selinux" and you will see. In case none does the job automatically, search how to do it manually.
In my case, the TWRP+SuperSU method worked just fine, looks definitive. BUT, before i found this, the only other real option was a chinese app called 360root. None other root app works on my device so far. But its root was unstable and not compatible with all apps, thats why i searched for a permanent root.
THis 360root only worked on the older firmware (also 5.1.1, but older samsung release).
My opinion is... in case you dont mind using kitkat (android 4.4) i would flash the oldest firmware and try to root it with Kingo (which owners of variants of the MEGA 2 claim is the only tool capable, it even turns knox off in some cases). Remembering that if this worked, you would have to disable automatic firmware updates. Letting a rooted device to auto-update usually creates more trouble.
If kitkat is a no go for ya and you want to stick with lollipop, i would first try to disable the protections via apps (root ; dont reset, install app, try). Same applies to manually trying "disabling commands" via Terminal or ADB, root, try.
If that still does not work ... i would try to download a stock lolipop firmware and extract its files. I would then try to create a custom recovery (read tutorials) and also check if there were any options i could manually reprogram inside boot.img , recovery.img, system.img etc... (more tutorials lol)
Again man, im no expert, but thats what i would do! i actually downloaded that lollipop stock firmware for your device and will try to look inside it when i have time.
Piridroid said:
OK, so it was supersu-me and the issue has to do with SElinux right.
dude i own a Galaxy J1 mini and i was the "first person" to root the B/F/M/Y versions (custom recovery method, based on an obscure version created for the H version) , this device is also a 5.1.1 android, SElinux activated from factory. The website which provided the root for the H version vanished a couple of weeks after they annouced it... lucky to find it, i just had to read easy tutorials here in XDA to learn how to properly port the TWRP for my specific model B and later on for the other J1 mini variants on ppl demand.
What i find out from my experience is, if i was going to wait for some expert to find how to root it, i would still be waiting... keep trying!
I would personally as a noob, try to find out how to disable KNOX or SElinux . There are probably commands which can be run as root user to disable them, for instance "selinux set permissive" (i know it exists, something like that, maybe). There are apps which claim to do those stuff, just search playstore for "knox" or "selinux" and you will see. In case none does the job automatically, search how to do it manually.
In my case, the TWRP+SuperSU method worked just fine, looks definitive. BUT, before i found this, the only other real option was a chinese app called 360root. None other root app works on my device so far. But its root was unstable and not compatible with all apps, thats why i searched for a permanent root.
THis 360root only worked on the older firmware (also 5.1.1, but older samsung release).
My opinion is... in case you dont mind using kitkat (android 4.4) i would flash the oldest firmware and try to root it with Kingo (which owners of variants of the MEGA 2 claim is the only tool capable, it even turns knox off in some cases). Remembering that if this worked, you would have to disable automatic firmware updates. Letting a rooted device to auto-update usually creates more trouble.
If kitkat is a no go for ya and you want to stick with lollipop, i would first try to disable the protections via apps (root ; dont reset, install app, try). Same applies to manually trying "disabling commands" via Terminal or ADB, root, try.
If that still does not work ... i would try to download a stock lolipop firmware and extract its files. I would then try to create a custom recovery (read tutorials) and also check if there were any options i could manually reprogram inside boot.img , recovery.img, system.img etc... (more tutorials lol)
Again man, im no expert, but thats what i would do! i actually downloaded that lollipop stock firmware for your device and will try to look inside it when i have time.
Click to expand...
Click to collapse
Ok let me know what you find with the firmware when you get the chance.I have used 360root also in the past myself on devices when nothing else would work.I have tried several times and different ways.Disabled Knox via terminal with temp. root and still no go.It's the SELinux enforcing is the biggest problem.Kingo will install as a system app..but you won't have full root unless you run the apk to root the device again and it reboots on it's own after about 5 minutes or so.I'll keep stabbing at it..and post my findings.I assume I'm not the only one that could use this.Thanks for your time Piridroid.
Anything new on this?