Database Develop

[Q] WiFi Speed Issues

I have an AT&T Version HTC One, I just flashed a few different 4.4 ROMs (Revolution HD, One Droid, Beanstalk, etc) and I'm having the same frustrating issue- my WiFi speeds are horrible!!! I can't seem to do more than one thing at a time because the WiFi takes forever to load anything.It seems to be only an issue with the download speed topping out at 3Mbps (every other device gets around 45Mbps) but the upload speeds are still fine on my phone.
Any thoughts or ideas are greatly appreciated! Is there a Wifi radio I should flash? I'm curently on Android Revolution HD 4.4 with Sense 5.5
Happy Holidays!

abenitez64 said:
I have an AT&T Version HTC One, I just flashed a few different 4.4 ROMs (Revolution HD, One Droid, Beanstalk, etc) and I'm having the same frustrating issue- my WiFi speeds are horrible!!! I can't seem to do more than one thing at a time because the WiFi takes forever to load anything.It seems to be only an issue with the download speed topping out at 3Mbps (every other device gets around 45Mbps) but the upload speeds are still fine on my phone.
Any thoughts or ideas are greatly appreciated! Is there a Wifi radio I should flash? I'm curently on Android Revolution HD 4.4 with Sense 5.5
Happy Holidays!
Click to expand...
Click to collapse
all the KitKat roms are based off the developer edition release, and if your like me all the developer edition files do not get along with my AT&T One. I have always had horrible WiFi and Data service on all developer edition versions. I went back to InsertCoin 6.0.5 (3.62.401.1 - 4.3 base) until AT&T releases their KitKat Update.

clsA said:
all the KitKat roms are based off the developer edition release, and if your like me all the developer edition files do not get along with my AT&T One. I have always had horrible WiFi and Data service on all developer edition versions. I went back to InsertCoin 6.0.5 (3.62.401.1 - 4.3 base) until AT&T releases their KitKat Update.
Click to expand...
Click to collapse
Darn, I guess I'm going to have to wait. Thanks for shedding some light on the issue, I'm going crazy flashing all these ROMs

abenitez64 said:
Darn, I guess I'm going to have to wait. Thanks for shedding some light on the issue, I'm going crazy flashing all these ROMs
Click to expand...
Click to collapse
Just stick with 4.3 base for now it won't be much longer

I can't stand this anymore! Anyone else running a Kit Kat ROM with Wifi speed issues? I've gone through countless ROMs now and I still have the same issue.
I'm currently using SkyDragon Google Play edition http://forum.xda-developers.com/showthread.php?t=2400161 but I'm still having my Wifi top out at 3Mbps when everything else in my house runs at 50Mbps. Is there a wifi radio that I need to flash or firmware update??

abenitez64 said:
I can't stand this anymore! Anyone else running a Kit Kat ROM with Wifi speed issues? I've gone through countless ROMs now and I still have the same issue.
I'm currently using SkyDragon Google Play edition http://forum.xda-developers.com/showthread.php?t=2400161 but I'm still having my Wifi top out at 3Mbps when everything else in my house runs at 50Mbps. Is there a wifi radio that I need to flash or firmware update??
Click to expand...
Click to collapse
are you s-off and what is your current firmware ?
do a fastboot getvar all and post the results (minus your iemi and serial)
I'll help you find the correct files to try and up your speed

clsA said:
are you s-off and what is your current firmware ?
do a fastboot getvar all and post the results (minus your iemi and serial)
I'll help you find the correct files to try and up your speed
Click to expand...
Click to collapse
I am s-off and on radio 4A.17.3250.20 if that helps
I'll have to fastboot later to get that info. Thanks

Android N Ok Google not working in any screen

Does anyone know how to fix the Ok Google voice function in android 7? It only works in the Google app and not everywhere.
tApPeD fROM mY nExUs 6

This works, if not try to do it with an older version of google app, and then update to latest beta
http://forum.xda-developers.com/showpost.php?p=69190540&postcount=82

Try the above, but for me that didn't work. The only alternative I found was to switch to a stock-based ROM. No one has been able to pin down the reason why as of yet, but OK Google detection simply isn't working correctly on Nexus 6 AOSP ROMs. Yet it works like a champ on my Galaxy S4 running Android 7.0 AOSP.

