Oxygen 9.5.9 is out - OnePlus 7 Pro Guides, News, & Discussion

Oxygen 9.5.9 is out.
Use Oxygen Updater if needed.

Animaitons are even faster wtf, lol.
Great update

velvethammer said:
Animaitons are even faster wtf, lol.
Great update
Click to expand...
Click to collapse
If I want to retain TWRP & Magisk after the update, is my procedure correct?
1. Reboot to TWRP
2. Flash 9.5.9
3. Flash TWRP
4. Reboot TWRP
5. Flash Magisk
6. Reboot system

storytellerz said:
If I want to retain TWRP & Magisk after the update, is my procedure correct?
1. Reboot to TWRP
2. Flash 9.5.9
3. Flash TWRP
4. Reboot TWRP
5. Flash Magisk
6. Reboot system
Click to expand...
Click to collapse
or
1. Download update and flash via Local Storage in Settings > System > System Update > click on Gear Icon (that way you can still use your phone while its installing and you won't miss calls or texts)
2. Once Done and Installed DO NOT REBOOT
3. Open Magisk and Click Install > Install > Install to Inactive Slot (After OTA)
3.5 Reboot...
4. (Optional if u want to install TWRP at the moment) Open Magisk and Install TWRP Installer (Do Not Reboot)
5. Go Back to Magisk click Install > Install > Direct Install
5.5 Reboot...
Done!

My bootloader is unlocked, but I am not rooted. Downloaded with oxygen updater, but installation fails at 86% each time.
Sent from my GM1917 using Tapatalk
---------- Post added at 10:02 PM ---------- Previous post was at 09:33 PM ----------
Ok downloaded the full update and it installed fine.
Sent from my GM1917 using Tapatalk

I'm loving this update. It does seem snappier, and the reddish screen tint I was experiencing has been fixed. Also, I noticed that when using gesture navigation, Gboard has been moved up so that the symbols and enter key aren't cut off by the rounded lower corners. This is my first OnePlus device and I'm impressed at their attention to detail.

Yep, this update Rock's!??

velvethammer said:
Animaitons are even faster wtf, lol.
Great update
Click to expand...
Click to collapse
I find that even with animation scale set to .5 in developer settings I was really happy with the phone.
But playing around after the update I found a setting in accessibility that allowes for announcing to be turned off completely and I'll tell you what besides a blink of screen change its for sure the quickest phone I've ever used. Haven't used Samsung since gs7 so that's not much to say. Very happy with updates and phone. 1st OP device and wow.

I didn't recieve any update.
Is it out for model GM1911?

Auto brightness still sucks ass, autofocus seems to be a bit better, need some more testing.
Everything else seems very smooth. Keep those updates coming, 1+.

don't notice any differences. especially with the camera in pro mode as advertised. I think they add the same statements every update lol

paysen said:
Auto brightness still sucks ass, autofocus seems to be a bit better, need some more testing.
Everything else seems very smooth. Keep those updates coming, 1+.
Click to expand...
Click to collapse
Before the update my auto brightness was very slow to dim at night.... Now it's faster... What's your problem?.... Maybe I will notice something...?

My vibration for texts isn't as strong as it used to be on this update. Has anyone else notice this?

Bradl79 said:
or
1. Download update and flash via Local Storage in Settings > System > System Update > click on Gear Icon (that way you can still use your phone while its installing and you won't miss calls or texts)
2. Once Done and Installed DO NOT REBOOT
3. Open Magisk and Click Install > Install > Install to Inactive Slot (After OTA)
3.5 Reboot...
4. (Optional if u want to install TWRP at the moment) Open Magisk and Install TWRP Installer (Do Not Reboot)
5. Go Back to Magisk click Install > Install > Direct Install
5.5 Reboot...
Done!
Click to expand...
Click to collapse
i dont get why people say not to reboot
just update via the local updater
reboot - let the update finish installing
then reboot-bootloader and boot twrp, flash twrp, magisk and reboot.
unless you dont have access to a computer.

virtyx said:
i dont get why people say not to reboot
just update via the local updater
reboot - let the update finish installing
then reboot-bootloader and boot twrp, flash twrp, magisk and reboot.
unless you dont have access to a computer.
Click to expand...
Click to collapse
They said no reboot so that you can preserve twrp if you are away from a computer. Its a lot slow to have to boot twrp using adb each time.
Easier method is to not reboot, and flash Twrp retention script.

mlock420 said:
Before the update my auto brightness was very slow to dim at night.... Now it's faster... What's your problem?.... Maybe I will notice something...?
Click to expand...
Click to collapse
It was alternating between "way too bright" and "way too dark" in my bedroom when the light's are turned off. Sometimes you just scroll a website and the auto brightness dims the display, because the display seems to block the sensor.

paysen said:
It was alternating between "way too bright" and "way too dark" in my bedroom when the light's are turned off. Sometimes you just scroll a website and the auto brightness dims the display, because the display seems to block the sensor.
Click to expand...
Click to collapse
Got ya....I too have noticed that?

mlock420 said:
Got ya....I too have noticed that
Click to expand...
Click to collapse
I just use it (auto brightness) in daytime atm, have to readjust very often though. As soon as it is getting darker, I use it only manually. No surprises then

paysen said:
I just use it (auto brightness) in daytime atm, have to readjust very often though. As soon as it is getting darker, I use it only manually. No surprises then
Click to expand...
Click to collapse
Yeah I don't use auto brightness all that much... No biggie

I managed to get all the other updates with a German VPN, but this one is still not showing. I don't want to use any third-party tool or download zips, which is why I prefer to use the built-in OTA downloader.

Related

Logs for MIUI 6

Hello.
I have a problem with my phone: I install MIUI 6 (doesn't matter what version), I set it up with restore, it runs ok till the first manual reboot. Then it gets blocked at the black "MI"screen. Won't enter in the OS. Any methods to determine the culprit? Maybe taking a log (how to do that?) It gets kinda annoying to flash the zip again and again everytime I do a reboot.
Thank you.
reneftw said:
Hello.
I have a problem with my phone: I install MIUI 6 (doesn't matter what version), I set it up with restore, it runs ok till the first manual reboot. Then it gets blocked at the black "MI"screen. Won't enter in the OS. Any methods to determine the culprit? Maybe taking a log (how to do that?) It gets kinda annoying to flash the zip again and again everytime I do a reboot.
Thank you.
Click to expand...
Click to collapse
dot restore,just go for a fresh clean install,
if that also doesn't work,then simply go for fast boot method
ZenR2 said:
dot restore,just go for a fresh clean install,
if that also doesn't work,then simply go for fast boot method
Click to expand...
Click to collapse
I have lots of apps and it would take me ages to manually install them all. Back-up and restore from MIUI is my savior.
I also have Xposed Framework, that requires a reboot after install. That reboot works. First I thought it was xposed's fault, but I guess if it would have been that the phone won't start after the reboot it required. Same thing happens with wsm.
Don't install xposed ..
(I had same problem)
Clean install miui 6 once again
Paras1259 said:
Don't install xposed ..
(I had same problem)
Clean install miui 6 once again
Click to expand...
Click to collapse
Same problem meaning your phone won't boot after a while or right after installing Xposed?
I really don't get it. For example, i just clean installed MIUI, restored the apps, installed Xposed + modules and I can do as many restarts as I want, it will boot every single time. The problem appears after a while, I guess starting tomorrow morning it will get screwed up again, although I won't install any apps or anything in the meanwhile.

Picture turn green after shooting

Hi guys
I got rooted device running android 7.0
Lately , when I take pictures , most of the pictures turn green after shooting.
But it works well on a videos
In the camera app, have you changed the settings under Manual mode? If yes then try setting it on Auto. You can access the menu by swiping right from the left edge of the screen in portrait mode.
If the issue still persists, try rebooting to recovery mode by pressing POWER + VOLUME DOWN buttons simultaneously until your device reboots and you see the oneplus splash screen. Then wipe caches and check if your issue is solved
TweaknFreak said:
In the camera app, have you changed the settings under Manual mode? If yes then try setting it on Auto. You can access the menu by swiping right from the left edge of the screen in portrait mode.
If the issue still persists, try rebooting to recovery mode by pressing POWER + VOLUME DOWN buttons simultaneously until your device reboots and you see the oneplus splash screen. Then wipe caches and check if your issue is solved
Click to expand...
Click to collapse
mabye you could help me with it : https://forums.oneplus.net/threads/solid-green-photos.453215/
as you can understand i tried to change the build prof usuing buildprop editor
to use google assitant
somone right there that i need to change permissions .. how should i change it ?
fakeclown said:
mabye you could help me with it : https://forums.oneplus.net/threads/solid-green-photos.453215/
as you can understand i tried to change the build prof usuing buildprop editor
to use google assitant
somone right there that i need to change permissions .. how should i change it ?
Click to expand...
Click to collapse
Did you take a backup of build.prop prior to modifying it? If yes then restore it, otherwise dirty flash the OOS VERSION, you have installed.
I got backup for this tried to restore but its didn't help
fakeclown said:
I got backup for this tried to restore but its didn't help
Click to expand...
Click to collapse
Then dirty flash the OOS and check if it solved.
How should I do it?
Download OOS 4.0.2 or if you already have it then follow this guide to install TWRP, Format data, flash the OOS and you're good to go. Keep TWRP of you want to experiment, otherwise flash the stock recovery and enjoy
https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.475142/
And its should delete my data?
fakeclown said:
And its should delete my data?
Click to expand...
Click to collapse
Yeah, your data would be lost.
That's why after installing a ROM(official or custom) I set it up, make a backup from TWRP. Also, dont give lockscreen patterns or add fingerprint prior to backup.
Do You Have TWRP Installed ?
fakeclown said:
And its should delete my data?
Click to expand...
Click to collapse
If Installed Then Backup Your Data Then Wipe Out Everything Except Internal Storage, Flash Latest TWRP And Flash OOS 4.0.2 Through Latest TWRP. After That Restore Your Data. 100% Confirmed. You will Not Loose Your Data. I Also Faced Similar Issue. I Even Can't Record Videos. When I Click On Record, Camera App Crashes. But I Saved My Data By Above Method
i faced this issue currently. i found out different combination produced similar problem.
Problem:
1. Photo Turns Green when settings are
i. Flash Auto, HDR Auto
ii. Flash Auto, HDR Off.
iii. Flash Off, HDR Auto
iv. Flash Off, HDR Off.
v. Flash Off, HDR off, HQ off.
vi. Flash Off, HDR off, HQ ON.
Solution: Set Flash Auto, HDR ON.
However the problems above does not exist at good lighting scenarios (or ISO higher than 200).

Updated to Xiaomi.eu 10.1.2.0, can't unlock screen.

I was very excited to install this update that released today, but after installing it, I can't sign in to my phone. When it boots up, it flashes the homescreen wallpaper, not the lockscreen wallpaper for a second or two then the screen turns black. If I hold the power button I can view the power settings (reboot, silent, airplane mode, shut down) and also if I double press the power button, which my camera shortcut, it opens the camera. Aside from these actions, I can't do anything.
My method to installing this rom was this:
Download the rom from xiaomi.eu website
use the built in updater where I select a rom on my phone and it automatically boots to recovery for me (I'm using TWRP)
Let it do its thing, and boot up, then when it boots the errors occur.
I tried wiping cache and dalvik, but no change.
Did I miss something? Is there something I should have done differently when updating my phone? Is there a special procedure in upgrading Android versions? (1.1.2.0 is first Android Pie version on my phone)
Thank you very much.
Edit 1: I have flashed a second time, this time flashing cache, dalvik, and data. I was able to get into MIUI and set up my device, but after I rebooted the phone for a separate reason, I am experiencing the same errors as before.
Edit 2: Not 100% sure because I switched ROMs, but I probably could have gotten it working by wiping /system as well.
Hello, same thing here.
Clean install and same problem... very sad
DaniloFerracini said:
Hello, same thing here.
Clean install and same problem... very sad
Click to expand...
Click to collapse
Yep same here. I tried it again, wiping data partition and same issue. Can't downgrade because rollback protection too. I guess I'll try out Pixel Experience??
DaniloFerracini said:
Hello, same thing here.
Clean install and same problem... very sad
Click to expand...
Click to collapse
Hey, by the way, what launcher are you using? This seems to be a problem with just the lock screen so maybe there is a weird interaction happening between the launcher and the lock screen. I was using Rootless Pixel Launcher.
Edit: one more question: did you do the same thing as me where I first flashed without formatting data, then you flashed a second time, that time formatting the data? I'm thinking it could also be just because we flashed it incorrectly the first time, future flashes are gonna be messed up.
Where's the download I can find only 10.1.1.0
AquaticPossum said:
Hey, by the way, what launcher are you using? This seems to be a problem with just the lock screen so maybe there is a weird interaction happening between the launcher and the lock screen. I was using Rootless Pixel Launcher.
Edit: one more question: did you do the same thing as me where I first flashed without formatting data, then you flashed a second time, that time formatting the data? I'm thinking it could also be just because we flashed it incorrectly the first time, future flashes are gonna be messed up.
Click to expand...
Click to collapse
I make a dirty flash and clean flash, nova launcher and stock launcher, both dont work
kekkojoker90 said:
Where's the download I can find only 10.1.1.0
Click to expand...
Click to collapse
https://sourceforge.net/projects/xi...ulti_MI8_V10.1.2.0.PEACNFI_v10-9.zip/download
DaniloFerracini said:
Hello, same thing here.
Clean install and same problem... very sad
Click to expand...
Click to collapse
Try this : https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008
You must have a valid custom recovery
Edit : the recovery method won't work... It's a problem with the rom. Just switch to another version....
https://xiaomi.eu/community/threads/miui-10-0-10-1-stable-release.47170/page-23 see the last posts about that
my phone also dead after install the last pie my phone stuck on a black screen
tried downgrading the miui to oreo and the phone did not work well the phone reboot after 30 sec
and after that happened I backed to pie version again but the same problem stuck on a black screen I don't want to lose my data what can I do?
there is possible to back the oreo version and restore that data from twrp backup? the apps work well or not?
almog250 said:
my phone also dead after install the last pie my phone stuck on a black screen
tried downgrading the miui to oreo and the phone did not work well the phone reboot after 30 sec
and after that happened I backed to pie version again but the same problem stuck on a black screen I don't want to lose my data what can I do?
there is possible to back the oreo version and restore that data from twrp backup? the apps work well or not?
Click to expand...
Click to collapse
You shouldn't downgrade :/
kekkojoker90 said:
You shouldn't downgrade :/
Click to expand...
Click to collapse
Even with xiaomi.eu rom ?
Otarie004 said:
Even with xiaomi.eu rom ?
Click to expand...
Click to collapse
You can downgrade from Pie to Oreo with EU rom and TWRP, the phone boot up normaly but some processes say stop working.
I had same problem yesterday. I recommend wipe system before reinstalling Oreo rom and waiting a fixed Pie rom
kekkojoker90 said:
Where's the download I can find only 10.1.1.0
Click to expand...
Click to collapse
This is the Xiaomi.eu ROM which is based on China Stable.
AquaticPossum said:
I was very excited to install this update that released today, but after installing it, I can't sign in to my phone. When it boots up, it flashes the homescreen wallpaper, not the lockscreen wallpaper for a second or two then the screen turns black. If I hold the power button I can view the power settings (reboot, silent, airplane mode, shut down) and also if I double press the power button, which my camera shortcut, it opens the camera. Aside from these actions, I can't do anything.
My method to installing this rom was this:
Download the rom from xiaomi.eu website
use the built in updater where I select a rom on my phone and it automatically boots to recovery for me (I'm using TWRP)
Let it do its thing, and boot up, then when it boots the errors occur.
I tried wiping cache and dalvik, but no change.
Did I miss something? Is there something I should have done differently when updating my phone? Is there a special procedure in upgrading Android versions? (1.1.2.0 is first Android Pie version on my phone)
Thank you very much.
Edit 1: I have flashed a second time, this time flashing cache, dalvik, and data. I was able to get into MIUI and set up my device, but after I rebooted the phone for a separate reason, I am experiencing the same errors as before.
Click to expand...
Click to collapse
This stable ver has many problems. It's hasnt stable yet. Even when you could turn the screen on, if you use the 3 buttons as default, everything is normal, but if you use fullscreen gestures and reboot your phone, you will stuck in black screen again. Many friends and me have the same black screen problems. So my advice is you should stay where you are waiting for a real "stable" ver.
For all who want to use FSG in version 10.1.2.0 I would recommend the following workaround:
a) Startup freshly installed system
b) Select navigation bar as preferred method and finish setting up the phone
c) Download Magisk v18.0
d) Reboot into TWRP and flash Magisk v18.0 zip
e) Reboot to system
f) Download the free application "Fluid Navigation Gestures" and setup the same Gestures as in Stock mi8
g)Optional: In Fluid NG, choose "Hide Navigation Bar"
It doesn't have the exact same feeling as stock but is pretty close and I think it's valid as a meantime workaround.

