set come with iccoming ok-outgoing problem
did hard reset-still same problem-so decide to flash-but after flash big problem
no incoming and outgoing
menu -mobile networks-network mode inactive-so """ni incoming/outgoping"""before flash it active
i tried below files for flashing
XT1526_SURNIA_ACG_LTE_5.1_LPI23.29-30_cid9_subsidy-DEFAULT_CFC.xml.zip
XT1526_SURNIA_REPW_5.1_LPI23.29-22-R.10_cid6_subsidy-REPUB_CFC.xml.zip
or any other way to active mobile networks?
can i flash NON-HLOS.bin from another version
OTUS_RETUAWS_5.0.2_LXC22.99-12_cid9_subsidy-DEFAULT_CFC.xml.zip
Try using the mvno slayer r4 zip file, that should get your connection working again
Sent from my XT1526 using Tapatalk
Related
I flashed my phone using Fusionideos 2.7 and now I have no mobile network. Ive tried entering the SPC and nothing happens. Im trying to reprogram the service and can't find a way to enter my MDN, MIN, PRL, to get my metro pcs service back. If any one happens to have an idea of what to enter to get to these or might have a Metro PCS stock rom for Huawei m835 i can flash back too it'll be highly appreciated. Ill even deal with a backup image of someone running FusionIdeos that is connected to the MetroPCS network.
Okay so I figured out how to get it back all I did was flash a higher firmware like gingerman 2.3 and then flashed to dronix which runs android 2.2.1 and that was it
Sent from my DroniX using XDA Premium App
After flashing latest cm9 build i begin to have no signal instead of the name of my network operator i try to enter airplane mode and exit it the signal sometimes return after about 10 minutes and remain but if phone hangs the signal is lost again tried to return to previous build via nandroid backup and returned and signal lost again so i entered airplane mode then exited and signal return after 10 minutes and remain afraid signal lost again tried nitrality said restored successful what can i do to make sure signal remain? i think latest build screwed signal somewhat
Sent from my GT-I9100 using xda app-developers app
Mohamedselim said:
After flashing latest cm9 build i begin to have no signal instead of the name of my network operator i try to enter airplane mode and exit it the signal sometimes return after about 10 minutes and remain but if phone hangs the signal is lost again tried to return to previous build via nandroid backup and returned and signal lost again so i entered airplane mode then exited and signal return after 10 minutes and remain afraid signal lost again tried nitrality said restored successful what can i do to make sure signal remain? i think latest build screwed signal somewhat
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
change your modem.
You can get modems here
how?
-download any modem that best suits your carrier/region
-boot to cwm recovery
-flash modem as normal zip
-reboot phone
problem solved
reboot phone
So recently I downloaded the cm12 nightly ROM on my Galaxy note 3 (sprint). Everything works fine, but I can't make/receive calls or text. I took it to the Sprint store and they told me to backup the ROM, then restore the backup of the stock ROM and do a profile update, then restore the custom ROM after that... Problem is that when I went back to the stock ROM I still had the problem, even after the profile update... this isn't my first time flashing ROMs, I've successfully flashed C-ROM and CM ROMs in the past and never came across this problem. Has anyone encountered a similar problem? And found a solution?
Odin stock tar file.
Ammar335i said:
So recently I downloaded the cm12 nightly ROM on my Galaxy note 3 (sprint). Everything works fine, but I can't make/receive calls or text. I took it to the Sprint store and they told me to backup the ROM, then restore the backup of the stock ROM and do a profile update, then restore the custom ROM after that... Problem is that when I went back to the stock ROM I still had the problem, even after the profile update... this isn't my first time flashing ROMs, I've successfully flashed C-ROM and CM ROMs in the past and never came across this problem. Has anyone encountered a similar problem? And found a solution?
Click to expand...
Click to collapse
What kernel are you using? You should be using the Stock CM12 Kernel with the same build date as your CM12 Install.
If you are running a different kernel on Official CM12 it will cause you to loose voice service. This issue started on April 03 2015 Nightly and hasn't been fixed yet.
What Radio/Baseband are you using? You should be on NH7 or NK4 when running CM12.
I will assume you are doing a clean install each time before flashing CM12 by performing a factory reset in recovery which wipes data, cache, and dalvik.
If you open up your dialer and dial *#*#4636#*#* it opens up a secret testing menu. Go to Phone Information and check if your "Set preferred network type:" is set as "LTE/CDMA". If it is not, do so and see if that changes anything.
Ammar335i said:
So recently I downloaded the cm12 nightly ROM on my Galaxy note 3 (sprint). Everything works fine, but I can't make/receive calls or text. I took it to the Sprint store and they told me to backup the ROM, then restore the backup of the stock ROM and do a profile update, then restore the custom ROM after that... Problem is that when I went back to the stock ROM I still had the problem, even after the profile update... this isn't my first time flashing ROMs, I've successfully flashed C-ROM and CM ROMs in the past and never came across this problem. Has anyone encountered a similar problem? And found a solution?
Click to expand...
Click to collapse
Sounds to me like you have bad download of CM12. I would download it again. Compare properties of both downloads see if you have the same number of bytes. Make sure you are rooted, stock OS, and a custom recovery installed. With the bootloader current binary and system status both having a "custom" status. Then try to flash CM12 through your custom recovery again. For more info just click flashing roms in my signature.
Get your carrier to check if your imei is blacklisted on their eir node connected to imeidb.org
Sent from my D5803 using XDA Free mobile app
rbeavers said:
Odin stock tar file.
Click to expand...
Click to collapse
Sorry I'm fairly new to this, you're gonna have to tell me how to find that
Sent from my SM-N9005 using XDA Free mobile app
Philux-X said:
What kernel are you using? You should be using the Stock CM12 Kernel with the same build date as your CM12 Install.
If you are running a different kernel on Official CM12 it will cause you to loose voice service. This issue started on April 03 2015 Nightly and hasn't been fixed yet.
What Radio/Baseband are you using? You should be on NH7 or NK4 when running CM12.
I will assume you are doing a clean install each time before flashing CM12 by performing a factory reset in recovery which wipes data, cache, and dalvik.
If you open up your dialer and dial *#*#4636#*#* it opens up a secret testing menu. Go to Phone Information and check if your "Set preferred network type:" is set as "LTE/CDMA". If it is not, do so and see if that changes anything.
Click to expand...
Click to collapse
I did the secret testing menu and changed the preferred network to LTE/CDMA and my calls started working and I started receiving sms (thank you). I can't send SMS though. Plus I lost data connectivity.
Also, I did do clean installs.
Sent from my SM-N9005 using XDA Free mobile app
Your on the wrong version of CM12. You need to be using hltespr. Your on hlte.
Download from here
http://download.cyanogenmod.org/?device=hltespr
Philux-X said:
Your on the wrong version of CM12. You need to be using hltespr. Your on hlte.
I tried downloading hltespr using TWRP but it kept saying unsuccessful, so I looked it up and others were having the same problem. So I switched to cwm recovery and it also said unsuccessful, and It gave the message saying that the ROM was hltespr and this device was hlte. Also all the other ROMs I downloaded in the past were all hlte and they worked fine.
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
The old versions might have worked, but the new ones will not because of telephony changes done by CM on April03. Its getting hung up on the device name from build.prop. At least that has been my experience in the past.
Do an advanced wipe. Data/System/Cache/Dalvik
Do a Reboot to recovery
Then flash hltespr.
I'm using TWRP 2.8.5 btw.
Other things to try if that does not work:
You can try flasing hltespr ontop of hlte and see if that works.
Try flashing ViSXN3N custom rom and then flash hltespr.
Philux-X said:
The old versions might have worked, but the new ones will not because of telephony changes done by CM on April03. Its getting hung up on the device name from build.prop. At least that has been my experience in the past.
Do an advanced wipe. Data/System/Cache/Dalvik
Do a Reboot to recovery
Then flash hltespr.
I'm using TWRP 2.8.5 btw.
Other things to try if that does not work:
You can try flasing hltespr ontop of hlte and see if that works.
Try flashing ViSXN3N custom rom and then flash hltespr.
Click to expand...
Click to collapse
Okay I'll try that now, what is ViSXN3N custom ROM? I can't find anything on it
Sent from my SM-N9005 using XDA Free mobile app
ViSXN3N is here
http://forum.xda-developers.com/showthread.php?t=2696396
Philux-X said:
ViSXN3N is here
http://forum.xda-developers.com/showthread.php?t=2696396
Click to expand...
Click to collapse
Same problem, it says that this is for sm-n900p hltespr and i have hlte... also i just noticed that the message i have on the bottom of my posts say sent from my Sm-N9005..? is my phone confused? lol
update
So I installed cm11 to see if it would work and it did... I guess that means it was just the ROM? Although I loved the interface of cm12, so im going to try and flash a different version to see if that works.
Turns out when I first rooted my phone I downloaded a hlte recovery. After flashing a hltespr recovery using Odin and then flashing the correct hltespr ROM, everything worked fine. Thanks for the help guys
Sent from my SM-N900P using XDA Free mobile app
I flashed my phone to a newer version of CM 12.1 that I found here:
http://android.cmphys.com/cyanogenmod-fireball/
it was an attempt to fix an issue with my data network. This build included a patch for the Fireball Radio. A few hours after the flash, I tried making a call. I have a signal but the phone says "Cellular network not available". I've restored a backup of the previous ROM, wiped cache and reseated the SIM. Still having the same problem. The phone is Straight Talk/Verizon using CDMA/LTE. Before I ditch the phone, is there anything else I can try? Would going back to stock ROM change anything? I've not touched baseband, etc unless they are port of the ROM I installed. I like the phone but I also need one that works.
Try returning to stock http://android.cmphys.com/stock-fireball/ or search for the ruu here to see if that helps. And make sure you have the most updated firmware 2.19.605.2.zip
Sent from my Nexus 7 WiFi using XDA Free mobile app
wmuflyer said:
Try returning to stock http://android.cmphys.com/stock-fireball/ or search for the ruu here to see if that helps. And make sure you have the most updated firmware 2.19.605.2.zip
Sent from my Nexus 7 WiFi using XDA Free mobile app
Click to expand...
Click to collapse
the phone is s-off boot loader unlocked and partition swapped. I know I have to reverse the partition swap. Do I need to relock bootloader, etc or will the stock ROM work after the partitions are swapped back?
Trying to update firmware, I am using these step
Reboot the device to HBOOT: adb reboot-bootloader
Enter the OEM update mode: fastboot oem rebootRUU
Flash the firmware package. cd to the directory containing fireball-firmware-2.19.605.2.zip and run:
fastboot flash zip fireball-firmware-2.19.605.2.zip
Wait for the process to finish
Reboot the phone: fastboot reboot
I get to step 2, and my laptop says it is waiting for device. am I supposed to do anything on the phone or just wait?
Just swapping partitions back should work.
Sent from my Nexus 7 WiFi using XDA Free mobile app
---------- Post added at 09:05 PM ---------- Previous post was at 09:04 PM ----------
Did you get stock recovery installed?
Sent from my Nexus 7 WiFi using XDA Free mobile app
wmuflyer said:
Just swapping partitions back should work.
Sent from my Nexus 7 WiFi using XDA Free mobile app
---------- Post added at 09:05 PM ---------- Previous post was at 09:04 PM ----------
Did you get stock recovery installed?
Sent from my Nexus 7 WiFi using XDA Free mobile app
Click to expand...
Click to collapse
Do I need stock recovery? I was hoping to just update the firmware and see if that fixes it. Do I need stock recovery to flash stock ROM and/or the firmware?
If I remember correctly the ruu command requires the stock recovery.
Sent from my Nexus 7 WiFi using XDA Free mobile app
wmuflyer said:
If I remember correctly the ruu command requires the stock recovery.
Sent from my Nexus 7 WiFi using XDA Free mobile app
Click to expand...
Click to collapse
ok thanks. I can;t hurt the phone any more than it already is.
I figured it out. I'm in Linux and had to su to root to get fastboot to flash anything. oddly, the reboot commands just fine when I'm not root.
So, were you successful getting your voice connection back?
Nexus 5 Chroma
No. And it doesn't appear I was successful at flashing firmware either. The phone still says I am version 1.5 I tried flashing stock recovery then repeating the firmware flash. I am going to be looking for a new phone today.
Gets another option to try http://forum.xda-developers.com/showthread.php?t=2759010
Sent from my Nexus 7 WiFi using XDA Free mobile app
I replaced the phone today. I am on call tonight and tomorrow and needed a working phone. I could use a land line but it would be painful. thanks for all the help. I spent some time on the phone last night with Verizon. I'm wondering if either they figured out the phone was unlocked or its just older so they flipped a bit somewhere to keep it from connecting. I could also try a GSM SIM and may keep the phone for if I ever travel international.
Yeah, Verizon is slightly fishy that way, on mine two days before my contract was up my LTE just stopped working. Good luck with the new phone.
Sent from my Nexus 7 WiFi
try
crokett said:
I flashed my phone to a newer version of CM 12.1 that I found here:
http://android.cmphys.com/cyanogenmod-fireball/
it was an attempt to fix an issue with my data network. This build included a patch for the Fireball Radio. A few hours after the flash, I tried making a call. I have a signal but the phone says "Cellular network not available". I've restored a backup of the previous ROM, wiped cache and reseated the SIM. Still having the same problem. The phone is Straight Talk/Verizon using CDMA/LTE. Before I ditch the phone, is there anything else I can try? Would going back to stock ROM change anything? I've not touched baseband, etc unless they are port of the ROM I installed. I like the phone but I also need one that works.
Click to expand...
Click to collapse
try this http://forum.xda-developers.com/showthread.php?t=2770176
just flashing
when im using custom roms i cant back up or restore whats app via jio 4g. its says you are on roaming. is there any option change that.