I am using OnePlus 8 and planning to install Oxygen 11 Beta. Any Beta users here? How smoothly it runs as compared to OT? Is there any problems in app support?
I've had no issues so far. Started when Dp3 was released and now on Dp4. Runs as well or better than my Pixel 2xl. Everyone's experience will vary depending on apps used, etc.
Been on DP4 since day one. It is my daily driver. Very stable.
Anyone using it on a T-Mobile Device?
I'm on T-Mobile device that has been converted.
Same here.
joe1gun said:
I'm on T-Mobile device that has been converted.
Click to expand...
Click to collapse
Can you update without rooting if your sim unlocked and can toggle the b/l unlock toggle in dev settings?
Edit-mine shows as an in2017
prozack1983 said:
Can you update without rooting if your sim unlocked and can toggle the b/l unlock toggle in dev settings?
Edit-mine shows as an in2017
Click to expand...
Click to collapse
You have to flash global firmware to run beta builds, there is a forum/guide on how to do that.
Awesome
I installed the beta a bit ago. I'm TMobile converted and I am very happy about the beta. It's very smooth .
Installed it yesterday. Someone mentioned netflix wasn't working but for me it's working fine.
Only thing I can't get setup yet is Google Pay.
I came from the latest official rom, just put the update file in the root directory and flash via the updater.
Does the open beta require a data wipe?
As I said in my first post the beta is awesome and I'm glad aod is back but I had to use the rollback package because 90fps is no longer an option on fortnite. So if your like me you need that 90fps gameplay:good:
---------- Post added at 10:05 AM ---------- Previous post was at 10:03 AM ----------
Bastienhere said:
Does the open beta require a data wipe?
Click to expand...
Click to collapse
No it does not however if you wish to go back to android 10 you will have to use the rollback zip provided in the oxygen updater. Just so you know that the rollback package will indeed wipe data.
Zelete said:
Installed it yesterday. Someone mentioned netflix wasn't working but for me it's working fine.
Only thing I can't get setup yet is Google Pay.
I came from the latest official rom, just put the update file in the root directory and flash via the updater.
Click to expand...
Click to collapse
Google pay works fine if you root with magisk and update the device fingerprint to pass cts. I have it working.
How to root open beta please? Does it work normally?
danceeeee said:
How to root open beta please? Does it work normally?
Click to expand...
Click to collapse
Depends what is normal. Extract boot img from payload. Patch with magisk canary. Adb flashed.... Is working fine. [emoji106]
Ehm, Payload? Not sure what does it mean?
danceeeee said:
Ehm, Payload? Not sure what does it mean?
Click to expand...
Click to collapse
Do a search on rooting with magisk [emoji6]
---------- Post added at 06:40 PM ---------- Previous post was at 06:36 PM ----------
Sorry to be vague but if you don't understand what I said. I'm not sure I would be risking my phone.
I do understand, i have root on my phone. Just never heard of term Payload
AndyBury said:
Depends what is normal. Extract boot img from payload. Patch with magisk canary. Adb flashed.... Is working fine. [emoji106]
Click to expand...
Click to collapse
i tried flashing my patched boot.imgfrom the ob1 payload in fastboot and fastbootd but magisk manager still doesnt show magisk is installed
42o247 said:
i tried flashing my patched boot.imgfrom the ob1 payload in fastboot and fastbootd but magisk manager still doesnt show magisk is installed
Click to expand...
Click to collapse
Did it complete OK in the cmd windows?
I had to do it about 5 or 6 times till it completed OK.
It would see it in adb devices.... Then seem to lose connection....
Related
So I have a few questions about the android P beta program. I was wondering if anyone could answer before I opt into it
1) if I opt into I get ota updates which won't be Verizon variants so would I be able to jump back to Oreo?
2)would this allow me to unlock my bootloader possibly?
1) You should be able to go back to oreo by opting out of the beta and taking the subsequent ota from Google. Or you can manually flash a newer ota you downloaded from your computer. Must be a newer build than the the one you are on.
2) Almost certainly not. Unless there is some error, your bootloader will not be unlockable. You are not currently receiving "Verizon" builds. No such thing. Your device info is on a server side whitelist / blacklist. It has nothing to do with the build you have installed. That is my understanding.
dbrohrer said:
1) You should be able to go back to oreo by opting out of the beta and taking the subsequent ota from Google. Or you can manually flash a newer ota you downloaded from your computer. Must be a newer build than the the one you are on.
2) Almost certainly not. Unless there is some error, your bootloader will not be unlockable. You are not currently receiving "Verizon" builds. No such thing. Your device info is on a server side whitelist / blacklist. It has nothing to do with the build you have installed. That is my understanding.
Click to expand...
Click to collapse
Thanks so much for this information I'm gonna opt in for the hell of it
dbrohrer said:
1) You should be able to go back to oreo by opting out of the beta and taking the subsequent ota from Google. Or you can manually flash a newer ota you downloaded from your computer. Must be a newer build than the the one you are on.
2) Almost certainly not. Unless there is some error, your bootloader will not be unlockable. You are not currently receiving "Verizon" builds. No such thing. Your device info is on a server side whitelist / blacklist. It has nothing to do with the build you have installed. That is my understanding.
Click to expand...
Click to collapse
Im not sure i understood this properly, I've already unlocked the bootloader of my Verizon pixel 2 on 8.1, if I update to P, will the bootloader be locked back? Or I can update and still enjoy the unlocked bootloader?
Thanks!
daede86 said:
Im not sure i understood this properly, I've already unlocked the bootloader of my Verizon pixel 2 on 8.1, if I update to P, will the bootloader be locked back? Or I can update and still enjoy the unlocked bootloader?
Thanks!
Click to expand...
Click to collapse
If you unlocked the bootloader already, it will stay unlocked until you lock it via fastboot from your computer. Flashing firmware will not relock it. Don't worry, updating to Android p won't mess with that.
I'm really enjoying this beta so far. The new navigation gestures are cool. Nothing so far that makes me want to go back to 8.1.
dbrohrer said:
If you unlocked the bootloader already, it will stay unlocked until you lock it via fastboot from your computer. Flashing firmware will not relock it. Don't worry, updating to Android p won't mess with that.
I'm really enjoying this beta so far. The new navigation gestures are cool. Nothing so far that makes me want to go back to 8.1.
Click to expand...
Click to collapse
thanks so much! i've installed android p but i'm not able to root the phone.. i've installed magisk but it fails while patching boot.img.. any idea?
thanks again!
daede86 said:
thanks so much! i've installed android p but i'm not able to root the phone.. i've installed magisk but it fails while patching boot.img.. any idea?
thanks again!
Click to expand...
Click to collapse
What version of magisk are you flashing? You should be using the beta magisk. Looks like people are having some success rooting with version 16.4.
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Hope this helps.
dbrohrer said:
What version of magisk are you flashing? You should be using the beta magisk. Looks like people are having some success rooting with version 16.4.
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Hope this helps.
Click to expand...
Click to collapse
thanks so much!!
i'm trying to flash magisk using this tutorial https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535 but as soon as i launch fastboot boot [twrp image filename].img, it loads up twrp (i see the splash screen) but right after it crashed and reboot.. so i'm not able to flash magisk beta
is there a way to install magisk manager (beta) and being able to patch the boot.img without passing through twrp?
thanks again and sorry for all my questions!
daede86 said:
thanks so much!!
i'm trying to flash magisk using this tutorial https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535 but as soon as i launch fastboot boot [twrp image filename].img, it loads up twrp (i see the splash screen) but right after it crashed and reboot.. so i'm not able to flash magisk beta
is there a way to install magisk manager (beta) and being able to patch the boot.img without passing through twrp?
thanks again and sorry for all my questions!
Click to expand...
Click to collapse
Do you have the Pixel 2 or 2 XL? Are you booting with twrp 3.2.1-2 img?
dbrohrer said:
Do you have the Pixel 2 or 2 XL? Are you booting with twrp 3.2.1-2 img?
Click to expand...
Click to collapse
i have a pixel 2 verizon with bootloader unlocked trying to boot twrp-3.2.1-2-walleye.img. am i doing something wrong?
thanks again!
daede86 said:
i have a pixel 2 verizon with bootloader unlocked trying to boot twrp-3.2.1-2-walleye.img. am i doing something wrong?
thanks again!
Click to expand...
Click to collapse
That's correct. Just checking. You need to boot to twrp to flash magisk. There isn't another way that I know of. Maybe download twrp img again? I doubt its a corrupt download since you get the twrp splash screen, but its worth a try.
dbrohrer said:
That's correct. Just checking. You need to boot to twrp to flash magisk. There isn't another way that I know of. Maybe download twrp img again? I doubt its a corrupt download since you get the twrp splash screen, but its worth a try.
Click to expand...
Click to collapse
no luck
should i try to flash again the factory image?
or maybe opt out from androind p beta, install back oreo, root and flash android p without deleting my data?
daede86 said:
no luck
should i try to flash again the factory image?
or maybe opt out from androind p beta, install back oreo, root and flash android p without deleting my data?
Click to expand...
Click to collapse
You can boot into the OS right? Are you're platform tools the latest version?
Reverting back to oreo, rooting, and updating to p beta will either fail or wipe out root. You won't end up with p beta and root. Don't do that.
dbrohrer said:
You can boot into the OS right? Are you're platform tools the latest version?
Reverting back to oreo, rooting, and updating to p beta will either fail or wipe out root. You won't end up with p beta and root. Don't do that.
Click to expand...
Click to collapse
ok thanks again, really appreciated.
yes, at least i can boot and use my pixel with no problem, i'd only like to root it and restore my backup
daede86 said:
ok thanks again, really appreciated.
yes, at least i can boot and use my pixel with no problem, i'd only like to root it and restore my backup
Click to expand...
Click to collapse
I understand that. I am not sure whats going on then. Sorry.
i've solved the problem!! just to share, i had installed handbrake in my mac to share files via usb and i guess it caused some incompatibility issue.. i've just uninstalled it and i've managed to flash it properly!
How to root your device using magisk?
all the credits go to Magisk team
there`s too many thread about rooting phone using magisk patch method but in this thread i want to make it easier for the newboi it's working on all Nokia 6.1 / Nokia x6 / Nokia 6.1 plus
check first which security patch you have then pick the one matching it
don`t flash it
only boot it don`t flash it if you flash it you probably going to brike your WIFI
In case you flash it by mistake reflash your stock boot
INSTALLATION
1- bootloader unlocked
2- enable usb debugging from developer option
3-adb and fastboot tools
4- use this codes
Code:
adb shell
Code:
reboot bootloader
now we boot it temporary
Code:
fastboot boot <File name>.img
5- after your system boot up install Magisk Manager from here
https://******************/downloading-magisk-manager
6- go to Magisk manager tab install then choose install dirctly recommanded then after the process done reboot
7- now your phone rooted enjoy
8- don't forget to hit like
DOWNLOAD
February patch Pie-9.0
https://drive.google.com/file/d/1L4xnrx9_I3hXou94JT5ED32ju3-Af-Ly/view?usp=drivesdk
January patch Pie-9.0
https://drive.google.com/file/d/1LA9FceK-m4Eyx-NGgqtiD0SFVpGCE2Iv/view?usp=drivesdk
October patch Pie-9.0
https://drive.google.com/file/d/1oP5Eww3ew8yem4DEddDlimayAQ-v9JaO/view?usp=sharing
September patch
https://drive.google.com/file/d/1ub0eBYAzlrpdNsVjEFdNzNU_Yx0kgtsi/view?usp=sharing
August patch
https://drive.google.com/file/d/1B2U_mmqHzLTUl7WXZtWgywwLvfbggcOR/view?usp=drivesdk
June patch
https://drive.google.com/file/d/1FNZ6uG42n_wf6wQiQyB6RJ6ZQ2eRvQZG/view?usp=sharing
July patch
https://drive.google.com/file/d/1jOUe_v0p9xqHdhialMeuwHZ_JRgZcxgb/view?usp=sharing
Reserved
#Reserved
Thanks Maher for you tutorials and help. I was able to instal Global Firmware and update to August OTA. I then used this rooting guide and it worked great. You should link this rooting guide to the last step on the Global Firmware tutorial as optional for people who want to root.
Any root for September? My phone auto updated from August patch. Thanks for all the hard work!
P.S. When a new security patch is installed is it supposed to unroot your device and you have to re-apply one of the patches above to fix?
lespy_laz said:
Any root for September? My phone auto updated from August patch. Thanks for all the hard work!
P.S. When a new security patch is installed is it supposed to unroot your device and you have to re-apply one of the patches above to fix?
Click to expand...
Click to collapse
now uploading patch boot for September
Maherabed1986 said:
now uploading patch boot for September
Click to expand...
Click to collapse
Is already available the September security patch for 6.1 plus ?
neodante said:
Is already available the September security patch for 6.1 plus ?
Click to expand...
Click to collapse
Yes sir uploaded it already
Maherabed1986 said:
Yes sir uploaded it already
Click to expand...
Click to collapse
Thanks for uploading bro. One question, did you receive the september patch update already? I haven't got mine on nokia 6.1 plus.
Also i just wanna confirm the steps i should do, to unroot and updating to September update. ( I am currently rooted with magisk and august patched boot image). Thanks.
raza_maestro said:
Thanks for uploading bro. One question, did you receive the september patch update already? I haven't got mine on nokia 6.1 plus.
Also i just wanna confirm the steps i should do, to unroot and updating to September update. ( I am currently rooted with magisk and august patched boot image). Thanks.
Click to expand...
Click to collapse
i have Nokia 6.1 not plus but this method working on all nokia 6 ,6.1,6.1 plus,x6,7 so on our 6.1 yes we received September update already
to unroot you need to flash your stock boot.image
Maherabed1986 said:
i have Nokia 6.1 not plus but this method working on all nokia 6 ,6.1,6.1 plus,x6,7 so on our 6.1 yes we received September update already
to unroot you need to flash your stock boot.image
Click to expand...
Click to collapse
Okay great. Thanks.
Can you still update after this? Will you have to re-root?
bobbyraduloff said:
Can you still update after this? Will you have to re-root?
Click to expand...
Click to collapse
yes you still can if your system not modified or you have installed magisk modules
i ca't open wifi when flash September patch on my Nokia X6 (TA 1099) hmmm,maybe i'll try again
phanmanhcuong said:
i ca't open wifi when flash September patch on my Nokia X6 (TA 1099) hmmm,maybe i'll try again
Click to expand...
Click to collapse
bro don't flash it i mentioned that 1st post you will brike your wifi only follow the guide please to be in safe side
Maherabed1986 said:
bro don't flash it i mentioned that 1st post you will brike your wifi only follow the guide please to be in safe side
Click to expand...
Click to collapse
i've forgot it,sorry man
---------- Post added at 05:02 PM ---------- Previous post was at 04:52 PM ----------
i've boot it but my phone still can't open wifi :/
phanmanhcuong said:
i've forgot it,sorry man
---------- Post added at 05:02 PM ---------- Previous post was at 04:52 PM ----------
i've boot it but my phone still can't open wifi :/
Click to expand...
Click to collapse
ofcourse my friend you already broke your wifi now you must flash stock boot image ask if someone have it on the group after that come again and follow the thread step by step
Maherabed1986 said:
ofcourse my friend you already broke your wifi now you must flash stock boot image ask if someone have it on the group after that come again and follow the thread step by step
Click to expand...
Click to collapse
Bro, i am rooted with magisk via patched boot image. So to install OTA i need to restore stock boot image right? For that can i restore stock image by going to magisk->uninstall->restore images?
raza_maestro said:
Bro, i am rooted with magisk via patched boot image. So to install OTA i need to restore stock boot image right? For that can i restore stock image by going to magisk->uninstall->restore images?
Click to expand...
Click to collapse
in order to uninstall magisk you need twrp and OTA not working with custom recovery so easier for you to flash the stock boot
Maherabed1986 said:
in order to uninstall magisk you need twrp and OTA not working with custom recovery so easier for you to flash the stock boot
Click to expand...
Click to collapse
I am think i did not made myself clear. I am not on twrp, still on stock recovery. I rooted via booting in patched boot image and installed magisk.
Started to download but it is 1am.
Need to sleep
Strange issue.
After installing full OTA, I am not able to use magisk to patch the OTA slot. Option not available in magisk. Only uninstall.
UPDATE: I had a to low DPI resolution, 320dp. That was reason I couldn't see the install button.
If I reboot now, I will loose root.
BTW. I do not use TWRP
Anyway. Rebooted and lost root. Will wait for patched boot image.
Everything else seems to work
UPDATE: Used the beta 1 patched boot image to fastboot -- used magisk to patch -- root is back!
I'm uploading to Google Drive now
Thanks for sharing, downloading
Sent from my ONEPLUS A6003 using Tapatalk
https://otafsg.h2os.com/patch/amazo...us6Oxygen_22_OTA_007_all_1809071908_8f1d8.zip
Official OOS OB 2 link from One Plus
Here is link to my Google Drive download and instructions
https://forum.xda-developers.com/on...droid-pie-oxygenos-beta-t3831803/post77568541
alirey said:
Started to download but it is 1am.
Need to sleep
Strange issue.
After installing full OTA, I am not able to use magisk to patch the OTA slot. Option not available in magisk. Only uninstall.
UPDATE: I had a to low DPI resolution, 320dp. That was reason I couldn't see the install button.
If I reboot now, I will loose root.
BTW. I do not use TWRP
Anyway. Rebooted and lost root. Will wait for patched boot image.
Everything else seems to work
UPDATE: Used the beta 1 patched boot image to fastboot -- used magisk to patch -- root is back!
Click to expand...
Click to collapse
can you explain me exactly how you fixed the root problem? Where is the OOS beta 1 patch boot image, and how would i use magisk to patch it, sry i'm noob
edit: nevermind i figured it out, thanks!
Is t mobile volte working on this build?
fantasy2c said:
Is t mobile volte working on this build?
Click to expand...
Click to collapse
VoLte and VoWifi work fine now on Tmobile USA on OB2.
SMS786 said:
VoLte and VoWifi work fine now on Tmobile USA on OB2.
Click to expand...
Click to collapse
Awesome thank you
alirey said:
Started to download but it is 1am.
Need to sleep
Strange issue.
After installing full OTA, I am not able to use magisk to patch the OTA slot. Option not available in magisk. Only uninstall.
UPDATE: I had a to low DPI resolution, 320dp. That was reason I couldn't see the install button.
If I reboot now, I will loose root.
BTW. I do not use TWRP
Anyway. Rebooted and lost root. Will wait for patched boot image.
Everything else seems to work
UPDATE: Used the beta 1 patched boot image to fastboot -- used magisk to patch -- root is back!
Click to expand...
Click to collapse
You can root without using patched boot image
https://forum.xda-developers.com/oneplus-6/how-to/root-solve-issue-oxgyen-os-beta-1-t3839939
does this happen to you guys too when quick switching between apps? in oos beta 1 and still problem persists in oos beta 2
kewlest22 said:
does this happen to you guys too when quick switching between apps? in oos beta 1 and still problem persists in oos beta 2
Click to expand...
Click to collapse
Yes, this occurs when you use any launcher other than the OnePlus stock launcher.
While it wasn't this broken, in the HydrogenOS beta 2 the quick switch performed notably worse when using a non-stock launcher.
This issue, and issues like it, may effectively end up circumvented in the future when third party launchers start implementing their own recent apps implementations.
Open beta 2 changelog
Moderator Information,
Thread closed, We have an existing thread here: [Official Android Pie Beta] Oxygen OS Open Beta 2 for the OnePlus 6 .
Many thanks,
Stephen
As the title says, Magisk crashes when I try to patch the boot.img after installing the latest March security patch on my Pixel 3a.
You are right, wait for a fix at
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
In the meantime, I did go back to the February security patch...
biontx said:
You are right, wait for a fix at
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
In the meantime, I did go back to the February security patch...
Click to expand...
Click to collapse
Thanks for letting me know, should've checked the Magisk Canary thread first ^^
However, I get into a bootloop when I try to downgrade back to the February patch. Guess I'll just wait it out...
I'm on the March patch as well and I was able to successfully patch the boot.img using the lastest magisk manager.
NinjaCoool said:
I'm on the March patch as well and I was able to successfully patch the boot.img using the lastest magisk manager.
Click to expand...
Click to collapse
That's weird. How did you update? Magisk OTA, sideload OTA or flashing March factory image?
In any case, would you mind sharing your patched boot.img? I'm not sure I want to live without root until they fix it ^^
EDIT: Scratch that, it seems that flashing a prepatched boot.img causes a bootloop. They probably changed something in the files, that causes the issues when flashing the factory image.
I had the same issue with crashing while patching. I had to install MagiskManager 7.5.1 from the xda forum. After that patching succeeded.
AndDiSa said:
I had the same issue with crashing while patching. I had to install MagiskManager 7.5.1 from the xda forum. After that patching succeeded.
Click to expand...
Click to collapse
But 7.5.1 is the stable/beta relase channel which doesn't even support Android 10 yet?! I can patch the boot.img with that, but it doesn't boot.
I had no problems applying the February update but I did it before it was available through system update. So I had to do it the long way - uninstalling magisk, downloading the update and installing it, downloading the boot image, patching it, and then installing the magisk patched boot image. It all worked fine though with no issues after the update.
My Magisk version is 20.3 and Magisk Manager is 7.5.1.
Velcorn said:
But 7.5.1 is the stable/beta relase channel which doesn't even support Android 10 yet?! I can patch the boot.img with that, but it doesn't boot.
Click to expand...
Click to collapse
If I remember correctly versions before 19.1 /7.3.x didn't support Android 10. For me 7.5.1 worked flawlessly.
yaconsult said:
I had no problems applying the February update but I did it before it was available through system update. So I had to do it the long way - uninstalling magisk, downloading the update and installing it, downloading the boot image, patching it, and then installing the magisk patched boot image. It all worked fine though with no issues after the update.
My Magisk version is 20.3 and Magisk Manager is 7.5.1.
Click to expand...
Click to collapse
Weird, thanks for letting me know. I manually updated through flashing the March factory image and when I patch the boot.img through MM 7.5.1 I just get into a bootloop.
I did the sideload. 7.5.1 beta. Patched ok. Flashed ok all set for another month.
dkryder said:
I did the sideload. 7.5.1 beta. Patched ok. Flashed ok all set for another month.
Click to expand...
Click to collapse
Could you upload your patched boot.img please?
It said file too large when I tried. It's about 30MB. Not sure what's up with that.
Latest magisk from topjohnwu's github set to beta update channel, March update straight from Google, bootloader unlocked. Patched with magisk 1st time, and flashed via fastboot. Booted first time.
Not sure what to advise, just wanted to let you know that it does work with the latest versions of both magisk and firmware. Did you enable adb and enable OEM unlock in Developer Options?
---------- Post added at 01:19 AM ---------- Previous post was at 01:01 AM ----------
biontx said:
Could you upload your patched boot.img please?
Click to expand...
Click to collapse
here you go mate, Pixel3a (Sargo) March firmware straight from google, patched and confirmed working.
http://bit.ly/sargobootpatchedmarch
MD5: d69ee45e403b5bcf24c43cacf31cb7c2
captain sideways said:
Latest magisk from topjohnwu's github set to beta update channel, March update straight from Google, bootloader unlocked. Patched with magisk 1st time, and flashed via fastboot. Booted first time.
Not sure what to advise, just wanted to let you know that it does work with the latest versions of both magisk and firmware. Did you enable adb and enable OEM unlock in Developer Options?
---------- Post added at 01:19 AM ---------- Previous post was at 01:01 AM ----------
here you go mate, Pixel3a (Sargo) March firmware straight from google, patched and confirmed working.
http://bit.ly/sargobooypatchedmarch
MD5: d69ee45e403b5bcf24c43cacf31cb7c2
Click to expand...
Click to collapse
Super, tx
Is anyone else having issues with Safetynet CTS after the latest security patch? For some reason it doesn't work for me anymore. I haven't made any other changes.
captain sideways said:
Latest magisk from topjohnwu's github set to beta update channel, March update straight from Google, bootloader unlocked. Patched with magisk 1st time, and flashed via fastboot. Booted first time.
Not sure what to advise, just wanted to let you know that it does work with the latest versions of both magisk and firmware. Did you enable adb and enable OEM unlock in Developer Options?
---------- Post added at 01:19 AM ---------- Previous post was at 01:01 AM ----------
here you go mate, Pixel3a (Sargo) March firmware straight from google, patched and confirmed working.
http://bit.ly/sargobooypatchedmarch
MD5: d69ee45e403b5bcf24c43cacf31cb7c2
Click to expand...
Click to collapse
Thanks for the effort. Still ends in a bootloop for me. Guess it's time for a fullwipe...
Velcorn said:
Thanks for the effort. Still ends in a bootloop for me. Guess it's time for a fullwipe...
Click to expand...
Click to collapse
Sorry it didn't help, thanks for letting me know though, but I'm out of ideas now
MeowDotEXE said:
Is anyone else having issues with Safetynet CTS after the latest security patch? For some reason it doesn't work for me anymore. I haven't made any other changes.
Click to expand...
Click to collapse
Me too. It's the first time now with the March update.
"cts profile: false"
Made an account to say I had the same problem with Pixel 3XL and I did what captain sideways posted. I went to the github for magisk, took the apk from the latest zip file release and installed that. I was able to patch my boot image afterwards. Root works fine. I flashed the patched boot image to both slots. However, the ctsProfile does fail like mentioned above.
Read the full page of OnePlus 9 thread! No firmware and boot files were found
iSkyJIE said:
Read the full page of OnePlus 9 thread! No firmware and boot files were found
Click to expand...
Click to collapse
What're you on about?
TheKnux said:
What're you on about?
Click to expand...
Click to collapse
Did not find the T-Mobile version of OnePlus 9 firmware or boot.img! Need boot files to root this phone！
You pull the boot.img yourself
iSkyJIE said:
Did not find the T-Mobile version of OnePlus 9 firmware or boot.img! Need boot files to root this phone！
Click to expand...
Click to collapse
There's ways to pull the boot.img using adb/fastboot commands once your bootloader is unlocked. Then all you have to do is patch it using Magisk and flash it in fastboot.
TheKnux said:
You pull the boot.img yourself
There's ways to pull the boot.img using adb/fastboot commands once your bootloader is unlocked. Then all you have to do is patch it using Magisk and flash it in fastboot.
Click to expand...
Click to collapse
Thank you for your reply！
My bootloader has been unlocked! But I don't know how to extract it to boot.img
You don't specifically need the T-Mobile boot.img to root your phone. Get the boot.img from this post: https://forum.xda-developers.com/t/root-oneplus-9.4253651/page-4#post-84874313
Install the Magisk App on your phone
Reboot into fastboot
fastboot boot boot11244AAmagisk.img
Once your phone boots, open the Magisk app
Ignore any message about it needing to setup
Install Magisk with a direct install
Reboot and now your phone should be rooted
I've tested this on my one T-Mobile OnePlus 9 and it works perfectly, even passing SafetyNet
Lomeli12 said:
You don't specifically need the T-Mobile boot.img to root your phone. Get the boot.img from this post: https://forum.xda-developers.com/t/root-oneplus-9.4253651/page-4#post-84874313
Install the Magisk App on your phone
Reboot into fastboot
fastboot boot boot11244AAmagisk.img
Once your phone boots, open the Magisk app
Ignore any message about it needing to setup
Install Magisk with a direct install
Reboot and now your phone should be rooted
I've tested this on my one T-Mobile OnePlus 9 and it works perfectly, even passing SafetyNet
Click to expand...
Click to collapse
Thank you,
I'll try extracting the 11.2.2.2AA international version of boot, which I'm currently version 11.2.2.2
If anyone has the stock oneplus9
T-mobile 11.2.2.2 boot.img please kindly share.In haste, trying to root my phone I accidentally flashed a patched 11.2.2.2 boot.img from the eu version. It got root but now I can't pass safety check. I would like to restore stock T-Mobile boot.img
inspron said:
If anyone has the stock oneplus9
T-mobile 11.2.2.2 boot.img please kindly share.In haste, trying to root my phone I accidentally flashed a patched 11.2.2.2 boot.img from the eu version. It got root but now I can't pass safety check. I would like to restore stock T-Mobile boot.img
Click to expand...
Click to collapse
MagiskHide enabled?
TheKnux said:
MagiskHide enabled?
Click to expand...
Click to collapse
Yes.
inspron said:
Yes.
Click to expand...
Click to collapse
Not sure then. I'm at work right now so I'm kinda tied up for helping you out until I get home.
TheKnux said:
Not sure then. I'm at work right now so I'm kinda tied up for helping you out until I get home.
Click to expand...
Click to collapse
Thank you. I am hopping that the problem will be fixed when I have access to a stock boot.img from T-Mobile oneplus9.
Attached is my stock 11.2.2.2 boot.img from T-Mobile oneplus 9 (LE2117).
Hope it helps you out.
boot.img
drive.google.com
inspron said:
If anyone has the stock oneplus9
T-mobile 11.2.2.2 boot.img please kindly share.In haste, trying to root my phone I accidentally flashed a patched 11.2.2.2 boot.img from the eu version. It got root but now I can't pass safety check. I would like to restore stock T-Mobile boot.img
Click to expand...
Click to collapse
Magisk 22.1 stable, has a safety net api error. Not sure if that is your issue. Mine fails in magisk app but passes on safety net test apk.
Jg1234 said:
Magisk 22.1 stable, has a safety net api error. Not sure if that is your issue. Mine fails in magisk app but passes on safety net test apk.
Click to expand...
Click to collapse
Wow! Thank you. Failed Magisk but It does pass this https://play.google.com/store/apps/details?id=org.freeandroidtools.safetynettest
Jg1234 said:
Attached is my stock 11.2.2.2 boot.img from T-Mobile oneplus 9 (LE2117).
Hope it helps you out.
boot.img
drive.google.com
Click to expand...
Click to collapse
Thank you stranger!!!
Jg1234 said:
Magisk 22.1 stable, has a safety net api error. Not sure if that is your issue. Mine fails in magisk app but passes on safety net test apk.
Click to expand...
Click to collapse
I am curious, when we get an incremental update from T-mobile, we will be able to apply the update if we pass Safety net or it's not related?
inspron said:
I am curious, when we get an incremental update from T-mobile, we will be able to apply the update if we pass Safety net or it's not related?
Click to expand...
Click to collapse
I'm not to sure on that one.. I came from the 6t t-mobile version and it had the local upgrade option.
inspron said:
I am curious, when we get an incremental update from T-mobile, we will be able to apply the update if we pass Safety net or it's not related?
Click to expand...
Click to collapse
No, T-mobile doesn't allow update if bootloader unlocked. has nothing to do with safetynet. If you look in system after unlocking your bootloader and rebooting you will see system update no longer avail.
Jg1234 said:
Attached is my stock 11.2.2.2 boot.img from T-Mobile oneplus 9 (LE2117).
Hope it helps you out.
boot.img
drive.google.com
Click to expand...
Click to collapse
11.2.2.2 AA International’s BOOT is only 96MB, and the T-MOBILE 11.2.2.2 BOOT you provide is 192MB, maybe this is the difference.