[FIX] How to receive OTA update after root? - Samsung Galaxy S7 Questions and Answers

hello xda,
This tutorial shows you that how to make your device fully functional with root.
but most of the peoples question is to pass SafetyNet, make their device status "Official" and also to work with Private Mode after root and with custom kernel. And here is the answer ,
BEFORE BEGIN, BACKUP YOUR DATA AND DOWNLOAD CORRECT FILES. I AM NOT RESPONSIBLE FOR ANY DAMAGE CAUSE TO YOUR DEVICE BY THIS PROCEDURE!!!
1. Download and flash stock oreo firmware via ODIN.
2. After boot, Turn on developer mode and turn on OEM Unlock.
3. turn off your device and get in to download mode.
4. Flash latest TWRP recovery via ODIN.
6. Get in to twrp recovery and format data and again boot into twrp.
7. first flash "no-verity-opt-encrypt-6.0", secondly flash "latest magisk", thirdly flash "TGP kernel v6.8.0".
8. After boot, update magisk app itself ( Latest v17.1 ).
9. download and install any root browser app ( root explorer recommanded) and give the root permission.
10. Navigate to /system/priv-app/PersonalPageService and delete the apk file and replace with modified apk
( Do not forget to set correct permission "rw-r-r" or chmod 644).
11. Navigate to /system/app/sysscope and delete the apk file and replace with modified apk
( Do not forget to set correct permission "rw-r-r" or chmod 644).
12. Reboot the device.
13. Now you can check SafetyNet, System Status and private mode.
NOTE :
DO NOT ATTEMPT TO INSTALL SYSTEM UPDATE. BECAUSE YOU MAY HAVE INSTALLED CUSTOM RECOVERY. SO THE UPDATE WILL PROBABLY FAIL.
YOU CAN OBTAIN UPDATE PACKAGE AT "/data/fota".
YOU CAN ALSO RIDE WITH BANKING APPS AND OTHER APPS WITH ROOT.
CAUTION :
●DO NOT FLASH CF SU.
●DO NOT ATTEMPT TO FLASH SYSTEM UPDATE.
●DO NOT INSTALL XPOSED FRAMEWORK. THIS WILL TRIGGER SAFETYNET.
KNOWN BUGS : NOTHING YET. TESTED ON GALAXY S7 (EXYNOS).
Files
( sysscope, PersonalPageService ) : https://drive.google.com/folderview?id=1ekOXMNMYGhaMke58y_xkVMFiAvP-Ncpm
no-verity-opt-encrypt-6.0 :
https://androidfilehost.com/?fid=817906626617949632
TGP Kernel v6.8.0 :
https://androidfilehost.com/?fid=1322778262903992351
Systemless magisk :
https://www.google.lk/amp/s/forum.x...-magisk-v7-universal-systemless-t3473445/amp/

second method:
Download (e.g. with SamFirm (v0.3.6)) and flash stock oreo firmware via Odin
After boot, Turn on developer mode and turn on OEM Unlock.
Turn off your device and get in to download mode.
Flash latest TWRP recovery via ODIN.
Get in to twrp recovery and format data and again boot into twrp.
First flash "no-verity-opt-encrypt-6.0", secondly flash "latest magisk"
After boot install latest magisk manager
In magisk manager install the module Xposed Framework (SDK 26) systemless
Install XposedInstaller_3.1.5-Magisk from https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
In XposedInstaller-App install Firefds Kit [Oreo]
Start Firefds Kit [Oreo] and enable in Security hack "Fake system status"
Now the system status is official and you can download the OTA-Update.
To get ctsProfile: true and basicIntegrity: true you have to deactivate Xposed in the XposedInstaller-App (disable Xposed Status) and disable the module in magisk manager
But the interessting question would be how to install OTA updates without loosing root.

Because, if you go in the xposed method, It will probably trigger SafetyNet. So you couldn't be able to ride with updates, banking apps and etc.
This is why I placed modified Sysscope in order to make official.
And yes, stock private mode checks for custom binary or custom kernel. So the best way to modify the apk to work with custom binary.
Unfortunately, you cannot be able to install system updates via recovery. But, you can extract the fota.zip and place those files manually at your own risk. But I recommend you not to do.
DO NOT INSTALL XPOSED. IT WILL TRIGGER SAFETYNET. EVEN THOU SYSTEMLESS METHOD WOULDN'T HELP.

What should I do to get root again after the OTA?

Reflash magisk to regain root access

Are there any news to this topic?

Related

Private Mod Fixed on Latest MM Update Rooted Debloat Knox-Free !

