Is it possible to install accent colors without root like in oreo? Or is there some way to temporarily bypass signature check to install overlay apks since they now require platform certificate??
I need that too ?
I'm searching for that I need that too
i need?
Try powershade , it's a little buggy but does the job
Powershade isn't the solution for changing accent color of whole system UI ,
We want accent colors like oreo
Adish123 said:
Powershade isn't the solution for changing accent color of whole system UI ,
We want accent colors like oreo
Click to expand...
Click to collapse
Magisk module: System Accent Theme (colors) for P.
It changes accents in whole system.
I didn`t find any other solution without root.
Not possible without root as far as I know. But fairly easy to use with Magisk and systemless Substratum module.
_mysiak_ said:
Not possible without root as far as I know. But fairly easy to use with Magisk and systemless Substratum module.
Click to expand...
Click to collapse
Substratum themes are not applying, i have rooted my phone.
Suman1408 said:
Substratum themes are not applying, i have rooted my phone.
Click to expand...
Click to collapse
Install substratum, install theme, choose what you want to theme, build it, reboot phone, apply what you have built. Between build and apply you have to reboot the phone, otherwise it won't work.
_mysiak_ said:
Install substratum, install theme, choose what you want to theme, build it, reboot phone, apply what you have built. Between build and apply you have to reboot the phone, otherwise it won't work.
Click to expand...
Click to collapse
Tried everything that you have said, but after applying the theme successfully even after reboot its neither showing in theme under display nor it is applying as default
Flash this module in magisk and you will get all the colour options in display settings.
Suman1408 said:
Tried everything that you have said, but after applying the theme successfully even after reboot its neither showing in theme under display nor it is applying as default
Click to expand...
Click to collapse
Themes should be enabled/applied in Substratum manager as the last step, not via system settings.
Don't use substratum. Root with magisk and use module that i mentioned. That's what you need. System accent color. After applying go to settings --> display and on the bottom there will be accent colors.
_mysiak_ said:
Themes should be enabled/applied in Substratum manager as the last step, not via system settings.
Click to expand...
Click to collapse
Thanks, got it. Appreciate your help !!
Xiaomi mi a1 oreo 8.0 stock. Security patch: May 5th 2018. Not working. : ((((Will it work if I flash the phone with android 8.0 with a lower security patch?
Related
EDIT: This post applies to Fire OS 4.5.n. Beginning with OS 5, Lollipop, we're able to put wallpaper on custom launchers.
This method lets you use any image for wallpaper and works with most launchers. If it doesn't work with yours and you really, really want wallpaper, try a different launcher.
This requires root and does not apply to the stock Fire launcher. You can't put wallpaper on that.
Requirements
Root
Xposed framework v. 2.6.1 from here. (Look under Show older versions for 2.6.1. Don't use experimental 2.7)
Gran PC's KindleBG module here
A file explorer to install Xposed and KindleBG
QuickPic app from the Play Store
Instructions
Install and open Xposed. Choose the Framework option and press Install/Update. Tap Reboot and say Yes at "Are you sure?" [Fire reboots].
Install KindleBG.
Run Xposed and choose Modules. Tick the KindleLockBG box. Go back to the Framework screen and reboot.
Run QuickPic and choose the image you want for wallpaper.
Open the QuickPic menu, choose Set as, and then QuickPic wallpaper.
Crop the image the way you want it and press the checkmark at top of screen.
Linker Warning with Shell Commands
With Xposed installed, Android displays a linker warning with the commands we use to block/unblock system apps. You can safely ignore this. Xposed does not cause a memory leak and, at least with the the KindleBG module, does not pose any security risk.
is this for the fire HD6 and HD7. I've heard reports of bricks due to exposed on these devices
powerpoint45 said:
is this for the fire HD6 and HD7. I've heard reports of bricks due to exposed on these devices
Click to expand...
Click to collapse
Yes, Fire HDs. I've been using Xposed on my Fire HD 7 for several days without problem. BUT FWIW, I did not install SuperSU.
EDIT: Installed SuperSU yesterday and np with Xposed through lots of boots and messing around.
DoLooper said:
Yes, Fire HDs. I've been using Xposed on my Fire HD 7 for several days without problem. BUT FWIW, I did not install SuperSU. Still using Kingroot. If you think Xposed with SuperSU is a problem, I'll edit OP.
Click to expand...
Click to collapse
DoLooper, would you care to do a detailed report on what you tried with Xposed that worked besides the wall paper? I'd like to try it, but the bricking reports scare me for now, since I don't understand fully what Xposed does.
bibikalka said:
DoLooper, would you care to do a detailed report on what you tried with Xposed that worked besides the wall paper?
Click to expand...
Click to collapse
Hey bibikalka, so far I've only done the steps I wrote--installed Xposed, the BG module and also Gran PCs module to block OTA updates. Today, I uninstalled Xposed and installed superSU, reinstalled Xposed and modules--just to make sure the SU didn't have an effect.
Better question might be what I haven't done, which is mess with any system apps or other internals. Did use JMZ's great tool to install gapps, but don't think that should matter.
Anyway, will install Gravity Box later (one of the more fun xposed modules) and keep you posted.
powerpoint45 said:
is this for the fire HD6 and HD7. I've heard reports of bricks due to exposed on these devices
Click to expand...
Click to collapse
So I scoured the Fire HD 6/7 forums for posts of bootloops/bricks caused by Xposed and everything comes back to just one post. This from @Drew123abc123 where he says:
I installed a custom boot animation, did a few system modifications and everything was working fine. But then, the next day (today) I tried to install Xposed and rebooted and got a bootloop.
Click to expand...
Click to collapse
I wouldn't wish unrecoverable bootloop on anyone, but wonder what were those mods? Did he reboot after? Did he install the xposed 2.7 (experimental) or any "unusual" modules? But that said, Xposed can put devices into bootloops--see "In case you get into a bootloop"--so I understand people being reluctant.
Only know that Xposed with the BG module is working fine on my "pretty clean" rooted HD 7--and I've got wallpaper!
DoLooper said:
So I scoured the Fire HD 6/7 forums for posts of bootloops/bricks caused by Xposed and everything comes back to just one post. This from @Drew123abc123 where he says:
I wouldn't wish unrecoverable bootloop on anyone, but wonder what were those mods? Did he reboot after? Did he install the xposed 2.7 (experimental) or any "unusual" modules? But that said, Xposed can put devices into bootloops--see "In case you get into a bootloop"--so I understand people being reluctant.
Only know that Xposed with the BG module is working fine on my "pretty clean" rooted HD 7--and I've got wallpaper!
Click to expand...
Click to collapse
Ah ok then I think this should be just fine. Too bad I lost root /:
With Nova Launcher you Doesnt need QuickPic
That's fine. This is for anyone who can't get wallpaper
Just a little bump for others who need this now.
When I try to install the Xposed Framework I get an error saying "Failed to get root access."
I just upgraded to 4.5.4 via instructions here: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
I believe I am rooted (Titanium Backup says so) but I do not see the Superuser app in my app drawer?
Edit - Just installed Superuser from the Play Store and that fixed it!
is there a way to modify the lock screen images using this process?
No. They can't be changed.
Prior to this build, changing lockscreen was not a problem..Did they remove the feature in 5.2.2u2
coolguy2488 said:
Prior to this build, changing lockscreen was not a problem..Did they remove the feature in 5.2.2u2
Click to expand...
Click to collapse
You can still block ads and get Amazon's wallpapers, but you can't put your own images on lockscreen, which I thought the OP was asking about. Vaguely remember you could use own image in Developer's Preview, which was much more AOSP. 5.2.2u2 is all Amazon all the time again.
DoLooper said:
You can still block ads and get Amazon's wallpapers, but you can't put your own images on lockscreen, which I thought the OP was asking about. Vaguely remember you could use own image in Developer's Preview, which was much more AOSP. 5.2.2u2 is all Amazon all the time again.
Click to expand...
Click to collapse
Yes I had a custom wallpaper on my lockscreen in Developer's Preview. I have since bricked that one and putting it back on there would be my last step to my new refurb. I could even rename my tablet which is greyed out now on 5.1.1.
Is it possible to downgrade back to Developer's Preview?
I would ask bibikalka in this thread: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Hello guys,
I'd like to know if it's possible to get a fully black theme (settings, notifications, all options i mean like in Substratum) with no root. It's because I just bought this phone, and don't want to lose the warranty by rooting it.
PS : Is it a significant battery saver to get a black theme, or does it just give you 5 minutes more of battery life ?
Thx
AMOLED will save battery by displaying black screens. Not just dark. It has to be black. Hex #000000, black. Basically it keeps the individual pixels off instead of turning them on to display black.
As far as I know, there's no way to fully theme everything without root. Notifications require theming of framework which will require root. Either to use Substratum or decompiling, editing & recompiling & pushing back to system.
Also, the only way I could see root voiding your warranty is if you use root to overclock your CPU to absurd voltages and short out the phone. There's a thread buried in general somewhere where someone posted chat logs from Google. They mentioned warranty could be void due to problems caused by root (like mentioned above), however unlocking the bootloader and rooting shouldn't automatically void it. I know the unlocked BL won't, not 100% on root. Then again I've sent it rooted Galaxy Nexus, rooted Nexus 5 and a rooted Nexus 6P in for warranty repairs / exchanges and was never once charged. Fully functional phones that booted and they could easily see I was unlocked, rooted & running a custom ROM, etc.
RoyJ said:
As far as I know, there's no way to fully theme everything without root. Notifications require theming of framework which will require root. Either to use Substratum or decompiling, editing & recompiling & pushing back to system.
Click to expand...
Click to collapse
Do you recommend any theming app?
neeko92 said:
Do you recommend any theming app?
Click to expand...
Click to collapse
Substratum, but again, you'll need root.
If you do go down that route, be careful theming framework on 7.1.1, it will cause boot loops. It was broken by Google who has since fixed it internally. We just need to wait for an update. Know how to recover if that happens. I'd recommend to follow Substratum Development on Google+ for more info.
In the last week I received my xperia x compact completely stock. First thing I do when I get a new phone before even activating it is root it. I was utilizing this guide to root my xperia x compact "Guide: Root + Custom Kernel + Clean rom + TA for X Compact" and I am stuck on the step where you are instructed to flash the modified XC-GenesisKernel-v1.04-nodrm kernel and SU. Flashing this kernel always results in a boot loop (Ive waited more then 30 minutes for it to resolve). I reflash the stock service exchange unit - 34.1.A.1.198 MM firmware to get back a functioning phone. The guide recommends:
"Run xperifirm and download the "service exchange unit - 34.1.A.1.198" firmware for posterity and latest rom for your region."
Am I supposed to use the most current nougat firmware for the following steps and only use the service exchange unit firmware if I need to downgrade to the lower original firmware? The thread for the XC-GenesisKernel states it is for nougat roms, which would explain a boot loop when I try to use the service exchange unit MM rom. Ideally Id like to stay on MM so that I can use xposed. Root and the phone being fully functional with no loss of camera and such is my main desire, xposed is secondary. I have a Backup TA of my DRM keys, the phone bootloader is unlocked, and I am looking for a little direction / clarification, any help in this respect is greatly appreciated.
Thanks
efaustus9 said:
help in this respect is greatly appreciated.
Click to expand...
Click to collapse
Click the first link in the guide and read it.
XperienceD said:
Click the first link in the guide and read it.
Click to expand...
Click to collapse
Thanks, I read through it and I see indeed the latest nougat firmware is what I should use in the later steps of tuten1000's guide and is the source of the boot loop I am experiencing.
If possible I would like to stay on marshmallow so I can used xposed framework. Are you aware of or can you recommend a kernel I can flash that will give me root, fingerprint, and use of most DRM functions while still on marshmallow.
Maybe you can try my guide using Magisk with full DRM, Xposed and root. But you need to flash back to MM first if you need Xposed.
https://forum.xda-developers.com/x-compact/how-to/android-pay-safety-net-rooted-unlocked-t3610342
itandy said:
Maybe you can try my guide using Magisk with full DRM, Xposed and root. But you need to flash back to MM first if you need Xposed.
https://forum.xda-developers.com/x-compact/how-to/android-pay-safety-net-rooted-unlocked-t3610342
Click to expand...
Click to collapse
Excellent itandy, this this just what I had in mind. I never downloaded and flashed a nougat rom as xposed was important to me. In following tuten1000's guide I did flash the XC genesis kernel as well as SU in recovery. This resulted in a boot loop but a prerequisite in your guide is a /system partition without any trace of su. Since I reflashed the stock service exchange unit 34.1.A.1.198 MM firmware I should be good to proceed right?
efaustus9 said:
Excellent itandy, this this just what I had in mind. I never downloaded and flashed a nougat rom as xposed was important to me. In following tuten1000's guide I did flash the XC genesis kernel as well as SU in recovery. This resulted in a boot loop but a prerequisite in your guide is a /system partition without any trace of su. Since I reflashed the stock service exchange unit 34.1.A.1.198 MM firmware I should be good to proceed right?
Click to expand...
Click to collapse
You're all good to begin with MM stock ROM.
itandy said:
You're all good to begin with MM stock ROM.
Click to expand...
Click to collapse
It worked beautifully, thank you so much itandy :victory:
Anyway to get rid of the device is not secure screen on boot?
efaustus9 said:
It worked beautifully, thank you so much itandy :victory:
Anyway to get rid of the device is not secure screen on boot?
Click to expand...
Click to collapse
This is a common request but the answer is no.
itandy said:
This is a common request but the answer is no.
Click to expand...
Click to collapse
Okay, it would be nice to be rid of but it is a worthwhile trade off.
In your guide you mention a safety net, and installing xposed breaks it. What is this safety net and what is the draw back to breaking it? Am I locked out of certain apps or functions?
efaustus9 said:
Okay, it would be nice to be rid of but it is a worthwhile trade off.
In your guide you mention a safety net, and installing xposed breaks it. What is this safety net and what is the draw back to breaking it? Am I locked out of certain apps or functions?
Click to expand...
Click to collapse
SafetyNet is the security checking API used by some apps like Android Pay and Pokemon Go to make sure your device is not tampered with. Simply put it makes sure your device is stock, not unlocked, rooted or modified. Magisk currently is able to bypass SafetyNet checking for root and some other "unwanted" apps. But Xposed will still be detected because it works in much lower system level. And with Magisk you can simply disable Xposed temporarily and reboot if you want to use, say, Android Pay.
itandy said:
SafetyNet is the security checking API used by some apps like Android Pay and Pokemon Go to make sure your device is not tampered with. Simply put it makes sure your device is stock, not unlocked, rooted or modified. Magisk currently is able to bypass SafetyNet checking for root and some other "unwanted" apps. But Xposed will still be detected because it works in much lower system level. And with Magisk you can simply disable Xposed temporarily and reboot if you want to use, say, Android Pay.
Click to expand...
Click to collapse
ah very informative, thanks again.
I installed the xposed framework SDK23 in Magisk manager, it is showing up as installed under modules in magisk but xposed is not in the app drawer and I cant seem to access it.
efaustus9 said:
ah very informative, thanks again.
I installed the xposed framework SDK23 in Magisk manager, it is showing up as installed under modules in magisk but xposed is not in the app drawer and I cant seem to access it.
Click to expand...
Click to collapse
You need to install Xposed Installer separately. Try this unofficial app.
https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
itandy said:
You need to install Xposed Installer separately. Try this unofficial app.
https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
Click to expand...
Click to collapse
Haha once again you come through. You are really helping me get this all sorted with so little fuss, I am very grateful.
This is my first xperia experience, I am coming from a samsung s3 running a KK slimrom and things are a bit different on this device. Any other pointers or recommendations for this new phone? Is there a way to make the soft key bar transparent so I can actually utilize the full 4.6"?
efaustus9 said:
Haha once again you come through. You are really helping me get this all sorted with so little fuss, I am very grateful.
This is my first xperia experience, I am coming from a samsung s3 running a KK slimrom and things are a bit different on this device. Any other pointers or recommendations for this new phone? Is there a way to make the soft key bar transparent so I can actually utilize the full 4.6"?
Click to expand...
Click to collapse
I remember there're mods (maybe Xposed modules) to make the navbar autohide. Maybe you'd also like to check out my navbar Xposed module. See my signature.
itandy said:
I remember there're mods (maybe Xposed modules) to make the navbar autohide. Maybe you'd also like to check out my navbar Xposed module. See my signature.
Click to expand...
Click to collapse
Great, I will definitely check out your app. Ideally Id like to mimic what I believe is called the "immersive mode" in supported apps. In this mode the app takes up the full screen and the icons are replaced with three persistent minimal dots.
Here's how to play fortnite with custom ROM and/or root.
Works for me Galaxy S8 G950F.
1 - disable usb debugging in developer options.
2 - Download and install Fortnite installer and Fortnite app.
3 - Enable magisk hide and hide fortnite app.
4 - Magisk manager settings and select hide magisk manager.
5 - Reboot and enjoy.
If these steps don't work for you then do this.
6 - You have to delete the following folder then do the steps in OP.
/storage/emulated/0/MagiskManager
Thanks to @ashabraja2 for letting me know about this.
callumbr1 said:
Here's how to play fortnite with custom ROM and/or root.
Works for me Galaxy S8 G950F.
1 - disable usb debugging in developer options.
2 - Download and install Fortnite installer and Fortnite app.
3 - Enable magisk hide and hide fortnite app.
4 - Magisk manager settings and select hide magisk manager.
5 - Reboot and enjoy.
Click to expand...
Click to collapse
It works! Thx
Sent from my Samsung Galaxy S8+ using XDA Labs
callumbr1 said:
Here's how to play fortnite with custom ROM and/or root.
Works for me Galaxy S8 G950F.
1 - disable usb debugging in developer options.
2 - Download and install Fortnite installer and Fortnite app.
3 - Enable magisk hide and hide fortnite app.
4 - Magisk manager settings and select hide magisk manager.
5 - Reboot and enjoy.
Click to expand...
Click to collapse
I tried this on S9 LightROM and it doesn't work for me. It just kicks me out of the game after jumping from the bus. What ROM are you running?
ashabraja2 said:
I tried this on S9 LightROM and it doesn't work for me. It just kicks me out of the game after jumping from the bus. What ROM are you running?
Click to expand...
Click to collapse
Renovate ROM. Did you hide the magisk manager also? In magisk settings?
callumbr1 said:
Renovate ROM. Did you hide the magisk manager also? In magisk settings?
Click to expand...
Click to collapse
Yes, I even used Magisk core on top. Still getting kicked. I'll try RiCE ROM then.
ashabraja2 said:
Yes, I even used Magisk core on top. Still getting kicked. I'll try RiCE ROM then.
Click to expand...
Click to collapse
It shouldn't matter about the ROM it's magisk. Try disabling OEM unlock also. For me the exact steps above work perfect.
callumbr1 said:
It shouldn't matter about the ROM it's magisk. Try disabling OEM unlock also. For me the exact steps above work perfect.
Click to expand...
Click to collapse
But if I disable OEM unlock, my phone can't get past the "Galaxy S8" splash screen. I had to reflash the stock firmware, which is not an option since I'll be out of town for a few days with no PC at hand.
ashabraja2 said:
But if I disable OEM unlock, my phone can't get past the "Galaxy S8" splash screen. I had to reflash the stock firmware, which is not an option since I'll be out of town for a few days with no PC at hand.
Click to expand...
Click to collapse
Ahh yes I see, strange. All the steps work for me and others. Ask in lightrom telegram group? Maybe yash can help
callumbr1 said:
Ahh yes I see, strange. All the steps work for me and others. Ask in lightrom telegram group? Maybe yash can help
Click to expand...
Click to collapse
I've flashed Renovate Ice on my phone and have tried all the steps you listed in OP. Does Fortnite check Knox 0x1 by any chance? (Renovate Ice does not have an OEM unlock option)
ashabraja2 said:
I've flashed Renovate Ice on my phone and have tried all the steps you listed in OP. Does Fortnite check Knox 0x1 by any chance? (Renovate Ice does not have an OEM unlock option)
Click to expand...
Click to collapse
OEM unlock should be optional. Fortnite only checks for adb and it uses safety net. So long as magisk the apk is hidden (in magisk settings) and Fortnite is hidden (magisk hide) it should work for you also. There is a file you can edit to bring the OEM toggle back if you wanna try that
just delete magiskmanager folder .....will surely work give it a reboot
callumbr1 said:
OEM unlock should be optional. Fortnite only checks for adb and it uses safety net. So long as magisk the apk is hidden (in magisk settings) and Fortnite is hidden (magisk hide) it should work for you also. There is a file you can edit to bring the OEM toggle back if you wanna try that
Click to expand...
Click to collapse
So I've figured it out, and I'll leave this here incase anyone else reads this. You have to delete the following folder then do the steps in OP.
/storage/emulated/0/MagiskManager
Thanks for the help man, appreciate it.
ashabraja2 said:
So I've figured it out, and I'll leave this here incase anyone else reads this. You have to delete the following folder then do the steps in OP.
/storage/emulated/0/MagiskManager
Thanks for the help man, appreciate it.
Click to expand...
Click to collapse
Thanks buddy I'll add to OP
s9 port rom with su install no magisk. any one?
mtayabkk said:
s9 port rom with su install no magisk. any one?
Click to expand...
Click to collapse
Need magisk, for magisk hide
Hey, I am using Cherish OS with no magisk but still I cannot get into the game
I haven't flashed magisk yet and my usb debugging is also on
jeet2114 said:
Hey, I am using Cherish OS with no magisk but still I cannot get into the game
I haven't flashed magisk yet and my usb debugging is also on
Click to expand...
Click to collapse
Try installing magisk and use magisk hide to hide fortnite then hide magisk apk
Hi XDA community,
I will receive my new OnePlus Pro 8 tomorrow.
This will be my first OnePlus phone and it will likely be the North American version.
Primarily, I would like to unlock the bootloader and root the phone, additionally also have the Dual-sim functionality enabled.
I don't have a lot of experience with rooting, but can follow steps and instructions
1) Should I start the new phone let it update all the way to oxygen OS 11 and than follow steps to unlock the bootloader and root the phone and than transfer my data? - Will this process be more complicated than doing it with Oxygen OS 10.?
2) Once the phone is rooted, can I transfer data from my old phone through the USB/Phone/data transfer apps so it gets setup automagically ?
3) Does TWRP work with OS 11 ? if not is there an update schedule for it?
4) Does Dual Sim for NA phones work with Oxygen OS 10 or is it enabled only at Oxygen OS 11 ?
Any things else that I should be aware of? (this process or the phone in general as well?)
Thank you all
DV
Peace.
dvartak said:
Hi XDA community,
I will receive my new OnePlus Pro 8 tomorrow.
This will be my first OnePlus phone and it will likely be the North American version.
Primarily, I would like to unlock the bootloader and root the phone, additionally also have the Dual-sim functionality enabled.
I don't have a lot of experience with rooting, but can follow steps and instructions
1) Should I start the new phone let it update all the way to oxygen OS 11 and than follow steps to unlock the bootloader and root the phone and than transfer my data? - Will this process be more complicated than doing it with Oxygen OS 10.?
2) Once the phone is rooted, can I transfer data from my old phone through the USB/Phone/data transfer apps so it gets setup automagically ?
3) Does TWRP work with OS 11 ? if not is there an update schedule for it?
4) Does Dual Sim for NA phones work with Oxygen OS 10 or is it enabled only at Oxygen OS 11 ?
Any things else that I should be aware of? (this process or the phone in general as well?)
Thank you all
DV
Peace.
Click to expand...
Click to collapse
1. I would prefer to unlock the phone first and than boot twrp and flash magisk. After you got root update the system and install magisk to inactiv slot.
2. I don't know.
3. Nope.
4. Should also work with OOS 10.
Thank you for your reply..
Kollachi said:
1. I would prefer to unlock the phone first and than boot twrp and flash magisk. After you got root update the system and install magisk to inactiv slot.
2. I don't know.
3. Nope.
4. Should also work with OOS 10.
Click to expand...
Click to collapse
Thanks for your reply
Is there a forum thread for how I can unlock the bootloader and to perform root, the XDA forum threads while very resourceful are a bit overwhelming as there seem to be multiple methods of achieving root.
I am not planning on installing customROMS as yet, just want the phone to be unlocked and so I can enable the colour filter, installing gcam etc for now.
Cheers,
DV
dvartak said:
Thanks for your reply
Is there a forum thread for how I can unlock the bootloader and to perform root, the XDA forum threads while very resourceful are a bit overwhelming as there seem to be multiple methods of achieving root.
I am not planning on installing customROMS as yet, just want the phone to be unlocked and so I can enable the colour filter, installing gcam etc for now.
Cheers,
DV
Click to expand...
Click to collapse
I have a couple in the guides section..have a look. So long as you follow it correctly you should be fine.
One for the bootloader.
One for updating, rooting and payload dumper.
A few more questions...
dladz said:
I have a couple in the guides section...have a look. So long as you follow it correctly you should be fine.
One for the bootloader.
One for updating, rooting and payload dumper.
Click to expand...
Click to collapse
Do you mind pasting the links here, I have managed to get the bootloader unlocked using fastboot.
(NVM, I think I found your threads oneplus-8-pro/how-to/root-uk-eu-patched-magisk-boot-img-t4175033 & )
My model is IN2025
OS: 10.5.10.IN11AA
I wanted to know,
1) OxyOS updater is prompting that there is an update to Oxygen OS 11.IN11AA
Can I update to OxyOS 11 and still keep the bootloader unlocked ?
"It displays that OEM unlock is detected, system will download the full upgrade package, please backup data...etc."
2) Should I root my phone now and later will I be able to upgrade / flash to Oxygen OS 11 ? -North-American market requires OS 11 for dual sim
Where can I find the appropriate files to get make a 'patch' using payload for this version (10.5.10.IN11AA) ?
Thank you
dvartak said:
Do you mind pasting the links here, I have managed to get the bootloader unlocked using fastboot.
(NVM, I think I found your threads oneplus-8-pro/how-to/root-uk-eu-patched-magisk-boot-img-t4175033 & )
My model is IN2025
OS: 10.5.10.IN11AA
I wanted to know,
1) OxyOS updater is prompting that there is an update to Oxygen OS 11.IN11AA
Can I update to OxyOS 11 and still keep the bootloader unlocked ?
"It displays that OEM unlock is detected, system will download the full upgrade package, please backup data...etc."
2) Should I root my phone now and later will I be able to upgrade / flash to Oxygen OS 11 ? -North-American market requires OS 11 for dual sim
Where can I find the appropriate files to get make a 'patch' using payload for this version (10.5.10.IN11AA) ?
Thank you
Click to expand...
Click to collapse
Yes you can
Yes that's fine
Easiest way is whatever you like .
You can either root now then take the update and then OTA install magisk patched or just boot the magisk patched after and then directly install
Sorry, I still have some more questions..
dladz said:
Yes you can
Yes that's fine
Easiest way is whatever you like .
You can either root now then take the update and then OTA install magisk patched or just boot the magisk patched after and then directly install
Click to expand...
Click to collapse
I updated to OS11.IN11AA to enable Dual Sim first.
I guess I can try rooting now. Sorry I still have a few queries:
1)
In your instructions you suggest extracting 'your own' boot.img using the payload_dumper.
My phone (thanks to the OEM unlock) has downloaded a large 2GB+ zip file on the phone, should I use that payload.bin to extract the boot.img
or
the one on the oneplus website will work as well? - They appear to be the same but would like to know if there is a difference.
From the oneplus Website: OnePlus8ProOxygen_15.O.30_OTA_0300_all_2010031617_2198430880804411.zip
From the phone: OnePlus8ProOxygen_15.O.30_OTA_0300_all_2010031617_f9ca0bfd1b.zip
2)
I installed MagiskManager from the link in your thread (Preferred magisk manager- https://mega.nz/file/LU9U3aSC#EFJTOK...ejzi-VyUa3nQq8)
There weren't any updates till I selected the stable channel and than canary again. I have installed the whatever updates, it showed:
It now reads:
Magisk (latest): 1469b82a
Installed: N/A <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Why does it show N/A ?, will this change after the rooting process ?
Ramdisk: Yes
A/B: yes
SAR: yes
Crypto: File
Manager (latest) 1469b82a(315)(14)
installed: 1469b82a(315)
Does this seem correct?
You have been really awesome !
Cheers,
DV
dvartak said:
I updated to OS11.IN11AA to enable Dual Sim first.
I guess I can try rooting now. Sorry I still have a few queries:
1)
In your instructions you suggest extracting 'your own' boot.img using the payload_dumper.
My phone (thanks to the OEM unlock) has downloaded a large 2GB+ zip file on the phone, should I use that payload.bin to extract the boot.img
or
the one on the oneplus website will work as well? - They appear to be the same but would like to know if there is a difference.
From the oneplus Website: OnePlus8ProOxygen_15.O.30_OTA_0300_all_2010031617_2198430880804411.zip
From the phone: OnePlus8ProOxygen_15.O.30_OTA_0300_all_2010031617_f9ca0bfd1b.zip
2)
I installed MagiskManager from the link in your thread (Preferred magisk manager- https://mega.nz/file/LU9U3aSC#EFJTOK...ejzi-VyUa3nQq8)
There weren't any updates till I selected the stable channel and than canary again. I have installed the whatever updates, it showed:
It now reads:
Magisk (latest): 1469b82a
Installed: N/A <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Why does it show N/A ?, will this change after the rooting process ?
Ramdisk: Yes
A/B: yes
SAR: yes
Crypto: File
Manager (latest) 1469b82a(315)(14)
installed: 1469b82a(315)
Does this seem correct?
You have been really awesome !
Cheers,
DV
Click to expand...
Click to collapse
Hey,
1.) Yep that's absolutely fine, I tend to use oxygen updater as it's been absolutely flawless up until now and it won't allow you to download a firmware not compatible with your device.
Wherever you choose the numbers you've shown seem good to me, but id I had to choose I'd go with oxygen updater.
2.) Some people have had a lot more luck with the beta channel, so long as you have the install/update buttons then you're ready to patch the boot.img and go ahead and boot it using Fastboot.
Don't worry about N/A that just states that magisk_patched isn't there yet, which is normal.
So at this point, you're welcome to stick with stable but I couldn't recommend it as I've not done this myself, I've only had luck with canary but others have had luck with beta.. I'd recommend one of them channels, changing back to canary may now show the buttons that were missing..
If not then beta.
There are some troubleshooting steps at the end of the guides at the bottom. As well as all the files which I used.
Let me know how you get on
dladz said:
Hey,
2.) Some people have had a lot more luck with the beta channel, so long as you have the install/update buttons then you're ready to patch the boot.img and go ahead and boot it using Fastboot.
Don't worry about N/A that just states that magisk_patched isn't there yet, which is normal.
So at this point, you're welcome to stick with stable but I couldn't recommend it as I've not done this myself, I've only had luck with canary but others have had luck with beta.. I'd recommend one of them channels, changing back to canary may now show the buttons that were missing..
If not then beta.
There are some troubleshooting steps at the end of the guides at the bottom. As well as all the files which I used.
Let me know how you get on
Click to expand...
Click to collapse
Thanks again for all your help!
So I believe, the channel display when first opened did not show any install / update buttons but the settings showed channel: Canary.
I believe I switched to stable and the buttons showed up (i did not install than), after which I switched channels to canary and than installed.
When I search for the "1469b82a" and magisk it shows this as a Update to Canary channel (3days ago) https://github.com/topjohnwu/magisk_files/blob/canary/notes.md
I hope I am on the right track..
-------------------------------
UPDATE: So I think it has worked,
It seems I am rooted now, I have installed Titanium and bunch of other stuff that needs root.
(but I think I may have goofed up and ended up mixing your two solutions)
It was installed in 'b - drive/section'.
fastboot flash boot magisk_patched.img <(This is different from your step 4, where you do fastboot boot magisk_patched)
(I am hoping this did not goof things up, I misread )
It flashed just on 'b' - drive.
I did not flash in both 'a' and 'b'.
I also did'
"
5. Open magisk manager and click install/update, if you are missing the install/ update buttons, change magisk version to beta in magisk settings.
6. Select Direct install (recommended)
"
When I open Magisk Manager now, I see installed 1469b82a (21101) < same as the latest
I also have the "Uninstall Magisk button" showing which wasn't before. and settings shows me many more options (super user, magisk hide etc.)
2) Also what does Magisk hide do?,
> I have read many bank apps wont install due to rooting, will that help?
Thanks for being so patient and answering all questions !
dvartak said:
Thanks again for all your help!
So I believe, the channel display when first opened did not show any install / update buttons but the settings showed channel: Canary.
I believe I switched to stable and the buttons showed up (i did not install than), after which I switched channels to canary and than installed.
When I search for the "1469b82a" and magisk it shows this as a Update to Canary channel (3days ago) https://github.com/topjohnwu/magisk_files/blob/canary/notes.md
I hope I am on the right track..
-------------------------------
UPDATE: So I think it has worked,
It seems I am rooted now, I have installed Titanium and bunch of other stuff that needs root.
(but I think I may have goofed up and ended up mixing your two solutions)
It was installed in 'b - drive/section'.
fastboot flash boot magisk_patched.img <(This is different from your step 4, where you do fastboot boot magisk_patched)
(I am hoping this did not goof things up, I misread )
It flashed just on 'b' - drive.
I did not flash in both 'a' and 'b'.
I also did'
"
5. Open magisk manager and click install/update, if you are missing the install/ update buttons, change magisk version to beta in magisk settings.
6. Select Direct install (recommended)
"
When I open Magisk Manager now, I see installed 1469b82a (21101) < same as the latest
I also have the "Uninstall Magisk button" showing which wasn't before. and settings shows me many more options (super user, magisk hide etc.)
2) Also what does Magisk hide do?,
> I have read many bank apps wont install due to rooting, will that help?
Thanks for being so patient and answering all questions !
Click to expand...
Click to collapse
That's ok you just flashed it twice.
Reason for the boot and not flash is due to the fact that boot images can always go wrong,, bad copy or just corruption. But if you're rooted then you're all good
Magisk hide attempts to hide itself from apps that works otherwise detect it, meaning you can go ahead and use Google pay our your banking apps.
In theory anyway, but some apps have other ways of detecting root and thus it won't work.
Up until now I've been ok.
I see..
Ah I see, Thanks again. Google pay complains about root, but my other Bank apps seem fine so far. I'll try my luck with hide magisk.
I suppose next time the phone updates, I will lose root as the active partition will switch ?
The only odd thing that has happened is the I have an extra/duplicate icon for the Android Files App. I don't know how to get rid of it...but it's not a big issue.
Thanks again for your help!
Cheers,
DV
dvartak said:
Ah I see, Thanks again. Google pay complains about root, but my other Bank apps seem fine so far. I'll try my luck with hide magisk.
I suppose next time the phone updates, I will lose root as the active partition will switch ?
The only odd thing that has happened is the I have an extra/duplicate icon for the Android Files App. I don't know how to get rid of it...but it's not a big issue.
Thanks again for your help!
Cheers,
DV
Click to expand...
Click to collapse
Change to systemless and turn on magisk hide
dladz said:
Change to systemless and turn on magisk hide
Click to expand...
Click to collapse
remember to backup persist partition. i just got my oneplus 8 pro as well. it has a great deal for Black Friday in US.
dlhxr said:
remember to backup persist partition. i just got my oneplus 8 pro as well. it has a great deal for Black Friday in US.
Click to expand...
Click to collapse
How do I backup persist partition?, Will Titanium backup help or something else ?
I am new to the whole rooting thing.
dlhxr said:
remember to backup persist partition. i just got my oneplus 8 pro as well. it has a great deal for Black Friday in US.
Click to expand...
Click to collapse
Me? I have pal