Develop Bugs

[RECOVERY][UNOFFICIAL] TWRP 3.2.2-1

This is for the Mediapad M5.
NOTE: Decrypting data is not currently supported. MTP also does not work, but you can use adb to push and pull files.
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
NOTE: Decrypting data is not currently supported. MTP also does not work, but you can use adb to push and pull files.
NOTE: fastboot flash to recovery_ramdisk and not to recovery as this device does not have a regular recovery partition
Fastboot Install Method (No Root Required):
You will need the platform-tools from the Android SDK on your computer. Find the Android command line tools section on the page linked and install the SDK tools package. From the SDK Manager, download only the platform-tools to get adb and fastboot binaries.
Windows users will need proper drivers installed on their computer. You can try the simple FWUL adb/fastboot ISO or the Naked ADB drivers or the Universal ADB drivers if you don't already have a working driver installed
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
adb reboot bootloader
You should now be in fastboot mode.
Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
flash recovery_ramdisk twrp.img
reboot
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.[/QUOTE]
XDA:DevDB Information
[RECOVERY][UNOFFICIAL] TWRP 3.2.2-1, ROM for the Huawei MediaPad M5
Contributors
schwabe93
ROM OS Version: 8.x Oreo
Version Information
Status: Beta
Created 2018-07-08
Last Updated 2018-07-08

Download on Androidfilehost:
TWRP for Mediapad
Telegram Group for MediapadM5:
Join

Information
With this TWRP you can flash Magisk etc.
You can flash my LineageOS build
You cannot Backup StockROM as decryption not work

schwabe93 said:
Download on Androidfilehost:
TWRP for Mediapad
Telegram Group for MediapadM5:
Join
Click to expand...
Click to collapse
Hi, first i wanted to say thank you for bringing twrp to our device. Can you please check download link beceuse it does not work for me. I found recovery on your profile on Androidhost, but I want to be sure i downloaded correct file.

xabat said:
Hi, first i wanted to say thank you for bringing twrp to our device. Can you please check download link beceuse it does not work for me. I found recovery on your profile on Androidhost, but I want to be sure i downloaded correct file.
Click to expand...
Click to collapse
Hey, thanks for informing me, the link should now work.
Regrads Alex

schwabe93 said:
With this TWRP you can flash Magisk etc.
Click to expand...
Click to collapse
Try to install Magisk-v16.0.zip, but got error
"Process ended with error 255"
so as on previous twrp

ZeuseZ said:
Try to install Magisk-v16.0.zip, but got error
"Process ended with error 255"
so as on previous twrp
Click to expand...
Click to collapse
Have you tried MagiskBeta16.4?
For me it works with the Beta.
On stock and on Lineage

unfortunately i get error 64 wrong architecture when installing opengapps, which is a known issue for twrp 3.2.x
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1070

Thank you for your work. One question:
Why in TWRP for Emui 8.0 (link below) it is possible to decrypt data and here it is not?
Also MTP is working there..
https://forum.xda-developers.com/p1...rp-3-2-1-0-emui-8-0-4-04-2018-t3773449/page10

Huawei Mediapad M5 - CMR-AL09 8.0.0.161(C432)
I am use twrp_p10_0.1.img : this TWRP work with encrypt on MY device
If i lost my device - the "data" is encrypt
If i use TWRP without encrypt the first action = boot to TWRP, go to Wipe, format "data", reboot from TWRP to TWRP
Now is "data" without crypt. If i lost the device now : data is readable from everyone
I am setting PIN for login / stand by and wake up (screen off and on).
If encrypt work you see by start recovery (TWRP), TWRP need PIN and decrypt "data"
If this TWRP work on other M5 Model/Coutry(= build) : i dont know / i dont have

Thank you for bringing TWRP to the M5 - really appreciate your hard work! Will this work with the 8.4 WiFi variant, SHT-W09?

