This guide is based on the original PewPewK post.
Which, in turn, was inspired by TopJohnWu's 'Samsung (System-as-root)' Magisk Installation Guide
It is an extended walk through aimed at ALL users, meant specifically for the SM-T720 (Tab S5e) BUT specifically meant to:
UNLOCK THE BOOTLOADER
INTRODUCE ROOT
RESTORE STOCK/RELOCK THE BOOTLOADER
Because of the community support, the options available to you have become numerous!
So if you're looking to squeeze EVERY inch out of your tablet, search the thread for suggestions or see the links below:
Go HERE if you are interested in custom recovery (e.g., TWRP).
Go HERE if you are interested in custom ROMs or kernels.
ROOT WARNING
Introducing root and further tampering may lead to unfavorable performance and/or shortened device lifespan.
In extreme circumstances, it may render your device OR specific hardware components unstable or non-functioning.
By following this guide, you ACKNOWLEDGE these risks and release AHE_XDA, XDA and its CONTRIBUTORS of ANY and ALL responsibility.
WARRANTY WARNING
In many states, countries, provinces and territories, introducing root voids device warranty (manufacturer's and/or third-party). Please consult your regional Samsung office, place of purchase or third-party warranty company to determine if these terms are applicable to you.
ALTERNATIVES TO ROOT
If you are looking to maintain warranty and continue access to Samsung-specific features, consider disabling or uninstalling unwanted applications via the Android Debugging Bridge (ADB).
TiTiB, a genius in his own right, has a thread dedicated to the Tab S5e and bloat removal without the cost of warranty.
Visit it HERE and click 'Thanks!' if it helped.
Known Issues (January 31, 2020)
KNOWN ISSUES (January 31, 2020)
Where's Recovery?
Explanation: TWRP (custom recovery) is NOW available. Please visit TeamWin for instructions.
Workaround: Resolved as of August 6, 2019.
Magisk shows as 'Not Installed.'
Explanation: Magisk, due to the changes to the recovery partition in Android Pie & above, will not boot automatically. It requires user intervention.
Workaround: To enable root access, be prepared to hold 'Volume Up' and the 'Power' keys on EVERY BOOT or REBOOT.
WiFi stopped working after installing 'magisk_patched.tar' with Odin.
Explanation: Cause unknown as of January 31, 2020.
Workaround: In some cases, after introducing root ('magisk_patched.tar'), WiFi may stop working. If this happens, do the following:
From the app drawer, go to Settings > Connections > Wi-Fi.
Highlight and select your WiFi network.
Long press the network name and select "Forget Network".
Wait 3 to 5 seconds.
Press and click on the network in which you asked Android to forget.
Re-enter your password.
If entered correctly, WiFi will resume connectivity.
"Your phone is locked because the payment service was uninstalled."
OR
Only official released binaries are allowed to be flashed (vbmeta).
Explanation: To protect against various threats (e.g., compromised data, theft or root), Samsung, as of December 2017, introduced a series of low-level initiatives to LOCK the device should ANY part of Knox be compromised. These initiatives are frequently referred to as 'KG' (KnoxGuard) or 'RMM' (Remote Monitoring and Management).
Further details can be found HERE.
Workaround: A workaround now exists, thanks to @ianmacd, but requires TWRP to be installed followed by the Samsung multi-disabler file.
If you do NOT intend to install TWRP, precautions MUST be taken not to freeze, disable or remove the following files:
'Payment Services' (com.samsung.android.kgclient)
'KnoxGuard' (knoxguard.apk)
In most circumstances, the issue will present itself immediately after the application(s) is frozen, disabled or removed. In rare circumstances, only after a device restart.
PRO-TIP: Do NOT reboot unless absolutely necessary; opt to power down the device.
Should you encounter EITHER error, you will need to boot into 'Download Mode', revert to original factory settings and verify your Google account to avoid an FRP LOCK.
To enter 'Download Mode' and recover from the error:
Connect a USB cable to your Laptop/PC.
With power-off on the device, hold down BOTH 'Volume Up' and 'Volume Down'.
Connect the USB cable to the device, while holding down both volume keys, and press 'Power'.
If done correctly, the device will boot to 'Download Mode'.
My Streaming Service won't log me in, no longer provides HD viewing or doesn't allow offline downloads.
Explanation: Widevine is a digital rights management platform used by major streaming companies to prevent piracy.
Low-level details can be found HERE.
Workaround:
Resolved by @ianmacd and his 'liboemcrypto disabler' via Magisk Manager and/or Custom Recovery (e.g, TWRP) as of April 4, 2018.
NOTE: If you installed TWRP and flashed the Samsung multi-disabler file, this issue is resolved of as December 13, 2019.
If you do NOT intend to install TWRP, log-out and uninstall your streaming application(s). With root introduced and magisk enabled, download 'liboemcrypto' from 'Modules' within Magisk Manager. You will be asked to restart after installing the module. Do this and re-enable Magisk on boot. Sideload your streaming application(s) from a source OUTSIDE the Playstore. Log in and resume streaming.
Items are ADDED and UPDATED as they are discovered, solved or a workaround is introduced. Please message me directly if something is missing.
Requirements & Instructions
HARDWARE & SOFTWARE REQUIREMENTS
Windows Laptop/PC with more than 25GB of available storage space
SM-T720 Tablet (Galaxy Tab S5e)
Samsung USB Type-C Cable (as found in the original packaging)
WIFI connection (and if necessary, login details)
SECTION ONE - LOG-OUT & BACK-UP YOUR DATA
Log out of your Samsung and Google account(s).
Back-up ANY and ALL data as following this guide will result in COMPLETE data loss.
SECTION TWO - DOWNLOAD THE RIGHT UTILITIES
In order to root, you require several utilities.
They are as followed:
Samsung USB Drivers - Provides connectivity between Laptop/PC and your device.
7-Zip - An open-source file archiver.
Odin 3.13.1 - Used to flash original or custom Samsung firmware.
Frija - Downloads the latest available Samsung firmware.
Magisk Manager (APK) - Helps obtain/manage and extend root options. Download the latest .APK (Application Package).
Click on the UNDERLINED NAME of the above utilities to download them to your local Laptop/PC.
PRO-TIP: Create sub-directories, like pictured below, and organize your downloads accordingly:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PRO-TIP: Consider a donation to Frija, Magisk or your favorite developers as a token of goodwill and to help ensure future development efforts.
SECTION THREE - DOWNLOAD THE RIGHT FIRMWARE
In order to root or, at a later time, return to original factory settings; you MUST have a local copy of firmware.
This requires knowing our CSC; a three letter code that Samsung devices use to comply with local telecommunication standards and determine device-specific features or updates.
To locate your CSC, perform the following:
On your device, go to 'Settings'
From 'Settings', scroll down to 'About Tablet'.
Press on 'About Tablet' followed by a press on 'Software Information'
Scroll downwards until you see 'Service Provider SW Ver.'
There are three lines.
The third line will read similar to the following:
TUR//
Those three characters (e.g., TUR) represent the CSC code for your region.
PRO-TIP: Your CSC may OR may not be the same as the example; that's expected and perfectly normal.
Open Frija, which you downloaded under 'Section One', and input your model and CSC.
Make sure 'Auto' is selected and click on 'Check Update'.
If the right values are inputted, Frija will look similar to the following:
Click on 'Download' and select a location on your Laptop/PC.
When the download is complete, Frija will verify and decrypt the firmware.
Once finished, Frija will look similar to this example:
PRO-TIP: If you can't get Frija to open or download, right click and select 'Run as administrator'.
SECTION FOUR - UNLOCK THE BOOTLOADER
THIS STEP WILL REMOVE ALL DATA FROM YOUR DEVICE. PLEASE REFER TO 'SECTION ONE' FOR MORE DETAILS.
Power off the device.
Power on your Laptop/PC and login into your Windows account.
Connect the USB cable to your Laptop/PC but NOT to your device.
On the device, hold the 'Volume Up' and 'Volume Down' keys at the SAME time.
Connect the USB Cable from your Laptop/PC to the device.
You MUST hold BOTH keys during AND after inserting the USB Cable to receive the following warning:
PRO-TIP: In SOME cases, you may also need to hold 'POWER' as well.
To continue towards unlocking your bootloader, hold the 'Volume Up' key for approximately 4 to 5 seconds (or until the screen goes black).
After 4 to 5 seconds have passed (or if the screen went black), release the 'Volume Up' key and you will be presented with one last warning:
Press and click on the 'Volume Up' key to finalize your decision.
The device will factory reset and from now on, until the bootloader is re-locked, you will receive this warning:
Leave the device to reinitialize. This will take approximately three minutes. The device will erase itself and you will notice several reboots. Afterwards the only activity you'll see is a pulsing 'SAMSUNG' logo. Eventually you will be presented with the 'Let's Go!' set-up screen. Set the device aside for now.
SECTION FIVE - INSTALLING 7-ZIP
If you correctly followed the first FOUR sections, you now have the required utilities, firmware and an unlocked bootloader.
In order to proceed, you MUST install 7-Zip to extract and manipulate key files required for root.
If you have prior experience with 7-Zip or an alternate compression manager, SKIP this step and proceed to 'SECTION SIX'.
It IS enough to double-click the EXECUTABLE and install it; you need NOT configure anything.
However, for a visual reference, follow this LINK to see 7-Zip in use.
Alternately, for technical support and assistance SPECIFIC to 7-Zip, use this LINK. Search thoroughly before posting.
SECTION SIX - EXTRACTING FIRMWARE
Like the CSC code, mentioned in 'SECTION THREE', the name of your download will differ slightly but 'SM-T720' and 'AP_T720' will be in the file name:
Using 7-Zip, you must extract the following file:
AP_T720XXU1ASF1_CL15813856_QB24038915_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar.md5
From the following ZIP container:
SM-T720_1_20190603182427_gegcc1ebw1_fac.zip
Right click on your ZIP container, navigate to '7-Zip' and, from the sub-menu, select 'Extract Here'.
7-Zip will begin to decompress the necessary files and will result in the following output:
Delete ALL files except for the following:
SM-T720_1_20190603182427_gegcc1ebw1_fac.zip
AP_T720XXU1ASF1_CL15813856_QB24038915_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar.md5
Rename the extension of 'AP_T720XX.....tar.md5' to 'AP_T720XX.....tar' and ignore the warning provided by Windows.
When finished, your folder contents will look similar to this:
The AP file is required for root.
PRO-TIP: Keep the ZIP container should you ever want to revert back to original factory settings. If not, delete it and download again later using Frija.
SECTION SEVEN - ENABLE WIFI, TRANSFER FILES & INSTALL MAGISK MANAGER
In 'SECTION FOUR', the device was left to reinitialize.
This means you have a device that requires set-up:
Do NOT log into your Samsung or Google account. The ONLY thing required is WIFI:
PRO-TIP: WIFI and Magisk work together to help achieve root access, provide updates and for module repository access.
Once you've arrived at the home screen, you need to enable 'Developer Options' to ensure the bootloader is unlocked.
To verify your bootloader is unlocked, perform the following:
On your device, go to 'Settings'.
From 'Settings', scroll down to 'About Tablet'.
Press on 'Software Information'.
Scroll downwards until you see 'Build Number'.
Tap 'Build Number' seven times to enable 'Developer Options'.
Press the back button on the navigation bar to return to 'Settings'.
Underneath 'About Tablet', you will now see 'Developer Options'.
Open this and locate 'OEM Unlocking'.
If you've followed the outlined steps, your screen should match this example:
PRO-TIP: If your screen does NOT match the example, it is possible you are NOT connected to WIFI or you did NOT successfully unlock the bootloader. If all these conditions are true, restart the device and check again. If the issue persists, create a NEW response in the thread.
Now connect the device to your Laptop/PC and, when prompted, 'Allow access to tablet data'.
Using Windows Explorer, copy the following files to the 'Download' folder of your device:
MagiskManager-v7.3.2.apk
AP_T720XXU1ASF1_CL15813856_QB24038915_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar
Due to the size of the AP file, this may take several minutes on a low-end Laptop/PC.
Once the copy is complete, go to your device and double press on 'MagiskManager-v7.3.2.apk' to initiate the install process.
PRO-TIP: Due to changes introduced in Android Oreo, you MUST allow permission to install applications (APKs) not obtained from the PlayStore.
Click on 'Settings' to open the 'Install unknown apps' screen and toggle 'Allow from this source' on.
Press the back button on the navigation bar to allow the installation:
SECTION EIGHT - PATCH YOUR AP FILE
Open your app tray by swiping up and open Magisk Manager.
You will see a RED QUESTION MARK and the following error:
'Magisk is not installed.'
Click on 'Install' and, when prompted by Magisk, select 'Install' again:
Magisk will provide another prompt:
Choose 'Select and Patch a File' to proceed.
Magisk will now prompt for device access:
Click on 'Allow' and the internal Device File Explorer will open to the 'Recent' tab:
Click on the top app bar and select 'Downloads' to find your AP file:
And then:
Once inside the 'Downloads' folder, select your AP file to begin the flash process.
Once the flash process is complete, the status on the top title bar will change from 'Flashing' to 'Done!':
SECTION NINE - RETRIEVAL & DISSECTION
With our AP file patched by Magisk, you must now locate and transfer it back to our Laptop/PC.
If you have not already done so, reconnect the device to your Laptop/PC:
Open Windows Explorer, double-click on 'Tab S5e', double-click again on 'Tablet' and open the 'Downloads' folder:
Under 'Downloads', you will see THREE files:
AP_T720XXU1ASF1_CL15813856_QB24038915_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar
magisk_patched.tar
magisk_install_log_2019-07-10T225845Z
PRO-TIP: 'magisk_install_log' is an output of the AP file patching process. If you encountered ANY errors, keep a copy and raise a question in the thread.
Delete 'AP_T720XX.....tar' and copy 'magisk_patched.tar' back to your Laptop/PC; preferably to the 'FIRMWARE' sub-directory suggested in 'SECTION TWO'.
Due to the size of the 'magisk_patched.tar' file, this may take several minutes on a low-end Laptop/PC.
Once the transfer is complete, let's make room in our 'FIRMWARE' folder by deleting the 'AP_T720XX.....tar' file.
This should leave you with TWO files:
SM-T720_1_20190603182427_gegcc1ebw1_fac.zip
magisk_patched.tar
Move OR delete the 'SM-T720.....fac.zip' container so you can focus exclusively on 'magisk_patched.tar'.
With NO files left except for 'magisk_patched.tar', you must now use 7-Zip again to extract its contents.
PRO-TIP: Refer to 'SECTION FIVE' if you need a refresher on 7-Zip.
Right-click on the 'magisk_patched.tar' container, navigate to '7-Zip' and, from the sub-menu, select 'Extract Here'.
Once all files are extracted, your output will look similar to, if NOT exactly like, this:
Now DELETE these files:
dtbo.img.lz4
magisk_patched.tar
modem.bin.lz4
persist.img.ext4.lz4
system.img.ext4.lz4
userdata.img.ext4.lz4
vendor.img.ext4.lz4
In order to have the following:
meta-data [FOLDER]
boot.img
recovery.img
vbmeta.img
If done correctly, your folder output will look like this:
SECTION TEN - CREATE YOUR TAR
In 'SECTION NINE', you organized the following list of files/folder:
meta-data [FOLDER]
boot.img
recovery.img
vbmeta.img
Using Windows Explorer, navigate to your 'Firmware' folder (or whatever location you used).
Now, using 7-Zip, you need to compress these files into a TAR container.
This means you must select ALL files.
This can be achieved by using CRTL + A on your keyboard or simply by highlighting them all with a left-click:
Right-click on the selected files, navigate to '7-Zip' and, from the sub-menu, select 'Add to archive...':
If done correctly, the following screen will present itself:
Only THREE things MUST be done to complete our TAR:
Change the filename to 'magisk_patched' WITHOUT quotations
Change the 'Archive format' to 'TAR'
Click on 'OK' to confirm your decisions and begin compression:
PRO-TIP: If, for ANY reason, you don't want to keep these files, you can select 'Delete files after compression' before clicking on 'OK'.
With this step complete, you are left with the following output:
SECTION ELEVEN - DOWNLOAD MODE
Using the 'Power' key on your device , select 'Power off':
Disconnect the USB cable or the device will switch to 'Charging Mode':
On your device, hold 'Volume Up' and 'Power' together until the 'Android Recovery' screen appears:
'VOLUME UP' will navigate upwards, 'VOLUME DOWN' will navigate downwards, and 'POWER' will highlight and confirm your choice.
PRO-TIP: You may have to press 'POWER' twice.
Highlight and select 'Reboot to bootloader' to properly put your device into 'Download Mode':
Reconnect the device back to your Laptop/PC.
SECTION TWELVE - ODIN PREPARATION AND FLASH
Now, because recovery is unavailable, you must use Odin to flash your TAR file to introduce root.
In 'SECTION TWO', you downloaded Odin and created a folder for it.
You must now go to that folder, or whatever folder you opted to use, and decompress Odin.
Right-click on the 'Odin3_v3.13.1.zip' container, navigate to '7-Zip' and, from the sub-menu, select 'Extract Here'.
This will create a sub-directory called 'Odin3_v3.13.1'.
Double-click and you will be presented with the following output:
Double-click on 'Odin3 v3.13.1.exe' to launch the application.
You will receive a prompt written in both English and Korean. Click 'OK' to close the warning.
With Odin open, locate and click on the second tab called 'Options' and uncheck 'Auto Reboot':
When you click on the 'AP' button, Windows File Explorer will automatically launch.
As per 'SECTION NINE', and using Windows File Explorer, navigate to the location you created and saved 'magisk_patched.tar'.
Double-click 'magisk_patched.tar' (or alternatively, highlight the file and select 'Open') to have it load into the AP slot:
With all these steps completed and your device connected, STOP and read below:
A green navigation bar on Odin, and a white bar on you device, will appear.
This indicates that key files are being written to your device.
Irregardless of how quick or slow the progress bar is, DO NOT disconnect the device.
The device, no matter if the flash was successful or not, will do NOTHING because you unchecked 'Auto Reboot'.
Wait for 'PASS!' to appear in Odin before you disconnect your device.
If everything was done correctly, Odin will look like this:
Your device, on the other hand, will have the following bar across its screen:
Now disconnect the device, STOP and read below until you feel comfortable enough to execute the instructions:
Hold 'Volume Down' and 'Power' until the screen goes black (also known as a 'Soft Reset').
The moment the screen goes black, continue to hold down 'Power' but QUICKLY switch so now only 'Volume Up' is being held.
Do this until you enter 'Android Recovery'.
As outlined in 'SECTION ELEVEN', use the 'Volume Keys' & 'Power' to navigate the menu.
First select 'Wipe Data/Factory Reset' and, upon completion, choose 'Reboot System Now'.
Your device will reboot several times. This is expected behavior.
If everything was done correctly, your device will reinitialize and require set-up again:
SECTION THIRTEEN - ROOT VERIFICATION
Like 'SECTION SEVEN', you need WIFI to complete set-up but mustn't log into ANY accounts.
Also, like 'SECTION SEVEN', you will need to install Magisk Manager again.
Once the first two steps are complete, power-off the device:
With the device powered off AND disconnected, hold down 'Volume Up' and 'Power' until you see the following warning:
WARNING: From now on, on EVERY BOOT or REBOOT, you MUST do this if you want Magisk enabled.
Release all keys and allow the device to boot.
Once Android is loaded, launch Magisk from your app drawer.
If you are prompted to update, do so but select 'Direct Install (Recommended)' and remember the key sequence on reboot:
Magisk Manager, if set-up properly AND with root enabled, will look like this:
Magisk Manager, if NOT set-up properly OR with root disabled, will look like this:
PRO-TIP: To further validate root, you can use an application like 'Root Checker' to verify:
You may now log into your accounts and finish configuring the device.
Recognition & Sharing Policy
RECOGNITION
This guide, and the required methods and software, would NOT be possible with the efforts of the following individuals:
@topjohnwu
@ianmacd
@LuK1337
@invmini
@CrazyApe
@eragon5779
@PewPewK
A sincere thank you for your time, hard work and, most importantly, determination to explore.
Praise and tribute is also extended to @TiTiB for his editorial skills, testing and much needed feedback.
SHARING POLICY
Do NOT reuse any part of this guide without first asking.
Do NOT reuse any part of this guide without giving credit to those in the 'RECOGNITION' header.
ALL photographs, not screenshots, are the property of myself (AHE_XDA). I spent considerable time capturing and editing each posted photograph. Therefore photographs may NOT be downloaded, copied, reproduced or used anyway without consent.
If there's something you like (styling/format/text/photographs) and want to use, ask.
Return To Stock Instructions
To return to stock and/or relock the bootloader, these are the best instructions available:
https://forum.xda-developers.com/showpost.php?p=79698366&postcount=44
They are originally intended for the Galaxy S10 series but work perfectly for the Tab S5e (SM-T720).
Full credit to @robbo1947.
Very nice how-to!!!
Would've made my first attempts much easier
I made it through the old way, getting all bits and pieces from through the other thread, this saves new comers hours of reading through all info available and getting it done at once.
---------- Post added at 07:25 PM ---------- Previous post was at 07:24 PM ----------
Side note I never used the key combo on rebooting for magisk updates or other stuff, always had root enabled afterwards.
You've done one helluva job @AHE_XDA!! I can't even imagine how long it took to put all of this together. It leaves nothing to be desired. Honestly, I've never seen such a comprehensive guide on xda before. Here's some $$$$$$$$$$ in thanks.
BTW, I'm fully up and running with Magisk and am currently freezing away many apps.
CAUTION: Be very careful when freezing anything Samsung 'billing' related.
I got a bit carried away freezing Samsung stuff and locked it up tighter than a drum.
FYI, before rooting I was disabling every Samsung app I could (including com.sec.android.app.billing) and had no problems. Root really *is* powerful.?
Anyways, if you get in to a predicament like mine and see these screens there is still hope.
Power off> Hold both VOL> Plug in PC-connected USB cable> Press PWR
Might take a few tries, but eventually you should get to DOWNLOAD screen.
Pics are in reverse order. You would see the one on the right first.
@TiTiB
I was able to reproduce your error.
I updated the 'Known Issues' to reflect this.
It is either 'Payment Services' (com.samsung.android.kgclient)' or 'KnoxGuard' (knoxguard.apk) that caused the error.
I can disable, freeze or delete 'Samsung Billing' (com.sec.android.app.billing) without issue.
Thank you for this info! It really helps in my continuing persuit to get rid of as much Samsung stuff as possible, while still retaining OneUI functionality. It gets a bit unnerving freezing stuff when you're several days in to setting up stuff. I'm going slower this time.
@AHE_XDA first of all thanks for this manual, I had never seen more comprehensive here!
Second, I had one attempt to root t725, it was 2 months ago. I done all steps, made patched AP, glashed successfully (only ap, not other 3 files). After reboot I got exactly same messages as described in upper post! Not debloat, but straight from boot with root.
I afraid, gone to download mode and flashing stock. Got it back.
Never tried again.
Have you idea what was wrong?
I want to do again, but afraid a little...
Thanks
ivanox1972 said:
@AHE_XDA first of all thanks for this manual, I had never seen more comprehensive here!
Second, I had one attempt to root t725, it was 2 months ago. I done all steps, made patched AP, glashed successfully (only ap, not other 3 files). After reboot I got exactly same messages as described in upper post! Not debloat, but straight from boot with root.
I afraid, gone to download mode and flashing stock. Got it back.
Never tried again.
Have you idea what was wrong?
I want to do again, but afraid a little...
Thanks
Click to expand...
Click to collapse
After you flash the AP file with Magisk, you don't want to re-install the entire binary with Odin.
You need to dissect its contents, re-compress it and THEN install with Odin.
Take a look at 'Section Ten' on the first page to see what I'm talking about.
Any questions, place them on thread or PM me.
AHE_XDA said:
@TiTiB
I was able to reproduce your error.
I updated the 'Known Issues' to reflect this.
It is either 'Payment Services' (com.samsung.android.kgclient)' or 'KnoxGuard' (knoxguard.apk) that caused the error.
I can disable, freeze or delete 'Samsung Billing' (com.sec.android.app.billing) without issue.
Click to expand...
Click to collapse
Check this-wtf?
TiTiB said:
Check this-wtf?
Click to expand...
Click to collapse
Yes, there is a dependency between the two. With App Inpector, you don't see 'KnoxGuard' explicitly listed but if you use something like 'Root Explorer', you'll find it.
Until we get recovery, like the other Samsung devices on Pie, we simply can't touch these files.
AHE_XDA said:
Yes, there is a dependency between the two. With App Inpector, you don't see 'KnoxGuard' explicitly listed but if you use something like 'Root Explorer', you'll find it.
Until we get recovery, like the other Samsung devices on Pie, we simply can't touch these files.
Click to expand...
Click to collapse
I use MiXplorer and have seen those while 'xploring'. Before rooting, when I was using PackageDisabler, kgclient was one of the disabled packages....uh, so my point is WTF?
@TiTiB
So to make sure we understand each other; you could disable/uninstall it through ADB but a removal of the apk froze the device (along with the error)?
Bixby Is Coming - July Update
In the next build of software for the Tab S5e (July), Bixby will be introduced and fully integrated into the system.
This means nothing for root but means you'll have more to uninstall/disable.
If you don't want or need Bixby, stay on ANY release prior to July.
AHE_XDA said:
@TiTiB
So to make sure we understand each other; you could disable/uninstall it through ADB but a removal of the apk froze the device (along with the error)?
Click to expand...
Click to collapse
I disabled kgclient using Disabler Pro app with no ill effects (before rooting). It's in my 'disabledpackages133-OK.xml', so I assume it was disabled. Perhaps the Disabler app handled it differently or something, idk.
After I rooted, while I was freezing Samsung apps using '3C Toolbox Pro', and I'm *almost* 100% certain Payment Services/kgclient was among them, the tablet locked up. AFAIK, these two actions, using these two apps is effectively the same thing, therefore the 'wtf' statement.
I am curious enough that I'm going to prepare for disaster, then mess around with this package—first, disabling it with the 'CCSWE App Manager (SAMSUNG)' app, then manipulating the package's contents (expecting disaster), then freezing it with 3C Toolbox—I MUST HAVE THE ANSWER!! (TiTiB *does* stand for Tweak it Til it Breaks, after all) ?
It wiil be an hour or two, and, of course, I'll post my results here.
@TiTiB
Whenever you disable or remove a system app without root; the application still exists on the device.
It's never truly gone.
It's only been removed from your profile; usually referred to as user 0 (current user).
A factory reset will bring that application right back.
Introduce root and now, because you have administration access over the entire device, remove the application and it's gone for good (or at least until you flash stock firmware).
Alter them at a root level, freeze/remove/disable, it's likely you're going to see the same error as before.
TiTiB said:
I disabled kgclient using Disabler Pro app with no ill effects (before rooting). It's in my 'disabledpackages133-OK.xml', so I assume it was disabled. Perhaps the Disabler app handled it differently or something, idk.
After I rooted, while I was freezing Samsung apps using '3C Toolbox Pro', and I'm *almost* 100% certain Payment Services/kgclient was among them, the tablet locked up. AFAIK, these two actions, using these two apps is effectively the same thing, therefore the 'wtf' statement.
I am curious enough that I'm going to prepare for disaster, then mess around with this package—first, disabling it with the 'CCSWE App Manager (SAMSUNG)' app, then manipulating the package's contents (expecting disaster), then freezing it with 3C Toolbox—I MUST HAVE THE ANSWER!! (TiTiB *does* stand for Tweak it Til it Breaks, after all)
It wiil be an hour or two, and, of course, I'll post my results here.
Click to expand...
Click to collapse
Sho'nuff, stay away from Samsung Payment/kgclient if rooted.
Related
I am making this tutorial as I have had multiple versions of the LG LTE Leon and have used many firmware versions. I have created a stable method that has the least issues as I have had trouble with the latest firmware (MS34510f) disabling my root privileges. I have created a MEGA account specifically for all of the files necessary to complete this operation and have your device run smoothly. So, please follow my instructions exactly as stated and you should not have any issues. THIS PROCESS WILL REMOVE ALL DATA NOT SYNCED, DO READ BELOW NOTES IT IS VERY BENEFICIAL
Important Notes:
+This process will wipe all data that is not synced, it is important to ensure that no newer LG process are still on the device. Some might argue to leave data, to that I say good luck keeping your root and tethering without the device becoming suspiciously unstable.
+ I am not GUARANTEEING this will work on every model, but I have had an extremely high success rate with all Leon versions.
+ In this tutorial the process in which I remove Kingroot and replace it with SuperSu is for system stability. I find that most root functions I use seem to not work properly. (Wifi Tether Router and many others). So, I do recommend doing so.
+After the new OS is installed a MetroPCS splash screen will appear even if you do have T-Mobile. DO NOT BE ALARMED this firmware will not limit any functionality you had before, it will even help with tethering functionality.
Tutorial:
Let's Begin.
1. Download the link posted to obtain required files for this tutorial
Link: https://mega.nz/#F!PM4CQRqb!92kgIOnD0ZBY-8HVbtTwGQ
2. Open up LGFlashTool2014.exe
Begin by copying settings posted below, then click "normal flash"
3. Next click the "START" button
4. At this time, I recommend you verify all sync settings are to your liking and that all personal info needed is backed up
a. You have the option to throw all of your personal documents/pictures onto your SD card and removing it appropriately
(Go to: Settings - Storage - [scroll down to] Unmount SD card)
b. Next, navigate to Settings -Backup & reset [leave options default; both checked off] - Factory data reset - reset phone
c. Once reset it will most likely reboot, wipe, and then back to a OS. Now, you will Power Off entirely (make sure it is not plugged in so it will not go to charging mode)
d. Here is where we will hold down the Volume Up button with the phone unplugged from your PC. Then you must plug the USB into your phone.
e. A black screen with white text should post onto your screen, here we will continue to step 6
note: If this screen does not appear please power off and retry step d.
6. Next, follow the posted settings. Make sure to click the "Clear phone Software update Registry" button Then click "OK"
7. A new screen will arrive, and should begin the firmware download process. At this time it will take a few minute to load and should reboot to a fresh OS.
8. With the new OS in place, you can either follow the setup tutorial now or skip through for a later setup.
note: you can now insert your SD card
9. In the tools folder of the folder you downloaded copy the "mrw" folder to the Main Storage folder of your phone
10. Now copy the Kingroot apk to your downloads folder located on the main storage.
11. Go to Settings - About Phone - Software Info
At this time click the build number box a few times until it says you are a developer
12. Hit back until you are at the Setting menu, click on Developer options and check off "Stay Awake" and "Enable OEM Unlock" as well as "USB Debugging"
13. You may now run Kingroot, if it does not install root the first time it should flawlessly install the next.
14. After root is obtained, please go to your home screen and click the "Google Search" widget. Press Update Google Services and let it run. After that has been updated search for terminal emulator and install.
note: If the Play Store is acting fishy and force closing while typing in the search bar do not fret it will be fixed after reboot in further instruction
as an allternative use the jackpal.androidterm-1.0.70-71-minAPI4.apk provided in the "tools" folder
15. Open terminal and in a new window type: Su
16. Allow root usage and at this time type: sh /storage/emulated/0/mrw/root.sh
17. It will run with a few failed messages do not worry it should open SuperSu momentarily
18. Once SuperSu opens up allow it to update binaries using the "NORMAL" option but DO NOT REBOOT YET
19. At this time either download TWRP Manager from the play store or alternatively use the com.jmz.soft.twrpmanager-7.5.1.3-82-minAPI11.apk provided in the tools folder
20. Install and open TWRP Manager. Once opened click on device name and scroll until you see "LG Leon LTE (c50)"
a. Click on Recovery Version to Install and select "twrp-2.8.7.0-c50.img"
b. next click "Install Recovery" and if prompted for verification of install path and for install version select "YES" & "NORMAL"
21. After the TWRP setup is complete it may prompt you to reboot, if not click the arrow in the top left of the TWRP Manager screen and scroll down to "Reboot" and select "Reboot device"
22. After Reboot click TWRP Manager and verify a SuperSu prompt comes up if it hasn't already before the boot
At this point the device should be running smoothly. From here I prefer to do the following steps.
My Personal Setup after new install:
+Personally I like to install use a Root Uninstaller (I use 3C Toolbox Pro) and Uninstall and Backup all MetroPCS BloatWare including the Metro Browser.
+I also access the Hidden Menu by using the Dialer and Dial "2776348*#*"
- I scroll down to ApnUnlock and click to "Unlock APN"
- Then I navigate to Settings -Tethering & networks - Mobile Networks (I check off roaming data) - Access point names
--I then select the top APN and edit APN Type to: default,supl,mms,dun
---I click save from the top right selection, then turn on and off airplane mode
+If you are and Xposed user download "xposed-v79-sdk22-arm.zip","xposed-uninstaller-20150831-arm.zip", and "XposedInstaller_3.0_alpha4.apk" from: http://forum.xda-developers.com/showthread.php?t=3034811
-install the Xposed Installer, then Go to TWRP Manager, use reboot to recovery and from there click install and navigate to the "xposed-v79-sdk22-arm.zip" and install and reboot, it will reboot with a installing screen before your home screen, takes 5 minutes.
+I also use this AMAZING app "Wifi Tether Router", it is the only tethering app I use that works consistently (if you have an unlimited data plan). I get 30mbps up and down, playing many multiplayer games off my PC and PS4 averaging ping as low as 30 ! Setting I use for our device are in a post I created here: http://forum.xda-developers.com/leon/help/unlimited-metropcs-t-mobile-tether-t3290180
---------------------------------------------------------------------------------------------------------------------------------------------------------------
Special Thanks to:
MrW0lf from www.W0lfdroid.com for the Kingroot to SuperSU scrip
Numerous users on the XDA forums I pieced all of this information with
Fabio Grasso for making the amazing Wifi Tether Router
Team Win for being creating an awesome utility that has saved me from numerous bricks creating a stable method
Xposed and the creators of awesome additions such as Lolistat, Lucky Patcher, Max Lock, and SNAPPREFS
Any feedback? Did I do Okay? Questions? Let me know!
Worked for me on T-mobile H345
Worked for me on T-mobile H345 any way to install a H340 firmware on it? I GeT a Binary not authorised when trying to flash.
kodacy said:
Worked for me on T-mobile H345 any way to install a H340 firmware on it? I GeT a Binary not authorised when trying to flash.
Click to expand...
Click to collapse
Apologies for the late response, I never received a notification of your posting. I would not recommend that as I believe the H340 has a different "radio" driver or cellular chip, If I'm not mistaken the H340 isn't even LTE, the H345 is. In that case it may be possible. One thing I suggest doing before wasting your time in using any other ROM is googling H345 vs Ms345, typically the phonemore.com results will provide you with an abundance of hardware specs and let you know if they're different! Just be weary of the newest MS34510f_00.KDZ firmware I believe it has an active unroot process I've had some stability issues. I am using MS34510D_00.KDZ for months and have had no issues whatsoever! Again, I'm sorry I got back to you so late, let me know how everything goes!
brad2192 said:
Apologies for the late response, I never received a notification of your posting. I would not recommend that as I believe the H340 has a different "radio" driver or cellular chip, If I'm not mistaken the H340 isn't even LTE, the H345 is. In that case it may be possible. One thing I suggest doing before wasting your time in using any other ROM is googling H345 vs Ms345, typically the phonemore.com results will provide you with an abundance of hardware specs and let you know if they're different! Just be weary of the newest MS34510f_00.KDZ firmware I believe it has an active unroot process I've had some stability issues. I am using MS34510D_00.KDZ for months and have had no issues whatsoever! Again, I'm sorry I got back to you so late, let me know how everything goes!
Click to expand...
Click to collapse
No problem thank you for your help!
will i still have metro service?
Port(usb or serial) not found! tried on, off, update mode, changing ports and unplugging every other port. any thoughts?
kap10nuka said:
Port(usb or serial) not found! tried on, off, update mode, changing ports and unplugging every other port. any thoughts?
Click to expand...
Click to collapse
Same here (firmware update) usb not detected when using the S/W update tool
After going all the way through this guide with a T-Mobile Leon, I do indeed have a Metro PCS ROM and root, which is great! Unfortunately, it also refuses to acknowledge my T-Mobile SIM. In fairness, I did not even insert a SIM for the first time (just got the phone) until the end of the process, but it shows as carrier locked which is significantly less than useful. I'll flash back to a TMO rom and put the SIM in to double check, but it's quite a bummer. Great job on the guide otherwise, though! It definitely did what it says on the tin; I have root and apart from the SIM lock which may be my fault somehow it works great.
Hey bud those links are no longer valid know where i can get them?
Before starting (if you have SM-G973F NEE, you can use my prepatched/generated files and save 2 million years in preparation, see the guide at the bottom of this page):
1. Root and flash Magisk: https://topjohnwu.github.io/Magisk/samsung
Note: remember to use the button combination when booting/rebooting, and also remember to use internet when compleeting the android wizard when it runs.
2. Flash TWRP: https://forum.xda-developers.com/ga...ecovery-twrp-3-3-0-galaxy-s10-exynos-t3924856
Note: remember to use the button combination when booting/rebooting.
3. Create your SmaliPatch: https://forum.xda-developers.com/apps/magisk/module-smali-patcher-0-7-t3680053
Note: ALSO check "Magisk Reboot (Galaxy S10)". Keep the default checks.
4. Install generated SmaliPatch in Magisk and then reboot.
The actual guide:
Note - again: remember to use the root button combination when booting. Yes, this might be solved by our SmaliPatch, but i would´t trust it when going out of TWRP and so on, so to be on the safe side, always use this combination.
1. Download and install F-droid: https://f-droid.org/FDroid.apk
2. In F-droid, install "Amaze (Manage local files)", and "Termux".
3. In Amaze: Go to settings and check "Root Explorer" under Advanced. Grant root for Amaze in Magisk.
4. Download and install "Aurora Store": https://androidfilehost.com/?fid=1395089523397955190
5. In Aurora Store, install: "Titanium Backup"
6. Download NanoDroid: https://downloads.nanolx.org/NanoDroid/Stable/
Or download the one I flashed here (and skip step 7, 8 and 9): https://mega.nz/#!rrIXSSLZ!4dV5Qx1W0hJXFbnY8heYcAUmOEWmkgdzcnfb2DhtRgo
7. Open the downloaded file with 7zip (right-click, 7zip, Open archive), and right-click on ".nanodroid-setup" and click on Edit
8. Change "nanodroid_gmscore=0" to "nanodroid_gmscore=1". This is to install MicroGs original GMSCore, and not NanoDroids (which is good, but did not work 100% this time). Documentation on alter installation can be found here: https://github.com/Nanolx/NanoDroid/blob/master/doc/AlterInstallation.md
9. Save and close ".nanodroid-setup", and 7-zip should ask you if you want to update the changes in the archive. Click yes. If this does not work for some reson, just drag ".nanodroid-setup" to the desktop, modify it, save, and drag it back.
10. Copy your modified NanoDroid zip into your phone (Download folder).
11. In Amaze: copy your NanoDroid zip in the Download folder to "/data/". This is to be able to access this file from TWRP later.
12: Debloat: run debloat.bat. This script keeps the launcher and a few other things. It keeps the apps that i think is the most essential, but removes Samsung Health for example. You can modify if you know what you want and how to do it.
Download here: https://mega.nz/#!62YHFSaS!di_HY7ceHMgfKyRfpTOnLgFoviWub0MCojrLyH4Jnho
13. In Titanium: uninstall "Play Services" and GMS, and GMS policy-something (don´t remember the package name, but search for gms). Titanium might seem to "hang" on uninstalling some of these apps, if so, just reboot and continue. This is normal.
SINCE I FORGOT THE PACKAGE NAMES, CAN SOMEONE PLEASE SEND ME A SCREENSHOT OF THE ONES THAT APPEARS WHEN SEARCHING ON "gms"? I will update this guide when i know what the exact names are.
14. In Amaze: click Root(/) in the menu, go to "/system/priv-app/", remove these dirs: GMSCore, GoogleServicesFramework, Phonesky
15. Reboot into TWRP, mount "/system" and "/data". Flash your NanoDroid file located in "/data/". Do not wipe cache. Reboot to get out of TWRP.
16. Launch "MicroG Settings". Click on permissions warning, and let Android get all permissions it asks for. Then click on "Google device registration" and turn ON (check). Do the same for "Google Cloud Messaging".
17. Still in "MicroG Settings" app: Click on "UnifiedNlp Settings", then on "Configure location backends", then check the checkbox (allow location permission if prompted). Do the same for "Configure address lookup backends".
18. Open the terminal that you installed in step 5, and run this:
Code:
su
Grant root access if prompted, otherwise, to go magisk and grant root for "shell".
19. Run these commands:
Code:
pm grant com.google.android.gms android.permission.ACCESS_FINE_LOCATION
pm grant com.google.android.gms android.permission.ACCESS_COARSE_LOCATION
20. In Aurora Store: install "push notification checking-fix" and run. Run the new installed app, then click "Confirmation".
21. Go to "MicroG Settings" again, click on "Google Cloud Messaging", check if "Current State" is NOT disconnected (something "connected" is good). Not connected? Reboot and do step 20 again.
22. Install Afwall and lock your sh*t down.
In AFwall, I also go to "Preferences", then "Experimental", click on "Startup directory path for script", then click on "/system/etc/init.d/", then click on "Fix startup data leak".
AFWall documentation on what to block/allow: https://github.com/ukanth/afwall/wiki/System-Applications-to-block-or-allow
Congrats, you are now in privacy heaven!
For SM-G973F NEE (nordic):
Prepatched Magisk, TWRP and SmaliPatch for and other files can be downloaded here: https://mega.nz/#F!LjQ0HYqR!2X72CW1kp3zh2kBxWDwG6A
These are the files that i used.
The prepatched Magisk image is based on "SM-G973F_1_20190417080614_xq2zehce6z_fac", downloaded with SamFirm.
REMEMBER THIS AFTER FLASHING PREPATCHED MAGISK:
(Powering up normally) → (System with no Magisk)
(Power + Bixby + Volume Up) → (Bootloader warning) → (Release all buttons) → (System with Magisk)
(Power + Bixby + Volume Up) → (Bootloader warning) → (Keep holding volume up) → (Actual recovery)
Quick guide to root, install Magisk, TWRP and SmaliPatch:
1. Unlock bootloader: https://www.androidexplained.com/galaxy-s10-unlock-bootloader/
2. Flash prepatched Magisk: https://mega.nz/#!2uRHkKCR!0j3Bx6iKbNL7yxqWHFBoAD7SpSGsvrrLdfIdJb73Hbk
BE READY FOR AUTO REBOOT (if you did not uncheck it in Odin)
3. Go directly to recovery and do a factory reset
4. Reboot, and be ready for one more auto reboot after the samsung logo!
5. Finish the android wizard WITH internet
6. Reboot again
7. Open Magisk (will be added after a while automatically), it will ask to finish the Magisk installation, click yes, be ready for automatic reboot
8. In Magisk install (as module): https://mega.nz/#!KzZRmQLS!ClmDmFAgaKd10o8hfjgmvI3PEdf3GCsV0lZKLtYPhFo
9. Reboot
10. Flash TWRP: https://mega.nz/#!72BFiQIK!yCVddqBDgPrBPlMNr6Y9x1OBNWpD3JBxmyf57D3eOAY
11. Follow the actual guide above
Please me feedback on what to make better. I want everybody to be able to get their privacy back!
Credits to:
topjohnwu for Magisk
Geiti94 and ianmacd for TWRP
fOmey for Smali Patcher
Nice to see development for the S10 - maybe you should move the post to the ROMS, Kernel, Recoveries Section.
As for improvements:
First that pops to mind, maybe you should credit the people who made Root, TWRP & Smali.
Second, which Pie version (ASD5)??
Third, maybe some pics.
Norup58 said:
Nice to see development for the S10 - maybe you should move the post to the ROMS, Kernel, Recoveries Section.
As for improvements:
First that pops to mind, maybe you should credit the people who made Root, TWRP & Smali.
Second, which Pie version (ASD5)??
Third, maybe some pics.
Click to expand...
Click to collapse
Thanks for your feedback. I have added credits and firmware information.
I wanted to post in dev, but I was not allowed due to too few posts.
Great work! I am about to take my privacy back as well but I have some questions:
- Will the same method work by flashing microg packages from official project, instead of flashing the nanodroid package you mention?
- Is it possible to encrypt /data folder and lock bootloader, so if telephone gets stolen there is no way they access your data?
- How do you handle OTA updates? Do you need to run the above guide every new OTA update?
Thanks!
dklearhos said:
Great work! I am about to take my privacy back as well but I have some questions:
- Will the same method work by flashing microg packages from official project, instead of flashing the nanodroid package you mention?
- Is it possible to encrypt /data folder and lock bootloader, so if telephone gets stolen there is no way they access your data?
- How do you handle OTA updates? Do you need to run the above guide every new OTA update?
Thanks!
Click to expand...
Click to collapse
Sorry for a late response.
Good on you! Since you asked almost a month ago, I guess you have already proceeded? In that case, what did you do?
Well, this was an early way to take your privacy back for s10, but time has changed and new ways seems to be avaliable now.
For one, there is a custom rom out there that use Aroma to debloat, but I don't know if it removes g stuff (I asked but the answer was vague, to say at least).
The other thing is that the encryption stuff has been improved too, and other things that makes the root easier to live with. Like updates that you mentioned (maybe not ota, but not custom rom updates with latest security patches).
I will have to take a look at this soon, because the way described in the main thread is causing some problems with WiFi and Bluetooth. Not unusable but my watch and headphones has to be re-paired every time I reboot the phone. And no updates. Except for that, I have been very pleased with my setup the last months.
I will make a new thread or update this when I know the steps to take our privacy back with the new roms and what not. Wish you all luck until then!
petriusus said:
Before starting (if you have SM-G973F NEE, you can use my prepatched/generated files and save 2 million years in preparation, see the guide at the bottom of this page):
1. Root and flash Magisk: https://topjohnwu.github.io/Magisk/samsung
Note: remember to use the button combination when booting/rebooting, and also remember to use internet when compleeting the android wizard when it runs.
2. Flash TWRP: https://forum.xda-developers.com/ga...ecovery-twrp-3-3-0-galaxy-s10-exynos-t3924856
Note: remember to use the button combination when booting/rebooting.
3. Create your SmaliPatch: https://forum.xda-developers.com/apps/magisk/module-smali-patcher-0-7-t3680053
Note: ALSO check "Magisk Reboot (Galaxy S10)". Keep the default checks.
4. Install generated SmaliPatch in Magisk and then reboot.
The actual guide:
Note - again: remember to use the root button combination when booting. Yes, this might be solved by our SmaliPatch, but i would´t trust it when going out of TWRP and so on, so to be on the safe side, always use this combination.
1. Download and install F-droid: https://f-droid.org/FDroid.apk
2. In F-droid, install "Amaze (Manage local files)", and "Termux".
3. In Amaze: Go to settings and check "Root Explorer" under Advanced. Grant root for Amaze in Magisk.
4. Download and install "Aurora Store": https://androidfilehost.com/?fid=1395089523397955190
5. In Aurora Store, install: "Titanium Backup"
6. Download NanoDroid: https://downloads.nanolx.org/NanoDroid/Stable/
Or download the one I flashed here (and skip step 7, 8 and 9): https://mega.nz/#!rrIXSSLZ!4dV5Qx1W0hJXFbnY8heYcAUmOEWmkgdzcnfb2DhtRgo
7. Open the downloaded file with 7zip (right-click, 7zip, Open archive), and right-click on ".nanodroid-setup" and click on Edit
8. Change "nanodroid_gmscore=0" to "nanodroid_gmscore=1". This is to install MicroGs original GMSCore, and not NanoDroids (which is good, but did not work 100% this time). Documentation on alter installation can be found here: https://github.com/Nanolx/NanoDroid/blob/master/doc/AlterInstallation.md
9. Save and close ".nanodroid-setup", and 7-zip should ask you if you want to update the changes in the archive. Click yes. If this does not work for some reson, just drag ".nanodroid-setup" to the desktop, modify it, save, and drag it back.
10. Copy your modified NanoDroid zip into your phone (Download folder).
11. In Amaze: copy your NanoDroid zip in the Download folder to "/data/". This is to be able to access this file from TWRP later.
12: Debloat: run debloat.bat. This script keeps the launcher and a few other things. It keeps the apps that i think is the most essential, but removes Samsung Health for example. You can modify if you know what you want and how to do it.
Download here: https://mega.nz/#!62YHFSaS!di_HY7ceHMgfKyRfpTOnLgFoviWub0MCojrLyH4Jnho
13. In Titanium: uninstall "Play Services" and GMS, and GMS policy-something (don´t remember the package name, but search for gms). Titanium might seem to "hang" on uninstalling some of these apps, if so, just reboot and continue. This is normal.
SINCE I FORGOT THE PACKAGE NAMES, CAN SOMEONE PLEASE SEND ME A SCREENSHOT OF THE ONES THAT APPEARS WHEN SEARCHING ON "gms"? I will update this guide when i know what the exact names are.
14. In Amaze: click Root(/) in the menu, go to "/system/priv-app/", remove these dirs: GMSCore, GoogleServicesFramework, Phonesky
15. Reboot into TWRP, mount "/system" and "/data". Flash your NanoDroid file located in "/data/". Do not wipe cache. Reboot to get out of TWRP.
16. Launch "MicroG Settings". Click on permissions warning, and let Android get all permissions it asks for. Then click on "Google device registration" and turn ON (check). Do the same for "Google Cloud Messaging".
17. Still in "MicroG Settings" app: Click on "UnifiedNlp Settings", then on "Configure location backends", then check the checkbox (allow location permission if prompted). Do the same for "Configure address lookup backends".
18. Open the terminal that you installed in step 5, and run this:
Grant root access if prompted, otherwise, to go magisk and grant root for "shell".
19. Run these commands:
20. In Aurora Store: install "push notification checking-fix" and run. Run the new installed app, then click "Confirmation".
21. Go to "MicroG Settings" again, click on "Google Cloud Messaging", check if "Current State" is NOT disconnected (something "connected" is good). Not connected? Reboot and do step 20 again.
22. Install Afwall and lock your sh*t down.
In AFwall, I also go to "Preferences", then "Experimental", click on "Startup directory path for script", then click on "/system/etc/init.d/", then click on "Fix startup data leak".
AFWall documentation on what to block/allow: https://github.com/ukanth/afwall/wiki/System-Applications-to-block-or-allow
Congrats, you are now in privacy heaven!
For SM-G973F NEE (nordic):
Prepatched Magisk, TWRP and SmaliPatch for and other files can be downloaded here: https://mega.nz/#F!LjQ0HYqR!2X72CW1kp3zh2kBxWDwG6A
These are the files that i used.
The prepatched Magisk image is based on "SM-G973F_1_20190417080614_xq2zehce6z_fac", downloaded with SamFirm.
REMEMBER THIS AFTER FLASHING PREPATCHED MAGISK:
(Powering up normally) → (System with no Magisk)
(Power + Bixby + Volume Up) → (Bootloader warning) → (Release all buttons) → (System with Magisk)
(Power + Bixby + Volume Up) → (Bootloader warning) → (Keep holding volume up) → (Actual recovery)
Quick guide to root, install Magisk, TWRP and SmaliPatch:
1. Unlock bootloader: https://www.androidexplained.com/galaxy-s10-unlock-bootloader/
2. Flash prepatched Magisk: https://mega.nz/#!2uRHkKCR!0j3Bx6iKbNL7yxqWHFBoAD7SpSGsvrrLdfIdJb73Hbk
BE READY FOR AUTO REBOOT (if you did not uncheck it in Odin)
3. Go directly to recovery and do a factory reset
4. Reboot, and be ready for one more auto reboot after the samsung logo!
5. Finish the android wizard WITH internet
6. Reboot again
7. Open Magisk (will be added after a while automatically), it will ask to finish the Magisk installation, click yes, be ready for automatic reboot
8. In Magisk install (as module): https://mega.nz/#!KzZRmQLS!ClmDmFAgaKd10o8hfjgmvI3PEdf3GCsV0lZKLtYPhFo
9. Reboot
10. Flash TWRP: https://mega.nz/#!72BFiQIK!yCVddqBDgPrBPlMNr6Y9x1OBNWpD3JBxmyf57D3eOAY
11. Follow the actual guide above
Please me feedback on what to make better. I want everybody to be able to get their privacy back!
Credits to:
topjohnwu for Magisk
Geiti94 and ianmacd for TWRP
fOmey for Smali Patcher
Click to expand...
Click to collapse
Make a rom with all these mods via Superr's Kitchen and post it at Roms.
ExtremeGrief said:
Make a rom with all these mods via Superr's Kitchen and post it at Roms.
Click to expand...
Click to collapse
Yes, that would be awesome.
Do you know if my rom would only be work with phones with the same firmware that i am using?
Sorry, but what benefits actually does this provide?
FlatOutRU said:
Sorry, but what benefits actually does this provide?
Click to expand...
Click to collapse
Taking back privacy or making a rom?
@petriusus
Thanks for the guide. Privacy is becoming more and more of a luxury these days.
petriusus said:
Taking back privacy or making a rom?
Click to expand...
Click to collapse
----------------------------------------------------------------------------------------------
Does this method allow one to still use the Stock Samsung OS, or, does this involve using a Custom ROM? Thanks for your time.
CommanderSozo said:
----------------------------------------------------------------------------------------------
Does this method allow one to still use the Stock Samsung OS, or, does this involve using a Custom ROM? Thanks for your time.
Click to expand...
Click to collapse
It's all on stock.
Keule-T said:
It's all on stock.
Click to expand...
Click to collapse
---------------------------------------------------------------------
Ok. I'm new to all of this - could I follow the same steps for a Samsung Galaxy Note 9 SM-N960F/DS model to achieve the same Privacy while being able to use Samsung One UI combined with full S-Pen functionality? If this is possible and just so I am on the same page, I could also completely remove GAPPS/Google Play Services and replace with MicroG? If the method to achieve this is different on a Note 9, do you know if there are any Instructions? Thanks again.
CommanderSozo said:
---------------------------------------------------------------------
Ok. I'm new to all of this - could I follow the same steps for a Samsung Galaxy Note 9 SM-N960F/DS model to achieve the same Privacy while being able to use Samsung One UI combined with full S-Pen functionality? If this is possible and just so I am on the same page, I could also completely remove GAPPS/Google Play Services and replace with MicroG? If the method to achieve this is different on a Note 9, do you know if there are any Instructions? Thanks again.
Click to expand...
Click to collapse
It should all be the same. For specifics have a look in the N9 forum (I don't own one, so for specific steps I can't help).
@petriusus
Long time since last post - so I have not found that and start a simular thread. Sorry for that.
Debloated stock -without Google apps- for best performance/privacy
One word ahead: I am a huge fan of Custom Rom (LOS). Nevertheless some feature will be missed (volte) and performance might be not perfect (camera, dolby) due to proprietary firmware. On the other hand I like to keep away from data collecting...
forum.xda-developers.com
I am wondering whether you have done updates from the initial Android 9? Bringing Magisk/TWRP to the device is rather complex, so how all that behaves in terms of security updates. How to spoof a A11?
First of All, these are my knowledge which was gained through hard reading from XDA Developers Forum, GitHub, reddit, different websites & watching YouTube Videos.DISCLAIMER: Here, I will explain all the process of unlocking Bootloader, Flashing Recovery & Rooting Your Xiaomi Phone, though the general idea is the same, so you can read it from TOP TO BOTTOM because you can use this knowledge FOR ANY ANDROID PHONE GENERALLY. Here, I also explained ALL THE PROBLEMS YOU MIGHT FACE WHILE DOING THIS, AND HOW TO GET OUT OF THOSE PROBLEMS, BECAUSE XDA THREADS AND YOUTUBE VIDEOS DOES NOT ANSWER YOUR PROBLEMS IN ONE THREAD OR IN ONE VIDEO, ONLY WHILE DOING IT, WE FIND THAT, DOING THESE WEREN'T SO EASY LIKE YOUTUBE VIDEOS OR XDA THREADS
AND OF COURSE, DO THESE ON YOUR OWN RISK, IF SOMETHING HAPPENS TO YOUR DEVICE AND YOU BLAME ME, I WILL LMAO AT YOU.
REQUIREMENTS: 1. PC/LAPTOP 2. PENDRIVE WITH OTG CABLE (FOR PRECAUTION, GO TO STEP 4.3 TO LEARN WHY)
Step Number 01: Backup All Your Data:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
YOU HAVE BACKUP ALL YOUR DATA, INCLUDING APP DATA, GALLARY PHOTOS, ALL OF THEM BECUASE UNLOCKING BOOTLOADER WILL RESET EVERYTHING, IT WILL START FROM THE MOMENT WHEN YOU BOUGHT YOUR PHONE FIRST & SWITCHED IT ON.
STEPS:
To Backup All Your Data-
Go to settings "backup and restore" in additional setting (or in MY DEVICE - BACK UP & RESTORE) you can use either mobile or computer backup, both are same, after backing up, transfer it to computer.
Backup your contact from "contacts" (optional, because "step a" includes this)
Then connect your phone with your pc & backup all the necessary files, for example, create a backup of these folders:
DCIM
Download
Pictures
MIUI (Gallery, recorder etc.)
Shareit, vidmate folder
Whatsapp folder (you can also backup it in google, goto SETTINGS - CHATS - CHAT BACKUP)
and others as per your necessity
My process is a manual process, so no app is required.
READ IT: in internet, you will find that you can use rooted app to backup these, like TITANIUM, or take a NANDROID BACKUP (SYSTEM AND APPS) USING TWRP RECOVERY, my boy, listen well, you haven't yet unlocked your bootloader, how can you have a rooted device and twrp recovery? (well you can have a rooted device but that also requires unlocked bootloader which will reset everything on your phone)
Step Number 02: Unlock Your Bootloader
STEPS:
Enable developer option by clicking on MIUI version 7 times
from "Additional setting", go to "developer option". there, do these:
enable OEM UNLOCKING
in device unlocking, add your MI account. if shows problem or error, remove your MI account then add it again from device unlocking, (NOT FROM MY DEVICE, ADD ACCOUNT) then, it will take you to main settings, just come back and click add again, it will work in Sha Allah.
now in your pc, download MI Flash Unlock from official MI website, HERE (better to install the latest)
Unzip it, run it using "batch_unlock", add your mi account
in additional settings again, in developer option, enable "USB DEBUGGING"
now in pc, connect your phone in fastboot mood, (swithing off then holding power button and volume down will take you to fastboot mood, there is another process of going to fastboot mood, which is described in step 3)
if your device is recognized IN MIUI UNLOCK TOOL but after connecting it in miui unlock tool, fastboot mood turns of and says "PRESS ANY KEY TO SHUTDOWN" in your phone, you may try swithing to USB port 2 but it didn't work for me. Instead, I ran this bat file code "AS ADMINISTRATOR" from XDA developer forum, you can do it too. I renamed it as "a.bat" first thing to come it my mind. then disconnect USB and connect again in your fastboot mood. Click Refresh in unlock tool.
(OR, IF YOUR DEVICE IS NOT RECOGNIZED IN MIUI UNLOCK TOOL, FOLLOW THESE:
remove MI account from unlock tools and again add, if password shows error even after typing correctly, use phone number and pass to log in, in stead of email and password. Check if device if recognized or not.
If not, try these, Download MIUI Flash Tool and unzip it, run XiaoMiFlash.exe. At the top line, find DRIVER, install all DRIVERS.
IF YOU FACE LOG FILE ERROR,
SOLUTION: JUST CREATE A FOLDER NAMED "log" in the same directory. DONE, YOUR DRIVER WILL BE INSTALLED, CLICK YES EVERY TIME, THEN CONNECT YOUR PHONE WITH MIUI UNLOCK TOOL AND CLICK REFRESH.
your device will be shown in "batch_unlock" in sha Allah. Click unlock. Remember, your phone will loose all data, just full factory reset.
8. after 99% it will show "unlock sign" at the top of your phone, and your phone will reboot, just let it reboot. It will take at best 12 minutes to reboot. Don't worry, seat tight, watch a YouTube Video of Dr. Zakir Naik or Ahmed Deedat Sir <3.9. setup your phone as if it's a new device. (it is necessary, because after this, we will flash recovery and root your phone, because it is really important to take a backup of your original "PERSIST.IMG" . it is possible for rooted device only. (though it can be done through recovery, but from magisk, it's the best way and safest).10. you can restore all backup from your pc now. (not necessary, if you want to change ROM)
Step Number 03: Install ADB (PC) & TWRP RECOVERY (Android)STEPS:
download latest SDK from OFFICIAL WEBSITE.
2. name of the download will be "platform-tools_r31.0.2-windows.zip" unzip it in DESKTOP (IMPORTANT). it's name will be "platform-tools", open it. (ADB COMMAND WILL RUN ONLY IN THIS FOLDER.
ALTERNATIVE ADB: you can also do it by one click adb installer, just install the file, and cmd will work at any position. File is given in the telegram, in my .rar file. But sometimes it shows problem, adb command is not recognized by the windows. then, above platform tools folder is useful as it always works.
3. downlead latest TWRP specific for your device from HERE. website guide: >find your device name> device model> Download Links > click either "Primary (Americas)" or "Primary (Europe)" or you can download them from XDA too (XDA process: search in google "TWRP for MI 9 se (your specific device with model number, not Mi9SE) XDA" then, go to the thread, below you will find GITHUB or any other download link, go there and you can download it from there.
4. (YOU CAN IGONORE THIS STEP, LET ME KNOW IF YOU FACED ANY PROBLEM, THOUGH YOU SHOULDN'T) rename the twrp file to twrp.img (not necessary though, check if your device extension is hidden or not, if hidden, you will not see any extension after any file, in that case, you can just rename "twrp" because img extention is already there and it's hidden. How to check hidden extention: in that folder, go to view at the top of the screen of that folder, (at beginning - beside cross, minimize then click "view"> click "option" in one row down, at extreme right side of it > click "view"> in downwards, untick "hide extensions for known file type"> click "apply">click "ok" then close it.)
5. keep the "twrp.img" (the file you downloaded, no need to rename, .img will show depending on unhidden condition) in the "platform tools" folder.
6. now go to "platform tools" folder. it's better to keep the folder in "desktop". go to the folder address, it is above the "Name, Date Modified, Type, Size" row, where it is written all the folders name that you have clicked to come to this folder. Now, click on the folder address, write "cmd", hit enter.
7. now connect your phone making sure "USB DEBUGGING IS STILL ON" because after unlocking bootloader, it will automatically be set to OFF.
write these commands: (after each command hit enter)
adb devices (it will show your device number if it is connected properly, if shows unauthorized, g0 to your phones home screen, disconnect and connect the usb again, in cmd write adb devices, a permission will pop up in your phone at bottom, not in notifications, click YES, your device will be authorized)
adb reboot bootloader (it will take you to fastboot mood instantly)
fastboot devices (it will show your device number it it is connected properly, to make sure it is still connected)
fastboot flash recovery (give space after recovery, then drag the twrp.img file here)
fastboot boot (give space after boot, then drag the twrp.img file here, your phone will boot into recovery.) ALTERNATIVE TO THIS STEP: fastboot reboot (it will reboot, but stop it instanlty by holding "power and volum up button", it is a must, it will take you to twrp manu, if you don't go now, later twrp will be removed by your phone)
AND OF COURSE, YOU HAVE TO ROOT YOUR PHONE RIGHT NOW, EVEN IF YOU DON'T WANT IT, CAUSE IF YOU DON'T, YOUR PHONE WILL REMOVE TWRP AS YOUR RECOVERY.
8. you will see twrp screen, then asking you "to keep system files as read only or swipe to allow modification, tick in DON'T SHOW AGAIN AND SWIPE TO ALLOW MODIFICATION". Then it will ask for a password to decrypt your phone, give the password to decrypt your phone. (to learn about encryption decryption, go to step number 4.3).
IF YOU FACE BOOTLOOP OR ANY OTHER ISSUE LIKE TWRP RECOVERY IS NOT STARTING AS IT SUPPOSED TO:
Again, go to fastboot mood by pressing power + volume down button. Download this vbmeta file. Go to platform tools > cmd > type
fastboot --disable-verity --disable-verification flash vbmeta (space, then drag the vbmeta file and hit enter, then follow step number 3.7
(3 is step number, 7 is the point number under step number 3)
Step Number 04: Install MagiskSTEPS:
1. you should stay in TWRP manu from the last step of STEP NUMBER 3 and your phone is connected with your computer via USB.
2. In your computer, download MAGISK FROM OFFICIAL GITHUB PAGE . Copy the magisk.apk and paste it twice in the same folder, now you have three magisk apk, rename the second one removing the "copy from name and just add .zip in stead of .apk at last. Rename the third one as this: "uninstaller.zip"
3. Now listen carefully, this is very important part of this topic:
your phone has two state: a. encrypted b. decrypted
a. IF ENCRYPTED AND CAN'T BE DECRYPTED THROUGH TWRP, that is TWRP IS NOT ASKING PASSWORD AT THE BEGINNING TO DECRYPT YOUR PHONE, THEN: some china rom's security is so encrypted, LIKE MY MI9SE, THAT TWRP CAN'T DECRYPT IT, EVERYTIME I HAVE TO RESET THE PHONE TO DECRYPT, IN THIS CASE ,YOU CAN'T ACCESS YOUR PHONE'S INTERNAL STORAGE NEITHER FROM TWRP NOR FROM PC (TWRP ACTS AS MTP, MEDIA TRANSFER PROTOCOL, MEANING YOU CAN TRANSFER FILE BETWEEN PHONE AND ANDROID IN RECOVERY MOOD), SO YOU CAN'T ACCESS YOUR INTERNAL STORAGE, YOU CAN'T INSTALL MAGISK. HERE, PENDRIVE WITH OTG COMES HANDY. Disconnect your phone Keep those three files in pendrive and connect it in OTG with your phone. go to twrp > install > select storage at bottom > select pendrive > select magisk.zip > swipe to flash. CONGRATULATIONS, YOUR PHONE IS ROOTED.
b. IF YOUR PHONE IS DECRYPTED BY TWRP AFTER GIVING PASSWORD:
Copy those three magisk file from your computer and drop it in your phones internal storage. go to twrp > install > select magisk.zip > swipe to flash. CONGRATULATIONS, YOUR PHONE IS ROOTED.
4. Reboot Your Phone (If your phone is bootlooped, which never happened to anyone I know, still for safety, again go to recovery by holding POWER + VOLUME UP BUTTON. go to twrp > install > select uninstaller.zip > swipe to flash. This will uninstall magisk from your phone and then reboot to system, your phone will reboot normally)
5. A Magisk app will be shown among your apps which is not like magisk logo. Don't touch it, Goto file manager, find those three magisk files, one file is the original magisk.apk file you downloaded, install it normally like any other app.
6. CONGRATULATIONS, YOUR PHONE IS COMPLETELY ROOTED.
Step Number 05: Backing up your PERSIST.IMG (MOST IMPORTANT)STEPS:
You will know from my other threads about what is persist partition of your phone. But let's just back it up now without knowing it. Copy it to your computer, cloud so that you never loose it.
Assuming you still have your phone connected through usb to the computer.
Install TERMUX from playstore or from HERE if you don't have play store.
in termux, type su to obtain root permission. A pop up will be shown to grant root permission, if it doesn't work, leave termux app, go to magisk app, at bottom, you will be 4 options, click the second one, you will see this screen.
grant super user permission for termux from here.
4. again go to termux, type this:
su (hit enter)
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img (hit enter)
5. your persist.img is backed up in your internal storage.
6. you can transfer it to pc manually or
use this process because it is relatively safe, though I never found any difference,
go to platform tools in cmd, type this:
adb pull /sdcard/persist.img D:\
it will take around 10 seconds, you will find the file persist.img in your PC's D drive folder, whatever the name is, the next folder to C drive, okay? Copy the persist.img wherever you want to keep it. I am again saying, it's not mandatory to do it in this way, just do normal copy paste from your phone's internal storage to your PC, it will do the work.
THANK YOU GUYS FOR READING IT ATTENTIVELY, FROM TOP TO BOTTOM, AND IF YOU DIDN'T, WHAT CAN I SAY. IT TOOK MORE THAN 30 DAYS TO ACQUIRE ALL THESE KNOWLEDGE AND YOU ARE GETTING IT WITHOUT ANY EFFORT, FREE, WHAT MORE DO YOU WANT?
My Other Threads according to "how should you read them" serial:
1. MIUI 12.5 Chinese ROM Google PlayStore Stopped Working
2. MIUI Unlocking Bootloader, Flashing Recovery & Rooting Process (This Thread)
3. Android Terminology You Must Know Before Toying with Your Android
4. ROM Naming & CUSTOM ROM, AOSP ROM, TREBLE ROM, GSI ROM, PORTED ROM
shafi1885 said:
First of All, these are my knowledge which was gained through hard reading from XDA Developers Forum, GitHub, reddit, different websites & watching YouTube Videos.DISCLAIMER: Here, I will explain all the process of unlocking Bootloader, Flashing Recovery & Rooting Your Xiaomi Phone, though the general idea is the same, so you can read it from TOP TO BOTTOM because you can use this knowledge FOR ANY ANDROID PHONE GENERALLY. Here, I also explained ALL THE PROBLEMS YOU MIGHT FACE WHILE DOING THIS, AND HOW TO GET OUT OF THOSE PROBLEMS, BECAUSE XDA THREADS AND YOUTUBE VIDEOS DOES NOT ANSWER YOUR PROBLEMS IN ONE THREAD OR IN ONE VIDEO, ONLY WHILE DOING IT, WE FIND THAT, DOING THESE WEREN'T SO EASY LIKE YOUTUBE VIDEOS OR XDA THREADS
AND OF COURSE, DO THESE ON YOUR OWN RISK, IF SOMETHING HAPPENS TO YOUR DEVICE AND YOU BLAME ME, I WILL LMAO AT YOU.
REQUIREMENTS: 1. PC/LAPTOP 2. PENDRIVE WITH OTG CABLE (FOR PRECAUTION, GO TO STEP 4.3 TO LEARN WHY)
Step Number 01: Backup All Your Data:
YOU HAVE BACKUP ALL YOUR DATA, INCLUDING APP DATA, GALLARY PHOTOS, ALL OF THEM BECUASE UNLOCKING BOOTLOADER WILL RESET EVERYTHING, IT WILL START FROM THE MOMENT WHEN YOU BOUGHT YOUR PHONE FIRST & SWITCHED IT ON.
STEPS:
To Backup All Your Data-
Go to settings "backup and restore" in additional setting (or in MY DEVICE - BACK UP & RESTORE) you can use either mobile or computer backup, both are same, after backing up, transfer it to computer.
Backup your contact from "contacts" (optional, because "step a" includes this)
Then connect your phone with your pc & backup all the necessary files, for example, create a backup of these folders:
DCIM
Download
Pictures
MIUI (Gallery, recorder etc.)
Shareit, vidmate folder
Whatsapp folder (you can also backup it in google, goto SETTINGS - CHATS - CHAT BACKUP)
and others as per your necessity
My process is a manual process, so no app is required.
READ IT: in internet, you will find that you can use rooted app to backup these, like TITANIUM, or take a NANDROID BACKUP (SYSTEM AND APPS) USING TWRP RECOVERY, my boy, listen well, you haven't yet unlocked your bootloader, how can you have a rooted device and twrp recovery? (well you can have a rooted device but that also requires unlocked bootloader which will reset everything on your phone)
Step Number 02: Unlock Your Bootloader
STEPS:
Enable developer option by clicking on MIUI version 7 times
from "Additional setting", go to "developer option". there, do these:
enable OEM UNLOCKING
in device unlocking, add your MI account. if shows problem or error, remove your MI account then add it again from device unlocking, (NOT FROM MY DEVICE, ADD ACCOUNT) then, it will take you to main settings, just come back and click add again, it will work in Sha Allah.
now in your pc, download MI Flash Unlock from official MI website, HERE (better to install the latest)
Unzip it, run it using "batch_unlock", add your mi account
in additional settings again, in developer option, enable "USB DEBUGGING"
now in pc, connect your phone in fastboot mood, (swithing off then holding power button and volume down will take you to fastboot mood, there is another process of going to fastboot mood, which is described in step 3)
if your device is recognized IN MIUI UNLOCK TOOL but after connecting it in miui unlock tool, fastboot mood turns of and says "PRESS ANY KEY TO SHUTDOWN" in your phone, you may try swithing to USB port 2 but it didn't work for me. Instead, I ran this bat file code "AS ADMINISTRATOR" from XDA developer forum, you can do it too. I renamed it as "a.bat" first thing to come it my mind. then disconnect USB and connect again in your fastboot mood. Click Refresh in unlock tool.
(OR, IF YOUR DEVICE IS NOT RECOGNIZED IN MIUI UNLOCK TOOL, FOLLOW THESE:
remove MI account from unlock tools and again add, if password shows error even after typing correctly, use phone number and pass to log in, in stead of email and password. Check if device if recognized or not.
If not, try these, Download MIUI Flash Tool and unzip it, run XiaoMiFlash.exe. At the top line, find DRIVER, install all DRIVERS.
IF YOU FACE LOG FILE ERROR,
SOLUTION: JUST CREATE A FOLDER NAMED "log" in the same directory. DONE, YOUR DRIVER WILL BE INSTALLED, CLICK YES EVERY TIME, THEN CONNECT YOUR PHONE WITH MIUI UNLOCK TOOL AND CLICK REFRESH.
your device will be shown in "batch_unlock" in sha Allah. Click unlock. Remember, your phone will loose all data, just full factory reset.
8. after 99% it will show "unlock sign" at the top of your phone, and your phone will reboot, just let it reboot. It will take at best 12 minutes to reboot. Don't worry, seat tight, watch a YouTube Video of Dr. Zakir Naik or Ahmed Deedat Sir <3.9. setup your phone as if it's a new device. (it is necessary, because after this, we will flash recovery and root your phone, because it is really important to take a backup of your original "PERSIST.IMG" . it is possible for rooted device only. (though it can be done through recovery, but from magisk, it's the best way and safest).10. you can restore all backup from your pc now. (not necessary, if you want to change ROM)
Step Number 03: Install ADB (PC) & TWRP RECOVERY (Android)STEPS:
download latest SDK from OFFICIAL WEBSITE.
2. name of the download will be "platform-tools_r31.0.2-windows.zip" unzip it in DESKTOP (IMPORTANT). it's name will be "platform-tools", open it. (ADB COMMAND WILL RUN ONLY IN THIS FOLDER.
ALTERNATIVE ADB: you can also do it by one click adb installer, just install the file, and cmd will work at any position. File is given in the telegram, in my .rar file. But sometimes it shows problem, adb command is not recognized by the windows. then, above platform tools folder is useful as it always works.
3. downlead latest TWRP specific for your device from HERE. website guide: >find your device name> device model> Download Links > click either "Primary (Americas)" or "Primary (Europe)" or you can download them from XDA too (XDA process: search in google "TWRP for MI 9 se (your specific device with model number, not Mi9SE) XDA" then, go to the thread, below you will find GITHUB or any other download link, go there and you can download it from there.
4. (YOU CAN IGONORE THIS STEP, LET ME KNOW IF YOU FACED ANY PROBLEM, THOUGH YOU SHOULDN'T) rename the twrp file to twrp.img (not necessary though, check if your device extension is hidden or not, if hidden, you will not see any extension after any file, in that case, you can just rename "twrp" because img extention is already there and it's hidden. How to check hidden extention: in that folder, go to view at the top of the screen of that folder, (at beginning - beside cross, minimize then click "view"> click "option" in one row down, at extreme right side of it > click "view"> in downwards, untick "hide extensions for known file type"> click "apply">click "ok" then close it.)
5. keep the "twrp.img" (the file you downloaded, no need to rename, .img will show depending on unhidden condition) in the "platform tools" folder.
6. now go to "platform tools" folder. it's better to keep the folder in "desktop". go to the folder address, it is above the "Name, Date Modified, Type, Size" row, where it is written all the folders name that you have clicked to come to this folder. Now, click on the folder address, write "cmd", hit enter.
7. now connect your phone making sure "USB DEBUGGING IS STILL ON" because after unlocking bootloader, it will automatically be set to OFF.
write these commands: (after each command hit enter)
adb devices (it will show your device number if it is connected properly, if shows unauthorized, g0 to your phones home screen, disconnect and connect the usb again, in cmd write adb devices, a permission will pop up in your phone at bottom, not in notifications, click YES, your device will be authorized)
adb reboot bootloader (it will take you to fastboot mood instantly)
fastboot devices (it will show your device number it it is connected properly, to make sure it is still connected)
fastboot flash recovery (give space after recovery, then drag the twrp.img file here)
fastboot boot (give space after boot, then drag the twrp.img file here, your phone will boot into recovery.) ALTERNATIVE TO THIS STEP: fastboot reboot (it will reboot, but stop it instanlty by holding "power and volum up button", it is a must, it will take you to twrp manu, if you don't go now, later twrp will be removed by your phone)
AND OF COURSE, YOU HAVE TO ROOT YOUR PHONE RIGHT NOW, EVEN IF YOU DON'T WANT IT, CAUSE IF YOU DON'T, YOUR PHONE WILL REMOVE TWRP AS YOUR RECOVERY.
8. you will see twrp screen, then asking you "to keep system files as read only or swipe to allow modification, tick in DON'T SHOW AGAIN AND SWIPE TO ALLOW MODIFICATION". Then it will ask for a password to decrypt your phone, give the password to decrypt your phone. (to learn about encryption decryption, go to step number 4.3).
IF YOU FACE BOOTLOOP OR ANY OTHER ISSUE LIKE TWRP RECOVERY IS NOT STARTING AS IT SUPPOSED TO:
Again, go to fastboot mood by pressing power + volume down button. Download this vbmeta file. Go to platform tools > cmd > type
fastboot --disable-verity --disable-verification flash vbmeta (space, then drag the vbmeta file and hit enter, then follow step number 3.7
(3 is step number, 7 is the point number under step number 3)
Step Number 04: Install MagiskSTEPS:
1. you should stay in TWRP manu from the last step of STEP NUMBER 3 and your phone is connected with your computer via USB.
2. In your computer, download MAGISK FROM OFFICIAL GITHUB PAGE . Copy the magisk.apk and paste it twice in the same folder, now you have three magisk apk, rename the second one removing the "copy from name and just add .zip in stead of .apk at last. Rename the third one as this: "uninstaller.zip"
3. Now listen carefully, this is very important part of this topic:
your phone has two state: a. encrypted b. decrypted
a. IF ENCRYPTED AND CAN'T BE DECRYPTED THROUGH TWRP, that is TWRP IS NOT ASKING PASSWORD AT THE BEGINNING TO DECRYPT YOUR PHONE, THEN: some china rom's security is so encrypted, LIKE MY MI9SE, THAT TWRP CAN'T DECRYPT IT, EVERYTIME I HAVE TO RESET THE PHONE TO DECRYPT, IN THIS CASE ,YOU CAN'T ACCESS YOUR PHONE'S INTERNAL STORAGE NEITHER FROM TWRP NOR FROM PC (TWRP ACTS AS MTP, MEDIA TRANSFER PROTOCOL, MEANING YOU CAN TRANSFER FILE BETWEEN PHONE AND ANDROID IN RECOVERY MOOD), SO YOU CAN'T ACCESS YOUR INTERNAL STORAGE, YOU CAN'T INSTALL MAGISK. HERE, PENDRIVE WITH OTG COMES HANDY. Disconnect your phone Keep those three files in pendrive and connect it in OTG with your phone. go to twrp > install > select storage at bottom > select pendrive > select magisk.zip > swipe to flash. CONGRATULATIONS, YOUR PHONE IS ROOTED.
b. IF YOUR PHONE IS DECRYPTED BY TWRP AFTER GIVING PASSWORD:
Copy those three magisk file from your computer and drop it in your phones internal storage. go to twrp > install > select magisk.zip > swipe to flash. CONGRATULATIONS, YOUR PHONE IS ROOTED.
4. Reboot Your Phone (If your phone is bootlooped, which never happened to anyone I know, still for safety, again go to recovery by holding POWER + VOLUME UP BUTTON. go to twrp > install > select uninstaller.zip > swipe to flash. This will uninstall magisk from your phone and then reboot to system, your phone will reboot normally)
5. A Magisk app will be shown among your apps which is not like magisk logo. Don't touch it, Goto file manager, find those three magisk files, one file is the original magisk.apk file you downloaded, install it normally like any other app.
6. CONGRATULATIONS, YOUR PHONE IS COMPLETELY ROOTED.
Step Number 05: Backing up your PERSIST.IMG (MOST IMPORTANT)STEPS:
You will know from my other threads about what is persist partition of your phone. But let's just back it up now without knowing it. Copy it to your computer, cloud so that you never loose it.
Assuming you still have your phone connected through usb to the computer.
Install TERMUX from playstore or from HERE if you don't have play store.
in termux, type su to obtain root permission. A pop up will be shown to grant root permission, if it doesn't work, leave termux app, go to magisk app, at bottom, you will be 4 options, click the second one, you will see this screen.
grant super user permission for termux from here.
4. again go to termux, type this:
su (hit enter)
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img (hit enter)
5. your persist.img is backed up in your internal storage.
6. you can transfer it to pc manually or
use this process because it is relatively safe, though I never found any difference,
go to platform tools in cmd, type this:
adb pull /sdcard/persist.img D:\
it will take around 10 seconds, you will find the file persist.img in your PC's D drive folder, whatever the name is, the next folder to C drive, okay? Copy the persist.img wherever you want to keep it. I am again saying, it's not mandatory to do it in this way, just do normal copy paste from your phone's internal storage to your PC, it will do the work.
THANK YOU GUYS FOR READING IT ATTENTIVELY, FROM TOP TO BOTTOM, AND IF YOU DIDN'T, WHAT CAN I SAY. IT TOOK MORE THAN 30 DAYS TO ACQUIRE ALL THESE KNOWLEDGE AND YOU ARE GETTING IT WITHOUT ANY EFFORT, FREE, WHAT MORE DO YOU WANT?
My Other Threads according to "how should you read them" serial:
1. MIUI 12.5 Chinese ROM Google PlayStore Stopped Working
2. MIUI Unlocking Bootloader, Flashing Recovery & Rooting Process (This Thread)
3. Android Terminology You Must Know Before Toying with Your Android
4. ROM Naming & CUSTOM ROM, AOSP ROM, TREBLE ROM, GSI ROM, PORTED ROM
Click to expand...
Click to collapse
I have redmi k40 bootloader locked and stuck on fastboot mode and can't unlock it through mi unlock tool so any solution for that problem beside edl ? And if I go with edl which flashing tool i will use ??
Hussein Gbr said:
I have redmi k40 bootloader locked and stuck on fastboot mode and can't unlock it through mi unlock tool so any solution for that problem beside edl ? And if I go with edl which flashing tool i will use ??
Click to expand...
Click to collapse
have you flashed any rom? or flashed anything? if you haven't, just restart your phn using power button. and if you have flashed anything already, how on earth you did it without unlocking your bootloader?
shafi1885 said:
have you flashed any rom? or flashed anything? if you haven't, just restart your phn using power button. and if you have flashed anything already, how on earth you did it without unlocking your bootloader?
Click to expand...
Click to collapse
My bootloader was unlocked but when i try to use mi flash tool by mistake or by default flash and lock bootloader option with there and the flash didnt go through in last second
Is there a way to unlock the phone if it only turns on in fastboot mode and is not associated with a xiaomi account?
Hello there, I would like to contribute to this tutorial if you agree
There is a way for people that have encrypted storage and no usb otg pendrive:
Step 4.3:
a-alternative. If encrypted, but no OTG Pendrive at your disposal:
You still can use the adb push command to send your Magisk folder into a decrypted part of your phone’s root folder. You are going to use your phone “/tmp” folder.
“/tmp” folder is suitable for temporary files just as our files (We will not need these files anymore after this tutorial). There is no risk to add files into this folder while it is not encrypted but do not delete any files already present into your /tmp folder!
1.Copy your Magisk folder containing your three Magisk files into the Plateform-tool folder:
2.Then in the cmd execute: adb push [replace_brackets_by_your_Magisk_folder_address_location] /tmp
3.Your Magisk folder should be now copied into your /tmp folder
4.twrp > install > select tmp/magisk.zip > swipe to flash. CONGRATULATIONS, YOUR PHONE IS ROOTED.
4.5-alternative. (This step only for those that processed through the “a-alternative” step) After rebooting your phone, you might have no chance to access the Magisk folder you’ve pushed earlier into the /tmp folder. However, now you have booted into your MIUI usual OS, you can copy the Magisk folder again into your internal storage using the classical drag and drop thanks to MTP protocol, to continue through this tutorial.
Hope this will help
Two years after my previous guide for Android 10, this is Niall's modernised guide to reconfiguring stock Samsung S10 Android 11 into a privacy focused MicroG based system purged of the stock spyware and annoying and useless stuff, but with the actually useful Samsung Apps such as Camera, and VoLTE remaining fully functional. Don't get me wrong here, LineageOS on the S10 is better in all ways especially in regular security updates, but the current LineageOS camera experience just can't compete with Samsung's deep integration of camera software and hardware. I therefore reluctantly offer this guide as a stopgap until LineageOS gets a better Samsung camera experience.
NOTE: The previous version of this guide for Samsung S10 Android 10 can be found at https://forum.xda-developers.com/t/...sed-privacy-reconfigure-step-by-step.4174691/. Before anyone asks, no I don't have a guide for Android 12, nor do I expect to make one for at least a year from now (I trail major Android releases, I don't lead them, it's too much work!)
After completing this guide, you will have only these apps left installed visibly in the launcher:
Aurora Services and Aurora Store (to replace Play Store)
Brave privacy web browser + Bromite privacy web view
Samsung Calendar
Samsung Camera
Samsung Clock
Samsung Contacts
F-Droid
Samsung Gallery
Magisk Manager (root, customisations etc)
Google Maps (retained only due to its great usefulness for public transport)
Samsung Messages (for text messages)
microG Settings
NextDNS to prevent even more personal data leakage (and optionally ads)
Samsung My Files
OsmAnd (for offline navigation)
Samsung Phone
Samsung Settings
Samsung Launcher and its Recent Apps switcher, as with a bit of reconfiguring it's not too bad actually.
Upon each boot you can choose whether you will have root via Magisk by booting your phone with the correct buttons pressed (Volume Up + Bixby + Power, but released after the boot screen). There is no need to run with root available, per boot, unless you want it. This makes my solution markedly superior in my opinion to the more popular Magisk + Zygisk + LSposed + FakeGapps MicroG approach which relies on injecting code into every app you run, which in turn requires you to always boot with root enabled. Personally speaking, I am also not comfortable with injecting code into my banking apps etc.
The principle things removed from stock are:
Samsung AR stuff
Samsung Bixby (apart from QR codes and Routines which are useful)
Google Chrome (it keeps hanging and stalling if used with MicroG, and besides it leaks your browsing habits)
Google GMail
Facebook (all traces)
Google YouTube (you ought to use NewPipe from F-Droid instead)
Samsung App store
Samsung Games home app
Microsoft OneDrive
Samsung Tips
Samsung DexOnPC (it spams you with messages)
Samsung EasySetup (also spams you with messages)
Samsung Edge Panel (the swipey translucent tab which floats above at the top right and gets in the way of taps)
Google Play Store
Google Accounts
Google Services
Note that this is NOT a deep "debloat", I only removed the bits you can see, which make themselves noticeable, or stuff known to leak your information to others. I left everything else alone, even if on most common "debloat" lists for the S10.
I also didn't remove ALL of the annoying popup notification Samsung stuff in this guide, unlike for my Android 10 guide. This is because removing all of it breaks the Samsung TouchWiz launcher which my Android 10 guide completely replaced. Besides, Android 11 is good at letting you suppress annoying notifications caused by things really wanting you to activate them e.g. "Find my Mobile", which requires a Samsung account.
This guide uses Nanodroid, which has a reputation for installing lots of stuff you don't want, which puts a lot of people off using it. As of recently, Nanodroid now offers small, single purpose, packages which you individually combine to get what you want. So no more random ringtones nor backdrops being installed that you don't want!
You should be warned that this conversion leaves your device insecure. OTA updates from Samsung self disable as soon as you modify any system image, so you'll need to manually go retrieve new firmwares and repeat the below instructions (obviously flashing HOME_CSC instead of CSC to not factory reset the device) to stay secure.
Privacy achieved limitations (so you know what we can't keep private)
As with any device with a mobile (cellular) connection, as soon as you see a mobile phone (cell) signal, your position is exposed as they can track you by IMEI. Outside the EU, your historical, and sometimes current, location data is routinely sold for money by your provider to commercial third parties. Within the EU, your mobile provider is not supposed to expose your location to anyone but law enforcement without your explicit permission, but some providers are still catching up with GDPR and still relying on implicit permission buried deep inside EULA text. In any case, as soon as you see a mobile phone tower with your phone you have declared your position, and only airplane mode prevents that. This is unavoidable no matter how you configure any device capable of interacting with mobile phone masts.
Google Maps obviously leaks your location and movements to Google as soon as you open it, so you should prefer to use OsmAnd for offline maps and navigation whenever possible. Equally only Google Maps can route over public transport, knows when buses will arrive etc, so that's why I've kept it. Use judiciously!
MicroG needs to register with Google for push notifications, otherwise stuff like WhatsApp doesn't work. MicroG leaks as little information about you as it can, but ultimately Google can see from where you register including if by wifi alone, and thus determine your coarse location. You may wish to consider a VPN if you wish to obscure your physical location.
As much as you may secure your phone, individual apps you install may leak a great deal about you. For example most apps for tracking ovulation and when you have sex sell your personally identifying data and when you do it to others for money. You personally may not install such apps, but if anyone enters your private information into any phone, then your information is leaked. That information is composed into commercial databases which record everything about everyone. Is this paranoid? Note I said commercial databases. Most western governments are prohibited from mass survellience, so they simply buy the data from private firms which aggregate everything there is to know electronically about you. Amongst the many companies providing such service are Experian (you can request a dump of what they know about you, prepare to be disgusted) and Palantir (legislation hasn't caught up with them yet).
Finally, even if you are always in airplane mode, and all your friends and loved ones are as aware of personal data leakage as you are, ultimately this is a losing fight. Every time a CCTV camera facial recognises you, every time a satellite tracks your car, it's all being aggregated into databases about everyone, and more importantly, whom everyone has relations with. Even the device-less person is recorded, studied, tracked, and inferred from by algorithms. There is only so much any of us can do.
Instructions
Preparation: go find APKs for the following:
Magisk Manager. Rename it to MagiskManager.apk.
You really ought to insert a micro sd card. It makes life vastly easier when wiping the device, and this guide assumes that you have inserted one.
Make sure your bootloader is unlocked and your device has been configured to accept unofficial binaries. You can find instructions for how to do this at https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root. You will need adb shell working with your device in Developer mode.
First install: In Odin, flash your choice of stock Android 11. Flash all parts, choosing CSC not HOME_CSC for the CSC slot in order to ensure a factory reset. Do NOT skip this complete reset to stock. Optional: Boot into stock firmware, enable wifi, and download and install any security updates available. Do NOT upgrade to One UI 4.0 or later (that is Android 12 or later, this guide is written for One UI 3.5/Android 11 only)
Upgrade: In Odin, flash your choice of stock Android 11. Flash all parts, choosing HOME_CSC not CSC for the CSC slot in order to prevent a factory reset. Do NOT let the device try to boot into the system, it will wipe your data!
You will need to reboot the downloader for the next step. Be aware that if you are upgrading and you mess this up even just once, all existing data will be wiped and you'll need to start again as if first install. With a USB cable connected to the computer, you need to hold volume Down, Bixby and Power to boot into Download. If it goes to screen dark and doesn't continue, try releasing Power.
Restart Odin, then flash AP slot with the TWRP TAR archive and the CP slot with the vbmeta.tar using images and instructions from https://forum.xda-developers.com/t/...-0-x-twrp-for-galaxy-s10-e-5g-exynos.4180287/.
Boot into TWRP recovery using Volume Up + Bixby + Power On by holding them down until the recovery starts. This can take multiple attempts. It may be useful to know, if stuck on the first boot Samsung logo (you don't need to worry about interrupting first boot right now), that holding volume down and power button for long enough will force reboot the device.
First install: In TWRP format data. Do NOT skip this part. This removes Samsung's encryption of the internal sdcard so you can take backups of your data etc in TWRP.
Upgrade: Do NOT format data, for obvious reasons.
In TWRP install the multidisabler zip available from https://forum.xda-developers.com/t/...-0-x-twrp-for-galaxy-s10-e-5g-exynos.4180287/.
Put into a file called .nanodroid-setup:
Code:
nanodroid_nlpbackend=1001
nanodroid_play=21
nanodroid_gsync=0
This custom .nanodroid-setup adds the install of the radiocells location backend (this uses a downloaded on-device database of mobile phone mast ids to locate you), and prevents the install of the Google Sync Adapters which prevents Google getting your contacts list and calendar.
In TWRP mount Product, System and Vendor.
Do the following from your PC with TWRP still running:
Code:
adb shell
rm /system_root/system/app/ARZone/ARZone.apk
rm /system_root/system/app/BixbyWakeup/BixbyWakeup.apk
rm /system_root/system/app/FBAppManager_NS/FBAppManager_NS.apk
rm /system_root/system/app/Facebook_stub/Facebook_stub.apk
rm /system_root/system/app/YouTube/YouTube.apk
rm /system_root/system/priv-app/Bixby/Bixby.apk
rm /system_root/system/priv-app/BixbyAgentStub/BixbyAgentStub.apk
rm /system_root/system/priv-app/BixbyService/BixbyService.apk
rm /system_root/system/priv-app/GalaxyAppsWidget_Phone_Dream/GalaxyAppsWidget_Phone_Dream.apk
rm /system_root/system/priv-app/GalaxyApps_OPEN/GalaxyApps_OPEN.apk
rm /system_root/system/priv-app/GameHome/GameHome.apk
rm /system_root/system/priv-app/FBInstaller_NS/FBInstaller_NS.apk
rm /system_root/system/priv-app/FBServices/FBServices.apk
rm /system_root/system/priv-app/EasySetup/EasySetup.apk
rm /system_root/system/priv-app/OneDrive_Samsung_v3/OneDrive_Samsung_v3.apk
rm /system_root/system/priv-app/Tips/Tips.apk # stupid Samsung Tips popups
rm /system_root/system/priv-app/DeXonPC/DeXonPC.apk
rm /system_root/system/priv-app/CocktailBarService_v3.2/CocktailBarService_v3.2.apk # Edge panel top right floats
rm /system_root/system/app/Chrome/Chrome.apk
rm /system_root/system/app/ChromeCustomizations/ChromeCustomizations.apk
rm /system_root/system/app/Gmail2/Gmail2.apk
rm /system_root/system/app/GoogleCalendarSyncAdapter/GoogleCalendarSyncAdapter.apk
rm /system_root/system/app/GoogleContactsSyncAdapter/GoogleContactsSyncAdapter.apk
rm /system_root/system/app/GoogleLocationHistory/GoogleLocationHistory.apk
rm /system_root/system/system_ext/priv-app/SetupWizard/SetupWizard.apk # Without removal never passes initial setup
# New annoying popping up stuff in Android 11
rm /system/priv-app/ConfigUpdater/ConfigUpdater.apk
rm /system/priv-app/KnoxPushManager/KnoxPushManager.apk
rm /system/priv-app/SamsungAccount/SamsungAccount.apk
rm /system/priv-app/SPPPushClient/SPPPushClient.apk
# Stuff replaced by MicroG
rm /system_root/system/priv-app/GmsCore/GmsCore.apk
rm /system_root/system/system_ext/priv-app/GoogleServicesFramework/GoogleServicesFramework.apk
rm /system_root/system/priv-app/Phonesky/Phonesky.apk
rm /system_root/system/priv-app/Velvet/Velvet.apk
exit
adb push .nanodroid-setup /sdcard/
All the removed apps free up enough space on the priv-app partition to install the Nanodroid apps coming next, so the above step isn't really avoidable. You also need to repeat it after any firmware upgrade.
(Incidentally, if you want to figure out what other apks to prevent being installed on first boot, once installed from adb shell do
Code:
pm list packages -f
and it will print all installed apks and the path from where they came. If that isn't enough to track a bloatware package down,
Code:
adb shell dumpsys package packages > all_package_info.txt
will give you a searchable text file of detailed information)
In TWRP install exactly these individual packages from https://gitlab.com/Nanolx/NanoDroid:
NanoDroid-BromiteWebView-23.1.2.20210117.zip
NanoDroid-fdroid-23.1.2.20210117.zip
NanoDroid-microG-23.1.2.20210117.zip
NanoDroid-OsmAnd-23.1.2.20210117.zip
(Later, but not earlier, versions will probably work fine too)
Try installing in TWRP NanoDroid-patcher-XXX.zip. If it works (the 23.1.2.20210117 version did not for me), great. If it doesn't, you'll need to manuall do the patching, see below for how to do that.
Reboot into System. It will get stuck on the Samsung boot logo for a while, but will eventually open onto either the enter Samsung account stage of setup, or the Setup All Done stage (we earlier removed all the earlier parts of setup). Hit Skip and/or Finish to reach the Launcher. Enable wifi and connect to your wifi connection.
Enable Developer Mode by entering Settings => About Phone => Software Information then tap the Build Number ten times. In Developer options, enable USB debugging and authorise your PC via USB cable.
If NanoDroid-patcher failed to work earlier, we need to do the patch by hand via root. Install MagiskManager.apk using
Code:
adb install MagiskManager.apk
. Extract the TWRP recovery.img from the TAR file and copy it to the sdcard, then open Magisk Manager with a wifi connection active. Choose install. Then choose Select and Patch file. Patch the TWRP img previously copied. Magisk Manager will output a root patched img into Downloads. Copy that back to the PC. Make a new TAR file of that. Flash that in Odin in the AP slot. Boot the device using Volume Up + Bixby + Power, but release as soon as the bootloader warning screen appears, so you boot into the system with root enabled. Go back into Magisk Manager, ensure Magisk appears as installed. If not, reboot and again try the key combination until it works. If in the future root ever appears to have got lost or isn't working, check the Magisk Manager, you probably forgot to hold the right keys during boot.
In Magisk Manager, choose the Modules tab, then Install from Storage. Copy in NanoDroid-patcher-23.1.2.20210117.zip to the device again. Let Magisk install it, it will appear to work, but in fact on your next reboot your device will never start again. Before that happens, copy the patched services.jar out to your PC:
Code:
adb shell
su # magisk will prompt to allow
cp /data/adb/modules/NanoDroid_Patcher/system/framework/* /sdcard/
exit
exit
adb pull /sdcard/org.spoofing.apk
Start again from the top of this guide i.e. reinstall stock, TWRP (but this time flash the rooted patched edition). Once into TWRP format data, mount Product, System and Vendor. Copy out the services.jar file to your PC:
Code:
adb pull /system_root/system/framework/services.jar
Get the Android 11 patch files from https://forum.xda-developers.com/t/signature-spoofing-on-unsuported-android-11-r-roms.4214143/ and execute:
Code:
java -jar dexpatcher-1.8.0-beta1.jar -a 11 -M -v -d -o ./ services.jar haystack-11-attempt\11-hook-services.jar.dex haystack-11-attempt\11core-services.jar.dex
Open the original services.jar in WinRAR and drag in the newly generated classes.dex, classes2.dex, classes3.dex, classes4.dex, replacing the three classes files in there. Your patched services.jar file will now be half the size, for some reason the original one was created without ZIP compression. It doesn't matter, adb push your patched files:
Code:
adb push services.jar /system_root/system/framework/
adb push org.spoofing.apk /system_root/system/framework/
Reboot into system, remembering holding down the keys to enable root for this boot, and reinstall Magisk Manager again.
Once back into the device, open the microG settings app. Run the Self-Check, the "System grants signature spoofing" will be unticked. Tap it, grant permission. The item "Play Store (Phonesky) has correct signature" will also be unticked. Tap that, grant permission. Now the self check should report everything is working and having correct signature. Signature spoofing should be working.
Within MicroG settings, enable Google device registration, cloud messaging and safety net. If you don't enable these, any applications you install next will never receive notifications, ever. Enter location modules. Enable Deja Vu, Radiocells and Nominatim backends. The Deja Vu backend doesn't need configuring, it simply records Wifi and mobile phone mast data and your GPS location when available, and builds a database matching wifi and mast data to GPS. Next tap the Radiocells entry, then Configure, then download offline catalog now, choose your country, then choose offline mode. Now your phone can locate itself purely using an offline database of phone masts and wifi. Next tap the Nominatum entry, then Configure, then choose Nominatum API server, and then OSM.
Open OsmAnd~ the app, choose your country, and download your offline map so you can navigate without an internet connection. Open the app, ensure navigation is working.
Enable and enter Developer options in the settings, open the WebView implementation, and set it to Bromite System WebView.
Go to https://nextdns.io/ and create yourself an account and unique id. From Aurora Store, find and install the NextDNS app. Configure the app with the id you got from your account on the website, and tell it to send your device's name. NextDNS acts as if a VPN for your Android device and thus all internet traffic routes through it, but it blackholes DNS lookup for a configurable list of items in your NextDNS account. Via this, you can block a long list of leakage of your personal information, and also optionally block ads on your device. If you log into nextdns.io from time to time, you will no doubt be fairly saddened by how much of your data is attempted to be leaked all the time.
From Aurora Store, find and install the Brave privacy web browser. As we removed Chrome due to it not working well with this modified system (it keeps stalling), you will need a new system web browser in any case and out of the box, Brave blocks all adverts and tracking. If you enter its settings, you can also disable Javascript by default (only enable it per site on a case by case basis, you can enable temporarily per site, or store an exception). Be aware that if you don't enable Brave rewards, the Brave authors silently pocket any BAT tokens your web browsing earns, so you may wish to enable Brave rewards for the very tiny income generated by your attention if you leave Brave ads disabled (it is local browser only, nothing gets enabled online, BAT tokens are conferred by crypto exchange so none of your browsing gets leaked). Personally speaking, I'm quite keen on the idea of me getting paid personally to see adverts as none of my personal browsing history leaves the Brave browser, even if it's pennies a month, so I leave that stuff turned on.
Brave defaults to regularly pinging you with Android notifications with Ads, which is very annoying, but deep inside the Brave settings you can specifically disable Ads notifications completely.
Settings
You probably want a decent set of settings rather than iterating through the Settings app. These are mine obviously, so you can skip these or not. With Developer Mode enabled, do the following:
Code:
adb shell
settings put global display_size_forced 1440,3040
settings put global navigationbar_key_order 1
settings put secure default_display_density_forced 560
settings put secure display_density_forced 560
settings put secure default_display_size_forced 1440,3040
settings put secure package_verifier_state 1
settings put secure screensaver_components
settings put secure selected_input_method_subtype 65538
settings put secure ui_night_mode 2
settings put system hdr_effect 1
settings put system display_night_theme_wallpaper 1
settings put system screen_off_timeout 300000
settings put system aod_servicebox_page_gravity 17
settings put system aod_show_state 1
settings put system aod_tap_to_show_mode 0
settings put system display_night_theme 1
settings put system hearing_diagnosis 1
settings put system hearing_direction 0
settings put system hearing_musiccheck 0
settings put system hearing_parameters 5,5,5,5,5,5,5,5,5,5,5,5
settings put system hearing_revision 0
settings put system hearing_videocheck 0
settings put system lock_clock_adaptive_colors 'fffaeecd;ffd9faeb;fffae7b4;ffc0fae0'
settings put system qs_detail_content_primary_text_color -2500135
settings put system qs_detail_content_secondary_text_color -1710619
settings put system remote_control 0
This is mainly how I like my settings. I want the actual resolution of my fancy device, not some subset (why bother buying a device with better otherwise?). I want dark theming to take advantage of power saving in my fancy AMOLED screen.
Swype keyboard
Enter Settings, General Management, Samsung Keyboard settings, and then Swipe, Keyboard swipe controls. Enable Swipe to type.
Firmware upgrades
To apply future firmware upgrades, you will need to acquire the latest Samsung firmware for your device from a reputable source. You almost certainly want to take a full backup in Titanium Backup, and copy that backup onto an external sd card to be safe. During flashing in Odin, flash the HOME_CSC, not the CSC, image into the CSC slot. This should preserve all your settings and installed applications. Disable auto rebooting in the Odin options. Then when the flash is done, manually reboot into Download, then repeat all the steps above.
If you do it right, you'll reboot into your device just as you left it, just with all the components upgraded to latest. If you screwed up, that Titanium Backup you made will be very useful.
Not that I'd recommend running out of date firmware images, but I would say that by far the most common upgrade you'll need to do is latest MicroG because Google bumped the minimum version of Play Services its apps will accept, so for example Google Maps will barf about Play Services being too old. There is a very simple fix for this: don't upgrade Google apps! An older Google Maps works just fine even if it's many months old.
Credits
What this guide achieves wouldn't have been possible without the following hard work from many people creating the components I have reused:
topjohnwu
ianmacd
Christopher Roy Bratusek
RandomAJL
mar-v-in
Whomever makes available Samsung Odin and the other stuff which makes LineageOS and AOSP become ever better for the S10 devices.
This is well written. I was familiar with most of this. I tried Lineage, but since VoLTE was not supported, I could not make or receive phone calls.
I got stuck on step 12. At that point, all the zip files were invalid. I was able to do steps 14 & 15, but gave up after 16. I could not install any apps as I had no microG or Aurora. I downloaded the files directly from NanoDroid Christopher Roy Bratusek. Any ideas what I did wrong?
The one difference is I am using an S10e, SM-G970F. I verified it is European, Exynos (I don't think I could have gotten to 12 if it was not). However, the two year ago thread said it should work with the e model.
I downloaded the files from NanoLx and got those installed. I cannot get root. I have tried the key combinations over and over again. I just get booted into TWRP recovery, no matter how soon I release the buttons. I have made many attempts.
It's because so far I cannot successfully Odin the magisk patched TWRP in the AP slot. It never shows any progress.
I patched the file 3 times, every time wi-fi was active. Different SHA256, but all same size. Not one would write in AP slot with Odin. I was able to flash AP with TWRP and CP with vbmeta, so I know how to do it. It will not write this file.
With great persistence, I was finally able to use Odin to write the patched AP file. Odin said success. However, I have tried hundreds of times to get the button combination, and nothing works. I have tried holding all three buttons (up, bixby, power), releasing power and holding up and bixby, and also only holding up. All of these I have tried various lengths of time. I was not able to get magisk root with Lineage, either. I believe I got root with SU, but the app was discontinued and not supported.
I have watched numerous tutorials on the button combination, most of them similar, and tried all of them. Counting the screens (most say 3, some 2), and many other times. Again, hundreds of iterations.
Does anyone have a reliable way of getting magisk root access? I am stuck in the middle of step 16. I restarted at the top with a complete factory reset (CSC, not HOME_CSC). Everything was smooth until the button combination.
Sorry to hear that you have found the going tough. I would say that the guide above hides how many times you need to repeat and rinse when you are writing the guide in the first place. The way I wrote the guide above is basically throw on a movie, one which doesn't require much attention, and in the background almost semi-automatically just keep rinse and repeating the guide until it succeeds. Very occasionally I pause the movie if I need to concentrate on something for a bit. The guide then is just a sequence of very frequently repeated steps.
You sure you are using Magisk to patch the TWRP image and not the system firmware image? The way root works on these devices is that Magisk is installed as a recovery firmware. When you boot with the recovery buttons, it runs Magisk. Magisk then counts down a timer, if the buttons are still held down it'll boot TWRP, otherwise it'll boot the main system with root enabled. If no buttons or the wrong buttons are pressed on boot, then neither Magisk nor TWRP ever get involved, the system boots without root.
Hopefully this makes sense. Also, given some of the Odin flash problems you've seen, I'd suggest trying a different USB cable. I've never found Odin will fail to work if the device is freshly booted into Downloader mode unless your USB cable is flaky. If you leave the device in Downloader mode for too long, it seems to time out. Also, it won't accept a second flash if it's already done a first flash without an intermediate reboot back into Downloader mode.
Hope this help.
I never did get it to work with this method. I did gain root access with
Tutorial : Root Galaxy S10 Series Android 12 One UI 4.1 Stock Firmware
Root Samsung Galaxy S10 Series Android 12, WITHOUT Ramdisk Root Samsung S10+ - S10 - S10e SM-G97xxx, Stock Rom Android 12 - UI 4.1 Latest Version (I tested G970FXXSGHWC2) (Without combination keys for active Magisk after normal restart –...
forum.xda-developers.com
After that, I eliminated google play and used microg with
Samsung Android 11 stock to no-Google MicroG based privacy reconfigure step by step
Two years after my previous guide for Android 10, this is Niall's modernised guide to reconfiguring stock Samsung S10 Android 11 into a privacy focused MicroG based system purged of the stock spyware and annoying and useless stuff, but with the...
forum.xda-developers.com
Thank you for your help.
The govt. in my state has been distributing free phones and tablets recently. But there is a catch, it's loaded with work policies. There is an app running 24/7 in background all the time. You cannot change the wallpaper, and they can snoop on your personal data anytime. And it's all because of KNOX!
Note that this guide requires root. It was possible without root but Android 13 has made it nearly impossible to do it to this point that it's easier to root it.
Prerequisites:
- Root access. This guide is to be followed after you reach the welcome screen. In case you didn't and you have set it up, then you'll have to flash stock firmware then flash patched boot.tar again because factory reset is disabled as part of the work policies.
- This guide assumes that you are on the latest firmware.
- Magisk APK and Termux APK already downloaded and stored in USB drive and it's connected or in SD card but not in internal storage.
Guide:If you are connected to the internet with mobile data (sim card) then continue. If you aren't then just go 2 steps to the wifi screen in the Android setup, put in your password and then immediately press the back button. If you wait then it will continue automatically. You only need to be connected if you didn't download the APKs before. If you did then it's not required to be connected to the internet!
1. At the welcome screen tap on "accessibility".
2. Toggle "Assistant menu".
3. Tap on the menu.
4. Swipe until you find the "menu settings" option and tap on it.
5. Keep pressing the back arrow on the top left until the main accessibility window shows up.
6. Tap on "recommended for you".
7. Tap on "go to modes and routines".
- If you downloaded the APKs as stated beforehand:
8. Create a new routine, set it to execute manually and select the files app.
9. Execute it and the files app will open, allow it to access files.
10. Tap on SD card and install Magisk APK first and then Termux APK and then open Termux when it prompts so.
- If you didn't do so:
11. Create a new routine and do the same as before but set it to open chrome.
12. Go to https://hyperio546.github.io/knox-bypass-samsung/.
13. Click on Termux and download the APK.
14. Click on Magisk and download the APK.
(If you are worried about the safety then check the markdown source, it's linked to their original GitHub repos.)
15. Install in the same order as specified in rule no. 10.
16. Open Termux and type
Code:
su
17. Grant it superuser access from the popup.
18. Type this command and press enter
Code:
pm uninstall -k –user 0 com.sec.enterprise.knox.cloudmdm.smdms
19. Type exit, and then type exit again.
20. Keep pressing back button in the bottom left until it gets to "Welcome!" again.
21. Setup your device like normal.
22. You have *your* device back!
Optional:
If you want to remove the assistant menu then just repeat step 4 and then toggle it off.
Thank You so Much for this Guide