Samsung S10 - How to take your privacy back with NanoDroid (MicroG) and AFWall - Samsung Galaxy S10 Guides, News, & Discussion

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?

Related

MetroPCS & T-Mobile LG Leon STABLE Root (WORKS EVERY TIME 100%)

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?

[TUTORIAL] [Magisk] Root Android Wear 6.0.1 [squashfs compatible]

Root your LG G Watch (W100) with Magisk!
Things You Will Need
Magisk-vXX.zip from this thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
TWRP with squashfs support from here (Credits to: Xmaster24): http://www.mediafire.com/download/apwtscp0tn0y8qd/twrp-3.0.0-0-dory+squashfs.img
My custom ZIP file that flashes Magisk manager v4.3.1 apk & local.prop file: https://mega.nz/#!QvphGIbS!LIFsKzN5RxBRvMuwFGNGCa56XruMqut92tjfDO82RDE
Things You Will Need If You Mess up
Magisk-uninstall-XX.zip from this thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
TWRP with squashfs support from here (Credits to: Xmaster24): http://www.mediafire.com/download/apwtscp0tn0y8qd/twrp-3.0.0-0-dory+squashfs.img
Default boot.img if magisk-uninstall-XX.zip doesn't work: https://mega.nz/#!rxQ1EIDI!0ytWk965bt5KqSBuhMT4vbgD3dxO_qRyiN0LeAV4MrI
Guide
Step 1. (If your bootloader is already unlocked skip to Step 3.) Enable Developer Options On Watch: Settings->About->Tap Build number 7 times->Settings->Developer Options->ADB Debugging->Enable It
Step 2. Plug watch into cradle and usb plug into PC, make sure you have adb and fastboot
Step 3. run
Code:
adb reboot bootloader
watch may ask to allow debugging from this PC either allow or always allow.
Step 4. Once in the bootloader run
Code:
fastboot boot "twrp-3.0.0-0-dory+squashfs.img"
Step 5. run
Code:
adb push Magisk-vXX.zip /sdcard/
and
Code:
adb push dory-localprop-and-magisk-manager.zip /sdcard/
Step 6. In TWRP click Install-> Install ZIP -> Scroll Down -> Select Magisk-vXX.zip -> Tick button -> Swipe to flash -> When finished click the back key ->
Step 7. Install ZIP -> Select dory-localprop-and-magisk-manager.zip -> Tick button -> Swipe to Flash
Step 8. Reboot System button -> Swipe to confirm don't worry abot no OS error.
Step 9. Open Magisk Manager App -> Click Hamburger Menu (three lines) -> Scroll Down to Settings (Labelled Setti on small screen) -> Click it
Step 10. Scroll Down -> Enable Magisk Hide
Tip
Scroll Down in Magisk Manager settings and change "Automatic Response" to "grant" whenever you want to use root and "deny" when you don't. This is because the prompt window is designed for phones and is too big.
Guide for If you messed up or want to unroot
Step 1. run
Code:
adb reboot bootloader
Step 2. once bootloader is there run
Code:
fastboot boot "twrp-3.0.0-0-dory+squashfs.img"
Step 3. once booted into TWRP
Code:
adb push magisk-uninstall-XX.zip /sdcard/magisk-uninstaller.zip
Step 4 Go to install
Step 5. Install ZIP -> Scroll Down -> Select magisk-uninstaller.zip -> Tick button -> Swipe to flash
Step 6. Want to be rooted? Follow Original Guide from Step 6, if not follow Step 7 and onward
Step 7. While still in recovery run
Code:
adb shell "rm /data/local.prop"
Step 8. run
Code:
adb reboot
Step 9. Once back into the system run
Code:
adb uninstall com.topjohnwu.magisk
Step 10. Done.
Hahha this is what I love about this! You can do it because you can.
I'll dig up my G Watch and unlock the bootloader.
Why should I root my watch?
Theking3737 said:
Why should I root my watch?
Click to expand...
Click to collapse
There's no reason really, I just managed to get magisk to work on an android wear device as a proof of concept and wanted to share it.
Theking3737 said:
Why should I root my watch?
Click to expand...
Click to collapse
adjust kernel settings with kernel aduitor?
Nice, I thought about doing this myself but unfortunately my g watch met an untimely demise, I still update SuperSU tho since I know that works fine and didn't need to test it first. Good to see someone is still keeping this watch alive!
BTW this method should work on all watches, SuperSU does anyway.
i got it rooted well it sasy tis is but i want to change the bootanimation to match my PN one i have the file pushed to the watch but i cant put it in the /system/mesia location it says its read-only. can you help me with that thanks
Would this work on a other android wear watch? Like Sony smartwatch 3? Or is it trial and error?
Help me please . I'm a user from China and now my watch doesn't work anymore. The thing is, I didn't use it for a couple of months, now it just can't charge. When I Link it to my computer,the gwatch recovery tool can't find my devices. what should I do . Plz
Hey the op should be updated to say use magisk v12 as magisk 13+ requires manager 5+ to work
This also works on ZenWatch2 running latest AW2 update
Does this mean we can also use Magisk to change system-level things, such as boot animation?
Will this work on the LG Watch Urbane 2nd Edition LTE (W200A) and does android pay work with Magisk installed?
Post removed
Thanks @TheDevFreak.
It still works. I tried with Latest Magisk Version v15.3 & APK - 5.5.5.
Note: In the app, you have to set Automatic response to Grant under Settings. Because Root Access dialog not showing properly to click Grant button.
svprm said:
Thanks @TheDevFreak.
It still works. I tried with Latest Magisk Version v15.3 & APK - 5.5.5.
Note: In the app, you have to set Automatic response to Grant under Settings. Because Root Access dialog not showing properly to click Grant button.
Click to expand...
Click to collapse
The note you noted has been in the OP since I made it
Here's a tip if you can't reach the settings menu of magisk: Activate the zooming option in the system setting. On my TicWatch I have to tap three times and it will zoom to the tapped area. By that I was able to reach the settings menu.
Does this also works on Magisk 17?
Theking3737 said:
Why should I root my watch?
Click to expand...
Click to collapse
So you can extract the watch faces and share them with us
Hello,
The mega link for Magisk manager v4.3.1 apk & local.prop does not work anymore
Would someone have another link ?
Thanks

Rebrand-Update-Tool-HWOTA7-P9-PLUS-VIE