mroshaw said:
Thank you for bringing TWRP to the M5 - really appreciate your hard work! Will this work with the 8.4 WiFi variant, SHT-W09?
Click to expand...
Click to collapse
Can confirm. Installed and running on my WiFi variant 8.4 SHT-W09(C567) along with Magisk.

Kerr Avon said:
Can confirm. Installed and running on my WiFi variant 8.4 SHT-W09(C567) along with Magisk.
Click to expand...
Click to collapse
Any problems or weird behaviour? Is Magisk Hide working okay? Any app or service impacted by root / Magisk?
Do you use Netflix and / or Amazon Prime Video? Still working and receiving HD streams?
Thanks! :good:

mroshaw said:
Any problems or weird behaviour? Is Magisk Hide working okay? Any app or service impacted by root / Magisk?
Do you use Netflix and / or Amazon Prime Video? Still working and receiving HD streams?
Thanks! :good:
Click to expand...
Click to collapse
Check yourself and let us know like a pro

sebarkh said:
Check yourself and let us know like a pro
Click to expand...
Click to collapse
Awww man, I'm too scared to! Just bought the thing - if someone's already dared to root, I'd rather find out from them if it FUBARs the tablet! Haha! :laugh:

mroshaw said:
Any problems or weird behaviour? Is Magisk Hide working okay? Any app or service impacted by root / Magisk?
Do you use Netflix and / or Amazon Prime Video? Still working and receiving HD streams?
Thanks! :good:
Click to expand...
Click to collapse
Can't answer HD in Netflix & Amazon but Magisk hide and root works fine without issue. I'm not using this version of TWRP but you don't need TWRP to install Magisk.

The tablet with this LineageOS is only L1 security level when checked with DRM info, so no HD on both Amazon Prime and Netflix.

@DF5JT sorry, but L1 means already best security mode otherwise it would have L3 only. Netflix and Amazon Prime videos should work without issues ... unless you unlocked the bootloader which might have influence.

AndDiSa said:
@DF5JT sorry, but L1 means already best security mode otherwise it would have L3 only. Netflix and Amazon Prime videos should work without issues ... unless you unlocked the bootloader which might have influence.
Click to expand...
Click to collapse
Sorry, I misspoke. The M5 with LineageOS and unlocked bootloader is only L3 security. My bad.

Mp
Does this work with mediapad 8.4 lte EU version?

Android Auto - Something went wrong. Google play services doesn't seem to be working

I have had a problem loading Android Auto (AA) on my LG G4. I have rooted with Steadfaster's UsU and installed his Lineage 15.1 rom, opengapps nano (Sept 30) and the phone is working great. Prior to rooting the phone AA worked fine with MM 6.0. After rooting the phone, when I open the AA app on the phone I get the error "Something went wrong. Google play services doesn't seem to be working right now". The error comes up immediately and then the app closes. I tried plugged into in the car as well (Pioneer AVIC 4200 deck), but the error stops the phone when opened.
I have been through Google's forums and there have been lots of posts about this error and no real solutions for me posted. I have also tried other "fixes" I have come across, including this one - https://forum.xda-developers.com/android/help/delete-disable-downgrade-prevent-update-t3091832/. This method involves:
1. Download and install System App Remover from the Google Play Store.
2. Put your device in Airplane Mode in order to prevent auto upgrade of GPS.
3. Open System App Remover and select "System App" from the menu.
4. Find Google Play Services in the list. It should be marked "Should keep", which is a suggestion from the publisher. Select it and press "Uninstall". Ignore completion message.
5. Using Settings/Apps, verify that Google Play Services has reverted to the factory-supplied version. It should be <7. "Force Stop", "Uninstall Updates", and "Disable" buttons should no longer be grayed out.
7. Reboot device and toggle Airplane Mode off.
I followed these steps, but unfortunately stock seems to be the version that came with opengapps which is current.
I'm out of ideas with this problem and need some help. AA is a great app for me and really handy on long trips. I would like to get it running if at all possible.
Appreciate any help you can provide.

