No WiFi After Flashing Custom Roms - OnePlus 5 Questions & Answers

Hey all,
I have been stressing out about this the past week or two trying to get myself to a new rom.
AICP, Slimrom 7 and ViperOS seem to break my WiFi and cause my MAC address to default to 02:00:00:00:00:00.
Using my cellular data to set up my phone doesn't work either.
When I choose "don't use any network for set up," there seems to be no data connection (and obv no Wifi) to set up anything from the Playstore later on.
This happens every time flashing a rom that is not of OOS.
What are some ideas to get these roms a working?
I have to format through TWRP and reinstall OOS to get WiFi back rockin.
I am bored of OxygenOS. Help me out?
Maybe I'm overlooking another thread so link me if you can.
Thanks!

Are you clean flashing the ROMs? I haven't tried the ROMs you listed but I have had no luck with any AOSP ROMs on the OP5 because I get a poor phone signal on all of them--but I never had a problem with the WiFi. Maybe clean flash Pure Fusion which is popular and see if the WiFi issue still happens.
You might also be using ROMs that are incompatible with the firmware from whatever build of OOS you are running. Usually the ROM thread will tell you which firmware version you need and sometimes includes links to download the compatible firmware in zip form so you can flash it with the ROM.

Clean flash every time. I'll try Pure Fusion. When I was trying ViperOS there was a firmware and modem zip that went along with the flashing process. Even with that separate zip, I resulted with the same WiFi situation.

Just went from
format data > freedomOS (working wifi) > format data > wipe & formats> Pure Fusion > Gapps nano > magisk 14.3
boot to setup and errors say
com.android.phone has stopped

From the boot up errors I decided to go new rom. Did the wipes necessary to flash Ressurection Remix and this seems to be running ok. I am confident that flashing a new rom will break WiFi, so I'm gonna ride Resurrection Remix out for now.

ckrummi said:
Just went from
format data > freedomOS (working wifi) > format data > wipe & formats> Pure Fusion > Gapps nano > magisk 14.3
boot to setup and errors say
com.android.phone has stopped
Click to expand...
Click to collapse
You just need to reboot once you get to the setup screen and those errors go away

I was a flashaholic with my Nexus 6P, so when I received my OP5 3 weeks ago, I went flashing within minutes
I was having the same issue...but I was able to connect to WIFI...but certain 5GHz wifi SSIDs were giving me issues and it would not let me connect.
Happened with decrypted & encrypted ROMS
right now I'm stuck on OOS 4.5.13 (which isn't a bad stock ROM at all) until I find a thread with a solution.

Related

Problems CM based roms

Hi I got problems with my lux on every cm based rom. On every cm rom I get no reception of my carrier. I don't know if it's a device tree issue or just apn trouble. Since there are no aosp roms, I'm a little hung up. Stock rom works fine. I own the xt1562 operating on German carrier o2. Sometimes I get a few seconds of reception on cm roms, but it's leading just to no signal after a few seconds again. I nearly tired everything, flashed a different firmware etc. When I've flashed a rom I get the information that no sim card was found. After I restart the device he's asking for a pin. Also tried another sim card with the same result. Really could need some help.
flash the original fimrware from ur carrier or region
flash twrp
install cm and see if works
if not,flash only the radio modem from original firmware
Already did. Didn't work. Flashed the new cm12.1 from h2o64. This one is working.
I have the exact same problem with my XT1562 I bought from Germany through Moto Maker.
I installed h2o64's CM build from 10-10 after a full wipe (everything except internal data), and never got any proper signal. I tried squid2's CM build 10-12 as well, to no avail. Installing the XT1562 EU stock firmware following the linked explanation in the stock firmwares thread I had good, working signal, but then installing h2o64's CM build 10-14 with a factory reset rather than a full wipe resulted in the same issues described in this thread again.
I've read about these issues in different threads, mostly resolved somehow by installing the stock firmware, sometimes by selecting LTE as the preferred network type. I've tried these suggestions, but haven't had any success, and I don't know how to proceed.
Did I install the right stock firmware? (I would think so as it worked while it was installed.)
Did I forget to do something (like wipe, fix permissions, reboot the phone three times, howl at the moon,...)?
I use OpenGApps rather than tkruzze's since they're available in x64 as well so I can use them on all my devices. But that surely can't be it?
I'm at a complete loss at the moment, which is rather frustrating. Can anyone provide any help?
Gesendet von meinem Nexus 9 mit Hilfe von XDA Forums Pro.
I managed to install h2o64's CM build 10-14 and getting proper signal now.
I flashed the RETASIA firmware from XMoDuLeSx's Official stock firmwares added for xt1562,xt1563 thread following the instructions linked in the first post, and then after a wipe of system, data, cache, dalvik-cache I installed [ROM][lux][5.1.1] Cyanogenmod 12.1 - 2015-10-14 [UNIFIED].
Keep in mind that I have ordered my Moto X Play from Germany, so it shouldn't require a RETASIA firmware. I'm not advising to install this, as it was nothing but a shot in the dark that surprisingly didn't brick my phone. Still, I wanted to share that I got it working after all, simply to follow up my previous post properly. Should the signal break again, I'll update this thread; if I haven't, assume that it's still working.
Either way, though: If you decide to go down this road and install a firmware that isn't right for your phone and brick it, don't come to me. I'm advising against doing this.
Seems i'm having the same issue...
I did all the wipes and clean installs but I can't connect to my carrier.
Although my phone only supports one sim card, settings shows two. The first one is the one i'm using and it is displayed correctly. The quick settings tile though tells me that there is no sim card inserted.
I came from stock, unlocked, flashed TWRP from squid2's kernel page, rooted, flashed CM(squid2), kernel(squid2) and OpenGApps.
Did I do something wrong?
Is there any news on how to fix this problem or do I have to try again and again an hope to hit the spot?
Mafaldine said:
Seems i'm having the same issue...
I did all the wipes and clean installs but I can't connect to my carrier.
Although my phone only supports one sim card, settings shows two. The first one is the one i'm using and it is displayed correctly. The quick settings tile though tells me that there is no sim card inserted.
I came from stock, unlocked, flashed TWRP from squid2's kernel page, rooted, flashed CM(squid2), kernel(squid2) and OpenGApps.
Did I do something wrong?
Is there any news on how to fix this problem or do I have to try again and again an hope to hit the spot?
Click to expand...
Click to collapse
You need two more posts before you can post this in the CM thread from squid2. Squid2 is always fast with bugfixes. So make 2 other post and then explain your problem to him.
Lennyz1988 said:
You need two more posts before you can post this in the CM thread from squid2. Squid2 is always fast with bugfixes. So make 2 other post and then explain your problem to him.
Click to expand...
Click to collapse
Thanks for your reply!
I will do that
Meanwhile I managed to get a connection to my carrier by flashing h2o64's CM build 10-14 and then squid2's on top without wiping anything...
RR Lux 5.5.8 didn't work Wifi, after 2 clean instalation, wifi turn on and off then

