Develop Bugs

XT1064 Lollipop Root

Step 1: Download this: http://downloads.codefi.re/savoca/root/titan
Step 2: fastboot flash boot xt1064_lollipop_boot.img
Step 3: Flash SuperSU
http://imgur.com/jJO86tC

Unlocked boot-loader needed right?

surenzxx said:
Unlocked boot-loader needed right?
Click to expand...
Click to collapse
Of course.

savoca said:
Of course.
Click to expand...
Click to collapse
Do you know if any custom recoveries work on Lollipop at the moment?

surenzxx said:
Do you know if any custom recoveries work on Lollipop at the moment?
Click to expand...
Click to collapse
I'm using TWRP 2.8.0.1, only used it to backup/restore boot partition a few times and install SuperSU.

Did you have your boot-loader unlocked before your install of Lollipop?
I had to re-lock mine to install the OTA and I just finished unlocking it again. I think it's stuck on a bootloop. I'm also not able to boot into Android recovery. Any ideas?
EDIT: Nevermind; sorry for the mistake. It's booting back up.

surenzxx said:
Did you have your boot-loader unlocked before your install of Lollipop?
I had to re-lock mine to install the OTA and I just finished unlocking it again. I think it's stuck on a bootloop. I'm also not able to boot into Android recovery. Any ideas?
Click to expand...
Click to collapse
No I just uninstalled Xposed, restored stock recovery, took the OTA and moved on. You may have to restore factory firmware from fastboot.

savoca said:
No I just uninstalled Xposed, restored stock recovery, took the OTA and moved on. You may have to restore factory firmware from fastboot.
Click to expand...
Click to collapse
Thanks for your help. So we just flash the .img, flash SuperSu from the site, and fastboot flash recovery? Thanks again.
EDIT: Uh, I'm not booting past the unlocked bootloader screen after flashing your .img.
EDIT 2: I'm just a person that worries a lot. Gave it a few minutes to load and it works. Thanks. Really sorry to discredit you.
EDIT 3: Thanks man.
{
"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"
}

I can't seem to get root, I flash superSu after the boot img but still no root
edit: nevermind I figured it out thanks!

Hello.
Are you using chainfires method as described here https://plus.google.com/app/basic/stream/z13fjtr4voemxt4ph04cjl1aoor5ezninhc
Does this method set all selinux permissive or just the part that will allow the root daemon to be called at init?
Also have you tried modifying the hosts file? Does it work?
Sent from my XT1064 using XDA Free mobile app

Which Version of SuperSU are you flashing?
2.16?
Beta 2.17 or 2.19?
Greetz

savoca said:
I'm using TWRP 2.8.0.1, only used it to backup/restore boot partition a few times and install SuperSU.
Click to expand...
Click to collapse
Did you use these?
90948cf5c618f3dd3c3c8bd9f4b217a8 *TWRP_2.8.0.1_Titan_v2.img
75470360687a16f08289d81bc58f1130 *UPDATE-SuperSU-v2.16.zip
They worked fine for me on 4.4.4, just like verification for the "warm fuzzy."

who_ohw said:
Hello.
Are you using chainfires method as described here https://plus.google.com/app/basic/stream/z13fjtr4voemxt4ph04cjl1aoor5ezninhc
Does this method set all selinux permissive or just the part that will allow the root daemon to be called at init?
Also have you tried modifying the hosts file? Does it work?
Sent from my XT1064 using XDA Free mobile app
Click to expand...
Click to collapse
All I did allow the su daemon to init from the ramdisk - similar to how custom ROMs implement this.
luckiesjohnny said:
Which Version of SuperSU are you flashing?
2.16?
Beta 2.17 or 2.19?
Greetz
Click to expand...
Click to collapse
fathergweedo said:
Did you use these?
90948cf5c618f3dd3c3c8bd9f4b217a8 *TWRP_2.8.0.1_Titan_v2.img
75470360687a16f08289d81bc58f1130 *UPDATE-SuperSU-v2.16.zip
They worked fine for me on 4.4.4, just like verification for the "warm fuzzy."
Click to expand...
Click to collapse
Yes to the TWRP, (though we should make it an official build )
And 2.16 worked for me but I am currently using this: http://imgur.com/nYiwW7L

Thanks a lot.
I've tried it already with 2.19 and it worked fine.

