Database Users

My 6P is still on 6.0.0 (Oct. build) because instructions not clear. Question about i

It's about time I finally do this. I have 1 question though.
I'm currently on SU2.52, 6.0.0 and I'm updating to SU 2.66 6.0.1. Chainfire mentions that with the newer systemless root we can install it as traditional root instead. I'm just not clear on how and what to do with what he says below...
His full instructions are:
"Notes on 2.62+
A poor man's overlay is used on /system/xbin. We are creating a copy of /system/xbin in /su/xbin_bind, adding a symlink to /su/bin/su there, then mounting the entire thing on top of the original /system/xbin. This is likely to fix some compatibility issues with some apps, without actually modifying /system. Removing /su/xbin_bind and rebooting will disable this feature, or "echo BINDSYSTEMXBIN=false>>/data/.supersu" in recovery root shell before a SuperSU ZIP flash.
If you have one of those devices that refuse to remount system r/w in Android such as the Nexus 6P, but you do want to do this, "echo FSTABSYSTEMRW=true>>/data/.supersu" in recovery root shell before a SuperSU ZIP flash will patch the boot image in such a way that remounting will work. This feature itself breaks OTA compatibility, regardless of if you end up writing to /system or not.
Both of these features are likely temporary.
Notes on 2.64+
There have been a lot of changes to the ZIP installer. Hopefully they won't break a lot of installs. If 2.64 works well, it is likely to be promoted to the "main beta" in place of 2.52, and the How-To SU document will be updated with the relevant information.
A major change in setup is that the ZIP installer will try to detect 6.0 firmwares that can be rooted without doing a systemless install. In other words, a root that modifies only /system, but not the boot image. If this is possible, the installer will install into /system (unless you override via "echo SYSTEMLESS=true>>/data/.supersu").
This may catch (a) firmwares that allow sepolicy reloading from /data but have a locked bootloader and (b) custom firmwares setup to handle this. Regarding the latter, while it is not as clean as systemless, those running custom firmwares are more likely to want to modify /system anyway, it is less likely to mess with updates to those firmwares, and it prevents the necessity of reflashing the ZIP after each kernel switch. Of course, the kernel's SELinux policies must support this! See this thread for details for devs.
Click to expand...
Click to collapse
1.) Can someone rephrase what he said and make it sound a little simpler?
2.) Do I do both of these or one? (I'm flashing 2.66).
echo FSTABSYSTEMRW=true>>/data/.supersu or echo BINDSYSTEMXBIN=false>>/data/.supersu do both or 1?
3.) Should I override this with 6P? "The (2.64+) zip installer will try to detect a root that modifies only /system, but not the boot image. If this is possible, the installer will install into /system (unless you override via "echo SYSTEMLESS=true>>/data/.supersu")."
I have a ton of apps that rely on root so I want to go with the best method that will give me the least compatibility problems. I don't care for android Pay.

Bump please

are you basically saying you want traditional root using 2.66?
Sent from my Nexus 6P using Tapatalk
---------- Post added at 06:02 PM ---------- Previous post was at 06:01 PM ----------
toknitup420 said:
are you basically saying you want traditional root using 2.66?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
If you want traditional root flash a modified boot.img that will allow traditional root to work. Then flash SuperSU 2.66 and it will automatically install as traditional root.
Sent from my Nexus 6P using Tapatalk

toknitup420 said:
are you basically saying you want traditional root using 2.66?
Sent from my Nexus 6P using Tapatalk
---------- Post added at 06:02 PM ---------- Previous post was at 06:01 PM ----------
If you want traditional root flash a modified boot.img that will allow traditional root to work. Then flash SuperSU 2.66 and it will automatically install as traditional root.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Basically I'm trying to decipher what he is saying in his notes I've quoted. There are 3 things he mentions that I could do if I wanted to and I'm asking what those 3 things are (question 2&3 in my op).
I shouldn't need a modified boot for 2.66 and would prefer not to.

JustRootDontCustomRomIt said:
Basically I'm trying to decipher what he is saying in his notes I've quoted. There are 3 things he mentions that I could do if I wanted to and I'm asking what those 3 things are (question 2&3 in my op).
I shouldn't need a modified boot for 2.66 and would prefer not to.
Click to expand...
Click to collapse
You don't need one if you're using systemless root. If you want traditional root then you need modified boot.img or custom kernel.
Sent from my Nexus 6P using Tapatalk