Magisk GT King compatible

Hi all, has any GT King owner tried to root it with Magisk?
Many thx!
PLAY911 said:
Hi all, has any GT King owner tried to root it with Magisk?
Many thx!
Click to expand...
Click to collapse
Does not work and trying it will remove the current root on the device which will require re-flash of ROM to get it back.
syked said:
Does not work and trying it will remove the current root on the device which will require re-flash of ROM to get it back.
Click to expand...
Click to collapse
Yes I learned this hard way . Flashed it and lost root . Hoping something can be done soon enough to get Magisk supported on this device . Currently I'm still on without root which is fine for some apps that will not run on root . Unfortunately one of the sports app that detects root which works now keeps bombarding my device with pop-ups ads . Really unusable .
[email protected] said:
Yes I learned this hard way . Flashed it and lost root . Hoping something can be done soon enough to get Magisk supported on this device . Currently I'm still on without root which is fine for some apps that will not run on root . Unfortunately one of the sports app that detects root which works now keeps bombarding my device with pop-ups ads . Really unusable .
Click to expand...
Click to collapse
You could just force close the app in question and that way the ads won't appear in the background. Surely the ads won't appear when using the app and watching your sport.
Otherwise you can can flash the stock rom again (this will re-root) but will delete your data.
Alternatively, download blokada which is a ad blocking software. The catch is if you run an actual VPN, you won't be able to run this together as it's also treated as a VPN.
syked said:
You could just force close the app in question and that way the ads won't appear in the background. Surely the ads won't appear when using the app and watching your sport.
Otherwise you can can flash the stock rom again (this will re-root) but will delete your data.
Alternatively, download blokada which is a ad blocking software. The catch is if you run an actual VPN, you won't be able to run this together as it's also treated as a VPN.
Click to expand...
Click to collapse
They do trust me . When you watch live or replay games 5-10 min you just get full screen plastered add that won't go away unless you close it yourself sometimes 2 times and game gets paused while that happens . Tried Blokada didn't work some apps won't even start while running even if white listed . Only one that does the job best is AdAway which requires root obviously but then sport app will not run since detects root and so on and on.....very annoying .
[email protected] said:
They do trust me . When you watch live or replay games 5-10 min you just get full screen plastered add that won't go away unless you close it yourself sometimes 2 times and game gets paused while that happens . Tried Blokada didn't work some apps won't even start while running even if white listed . Only one that does the job best is AdAway which requires root obviously but then sport app will not run since detects root and so on and on.....very annoying .
Click to expand...
Click to collapse
Yeah I can imagine that's annoying. There is a way to install magisk but you have to use the recovery partition. Have a read through magisk instructions and how to load it into the recovery partition.
Ive tried it and and it works but you have to boot into recovery every time and will actually start the system but with magisk installed.
You could boot into recovery once and keep the device on.
You do lose the actual recovery partition though...but guessing you could fast boot via ADB to load that or maybe having the recovery on the SD card and depressing the reset pinhole underneath whilst plugging in power.
Btw, what streaming app are you using? I'm also a fellow Aussie.
syked said:
Yeah I can imagine that's annoying. There is a way to install magisk but you have to use the recovery partition. Have a read through magisk instructions and how to load it into the recovery partition.
Ive tried it and and it works but you have to boot into recovery every time and will actually start the system but with magisk installed.
You could boot into recovery once and keep the device on.
You do lose the actual recovery partition though...but guessing you could fast boot via ADB to load that or maybe having the recovery on the SD card and depressing the reset pinhole underneath whilst plugging in power.
Btw, what streaming app are you using? I'm also a fellow Aussie.
Click to expand...
Click to collapse
G'day mate . Optus Sport . Will give that a try I guess . This is by far the best Android Box I ever owned getting Full Magisk working on it would make this amazing . I also own one of X96 Android Box which runs Android 8.0 . Got Magisk installed and managed to hide app . Unfortunately box just doesn't seem to like Magisk at all so I deleted it . Luckily app starts ok . But there 's heaps of issues with this one video lags, freezes sometimes not a daily device at all . That is the reason I got myself Gt-King in the first place .
[email protected] said:
G'day mate . Optus Sport . Will give that a try I guess . This is by far the best Android Box I ever owned getting Full Magisk working on it would make this amazing . I also own one of X96 Android Box which runs Android 8.0 . Got Magisk installed and managed to hide app . Unfortunately box just doesn't seem to like Magisk at all so I deleted it . Luckily app starts ok . But there 's heaps of issues with this one video lags, freezes sometimes not a daily device at all . That is the reason I got myself Gt-King in the first place .
Click to expand...
Click to collapse
G'day mate.
That's strange. I have never seen Optus sport display pop up ads. I've just watched over 15 mins of an UEFA Champions league game on my un rooted Android tablet using the Optus sport app and there were no ads.
Are you sure there's no other apps running in the background that could be generating the pop up ads but thinking it's Optus sport.
Agreed. It is an awesome box
For me it was just easier to Chromecast from my phone or tablet when using the Optus sport app because I couldn't be bothered continuously loading into recovery to have magisk hide work and I don't see the point to leave my box on just for that reason.
As it stands my box is default rooted and I'm using ALVATECHs rom which I find works great.
I'll post some steps later to help you and others loading magisk though.
Magisk in Recovery mode
Before anything always back up your box. If you use TWRP then create a whole back up which makes it easier to restore and if don't use TWRP then maybe you should.
To get Magisk working on the GT-King follow these steps.
Magisk will be installed into the recovery partition so if you flash the image to recovery, you will loose TWRP or default recovery but you could use an SD card to load into TWRP or default recovery and similarly you can use the patched recovery image from Magisk to and load that from SD card when required. I have not worked out how you can load Magisk recovery partition but also load TWRP when required. Technically this is possible because it's a patched recovery image with TWRP. There might be some sort of key sequence that will allow this but have not played enough with it to work it out. If you leave your box on all the time it should be fine because you can boot into "magisk recovery" once and then leave it on.
1) You need a recovery image.
a)If you have root already (such as default root), you can use this command in a terminal app which will covert the recovery file from the system to recovery.img and we will save it on the internal storage (home level).​
Code:
dd if=/dev/block/revovery of=/mnt/sdcard/recovery.img
b) if you don't have root because you tried flashing Magisk through TWRP or have manually unrooted then or if you can't be bothered using terminal, you can use my recovery.img here recovery image and save this to a location of your choice​2) Download and install Magisk Manager APK from here
3) In Magisk manager main screen click advanced options tick Recovery mode
4) Now next to Magisk Click install then selection the option where you have to select the image
5) Select the image file from either step 1a) or 1b)
6) Give it a few moments and Magisk manager will create a patched recovery img to the same location as the original recovery img
7) Now you need to unroot your device if it's not already by trying to flash Magisk in TWRP. I use impactor universal unroot for this which can be sourced from the play store or other means and follow the instructions in the app. After you restart, the device is no longer rooted but we will need use the magisk patched recovery which will give you root
Now here is where you decide what to do next....
i)Do you boot into existing TWRP recovery via depressing the reset pinhole whilst plugging in the power and then permanently flashing the new patched recovery image or
ii)Do you copy that patched recovery image to a SD Card, renaming it to recovery.img and booting off that temporarily via depressing the reset pinhole whilst plugging in the power
Either way, once you boot into that "magisk recovery" it is now installed and works a treat and have root access but you can hide root per app via Magisk hide
The systemless-host module can be installed via the module manager if you use Hosts file to block ads (I use energized host file for this). I think the path for this after it's installed is /data/adb/modules/hosts
Really appreciate effort and detailed info mate . Will try that later tonight and will let you know. Cheers
Sent from my SM-G950F using Tapatalk
I flashed the magisk_patched/stock-recovery.img with twrp.app and worked!
Many thanks to Syked for this detailed info how to get Magisk working.
Maybe somebody could confirm this is working on the new 2022 GT king ii with the Amlogic a311D2 CPU.
Magisk is a must for me so I'm not buying until this is possible.

