I have an International KB2005 OnePlus 8T. I had it working great on official Evolution X, F15 firmware copied to both slots, rooted with Magisk Delta 6, passing SafetyNet, banking apps, streaming apps EXCEPT for Netflix. I turned on Netflix spoof in The Evolver settings but this only let it install, when I launched it it would just hang forever.
I checked my Widevine info with DRM info. At the time I had L1 but an invalid System ID (very long digit, way longer than 5 numbers but I don't remember.) I'm pretty sure that was the issue based on some conversations I had.
Ok so I want to fix my widevine giving it L1 with a valid system ID. So I do the "nuclear" option and msmtool back to OOS 11.0.7.9. msmtool completes successfully, bootloader is locked but now widevine is L3 with System ID 8159.
I don't have any original backup files from the phone, I also didn't try the older msmtool to the earlier OOS release. What is the correct way to not only get L1 widevine with a valid system ID on OOS, but what's the correct procedure to unlock bootloader, install a ROM and still retain L1?
TL;DR: how to get L1 widevine with valid system id on KB2005?
I was on the same page as you. I tried searching everywhere and didn't find about it anywhere. There isn't any way to fix the system id as of now. However there is a workaround to get netflix working, if thats what you are trying to do.
Step 1: MSMtool back to oos 11.0
Step 2: Unlock bootloader. (it changes the system id to 4 digit number which is L1 secrity)
Step 3: Install netflix and other apps that dont work with broken system ID. Log in your account.
Step 4: Update your rom.
System ID breaks but your apps works fine.
AstronxD said:
I was on the same page as you. I tried searching everywhere and didn't find about it anywhere. There isn't any way to fix the system id as of now. However there is a workaround to get netflix working, if thats what you are trying to do.
Step 1: MSMtool back to oos 11.0
Step 2: Unlock bootloader. (it changes the system id to 4 digit number which is L1 secrity)
Step 3: Install netflix and other apps that dont work with broken system ID. Log in your account.
Step 4: Update your rom.
System ID breaks but your apps works fine.
Click to expand...
Click to collapse
So when going from OOS 11.0 to a custom ROM, are you suggesting to dirty flash and not wipe data (I always thought this was a terrible idea)? Or still do a clean flash of the ROM then re-install those apps and it will work?
It is a terrible for some ROM
Dopamin3 said:
So when going from OOS 11.0 to a custom ROM, are you suggesting to dirty flash and not wipe data (I always thought this was a terrible idea)? Or still do a clean flash of the ROM then re-install those apps and it will work?
Click to expand...
Click to collapse
I had tried restoring with titanium backup but the results were same, they dont work. So yeah dirty flash is a terrible idea for some rom while some ROM allow dirty flashing. I have only tested on updating ROM from OOS 11 to OOS 13 and its working.
AstronxD said:
It is a terrible for some ROM
I had tried restoring with titanium backup but the results were same, they dont work. So yeah dirty flash is a terrible idea for some rom while some ROM allow dirty flashing. I have only tested on updating ROM from OOS 11 to OOS 13 and its working.
Click to expand...
Click to collapse
I've never ever ever seen a ROM that doesn't require a wipe when going from stock to the ROM. However once you're on the ROM, you can usually dirty flash updates unless the maintainer specifically says a new build requires a clean flash. Maybe this would work if there was a modified ROM based on OOS.
I appreciate your responses, but OOS 13 is the worst version of Android I've ever tried. I guess my dream of getting the 8T working with an A13 AOSP/LOS based ROM is still dead (with the valid L1 cert, otherwise it works fine).
I'm sticking with Pixels from now on. On every Pixel I've ever messed with (3a XL, 5a 5G RIP mobo, 6a, 7 Pro) I've been able to do anything- unlock the bootloader, try any custom ROM and/or kernel, use a custom recovery, have safetynet passing or failing and the valid L1 widevine cert just persists. Seems like a silly reason to dump OnePlus, but I need that valid L1 cert and I'm not willing to stay on the good, outdated OOS 11 or use the terrible, new OOS 13.
Related
Greetings. After trying Derpfest on my Redmi Note 7 Pro, I decided to switch back to MiUI. I wiped out the entire Custom ROM, then installed Indian version firmware, and then installed the latest MiUI ROM in recovery mode (I prefer Orange Fox). After that, I wanted to relock my bootloader so I got the latest MiUI 11 fastboot ROM and then used MiFlash and used the clean_all_and_lock option. My device relocked it's bootloader, however, it turned out that several things like sensors or Find Device service were not working correctly. It also showed a message "Find device storage corrupted, your device is now unsafe". Looking for solutions, I ended up unlocking the bootloader again, getting back OFox, and installing the persist.img file which I extracted from my fastboot ROM. This fixed the issue with the sensors. But now, I still can't get access to services like Find Device (both from Xiaomi and Google). If I have to avoid the 'Find Device Storage corrupted' error, I have to unlock bootloader. If I have to lock bootloader, I get the error message. What am I supposed to do?
I also have tried older Fastboot ROMs, although they were all MiUI 11. Should I try fastbooting into a MiUI 10 ROM and then get OTA to do everything else? If this is the case, which specific version of MiUI 10 ROM should I flash? I can't remember which version my phone came with. My model number M1901F7S. And also, I've never used Magisk. I didn't really care if I wanted to root or not. Derpfest passed Safetynet pretty nicely. But now I do not wish to root. I don't want Magisk or anything else, I want to secure the phone just as it was before.
EDIT : Turns out that Find Device (from both Google and Xiaomi) are actually working, just in a less effective scale than what I previously used to have (before getting the custom ROM). But yet, can I bring my phone back to the locked bootloader state? I want to secure it completely, just like how it was when it came out of the box. I also cannot install apps like Netflix. I would really like to know how to relock my bootloader.
EDIT 2: I've fixed it. Indeed, I had to flash a stock MiUI 10 ROM. Version 10.0.2 and whatever number ahead worked for me and gave me no problems, and then I simply updated to MiUI 11 using OTA Updates.
However, I do not recommend using MiFlash tool, and instead recommend pasting the ROM files into your platform_tools folder and then running flash_all_lock/flash_all. MiFlash may sometimes glitch and cause problems.
Hello,
I followed a few different guides with different methods attempting to update my Oneplus 8T KB2005 from Oxygen OS 11.0.5.6 to KB2005_11_C.11 it ending up bricking my phone and i had to Fastboot flash TWRP to get the ability to wipe my entire phone loosing all 9000 photos and other data. needless to say the phone is now working but it reverted back to 11.0.5.6 with root still just with no data apps or anything.
I would prefer to update to Oxygen OS 12 and retain root. Can someone please direct me to the best method out thats using stable build not something thats gonna potentially be causing me to send CLI commands in fastboot for next 2 hours...
Reasons for updating are the buggy VO-wifi VO-LTE and the not usable 5G.
Thanks
acidreian said:
Hello,
I followed a few different guides with different methods attempting to update my Oneplus 8T KB2005 from Oxygen OS 11.0.5.6 to KB2005_11_C.11 it ending up bricking my phone and i had to Fastboot flash TWRP to get the ability to wipe my entire phone loosing all 9000 photos and other data. needless to say the phone is now working but it reverted back to 11.0.5.6 with root still just with no data apps or anything.
I would prefer to update to Oxygen OS 12 and retain root. Can someone please direct me to the best method out thats using stable build not something thats gonna potentially be causing me to send CLI commands in fastboot for next 2 hours...
Reasons for updating are the buggy VO-wifi VO-LTE and the not usable 5G.
Thanks
Click to expand...
Click to collapse
[GUIDE] Root and keeping root options
Update 230526: Correct numbering of "B.1.1 Simple" to "B.1.2 Simple", use "OOS 13+" instead of "OOS 13" as OOS 13.1 is now available A. First time rooting This process is common across all options A.1 Flashing Magisk patched boot image There...
forum.xda-developers.com
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.
Booted up a oneplus 9 pro boot image, it fixed my phone being stuck in fastboot because I didn't have stock image.
Now updates don't work.
Oneplus 9 T-Mobile, stock rom, pro boot image, unlocked bootloader, unlocked sim - Any help would be appreciated.
Was thinking MSM tool but unsure what one to use.
I'm in a similar situation but I can't get out of fastboot. What OnePlus Pro boot image did you flash to your phone and what firmware are you on?
I gave the pro boot.img a try and it worked!
I grabbed it from this post: https://forum.xda-developers.com/t/...t-keep-root-oos-12-c-48.4252373/post-87096189
I want to back a few things up before tinkering anymore but will report back on how I try to fix it.
Thinking ahead, did Oxygen Updater not allow you to change your device back to a OnePlus 9, download the software update, flash and revert back?
Glad you could get your phone fixed...
I wish my system updates worked though lol ugh
Harley1979 said:
Glad you could get your phone fixed...
I wish my system updates worked though lol ugh
Click to expand...
Click to collapse
Are you using Oxygen Updater or the native update tool?
If the latter I would try the former.
Oxygen Updater - Apps on Google Play
Skip staged rollout queues and update your OnePlus device ASAP!
play.google.com
No I'm on a t-mobile oneplus 9 with android 12.
Soooo have you tried Oxygen Updater?
No it doesn't work for my version of this phone.
Thanks though
I wish I had a copy of the original boot image of my phone, T-Mobile variant boot.imge I'm guessing and for the non-pro version. I'm assuming that may fix my issue with the T-Mobile system updates and my incompatibility app issues with Google Play...
Harley1979 said:
I wish I had a copy of the original boot image of my phone, T-Mobile variant boot.imge I'm guessing and for the non-pro version. I'm assuming that may fix my issue with the T-Mobile system updates and my incompatibility app issues with Google Play...
Click to expand...
Click to collapse
If your bootloader is unlocked and Google Play is telling you that your device is not supported, it's because of the unlocked bootloader most likely. Are you successfully passing both basic and CTS safetynet profiles?
Not sure sry... Only few apps are incompatible.
This is what the OnePlus updater shows.
Harley1979 said:
Not sure sry... Only few apps are incompatible.
This is what the OnePlus updater shows.
Click to expand...
Click to collapse
I think your problem is that your bootloader is unlocked and it needs to be locked in order to pass safeynet. More and more apps are not allowing for detected unlocked bootloaders in which makes safetynet fail.
Wish I knew how to relock it... Little reluctant to use a random site's information... Xda probably has information on relocking it, wish I had a link to a good post.
Could it possibly brick my phone if I'm using a pro boot image an try to lock bootloader?
Any advice or help would be much appreciated thanks for your time.
I will follow-up more later as I'm walking out the door. I'm not convinced that we are on a different or should I say, incompatible boot.img. When I get home I need to do some research to see what is actually different in the boot.img when being compared each other (C.61 boot.img on OP9 and OP9 Pro).
Back history for anyone following along... I was unlocked, rooted, Google Play certified and on C.48. I upgraded via OTA, no reboot and chose an inactive slot. It did not work and soft bricked slot a. I lost root, was on C.48 still but on slot B. I successfully upgraded to C.61 but didn't have root. I could not find a good boot.img or patched_boot.img. I tried a stock OP9 Pro image and that got me working. That same user provided a patch img too so I tried that and obtained root as well.
Soooo what is the difference between the boot images on C.61 pro and non-pro OP9 models?
Stay tuned....!
Thanks I'll keep checking back on this
Unfortunately the difference is that the pro version is available to tinker with and the non pro version isn't. Sorry to state the obvious.
My phone so far is working fine on the OP9 Pro kernel. C.61 is rooted and Google Play is certified. All my previous Magisk config is there as well and modules. I'm not sure what the difference between the kernels are at this point but also not a kernel expert either.
Once the next full release comes out for OP9, I will swap it out.
@Harley1979 I got your PM and will follow-up with you there.
I have a stock GM1917, running OSS 11.0.9.1.GM21AA. I've never unlocked bootloader, ironically because I didn't want to lose L1. I just download DRM Info and it reports Widevine L3.
What's up with that, and is there anything I can do about it? I'm thinking about rooting now that I can see that you can retain L1.
Try flashing latest OOS 11 image from MSM tool. Internet says it fixes the L3 issue.
Note:
1) Flashing ROM from MSM tool will wipe data so backup first.
2) The image necessarily needs to be Oxygen OS 11. Version 10 won't fix anything.
I have this issue as well. But I am living with it as I don't use Netflix stuffs. Let the community know if it fixes.
MSM flashing didn't help. Tried multiple times/versions, including before ever unlocking the bootloader for the first time. I think some of us just have a bad device that can't be fixed by MSM.
I have the same problem on my 7 pro (GM1911), Did anyone found any solution to this issue ?