LG G2 D02 CM 13 Problems - G2 Q&A, Help & Troubleshooting

My boss rooted his LG G2-D02 and installing CM 12.1 in the process. Now, after knowing that CM 13 was already released, he downloaded a copy of it and immediately flashed it onto his phone. He got a problem with Gapps and DL-ed a problematic version which caused the notification,"Unfortunately, Setup Wizard has stopped" to pop up repeatedly. We had tried following a few advices from this website but to no avail.
1.) We already tried using Force Stop and Disable under Apps->(Show system apps)->Setup Wizard (CM). I had also tried giving it app permissions, but all app permissions were already available.
2.) The only option is to flash CM 12.1 back again but it can't be done. My boss set the default recovery app to Cyanogenmod's own recovery program, which had limited functions, so I can't
also use TWRP ATM.
3.) My boss also tried something on ADB but to no avail
4.) Factory reset didn't also solve the problems.
I'm almost running out of solutions... Perhaps, I can use a helping hand from brighter minds in this community.
TIA

I'm using cloudyg2 v3.3 because cm13 has got a lot of bug for example
-I can't proceeded to music
-systtem has stopped once a hour
-I can't close touching vibration
I can't remember now but cm13 has got really much bug (yeah my english is very bad,I know this)

Now system is stable and battery is very very good but still İ can't scretch to music

Related

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

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.

H918 WETA ROM 4.9.4 + Magisk 12.0 bootlooping

Hello there, I've been using the V20(H918) for a little while now and was running WETA Rom 4.8.5 with Magisk 11.0. When Magisk 12.0 released after rebooting and being on for a minute or 2 my phone would suddenly go back to the T-mo splash screen as if it were soft rebooting and then would repeat this process. I thought it might have been a download or flash issue so I tried wiping and doing a fresh install but if I ever restarted the device the same issue would appear. I've tried selecting or deselecting a majority of the options in the aroma installer for WETA but nothing seems to work. The rom seems to work fine with SuperSU installed so I'm thinking it might be something about the way my phone is set up but I haven't been able to pinpoint exactly what it is and I really would like to use Magisk for the hide feature. Based on the thread it doesn't seem like there should be any issues and I'm unable to ask my question directly in the thread. I'm not very experienced with these kinds of things so I'm sorry if I'm not being specific enough or if the solution is obvious. Thanks for anyone's help and time with this issue!
survivingarch said:
Hello there, I've been using the V20(H918) for a little while now and was running WETA Rom 4.8.5 with Magisk 11.0. When Magisk 12.0 released after rebooting and being on for a minute or 2 my phone would suddenly go back to the T-mo splash screen as if it were soft rebooting and then would repeat this process. I thought it might have been a download or flash issue so I tried wiping and doing a fresh install but if I ever restarted the device the same issue would appear. I've tried selecting or deselecting a majority of the options in the aroma installer for WETA but nothing seems to work. The rom seems to work fine with SuperSU installed so I'm thinking it might be something about the way my phone is set up but I haven't been able to pinpoint exactly what it is and I really would like to use Magisk for the hide feature. Based on the thread it doesn't seem like there should be any issues and I'm unable to ask my question directly in the thread. I'm not very experienced with these kinds of things so I'm sorry if I'm not being specific enough or if the solution is obvious. Thanks for anyone's help and time with this issue!
Click to expand...
Click to collapse
alot of people have this problem with 12.0 flash the 11.0 and dont update
survivingarch said:
Hello there, I've been using the V20(H918) for a little while now and was running WETA Rom 4.8.5 with Magisk 11.0. When Magisk 12.0 released after rebooting and being on for a minute or 2 my phone would suddenly go back to the T-mo splash screen as if it were soft rebooting and then would repeat this process. I thought it might have been a download or flash issue so I tried wiping and doing a fresh install but if I ever restarted the device the same issue would appear. I've tried selecting or deselecting a majority of the options in the aroma installer for WETA but nothing seems to work. The rom seems to work fine with SuperSU installed so I'm thinking it might be something about the way my phone is set up but I haven't been able to pinpoint exactly what it is and I really would like to use Magisk for the hide feature. Based on the thread it doesn't seem like there should be any issues and I'm unable to ask my question directly in the thread. I'm not very experienced with these kinds of things so I'm sorry if I'm not being specific enough or if the solution is obvious. Thanks for anyone's help and time with this issue!
Click to expand...
Click to collapse
Im currently running weta rom with magisk 12.0 on my h918. However there are 2 possible differences between yours and mine. 1) you are not in the latest version of weta rom 4.9.4. 2) you are probably flashing the stock kernel that comes in the weta aroma installer. Try with konvergent or another kernel other than the one from weta rom. (as soon as i flashed the weta kernel my phone was experiencing the dame thing yours did , then after i flashed konvergent back it came back to normal)
jinkerz9430 said:
Im currently running weta rom with magisk 12.0 on my h918. However there are 2 possible differences between yours and mine. 1) you are not in the latest version of weta rom 4.9.4. 2) you are probably flashing the stock kernel that comes in the weta aroma installer. Try with konvergent or another kernel other than the one from weta rom. (as soon as i flashed the weta kernel my phone was experiencing the dame thing yours did , then after i flashed konvergent back it came back to normal)
Click to expand...
Click to collapse
Did what you said and everything seems to be running smoothly, thanks very much for your help! Hoping a more updated kernel that doesn't force SuperSU and works with magisk comes out soon!