toknitup420 said:
You don't need one if you're using systemless root. If you want traditional root then you need modified boot.img or custom kernel.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I'm not sure if that's right. I think systemless can be installed into system permanently without boot. The systemless versions patch the boot automatically...

JustRootDontCustomRomIt said:
I'm not sure if that's right. I think systemless can be installed into system permanently without boot. The systemless versions patch the boot automatically...
Click to expand...
Click to collapse
See the part where he mentions the kernel(boot) se policy, this is what you have to modify for root. So yes. It does require a modified boot to install to system. Which is exactly what is explained in the last 2 paragraphs of that quote. However you can override that and force a systemless install if you desire. See the echo command at the end of the 2nd to last paragraph in quote.
JustRootDontCustomRomIt said:
I'm not sure if that's right. I think systemless can be installed into system permanently without boot. The systemless versions patch the boot automatically...
Click to expand...
Click to collapse
Sent from my Nexus 6P using Tapatalk

toknitup420 said:
See the part where he mentions the kernel(boot) se policy, this is what you have to modify for root. So yes. It does require a modified boot to install to system. Which is exactly what is explained in the last 2 paragraphs of that quote. However you can override that and force a systemless install if you desire. See the echo command at the end of the 2nd to last paragraph in quote.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Not saying you're wrong here because I actually don't know but it isn't what I've been reading throughout the forum. Hoping to get a second opinion on this.

JustRootDontCustomRomIt said:
I'm not sure if that's right. I think systemless can be installed into system permanently without boot. The systemless versions patch the boot automatically...
Click to expand...
Click to collapse
You definitely need a modified boot.img for none systemless root that includes a few system checks removed and a sepolicy. I do this myself on every factry imgs because I will never use systemless root is stupid and pointless...So he was dead right for root on 2.66 you need modified boot.img

Tigerstown said:
You definitely need a modified boot.img for none systemless root that includes a few system checks removed and a sepolicy. I do this myself on every factry imgs because I will never use systemless root is stupid and pointless...So he was dead right for root on 2.66 you need modified boot.img
Click to expand...
Click to collapse
Ok. That's a bummer I guess.
Still confusing though because it's the first I hear about this. I could of swore I read that chainfire said the systemless versions will automatically patch boot.. I think I probably misread.
I'm going to sleep right now but could you help me get started? Anything to get me on the right start is appreciated. I know I'll need a modified boot img that works for 6.0.1. you're on 6p right? Because systemless sounds pretty good for me atm. Sounds simpler. It supposedly the same thing as traditional except a very few apps that I hear have compatibility issues. Nothing that can't be fixed with a symlink I believe.
I'm still weighing everything in.

JustRootDontCustomRomIt said:
Ok. That's a bummer I guess.
Still confusing though because it's the first I hear about this. I could of swore I read that chainfire said the systemless versions will automatically patch boot.. I think I probably misread.
I'm going to sleep right now but could you help me get started? Anything to get me on the right start is appreciated. I know I'll need a modified boot img that works for 6.0.1. you're on 6p right? Because systemless sounds pretty good for me atm. Sounds simpler. It supposedly the same thing as traditional except a very few apps that I hear have compatibility issues. Nothing that can't be fixed with a symlink I believe.
I'm still weighing everything in.
Click to expand...
Click to collapse
if you like I can share my modified boot.img I did myself and yes I can help you just PM me. It will only take a few mins. You have working fastboot setup already? It's not the same I don't have time to explain right now tho. If you want help PM me when your ready

Tigerstown said:
if you like I can share my modified boot.img I did myself and yes I can help you just PM me. It will only take a few mins. You have working fastboot setup already? It's not the same I don't have time to explain right now tho. If you want help PM me when your ready
Click to expand...
Click to collapse
Pm you. I have fastboot ready.

JustRootDontCustomRomIt said:
Pm you. I have fastboot ready.
Click to expand...
Click to collapse
I didn't get a Pm. But I'm eating right this minute first you need to flash factory imgs for 6.0.1 via fastboot. Have you don't that before?

Supersu abort on 7.1.1

Has anyone had any issues trying to flash the latest supersu beta on 7.1.1? I get an abort message whenever I flash

Guitarboarder28 said:
Has anyone had any issues trying to flash the latest supersu beta on 7.1.1? I get an abort message whenever I flash
Click to expand...
Click to collapse
Chainfire has stated before that root with SuperSU on 7.1 may be a while, that he's working on it but a lot has changed (at least I read this all from him on a Pixel related thread...I assume much of it holds true for 7.1 in general).

