NOT FOR OOS, If you do this on TMO OOS you will lose connectivity.
So Lineage and all other AOSP based ROMs does not enable dual SIM for kebabt due to the T-Mobile modem having a hissy fit. However, you can flash the US/Global modem, retain all your 5G goodness, and enable dual-SIM as follows:
Download the Global modem: https://www.androidfilehost.com/?fid=2188818919693783632
Download the dsds magisk module: https://www.androidfilehost.com/?fid=2188818919693783509
Flash the Global modem:
Code:
fastboot flash modem modem.img
Install the dsds magisk module
Make sure you follow all instructions in the lineage installation https://wiki.lineageos.org/devices/kebab, that will be my first question if you have any issues.
As always, thanks @LuK1337 and LineageOS Team
Well I can confirm this does NOT work if you're still on tmo firmware...
All it did for me was give no service and I had to go flash my original modem.img
spart0n said:
Well I can confirm this does NOT work if you're still on tmo firmware...
All it did for me was give no service and I had to go flash my original modem.img
Click to expand...
Click to collapse
Well... I did say it's for Lineage/AOSP... But I'll make it clear in the OP
craznazn said:
Well... I did say it's for Lineage/AOSP...
Click to expand...
Click to collapse
Figured I'd try it out anyway
hello can you help me I have my umidigi 2020 bison that does not detect the SIM 2 by accident I moved that option and I can not activate again to the same opinion
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
by: Santosh Yadav
-Using ADB + root-
su
setprop persist.vendor.radio.multisim_switch_support true
setprop persist.radio.multisim.config dsds
REBOOT
craznazn said:
Well... I did say it's for Lineage/AOSP... But I'll make it clear in the OP
Click to expand...
Click to collapse
Hello friend ! I use 8T TMO, after upgrading to CBT 12, my device only accepts 1 sim, because the imei is duplicated, sim 2 can't be used, is there any way to fix it?
Not sure, I haven’t upgraded to 12 yet to test
craznazn said:
Not sure, I haven’t upgraded to 12 yet to test
Click to expand...
Click to collapse
i am using TMO carrier version , now i think on ColorOS android 11 will get enough signal , because i have experienced CBT OOS 12 on 8T , it also has the same error with COS , i flash colorOS 11 ROM with msmtool but since my device is TMO , can you make a conversion?
Diangucmau said:
嘿，朋友！我使用8T TMO，升级到CBT 12后，我的设备只接受1张SIM卡，因为imei是重复的，sim 2无法使用，有什么办法可以修复它吗？
Click to expand...
Click to collapse
Diangucmau said:
嘿，朋友！我使用8T TMO，升级到CBT 12后，我的设备只接受1张SIM卡，因为imei是重复的，sim 2无法使用，有什么办法可以修复它吗？
Click to expand...
Click to collapse
我也处于这种情况。你解决了吗
David Ortega said:
hello can you help me I have my umidigi 2020 bison that does not detect the SIM 2 by accident I moved that option and I can not activate again to the same opinionView attachment 5415687
Click to expand...
Click to collapse
Someone please give a reply on this
Crescendo Xenomorph said:
by: Santosh Yadav
-Using ADB + root-
su
setprop persist.vendor.radio.multisim_switch_support true
setprop persist.radio.multisim.config dsds
REBOOT
Click to expand...
Click to collapse
THANK YOU VERY MUCH
This worked on my OnePlus 8t kb2007 using nameless 13
Crescendo Xenomorph said:
by: Santosh Yadav
-Using ADB + root-
su
setprop persist.vendor.radio.multisim_switch_support true
setprop persist.radio.multisim.config dsds
REBOOT
Click to expand...
Click to collapse
My 8T bootloader is locked, and unrooted. Is there any way to do this without needed to unlock bootloader (and therefore wipe my device)?
Thanks!
raven911 said:
My 8T bootloader is locked, and unrooted. Is there any way to do this without needed to unlock bootloader (and therefore wipe my device)?
Thanks!
Click to expand...
Click to collapse
I think no. To flash abl.img from beta OOS you need unlocked bootloader, and for changing props you need root permissions.
But i read that you can lock bootloader straight after flashing one from OOS beta, though i didn't test it myself.
mofinheim said:
THANK YOU VERY MUCH
This worked on my OnePlus 8t kb2007 using nameless 13
Click to expand...
Click to collapse
Are these commands to enable DSDS without flashing modem and installing magisk module?
mofinheim said:
THANK YOU VERY MUCH
This worked on my OnePlus 8t kb2007 using nameless 13
Click to expand...
Click to collapse
Can you detail how that's done? I tried pulling the build.prop and the command says it's successful I can't seem to find the file in my windows laptop. Thanks!
just4sc said:
Can you detail how that's done? I tried pulling the build.prop and the command says it's successful I can't seem to find the file in my windows laptop. Thanks!
Click to expand...
Click to collapse
NM. I was able to do it via ADB shell and it looks like it's working. Just wondering if it sticks or do I have to it every time. If so, I'll need to find out how to edit build.prop. Try doing so via ADB but can't seem to pull the file to local. Says it's sent but I don't see the file locally.
I'm on LineageOS20.
I just ran these command and didn't run steps in the first post.
su
setprop persist.vendor.radio.multisim_switch_support true
setprop persist.radio.multisim.config dsds
Click to expand...
Click to collapse
I can see both SIMs but the 2nd SIM slot does not accept/send any sms. Both slots share the same IMEI.
What's the possible issue here?
urover said:
I'm on LineageOS20.
What's the possible issue here?
Click to expand...
Click to collapse
It depens on what base OOS ROM you have installed.
If OOS13, try to flash abl.img from OOS F.10 beta.
Rootk1t said:
It depens on what base OOS ROM you have installed.
If OOS13, try to flash abl.img from OOS F.10 beta.
Click to expand...
Click to collapse
Thanks. Base ROM was OOS13-EU.
I just went back to OOS13-EU since I didn't like Lineage and Evolution-X. Got dual-SIM working by flashing the firmware flasher from another thread.. which flashes abl.img like you said.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As requested, this is my build of the Android Marshmallow for the Xperia Z2.
This ROM was build after this instructions.
Download
Android File Host
What you need to know:
- This ROM does not have an recovery at the moment.
- This ROM requires an unlocked bootloader.
- This ROM is not rooted.
- This is pure AOSP, nothing more.
FAQ:
Where are my Google Apps?
There are no Google Apps included in this ROM.
Click to expand...
Click to collapse
Why is there no recovery so far?
Because this is the pure AOSP code so far.
Click to expand...
Click to collapse
Bugs:
- SD card is not accessible
- No Mobile Connections (does not detect SIM card)
Installation Instructions:
- Download .zip file & unpack (don't flash)
- flash different images via fastboot (DANGER: flashing userdata.img will erase the complete internal storage)
Code:
fastboot flash userdata userdata.img
Code:
fastboot flash system system.img
Code:
fastboot flash boot boot.img
- Reboot
Code:
fastboot reboot
This ROM goes straight from my PC online. I did not try this at home. Please report if something does not work properly, I will respond and try to help you as fast as I can.
XDA:DevDB Information
AOSP, ROM for the Sony Xperia Z2
Contributors
_heisenberg, _heisenberg
Source Code: https://android.googlesource.com/
ROM OS Version: 6.0.x Marshmallow
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP
Version Information
Status: Testing
Created 2015-10-17
Last Updated 2015-10-17
Reserved
Also Reserved
_heisenberg said:
Also Reserved
Click to expand...
Click to collapse
Finally, thank you so much for the first aosp ROM
I can not get contact to a moderator, if anyone could move this thread to Xperia Z2/Android Development, this would be nice!
Actually, the pure AOSP builds have root rights, they only work via terminal emulator or adb shell. I managed to get Gapps and SuperSU working on my build by temporarily flashing CM12.1 boot.img to get to the recovery and flashing them. But it isn't exactly usable, as the Google config screen is constantly getting FC'd. Well, that's Sony for you .
mario972 said:
Actually, the pure AOSP builds have root rights, they only work via terminal emulator or adb shell. I managed to get Gapps and SuperSU working on my build by temporarily flashing CM12.1 boot.img to get to the recovery and flashing them. But it isn't exactly usable, as the Google config screen is constantly getting FC'd. Well, that's Sony for you .
Click to expand...
Click to collapse
Yeah you could try that too here, do you use Marshmallow as a daily driver?
_heisenberg said:
Yeah you could try that too here, do you use Marshmallow as a daily driver?
Click to expand...
Click to collapse
Nope, I'd probably do but there are two major problems - the Gapps FC's and the delayed lockscreen. And I had to compile it TWICE, making the mistake of typing the NUMBER in and not the NAME, I've been compiling the generic version for almost 8 hours. So yeah, I'm waiting for Sony's Marshmallow or CM13.
mario972 said:
Nope, I'd probably do but there are two major problems - the Gapps FC's and the delayed lockscreen. And I had to compile it TWICE, making the mistake of typing the NUMBER in and not the NAME, I've been compiling the generic version for almost 8 hours. So yeah, I'm waiting for Sony's Marshmallow or CM13.
Click to expand...
Click to collapse
You mean typing the number at 'lunch'? I also did that...
_heisenberg said:
You mean typing the number at 'lunch'? I also did that...
Click to expand...
Click to collapse
Enter the following commands:
source build/envsetup.sh && lunch
When prompted, pick the number corresponding to your device in the list displayed and press enter.
Click to expand...
Click to collapse
Well, that's Sony for you.
mario972 said:
Well, that's Sony for you.
Click to expand...
Click to collapse
Lol what do you mean? xD
_heisenberg said:
Lol what do you mean? xD
Click to expand...
Click to collapse
Well, Sony's build instructions clearly stated to
When prompted, pick the number
Click to expand...
Click to collapse
Why is this marked as stable? AFAIK camera and other things aren't working at all?
nexuspur said:
Why is this marked as stable? AFAIK camera and other things aren't working at all?
Click to expand...
Click to collapse
As I said, I did not test it. Please test and report, I will change it if it's not correct.
It must be Testing because kernel 3.10 is warned highly experimental on fxpblog (fxp is a part of Sony Developer Program)
its stable! no bugs?
some screenshot?
RyTekk said:
It must be Testing because kernel 3.10 is warned highly experimental on fxpblog (fxp is a part of Sony Developer Program)
Click to expand...
Click to collapse
Changed to testing, thanks for the information.
Okay, so here is my Impression with this ROM after a first use:
- SIM does not work for me (no mobileconnection in general)
- Wifi does work
- SD card does not work
- Camera was not tested -> could not download an app due to playstore missing and SD not working properly
Any progress?
Hi, can anyone confirm the oreo update appeared on FF for European version?
Was-lx1c432b321-log (8.0.0.321)
If yes, is it for p10 lite single sim or dual sim?
Thanks
I'm downloading it right now.
I noticed that it contains the main update package and the secondary ones that is supposed to work with both ds and ss versions
Anyway i think that is Oreo but maybe a beta?
Ra2rd said:
I'm downloading it right now.
I noticed that it contains the main update package and the secondary ones that is supposed to work with both ds and ss versions
Anyway i think that is Oreo but maybe a beta?
Click to expand...
Click to collapse
How did it go anything new ?
'nuff said
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
西村大一 said:
'nuff said
Click to expand...
Click to collapse
How do u update it. I try trought DNS from FF but it gives me error that it's not approved
西村大一 said:
'nuff said
Click to expand...
Click to collapse
Can you run the "getprop ro.treble.enabled" command in terminal (or ADB if you prefer)? Would be nice to see if it's supported.
With skill. Find it yourself. There is a way to force install ANY update. For free. But you have to have some brain to first find it, to be sure that you have, again, enough brain to not brick your device. I will not link anything. Until you acknowledge you will do AS INSTRUCTED, NO OTHER STEPS.
---------- Post added at 23:04 ---------- Previous post was at 23:02 ----------
Trixanity said:
Can you run the "getprop ro.treble.enabled" command in terminal (or ADB if you prefer)? Would be nice to see if it's supported.
Click to expand...
Click to collapse
Code:
HWWAS-H:/ $ getprop ro.treble.enabled
true
HWWAS-H:/ $
this is what the device says
西村大一 said:
this is what the device says
Click to expand...
Click to collapse
Thanks.
Nice.
How does it run on the P10 lite ?
Any noticeable diffrence ?
AymZ12 said:
How does it run on the P10 lite ?
Any noticeable diffrence ?
Click to expand...
Click to collapse
There is the UI smoothness because it is a fresh install, Project Treble is enabled, and all around it is more polished than EMUI 5.
西村大一 said:
There is the UI smoothness because it is a fresh install, Project Treble is enabled, and all around it is more polished than EMUI 5.
Click to expand...
Click to collapse
Nice
Thanks bro
西村大一 said:
There is the UI smoothness because it is a fresh install, Project Treble is enabled, and all around it is more polished than EMUI 5.
Click to expand...
Click to collapse
いいね！thanks for info
there is no compatible twrp recovery for this rom. can't root
Do you know if Oreo has released for WAS-LX3605B?
西村大一 said:
With skill. Find it yourself. There is a way to force install ANY update. For free. But you have to have some brain to first find it, to be sure that you have, again, enough brain to not brick your device. I will not link anything. Until you acknowledge you will do AS INSTRUCTED, NO OTHER STEPS.
---------- Post added at 23:04 ---------- Previous post was at 23:02 ----------
Code:
HWWAS-H:/ $ getprop ro.treble.enabled
true
HWWAS-H:/ $
this is what the device says
Click to expand...
Click to collapse
1. Unlock bootloader
2. Flash nocheck recovery or something like that.
3. put the update.app into a folder on the sd card.
4. Boot into eRecovery and apply the update
Right ? I only had HTC and Nexus devices so I don't really know how the update process works on Huawei devices with 2 recovery's
Eurofighter_ty said:
1. Unlock bootloader
2. Flash nocheck recovery or something like that.
3. put the update.app into a folder on the sd card.
4. Boot into eRecovery and apply the update
Right ? I only had HTC and Nexus devices so I don't really know how the update process works on Huawei devices with 2 recovery's
Click to expand...
Click to collapse
Sort of. But it's pretty difficult to do it yourself. There is a script out here that will do that for you automagically.
西村大一 said:
Sort of. But it's pretty difficult to do it yourself. There is a script out here that will do that for you automagically.
Click to expand...
Click to collapse
This one ?
https://forum.xda-developers.com/p10-lite/development/hwota-huawei-p10-lite-t3776186
Eurofighter_ty said:
This one ?
https://forum.xda-developers.com/p10-lite/development/hwota-huawei-p10-lite-t3776186
Click to expand...
Click to collapse
Bingo.
西村大一 said:
Bingo.
Click to expand...
Click to collapse
Can I lock the bootloader ? TWRP is removed after I ran the script ?
Eurofighter_ty said:
Can I lock the bootloader ? TWRP is removed after I ran the script ?
Click to expand...
Click to collapse
Gonna test the bootloader relock, but the TWRP is indeed removed after. But be careful, that script can't revert the update since the Oreo update changes the partitions' structure....
geeklynx said:
Gonna test the bootloader relock, but the TWRP is indeed removed after. But be careful, that script can't revert the update since the Oreo update changes the partitions' structure....
Click to expand...
Click to collapse
Yep, it is removed. I ran the script and everything works great even VoLTE for Orange Romania !
I don't really want to downgrade because it's pretty stable for me
As we know after installing logkit and engineermode apks on oxygenos somehow we can enable volte and vowifi on oxygenos. But it is much easier on coloros.
Just flash voenabler magisk module and voila !
Proof
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tested on KB2003 / Turkey / Vodafone and Turkcell
Voenabler Magisk Module Download
How to root ?
mahmutuslu34 said:
How to root ?
Click to expand...
Click to collapse
Patch boot.img and flash with stock vbmeta
Pls upload patch boot ?
mahmutuslu34 said:
Pls upload patch boot ?
Click to expand...
Click to collapse
You can extract the boot.img from the MSM .ops file, and then patch it with magisk.
JuliusGudni said:
You can extract the boot.img from the MSM .ops file, and then patch it with magisk.
Click to expand...
Click to collapse
how will i extract it from MSM?
enderguzel said:
how will i extract it from MSM?
Click to expand...
Click to collapse
GitHub - bkerler/oppo_decrypt: Oppo .ofp Firmware decrypter and oneplus .ops de-/encrypter
Oppo .ofp Firmware decrypter and oneplus .ops de-/encrypter - GitHub - bkerler/oppo_decrypt: Oppo .ofp Firmware decrypter and oneplus .ops de-/encrypter
github.com
Phreaker8 said:
As we know after installing logkit and engineermode apks on oxygenos somehow we can enable volte and vowifi on oxygenos. But it is much easier on coloros.
Just flash voenabler magisk module and voila !
Proof
View attachment 5327773
Tested on KB2003 / Turkey / Vodafone and Turkcell
Voenabler Magisk Module Download
Click to expand...
Click to collapse
How to enable whitnot root?
Biraz daha yardımcı olsanız bizde yapalım
karel23 said:
Biraz daha yardımcı olsanız bizde yapalım
Click to expand...
Click to collapse
Please post in English on XDA next time. You can post in your native language, but English translation is needed as well. Thanks.
Translation:
If you could help a little more, we'll do it.
Click to expand...
Click to collapse
Doesn't work for me. Just keep changing into 3g/H+ when I make calls.
Confirmed working with color is 11 OnePlus 8 , thanks
MsuatafaKhatab said:
Confirmed working with color is 11 OnePlus 8 , thanks
Click to expand...
Click to collapse
How did you root ColorOS on Oneplus 8? Itried but not working
AxelAG1213 said:
How did you root ColorOS on Oneplus 8? Itried but not working
Click to expand...
Click to collapse
[Guide] Root OnePlus 8T ColorOS 11
This guide should work with all variants that were converted from OxygenOS to ColorOS (Spoofed as OnePlus KB2000) on Build Number KB2000_11_C.01, but I AM NOT RESPONSIBLE FOR ANY DATA LOSS, DAMAGE, OR BROKEN DEVICES, OR ANY DAMAGE THAT OCCURS BY...
forum.xda-developers.com
Does this same method apply on ColorOS12?
Phreaker8 said:
As we know after installing logkit and engineermode apks on oxygenos somehow we can enable volte and vowifi on oxygenos. But it is much easier on coloros.
Just flash voenabler magisk module and voila !
Proof
View attachment 5327773
Tested on KB2003 / Turkey / Vodafone and Turkcell
Voenabler Magisk Module Download
Click to expand...
Click to collapse
Hello friend ! I use 8T TMO, after upgrading to CBT 12, my device only accepts 1 sim, because the imei is duplicated, sim 2 can't be used, is there any way to fix it?
Diangucmau said:
Hello friend ! I use 8T TMO, after upgrading to CBT 12, my device only accepts 1 sim, because the imei is duplicated, sim 2 can't be used, is there any way to fix it?
Click to expand...
Click to collapse
You flashed the old cbt . I don't think cbt 12 is out . It doesn't make sense even both imei were same . I had the same problem my imei was not same only sim 1 is working on sim 2 it display nothing . No sim .then I went back to android 11 and today I flashed cbt7 on my OnePlus 8 pro . Now both sims are working fine
Diangucmau said:
Hello friend ! I use 8T TMO, after upgrading to CBT 12, my device only accepts 1 sim, because the imei is duplicated, sim 2 can't be used, is there any way to fix it?
Click to expand...
Click to collapse
I had same issue second imei was displaying null
Any way to do it without root? I don't want root on my mobile
OxygenOs 12 CBT for kb2001 - working on all variants (you install at your own risk)
File on MEGA
mega.nz
maciek84325 said:
OxygenOs 12 CBT for kb2001 - working on all variants (you install at your own risk)
File on MEGA
mega.nz
Click to expand...
Click to collapse
Just a heads up. This will be removed as it violates the OnePlus tos
ElliSkyline said:
Just a heads up. This will be removed as it violates the OnePlus tos
Click to expand...
Click to collapse
Why? Please contact me directly if you can point this out exactly how.
Timmmmaaahh! said:
Why? Please contact me directly if you can point this out exactly how.
Click to expand...
Click to collapse
according to the moderator here
[CLOSED]OnePlus 8t oxygen os 12 cbt
Download link: I have removed it due to the request of OnePlus staff and I will respect that decision. Incase your still on this I suggest you use msm to revert back to 11 since hard bricks are possible on this build
forum.xda-developers.com
Read the last few post
ElliSkyline said:
according to the moderator here
[CLOSED]OnePlus 8t oxygen os 12 cbt
Download link: I have removed it due to the request of OnePlus staff and I will respect that decision. Incase your still on this I suggest you use msm to revert back to 11 since hard bricks are possible on this build
forum.xda-developers.com
Read the last few post
Click to expand...
Click to collapse
Read them yourself, the esteemed moderator didn't take a stance and locked at OP's request because OP *thinks* he broke tos. I don't see any violation on our side.
Okay cool!
How to install from OOS11? Just local upgrade in oxygen system updater?
And how to persist root? -> OTA Method in Magisk installer?
Thanks for your guidance.
maciek84325 said:
OxygenOs 12 CBT for kb2001 - working on all variants (you install at your own risk)
File on MEGA
mega.nz
Click to expand...
Click to collapse
It isn't working on all variants. On most variants you will be without network connectivity.
i have kb2003. Will I lose my network?
Laapander said:
i have kb2003. Will I lose my network?
Click to expand...
Click to collapse
on kb2003 all working great for some devices. But I don't know why it works on some devices and not on the rest.. You must try to see it will work for your device..
Probably that's the reason:
"It's not cause it was designed for indian models (but it was) some OnePlus 8t have ddr5 ram instead of ddr4 and the ones with ddr5 are the ones who will most likely have network issues."
If you want to back stable rom, use this tool (https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/)
Raza Qadri said:
It isn't working on all variants. On most variants you will be without network connectivity.
Click to expand...
Click to collapse
In fact, sorry for my mistake. Probably the type of RAM is to blame
I have ddr5 variant. So I think I will wait for something more sure.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Laapander said:
I have ddr5 variant. So I think I will wait for something more sure.
Click to expand...
Click to collapse
I also have ddr5 variant. (I check - "adb shell getprop ro.boot.ddr_type" and answer is 1)
If I have time during the weekend, I will backup, downgrade to OOS 11.0.7.10 (because 11.0.12.12 is newer than CBT and updater shows error) and install CBT. Then I will test and write comment if ewerything works
FYI, this OOS 12 payload.bin has both (xbl, xbl_config) and (xbl_lp5, xbl_config_lp5) images so it caters for both ddr4 and ddr5 - just like an OOS 11 payload.bin does.
I installed OOS 12 CBT - WITHOUT doing a factory reset - using the latest TWRP (3.6.0_11-3) and it worked flawlessly.
All my installed apps are present and everything looks fine. There are only two significant issues I have found so far:
1. The fingerprint reader doesn't work (maybe because I didn't do a clean install). Edit: after a reset (which does a "format data") FP works
2. I cannot boot back into TWRP unless I switch slots. But since this thread is not about TWRP, I wont talk about it here any more.
Edit:
3. I've not been able to get adb to work.
I can make phone calls, send SMS, connect to the internet using both WIFI and mobile data. And my phone is a DDR5 device.
But face unlock works brilliantly.
BillGoss said:
I installed OOS 12 CBT - WITHOUT doing a factory reset - using the latest TWRP (3.6.0_11-3) and it worked flawlessly.
All my installed apps are present and everything looks fine. There are only two significant issues I have found so far:
1. The fingerprint reader doesn't work (maybe because I didn't do a clean install).
2. I cannot boot back into TWRP unless I switch slots. But since this thread is not about TWRP, I wont talk about it here any more.
I can make phone calls, send SMS, connect to the internet using both WIFI and mobile data. And my phone is a DDR5 device.
Click to expand...
Click to collapse
Did you installed in top of newest OOS 11?
Laapander said:
Did you installed in top of newest OOS 11?
Click to expand...
Click to collapse
Yup!
I flashed this beta in TWRP and for a brief look and testing I haven't found any bugs ATM
Seems pretty smooth
I'm really stupid..
Why I didn't think to use twrp and them I do not need to delete data and downgrade to older OOS.
I can even backup in twrp and then if I don't like it, restore the backup and the device will be restored to the state before cbt installation..
This is the best option I think. if the system works fine for me then I will do a clean install without twrp
1) After rooting your phone, download the Qualcomm driver from below:
2) Run cmd here in Minimal ADB after install and type adb devices and enter, make sure that you can see your device's adb number
4)Type adb shell then press enter
5)Type su
6) Type setprop sys.usb.config diag,serial_cdev,rmnet,adb then press enter
7)Reboot your phone.
8) Your volte should be working now.
Sorry, but no Work for me. error on item 5
[email protected] said:
Sorry, but no Work for me. error on item 5
Click to expand...
Click to collapse
The problem i see here:
"setprop" is an android cli program and it doesn't exists on PC
It change android system props and basically needs root access to run
@kennethyha please explain how to run "setprop" when the phone is in EDL ?!
Sorry. Just checked back the steps I did. Root is indeed needed.
Just simply flash this module in Magisk ( ofc Root is needed )....
kennethyha said:
Sorry. Just checked back the steps I did. Root is indeed needed.
Click to expand...
Click to collapse
Yes. I have Root my device
LinhBT said:
Just simply flash this module in Magisk ( ofc Root is needed )....
Click to expand...
Click to collapse
Thank you very much... It works with WindTre (Italy)
[email protected] said:
Yes. I have Root my device
Click to expand...
Click to collapse
Did you manage to get it work using my discovered method?
Sting1971 said:
Thank you very much... It works with WindTre (Italy
Click to expand...
Click to collapse
Yes, but first I used Module un Magisk
Every Update I download using the Oxygen Updater App is giving an Error - "Verification Failed"
How can I fix this ?
HMBR said:
Every Update I download using the Oxygen Updater App is giving an Error - "Verification Failed"
How can I fix this ?
Click to expand...
Click to collapse
This is the 3rd or 4th post of yours that I've seen in different threads saying the exact same thing.
The XDA forum rules (#5) explicitly say to stay on topic and only post once.
📚 XDA Developers Forum Rules 📚
XDA-Developers FORUM RULES List of Forum Moderators, click HERE Delete Your XDA Account HERE 1. Search before posting. Use one of our search functions before posting or creating a new thread. Whether you have a question or just something new...
forum.xda-developers.com
HMBR said:
Every Update I download using the Oxygen Updater App is giving an Error - "Verification Failed"
How can I fix this ?
Click to expand...
Click to collapse
Did you check if the firmware target is the same as your phone?
kennethyha said:
Did you check if the firmware target is the same as your phone?
Click to expand...
Click to collapse
The Firmware is the same as the Target Phone - the Current Firmware is
KB2003_11_C.20
Did you confirm that your package is OnePlus 8T EU C.33 or the latest one now which is C.35?
The name of the file is C.33 and C.35 - Is there another way of confirming the Package ?
This is the latest firmware
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
kennethyha said:
This is the latest firmwareView attachment 5720417
Click to expand...
Click to collapse
the second sim work whith you after update
amine tenes said:
the second sim work whith you after update
Click to expand...
Click to collapse
I don't use second sim so I do not really know
amine tenes said:
the second sim work whith you after update
Click to expand...
Click to collapse
Yes, both sims work o C.35.
Thanks for the Magisk module guys, everything works now