Database Info

Worth it to upgrade from Android 10 Sept 2020 to Android 11 right now or wait?

Or wait a couple of months for them to tweak it a bit?
I only run Magik and not Xposed, not that it matters!

I'm not rooted, but I've been running R since the first public ßeta.
It's been the smallest update so far in a long time for Android. Very little has changed, compared to previous major version upgrades.
If you can root (and from what I read i think you can with Magisk), make a full backup and try it.
Sent from my Pixel 4 XL using Tapatalk

I don't really know what you'd be waiting for. I don't think a non-rooted person would notice much in terms of drawbacks. Magisk modules level, there were some issues... but I think most things are getting worked out. Xposed technically works, but more than half of my modules broke in a way that probably won't be fixed for a while. I still feel like I'm at a net-negative in terms of phone features. A11 brought little and broke a lot of my QoL tweaks that used Xposed.
I make no claims about SafetyNet as I use no apps that even check it.

I think A11 has been released formally by google and most of issues have been fixed or addressed.
I used magisk and edxposed. That's not a problem for me(I used Edxposed for fingerface only). Regarding of safetynet issue, it also has solution to make it pass by magisk modules and kernel side.
Until now, I'm happy with A11.

I ended up doing a full wipe and upgrade to Android 11 Oct 2020.
I have Magisk running with the SQL Lite mods for Google Pay and obviously I have root so I'm basically back where I was on Android 10.
I hadn't use Xposed yet and I don't know if I will yet. I was using Viper Audio mod but I don't know if I noticed a major difference, mostly I just stream bluetooth in my SUV.
So far, so good.

I tried it and reverted back to 10 - as mentioned didn't gain much but broke a lot. Even in stock form I can't get videos to load a subtitle file because of storage permissions and what not. A tweaked out install of 10 is faaaar nicer imo so that's what I'm running, probably until a new phone comes out sadly.

Kris Chen said:
I think A11 has been released formally by google and most of issues have been fixed or addressed.
I used magisk and edxposed. That's not a problem for me(I used Edxposed for fingerface only). Regarding of safetynet issue, it also has solution to make it pass by magisk modules and kernel side.
Until now, I'm happy with A11.
Click to expand...
Click to collapse
can i ask how you upgraded to A11? Im on 10 rooted with magisk and keep hearing mixed messages on upgrading. And is it necessary to wipe? I really don't want to.

A11 is not too bad, but as others have said little things here and there that break. Like for me I listen to SiriusXM app on mobile and for some odd reason it will stop playing all of a sudden and close. It's like the aggressive memory management kills the app for no reason. I even have battery optimization turned off and still does it.
Thinking about moving back to A10 from August, not really much I have to have to stick with latest A11 updates.

qman66 said:
can i ask how you upgraded to A11? Im on 10 rooted with magisk and keep hearing mixed messages on upgrading. And is it necessary to wipe? I really don't want to.
Click to expand...
Click to collapse
Flash the factory image, but remove the -w in the flash-all file. Then in Magisk Manager switch tot he beta channel and patch the boot image with that. Flash it and you're done.

GjorgiDxc said:
Flash the factory image, but remove the -w in the flash-all file. Then in Magisk Manager switch tot he beta channel and patch the boot image with that. Flash it and you're done.
Click to expand...
Click to collapse
You do know the latest version of magisk has a11 support?

GjorgiDxc said:
Flash the factory image, but remove the -w in the flash-all file. Then in Magisk Manager switch tot he beta channel and patch the boot image with that. Flash it and you're done.
Click to expand...
Click to collapse
Ok so I shouldn't install it via the ota? I keep getting the pop up to update every day.

Does using Magisk to dl / install the OTA, then patch the non-live and newly flashed partition, then finally rebooting not work?
When I was rooted that was always the easiest way.
And based upon the post 2 above this one, Magisk now supports A11 without ẞeta, right?
From Coral, with Tapatalk.

kdoggy said:
I ended up doing a full wipe and upgrade to Android 11 Oct 2020.
I have Magisk running with the SQL Lite mods for Google Pay and obviously I have root so I'm basically back where I was on Android 10.
I hadn't use Xposed yet and I don't know if I will yet. I was using Viper Audio mod but I don't know if I noticed a major difference, mostly I just stream bluetooth in my SUV.
So far, so good.
Click to expand...
Click to collapse
How is 11 for you going so far, I am thinking in reverting back to 10, battery is awful on 11

Hey Whats up with Magisk?