Strephon Alkhalikoi said:
Try the above, but for me that didn't work. The only alternative I found was to switch to a stock-based ROM. No one has been able to pin down the reason why as of yet, but OK Google detection simply isn't working correctly on Nexus 6 AOSP ROMs. Yet it works like a champ on my Galaxy S4 running Android 7.0 AOSP.
Click to expand...
Click to collapse
Just installed cyanide and it works very well

Is that a Cyanogenmod ROM? If so, that's not AOSP as I define it.

Strephon Alkhalikoi said:
Is that a Cyanogenmod ROM? If so, that's not AOSP as I define it.
Click to expand...
Click to collapse
No, i don't think so, it runs on aosp too, nitrogen
for example

I was running Pure Nexus the entire time, until this issue occurred. Obviously, Pure Nexus is an AOSP ROM, and nothing I tried worked. In fact, the last thing I tried, which was to install Open GApps instead of Pure Nexus GApps, completely crashed the Google app so it was impossible to complete setup.
For alternatives, I've tried running Nitrogen and one other ROM, though I forgot which one. All of them built with an AOSP core, and all of them failed. The only ROMs that actually worked were danvdh's stock lite ROM and tupac4u's debloated stock. Factory resets do not help. I tried that as well and the problem still presents itself when an AOSP ROM is installed. Since only the stock ROMs have worked for me, there has to be an issue somewhere in the AOSP ROMs that is causing this.
Oh, and before I forget, Cyanogenmod is not an option. I refuse to run it on this device, and in fact none of the devices suitable for use as a daily driver in house use it.

Strephon Alkhalikoi said:
I was running Pure Nexus the entire time, until this issue occurred. Obviously, Pure Nexus is an AOSP ROM, and nothing I tried worked. In fact, the last thing I tried, which was to install Open GApps instead of Pure Nexus GApps, completely crashed the Google app so it was impossible to complete setup.
For alternatives, I've tried running Nitrogen and one other ROM, though I forgot which one. All of them built with an AOSP core, and all of them failed. The only ROMs that actually worked were danvdh's stock lite ROM and tupac4u's debloated stock. Factory resets do not help. I tried that as well and the problem still presents itself when an AOSP ROM is installed. Since only the stock ROMs have worked for me, there has to be an issue somewhere in the AOSP ROMs that is causing this.
Oh, and before I forget, Cyanogenmod is not an option. I refuse to run it on this device, and in fact none of the devices suitable for use as a daily driver in house use it.
Click to expand...
Click to collapse
i actually think its a google now issue. both my lg k7 and lg blahblahblah both had it working on any screen, then it stopped working, and options disappeared. a few days later, the options reappeared, i enabled them, and now works again on any screen.

I guess I didn't word things quite right, as I meant to say the interaction between the Google app and ROM was causing the issue. Hopefully you're right about it being app related so I can move back to Pure Nexus.

I'll give it a shot... I'm running Chroma MM and it works but not in Nitrogen OS. I think it was working on the sky dragon ROM but I was having corruption issues on boot with it while using multirom.
tApPeD fROM mY nExUs 6

Coming to find out, in my case it apparently wasn't app or ROM related. As of right now I have OK Google anywhere working properly with Pure Nexus, and sticking through reboots as well. My solution?
Follow the ROM instructions.
Pure Nexus requires updating both bootloader and modem and strongly recommends using fastboot to do it. I had done the update about two weeks prior to Pure Nexus being released, but using flashable zips that are available on the forums. Obviously, those zips did not flash a complete package.
EDIT: OK Google detection is once again broken. Hopefully Google solves this problem, because this is annoying.

Anybody figure this out? It only seems to work on factory images, not AOSP ROMs.

Strephon Alkhalikoi said:
Coming to find out, in my case it apparently wasn't app or ROM related. As of right now I have OK Google anywhere working properly with Pure Nexus, and sticking through reboots as well. My solution?
Follow the ROM instructions.
Pure Nexus requires updating both bootloader and modem and strongly recommends using fastboot to do it. I had done the update about two weeks prior to Pure Nexus being released, but using flashable zips that are available on the forums. Obviously, those zips did not flash a complete package.
EDIT: OK Google detection is once again broken. Hopefully Google solves this problem, because this is annoying.
Click to expand...
Click to collapse
Sorry to rehash this but it's a bit of a bump. It's actually not Google's fault. OoenGapps made a change back in September, changing HotwordEnrollment.apk. okGoogle anywhere has been broken ever since. It's only happening to AOSP Roms like the person above stated. The maintainers of CM for the 6P are trying to get to the bottom of it to see if they can do anything to fix the issue.
MrBrady said:
Anybody figure this out? It only seems to work on factory images, not AOSP ROMs.
Click to expand...
Click to collapse

