Hello people,
I've got a problem:
I've bought a Newman N2. Unfortunately I've updated the stock rom - and now I've got no more detection of my Sim card.
It has Firmware Newman_N2_00.22 - IMEI is also correct.
My Sim card works in another handy correct.
I don't know what to do - I've searched already here, but it didn't help me what I found.
Could it be something with the EFS Filesystem? Can I restore it somehow whitouth flashing?
I can't install the CWM. Didn't work for me. The fastboot doesn't work for some reason
Thanks in advance for your help!
There was an info on the newman forums about you must flash the phone without sim.
What if you try it with wipe before flash, and reflash then?
Didn't read that unfortunately... What can I do now?
Try to install the 00.20 FW, but wipe data, and wipe cache before it. And ofc without the SIM.
After it you can isntall the 00.22 FW. It is the latest.
00.20 http://pan.baidu.com/share/link?shareid=188071&uk=1143976775
00.22 http://pan.baidu.com/share/link?shareid=190980&uk=1143976775
Any luck? I found something. To go back to the stock FW you need to flash it via Windows.
"Warning: People who have the first Version of the Firmware ( Date 2012.12.13 ), they should first update to second version ( Date 2012.12.15 ) and then they can update to the last version ( Date 2013.01.12). Because you can get some problems with SIM."
Unfortunately only 32bit drivers included.
thefiqs said:
Any luck? I found something. But I think to go back to the stock FW you need to flash it via Windows.
"Warning: People who have the first Version of the Firmware ( Date 2012.12.13 ), they should first update to second version ( Date 2012.12.15 ) and then they can update to the last version ( Date 2013.01.12). Because you can get some problems with SIM."
Unfortunately only 32bit drivers included.
Click to expand...
Click to collapse
I read this too, was because of me this topic
I sent it to a friend, who will flash it with his box.
Finally flashed it to the basic firmware.
Also tried several other firmwares, resetting IMEI - also different sim cards.
We guess the SIM Slot should be broken. Does anybody know if we can order just the SIM Module Slot? Or it would be just the whole mainboard?
ChrizZzz0w said:
Hello people,
I've got a problem:
I've bought a Newman N2. Unfortunately I've updated the stock rom - and now I've got no more detection of my Sim card.
It has Firmware Newman_N2_00.22 - IMEI is also correct.
My Sim card works in another handy correct.
I don't know what to do - I've searched already here, but it didn't help me what I found.
Could it be something with the EFS Filesystem? Can I restore it somehow whitouth flashing?
I can't install the CWM. Didn't work for me. The fastboot doesn't work for some reason
Thanks in advance for your help!
Click to expand...
Click to collapse
baseband problem
See IMEI sim card phone is not registering. Imeili clone phones updated when the network is losing record. I think they do the installation again with Box
After updating to the latest update, android 11 global for poco f2 both my sim card slots have been turned off.
When i try to turn on sim1 it tells me that only 1 sim card can have 5g enabled and to change my network settings.
Unfortunately none of the slots wont turn on so i cant change the network settings for either sim.
Have tried putting in 1 sim and restarting, in either slot 1 or 2 the sim slot still wont turn on.
Is there any other way to do it other than a factory reset?
I have same problem with you. I cannot turn on sim card 1 or 2. İt is very weird problem. Did u solve the problem ?
A hard reset maybe help
usmanjavid said:
A hard reset maybe help
Click to expand...
Click to collapse
Yeap i did it. I had another bugs after the update. But factory reset fixed all of them
This version (stable BETA) in android 11 has multiple bugs. Many prefer to revert to the previous version.
https://forum.xda-developers.com/t/...11-general-discussions-bugs-features.4165065/
Great,! Wish I'd bloody read this thread before I updated. At least I know now, it's not just me. Unfortunately, for me at least, I'm on stock & haven't modded, unlocked bootloader, rooted or flashed anything at all. Does anyone know if Xiaomi's backup utility is any good or shall I not bother before I factory reset?. Cheers.
Howdy.
So, not trying to steal anyone's thunder, but this Convert T-Mobile OnePlus 9 to Global (or other) firmware thread has not been updated by the OP (@Lomeli12) in awhile, and I ran into some hiccups when following the directions, along with a couple clarifications scattered across different threads. Credit of course to the original thread above that is still very helpful minus being out of date, @craznazn for the conversion script, @Ju5t3nC4s3 for the OEM toggling tool, and the advice of other kind XDAers responding to my questions.
The key here, that the thread above does not indicate, is that the conversion takes you back to 11.2.2, and that when you try the OEM updater or the Oxygen Updater, both just want to take you straight to Android 12 (C.48). For whatever reason, probably some preliminary prep that takes place in later Android 11 updates, the C.48 update fails exactly at 25%. I tried the conversion and update multiple times, just to make sure that wasn't a corruption issue.
After this dead end, I decided to check out the sadly not current official OTA download site to see what was available. Interestingly, their current OTA was not C.48, it was 11.2.10.10. I quickly downloaded that, and lo and behold the update succeeded! Afterwards I checked and my device model had changed to the correct LE2115 as I wanted it too (it had not changed after running the conversion script).
Then I checked the system updater, and C.48 was waiting. Installed, rebooted, and boom I was on Android 12. Then C.63 with the August 5th security update was ready. Installed seamlessly.
Helpful tips/findings/clarifications:
You will receive this final error at the end of the conversion script, but you can ignore
fastboot -w
Erasing 'userdata' OKAY [ 0.317s]
CreateProcess failed: The system cannot find the file specified. (2)
fastboot: error: Cannot generate image for userdata
Done!
Please reboot to recovery via the menus and wipe everything prior to boot
Your device model will still show TMo (2117) until you successfully apply the 11.2.10.10 update
For anyone confused by multiple threads that are seemingly contradictory, you do NOT have to be SIM unlocked to do this. You just need this nifty little tool from @Ju5t3nC4s3 that enables you to toggle the OEM unlock and subsequently get the unlock code to submit to 1+ and then unlock the bootloader with the token 1+ sends you
If you don't plan on leaving TMo, then leaving SIM locked is fine. If you do decide to change carriers, you'll need this MSM to flash back to TMo firmware to then request SIM unlock
You definitely can apply OTAs with an unlocked bootloader. Just not a rooted boot.
If you have root, you can easily pull your modem and persist imgs via Partitions Backup & Restore
If you do not have root, I received confirmation from @EtherealRemnant in this thread that the modem and persist that I pulled via the above mentioned MSM are in fact valid.
Root is easy as booting, NOT flashing, a patched boot, then using Magisk manager to patch. This enables your to easily revert back to stock boot. If you flash, your stock boot is gone
Hope this helps someone else avoid many hours of thread scanning
Phoenix47 said:
When I do msm on t-mobile variant, I get oos12 ota straight from oos 11.2.2.2 but it is not actually oos12 ota. It have 500mb size and updates phone to 11.2.8.8 version on tmo but can't get any more ota updates after that.
Click to expand...
Click to collapse
What MSM specifically? If it is the TMo one, then you won't get OTAs from 1+, they come from TMo. 11.2.8.8 is the latest from TMo
Phoenix47 said:
And the tmo to global conversion msmtool is not good. You get sim issue after updating to global oos12.
Click to expand...
Click to collapse
What SIM issues?
Phoenix47 said:
I was on TMO oos 11.2.9.9 before and got oos12 ota update with 5gb size. But now I only get ota till 11.2.8.8 on tmobile rom after using tmobile msm 11.2.2.2 available on xda.
.
.
Regarding sim issue, the global oos12 convert my single sim LE2117 to dual sim LE2115 which cause NO SIM bug.
Click to expand...
Click to collapse
Interesting, I never got 12 when I was TMo, only 11.2.8.8. Maybe different areas get different stages? It is weird the TMo ROM is so far behind though...
Did you follow step 9 of the conversion guide?
Really, all of these methods are outdated. The best way to do it is to use Fastboot Enhance.
Safely convert regions (includes T-Mobile) as well as restore the ability to use OOS12 after using Indian MSM to recover from a brick (Windows only)
It seems lots of us have had to use the India 9 Pro MSM to recover our devices and in the process, we lose the ability to go back to OOS12 or ROMs based on that firmware because the touchscreen stops working and also trying to convert T-Mobile...
forum.xda-developers.com
After doing that, you just have to flash the Magisk fix to get back working data (because of the aforementioned dual SIM bug).
Phoenix47 said:
Step 9 is flashing modem.img from tmo rom, which also require unlocking bootloader. Actually the issue can also be fixed by a small magisk module which convert phone back to single sim on oos12. Did you flash the tmo oos11 modem.img on global oos12 ?
.
I am just saying, there is no way to fix that issue on locked bootloader after using the conversion msm.
Click to expand...
Click to collapse
Ah, I am not sure then how you'd fix the issue as I have an unlocked bootloader and root.
And I have not flashed the file yet or the Magisk fix. I have to send the phone off for screen repair, so I haven't popped a SIM in it since converting.
Phoenix47 said:
When I do msm on t-mobile variant, I get oos12 ota straight from oos 11.2.2.2 but it is not actually oos12 ota. It have 500mb size and updates phone to 11.2.8.8 version on tmo but can't get any more ota updates after that.
Click to expand...
Click to collapse
I'm also facing this issue
It's been over a week and still no updates after 11.2.8.8
My device was previously on OOS12 C.19 before i bricked it and uses the MSM tool
centifanto said:
Howdy.
So, not trying to steal anyone's thunder, but this Convert T-Mobile OnePlus 9 to Global (or other) firmware thread has not been updated by the OP (@Lomeli12) in awhile, and I ran into some hiccups when following the directions, along with a couple clarifications scattered across different threads. Credit of course to the original thread above that is still very helpful minus being out of date, @craznazn for the conversion script, @Ju5t3nC4s3 for the OEM toggling tool, and the advice of other kind XDAers responding to my questions.
The key here, that the thread above does not indicate, is that the conversion takes you back to 11.2.2, and that when you try the OEM updater or the Oxygen Updater, both just want to take you straight to Android 12 (C.48). For whatever reason, probably some preliminary prep that takes place in later Android 11 updates, the C.48 update fails exactly at 25%. I tried the conversion and update multiple times, just to make sure that wasn't a corruption issue.
After this dead end, I decided to check out the sadly not current official OTA download site to see what was available. Interestingly, their current OTA was not C.48, it was 11.2.10.10. I quickly downloaded that, and lo and behold the update succeeded! Afterwards I checked and my device model had changed to the correct LE2115 as I wanted it too (it had not changed after running the conversion script).
Then I checked the system updater, and C.48 was waiting. Installed, rebooted, and boom I was on Android 12. Then C.63 with the August 5th security update was ready. Installed seamlessly.
Helpful tips/findings/clarifications:
You will receive this final error at the end of the conversion script, but you can ignore
fastboot -w
Erasing 'userdata' OKAY [ 0.317s]
CreateProcess failed: The system cannot find the file specified. (2)
fastboot: error: Cannot generate image for userdata
Done!
Please reboot to recovery via the menus and wipe everything prior to boot
Your device model will still show TMo (2117) until you successfully apply the 11.2.10.10 update
For anyone confused by multiple threads that are seemingly contradictory, you do NOT have to be SIM unlocked to do this. You just need this nifty little tool from @Ju5t3nC4s3 that enables you to toggle the OEM unlock and subsequently get the unlock code to submit to 1+ and then unlock the bootloader with the token 1+ sends you
If you don't plan on leaving TMo, then leaving SIM locked is fine. If you do decide to change carriers, you'll need this MSM to flash back to TMo firmware to then request SIM unlock
You definitely can apply OTAs with an unlocked bootloader. Just not a rooted boot.
If you have root, you can easily pull your modem and persist imgs via Partitions Backup & Restore
If you do not have root, I received confirmation from @EtherealRemnant in this thread that the modem and persist that I pulled via the above mentioned MSM are in fact valid.
Root is easy as booting, NOT flashing, a patched boot, then using Magisk manager to patch. This enables your to easily revert back to stock boot. If you flash, your stock boot is gone
Hope this helps someone else avoid many hours of thread scanning
Click to expand...
Click to collapse
Did you run into SIM card issues after updating to C.48 using this method?
I'm just wondering if i can use the TMO-GLO MSM tool to get 11.2.2 them use the local update to 11.2.10.10 then go to C.48 to hopefully retain Cell service/SIM Card, any help on the matter would be appreciated!
Phoenix47 said:
It is weird that global rom shows dual sim on oos12. I mean there is single sim global model also.
.
And that magisk fix don't work on custom roms.
Click to expand...
Click to collapse
The T-Mobile model is actually dual SIM but with a single SIM tray from my understanding, hence the software bug.
Phoenix47 said:
Step 9 is flashing modem.img from tmo rom, which also require unlocking bootloader. Actually the issue can also be fixed by a small magisk module which convert phone back to single sim on oos12. Did you flash the tmo oos11 modem.img on global oos12 ?
.
I am just saying, there is no way to fix that issue on locked bootloader after using the conversion msm.
Click to expand...
Click to collapse
Flashing modem is only required on the 9 Pro because it has an mmWave modem.
Phoenix47 said:
So you are saying that adding dual sim tray will fix the NO SIM CARDS issue ?
Click to expand...
Click to collapse
No because it doesn't work right either.
EDIT: Looks like I misspoke anyway because it's only the LE2127.
ENABLE DUAL SIM ON TMO 9 PRO ONLY!!!
Frist off I'm not Responsible for anything that happens to your phone!!! THIS HAS BEEN TESTED AND WORKING 100% ON TMO 9PRO LE2127!!ALSO MODEM RETENTION. (THIS IT NOT FOR THE UNLOCKED 9PRO LE2125) DO THIS AT YOU OWN RISK!! THIS METHOD IS...
forum.xda-developers.com
This worked great on my le2117 That is SIM and Bootloader unlocked. I didn’t have to flash the modem at all. Interestingly, it didn’t change model to le2115 until did the local update to c.48. Then I was able to OTA to c.63.
the only thing I see is that Netflix does not work or allow me to update…anybody know the fix and are there any other apps that I should expect that behavior?
Great info on this thread…I think I’m going to try to load Nameless soon.
Does anyone have the TMO 11.2.8.8 or anything around there? I've heard of 11.2.9.9. I was on EU 11.2.10.10. it was mostly ok but I was having a few communication issues*. I want to compare to a stock TMO later-11 version. I'm currently on 11.2.3.3le5acb
I tried searching the forum but it doesn't allow searching for "11.2.8.8" type strings. Or short strings.
*Wifi stopped connecting to some of my APs. Until I toggled Mac randomization, then it was fine. It's no problem in my 7TP5G.
5G would drop off to LTE, no problem... But then, LTE would drop off into no data. SMS would sometimes get stuck until reboot. Visual voicemail worked when it wanted to. None of these were consistently happening but all more than once.
Overall it wasn't too bad really but I want to try a late-11 and see how it goes.
Thanks
EtherealRemnant said:
Really, all of these methods are outdated. The best way to do it is to use Fastboot Enhance.
Safely convert regions (includes T-Mobile) as well as restore the ability to use OOS12 after using Indian MSM to recover from a brick (Windows only)
It seems lots of us have had to use the India 9 Pro MSM to recover our devices and in the process, we lose the ability to go back to OOS12 or ROMs based on that firmware because the touchscreen stops working and also trying to convert T-Mobile...
forum.xda-developers.com
After doing that, you just have to flash the Magisk fix to get back working data (because of the aforementioned dual SIM bug).
Click to expand...
Click to collapse
i can agree with him. i was one of the first people to try this method on the thread he created. works wonderfully. hence why his thread was stickied to the top of xda oneplus 9 page.
I did look through bunch of threads but cant seem to find an answer . . Is there a way to enable dual sim on the LE2115 and if someone has tried successfully (with or without any known issues) ?
If someone can point me to the right steps to follow ?
TIA
centifanto said:
2.10.10. I quickly downloaded that, and lo and behold the upda
Click to expand...
Click to collapse
bguzz said:
This worked great on my le2117 That is SIM and Bootloader unlocked. I didn’t have to flash the modem at all. Interestingly, it didn’t change model to le2115 until did the local update to c.48. Then I was able to OTA to c.63.
the only thing I see is that Netflix does not work or allow me to update…anybody know the fix and are there any other apps that I should expect that behavior?
Great info on this thread…I think I’m going to try to load Nameless soon.
Click to expand...
Click to collapse
how you did the local update? did you have to unlock your bootloader?
centifanto said:
Howdy.
So, not trying to steal anyone's thunder, but this Convert T-Mobile OnePlus 9 to Global (or other) firmware thread has not been updated by the OP (@Lomeli12) in awhile, and I ran into some hiccups when following the directions, along with a couple clarifications scattered across different threads. Credit of course to the original thread above that is still very helpful minus being out of date, @craznazn for the conversion script, @Ju5t3nC4s3 for the OEM toggling tool, and the advice of other kind XDAers responding to my questions.
The key here, that the thread above does not indicate, is that the conversion takes you back to 11.2.2, and that when you try the OEM updater or the Oxygen Updater, both just want to take you straight to Android 12 (C.48). For whatever reason, probably some preliminary prep that takes place in later Android 11 updates, the C.48 update fails exactly at 25%. I tried the conversion and update multiple times, just to make sure that wasn't a corruption issue.
After this dead end, I decided to check out the sadly not current official OTA download site to see what was available. Interestingly, their current OTA was not C.48, it was 11.2.10.10. I quickly downloaded that, and lo and behold the update succeeded! Afterwards I checked and my device model had changed to the correct LE2115 as I wanted it too (it had not changed after running the conversion script).
Then I checked the system updater, and C.48 was waiting. Installed, rebooted, and boom I was on Android 12. Then C.63 with the August 5th security update was ready. Installed seamlessly.
Helpful tips/findings/clarifications:
You will receive this final error at the end of the conversion script, but you can ignore
fastboot -w
Erasing 'userdata' OKAY [ 0.317s]
CreateProcess failed: The system cannot find the file specified. (2)
fastboot: error: Cannot generate image for userdata
Done!
Please reboot to recovery via the menus and wipe everything prior to boot
Your device model will still show TMo (2117) until you successfully apply the 11.2.10.10 update
For anyone confused by multiple threads that are seemingly contradictory, you do NOT have to be SIM unlocked to do this. You just need this nifty little tool from @Ju5t3nC4s3 that enables you to toggle the OEM unlock and subsequently get the unlock code to submit to 1+ and then unlock the bootloader with the token 1+ sends you
If you don't plan on leaving TMo, then leaving SIM locked is fine. If you do decide to change carriers, you'll need this MSM to flash back to TMo firmware to then request SIM unlock
You definitely can apply OTAs with an unlocked bootloader. Just not a rooted boot.
If you have root, you can easily pull your modem and persist imgs via Partitions Backup & Restore
If you do not have root, I received confirmation from @EtherealRemnant in this thread that the modem and persist that I pulled via the above mentioned MSM are in fact valid.
Root is easy as booting, NOT flashing, a patched boot, then using Magisk manager to patch. This enables your to easily revert back to stock boot. If you flash, your stock boot is gone
Hope this helps someone else avoid many hours of thread scanning
Click to expand...
Click to collapse
why when i try to install 11.2.10.10 my phone reset and keep saying is LE2117, it won't let me install LE2115_11.F.16. Pls help
After all procedure I'm on latest global A13 with December security patch but I have very strange issue, after airplane mode or restart my sim stop working and I have to eject and re-insert the sim for network service any solution
OnePlus 8t devices are dual sims except for the TMobile version which i have
BUT , after using msm tool to change it from TMobile to EU version (kb2007 > kb2003)
Now it can run dual sims BUT only in oos11
Someone tried using the beta 1 version of oos13 and it was working with dual sims but when the stable update came it disabled the second sim
When i searched , people say that the system recognize that the phone is a TMobile kb2007 and only runs a one sim at a time in both oos13 and oos12
My question is , what was oos11 doing with the sim file to make it run both sims together? And if we can use the same thing on the oos13 ?
That's a very good question, I'm also interested in this.
Specifically because I have a KB2007 which I want to use with dual sim, and need to know if I have to stay on OOS11 (which is becoming more and more difficult due to forced updates ). On top of that LineageOS (which I was planning to use) does not even publish regular builds based on OOS11 anymore.
FreeDee said:
That's a very good question, I'm also interested in this.
Specifically because I have a KB2007 which I want to use with dual sim, and need to know if I have to stay on OOS11 (which is becoming more and more difficult due to forced updates ). On top of that LineageOS (which I was planning to use) does not even publish regular builds based on OOS11 anymore.
Click to expand...
Click to collapse
I can help you out with dual sim on OOS 13 stable build.. only con is i cant relock bootloader on OOS 13.. telegram me if you're interested would happily assist you @ignghost1
FreeDee said:
That's a very good question, I'm also interested in this.
Specifically because I have a KB2007 which I want to use with dual sim, and need to know if I have to stay on OOS11 (which is becoming more and more difficult due to forced updates ).
Click to expand...
Click to collapse
[T-Mobile] Enable dual SIM OOS 13 or COS 13
1. Download F10 abl.img 2. Reboot to fastboot and flash F10 abl adb reboot fastboot fastboot flash abl abl.img 3.. Reboot fastboot reboot and you can use dual SIM.
forum.xda-developers.com
Enable dual SIM (KB2005 converted from T-Mobile) Android 13 F_15
I honestly don't know how I did but I'll show the tweaks I've made that made it happen. It's most likely the firmware flasher script that did it, but I'm not sure. Watch this video to see all of the tweaks/modules I'm using.
forum.xda-developers.com
Rootk1t said:
[T-Mobile] Enable dual SIM OOS 13 or COS 13
1. Download F10 abl.img 2. Reboot to fastboot and flash F10 abl adb reboot fastboot fastboot flash abl abl.img 3.. Reboot fastboot reboot and you can use dual SIM.
forum.xda-developers.com
Enable dual SIM (KB2005 converted from T-Mobile) Android 13 F_15
I honestly don't know how I did but I'll show the tweaks I've made that made it happen. It's most likely the firmware flasher script that did it, but I'm not sure. Watch this video to see all of the tweaks/modules I'm using.
forum.xda-developers.com
Click to expand...
Click to collapse
Does the first one requires unlocked bootloader?
ghost.ign said:
Does the first one requires unlocked bootloader?
Click to expand...
Click to collapse
I reckon so.