Has anyone else noticed that magisk has stopped working? The latest addition? There is no longer any access to hide magisk features with the latest features?
For instance for Pokemon Go to work on a custom rom you need magisk hide to hide magisk an hide from app.
I cannot even get it to open after it forces update?

Bryceicle1971 said:
Has anyone else noticed that magisk has stopped working? The latest addition? There is no longer any access to hide magisk features with the latest features?
For instance for Pokemon Go to work on a custom rom you need magisk hide to hide magisk an hide from app.
I cannot even get it to open after it forces update?
Click to expand...
Click to collapse
Happy new year. Maybe reinstall Magisk manager? For me it works perfectly, just be sure to install 21.2 magisk and you should be good to go.

Slim K said:
Happy new year. Maybe reinstall Magisk manager? For me it works perfectly, just be sure to install 21.2 magisk and you should be good to go.
Click to expand...
Click to collapse
I actually listened to another members post an have had success flashing an rooting 3 roms that I could not do either of those with. Apparently there is some kind of conflict bwteeen something in android 10 an android 11. So Ofox 12.0.6 an global firmware for surya 12.0.3.0 are the solutions.
Magish 21.0 worked every time with an android 11. Neither 21.1 or 21.2 worked for me with A11 roms. Only magisk 21 had full functionality

Bryceicle1971 said:
I actually listened to another members post an have had success flashing an rooting 3 roms that I could not do either of those with. Apparently there is some kind of conflict bwteeen something in android 10 an android 11. So Ofox 12.0.6 an global firmware for surya 12.0.3.0 are the solutions.
Magish 21.0 worked every time with an android 11. Neither 21.1 or 21.2 worked for me with A11 roms. Only magisk 21 had full functionality
Click to expand...
Click to collapse
Weird . For me it was the opposite. I had to flash global MIUI 12.0.4.0 to make anything custom work. Until I upgraded to 12.0.7.0, ever since everything works perfectly. Magisk below 21.0 never worked for me on this device.
I have a hypothesis, that all device variants (Indonesian, European, global, Russian) have different vendors and not 100% compatible, Maybe different modem configuration as well. I noticed in mine (European version) that LTE battery consumption is a lot better (by 2hrs SOT!!!) so i'm confused on what to do. Should I stay on MIUI with all it's issues or switch to a custom ROM and lose 1-2 hours of screen on time.

Slim K said:
Weird . For me it was the opposite. I had to flash global MIUI 12.0.4.0 to make anything custom work. Until I upgraded to 12.0.7.0, ever since everything works perfectly. Magisk below 21.0 never worked for me on this device.
I have a hypothesis, that all device variants (Indonesian, European, global, Russian) have different vendors and not 100% compatible, Maybe different modem configuration as well. I noticed in mine (European version) that LTE battery consumption is a lot better (by 2hrs SOT!!!) so i'm confused on what to do. Should I stay on MIUI with all it's issues or switch to a custom ROM and lose 1-2 hours of screen on time.
Click to expand...
Click to collapse
I've sorted everything out. I recommend the firmware you already use for android 11 custom roms. One rom I read other guides for an watched YouTube guides. It's EvolutionX 5.2. It has basically converted my Poco X3 NFC global into a Google pixel 5.
This rom is head an shoulders the best rom for our device. It only needs firmware 12.0.7.0. Which I also found solved all issues an to be flashed from the phones internal memory.
It's beautiful. No bugs. I only use that new twrp ending in 15 an magisk 21. Newer magisks fail to root.
But yes could be to do with different countries.
Edit: Evolution is not the highest benchmarking. An is not the fastest. Its an all round rom for daily driver use. Antutu bench's in the mid 270-280k area.

[Help Please] Setting up Magisk on Lineage 18.1

Hello everyone. Long time since I had an android device and I'm cutting the chains of my iPhone wanting to be de-Googled and de-Appled. I was running Lineage 17.1 from Microg and thought I had everything working on it until I started updating some software on my phone over the air. I rebooted and it went to bootloop. Since then I re-installed 17.1 and got things working again. I just upgraded to 18.1 and want to make sure it's all set up properly and won't have any errors.
Magisk says SafetyNet has an "SafetyNet API Error." "Basicintegrity, ctsProfile, evalType N/A." all in red when I check if it's working. I've done some digging, but want to make sure I do this right. I need to get the boot.img file from the original firmware. Should I get this from the oneplus website, or should I be looking for something else since I have Lineage? Can anyone provide the raw boot.img file for the OnePlus 7 Pro that I should use? I'm a little overwhelmed with all of the steps to extract it from the original firmware. Please and thanks for any help getting this phone set up the way I need it to work!

