hi to all:
my phone have a camera problem, some parts are fuzzy
i'm going to return to gearbest under warranty, but i have a problem, the phone comes with a fake rom 8.0.10.0.0, i download oficial global stabale 8.0.3.0, put it on internal memory and update with updater program
and the fuzzy camera is still, i try with other camera apps and same problem
now, i have to restore to original rom because in gearbeset page says:
This Android/Windows device is designed to function specifically with the current Android/Windows OS installed on it. Any alterations such as upgrades, modding with custom ROMs, rooting or flashing the Android device with other firmware will automatically void the device's warranty.
i have restored the phone and the rom is the global stable 8.0.3.0, and i need to restore to 8.0.10.0.0
please, help
thanks in advance
blog.geekbuying.com index.php 2016 11 05 xiaomi-mi-5s-qualcomm-snapdragon-821-miui-8-android-6-0-smartphone-firmware-212277-161105
add slash
thanks!!!
downloaded and extracted, but now i don't know what i have to do ....
litlle guide step by step???
thanks in advance
alexilou said:
thanks!!!
downloaded and extracted, but now i don't know what i have to do ....
litlle guide step by step???
thanks in advance
Click to expand...
Click to collapse
I don't even know what in archive... I took it from other forum, but it should work. Can you send me a screenshot of file list that you unpacked?
Here's what to do to flash that ROM:
You must have an unlocked bootloader first.
1. Enter fastboot mode
2. Run the flash_all.bat
3. Wait until done, the phone will restart.
(I reckon that you can use MiFlash to do this too, but ¯\_(ツ)_/¯ )
awaaas said:
Here's what to do to flash that ROM:
You must have an unlocked bootloader first.
1. Enter fastboot mode
2. Run the flash_all.bat
3. Wait until done, the phone will restart.
(I reckon that you can use MiFlash to do this too, but ¯\_(ツ)_/¯ )
Click to expand...
Click to collapse
But we don't know what in archive... If there another zip?) For recovery?
Ok, If you have few .img files, one folder and 2 or 3 .bat files - you have ROM pack for fastboot. You should activate fadtboot mode on phone ( turn off, volume down+power or volume up+power, I don't remember ). After that launch Mi Flash, connect phone in this mode, after that press refresh, phone should appear in program's window. Next - find folder with unpacked ROM through Mi Flash, choose variant of flash ( bottom right corner, I recommend flash all and lock for your variant ). Wait until the end ( usually 2-5 minutes ). Done! Don't forget to press thanks button if I helped you.
Is the page u bought from says the Rom is a custom one? If not it's their problem not yours, as the item is not as described, plus he has malware, so contact paypal, they will help u
BlackJetCat said:
But we don't know what in archive... If there another zip?) For recovery?
Ok, If you have few .img files, one folder and 2 or 3 .bat files - you have ROM pack for fastboot. You should activate fadtboot mode on phone ( turn off, volume down+power or volume up+power, I don't remember ). After that launch Mi Flash, connect phone in this mode, after that press refresh, phone should appear in program's window. Next - find folder with unpacked ROM through Mi Flash, choose variant of flash ( bottom right corner, I recommend flash all and lock for your variant ). Wait until the end ( usually 2-5 minutes ). Done! Don't forget to press thanks button if I helped you.
Click to expand...
Click to collapse
Here is what inside the archive:
Code:
Xiaomi Mi 5S Qualcomm Snapdragon 821 MIUI 8 Android 6.0 Smartphone Firmware 212277 161104.rar
│ flash_all.bat
│
└───images
adspso.bin
boot.img
BTFM.bin
cache.img
cmnlib.mbn
cmnlib64.mbn
crclist.txt
cust.img
devcfg.mbn
devinfo.img
dummy.img
emmc_appsboot.mbn
Gboot.img
gpt_backup0.bin
gpt_backup1.bin
gpt_backup2.bin
gpt_backup3.bin
gpt_backup4.bin
gpt_backup5.bin
gpt_both0.bin
gpt_both1.bin
gpt_both2.bin
gpt_both3.bin
gpt_both4.bin
gpt_both5.bin
gpt_empty0.bin
gpt_empty1.bin
gpt_empty2.bin
gpt_empty3.bin
gpt_empty4.bin
gpt_empty5.bin
gpt_main0.bin
gpt_main1.bin
gpt_main2.bin
gpt_main3.bin
gpt_main4.bin
gpt_main5.bin
hyp.mbn
keymaster.mbn
lksecapp.mbn
logo.img
misc.img
NON-HLOS.bin
partition.xml
patch0.xml
patch1.xml
patch2.xml
patch3.xml
patch4.xml
patch5.xml
persist.img
pmic.elf
prog_ufs_firehose_8996_ddr.elf
rawprogram0.xml
rawprogram1.xml
rawprogram2.xml
rawprogram3.xml
rawprogram4.xml
rawprogram5.xml
recovery.img
rpm.mbn
splash.img
system.img
tz.mbn
userdata.img
xbl.elf
As I said, it's like normal fastboot ROM, so flash it under fastboot mode, or use Mi Flash to use it (I reckon that you can flash it under EDL mode too if you want).
awaaas said:
Here is what inside the archive:
As I said, it's like normal fastboot ROM, so flash it under fastboot mode, or use Mi Flash to use it (I reckon that you can flash it under EDL mode too if you want).
Click to expand...
Click to collapse
Users have troubles with EDL sometimes. But now we know that it is the fastboot ROM package)
hi to all:
i don't know...
phone is un fastboot mode, connetcted to pc, open miflash, select path where all +.bin and +. img are extracted, press flash and 1 second elapse, progress bar is green, flash done
but the same rom installed on phone
if i run flash_bat this mesagge appears fastboot getvar product 2>&1 | findstr /r /c:"^product: *MSM8996_A7" || echo Missmatching image and device
i don't know
thanks for your support
Hi everyone,
I purchased a OnePlus 9 Pro directly from the OnePlus website itself while in the US. I was very disappointed to discover that they removed dual-sim support from the NA variant of the device. I travel between two countries for work, and having dual-sim support would be incredibly useful.
I did cheer up, however, when I read some posts saying that the physical pins weren't removed from the device, and that it's likely a software block.
Various people are saying different things, though, so I was hoping to get some clarification.
Is it at all likely that the US variant can get dual-sim support, whether by changing some device props or flashing a different variant's (or custom) ROM?
Thanks in advance for taking the time to answer.
I am trying to determine if there is actually a hardware fuse somewhere that is set for Dual SIM, or if it's purely software, so I need some help from you all. If you are close to the Phoenix, AZ area in the USA, or know anyone who is nearby, and have a Chinese or EU version of the OP9Pro, I would like to borrow the device for a few hours.
If it turns out that nobody lives in the desert, then I would like the help of someone with a Dual SIM enabled device to make a ufs dump via edl and allow me to have a copy of it, roughly 6.5GB. Linux and knowledge of bash required. PM me if available.
craznazn said:
I am trying to determine if there is actually a hardware fuse somewhere that is set for Dual SIM, or if it's purely software, so I need some help from you all. If you are close to the Phoenix, AZ area in the USA, or know anyone who is nearby, and have a Chinese or EU version of the OP9Pro, I would like to borrow the device for a few hours.
If it turns out that nobody lives in the desert, then I would like the help of someone with a Dual SIM enabled device to make a ufs dump via edl and allow me to have a copy of it, roughly 6.5GB. Linux and knowledge of bash required. PM me if available.
Click to expand...
Click to collapse
Not sure what exactly you want to check on SW side, but can't you "just" compare the full OTA zips of different versions?
craznazn said:
I am trying to determine if there is actually a hardware fuse somewhere that is set for Dual SIM, or if it's purely software, so I need some help from you all. If you are close to the Phoenix, AZ area in the USA, or know anyone who is nearby, and have a Chinese or EU version of the OP9Pro, I would like to borrow the device for a few hours.
If it turns out that nobody lives in the desert, then I would like the help of someone with a Dual SIM enabled device to make a ufs dump via edl and allow me to have a copy of it, roughly 6.5GB. Linux and knowledge of bash required. PM me if available.
Click to expand...
Click to collapse
Unfortunately, I'm nowhere near Arizona and only own the US variant, or I'd be more than happy to help.
I do encourage owners of those variants to volunteer a bit of their time to help with this.
Nobody knows, I'm sure I'm not the only one
drozd128 said:
Not sure what exactly you want to check on SW side, but can't you "just" compare the full OTA zips of different versions?
Click to expand...
Click to collapse
Nope, you can just flash the EU OTA to US and it obviously won't work. I need more than just the extracted MSM too, I actually need to compare other partitions baked into each device.
craznazn said:
Nobody knows, I'm sure I'm not the only one
Nope, you can just flash the EU OTA to US and it obviously won't work. I need more than just the extracted MSM too, I actually need to compare other partitions baked into each device.
Click to expand...
Click to collapse
I see your idea of dumping the phone to PC, but I don't think you need the dump of the EU phone. You should be able to compare either full OTAs, or your dump with full EU OTA (as far as I remember, there should be everything, boot, kernel, ... but I can be wrong on this, that was my experience with TCL phone 2-3y ago).
Also quick google search brought me this: https://forum.xda-developers.com/t/how-i-achieved-dual-sim-operation-on-rp2.3923159/ I guess, it is worth reading.
EDIT: I'm talking about unpacking and comparing, not flashing.
drozd128 said:
I see your idea of dumping the phone to PC, but I don't think you need the dump of the EU phone. You should be able to compare either full OTAs, or your dump with full EU OTA (as far as I remember, there should be everything, boot, kernel, ... but I can be wrong on this, that was my experience with TCL phone 2-3y ago).
Also quick google search brought me this: https://forum.xda-developers.com/t/how-i-achieved-dual-sim-operation-on-rp2.3923159/ I guess, it is worth reading.
EDIT: I'm talking about unpacking and comparing, not flashing.
Click to expand...
Click to collapse
You are operating under the assumption that the OTA has the SW to enable dual sim. If that was the case, flashing a EU rom on US would finish the job already.
To give you an idea of the difference, this is the directory list of the extracted OTA:
Code:
abl.img
aop.img
bluetooth.img
boot.img
cpucp.img
devcfg.img
dsp.img
dtbo.img
featenabler.img
hyp.img
imagefv.img
keymaster.img
modem.img
multiimgoem.img
odm.img
oplus_sec.img
oplusstanvbk.img
product.img
qupfw.img
qweslicstore.img
shrm.img
splash.img
system_ext.img
system.img
tz.img
uefisecapp.img
vbmeta.img
vbmeta_system.img
vbmeta_vendor.img
vendor_boot.img
vendor.img
vm-bootsys.img
xbl_config.img
xbl.img
Now, this is the directory list of an extracted MSM, ignoring folder structure:
Code:
carrier.img
frp.bin
gpt_backup0.bin
gpt_main0.bin
metadata.img
misc.bin
oem_stanvbk.bin
opluslog.img
param.bin
patch0.xml
persist.img
rawprogram0.xml
super.img
userdata.img
vbmeta_system.img
vbmeta_vendor.img
gpt_backup1.bin
gpt_main1.bin
patch1.xml
rawprogram1.xml
xbl_config.elf
xbl.elf
gpt_backup2.bin
gpt_main2.bin
patch2.xml
rawprogram2.xml
engineering_cdt.img
gpt_backup3.bin
gpt_main3.bin
ocdt.bin
patch3.xml
rawprogram3.xml
abl.elf
abl_log.bin
android_log.bin
aop.mbn
apdp.mbn
boot.img
BTFM.bin
cpucp.elf
devcfg.mbn
devinfo.bin
DRIVER.ISO
dspso.bin
dtbo.img
featenabler.mbn
gpt_backup4.bin
gpt_main4.bin
hyp_log.bin
hypvm.mbn
imagefv.elf
kernel_log16M.bin
km41.mbn
logfs_ufs_8mb.bin
mdcompress.mbn
multi_image.mbn
NON-HLOS.bin
oplusreserve2.img
oplus_sec.mbn
patch4.xml
qsee_log.bin
qupv3fw.elf
qweslicstore.bin
rawprogram4.xml
rtice.mbn
sec.elf
shrm.elf
splash.img
spunvm.bin
storsec.mbn
tz.mbn
uefi_sec.mbn
vbmeta.img
vendor_boot.img
vm-bootsys.img
emmc_fw.bin
gpt_backup5.bin
gpt_main5.bin
patch5.xml
rawprogram5.xml
Finally, an extracted phone with all the partitions dumped, again ignoring folder structure:
Code:
carrier.bin
frp.bin
gpt_backup0.bin
gpt_main0.bin
keystore.bin
metadata.bin
misc.bin
oplusdycnvbk.bin
opluslog.bin
oplusstanvbk_a.bin
oplusstanvbk_b.bin
param.bin
persist.bin
persist_bkp.bin
rawdump.bin
rawprogram0.xml
ssd.bin
super.bin
vbmeta_system_a.bin
vbmeta_system_b.bin
vbmeta_vendor_a.bin
vbmeta_vendor_b.bin
gpt_backup1.bin
gpt_main1.bin
rawprogram1.xml
xbl_a.bin
xbl_config_a.bin
gpt_backup2.bin
gpt_main2.bin
rawprogram2.xml
xbl_b.bin
xbl_config_b.bin
ALIGN_TO_128K_1.bin
cdt.bin
ddr.bin
dinfo.bin
engineering_cdt_a.bin
engineering_cdt_b.bin
gpt_backup3.bin
gpt_main3.bin
ocdt.bin
rawprogram3.xml
abl_a.bin
abl_b.bin
abl_log.bin
android_log.bin
aop_a.bin
aop_b.bin
apdp.bin
apdp_full.bin
bluetooth_a.bin
bluetooth_b.bin
boot_a.bin
boot_b.bin
connsec.bin
cpucp_a.bin
cpucp_b.bin
devcfg_a.bin
devcfg_b.bin
devinfo.bin
dip.bin
DRIVER.bin
dsp_a.bin
dsp_b.bin
dtbo_a.bin
dtbo_b.bin
featenabler_a.bin
featenabler_b.bin
gpt_backup4.bin
gpt_main4.bin
hyp_a.bin
hyp_b.bin
hyp_log.bin
imagefv_a.bin
imagefv_b.bin
kernel_log.bin
keymaster_a.bin
keymaster_b.bin
limits.bin
limits-cdsp.bin
logdump.bin
logfs.bin
mdcompress.bin
mdtp_a.bin
mdtp_b.bin
mdtpsecapp_a.bin
mdtpsecapp_b.bin
modem_a.bin
modem_b.bin
modemdump.bin
multiimgoem_a.bin
multiimgoem_b.bin
oplusreserve2.bin
oplusreserve3.bin
oplusreserve4.bin
oplusreserve5.bin
oplus_sec_a.bin
oplus_sec_b.bin
qmcs.bin
qsee_log.bin
qupfw_a.bin
qupfw_b.bin
qweslicstore_a.bin
qweslicstore_b.bin
rawprogram4.xml
rtice.bin
secdata.bin
shrm_a.bin
shrm_b.bin
splash_a.bin
splash_b.bin
spunvm.bin
storsec.bin
tz_a.bin
tz_b.bin
tzsc.bin
uefisecapp_a.bin
uefisecapp_b.bin
uefivarstore.bin
vbmeta_a.bin
vbmeta_b.bin
vendor_boot_a.bin
vendor_boot_b.bin
vm-bootsys_a.bin
vm-bootsys_b.bin
vm-data.bin
ALIGN_TO_128K_2.bin
fsc.bin
fsg.bin
gpt_backup5.bin
gpt_main5.bin
modemst1.bin
modemst2.bin
oplusreserve1.bin
rawprogram5.xml
OTA: 34 files
MSM: 80 files
Full dump: 135 files
In fact, I'll attach the MSM manifest.xml for you to check. Anywhere that has file="" means the public (non-factory) MSM doesn't even write. This includes obvious things like modemst1, and less obvious things like oplusdycnvbk. Obviously, things in _b doesn't need to be dumped, and is not even included in the MSM, but the fact is that even a MSM doesn't have all the SW components I need to analyze. EDIT: doesn't let me attach manifest.xml for some reason, oh well.
As for your link, thats one of the first things I did.... It might have worked in previous OP devices, since device_policy.xml was the same in all devices... however, see attached device_policy, we're gonna be flashing via QPST if we even get it to work. (Yes, I tried flashing it already, crashes modem)
Trust me, I don't want to have to borrow other people's devices...
craznazn said:
You are operating under the assumption that the OTA has the SW to enable dual sim. If that was the case, flashing a EU rom on US would finish the job already.
To give you an idea of the difference, this is the directory list of the extracted OTA:
Code:
abl.img
aop.img
bluetooth.img
boot.img
cpucp.img
devcfg.img
dsp.img
dtbo.img
featenabler.img
hyp.img
imagefv.img
keymaster.img
modem.img
multiimgoem.img
odm.img
oplus_sec.img
oplusstanvbk.img
product.img
qupfw.img
qweslicstore.img
shrm.img
splash.img
system_ext.img
system.img
tz.img
uefisecapp.img
vbmeta.img
vbmeta_system.img
vbmeta_vendor.img
vendor_boot.img
vendor.img
vm-bootsys.img
xbl_config.img
xbl.img
Now, this is the directory list of an extracted MSM, ignoring folder structure:
Code:
carrier.img
frp.bin
gpt_backup0.bin
gpt_main0.bin
metadata.img
misc.bin
oem_stanvbk.bin
opluslog.img
param.bin
patch0.xml
persist.img
rawprogram0.xml
super.img
userdata.img
vbmeta_system.img
vbmeta_vendor.img
gpt_backup1.bin
gpt_main1.bin
patch1.xml
rawprogram1.xml
xbl_config.elf
xbl.elf
gpt_backup2.bin
gpt_main2.bin
patch2.xml
rawprogram2.xml
engineering_cdt.img
gpt_backup3.bin
gpt_main3.bin
ocdt.bin
patch3.xml
rawprogram3.xml
abl.elf
abl_log.bin
android_log.bin
aop.mbn
apdp.mbn
boot.img
BTFM.bin
cpucp.elf
devcfg.mbn
devinfo.bin
DRIVER.ISO
dspso.bin
dtbo.img
featenabler.mbn
gpt_backup4.bin
gpt_main4.bin
hyp_log.bin
hypvm.mbn
imagefv.elf
kernel_log16M.bin
km41.mbn
logfs_ufs_8mb.bin
mdcompress.mbn
multi_image.mbn
NON-HLOS.bin
oplusreserve2.img
oplus_sec.mbn
patch4.xml
qsee_log.bin
qupv3fw.elf
qweslicstore.bin
rawprogram4.xml
rtice.mbn
sec.elf
shrm.elf
splash.img
spunvm.bin
storsec.mbn
tz.mbn
uefi_sec.mbn
vbmeta.img
vendor_boot.img
vm-bootsys.img
emmc_fw.bin
gpt_backup5.bin
gpt_main5.bin
patch5.xml
rawprogram5.xml
Finally, an extracted phone with all the partitions dumped, again ignoring folder structure:
Code:
carrier.bin
frp.bin
gpt_backup0.bin
gpt_main0.bin
keystore.bin
metadata.bin
misc.bin
oplusdycnvbk.bin
opluslog.bin
oplusstanvbk_a.bin
oplusstanvbk_b.bin
param.bin
persist.bin
persist_bkp.bin
rawdump.bin
rawprogram0.xml
ssd.bin
super.bin
vbmeta_system_a.bin
vbmeta_system_b.bin
vbmeta_vendor_a.bin
vbmeta_vendor_b.bin
gpt_backup1.bin
gpt_main1.bin
rawprogram1.xml
xbl_a.bin
xbl_config_a.bin
gpt_backup2.bin
gpt_main2.bin
rawprogram2.xml
xbl_b.bin
xbl_config_b.bin
ALIGN_TO_128K_1.bin
cdt.bin
ddr.bin
dinfo.bin
engineering_cdt_a.bin
engineering_cdt_b.bin
gpt_backup3.bin
gpt_main3.bin
ocdt.bin
rawprogram3.xml
abl_a.bin
abl_b.bin
abl_log.bin
android_log.bin
aop_a.bin
aop_b.bin
apdp.bin
apdp_full.bin
bluetooth_a.bin
bluetooth_b.bin
boot_a.bin
boot_b.bin
connsec.bin
cpucp_a.bin
cpucp_b.bin
devcfg_a.bin
devcfg_b.bin
devinfo.bin
dip.bin
DRIVER.bin
dsp_a.bin
dsp_b.bin
dtbo_a.bin
dtbo_b.bin
featenabler_a.bin
featenabler_b.bin
gpt_backup4.bin
gpt_main4.bin
hyp_a.bin
hyp_b.bin
hyp_log.bin
imagefv_a.bin
imagefv_b.bin
kernel_log.bin
keymaster_a.bin
keymaster_b.bin
limits.bin
limits-cdsp.bin
logdump.bin
logfs.bin
mdcompress.bin
mdtp_a.bin
mdtp_b.bin
mdtpsecapp_a.bin
mdtpsecapp_b.bin
modem_a.bin
modem_b.bin
modemdump.bin
multiimgoem_a.bin
multiimgoem_b.bin
oplusreserve2.bin
oplusreserve3.bin
oplusreserve4.bin
oplusreserve5.bin
oplus_sec_a.bin
oplus_sec_b.bin
qmcs.bin
qsee_log.bin
qupfw_a.bin
qupfw_b.bin
qweslicstore_a.bin
qweslicstore_b.bin
rawprogram4.xml
rtice.bin
secdata.bin
shrm_a.bin
shrm_b.bin
splash_a.bin
splash_b.bin
spunvm.bin
storsec.bin
tz_a.bin
tz_b.bin
tzsc.bin
uefisecapp_a.bin
uefisecapp_b.bin
uefivarstore.bin
vbmeta_a.bin
vbmeta_b.bin
vendor_boot_a.bin
vendor_boot_b.bin
vm-bootsys_a.bin
vm-bootsys_b.bin
vm-data.bin
ALIGN_TO_128K_2.bin
fsc.bin
fsg.bin
gpt_backup5.bin
gpt_main5.bin
modemst1.bin
modemst2.bin
oplusreserve1.bin
rawprogram5.xml
OTA: 34 files
MSM: 80 files
Full dump: 135 files
In fact, I'll attach the MSM manifest.xml for you to check. Anywhere that has file="" means the public (non-factory) MSM doesn't even write. This includes obvious things like modemst1, and less obvious things like oplusdycnvbk. Obviously, things in _b doesn't need to be dumped, and is not even included in the MSM, but the fact is that even a MSM doesn't have all the SW components I need to analyze. EDIT: doesn't let me attach manifest.xml for some reason, oh well.
As for your link, thats one of the first things I did.... It might have worked in previous OP devices, since device_policy.xml was the same in all devices... however, see attached device_policy, we're gonna be flashing via QPST if we even get it to work. (Yes, I tried flashing it already, crashes modem)
Trust me, I don't want to have to borrow other people's devices...
Click to expand...
Click to collapse
It still can be driver enabling/disabling 2nd SIM slot based on SN of board or something... I will download EU OTA and check if I can find something in there (I don't have the phone so can't do much more than that, sorry).
I can confirm that flashing the full EU OTA does not result in the slot being active. The getprop still shows persist.radio.multisim.config = ssss, despite the build.prop for the EU ROM having it set to dsds. I also flashed the param partition from an EU device, and that also did not resolve the issue. I have a second tray coming in the mail, so I'll do more testing when I receive it.
Something I noticed in getprop from an EU device was the presence of this parameter: persist.radio.check.two.sim = 1. Setting that prop manually does not change anything, but interesting to note that the parameter only exists on EU devices, and not my US device flashed to the EU build.
There must be a flag somewhere else that's tripping it.
I just got my dual-sim tray today. I'm not very technical but I know my way around, would be happy to help with any testing
I already have my device rooted and flashed the EU ROM
baselaa said:
I just got my dual-sim tray today. I'm not very technical but I know my way around, would be happy to help with any testing
I already have my device rooted and flashed the EU ROM
Click to expand...
Click to collapse
Does the dual SIM tray you ordered fit flush? If so, can you share the link? The one I ordered unfortunately doesn't fit right.
xian1243 said:
Does the dual SIM tray you ordered fit flush? If so, can you share the link? The one I ordered unfortunately doesn't fit right.
Click to expand...
Click to collapse
Actually I haven't tried it yet, I'm not staying home for a few days, will try it once I get back.
This is the one I got
https://www.aliexpress.com/item/1005002505723328.html?spm=a2g0o.productlist.0.0.716232d9cFVzRo&algo_pvid=5137e46b-7079-4bda-9876-75b2433ee2a6&algo_expid=5137e46b-7079-4bda-9876-75b2433ee2a6-0&btsid=0b0a556716201128566294751e9b01&ws_ab_test=searchweb0_0,searchweb201602_,searchweb201603_
Is there any progress on this?
So the Dual-Sim tray does remain flush and 100% for the 9Pro, however, even with the EU ROM it doesn't run dual-sim.
Is there anything I can test? I'm rooted and please feel free to have me try anything
The sim reader part numbers are different.
You can see the part numbers by watching the teardown videos of a single and dual sim phone.
Single Sim: c114 0001
Dual Sim: c114 0003
I can't find the dual sim board for sale.
Since I've now read every thread in my search results, is it safe to assume no one has gotten dual SIM working for the US version of the phone? I'm rooted and running EU/BA version of OOS. I ordered a dual SIM tray but it won't be here for a couple of weeks. I don't see options for SIM2 in Settings, but I'm sure it was there at one point (earlier version of OOS?). I'm also happy to install a custom ROM if there's one that works.
I can also enable dual sim but 2nd slot sim not working