Marshmallow ROMs freeze and crash = Hardware Problem?

Hello everyone!
I have been experiencing a strange issue with almost all the Marshmallow ROMs currently in the development section. The Phone boots, Setup Wizard runs, and in between, the screen freezes/hangs and after 5-10 seconds the phone reboots. Again the setup wizard runs and even if i'm able to complete the wizard, the phone frequently hangs and then reboots.
I had been running Paranoid Android 5.1 ROM before flashing the Marshmallow ROM and this strange issue suddenly started. I have tried to flash stock rom and then flash twrp, then flash the ROM, even wiped everything several times. Still the same issue persists. This is really getting annoying as i have tried 3-4 different ROMs and 2 GApps and still the screen freezes and then phone reboots.
And this happens only on Marshmallow ROMs as i again have currently installed Chroma 5.1.1 ROM and its running smoothly. I am beginning to think of it to be a hardware issue. Can anyone help me solve this?
imrock0 said:
Hello everyone!
I have been experiencing a strange issue with almost all the Marshmallow ROMs currently in the development section. The Phone boots, Setup Wizard runs, and in between, the screen freezes/hangs and after 5-10 seconds the phone reboots. Again the setup wizard runs and even if i'm able to complete the wizard, the phone frequently hangs and then reboots.
I had been running Paranoid Android 5.1 ROM before flashing the Marshmallow ROM and this strange issue suddenly started. I have tried to flash stock rom and then flash twrp, then flash the ROM, even wiped everything several times. Still the same issue persists. This is really getting annoying as i have tried 3-4 different ROMs and 2 GApps and still the screen freezes and then phone reboots.
And this happens only on Marshmallow ROMs as i again have currently installed Chroma 5.1.1 ROM and its running smoothly. I am beginning to think of it to be a hardware issue. Can anyone help me solve this?
Click to expand...
Click to collapse
Flash Frank ROM, Flash Tuxi Gapps from Frank's OP, no one is having any issues now. Also don't forget to do a factory reset if you can even the Internal data.
sidnoit22 said:
Flash Frank ROM, Flash Tuxi Gapps from Frank's OP, no one is having any issues now. Also don't forget to do a factory reset if you can even the Internal data.
Click to expand...
Click to collapse
I have done factory reset several times. Even flashed stock via fastboot multiple times. Done the exact same steps you mentioned. Its not only with Frank ROM actually, i tried another Marshmallow ROM and the same thing happened again.
How is it that Lollipop ROMs are running smooth and Marshmallow ROMs are crashing?
imrock0 said:
I have done factory reset several times. Even flashed stock via fastboot multiple times. Done the exact same steps you mentioned. Its not only with Frank ROM actually, i tried another Marshmallow ROM and the same thing happened again.
How is it that Lollipop ROMs are running smooth and Marshmallow ROMs are crashing?
Click to expand...
Click to collapse
seems like it's Gapps/ ROM problem (with setup wizard)
this my only suggestions:
1. try to flash Frank's M without Gapps > reboot normaly
if this worked, then it's related to Gapps issue...
if it still remains, then
2. Flash ROM, Gapps, wipe, etc.
after that back to home of TWRP > Mount > Mount system > back > Advanced > File manager > go to /system/priv-app
search for folder name related to Setup wizard/ Google setup wizard (NOT GooglePartnerSetup) > delete it > reboot
3. fingercrossed it will bring you to home screen without any problem...
good luck then :fingers-crossed:
yayakuya said:
seems like it's Gapps/ ROM problem (with setup wizard)
this my only suggestions:
1. try to flash Frank's M without Gapps > reboot normaly
if this worked, then it's related to Gapps issue...
if it still remains, then
2. Flash ROM, Gapps, wipe, etc.
after that back to home of TWRP > Mount > Mount system > back > Advanced > File manager > go to /system/priv-app
search for folder name related to Setup wizard/ Google setup wizard (NOT GooglePartnerSetup) > delete it > reboot
3. fingercrossed it will bring you to home screen without any problem...
good luck then :fingers-crossed:
Click to expand...
Click to collapse
Thanks i'll try this out when i get back home. Although i did try flashing just the ROM to see if GApps were causing the issue. Without GApps, the phone booted to the homescreen, but then after 5-10 mins would reboot itself. I don't know may be it has got something to do with temperature? Because i've noticed that the phone becomes very hot when it first boots up on a new ROM(i know its normal for it to get hot). But when i used the phone on a Marshmallow ROM when the phone was NOT hot, it went on pretty well for 20-30 mins and then again rebooted.
yayakuya said:
seems like it's Gapps/ ROM problem (with setup wizard)
this my only suggestions:
1. try to flash Frank's M without Gapps > reboot normaly
if this worked, then it's related to Gapps issue...
if it still remains, then
2. Flash ROM, Gapps, wipe, etc.
after that back to home of TWRP > Mount > Mount system > back > Advanced > File manager > go to /system/priv-app
search for folder name related to Setup wizard/ Google setup wizard (NOT GooglePartnerSetup) > delete it > reboot
3. fingercrossed it will bring you to home screen without any problem...
good luck then :fingers-crossed:
Click to expand...
Click to collapse
Here's another update. I tried the new Chroma Marshmallow ROM and it too had the same issue. The phone hangs/freezes randomly and then reboots. After trying so many ROMs, i think the issue is with hardware itself. None other has reported this issue, nor could i find it anywhere else. I guess i can say that my(and only my) nexus 4 is not compatible with Marshmallow officially and unofficially.
I don't know what kernel Frank's uses but you could always try to flash an alternate kernel. I haven't taken the jump to Marshmallow yet, but it seems TaUrUs and hellsCore support M (I currently use hellsCore with stock L).
bjb2 said:
I don't know what kernel Frank's uses but you could always try to flash an alternate kernel. I haven't taken the jump to Marshmallow yet, but it seems TaUrUs and hellsCore support M (I currently use hellsCore with stock L).
Click to expand...
Click to collapse
I'll try another kernel and ping back.
Probably lacked boot the system before you install GApps.
imrock0 said:
I'll try another kernel and ping back.
Click to expand...
Click to collapse
The FC of Setup Wizard is discussed in the ROM thread of Chroma.
You can try this because it is advised by the Dev of Chroma and supported by many others and I have succeeded with this.
Flash stock L and boot up.
Boot into TWRP (make sure you have the latest) and factory reset.
Flash Chroma 1/11/2015 and Bank's Gapps without boot/reboot in between and no wipe afterwards.
Reboot.
---------- Post added at 07:03 PM ---------- Previous post was at 07:00 PM ----------
webg3brasil said:
Probably lacked boot the system before you install GApps.
Click to expand...
Click to collapse
At least for Chroma, that is a wrong approach. No boot between ROM and Gapps flash.
Make sure you have permissions granted to all of the apps. I had similar issues, and had to do with Location and apps making calls to GPS. Would cause a reboot, and not just a force close. Try amending the Location settings as well. All else fails, capture a logcat.
Everyone thanks for your time!
I found the solution. bjb2's suggestion did the trick. I flashed TaUrUs-Mallow Kernel after Frank Marshmallow ROM and everything seems fine now. Have been running Marshmallow since a day without any issues. Still it's curious why the stock kernel gave such errors.
Thanks everyone again for your suggestions and help

