How to root Obi Worldphone MV1 - Android Q&A, Help & Troubleshooting

First of all, Obi is a Chinese OEM. So the support for their products is very bad. Unlike renowned Chinese OEMs like Xiaomi and OnePlus. They never bother to release their kernel map. So most rooting apps won't work. Then they have implemented Bootloader lock, Signature Verification at boot, Secure Boot and A/B authentication and secure Ramdisk. All these are good from a security perspective. Would've been one of the most secure devices had they continued to support it by regularly patching security updates.
This was a bit of hit or miss on my part, I admit. But I'm proud and happy with the results. So let's get right to it. Follow the steps in the sequence otherwise can't guarantee whether it will work or not. There'll be video link posted. Showing the process or part of it at least. So you can use it for reference. I'm working on a custom ROM for this device as well. I'll also be porting a CWM/TWRP recovery for this device, unofficial as it's my personal project. The file lists and maps will also be uploaded for anyone who wants to help. This process also works on Obi Worldphone SF1.
Here's the video tutorial:
youtu.be/MmkaCb2C8wY
Step 1: Download Kingo ROOT 4.5.8 from the official website. Make sure your phone is charged. Close all apps running in the background using recents. This is done as the phone is very slow and underpowered. This is to help prevent it from crashing due to it's underwhelming performance.
Step 2: Click on One-Click Root in Kingo ROOT app. Wait for it. It'll be slow at 30% and 80%. Leave it as it is. Don't disturb and touch it. You'll see Rooted Successfully.
WAIT. DON'T START REJOICING NOW.
Step 3: Since the phone is Bootloader locked, what we have achieved here is a temporary root. The moment you reboot it, the root will be lost. If you want to make Payments, use apps which won't work on Root. You can leave the phone as it is. And root everytime you reboot. Following the same process. That way you'll always be able to retain that system intergrity and never lose your Bootloader locked status. The phone will be as secure as possible after a reboot. But in case, you want to keep the root after reboot and permanently root it. Follow the steps below.
Step 4: Since the Bootloader is locked, the SuperUser app can't be moved to /system/app directory. The temporary root won't allow such /system/ modifications. So to completely breach the system protection against rooting. We'll need BusyBox, Magisk Manager and XposedInstaller. Download from the official sources.
Step 5: Install BusyBox, Magisk Manager and XposedInstaller.
Step 6: Open BusyBox app and press Install. Wait for it to complete. You may notice that you were not asked to give it root/su permission. This is because of Temporary Root. It'll continue to grant all apps which require root permissions. So always be careful that you don't have harmful/malicious apps installed.
Step 7: Open XposedInstaller and install Xposed Framework. It'll reboot automatically. Once done, proceed.
Step 8: Now open Magisk Installer. There'll be two Install options one for Magisk and the other for Manager. If an update is available for the Magisk Manager from within the app, install it. It'll download to your Internal storage/Download/ directory. Install it directly or manually by going to that folder. Now install Magisk. You can choose to preserve AVB 2.0/dm-verity and force encryption if you still want to retain SafetyNet features. I'd recommend you to uncheck both else you may suddenly lose root access with no way to root it again. Hit next. In method, select Direct Install(recommended). Hit Let's go. Wait for it to complete. It'll download it from the internet then flash it. In case, you encounter, Signature Verification failed, reinstall XposedInstaller and retry.
Step 9: Will all that done, if you're greeted with Installed in Magisk. Then reboot your phone.
Step 10: Make Magisk Manager using Lucky Patcher as System App. It'll automatically do it for you. Otherwise you can use RootExplorer/ES File Explorer(first turn on Root Explorer and grant SU permission to ES File Explorer; yes this time due to successful install of Magisk it'll show a toast for 10 sec. to ask for root permissions) then go to system/app/MagiskManager (create this folder) then drag and drop the apk. Rename the apk to MagiskManager.apk and set permissions as rw_r__r__ using properties of either explorer. Then uninstall the app. Then reboot. You may need to repeat step 8 after re-rooting using Kingo ROOT app.
Step 10: After all this is done, just uninstall Kingo ROOT or leave it(In case, you choose to preserve the AVB2.0/dm-verity and force encryption, as you'll suddenly lose the root some day randomly). And you're done.
Things to keep in mind: In case, Root Unsuccessful using Kingo ROOT app. It'll ask to try using the PC Version. There's no need for it. The PC version won't work and no other ADB or Fastboot method work to unlock the bootloader of this device. Just go to app info and clear data. Then try again. This should fix the issue. You must have developer tools unlocked and ADB Debugging turned on. OEM Unlocking should be turned on as well.

Related

[TUTORIAL] Rooting LG Optimus L9 with CHINESE method + restoring normal SuperSU

Due to lack of tutorials which contained CLEARLY written instructions on how to root LG Optimus L9 with Chinese method, I decided to write my own in which I'll explain everything step-by-step.
I also found (as I think) a 100% working way to restore normal SuperSU and delete the Chinese one, after resarching on it for about 5 hours.
WARNING: USE INFORMATION AND FILES AT YOUR OWN RISK. You follow this tutorial and use method described here at your own risk.
Step 1: Download and install LG drivers.
Because of the post limit I cannot post direct link to download, but they can be found here, in step 3): CLICK
Step 2: Download and install Chinese root.
a) Download this file: www--mgyun.com/vroot (replace -- with a dot .)
b) Install the software, using the installation buttons as you would on any other windows installation.
c) Connect your phone to your PC with ENABLED USB debugging and select "LG Software" as connection option.
d) Start the program, you will see a green button, press it.
e) When the phone is connected the software will recognise the phone and the green button will show "ROOT", click on it.
f) The phone is going to be rooted in some seconds and the process is finished when it will show a tick on the software.
g) The phone will reboot.
Tutorial taken from this topic: http://forum.xda-developers.com/showthread.php?t=2439667
Credits for it to aristide1997​
Step 3: Download SuperSU application from Google Store.
Step 4: Launch SuperSU application.
a) It'll ask you to install SU binaries. Select NORMAL if you don't have TWRP/CWM installed.
b) A Chinese Superuser prompt will show up, asking if you want to grant SuperSU su privileges. Click the button on the right. Square should be checked.
c) If you followed previous steps correctly, SuperSU should install binaries without problems.
WARNING: It'll ask you if you want to uninstall other applications that are managing Superuser right but DON'T DO IT. If you uninstalled the Chinese Superuser, and now SuperSU doesn't work, go to Step 8.
If you encounter problems (Binaries couldn't be installed):
a) Make sure you have a strange Chinese application in your Application Drawer. It's icon is a shield with a gear inside. If not, go to Step 2 and repeat.
b) Make sure you've clicked button on the RIGHT with SQUARE CHECKED when Chinese Superuser prompt showed.​
Step 5: Exit SuperSU application, reboot the phone.
Step 6: After reboot, launch SuperSU application. If there is no prompt saying that SU binaries must be installed and everything is normal, go to Step 7.
Step 7: Download Root Checker from Google Store and launch it.
a) Check for Root Status in Root Checker.
b) If there is a prompt from SuperSU, asking if you want to give Root Checker su privileges, confirm it and you're good to go. You can uninstall Chinese root.
c) If there is a prompt from CHINESE SUPERUSER, asking if you want to give Root Checker su privileges, just click back (don't confirm or deny). It means there is a problem. Go to Step 8.​
Step 8 (TROUBLESHOOTING):
If you uninstalled Chinese Superuser and now SuperSU doesn't have root rights, go to a); otherwise go to b)
a) If you uninstalled Chinese Superuser and SuperSU doesn't work (saying that binaries installation failed), don't worry. Connect your phone to your PC with USB Debugging ENABLED and start Chinese Root Program again. It should find your device automatically and restore the Chinese Root. Go to Step 4 and repeat.
b) If there is a prompt from CHINESE SUPERUSER to give su rights to applications, instead of SuperSU it means that SuperSU didn't become the main Superuser application and Chinese Superuser still is managing su rights. It can be fixed though.
c) Go to Google Store and download Superuser by ChainsDD (NOT SuperSU. The application you need is named Superuser).
d) Launch it and scroll left. Click on "SU Binaries" with green text in it, under "Elite version is not installed".
e) You should see a console. There should be a red text in it, at the end about "myung" su binaries.
f) Click "Update" button.
g) A prompt will show up, if it's in Chinese click the button on the right to grant Superuser su privileges.
h) New SU binaries will be installed, making Superuser new default application to manage su rights.
i) You can now uninstall Chinese Superuser and install SuperSU or stay with Superuser.​
ok so I'm completely new to all of this ROOT/Flash business... can someone tell me the easiest way to put android 4.4 on my LGMS76910e? or do I need to flash v20h first in order to move forward to get KitKat? My phone is already rooted right now. I used the chinese program and then installed SuperSu gave SuperSu Su permissions and made it a system app.... once I did that I rebooted into CWM v6.x(cant remember the whole thing) and tried to flash BobZhome's CM 11 android 4.4 for LG L9 but my phone said it couldn't be completed because my phone was a p940(I think).... so then I restarted the whole process....but haven't tried to flash BZ's stuff again.... What should I do? someone help me please!!
@halomastah09 you got very lucky that bobz set his CM11 to run on the 769's only, and when you flashed to v20h it changed your model# qand wouldn't allow you to install his rom. If it would've finished flashing you would've bricked your phone. Before you flash any custom roms to this phone you have to first unlock the bootloader.
My phone is LG MS76910e
my phone is recognized as LG P765 optimus L9. But it is a optimus L9 LG MS76910e model P769.
Does anything get screwed up if I root it?