jjcdennis said:
I have had a problem loading Android Auto (AA) on my LG G4. I have rooted with Steadfaster's UsU and installed his Lineage 15.1 rom, opengapps nano (Sept 30) and the phone is working great. Prior to rooting the phone AA worked fine with MM 6.0. After rooting the phone, when I open the AA app on the phone I get the error "Something went wrong. Google play services doesn't seem to be working right now". The error comes up immediately and then the app closes. I tried plugged into in the car as well (Pioneer AVIC 4200 deck), but the error stops the phone when opened.
I have been through Google's forums and there have been lots of posts about this error and no real solutions for me posted. I have also tried other "fixes" I have come across, including this one - https://forum.xda-developers.com/android/help/delete-disable-downgrade-prevent-update-t3091832/. This method involves:
1. Download and install System App Remover from the Google Play Store.
2. Put your device in Airplane Mode in order to prevent auto upgrade of GPS.
3. Open System App Remover and select "System App" from the menu.
4. Find Google Play Services in the list. It should be marked "Should keep", which is a suggestion from the publisher. Select it and press "Uninstall". Ignore completion message.
5. Using Settings/Apps, verify that Google Play Services has reverted to the factory-supplied version. It should be <7. "Force Stop", "Uninstall Updates", and "Disable" buttons should no longer be grayed out.
7. Reboot device and toggle Airplane Mode off.
I followed these steps, but unfortunately stock seems to be the version that came with opengapps which is current.
I'm out of ideas with this problem and need some help. AA is a great app for me and really handy on long trips. I would like to get it running if at all possible.
Appreciate any help you can provide.
Click to expand...
Click to collapse
Even when it sounds obvious but have you installed AA clean so without restoring data from a backup? Do you have tried to completely factory reset the phone? Do you have tried to format data in TWRP? Obviously you should have a backup of your internal storage when doing so .
You should also catch a logcat when starting the app
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Even when it sounds obvious but have you installed AA clean so without restoring data from a backup? Do you have tried to completely factory reset the phone? Do you have tried to format data in TWRP? Obviously you should have a backup of your internal storage when doing so .
You should also catch a logcat when starting the app
After rooting with UsU I followed sdembiske's recommendations for installing Lineage. This included a factory reset and formatting data with TWRP. I then installed Lineage 15.1 UsU and opengapps nano and then installed the apps I wanted. AA went on clean without restoring data. I will capture a logcat and post.
Thanks
Click to expand...
Click to collapse

steadfasterX said:
Even when it sounds obvious but have you installed AA clean so without restoring data from a backup? Do you have tried to completely factory reset the phone? Do you have tried to format data in TWRP? Obviously you should have a backup of your internal storage when doing so .
You should also catch a logcat when starting the app
After rooting with UsU I followed sdembiske's recommendations for installing Lineage. This included a factory reset and formatting data with TWRP. I then installed Lineage 15.1 UsU and opengapps nano and then installed the apps I wanted. AA went on clean without restoring data. It never opened without the error I titled this thread with.
My first attempt at a logcat. I searched in Notepad++ and used carservice as the keyword. Some errors were shown. I don't know how to interpret them and would appreciate your help
Thanks
Click to expand...
Click to collapse

jjcdennis said:
steadfasterX said:
Even when it sounds obvious but have you installed AA clean so without restoring data from a backup? Do you have tried to completely factory reset the phone? Do you have tried to format data in TWRP? Obviously you should have a backup of your internal storage when doing so .
You should also catch a logcat when starting the app
After rooting with UsU I followed sdembiske's recommendations for installing Lineage. This included a factory reset and formatting data with TWRP. I then installed Lineage 15.1 UsU and opengapps nano and then installed the apps I wanted. AA went on clean without restoring data. It never opened without the error I titled this thread with.
My first attempt at a logcat. I searched in Notepad++ and used carservice as the keyword. Some errors were shown. I don't know how to interpret them and would appreciate your help
Thanks
Click to expand...
Click to collapse
I just searched a bit regarding the errors of your logcat and found this:
https://productforums.google.com/forum/#!topic/nexus/-N8jJo7A8nI
maybe something there helps you out.
It seems definitively an issue with google play app/updates..
btw: I have just installed AA here without an issue, running LOS 15.1 on my h815..
.
Click to expand...
Click to collapse