New User - CyanogenMod Questions

Hello,
I received my Nexus 6P yesterday and got my SIM card activated without any issues at Verizon. I immediately took it home, unlocked the bootloader, installed TWRP, and then flashed CyanogenMod's latest nightly. After booting in, wireless networks weren't detected, and I only had 3G (no 4G LTE as I should). I restored my backup of the stock ROM that I made in TWRP and it hung at the Google logo. I'm not sure why. I then flashed all the latest factory restore images (MTC19X) to get it working again and determined that the issues I had in CyanogenMod might have happened due to the vendor.img I had on my phone at the time not being compatible with that build of CM13.
My questions are:
1) What are the known issues that would likely occur due to vendor.img being a different version than what CM13 was based on? The concept of vendor.img is new to me. I haven't had this, as far as I know, on any of my other phones (granted I'm coming from a locked Samsung Galaxy S5 that I've had for almost 2 years)
2) How can you easily tell which vendor.img CM was based on so you know which one to flash?
3) Is there anything else I should be made aware of before attempting to flash CM13 again?
4) While using CM13, do most people recommend a custom kernel? If so, which one and how stable is it? What are the benefits of switching from the stock kernel, and how simple is it to go back if there's a problem?
Thanks!!
dude...I just got the N6P and ran CM13 within hours. This is what I did...
unlocked the bootloader
downloaded the lastest (MTC19X) image off of https://developers.google.com/android/nexus/images and unpacked it into the C:\Program Files (x86)\Android\android-sdk\platform-tools folder
ran the flash-all.bat
fastbooted TWRP
installed CM13. (didn't wipe internal storage)
installed arm64 open Gapps pico
BAM!!!
right now running stock kernel. it's cool. I'm PrivacyGuard-ing the hell out of all my apps (turned off START AT BOOT and KEEP AWAKE for almost every downloaded app), though, so battery is OK
also using Kernel Adiutor but underclocking values for the CPUs doesn't seem to stick
So it likely worked for you since you had flashed the newest vendor.img first. Apparently there are compatibility issues with certain features that cause them not to work (such as WiFi) if you're using an older one.
chaoticyeshua said:
Hello,
I received my Nexus 6P yesterday and got my SIM card activated without any issues at Verizon. I immediately took it home, unlocked the bootloader, installed TWRP, and then flashed CyanogenMod's latest nightly. After booting in, wireless networks weren't detected, and I only had 3G (no 4G LTE as I should). I restored my backup of the stock ROM that I made in TWRP and it hung at the Google logo. I'm not sure why. I then flashed all the latest factory restore images (MTC19X) to get it working again and determined that the issues I had in CyanogenMod might have happened due to the vendor.img I had on my phone at the time not being compatible with that build of CM13.
My questions are:
1) What are the known issues that would likely occur due to vendor.img being a different version than what CM13 was based on? The concept of vendor.img is new to me. I haven't had this, as far as I know, on any of my other phones (granted I'm coming from a locked Samsung Galaxy S5 that I've had for almost 2 years)
2) How can you easily tell which vendor.img CM was based on so you know which one to flash?
3) Is there anything else I should be made aware of before attempting to flash CM13 again?
4) While using CM13, do most people recommend a custom kernel? If so, which one and how stable is it? What are the benefits of switching from the stock kernel, and how simple is it to go back if there's a problem?
Thanks!!
Click to expand...
Click to collapse
1) Depends on ROM /VENDOR, sometimes nothings happens then an error message, sometimes things doesnt work
2) Just download fresh the latest snapshot, release or nightly (they are much more stable then for a few years!) and vendor image (use these ones which are recommended!)
https://wiki.cyanogenmod.org/w/Install_CM_for_angler (there is a link for the vendor)
3) If you stay close on the tutorials, i dont know what should happen (flashing a rom is normally not critical, installing a recovery can be!)
4) Custom kernels can be great, but its not a must-have. Which kernel you should use depends on your wishes: better battery, more power etc.
Hope i could have help you a little bit!
kaufikauf said:
1) Depends on ROM /VENDOR, sometimes nothings happens then an error message, sometimes things doesnt work
2) Just download fresh the latest snapshot, release or nightly (they are much more stable then for a few years!) and vendor image (use these ones which are recommended!)
https://wiki.cyanogenmod.org/w/Install_CM_for_angler (there is a link for the vendor)
3) If you stay close on the tutorials, i dont know what should happen (flashing a rom is normally not critical, installing a recovery can be!)
4) Custom kernels can be great, but its not a must-have. Which kernel you should use depends on your wishes: better battery, more power etc.
Hope i could have help you a little bit!
Click to expand...
Click to collapse
Very much so. I appreciate it!
Has anyone encountered the constant popup of the Select Sim Card message? I'm using project fi and I am still unable to find a solution to this issue.