Rebrand-Update-Tool HWOTA7 for Huawei P9-Plus-VIE ​
The classic HWOTA Tool is available for all newer Huawei models. Now it is also available for the P9-PLUS-VIE
→ It is programmed for use with Android 7 (Nougat) and does not work on Android 8 (Oreo) - with the exception of the Update to Oreo.
Don't use this Tool to update your phone from Android 6 to Android 7 or Android 8.
You must already have Android 7 on your phone.!
Update to Oreo from Nougat is possible, but once you're on Oreo, the tool can not be used again until downgraded to nougat.
→ The same Tool for P9-EVA is different: https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
Features of HWOTA7 for P9 Plus VIE:
Update your Firmware with FullOTA-MF Firmware (3 zip files, two renamed) = Using the script /1. Change firmware
Rebrand between L09-L29-AL10 (your hardware does not change on VIE) = Using the script /2. Change location
Debrand from Vodafone, Telekom or other to: open cust ( current: 5 oeminfo files)
Note: If your Phone has SIM Lock, Debranding does not unlock mobile network - you can do that with HCU Client by DC Unlocker
The best feature is: You can update the P9-Plus-VIE to the official Android 8 (Oreo) unofficially with HWOTA7. This requires a rebranding of your device to VIE-AL10. How to manage this is explained in Post #2: https://forum.xda-developers.com/showpost.php?p=77650678&postcount=2
→ How to get back to the original model from Oreo is explained in Post # 4: https://forum.xda-developers.com/showpost.php?p=77650687&postcount=4
Note: To return to the original model related oeminfo is required - should your oeminfo not be included in the HWOTA7 tool, make a backup of the oeminfo with TWRP before Rebranding. If you give it to me, I can integrate it into the tool.
Requirements:
Bootloader Unlock code → if you do not have it, it can be read out with HCU Client by DC Unlocker
Developer Options enabled → OEM Unlock + ADB Debugging in charging only mode + USB Debugging (in this order) enabled
HiSuite HDB in Settings on the phone disabled, HiSuite on PC closed
Working USB Connection (drivers) between P9 Plus and PC (MTP, ADB and Fastboot → Allow access to the phone, accept RSA key fingerprint)
Windows 7, 8.1, 10 (the tool does not work on Mac or Linux or on Virtual machine)
Battery should be charged
Backup your important data (folders from internal storage such as WhatsApp, DCIM, downloads, music, etc. - as well as user apps with data, contacts, calendars, sms, etc.) → The internal storage is erased several times during this process.
Follow the instructions
How HWOTA7 works and what to keep in mind:
Download HWOTA7, extract it on PC and place HWOTA7 on: C:\HWOTA7 - without subfolders between.
Do not change the folder structure. The tool has two working folders:
→ C:\HWOTA7\tools\Windows - you can use: cmd-here.exe (run as Administrator) to check ADB/Fastboot or to flash an image later
→ C:\HWOTA7\update - this is the main working folder. You have to copy in this folder the FullOTA-MF firmware (3 zip files, two renamed)
If you are on custom ROM, first go back to Stock Firmware ("Using script" and "Change firmware" - use the Firmware that matches your device and cust)
HWOTA7 is self-explanatory. It detects what to do and prompts you to press certain key combinations or enter the unlock code.
→ The USB cable between the phone and PC remains connected throughout the process!
→ Only press "Enter" in the terminal if the described step, in the line before, was executed.
→ If you face an error like: "adb: error: connect failed: no devices/emulators found" - close Terminal, reboot phone into Fastboot mode and restart HWOTA7
The HWOTA7 tool is started by double clicking on "update_eng.bat"
The phone is connected to the PC via USB and you start with the key combination: VOL- and Power Button key into Fastboot mode.
When the Bootloader is locked, the tool unlocks the Bootloader with the code. Thereafter, a factory reset is performed by clearing the internal storage = Lowlevel Wipe.
When the Bootloader is open, the tool automatically flashes TWRP and prompts you to press (and hold) VOL+ and Power Button to start into TWRP.
Then you click 2x in the terminal on "Enter"
→ Before you choose: 2. Using the script and 1. Change firmware or 2. Change location - make sure, the FullOTA-MF Firmware is already in the update folder: C:\HWOTA7\update - and two zip files are renamed!
Rename the two zip files of the FullOTA-MF firmware → incorrect renaming such as "update_all_hw.zip.zip" does not work
update.zip = update.zip (do not rename)
update_full_VIE-AL10_all_cn.zip -rename to: update_all_hw.zip
update_data_full_public.zip - rename to: update_data_public.zip
Important - The difference between four different situations:
1) When the Bootloader is closed, HWOTA7 opens it with the code, a "lowlevel" factory reset is performed and the device must then boot into the system. In the setup everything can be skipped (which is possible) - but the developer options must be switched on (1.ADB Debugging + 2.USB Debugging enabled). And HiSuite HDB disabled.
2) If you select "Change firmware" to flash the firmware, the tool copies the ZIP files to the phone in the /data directory, flashes the Nocheck recovery, and installs the firmware. In this case, you also need to boot into the system and check if Developer options with the required settings are enabled.
3) But if you do the step: "Change location" - it is different! The tool will flash the corresponding "oeminfo", close the Bootloader and request the Unlock code to unlock the device and force a "lowlevel" factory reset → In this case (only), you should NOT boot into the system after the reset. Wait until the EMUI recovery is 100% done with the reset. Then comes the message "Reset succesful, device will restart" Now press (only) the VOL+ button and keep it pressed so that the device starts into TWRP. Now click on "Enter" in the terminal. HWOTA7 now copies the firmware to the device, flashes the Nocheck recovery, reboots and flashes the firmware belonging to the "oeminfo". After this step, the device must be booted into the system.
4) If the device boots into the system and you have a black screen, with an input field in the middle and possibly the keyboard (do not get worried) - the Bootloader was locked by the firmware during rebranding. In this case, press the Power Button to restart and hold down the VOL- button during the restart to start the device into Fastboot mode. Close the Terminal Script and restart update_eng.bat. Click on "Enter" in the Terminal and HWOTA7 will ask you for the Unlock Code and unlock again the Bootloader. Confirm the unlock on the device with the keys, then there is a factory reset followed by a reboot into the system. Now everything is fine.
Where can I get the firmware I need?
Note: The firmware must match your device and your "cust" - if you want to update, or coming back from a Custom ROM to Stock firmware - If you do a "rebranding", the firmware must match the "oeminfo" that you "rebrand"
Install "Firmware Finder" from the Playstore
In Settings (3 dot menu/settings) change to "Show only FullOTA" In main window "Add model" Example: VIE-L09C432. Click on FullOTA-MF Firmware (that matches) and "Check Firmware Access" and "Check Availability" If it says: "The firmware is not approved for installation" - I would not recommend . If it shows: "Firmware approved for installation Models VIE-Lxx" (and it matches your device/cust or the cust you want to rebrand)- click on Download.
Tip: If you enable in Developer Options "Keep phone awake during USB charging" you make sure, the Download get not corupted. Additional I would try to open the zip file after Download in a zip viewer to check if the zip file is complete.
The other possibility is, download the zip files to PC instead on the phone. Finally, it is needed on the PC and needs to be copied to the C:\HWOTA7\update
If you click in Firmware Finder on Download you will see 4 zip files - but you need only 3 of them: update.zip, update_data_full_public.zip and the third file must match your device (which you like to update or rebrand to) When you see the 4 files, choose the 3 files you need.
When you click on "Share Firmware" - then you can store the Links in a txt file. In this case you can download the files on PC. When you click instead "ok" Firmware Finder will download the Firmware to the Phone.
Alternatively you can use the Direct Link on PC:
http://pro-teammt.ru/firmware-database/?firmware_model=&firmware_page=0
Enter the correct model name and cust (Example: VIE-L09c432) and press enter. Choose only FullOTA-MF. Click on FILELIST and wait until a new Window pops up with the Links you need for Download. However, here you dont see if the Firmware is approved for installation.
The Third possibility - Firmware Finder for PC:
http://pro-teammt.ru/projects/hwff/v2/GetLatestVersion.action
Unzip it and double click on FirmwareFinder.exe. Click on "Common Base" and enter your model name with cust. Search on "Type" for FullOTA-MF and click on FILELIST. After you can copy with right click on changelog and above in the symbol "check availability" you can check, if the Firmware is approved (even with your IMEI, if you like)...
→ In the second post there is a step by step guide to rebrand the P9 Plus VIE to VIE-AL10 (including the links) and update to Android 8 Oreo.
Download P9PlusVIE-HWOTA7:
https://www.androidfilehost.com/?fid=1322778262904007988
MD5: 1edc0c8aedbf3f3470fb419dc67d7c26
→ Extract the zip on your PC, the zip contains the folder: HWOTA7 - Copy the folder to C:\ = C:\HWOTA7
Have fun
Credits:
@Atarii VIE-NoCheck Recovery
@OldDroid Android 7 TWRPs for many Huawei devices, Lead Developer/Maintainer Open Kirin Team
@Pretoriano80 Android 8 TWRP for many Huawei devices
@urbanmec Huawei Tweak Professor
XDA:DevDB Information
Rebrand-Update-Tool-HWOTA7-P9-PLUS-VIE, Tool/Utility for the Huawei P9 Plus
Contributors
Tecalote
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2018-09-18
Created 2018-09-18
Last Updated 2018-09-18
Update Huawei P9 Plus VIE to official Android 8 Oreo
Unofficial method to update European models of Huawei P9 Plus VIE to official Android 8 Oreo
- for VIE-L09 and VIE-L29​
Originally, all models of the P9 Plus VIE and P9 EVA should receive the Android Oreo update. Unfortunately, Huawei has decided to only supply the Chinese models with Android 8.
For this reason, there is an unofficial way to update to the official Oreo → by rebranding the European models to VIE-AL10.
Note: This Guide is for P9 Plus VIE → (P9-EVA HWOTA7 with Update Guide to Oreo you can find here: https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849)
Oreo runs smoothly and well on P9 Plus, the battery last longer and with Android 8 there is Treble Support.
Since it is possible to update P9 Plus to Oreo - Huawei P9 VIE is officially supported by the OpenKirin Team :https://forum.xda-developers.com/p9/development/roms-openkirin-aosp-collection-t3828806
See OpenKirin supported devices: https://openkirin.net/devices/
Here is a small Guide how to go back from OpenKirin ROM to EMUI: https://forum.xda-developers.com/showpost.php?p=77905152&postcount=833
Preparation for the update to Oreo:
If you are on any Custom Rom - go back to Stock firmware first - before rebrand to another location!
You should be on the latest approved Firmware for your device - if you have not the latest approved Firmware, use HWOTA7 Tool to update your Firmware.
Do for every case a Backup (TitaniumBackup /Huawei Backup - without System-Apps/Settings) before. TWRP Backup makes no sence, because you can not restore it on Oreo! Make sure, the Update-Firmware is copied to the folder C:\HWOTA7\update - and two zip files are RENAMED as mentioned in OP → read OP Post#1. Update your Firmware by using the script (HWOTA7 Terminal: 2. Using the script + 1. Change firmware)
Instructions for updating to Oreo by rebranding your phone to VIE-AL10:
Requirements:
A) HWOTA7 Tool
B) Bootloader Unlock Code for your device
C) Micro SD Card → formatted as exFAT
D) For rebranding from VIE-L09 or VIE-L29 to → VIE-AL10 you need to download the following 2 Firmwares:
A) VIE-AL10c00b399SP20 /Android 7 (this Firmware is required for the Update to Oreo):
update.zip: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1891/g1755/v139083/f1/full/update.zip
update_full_VIE-AL10_all_cn.zip: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1891/g1755/v139083/f1/full/VIE-AL10_all_cn/update_full_VIE-AL10_all_cn.zip
update_data_full_public.zip: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1891/g1755/v139083/f1/full/public/update_data_full_public.zip
B) VIE-AL10C00B537 (8.0.0.537) OREO
update.zip:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3133/g1699/v200303/f1/full/update.zip
update_full_VIE-AL10_all_cn.zip:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3133/g1699/v200303/f1/full/VIE-AL10_all_cn/update_full_VIE-AL10_all_cn.zip
update_data_full_public.zip:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3133/g1699/v200303/f1/full/public/update_data_full_public.zip
→ rename for each Firmware two zip files as described in OP (Post #1)
Step-by-step:
0) Developer Options enabled (7x click on Build-Number in Settings /About phone) - In Developer Options: OEM Unlock, ADB Debugging + USB Debugging (in this order) enabled, HiSuite HDB (in Settings /Adv.Settings /Security) disabled, HiSuite on PC closed, working USB Connection
1) Connect your device with USB to PC and start from HWOTA7 main folder: update_eng.bat - Accept possibly the RSA query on the display of the P9 Plus
2) Restart your P9 Plus into Fastboot mode (use restart/restart and press VOL- /or shutdown phone and press VOL- and Power Button)
→ Note: During all steps USB Cable stays connected between phone and PC and you only press "Enter" in the terminal when the described step, in the line before, was executed.
3) HWOTA7-terminal detects if Bootloader is open or closed - if the Bootloader is closed go to 4) - if the Bootloaer is open go to 7)
4) Terminal ask you for the Unlock code - enter the Unlock code and confirm the Unlock on the phone
5) Your P9 Plus reboots and an automatic factory reset is done with internal storage wipe (lowlevel reset) - wait until the phone reboot to system. Skip everything during setup (except what can not be skipped) - Important: Enable Developer Options with ADB Debugging and USB Debugging
6) Restart your P9 Plus into Fastboot mode - now hit "Enter" Button - HWOTA7 Terminal will flash automatically TWRP for Android 7 and gives you the order to boot into TWRP by pressing VOL+ and Power Button (dont hit "enter" before this step is done)
7) In TWRP swipe to allow system modification - now hit "enter" (2x) in the Terminal - after a short while you will see: Upgrade Options
8) 2. Using script: 2.Change location - you will see a list of available "oeminfo" - use: 1.VIE-AL10c00
→ Note: The Firmware for VIE-AL10c00b399SP20 (Nougat) must be already in the update folder (and two zip files renamed)!
9) HWOTA7 flashes now oeminfo for VIE-AL10, Bootloader is getting closed, confirm the Unlock on device - automatic factory reset is executed, wait until 99% and 100% restarts the phone → NOW PRESS VOL+ to boot the phone into TWRP instead of system!
10) Allow system modification in TWRP and hit "Enter" Button for Terminal - HWOTA7 copies now the firmware to the directory: /data/update/HWOTA - phone will restart automatically and flashes the Firmware with NoCheck EMUI Recovery.
→ After your P9 Plus has started into the system - you may see a black screen with an input field and a keyboard - if yes, go to 11) - if no, go to 13)
11) Close HWOTA7 Terminal and press Power Button on P9 Plus to restart your Phone, restart phone, in the moment of restart press VOL- Button to boot into Fastboot Mode → Bootloader is closed. BTW: Chinese Brands dont have FRP.
12) Open update_eng.bat, click enter, enter the Unlock code, confirm Unlock on phone, phone makes a Factory reset with lowlevel wipe. Then the P9 Plus starts automatically into the system. Now you have already rebranded to VIE-AL10c00b399SP20 (Nougat) :good:
13) Accept the terms and conditions (Huawei + Google Services) and skip the rest, what can be skipped. Do not be nervous, your P9 Plus has no IMEI at the moment and no mobile network. This is normal. In the settings in the search bar, search for "Trust Space" and "HiSuite HDB" - disable both. Enable again Developer Options and inside: ADB Debugging and USB Debugging (in this order).
14) Click enter in Terminal, select 2. "No, I would not" and HWOTA7 will be closed. → Change now the Firmware in the update folder to: VIE-AL10C00B537 (8.0.0.537) OREO (remember: two zip files has to be renamed!)
15) Start again update_eng.bat. Reboot phone into Fastbood Mode. Hit "enter" for Terminal - TWRP will be flashed automatically - reboot with VOL+ and Power Button into TWRP - allow system modification - hit "enter" in HWOTA7 Terminal
16) Use Upgrade options: 2.Using the script - 1.Change firmware (Same brand update /but Oreo)
17) Click enter in Terminal, Firmware will be copied to: /data/update/HWOTA - "System update should start automatically" → if you receive any error like: "connect failed, no devices/emulators found" - go to 18) - if everything is okay go to 19)
18) Close HWOTA7 Terminal and use menu of TWRP to reboot into Bootloader, start again update_eng.bat - TWRP will be flashed again - boot into TWRP with VOL+ and Power Button - allow system modification - hit "enter" in HWOTA7 Terminal - Firmware will be copied to: /data/update/HWOTA - Phone will make reboot and flash the Firmware for Oreo automatically.
19) You have now successfully updated to Android 8. :good: Phone will reboot into VIE-AL10C00B537 (8.0.0.537) OREO
→ You should accept the terms and conditions (Huawei + Google Services) - otherwise Playstore will not work later! Do not enable WLAN and do not set up your phone (Fingerprint etc)right now! - skip, what can be skipped. → You will have "unknown IMEI" and no mobile network at the moment, that is normal. Open Settings/System and enable again Developer Options/ADB+USB Debugging. In Settings /Security+Privacy you can find "Trust Space" - disable it - and in same menu you find in "More" "Allow HiSuite to use HDB" - disable it! → Now we must help the phone to recognize the IMEI and enable mobile network and NFC on VIE-L09 and Dual-SIM on VIE-L29 as well as disable Chinese apps, which we do not need in Europe (and some of them would not work here)
20) Downloads:
TWRP for OREO: P9-VIE_EVA-8.0.0-TWRP-v4.img https://www.androidfilehost.com/?fid=1322778262904008816 - we need this to flash the important changes to system without the need of Root!
This TWRP is made by @Pretoriano80 for Honor 9 Lite. I made just small changes for assert hi3650. You can backup and restore everything, except data! There is no access to /data - means: you can not do Factoryreset from TWRP - and decryption of the internal storage for the TWRP session is not working. → For Backkup and restore data you can use HiSuite or Huawei Backup or Titanium Backup. MTP ist working, when you just disable/enable it once.
Network-Patch zip files (new released 03.03.2019):
→ select the zip according to your original model (which you had before rebranding to VIE-AL10)
→ Copy the zip file to the external SD or to the USB Stick, which you connect to P9 Plus after with OTG cable. Since TWRP can currently not access /data (internal storage) - you can not flash this Patches without → external SD or USB OTG
→ The Network Patch zip files can be used for b537. If you are already on Oreo and have an older Firmware (b528, b535), you must update first to b537.
→ Update from older Oreo Firmware to b537: see Post #5
VIE-L09_b537-SingleSIM_NetworkPatch-v2.5.zip: https://www.androidfilehost.com/?fid=1395089523397898649
MD5: c22b40706584852ee1b1873fc7c28e54
VIE-L29_b537-DUAL-SIM_NetworkPatch-v2.5.zip: https://www.androidfilehost.com/?fid=1395089523397898655
MD5: 9f8f5df0f8abfe5afe49097b6bc6c4d3
VIE-EVA-FaceUnlock-Oreo-v1.5.zip: https://www.androidfilehost.com/?fid=1395089523397898647
MD5: 973d006c55fa812d722b653a57c844c0
21) Copy the downloaded TWRP (from STEP 20) into the folder C:\HWOTA7\tools\Windows - connect P9 Plus with USB to PC - right click on cmd-here-exe (run as administrator) - type: adb reboot bootloader (enter, to restart your P9 Plus into Fastboot mode)
Code:
fastboot flash recovery_ramdisk P9-VIE_EVA-8.0.0-TWRP-v4.img
22) Disconnect the USB cable from P9 Plus and press (with the left hand) VOL+ and Power Button (with the right hand) and keep pressing until the Phone is rebooted into TWRP.
23) On the first Screen click on "Cancle" (because decryption is not working for now) but swipe to confirm to "Allow System modification"
→ Go to: Install /select storage: Micro SD (or USB-OTG) and flash the downloaded NetworkPatch.zip file. If you like, you can use the function down left "Add zip file" and choose the VIE-EVA-FaceUnlock-Oreo-v1.5.zip
24) Swipe to confirm flashing the Network Patch (and the optional added VIE-EVA-FaceUnlock-Oreo-v1.5.zip file)
25) If you had used an older NetworkPatch before flashing the newest one - go back to the main menu of TWRP, go to wipe → advanced wipe and choose only "cache" (not Dalvik) → but if you are new on Oreo b537 you can skip this step
26) Reboot to the system
27) Finally, Playstore and any keyboard is needed. Download the apks from here (February 2019): https://www.androidfilehost.com/?w=files&flid=290472
28) Install it, enable keyboard, open Playstore and log into your account. After that reboot your phone. Now you can update apps, download and install your favorite apps and additional all other Google apps from Playstore → do not flash GApps instead!
29) After you have installed all required files, you have currently TWRP installed → this is good for Users, which like to have Root and disabled OTA.
Root Guide can be found here: LINK WILL COME SOON
→ But if you like to enable OTA instead:
A) Download and flash: Enable-Hwota.zip from here: https://www.androidfilehost.com/?w=files&flid=290480
B) Go back to the main menu of TWRP and Reboot to Bootlader
C) flash in Fastboot mode the Stock EMUI Recovery
Code:
fastboot flash recovery_ramdisk VIE-b537-EMUI-RECOVERY_RAMDIS.img
Download from here: https://www.androidfilehost.com/?fid=1395089523397898696
Reboot Phone and enjoy
If you search for older files (Network Patches etc) for older Firmwares, you can also search my folder on Android Filehost:
https://androidfilehost.com/user/?w=settings-dev-files&flid=131030
Note: It is not possible to lock the Bootloader on to VIE-AL10 rebranded phone with Network Patch and FaceUnlock! This would revert all the required changes and in the worst case push your phone into a bricked state.
→ But what you can do with installed EMUI Recovery (instead of TWRP): You can do from settings /system /reset a Factoryreset with wipe of the internal storage (to clean up previous instalations) → in this case the Factoryreset lowlevel does not revert the changes! The only difference is: When you get Push notifications, the Badges over the app symbol on Homescreen will change from numbers to points (which is standard on Oreo) → which is currently not change able in settings without Factoryreset.
Known issues:
VoLTE and WiFi-Calling is is visible in the menu - but does not work for now!
If you want synchronisation between Google calendar and EMUI calendar - you need to install Google calendar from Playstore.
If you like to use Google Assistant and have problems to teach this app with your voice "Hello Google" - just open settings /apps & notifications /standard (default) apps - and choose Google Assistant as default app (then it will work).
→ Please read also the next few posts (Root, current firmware with eRecovery, Update Firmware on Oreo with HWOTA8, going back to EVA-AL10 Nougat and rebrand back to original model)
→ Currently working to update this posts (will be ready soon).
Instructions for root
Instructions for root access
Root is not required, but if you still wish, here is the guide:​
Due to the fact TWRP cannot access the encrypted data partition, you cannot JUST flash Magisk!!
→ A) But you can flash Magisk with TWRP using a workaround
→ B) Alternatively it is possible to flash a Magisk patched ramdisk.img in Fastboot mode
A) Workaround for flashing Magisk with TWRP – for Advanced Users:
1) Download the favorite Magisk version from here (all releases): https://github.com/topjohnwu/Magisk/releases
The actual and newest stable version you can get always from here too: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
2) Copy the flashable Magisk-vXX.zip and Magisk Manager apk to external SD – and make sure, you have Developer options with 1) ADB Debugging and 2) USB Debugging (in this order) enabled.
3) Reboot device to TWRP, cancle Password, allow system-modification (swipe to confirm)
4) On the main menu go first to "Mount" - down left click on "Select storage" and choose "Micro SD"
5) Go back to main menu and open "Advanced" and open "Terminal"
NOTE:
If you have got a OTA-Firmware Update with “Patch02” or “Patch01” before flashing the Network Patch (after Network Patch, you will not see this in "About phone"!) or if you don’t remember, then use following both Lines in Terminal, but if you are sure, you have only Firmware without Patch 01 or Patch02, then use just "Keep Force encrypt" Line. Write the Lines in TWRP/Terminal exactly.
6) Write following code with Terminal:
Code:
echo KEEPVERITY=true>>/cache/.magisk
echo KEEPFORCEENCRYPT=true>>/cache/.magisk
→ Confirm each Line with blue/white checkmark on keyboard, before writing the next Line and confirm also the second Line (if you use two)
7) Go back to the main menu to "Install" and flash Magisk - after that reboot phone without wipe of Dalvik/Cache!
8) Search for Magisk Manager on Homescreen - if it is not installed, just install the Magisk Manager apk
9) Open Magisk Manager → everything should be okay
10) Open normal settings /apps & notifications /Magisk Manager /permissions and make sure Magisk Manager has permission for storage.
11) From Magisk Manager menu above left, section “Downloads” – download and install directly “Busybox for Android NDK” by osmosis – save log and reboot phone.
→ If Magisk get a major update, uninstall first Magisk from Magisk Manager and use “uninstall” button. “Uninstall complete” The phone restarts automatically. After that you can flash the new Magisk and reflash the modules.
B) Flashing Magisk with patched ramdisk.img in Fastboot mode:
If you don’t want flash Magisk with the TWRP workaround – you can use a Magisk patched ramdisk.img instead.
1) You can patch ramdiks.img from update.app by yourself, with following method:
Extract the update.zip of the current installed Firmware, because we need the UPDATE.APP.
Download Huawei Extractor v0.9.9.5 from here: https://forum.xda-developers.com/showthread.php?t=2433454
In the settings of the Huawei Extractor disable "verify header checksum" - then put with drag and drop the UDPATE.APP into Huawei Extractor and extract by right click the RAMDISK.img (on earlier Android Versions it would be: BOOT.img)
2) Copy the original RAMDISK.img to your phone to the internal storage in the folder: Download
3) Install the latest Magisk Manager: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
4) Open Magisk Manager, Magisk Manager ask you "Install Magisk-vx.zip?" - first click on: no thanks
5) Since internal storage is encrypted by default, you must first enable the checkbox: "Preserve force encryption"
5) If you have installed a OTA-Firmware Update with Patch01 or Patch02 – then enable additional the checkbox "Preserve AVB 2.0/dm-verity" in Magisk Manager.
6) Then click on "Install" - "You want to install Magisk-v1x.zip now?" - Install - Patch Boot Image File...
7) Navigate to Download folder, and choose RAMDISK.img
8) Magisk will now patch the RAMDISK.img and and once that's done, Magisk will save the patched ramdisk.img with the new name: patched_boot.img in the "Download" folder on internal storage.
→ Do not be confused - this is just named “patched_boot.img, but it is in fact the patched ramdisk.img !
9) Go to Settings /Apps & notifications/Apps and uninstall Magisk Manager
10) Now you must flash the “patched_boot.img” – Reboot your phone into Fastboot mode
Android 8:
Code:
fastboot flash ramdisk patched_boot.img
10) Reboot phone, install again newest Magisk Manager, open it and you will be asked: "Requires Additional setup - to you want to proceed now" Yes. → This step is required for to work properly.
Google Playstore certification
You can try it with method by @zgfg:
https://forum.xda-developers.com/showpost.php?p=79070144&postcount=1574
→ If it does not work you can try advanced method:
1) Set your phone into Flight Mode (no network should be connected)
2) Open Settings/Apps & notification/Apps and down right in the dot menu click on: show systemprocessing
3) Go step by step into following Apps (if there): Google - Google Play Store - Google Play Services - Google-Service-Framework - each has the entry: storage - delete ONLY cache /not data
4) Open with Mixplorer the directory:
/data/data/com.android.vending/shared_prefs - search for the xml file: finsky.xml
5) Open finsky.xml with TEXT Mixplorer Text Editor
6) Search inside finsky.xml for: <boolean name="device-google-certified"value="false" - change it to:
Code:
<boolean name="device-google-certified"value="true"
- means, you change only "false" to: "true"
7) click on the save symbol to save the changes! - close Mixplorer and everything in the Background
8) Disable Flight Mode (so Phone search for network connections)
9) Reboot your Phone
10) Open Playstore menu /settings/ =certified
If you have problems with current version of Magisk and using Gpay (Google Pay), try following workaround:
https://forum.xda-developers.com/showpost.php?p=79028818&postcount=5
How to uninstall Magisk:
A) Before you doing an OTA Update, it is required to uninstall Magisk → and also make sure, to have Stock EMUI Recovery installed (instead of TWRP).
B) In case for a “major” Magisk update it is also sometimes necessary to uninstall Magisk before installing the new version, because with directly update the phone could get a Bootloop. (But normally Magisk updates can be done directly and without uninstalling Magisk before).
C) If your device can not boot into system due to an incompatible Magisk Module.
a + b) If you can boot normally to system, you can uninstall Magisk from Magisk Manager - just use the "Uninstall" button “Uninstall complete”. Magisk will be uninstalled and Magisk files deleted from /data directory. Thereafter, the P9 is restarted automatically.
c) If your device can not boot into system due to an incompatible Magisk Module, you can flash the original EMUI Stock ramdisk.img (which is not patched with Magisk)
→ ramdisk.img must match the Firmware version of your device
For the current Firmware VIE-AL10 b537 you can download the original ramdisk.img here:
VIE-b537-RAMDISK.img:
https://www.androidfilehost.com/?fid=1395089523397898698
You can flash it in Fastboot Mode:
Code:
fastboot flash ramdisk VIE-b537-RAMDISK.img
Alternatively, you can flash the image with TWRP.
In this case you flash the img with TWRP by using: "flash img" - but important is, you must flash it to: ramdisk (and NOT to recovery_ramdisk !!)
Soon you have installed the EMUI ramdisk.img, the device can boot to system again and Magisk is disabled.
Credits:
@osm0sis Busybox for Android NDK
@Didgeridoohan MagiskHidePropsConfig module
@topjohnwu Magisk root
Restore Firmware - downgrade to Nougat - rebrand back
Restore current firmware (if you are on EMUI or OpenKirin ROM) → check out following Post:
https://forum.xda-developers.com/showpost.php?p=77905152&postcount=833
How to go back from Oreo to Nougat → and rebrand back​
A) Method by using HiSuite (on PC):
1) If you have Magisk Root - uninstall Magisk with Magisk Manager (Button Uninstall)
2) Make sure, you have EMUI-Stock-Recovery installed (it does not work with TWRP)
3) Download Huawei HiSuite: https://consumer.huawei.com/minisite/HiSuite_en/
4) Update HiSuite on PC to (minimum) version: 8.0.1.302_OVE and connect your Phone with PC and HiSuite.
5) Let HiSuite install HiSuite App on your Phone - accept the Permission requests. Once that is done:
6) Click on "Systemupdate" - a new window pop up and show you your current version, click on the Link "Change version" - then you can downgrade to the latest Android 7 AL10 firmware
7) → then it is possible to use HWOTA7 again for rebranding back...
B) Method by using HuRUpdater → requires external SD or USB OTG:
If you want to go back from unofficial Oreo to Nougat and rebrand back to your original brand, you can do it with simply steps.
→ Note: HuRUpdater can not only be used for Downgrade, it can also be used for Update Firmware - It depends only on which firmware you pack together with HuRUpdater in the folder (which you have created on external SD or USB OTG)
→ The Firmware must be FullOTA-MF (same renaming than with HWOTA7 Tool)
1) Bootloader must be open
2) Flash TWRP for Oreo Download TWRP by Pretoriano80: https://www.androidfilehost.com/?fid=1322778262903998750
3) Backup your data with Huawei Backup (because TWRP can not acces data for now, because it has no encryption/decryption support)
4) Make a folder on your external SD and name it: Downgrade or Update (or however)
5) Copy the 3 Firmware zip files into the folder and make sure, two zip files are renamed (same as you did for HWOTA7)
6) Download HuRUpdater_0.4.zip from here:http://www.mediafire.com/file/r14sor2g4cbugzw/HuRUpdater_0.4.zip
7) Copy HuRUpdater into the same folder together with the firmware zip files. If you have the Nougat AL10 zip files inside, you will downgrade.
The folder contains now 4 files:
HuRUpdater_04.zip
update.zip
update_all_hw.zip
update_data_public.zip
8) Boot into TWRP. It will ask you for password. Just cancle. In TWRP open "Wipe" - but dont wipe anything - you must use the Button on the right Format Data. Confirm with typing: yes. Soon data is formatted, go back to the main menu and open Reboot - but do not reboot System - you must Reboot Recovery
→ Note: Format data is only important until we have TWRP with working data decryption
9) After TWRP is rebooted go "Install".
10) Navigate to the folder which containes the files and flash ONLY HuRUpdater_04.zip In some seconds the Akku vibrates - in this moment press for one second the VOL- Button. Now HuRUpdater will flash automatically the FullOTA-MF Firmware.
11) Once it is done, use on the left: Wipe Cache Button. After go back to the main menu and Reboot RECOVERY.
12) Your device has rebooted now into EMUI Stock Recovery. From there perform Wipe Cache Partition and Factory reset and boot to system.
Once you are back to Nougat - you can use again the HWOTA7 Tool to rebrand back to your original brand. Just use Change location (for your original cust) and make sure, the Firmware is in the update folder..
Credits:
@zxz0O0 Many thanks for HuRUpdater
HuRUpdater Thread: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
How to update older Oreo Firmware to → b537
How to update manually the Firmware from Oreo b528 or b535 to → b537
This method is based on VIE-EVA-Nocheck EMUI-Recovery for Oreo.
Required for the Firmware update is installed TWRP https://www.androidfilehost.com/?fid=1322778262903998750
Additonal information to the manual Firmware-Update from b535 (or even from b528) → to b537 → or even to next version in the future:
1) Download current Firmware VIE-AL10C00B537 (8.0.0.537):
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3133/g1699/v200303/f1/full/update.zip
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3133/g1699/v200303/f1/full/public/update_data_full_public.zip
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3133/g1699/v200303/f1/full/VIE-AL10_all_cn/update_full_VIE-AL10_all_cn.zip
2) Let Windows show file extensions (to make sure you have at the end not zip.zip) and rename the last two zip files - (update.zip - do not rename)
update_data_full_public.zip - rename to: update_data_public.zip
update_full_VIE-AL10_all_cn.zip - rename to: update_all_hw.zip
3) Download FirmwareUpdate_onOreo_from-externalSD.zip file and extract (unzip) it:
https://www.androidfilehost.com/?fid=1395089523397898767
Inside is the folder: HWOTA and contains two files. Do not rename that files.
4) Create a folder on your external SD with the Name HWOTA in the main directory (dont use another name!) - or copy the HWOTA folder from unzipped Firmware-Update.zip instead to your external SD
5) So you have now the folder HWOTA on your external SD (without Subfolders between)
6) The folder HWOTA must contain:
eva_vie_recovery_nocheck.img
ExtSD-FirmwareUpdateScript.zip
update.zip
update_all_hw.zip
update_data_public.zip
7) Now boot to TWRP, cancle Password, allow system modification, go to Install, select storage: Micro SD - and flash ONLY the one zip file with the name: ExtSD-FirmwareUpdateScript.zip
8) The phone will automatically reboot and needs a while to flash automatically the No Check EMUI-Recovery and this needs also a while until the Firmware will be flashed automatically as well as Phone reboots after. Just wait, until it boot up.
→ if you have Root, there is no need to Unroot before and you will loose no installed apps but probably Playstore and/or Keyboard (if the apps were not updated, if the were updated, you will not loose Playstore and not Keyboard). If Playstore is missing, just install the Playstore apk and Keyboard apk and reboot phone. → Links for the apks in Post #2
Nothing will be wiped, except mobile network settings are gone and some additional Chinese Apps are installed.
9) Flash again TWRP and select your NetworkPatch.zip (that matches your real device) and in the middle you find the button "add zip" just add: Faceunlock.zip
→ flash both together with swipe to confirm and reboot phone without wipe anything.
Note: You must use the new released Files from Post #2 step 20-29: https://forum.xda-developers.com/showpost.php?p=77650678&postcount=2
10) You are now on b537 - The Chinese Apps are automatically deleted and everything works as it should
Enjoy :good:
And here it is ? Can't wait to try it. On holidays right now, I'll test it by two weeks, I just need to recover a Windows laptop as I'm using Linux right now. Anyway, thank you a lot for the effort!
thank you so much for the hardwork. Love to see this happening for the p9 plus. keep the good work up. i will try out the tools this weekend.
Just to be sure, to update an european modelo (c432) we need to follow instruction in post 1 and post 2 ?
Fil76 said:
Just to be sure, to update an european modelo (c432) we need to follow instruction in post 1 and post 2 ?
Click to expand...
Click to collapse
Hi, welcome in this Thread
→ Reading OP (Post # 1) is required because some information from there is required in Post # 2. OP is a general overview of how the tool works and what to look for.
Post # 2 is an exact guide for rebranding the European model to VIE-AL10 and updating to Android Oreo.
On Oreo, initially no IMEI is detected and there is no mobile network available - the P9 Plus must therefore be adapted. This is done by means of a zip file, which you choose according to your original model. The zip must be flashed with TWRP, after a factory reset must be performed with the EMUI Stock Recovery.
Yes, if you want your device to work with the Chinese firmware on Oreo, then you must read both Instructions and following the Guide.
I spent a lot of time for free into this project, so that the user is able to get the "impossible" possible. Everything was tested thoroughly by me and others.
FYI: I am not responsible for any mistakes or bricks that occur if someone do not follow the instructions exactly
Post #3 - Root instructions → ready
Fantastic to see this tool also for P9 Plus!
Thank you very much for the time and the work spent to create this tool!
edit:error in progress
Fil76 said:
edit:error in progress
Click to expand...
Click to collapse
? Please more detailed, if you need help
i had fastboot connection problem due to cable (one original and one not) and cause i'm dumb i didn't rename a nougat file correctly and got nrm90 test key as build number
resolved after installing oreo update (i tried restarting all the procedure with hwota setting again al10 but nrm90 etc remain)
But i'm in working progress cause i installed oreo and build numer now it's correct
now i'm continuing following your guide
let's hope....lol
edit2:YEAH ALL FINE THANK YOU FOR YOUR TOOL
the only one problem that i got that everytime i boot i got message that bootloader is unlocked
Fil76 said:
YEAH ALL FINE THANK YOU FOR YOUR TOOL
the only one problem that i got that everytime i boot i got message that bootloader is unlocked
Click to expand...
Click to collapse
That's not a problem
That's always on every Android version from Marshmallow /Nougat /Oreo above..
If the Bootloader is opened you will get this message as long the Bootloader is unlocked.
And there's nothing what could be done to hide this message.
But the other side is, without unlocked Bootloader you couldn't change anything.
And if you would relock the Bootloader - you would loose all the settings necessary for European VIE to work properly on Oreo
First of all, thanks @Tecalote and team to let my Vie-p9 plus fly again^^, i followed each step carefully and successful debrand and upgrade to Oreo, everything works like a charm and after restore all the apps and all works without problem only NFC(because i need google pay as my transport payment method), the nfc icon show in the pull down drawer but it grey out and no respond. And inside setting> device connection> only have bluetooth, Multi-screen, usb and printing options but only missing the NFC.
is it any way to fix it?
htc_black said:
First of all, thanks @Tecalote and team to let my Vie-p9 plus fly again^^, i followed each step carefully and successful debrand and upgrade to Oreo, everything works like a charm and after restore all the apps and all works without problem only NFC(because i need google pay as my transport payment method), the nfc icon show in the pull down drawer but it grey out and no respond. And inside setting> device connection> only have bluetooth, Multi-screen, usb and printing options but only missing the NFC.
is it any way to fix it?
Click to expand...
Click to collapse
Hello @htc_black
What was your original model? VIE-L29 ? - okay, I am sorry. I saw just right now, that L29 includes also NFC - I did not know that. I will upload corrected zips for L29 in about 30 minutes.
I thought, it is the same than on EVA (EVA L09 = NFC, no Dual SIM, L19+L29 = no NFC, but Dual SIM) - but VIE has NFC on L09 as well as on L29....
So, it can be fixed, no problem.
I had only L09 to test and dont own L29
After upload the corrected zip, please install and let me know, if it works! Thanks
Tecalote said:
Hello @htc_black
What was your original model? VIE-L29 ? - okay, I am sorry. I saw just right now, that L29 includes also NFC - I did not know that. I will upload corrected zips for L29 in about 30 minutes.
I thought, it is the same than on EVA (EVA L09 = NFC, no Dual SIM, L19+L29 = no NFC, but Dual SIM) - but VIE has NFC on L09 as well as on L29....
So, it can be fixed, no problem.
I had only L09 to test and dont own L29
After upload the corrected zip, please install and let me know, if it works! Thanks
Click to expand...
Click to collapse
Finally finally finally:laugh: rebranded , updated to Oreo and rooted :victory: :laugh:
Thank you so much for your great effort and helping us
Really you are a genius
Everything is working well, only NFC is not working but the rest is perfect
From VIE-L29 to VIE-AL0
meshoo00oo said:
Finally finally finally:laugh: rebranded , updated to Oreo and rooted :victory: :laugh:
Thank you so much for your great effort and helping us
Really you are a genius
Everything is working well, only NFC is not working but the rest is perfect
Click to expand...
Click to collapse
NFC patch is just uploading, coming in a few minutes. I post it here

[GUIDE][MIUI] GESTURE NAVIGATION WITH THIRD-PARTY LAUNCHERS IN ANDROID 11 (NO ROOT)

Hi everyone!
First, I hope I am in the correct section to post this. I'm not a developer, I just want to share what the ultimate solution was for me. This process worked great for my Xiaomi Mi 9 (cepheus) with MIUI on Android 11. NO ROOT REQUIRED.
​► HOW TO USE GESTURE NAVIGATION WITH THIRD-PARTY LAUNCHERS IN ANDROID 11 ◄​
1. First it is important to have one of the apps:
- Infinity Gestures
- Fluid Navigation Gestures (I chose the Pro version)
2. Reboot your phone in recovery mode.
3. If you use:
- Orange Fox: You go to MENU > MOUNT and check the boxes for CACHE, SYSTEM, DATA.
- TWRP: You go to MOUNT and check only the boxes for CACHE, SYSTEM, DATA.
In both cases the ENABLE MTP option is activated, check it just in case.
4. Use MinimalADB & Fastboot or if you want, Platformtools to open a command console.
5. You write without quotes "adb devices", you hit ENTER and you wait for it to detect your phone.
6. Without quotes, put the command "adb pull /system/build.prop" and hit ENTER.
7. In the MinimalADB or Platformtools folder you will now see a file with an unknown extension called "build.prop". You give it RIGHT CLICK > EDIT or RIGHT CLICK > OPEN WITH > NOTEBOOK (or any other editor of your choice).
8. You go to the end of the file and ADD without the quotes a last line that says "qemu.hw.mainkeys=1"
9. SAVE the changes and CLOSE the editor. You return to the command console.
10. In the command console you write without quotes "adb push build.prop /system/" and press ENTER.
11. Now you have to reboot your phone. Once it starts you will see that you no longer have the navigation bar (buttons).
12. You open the gesture app that you have downloaded, you block it so that the task is not deleted (apply the padlock), you grant the app all the permissions it asks for. In addition, you must go to APP INFORMATION > BATTERY SAVER and there choose the first option "NO RESTRICTIONS" as well as see that the AUTOMATIC START option is ACTIVATED.
NOTE: This point applies to MIUI, in the AOSP it is not necessary.
13. Enjoy gesture navigation with third-party launchers on MIUI and space on the keyboard for AOSPs.
​►►► THE EASIEST METHOD (SIMPLIFIED) ◄◄◄​
A big thanks to the developer Poney70 from the Xiaomi.eu team for reading the tutorial and taking the time to make this ZIP file.
1. First it is important to have one of the apps installed:
- Infinity Gestures
- Fluid Navigation Gestures (I chose the Pro version)
2. Reboot your phone in recovery mode.
3. Flash THIS ZIP in TWRP or Orange Fox.
NOTE: Flashing it again will reverse the change.
4. Reboot your phone.
5. Open the gesture app that you have downloaded, you block it so that the task is not deleted (apply the padlock), you grant the app all the permissions it asks for. In addition, you must go to APP INFORMATION > BATTERY SAVER and there choose the first option "NO RESTRICTIONS" as well as see that the AUTOMATIC START option is ACTIVATED.
NOTE: This point applies to MIUI, in the AOSP it is not necessary.
6. Enjoy gesture navigation with third-party launchers on MIUI and space on the keyboard for AOSPs.​
Thank you so much. I was searching for this kind of tweak.
ammaralidj said:
Thank you so much. I was searching for this kind of tweak.
Click to expand...
Click to collapse
You're welcome. A pleasure for me to share this with others.
i have this error message:"failed to copy 'build.prop' to '/system//build.prop': write failed: No space left on device". Any fix? The zip doesn't work. I'm not on stock miui.
xBinyWolf said:
i have this error message:"failed to copy 'build.prop' to '/system//build.prop': write failed: No space left on device". Any fix? The zip doesn't work. I'm not on stock miui.
Click to expand...
Click to collapse
It should be well known that for A11 SAR (System As Root) is read-only and no rooting 'help' here
Open /vendor/etc/fstab.* file-system table and analyze the lines for / or /system - if you find ro it means read-only
That's why Magisk provides Systemless changes mechanism
E.g., for AdAway you have to enable Systemless hosrs bcs it cannot write directly to /ysyrem/etc/hosts
Similarly for your props. Use e g . Magisk module Magisk Hide Props Config - it has options to edit custom props of your choice
Do you think this can be done in a12? I've already rooted my phone.
warhead1721972 said:
Do you think this can be done in a12? I've already rooted my phone.
Click to expand...
Click to collapse
Of course. Many times I used it in the AOSP with A12. Currently, I have also tested it on A12 + MIUI 13 on a Poco (Xaga).
AJSRO said:
Hi everyone!
First, I hope I am in the correct section to post this. I'm not a developer, I just want to share what the ultimate solution was for me. This process worked great for my Xiaomi Mi 9 (cepheus) with MIUI on Android 11. NO ROOT REQUIRED.
​► HOW TO USE GESTURE NAVIGATION WITH THIRD-PARTY LAUNCHERS IN ANDROID 11 ◄​
1. First it is important to have one of the apps:
- Infinity Gestures
- Fluid Navigation Gestures (I chose the Pro version)
2. Reboot your phone in recovery mode.
3. If you use:
- Orange Fox: You go to MENU > MOUNT and check the boxes for CACHE, SYSTEM, DATA.
- TWRP: You go to MOUNT and check only the boxes for CACHE, SYSTEM, DATA.
In both cases the ENABLE MTP option is activated, check it just in case.
4. Use MinimalADB & Fastboot or if you want, Platformtools to open a command console.
5. You write without quotes "adb devices", you hit ENTER and you wait for it to detect your phone.
6. Without quotes, put the command "adb pull /system/build.prop" and hit ENTER.
7. In the MinimalADB or Platformtools folder you will now see a file with an unknown extension called "build.prop". You give it RIGHT CLICK > EDIT or RIGHT CLICK > OPEN WITH > NOTEBOOK (or any other editor of your choice).
8. You go to the end of the file and ADD without the quotes a last line that says "qemu.hw.mainkeys=1"
9. SAVE the changes and CLOSE the editor. You return to the command console.
10. In the command console you write without quotes "adb push build.prop /system/" and press ENTER.
11. Now you have to reboot your phone. Once it starts you will see that you no longer have the navigation bar (buttons).
12. You open the gesture app that you have downloaded, you block it so that the task is not deleted (apply the padlock), you grant the app all the permissions it asks for. In addition, you must go to APP INFORMATION > BATTERY SAVER and there choose the first option "NO RESTRICTIONS" as well as see that the AUTOMATIC START option is ACTIVATED.
NOTE: This point applies to MIUI, in the AOSP it is not necessary.
13. Enjoy gesture navigation with third-party launchers on MIUI and space on the keyboard for AOSPs.
​►►► THE EASIEST METHOD (SIMPLIFIED) ◄◄◄​
A big thanks to the developer Poney70 from the Xiaomi.eu team for reading the tutorial and taking the time to make this ZIP file.
1. First it is important to have one of the apps installed:
- Infinity Gestures
- Fluid Navigation Gestures (I chose the Pro version)
2. Reboot your phone in recovery mode.
3. Flash THIS ZIP in TWRP or Orange Fox.
NOTE: Flashing it again will reverse the change.
4. Reboot your phone.
5. Open the gesture app that you have downloaded, you block it so that the task is not deleted (apply the padlock), you grant the app all the permissions it asks for. In addition, you must go to APP INFORMATION > BATTERY SAVER and there choose the first option "NO RESTRICTIONS" as well as see that the AUTOMATIC START option is ACTIVATED.
NOTE: This point applies to MIUI, in the AOSP it is not necessary.
6. Enjoy gesture navigation with third-party launchers on MIUI and space on the keyboard for AOSPs.​
Click to expand...
Click to collapse
hi. i tried your tutorial. i used flasable zip. but my navbar still there, it not hidden. any solution ?
my device poco m4 pro 4g( Fleur) + 13.0.10 Global rom rooted Android 11 + Miui 13

(ROOT) Removing Uttar Pradesh government (India) privacy invasion and software restrictions in Samsung Galaxy A03

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

Categories

Resources