How to root any phone using kingroot and replace it with super SU!

How to use KingRoot to root any Android Device
Key Points to Remember
HTML:
If KingRoot finds Sony_RIC is enabled and system can't be mounted, then you need to unroot the device first. Then you can re-root it and disable RIC automatically.
Those who have already installed KingUser on their device, need to install KingUser 4.0.5 fix, before uninstalling the same. Only after uninstalling the KingUser app, you will be able to re-root the device using KingRoot tool.
In case you face issues while removing KingUser, try force stopping KingUser, perform wipe cache data and then root with KingRoot again.
There are two versions of the KingRoot tool: Mobile and desktop.
•I m not responsible for any damage to you're phone.: D
Step 1: On your Android Device, Open Settings > Security > Device Administration > Unknown Source (tick to enable it).
xD
Step 2: Download and install KingRoot APK on your Android Device.
Step 3: Once Installation is completed, you will be able to see the following icon in the Launcher
Step 4: Tap on the KingRoot Icon to Open it. Once KingRoot Application is launched you will be able to see the following screen:
Step 5: Now, Tap on the Start Root Button to begin the root process.
Step 6: Now, KingRoot will start the rooting process.
Step 7: Within a minute or two you will be able to see the Big Green Tick, which signifies that your device is rooted successfully.
Step 8: Restart your Android Device.
Now to replaced kinguser with superSU
Caution: It seems SuperSU-Me App isnt working any more on latest Android Devices. I arent recommending you to try the tutorial on latest Android devices, as it may cause bootloop. If you still want to use, then use it at your own risk.
Remove or Replace KingUser with SuperSU
Step 1: Download Free Version or Download Pro Version of SuperSu-Me Application on you android device.
Step 2: Once, SuperSu-Me Application is installed on your device Open It.
Step 3: Once, SuperSU-Me application is launched, it will ask for the root Permission. Tap on the Allow button to continue.
Step 4: Once SuperSu-Me is fully launched, you will be able to see the following screen:
Step 5: Now, Tap on the Blue Android Button to begin the replacing process (replacing process may take 30-50 seconds to finish).
Step 6: Once replacing process is completed, SuperSU application will launched automatically.
Step 7: Now, you will notice that KingRoot, KingUser and other Chinese application is deleted from the application launcher and SuperSU is installed.
Optional: You can also verify that SuperSU is working correctly or not using any Root Checker Application.