Try to freeze the hotword enrollment apk.....I use ROM Toolbox Pro for this. It is a system app.....froze it and then followed the directions around the forums and google assistant worked for me on nitrogen on screen off, it seemed to me to be a little more "finicky" at starting from screen off then on stock, but that could just be me and how my voice training was saved or whatever....good luck

7.1.1 with RADIO and KERNEL of 6.0.1??? IN SEARCH FOR A FIX FOR WIFI/CONNECTIVITY

Hello,
Like many others, my phone was solid on 6.0.1. My phone was on shamu-mmb31c image that comes with radio radio-shamu-d4.01-9625-05.32+fsg-9625-02.109.
After upgrading to 7.1.1, I started to have wifi/connectivity issues. No workaround was helping.
I started flashing older radios in hope that it will fix the issue. Even radio of 6.0.1 (above) did not resolve the issue. To just prove to myself that issue is not hardware related I flashed back factory image of 6.0.1 shamu-mmb31c and all the connectivity issues were resolved.
After above experiment, I came to the conclusion that the issue with 7.1.1 is not just the radio, reason being that flashing radio of 6.0.1 did not fix it.
For next step I want to flash 7.1.1 , then flash radio AND kernel of 6.0.1 over it. to see if it will give me a good result or not,===== having 7.1.1 and solid connectivity.
Now my question is,:
Will having an older kernel flashed on 7.1.1 cause any failure? Will it be a good test? Does it even make sense? What would be the caveat of having old kernel on 7.1.1 ? Will features of 7.1.1 stop working?
Thanks,

You can't use an M kernel on N or vice versa. Won't work.

joseph230 said:
Hello,
Like many others, my phone was solid on 6.0.1. My phone was on shamu-mmb31c image that comes with radio radio-shamu-d4.01-9625-05.32+fsg-9625-02.109.
After upgrading to 7.1.1, I started to have wifi/connectivity issues. No workaround was helping.
I started flashing older radios in hope that it will fix the issue. Even radio of 6.0.1 (above) did not resolve the issue. To just prove to myself that issue is not hardware related I flashed back factory image of 6.0.1 shamu-mmb31c and all the connectivity issues were resolved.
After above experiment, I came to the conclusion that the issue with 7.1.1 is not just the radio, reason being that flashing radio of 6.0.1 did not fix it.
For next step I want to flash 7.1.1 , then flash radio AND kernel of 6.0.1 over it. to see if it will give me a good result or not,===== having 7.1.1 and solid connectivity.
Now my question is,:
Will having an older kernel flashed on 7.1.1 cause any failure? Will it be a good test? Does it even make sense? What would be the caveat of having old kernel on 7.1.1 ? Will features of 7.1.1 stop working?
Thanks,
Click to expand...
Click to collapse
Your issue is 7.1.1. Android N is full of issues that are causing many people to go back to android 6.0. Every Odd numbered release from google seems to be buggy ones.

zelendel said:
Your issue is 7.1.1. Android N is full of issues that are causing many people to go back to android 6.0. Every Odd numbered release from google seems to be buggy ones.
Click to expand...
Click to collapse
LOL, Seems Microsoft Windows curse is universal (95,98,2000,xp,vista,7,8,...10).

zelendel said:
Your issue is 7.1.1. Android N is full of issues that are causing many people to go back to android 6.0. Every Odd numbered release from google seems to be buggy ones.
Click to expand...
Click to collapse
I flashed radio of 7.1.1 over 6.0.1 and it did not cause any issues. This is a proof to what you just said. Kernel is full of bugs and that is hard to fix
Sticking with 6.0.1 for now! Maybe I should get back into using custom roms again!
Thanks.

joseph230 said:
LOL, Seems Microsoft Windows curse is universal (95,98,2000,xp,vista,7,8,...10).
Click to expand...
Click to collapse
Heck 98, XP and 7 were the only good ones. Dont even get me started on 10. I had to go back and revert over 300 PC to windows 7 when the 10 upgrade happed. That was just a nightmare.

What sort of issues are you talking about? Besides the speakerphone echo.

