PREWARNING
THIS GUIDE IS !!ONLY!! FOR N9600 (INTERNATIONAL Snapdragon Model)
DO NOT ATTEMPT ON SPRINT, VERIZON, T-MOBILE, AT&T, OR ANY OTHER US (United States) MODEL PHONE.
BEWARE!! N960U or N960U1 HAS A LOCKED BOOTLOADER WHICH CAN NEVER BE UNLOCKED!
IF YOU ATTEMPT TO ROOT ON ANY US MODEL, YOU WILL BRICK YOUR PHONE!
If you have an N9600 international snapdragon model, please proceed. If not, read for your pleasure or future consideration but DO NOT attempt on a US model.
This guide can also be useful for N960F or N960FD international Exynos models, but you would have to change some things like use the right links.
==================================================================================================
Intro Notes:
I REPEAT: THIS GUIDE IS !!ONLY!! FOR N9600 (INTERNATIONAL Snapdragon Model)
If you have an N9600 international snapdragon model, please proceed. If not, read for your pleasure or future consideration but DO NOT attempt on a US model.
After much thought, research, reading, and contemplation, between Note 8, Galaxy S9+, and Note 9, I have decided on the Note 9.
Out of the available options for rooting, there are the devices, N960F, N960FD, and N9600.
Of course, N960F N960FD are Exynos. Unfortunately, these will not work on Verizon, so I would have to switch to T-Mobile. To stay on Verizon it would have to be N9600.
Ultimately, I decided on N9600. Why? Because with Detonator, I can root the N9600 on Verizon, and it's the only model that I can use on Verizon fully rooted. (There is a partial root on N960U, the US Snapdragon variant, but the root is only partial and will have bugs or may not wok.) I could root with a partial root the Note 8 US version, but it is not that much cheaper and it would only be a partial root, so I decided on N9600.
You can root fine on the Exynos versions, but you could not use Detonator for WIFI calling and other features on Verizon.
Rooting Guide
0. Battery must be above 82% before rooting.
1. Root N9600 using TWRP method (Beta)
PLEASE READ ALL INSTRUCTIONS THERE FOR ROOTING.
https://forum.xda-developers.com/ga...ecovery-twrp-galaxy-note9-snapdragon-t3845536
(Official XDA Magisk Install Guide, don't follow directly just reference)
2. RMM State Fix (Prevent "Prenormal")
IMMEDIATELY after getting into TWRP, flash the RMM-State_Bypass_Mesa_v2.zip (linked below).
If you do not, then you will get locked out for 7 days in the event you flash anything or flash a new OS or downgrade to Oreo, etc.
You have to do this EVERY TIME you flash something to prevent RMM state to going to "Prenormal" which means wait 7 days before you can flash any non-samsung firmware.
3. How to fix: Stuck on Prenormal and didn't bypass, OEM Unlock missing
You might be stuck because you didn't do the RMM bypass above. In this event, you will be blocked from flashing custom binaries including TWRP. The only thing you will be able to flash is original Samsung firmware.
How to bypass now? There are two solutions for solving Prenormal RMM state. I have done both successfully. There is a third but it rarely seems to work (date hack, available at many sites.)
METHOD 1: Long way around. Wait 7 days.
First wipe your whole device again and reflash your original OS in ODIN. If you don't do this then it's possible that after 7 days, OEM unlock will not show up.
Now wait 7 days.
Do not reboot your device, just for good measure. I did reboot my device, several times, and it still appeared after 7 days and a reboot. Don't know if you'll have the same luck.
The second time after turning on OEM Unlock, however, when it wiped my device, I did NOT reflash the whole OS again. And, after 7 days again, it did NOT show up.
METHOD 2: I waited 7 days, but no OEM unlock! Solution: Chimera application for windows. NOT FREE!
I was tired of waiting so I decided to try it, and it worked.
Activate Developer options
Activate USB Debugging (in Developer Options)
DISABLE "Verify apps via USB" (in Developer Options)
Go to https://chimeratool.com/
Buy the 3 days trial.
Download after paying in PayPal.
Install full application and all drivers. Don't customize it just install full.
Put your phone into Download mode
Turn off phone.
Hold Bixby & Volume Down
Plug phone into PC.
Press volume up at prompt. Download mode will be activated.
Now in Chimera application in Windows it will find your phone.
Choose the option "UNLOCK".
Choose the sub option, "RMM Unlock".
SUCCESS!! NO WAITING!! OEM Unlock activated. Worth every penny in my opinion (because it wasn't too many pennies).
Proceed to install TWRP and DO NOT FORGET TO INSTALL RMM BYPASS AFTER EVERY SINGLE FLASHING OF ANYTHING!!
4. After rooted, flash Detonator
File: Verizon EFS/CSC Detonator: Detonator v3 for Oreo 8.1 (linked in file list below)
(There is no Detonator for Pie on Verizon as of this writing, only Oreo)
0. Download DETONATOR_XXX_OREO_VZW_EFS-CSC_vx.x_INT_TEKHD.zip to your phone.
Maybe just copy to your SD card, easiest way.
In order to flash detonator, in TWRP select every box on the Mount screen (OTB will not be available unless you have one connected, but everything else).
Backup all partitions via TWRP.
Then go to Install (in TWRP) and flash the zip file for Detonator which applies to you. (Do NOT flash right after flashing a ROM!; First boot ROM at least one time… then go back to TWRP and flash Detonator)
After you successfully flash detonator and there are no errors, now if you want to remove the Verizon boot screen now go ahead and flash (through Install screen in TWRP) the Samsung BootAnimation zip on the Detonator website. This will replace your boot with the stock black samsung boot.
After doing these, please remember to flash the RMM State zip file. Always do this again after every flash of anything in TWRP!
Detonator features (from the website):
*With the Verizon Detonator you will get:
– VoLTE, Wifi-Calling /4G/LTE/ONLINE services & features.
– AdAway
– AppLock
– OperaMax (VPN/Data Saving)
– Caller ID & Spam Protection
– Phone and messaging Firewall
– Floating Messages
– Screencast/ScreenRecorder
– Ultra Data Saving Mode
– When booting for the first time… turn off “Confirm Network Connection” Under Settings -> Connections… (*IF AVAILABLE*) (see image below)
Changelog for Verizon Detonator:
v3 – CSC Features added / Wi-Fi Calling APK Update
vPRE-2.2 – Smart Manager Device Security Fix
vPRE-2.1 – Added Mobile Data Toggle to Power Menu.
vPRE-2 – Fixed XML Code / Features Added
vPRE-1 – Initial Release. (Test Phase)
NOTE: After installing Detonator, WIFI Calling button disappeared. I confirmed that I do NOT have WIFI calling, sadly. It doesn't work.
Test it by turning on airplane mode, then connecting to WIFI, then try to make a call. You will get a popup with option to turn on WIFI calling. If you try, it will result in an error, "Unable to activate WIFI Calling at this time, please try again later".
There is presently no solution I am aware of, but maybe someone else knows how, search the forums. Also maybe it has to do with the particular OS I decided to use. I could start over from scratch and try again, but it would be a lot of work and I am out of time for now.
Keep in mind you have to activate on Verizon (see below) before trying to make a call.
5. ACTIVATE ON VERIZON:
Activating on Verizon cannot be done through their site, it will result in an error that your device is incompatible, so don't bother with that.
0. In order to activate you just need an already working SIM card.
Activate a new Verizon SIM card on your PREVIOUS device.
If you need an excuse say you need it for your new phone and YOU will activate it yourself right in the store. Then say it's not working let's try activating on my old phone first.
After the new SIM is working on your OLD phone, leave the store and go home. Now, at your leisure remove the SIM from your old phone and now insert it into your N9600.
Reboot. Now you will be activated on Verizon! (NOTE: YOU MUST ALREADY HAVE DONE DETONATOR, FOLLOW ALL STEPS ABOVE FIRST.)
After you do the rooting below, you'll get messages from SecurityLogAgent saying "security error your device was modified, reboot to revert the changes". You can eliminate this by going into Titanium Backup and FREEZE the following:
SecurityLogAgent
Security policy updates
Software update
Configuration Update
6. Magisk Manager
Boot into phone. If you see Magisk Manager it means you are rooted, probably.
To check it open the Magisk Manager app on your phone.
Feel free to update Magisk. I updated it in the app to 19.3 for Magisk and the installer (flashed from the zip in TWRP) is 7.2
Tap to start safetynet, and accept all prompts.
Reboot
Test if rooted by installing Titanium Backup. If it asks for SuperSU permission then Grant, and it means you are rooted!
7. After rooted, install Xposed
Download xposed from the link in the files section below. If you have a Note 9 on Oreo 8.1 then your file is the SDK 27 for Arm64.
In TWRP, flash the zip file.
Now flash the RMM State zip file. Always do this again after every flash of anything in TWRP!
Backup if desired.
Boot your phone.
Go to the xposed links and get the APK file for xposed. This will be the app you use to manage xposed.
WARNING:
One or more of the settings in the xposed module GravityBox [O] causes bugs and removes your Verizon compatibility. In order to solve the error "No SIM card inserted" (but it is inserted!), what you have to do is to go back into TWRP, and do all steps for the Detonator instructions that I wrote above (it will NOT wipe your device, so don't worry). Once you re-flash Detonator, your Verizon will work again and the SIM card message will be gone.
WARNING 2:
There was another xposed module that caused a similar issue but worse. The issue in reference is you get a black screen at the lock screen but nothing can come up but the reboot menu. You cannot get into the phone. I was about to consider having to factory reset before I solved the issue. Since the issue was an xposed module, then the solution is to:
Download the most recent arm64 xposed uninstaller .zip file from here: https://dl-xda.xposed.info/framework/uninstaller/
Boot into TWRP, flash the xposed uninstaller zip.
Clear the cache and dalvik cache like it suggests using that button on the screen there.
Now flash the RMM State zip file. Always do this again after every flash of anything in TWRP!
Reboot into your phone, your problem is now solved!
Finally, go into Xposed Installer and find the Module that was causing the issue, long-press on it and choose uninstall. I know you want to keep it, but it's too bad, you can re-download it later, you will be unable to simply unselect it. You have to uninstall it.
Now you can go back into TWRP and reinstall xposed.
Last step: flash the RMM State zip file. Always do this again after every flash of anything in TWRP!
Files Needed
ODIN: https://odindownload.com/
- Odin 13.3.1
TWRP: https://forum.xda-developers.com/devdb/project/?id=29220#downloads
- TWRP_3.2.3-0_N9600_beta3.tar.md5
- boot.img (he recommends to use this, see tutorial)
- Encryption disabler.zip
MAGISK: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
- Magisk 16.7 19.3 (can I use latest version 19.3? Answer: YES, I used 19.3 without any problems.)
USB DRIVERS: https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
- SAMSUNG_USB_Driver_for_Mobile_Phones.zip
BYPASS RMM STATE: https://forum.xda-developers.com/showpost.php?p=75360965
- RMM-State_Bypass_Mesa_v2.zip
DETONATOR: http://tekhd.com/detonator-o/
- DETONATOR_N9_OREO-8.x_VZW_EFS-CSC_v3_INT_TEKHD.zip
DIRECT LINK (VZW v3): https://androidfilehost.com/?fid=11410963190603842742
MIRROR: https://mega.nz/#!cP52EYKS!L9Oc7nihQ2RoXddZPAPXCPdVLvzhXq3VZtaZXGzBtDQ
(link is was down but I have the file which I uploaded for you: [EDIT: TekHD link is back up now! The domain was expired but I spent some time on the phone with GoDaddy trying to renew their domain for them, maybe the dev was able to see it since I told them to reach out to him specifically. GoDaddy refused to let me donate to renew his domain for him. Again update it appears the site is down again. But not expired this time, it just says "pageok". I do have all the data from that site so I will upload it for the community sometime.]
XPOSED (for Oreo 8.1): https://dl-xda.xposed.info/framework/sdk27/arm64/
- xposed-v90-sdk27-arm64-beta3.zip
XPOSED UNINSTALLER (to fix a bad module. See Warning 2.): https://dl-xda.xposed.info/framework/uninstaller/
- xposed-uninstaller-20180117-arm64.zip
OREO 8.1 FIRMWARE (for downgrade):
- N9600ZHS1ASB1 / N9600OWA1ARL5 (N9600 8.1 Oreo 2019-02-01 Chile) https://www.sammobile.com/firmwares/galaxy-note9/SM-N9600/CHL/download/N9600ZHS1ASB1/259310/
- N9600ZHU1ARG6 / N9600OWA1ARG6 (N9600 8.1 Oreo 2018-07-01 Dom Rep) https://www.sammobile.com/firmwares/galaxy-note9/SM-N9600/CDR/download/N9600ZHU1ARG6/231741/
- N9600ZHU1ARG6 / N9600OWE1ARG6 (N9600 8.1 Oreo 2018-07-01 Ecuador) https://www.sammobile.com/firmwares/galaxy-note9/SM-N9600/ALE/download/N9600ZHU1ARG6/231755/
** These three files have been removed from sammobile as of today 2019-05-25, because they were there yesterday. You can still view directly but they will no longer show on the page for the N9600 because sammobile is no longer showing any Oreo (8.0, 8.1) firmwares for the N9600 on their site, only Pie firmwares (9). It's likely these will be removed soon, so I will upload mirrors to the firmwares once they are finished downloading.
(NOTE: DO NOT download firmware N9600ZHS1ASA7_N9600OWT1ARK1_SAM because it will after initializing forcefully change your boot branding to a bright baby blue screen with Movistar carrier branding instead of a normal black samsung boot screen. This will be removed by re-flashing so it's harmless, just annoying. Instead use the above linked. So far I have only tested N9600ZHS1ASB1 above which is fine, it is on the Clara carrier and installs minimal carrier bloat which can be removed after rooting. I linked the other two which I will try as they use pre-August 2018 firmware so hopefully I can get the OEM Unlock to show since I didn't know about the RMM state fix before flashing Pie down to Oreo.)
UPDATE:
This guide is now completed and released. The steps are fully working to get your N9600 working on Verizon.
Someone asked me if regular calling works if they don't have WIFI. Of course. Your phone will fully work on Verizon as normal. In addition to fully working, WIFI calling also works (for some firmwares).
UPDATE 2:
DEAR EVERYONE:
Sorry it took so long for me to upload the files. It appears that TekHD website is now dead for good. It's been down for months. So, since I already had downloaded all the content from the website, including the website pages themselves, I'm now uploaded everything from TekHD for your use. I'm also including all of my rooting files for your use and enjoyment.
Will update the links here when the uploads complete. Enjoy!
EDIT: Here's the link!
https://mega.nz/#F!UbZFSAwC!FObELw39ZmADygAJOFVlyw
-
[moved content from here into original post]
[reserved]
I used a exynos S9+ and I'm using a note 9 exynos on Verizon. You don't need to flash anything because if you use shortcutmaster to bring up Ims settings, with root of course, you can enable all you need.
But you don't have wifi calling or several other things right?
I also had to do a RMM state flash. But I didn't know and now I am blocked from doing anything for a week after downgrading OS. Wish someone would have told me ahead of time. The hacks to change date to bypass and re-enable OEM lock DOES NOT WORK. Trying many things, wasted my whole saturday needlessly.
I finally got the OEM unlock to show.
STEPS:
1. Using Odin flash the whole OS from sammobile. I used 8.1 which is compatible with Detonator.
2. During setup, DO NOT CONNECT TO INTERNET.
3. Choose a date some time in the past like a month or even a year ago. I chose a year ago.
4. finish setup disabling everything.
5. General Management → Date and time. DISABLE Automatic date and time.
6. Enable developer options.
a. Settings > About phone
b. tap seven times on ‘Build number’
7. Settings > Developer options > DISABLE Auto update system
8. It will not work unless you also log into a samsung account.
a. Connect to internet now.
b. Cloud and accounts > Accounts > Add account
c. Sign in or create a new Samsung account.
d. You have to log in and add the account, go back and it should say added.
9. DISCONNECT FROM INTERNET
10. Go to date and time. Choose a date in the future. I chose a few months in the future.
11. Settings > Software update > tap on Download updates automatically (it will error because not connected. It's fine. Don't connect!)
12. REBOOT
13. Settings > Developer options. The OEM unlock option should be visible now.
I think the above is what I did. I might have the order above wrong because I tried so many times I can't remember if that's the exact order. I think it is, but if it doesn't work try a few different ways and eventually you'll get it.
EDIT: When I tried again, above does not work so I must not have remembered what I did perfectly, OR for some reason it just didn't work the second time.
[.]
Before I bust out the Type-C cable, I must ask, will this work on the Sprint variant?
Any plan to ad sprint to the list
eastside08 said:
Before I bust out the Type-C cable, I must ask, will this work on the Sprint variant?
Click to expand...
Click to collapse
NO!!! BEWARE, N960U or N960U1 HAS A LOCKED BOOTLOADER.
IF YOU ATTEMPT TO ROOT ON ANY US MODEL, YOU WILL BRICK YOUR PHONE!
The ONLY Snapdragon model that can be rooted is the INTERNATIONAL N9600. I specifically bought the N9600 for this. This N9600 has an unlocked bootloader.
I was planning on running Detonator on the Oreo 8.1 since the developer TekHD has not yet developed a Detonator for Pie on Verizon. Plus, I read that many people prefer Oreo over Pie. Moreover, Oreo will have more dev support than Pie since Pie is still very new.
I am still working on this so will continue progress updates.
Right now I am stuck because I didn't know about the RMM State so I am stuck on Prenormal, which means 7 days waiting. I had gotten the OEM unlock to show because I was going to disable and re-enable OEM unlock, and when I proceeded it wiped, and then changed to Prenormal preventing from installing TWRP again.
If I had known ahead of time, I could have flashed the RMM fix zip while I had TWRP on there and could have avoided this fiasco. If I get OEM unlock to show again then I will use that to avoid future lockouts.
Right now I am downloading a July 2018 version of Oreo 8.1. I tried flashing several Oreo 8.1 and that is easy with Odin, but could not get the OEM unlock to show up again no matter what I tried. According to this page** (link below), the method of switching the time doesn't work on pre- August 2018 firmwares. That's not entirely accurate as I got it to show up the first time, but I may be stuck now.
So in an effort to try anything, I am downloading and will flash the earlier version of 8.1 from July. Then will try the date method to try to get it to show up. Hopefully it works.
** NOTE: link from above is https://www.thecustom droid.com/prenormal-rmm-state-on-samsung-galaxy-guide/ (remove the space between custom and droid)
For future reference, guides go in the guides section, not development.
Update: I can't get OEM unlock to show up and ran out of time. So, I have to take the long way around and wait a week for it to show up. So, I'll be back on Sunday if OEM unlock shows up.
Im guessing this trips knox ?
why put 'Verizon Full Rooting Guide' when rooting has nothing to do with carriers.
the guide is to get verizon csc on a n9600. you should change the way you named the thread if you dont want to get a gazilion questions from n960u uers.
i sure am confused.
are you able to root a international note9 and use it on verizon network in the usa, or not?
i know elliwigy is working on getting root for a specific model of note9, i think for the usa unlocked or verizon locked model, but it's not useable on stock firmware yet.
UPDATE:
After 7 days, a reboot, and pressing check for updates (but not updating), then checking for the OEM unlock, it did in fact show up.
Unfortunately, enabling OEM unlock also factory resets your phone which AGAIN puts the 7 day lock - which is f*ing ridiculous.
So now I have to wait ANOTHER 7 days before proceeding, so that Prenormal will be able to go to Normal and I can flash TWRP and custom binaries.
Will update again in another week.
bober10113 said:
why put 'Verizon Full Rooting Guide' ... if you dont want to get a gazilion questions from n960u uers.
Click to expand...
Click to collapse
Please note the tag [N9600], if N960U users fail to read the full title, that's their fault. I put all the disclaimers in red anyway just in case, so they can know.
This indeed is about using an international N9600 on Verizon in the USA. I am still working on this and as per my previous post, in another week once the 7 day wait period is over again so I can finish the root and flashing, then I will continue to update about how to get the N9600 working on Verizon.
It is worth noting that you are required to root the N9600 in order to use Detonator.
siriom said:
Im guessing this trips knox ?
Click to expand...
Click to collapse
The answer to this is Yes. It trips Knox. You cannot root without tripping Knox.
dumbfone said:
are you able to root a international note9 and use it on verizon network in the usa, or not?
i know elliwigy is working on getting root for a specific model of note9, i think for the usa unlocked or verizon locked model, but it's not useable on stock firmware yet.
Click to expand...
Click to collapse
The answer to this is hopefully yes, and I have known others to get the N9600 working on Verizon. But I have to wait another week before I can proceed, so please check back next week to see my progress and additional instructions.
Hello everyone,
I have wonderful and amazing news. I have completed fully rooting my Note 9 N9600 and also getting it fully working on Verizon. I am updating the original post now with the details and remaining steps.
It's worth noting that after the second 7 days, OEM unlock would NOT show up. I waited hours more, but still no luck. Instead, I used an application called Chimera which I actually paid for in order to get OEM unlock to finally show up, and it worked.
Update: See the above completed and updated guide.
zxzxzxzxzxzxzxzxzx said:
Update: See the above completed and updated guide.
Click to expand...
Click to collapse
so the way to do it is just flashing the latest detonator?
http://tekhd.com/detonator/
(apparently with full wifi calling support too..)
http://tekhd.com/detonator-o/#vzwdetonator
(or go to detonator telegram channel for possibly modded comunity version...rumor i heard)
implicitly, people probably already know how to root by following the steps outlined from the snapdragon thread..
I know there are ways to enable VOLTE for OOS 9, but the toolkit will need to be downloaded. Does anyone know if there are ways to enable VOLTE for OOS 10?
lloydlim996 said:
I know there are ways to enable VOLTE for OOS 9, but the toolkit will need to be downloaded. Does anyone know if there are ways to enable VOLTE for OOS 10?
Click to expand...
Click to collapse
Download the latest OEMlogkit app from apkmirror and install
And then in the Telephone App *#800# Choose
And then under function Switch you can activate it
lloydlim996 said:
I know there are ways to enable VOLTE for OOS 9, but the toolkit will need to be downloaded. Does anyone know if there are ways to enable VOLTE for OOS 10?
Click to expand...
Click to collapse
same toolkit method works or just follow tutorial from here
also read my note https://forum.xda-developers.com/on...lte-vowifi-t3934227/post79987003#post79987003
Is it that every update need to use pdc to activate volte and vowifi? Mine was gone after installed incremental update 10.0.0.1
You do not need any apk or modify anything.
Settings/WiFi & internet/SIM & Network/click SIM 1 (your provider) you will see enhanced communications.
ben3003 said:
Is it that every update need to use pdc to activate volte and vowifi? Mine was gone after installed incremental update 10.0.0.1
Click to expand...
Click to collapse
yes the updates are overwriting the settings in the firmware partition (modem)
I just brought an unlocked Oneplus 9 and using it on T-mobile network. I am having the following problems with Android 12 (OOS LE2115_11_C.61). I am wondering if Android 11 have these problems as well or not (only had the phone for less than 2 days).
1. Wifi Calling: Able to dial call but unable to hear audio from the other party. However, they can hear me w/o any issues. Tried resetting my network, it didn't resolve this issue. Currently using phone w/ wifi calling off.
2. Lockscreen Issue: There are no option to hide the actual pattern lock and also the pattern lock placement seems to moved further up on the screen.
3. Battery charging time no longer indicates on the lockscreen.
4. Sometimes the "Close All" button only closes all other apps besides the last one I were on. Sometimes it works. So, it's random.
If downgrading to Android 11 resolve some of the above issues, I have the following questions about the downgrade.
1. Is there a way to back up all my apps and app data locally and restore it after downgrade (like Tatinium Backup)?
2. Does downgrade require unlock bootloader?
3. If unlocked bootloader, would you suggest root, go for a custom rom or stay with OOS 11?
4. If downgrade to OOS 11, is there a way to keep security update w/o going to Android 12?
Thanks in advance!
drift08 said:
If downgrading to Android 11 resolve some of the above issues, I have the following questions about the downgrade.
1. Is there a way to back up all my apps and app data locally and restore it after downgrade (like Tatinium Backup)?
2. Does downgrade require unlock bootloader?
3. If unlocked bootloader, would you suggest root, go for a custom rom or stay with OOS 11?
4. If downgrade to OOS 11, is there a way to keep security update w/o going to Android 12?
Thanks in advance!
Click to expand...
Click to collapse
1. Use Swift Backup. However, you will have to move all your data to a PC because it'll wipe when you go back to 11.
2. No. You'll have to unlock it again. Don't move your data back until after you unlock the bootloader though as it factory resets as part of it.
3. I rooted. My big thing is Gravity Box and ad blockers. Stayed with OOS though. Others are too much hassle compared to previous OPs. xXx (Magisk Rom) from the 7 and 8 days still works fairly well on 11. It hasn't been updated, but it also don't touch anything underneath. If you don't like it, it's easy to get rid of. It's customizable by a text profile you edit.
4. Not that I know of. I believe OP has gone on to A12. If you root, you can't take OTAs, you have to have full images. You can download them from one of the stickies.
drift08 said:
I just brought an unlocked Oneplus 9 and using it on T-mobile network. I am having the following problems with Android 12 (OOS LE2115_11_C.61). I am wondering if Android 11 have these problems as well or not (only had the phone for less than 2 days).
1. Wifi Calling: Able to dial call but unable to hear audio from the other party. However, they can hear me w/o any issues. Tried resetting my network, it didn't resolve this issue. Currently using phone w/ wifi calling off.
2. Lockscreen Issue: There are no option to hide the actual pattern lock and also the pattern lock placement seems to moved further up on the screen.
3. Battery charging time no longer indicates on the lockscreen.
4. Sometimes the "Close All" button only closes all other apps besides the last one I were on. Sometimes it works. So, it's random.
If downgrading to Android 11 resolve some of the above issues, I have the following questions about the downgrade.
1. Is there a way to back up all my apps and app data locally and restore it after downgrade (like Tatinium Backup)?
2. Does downgrade require unlock bootloader?
3. If unlocked bootloader, would you suggest root, go for a custom rom or stay with OOS 11?
4. If downgrade to OOS 11, is there a way to keep security update w/o going to Android 12?
Thanks in advance!
Click to expand...
Click to collapse
1. If you use the local back up option under settings > system settings > back up and reset > local backup then most of your apps get backed up, but the downloaded data will not be saved and you have to log into the accounts on each app. I'm still looking for another way to backup, but I'm hesitant because this method of backup retains my T-Mobile SIM settings after I converted it to Global.
2. I was on OOS 12.41 on a T-Mobile branded OP9, and when I used @craznazn 's MSM conversion tool, it downgraded my phone to Global OOS 11.2.2. I suppose if you wanted to downgrade you could use his tool, or any MSM tool made for a T-Moble version on OOS 11, and it would boot that version, and then you could update to the latest 11.
3. I would suggest root if you have your bootloader and sim unlocked, if not, I would just stay on a stable version of OOS since you wouldn't be able to flash under fastboot or anything of the sort.
4 I don't think OP is doing security updates for the OP9 on 11 since it supports 12, but the option to go back is always there via MSM conversion through EDL mode on your phone.
DarkPaladinZant said:
1. If you use the local back up option under settings > system settings > back up and reset > local backup then most of your apps get backed up, but the downloaded data will not be saved and you have to log into the accounts on each app. I'm still looking for another way to backup, but I'm hesitant because this method of backup retains my T-Mobile SIM settings after I converted it to Global.
2. I was on OOS 12.41 on a T-Mobile branded OP9, and when I used @craznazn 's MSM conversion tool, it downgraded my phone to Global OOS 11.2.2. I suppose if you wanted to downgrade you could use his tool, or any MSM tool made for a T-Moble version on OOS 11, and it would boot that version, and then you could update to the latest 11.
3. I would suggest root if you have your bootloader and sim unlocked, if not, I would just stay on a stable version of OOS since you wouldn't be able to flash under fastboot or anything of the sort.
4 I don't think OP is doing security updates for the OP9 on 11 since it supports 12, but the option to go back is always there via MSM conversion through EDL mode on your phone.
Click to expand...
Click to collapse
Swift Backup is great for backing up the stuff that you'll want to save, such as Messages, Call Logs, Apps + App Data, some other things. Root is required for the App data backup, otherwise you can still use it for most functions without being rooted, or to enable more backup features without root, you can adb grant SECURE_WRITE to the app. Definitely worth checking out.
AtoZ0to9 said:
Swift Backup is great for backing up the stuff that you'll want to save, such as Messages, Call Logs, Apps + App Data, some other things. Root is required for the App data backup, otherwise you can still use it for most functions without being rooted, or to enable more backup features without root, you can adb grant SECURE_WRITE to the app. Definitely worth checking out.
Click to expand...
Click to collapse
Oh wow yeah I'll definitely have to check it out! I've been testing my OP9 going back and forth from Tmo to Global to find the most reliable way to get there with the modem still intact, as I'm still a couple of days away from getting my unlock token.
Android 12 just dropped for TMobile OnePlus8T. I already want to roll back to 11 but after reading the guides none of them work and I'm assuming it's because you can't do that on a KB2007. But my phone is carrier and bootloader unlocked?
I'm struggling because mine is going to force the update at night, even tho I have automatic updates disabled on developer options. I have been looking for a way to stop it but nothing seems to work, not even the adb command to uninstall/disable the updater package. I don't know what else to do beside turning off the phone every night so it doesn't update itself.
fitrockx said:
I'm struggling because mine is going to force the update at night, even tho I have automatic updates disabled on developer options. I have been looking for a way to stop it but nothing seems to work, not even the adb command to uninstall/disable the updater package. I don't know what else to do beside turning off the phone every night so it doesn't update itself.
Click to expand...
Click to collapse
[Guide] OnePlus 8T EASY ROOT (for all unlocked variants)
DO NOT FOLLOW THIS GUIDE IF YOU HAVE ANDROID 12 Visit this thread for more information ________________________________________________________ CAVEAT I've only tested this on my device running Android 11 (KB2005 / KB05AA), but it should be...
forum.xda-developers.com
Rootk1t said:
[Guide] OnePlus 8T EASY ROOT (for all unlocked variants)
DO NOT FOLLOW THIS GUIDE IF YOU HAVE ANDROID 12 Visit this thread for more information ________________________________________________________ CAVEAT I've only tested this on my device running Android 11 (KB2005 / KB05AA), but it should be...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you for the information. Sadly mine can't be rooted yet. Once I'm able to get the unlock from T-Mobile I'll definitely try that.
Hello,
My initial plan was to switch from Oxygen OS 12 to Lineageos.
As it wasn't possible to go from OOS12 to Lineage Os directly, I downgraded to OOS11.
After installing Lineageos 13, I was not able to get mobile internet connection.
This is why I tried Pixel Experience.
Unfortunately mobile internet connection is still not possible with Pixel Eperience.
It worked with OOS12 but I haven't checked with OOS 11.
My plan was now to check, if mobile network will work again when I go back to OOS12.
But the guides regarding this failed because I don't have the "oem unlock" menu option in Pixel experience. And I am not confident if I'm doing according the right guide.
...I'm kinda stuck now because I feel as I can do nothing w/o oem unlock and I failed to get that option..
Could someone give me a hint how I can:
1) Activate OEM unlock on Pixel Pxperience (Of course only if necessary at all)
2) Get mobile network working (I assume this might be a problem of some not ROM related "Piece of software"?!)
3) Get back to LineageOS with working mobile network
Thanks in advance
One time you do the OEM unlock, this will remain unlocked until you flash the stock rom with MSM option
Yeah, some ROMs hide the OEM unlock option because there is people that try to relock BL with custom ROM and this generally causes a hardbrick.
About get network working, idk if its custom rom issue, since my op7 pro is carrier locked and im unable to unlock it, sometimes custom roms shows me like i have no sim insterted (even though I have a sim put on of course)
So, if its a recurring problem, id suggest to revert to OOS first and try again.
And since you can't unlock bootloader on OOS12 due to some issues that haven't solved, you need to do it on OOS11 or lower and upgrade to OOS12, Two times (some custom ROMS needs to have OOS12 on both partitions)
Also, LineageOS is based on OOS12, the only rom i know is based on OOS11 is YAAP. So, that's might be the issue.
I'm not that kind of expert, but maybe another user can help you better, also, sorry for my english!
Good luck c:
MSM worked for me, thanks for the help. I switched back to OOS 11 successfully. Mobile data was working there, again. After installing LOS20, mobile internet didn't work again.
Did I understand your instruction correctly?
1) LOS20
2) OOS11
3) Unlock
4) OTA to OOS12
5) LOS20
How can I go to OOS12 "two times"?
leueku said:
MSM worked for me, thanks for the help. I switched back to OOS 11 successfully. Mobile data was working there, again. After installing LOS20, mobile internet didn't work again.
Did I understand your instruction correctly?
1) LOS20
2) OOS11
3) Unlock
4) OTA to OOS12
5) LOS20
How can I go to OOS12 "two times"?
Click to expand...
Click to collapse
Basically is MSM stock rom flash first, from here, the steps should be like:
1) Update to OOS11 or stay at OOS10/9 (it depends of the MSM package you found)
2) Bootloader unlock
3) Update to OOS12
4) Use the localupdate.apk found on Oneplus forums to "update" again over OOS12, this option will install OOS12 on the inactive slot, and you will have OOS12 on both slots
5) LOS20
i know you can flash OOS12 by fastboot method, but I don't know the steps to follow in this case, but it is likely that you can get a guide here
It worked! I have now mobile internet with LOS20. Thanks a lot for your help!