CM reboots when making or receiving calls :confused:

Hi guys, I had to give up using CM Roms since the phone reboots every time I try making a call or receive one, I understand there is some king of bug with the dialer framework included in the GAPPS package and that installing the Google Dialer from the play store should solve it but in my case i hasn't. This is what I've tried to no avail:
- Intalled Google DIaler from PlayStore/APK and set it default with all the permissions enabled.
- Installed Google Dialer apk as system app and set it default with all the permissions enabled.
- Installed the full GAPPS package.
- Removed the stock dialer and did all things above.
Hope someone can help me out here,
Thanks.
This happens when you have multiple phone dialer apps enabled. To use any other dialer than the included (when you flash Gapps Tiny or Micro which is recommended since the bigger packs replaces the CM app).
If you don't like the CM one, you should still flash a smaller Gapps and then disable CM dialer and download the one you want. If you already flashed a bigger Gapps, you should format system, cache and dalvik/arts partition and then reflash CM and then the smaller Gapps.
Should be enough to go settings, apps, click the gear weel (next to 3 dot menu), choose standard apps from this menu and determine your dailer as standard app..
This is a classical issue..
Sent from my OnePlus2 using XDA Labs
Sam Nakamura said:
Should be enough to go settings, apps, click the gear weel (next to 3 dot menu), choose standard apps from this menu and determine your dailer as standard app..
This is a classical issue..
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
Hi Sam, that's what I mean when I've set it as default.
pitrus- said:
This happens when you have multiple phone dialer apps enabled. To use any other dialer than the included (when you flash Gapps Tiny or Micro which is recommended since the bigger packs replaces the CM app).
If you don't like the CM one, you should still flash a smaller Gapps and then disable CM dialer and download the one you want. If you already flashed a bigger Gapps, you should format system, cache and dalvik/arts partition and then reflash CM and then the smaller Gapps.
Click to expand...
Click to collapse
Hey pitrus, this issue actually started while only having CM dialer installed since I mainly flash pico gapps.
Will try it again since its been like a month since I gave up on it. Let you know later.
J3RI3L said:
Hi Sam, that's what I mean when I've set it as default.
Click to expand...
Click to collapse
Well, okay.. Thanks for clarification :good:
Maybe you'd like to give Banks a shot, I think it's worth to try...
https://download.dirtyunicorns.com/gapps/Banks/
I never had this specific problem, only when it wasn't set to be default but a also only use one dailer.. The one that is default on cm based roms..
Sent from my OnePlus2 using XDA Labs
Guys I've had no luck, tried with a clean install of CM14 and still facing the same problem. Just today did a CM14.1 install and it is still present for me.
I guess that I could flash just CM and not gapps but I rely on Google services for a lot of stuff. Will keep trying though.
I'm having the exact same problem, random reboots during calls only, sometimes I don't even have time to answer. I'm running CM13 and only have one phone app, also set as default. When running stock and Cyanogen all was fine, this only started after flashing CM13.
Developemt for Cyanogen stopped that's why I switched, maybe coming from another rom is causing this? I did a full wipe when flashing and have updated to several nightlies and the problem remains. Maybe I'll try another rom and test it for a while.
Installed Dirty Unicorns a few days ago and the problem seemed to have been fixed, but yesterday it started acting out again. Is there a way to check if this problem is hardware related?
I'm now doing a factory reset and installing Oxigen hoping that'll fix this once and for all.
It's a problem related to Gapps
rtorresz said:
Installed Dirty Unicorns a few days ago and the problem seemed to have been fixed, but yesterday it started acting out again. Is there a way to check if this problem is hardware related?
I'm now doing a factory reset and installing Oxigen hoping that'll fix this once and for all.
Click to expand...
Click to collapse
It is not a hardware problem, I don't have this issue when running Oxygen OS, it only happens to me when running any AOSP based rom with Gapps installed.
Flash Oxygen from here http://downloads.oneplus.net/devices/oneplus-2/ and it will fix it, it's not the same as running CM though.
J3RI3L said:
It is not a hardware problem, I don't have this issue when running Oxygen OS, it only happens to me when running any AOSP based rom with Gapps installed.
Flash Oxygen from here http://downloads.oneplus.net/devices/oneplus-2/ and it will fix it, it's not the same as running CM though.
Click to expand...
Click to collapse
Sounds like you flashed the full version of Gapps instead of the recommended Nano or Micro which does not replace the dialer app with Googles own, try the smaller Gapps and you should be ok.
pitrus- said:
Sounds like you flashed the full version of Gapps instead of the recommended Nano or Micro which does not replace the dialer app with Googles own, try the smaller Gapps and you should be ok.
Click to expand...
Click to collapse
I've installed them all with the same result, last time I was using Pico Gapps with Seraph's CM14 and it happened eandomly, sometimes I could make and receive calls normally but a most of the time it would reboot as soon as the phone started ringing.
Currently I've tried a lot of solutions so I'm not really sure of what's wrong.
J3RI3L said:
It is not a hardware problem, I don't have this issue when running Oxygen OS, it only happens to me when running any AOSP based rom with Gapps installed.
Flash Oxygen from here http://downloads.oneplus.net/devices/oneplus-2/ and it will fix it, it's not the same as running CM though.
Click to expand...
Click to collapse
I flashed the latest OOS and now things are only a little bit better, instead of reboots I get dropped calls and a "No available network" message. This seems to happen only when I'm on a 3G or 4G network, if I change to a 2G network I can make calls without problems. This is driving me crazy, I've tried almost everything and I can't see what I'm missing.
rtorresz said:
I flashed the latest OOS and now things are only a little bit better, instead of reboots I get dropped calls and a "No available network" message. This seems to happen only when I'm on a 3G or 4G network, if I change to a 2G network I can make calls without problems. This is driving me crazy, I've tried almost everything and I can't see what I'm missing.
Click to expand...
Click to collapse
Its happening to me as well just as you describe it. It is very weird. In thinking of flashing the stock OOS 2.2.0 just to check whether it makes any diference.
Yesterday I restored my phone back to stock, but the problen remains.
This definitely has something to do with mobile data. If I disconnect mobile data I can make calls without any problem, when I'm connected to a wifi network too (I'm guessing because the phone has no need to use mobile data).
Some suggest that this might be related to VoLTE and operators not supporting it, but I can't find anyway to see if this is even exists or if its activated in OOS.
Later today I'll try Hydrogen and see what happens.
UPDATE: Flashing Hyrogen didn't solve the issue, calls keep dropping when mobile data is activated on LTE network.
UPDATE 2: Going back to OOS 2.2.1 didn't solve the problem either.
Kinda solved now
rtorresz said:
Yesterday I restored my phone back to stock, but the problen remains.
UPDATE: Flashing Hyrogen didn't solve the issue, calls keep dropping when mobile data is activated on LTE network.
UPDATE 2: Going back to OOS 2.2.1 didn't solve the problem either.
Click to expand...
Click to collapse
It seems I have solved my problem with the reboots and I think might help with your droped calls as well.
Firstly I flashed this OOS 3 firmware https://www.androidfilehost.com/?fid=24591020540821656, it comes with a hybrid TWRP, after that flashed the official CM14.1 and pico Open Gapps.
I think the firmware file did the trick or maybe it was the recovery since I haven't had a reboot in the past 2 days when receiving calls or making them.
Hope it helps
It's been a few days since I tried the last solution and so far my problem seems to be solved.
What worked for me was flashing the latest modem from H2OS 2.5 which also is supposed to enable VoLTE, but I can't confirm this since my carrier does not support VoLTE yet. To do this I first flashed CM 14.1 and then the modem, it worked fine since the first boot. Since my battery life wasn't the best in Nougat I went back to CM13 and the phone is still working fine.