That error show when safety net API download was incomplete/corrupt, you can try to erase data from magisk manager and check safetynet again but with a better internet connection or use another magisk version like canary
And if you end in a bootloop for any magisk module just turn off your device and in your computer in a CMD/powershell/terminal window enter this command
adb wait-for-device shell magisk --remove-modules
Then connect and turn on your phone and automatically your phone will reboot with all your magisk modules disabled

Use magisk canary bro,,,

I sideloaded Canary and still get the red SafetyNet API error screen after opening it. Can someone direct me to a full tutorial on how Magisk works and what the modules do? I'm thinking I might need to do a full uninstall of Magisk and start over. If I do this will I lose all the data on the phone and have to start from scratch? Thanks for your help so far!

Well I've spent several hours researching tutorials and typing in codes via Terminal on my Mac and have gotten the phone restocked twice and working normal on stock OS, but after putting TWRP on it and then installing Lineage 18.1 it goes into a Lineage logo boot loop. What am I missing here?
It seems to me that TWRP is not compatible with Lineage. Sometimes when I rebooted the phone and was playing with the Recovery.IMG I saw the Lineage Recovery, then other times the TWRP would flash on and off in a boot loop. I have been careful about using the command " ./fastboot boot TWRP.img " and not "flash" TWRP, as would be the case for non a/b storage devices. On a couple occasions I could reboot with the Lineage Recovery.IMG and it would boot to startup, but if I rebooted to Recovery from the home screen, it would get stuck on TWRP.
I'm probably just missing something simple, but what might I be doing wrong? Is it the timing of installing TWRP and then installing Lineage in the same TWRP session?
This all stemmed from me wanting to get TWRP with Lineage 18.1 and getting Magisk and Microg working correctly for a "de-googled" phone with working apps. I'm frustrated, but will keep trying if I can get some direction. Thanks for your input.
-L

Lear31pilot said:
Well I've spent several hours researching tutorials and typing in codes via Terminal on my Mac and have gotten the phone restocked twice and working normal on stock OS, but after putting TWRP on it and then installing Lineage 18.1 it goes into a Lineage logo boot loop. What am I missing here?
It seems to me that TWRP is not compatible with Lineage. Sometimes when I rebooted the phone and was playing with the Recovery.IMG I saw the Lineage Recovery, then other times the TWRP would flash on and off in a boot loop. I have been careful about using the command " ./fastboot boot TWRP.img " and not "flash" TWRP, as would be the case for non a/b storage devices. On a couple occasions I could reboot with the Lineage Recovery.IMG and it would boot to startup, but if I rebooted to Recovery from the home screen, it would get stuck on TWRP.
I'm probably just missing something simple, but what might I be doing wrong? Is it the timing of installing TWRP and then installing Lineage in the same TWRP session?
This all stemmed from me wanting to get TWRP with Lineage 18.1 and getting Magisk and Microg working correctly for a "de-googled" phone with working apps. I'm frustrated, but will keep trying if I can get some direction. Thanks for your input.
-L
Click to expand...
Click to collapse
TWRP is not working for OOS11 or A11 ROMs using Oos11 blobs.

Lossyx said:
TWRP is not working for OOS11 or A11 ROMs using Oos11 blobs.
Click to expand...
Click to collapse
Got it! I'll go back to 17.1 Thanks!

Bump
Still trying to find a solution. I get fairly far into flashing the ROM, getting TWRP working and then end up stuck at Microg not letting me open the location menu. If only there were a guide with start to finish Lineage 17.1 or 18.1 with Microg and Magisk for my OnePlus 7 Pro. I find some guides, but there isn't one that encompasses everything that actually works. I'm going to try Lineage 18.1 with Microg built in and then flash Magisk.

Lear31pilot said:
Bump
Still trying to find a solution. I get fairly far into flashing the ROM, getting TWRP working and then end up stuck at Microg not letting me open the location menu. If only there were a guide with start to finish Lineage 17.1 or 18.1 with Microg and Magisk for my OnePlus 7 Pro. I find some guides, but there isn't one that encompasses everything that actually works. I'm going to try Lineage 18.1 with Microg built in and then flash Magisk.
Click to expand...
Click to collapse
I never installed lineage but i guess you can flash the ROM, change slots, then format data(this will erase all your stuff) and flash magisk then reboot into system
And for the safety net error yesterday was released a "fix" for that so try again