savoca said:
All I did allow the su daemon to init from the ramdisk - similar to
Yes to the TWRP, (though we should make it an official build )
And 2.16 worked for me but I am currently using this: http://imgur.com/nYiwW7L
Click to expand...
Click to collapse
Gracias. Will get it later today...

ok... so how do i get past the whole mismatched partition size block that has also kept me from flashing a custom recovery?

Bobboman said:
ok... so how do i get past the whole mismatched partition size block that has also kept me from flashing a custom recovery?
Click to expand...
Click to collapse
If you're talking about the line in the bootloader, just ignore it. Your recovery still flashed.

yea i figured that out...however now i can't even boot my moto g to anything but the bootloader
thank god i have the 4.4.4 stock files on my laptop, time to get flashing...anyone got a link to the most recent version of supersu?

Will this work on XT1063 variant, or will it require a separate kernel patch?

blah i think i bricked my phone, i cant get past the moto logo, but i can get into the bootloader, not that helps anything

OTA update after rooting

Hi. I have just rooted my Pixel 2 XL with Magisk after reading the guides here on XDA. This is my first Android phone and my first time rooting so I'm trying to figure out the update situation here. How would I go about installing version 8.1 when I get the OTA update for it? Would I have to wipe my device again and reinstall Magisk?
On a side note, does anyone know if MinMinGuard on systemless Xposed breaks SafetyNet?
Thanks in advance.

Unroot, apply OTA, re-root.

I have not yet done this myself, I will soon though. https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips

dyingearth said:
Unroot, apply OTA, re-root.
Click to expand...
Click to collapse
Can you install OTA with unlocked bootloader?

dyingearth said:
Unroot, apply OTA, re-root.
Click to expand...
Click to collapse
Thanks. Would this remove all of my data?

darkfire404 said:
Thanks. Would this remove all of my data?
Click to expand...
Click to collapse
OTA does not remove your data. What you do want to do is to download the factory image to get the 8.1 boot.img after you're done with OTA. You can then follow instruction on rooting it.
Basically to apply 8.1 OTA, get the previous boot.img and reapply it to your phone:
Unroot:
adb reboot bootloader
fastboot flash boot boot.img
fastboot reboot
Apply OTA
download the OTA zip
follow instruction at https://developers.google.com/android/ota for apply ota
Reroot
download 8.1 image. extract it to get boot.img.
follow instruction for magisk