ohlin5 said:
Chainfire has stated before that root with SuperSU on 7.1 may be a while, that he's working on it but a lot has changed (at least I read this all from him on a Pixel related thread...I assume much of it holds true for 7.1 in general).
Click to expand...
Click to collapse
Oh thanks. I've seen others talk about rooting on 7.1 no problem. I'll have to do more digging I guess

I rooted the 7.1 DP 1 With supersu SR1-v2.78.
No issues at all (even A.R.I.S.E. worked after deleting audio_effects.conf)

Mgrev said:
I rooted the 7.1 DP 1 With supersu SR1-v2.78.
No issues at all (even A.R.I.S.E. worked after deleting audio_effects.conf)
Click to expand...
Click to collapse
Did you root after flashing the ota or full image? I've been trying sr1 and for whatever reason after the ramdisk patch script it fails.

Guitarboarder28 said:
Did you root after flashing the ota or full image? I've been trying sr1 and for whatever reason after the ramdisk patch script it fails.
Click to expand...
Click to collapse
I used Fastboot and flashed every image manually (so that i wouldn't loose data). I used twrp 3.0.2-2 fyi. What about you?

Mgrev said:
I used Fastboot and flashed every image manually (so that i wouldn't loose data). I used twrp 3.0.2-2 fyi. What about you?
Click to expand...
Click to collapse
I was trying after flashing the ota. I even tried the full image without wiping (same version of twrp as you). Something must have just gotten messed up flashing the ota though. I gave up and did a full flash with wipe and sr1 flashed no problem. Thanks for trying to help me out though, I appreciate it
Edit: worded better. @Mgrev no hate was meant, thanks for trying to help me out!

Guitarboarder28 said:
you sound like you need a hug!
Oh thanks. I've seen others talk about rooting on 7.1 no problem. I'll have to do more digging I guess
Click to expand...
Click to collapse
Interesting...maybe he was exclusively referring to the new Pixel partition structure, etc...Not sure. Good luck

I was able to flash SuperSU R1 from TWRP and it worked, but when I added SUHIDE it hangs at boot animation. I flashed the factory image file by file, and not the OTA.

ohlin5 said:
Interesting...maybe he was exclusively referring to the new Pixel partition structure, etc...Not sure. Good luck
Click to expand...
Click to collapse
Yes that's my guess too I'm assuming he's talking about the pixel and it's new partitions
dratsablive said:
I was able to flash SuperSU R1 from TWRP and it worked, but when I added SUHIDE it hangs at boot animation. I flashed the factory image file by file, and not the OTA.
Click to expand...
Click to collapse
oh thanks for the heads up. Who knows if we'll ever see an updated suhide with safetynet checking the bootloader it may never be possible to pass safety net anymore

Guitarboarder28 said:
Yes that's my guess too I'm assuming he's talking about the pixel and it's new partitions
oh thanks for the heads up. Who knows if we'll ever see an updated suhide with safetynet checking the bootloader it may never be possible to pass safety net anymore
Click to expand...
Click to collapse
Well not worried about passing safetynet, since I can do without Android Pay, just want to hide root to play PoGo.

dratsablive said:
Well not worried about passing safetynet, since I can do without Android Pay, just want to hide root to play PoGo.
Click to expand...
Click to collapse
Oh is it no longer using safetynet? There's a new hide method with magisk V8 maybe that'll work

Guitarboarder28 said:
Oh is it no longer using safetynet? There's a new hide method with magisk V8 maybe that'll work
Click to expand...
Click to collapse
Well my bootloader is unlocked, but having suhide installed on the developer preview causes a boot hang. Will have to try the other method out. Thanks.

Guitarboarder28 said:
I was trying after flashing the ota. I even tried the full image without wiping (same version of twrp as you). Something must have just gotten messed up flashing the ota though. I gave up and did a full flash with wipe and sr1 flashed no problem. Thanks for trying to help me out though, I appreciate it
Edit: worded better. @Mgrev no hate was meant, thanks for trying to help me out!
Click to expand...
Click to collapse
I didn't think you meant to express hate either!
I seemed to forget to mention that i backed up my data with titanium backup, flashed, then wiped, and then restored it. So in the end, you probably need to wipe (just like you did)

dratsablive said:
Well my bootloader is unlocked, but having suhide installed on the developer preview causes a boot hang. Will have to try the other method out. Thanks.
Click to expand...
Click to collapse
Magisk hide just hides Magisk itself... it doesn't do anything for root. As for PoGo, right now the only way to do that on 7.1.1 is to NOT be rooted.
Once the kernel sources for the 7.1.1 are released, this patch will make its way onto custom kernels, which means you'll still be able to edit /system while rooted, unroot, and keep the changes via the patched kernel, as well as bypassing the SafetyNet bootloader check.
A kernel does exist now with that patch (francokernel), but it is based on the 7.0 kernel sources, so some things are broken if used on 7.1.1.
In re: to the superSU ramdisk install failure, this will happen if there are old files left over in /data from a previous magisk install and/or patched boot images. The SuperSU installer script will detect those and step into code branches that it doesn't need to be in, and thus fail. The solution is deleting the offending files from TWRP w/ adb, and installing SuperSU zip again.
/thread

Thread cleaned a bit, please stay on topic.
Have a good day!
Forum moderator,
Matt

Works fine for me flashed 7.1.1 OTA then flashed SuperSU zip

[GUIDE] Log in to Snapchat on Stock Rooted ROM (NOOB-friendly)

tl;dr: fastboot boot to stock boot.img, log in to snapchat, reboot.
Hello All,
I was trying to log in to Snapchat and I discovered that it won't let you log in if you're rooted. I searched the forums and I found a lot of different solutions, but they required me to install Xposed or fully unroot, which seemed like a hassle. So, I decided to make a guide for the best way to do this on a stock rooted ROM.
1. Download the full system image for your device + build (https://developers.google.com/android/images)
This worked on my Pixel, it should work for other Nexus/Pixel/Pixel XL devices as well though.
2. Unzip the file
3. Unzip the image-sailfish-XXXXXX.zip inside the new folder
4. Connect your device to your computer with ADB and reboot to bootloader
5. fastboot boot path/to/boot.img (inside the folder from step 3.)
NOTE: Please make sure to fastboot BOOT, NOT fastboot FLASH.
6. Once booted, log in to Snapchat. It should work.
7. Reboot.
8. Backup Snapchat in Titanium Backup so you don't have to do this again.
You should now be logged in to Snapchat! Since you only booted to the stock unrooted image, you should still be rooted after you reboot in step 7.

Doesn't work babe

I just use magisk yes it's limited but it does what it need it for

avenator14 said:
tl;dr: fastboot boot to stock boot.img, log in to snapchat, reboot.
Hello All,
I was trying to log in to Snapchat and I discovered that it won't let you log in if you're rooted. I searched the forums and I found a lot of different solutions, but they required me to install Xposed or fully unroot, which seemed like a hassle. So, I decided to make a guide for the best way to do this on a stock rooted ROM.
1. Download the full system image for your device + build (https://developers.google.com/android/images)
This worked on my Pixel, it should work for other Nexus/Pixel/Pixel XL devices as well though.
2. Unzip the file
3. Unzip the image-sailfish-XXXXXX.zip inside the new folder
4. Connect your device to your computer with ADB and reboot to bootloader
5. fastboot boot path/to/boot.img (inside the folder from step 3.)
NOTE: Please make sure to fastboot BOOT, NOT fastboot FLASH.
6. Once booted, log in to Snapchat. It should work.
7. Reboot.
8. Backup Snapchat in Titanium Backup so you don't have to do this again.
You should now be logged in to Snapchat! Since you only booted to the stock unrooted image, you should still be rooted after you reboot in step 7.
Click to expand...
Click to collapse
This method wont work with the stock kernel. You would need to use a kernel that includes the safetynet patch since Snapchat checks against this. Magisk does work though. Just select Snapchat from the Magisk Hide settings menu once you get it installed properly.

uodii said:
This method wont work with the stock kernel. You would need to use a kernel that includes the safetynet patch since Snapchat checks against this. Magisk does work though. Just select Snapchat from the Magisk Hide settings menu once you get it installed properly.
Click to expand...
Click to collapse
I got this to work on my own stock rooted Pixel with the stock kernel. You are booting into an unrooted image using my method, so the SU binary will not be present. This was sufficient to allow me to log in to Snapchat, even though my bootloader was still unlocked. This works because the Pixel uses a systemless root.

real_stacky said:
Doesn't work babe
Click to expand...
Click to collapse
Are you using the right image? Make sure you are downloading the factory image, not the OTA image. This will only work if you are on stock firmware, and make sure to download the right factory image for your device and version.

avenator14 said:
Are you using the right image? Make sure you are downloading the factory image, not the OTA image. This will only work if you are on stock firmware, and make sure to download the right factory image for your device and version.
Click to expand...
Click to collapse
SafetyNet checks for an unlocked bootloader. That's why I said a patched kernel is required...Unless they changed something again, but this was definitely required a few months back.

uodii said:
SafetyNet checks for an unlocked bootloader. That's why I said a patched kernel is required...Unless they changed something again, but this was definitely required a few months back.
Click to expand...
Click to collapse
Hm yeah I can't really speak to the inner workings of SafetyNet, however I did have an unlocked bootloader at the time of performing this, so from my own anecdotal experience I can say that this method allows Snapchat to log in with an unlocked bootloader (I haven't tried it with other apps) on build NHG47K.

avenator14 said:
Hm yeah I can't really speak to the inner workings of SafetyNet, however I did have an unlocked bootloader at the time of performing this, so from my own anecdotal experience I can say that this method allows Snapchat to log in with an unlocked bootloader (I haven't tried it with other apps) on build NHG47K.
Click to expand...
Click to collapse
If that's the case, then it's good info. Maybe it only does a SU check instead of SafetyNet. Good info.

avenator14 said:
Are you using the right image? Make sure you are downloading the factory image, not the OTA image. This will only work if you are on stock firmware, and make sure to download the right factory image for your device and version.
Click to expand...
Click to collapse
Nvm i found an app on the play store that does the trick called Hide Rooting Lite. (Can't link it soz)

thanx this actually worked flawlessly. latest build twrp rc1 and rooted. I follow your instruction and it worked. now TB backup. thanx and rep for u.
Edit: after doing this I actually did a TB backup. deleted snapchat app and restore app+data using TB. having root and it still works.

Failed to boot boot.img ..... "dtb not found"....?

+1 mate
Titanium backup is also good for me cause I use the app kik and when you sign out you lose all your messages so I make backups and when restoring all my messages are back!!
Going be using that app more often now!!

https://www.youtube.com/watch?v=a-PtwtQFBWg
I made a video on how to increase your snap score. Hope you enjoy it!

cgrimm9 said:
I just use magisk yes it's limited but it does what it need it for
Click to expand...
Click to collapse
What do you mean it's limited? More features than SuperSU
---------- Post added at 11:29 AM ---------- Previous post was at 11:14 AM ----------
eduardmc said:
thanx this actually worked flawlessly. latest build twrp rc1 and rooted. I follow your instruction and it worked. now TB backup. thanx and rep for u.
Edit: after doing this I actually did a TB backup. deleted snapchat app and restore app+data using TB. having root and it still works.
Click to expand...
Click to collapse
Just use Magisk m8

Magisk

Dear advisors,
Iam using stock samsung note 4 SM-910G. Snapdragon 805. Android 6.0.1. Marshmallow. I need advise on to how to install magisk on my device. Can it be done? Appreciate on a step by step instruction on how do i install it.

I don' think this is the right place for this, but it't not my job to decide.
Anyways, which ROM are you using? Are you on stock TouchWiz?

No roms its just stock. Ive rooted on my note 2 previously but i wanna know how on note 4 but rooting via magisk.
So where do i need to post this question?

Firdhaus81 said:
No roms its just stock. Ive rooted on my note 2 previously but i wanna know how on note 4 but rooting via magisk.
So where do i need to post this question?
Click to expand...
Click to collapse
You should've asked in the Q&A section. Thread moderators will probably move this one as soon as they notice, don't worry, you're a relatively new user so you can't know everything yet.
By the way, you can't root with Magisk, if you're not rooted with other methods, because your bootloader is still locked and neither stock recovery or Odin would allow it. You first need to get root access by using some specific software such as ChainFire Autoroot. There are some guides available, but first you have to search for the zip file on the ChainFire website (link), pay attention to the model and check if Odin is included with the package. If it's not, just do a Google search for a fairly recent version. When you have everything you need, use this guide to root your device (link), just go to the second post for the exact procedure.
Once you're done, use some software to verify root access, then download Flashify from Play Store. Go to the TWRP website and get the latest recovery (version 3.1.1) for your device. N910G codename should be 'trlte', better verify yourself to avoid issues. You can now flash the recovery using Flashify.
You're now at a good point, your device is ready for further steps to get Magisk. I'll post the rest of the procedure as soon as you're ready, I just want to warn you that Magisk could possibly create some issues like app instability or inability to use certain services. I got rid of it after few months and flashed SuperSU instead, which is the better option in my opinion. I've never used it on TouchWiz so I can't tell you anything specific about that, you may want to backup your current ROM into an external MicroSD using TWRP, just in case.

Black Shade said:
You should've asked in the Q&A section. Thread moderators will probably move this one as soon as they notice, don't worry, you're a relatively new user so you can't know everything yet.
By the way, you can't root with Magisk, if you're not rooted with other methods, because your bootloader is still locked and neither stock recovery or Odin would allow it. You first need to get root access by using some specific software such as ChainFire Autoroot. There are some guides available, but first you have to search for the zip file on the ChainFire website (link), pay attention to the model and check if Odin is included with the package. If it's not, just do a Google search for a fairly recent version. When you have everything you need, use this guide to root your device (link), just go to the second post for the exact procedure.
Once you're done, use some software to verify root access, then download Flashify from Play Store. Go to the TWRP website and get the latest recovery (version 3.1.1) for your device. N910G codename should be 'trlte', better verify yourself to avoid issues. You can now flash the recovery using Flashify.
You're now at a good point, your device is ready for further steps to get Magisk. I'll post the rest of the procedure as soon as you're ready, I just want to warn you that Magisk could possibly create some issues like app instability or inability to use certain services. I got rid of it after few months and flashed SuperSU instead, which is the better option in my opinion. I've never used it on TouchWiz so I can't tell you anything specific about that, you may want to backup your current ROM into an external MicroSD using TWRP, just in case.
Click to expand...
Click to collapse
Thank you for the advices. I did root following all those steps u gave me. For rooting i dont have a problem but its only after which when im tryin to install magisk i get error sayin that magisk only works for lollipop. Abit confused there. From my knowledge i knew that to install magisk i need to unroot superSu which i did & kept my twrp custom recovery. But somehow i cant seem to keep the twrp recovery & thats where i cant flash the 13.3v magisk.

Firdhaus81 said:
Thank you for the advices. I did root following all those steps u gave me. For rooting i dont have a problem but its only after which when im tryin to install magisk i get error sayin that magisk only works for lollipop. Abit confused there. From my knowledge i knew that to install magisk i need to unroot superSu which i did & kept my twrp custom recovery. But somehow i cant seem to keep the twrp recovery & thats where i cant flash the 13.3v magisk.
Click to expand...
Click to collapse
As I thought, Magisk won't work with the stock ROM. The main issue here is the kernel, which doesn't allow such modification. ChainFire has found a workaround to bring SuperSU on TouchWiz, but the fact it's not open source doesn't allow Magisk developers to use the same method. The head developer, few months ago, said that he was working on it and he was making some progress, but apparently it's not ready yet. I think it's not worth trying again, it won't work at the moment. I suggest keeping an eye on the thread, in case there are some updates. At the moment, I recommend either using SuperSU (which I recommend anyways), or flashing a different ROM, since deodexed TouchWiz ROMs with H-Vitamin or RAM Kernel do actually support Magisk, I tried myself.

Thread moved to proper section

The thing is ive seen in youtube they do get to root via magisk. I need this as to get my pokemon go workin.. :laugh:

Firdhaus81 said:
The thing is ive seen in youtube they do get to root via magisk. I need this as to get my pokemon go workin.. [emoji23]
Click to expand...
Click to collapse
Black Shade is right about the kernel. Using the wrong kernel will cause the install to fail. I'm on an n910t3, using ramrom v3 kernel, and I'm using magisk 13.3 for Android pay and viper audio. There's an official magisk 13.3 thread on xda somewhere. You should try there as a start.
Sent from my SM-N935S using Tapatalk

Attached my kernel info if u can help to check?

Found working magisk root method note 4 sm-n910g
Hello, I'm unsure if it'll work for you but it did for me.
1. Downloaded latest firmware from sammobile & flashed it to phone. (You can just try and find your current boot.img and skip to step 4)
2. Opened stock ROM zip & md5 file - using 7zip
3. Extracted boot.img
4. Place onto SD-CARD
5. Install Magisk apk
6. Magisk > settings > output format > change to ".tar" file
7. Magisk > patch boot.img
8. Locate "patched boot.img" > flash in Odin AP
Done
Worked for my galaxy note 4 SM-N910G

thanks, followed your instruction and it works for me. now i am able to flash magisk on my stock Note 4 though i had to surf more inform on xda using tar-Tool_Odin3-v3.10.7
Worked for my galaxy note 4 SM-N910G[/QUOTE]

MagiskFan said:
Found working magisk root method note 4 sm-n910g
Hello, I'm unsure if it'll work for you but it did for me.
1. Downloaded latest firmware from sammobile & flashed it to phone. (You can just try and find your current boot.img and skip to step 4)
2. Opened stock ROM zip & md5 file - using 7zip
3. Extracted boot.img
4. Place onto SD-CARD
5. Install Magisk apk
6. Magisk > settings > output format > change to ".tar" file
7. Magisk > patch boot.img
8. Locate "patched boot.img" > flash in Odin AP
Done
Worked for my galaxy note 4 SM-N910G
Click to expand...
Click to collapse
Hi, I know is kind of old post here. Just wanna ask, have you try the latest version of Magisk on your note 4 SM-N910G? New version of magisk does not have the option to choose the output format to ".tar" file.

pippideniro said:
thanks, followed your instruction and it works for me. now i am able to flash magisk on my stock Note 4 though i had to surf more inform on xda using tar-Tool_Odin3-v3.10.7
Worked for my galaxy note 4 SM-N910G
Click to expand...
Click to collapse
[/QUOTE]
Hi, I know is kind of old post here. Just wanna ask, have you try the latest version of Magisk on your note 4 SM-N910G? New version of magisk does not have the option to choose the output format to ".tar" file.

@lhooipg Were you asking to help him, or do you wanna know yourself?

bmwdroid said:
@lhooipg Were you asking to help him, or do you wanna know yourself?
Click to expand...
Click to collapse
I wanna know myself, I am facing the same issue as him. Thank you.

[Tutorial] Flashing OTA Updates on Unlocked, Rooted Pixel 2 w/o Custom Recovery

PLEASE READ MY IMPORTANT NOTICE ABOUT 8.1 BELOW
See update as well!
Hey, guys! This is my first thread ever, so please give me some grace. (I do not know all the formatting stuff yet)
I decided that because I had to wipe my Pixel 2 XL twice in the process of trying to figure this out, I may as well write a quick tutorial on how to do this the easy (and mostly safe) way.
This is where they all insert the disclaimer:
Code:
This tutoial is based on software I did not write or contribute to in any way, If you have issues with it, contact their respective developers, Google can help with this. DO NOT blame me for your now-a-fancy-paperweight-pixel,
I have diplomatic immunity and will tell you to contact my lawyer who doesn't care. You risk what you risk, take responsibility for that.
Now for the meat....
What you need:
Unlocked bootloader with MAGISK ROOT (other root may work, only tested magisk beta)
The Latest OTA File from the official download page, saved to your device
The Flashfire App by one of the greatest XDA legends of all time, Chainfire
The flashable zips for Magisk and any other stuff you want installed (like a custom kernel) when the update gets flashed (typically magisk modules do not need to be reflashed, they stay installed)
Advisable: nothing that has modified your system partitions (only have systemless mods like magisk)
Now that you're all set:
Open Flashfire and grant it root permissions.
Tap through all the warnings
Hit the plus sign and hit "Flash ZIP or OTA"
Find your stored OTA file you downloaded from the Google OTA page.
Check all three available options, (Auto-mount, Mount system..., and Restore Boot and Recovery)
Repeat step #3 with your newfound ability to flash zips, add a kernel (I use Flash Kernel) and flash the newest official magisk beta the same way. NOTE: Check boxes for these shouldn't need to include "auto-mount" or "restore boot and recovery images"
DISABLE ever-root settings completely from the flash queue.
Click the red lightning button at the bottom left.
Give it up to 5 minutes to do its business.
Reboot and profit.
If that didn't make sense, watch my simple video!!
(there is one mistake in the video, on all other things than the OTA itself, DO NOT check the box for restoring stock boot and recovery)
NOTE: You are unable to flash recoveries through this method, I've tried it and so far no luck. We may be able to later when apps let us flash the boot partition properly but for now, it won't stick.
Credits:
Chainfire for his amazing flashfire app!
Team Pixel for their awesome phone.
XDA for all the years of being awesome.
topjohnwu for magisk badassery
If you should be credited, PM ME.
IMPORTANT NOTICE:
Magisk beta thread clearly states that currently (12/05/2017) Magisk 14.5 with official pixel support is only tested up to 8.0, NOT 8.1 yet. Due to this and the fact that aosp 8.1 is super duper new and most kernels likely don't have an 8.1 version, I'd recommend waiting till this post is updated to flash anything 8.1
UPDATE 12/29/2017: As of now flashfire works for some things on oreo, but Ill need to look into it after we get another Oreo update to see if it can be flashed from there, however this may become obsolete assuming you can just use magisk's new features to do updates the official way. (google it)
That's all, Folks!
If this helped you, SMASH that thanks button! Also, Please try to keep OT stuff to a minimum.
I'll be posting a video soon that shows the flashfire process in a little better detail. Posted it, in the instructions!!

Nice work man. Always nice seeing people share their processes.
Sent from my Pixel 2 XL using Tapatalk

I've done similar ota flash with Flashfire on other devices. Will try this on my Pixel XL 2 with the next ota! Kudos

This method should work to flash the DP2 OTA from november update right?

Triscuit said:
This method should work to flash the DP2 OTA from november update right?
Click to expand...
Click to collapse
As long as the update is a newer one than your current one, is NOT an 8.1 beta, and is a FULL Ota (as in, it's larger than 1gb file) then it should flash. Of note: these are NOT the factory images you find on a very close by page from Google, they have to be the OTA zips.

What do you need to do if you have TWRP installed already? Can you still use this method?

uofirob said:
What do you need to do if you have TWRP installed already? Can you still use this method?
Click to expand...
Click to collapse
From what I remember from my Nexus 6p, having TWRP or Stock recovery made no difference flashing the update in FlashFire. But if you want TWRP installed you'll have to flash it again after the OTA due to the OTA replacing it unless you chose "Restore boot and recovery" during the zip selection process. Eben then I am not 100% sure TWRP will remain.
Sent from my Pixel 2 XL using Tapatalk

Does the OTA with this method delete the userdata partition? Or does it keep personal data intact?

so the magisk "install to Second slot (After OTA)" doesnt work?

FlashFire has not been updated since the Pixel 2 was released. Is it really meant to work with the Pixel 2?

cb474 said:
FlashFire has not been updated since the Pixel 2 was released. Is it really meant to work with the Pixel 2?
Click to expand...
Click to collapse
This is what I'm thinking. I doubt this will work at all. Flashfire is finicky at best. Works great when it works. Has never been updated to work on our device.

rester555 said:
Does the OTA with this method delete the userdata partition? Or does it keep personal data intact?
Click to expand...
Click to collapse
Nope. It updates, just like the title says. No wiping your rear required. Just a clean plop.

JeffBea said:
This is what I'm thinking. I doubt this will work at all. Flashfire is finicky at best. Works great when it works. Has never been updated to work on our device.
Click to expand...
Click to collapse
It fully recognized my device as supported, and the update worked, I have tested it.

thomasamas said:
It fully recognized my device as supported, and the update worked, I have tested it.
Click to expand...
Click to collapse
I'll definitely try this then when December updated hits then. This was my preferred update method on my 6p.

JeffBea said:
I'll definitely try this then when December updated hits then. This was my preferred update method on my 6p.
Click to expand...
Click to collapse
Make sure to check for Magisk and your preferred kernel compatibility with the 8.1 update when it comes. Flashing Magisk when the OS doesn't yet work with it could cause some serious headaches, so check the Magisk thread. I'm sure you know what happens when you flash an incompatible kernel too....
In the case Magisk isn't compatible yet, you can always check for SUPERSU systemless compatibility, and do that instead of flashing Magisk.

linezero said:
so the magisk "install to Second slot (After OTA)" doesnt work?
Click to expand...
Click to collapse
This is what I would like to know as well

For those of us that were on the original pixel phone without a custom recovery, the blow method was always the fastest and easiest way to update without losing root. Anyone tried on the Dec update?
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips

Just tried this method and worked flawlessly.. Thank you OP!
Sent from my Pixel 2 XL using Tapatalk

mrbracht said:
Just tried this method and worked flawlessly.. Thank you OP!
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Did you use this process to upgrade to the release build of 8.1 (Dec update)?

Jexx11 said:
This is what I would like to know as well
Click to expand...
Click to collapse
As far as I know, Magisk 14.5 understands both partitions now, and will flash to BOTH a/b, if you check the script for it, that's what it does. If this isn't what you're looking for, please clarify!