hi,
I dont know why i having this network issue.
I flashed lineage os8.1 on my phone and my sim isn't getting any signals. Yep o tried to wait for more than 2 hours, yep i tried different locations, yep my sim is working on other devices, yep i tried to put a different sim but all that didn't work. Mind you my wifi, gps, Bluetooth etc all are working. I tried to flash modem 1 and 2 with non-hlos etc but that didn't work either. So decided to flash stock firmware. Mind you i was on December security patch 2017, meaning having bootloader version 91.08. But since indian firmware flash file is 6.0.1, it won't be compatible, as the bootloader version cant be downgraded. So to get stock firmware back and running i decided to flash RETUS retail version. That firmware did have bootloader v91.08. But unfortunately, I'm getting bootloader remote failure errors, and phone gets into a bootloop. Then i decided to flash RETCN firmware. That did work, my phone is up and running but then again that my sim isn't showing ant signals. I tried with different sims. and dont know what to do.
Oh and one more thing, my imei is visible.
Please help me with this weird sim signal issue.
lazlow_og said:
hi,
I dont know why i having this network issue.
I flashed lineage os8.1 on my phone and my sim isn't getting any signals. Yep o tried to wait for more than 2 hours, yep i tried different locations, yep my sim is working on other devices, yep i tried to put a different sim but all that didn't work. Mind you my wifi, gps, Bluetooth etc all are working. I tried to flash modem 1 and 2 with non-hlos etc but that didn't work either. So decided to flash stock firmware. Mind you i was on December security patch 2017, meaning having bootloader version 91.08. But since indian firmware flash file is 6.0.1, it won't be compatible, as the bootloader version cant be downgraded. So to get stock firmware back and running i decided to flash RETUS retail version. That firmware did have bootloader v91.08. But unfortunately, I'm getting bootloader remote failure errors, and phone gets into a bootloop. Then i decided to flash RETCN firmware. That did work, my phone is up and running but then again that my sim isn't showing ant signals. I tried with different sims. and dont know what to do.
Oh and one more thing, my imei is visible.
Please help me with this weird sim signal issue.
Click to expand...
Click to collapse
Definitely you have flashed other region firmware with its own NON-HLOS.bi. so the solution is this that you have to flashed your own region firmware according to your bootloader version.
Faheem1234 said:
Definitely you have flashed other region firmware with its own NON-HLOS.bi. so the solution is this that you have to flashed your own region firmware according to your bootloader version.
Click to expand...
Click to collapse
But the issue is im on bootloader version 91.08, nougat 7.1.1 and my devide is RETIN and the only fiemware available for Indian moto z (RETIN) is 6.0.1
I dont know which firmware to flash to fix my issue
lazlow_og said:
But the issue is im on bootloader version 91.08, nougat 7.1.1 and my devide is RETIN and the only fiemware available for Indian moto z (RETIN) is 6.0.1
I dont know which firmware to flash to fix my issue
Click to expand...
Click to collapse
Yes my brother I also having the same problem. My device is also retin and I also had flash the same retus firmware in my device. Because there is no firmware available for India. The thing is go to the authorised Moto service centre and asked them to update your phone. Do not say about baseband ,even if you say they are going to do but they don't know what is baseband, so they will deny that bootloader is unlocked. Or wait for the Oreo update. It will fix up everything because it comes with everything updated. Only and only if you have retin software channel. But by the way can you tell me your baseband version."it is important to know for me and for you". You can check it out by seeing in about phone.
facing similar issue
Hi,
Were you able to solve the issue?
same issue here
any solution..pls share
kodo1 said:
any solution..pls share
Click to expand...
Click to collapse
The only thing which will work here is FLASH ANY CUSTOM ROM because no one can fix your problem. Not even Motorola.
And you will be surprised that I am the only one who solved this problem with stock rom. And dude it took a whole month.
Faheem1234 said:
The only thing which will work here is FLASH ANY CUSTOM ROM because no one can fix your problem. Not even Motorola.
And you will be surprised that I am the only one who solved this problem with stock rom. And dude it took a whole month.
Click to expand...
Click to collapse
Already use lineage 15.1 but signal still no luck..wifi and BT is okay.
Use *#*#4636#*#* mobile radio power off, tapping to turn ON..but it is back turning off
Related
I've got a Z5 Compact (E5803). My AT&T SIM works perfectly fine with it. I tried the E5823 Customized UK firmware (1298-5497 - 32.2.A.0.305_R13C) and the fingerprint works but the AT&T SIM does not. If the phone is on and I insert or eject the SIM it registers and reboots the phone. But otherwise it does not see the SIM. It keeps saying insert SIM.
I could try firmware after firmware but I thought it might be faster to ask here. I just want to use it with my AT&T SIM and have fingerprint working.
Maybe one of the other E5803 firmwares? I'm gonna trying Customized GEL until I hear from others..
imthenachoman said:
I've got a Z5 Compact (E5803). My AT&T SIM works perfectly fine with it. I tried the E5823 Customized UK firmware (1298-5497 - 32.2.A.0.305_R13C) and the fingerprint works but the AT&T SIM does not. If the phone is on and I insert or eject the SIM it registers and reboots the phone. But otherwise it does not see the SIM. It keeps saying insert SIM.
I could try firmware after firmware but I thought it might be faster to ask here. I just want to use it with my AT&T SIM and have fingerprint working.
Maybe one of the other E5803 firmwares? I'm gonna trying Customized GEL until I hear from others..
Click to expand...
Click to collapse
why would you use a firmware that is for E5823 and put it on E5803?
madshark2009 said:
why would you use a firmware that is for E5823 and put it on E5803?
Click to expand...
Click to collapse
For fingerprint? I had asked on another post and someone said I could since the hardware for the two is the same. I'm using the Australian firmware for the E5823 and it seems to be working...
imthenachoman said:
For fingerprint? I had asked on another post and someone said I could since the hardware for the two is the same. I'm using the Australian firmware for the E5823 and it seems to be working...
Click to expand...
Click to collapse
i dont get it ... they both come with fingerprint scanner button , why would you install another firmware to use it, makes no sense? am I missing some thing?
madshark2009 said:
i dont get it ... they both come with fingerprint scanner button , why would you install another firmware to use it, makes no sense? am I missing some thing?
Click to expand...
Click to collapse
Yes, due to legal issues Sony intentionally disabled the fingerprint scanner in the USA firmware version. The fingerprint scanner is physically there though so if you flash another FW it may work. However I am currently having difficulty getting my SIM card to be recognized when I flash to the newest UK version of the E8523
slim150 said:
Yes, due to legal issues Sony intentionally disabled the fingerprint scanner in the USA firmware version. The fingerprint scanner is physically there though so if you flash another FW it may work. However I am currently having difficulty getting my SIM card to be recognized when I flash to the newest UK version of the E8523
Click to expand...
Click to collapse
I was having the same issue. I used the Australian (Customized AU) and it started working.
imthenachoman said:
I was having the same issue. I used the Australian (Customized AU) and it started working.
Click to expand...
Click to collapse
I am getting a E5803, and I live in Australia. Can I easily use Xperifirm and flash the Customized AU on the E5803? I really want the AU baseband/modem.
slim150 said:
Yes, due to legal issues Sony intentionally disabled the fingerprint scanner in the USA firmware version. The fingerprint scanner is physically there though so if you flash another FW it may work. However I am currently having difficulty getting my SIM card to be recognized when I flash to the newest UK version of the E8523
Click to expand...
Click to collapse
I also have a US version of the phone (E5803) and also wanted to enable the fingerprint scanner. When I loaded the latest UK version (which is E5823), my SIM (Canadian) was not detected. Bluetooth would also continuously toggle off and on. I'd never tried loading firmware from the other model before, so I just assumed E5803 and E5823 couldn't be mixed. If the AU version works for you, I guess the limitation isn't necessarily the phone model.
Previously I was running Android 6 from the Customized SG (Singapore), and now Android 7 from Customized MY (Malaysia), and both seem to work fine.
The AU version ended up working for me and I haven't looked back since
my e5803 fingerprint scanner works perfect on 7
I have a similar question: just got a Z5c E8523 but using it in the US with AT&T - which firmware should I be using? Customized UK, Customized AUS? Do I still need to flash the MODEM and BASEBAND portions from a US firmware?
Thanks!
If your model number is E5823, the fingerprint sensor should work without any modification. If it is E5803, you'll have to compile or flash a E5823 with any firmware except US. In my personal experience, the AU firmware typically receives firmware updates the fastest.
I have a similar question: just got a Z5c E8523 but using it in the US with AT&T - which firmware should I be using? Customized UK, Customized AUS? Do I still need to flash the MODEM and BASEBAND portions from a US firmware?
Click to expand...
Click to collapse
Okay, so I can't get it to work. I spent all morning trying to get Flashtool to work.
I am trying to flash E5823_32.2.A.5.11_Australia_Generic on my E5803. Each time I get a ERROR - Can't read a byte value.
I initially tried the latest version of Flashtool 0.9.23.2. Then I tried 0.9.18.6 where bricked the device. I then tried 0.9.22.2. Still no luck. I had to re-flash the Customized US version that came with the phone (E5803_32.2.A.5.11_1298-3109).
Should I try flashing the Customized UK version first then try the AU version? Very annoying tbh
Wow, got there in the end (only took me half the day).
After the successful flash of E5803_32.2.A.5.11_1298-3109 after bricking the phone, I tried to flash Customized AU 32.3.A.0.376 / R2D . That one also bricked the phone due to the old version of Flashtool I was using (0.9.22.2). I then tried to flash E5823_32.2.A.5.11_Australia_Generic which now worked.
The main reason I wanted the AU version was for the Baseband... Turns out it was the same lol
you should be able to keep the same modem settings, and the phone should be able to switch configurations when it detects the appropriate bands... provided your carrier is operating at those frequencies.
Wiingy said:
Wow, got there in the end (only took me half the day).
After the successful flash of E5803_32.2.A.5.11_1298-3109 after bricking the phone, I tried to flash Customized AU 32.3.A.0.376 / R2D . That one also bricked the phone due to the old version of Flashtool I was using (0.9.22.2). I then tried to flash E5823_32.2.A.5.11_Australia_Generic which now worked.
The main reason I wanted the AU version was for the Baseband... Turns out it was the same lol
Click to expand...
Click to collapse
Don't you have to do something like make the phone think it's a E5823 in build prop first?
Hi there, I recently bought an Z5C (E5803) that was on android 6.1 marshmallow and was Customized Movistar EC, wich is one of my country´s carrier, so 7.0 OTA is long long wait to come.
Long story sort, I used Xperifirm and got 32.3.A.0.376 Customized US for the E5803, flashed and the fingerprint sensor was gone. So I read a little and find out that in US there is no Fingerprint suport for del Z5C.
Then I flashed 32.3.A.0.376 Customized GEL for E5803 and bingo!! Fingerprint sensor worked again.
I don´t think you have to change the firmware for another model for the fingerprint sensor to work.
Hope this help.
Hello there, this is my first time posting here.
I have a Samsung Galaxy S6 edge (SM-G925I) (TTT Firmware). After updating it to Marshmallow, the phone worked well.
Suddenly, one day, I can't connect to network, can't make calls and can't even connect to 4G/3G/2G.
I am aware of the solutions that have been already posted as:
-Search automatically for network
-Flash Stock ROM Firmware from Sammobile
-Backup/Restore EFS
IMEI and Serial Numbers seem to be the same as on the back of the phone and the phone recognizes the SIM as it shows contacts.
I have already sent it once for repair to some guy, and the phone came with a Movistar ROM 5.1.1 (OJ6), which I didn't like, but surprisingly the Network worked.
I decided to flash my stock firmware, as I didn't want to be stuck in Lollipop, but now the network won't work again.
I would appreciate your help on how to fix this. I have been able to root Marshmallow successfully and I am ready to apply a solution.
Proud owner of G925I running Alexis Rom. Change the sim card...its metal part has damaged and you will be good to go.
Indranuj Kar said:
Proud owner of G925I running Alexis Rom. Change the sim card...its metal part has damaged and you will be good to go.
Click to expand...
Click to collapse
I apologize for not mentioning earlier, but it perhaps isn't a hardware issue, as my SIM works on other phones, as other SIMs won't connect in mine.
What is the OS version you are running now?
Indranuj Kar said:
What is the OS version you are running now?
Click to expand...
Click to collapse
Currently Android 6.0.1 MM. I flashed 5.1.1 to test before, but no luck.
Would suggest you to switch to MM. And also to go to service center to fix up the device. It might be a hardware issue. Also tell the service center guys you need MM on this and not Lollypop
mine G925I only works on LTE only mode.
cant able to call.
Hello!
I need to fix this issue it's ****ing annoying to be honest. So I have an ATT S9+ and after the Pie update my phone NEVER HAS FULL SIGNAL! I've even went as far as standing under the cell tower and nothing. I was on the CS7 and updated to the CS8 via Odin and the problem PERSISTS! When I was on Oreo I didn't have this issue, this problem started right after I upgraded to Pie.
I'm want to Downgrade or switch this one to TMB but I'm afraid of tripping knox or locking the phone to TMB. (It's code unlocked).
I really want to fix this issue. It's very annoying.
I know your frustrated but the answer won't change if you make a new thread asking the same thing as your old one...
Also standing under the cell tower won't give you realistic results. While capable of sending/recieving signals in a wide area they are not aimed at (or pointing) downwards at the tower base.
Flashing from G965U firmware to G965U1 firmware will not trip knox at all because your flashing official firmware files. I myself have gone from Sprint firmware to the unlocked firmware (G965U1) and to Tmobile firmware without any knox issues.
As for downgrading this is where your out of luck unfortunately. Downgrading is not possible because of the bootloader version your using. Specifically CSC8 uses bootloader version 4 and the last oreo release uses bootloader version 3.
You can only flash firmware that has a bootloader version that is the same (or higher) then what is installed on your phone.
TBH I would contact your cellular provider and ask them to look into the issue. Maybe they can do something to help resolve your issue.
scottusa2008 said:
I know your frustrated but the answer won't change if you make a new thread asking the same thing as your old one...
Also standing under the cell tower won't give you realistic results. While capable of sending/recieving signals in a wide area they are not aimed at (or pointing) downwards at the tower base.
Flashing from G965U firmware to G965U1 firmware will not trip knox at all because your flashing official firmware files. I myself have gone from Sprint firmware to the unlocked firmware (G965U1) and to Tmobile firmware without any knox issues.
As for downgrading this is where your out of luck unfortunately. Downgrading is not possible because of the bootloader version your using. Specifically CSC8 uses bootloader version 4 and the last oreo release uses bootloader version 3.
You can only flash firmware that has a bootloader version that is the same (or higher) then what is installed on your phone.
TBH I would contact your cellular provider and ask them to look into the issue. Maybe they can do something to help resolve your issue.
Click to expand...
Click to collapse
Hey! Thank you for the info! I tried with another sim card from another carrier but the issue remained. I'm going to try to flash everything again with another version of odin and uncheck the auto-reboot option so that I can factory reset from the recovery after its done.
scottusa2008 said:
I know your frustrated but the answer won't change if you make a new thread asking the same thing as your old one...
Also standing under the cell tower won't give you realistic results. While capable of sending/recieving signals in a wide area they are not aimed at (or pointing) downwards at the tower base.
Flashing from G965U firmware to G965U1 firmware will not trip knox at all because your flashing official firmware files. I myself have gone from Sprint firmware to the unlocked firmware (G965U1) and to Tmobile firmware without any knox issues.
As for downgrading this is where your out of luck unfortunately. Downgrading is not possible because of the bootloader version your using. Specifically CSC8 uses bootloader version 4 and the last oreo release uses bootloader version 3.
You can only flash firmware that has a bootloader version that is the same (or higher) then what is installed on your phone.
TBH I would contact your cellular provider and ask them to look into the issue. Maybe they can do something to help resolve your issue.
Click to expand...
Click to collapse
By any chance, do you know where I can find the stock ATT files? I can't find the anywhere.
Pigoath said:
By any chance, do you know where I can find the stock ATT files? I can't find the anywhere.
Click to expand...
Click to collapse
Sorry unfortunately I do not. I haven't been able to find them myself when I used my S9+ on AT&T before switching to T-Mobile...
When I was with AT&T I had just used the G965U1 firmware since I would not have gotten access to any VoLTE and etc that required an AT&T whitelisted IMEI (to be provisioned for the features) and my phone wasn't an AT&T branded phone (since it was originally from Sprint).
Hey guys, i've come across some bugs while installing the RMX1921EX_11_C.02 version from the Indian site to my phone and i would like some clarifications or help if someone faced those and overcame them.
- To begin with let me start by saying that I bought a global Realme XT with the firmware being RMX1921EX_11_A.05.
- I then managed to brick cyclops the device by trying to install RMX1921EX_11_A.10. Phone wouldn't boot, stuck on the Realme black/white logo.
- I managed to install RMX1921EX_11_A.06 through recovery and sd card.
- Then I downloaded from the Indian support site and installed through file manager the version RMX1921EX_11_C.02.
Now, on this version everything seems to work ok minus some bugs:
- Phone gets a bit laggy sometimes
- Brightness in automatic mode is not working
- Software update through settings won't work. Crashes a while after opening
- Battery life seems affected, won't last anyway near to what it was on RMX1921EX_11_A.05
So my question is, has anyone experienced any of those and found a solution to the bugs?
Also, is there anyway to obtain and roll back to the original stock rom RMX1921EX_11_A.05 from the beginning and then wait for the official OTA update?
Thank you in advance
Are you sure your phone firmware is RMX1921EX_11_A.05. (India version) not RMX1921EUEX (global version)?
If your firmware is India version, you should be able to unlock the bootloader and install twrp.
donkeyman1234 said:
Are you sure your phone firmware is RMX1921EX_11_A.05. (India version) not RMX1921EUEX (global version)?
If your firmware is India version, you should be able to unlock the bootloader and install twrp.
Click to expand...
Click to collapse
Yes, absolutely sure but im confused as RMX1921EX_11_A.05. is supposed to India version which my phone had but then the place i bought it was advertised as the global version and also i didn't receive the official ota update through the phone's update settings (and supposedly having the indian version). Seriously, realme's firmware naming and distribution is so confusing and impractical. but let's say i indee have the indian version, what does unlocking the bootloader and installing twrp mean? how will that help me and are there any cons into doing that? Thanks man
unlock the bootloader you can root the phone
https://forum.xda-developers.com/re...ecovery-unofficial-twrp-realme-5-pro-t3985459
My XT is was some as the global version. But from what I'm reading this says I'm using the Indian version? But I have NFC. This is so confusing. Bought this phone thinking I could unlock and root.
This confusing but normal. I bought two EU phones with NFC. One for me and one for my girlfriend. She is still on RMX1921EX_11_A.05.
I updatet my Phone to A.06 and when i look in phonedetails is called RMX1921EX_11_A.06.
I read that A.05 can be unlocked in the other thread. I would test this by myself, but yeah i don't want drama with my girlsfriends phone.
So i don't touch it
schwatter said:
This confusing but normal. I bought two EU phones with NFC. One for me and one for my girlfriend. She is still on RMX1921EX_11_A.05.
I updatet my Phone to A.06 and when i look in phonedetails is called RMX1921EX_11_A.06.
I read that A.05 can be unlocked in the other thread. I would test this by myself, but yeah i don't want drama with my girlsfriends phone.
So i don't touch it
Click to expand...
Click to collapse
India version comes with no NFC. You can try Depth test apk , it won't hurt your phone even you pass it. Let us know if your global version can pass it or not.
mario0788 said:
Hey guys, i've come across some bugs while installing the RMX1921EX_11_C.02 version from the Indian site to my phone and i would like some clarifications or help if someone faced those and overcame them.
- To begin with let me start by saying that I bought a global Realme XT with the firmware being RMX1921EX_11_A.05.
- I then managed to brick cyclops the device by trying to install RMX1921EX_11_A.10. Phone wouldn't boot, stuck on the Realme black/white logo.
- I managed to install RMX1921EX_11_A.06 through recovery and sd card.
- Then I downloaded from the Indian support site and installed through file manager the version RMX1921EX_11_C.02.
Now, on this version everything seems to work ok minus some bugs:
- Phone gets a bit laggy sometimes
- Brightness in automatic mode is not working
- Software update through settings won't work. Crashes a while after opening
- Battery life seems affected, won't last anyway near to what it was on RMX1921EX_11_A.05
So my question is, has anyone experienced any of those and found a solution to the bugs?
Also, is there anyway to obtain and roll back to the original stock rom RMX1921EX_11_A.05 from the beginning and then wait for the official OTA update?
Thank you in advance
Click to expand...
Click to collapse
Try this post
https://forum.xda-developers.com/realme-xt/help/realme-ui-bugs-eu-device-t4076145
donkeyman1234 said:
Try this post
https://forum.xda-developers.com/realme-xt/help/realme-ui-bugs-eu-device-t4076145
Click to expand...
Click to collapse
Brother I sincerely thank you for point out that to me!! Much appreciated!!
I bought a second hand Xperia 1 iii A101so in Pakistan. The phone has serious network connectivity issues after updating to Android 12 lastest update the phone even stops to connect to carrier. I just tried many solution but no improvement. Being a novice i planned to update it with global ROM as mostly on internet people were getting rid of signal issues with flashing Global FW. Not knowing the global ROM are desinged for Dual SIMs, I just updated my A101So with XQ-BC52 using newflasher tool and it worked. After installation there was no connectivity and even no signal was discovered by my phone. I searched again and found that global FW only works on dual model. Then i thought of flashing it again to go back to A101SO but phone is not flashing and showing "Device is Corrupted and Cannot Be Trusted Error" . I tried repairing with Xperia companion but it did not workout. Now i flashed Global XQ-BC52 agan and it working again. I need following help:
1) how can i downgrade my xperia 1-iii to Android 12 with its original stock A101so ROM ?
2) how can i resolve the singal issues on A101SO? can i patch gobal mdem files to A101So to get rid of signal issues?
Currently XQ-BC52 global FW is running on my device with no mobile connectivity. expect that the phone is showing full functionality.
Looking forward to help in this regards
crazycolor786 said:
I bought a second hand Xperia 1 iii A101so in Pakistan. The phone has serious network connectivity issues after updating to Android 12 lastest update the phone even stops to connect to carrier. I just tried many solution but no improvement. Being a novice i planned to update it with global ROM as mostly on internet people were getting rid of signal issues with flashing Global FW. Not knowing the global ROM are desinged for Dual SIMs, I just updated my A101So with XQ-BC52 using newflasher tool and it worked. After installation there was no connectivity and even no signal was discovered by my phone. I searched again and found that global FW only works on dual model. Then i thought of flashing it again to go back to A101SO but phone is not flashing and showing "Device is Corrupted and Cannot Be Trusted Error" . I tried repairing with Xperia companion but it did not workout. Now i flashed Global XQ-BC52 agan and it working again. I need following help:
1) how can i downgrade my xperia 1-iii to Android 12 with its original stock A101so ROM ?
2) how can i resolve the singal issues on A101SO? can i patch gobal mdem files to A101So to get rid of signal issues?
Currently XQ-BC52 global FW is running on my device with no mobile connectivity. expect that the phone is showing full functionality.
Looking forward to help in this regards
Click to expand...
Click to collapse
see this thread https://forum.xda-developers.com/t/...ssues-downgrading-after-a-crossflash.4570707/
Hi bro. I was going to buy this device. Should I go for it. ? Or maslay Hain?
connectwithjalal said:
Hi bro. I was going to buy this device. Should I go for it. ? Or maslay Hain?
Click to expand...
Click to collapse
Better not to buy was after Android 13 update it stopped to detect the network signals.
Which model of Xperia 1 III is safe to buy in Pak ? And some models have very less PTA tax right ?
crazycolor786 said:
Better not to buy was after Android 13 update it stopped to detect the network signals.
Click to expand...
Click to collapse
Which model of Xperia 1 III is safe to buy in Pak ?
Shuaib_Ahsan said:
Which model of Xperia 1 III is safe to buy in Pak ?
Click to expand...
Click to collapse
I think mostly are importing A101SO from Japan the bad thing about them is that they bootloader are hardlocked. you cant even intall a custom rom there. better not to risk any money.
crazycolor786 said:
I think mostly are importing A101SO from Japan the bad thing about them is that they bootloader are hardlocked. you cant even intall a custom rom there. better not to risk any money.
Click to expand...
Click to collapse
Ok, any good alternative with good camera you have come across for Pak ?
pixel 6 pro is good