RokCruz said:
I never installed lineage but i guess you can flash the ROM, change slots, then format data(this will erase all your stuff) and flash magisk then reboot into system
And for the safety net error yesterday was released a "fix" for that so try again
Click to expand...
Click to collapse
Thank you. I'll have to address this at some point. I got the phone restocked, and flashed 18.1 Lineage on it again. Got all my apps and accounts back up on it. I'm just debating running Magisk again knowing that I'll likely have to start from scratch again. I wasn't able to get TWRP working correctly, so I left Lineage Recovery on, so it will be some time before I try going through this again. I'm going to do some research on what exactly is happening when I put recoveries and ROMs on different slots. Same goes for the Magisk. It's all quite new to me with the "slots" and what information has to go on which slot. I also need to find out how to backup my apps so if I re-flash a ROM, it's not so painful to get my data back on the phone.
At least I have a working phone without a Google login and most of the apps I want work. I'm only missing Lyft and my bank app. Again, thanks for the reply, and I'll look into this when I have some time to play with the phone again.

Lear31pilot said:
Thank you. I'll have to address this at some point. I got the phone restocked, and flashed 18.1 Lineage on it again. Got all my apps and accounts back up on it. I'm just debating running Magisk again knowing that I'll likely have to start from scratch again. I wasn't able to get TWRP working correctly, so I left Lineage Recovery on, so it will be some time before I try going through this again. I'm going to do some research on what exactly is happening when I put recoveries and ROMs on different slots. Same goes for the Magisk. It's all quite new to me with the "slots" and what information has to go on which slot. I also need to find out how to backup my apps so if I re-flash a ROM, it's not so painful to get my data back on the phone.
At least I have a working phone without a Google login and most of the apps I want work. I'm only missing Lyft and my bank app. Again, thanks for the reply, and I'll look into this when I have some time to play with the phone again.
Click to expand...
Click to collapse
TWRP can't boot in devices with OOS 11 blobs and encrypted data, for Magisk the only way I can imagine is using a patched boot.img.
Make a backup of your current boot.img(lineage) with apps like Franco kernel, then Patch it with magisk, then flash it in fastboot (fastboot flash boot boot.img)
if something woes wrong you can restore the backup from Franco kernel

RokCruz said:
TWRP can't boot in devices with OOS 11 blobs and encrypted data, for Magisk the only way I can imagine is using a patched boot.img.
Make a backup of your current boot.img(lineage) with apps like Franco kernel, then Patch it with magisk, then flash it in fastboot (fastboot flash boot boot.img)
if something woes wrong you can restore the backup from Franco kernel
Click to expand...
Click to collapse
Thanks RokCruz,
I'm going to get 18.1 back on with the LOS Recovery again. I'll try the boot patch method with the LOS boot.img from 18.1 for Magisk. I haven't tried the Franco kernel as I just now found out about it. I don't really need to do anything else fancy with the phone in terms of overclocking or underclocking. Does that kernel facilitate easier backups? I'm still learning a LOT about how Android works. It's been a steep learning curve. Fortunately, I can get myself out of any binds with a restock and fastboot!

Lear31pilot said:
Thanks RokCruz,
I'm going to get 18.1 back on with the LOS Recovery again. I'll try the boot patch method with the LOS boot.img from 18.1 for Magisk. I haven't tried the Franco kernel as I just now found out about it. I don't really need to do anything else fancy with the phone in terms of overclocking or underclocking. Does that kernel facilitate easier backups? I'm still learning a LOT about how Android works. It's been a steep learning curve. Fortunately, I can get myself out of any binds with a restock and fastboot!
Click to expand...
Click to collapse
Yes only for boot backups, I always made a backup of my boot.img of every OB just in case something goes wrong but i have never experienced that.
I personally prefer OOS, just install custom kernel and some mods like Cyberpunk 2077 theme, Riru Lsposed and a adbloker and that's all I need

RokCruz said:
Yes only for boot backups, I always made a backup of my boot.img of every OB just in case something goes wrong but i have never experienced that.
I personally prefer OOS, just install custom kernel and some mods like Cyberpunk 2077 theme, Riru Lsposed and a adbloker and that's all I need
Click to expand...
Click to collapse
I'm trying to de-google. Can I de-google on OOS? Most stock ROMs require a google login.