Can't install magisk, after adding wrong module

Hi, I wanted to try the debloater module, so i installed it on my Oneplus 7 Pro. After the installisation and reboot, the device always stayed on the bootlocker warning screen really long. After that it always startet to fastboot.
My first try was to flash the module uninstaller: https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242.
-> Flash was sucessfull, but it did not work at all.
Second try was to delete the modules via TWRP File explorer, so i deleted the folder of the module.
-> Still same problem, boots from bootloader unlocked warning screen directly to fastboot.
My next try was to flash the magisk uninstaller.
-> Flash sucessful, phone running again.
After that i reflashed magisk.
-> Problem started again.
Next step was flashing the uninstaller and then booting to android, to delete the magisk Manager. After that reflashing magisk.
->Same Problem as in the beginning. But there is no module when i have a look at /data/adb
Right now my device is running, but i have no idea how to reinstall magisk. Is there anybody who could help me?
I'd like to get magisk back and would prefer not to factory reset or wipe any sd data...
If there are no modules installed, there's likely something else going on...
Examples of things to do/try:
Don't install TWRP. Leave the boot image untouched and just boot TWRP to install Magisk (there's been instances where Magisk and TWRP conflict).
Reflash just the system images and leave data untouched.
Ask for advice in your device's forum. That's usually where you'll get the best device specific help.
Thank you for the advice!
So you mean i should flash the stock recovery again? And then sideload TWRP, or simply patch my boot image and flash it via ADB?
But why did i not have any problem with TWRP and magisk all the time before? Everything startet with the reboot after installing a new module?
I will also post my question in the OP 7 Pro forum!
Download Magisk 20.1
fastboot boot twrp (I'm using .72 but some say they have issues with it, try .70 or .74)
adb sideload twrp.zip (or flash it, if it is on your device)
reboot twrp
adb sideload magisk 20.1 (or flash it, if it is on your device)
Reboot.
Not sure what you are trying to debloat but I also have a 7pro and I used xxxnolimits magisk rom which has some debloating in it, I recommend trying it.
GeekMcLeod said:
Download Magisk 20.1
fastboot boot twrp (I'm using .72 but some say they have issues with it, try .70 or .74)
adb sideload twrp.zip (or flash it, if it is on your device)
reboot twrp
adb sideload magisk 20.1 (or flash it, if it is on your device)
Reboot.
Not sure what you are trying to debloat but I also have a 7pro and I used xxxnolimits magisk rom which has some debloating in it, I recommend trying it.
Click to expand...
Click to collapse
Worked finde for me! Only problem was with twrp 74, data was not decrypted, so i had to fastboot twrp 70.
Thankyou very much! I also combined it with updating from 10.0.1 to 10.0.2.
I just wanted to debloat the oneplus galerie, so i could install an older version from apk mirror, that still has the never settle stamp.
6nchris said:
Worked finde for me! Only problem was with twrp 74, data was not decrypted, so i had to fastboot twrp 70.
Thankyou very much! I also combined it with updating from 10.0.1 to 10.0.2.
Click to expand...
Click to collapse
Glad to have helped out! I love the 7pro. Only had it for like two weeks? Maybe only 1. Came from The 6t and I have everything as it was on my 6t. So much easier too.
GeekMcLeod said:
Glad to have helped out! I love the 7pro. Only had it for like two weeks? Maybe only 1. Came from The 6t and I have everything as it was on my 6t. So much easier too.
Click to expand...
Click to collapse
You really did help out. I love it to, there is only one big problem i think. The proximity sensor does not work good at all, so sometimes in calls screen turns on and your ear touches something... I really hope they will find a solution. Even turning the screen of with the power button and wake it up by pressing the power button again would be okay, but when you turn the screen of by pressing the button the proximitx sensor sometimes turns it on again..
i came from 3T to the essential phone. I Think modding the OP 3T or the OP 7Pro is much easier than the essential PH1...
6nchris said:
You really did help out. I love it to, there is only one big problem i think. The proximity sensor does not work good at all, so sometimes in calls screen turns on and your ear touches something... I really hope they will find a solution. Even turning the screen of with the power button and wake it up by pressing the power button again would be okay, but when you turn the screen of by pressing the button the proximitx sensor sometimes turns it on again..
Click to expand...
Click to collapse
Ahh, sad too say but I can't help with that. I don't take calls often so never noticed anything like that.

Categories

Resources