While some of these instructions are copied from other sources, I combined all the different things I learned, because no one guide was sufficient, and all needed additional info, so I expanded it all to one place. Part I is partly from @nevertechdose. Parts II & III are mostly copied from @thatha's guide. Part V is mostly @razs.originals guide. Parts IV, VI, VII, VIII, IX, X, XI, etc are my guides.
Special thanks to @thatha for their guide & T225 files, @Talich52 for their post & T220 file, @realbbb for their post & odin files, & @nevertechdose for their OEM Unlock guide. Also to @razs.originals for their bootloader warning removal guide.
I. Get OEM Unlock to show up (If it doesn't show already. If it shows, skip to Part II.)
Factory Reset Device (Sorry but this will happen when you unlock & root anyway, and has to be done first.)
Skip everything on the first boot setup including WiFi settings (you'll connect to the Internet later). (You can still during setup decline to provide sensitive info - just select the first two bubbles and accept - and you can also still turn off the three privacy sharing buttons.)
I did not change any settings when I booted in, just proceeded to step 4.
Enable developer options and disable automatic system updates from there.
Disable automatic software update. Settings > Software Update > turn off.
Connect to a WiFi network.
DISCONNECT from internet after a few seconds. You'll see it trying to update things in the pull down menu, disconnect from internet, you don't want it to update anything. It just needs to be connected long enough to update the day and time to the correct day and time, and register your device. If it didn't work, it didn't register your device yet.
For me, it did get to the point where there was a notification that said, "Finish setting up your Tab A7 Lite." DO NOT finish setting anything up, but do make sure internet is disconnected. Ignore notification, but you should see that.
Go to General > Date and Time settings and select for the time to be set manually (don't touch time zone). Set the date to be EXACTLY 10 days BEHIND from your current date.
Go to Developer Options, and OEM Unlock should be there!
If it still doesn't work, you may have to go to extreme measures, but I didn't have to. But first just make sure you did the above steps EXACTLY.
Go here for extreme measures if you did EXACTLY like above and still didn't work (my instructions above were a bit different) https://forum.xda-developers.com/t/a7-2017-w-binary-9-rmm-state-unlock.4057831/post-82049513
II. Unlock bootloader (Thanks @thatha)
Enable developer options by going to Settings > About Tablet > Software information > and tap "build number" 7 times
Go to Developer options, turn on OEM Unlock (If it doesn't show up, skip to Part III and then come
Turn off Tab A7 Lite, connect it to the computer while holding Volume Up and Volume Down keys until you see the bootloader screen
Long-press Volume Up key to enter Device Unlock mode
Press Volume Up key to confirm and unlock the bootloader
III. Create your device's patched boot (You can skip this if you have one of the 3 devices with the files in part IV.1 below.)
Download your firmware from samfirm or other source (I didn't have to do this, so I can't instruct on it)
(On PC) Extract boot.img.lz4 from Stock AP...tar file, then copy it to Tab
(On Tab) Install ZArchiver to extract boot.img from boot.img.lz4
(On Tab) Install Magisk and patch the boot.img that you have just extracted from step 3
(On PC) Copy magisk_patched.img (in Tab\download) to pc, rename it to boot.img
(On PC) Use 7zip to pack boot.img from step 5 into boot.img.tar
IV. Root Tab A7 Lite
Download correct boot.img.tar for your device (For T220XXU1AUJ1 it's magisk_patched-23000_acKsR.tar), it will probably be a zip, if so you'll need to unpack it to a tar (you can use 7zip for that). The two T225 files were pulled from here. The T220 file (my device) was pulled from here. I inserted and attached them for future proofing and to make it easier for you.
You can find your device under Settings > About Tablet > Software information > Build Number. Mine is a Wifi model Tab A7 Lite, model T220 4GB/64GB, my build is T220XXU1AUJ1.
The files below are direct links to the attachments in this thread (take CAREFUL note of the T220 or T225 in the name - they are different).
For T220XXU1AUJ1:
https://forum.xda-developers.com/attachments/magisk_patched_t220xxu1auj1-23000_acksr-zip.5544869/
For T225XXU1AUJ1:
https://forum.xda-developers.com/attachments/boot_t225xxu1auj1-tar.5544889/
For T225XXU1AUL1:
https://forum.xda-developers.com/attachments/boot_t225xxu1aul1-tar.5544891/
For T220XXU1AUL2:
https://forum.xda-developers.com/attachments/boot_t220xxu1aul2-tar.5547521/
If you don't have one of the above 3 devices, then follow the Part III guide above to create the correct boot.img.tar file. DON'T FLASH THE ABOVE IF IT IS NOT YOUR DEVICE!
Get Odin 3.14.1. (All 3.14.4 are FAKE!) The exact one I used was Odin3 v3.14.1_3B_PatcheD. Get it from here ONLY! https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
I also attached the same file to this post. Download from the other page if you don't trust me.
Boot into Download Mode
(If you're stuck at SetupConnection in Odin, it's because you have to run it from Download Mode, it won't run while device is on.)
- Power off device
- Hold Volume Up & Volume Down buttons at the same time, connect USB cable, keep holding until you see the screen.
- Press Volume Up to go to Download Mode
Here's a video for this device on how to do it and what it looks like (credit goes to the maker of the video, not me):
Open Odin as Administrator (Right-click > Run as Administrator)
Click AP and find the file magisk_patched-23000_acKsR.tar (for T220XXU1AUJ1). NOT THE ZIP. And not the raw boot file(s). Has to be the tar.
If successful, it wlil say this:
<ID:0/008> Added!!
<ID:0/008> Odin engine v(ID:3.1401)..
<ID:0/008> File analysis..
<ID:0/008> Total Binary size: 32 M
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> NAND Write Start!!
<ID:0/008> SingleDownload.
<ID:0/008> vbmeta.img
<ID:0/008> boot.img
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Removed!!
<ID:0/008> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Device will reboot. It will say bootloader unlocked continue, so press Power button like it asks. You will see a screen with red text warning you it's been altered.
It will not boot. Don't worry it will reboot again, same thing as step 6. Now it fails and asks you to Factory Data Reset. Ignore the errors it's telling you, and Yes, go ahead and click Factory Data Reset (you have to).
It will go through step 6 again, this time, after a few minutes it will boot up into Android and prompt you to setup device. Success!
V. Remove Bootloader Warning ⚠ (thanks to @razs.originals for their guide & file)
@razs.originals provided a guide and the needed file, but their guide was slightly lacking for those less experienced, so I'll expand it slightly to be more precise what to do. This removes all the bootloader unlock warnings on boot.
Get the free app Termux.
Download the up_param.tar file and move it to download folder (internal storage) - it might be the default location, if not then it should be here:
/storage/emulated/0/Download/up_param.tar
Open Termux, and then type the next series of lines of code (press enter in between each line):
su
cd /
Code:
dd if=/storage/emulated/0/Download/up_param.tar of=/dev/block/platform/bootdevice/by-name/up_param
Now reboot, and the bootloader warning screens should be gone!
VI. Install/Update Magisk on Tab A7 Lite
Magisk will exist in apps, but clicking on it asked me to update but nothing happened. If that's the case for you too, then:
Download Magisk latest version from their official Github. (DO NOT DOWNLOAD FROM ANY OTHER SOURCES!) I included the apk from the github page here for future proofing and reference, I am using Magisk 24.1 which worked.
Install the APK. Open file manager if you need to and then find it in Downloads or wherever you downloaded it.
Open Magisk, it will ask you to update. Choose "Direct Install (Recommended)" and then click Let's Go in the top right.
It will flash the image and then say All Done!, then you can click the Reboot button in the bottom right.
You can now check root by installing any app that needs root, for example Titanium Backup which is an essential one for me. There's also OandBackupX, which is a free and open source fork of Titanium backup.
You will be greeted with a Superuser popup if you are rooted, so grant permissions and you can see you are rooted! Congratulations!
Nothing special is needed on reboot, if you ever reboot your device, it just reboots as normal and stays rooted. Congratulations on completing the guide! Please remember to like this if you liked the guide (only if you liked it), so I know I am helping.
VII: Install LSPosed (Successor to Xposed) on Tab A7 Lite
Download LSPosed latest version from the official Github.
- Make sure to choose the Zygisk version (e.g lsposed-vx.x.x-xxxx-zygisk-release.zip).
- Why Zygisk? Because Riru is retired. You don't need it anymore.
- Don't worry about downloading any Zygisk or Riru. Riru is retired and Zygisk is now integrated in Magisk.
Copy the zip file to your device.
Open Magisk, go to Modules, click Install from Storage, and find the zip you just copied for lsposed zygisk version.
Click Reboot button in the bottom right when it's finished.
VIII: Activate Zygisk (Successor to Riru) on Tab A7 Lite
You're not done yet. Now go into Magisk, click Settings button in the top right.
Scroll down and enable Zygisk (Beta).
Below that, enable Enforce DenyList.
Below that, click Configure DenyList.
In the top right, click the 3 dots menu and check the box Show System Apps.
Select Google Play Services by checking the box.
Tap on Google Play Services to open all the items for it, and enable all the items for Google Play Service.
For anything else you deny in the DenyList that you configure, Zygisk will not work for it, because you denied it. So in the future if you want to disable Zygisk for anything else, this is how. But if you don't konw what this means, don't worry about it.
That's it! Now go ahead and reboot your device by holding the Power button for a couple seconds and clicking Reboot (If you choose Power Off by accident then it won't reboot without you turning it back on )
On reboot, it will ask if you want to add a home page shortcut. Choose YES, because it won't show in your apps, so you want an easy way to access LSPosed.
Open Magisk and click on Modules to see that LSPosed is active! Congratulations you now have LSPosed installed and working!
IX: Xposed Modules for LSPosed
I recommend a couple mods for LSPosed. There aren't a ton yet for Android 11 and less for Android 12.
Browse the Xposed Repository, because you apparently can't from within LSPosed.
- Note - Don't use any modules you don't know what they do.
Recommended Module: GravityBox [R] (For Android 11) - Allows you to do lots of customizations. (Enable dark theme for GravityBox under the About at the bottom, after you activate it using steps 5 and 6.)
Recommended Module: DarkTricks (For Android 11) - More customizations and tricks. Nothing "dark" about it, just the user's name.
Recommended Module: FireFds Kit [R] (For Android 11) - Activate Advanced Power Menu, Disable restart confirmation, Date in Status Bar, etc.
Recommended Module: App Settings Reborn (For Android 11)
- Allows you to set custom DPI per-app. I used it to put Swype into tablet mode using these settings: DP: 175, Screen (dp): 1080x1920)
To install, just copy to your device, and browse to the apk through file manager, and install it.
When you install, you will get a notification, "Module is installed but not activated". Either click on the notification and Enable, or open LSPosed, go to Modules, click on the greyed-out modules, and click Enable on each module you want to activate.
Then reboot to activate the module. If you don't reboot, then the module isn't going to work when you click on it, but it will after you restart.
X: Install Shamiko (Magisk Hide Alternative) & Momo [Both In Development ALPHA (Pre-Beta)]
Magisk Hide was permanently removed from the latest versions of Magisk. The alternative is Shamiko, although it's still in development. Install at your own risk.
Momo simply checks your environment for your knowledge. It can help detect if you successfully hid Magisk.
Shamiko Development Version: https://t.me/magiskalpha/438
Momo Development Version: https://t.me/magiskalpha/379
Install Shamiko using Magisk like you did in Part VI: Go to Modules, Install from Storage, Find the Shamiko .zip file, Install, Reboot.
Install the Momo APK. You can open it right away.
Official Telegram: https://t.me/s/magiskalpha (Find latest versions here on the Telegram page. I had to use actual Telegram to download them. So I attached the apks above.)
More details on Shamiko & Momo: https://xiaomiui.net/a-new-method-for-hiding-root-is-on-the-way-2720/
XI: Tweaks
Disable tablet mode in apps universally:
Go to:
Settings > Developer Options > Drawing > Minimum width
Set to 598 (Default 600)
- This will disable the annoying tablet mode, browsers and other apps look weird. Yandex had search bar at top, no extension support, and no dark theme. This hack brought everything back.- Will not affect size or resolution at all. It will just trick apps into displaying in normal phone mode.- You can also disable on a per-app basis using xposed module in the above section.
Turn off animations (Optional):
Go to:
Settings > Developer Options > Drawing >
Window animation scale: 0.5
Transform animation scale: 0.5
Animator duration scale: None
I will add more later if I find anything else major, and also if a working TWRP is released and I find it, I will post it in a new section here.
It worked for me
$cronos_ said:
Nice guide, unfortunately I don't have much money, thus don't have one of these tablets. I will, however, save up for one.
Click to expand...
Click to collapse
I got a 4GB/64GB (top model) T220 on sale from the Best Buy ebay page for only $150!
Sams Club and Costco have the 3GB/32GB model on sale right now for only $130!
Added Part V: Magisk
Added instructions for LSPosed (Xposed successor) & Zygisk (Riru successor)
Added Xposed (LSPosed) Modules section
Excellent guide and work. Thank you for your time.
nikoum said:
Excellent guide and work. Thank you for your time.
Click to expand...
Click to collapse
Thank you and glad to help. This was a lot of work, so I hoped to save others the time and energy and make it possible for more people.
Thanks for the awesome tutorial! I just rooted my device successfully. It actually took me two attempts, and the first time I nearly bricked my brand new tablet, lol
My model is T220XXU1AUL2, no readily available boot.tar was provided so I thought I'd share the one I created, which successfully rooted my tablet on my second attempt.
xbt- said:
I got a 4GB/64GB (top model) T220 on sale from the Best Buy ebay page for only $150!
Sams Club and Costco have the 3GB/32GB model on sale right now for only $130!
Click to expand...
Click to collapse
Picked up the 3GB/32GB model on Amazon for $119 this week.
@1984Shovelhead on the linked tutorial reported that if you make your own boot file to flash, you have to name it boot.img.tar, not boot.tar, because boot.tar will not flash. Updated instructions.
xbt- said:
While some of these instructions are copied from other sources, I combined all the different things I learned, because no one guide was sufficient, and all needed additional info, so I expanded it all to one place. Part I is partly from @nevertechdose. Parts II & III are mostly copied from @thatha's guide. Parts IV, V, VI, VII, etc are my guides.
Special thanks to @thatha for their guide & T225 files, @Talich52 for their post & T220 file, @realbbb for their post & odin files, & @nevertechdose for their OEM Unlock guide.
I. Get OEM Unlock to show up (If it doesn't show already. If it shows, skip to Part II.)
Factory Reset Device (Sorry but this will happen when you unlock & root anyway, and has to be done first.)
Skip everything on the first boot setup including WiFi settings (you'll connect to the Internet later). (You can still during setup decline to provide sensitive info - just select the first two bubbles and accept - and you can also still turn off the three privacy sharing buttons.)
I did not change any settings when I booted in, just proceeded to step 4.
Enable developer options and disable automatic system updates from there.
Connect to a WiFi network.
DISCONNECT from internet after a few seconds. You'll see it trying to update things in the pull down menu, disconnect from internet, you don't want it to update anything. It just needs to be connected long enough to update the day and time to the correct day and time, and register your device. If it didn't work, it didn't register your device yet.
For me, it did get to the point where there was a notification that said, "Finish setting up your Tab A7 Lite." DO NOT finish setting anything up, but do make sure internet is disconnected. Ignore notification, but you should see that.
Disable automatic software update. Settings > Software Update > turn off.
Go to General > Date and Time settings and select for the time to be set manually (don't touch time zone). Set the date to be EXACTLY 10 days BEHIND from your current date.
Go to Developer Options, and OEM Unlock should be there!
If it still doesn't work, you may have to go to extreme measures, but I didn't have to. But first just make sure you did the above steps EXACTLY.
Go here for extreme measures if you did EXACTLY like above and still didn't work (my instructions above were a bit different) https://forum.xda-developers.com/t/a7-2017-w-binary-9-rmm-state-unlock.4057831/post-82049513
II. Unlock bootloader (Thanks @thatha)
Enable developer options by going to Settings > About Tablet > Software information > and tap "build number" 7 times
Go to Developer options, turn on OEM Unlock (If it doesn't show up, skip to Part III and then come
Turn off Tab A7 Lite, connect it to the computer while holding Volume Up and Volume Down keys until you see the bootloader screen
Long-press Volume Up key to enter Device Unlock mode
Press Volume Up key to confirm and unlock the bootloader
III. Create your device's patched boot (You can skip this if you have one of the 3 devices with the files in part IV.1 below.)
Download your firmware from samfirm or other source (I didn't have to do this, so I can't instruct on it)
(On PC) Extract boot.img.lz4 from Stock AP...tar file, then copy it to Tab
(On Tab) Install ZArchiver to extract boot.img from boot.img.lz4
(On Tab) Install Magisk and patch the boot.img that you have just extracted from step 3
(On PC) Copy magisk_patched.img (in Tab\download) to pc, rename it to boot.img
(On PC) Use 7zip to pack boot.img from step 5 into boot.img.tar
IV. Root Tab A7 Lite
Download correct boot.img.tar for your device (For T220XXU1AUJ1 it's magisk_patched-23000_acKsR.tar), it will probably be a zip, if so you'll need to unpack it to a tar (you can use 7zip for that). The two T225 files were pulled from here. The T220 file (my device) was pulled from here. I inserted and attached them for future proofing and to make it easier for you.
You can find your device under Settings > About Tablet > Software information > Build Number. Mine is a Wifi model Tab A7 Lite, model T220 4GB/64GB, my build is T220XXU1AUJ1.
The files below are direct links to the attachments in this thread (take CAREFUL note of the T220 or T225 in the name - they are different).
For T220XXU1AUJ1:
https://forum.xda-developers.com/attachments/magisk_patched_t220xxu1auj1-23000_acksr-zip.5544869/
For T225XXU1AUJ1:
https://forum.xda-developers.com/attachments/boot_t225xxu1auj1-tar.5544889/
For T225XXU1AUL1:
https://forum.xda-developers.com/attachments/boot_t225xxu1aul1-tar.5544891/
For T220XXU1AUL2:
https://forum.xda-developers.com/attachments/boot_t220xxu1aul2-tar.5547521/
If you don't have one of the above 3 devices, then follow the Part III guide above to create the correct boot.img.tar file. DON'T FLASH THE ABOVE IF IT IS NOT YOUR DEVICE!
Get Odin 3.14.1. (All 3.14.4 are FAKE!) The exact one I used was Odin3 v3.14.1_3B_PatcheD. Get it from here ONLY! https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
I also attached the same file to this post. Download from the other page if you don't trust me.
Boot into Download Mode
(If you're stuck at SetupConnection in Odin, it's because you have to run it from Download Mode, it won't run while device is on.)
- Power off device
- Hold Volume Up & Volume Down buttons at the same time, connect USB cable, keep holding until you see the screen.
- Press Volume Up to go to Download Mode
Here's a video for this device on how to do it and what it looks like (credit goes to the maker of the video, not me):
Open Odin as Administrator (Right-click > Run as Administrator)
Click AP and find the file magisk_patched-23000_acKsR.tar (for T220XXU1AUJ1). NOT THE ZIP. And not the raw boot file(s). Has to be the tar.
If successful, it wlil say this:
<ID:0/008> Added!!
<ID:0/008> Odin engine v(ID:3.1401)..
<ID:0/008> File analysis..
<ID:0/008> Total Binary size: 32 M
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> NAND Write Start!!
<ID:0/008> SingleDownload.
<ID:0/008> vbmeta.img
<ID:0/008> boot.img
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Removed!!
<ID:0/008> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Device will reboot. It will say bootloader unlocked continue, so press Power button like it asks. You will see a screen with red text warning you it's been altered.
It will not boot. Don't worry it will reboot again, same thing as step 6. Now it fails and asks you to Factory Data Reset. Ignore the errors it's telling you, and Yes, go ahead and click Factory Data Reset (you have to).
It will go through step 6 again, this time, after a few minutes it will boot up into Android and prompt you to setup device. Success!
V. Install/Update Magisk on Tab A7 Lite
Magisk will exist in apps, but clicking on it asked me to update but nothing happened. If that's the case for you too, then:
Download Magisk latest version from their official Github. (DO NOT DOWNLOAD FROM ANY OTHER SOURCES!) I included the apk from the github page here for future proofing and reference, I am using Magisk 24.1 which worked.
Install the APK. Open file manager if you need to and then find it in Downloads or wherever you downloaded it.
Open Magisk, it will ask you to update. Choose "Direct Install (Recommended)" and then click Let's Go in the top right.
It will flash the image and then say All Done!, then you can click the Reboot button in the bottom right.
You can now check root by installing any app that needs root, for example Titanium Backup which is an essential one for me. There's also OandBackupX, which is a free and open source fork of Titanium backup.
You will be greeted with a Superuser popup if you are rooted, so grant permissions and you can see you are rooted! Congratulations!
Nothing special is needed on reboot, if you ever reboot your device, it just reboots as normal and stays rooted. Congratulations on completing the guide! Please remember to like this if you liked the guide (only if you liked it), so I know I am helping.
VI: Install LSPosed (Successor to Xposed) on Tab A7 Lite
Download LSPosed latest version from the official Github.
- Make sure to choose the Zygisk version (e.g lsposed-vx.x.x-xxxx-zygisk-release.zip).
- Why Zygisk? Because Riru is retired. You don't need it anymore.
- Don't worry about downloading any Zygisk or Riru. Riru is retired and Zygisk is now integrated in Magisk.
Copy the zip file to your device.
Open Magisk, go to Modules, click Install from Storage, and find the zip you just copied for lsposed zygisk version.
Click Reboot button in the bottom right when it's finished.
VII: Activate Zygisk (Successor to Riru) on Tab A7 Lite
You're not done yet. Now go into Magisk, click Settings button in the top right.
Scroll down and enable Zygisk (Beta).
Below that, enable Enforce DenyList.
Below that, click Configure DenyList.
In the top right, click the 3 dots menu and check the box Show System Apps.
Select Google Play Services by checking the box.
Tap on Google Play Services to open all the items for it, and enable all the items for Google Play Service.
For anything else you deny in the DenyList that you configure, Zygisk will not work for it, because you denied it. So in the future if you want to disable Zygisk for anything else, this is how. But if you don't konw what this means, don't worry about it.
That's it! Now go ahead and reboot your device by holding the Power button for a couple seconds and clicking Reboot (If you choose Power Off by accident then it won't reboot without you turning it back on )
On reboot, it will ask if you want to add a home page shortcut. Choose YES, because it won't show in your apps, so you want an easy way to access LSPosed.
Open Magisk and click on Modules to see that LSPosed is active! Congratulations you now have LSPosed installed and working!
VIII: Xposed Modules for LSPosed
I recommend a couple mods for LSPosed. There aren't a ton yet for Android 11 and less for Android 12.
Browse the Xposed Repository, because you apparently can't from within LSPosed.
- Note - Don't use any modules you don't know what they do.
Recommended Module: GravityBox [R] (For Android 11) - Allows you to do lots of customizations. (Enable dark theme for GravityBox under the About at the bottom, after you activate it using steps 5 and 6.)
Recommended Module: DarkTricks - More customizations and tricks. Nothing "dark" about it, just the user's name.
To install, just copy to your device, and browse to the apk through file manager, and install it.
When you install, you will get a notification, "Module is installed but not activated". Either click on the notification and Enable, or open LSPosed, go to Modules, click on the greyed-out modules, and click Enable on each module you want to activate.
Then reboot to activate the module. If you don't reboot, then the module isn't going to work when you click on it, but it will after you restart.
XI: Install Shamiko (Magisk Hide Alternative) & Momo [Both In Development ALPHA (Pre-Beta)]
Magisk Hide was permanently removed from the latest versions of Magisk. The alternative is Shamiko, although it's still in development. Install at your own risk.
Momo simply checks your environment for your knowledge. It can help detect if you successfully hid Magisk.
Shamiko Development Version: https://t.me/magiskalpha/438
Momo Development Version: https://t.me/magiskalpha/379
Install Shamiko using Magisk like you did in Part VI: Go to Modules, Install from Storage, Find the Shamiko .zip file, Install, Reboot.
Install the Momo APK. You can open it right away.
Official Telegram: https://t.me/s/magiskalpha (Find latest versions here on the Telegram page. I had to use actual Telegram to download them. So I attached the apks above.)
More details on Shamiko & Momo: https://xiaomiui.net/a-new-method-for-hiding-root-is-on-the-way-2720/
I will add more to Part XI: Mods later
Click to expand...
Click to collapse
Also there is an unofficial TWRP for 10" SM-T500 here https://www.mediafire.com/file/khmq9jajz16gidq/SM-T500-TWRP_3.5.2.tar/file Perhaps this can be modified for the smaller 8.7" SM-T220 model ? I do not have the skills, if you have any luck please post a reply here, thanks.
Added more xposed module recommendations, and a new section for tweaks.
vertab7 said:
Also there is an unofficial TWRP for 10" SM-T500 here https://www.mediafire.com/file/khmq9jajz16gidq/SM-T500-TWRP_3.5.2.tar/file Perhaps this can be modified for the smaller 8.7" SM-T220 model ? I do not have the skills, if you have any luck please post a reply here, thanks.
Click to expand...
Click to collapse
That TWRP didn't work, will need to be modified. Outside my scope. If someone gets it working, will add to this tutorial.
Added section (section V and reordered them) for removing the bootloader warnings on phone boot.
"Added section (section V and reordered them) for removing the bootloader warnings on phone boot."
Sweet, that will keep the wife from side eyeing me when she boots her Tab.
Worked like a charm.
Thank you again for your efforts!
is the magisked patch the boot.img.tar?
master12311 said:
is the magisked patch the boot.img.tar?
Click to expand...
Click to collapse
No it's the one that is specific to your device. If you do not use the right one, then you will brick your device. Check section IV.
xbt- said:
No it's the one that is specific to your device. If you do not use the right one, then you will brick your device. Check section IV.
Click to expand...
Click to collapse
yeah thanks bro i was about to brick it
master12311 said:
yeah thanks bro i was about to brick it
Click to expand...
Click to collapse
Glad to help. My guide is pretty comprehensive, just make sure to read everything.
Related
I am making this tutorial as I have had multiple versions of the LG LTE Leon and have used many firmware versions. I have created a stable method that has the least issues as I have had trouble with the latest firmware (MS34510f) disabling my root privileges. I have created a MEGA account specifically for all of the files necessary to complete this operation and have your device run smoothly. So, please follow my instructions exactly as stated and you should not have any issues. THIS PROCESS WILL REMOVE ALL DATA NOT SYNCED, DO READ BELOW NOTES IT IS VERY BENEFICIAL
Important Notes:
+This process will wipe all data that is not synced, it is important to ensure that no newer LG process are still on the device. Some might argue to leave data, to that I say good luck keeping your root and tethering without the device becoming suspiciously unstable.
+ I am not GUARANTEEING this will work on every model, but I have had an extremely high success rate with all Leon versions.
+ In this tutorial the process in which I remove Kingroot and replace it with SuperSu is for system stability. I find that most root functions I use seem to not work properly. (Wifi Tether Router and many others). So, I do recommend doing so.
+After the new OS is installed a MetroPCS splash screen will appear even if you do have T-Mobile. DO NOT BE ALARMED this firmware will not limit any functionality you had before, it will even help with tethering functionality.
Tutorial:
Let's Begin.
1. Download the link posted to obtain required files for this tutorial
Link: https://mega.nz/#F!PM4CQRqb!92kgIOnD0ZBY-8HVbtTwGQ
2. Open up LGFlashTool2014.exe
Begin by copying settings posted below, then click "normal flash"
3. Next click the "START" button
4. At this time, I recommend you verify all sync settings are to your liking and that all personal info needed is backed up
a. You have the option to throw all of your personal documents/pictures onto your SD card and removing it appropriately
(Go to: Settings - Storage - [scroll down to] Unmount SD card)
b. Next, navigate to Settings -Backup & reset [leave options default; both checked off] - Factory data reset - reset phone
c. Once reset it will most likely reboot, wipe, and then back to a OS. Now, you will Power Off entirely (make sure it is not plugged in so it will not go to charging mode)
d. Here is where we will hold down the Volume Up button with the phone unplugged from your PC. Then you must plug the USB into your phone.
e. A black screen with white text should post onto your screen, here we will continue to step 6
note: If this screen does not appear please power off and retry step d.
6. Next, follow the posted settings. Make sure to click the "Clear phone Software update Registry" button Then click "OK"
7. A new screen will arrive, and should begin the firmware download process. At this time it will take a few minute to load and should reboot to a fresh OS.
8. With the new OS in place, you can either follow the setup tutorial now or skip through for a later setup.
note: you can now insert your SD card
9. In the tools folder of the folder you downloaded copy the "mrw" folder to the Main Storage folder of your phone
10. Now copy the Kingroot apk to your downloads folder located on the main storage.
11. Go to Settings - About Phone - Software Info
At this time click the build number box a few times until it says you are a developer
12. Hit back until you are at the Setting menu, click on Developer options and check off "Stay Awake" and "Enable OEM Unlock" as well as "USB Debugging"
13. You may now run Kingroot, if it does not install root the first time it should flawlessly install the next.
14. After root is obtained, please go to your home screen and click the "Google Search" widget. Press Update Google Services and let it run. After that has been updated search for terminal emulator and install.
note: If the Play Store is acting fishy and force closing while typing in the search bar do not fret it will be fixed after reboot in further instruction
as an allternative use the jackpal.androidterm-1.0.70-71-minAPI4.apk provided in the "tools" folder
15. Open terminal and in a new window type: Su
16. Allow root usage and at this time type: sh /storage/emulated/0/mrw/root.sh
17. It will run with a few failed messages do not worry it should open SuperSu momentarily
18. Once SuperSu opens up allow it to update binaries using the "NORMAL" option but DO NOT REBOOT YET
19. At this time either download TWRP Manager from the play store or alternatively use the com.jmz.soft.twrpmanager-7.5.1.3-82-minAPI11.apk provided in the tools folder
20. Install and open TWRP Manager. Once opened click on device name and scroll until you see "LG Leon LTE (c50)"
a. Click on Recovery Version to Install and select "twrp-2.8.7.0-c50.img"
b. next click "Install Recovery" and if prompted for verification of install path and for install version select "YES" & "NORMAL"
21. After the TWRP setup is complete it may prompt you to reboot, if not click the arrow in the top left of the TWRP Manager screen and scroll down to "Reboot" and select "Reboot device"
22. After Reboot click TWRP Manager and verify a SuperSu prompt comes up if it hasn't already before the boot
At this point the device should be running smoothly. From here I prefer to do the following steps.
My Personal Setup after new install:
+Personally I like to install use a Root Uninstaller (I use 3C Toolbox Pro) and Uninstall and Backup all MetroPCS BloatWare including the Metro Browser.
+I also access the Hidden Menu by using the Dialer and Dial "2776348*#*"
- I scroll down to ApnUnlock and click to "Unlock APN"
- Then I navigate to Settings -Tethering & networks - Mobile Networks (I check off roaming data) - Access point names
--I then select the top APN and edit APN Type to: default,supl,mms,dun
---I click save from the top right selection, then turn on and off airplane mode
+If you are and Xposed user download "xposed-v79-sdk22-arm.zip","xposed-uninstaller-20150831-arm.zip", and "XposedInstaller_3.0_alpha4.apk" from: http://forum.xda-developers.com/showthread.php?t=3034811
-install the Xposed Installer, then Go to TWRP Manager, use reboot to recovery and from there click install and navigate to the "xposed-v79-sdk22-arm.zip" and install and reboot, it will reboot with a installing screen before your home screen, takes 5 minutes.
+I also use this AMAZING app "Wifi Tether Router", it is the only tethering app I use that works consistently (if you have an unlimited data plan). I get 30mbps up and down, playing many multiplayer games off my PC and PS4 averaging ping as low as 30 ! Setting I use for our device are in a post I created here: http://forum.xda-developers.com/leon/help/unlimited-metropcs-t-mobile-tether-t3290180
---------------------------------------------------------------------------------------------------------------------------------------------------------------
Special Thanks to:
MrW0lf from www.W0lfdroid.com for the Kingroot to SuperSU scrip
Numerous users on the XDA forums I pieced all of this information with
Fabio Grasso for making the amazing Wifi Tether Router
Team Win for being creating an awesome utility that has saved me from numerous bricks creating a stable method
Xposed and the creators of awesome additions such as Lolistat, Lucky Patcher, Max Lock, and SNAPPREFS
Any feedback? Did I do Okay? Questions? Let me know!
Worked for me on T-mobile H345
Worked for me on T-mobile H345 any way to install a H340 firmware on it? I GeT a Binary not authorised when trying to flash.
kodacy said:
Worked for me on T-mobile H345 any way to install a H340 firmware on it? I GeT a Binary not authorised when trying to flash.
Click to expand...
Click to collapse
Apologies for the late response, I never received a notification of your posting. I would not recommend that as I believe the H340 has a different "radio" driver or cellular chip, If I'm not mistaken the H340 isn't even LTE, the H345 is. In that case it may be possible. One thing I suggest doing before wasting your time in using any other ROM is googling H345 vs Ms345, typically the phonemore.com results will provide you with an abundance of hardware specs and let you know if they're different! Just be weary of the newest MS34510f_00.KDZ firmware I believe it has an active unroot process I've had some stability issues. I am using MS34510D_00.KDZ for months and have had no issues whatsoever! Again, I'm sorry I got back to you so late, let me know how everything goes!
brad2192 said:
Apologies for the late response, I never received a notification of your posting. I would not recommend that as I believe the H340 has a different "radio" driver or cellular chip, If I'm not mistaken the H340 isn't even LTE, the H345 is. In that case it may be possible. One thing I suggest doing before wasting your time in using any other ROM is googling H345 vs Ms345, typically the phonemore.com results will provide you with an abundance of hardware specs and let you know if they're different! Just be weary of the newest MS34510f_00.KDZ firmware I believe it has an active unroot process I've had some stability issues. I am using MS34510D_00.KDZ for months and have had no issues whatsoever! Again, I'm sorry I got back to you so late, let me know how everything goes!
Click to expand...
Click to collapse
No problem thank you for your help!
will i still have metro service?
Port(usb or serial) not found! tried on, off, update mode, changing ports and unplugging every other port. any thoughts?
kap10nuka said:
Port(usb or serial) not found! tried on, off, update mode, changing ports and unplugging every other port. any thoughts?
Click to expand...
Click to collapse
Same here (firmware update) usb not detected when using the S/W update tool
After going all the way through this guide with a T-Mobile Leon, I do indeed have a Metro PCS ROM and root, which is great! Unfortunately, it also refuses to acknowledge my T-Mobile SIM. In fairness, I did not even insert a SIM for the first time (just got the phone) until the end of the process, but it shows as carrier locked which is significantly less than useful. I'll flash back to a TMO rom and put the SIM in to double check, but it's quite a bummer. Great job on the guide otherwise, though! It definitely did what it says on the tin; I have root and apart from the SIM lock which may be my fault somehow it works great.
Hey bud those links are no longer valid know where i can get them?
Hi guys,
I'm new on the forum but I follow you for a long time.
So, my purpose is writing a detailed and simply to read guide to Root and install Xposed on tablet Asus TF103C under Lollipop 5.0 update.
I've tested the following procedure and it works for me.
ROOT
1) enable USB debug in developer options
2) download "ZenFoneRootKit_20150528.zip" and extract it
Download link: ZenFoneRootKit_20150528.zip or just google it
3) with tablet turned on, run Root.bat in the folder
4) the device will reboot in fastboot and root automatically, it may take few minutes
XPOSED
1) Download "xposed-v85-sdk21-x86.zip", "xposed-uninstaller-20150831-x86.zip"*, "XposedInstaller_3.0_alpha4.apk" in INTERNAL memory of tablet.
Download links:
FRAMEWORK
UNISTALLER
APK(source: XDA forum)
2) Download "Temporary TWRP.zip" (temporary recovery) and extract it in C:/ on PC
Download link: Temporary TWRP
(source: 4pda.ru forum)
3) Enter in fastboot (press DOWN button+POWER untill Asus logo appears, then keep pressing only DOWN button)
4) Run "Launcher.bat" located in Temporary TWRP folder (extracted previously)
5) Temporary TWRP recovery will start on device:
Allow modifications when asked you
Enter in "Install" section >
Explore manager, find the folder where is xposed-v85-sdk21-x86.zip > select and flash it
reboot system
6) After optimizing apps, install Xposed apk ("XposedInstaller_3.0_alpha4")
*in case of bootloop, repeat procedure flashing "xposed unistaller" instead
I hope this could be useful.
List of stable Xposed modules
Here below a little list of Xposed modules that work for me on Asus TF103C under Lollipop update:
BootManager
EnhancedToast
GravityBox [LP]
Greenify
Lucky Patcher
MinMinGuard
Native Clipboard
NotifyClean
Youtube Background Playback
Network Speed Indicator
Working like a charm :victory:
Thanks again!!! :highfive:
prosquos said:
2) download "ZenFoneRootKit_20150528.zip" and extract it
Download link: ZenFoneRootKit_20150528.zip or just google it
I hope this could be useful.
Click to expand...
Click to collapse
This link requires a decryption key. ....
Edit: Google the file name and the first result is a GDocs link that worked for me.
Sorry for the incovenience, I've just updated Mega link, now it doesn't require the decription key.
So, i did all the steps to root it, but in fastboot it only shows "FASTBOOT CMD WAITING...", and if i connect it and THEN open Boot.bat, it shows "no valid installer medium found site".
Any suggestions? I need to get the junkware out of it, and optimize it a bit :C
Ah, and in the CMD i get this:
'
' Rooting, please be patient ..
'
'
< waiting for device >
Click to expand...
Click to collapse
Also adb devices shows nothing.
worked loading into clockwork once now it just says to many lines on pc cmd then loads up with a black screen nothing happens just hangs
Hello.
I know that is an old thread. I got this tablet that has this unresponsive screen problem. I wanted to try flashing a custom lollipop to see if the problem persist. Tryed everything i found on the web. Nothing worked. Did anyone managed to upgrade it?
Tnx for all replies.
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
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?
This guide is based on the original PewPewK post.
Which, in turn, was inspired by TopJohnWu's 'Samsung (System-as-root)' Magisk Installation Guide
It is an extended walk through aimed at ALL users, meant specifically for the SM-T720 (Tab S5e) BUT specifically meant to:
UNLOCK THE BOOTLOADER
INTRODUCE ROOT
RESTORE STOCK/RELOCK THE BOOTLOADER
Because of the community support, the options available to you have become numerous!
So if you're looking to squeeze EVERY inch out of your tablet, search the thread for suggestions or see the links below:
Go HERE if you are interested in custom recovery (e.g., TWRP).
Go HERE if you are interested in custom ROMs or kernels.
ROOT WARNING
Introducing root and further tampering may lead to unfavorable performance and/or shortened device lifespan.
In extreme circumstances, it may render your device OR specific hardware components unstable or non-functioning.
By following this guide, you ACKNOWLEDGE these risks and release AHE_XDA, XDA and its CONTRIBUTORS of ANY and ALL responsibility.
WARRANTY WARNING
In many states, countries, provinces and territories, introducing root voids device warranty (manufacturer's and/or third-party). Please consult your regional Samsung office, place of purchase or third-party warranty company to determine if these terms are applicable to you.
ALTERNATIVES TO ROOT
If you are looking to maintain warranty and continue access to Samsung-specific features, consider disabling or uninstalling unwanted applications via the Android Debugging Bridge (ADB).
TiTiB, a genius in his own right, has a thread dedicated to the Tab S5e and bloat removal without the cost of warranty.
Visit it HERE and click 'Thanks!' if it helped.
Known Issues (January 31, 2020)
KNOWN ISSUES (January 31, 2020)
Where's Recovery?
Explanation: TWRP (custom recovery) is NOW available. Please visit TeamWin for instructions.
Workaround: Resolved as of August 6, 2019.
Magisk shows as 'Not Installed.'
Explanation: Magisk, due to the changes to the recovery partition in Android Pie & above, will not boot automatically. It requires user intervention.
Workaround: To enable root access, be prepared to hold 'Volume Up' and the 'Power' keys on EVERY BOOT or REBOOT.
WiFi stopped working after installing 'magisk_patched.tar' with Odin.
Explanation: Cause unknown as of January 31, 2020.
Workaround: In some cases, after introducing root ('magisk_patched.tar'), WiFi may stop working. If this happens, do the following:
From the app drawer, go to Settings > Connections > Wi-Fi.
Highlight and select your WiFi network.
Long press the network name and select "Forget Network".
Wait 3 to 5 seconds.
Press and click on the network in which you asked Android to forget.
Re-enter your password.
If entered correctly, WiFi will resume connectivity.
"Your phone is locked because the payment service was uninstalled."
OR
Only official released binaries are allowed to be flashed (vbmeta).
Explanation: To protect against various threats (e.g., compromised data, theft or root), Samsung, as of December 2017, introduced a series of low-level initiatives to LOCK the device should ANY part of Knox be compromised. These initiatives are frequently referred to as 'KG' (KnoxGuard) or 'RMM' (Remote Monitoring and Management).
Further details can be found HERE.
Workaround: A workaround now exists, thanks to @ianmacd, but requires TWRP to be installed followed by the Samsung multi-disabler file.
If you do NOT intend to install TWRP, precautions MUST be taken not to freeze, disable or remove the following files:
'Payment Services' (com.samsung.android.kgclient)
'KnoxGuard' (knoxguard.apk)
In most circumstances, the issue will present itself immediately after the application(s) is frozen, disabled or removed. In rare circumstances, only after a device restart.
PRO-TIP: Do NOT reboot unless absolutely necessary; opt to power down the device.
Should you encounter EITHER error, you will need to boot into 'Download Mode', revert to original factory settings and verify your Google account to avoid an FRP LOCK.
To enter 'Download Mode' and recover from the error:
Connect a USB cable to your Laptop/PC.
With power-off on the device, hold down BOTH 'Volume Up' and 'Volume Down'.
Connect the USB cable to the device, while holding down both volume keys, and press 'Power'.
If done correctly, the device will boot to 'Download Mode'.
My Streaming Service won't log me in, no longer provides HD viewing or doesn't allow offline downloads.
Explanation: Widevine is a digital rights management platform used by major streaming companies to prevent piracy.
Low-level details can be found HERE.
Workaround:
Resolved by @ianmacd and his 'liboemcrypto disabler' via Magisk Manager and/or Custom Recovery (e.g, TWRP) as of April 4, 2018.
NOTE: If you installed TWRP and flashed the Samsung multi-disabler file, this issue is resolved of as December 13, 2019.
If you do NOT intend to install TWRP, log-out and uninstall your streaming application(s). With root introduced and magisk enabled, download 'liboemcrypto' from 'Modules' within Magisk Manager. You will be asked to restart after installing the module. Do this and re-enable Magisk on boot. Sideload your streaming application(s) from a source OUTSIDE the Playstore. Log in and resume streaming.
Items are ADDED and UPDATED as they are discovered, solved or a workaround is introduced. Please message me directly if something is missing.
Requirements & Instructions
HARDWARE & SOFTWARE REQUIREMENTS
Windows Laptop/PC with more than 25GB of available storage space
SM-T720 Tablet (Galaxy Tab S5e)
Samsung USB Type-C Cable (as found in the original packaging)
WIFI connection (and if necessary, login details)
SECTION ONE - LOG-OUT & BACK-UP YOUR DATA
Log out of your Samsung and Google account(s).
Back-up ANY and ALL data as following this guide will result in COMPLETE data loss.
SECTION TWO - DOWNLOAD THE RIGHT UTILITIES
In order to root, you require several utilities.
They are as followed:
Samsung USB Drivers - Provides connectivity between Laptop/PC and your device.
7-Zip - An open-source file archiver.
Odin 3.13.1 - Used to flash original or custom Samsung firmware.
Frija - Downloads the latest available Samsung firmware.
Magisk Manager (APK) - Helps obtain/manage and extend root options. Download the latest .APK (Application Package).
Click on the UNDERLINED NAME of the above utilities to download them to your local Laptop/PC.
PRO-TIP: Create sub-directories, like pictured below, and organize your downloads accordingly:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PRO-TIP: Consider a donation to Frija, Magisk or your favorite developers as a token of goodwill and to help ensure future development efforts.
SECTION THREE - DOWNLOAD THE RIGHT FIRMWARE
In order to root or, at a later time, return to original factory settings; you MUST have a local copy of firmware.
This requires knowing our CSC; a three letter code that Samsung devices use to comply with local telecommunication standards and determine device-specific features or updates.
To locate your CSC, perform the following:
On your device, go to 'Settings'
From 'Settings', scroll down to 'About Tablet'.
Press on 'About Tablet' followed by a press on 'Software Information'
Scroll downwards until you see 'Service Provider SW Ver.'
There are three lines.
The third line will read similar to the following:
TUR//
Those three characters (e.g., TUR) represent the CSC code for your region.
PRO-TIP: Your CSC may OR may not be the same as the example; that's expected and perfectly normal.
Open Frija, which you downloaded under 'Section One', and input your model and CSC.
Make sure 'Auto' is selected and click on 'Check Update'.
If the right values are inputted, Frija will look similar to the following:
Click on 'Download' and select a location on your Laptop/PC.
When the download is complete, Frija will verify and decrypt the firmware.
Once finished, Frija will look similar to this example:
PRO-TIP: If you can't get Frija to open or download, right click and select 'Run as administrator'.
SECTION FOUR - UNLOCK THE BOOTLOADER
THIS STEP WILL REMOVE ALL DATA FROM YOUR DEVICE. PLEASE REFER TO 'SECTION ONE' FOR MORE DETAILS.
Power off the device.
Power on your Laptop/PC and login into your Windows account.
Connect the USB cable to your Laptop/PC but NOT to your device.
On the device, hold the 'Volume Up' and 'Volume Down' keys at the SAME time.
Connect the USB Cable from your Laptop/PC to the device.
You MUST hold BOTH keys during AND after inserting the USB Cable to receive the following warning:
PRO-TIP: In SOME cases, you may also need to hold 'POWER' as well.
To continue towards unlocking your bootloader, hold the 'Volume Up' key for approximately 4 to 5 seconds (or until the screen goes black).
After 4 to 5 seconds have passed (or if the screen went black), release the 'Volume Up' key and you will be presented with one last warning:
Press and click on the 'Volume Up' key to finalize your decision.
The device will factory reset and from now on, until the bootloader is re-locked, you will receive this warning:
Leave the device to reinitialize. This will take approximately three minutes. The device will erase itself and you will notice several reboots. Afterwards the only activity you'll see is a pulsing 'SAMSUNG' logo. Eventually you will be presented with the 'Let's Go!' set-up screen. Set the device aside for now.
SECTION FIVE - INSTALLING 7-ZIP
If you correctly followed the first FOUR sections, you now have the required utilities, firmware and an unlocked bootloader.
In order to proceed, you MUST install 7-Zip to extract and manipulate key files required for root.
If you have prior experience with 7-Zip or an alternate compression manager, SKIP this step and proceed to 'SECTION SIX'.
It IS enough to double-click the EXECUTABLE and install it; you need NOT configure anything.
However, for a visual reference, follow this LINK to see 7-Zip in use.
Alternately, for technical support and assistance SPECIFIC to 7-Zip, use this LINK. Search thoroughly before posting.
SECTION SIX - EXTRACTING FIRMWARE
Like the CSC code, mentioned in 'SECTION THREE', the name of your download will differ slightly but 'SM-T720' and 'AP_T720' will be in the file name:
Using 7-Zip, you must extract the following file:
AP_T720XXU1ASF1_CL15813856_QB24038915_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar.md5
From the following ZIP container:
SM-T720_1_20190603182427_gegcc1ebw1_fac.zip
Right click on your ZIP container, navigate to '7-Zip' and, from the sub-menu, select 'Extract Here'.
7-Zip will begin to decompress the necessary files and will result in the following output:
Delete ALL files except for the following:
SM-T720_1_20190603182427_gegcc1ebw1_fac.zip
AP_T720XXU1ASF1_CL15813856_QB24038915_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar.md5
Rename the extension of 'AP_T720XX.....tar.md5' to 'AP_T720XX.....tar' and ignore the warning provided by Windows.
When finished, your folder contents will look similar to this:
The AP file is required for root.
PRO-TIP: Keep the ZIP container should you ever want to revert back to original factory settings. If not, delete it and download again later using Frija.
SECTION SEVEN - ENABLE WIFI, TRANSFER FILES & INSTALL MAGISK MANAGER
In 'SECTION FOUR', the device was left to reinitialize.
This means you have a device that requires set-up:
Do NOT log into your Samsung or Google account. The ONLY thing required is WIFI:
PRO-TIP: WIFI and Magisk work together to help achieve root access, provide updates and for module repository access.
Once you've arrived at the home screen, you need to enable 'Developer Options' to ensure the bootloader is unlocked.
To verify your bootloader is unlocked, perform the following:
On your device, go to 'Settings'.
From 'Settings', scroll down to 'About Tablet'.
Press on 'Software Information'.
Scroll downwards until you see 'Build Number'.
Tap 'Build Number' seven times to enable 'Developer Options'.
Press the back button on the navigation bar to return to 'Settings'.
Underneath 'About Tablet', you will now see 'Developer Options'.
Open this and locate 'OEM Unlocking'.
If you've followed the outlined steps, your screen should match this example:
PRO-TIP: If your screen does NOT match the example, it is possible you are NOT connected to WIFI or you did NOT successfully unlock the bootloader. If all these conditions are true, restart the device and check again. If the issue persists, create a NEW response in the thread.
Now connect the device to your Laptop/PC and, when prompted, 'Allow access to tablet data'.
Using Windows Explorer, copy the following files to the 'Download' folder of your device:
MagiskManager-v7.3.2.apk
AP_T720XXU1ASF1_CL15813856_QB24038915_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar
Due to the size of the AP file, this may take several minutes on a low-end Laptop/PC.
Once the copy is complete, go to your device and double press on 'MagiskManager-v7.3.2.apk' to initiate the install process.
PRO-TIP: Due to changes introduced in Android Oreo, you MUST allow permission to install applications (APKs) not obtained from the PlayStore.
Click on 'Settings' to open the 'Install unknown apps' screen and toggle 'Allow from this source' on.
Press the back button on the navigation bar to allow the installation:
SECTION EIGHT - PATCH YOUR AP FILE
Open your app tray by swiping up and open Magisk Manager.
You will see a RED QUESTION MARK and the following error:
'Magisk is not installed.'
Click on 'Install' and, when prompted by Magisk, select 'Install' again:
Magisk will provide another prompt:
Choose 'Select and Patch a File' to proceed.
Magisk will now prompt for device access:
Click on 'Allow' and the internal Device File Explorer will open to the 'Recent' tab:
Click on the top app bar and select 'Downloads' to find your AP file:
And then:
Once inside the 'Downloads' folder, select your AP file to begin the flash process.
Once the flash process is complete, the status on the top title bar will change from 'Flashing' to 'Done!':
SECTION NINE - RETRIEVAL & DISSECTION
With our AP file patched by Magisk, you must now locate and transfer it back to our Laptop/PC.
If you have not already done so, reconnect the device to your Laptop/PC:
Open Windows Explorer, double-click on 'Tab S5e', double-click again on 'Tablet' and open the 'Downloads' folder:
Under 'Downloads', you will see THREE files:
AP_T720XXU1ASF1_CL15813856_QB24038915_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar
magisk_patched.tar
magisk_install_log_2019-07-10T225845Z
PRO-TIP: 'magisk_install_log' is an output of the AP file patching process. If you encountered ANY errors, keep a copy and raise a question in the thread.
Delete 'AP_T720XX.....tar' and copy 'magisk_patched.tar' back to your Laptop/PC; preferably to the 'FIRMWARE' sub-directory suggested in 'SECTION TWO'.
Due to the size of the 'magisk_patched.tar' file, this may take several minutes on a low-end Laptop/PC.
Once the transfer is complete, let's make room in our 'FIRMWARE' folder by deleting the 'AP_T720XX.....tar' file.
This should leave you with TWO files:
SM-T720_1_20190603182427_gegcc1ebw1_fac.zip
magisk_patched.tar
Move OR delete the 'SM-T720.....fac.zip' container so you can focus exclusively on 'magisk_patched.tar'.
With NO files left except for 'magisk_patched.tar', you must now use 7-Zip again to extract its contents.
PRO-TIP: Refer to 'SECTION FIVE' if you need a refresher on 7-Zip.
Right-click on the 'magisk_patched.tar' container, navigate to '7-Zip' and, from the sub-menu, select 'Extract Here'.
Once all files are extracted, your output will look similar to, if NOT exactly like, this:
Now DELETE these files:
dtbo.img.lz4
magisk_patched.tar
modem.bin.lz4
persist.img.ext4.lz4
system.img.ext4.lz4
userdata.img.ext4.lz4
vendor.img.ext4.lz4
In order to have the following:
meta-data [FOLDER]
boot.img
recovery.img
vbmeta.img
If done correctly, your folder output will look like this:
SECTION TEN - CREATE YOUR TAR
In 'SECTION NINE', you organized the following list of files/folder:
meta-data [FOLDER]
boot.img
recovery.img
vbmeta.img
Using Windows Explorer, navigate to your 'Firmware' folder (or whatever location you used).
Now, using 7-Zip, you need to compress these files into a TAR container.
This means you must select ALL files.
This can be achieved by using CRTL + A on your keyboard or simply by highlighting them all with a left-click:
Right-click on the selected files, navigate to '7-Zip' and, from the sub-menu, select 'Add to archive...':
If done correctly, the following screen will present itself:
Only THREE things MUST be done to complete our TAR:
Change the filename to 'magisk_patched' WITHOUT quotations
Change the 'Archive format' to 'TAR'
Click on 'OK' to confirm your decisions and begin compression:
PRO-TIP: If, for ANY reason, you don't want to keep these files, you can select 'Delete files after compression' before clicking on 'OK'.
With this step complete, you are left with the following output:
SECTION ELEVEN - DOWNLOAD MODE
Using the 'Power' key on your device , select 'Power off':
Disconnect the USB cable or the device will switch to 'Charging Mode':
On your device, hold 'Volume Up' and 'Power' together until the 'Android Recovery' screen appears:
'VOLUME UP' will navigate upwards, 'VOLUME DOWN' will navigate downwards, and 'POWER' will highlight and confirm your choice.
PRO-TIP: You may have to press 'POWER' twice.
Highlight and select 'Reboot to bootloader' to properly put your device into 'Download Mode':
Reconnect the device back to your Laptop/PC.
SECTION TWELVE - ODIN PREPARATION AND FLASH
Now, because recovery is unavailable, you must use Odin to flash your TAR file to introduce root.
In 'SECTION TWO', you downloaded Odin and created a folder for it.
You must now go to that folder, or whatever folder you opted to use, and decompress Odin.
Right-click on the 'Odin3_v3.13.1.zip' container, navigate to '7-Zip' and, from the sub-menu, select 'Extract Here'.
This will create a sub-directory called 'Odin3_v3.13.1'.
Double-click and you will be presented with the following output:
Double-click on 'Odin3 v3.13.1.exe' to launch the application.
You will receive a prompt written in both English and Korean. Click 'OK' to close the warning.
With Odin open, locate and click on the second tab called 'Options' and uncheck 'Auto Reboot':
When you click on the 'AP' button, Windows File Explorer will automatically launch.
As per 'SECTION NINE', and using Windows File Explorer, navigate to the location you created and saved 'magisk_patched.tar'.
Double-click 'magisk_patched.tar' (or alternatively, highlight the file and select 'Open') to have it load into the AP slot:
With all these steps completed and your device connected, STOP and read below:
A green navigation bar on Odin, and a white bar on you device, will appear.
This indicates that key files are being written to your device.
Irregardless of how quick or slow the progress bar is, DO NOT disconnect the device.
The device, no matter if the flash was successful or not, will do NOTHING because you unchecked 'Auto Reboot'.
Wait for 'PASS!' to appear in Odin before you disconnect your device.
If everything was done correctly, Odin will look like this:
Your device, on the other hand, will have the following bar across its screen:
Now disconnect the device, STOP and read below until you feel comfortable enough to execute the instructions:
Hold 'Volume Down' and 'Power' until the screen goes black (also known as a 'Soft Reset').
The moment the screen goes black, continue to hold down 'Power' but QUICKLY switch so now only 'Volume Up' is being held.
Do this until you enter 'Android Recovery'.
As outlined in 'SECTION ELEVEN', use the 'Volume Keys' & 'Power' to navigate the menu.
First select 'Wipe Data/Factory Reset' and, upon completion, choose 'Reboot System Now'.
Your device will reboot several times. This is expected behavior.
If everything was done correctly, your device will reinitialize and require set-up again:
SECTION THIRTEEN - ROOT VERIFICATION
Like 'SECTION SEVEN', you need WIFI to complete set-up but mustn't log into ANY accounts.
Also, like 'SECTION SEVEN', you will need to install Magisk Manager again.
Once the first two steps are complete, power-off the device:
With the device powered off AND disconnected, hold down 'Volume Up' and 'Power' until you see the following warning:
WARNING: From now on, on EVERY BOOT or REBOOT, you MUST do this if you want Magisk enabled.
Release all keys and allow the device to boot.
Once Android is loaded, launch Magisk from your app drawer.
If you are prompted to update, do so but select 'Direct Install (Recommended)' and remember the key sequence on reboot:
Magisk Manager, if set-up properly AND with root enabled, will look like this:
Magisk Manager, if NOT set-up properly OR with root disabled, will look like this:
PRO-TIP: To further validate root, you can use an application like 'Root Checker' to verify:
You may now log into your accounts and finish configuring the device.
Recognition & Sharing Policy
RECOGNITION
This guide, and the required methods and software, would NOT be possible with the efforts of the following individuals:
@topjohnwu
@ianmacd
@LuK1337
@invmini
@CrazyApe
@eragon5779
@PewPewK
A sincere thank you for your time, hard work and, most importantly, determination to explore.
Praise and tribute is also extended to @TiTiB for his editorial skills, testing and much needed feedback.
SHARING POLICY
Do NOT reuse any part of this guide without first asking.
Do NOT reuse any part of this guide without giving credit to those in the 'RECOGNITION' header.
ALL photographs, not screenshots, are the property of myself (AHE_XDA). I spent considerable time capturing and editing each posted photograph. Therefore photographs may NOT be downloaded, copied, reproduced or used anyway without consent.
If there's something you like (styling/format/text/photographs) and want to use, ask.
Return To Stock Instructions
To return to stock and/or relock the bootloader, these are the best instructions available:
https://forum.xda-developers.com/showpost.php?p=79698366&postcount=44
They are originally intended for the Galaxy S10 series but work perfectly for the Tab S5e (SM-T720).
Full credit to @robbo1947.
Very nice how-to!!!
Would've made my first attempts much easier
I made it through the old way, getting all bits and pieces from through the other thread, this saves new comers hours of reading through all info available and getting it done at once.
---------- Post added at 07:25 PM ---------- Previous post was at 07:24 PM ----------
Side note I never used the key combo on rebooting for magisk updates or other stuff, always had root enabled afterwards.
You've done one helluva job @AHE_XDA!! I can't even imagine how long it took to put all of this together. It leaves nothing to be desired. Honestly, I've never seen such a comprehensive guide on xda before. Here's some $$$$$$$$$$ in thanks.
BTW, I'm fully up and running with Magisk and am currently freezing away many apps.
CAUTION: Be very careful when freezing anything Samsung 'billing' related.
I got a bit carried away freezing Samsung stuff and locked it up tighter than a drum.
FYI, before rooting I was disabling every Samsung app I could (including com.sec.android.app.billing) and had no problems. Root really *is* powerful.?
Anyways, if you get in to a predicament like mine and see these screens there is still hope.
Power off> Hold both VOL> Plug in PC-connected USB cable> Press PWR
Might take a few tries, but eventually you should get to DOWNLOAD screen.
Pics are in reverse order. You would see the one on the right first.
@TiTiB
I was able to reproduce your error.
I updated the 'Known Issues' to reflect this.
It is either 'Payment Services' (com.samsung.android.kgclient)' or 'KnoxGuard' (knoxguard.apk) that caused the error.
I can disable, freeze or delete 'Samsung Billing' (com.sec.android.app.billing) without issue.
Thank you for this info! It really helps in my continuing persuit to get rid of as much Samsung stuff as possible, while still retaining OneUI functionality. It gets a bit unnerving freezing stuff when you're several days in to setting up stuff. I'm going slower this time.
@AHE_XDA first of all thanks for this manual, I had never seen more comprehensive here!
Second, I had one attempt to root t725, it was 2 months ago. I done all steps, made patched AP, glashed successfully (only ap, not other 3 files). After reboot I got exactly same messages as described in upper post! Not debloat, but straight from boot with root.
I afraid, gone to download mode and flashing stock. Got it back.
Never tried again.
Have you idea what was wrong?
I want to do again, but afraid a little...
Thanks
ivanox1972 said:
@AHE_XDA first of all thanks for this manual, I had never seen more comprehensive here!
Second, I had one attempt to root t725, it was 2 months ago. I done all steps, made patched AP, glashed successfully (only ap, not other 3 files). After reboot I got exactly same messages as described in upper post! Not debloat, but straight from boot with root.
I afraid, gone to download mode and flashing stock. Got it back.
Never tried again.
Have you idea what was wrong?
I want to do again, but afraid a little...
Thanks
Click to expand...
Click to collapse
After you flash the AP file with Magisk, you don't want to re-install the entire binary with Odin.
You need to dissect its contents, re-compress it and THEN install with Odin.
Take a look at 'Section Ten' on the first page to see what I'm talking about.
Any questions, place them on thread or PM me.
AHE_XDA said:
@TiTiB
I was able to reproduce your error.
I updated the 'Known Issues' to reflect this.
It is either 'Payment Services' (com.samsung.android.kgclient)' or 'KnoxGuard' (knoxguard.apk) that caused the error.
I can disable, freeze or delete 'Samsung Billing' (com.sec.android.app.billing) without issue.
Click to expand...
Click to collapse
Check this-wtf?
TiTiB said:
Check this-wtf?
Click to expand...
Click to collapse
Yes, there is a dependency between the two. With App Inpector, you don't see 'KnoxGuard' explicitly listed but if you use something like 'Root Explorer', you'll find it.
Until we get recovery, like the other Samsung devices on Pie, we simply can't touch these files.
AHE_XDA said:
Yes, there is a dependency between the two. With App Inpector, you don't see 'KnoxGuard' explicitly listed but if you use something like 'Root Explorer', you'll find it.
Until we get recovery, like the other Samsung devices on Pie, we simply can't touch these files.
Click to expand...
Click to collapse
I use MiXplorer and have seen those while 'xploring'. Before rooting, when I was using PackageDisabler, kgclient was one of the disabled packages....uh, so my point is WTF?
@TiTiB
So to make sure we understand each other; you could disable/uninstall it through ADB but a removal of the apk froze the device (along with the error)?
Bixby Is Coming - July Update
In the next build of software for the Tab S5e (July), Bixby will be introduced and fully integrated into the system.
This means nothing for root but means you'll have more to uninstall/disable.
If you don't want or need Bixby, stay on ANY release prior to July.
AHE_XDA said:
@TiTiB
So to make sure we understand each other; you could disable/uninstall it through ADB but a removal of the apk froze the device (along with the error)?
Click to expand...
Click to collapse
I disabled kgclient using Disabler Pro app with no ill effects (before rooting). It's in my 'disabledpackages133-OK.xml', so I assume it was disabled. Perhaps the Disabler app handled it differently or something, idk.
After I rooted, while I was freezing Samsung apps using '3C Toolbox Pro', and I'm *almost* 100% certain Payment Services/kgclient was among them, the tablet locked up. AFAIK, these two actions, using these two apps is effectively the same thing, therefore the 'wtf' statement.
I am curious enough that I'm going to prepare for disaster, then mess around with this package—first, disabling it with the 'CCSWE App Manager (SAMSUNG)' app, then manipulating the package's contents (expecting disaster), then freezing it with 3C Toolbox—I MUST HAVE THE ANSWER!! (TiTiB *does* stand for Tweak it Til it Breaks, after all) ?
It wiil be an hour or two, and, of course, I'll post my results here.
@TiTiB
Whenever you disable or remove a system app without root; the application still exists on the device.
It's never truly gone.
It's only been removed from your profile; usually referred to as user 0 (current user).
A factory reset will bring that application right back.
Introduce root and now, because you have administration access over the entire device, remove the application and it's gone for good (or at least until you flash stock firmware).
Alter them at a root level, freeze/remove/disable, it's likely you're going to see the same error as before.
TiTiB said:
I disabled kgclient using Disabler Pro app with no ill effects (before rooting). It's in my 'disabledpackages133-OK.xml', so I assume it was disabled. Perhaps the Disabler app handled it differently or something, idk.
After I rooted, while I was freezing Samsung apps using '3C Toolbox Pro', and I'm *almost* 100% certain Payment Services/kgclient was among them, the tablet locked up. AFAIK, these two actions, using these two apps is effectively the same thing, therefore the 'wtf' statement.
I am curious enough that I'm going to prepare for disaster, then mess around with this package—first, disabling it with the 'CCSWE App Manager (SAMSUNG)' app, then manipulating the package's contents (expecting disaster), then freezing it with 3C Toolbox—I MUST HAVE THE ANSWER!! (TiTiB *does* stand for Tweak it Til it Breaks, after all)
It wiil be an hour or two, and, of course, I'll post my results here.
Click to expand...
Click to collapse
Sho'nuff, stay away from Samsung Payment/kgclient if rooted.