steadfasterX said:
jjcdennis said:
I just searched a bit regarding the errors of your logcat and found this:
https://productforums.google.com/forum/#!topic/nexus/-N8jJo7A8nI
maybe something there helps you out.
It seems definitively an issue with google play app/updates..
btw: I have just installed AA here without an issue, running LOS 15.1 on my h815..
.
Click to expand...
Click to collapse
I have been through that forum and tried the last post just now - uninstall updates, clear cache, open AA - and I immediately get the error.
I'm thinking about doing a Titanium backup on apps and data (minus AA) then wipe, reinstall LOS 15.2, TWRP, Lineage SU, do a reboot, reinstall AA first and if it works then run Titanium restore for apps and data.
Make sense?
Click to expand...
Click to collapse

jjcdennis said:
steadfasterX said:
I have been through that forum and tried the last post just now - uninstall updates, clear cache, open AA - and I immediately get the error.
I'm thinking about doing a Titanium backup on apps and data (minus AA) then wipe, reinstall LOS 15.2, TWRP, Lineage SU, do a reboot, reinstall AA first and if it works then run Titanium restore for apps and data.
Make sense?
Click to expand...
Click to collapse
Sounds like a plan
Nevertheless I would to a titanium backup of play and AA BEFORE restoring as well..
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse

steadfasterX said:
jjcdennis said:
Sounds like a plan
Nevertheless I would to a titanium backup of play and AA BEFORE restoring as well..
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Well I wiped cache, Dalvik, system and then formatted data, installed the 15.1 UsU rom, then installed Gapps, rebooted to recovery and installed the Lineage addonsu. I rebooted, went through setup and the first thing I did was open the Playstore install Android Auto and run it - immediate error again. Also the addonsu did not root the phone. And to top it all I did not disable the pin code.
Back to the drawing board.
Click to expand...
Click to collapse

steadfasterX said:
jjcdennis said:
btw: I have just installed AA here without an issue, running LOS 15.1 on my h815..
.
Click to expand...
Click to collapse
I have been beating the bushes and looking for a solution. None so far. You mention AA worked on your phone. Are you running LOS 15.1 and if no, which rom? Also re your install can you look in apps and notifications and see if the more options * is shown on the AA app. I have it, but when I select it nothing happens. My old Nexus 5 the * works and Android Auto opens no problem. LOS 7.1.2.
Thanks
Click to expand...
Click to collapse

jjcdennis said:
steadfasterX said:
I have been beating the bushes and looking for a solution. None so far. You mention AA worked on your phone. Are you running LOS 15.1 and if no, which rom? Also re your install can you look in apps and notifications and see if the more options * is shown on the AA app. I have it, but when I select it nothing happens. My old Nexus 5 the * works and Android Auto opens no problem. LOS 7.1.2.
Thanks
Click to expand...
Click to collapse
I run LOS 15.1 build 20181002 and at the time of installing that ROM version I used this opengapps version: open_gapps-arm64-8.1-nano-20180705.zip (download)
AA works here yes. I run it now for several days, daily, no issues here.
My version of AA is 3.7.584044 (attached: View attachment com.google.android.projection.gearhead-ffadc269cc39417e152ffcdd22183045.apk)
Not sure what you mean by "the more options *" but I've attached 2 screenshots of the app settings which may show what you meant.. if not show a pic of that setting.
oh you may meant the gear symbol at the top right? Here it opens fine but as that opens google stuff it makes sense that it fails on yours
.
Click to expand...
Click to collapse

