I have problem with 4g signal on oneplus 7 . After update to oxygen os 10.0.3 i have problem with 4g,i have no signal 4g ,and very poor Network signal.I did many things to fix that,did changed settings,did factory reset, nothing happened, problem still same. I did downgrade to Android 9 and oxygen os 9.5.8 same version was when i bought this phone, after downgrade anyway problem still same,no 4G signal. I did changed sim card replaced new sim card, nothing happened, problem still same.Maybe anyone knows how to fix that ?
Thanks
Hi, probably you lost some network bands if you are rooted you can check it with network signal guru from playstore.
If that's right there are some guides here on xda how to restore em up, for the guide check Mi A1 forum or let me know and I will send you the link.
Illuminatus_ said:
Hi, probably you lost some network bands if you are rooted you can check it with network signal guru from playstore.
If that's right there are some guides here on xda how to restore em up, for the guide check Mi A1 forum or let me know and I will send you the link.
Click to expand...
Click to collapse
Thank you for information,i tried to do root but have problem all the time, Bootloader already unlocked ,but when i trying to flash twrp image getting fault ( fastboot failed, remote unknown command) I don't know how to fix that. Can find anything on internet any info.
skeltukas said:
Thank you for information,i tried to do root but have problem all the time, Bootloader already unlocked ,but when i trying to flash twrp image getting fault ( fastboot failed, remote unknown command) I don't know how to fix that. Can find anything on internet any info.
Click to expand...
Click to collapse
Try this guide to root your phone
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
Dont forget to enable usb debugging in your phone.
Good luck.
skeltukas said:
Bootloader already unlocked ,but when i trying to flash twrp image getting fault ( fastboot failed, remote unknown command)
Click to expand...
Click to collapse
What version TWRP?
Although rooting to diagnose a network problem seems a little excessive.
How did you update, did the OTA download automatically, or did you pick the file yourself? If the latter, are you sure it is the right OTA file for your phone version?
TWRP version 3.3.1-1
When i got phone ,he arrived from China AliExpress. He arrived with Global oxygen os 9.5.8 , i did change to Europe version oxygen os, everything worked very well , I didn't had any problems,4G signal was good as well , till i was on android 10 and oxygen 10.0.2 was fine,but after i did get update to 10.0.3 my 4G gone . Few udates i did by Oxygen os updater,last one i did get OTA automatically. Now i did downgrade to 9.5.8 to global version. Still don't have 4G signal. Just battery very good on android 9 and oxygen os 9.5.8 , 11 hour screen on.
skeltukas said:
TWRP version 3.3.1-1
Click to expand...
Click to collapse
Too old to work with Android 10, that is why fastboot boot command is broken. You need to use one of the unofficial TWRP builds, I think at least -65 (current is -74).
Doesn't explain your LTE problem, just will fix the issue with booting TWRP (root, etc.).
redpoint73 said:
Too old to work with Android 10, that is why fastboot boot command is broken. You need to use one of the unofficial TWRP builds, I think at least -65 (current is -74).
Doesn't explain your LTE problem, just will fix the issue with booting TWRP (root, etc.).
Click to expand...
Click to collapse
Thank you for reply to my message, I don't know what about Android 10, I'm now currently on Android 9, as i wrote i did downgrade ,from Android 10 oxygen os 10.0.3 ,to Android 9 oxygen os 9.5.8
I did tried to flash
TWRP 3.3.1-1
TWRP 3.3.1-65
TWRP 3.3.1-70
TWRP 3.3.1-74
All the time have same error.
Sending boot img <56612> OKAY [ 2.714s ]
Booting Failed <remote: 'unknown comman'>
Fastboot : error: Coman failed
Illuminatus_ said:
Hi, probably you lost some network bands if you are rooted you can check it with network signal guru from playstore.
If that's right there are some guides here on xda how to restore em up, for the guide check Mi A1 forum or let me know and I will send you the link.
Click to expand...
Click to collapse
Hello, can you send me link? Seems i have problem with network bands.
Here you are , look's little complicated but it's easy.
https://forum.xda-developers.com/mi-a1/how-to/lte-t3854592/amp/
Illuminatus_ said:
Here you are , look's little complicated but it's easy.
https://forum.xda-developers.com/mi-a1/how-to/lte-t3854592/amp/
Click to expand...
Click to collapse
Thanks for sharing the info. I was in the same situation, followed the guide (I confirm, it's really easy) and now 4G+ is back!
I'm glad that you solved your problem, this guide helped lot of people especially Mi A1 users
(we lost band 20 after updating our device from Android 8.1 to 9)
Illuminatus_ said:
I'm glad that you solved your problem, this guide helped lot of people especially Mi A1 users
(we lost band 20 after updating our device from Android 8.1 to 9)[/QUOTE
I did everything by this guide ,but no luck,still same problem no LTE (4G) signal. I don't know what's wrong .
Click to expand...
Click to collapse
Related
I have a seemingly stupid but still annoying problem. As many of you know Android 8 + EMUI 8 came out this summer and I have updated my Honor8. Everything works well, even better (especially with regard to the battery) apart from a problem, quite annoying. I have seen that everyone around complains about the same problem, so it is clear that both a build bug and not a local problem.
Basically ... the bluetooth link with the multimedia system of my car doesn't work as it should, while it worked well with the 7.0.
Tracknames, music infos disappears, sometimes it connects regularly, starting the music, sometimes nothing happens, sometimes the music passes from the car speakers to smartphone (!!)... in short, manage the music in the car It has become a big problem!
I tried all possible options; reset pairing, reset bluetooth, clear cache, activate the developer options to control some low-level aspects of bluetooth, and finally installed Bluetooth Auto Connect which also has several advanced options. Nothing works. In the meantime an update of 8.0 has been released (mine is the buiold 521). The update came out in September ... maybe (MAYBE) this update fixes all bluetooth issues (but i don't have any detailed info about). Until today I have not received any updates and normally I check new version regularly every day. At this point I decided to return to Nougat!
And here the adventure begins!
I CANNOT IN ANY WAY do the downgrade.
What I tried:
- through HiSuite. The "back to previous version" option appears random (rarely); normally the program tells me "the system is up to date". Once appeared I tried to run the procedure, but after the decompression it gives me an error "error updating".
- by standard Rollback procedure. Using a microSD and putting the full version of Nougate in the dload folder. The installation starts but stops almost immediately with the same "update cannot be applied" error.
At this point I am desperate. I cannot update Oreo, I can't go back to Nougat and meanwhile the bluetooth still doesn't work with my car. Remember that before Oreo, everything worked very well!
What can I do? Can you help me?
Thank you
hi / i can help u / pls say me this:
your region(Ru/Eu/Cn.......)
your model( FRD-L09/L19/L04........)
Your Build number
and which build you upgrade to emui 8
m2relax said:
hi / i can help u / pls say me this:
your region(Ru/Eu/Cn.......)
your model( FRD-L09/L19/L04........)
Your Build number
and which build you upgrade to emui 8
Click to expand...
Click to collapse
Region: EU
Model: FRD-L09
Build: 8.0.0.521 (C432)
Previous Build: don't remember. It was Nougat, and I've upgraded around the first week of September. From that day I haven't received/applied any patch, because nothing appears until now.
This morning I've tried again with HiSuite. As usual it says I'm running the latest version and it doesn't offer any downgrade option .
Thelothian said:
Region: EU
Model: FRD-L09
Build: 8.0.0.521 (C432)
Previous Build: don't remember. It was Nougat, and I've upgraded around the first week of September. From that day I haven't received/applied any patch, because nothing appears until now.
This morning I've tried again with HiSuite. As usual it says I'm running the latest version and it doesn't offer any downgrade option .
Click to expand...
Click to collapse
dont worry/ do u change region of your phone past?
m2relax said:
dont worry/ do u change region of your phone past?
Click to expand...
Click to collapse
Never. And never jailbroken or rooted...
Thelothian said:
Never. And never jailbroken or rooted...
Click to expand...
Click to collapse
ok / pls do this work step by step :
1-Get Unlock Code for your Phone
2-Unlock your phone with Unlock Code
3-install TWRP recovery
4-after install TWRP notice me to send a file for u ( u must flash it from recovery TWRP )
5-after flashing u most install recovery stock
6-End and your problem is done! :fingers-crossed:
m2relax said:
ok / pls do this work step by step :
1-Get Unlock Code for your Phone
2-Unlock your phone with Unlock Code
3-install TWRP recovery
4-after install TWRP notice me to send a file for u ( u must flash it from recovery TWRP )
5-after flashing u most install recovery stock
6-End and your problem is done! :fingers-crossed:
Click to expand...
Click to collapse
I Heard TWRP doesn't work well on Oreo...
CurlyApple said:
I Heard TWRP doesn't work well on Oreo...
Click to expand...
Click to collapse
no if you use multi tools 8 for install twrp its work perfectly on oero
m2relax said:
no if you use multi tools 8 for install twrp its work perfectly on oero
Click to expand...
Click to collapse
The more you know...
Finally I've decide to try updating to 8.0.0.562. After a month of tries, fails (damn Huawei and his stupid update system), errors and a lot of other stupid things, I was finally able to update my Honor hoping the latest version will fix all the problems. It was a enormous waste of time (searching around internet)... but in the end I found a method described here: https://forum.xda-developers.com/huawei-p20-pro/help/p20-pro-bricked-t3868085#4And if you go ahead you should find the correct firmware link (on a Russian site). Although, IMHO, failing with the classic method was due to the impossibility or some bugs in the update system, to unpack the update files on sdcard. So the solution seems to be to leave both the zip and the unpacked folder.The problems with bluetooth remain, but I hope that now there is not to be crazy applying next updates. ATTENTION: the method above is NOT valid for rollback! If you try, you'll brick your Honor.
And finally I've taken an important decision... for me this is the last Huawei/honor device. Next time I'll go to another brand, with a serious update system.
Hello,
I have the same problem whit my honor, bluetooth lost signal random times, and my battery is faster get low, on android 7 i dont feel thees problems. Anyone have an idea how can i downgrade to nougat or marshmallow? My phone infos:
-FRD-L09 8.0.0.521(C432), I bought it in Hungary (i think its an EU modell), the phone have an unlocked bootloader, and flashed whit TWRP recovery
Who know the solution, pls reply here or, write me an email. Big thanks
scseke said:
Hello,
I have the same problem whit my honor, bluetooth lost signal random times, and my battery is faster get low, on android 7 i dont feel thees problems. Anyone have an idea how can i downgrade to nougat or marshmallow? My phone infos:
-FRD-L09 8.0.0.521(C432), I bought it in Hungary (i think its an EU modell), the phone have an unlocked bootloader, and flashed whit TWRP recovery
Who know the solution, pls reply here or, write me an email. Big thanks
Click to expand...
Click to collapse
flash this file with twrp and install stock recovery and do reset factor / finally use hisuite to rollback
https://cntechpost.com/2020/06/22/oppo-releases-coloros-based-on-android-11-beta-1/
*** It wipes all your data. So do backup.
It has Color OS 7.2 and still has GMS.
Download the zip and update in recovery. MAY BE BUGGY.
If you are in Beta, you may not be able to receive beta even when you rollback to 10
Update to Android 11 (For PDEM30. Chinese version)
Removed
Rollback to Android 10
Removed
i keep getting "installation failed" ;( and I'm using the 2025 version
juzzystar said:
i keep getting "installation failed" ;( and I'm using the 2025 version
Click to expand...
Click to collapse
Sorry I can't find ozip for Global version
ZZYSonny said:
Sorry I can't find ozip for Global version
Click to expand...
Click to collapse
Oh so this isn't global? That sucks
All good, I just corrupted the file during download
juzzystar said:
Oh so this isn't global? That sucks
Click to expand...
Click to collapse
Oh I didn't see this. Have a try. I only have the Chinese version.
This is extremely buggy. Reboots, 3-button navigation hitboxes interfering with app usage, random reboots to recovery,
I rollback to Android Q with the file that Oppo gives and it says now "No Sim Card" detected....
My model is CPH2025EU and their file is for the 2025PU... How can i fix that ? :-/
Oh dear, looks like this beta might not be worth trying yet.
But... well done to Oppo on offering it and to those of you willing to flash it.
gregou said:
I rollback to Android Q with the file that Oppo gives and it says now "No Sim Card" detected....
My model is CPH2025EU and their file is for the 2025PU... How can i fix that ? :-/
Click to expand...
Click to collapse
Same Problem here, IMEI disappears. Guess I have to bring it to service center lol.
You rolled back as well to Android Q ?
I guess we need to wait for an european firmware equals the chinese firmware 11_A_23 as the most recent european firmware for me is the 11_A_18 version.
gregou said:
You rolled back as well to Android Q ?
I guess we need to wait for an european firmware equals the chinese firmware 11_A_23 as the most recent european firmware for me is the 11_A_18 version.
Click to expand...
Click to collapse
Yes, I rolled back and got screwed lol.
I'm sure we're going to be several people affected by this issue.
Someone is going to find a solution quickly i hope :-/
gregou said:
I'm sure we're going to be several people affected by this issue.
Someone is going to find a solution quickly i hope :-/
Click to expand...
Click to collapse
The one who can find the solution must be "OPPO" themselves. Since nothing can be done with our device. No MSMDownloadTool nor OPPOdownloadtool (for consumer like us). Nothing can be done here. Guess they have a problem signing their package in the Kernel section.
Mine is Thai version. Dual SIM, CPH2025.
I tried to warn people in the comment section of ColorOS but sadly, I can't comment since my OPPO ID hasn't participated anything in their forum yet. So, I will let it go.
What about flashing a firmware through ADB ?
SIM card will no longer be read when you roll back in China version. The only solution is to install Android 11 Beta 1 again. I can now read the SIM card.
By the way, some people in the ColorOS community in China have similar symptoms.
Well in Beta 11, the phone detect my Sim Card, but i have no date mobile showing up even though i have my Operator setup appearing for MMS and 4G Data... Soits still a little problem.. i'm gonna flash Android Beta 11 then and hope for a second beta for Global version very soon...
EDIT : Beta 11 is really unusable ! The screen goes black and light up like crazy, multiples reboots, the phone gets warm as hell.... So no other choice than roll back to android Q, even if it means that i';ll not able tu use my Sim Card.... I can understand that a Beta may be buggy, but for this one, they really messed up !!
no sim card too
---------- Post added at 09:23 PM ---------- Previous post was at 09:22 PM ----------
no sim card too when rolling back 10. 2025 Global
no sim
I´ve got exactly the same problem...........
gregou said:
Well in Beta 11, the phone detect my Sim Card, but i have no date mobile showing up even though i have my Operator setup appearing for MMS and 4G Data... Soits still a little problem.. i'm gonna flash Android Beta 11 then and hope for a second beta for Global version very soon...
EDIT : Beta 11 is really unusable ! The screen goes black and light up like crazy, multiples reboots, the phone gets warm as hell.... So no other choice than roll back to android Q, even if it means that i';ll not able tu use my Sim Card.... I can understand that a Beta may be buggy, but for this one, they really messed up !!
Click to expand...
Click to collapse
I think we need to contact Oppo to ask them to release a rollback firmware specifically for others variants, but i'm afraid they'll tell us that they warn us that Beta 11 was just for the Cbinese model...
With the differences between the EU, Global variants, and software versions listed in the threads I've gone through, I am having trouble finding a guide that I am sure would be applicable to root my Oneplus 9 LE2117 11.2.5.5-LE54CB. (T-Mobile)(US)
My device is SIM unlocked, and the bootloader is unlocked, but I am unsure of the best method to root.
Could anyone point me in the right direction?
Follow the steps to install magisk.
Superguy said:
Follow the steps to install magisk.
Click to expand...
Click to collapse
Thanks for the response. I believe that's the last step I have to complete to be done, but that is where I seem to be getting lost. I can't find a boot image for the specific model and software numbers I have. From the threads I have read I think I could use the boot image for software version 11.2.2.2 but I am uncertain.
I went ahead and used the boot.img for 11.2.2.2 and it looks like it worked.
captain_howdy said:
With the differences between the EU, Global variants, and software versions listed in the threads I've gone through, I am having trouble finding a guide that I am sure would be applicable to root my Oneplus 9 LE2117 11.2.5.5-LE54CB. (T-Mobile)(US)
My device is SIM unlocked, and the bootloader is unlocked, but I am unsure of the best method to root.
Could anyone point me in the right direction?
Click to expand...
Click to collapse
You need 11.2.5.5 boot.img from any region. Then follow the instructions install magisk.
just use the AA image for tmobile. patch the image with magisk the file will go to your download file then fastboot boot the img file from the one get from magisk after patching and you will gain temp root. direct install with magisk and reboot. if you get into a bootloop. reset devices from recovery and you will still retain root after the reset. i have installed empty slot ota and direct install. bootlooped on ota empty slot but reset from recover fixed problem instantly and retained root. direct install no bootloop retained root.
Does anyone care to comment with insights or experiences in regards
to Rooting with Magisk which will allow for the installation on a Custom ROM at a later time -
that is, when a stable Lineage OS for example is available for the OP-9 (t-Mobile) ?
Thank You in Advance !
I doubt it but anything is possible. with the process to convert to different variants being fairly simple and accessible there will be very little focus on that particular software. It is compatible with gloabal pathched boot image to gain root and from there your pretty much able to customize to do what ever your heart desires.
Superguy said:
Follow the steps to install magisk.
Click to expand...
Click to collapse
Can you direct me where to find that ?
I'm having difficulties getting anything to work...
If you are on the latest Tmobile update,you can use 11.2.8.8.img from either AA,BA or DA. the boot.img are all the same.
Click to expand...
Click to collapse
I'm on 11.2.6.6.LE54CB - and I thought the end two letters were Important ?
avid_droid said:
Negative. Letters don't matter. The latest update from T-Mobile normally correlates with the latest of AA,BA,DA. If you are on the 11.2.6.6 it's 11.2.8.8. any of the boot.img will work.
Click to expand...
Click to collapse
See, the thing is, I was so accustomed to having an Un-Locked device from t-Mo, I didn't realize that the Awesome Dude who un-locks the SIM, does not actually un-lock the Phone. So Much Bull**** from t-Mo...
ANy-Hoo... I just applied thru the OP site to get my 9 completely un-locked.
Thank You for Your Time and Response!
avid_droid said:
Negative. Letters don't matter. The latest update from T-Mobile normally correlates with the latest of AA,BA,DA. If you are on the 11.2.6.6 it's 11.2.8.8. any of the boot.img will work.
Click to expand...
Click to collapse
Quick little bump, but I'm on 11.2.7.7.LE54CB. Has anything still changed or would I still be good to go to use the 11.2.8.8. boot.img to root or the latest 11.2.9.9.LE25AA from OnePlus's site directly?
I have managed to install the Eurepean 11.2.9.9.LE15BA for the 9 PRO le2117
I have the tmobile 9 5g version not the pro. camera doesnt pull up but otherwise runs fine
Need help here! I forgot to backup my oneplus 9 pro LE2127 when I tried to root my phone using TWRP,and I installed TWRP in my phone's boot partition which wiped out all data in that partition. I used TWRP side loaded Global ROM to recover my phone but the phone doesn't have any signal with sim card in. Used MSM tool backe to T-Mobile 11.2.5.5 and still same problem, sim card can be read but no signal. Flashed T-Mobile modem but modem b failed, it says no such partition.
Bought this phone from third party. Any suggestion is appreciated.
OnePlus 8 Verizon Bootloader is now unlockable. If anyone is installed Coloros on his op8 then please share you experience.
I'm doing it right now, for the fact. I'll attempt to install it and get back to you ASAP.
Update: Cellular data does not work for whatever reason. I'm pretty sure the Verizon variant just isn't compatible...
[email protected] said:
OnePlus 8 Verizon Bootloader is now unlockable. If anyone is installed Coloros on his op8 then please share you experience.
Click to expand...
Click to collapse
You can't even install it; I did exactly as the ColorOS guide suggested but the update still failed verification even though I was on the EU ROM. In any case, you won't be getting cellular data at all, likely because of the modem.img, and it's quite unoptimized.
Xryphon said:
You can't even install it; I did exactly as the ColorOS guide suggested but the update still failed verification even though I was on the EU ROM. In any case, you won't be getting cellular data at all, likely because of the modem.img, and it's quite unoptimized.
Click to expand...
Click to collapse
Thank alot bro. Please tell how you installed eu rom on your op8 Verizon. do eu rom works good on op8 Verizon?
[email protected] said:
Thank alot bro. Please tell how you installe gbd eu rom on your op8 Verizon. do eu rom works good on op8 Verizon?
Click to expand...
Click to collapse
I followed the conversion guide for the T - Mobile model that also works for the Verizon one. You also won't be getting cellular data if you switch to a global/ EU ROM. Other than that, it works fine.
Did you tired to relock your bootloader. I relocked my bootloader but its still showing device is not certified in play store.
[email protected] said:
Did you tired to relock your bootloader. I relocked my bootloader but its still showing device is not certified in play store.
Click to expand...
Click to collapse
I used MSMTool to restore; I'm not sure about the Google Play certification (I still get OTA updates from Verizon), so something is still working on my end.
Which msmtool you used Android 11 or 10?
Yes OTA is also working on my device.
[email protected] said:
Which msmtool you used Android 11 or 10?
Click to expand...
Click to collapse
I used the Android 11 one. We'll just have to wait until Verizon pushes the OOS 12 update (seems to be quite soon, as they recently released a security update).
Xryphon said:
I used the Android 11 one. We'll just have to wait until Verizon pushes the OOS 12 update (seems to be quite soon, as they recently released a security update).
Click to expand...
Click to collapse
Hope So.
Hello If I unlocked my Xiaomi 12 (CUPID) and managed to install TWRP, I have trouble understanding the suite to install Android 13 GLOBAL recovery (MIUI V13.0.4.0.TLCMIXM Stable Beta Official Update for Xiaomi 12 Global) Can someone post the procedure to install ANDROID 13 GLOBAL via TWRP on a CUPID XIAOMI 12; The, the answers, will benefit everyone here, Thank you
Pascal536 said:
Hello If I unlocked my Xiaomi 12 (CUPID) and managed to install TWRP, I have trouble understanding the suite to install Android 13 GLOBAL recovery (MIUI V13.0.4.0.TLCMIXM Stable Beta Official Update for Xiaomi 12 Global) Can someone post the procedure to install ANDROID 13 GLOBAL via TWRP on a CUPID XIAOMI 12; The, the answers, will benefit everyone here, Thank you
Click to expand...
Click to collapse
Twrp A12/wipe/format data type yes/reboot Twrp(Not mandatory but preferable.).
Put the recovery rom A13 at the root of the phone
then install Twrp A13*** : fastboot boot twrp.img
in Twrp go to Advanced - flash current TWRP.
Reboot Twrp flash rom
Use this TWRP https://androidfilehost.com/?w=files&flid=326450 A13
If too much bugs:
downgrade use Miflash https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
***Very recent may have one or more bugs
NOSS8 said:
Twrp A12/wipe/format data type yes/reboot Twrp(Not mandatory but preferable.).
Put the recovery rom A13 at the root of the phone
then install Twrp A13*** : fastboot boot twrp.img
in Twrp go to Advanced - flash current TWRP.
Reboot Twrp flash rom
Use this TWRP https://androidfilehost.com/?w=files&flid=326450 A13
If too much bugs:
downgrade use Miflash https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
***Very recent may have one or more bugs
Click to expand...
Click to collapse
Today i receive (MIUI V13.0.4.0.TLCMIXM Stable via OTA; Everything works well except when I insert my ORANGE SIM card (France). An app displays an error message and the phone reboots within 10 seconds. Without SIM card it works properly; well, it's still the main use of my phone. So I'm waiting for a new update from XIAOMI. PS: I don't have other SIMs from other operators to test.
Pascal536 said:
Today i receive (MIUI V13.0.4.0.TLCMIXM Stable via OTA; Everything works well except when I insert my ORANGE SIM card (France). An app displays an error message and the phone reboots within 10 seconds. Without SIM card it works properly; well, it's still the main use of my phone. So I'm waiting for a new update from XIAOMI. PS: I don't have other SIMs from other operators to test.
Click to expand...
Click to collapse
Try with the sim inside to reset network settings first then reboot.
Reset the phone
NOSS8 said:
Try with the sim inside to reset network settings first then reboot.
Reset the phone
Click to expand...
Click to collapse
I have reset Network of course and reset the phone too
Pascal536 said:
I have reset Network of course and reset the phone too
Click to expand...
Click to collapse
And the sim works on another phone?
in case send it back to garantie
13.0.4.0.TLCMIXM is a beta stable A13 (Xiaomi mess).
NOSS8 said:
And the sim works on another phone?
in case send it back to garantie
13.0.4.0.TLCMIXM is a beta stable A13 (Xiaomi mess).
Click to expand...
Click to collapse
Everything works well on Android 12, both Global and EEA
Pascal536 said:
Everything works well on Android 12, both Global and EEA
Click to expand...
Click to collapse
So your bootloader is unlocked.
Either ask orange to change your sim explaining the problem or downgrade you to A12.
I downgraded to Android 12, the phone works perfectly
And Orange is well able to ask me what ANDROID 13 is
Pascal536 said:
I downgraded to Android 12, the phone works perfectly
And Orange is well able to ask me what ANDROID 13 is
Click to expand...
Click to collapse
I'm not surprised, I see more of a rom problem than a sim problem. I had a problem on my Poco f2 pro with NRJ impossible to receive calls from Free fixed, it lasted 1 month of technical service in technical service, never find the reason for this problem, solution change operator.
BTW:Orange is expensive for what it provides.
NOSS8 said:
I'm not surprised, I see more of a rom problem than a sim problem. I had a problem on my Poco f2 pro with NRJ impossible to receive calls from Free fixed, it lasted 1 month of technical service in technical service, never find the reason for this problem, solution change operator.
BTW:Orange is expensive for what it provides.
Click to expand...
Click to collapse
Yes, I was quickly able to access SIM settings to observe Esim management. Finally it's a beta version, and the first
Pascal536 said:
Yes, I was quickly able to access SIM settings to observe Esim management. Finally it's a beta version, and the first
Click to expand...
Click to collapse
I don't believe it is Esim compatible
I have found this about Android 13 :
After installing Android 13, the phone force resets itself when the sim card is inserted.
my transactions;
1-soft/hard reset
2-image installation again
3-Different simcard trials (including different countries.) I live in Turkey.
4-I changed the preferred network type manually from the *#*#4636#*#* page. It worked until I turned off the phone myself, but when I turned the phone back on, I faced the Reset problem again.
What kind of problem do you think it could be and if you can think of anything for a solution, thank you.
-----------------------------------
you should try first;
1- without sim card inserted, you need to install android 13 in English.
2- If it gets better, you can continue to use English after the installation phase is over.
3- If it is not fixed, you can do the 1st and 2nd steps by flashing the radio file in the latest version of android 12.
You use a BETA VERSION.
The problem is the same on Google's pixels
Google's pixels phone A13?
Bug with A13
https://support.google.com/pixelpho...rkish-language-and-with-sim-card-placed?hl=en
XIAOMI 12 - Android 13 - System crashes in French language and with ORANGE SIM card placed
i update my mi12 to beta of a13, but i want rollback to android 12, how can i do this=?, without unlocking bootloader
AndroGeassX10 said:
i update my mi12 to beta of a13, but i want rollback to android 12, how can i do this=?, without unlocking bootloader
Click to expand...
Click to collapse
Not possible without unlocking bootloader.
I have to wait 14 days