ZTE Maven Z812--permanent rooted terminal and read-only system root (no kingoroot)

my method here will give you a permanent rooted shell and will give you read-only system root which is useful for using root apps to backup data or freeze system apps--works just like real root without being able to delete system contents--freezing apps however works like a charm and should reduce the need for rw root anyway
FOLLOW DIRECTIONS EXACTLY--I WILL NOT RESPOND TO STUPID QUESTIONS--PROBABLY WON'T RESPOND TO ANY QUESTIONS BECAUSE MY DIRECTIONS ARE PERFECT, WORK PERFECTLY WHEN FOLLOWED, AND ARE EASY TO READ. FOLLOW ALL STEPS EXACTLY. IF IT DIDN'T WORK, IT IS BECAUSE OF YOUR ERROR
This works best from a factory reset device, but will work from a already used device but all other root apps and superuser apps must have their data deleted and be uninstalled first
1) make sure device is at least 50% charged--doesn't matter most of the time; better safe than sorry
install latest superuser apk
http://www.mediafire.com/file/dx854fsys5pvxjh/SuperSU.apk
install dirty cow root apk (croowt) [comes from this post https://forum.xda-developers.com/android/software-hacking/root-tool-dirtycow-apk-adb-t3525120
http://www.mediafire.com/file/1hbey829hc7676a/CRooWt.apk
make sure usb debugging is activated in developer settings and make sure you have accepted the debugging access prompt on the phone for the computer you will use
make sure you have an external sdcard installed--the smaller the better for this first time
2) open dirty cow root apk
choose "get root"
choose "method 1"
hit "ok"
choose "ok"
app will direct you to unmount and remount sdcard, choose "ok" and it will take you to storage settings
unmount sdcard
remount sdcard
when finished proceed to step 3
3) open superuser
do not update su binary
go to settings and make the default action "grant"
remove any and all apps from superuser log including the croowt app
3) THIS MUST BE DONE FROM A REAL TERMINAL ON A PC--TERMINAL EMULATORS WILL NOT WORK FOR THIS STEP
from a working pc with adb setup, preferrably linux, input commands exactly as listed
adb shell
su
setprop persist.sys.k P816A06
reboot
5) once rebooted, open dirty cow root apk again
choose get root
choose "method 2"
hit "ok"
choose "ok"
if app asks you to open with a browser, choose one, and choose "always"
screen will go black, systemui will crash and then reboot
6) once systemui is back up and running
you now have read-only root
you can now freeze system apps or backup your data using apps that require root
Your shell will be permanently rooted when accessed from a computer using adb--this will last forever unless you undo the setprop
Your system however will only be temp, read-only rooted until the phone is rebooted.
If you wish to have your temp, read-only root reactivated, all you have to do is repeat step 5 and that is it.
You can do this over and over again.
GIVE STAYBOOGY SOME PROPS FOR MAKING YOUR LIFE WITH THIS PHONE BETTER
Does this only work to back up or freeze applications?
poseidon207 said:
Does this only work to back up or freeze applications?
Click to expand...
Click to collapse
ACTUALLY READ the first sentence of OP
I don't see how freezing system apps would negate the need for a real root method? Is this "Read-Only" root method working with lucky patcher or Kernel Auditor?
Can this be used to bypass the subscription check for tethering? I assume not since system isn't writeable.
Does this method work in the ZTE Maven 3 (Z835)?
I'm doing it wrong, probably
First of all, thank you so much for doing this. I've been following that other thread since it was new, and you've put far more effort into this than the phone or most of us deserve.
I've gotten stuck trying to run Dirty Cow. I have USB Debugging enabled, adb installed on my Linux computer which recognizes my Maven (i.e. I've allowed access on the phone), etc. It eventually goes from "Checking vulnerability" to "Your device is not vulnerable" and I'm unable to proceed to the "Get root" step. What am I doing wrong? Might be some recent system update? Probably less effort to just buy a Galaxy.
Please be gentle. I know I'm a noob.
z812 root
I previously rooted my maven with kingroot and the dirtycow exploit.sh file and today I was overwhelming the device by running multible windows and apps and the phone rebooted and root was still intact....haven't rebooted it again yet but I shall.

Need help to fix Supersu's prompting window after replacing Kingroot/kinguser with it

I don't know whereto put this thread although ths seems like a right forum,anyway, I have a problem with this persistent king root, and I want to remove it but these chinese 'communist' devs won't let me. I tried the following things:
1 Manually delete kinguser app from /system/app part, and then install supersu from play store. The result it just says what su binary is occupied.
2. Install BusyBox. Download this popular replace_kinguser_with_supersu_2.4.zip and 2.0 files (this ones with mrw folder) and run it. Supersu installs, asks for update and su binary update. Yes, yes, looks great, but doesn't work. When running any root app, like terminal emulator, nothing happens, no auth prompt pops up.
3. Reroot with older kingroot version (4.5), do the same as 2. Same result
4. Set auth mode in Supersu settings to allow/deny, when oddly it works. Allows or denies immediately, and I can find this in Supersu's log.
So, everything seems working fine except what Supersu doesn't want to show me my root promts when I need them.
If any information about my device needed, I will be happy to provide it. For starters, my device is ITELL K3300, I am not sure what else coud be needed if you want to help?

Samsung S10 - How to take your privacy back with NanoDroid (MicroG) and AFWall

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?

Categories

Resources