Hi everyone.
Thats annoying issue about "activating private mode" after knox removed and patched kernel for root. (after supersu installed)
A.N.D. i just did it.
i found an apk file on androidfilehost named "PersonalPageService.apk" i used it for the success.
i guess this is a "patched apk" but don't know where i got it and who patched also which version for.
but work perfect on: 08 Nov 2016 (N915FXXS1DPK3) Stock Fw.
i debloat and removed knox and all around from the phone.
after all; disappointed with "activating private mod fails"
then tried a lot of things. finally done it.
instructions:
1. You must have "stock kernel backup"
2. Root with latest supersu
3. Place the "PersonalPageService.apk" in attachment to /system/priv-app/PersonalPageService/
4. Set permissions rw-r--r--
5. Reboot to TWRP (recovery mode)
6. Wipe dalvik and cache
7. Restore the stock kernel backup (boot.img)
8. Reboot system.
9. Check if private mode can be enabled. (it should so)
10. after Once you activated and inactivated "private mode"
11. Reboot to Recovery mode (TWRP) and flash the latest SuperSu again.
12. After reboot the system, you will have rooted, knox free, debloated
Note: (must done before. for details; see this post: https://forum.xda-developers.com/showpost.php?p=70388470&postcount=2)
13. Also Private Mode working system.
if it helps, i am glad.
thanks.

[ROOT][L09/L19] Pre-rooted boot.img for P9 Nougat (b378)

This is now deprecated
See proper SuperSu root installation instruction by @hakaz here: https://forum.xda-developers.com/showpost.php?p=71588837&postcount=102
Install stock b378 boot image (L09) here first: https://mega.nz/#!v1RGRSzD!7Z9oKmvEbZHG9UGwxh-iCR_tEw2qjVJ2tHkb1mFSTLk
Splitting this out into separate thread for better visibility. Note that if you are already on L09 B378 root, no need to update -
What is this?
Root on Nougat for the Huawei P9. It's a boot image, pre-rooted with PHH's SuperUser. Requires an unlocked bootloader.
Downloads:
B378
L09: https://mega.nz/#!ekJVzLyY!pOhWHYpdhuRSFtBvxGYlMMFH5hFg0TG8bG17D13ZohM
L19: https://mega.nz/#!blgUnDpD!OAiHXwXvUfJ36OZeNBFbVkBeEocnNc-irHHo5CxMjrA
Installation:
Root install method 1 (no TWRP)
Reboot phone into bootloader mode
Download boot.img to PC and fastboot flash with: "fastboot flash boot rooted_b378_boot.img"
Reboot phone back into system
Install phh's SuperUser app from Play Store
Install JRummy's Busybox Installer and install to /vendor/xbin
Root install method 2 (with TWRP)
Download boot.img to phone (Internal Downloads or External SD)
Use OldDroid's TWRP: https://forum.xda-developers.com/p9/development/twrp-t3565703/post71244945#post71244945
Reboot into TWRP
Select "Install" -> Click "Images" -> Go to External SD and select your rooted_b378_boot.img
Flash and reboot phone back into system
Install phh's SuperUser app from Play Store
Install JRummy's Busybox Installer and install to /vendor/xbin
Note: To get AdAway working, go to Preferences, then scroll down to "Target hosts file" and set it to "custom target". Then set Custom target to "/vendor/etc/hosts"
No responsibility if this doesn't work/breaks your device/eats your cat etc. - make sure you backup your data and have a backup boot/recovery image handy
XDA:DevDB Information
Pre-rooted boot.img for P9 Nougat, Kernel for the Huawei P9
Contributors
Atarii, PHH, LastStandingDroid, OldDroid, Dkionline
Version Information
Status: Stable
Stable Release Date: 2017-03-17
Beta Release Date: 2017-01-20
Created 2017-03-17
Last Updated 2017-03-17
Update (17/03/2017):
* Added L19 pre-rooted boot.img
This is not systemless root yes? No OTA support?
askor said:
This is not systemless root yes? No OTA support?
Click to expand...
Click to collapse
Yes this is Systemless, OTA should be fine - I've manually flashed OTA via dload but not tested normal OTA upgrade
will this root method have any drawbacks compared to the standard method( installing twrp and then flasing super su) am i going to be able to do the same things that im able to do with any rooted device? thanks in advice
ricardo99831390 said:
will this root method have any drawbacks compared to the standard method( installing twrp and then flasing super su) am i going to be able to do the same things that im able to do with any rooted device? thanks in advice
Click to expand...
Click to collapse
SuperSu does not currently work on the P9 with Nougat, partially due to lack of loop mount support in the kernel. Kernel sources are needed to rectify this, so I encourage people to email Huawei asking for their Nougat kernel patches.
PHH is not perfect (some apps don't work fully) but it's the best we have right now
Atarii said:
SuperSu does not currently work on the P9 with Nougat, partially due to lack of loop mount support in the kernel. Kernel sources are needed to rectify this, so I encourage people to email Huawei asking for their Nougat kernel patches.
PHH is not perfect (some apps don't work fully) but it's the best we have right now
Click to expand...
Click to collapse
ohh okay thanks for the info and also the work, i guess im waiting till the fully working method is out.
I've heard that they will relase the source near this month or the next when they finsh updating every p9
Is it possible to use this prerooted boot.img for l19 honor 8?
No. It's for P9, Honor 8 isn't P9, right?
Atarii said:
Splitting this out into separate thread for better visibility. Note that if you are already on L09 B378 root, no need to update
What is this?
Root on Nougat for the Huawei P9. It's a boot image, pre-rooted with PHH's SuperUser. Requires an unlocked bootloader.
Installation:
Root install method 2 (with TWRP)
Download boot.img to phone (Internal Downloads or External SD)
Use OldDroid's TWRP: https://forum.xda-developers.com/p9/development/twrp-t3565703/post71244945#post71244945
Reboot into TWRP
Select "Install" -> Click "Images" -> Go to External SD and select your rooted_b378_boot.img
Flash and reboot phone back into system
Install phh's SuperUser app from Play Store
Install JRummy's Busybox Installer and install to /vendor/xbin
Note: To get AdAway working, go to Preferences, then scroll down to "Target hosts file" and set it to "custom target". Then set Custom target to "/vendor/etc/hosts"
Click to expand...
Click to collapse
Thank you for the guide, everything worked as described. I've got my P9 with c432 b378, rooted and TWRP installed.
By testing so far, RootChecker, AdAway (v3.2), Titanium and Reboot (to boot into TWRP or fastboot) all work fine with this phh's SuperUser
PS: It's possible to install Chainfire's SuperSU instead, and Viper4Android works too, see e.g.
https://forum.xda-developers.com/showpost.php?p=71761747&postcount=167
Hi all, is that ok to flash on my current P9 L09C432B383 ?
The stock and pre-rooted boot.img states its form .378 but would it be ok on .383?
I dont know how to get root on it currently...
Thanks
twerg said:
Hi all, is that ok to flash on my current P9 L09C432B383 ?
The stock and pre-rooted boot.img states its form .378 but would it be ok on .383?
I dont know how to get root on it currently...
Thanks
Click to expand...
Click to collapse
https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
flash this, V3 is the version i would suggest.

Help!!!!

Hi,i updated my Htc A9 device from Marshmallow stock rom to Nougat official rom.
My Device Info:
***UNLOCKED***
S-OFF
CID BS_US001
MID 2PQ912000
Os 2.18.617.10​​I decided to root my device but i have problem on that!!!
Step 1- installed twrp 3.1.1-0 by fastboot mode
Step 2-installed Magisk Manager and download magisk v 12.0 zip file from magisk manager.
Step 3-Reboot to twrp recovery and select (Swipe To Allow Modifictions),then i flashed Magisk v 12.zip file from install menu and after that reboot device.(recovery log)
Step 4-Run Magisk Manager and see this Status:
installed magisk ver 12.0 --->Iatest version magisk installed and Properly rooted--->8:MAGISKSU
(tpjohnwu)Pic 1.
Superuser show on Magisk manager menu(Pic 2) and apps send request for permission to #superuser(Pic 3).
On the surface everything is OK but i have problem,for example i installed Link2SD app to use that for uninstall system apps and freez apps but does not work properly & show error msg(Pic 4).
I would be honored if you tell me what is my problem,thanks...
Hi, did you install busybox? I'm not familiar with Magisk nor Link2SD, but I can imagine there's an option to "ignore systemless root" so you'll be able to make changes to the system partition.
Do other root apps have problems as well?
eavandijk83 said:
Hi, did you install busybox? I'm not familiar with Magisk nor Link2SD, but I can imagine there's an option to "ignore systemless root" so you'll be able to make changes to the system partition.
Do other root apps have problems as well?
Click to expand...
Click to collapse
I can't install busy box,when o clicked on install button,busy box closed!!!!
cowboy_ea said:
I can't install busy box,when o clicked on install button,busy box closed!!!!
Click to expand...
Click to collapse
I think you'll be better off if you install the latest LOS ROM (20170530) and flash SuperSU. I don't know about Magisk, but I've never experienced problems with SuperSU. Once rooted, install busybox from the playstore and install into "system/xbin/"
In SuperSU make sure you override LOS root settings since it's set to off by default. By the way, you can turn on LOS root settings manualy. That way you don't need Magisk or SuperSU at all. Settings can be unlocked by tapping the build number several times in settings-->Device status. A menu will be unlocked called Developers options. Within that menu you'll find the root settings.
Good luck

[Guide] Root with Magisk, easy method

Hello,
I have a Galaxy On5 Pro in my home and was running AdHell till it could. Now that Samsung has stopped providing keys, an alternate way of disabling stock bloats and adblock was needed.
I tried the simplest way of rooting this phone, should work with any phone on On5 series.
1. Download the latest Firmware for your Phone from Updato or in other thread. Make sure it matches what you already have on your phone. Open archive and extract boot.img from that.
2. In Developer Options, enable OEM Unlocking.
3. Install Magisk Manager (as you normally do any apk).
4. Open Magisk Manager and click install, then select patch boot image. Select the boot.img you extratced in step 1 and select format to be 'tar'. Copy this patched image in Computer.
5. Boot in Odin and flash the patched boot image. Reboot the device.
You are rooted with Magisk.
If anyone is interested, I can provide more information if needed.
Thank you.
Works on SM-S550TL (TracFone)?
indianets said:
Hello,
I have a Galaxy On5 Pro in my home and was running AdHell till it could. Now that Samsung has stopped providing keys, an alternate way of disabling stock bloats and adblock was needed.
I tried the simplest way of rooting this phone, should work with any phone on On5 series.
1. Download the latest Firmware for your Phone from Updato or in other thread. Make sure it matches what you already have on your phone. Open archive and extract boot.img from that.
2. In Developer Options, enable OEM Unlocking.
3. Install Magisk Manager (as you normally do any apk).
4. Open Magisk Manager and click install, then select patch boot image. Select the boot.img you extratced in step 1 and select format to be 'tar'. Copy this patched image in Computer.
5. Boot in Odin and flash the patched boot image. Reboot the device.
You are rooted with Magisk.
If anyone is interested, I can provide more information if needed.
Thank you.
Click to expand...
Click to collapse
Boss, do u have a video instruction regarding this?

[Guide] Magisk manager installation on Mi CC 9

If you install twrp recovery then it is very easy to install magisk manager.
just go on your twrp recovery mode
Select advanced and select install root.
Reboot your Phone .
See magisk manager install successfully.
Any help about mi cc9 magisk manager just coment here. I will be ready for replay just like you want.
.
Or Download this file and install through twrp recovery.
Latest stable magisk manager zip [flash file]
https://drive.google.com/file/d/1j6EWKPt1ZNzW7QgtILkgW5xphCzzcKNH/view?usp=drivesdk
Magisk manager apk
https://drive.google.com/file/d/1Hzvi5f2bZcUPyzWx-ETfqZanQjLCJHGq/view?usp=drivesdk
Lijlp0/02plppp000p7 lu6pppp?0lpl
Ul u?????//6000
I've installed magisk without twrp, just follow guide online. No need specific software because 7zip can extract boot.img easily from update file. After that install magisk manager app on phone, select install - patch own boot file, copy modified file to pc again, reboot into bootloader, flash modified boot.img and reboot.
eidrag said:
I've installed magisk without twrp, just follow guide online. No need specific software because 7zip can extract boot.img easily from update file. After that install magisk manager app on phone, select install - patch own boot file, copy modified file to pc again, reboot into bootloader, flash modified boot.img and reboot.
Click to expand...
Click to collapse
I need unlock BL to flash the modded boot.img?
RazrBR said:
I need unlock BL to flash the modded boot.img?
Click to expand...
Click to collapse
Yes, first unlock BL to be able to enter fastboot mode. Apply to unlock bootloader with Mi account, please follow guide on how to unlock the bootloader.
eidrag said:
I've installed magisk without twrp, just follow guide online. No need specific software because 7zip can extract boot.img easily from update file. After that install magisk manager app on phone, select install - patch own boot file, copy modified file to pc again, reboot into bootloader, flash modified boot.img and reboot.
Click to expand...
Click to collapse
Hi. Did you do these passages also on MIUI 12? Because I installed Magisk app, but it showed Ramdisk: no, and now I don't know if I should install it in recovery partition or not
there's twrp and orangefox that can be used for cc9 meitu/vela. Unlock bootloader, enable adb, flash custom recovery by fastboot. After that use custom recovery to install magisk. I'm sorry I don't use cc9 anymore since last weekend because miui12 notification and permission is too aggressive, have to restart app everytime so that can get contact info.

Categories

Resources