Hi everyone, I need your help please .. I updated the device to android 10 and I reset the factory settings, thus losing the enable camera2api. I have the bootloader already unlocked is there a way to enable camera2 api on android 10? :crying:
Yeah. Problems here too
TonyTerry99 said:
Hi everyone, I need your help please .. I updated the device to android 10 and I reset the factory settings, thus losing the enable camera2api. I have the bootloader already unlocked is there a way to enable camera2 api on android 10? :crying:
Click to expand...
Click to collapse
+1
Patched boot Android 10
is there a way to already have the patched boot of android 10?
lol y u guys doing a factory reset after the update?
And no, stop complaining, its not a problem. it was your choice.
Have you guys already tried enabling cam2api like you did on pie? if not try doing so before making a thread
Thats the same as pie just root and install magisk then enable camera 2 api with buildprop or magisk modules
Did anyone tried https://forum.xda-developers.com/apps/magisk/module-camera2api-enabler-t3656651 ?
salmonthefish said:
lol y u guys doing a factory reset after the update?
And no, stop complaining, its not a problem. it was your choice.
Have you guys already tried enabling cam2api like you did on pie? if not try doing so before making a thread
Click to expand...
Click to collapse
Ok
Sohailsamdani said:
Ok
Click to expand...
Click to collapse
I would like to retry the same method used with android pie, but where can I find stock image boot?
TonyTerry99 said:
I would like to retry the same method used with android pie, but where can I find stock image boot?
Click to expand...
Click to collapse
Why you need a patched kernel?
Unlock bootloader
fastboot boot twrp-3.3.1-0-jasmine_sprout.img
adb push Magisk-v20.3.zip /sideload
(go to /sideload in TWRP)
Flash Magisk
Reboot
(do the same steps to enable camera2api as ou did on Pie)
You didn't even touched the system.
If you only want to boot an 'Magisk' patched boot file.
I've created this just now. magisk_patched_androi10_a2_11.0.4.0.img
Unlock bootloader
fastboot boot magisk_patched_androi10_a2_11.0.4.0.img
(do the same steps to enable camera2api as ou did on Pie)
I got it by editing build.prop
No Magisk modules worked here.
Resolved . thank you all
I solved thanks to patched boot, temporary root with magisk and activated unlocked the camera 2 bees with termux, restarted and removed the root.
On android 10 ? Gcam n stock camera no crash.... if yes please guide me, how to install gcam,.
If someone finds a Magisk module which is working, please share
TonyTerry99 said:
I solved thanks to patched boot, temporary root with magisk and activated unlocked the camera 2 bees with termux, restarted and removed the root.
Click to expand...
Click to collapse
Does the stock camera crash now? ?
Zedsdeadbaby said:
If someone finds a Magisk module which is working, please share
Click to expand...
Click to collapse
Just edit build.prop
Look for the lines with the string "HAL3" (2 lines total) and change their value form 0 to 1.
Then look for persist.vendor.camera.stats.test line and change its value to 5.
I know it's easy, but the point of having a Magisk module doing this is to be able to disable it and use the stock camera app with just a reboot.
Zedsdeadbaby said:
I know it's easy, but the point of having a Magisk module doing this is to be able to disable it and use the stock camera app with just a reboot.
Click to expand...
Click to collapse
With Magisk, do we receive Security Patch via OTA?
Zedsdeadbaby said:
If someone finds a Magisk module which is working, please share
Click to expand...
Click to collapse
Try with this:
View attachment 4929815
Thank you !
Just tried it and it's not working
Related
So i flashed magisk on my phone 2 weeks ago and everything seemed fine and awesome but then for some reason i decided to use triangle away to reset my flash counter. After doing that i couldn't pass the safetynet test. I tried uninstalling magisk, flashing stock boot and finally flashed magisk zip file but still couldnt pass the safetynet test.
Extra info: i have a Samsung Note 4 N910H 6.0 marshmallow.
Read that disabling usb debugging mode might help but no luck.
Applied other fixes as well
Any help will be appreciated
Not one can help?
majd_90 said:
Not one can help?
Click to expand...
Click to collapse
No answer usually means just that...
When asking for help it's a good idea to include some kind of log. Upload a Magisk log (as an attachment). Maybe it'll show something (but don't hold your breath).
Didgeridoohan said:
No answer usually means just that...
When asking for help it's a good idea to include some kind of log. Upload a Magisk log (as an attachment). Maybe it'll show something (but don't hold your breath).
Click to expand...
Click to collapse
Was hoping for some kind of solution or idea to fix it ! I'll try finding the log and uploading it but i doubt it'll show any issues cause everything installed normally without an error or something
majd_90 said:
Was hoping for some kind of solution or idea to fix it ! I'll try finding the log and uploading it but i doubt it'll show any issues cause everything installed normally without an error or something
Click to expand...
Click to collapse
Install from Google Play the app called "RootBeer Sample", hide it from Magisk Hide, run it and upload a screenshot and upload the Magisk log.
AFAIK Note 4 doesn't have the original flash counter; it uses Knox and you can't revert that. The last device with a flash counter was S3/mini.
Deic said:
Install from Google Play the app called "RootBeer Sample", hide it from Magisk Hide, run it and upload a screenshot and upload the Magisk log.
Click to expand...
Click to collapse
Here you go ! I attached the screenshot and log ! Alot of Xs on the screenshot but it is rooted
Dexxxta said:
AFAIK Note 4 doesn't have the original flash counter; it uses Knox and you can't revert that. The last device with a flash counter was S3/mini.
Click to expand...
Click to collapse
Wish i knew that ! The flash counter (which triangle away indicated) was 21 , when i reset the counter it turned into 1
majd_90 said:
Here you go ! I attached the screenshot and log ! Alot of Xs on the screenshot but it is rooted
Click to expand...
Click to collapse
Okay, first you didn't hide RootBeer and second SafetyNet was update weeks ago. You need try Universal SafetyNet Fix module, I recommend the beta one
Deic said:
Okay, first you didn't hide RootBeer and second SafetyNet was update weeks ago. You need try Universal SafetyNet Fix module, I recommend the beta one
Click to expand...
Click to collapse
Ah ya i forgot ! I'll do it again if you want , And where can i get that module? From magisk manager?
Deic said:
Okay, first you didn't hide RootBeer and second SafetyNet was update weeks ago. You need try Universal SafetyNet Fix module, I recommend the beta one
Click to expand...
Click to collapse
Much better
Deic said:
Okay, first you didn't hide RootBeer and second SafetyNet was update weeks ago. You need try Universal SafetyNet Fix module, I recommend the beta one
Click to expand...
Click to collapse
Ok so i found it on xda , downloaded the beta one and added it to the modules in magisk manager , and then rebooted. Still not passing the safetynet test
majd_90 said:
Ah ya i forgot ! I'll do it again if you want , And where can i get that module? From magisk manager?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=72844209&postcount=633
@majd_90 Did you install F-Droid Privileged module like the posts say?
Deic said:
https://forum.xda-developers.com/showpost.php?p=72844209&postcount=633
@majd_90 Did you install F-Droid Privileged module like the posts say?
Click to expand...
Click to collapse
Yes i followed what the post mentioned
...
majd_90 said:
Yes i followed what the post mentioned
Click to expand...
Click to collapse
Did you have Xposed and can share post-fs-data.log in /magisk/xiaomi-safetynet-fix folder?
Deic said:
Did you have Xposed and can share post-fs-data.log in /magisk/xiaomi-safetynet-fix folder?
Click to expand...
Click to collapse
No never had Xposed on this phone before !
majd_90 said:
No never had Xposed on this phone before !
Click to expand...
Click to collapse
Can't execute /system/bin/sh... Do you can try this in terminal and post the result?
Code:
ls -la /system/bin/sh
Deic said:
Can't execute /system/bin/sh... Do you can try this in terminal and post the result?
Code:
ls -la /system/bin/sh
Click to expand...
Click to collapse
Here u go
Ok so safetynet just passed ! I went to the thread which had the universal safetynet fix module and looked around , i saw a link to another thread which had a lot of suggestions that might work ! So finally i enabled magisk core only mode in the settings, disabled systemless hosts and rebooted..
And vola it passed. Gonna keep monitoring it, i am afriad it might be luck it worked this time. Thanks everyone for your assistance
Good day all
Will xposed work on Note 8 (N950FD)?
Thanks in advance
I would guess that an installer for an S8+ might work since it is basically the same device. Since rooting with TWRP and SuperSU I've flashed a few things meant for S8 devices and they either work properly as is or with very minor script tweaking.
Kalm_Traveler said:
I would guess that an installer for an S8+ might work since it is basically the same device. Since rooting with TWRP and SuperSU I've flashed a few things meant for S8 devices and they either work properly as is or with very minor script tweaking.
Click to expand...
Click to collapse
Thanks alot for your quick and kind reply...
Yes it worked... Issue is closed
how are you guys gaining root access?
Hdhntr23 said:
how are you guys gaining root access?
Click to expand...
Click to collapse
Exynos models had root several days ago. I'm using SuperSU at the moment.
me7tarfeek said:
Yes it worked... Issue is closed
Click to expand...
Click to collapse
نوّرنا الله يرضى عليك.
We are here to learn, share and contribute. Otherwise, only the development section would be active (thanks to the developers) while the rest of the sections would be full of threads asking for help.
What method for root did you go with? URL for guide page?
What Xposed modules have you tried and are working? root cloak? Snapprefs?
Did you pass SafteyNet?
Thanks in advance.
Hello with xposed what stuff is actually working and is it stable at all for daily use please?
Kalm_Traveler said:
Exynos models had root several days ago. I'm using SuperSU at the moment.
Click to expand...
Click to collapse
Does Samsung Pay work?
طوني تبولة said:
نوّرنا الله يرضى عليك.
We are here to learn, share and contribute. Otherwise, only the development section would be active (thanks to the developers) while the rest of the sections would be full of threads asking for help.
What method for root did you go with? URL for guide page?
What Xposed modules have you tried and are working? root cloak? Snapprefs?
Did you pass SafteyNet?
Thanks in advance.
Click to expand...
Click to collapse
Sure will do
I root with Magisk 14.0 with SafeNet pass
Follow this https://forum.xda-developers.com/ga...t/recovery-twrp-galaxy-note-8-exynos-t3674036
Flashed 26-07-17-xposed-v87-sdk25-Xposed-by-PurifyOS.zip
Now I use the following modules in the image
SiNJiN76 said:
Does Samsung Pay work?
Click to expand...
Click to collapse
I don't think it ever works with a different country device, or on a rooted phone.
me7tarfeek said:
Sure will do
I root with Magisk 14.0 with SafeNet pass
Follow this https://forum.xda-developers.com/ga...t/recovery-twrp-galaxy-note-8-exynos-t3674036
Flashed 26-07-17-xposed-v87-sdk25-Xposed-by-PurifyOS.zip
Now I use the following modules in the image
Click to expand...
Click to collapse
This and Magisk exposed module—that's all to install Xposed?
Are you experiencing some instability—some apps FCing sometimes, or nothing at all?
白い熊 said:
This and Magisk exposed module—that's all to install Xposed?
Are you experiencing some instability—some apps FCing sometimes, or nothing at all?
Click to expand...
Click to collapse
I did not install Magisk xposed module.. I used the normal stand alone xposed... It worked perfect with no issues at all. My device is N950FD....
Hdhntr23 said:
how are you guys gaining root access?
Click to expand...
Click to collapse
Follow this link if your device is N950F/FD....
https://forum.xda-developers.com/ga...t/recovery-twrp-galaxy-note-8-exynos-t3674036
Kalm_Traveler said:
Exynos models had root several days ago. I'm using SuperSU at the moment.
Click to expand...
Click to collapse
Is lacky patcher working with super su ?
me7tarfeek said:
I did not install Magisk xposed module.. I used the normal stand alone xposed... It worked perfect with no issues at all. My device is N950FD....
Click to expand...
Click to collapse
Which root do you have—SuperSU or Magisk? I have Magisk, so tried with 26-07-17-xposed-systemless-v87-sdk25-by-PurifyOS.zip but that throws me into a bootloop directly?
How did you proceed chronologically?
First the Xposed apk (which one?), then flash the Purify zip? Did you wipe anything before or after, data or cache? I've read many conflicting reports, since you've done it should be possible to replicate it…
白い熊 said:
Which root do you have—SuperSU or Magisk? I have Magisk, so tried with 26-07-17-xposed-systemless-v87-sdk25-by-PurifyOS.zip but that throws me into a bootloop directly?
How did you proceed chronologically?
First the Xposed apk (which one?), then flash the Purify zip? Did you wipe anything before or after, data or cache? I've read many conflicting reports, since you've done it should be possible to replicate it…
Click to expand...
Click to collapse
I flashed Magisk 14 root... Restarted the device to check root... Then Installed xposed apk (XposedInstaller_by_dvdandroid_09_09_17)... Then flashed the above xposed framework. Restarted the device to check xposed, then installed modules...
No wipe at all... The device restarted normaly with no issue..
Good luck
me7tarfeek said:
I flashed Magisk 14 root... Restarted the device to check root... Then Installed xposed apk (XposedInstaller_by_dvdandroid_09_09_17)... Then flashed the above xposed framework. Restarted the device to check xposed, then installed modules...
No wipe at all... The device restarted normaly with no issue..
Good luck
Click to expand...
Click to collapse
Does this break Android Pay?
vinokirk said:
Does this break Android Pay?
Click to expand...
Click to collapse
I think so. As far as I know, root breaks Android Pay.
We do not have it here so I can not be sure...
Hey guys,
Trying to install the systemless XPosed for Nougat on my Note 8, but for some reason, after installation, it stops my 256GB Exynos Note 8 from booting up. Was able to recover it by running the Magisk uninstaller via TWRP.
Noticed that on the official XPosed thread, it states that it'll 'cause boot loop issues on stock Samsung ROM, but on the Systemless XPosed Page, it claims the SDK 24 and 25 are universal, so, what's wrong?
Any suggestions on getting systemless XPosed working on my Exynos Note 8 with Nougat? I especially want the systemless variant as it allows easy on/off whenever I'm going shopping and want to use Android Pay instead of having to uninstall all modules.
any suggestions on how to fix this? updated to the Mar 2020, extracted the boot image, patched in Magisk, flashed, and rebooted like I have done with the previous updates, however once the device is booted up all I get is a black screen! device is still responsive as pressing the power button brings up a menu allowing me to shutdown or reset. flashing a non-modded boot allows me to use the device normally again. help!
dimm0k said:
any suggestions on how to fix this? updated to the Mar 2020, extracted the boot image, patched in Magisk, flashed, and rebooted like I have done with the previous updates, however once the device is booted up all I get is a black screen! device is still responsive as pressing the power button brings up a menu allowing me to shutdown or reset. flashing a non-modded boot allows me to use the device normally again. help!
Click to expand...
Click to collapse
Did you remove all modules prior to rooting March update?
Tulsadiver said:
Did you remove all modules prior to rooting March update?
Click to expand...
Click to collapse
@Tulsadiver no, I neglected to do that since I was able to do so previously without ever having to... any idea how to do so at this point? do I need to wait for an updated image from your thread of https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557 ?
dimm0k said:
@Tulsadiver no, I neglected to do that since I was able to do so previously without ever having to... any idea how to do so at this point? do I need to wait for an updated image from your thread of https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557 ?
Click to expand...
Click to collapse
The old one might work but I'm making a new one for you now...
Edit: here it is
https://www.androidfilehost.com/?fid=4349826312261736126
Tulsadiver said:
The old one might work but I'm making a new one for you now...
Edit: here it is
https://www.androidfilehost.com/?fid=4349826312261736126
Click to expand...
Click to collapse
woohoo! this worked... now I need to figure out which module is fscking me... while you were making this, I followed the steps in your thread to attempt to create a boot image with core only, but mine didn't work. any idea why? regardless, thank you!!
dimm0k said:
woohoo! this worked... now I need to figure out which module is fscking me... while you were making this, I followed the steps in your thread to attempt to create a boot image with core only, but mine didn't work. any idea why? regardless, thank you!!
Click to expand...
Click to collapse
Did you put the whole folder from the zip file?
ramdisk/overlay.d
Tulsadiver said:
Did you put the whole folder from the zip file?
ramdisk/overlay.d
Click to expand...
Click to collapse
hah! I'm in idiot running around with my head cut off. I just checked, I dumped that folder into the root and not into ramdisk! anyway, turns out the culprit of my issue was your mod to increase the notifications to 7! hopefully you can make an updated mod for this update when you get some time
dimm0k said:
any suggestions on how to fix this? updated to the Mar 2020, extracted the boot image, patched in Magisk, flashed, and rebooted like I have done with the previous updates, however once the device is booted up all I get is a black screen! device is still responsive as pressing the power button brings up a menu allowing me to shutdown or reset. flashing a non-modded boot allows me to use the device normally again. help!
Click to expand...
Click to collapse
I was able to update and root, but latest Magisk stable is showing ctsprofile as false. Any ideas on how to fix this?
EVR_PR said:
I was able to update and root, but latest Magisk stable is showing ctsprofile as false. Any ideas on how to fix this?
Click to expand...
Click to collapse
I don't have the link handy, but there's a gpay module fix that should fix that for you. I'm definitely able to use Google Pay now!
dimm0k said:
I don't have the link handy, but there's a gpay module fix that should fix that for you. I'm definitely able to use Google Pay now!
Click to expand...
Click to collapse
Is it the MagiskHide Props Config module the one you're talking about?
So, I can't get Magisk to patch the boot image. It crashes every time I click let's go. I was on canary, went to the stable channel, rebooted, pushed the boot file over a few times, still nothing. Any ideas?
dimm0k said:
woohoo! this worked... now I need to figure out which module is fscking me... while you were making this, I followed the steps in your thread to attempt to create a boot image with core only, but mine didn't work. any idea why? regardless, thank you!!
Click to expand...
Click to collapse
Did you figure out which module? I have the same problem.
EVR_PR said:
I was able to update and root, but latest Magisk stable is showing ctsprofile as false. Any ideas on how to fix this?
Click to expand...
Click to collapse
Same issue, here's what I'm seeing with the ctsprofile. Magisk might need to be updated to support this feature drop.
dimm0k said:
hah! I'm in idiot running around with my head cut off. I just checked, I dumped that folder into the root and not into ramdisk! anyway, turns out the culprit of my issue was your mod to increase the notifications to 7! hopefully you can make an updated mod for this update when you get some time
Click to expand...
Click to collapse
I had some stuff running. Here you go.
Tulsadiver said:
I had some stuff running. Here you go.
Click to expand...
Click to collapse
Hey Tulsadiver, does your MagiskManager pass CTSProfile or are you using a module to fix the issue of it failing?
---------- Post added at 06:15 PM ---------- Previous post was at 06:13 PM ----------
arh2o said:
Same issue, here's what I'm seeing with the ctsprofile. Magisk might need to be updated to support this feature drop.
Click to expand...
Click to collapse
I dont have the preserve dm-verity option on nor did I have it on when I patched the boot image. Seems like that doesn't make a difference either?
EVR_PR said:
Hey Tulsadiver, does your MagiskManager pass CTSProfile or are you using a module to fix the issue of it failing?
---------- Post added at 06:15 PM ---------- Previous post was at 06:13 PM ----------
I dont have the preserve dm-verity option on nor did I have it on when I patched the boot image. Seems like that doesn't make a difference either?
Click to expand...
Click to collapse
Mine shows it as passing. I'm using beta channel.
Weiii said:
Did you figure out which module? I have the same problem.
Click to expand...
Click to collapse
for me it was the module provided by Tulsadiver to increase the notifications to 7... I'm guessing any modules that makes changes to system files might likely be the culprit. list your modules, but all I can do is take a guess as to which one it would be
dimm0k said:
for me it was the module provided by Tulsadiver to increase the notifications to 7... I'm guessing any modules that makes changes to system files might likely be the culprit. list your modules, but all I can do is take a guess as to which one it would be
Click to expand...
Click to collapse
For me it was smali patcher, i think. Not 100% sure because I booted from Tulsadrivers once I got stuck at the Google logo, this took me into safe mode inside of magisk. Every time I would reboot (after deleting the magisk cache file) with smali patcher enabled it would get stuck. After I disabled magisk safe mode I re-installed smali patcher(re-creating the zip on my desktop). After that everything booted fine and passed all safetynet checks.
EVR_PR said:
Is it the MagiskHide Props Config module the one you're talking about?
Click to expand...
Click to collapse
No, not magisk props config. I linked the module he was referring to. Make sure during installation you hit the volume up key when it prompts you to at the end because you need to let it clear the gpay data.
1dopewrx05 said:
No, not magisk props config. I linked the module he was referring to. Make sure during installation you hit the volume up key when it prompts you to at the end because you need to let it clear the gpay data.
Click to expand...
Click to collapse
I went ahead and installed the Magisk Props config module before I read your message and that fixed the problem. Apparently Google forgot to certify this specific build for ATT (the one ending 004.A1). Thank you for your help though.
Hey guys....I just have a strange problem on my mi A2 when i flashed back to the stock rom......the phone was normal then after 2 days.... Phone calls mute and call volume stopped working....when i call someone then i click the mute button....it clicks normally...but the one who i calling...is still hearing me....and when i press volume up or down....it appears that it raising and lowering....but when i hear the call volume it still the same...but when i restart the device it come back to normal for 5 min and then the problem come back again....how can i solve that...and what should i do???
Plz help !
MOhamed95613 said:
Hey guys....I just have a strange problem on my mi A2 when i flashed back to the stock rom......the phone was normal then after 2 days.... Phone calls mute and call volume stopped working....when i call someone then i click the mute button....it clicks normally...but the one who i calling...is still hearing me....and when i press volume up or down....it appears that it raising and lowering....but when i hear the call volume it still the same...but when i restart the device it come back to normal for 5 min and then the problem come back again....how can i solve that...and what should i do???
Plz help !
Click to expand...
Click to collapse
Since you have flashed stock but not mentioned any modifications, I think you should factory reset.
Tianhe said:
Since you have flashed stock but not mentioned any modifications, I think you should factory reset.
Click to expand...
Click to collapse
Okay thanks i will try:angel:
Tianhe said:
Since you have flashed stock but not mentioned any modifications, I think you should factory reset.
Click to expand...
Click to collapse
It's working... thanks....but when I root the device to enable the 2api and g cam ...the problem come back again
MOhamed95613 said:
It's working... thanks....but when I root the device to enable the 2api and g cam ...the problem come back again
Click to expand...
Click to collapse
1) Which version of Stock ROM are you using ? Try some other version and related TWRP.
2) Does the issue occur as soon as you are rooted or only after enabling Cam2Api?
3) Are you editing build.prop or using Magisk Module for Cam2Api ?
Tianhe said:
1) Which version of Stock ROM are you using ? Try some other version and related TWRP.
2) Does the issue occur as soon as you are rooted or only after enabling Cam2Api?
3) Are you editing build.prop or using Magisk Module for Cam2Api ?
Click to expand...
Click to collapse
1- QKQ1.190910.002 V11.0.6.0.QDIMIXM .... I tried older version (V11.0.2) and this latest version and i got the same problem ... And I will try to root using twrp (If u are pointing to a specific method... plz send me the link) and i will let you know ...thank you .
2- I don't know because i have rooted the device and enabled the cam2Api at the same time... but i will try to know.
3- I don't know what you actually mean but I installed magisk first and then enabled the cam2Api through out termux app.
Tianhe said:
1) Which version of Stock ROM are you using ? Try some other version and related TWRP.
2) Does the issue occur as soon as you are rooted or only after enabling Cam2Api?
3) Are you editing build.prop or using Magisk Module for Cam2Api ?
Click to expand...
Click to collapse
I created a stock boot image via magisk and then flashed it .
MOhamed95613 said:
1- QKQ1.190910.002 V11.0.6.0.QDIMIXM .... I tried older version (V11.0.2) and this latest version and i got the same problem ... And I will try to root using twrp (If u are pointing to a specific method... plz send me the link) and i will let you know ...thank you .
2- I don't know because i have rooted the device and enabled the cam2Api at the same time... but i will try to know.
3- I don't know what you actually mean but I installed magisk first and then enabled the cam2Api through out termux app.
Click to expand...
Click to collapse
I am still on V11.0.5.0.QDIMIXM (bugs in update) and use unofficial 4pda version TWRP for booting to custom recovery (Search in this forum, posted by Aerobatic).
Regarding Cam2API, I use Magisk module by LEPT for two reasons - 1) Systemless 2) Can deactivate to use Stock Cam if required.
(I know Magisk is now updated to 20.4 but I am still using 20.3, if it makes any difference)
The cause was easy to fix unpredictable
It was the call recorder app causing that problem.
Thank you for helping me out
[NE2215] OxygenOS 13 C.19 available in the Oxygen Updater app as of this morning.
Poloasis said:
(NE2215) OxygenOS 13 C.19 available in the Oxygen Updater app as of this morning.
Click to expand...
Click to collapse
It's available on c.16 on the phone.
Edit: link to zip. https://android.googleapis.com/packages/ota-api/package/6812ccee9a8a891032af1e053e3217731ac7ad92.zip
Here is the boot.img file that I pulled from the update today if anyone needs it.
I was able to successfully patch the Boot.img and achieve root in C.19
twinnfamous said:
It's available on c.16 on the phone.
Edit: link to zip. https://android.googleapis.com/packages/ota-api/package/6812ccee9a8a891032af1e053e3217731ac7ad92.zip
Click to expand...
Click to collapse
Um it's c.19 on phone. I did a double take and then looked at your screenshot. I did a clean install. Looking good.
the_rooter said:
Um it's c.19 on phone. I did a double take and then looked at your screenshot. I did a clean install. Looking good.
Click to expand...
Click to collapse
I'm installing right now. I hope it's got all the bugs worked out
Well I'm rooted and back up and running. There's been a few times with my 9 pro that it's not gone this easy LOL.
Could someone refresh my memory on the steps to install this? I have the boot.img already pulled. Thanks
foamerman said:
Well I'm rooted and back up and running. There's been a few times with my 9 pro that it's not gone this easy LOL.
Click to expand...
Click to collapse
How'd you update? There's the magisk way and there the unroot and reroot way.
Edit: you have to uninstall the magisk modules before you install the update, then reinstall Magisk after OTA
omega552003 said:
How'd you update? There's the magisk way and there the unroot and reroot way.
Edit: you have to uninstall the magisk modules before you install the update, then reinstall Magisk after OTA
Click to expand...
Click to collapse
I didn't have any modules installed. I downloaded the full zip. Installed it I lost root. I used python to pull the boot.img file. Patched the file re-rooted took me about 15mins.
foamerman said:
I didn't have any modules installed. I downloaded the full zip. Installed it I lost root. I used python to pull the boot.img file. Patched the file re-rooted took me about 15mins.
Click to expand...
Click to collapse
I used the 3party updater app with their local update app
Why this sharing in small window feature removed from beta?
Any word on an update for us? The stepchildren? LOL
doc.K said:
Why this sharing in small window feature removed from beta?
Click to expand...
Click to collapse
I dont use beta, but the feature is available in C.19 and C.20 btw.
Poloasis said:
I was able to successfully patch the Boot.img and achieve root in C.19
Click to expand...
Click to collapse
Hey, can you please attach the boot image that you used to root in C.19?
Is anybody having issues with delay in getting SMS/MMS messages. After updating to c19, I have noticed that sometimes I am not getting any messages. A reboot will temporarily fix the issue. I cleared the both Carrier Services and Messages app data which has not completely resolved the issue. I was just wondering if anyone else is having this issue? Also, I could not find Messages app listed under battery optimization list (may be because it's considered a system app?). BTW, I am not rooted and have 2215 running C19 version. Thanks.
I have the question battery working better than oxygen 12 ? Also apk file install normaly or I must sideload VIA adb ?
Diguinho76 said:
Hey, can you please attach the boot image that you used to root in C.19?
Click to expand...
Click to collapse
C19 Magisk patched boot OP10P NE2215