Hi,
i tried to flash cm 10.2 on my photon Q today.
I had the latest official rom working for half a year but i was missing some features i couldnt get with stock.
Anyway its a simcard modded unit i use in germany i was running stock jellybean (rooted, motochopper method) until today.
First i unlocked the boatloader, flashed latest open recovery and then flashed CM10.2 latest nightly (GSM) + gapps, after that i did a factory reset with open recovery.
After i configured the new firmware i noticed that i had no gsm, it didnt even ask for the pin of my locked card. I tried to switch from CDMA to GSM but with no effect. I also tried several reboots but i couldnt change the mobile network or get gsm to work.
I then tried to flash the latest cm snapshot but it doesnt work as well, the only difference is that the phone service always crashes when i try to change the network method.
Doesn anyone else have a idea? The thing is currently useless to me...
Thanks in advance.
Sonic-NKT said:
Hi,
i tried to flash cm 10.2 on my photon Q today.
I had the latest official rom working for half a year but i was missing some features i couldnt get with stock.
Anyway its a simcard modded unit i use in germany i was running stock jellybean (rooted, motochopper method) until today.
First i unlocked the boatloader, flashed latest open recovery and then flashed CM10.2 latest nightly (GSM) + gapps, after that i did a factory reset with open recovery.
After i configured the new firmware i noticed that i had no gsm, it didnt even ask for the pin of my locked card. I tried to switch from CDMA to GSM but with no effect. I also tried several reboots but i couldnt change the mobile network or get gsm to work.
I then tried to flash the latest cm snapshot but it doesnt work as well, the only difference is that the phone service always crashes when i try to change the network method.
Doesn anyone else have a idea? The thing is currently useless to me...
Thanks in advance.
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?p=47978878#post47978878
i looked at the build.prop and those options except:
ro.telephony.default_network=3
dont appear in the file...
Also this talks about GSM Data problem, i cant even do phonecalls/sms, its not even asking for my sim code..
I then tried to flash back to stock but now RSD Lite 6.1.5 wont show my device... (all drivers installed).
Im really getting frustrated.
EDIT:
ok tried another PC with Win7 (mine runs 8.1) and now RSD Lite seems to work
Update: Now back to stock... GSM Works fine after i activated it... i now try to reflash cm10.2 and see what happens
Ok its working now
everything out of the box...
i dont know what went wrong the first time cause i did exactly the same as far as i know...
Sonic-NKT said:
i looked at the build.prop and those options except:
ro.telephony.default_network=3
dont appear in the file...
Click to expand...
Click to collapse
Indeed this line was likely the relevant one
If missing just add it.
Related
Ok so the problem i am having is i am unable to get wifi to work without the phone saying error next to wifi. My One S has the lastest radio and HBOOT 1.06. So i understand that i do not need to flash the boot.img from fastboot, but i still do to make sure that it is flashing ok. That does not fix the problem. I have even used the stock T-MO nanodroid to go back to stock rom and i still flash the boot.img file from fastboot still not wifi. Everything on the phone works fine but wifi. After the phone boots up wifi is already on and it does scan and see networks. When i try to connect to one it doesn't connect, if i toggle wifi off and turn it back on again it gives me a error when turning wifi on. Only thing i am wondering is, i do not have a SIM CARD in the phone right now since i do not have a micro sim right now. Does the phone need a SIM CARD in it for wifi to work. I spent 3 hours last night flashing different roms and boot.imgs trying to get wifi to work. All with errors still. Anything ideas right now would be great.
edit: forgot to add when i flash the boot.img in fastboot i always get a finished with no errors as if the boot.img is flashing fine.
wifi problem
I just pulled my sim from my One s and found i had no problem with the wifi connection. What kind of error is it, do you have any code?
No code. If I do a full wipe the wifi scans for a network sees them but does not connect. Then it will turn off on its own and just say error next to the on and off button. It does it with every rom and kernel combo I have tried. Even going to back to the full stock rom it does it. I know the kernel is flashing since it shows the right kernel under about.
Sent from my Galaxy Nexus using Tapatalk 2
i've encountered the same issue, but only when i flashed an overclocked kernel. and when i flashed the kernel back the error went away. have you tried unrooting?
I was looking for a full stock unrooted rom and but couldn't find anything other then a nanodroid of stock rooted. I was thinking of just flashing the ruu and seeing if that fixes it. Not sure at this point because I have tried every kernel and rom all which do not work so far. I have also formated everything thinking maybe something was left behind no go as well. I know wifi works since I used the phone for a few days before I Dev unlocked it and rooted it. I also setup the phone on wifi with no sim card when I pulled it out of the box at the start. Something happen after the unlock and rooting part. Could updating the hboot help at all.
Sent from my Galaxy Nexus using Tapatalk 2
I fixed it. I flashed the TMO 1.84 RUU and wifi is working again. It updated the HBOOT to 1.09 and everything is stock with working wifi. I am starting all over to see if i can get it working with a rom as well now.
I searched around and couldn't find a definitive answer. The problem I'm having is connecting to wifi at all.
After getting a phone replacement, I unlocked the bootloader, flashed CWM recovery, rooted, flashed CM 10 nightly 09/29 and GApps but when I booted, I could not connect to wifi at all...I can't even turn on wifi because the toggle is greyed out. I have tried reflashing several times and even tried a different rom. but still no luck. Anyone else have this problem or know how I can fix it? I rely heavily on wifi because of ****ty data in my dorm. Any help would be much appreciated!
jaker.the.skater said:
I searched around and couldn't find a definitive answer. The problem I'm having is connecting to wifi at all.
After getting a phone replacement, I unlocked the bootloader, flashed CWM recovery, rooted, flashed CM 10 nightly 09/29 and GApps but when I booted, I could not connect to wifi at all...I can't even turn on wifi because the toggle is greyed out. I have tried reflashing several times and even tried a different rom. but still no luck. Anyone else have this problem or know how I can fix it? I rely heavily on wifi because of ****ty data in my dorm. Any help would be much appreciated!
Click to expand...
Click to collapse
Hello,
What was the version of software on you phone before rooting, was it a T-Mobile phone? The newest version for T-Mobile has created is issues for roms that aren't the same version.
Rsotbiemrptson
Sent from my Nexus 7 using xda premium
Yep, just found out that was the issue. kinda sucks because I'd rather have jelly bean! Oh well guess I'll deal with no wifi till a fix comes out.
why does the Ruu not work anymore i want to take my phone back to where the wifi works..... i have a cwm backup from before the update but that did not even fix the problem
____EDIT____
Well i got the wifi back. ( and the OTA update ? again )
Relocked the phone boot loader
I opened the RUU
took the Rom.zip from the folder.
took the stock recovery img
flashed the stock recovery img
start the phone back up
downloaded the update again. ( 4.0.4 )
did all the waiting etc
phone powers down reboots applies the updates to it self.
powers back up updating completed
WIFI WORKING.
go to try and do the ruu.exe again but no it says error 140( i think ) wrong bootloader version.
This update changes the bootloader to version 1.14___ So now the phone is non tamperd and says relocked so back to stock ( YAY )(((for now))))( i think lol )
Most importantly the Wifi is working.
If anyone wants i can take and give the files from the RUU ( not the whole zip but what ever img's you want from it ) Just send me a PM i will mail it to ya.
YousufWalton said:
why does the Ruu not work anymore i want to take my phone back to where the wifi works..... i have a cwm backup from before the update but that did not even fix the problem
____EDIT____
Well i got the wifi back. ( and the OTA update ? again )
Relocked the phone boot loader
I opened the RUU
took the Rom.zip from the folder.
took the stock recovery img
flashed the stock recovery img
start the phone back up
downloaded the update again. ( 4.0.4 )
did all the waiting etc
phone powers down reboots applies the updates to it self.
powers back up updating completed
WIFI WORKING.
go to try and do the ruu.exe again but no it says error 140( i think ) wrong bootloader version.
This update changes the bootloader to version 1.14___ So now the phone is non tamperd and says relocked so back to stock ( YAY )(((for now))))( i think lol )
Most importantly the Wifi is working.
If anyone wants i can take and give the files from the RUU ( not the whole zip but what ever img's you want from it ) Just send me a PM i will mail it to ya.
Click to expand...
Click to collapse
So did you use the 1.84 ruu? And you did this after applying the tmobile ota?
Please bare with me since this is the first time having to post for an issue since I usually find an answer on your forums
So here's the situation.
I bought the photon q 4g lte from ebay and it came with the unlocked bootloader.
Needless to say it was with the stock ics and i tried to find a jellybean update because it wasn't taking the ota and ended up going with cyanogen since i had no problems before. However those phones i had before were with sim cards not cdma.
I found out i couldn't update prl or profile manually without having to do something on the pc.
So after searching left and right i found i could use rsl lite (I used 6.1.5) and eventually found the "stock" file from this post
http://forum.xda-developers.com/showthread.php?t=2095536&highlight=rsd+lite
I did the stock jellybean, got it to go through the process and it booted up with no errors.
However, when it boots into the os it pops up a force close on omadmclient_sprint_dataservice and eventually also on the process com.android.phone.
I tried putting it in airplane mode to see if the service error would go away but it didn't work for the process part crashing.
I tried re-flashing, deleting cache in recovery, doing a data/factory reset in recovery and the one time i was able to do a data factory reset within the settings menu.
I could not find anyone that said they had a rom that worked with sprint and updating prl within the rom, if anyone knows of one let me know and i will flash it through rsd.
Otherwise does anyone have an idea of what could be happening because googling the omadmclient part did not pull up anything specific and pulling up the process issue for other phones has not helped me either.
Was this a hacked GSM phone, or are you using it as CDMA?
I've never heard of people having FC issues after flashing a FXZ from RSD. Which one did you flash? Android 4.1.2 - Sprint US - 9.8.2Q-122_XT897_FFW-5 (No simlock) ?
If you are on stock, you should be able to update the PRL within the ROM.
I was trying to use it with cdma network through sprint. and yeah that was the file i downloaded, had to remove the getvar to get it working but flashed with no errors after doing that.
As for updating the prl i can barely navigate through the phone, there is no home page loading and the process pop comes up often enough that its hard to go through the settings
crispy6 said:
I was trying to use it with cdma network through sprint. and yeah that was the file i downloaded, had to remove the getvar to get it working but flashed with no errors after doing that.
As for updating the prl i can barely navigate through the phone, there is no home page loading and the process pop comes up often enough that its hard to go through the settings
Click to expand...
Click to collapse
Sounds like something went wrong mate. Are you already activated on Sprint? I don't know if that would matter, it might.
I would honestly redownload and redo the RSD process.
arrrghhh said:
Sounds like something went wrong mate. Are you already activated on Sprint? I don't know if that would matter, it might.
I would honestly redownload and redo the RSD process.
Click to expand...
Click to collapse
I originally tried to activate the phone through cyanogen and then when the rep said he couldnt do it because of the lack of prl to update within the rom we just setup the activation back on the old phone/ That phone is working on the network.
I re-downloaded the file just in case and re-flashed but same problem. The only thing i thought of was maybe updating the radio but since its a stock rom it should work out of the gate. whats also weird is i tried turning wifi on but it didnt work either.
Anychange you know of a rom that works with sprint. I dont care if its stock since i would probably root later again.
crispy6 said:
I originally tried to activate the phone through cyanogen and then when the rep said he couldnt do it because of the lack of prl to update within the rom we just setup the activation back on the old phone/ That phone is working on the network.
I re-downloaded the file just in case and re-flashed but same problem. The only thing i thought of was maybe updating the radio but since its a stock rom it should work out of the gate. whats also weird is i tried turning wifi on but it didnt work either.
Anychange you know of a rom that works with sprint. I dont care if its stock since i would probably root later again.
Click to expand...
Click to collapse
Which one are you flashing?
Try another perhaps...? I honestly have never heard of this. It sounds like the phone might be damaged, or the RSD process just did not flash correctly.
I guess I should ask, was the phone modified at all for the GSM SIM slot mod? I wonder if having a non-Sprint SIM in is messing with it... That is just a shot in the dark.
arrrghhh said:
Which one are you flashing?
Try another perhaps...? I honestly have never heard of this. It sounds like the phone might be damaged, or the RSD process just did not flash correctly.
I guess I should ask, was the phone modified at all for the GSM SIM slot mod? I wonder if having a non-Sprint SIM in is messing with it... That is just a shot in the dark.
Click to expand...
Click to collapse
so far the only rom i tried was 10.1 cyanogen and the stock rom for jellybean. However for the stock rom it doesnt let me downgrade to ics with rsd 6.1.5 do you think if i downloaded an old version i could downgrade to a lower stock rom?
Also I honestly had not looked for the cdma roms since most of what i saw was troubleshooting related for this phone but i just saw this rom -AOKP 4.2.2 (Android Open Kang Project) (CDMA&GSM) that you created - http://forum.xda-developers.com/showthread.php?t=2293892
I re-rooted and installed that one and it looks great, just wondered how you got sprint to activate the phone or if you had done it before changing the rom? Also how would the prl and profile be updated.
Lastly the wifi wasn't turning on this time either, it did work initially when i got the phone so that has me stumped.
crispy6 said:
so far the only rom i tried was 10.1 cyanogen and the stock rom for jellybean. However for the stock rom it doesnt let me downgrade to ics with rsd 6.1.5 do you think if i downloaded an old version i could downgrade to a lower stock rom?
Also I honestly had not looked for the cdma roms since most of what i saw was troubleshooting related for this phone but i just saw this rom -AOKP 4.2.2 (Android Open Kang Project) (CDMA&GSM) that you created - http://forum.xda-developers.com/showthread.php?t=2293892
I re-rooted and installed that one and it looks great, just wondered how you got sprint to activate the phone or if you had done it before changing the rom? Also how would the prl and profile be updated.
Lastly the wifi wasn't turning on this time either, it did work initially when i got the phone so that has me stumped.
Click to expand...
Click to collapse
To downgrade to ICS, you need to remove some additional lines. See this post for more information on that.
However, you should be able to update the PRL on either stock ROM.
I think I said this before, but I will say it again. You need to do PRL updates, activate the phone, and get EVERYTHING working on stock BEFORE you flash ANY custom ROM. This is just standard practice - you don't want to put the cart before the horse! Get the phone working, then play with custom ROM's.
Hey guys, first of all a big hello to everyone, since this is my first post here on XDA!
I've been on this forum for a while, but it's only since now that I really can't figure things out anymore on my own, or trough other posts.
Now the situation:
I've got a sony Xperia E C1505 (codename Nanhu) (that's single SIM)
which is not running well even on stock software. On stock software (ROM version 11.3.A.0.47) the phone keeps freezing after a while, say 10 seconds after the reboot. When it freezes, it instantly reboots.
I got tired of this rebooting phone and first flashed Firefox O.S. to see what it looks like. It's quiete awesome but I didnt have any radio's... Anyways ATLEAST it didnt freeze on me.
So I flashed back again to the stock 11.3.A.0.47, to see myself run into the freezing problems AGAIN!
This time I decided that I'd flash CM10 to see what it does.
So far I came across 2 different versions:
- JB version (by jjim, am I correct?)
- FXP version (by FXP)
I've been running FXP228 now and it works flawlessly! Everything works, every radio is intact and even the camera app works.
But.. *drumroll..* here's the thing; My SIM card does not get detected. It doesen't even ask me for a PIN at startup!
I've downloaded this 3rd party app for my SIM info, it says the following:
SIM state: UNKNOWN
Phone Type: GSM
Network type: UNKNOWN
The IMEI is correct though
The baseband is correct aswell, atleast I believe so.
Btw, I live in the Netherlands and my SIM card is from Vodafone. I've already tested this card in another phone, it works as it should.
What can I do to make the SIM-Card be detected? I've scoured the forums looking for solutions.. Sadly enough, I only came across this which was my closest approach to my problem:
http://forum.xda-developers.com/showthread.php?t=2277279
I also noticed this:
http://forum.xda-developers.com/showthread.php?t=2209767
Anyway's.. I'm sort of stuck right now. The next step for me is to try n flash FXP 220..
If anyone's got a direct solution or workaround for me on this stage, I'd be happy.
Also, some explainment around the whole JB rom's would be nice. I understand that I first have to flash a modified stock ROM from JB to install CM10 ? Where can I get this .TFT file? I've already searched in http://forum.xda-developers.com/showthread.php?t=2326830 and http://forum.xda-developers.com/showthread.php?t=2330638 but I don't get much wiser out of it.
Looking forward to your responses!
- Ruud
Edit: SOLVED!!
http://forum.xda-developers.com/showthread.php?t=2276943
I used the xperia_e_single_jb_cwm.elf first, then i flashed nanhu-CM10DS-0.8.1.33-ota.zip
After 2 reboots it finally got into the home screen, asked me for the PIN straight away and works like a charm.
Many thanks to jjim
Hope this helps for a future user.
Things i have tried:
- Flash FXP firmware versions; (failed)
- 220 (failed)
- 224 (no gsm)
- 228 (no gsm)
- Restore stock over and over (failed)
- Modify stock (failed)
- Modified the FXP firmware with modem.zip files from the stock and re-flashed (failed)
- Flashed JB firmware. SUCCES!!!!
Greetings Ruud from the Netherlands
Why don't you just relock bootloader and apply for warranty
I'm sure it's been just a couple of months since Xperia E is released
Is there anything that stops you from applying warranty?:what::what:
Sent from my C1604 using xda app-developers app
I couldnt apply this phone for warranty because the previous user / owner already messed around with this phone.
Same to me. I've tried FXP238 and still no GSM network detected
Hey man, thanks a lot with your post, Im having exactly the same problem.
I have tried with FXP241 with no lock detecting the SIM card.
I downloaded the files you posted. Flashed the jjm34 boot+recovery and then installed the CM10DS file you mentioned. During the install I had the error "symlink: some symlinks failed"
Did you have the same problem?
Thanks!
Zdo
SIM no signal
have a xperia c1505 and after doing a root was no signal and can not make calls.
someone help me
hello
Do a factory reset and if that fails then flash the stock rom onto your phone
---------- Post added at 03:36 AM ---------- Previous post was at 02:42 AM ----------
You need to flash a file called cm_nanhu_DS-ota110 to fix any simcard problem ,I have it on my phone now and testing it atm Works okay
Ruud033 said:
Hey guys, first of all a big hello to everyone, since this is my first post here on XDA!
I've been on this forum for a while, but it's only since now that I really can't figure things out anymore on my own, or trough other posts.
Now the situation:
I've got a sony Xperia E C1505 (codename Nanhu) (that's single SIM)
which is not running well even on stock software. On stock software (ROM version 11.3.A.0.47) the phone keeps freezing after a while, say 10 seconds after the reboot. When it freezes, it instantly reboots.
I got tired of this rebooting phone and first flashed Firefox O.S. to see what it looks like. It's quiete awesome but I didnt have any radio's... Anyways ATLEAST it didnt freeze on me.
So I flashed back again to the stock 11.3.A.0.47, to see myself run into the freezing problems AGAIN!
This time I decided that I'd flash CM10 to see what it does.
So far I came across 2 different versions:
- JB version (by jjim, am I correct?)
- FXP version (by FXP)
I've been running FXP228 now and it works flawlessly! Everything works, every radio is intact and even the camera app works.
But.. *drumroll..* here's the thing; My SIM card does not get detected. It doesen't even ask me for a PIN at startup!
I've downloaded this 3rd party app for my SIM info, it says the following:
SIM state: UNKNOWN
Phone Type: GSM
Network type: UNKNOWN
The IMEI is correct though
The baseband is correct aswell, atleast I believe so.
Btw, I live in the Netherlands and my SIM card is from Vodafone. I've already tested this card in another phone, it works as it should.
What can I do to make the SIM-Card be detected? I've scoured the forums looking for solutions.. Sadly enough, I only came across this which was my closest approach to my problem:
http://forum.xda-developers.com/showthread.php?t=2277279
I also noticed this:
http://forum.xda-developers.com/showthread.php?t=2209767
Anyway's.. I'm sort of stuck right now. The next step for me is to try n flash FXP 220..
If anyone's got a direct solution or workaround for me on this stage, I'd be happy.
Also, some explainment around the whole JB rom's would be nice. I understand that I first have to flash a modified stock ROM from JB to install CM10 ? Where can I get this .TFT file? I've already searched in http://forum.xda-developers.com/showthread.php?t=2326830 and http://forum.xda-developers.com/showthread.php?t=2330638 but I don't get much wiser out of it.
Looking forward to your responses!
- Ruud
Edit: SOLVED!!
http://forum.xda-developers.com/showthread.php?t=2276943
I used the xperia_e_single_jb_cwm.elf first, then i flashed nanhu-CM10DS-0.8.1.33-ota.zip
After 2 reboots it finally got into the home screen, asked me for the PIN straight away and works like a charm.
Many thanks to jjim
Hope this helps for a future user.
Things i have tried:
- Flash FXP firmware versions; (failed)
- 220 (failed)
- 224 (no gsm)
- 228 (no gsm)
- Restore stock over and over (failed)
- Modify stock (failed)
- Modified the FXP firmware with modem.zip files from the stock and re-flashed (failed)
- Flashed JB firmware. SUCCES!!!!
Greetings Ruud from the Netherlands
Click to expand...
Click to collapse
Do you still have got the Modem.zip files for the stock rom ??
Hi Everyone,
I have purchased my Xperiz Z 'C6602' in the start of this year (2014). Yesterday, I faced a problem that my mobile was showing no Sim card detection. I have restarted my mobile many times, open the Sim slot and again placed it corrected but the problem persists. I have reset my mobile, check the aeroplane mode but all is well. I am wondering that how this happened because my mobile was working great. I used it at night very well and then after some hours at morning the mobile showed no network connection (detect no Sim) while the Sim was in the Sim Slot.
Please tell me the solution of this problem. Thanks
i got no signal at c1605 (dual)
I have no service and no cellular network problem on my N5, running dark rom 7.1.2 aosp, with franco kernel ( never had issues before ), newest radio and bootloader. This started happening when i got my new sim card from my provider and i got 4g signal in my area for the first time. I tried manually selecting radio by going in the hidden menu by entering *#*#4636#*#* and i got lte and full bars signal after selecting band 8 ( 1800 hz ) but only for a minute then it went back to empty triangle. Tried selecting 3g only in preffered network, tried manually selecting provider, tried toggling airplane mode on/off a bunch of times nothing works. Any suggestion would be highly appreciated, i love my N5 very much and i would hate to throw it in a drawer somewhere. Thanks in advance
Flash back to a stock ROM and test it worth your new new.
Does the sim work in another phone?
audit13 said:
Flash back to a stock ROM and test it worth your new new.
Does the sim work in another phone?
Click to expand...
Click to collapse
Yes the sim is working fine on any other phone. I will try gping back to stock thanks
EmilChurle23 said:
Yes the sim is working fine on any other phone. I will try gping back to stock thanks
Click to expand...
Click to collapse
Were you ever able to get this rectified? I have recently been having this problem as well. I have flashed back to ROMs I was previously using and flashed back to stock to no avail. My SIM card works in other devices as well. I really do not want to have to drop on a new phone, but I have tried every solution I have found online to no avail. I think it's fair to say that I am desperate right now.
edit: I found another thread on XDA that I'm looking into, I'll edit again if it works. I'm unsure how it took me so long to find that thread.
edit2: https://forum.xda-developers.com/go...getting-cdma-networks-to-nougat-roms-t3534679 is the thread that I found useful; I am now running Pure Nexus 7.1.2 with a full connection. Specifically, his second comment about installing 6.0.1 stock, backing up the efs, flashing the desired ROM, then restoring the efs is what ended up fixing it for me.
iamxaq said:
Were you ever able to get this rectified? I have recently been having this problem as well. I have flashed back to ROMs I was previously using and flashed back to stock to no avail. My SIM card works in other devices as well. I really do not want to have to drop on a new phone, but I have tried every solution I have found online to no avail. I think it's fair to say that I am desperate right now.
edit: I found another thread on XDA that I'm looking into, I'll edit again if it works. I'm unsure how it took me so long to find that thread.
edit2: https://forum.xda-developers.com/go...getting-cdma-networks-to-nougat-roms-t3534679 is the thread that I found useful; I am now running Pure Nexus 7.1.2 with a full connection. Specifically, his second comment about installing 6.0.1 stock, backing up the efs, flashing the desired ROM, then restoring the efs is what ended up fixing it for me.
Click to expand...
Click to collapse
Gonna try this fix now and I'll edit the result thanks for some hope
EmilChurle23 said:
Gonna try this fix now and I'll edit the result thanks for some hope
Click to expand...
Click to collapse
This morning it's not sticking with Pure Nexus, so I'll be trying DarkRom. I really don't want to use a CAF if I can avoid it, but it may become a necessity. Do people on T-Mobile have this problem?
iamxaq said:
This morning it's not sticking with Pure Nexus, so I'll be trying DarkRom. I really don't want to use a CAF if I can avoid it, but it may become a necessity. Do people on T-Mobile have this problem?
Click to expand...
Click to collapse
I wil try aosp by santosh m and see if it sticks
EmilChurle23 said:
I wil try aosp by santosh m and see if it sticks
Click to expand...
Click to collapse
So I've hit a point where I have 3G and nothing else. I can't yet get LTE to work. I'm using LineageOS CAF. How about yourself?
iamxaq said:
So I've hit a point where I have 3G and nothing else. I can't yet get LTE to work. I'm using LineageOS CAF. How about yourself?
Click to expand...
Click to collapse
No luck with aosp by santosh m and pure nexus 7.1.2 , can't even get it to connect. I guess my last hope is caf based i will try lineageos caf. All i need is the efs backup from stock? If i can get it to work with 3g i will be satisfied because i did some digging and found out that my network provider which is Vip MK has no lte support for nexus 5 d820 ( my model ) only 3g, but i can't even connect with 3g selected. I guess because this one is for US frequencies it will not work whatever i try but i will give lineageos caf a chance.
EmilChurle23 said:
No luck with aosp by santosh m and pure nexus 7.1.2 , can't even get it to connect. I guess my last hope is caf based i will try lineageos caf. All i need is the efs backup from stock? If i can get it to work with 3g i will be satisfied because i did some digging and found out that my network provider which is Vip MK has no lte support for nexus 5 d820 ( my model ) only 3g, but i can't even connect with 3g selected. I guess because this one is for US frequencies it will not work whatever i try but i will give lineageos caf a chance.
Click to expand...
Click to collapse
I was able to get 3G only to work on my Nexus 5 by reflashing the EFS from 6.0.1; I'm trying right now to see if I can install PureNexus 6.0.1 then dirty flash to PureNexus 7.1.2 with any success. Also, I might just switch to T-Mobile, but I have to wait until later this week for that.
Hi,
LTE band 8 is not in 1800 MHz but first of all you can check your N5 model - US model is D820 and is not supported for LTE on 1800 MHz (band 3). For 1800 Mhz band you need D821 model.
Regards,
iamxaq said:
Were you ever able to get this rectified? I have recently been having this problem as well. I have flashed back to ROMs I was previously using and flashed back to stock to no avail. My SIM card works in other devices as well. I really do not want to have to drop on a new phone, but I have tried every solution I have found online to no avail. I think it's fair to say that I am desperate right now.
edit: I found another thread on XDA that I'm looking into, I'll edit again if it works. I'm unsure how it took me so long to find that thread.
edit2: https://forum.xda-developers.com/go...getting-cdma-networks-to-nougat-roms-t3534679 is the thread that I found useful; I am now running Pure Nexus 7.1.2 with a full connection. Specifically, his second comment about installing 6.0.1 stock, backing up the efs, flashing the desired ROM, then restoring the efs is what ended up fixing it for me.
Click to expand...
Click to collapse
To clarify that:
You had the problem with not recognizing the sim or having no service at all. And you solved this by flashing the sstock 6.0.1 backing up the efs, flashing to Pure Nexus 7.1.2 and restoring the efs immediatley after flashing the rom (+kernel+root+etc)?
This solves this mysterious no sim/no service bug, which many (?) N5 owners experience? If this is true, I'd be really happy
Iced-Earth said:
To clarify that:
You had the problem with not recognizing the sim or having no service at all. And you solved this by flashing the sstock 6.0.1 backing up the efs, flashing to Pure Nexus 7.1.2 and restoring the efs immediatley after flashing the rom (+kernel+root+etc)?
This solves this mysterious no sim/no service bug, which many (?) N5 owners experience? If this is true, I'd be really happy
Click to expand...
Click to collapse
It didn't stick. After I lost it I was unable to get it back. I gave up and switched to T-Mobile, where it is no longer a problem. Apologies for not having more testing information. I was able to get solely 3G on multiple instances, but getting the elusive 4G was beyond me.
I've had this problem before in two nexus, one of them running latest stock and the other a customized ROM. I tried to flash a stock ROM image in both of them with no luck. I was pretty sure that the image I was flashing was the latest, so the radio & bootloader should be flashed to the latest versions. But it didn't worked.
Finally I found on a XDA thread where someone was posting only the latest bootloader & radio to flash. I did it with NRT (in Advanced Utilities) and it worked:
View attachment 4196236
I can't remember or find the thread, so I post the images here:
- Bootloader-hammerhead-hhz20h.img
- Radio-hammerhead-m8974a-2.0.50.2.30.img
I think I had to flash them twice because the first time it wasn't right, but there were 4 months since then and still no failure
ochoceros said:
I've had this problem before in two nexus, one of them running latest stock and the other a customized ROM. I tried to flash a stock ROM image in both of them with no luck. I was pretty sure that the image I was flashing was the latest, so the radio & bootloader should be flashed to the latest versions. But it didn't worked.
Finally I found on a XDA thread where someone was posting only the latest bootloader & radio to flash. I did it with NRT (in Advanced Utilities) and it worked:
View attachment 4196236
I can't remember or find the thread, so I post the images here:
- Bootloader-hammerhead-hhz20h.img
- Radio-hammerhead-m8974a-2.0.50.2.30.img
I think I had to flash them twice because the first time it wasn't right, but there were 4 months since then and still no failure
Click to expand...
Click to collapse
Thanks for your input. I'll check that when I have some time. This is really weird as it looks like a hardware problem but if you can fix it with this method it's clearly a software issue...
best regards