Related
Hey guys.
Just got my new Galaxy S7 - G930F
Baseband version: G930FXXU1APEQ
Build version: MMB29K.G930FXXU1APF2
Android version: 6.0.1
I'm trying to find the proper way to root & install custom recovery (TWRP) & install xposed framework.
First things first - Rooting.
I've found tons of guides, some use ChainFire auto-root, some use KingRoot, etc. not sure which is the best way?
Plus, in most of the guides there is a step described as:
" Now take Nandroid Backup and do a Factory Reset "
Right after installing "dm-verity and force encryption disable" zip file, just before flashing SuperSU
I can't seem to understand why is this step needed. do i have to lose all my data & settings upon rooting?
Second - Xposed installation. upon reading some posts, it seems that latest xposed framework causes bootloops in samsung devices? is this correct?
Isn't there a version which doesn't causes that?
If someone could post a recommended guide for rooting, would be much appreciated.
Also, if there's a way of rooting without tripping knox, so in the future i could unroot in order to use my warranty, this is even better.
Sorry if this was discussed here before, i really got lost in all the information available online, as there are so many of it - i got lost
Thanks
Greetings and I hope you enjoy your new device. If you search the forum you will find the answers to most of your questions. I will leave this thread open for now but please don't post the same questions in different threads it just clutters up the boards
http://forum.xda-developers.com/gal...b-friendly-t3341138/post68136230#post68136230
Regards
Moderation Team
I have a G930FD, and I rooted with CF-Auto-Root, installed flashfire from the app store, then installed Xposed framework with flashfire. I did this immediately after wiping to factory, since I couldn't get Xposed to install 3 to 4 times when I tried doing it after installing my apps. You need the Xposed version created by wanam, http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
I suggest not installing TWRP. There's a warning in the TWRP installation thread that an errant update could cause a half-flash state in the S7 which is non-recoverable.
There's no rooting method available now that does not trip Knox, so your warranty will be void if you root.
gregwee said:
I have a G930FD, and I rooted with CF-Auto-Root, installed flashfire from the app store, then installed Xposed framework with flashfire...
Click to expand...
Click to collapse
@gregwee
After you root and installed Xposed can you please tell is there any problem with private mode ?
I read somewhere on this forum that after Xposed, private mode not working.
Thanks
tomesiek said:
@gregwee
After you root and installed Xposed can you please tell is there any problem with private mode ?
I read somewhere on this forum that after Xposed, private mode not working.
Thanks
Click to expand...
Click to collapse
Private mode cannot be enabled on my phone.. In any case, it's not any great loss since the data is actually still there, just that it's "hidden" by Touchwiz.. You're better off using a real encrypted container if it's something that you really want to keep private..
gregwee said:
Private mode cannot be enabled on my phone..
Click to expand...
Click to collapse
Can you please try __THIS__
I know that I'm asking a lot, but I like when everything is working even if is not "real" private mode.
PS. What is a image you using now? I read that on newest firmware root my not works and I'm afraid that my phone "caught" new ROM
My phone is on MMB29K.G930FXXS1APGC.
Thanks.
tomesiek said:
Can you please try __THIS__
I know that I'm asking a lot, but I like when everything is working even if is not "real" private mode.
PS. What is a image you using now? I read that on newest firmware root my not works and I'm afraid that my phone "caught" new ROM
My phone is on MMB29K.G930FXXS1APGC.
Thanks.
Click to expand...
Click to collapse
The wanam xposed I have does not have the option for "Security hacks > Disable secure storage". The directories listed in the article are either not there, or are already empty.
I'm on Marshmallow, 6.0.1, build G930FXXU1APGJ, which should be the latest firmware. My S7 is the Hong Kong (TGY) version.
My Pixel will arrive in a few days, I'm excited. I want root for things like custom firewall, ad blocking, filesystem access - but I need to be able to use Android Pay for work. I've been doing some research on how to make Android Pay work with root and have a couple questions. I'd really appreciate if anyone could help answer these.
First, let me summarize my understanding. Root requires an unlocked bootloader. Android Pay uses SafetyNet to check for both root and an unlocked bootloader. These two things must both be addressed.
To get around the unlocked bootloader check, flash a kernal that's patched to circumvent the SafetyNet check.
In terms of rooting, the most recent and seemingly best method for doing so looks to be ChainFire's SuperSU v2.78 SR4.
Magisk can generally be used to easily get around the *root check*, but probably doesn't work on the Pixel yet.The Magisk developer says it's a work in progress as of Nov. 14, 2016. Technobuzz posted a guide on installing Magisk for the Pixel but in another thread people didn't seem to have much luck with it.
Question 1) Is it correct that Magisk's primary benefit in this case is to allow root to be either restricted from certain apps or to be toggled system-wide without a restart? In other words, I can still disable root directly through the SuperSU program, but without Magisk that then requires a restart.
Question 2) Does the Android Pay SafetyNet check only prevent the addition of cards into Android Pay, or does it also prevent the usage of Android Pay after a card has been added. I ask because I wouldn't mind restarting to disable root when I want to add a card, but I don't want to restart every time I want to simply use Android Pay (and have already added a card).
Question 3) ChainFire notes that suhide does not work on Pixels, nor does it work on Android 7.1 at all. I haven't been able to figure out exactly what suhide does and whether it matters to me. Do I care?
Question 4) In the slightly previous version of ChainFire's rooting (SuperSU v2.78 SR2) he calls out that the kernel must be patched. Sounds like since this doesn't require a kernel recompile that it shouldn't interfere with the custom kernel + SafeNet patch necessary to circumvent the unlocked bootloader check. Right?
Many thanks in advance for taking the time to read and respond.
You got the bootloader part right. None of anything else you listed applies to this phone.
Magisk doesnt work on this phone. The versions of SU you mention are the wrong versions for this phone. You need 2.79 SR3. Anything below that and you will bootloop.
There is a thread around here were some folks fot SUHide working for awhile, bit an update or two ago broke that.
I do not believe there is currently any way to get pay to work with root. Google seems to be pretty serious about Pay not working on modded phones.l
---------- Post added at 12:40 AM ---------- Previous post was at 12:39 AM ----------
And to answer question 2, it prevents it from working at all.
TonikJDK said:
You got the bootloader part right. None of anything else you listed applies to this phone.
Magisk doesnt work on this phone. The versions of SU you mention are the wrong versions for this phone. You need 2.79 SR3. Anything below that and you will bootloop.
There is a thread around here were some folks fot SUHide working for awhile, bit an update or two ago broke that.
I do not believe there is currently any way to get pay to work with root. Google seems to be pretty serious about Pay not working on modded phones.l
---------- Post added at 12:40 AM ---------- Previous post was at 12:39 AM ----------
And to answer question 2, it prevents it from working at all.
Click to expand...
Click to collapse
Thanks for responding. I see your point about SuperSU SR3. SR5 looks like it may work also. I admit that it's still unclear to me what suhide does. Are you saying that without suhide I won't be able to simply check the box within the SuperSU program to disable root and get around the root check (assuming I have patched bootloader also)?
fluidfocus said:
Thanks for responding. I see your point about SuperSU SR3. SR5 looks like it may work also. I admit that it's still unclear to me what suhide does. Are you saying that without suhide I won't be able to simply check the box within the SuperSU program to disable root and get around the root check (assuming I have patched bootloader also)?
Click to expand...
Click to collapse
Suhide was a project Chainfire did to hide root for Pay. It was a separate install that modded it to hide it. Currently not working on this phone.
2.78 SR5 will not work.
There is no disable root checkbox that i can find on mine. Perhaps something that was in previous versions.
I very recently purchased (as in less than a week ago) a Google Pixel (5") from the Google Play store. I would like to root it, but have a few questions that I could only seem to find vague answers to online. Firstly, does the Google Play purchased version of this phone come automatically with an unlocked bootloader? I saw several posts online that this was the case, but the posts are all pretty old (10/2016, about 9 months ago) and nothing really since then. Is there a way to verify/check if the bootloader is unlocked?
Secondly, the phone I got has Android 7.1.2 (build NKG47L). These - posts look to be the most recent info on rooting this phone, but they mention a different build number. Does anyone know if this is still an accurate process?
Unlock bootloader in developer options by toggling, then use OEM unlock in fastboot, Install TWRP, and flash latest superSU in TWRP. Done.......
Sent from my Pixel using Tapatalk
Are you the same alienjon as on FB, with the Light Whip?
Bootloader is probably locked - it was on mine when new from Google Play - Aus and about 6 months ago, but locked bootloader is part of Google policy so it probably still is. Unlock like this:
https://android.gadgethacks.com/how-to/unlock-bootloader-your-google-pixel-pixel-xl-0174627/
be aware that unlocking the bootloader will wipe your phone (would keep your data secure it someone had stolen it and was unlocking it to hack it), so do that early.
I root as per Chainfire's instructions, there's no easy way to update and keep root at the moment (Flashfire is supposed to work but it doesns't for me) so I reroot after each update, worked for the June update.
There are a few things to be aware of; TWRP is up to 302rc2 but some people have had trouble with that, I still use twrp 302 rc1 which works reliably (just boot it, to flash SU then reboot I haven't installed it). SU is currently 2.82 and as of the May update Pixel needs the boot image signed, which borked SU. Chainfire released a fix, a .zip which you need to flash after the SU zip as per this thread:
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
(apparently you can do without it for the June version of Pixel update, haven't checked that myself). Future versions of SU will include signing as part of the main install. I fine it useful to keep an eye on Chainfire's Google+ account which has links to the latest versions and any other significant changes:
https://plus.google.com/+Chainfire
Finally, did you mean to post your question twice? I think you can probably delete the second instance if you want to, save having replies scattered around.
@maulich That's perfect. Took me about an hour and a half to root, but most of that was reading and re-reading instructions to make sure I didn't mess anything up. I did notice that there is now some device protection feature that gets disabled when you unlock the bootloader. I checked online and it seems that this basically is a feature that factory resets the device in case someone tried to force themselves into a stolen device. I'll look around, but any suggestions for security features to implement for a rooted device?
@Clancy_s Sorry to disappoint, but no relation to an alienjon on FB. You are correct that it was locked, but I really love how easy it is to unlock. I'm used to phones purchased from Verizon that are beastly to unlock. My last phone (Galaxy S5) never got a workaround for the bootloader from what I recall (though after the Towel Root process stopped working it was almost a year and a half before a new rooting procedure was discovered - kudos to the devs that figured that problem out!)
In any event, thanks for the input on unlocking and rooting. I looked at a few different websites, but the procedure appears to be the same for unlocking that you found. This is the rooting procedure I used and worked fine, though the directions weren't as straightforward as you'd think; ie: the latest TWRP has a .zip but no .img to download on their website and I didn't trust anything else I found online that claimed to be the correct .img file. I used the next most recent version (RC1 - I saw several warnings against the alpha builds) and didn't have any problems. I also used the latest SuperSU (2.82, I believe). A few posts mentioned sticking with 2.79 because of bugs with the newer version, but those were from several months ago and elsewhere it stated that this issue was fixed. It seems to be working great for me
Clancy_s said:
SU is currently 2.82 and as of the May update Pixel needs the boot image signed, which borked SU. Chainfire released a fix, a .zip which you need to flash after the SU zip as per this thread:
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
(apparently you can do without it for the June version of Pixel update, haven't checked that myself). Future versions of SU will include signing as part of the main install. I fine it useful to keep an eye on Chainfire's Google+ account which has links to the latest versions and any other significant changes:
Click to expand...
Click to collapse
Unfortunately I didn't see your post until after I rooted. I can verify, though, that flashing the SuperSU zip worked fine without any additional steps. (ie: boot into TWRP image, flash TWRP and SuperSU zips, which I did together).
Clancy_s said:
Finally, did you mean to post your question twice? I think you can probably delete the second instance if you want to, save having replies scattered around.
Click to expand...
Click to collapse
I did not. When I tried to submit my initial post I got a server error. It didn't look like anything had gone through so I went back and resubmitted, which worked. I later realized that the first post did, in fact, go through but I couldn't figure out how to delete it. My apologies for the dupe.
alienjon said:
I couldn't figure out how to delete it. My apologies for the dupe.
Click to expand...
Click to collapse
In a web browser either on the PC or on the phone, click the exclamation point in the triangle /!\ in the lower left corner of the post you want to report, report it to a moderator and ask them to please delete it, or move it, if you ever post something in the wrong section.
Thanks. I'll remember that in case it comes up again.
OK, so, heres the situation, I got the new J3 Emerge (J327P) from Boost Mobile in effort to cut down cell costs and such. Its a decent phone but I am looking to root it. So I started looking up how to root it and such and came up with a pretty simple guide from google results. It is basically flash TWRP with ODIN then flash SuperSU from TWRP. Simple enough.
Now on my old phone I also had Xposed and loved it so I check and apparently you have to flash that in TWRP as well THEN install the APK? This is kinda where I start getting confused on things too. After looking through some other random pages online pertaining to rooting and xposed for this phone, some pages mentioned "system-less" root and xposed. Another page mentioned Magisk as well.
My question I guess really is which files are gonna give me the best end result of having (obviously) custom recovery, full root (with ability to, if needed disable at will), Xposed fully working (again, with the ability, if needed, to disable at will)?
Some links Ive come across but not read fully cause theyre simply too long.....
TWRP for J3 Emerge (J327P)
https://forum.xda-developers.com/ga...overy-twrp-3-1-0-1-samsung-galaxy-j3-t3573607
Xposed for MM by rovo89 - (Apparently doesnt work on Samsung phones though????)
https://forum.xda-developers.com/xposed/discussion-xposed-marshmallow-t3249095/
UNofficial Xposed for Samsung phones by wanam
https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960/
Magisk for "system-less" Root for Android 5+
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
UNofficial "system-less" Xposed by Magisk dev
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
The first rooting guide I found through google:
https://www.androidgunner.com/twrp-root-samsung-galaxy-j3-emerge/
My sister plays Pokemon Go and so I was looking up how to run it on a rooted phone for her and saw this:
https://devs-lab.com/pokemon-go-hacks-without-moving-anywhere.html
She has same exact phone as me.
In closing, I am familiar with how to use ODIN and the basics of TWRP. I just want to know which files are gonna give me the best end result for what I want.
John877 said:
In closing, I am familiar with how to use ODIN and the basics of TWRP. I just want to know which files are gonna give me the best end result for what I want.
Click to expand...
Click to collapse
The best combinaison is :
- TWRP.
- Magisk v14 (it gives you a lot of possibilities including hiding root and pass safetynet).
- In Magisk Manager you can install Xposed module within it. (but it will trip your safetynet).
That's it
So if I got this straight I flash or install the following in this order?
twrp-3.1.0-1-j327p-14317
Magisk-v14.0(1400) (Which I see includes Magisk Manager 5.3.0?) (from inside TWRP)
Reboot
Open Magisk Manager and install Xposed from there? Or can I flash inside TWRP the wanam Xposed? Is that even needed?
John877 said:
OK, so, heres the situation, I got the new J3 Emerge (J327P) from Boost Mobile in effort to cut down cell costs and such. Its a decent phone but I am looking to root it. So I started looking up how to root it and such and came up with a pretty simple guide from google results. It is basically flash TWRP with ODIN then flash SuperSU from TWRP. Simple enough.
Now on my old phone I also had Xposed and loved it so I check and apparently you have to flash that in TWRP as well THEN install the APK? This is kinda where I start getting confused on things too. After looking through some other random pages online pertaining to rooting and xposed for this phone, some pages mentioned "system-less" root and xposed. Another page mentioned Magisk as well.
My question I guess really is which files are gonna give me the best end result of having (obviously) custom recovery, full root (with ability to, if needed disable at will), Xposed fully working (again, with the ability, if needed, to disable at will)?
Some links Ive come across but not read fully cause theyre simply too long.....
TWRP for J3 Emerge (J327P)
https://forum.xda-developers.com/ga...overy-twrp-3-1-0-1-samsung-galaxy-j3-t3573607
Xposed for MM by rovo89 - (Apparently doesnt work on Samsung phones though????)
https://forum.xda-developers.com/xposed/discussion-xposed-marshmallow-t3249095/
UNofficial Xposed for Samsung phones by wanam
https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960/
Magisk for "system-less" Root for Android 5+
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
UNofficial "system-less" Xposed by Magisk dev
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
The first rooting guide I found through google:
https://www.androidgunner.com/twrp-root-samsung-galaxy-j3-emerge/
My sister plays Pokemon Go and so I was looking up how to run it on a rooted phone for her and saw this:
https://devs-lab.com/pokemon-go-hacks-without-moving-anywhere.html
She has same exact phone as me.
In closing, I am familiar with how to use ODIN and the basics of TWRP. I just want to know which files are gonna give me the best end result for what I want.
Click to expand...
Click to collapse
the latest magisk can patch your boot.img. it will flash in odin with no problems. this is the alternative to using twrp. i do not own a j3 emerge but I own a J3 prime with device model SM-J327t1 which has a locked bootloader and is unrootable currently. hope this helped.
Hello, everybody there!
I managed to unlock bootloader and root my Nokia 3. Actually my OS is Nougat 7.0. I hope some expert may answer these questions I have. If I failed to post such a thread here, please take my excuses by now and move the message where it should have been posted instead.
1. Should I decide to flash the OREO rom for my device, then, will I be able to root it just by flashing the SuperSU zip, the same way I did fot Nougat (with TWRP recovery of course)?
2. Possibile that you cannot find any custom rom for this device?
3. According to your experiences, a device like this, is better to be keept on Nougat, or does it run better on Oreo?
4. About Substratum theme engine. I have installed it and installed practically all of the themes around. To be honest, my goal was to apply the simplest theme of all, the Default Dark Theme. I just wanted to have a dark theme and choose an accent that was different from that cyan/teal you have by default. NOTHING. I got always errors, especially when I tried to apply system / UI parts. Now... is an issue related to the specific device I am using? As you know, Nokia roms are almost pure stock roms, so why cannot I apply themes that claims to be compatible with aosp roms? Should I remove SuperSU and install Magisk, things could work as expected or this is not something related to the point?
5. About Magisk. I would like to test it. I read the thread that talks about this. You provide there the boot.img of Nougat 7.1 and Oreo 8.0. Can anyone provide (or tell me how can I obtain it) the boot.img of a Nokia 3 with Nougat 7.0? Also, I read something about Magisk and modules. I see there is not so much modules to download... and among these, it appears the xposed one... Can you tell me what modules for Magisk justify to move from xposed to Magisk?
Many thanks in advance for your attention, mates!
Regards
Cosimo
jimgordon said:
Hello, everybody there!
I managed to unlock bootloader and root my Nokia 3. Actually my OS is Nougat 7.0. I hope some expert may answer these questions I have. If I failed to post such a thread here, please take my excuses by now and move the message where it should have been posted instead.
1. Should I decide to flash the OREO rom for my device, then, will I be able to root it just by flashing the SuperSU zip, the same way I did fot Nougat (with TWRP recovery of course)?
2. Possibile that you cannot find any custom rom for this device?
3. According to your experiences, a device like this, is better to be keept on Nougat, or does it run better on Oreo?
4. About Substratum theme engine. I have installed it and installed practically all of the themes around. To be honest, my goal was to apply the simplest theme of all, the Default Dark Theme. I just wanted to have a dark theme and choose an accent that was different from that cyan/teal you have by default. NOTHING. I got always errors, especially when I tried to apply system / UI parts. Now... is an issue related to the specific device I am using? As you know, Nokia roms are almost pure stock roms, so why cannot I apply themes that claims to be compatible with aosp roms? Should I remove SuperSU and install Magisk, things could work as expected or this is not something related to the point?
5. About Magisk. I would like to test it. I read the thread that talks about this. You provide there the boot.img of Nougat 7.1 and Oreo 8.0. Can anyone provide (or tell me how can I obtain it) the boot.img of a Nokia 3 with Nougat 7.0? Also, I read something about Magisk and modules. I see there is not so much modules to download... and among these, it appears the xposed one... Can you tell me what modules for Magisk justify to move from xposed to Magisk?
Many thanks in advance for your attention, mates!
Regards
Cosimo
Click to expand...
Click to collapse
1. There is a root/twrp thread on XDA for the Nokia 3 covering nougat and Oreo.
All your questions and concerns with a full tutorial (android 7.0 / 7.1.1 + android 8.0) is answered there.
2. There are NO custom ROMs as yet for Nokia 3, but Nokia have released the source and kernel codes for the Nokia 3.
This means development can now start - read the Nokia 3 development thread here on XDA for further information.
3. My Nokia 3 is way better on Oreo than it was on nougat (faster with much better battery life)
4. I've never had much success with substratum on any stock android device, but it does work very well on devices with lineage OS and similar custom ROMs.
Substratum doesn't like stock ROMs for some reason, even pure android ones like our Nokia, but it's excellent on custom ROMs.
5. Magisk is better than SU - there really is no argument there and most people will agree with that or tell you that.
FYI
All the information you asked is readily available in the Nokia 3 threads here on XDA.
Whilst I appreciate you want some feedback, in my own experience following others advice blindly can lead to issues that end in tears........I'll never ask other users for their suggestions or help here simply because the difference in answers is unbelievable and some people make out they know everything and in reality they know nothing at all.
Please don't let anyone talk you into doing something you are not comfortable or confident in doing - I learned that lesson the hard way, with having to buy an expensive device replacement for tampering with a device when I did not know what I was doing whilst others claimed they did and tried to talk me through every proceedure, only to then completely disappear off the face of the earth when I ran into problems.
Never again!
Regards.