Isn't mine basically the same as yours, other than H815? That gear icon will not open up the more options page. On my Nexus 5 with LOS 7.1.2 it opens a page with Settings for AA ie: Limit wifi, Connected cars, phone screen settings, etc.
If not the same maybe I should run your version of LOS.

jjcdennis said:
Isn't mine basically the same as yours, other than H815? That gear icon will not open up the more options page. On my Nexus 5 with LOS 7.1.2 it opens a page with Settings for AA ie: Limit wifi, Connected cars, phone screen settings, etc.
If not the same maybe I should run your version of LOS.
Click to expand...
Click to collapse
I've mentioned and linked the opengapps version, attached the AA version and mentioned the exact build for a reason yes.
The idea was that you try the exact same setup.
btw: which model do you have?
.-

steadfasterX said:
I've mentioned and linked the opengapps version, attached the AA version and mentioned the exact build for a reason yes.
The idea was that you try the exact same setup.
btw: which model do you have?
.-
Click to expand...
Click to collapse
H812 on the UsU Oreo build H812 build.
So I can copy what you have, other than I'm using the H812 versus the H815 LOS rom.
Thanks steadfasterX

steadfasterX, is it necessary that I format the data when I reload this rom. Takes a long time to restore everything.

jjcdennis said:
steadfasterX, is it necessary that I format the data when I reload this rom. Takes a long time to restore everything.
Click to expand...
Click to collapse
Use my latest preview version of TWRP then you can backup your data AND internal storage . you can first try without format. if you still have issues try to format it and if it doesn't fix anything you can restore by TWRP but ensure that you use build 144 or higher
Sent from my LG-H815 using XDA Labs

OK, thanks again. Will give it a go. I have your latest TWRP, 144_g4_0.
On the positive side after all kinds of failed troubleshooting my G4 has all of a sudden decided to connect with my PC. It shows as H812 in Explorer and in Device Manager as Lemobile Android Device with Android Composite ADB Device driver. A lot easier than using Cloud.

jjcdennis said:
OK, thanks again. Will give it a go. I have your latest TWRP, 144_g4_0.
On the positive side after all kinds of failed troubleshooting my G4 has all of a sudden decided to connect with my PC. It shows as H812 in Explorer and in Device Manager as Lemobile Android Device with Android Composite ADB Device driver. A lot easier than using Cloud.
Click to expand...
Click to collapse
Gave it a go, but as soon as I tapped on AA the error came up. I did format data to start from clean and used the older versions of AA and Google Play.
Update - I reinstalled all my apps via Titanium Pro (not AA) and set things up. I decided to tryy AA one more time before removing it and bingo it opened. Kinda waking on broken glass here and unsure whether or not the app will continue to function. Hooefully this fixed things.
Thanks again steadfasterX.

Android 10 WW BETA 10 OUT

Android 10 BETA WW
Special thanks as always to Vietnam ROG II Grp. They do amazing work.
Links removed due to request
Rename the downloaded file to UL-ASUS_I001_1-ASUS-16.0631.1912.22-1.1.227-user.zip then put on root of internal storage and restart.
Root & Bootstock for 1912.22 ANDROID 10 BETA
https://mega.nz/#!hxJGCQpT!6xU71ihzA1cA5JLDB_hMMJNg5iHt80FmOf6z8Hrb7gA
Use at your own risk, do not raise issues on Zentalk forums.
So far user feedback has been positive.
Please let us know your experiences.
Current known issues (some bad English here!):
When in the game scenario and answer the phone call, user will not hear the sound and cut off the call after 30 seconds later.
Can not open the icon manager and showing "System UI has stopped"
When you install Avast.apk don't have any scan notice.
Working with twinview dock and open one of a app on the phone side then press twinview side panel recent key. The phone side will back home screen.
When using DT Dock or twinview or Pro dock to play Netflix will keep portrait mode and only show subtitle.