Lear31pilot said:
I'm trying to de-google. Can I de-google on OOS? Most stock ROMs require a google login.
Click to expand...
Click to collapse
I guess you can, just use a debloater
But it's better to install HydrogenOS just disable Chinese apps, install micro g and it's complements and you can run any Google dependant app, safety net passes without problems too.
I installed hydrogen and it runs smoothly but Cyberpunk isn't available for it so I reinstalled OOS

RokCruz said:
I guess you can, just use a debloater
But it's better to install HydrogenOS just disable Chinese apps, install micro g and it's complements and you can run any Google dependant app, safety net passes without problems too.
I installed hydrogen and it runs smoothly but Cyberpunk isn't available for it so I reinstalled OOS
Click to expand...
Click to collapse
Thanks for the tip about Hydrogen. I'll do some research on that. And thanks for getting back so quickly. The Android community really has some great people. Happy to be apart of it!

So
Lear31pilot said:
Thanks for the tip about Hydrogen. I'll do some research on that. And thanks for getting back so quickly. The Android community really has some great people. Happy to be apart of it!
Click to expand...
Click to collapse
So at the end of the day, I ended up with HydrogenOS 11 and have F-Droid and Aurora Store installed and working fine. I didn't/don't need Magisk or MicroG since HOS apparently is OK'd by google and all of my apps work.
So this worked perfectly for me. I have a fully functional OS and no Google sign-in needed. I did as you said and just deleted the Chinese bloat apps. I can't manage to get rid of the "Market" app though.
Lyft works and all of my location requiring apps like Waze work as well. Thanks for pointing me in the right direction.
Question: Will OxygenOS work the same without a google login? If so, what would be the advantage of HOS vs OOS? HOS 11 has an entire section devoted to a Google login for different services. I left it blank, but just wondering what the difference would be on OOS.

Lear31pilot said:
So
So at the end of the day, I ended up with HydrogenOS 11 and have F-Droid and Aurora Store installed and working fine. I didn't/don't need Magisk or MicroG since HOS apparently is OK'd by google and all of my apps work.
So this worked perfectly for me. I have a fully functional OS and no Google sign-in needed. I did as you said and just deleted the Chinese bloat apps. I can't manage to get rid of the "Market" app though.
Lyft works and all of my location requiring apps like Waze work as well. Thanks for pointing me in the right direction.
Question: Will OxygenOS work the same without a google login? If so, what would be the advantage of HOS vs OOS? HOS 11 has an entire section devoted to a Google login for different services. I left it blank, but just wondering what the difference would be on OOS.
Click to expand...
Click to collapse
Market can be disabled if my mind serve me right, OOS could end in a bootloop if we remove all Google apps so it's better not to do that.
I never see that section, I only installed OB1 and OB2 and never see that.

And remember you need to install magisk in order to pass safetynet.

RokCruz said:
Market can be disabled if my mind serve me right, OOS could end in a bootloop if we remove all Google apps so it's better not to do that.
I never see that section, I only installed OB1 and OB2 and never see that.
Click to expand...
Click to collapse
Looks like I'm denied the ability to disable the Market App.
Photo's attached for the Google settings I have available on HOS 11.
Also unable to make the microphone work in the keyboard for voice to text, but I have a feeling I won't be able to make that work without logging in to Google. Currently looking for some workarounds.
What will passing Safetynet allow me to do that I'm not already able to do now? Use banking apps and "tap to pay" type apps? I haven't found my bank app on the Aurora Store just yet. "US Bank" if it makes a difference.
I'll continue to play with this OS, but so far, it seems the easiest to get working right from the get-go.

Question [HELP]Fat fingered OOS12 OTA update on rooted stock OOS11 and now I have no touch input.

Hello all,
I ****ed up, what I feel is big time?
I accidentally fat fingered the "install and restart" button for an OTA update for OOS12 on my rooted stock OOS11. From what I learned during my research phase of rooting my OP9, that's a big no no and can cause a lot of problems. When the phone booted back up I have no touch input at all. I have a mouse plugged into my phone and can use the phone that way and I am currently backing up as much as I can in the event I have to wipe my phone.
My question is, can I just dirty flash the previous OOS11 image I was running to go back to before the OOS12 OTA got applied? Just wanted to get the general consensus before I ruin my **** further.
I'm running stock recovery, stock OOS11.2.4.4 with Magisk, MagiskHide and not much else.
Much appreciated!

To my what i know you have to downgrade from 12 to 11 ect. I managed to get to global.
I messed up, and updated mine to 12. and from what i learned. my touch screen did not work due to the fact my update was for a global 9 pro, Not my oneplus 9-tmobile version. In the end I had to use the india msm tool to get back to working