dyingearth said:
OTA does not remove your data. What you do want to do is to download the factory image to get the 8.1 boot.img after you're done with OTA. You can then follow instruction on rooting it.
Basically to apply 8.1 OTA, get the previous boot.img and reapply it to your phone:
Unroot:
adb reboot bootloader
fastboot flash boot boot.img
fastboot reboot
Apply OTA
download the OTA zip
follow instruction at https://developers.google.com/android/ota for apply ota
Reroot
download 8.1 image. extract it to get boot.img.
follow instruction for magisk
Click to expand...
Click to collapse
This looks good. But for following section:
Code:
Unroot:
adb reboot bootloader
fastboot flash boot boot.img
fastboot reboot
can I get only the stock 8.0 boot.img (I would like to avoid downloading 1 GB+ of stock 8.0 image to get 50 MB of boot.img, if that's possible at all)?
Oh I see an option in Magisk Manager, never mind my question
{
"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"
}
Nitin

turboencab said:
I have not yet done this myself, I will soon though. https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Click to expand...
Click to collapse
Did it work?

Cowbell_Guy said:
Did it work?
Click to expand...
Click to collapse
I don't know, I got impatient and sideloaded the OTA. I essentially followed the procedure listed by dyingearth in post #6 above.

Just went to do this but Magisk says Stock Backup Doesn't Exist... I didn't delete anything, anyone know why this would happen? And now the question is... How do I go about getting an update with forking my phone? I don't mind freshly doing it all over from scratch, but would like to get Magisk to backup the stock stuff so that when I follow the OTA instrustions on the Magisk link tips it would work.

OTA
I'm on rooted Pixel XL 2 already on 8.1, can I take the security patch, or do I need to unroot before taking the update?
nitin.chobhe said:
This looks good. But for following section:
Code:
Unroot:
adb reboot bootloader
fastboot flash boot boot.img
fastboot reboot
can I get only the stock 8.0 boot.img (I would like to avoid downloading 1 GB+ of stock 8.0 image to get 50 MB of boot.img, if that's possible at all)?
Oh I see an option in Magisk Manager, never mind my question
Nitin
Click to expand...
Click to collapse

Bump

Following.
My 2xl unrooted today. On it's own. Went to break around 3 and had magisk notification about installing 15.3zip which I was already on. Looked in manager and it showed not installed. Have been reading yesterday about updating while rooted. Checked system update and shows available update today. So I tried to install but failed. Looks like I'll have to wait till after work....at 7pm!!

After taking ota update with magisk installed did not reboot through Magisk so I lost root. Magisk is still on phone but not installed. How to reinstall? Do I need to reflash or can I just hit install on app? Will gladly provide more info aas needed. I have searched and did not find a exact answer to my problem. Build number pq3a.190801.002

You need to sideload ota manually for updates

prot- said:
You need to sideload ota manually for updates
Click to expand...
Click to collapse
I can't figure out how it took the ota in the first place with no errors. I found the guide on how to do the ota with it installed but after i got the ota. When I open the Magisk it says i can install Magisk and Magisk Manager from the app. Im worried it will mess something up.

The quickest and simplest way to update your phone monthly:
- download the stock taimen image for current month
- unzip and edit the 'flash-all.bat' file by removing/deleting the '-w' from the code. Removing the '-w' ensures that your data is NOT wiped
- boot into bootloader and run the 'flash-all' script from your adb folder
- after it completes the update, let the phone boot into Android
- restart and boot into TWRP. Note: decryption is broken for some people (like me), you will need to remove your PIN code before booting into TWRP
- flash Magisk 19.3 or whatever you prefer (and any additional apps you such as Vanced YouTube, etc.)
- Reboot into rooted phone
- Add your PIN code (or whatever security measure you want to use)
If you need a more detailed information, please check the main rooting thread.

OP follow this exactly, and you will have no problems. https://forum.xda-developers.com/showpost.php?p=80039116&postcount=778

[GUIDE] how to fix Superuser dialog box not popping up/denying root on MIUI 11

Step 1. go to the 'Security' app
{
"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"
}
Step 2. Select 'Manage apps'
Step 3. Select 'Magisk manager' or 'Superuser' depending on what you rooted your phone with, in this case I'm using magisk manager
Step 4. Turn on 'Allow apps to start automatically' and 'Allow apps to be started by other apps' inside 'Autostart' and then open 'App permissions'
Step 5. Turn on 'Display pop-up windows while running in the background'
https://imgur.com/gallery/jfIw9cY

Hi
did you root on MIUI 11 or MIUI 10 and make OTA update
im on 10.4.1 and im so confused wath sould do first Root or OTA update

riyad_85 said:
Hi
did you root on MIUI 11 or MIUI 10 and make OTA update
im on 10.4.1 and im so confused wath sould do first Root or OTA update
Click to expand...
Click to collapse
Same question.
I previously hard brickes device rooted on 10.4.4 while flashing OTA 11.0.1
(Mighty Mi gave me brand new device, special thanks to Mi service).

coolvipcandy said:
Same question.
I previously hard brickes device rooted on 10.4.4 while flashing OTA 11.0.1
(Mighty Mi gave me brand new device, special thanks to Mi service).
Click to expand...
Click to collapse
Your previous device was on global or chinese version ?

riyad_85 said:
Your previous device was on global or chinese version ?
Click to expand...
Click to collapse
Indian version and the update was official OTA received but failed on TWRP (Error 7). OS Updater then downloaded full ROM automatically that eventually failed with same error.
I then tried to flash stock recovery to update, and this was last of it.

You should never take OTA updates and apply them via TWRP it hard bricks the device. Maybe in the future you might be able to but as far as right now i wouldn't attempt it. I would suggest flash stock boot img ( uninstall TWRP ) then take the OTA then reflash the TWRP.img and when rooting only use the supersu file which is archive magisk 19.4 then apply 20.0 magisk update through magisk manager. Some items take a min for the magisk grank root priv but once its granted its always there as soon as you open the app.

fastjohnson said:
You should never take OTA updates and apply them via TWRP it hard bricks the device. Maybe in the future you might be able to but as far as right now i wouldn't attempt it. I would suggest flash stock boot img ( uninstall TWRP ) then take the OTA then reflash the TWRP.img and when rooting only use the supersu file which is archive magisk 19.4 then apply 20.0 magisk update through magisk manager. Some items take a min for the magisk grank root priv but once its granted its always there as soon as you open the app.
Click to expand...
Click to collapse
so you suggest that I go from 10.4.1 to 11.0.1 via OTA uptade and root my device after
another question my devise is a global version I want to flash the Indonesian rom (call recording; call waiting message) is there any tutorial for that

fastjohnson said:
You should never take OTA updates and apply them via TWRP it hard bricks the device. Maybe in the future you might be able to but as far as right now i wouldn't attempt it. I would suggest flash stock boot img ( uninstall TWRP ) then take the OTA then reflash the TWRP.img and when rooting only use the supersu file which is archive magisk 19.4 then apply 20.0 magisk update through magisk manager. Some items take a min for the magisk grank root priv but once its granted its always there as soon as you open the app.
Click to expand...
Click to collapse
I was doing same, trying to flash the stock recovery bricked my device.

Fastboot flash boot then use just the stock boot IMG only. Don't factory reset or nothing that'll override TWRP and let it fully boot to implement stock recovery. That ditch root as well. Flashing Indonesian firmware just stay with in your os version and flash using the xiaomi mi tool. Really simple.

riyad_85 said:
Hi
did you root on MIUI 11 or MIUI 10 and make OTA update
im on 10.4.1 and im so confused wath sould do first Root or OTA update
Click to expand...
Click to collapse
Hi, sorry for the late reply, I'm using the MIUI 11 indonesian Rom with magisk 20.1, and i did the ota before rooting.

ch3510 said:
Hi, sorry for the late reply, I'm using the MIUI 11 indonesian Rom with magisk 20.1, and i did the ota before rooting.
Click to expand...
Click to collapse
thnx for your answer
your phone is Indonesian origin or you have switched from global ?
is there any tutorial for switching from global to indonesien
I found one on 4PDA but I fear being a victim of the translation google hhhhhh

I have a problem with flashing xiaomi.eu_multi_HMNote8Pro_V11.0.2.0. ROM on my Redmi note 8 pro EU version. I can install custom TWRP recovery and flashing from .zip file is going well but the phone is booting to recovery after I instalL EU ROM and I cannot install anything more because I cannot access to phone storage anymore just list of some folders with long names and if I want to copy .zip from PC to phone I cant do that at all. Only way to recover my device is to flash Fastboot ROM through Mi Flash tool and then install TWRP again and copy backup files I've made before and restore it. Can someone help me to install EU ROM?

FULL OTA OxygenOS 11.0.5.5.IN11AA (GLOBAL ROM)--Stock and magisk_patched boot.img

Hi everyone,
For those who need the boot image to root their oneplus 8pro global rom Oxygen OS 11.0.5.5.IN11AA.
I had a problem to update from rooted version 11.0.4.4.IN11AA to 11.0.5.5.IN11AA. I backed up all my files and used the MSM tool restore program to version 11.0.4.4.IN11AA then updated to version 11.0.5.5.IN11AA without encountering any error.
then I extracted the boot image to successfully root my 8pro.
GoogleDrive img link :
https://drive.google.com/drive/folders/1YdiopRnGCkx4lTuI0TMursEAVOjw85nh?usp=sharing
OnePlus8ProOxygen_15.O.35_OTA_0350_all_2103221813_3ec450423a214c40
GoogleDrive full OTA link :
https://drive.google.com/file/d/15Qxbp7pZ38CrOO0JSbLx8aFvpeFqF07J/view?usp=sharing
MD5 : 7ddceb429775242f556fb816f49f695c
OnePlus link : https://oxygenos.oneplus.net/OnePlus8ProOxygen_15.O.35_OTA_0350_all_2103221813_3ec450423a214c40.zip
{
"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"
}

Thanks!

Thanks for the work @buu'buu, but unfortunately I can't get my phone to update. It fails every time and I've tried everything short of using the MSM tool. I just don't know if an incremental update is worth wiping the phone and starting fresh. I assume you couldn't get the system update of the Oxygen updater to work either.

PieceKeepr said:
Thanks for the work @buu'buu, but unfortunately I can't get my phone to update. It fails every time and I've tried everything short of using the MSM tool. I just don't know if an incremental update is worth wiping the phone and starting fresh. I assume you couldn't get the system update of the Oxygen updater to work either.
Click to expand...
Click to collapse
I had the same problem : https://forum.xda-developers.com/t/...magisk-root-permissions.4233391/post-84526447
Backup all your apps and data, messages and call logs in the cloud, or on your phone and paste it on your PC (with SWIFT BACKUP app for exemple).
Then you can use MSM tool for a clean installation with @Some_Random_Username thread (11.0.4.4.IN11AA) : https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4084953/
Then update to version 11.0.5.5.IN11AA.
Now you can proced to the rooting.

Hello @buu'buu would you have the link for the update version of the rom 11.0.5.5IN11AA - I have the global version model IN2020, but the update does not appear.

PieceKeepr said:
Thanks for the work @buu'buu, but unfortunately I can't get my phone to update. It fails every time and I've tried everything short of using the MSM tool. I just don't know if an incremental update is worth wiping the phone and starting fresh. I assume you couldn't get the system update of the Oxygen updater to work either.
Click to expand...
Click to collapse
Providing it's a full update, you would download it then instead of just installing, go to system update, click options, then local, then locate the update and run it.
Once complete:
If you're rooted then at this point you wouldn't reboot, you'd open magisk then click install to unused slot OTA.
Then reboot
If you're not then just reboot.
Oxygen updater is the preferred way to do this, always make sure you are using the full update..
It's also possible with an incremental update.
If indeed you are rooted, is recommend stable 22.0, as it's shown to be working as expected in the EU version in my tests, as it has for the OP on the global variant.

jotha.dx said:
Hello @buu'buu would you have the link for the update version of the rom 11.0.5.5IN11AA - I have the global version model IN2020, but the update does not appear.
Click to expand...
Click to collapse
Hello @jotha.dx
No sorry, that's why I went through the MSM tool and then updated to version 11.0.5.5, all of that of course after making a backup of my data. Oxygen updater still did not offer me the latest version.
Either you have to wait or you can use my method and download the latest stable version of magisk 22 and my boot file magisk_patched to perform rooting.

dladz said:
Providing it's a full update, you would download it then instead of just installing, go to system update, click options, then local, then locate the update and run it....
It's also possible with an incremental update.
Click to expand...
Click to collapse
It's an incremental update and this is the method I tried after removing Magisk and trying to use the system update failed. Using system update goes into a loop saying that the update will continue when the phone isn't busy. Using this method just fails immediately.

PieceKeepr said:
It's an incremental update and this is the method I tried after removing Magisk and trying to use the system update failed. Using system update goes into a loop saying that the update will continue when the phone isn't busy. Using this method just fails immediately.
View attachment 5268281
Click to expand...
Click to collapse
Are you rooted?
Would flashing the stock boot image prior to accepting the update then rooting afterwards work?
Obviously extract the new boot image if you can first.
Quite odd the way the global ROM always comes out with incremental first and not full? Id have thought it would be the opposite way round?

dladz said:
Are you rooted?
Would flashing the stock boot image prior to accepting the update then rooting afterwards work?
Obviously extract the new boot image if you can first.
Quite odd the way the global ROM always comes out with incremental first and not full? Id have thought it would be the opposite way round?
Click to expand...
Click to collapse
Yes I am rooted. I tried booting the stock boot image and the update still didn't work. I then tried flashing the extracted boot.img from the full update obtained from the OnePlus support site and it failed to flash. In both cases I removed all Magisk modules first and rebooted then removed Magisk.

PieceKeepr said:
It's an incremental update and this is the method I tried after removing Magisk and trying to use the system update failed. Using system update goes into a loop saying that the update will continue when the phone isn't busy. Using this method just fails immediately.
View attachment 5268281
Click to expand...
Click to collapse
THATS THE EXACT PROBLEM IM HAVING MATE, I tried looking for the frimware on the one plus site but al they had was the beta from march 2 and the 11.0.4 etc, please let me know if u figure this out!

PieceKeepr said:
Yes I am rooted. I tried booting the stock boot image and the update still didn't work. I then tried flashing the extracted boot.img from the full update obtained from the OnePlus support site and it failed to flash. In both cases I removed all Magisk modules first and rebooted then removed Magisk.
View attachment 5268619
Click to expand...
Click to collapse
Ok so you're doing a flash "boot" command which should still work but......
Try this, but change the "magisk_patched" to whatever your boot image is called.
fastboot flash boot_a magisk_patched
Press enter.
fastboot flash boot_b magisk_patched
Press enter
Bare in mind this may still flash but may not boot, so make sure you have your stock boot image handy to recover.

dladz said:
Ok so you're doing a flash "boot" command which should still work but......
Try this, but change the "magisk_patched" to whatever your boot image is called.
fastboot flash boot_a magisk_patched
Click to expand...
Click to collapse
This worked but I was still unable to update. I tried removing Magisk completely and flashing the stock boot.img but even going that far I was still unable to update using either the system update or manually after downloading through Oxygen Updater. Thanks for trying to help with this. I don't get it.

Can someone confirm that this Oxygen OS 11.0.5.5.IN11AA fixes the DRM Widevine going to L3 for many users (rooted and unrooted)? You should be able to be rooted, and with magisk_props_config keep Widevine L1...

MetroWestMA said:
Can someone confirm that this Oxygen OS 11.0.5.5.IN11AA fixes the DRM Widevine going to L3 for many users (rooted and unrooted)? You should be able to be rooted, and with magisk_props_config keep Widevine L1...
Click to expand...
Click to collapse

But in netflix app specs

Yea -- this sucks. I just took my old OP 7 Pro, MSM'd it updated it to the new 11 release, rooted it and installed Magisk Properties and it gets L1. But my OP 8 Pro now has level L3 -- horrible.

Got it

MetroWestMA said:
Yea -- this sucks. I just took my old OP 7 Pro, MSM'd it updated it to the new 11 release, rooted it and installed Magisk Properties and it gets L1. But my OP 8 Pro now has level L3 -- horrible.
Click to expand...
Click to collapse
Look at post #72
https://forum.xda-developers.com/t/...ll-hd-official-playstore-application.4035219/

PieceKeepr said:
This worked but I was still unable to update. I tried removing Magisk completely and flashing the stock boot.img but even going that far I was still unable to update using either the system update or manually after downloading through Oxygen Updater. Thanks for trying to help with this. I don't get it.
Click to expand...
Click to collapse
what worked, you were able to root or something?

Question Help with unlocking the bootloader and root

HELLO EVERYONE
I have a few questions.
I'm still hesitant to unlock the bootloader and root my F3.
So:
When I unlock the bootloader, will I lose all my settings and data?
Do I have to root via magisk for banking payments to work?
What is the best custom rom yet? To make everything work like an original rom.
Custom rom should definitely have a very extensive adjustment, for example, the status bar - position clock, seconds in clock, etc. It should have adjusted the increased speaker volume, recording phone calls, just a lot of adjustments.
Furthermore, to make the custom rom long developed and constantly updated, including miui.
Lastly: I want to avoid brick, so some really detailed instructions on how to root through magisk and how to flash custom rom.
I would also like to use TWRP, I'm used to it from the previous mobile phone.
I have official android 11, miui 12.5.1.0 RKHEUXM.
I will unlock the bootloader, the waiting time for unlocking is over.
Thanks very much.

1. You will loose all settings and data
2. You need root with magisk to use magisk hide then you can use banking apps
3. Right now arrow os is the best available. Arrow os lacks in customisation. Although it has all customisation I need. I am not sure what you need. Its stable bug free and regularly updated. You can also try syberia os. Syberia os has more customisation options and also the dev is active in the thread. I have only used syberia for short period of time. So I can't say much about it.
4. Detailed explanation is given in rom threads. Just follow them if you encounter any problem just message someone will help you out.
5. I don't use twrp yet and suggest you the same. Cos it's still in alpha stage. If you want magisk then just boot into twrp and flash magisk. This way you won't loose arrow os recovery and also will have magisk installed.

So, will there be no problem on my current version to unlock the bootloader via the official utility mi unlock tool?
So how do I proceed, I mean root via magisk. You write that I should avoid twrp, but you also write that I should flash the magic over twrp.
I would need precise instructions please so I don't kill the device.
Thanks.

jkmaxfli said:
So, will there be no problem on my current version to unlock the bootloader via the official utility mi unlock tool?
So how do I proceed, I mean root via magisk. You write that I should avoid twrp, but you also write that I should flash the magic over twrp.
I would need precise instructions please so I don't kill the device.
Thanks.
Click to expand...
Click to collapse
There won't be any problems If you do it correctly. Install all the necessary drivers and stuff.
For rooting I told to boot into twrp. I didn't say to install twrp. There is a difference. Temporarily boot into twrp with "fastboot boot twrp.img" command and then flash magisk . This is the easy method I know of.

Ok.
So I would try syberia custom rom.
Would you have any links please to that magisk root? Thank you.

jkmaxfli said:
Ok.
So I would try syberia custom rom.
Would you have any links please to that magisk root? Thank you.
Click to expand...
Click to collapse
Magisk root should be linked in the Syberia thread

Thanks

So for now, I'll just unlock the bootloader and root with the help of magisk.
Can someone please describe to me exactly the detailed procedure and links where and what they will download?
And: for now, I'll stay on the stock rom. Will there be any way to update the stock rom if I will have root?
Thank you

No one will help?
I'd like to make it tonight.
So far only unlock bootloader and root magisk. I set everything up and save via titanium, at least the data application when Twrp is not working on backups.
Then I would try a custom rom.

I'm using ArrowOS, I'm not root and don't use Magisk. I can use my banking apps, even when they alerted me about being rooted and all that stuff. The solution I found was very easy.
Activate developer options and deactivate developer options. That's it. Nothing more.

But i need root for backup and other things that require root.

jkmaxfli said:
But i need root for backup and other things that require root.
Click to expand...
Click to collapse
You can root, then unroot by uninstall Magisk.

Ok.Thanks
One more question:
If I don't use a custom rom, but use an official rooted rom , how can I update it when new updates come out?

jkmaxfli said:
Ok.Thanks
One more question:
If I don't use a custom rom, but use an official rooted rom , how can I update it when new updates come out?
Click to expand...
Click to collapse
Same answer as #12.
Or MiFlash.

pl1992aw said:
Same answer as #12
Click to expand...
Click to collapse
jkmaxfli said:
HELLO EVERYONE
I have a few questions.
I'm still hesitant to unlock the bootloader and root my F3.
So:
When I unlock the bootloader, will I lose all my settings and data?
Do I have to root via magisk for banking payments to work?
What is the best custom rom yet? To make everything work like an original rom.
Custom rom should definitely have a very extensive adjustment, for example, the status bar - position clock, seconds in clock, etc. It should have adjusted the increased speaker volume, recording phone calls, just a lot of adjustments.
Furthermore, to make the custom rom long developed and constantly updated, including miui.
Lastly: I want to avoid brick, so some really detailed instructions on how to root through magisk and how to flash custom rom.
I would also like to use TWRP, I'm used to it from the previous mobile phone.
I have official android 11, miui 12.5.1.0 RKHEUXM.
I will unlock the bootloader, the waiting time for unlocking is over.
Thanks very much.
Click to expand...
Click to collapse
jkmaxfli said:
So for now, I'll just unlock the bootloader and root with the help of magisk.
Can someone please describe to me exactly the detailed procedure and links where and what they will download?
And: for now, I'll stay on the stock rom. Will there be any way to update the stock rom if I will have root?
Thank you
Click to expand...
Click to collapse
jkmaxfli said:
No one will help?
I'd like to make it tonight.
So far only unlock bootloader and root magisk. I set everything up and save via titanium, at least the data application when Twrp is not working on backups.
Then I would try a custom rom.
Click to expand...
Click to collapse
Just download magisk manager. Then inside, you will see on the top "Magisk" and "Application". Tap on installation next to Magisk, install Magisk by the recommended way (direct installation in English I believe). It's that simple.
When you install a OTA, after the update, don't reboot directly or Magisk will be gone. So install the OTA, DON'T REBOOT then go on Magisk manager, tap installation (Magisk) and choose the OTA way. Don't remember the exact name but you will see. By this way, Magisk will install itself on the other partition before the finalisation of the update so you will not loose Magisk after the update (OTA). I'm sorry if I'm not clear but my Magisk is in french, so I don't have the exact word in English.

Greenspoof said:
Just download magisk manager. Then inside, you will see on the top "Magisk" and "Application". Tap on installation next to Magisk, install Magisk by the recommended way (direct installation in English I believe). It's that simple.
When you install a OTA, after the update, don't reboot directly or Magisk will be gone. So install the OTA, DON'T REBOOT then go on Magisk manager, tap installation (Magisk) and choose the OTA way. Don't remember the exact name but you will see. By this way, Magisk will install itself on the other partition before the finalisation of the update so you will not loose Magisk after the update (OTA). I'm sorry if I'm not clear but my Magisk is in french, so I don't have the exact word in English.
Click to expand...
Click to collapse
{
"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"
}

Thanks guys, I'm done, I'm solving a Google pay malfunction in another thread.