Any bugs?

Link root from telegram

Anyone tried it? If yes can post pictures thanks

Successfully update to Android 10 beta with magisk installed but now I am without TWRP. Tried flash TWRP with adb but it reboot to bootloader every time. Maybe TWRP must be updated for Android.

This is failing for me. Gets to 2% then fails. I'm on Rooted 128 GB Tecent with WW ROM, fingerprint is changed to WW.

xbamaris1` said:
This is failing for me. Gets to 2% then fails. I'm on Rooted 128 GB Tecent with WW ROM, fingerprint is changed to WW.
Click to expand...
Click to collapse
If you're rooted then you probably need to flash it manually.

tsoureki said:
Successfully update to Android 10 beta with magisk installed but now I am without TWRP. Tried flash TWRP with adb but it reboot to bootloader every time. Maybe TWRP must be updated for Android.
Click to expand...
Click to collapse
Step for update without lost root sir?

If you are rooted on latest Android 9 you need to go in magisk, press uninstall and restore images. Then you can apply the beta 10 ota. For root flash on adb the modified boot image from op

Does anyone have the Android 10 beta full RAW firmware ???
Hello, if anyone has access to the full Android 10 beta RAW firmware, please share it with us. Thanks !!!

Wow it's amazing. The red tint gone and it's way too smooth

It seems this has also broken the ability to enable VoLTE (*#*#4636*#*#) greys out the options but they do show up in the Settings menus. So not sure what that means?
EDIT: Ignore, its because the profile set in PDC was reset as someone else has pointed out. I JUST got VOLTE to work again after working with AT&T to get a provisioning error resolved (this was on their end, but probably because I was swapping SIMs between phones for testing)
Im going to let this settle a little bit before I try upgrading again to this (I downgraded back to 9 in fear that VOLTE wasnt going to work again)

Gpay is not working

Is this WW or CN beta????

cheetah2k said:
Is this WW or CN beta????
Click to expand...
Click to collapse
When you download zip its named WW.

CTS doesn't pass on this version. Hence done apps like gpay may not work

I'm not sure what I'm doing wrong but as soon as I tap update it instantly just says failed. I am on ww rom ww fingerprint and have twrp.

Hello
What is the difference between a version and the orange star?

candiesdoodle said:
CTS doesn't pass on this version. Hence done apps like gpay may not work
Click to expand...
Click to collapse
Do you know if this version will keep getting OTA?

lol cloud1 you just posted without giving credit to the owner from telegram vietnam group. it is like u stealing their work. now they just informed they will not post any update anymore in that group.

Global Stable 11.0.3.0 Android 10

Global Update is there.

For those who installed it already, give us some feedback.. and one question, should factory rested be done before or after installing update? What is better, because i never did reset before, just apply update, but now would like to do reset also..

Works fine without reset. Smartphone was very hot during update. After installation I made a reboot. All Apps are working and Dark Mode is now available for most Apps.

This update broke my GooglePay, no longer passing ctsProfile in safetynet.

Seems to work fine. Before this update I was getting more and more bugs, but they seem to be gone now. Rebooting after the update took a long time, however. I was stuck on the Mix logo for 5-10 minutes.
There are some visual tweaks here and there, but that's all I can notice.

Themes available, region uk!

Latest update has caused my home launcher to crash. Am only able to use it cause of 3rd party launcher.

Does Magisk patched boot work with this? I was stuck a boot screen for over 10 mins before I had to reflash stock boot.img.
*update*
I had an out of date version of exposed installed that caused boot loop.

I can't install work email, and because my phone is CN region, of course, Google Pay not working. Not sure if boot options for the kernel changed, going to look and see if I need to update my flashable patcher zip.

blue1978 said:
Does Magisk patched boot work with this? I was stuck a boot screen for over 10 mins before I had to reflash stock boot.img.
Click to expand...
Click to collapse
Yes...work perfectly.

blue1978 said:
Does Magisk patched boot work with this? I was stuck a boot screen for over 10 mins before I had to reflash stock boot.img.
Click to expand...
Click to collapse
Not with the latest stable version. Take a look here so solve your problem: https://github.com/topjohnwu/Magisk/issues/2492#issuecomment-593149828

Any updates on anyone getting magisk to work on this? Can I use magisk patch with just the boot.img extracted from the OTA update .zip file?
I have the international not a china model.

Anybody found a solution for viper4android? I tried rootless 2.7 but driver will not install.

Quality_con_troll said:
Any updates on anyone getting magisk to work on this? Can I use magisk patch with just the boot.img extracted from the OTA update .zip file?
I have the international not a china model.
Click to expand...
Click to collapse
Magisk works.
But my ctsProfile fails on the safetynet.
Rendering GooglePay and PokemonGo unusable, which wasn't an issue for me before.
Also am international model.
After this update,
I was struggling to boot TWRP at first,
But my issue stemmed from trying to use adb / fastboot commands to boot into TWRP recovery, which only took me to stock recovery.
I got my Magisk back by doing a "fastboot flash recovery TWRP.img"
And then manually used the volume up + power button to boot TWRP (I used the unofficial mauronofrio)
And from there just install the Magisk zip.

spyke180 said:
Magisk works.
But my ctsProfile fails on the safetynet.
Rendering GooglePay and PokemonGo unusable, which wasn't an issue for me before.
Also am international model.
After this update,
I was struggling to boot TWRP at first,
But my issue stemmed from trying to use adb / fastboot commands to boot into TWRP recovery, which only took me to stock recovery.
I got my Magisk back by doing a "fastboot flash recovery TWRP.img"
And then manually used the volume up + power button to boot TWRP (I used the unofficial mauronofrio)
And from there just install the Magisk zip.
Click to expand...
Click to collapse
Just went through this process myself and came back here now to report on it.
This was my process for anyone also looking for guidance.
This will work for the new android 10 updated. I came from MIUI10 (10.0.3.2.0) using system update to go to MIUI11 and android 10 (11.0.3.0) via OTA update, which reverted to stock recovery and obviously lost root as well.
1. Saved most recent twrp 3.3.1-7-recovery.img for perseus by mauronofrio found in these XDA threads, magisk 20.3.zip found on magisk site and repository, and just to be sure disable forced encryption-treble.zip (just search for it) to my phone AND adb directory on Windows 10 computer.
ENSURE USB IS PLUGGED INTO 2.0 or 2.0 COMPATABILE HUB (Flashing recovery failed when connected to a USB3.0 port) and ADB/FASTBOOT is installed on your computer.
2. Booted into fastboot. (Power + Volume down)
3. Ran cmd.exe and entered "cd C:/(wherever you installed/platform-tools" without quotes.
4. Entered "fastboot devices" to ensure fastboot is connected. It should show device_id# and fastboot next to that.
5. Flashed TWRP3.3.1-7 for MiMix3 perseus (latest unofficial TWRP) by entering "fastboot flash recovery twrp3.3.1-7-recovery.img"
6. Entered "fastboot reboot recovery" the phone will reboot now, ENSURE YOU HOLD VOL+ ASAP or you will lose TWRP with stock recovery.
7. After booting into TWRP, entered password, wiped data and cache only.
8. In TWRP go to install and choose your disable_forced_encryption-treble.zip and flash it but do not select reboot device, it is selected by default.
(NOTE: Don't know if #8 is a necessary step especially for Global devices but did it anyways and it didn't hurt anything)
9. Go to install again and choose magisk20.3.zip, this time you can select reboot device.
10. After completing android setup download magisk manager 7.5.1 from play store and verify 20.3 is installed, if it is then congrats, you're rooted.
That's it! Like the above post said ctsProfile is reading false meaning you most likely will not be able to use Pay apps like Google Pay, etc.
Other apps that use google play services for verification may not work as well like Pokemon GO, Mario Kart, Harry Potter, or other banking/security apps. (Not sure about this one yet, try MagiskHide in the manager. Spyke180 is reporting above they do not work currently.) So if you can't live without Samsung Pay, or one of these games wait until a ctsProfile:true/SafetyNet passes solution is available.
Hopefully the next magisk update or someone in the community will be able to solve these issues in a timely manner, shouldn't be much of a wait.
Hope this made sense and can help some peeps out there perhaps.

CTSProfile is failing on my device as well. I tried using the boot cmdline patcher I made and it's still failing. I am wondering if Xiaomi released this update before getting the fingerprint in the CTS approved list. I can't think of anything else. My device is a CN device, so the BL is unlocked. I don't know if flashing Magisk with CN device and Global software still results in a boot loop but may try it.
Also, Magisk is detected through some methodology. I read all the posts made in both the release and beta threads in the last 3 days and it seems broken for everyone.

MMS stopped automatically sending and receiving on Google Messages app. But somehow works flawlessly on stock texting app. Notification tells me "Can't send MMS message. Tap to allow MMS messaging on (Carrier) when mobile data is off". Tapping the notification yields nothing. Even a factory reset does nothing.

siuyan187 said:
MMS stopped automatically sending and receiving on Google Messages app. But somehow works flawlessly on stock texting app. Notification tells me "Can't send MMS message. Tap to allow MMS messaging on (Carrier) when mobile data is off". Tapping the notification yields nothing. Even a factory reset does nothing.
Click to expand...
Click to collapse
If you go into settings, and then to "SIM cards & mobile networks", is the "Always receive MMS" toggle in the on position (blue)?

spyke180 said:
If you go into settings, and then to "SIM cards & mobile networks", is the "Always receive MMS" toggle in the on position (blue)?
Click to expand...
Click to collapse
Yep. Both in system settings and also in the app settings. Tried turning one on and the other off in different combinations, but still doesn't work.

siuyan187 said:
Yep. Both in system settings and also in the app settings. Tried turning one on and the other off in different combinations, but still doesn't work.
Click to expand...
Click to collapse
I see.
If you're rooted, you could try using the systemize module to make it a system app.
I verified my Google Messages and its notifications are working for me, even with both Wi-Fi and mobile data turned off.

Cant seem to update TWRP Official app after installing magisk/twrp, nor pass safetynet in magisk

Hey folks, im having an issue with getting twrp up and running, as well as magisk i guess?
when i go to update twrp through google play it tells me "cant install official TWRP App, Try again, and if it will doesnt work see common ways to fix the problem" When i go to install the app through their website it tries to update that way and the update fails as well just saying "app not installed", i only have the base version at the moment with nothing in it that just tells me to update the app because its a placeholder that fits into a recovery
on the safetynet end of things if i try and pass the safetynet check i just get an api error screen?
this has been a huge headache from start to finish so if anyone can help me out here it would be grealy apprciated

siccoblue said:
Hey folks, im having an issue with getting twrp up and running, as well as magisk i guess?
when i go to update twrp through google play it tells me "cant install official TWRP App, Try again, and if it will doesnt work see common ways to fix the problem" When i go to install the app through their website it tries to update that way and the update fails as well just saying "app not installed", i only have the base version at the moment with nothing in it that just tells me to update the app because its a placeholder that fits into a recovery
on the safetynet end of things if i try and pass the safetynet check i just get an api error screen?
this has been a huge headache from start to finish so if anyone can help me out here it would be grealy apprciated
Click to expand...
Click to collapse
That's because there is no twrp for the pixel 3. There is some development for the 3 XL, but nothing for the 3.

That's because there is no twrp for the pixel 3. There is some development for the XL, but nothing for the 3.