zelendel said:
Your issue is 7.1.1. Android N is full of issues...
Click to expand...
Click to collapse
I can confirm that.
Changed some things
Using lite stockROM of danvdh and Franco's kernel incl. speaker echo fix.
After debloat, decrypt and previous G-app(black) of TBO-team and removing Gmail and G-messenger it seems to work well.
Fingers crossed..., will report here.

Lawstorant said:
What sort of issues are you talking about? Besides the speakerphone echo.
Click to expand...
Click to collapse
Wifi and Radio connection drops all the time. Many people seem to experience it!

NLBeev said:
I can confirm that.
Changed some things
Using lite stockROM of danvdh and Franco's kernel incl. speaker echo fix.
After debloat, decrypt and previous G-app(black) of TBO-team and removing Gmail and G-messenger it seems to work well.
Fingers crossed..., will report here.
Click to expand...
Click to collapse
basically you are changing all the parts. I am hoping Google do that in future updates!!! Of course I doubt that since they do not care about old devices!

joseph230 said:
basically you are changing all the parts. I am hoping Google do that in future updates!!! Of course I doubt that since they do not care about old devices!
Click to expand...
Click to collapse
It seems to me that Google changed policy.
Till now the changes made the N6 great again.
No encryption, dark interface when possible.
Aquamail is better than Gmail, Signal is better than G-messenger. Nova launcher is better than G-now launcher.
I replace/disable G-apps and G-services when possible.
No Google Assistant, no Fit, no Pay, no Game, no Hangouts, no Wearable, no G-drive, no G-now.
Runs smoothly, no issues. Excellent battery life. Good to have XDA.

No Nougat Update for SM-G610Y

Can anyone help me with this.
All the other versions of the J7 Prime (G610F & G610M) have recieved 7.0 Nougart update 6 months ago.
My phone is pretty much the same underneath as the rest of these, No my phone is not carrier locked.
I'm not the only one having this issue, there are a lot of people in the Philippines, Pakistan and here in New Zealand who are wanting this update and cant get it.
Samsung wont tell me anything no matter how much I ask their help desk and support team
I feel like as a customer I deserve to at least know why I haven't got this update but the rest of the world has, and not get continuously told to turn auto updates on when its already on.

Same device bro
Bro, i am a Y variant and i'm on PH. We don't have a choice but to install custom rom to taste the nougat android. Just root your phone, install TWRP then install custom rom like NovaOS or Lineage OS 15.1 for J7 Prime. Just search it and you can find it.

Same issue here...just installed Xenos Rom and its more than enough for me with the features....there are other roms as well