warglock said:
Hello all,
I ****ed up, what I feel is big time?
I accidentally fat fingered the "install and restart" button for an OTA update for OOS12 on my rooted stock OOS11. From what I learned during my research phase of rooting my OP9, that's a big no no and can cause a lot of problems. When the phone booted back up I have no touch input at all. I have a mouse plugged into my phone and can use the phone that way and I am currently backing up as much as I can in the event I have to wipe my phone.
My question is, can I just dirty flash the previous OOS11 image I was running to go back to before the OOS12 OTA got applied? Just wanted to get the general consensus before I ruin my **** further.
I'm running stock recovery, stock OOS11.2.4.4 with Magisk, MagiskHide and not much else.
Much appreciated!
Click to expand...
Click to collapse
I would def recommend just MSM back to stock 11.2.4.4, I was in your same situation before and I always had the touchscreen issues if I was rooted when I upgraded to OOS12. I think I tried flashing back to 11 and just ended up soft bricking my device and having to MSM anyway. Also like the commenter said above I had to use the Indian MSM but Ive been able to use the Global MSM now with no issues so if thats what your're on Id recommend trying that one first and only using the Indian MSM if that one gives you errors.

So I'm running into this same problem and absolutely can not upgrade to OOS12. Each time, by display will not respond to touch. I went back to 11 via MSM (HAD TO USE OP9 Pro INDIA) because OP screwed something up with these phones.
I have tried multiple ways, went back to OOS 11, installed latest OOS 11 without root. Locked bootloader, Installed latest OOS 11 twice via system update to make sure everything was clean. Installed OOS 12 update and same problem.

Same problem here.....
I have installed the msm india and then the official android 11 for OP 9. After that the OP9 runs on Android 11. After that i have closed the bootloader and try the msm with the eu rom and i gets the "device not match image" error. Maybe i have the new rom for op9 installed and the productnumber is still on op9p ? Now i am going back to a custom rom. is there an option to get the fully working camera on a custom rom?

DerBaLu841 said:
Same problem here.....
I have installed the msm india and then the official android 11 for OP 9. After that the OP9 runs on Android 11. After that i have closed the bootloader and try the msm with the eu rom and i gets the "device not match image" error. Maybe i have the new rom for op9 installed and the productnumber is still on op9p ? Now i am going back to a custom rom. is there an option to get the fully working camera on a custom rom?
Click to expand...
Click to collapse
To get back to the correct ROM, boot to TWRP and flash the signed full zip to each slot.

Need help updating metro version moto one 5g ace from 10 to 11. Rooted

Title says is all, well not all. This would literally be the first update the phone got, I rooted day one out the box and keep the same firmware for flashing when switching roms, now that root is detected with a game, yes my root is depended on access to certain things, so I'm constantly rooting doing what is needed then uninstalling magisk. Very tiring. I wanted to get to Android 11, hoping no data loss, rooted if able and twrp if available for Android 11 on this one. Any pointers in the right direction would be helpful, thanks in advanced

Without taking the OTA update, I know of nothing that will get you to 11 without wiping your data. (That is why backups are good.) lolinet has 11 firmware. TWRP can be had on Telegram. Magisk is available on the github.

RETIEF said:
Without taking the OTA update, I know of nothing that will get you to 11 without wiping your data. (That is why backups are good.) lolinet has 11 firmware. TWRP can be had on Telegram. Magisk is available on the github.
Click to expand...
Click to collapse
I have all the files needed, even without root ota says you up to date security patch January 2021 lol. I heard somewhere to edit the fstab to not auto reboot, kinda like Odin with Samsung's. Then flash thru twrp, thinking that would delete twrp, but hey is 11 really better?

I don't think you can flash a stock ROM with TWRP. No, I don't think 11 is better. That is just my opinion.

RETIEF said:
I don't think you can flash a stock ROM with TWRP. No, I don't think 11 is better. That is just my opinion.
Click to expand...
Click to collapse
I honestly hate everything after 5 lol. 10 is frustrating. 11 has rw I'm doing it, hell 5g speeds 200 apps, 10 minutes lol and for splifs and giggles, imma try thru twrp, replacing recovery.img with twrp, vbmeta blanked then go into service file and flanh file and change the md5, what could go wrong?

Let us know how that worked out I have Moto one 5ga's with Comcast, mine is also rooted.