Need help getting LineageOS to be stable (15.1 UNOFFICIAL, hltevzw, TWRP 3.3.0)

I have an SM-N900V (Note 3, Verizon variant, hltevzw).
Detailed timeline:
- I flashed it back to firmware OB6 using Odin 3.09.
- I rooted it using ArabicToolApp.
- I used this tool to unlock the bootloader
- I installed a build of LineageOS 14.1 for hlte
- It didn't recognize the SIM so I did a dirty flash of this build of LineageOS 15.1 for hltetmo on top (hltetmo actually has different hardware than hlte, and the correct one for SM-N900V)
- Messed around with the APNs until it recognized and connected to Verizon's network. I DO have functioning SMS and LTE data, but I have not tested phone calls yet
- Messed around some with SuperSU in system- and systemless-mode. Bricked my device more times than I could count, then unbricked over and over using SuperSU's impeccable installer. Messed around with this quite a bit
- Also messed around with Xposed some. The OS is too unstable to run Xposed Installer correctly, so I uninstalled it
- Removed SuperSU, installed Magisk. Phone now passes SafetyNet
So, my phone now runs 8.1 and a Lineage build from 9 days ago. Cool. But, if I was satisfied I wouldn't be making this post. There are multiple instances of the same kind of "app freeze" - App screen freezes, sometimes it'll go completely black. Interactivity doesn't work, obviously, the app is completely frozen. Hold Back to kill doesn't work (Application Killed toast shows, but nothing happens). ANR (when it comes up) Close doesn't work. Home button works and brings me away from the app, but it's still there. Swipe away in Overview doesn't actually kill the app. Even in App Info, Force Stop doesn't work. The app is forever frozen. Tapping the icon from the launcher no longer does anything, it doesn't even bring up the app. The app is permanently crashed and inaccessible until a reboot.
Issues:
- Sometimes when booting the phone will not recognize the SIM until a reboot. As in, "No SIM" message and everything
- Sometimes it will get stuck at boot, I have foxy-boot installed, so I can see the logs. I don't remember what it was all about, if it comes up again I'll update the post
- Google Chrome sometimes crashes when trying to download a file. I've gotten my phone to self-host before, but this issue always seems to come back, and when it does Google Chrome ALWAYS crashes when trying to download a file. App Freeze
- Netflix installs and logs in but freezes at the "can't connect to service (-9)" message. App Freeze
- Certain apps like NativeScript Playground get stuck at the splash screen. App Freeze
- Xposed Installer did this when opening the Settings, whether Xposed was installed or not. App Freeze
- F-Droid also sometimes crashes, although it's somewhat arbitrary, I can't reproduce it reliably. App Freeze
I have tried reflashing the ROM, flashing Xposed uninstaller, reinstalling Magisk, none of it seems to work. I have TWRP 3.3.0 so I can do pretty much anything that doesn't involve the SD card (the SD card is probably broken in hardware, it's so read-only that Android and TWRP both can't write to it at all, but they can both read the same half-broken filesystem).
I fear that this OS is just too unstable for the phone and there's nothing I can do. I sincerely hope this is not the case.
Try other ROMs or perform a clean installation.
Make sure you are on PL1 bootloader/modem.
Currently using Resurrection Remix v5.8.5 Nougat because it was the last Android version for this device with working Bluetooth calls but if you don't use that feature you could use their Pie version as well.
RR ROMs are solid and work extremely well.
Do a clean installation via TWRP if you go this route.
terminator911 said:
Try other ROMs or perform a clean installation.
Make sure you are on PL1 bootloader/modem.
Currently using Resurrection Remix v5.8.5 Nougat because it was the last Android version for this device with working Bluetooth calls but if you don't use that feature you could use their Pie version as well.
RR ROMs are solid and work extremely well.
Do a clean installation via TWRP if you go this route.
Click to expand...
Click to collapse
I did a clean installation of RR 6.0.0 (Android 8.1) and it works a lot better than LineageOS did, with even more configuration options. I really really hate Pie and its gesture-based gimmicks (Screw you Google for copying more of Apple's bad design decisions), so I assumed Oreo would be more stable, but the ROM I installed still has crashing apps. Google Chrome still won't download most things (I've gotten it to download before), trying to change the accent color crashes the 'LineageOS Settings' app, and F-Droid is seriously messed up, but most other things are stable, including the Verizon network which required no pesky APN setup.
I'm on the OB6 bootloader/modem, is that a problem? I doubt that would be an issue, but I can always back up and reflash via Odin. The cool thing is that I installed a patch to TWRP which backs up /data/media along with everything else, after installing the custom ROM. So, really, I can do anything and be perfectly fine. There's, AFAIK, no way to ruin the phone unless something exploits the eMMC brick bug.
If there's another ROM you'd recommend me install, I'd be happy to try it out. I would really like to have a stable OS on here, where Chrome will work and download files. I'd also love Camera2 API since the phone has the chip for it (Snapdragon 800), but none of the ROMs I have support it and there's been no discussion online other than some years-old threads with no answers. I know there have been some articles online listing Note 3 as a phone that'd support Camera2 API with a software update. Would updating the bootloader/modem do anything on that front?
I would upgrade to PL1 bootloader/modem for your device. This is what I have and have had 0 issues. I'd recommend you trying the Samsung Internet browser over Google Chrome; it's much better in my opinion.
You can find the modem here:
https://androidfilehost.com/?w=files&flid=160694
As far as ROMs are concerned you can either try the Nougat version of RR which is what I am currently using as my daily driver with no issues at all including Bluetooth calls:
[ROM][HLTE\TMO\CHN][OFFICIAL]*** Resurrection Remix N 5.8.5 ***[13.03.2018]
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
See here to check whether or not your phone has the Camera2 API capabilities; if not use OpenCamera.
https://www.androidexplained.com/camera2-api-support/
terminator911 said:
I would upgrade to PL1 bootloader/modem for your device. This is what I have and have had 0 issues. I'd recommend you trying the Samsung Internet browser over Google Chrome; it's much better in my opinion.
You can find the modem here:
https://androidfilehost.com/?w=files&flid=160694
As far as ROMs are concerned you can either try the Nougat version of RR which is what I am currently using as my daily driver with no issues at all including Bluetooth calls:
[ROM][HLTE\TMO\CHN][OFFICIAL]*** Resurrection Remix N 5.8.5 ***[13.03.2018]
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
See here to check whether or not your phone has the Camera2 API capabilities; if not use OpenCamera.
https://www.androidexplained.com/camera2-api-support/
Click to expand...
Click to collapse
Excuse me but custom ROMs don't have "the Samsung Internet browser". Additionally the modem shouldn't cause app crashes (if it does, correct me please).
I might try the Nougat ROM. Bluetooth calls don't matter to me, but stability does. I just kinda really like Oreo and all its customization options but it may be too new for this old phone from 2013. It still works as a phone though, Messages and phone calls work fine, so I may just deal with it.
I use Open Camera, and I've tried multiple Camera2 API enablers. The phone has a Qualcomm Snapdragon 800 and the necessary links (in hardware, between the camera/other things) to support Camera2, but nobody seems to have tried it. Probably because the Verizon Note 3 is really locked down, and can only be rooted on a special version of the samsung ROM, and can only be bootloader-unlocked via the eMMC brick bug... There are Magisk modules for Camera2 on Exynos-based devices, but none for the Verizon Note 3 AFAIK.
I just found out that RR 7 officially supports `hltetmo`, but RR 6 doesn't. That's kinda sad, I hate Pie, but I might try it...
I've had the SEPL stuff before, that's the one that can't be rooted. I suppose I didn't consider upgrading again after I unlocked my bootloader. I'll try SEPL1 firmware again, but with a custom ROM...
You can install the Samsung browser from the Play Store. Again, highly recommended.
As far as SEPL1 just update the modem to it; that shouldn't cause any issues but it will ensure your SIM is recognized and data works with the latest ROMs. That is one requirement you will see listed on all of these ROMs.
Not sure which one you are trying to install but here are all the Resurrection Remix versions:
Nougat:
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
Oreo:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrection-remix-n-6-0-0-t3748689
Pie:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrectionremix-v7-0-0-t3894244
If you don't care about Bluetooth audio during calls then you can safely use Oreo and Pie options.
terminator911 said:
You can install the Samsung browser from the Play Store. Again, highly recommended.
As far as SEPL1 just update the modem to it; that shouldn't cause any issues but it will ensure your SIM is recognized and data works with the latest ROMs. That is one requirement you will see listed on all of these ROMs.
Not sure which one you are trying to install but here are all the Resurrection Remix versions:
Nougat:
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
Oreo:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrection-remix-n-6-0-0-t3748689
Pie:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrectionremix-v7-0-0-t3894244
If you don't care about Bluetooth audio during calls then you can safely use Oreo and Pie options.
Click to expand...
Click to collapse
Yeah but, data and calling worked fine on the LineageOS and RR roms, so there's no reason to update the modem.
Besides, I flashed SEPL1 6 times using Odin (multiple times by flashing, rebooting directly into download mode and flashing it once more) and it doesn't want to update. Still on OB6. On the latest (official Pie) RR rom, data worked on first boot but doesn't work anymore (I'm going to mess around with the data settings until it works), but I have no reason to believe that my phone needs a modem update to function.
I did, many times, make calls to various phone numbers and they all worked flawlessly. SEPL1 is therefore not needed if that's all it does.
And I do know about all the Resurrection Remix versions: One is Nougat from their archive, one is the Oreo version I had installed just yesterday before flashing Pie, and the other one is Pie which is now officially supported.
I am currently working on getting RR7 to work, it's only crashed a few times, and I don't even remember what those times were (I think it was using the Back button in Overview/Recents at the same time as the Overview button?)
When updating modem via Odin you have to pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot. If you look at the ROM threads for anything newer than Android v5 they all recommend updating to the latest bootloader & modem for your device which in this case is PL1. This can be to prevent crashes/no signal /no SIM, etc...
Are you dirty flashing these ROMs? I have never experienced any crashes with any of the RRs on my phone but I always do a clean install and make sure to also delete the "Android" folder on my SD Card via TWRP after doing the "Advanced" wipe and deleting everything listed there except for the External SD Card.
terminator911 said:
When updating modem via Odin you have to pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot. If you look at the ROM threads for anything newer than Android v5 they all recommend updating to the latest bootloader & modem for your device which in this case is PL1. This can be to prevent crashes/no signal /no SIM, etc...
Are you dirty flashing these ROMs? I have never experienced any crashes with any of the RRs on my phone but I always do a clean install and make sure to also delete the "Android" folder on my SD Card via TWRP after doing the "Advanced" wipe and deleting everything listed there except for the External SD Card.
Click to expand...
Click to collapse
"pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot"
So...
- Reboot phone into Download mode
- Pull battery while in Download mode
- Flash thingy
- Reboot back into Download mode
- Flash thingy again
? That will be very difficult to do with my dodgy charging cable that doesn't like being repositioned...
I do that without pulling the battery, but I could try it with.
I'm downloading the full SEPL stock image to flash. Once that's done, I'll flash it, reflash TWRP, restore my backup, and see if the baseband has updated.
And no, never dirty flashed the ROM. Always completely wiped data, system, cache and everything. I always backup first. I currently have 3 backups: Lineage OS (before installing RR), RR6 (Oreo), and RR7 (right now before that stock image I'm going to flash).
My external SD card is nonfunctional and read-only with some trash files from the previous phone.
I flashed the stock SEPL ROM. Baseband still didn't change. Restored from backup, SIM now works. Network is detected, SMS and data both work reliably on all reboots.
I will mention that I did brick my phone by using Odin to erase the eMMC, but I fixed that from TWRP, and now everything works flawlessly. There are still some app crashes, but most things are very stable. Camera2 API still nonexistent, which is sad because I got used to it on my old phone, but I shouldn't hope for it.

Categories

Resources