same ;(

Ah, those lazy Samsung coding teams...
My condolences, but you can always install the ROM closest to stock.

Australia G610Y received the Nougat update released April 11, 2018. The ROM is now available for download at SamMobile

No
To Y'all Users in the Philippines
I'n sad to say it but Samsung will not be releasing Nougat on our units
here's an email from samsung:
Thank you for contacting Samsung Philippines.
This is to acknowledge the receipt of your e-mail regarding Nougat update for your Samsung Galaxy J7 Prime (SM-G9610Y). We are here to provide you with necessary information about your concern.
Upon checking, Nougat will no longer be available for J7 Prime units released in the Philippine market. Kindly note that Samsung needs to perform multiple tests to ensure the compatibility of the software to the hardware as well as the security of the user.
However, after series of test, Samsung product and development team has decided not to release the nougat update due to some possible incompatibility issue.
We apologize for the limited assistance we can provide regarding this matter. Rest assured we will continue to check on how else we can improve the overall Samsung customer experience.
The reference number for this particular transaction is
Feel free to contact us again for any concern or inquiry.
---------- Post added at 08:27 AM ---------- Previous post was at 08:24 AM ----------
tjlabais said:
Australia G610Y received the Nougat update released April 11, 2018. The ROM is now available for download at SamMobile
Click to expand...
Click to collapse
Is there a way to install your Nougat in other G610Y's for the Philippines?

Leo Cruz said:
To Y'all Users in the Philippines
I'n sad to say it but Samsung will not be releasing Nougat on our units
here's an email from samsung:
Thank you for contacting Samsung Philippines.
This is to acknowledge the receipt of your e-mail regarding Nougat update for your Samsung Galaxy J7 Prime (SM-G9610Y). We are here to provide you with necessary information about your concern.
Upon checking, Nougat will no longer be available for J7 Prime units released in the Philippine market. Kindly note that Samsung needs to perform multiple tests to ensure the compatibility of the software to the hardware as well as the security of the user.
However, after series of test, Samsung product and development team has decided not to release the nougat update due to some possible incompatibility issue.
We apologize for the limited assistance we can provide regarding this matter. Rest assured we will continue to check on how else we can improve the overall Samsung customer experience.
The reference number for this particular transaction is
Feel free to contact us again for any concern or inquiry.
---------- Post added at 08:27 AM ---------- Previous post was at 08:24 AM ----------
Is there a way to install your Nougat in other G610Y's for the Philippines?
Click to expand...
Click to collapse
I actually downloaded their Nougat based stock rom and flashed it using ODIN. No problems so far... it's just that you won't be able to use their country specific apps which I think is not a big deal.

SignetSphere said:
I actually downloaded their Nougat based stock rom and flashed it using ODIN. No problems so far... it's just that you won't be able to use their country specific apps which I think is not a big deal.
Click to expand...
Click to collapse
There are no specific apps for Philippines G610Y except when you purchase through a Telco where settings like boot screen / default web pages all point to the Telco. Flashing Aussie Official G610Y ROM should be fine. In fact this should be a good base to create a custom ROM as it may contain updated drivers and the like.
I been running the Nougat Note FE XenOS v.1.1 without any problem so i dont need to worry bout waiting for an update from OTA

tjlabais said:
There are no specific apps for Philippines G610Y except when you purchase through a Telco where settings like boot screen / default web pages all point to the Telco. Flashing Aussie Official G610Y ROM should be fine. In fact this should be a good base to create a custom ROM as it may contain updated drivers and the like.
I been running the Nougat Note FE XenOS v.1.1 without any problem so i dont need to worry bout waiting for an update from OTA
Click to expand...
Click to collapse
One minor problem I have encountered so far now is whenever I switch to 3G/2G on network mode, it doesn't survive the reboot. It reverts nback to 2G/3G/LTE mode. Other than that the Stock ROm is stable so far. Battery life is incredible.

SignetSphere said:
One minor problem I have encountered so far now is whenever I switch to 3G/2G on network mode, it doesn't survive the reboot. It reverts nback to 2G/3G/LTE mode. Other than that the Stock ROm is stable so far. Battery life is incredible.
Click to expand...
Click to collapse
Need to troubleshoot 1x1. First, I noticed you are using Oxygen kernel. It could probably be an incompatibility with this one.
Another, which I can think of is incompatibility of CSC part if you didnt change your original.

tjlabais said:
Need to troubleshoot 1x1. First, I noticed you are using Oxygen kernel. It could probably be an incompatibility with this one.
Another, which I can think of is incompatibility of CSC part if you didnt change your original.
Click to expand...
Click to collapse
It was still present when I was still using the stock kernel. About the CSC though I have no idea. But maybe you're right because I flashed the original CSC tar.md5 file that came straight from the stock Aussie Nougat ROM. I don't know how I can change it. (Perhaps flash the stock CSC from MM?)

SignetSphere said:
It was still present when I was still using the stock kernel. About the CSC though I have no idea. But maybe you're right because I flashed the original CSC tar.md5 file that came straight from the stock Aussie Nougat ROM. I don't know how I can change it. (Perhaps flash the stock CSC from MM?)
Click to expand...
Click to collapse
I checked my csc if it changed , and yes it was changed together with xenos. So it might be something else. But then there are CSCs which are not multi CSCs. So i could be wrong.
Edit: ok i did some googling. CSC doesnt affect network selection its the baseband part. You can install phone info samsung to check what versions you are in.

tjlabais said:
I checked my csc if it changed , and yes it was changed together with xenos. So it might be something else. But then there are CSCs which are not multi CSCs. So i could be wrong.
Edit: ok i did some googling. CSC doesnt affect network selection its the baseband part. You can install phone info samsung to check what versions you are in.
Click to expand...
Click to collapse
Just tried flashing the old MM modem.bin Seems to work like a charm. Although the network mode still reverts the 2G/3G/4G mode, I'm getting consistent 2G signals now and no more signal drops. I just use 4G whenever I use the phone outside where there is no wifi or when I use Navigation apps like Waze. I assume it'll get the 4G/LTE signal when the signal is strong enough.

SignetSphere said:
Just tried flashing the old MM modem.bin Seems to work like a charm. Although the network mode still reverts the 2G/3G/4G mode, I'm getting consistent 2G signals now and no more signal drops. I just use 4G whenever I use the phone outside where there is no wifi or when I use Navigation apps like Waze. I assume it'll get the 4G/LTE signal when the signal is strong enough.
Click to expand...
Click to collapse
Glad that solved your network problem. I still cant get over thinking bout your network mode switching

tjlabais said:
Glad that solved your network problem. I still cant get over thinking bout your network mode switching
Click to expand...
Click to collapse
That still puzzles me as well. No matter how many reboots I do it just doesn't want to stick to 2G/3G mode.

Update to nougat
I heard that samsung would not release an update to nougat from marshmallow OS j7 prime users here in PH, is there someone that could provide me the instructions on how to download the rom links to update my OS? Please help ?5

SignetSphere said:
Just tried flashing the old MM modem.bin Seems to work like a charm. Although the network mode still reverts the 2G/3G/4G mode, I'm getting consistent 2G signals now and no more signal drops. I just use 4G whenever I use the phone outside where there is no wifi or when I use Navigation apps like Waze. I assume it'll get the 4G/LTE signal when the signal is strong enough.
Click to expand...
Click to collapse
Can you kindly guide me on how to flash modem.bin? I flashed NZ Nougat stock ROM on PH-bought G610Y and I'm having problem switching network mode when using dual sim. If I disable sim 2 I have no problem. But when both sims are enabled I can't swith sim 1 from 2G only to 4G/3G/2G. Switching doesn't do anything. It's stuck in 2G only.
Do I simply flash the file that starts with "CP"?
Update: I went ahead and flashed the CP file from Marshmallow and problem is fixed. Thanks for the tip!

SignetSphere said:
Just tried flashing the old MM modem.bin Seems to work like a charm. Although the network mode still reverts the 2G/3G/4G mode, I'm getting consistent 2G signals now and no more signal drops. I just use 4G whenever I use the phone outside where there is no wifi or when I use Navigation apps like Waze. I assume it'll get the 4G/LTE signal when the signal is strong enough.
Click to expand...
Click to collapse
I am experiencing problems with the new facebook app on XenOS v.1.1 FB is important for me because I need it for work. So, I decided to flash the New Zealand Nougat G610Y. Here are the steps I took for successful installation official nougat on Philippine based phone:
1. I flashed latest XTC G610Y MM so all partitions contain XTC (Philippines) based settings/customizations (BL / AP / CP / CSC)
2. I flashed G610YZTU1BRC3 Nougat (BL / AP) only which means CP/CSC remains XTC (xtc is multi CSC)
3. after step 2 finishes flashing from ODIN, it will encounter an error, but it will go to recovery mode
4. at recovery mode, I simply reboot the system and enjoyed a fresh copy of Nougat
I did not encounter any problem with network selection and tested rebooting it as well. Hope that helps your problem.

Please Assist me on this (i mean step by step instructions..)
SignetSphere said:
I actually downloaded their Nougat based stock rom and flashed it using ODIN. No problems so far... it's just that you won't be able to use their country specific apps which I think is not a big deal.
Click to expand...
Click to collapse
Please Assist me on this (i mean step by step instructions..)
Thank you...

How to upgrade from kitkat?

Recently got one of these phones and I love it, it really stood the test of time and I want to keep it for a while. But, the one I have is running android 4.4 kitkat. I got a custom kitkat rom installed, omni 4.4, and I can't install anything more recent. If I try to flash anything newer than android 5.0 it'll work just fine, but, I'll have no cellular connection. My guess is it's a radio issue. How can I fix this? I have a C6906. It's a Canadian phone, but I'm using it in the US on ATT.

Popeye64 said:
Recently got one of these phones and I love it, it really stood the test of time and I want to keep it for a while. But, the one I have is running android 4.4 kitkat. I got a custom kitkat rom installed, omni 4.4, and I can't install anything more recent. If I try to flash anything newer than android 5.0 it'll work just fine, but, I'll have no cellular connection. My guess is it's a radio issue. How can I fix this? I have a C6906. It's a Canadian phone, but I'm using it in the US on ATT.
Click to expand...
Click to collapse
Have you tried using flashtool?

trunglevt said:
Have you tried using flashtool?
Click to expand...
Click to collapse
I fixed it by flashing stock lollipop with flashtool.