Bootloop after installing whatsapp or updating app on cm13 Resurrection Remix Rom

Hello Guys,
pls help me.. after flashing cm13 RR ... when i m installing watsapp .. bootloop occurs.. camera 360 as well, i flashed stock fimware and the flashed cm13 rr ..but no luck
same problem
I have pretty much the same issue but it's not exclusive to whatsapp, other apps send the phone into a bootloop as well, this started a while ago, I installed the cm12 last year or so and it worked great for a long time, then after a while I tried to install the spotify app and things went south, phone went into bootloop so I deleted it from recovery mode and just ignored the issue. Yesterday I installed the cm13 hoping I would get a clean slate, I did everything right, full wipe, flashed the rom, gapps, patch and front cam fix and although everything kept crashing at first ( google launcher and pixel launcher) I eventually got it working, I installed messenger, worked fine, then tried to install whatsapp and it went into a bootloop. Anyone please help us.
DarudeNotSandstorm said:
I have pretty much the same issue but it's not exclusive to whatsapp, other apps send the phone into a bootloop as well, this started a while ago, I installed the cm12 last year or so and it worked great for a long time, then after a while I tried to install the spotify app and things went south, phone went into bootloop so I deleted it from recovery mode and just ignored the issue. Yesterday I installed the cm13 hoping I would get a clean slate, I did everything right, full wipe, flashed the rom, gapps, patch and front cam fix and although everything kept crashing at first ( google launcher and pixel launcher) I eventually got it working, I installed messenger, worked fine, then tried to install whatsapp and it went into a bootloop. Anyone please help us.
Click to expand...
Click to collapse
exactly.. we were on same page .. pls any one help us
I have the same issue on CM12. Phone get stuck in boot-loop after installing whatsapp latest version. I was able to get out of boot-loop after I deleted whatsapp app.
Its very important to use whatsapp. Please any fix for this?
I couldn't find a fix. The best you can do move to nougat ROMs like aicp or crdroid.
I installed crdroid and it's excellent
I too am now stuck on boot loop due to Whatsapp.
I do not need this app and will happily delete it, if this is what is causing the issues, but my problem is, how do I delete it now that I am stuck in a boot loop?
Enter safe mode and delete the app.
It's better to remove cm12 and install new ROM crdriod
GalaxyNote2_ said:
Enter safe mode and delete the app.
It's better to remove cm12 and install new ROM crdriod
Click to expand...
Click to collapse
Thanks for the reply.
This may sound a bit noob, but how do I get it into safe mode?
I have an Xperia Mini Pro SK17i
I managed to get it into recovery mode earlier, but cannot seem to get into safe mode
Yeah!
It happens in 5.1 / 6 custom roms!
Can any body help ??!!!
You need to read this thread. Every CM rom compiled before 2018 will have this problem.
https://forum.xda-developers.com/showpost.php?p=75391884&postcount=18

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