Database Users

I9505 random reboots

Hi! I recently updated my i9505 to the xugng8 firmware via kies. Ever since, my phone has been randomly rebooting itself. The reboots are quick enough, so it doesn't look like the phone is completely rebooting, more like a half reboot. I have tried formating, but that didn't help. I have the phone rooted but using stock firmware.
Any ideas what could be causing this? Thanks

juzzy16 said:
Hi! I recently updated my i9505 to the xugng8 firmware via kies. Ever since, my phone has been randomly rebooting itself. The reboots are quick enough, so it doesn't look like the phone is completely rebooting, more like a half reboot. I have tried formating, but that didn't help. I have the phone rooted but using stock firmware.
Any ideas what could be causing this? Thanks
Click to expand...
Click to collapse
You have to uninstall every Knox app, that will stop the reboots
Sent from my Galaxy S4 using Tapatalk

juzzy16 said:
Hi! I recently updated my i9505 to the xugng8 firmware via kies. Ever since, my phone has been randomly rebooting itself. The reboots are quick enough, so it doesn't look like the phone is completely rebooting, more like a half reboot. I have tried formating, but that didn't help. I have the phone rooted but using stock firmware.
Any ideas what could be causing this? Thanks
Click to expand...
Click to collapse
Remove all Knox related apps via "Titanium Backup" and you are good to go. :good:

there is also an xposed module that deals with these random reboots, but personally i think the best way is to revert to an earlier firmware. fnb8 is rock solid.

I have just upgraded my firmware to NG8 (UK) and my phone reboots randomly, no matter what I am doing. After receiving a call, using gmaps, etc..
I will try the suggested solution with removing the knox sh*t and report back.

Yes
juzzy16 said:
Hi! I recently updated my i9505 to the xugng8 firmware via kies. Ever since, my phone has been randomly rebooting itself. The reboots are quick enough, so it doesn't look like the phone is completely rebooting, more like a half reboot. I have tried formating, but that didn't help. I have the phone rooted but using stock firmware.
Any ideas what could be causing this? Thanks
Click to expand...
Click to collapse
Yes, same problem here exactly. Any solution to fix this WITHOUT ROOT or reverting back to xxufnb9 ?

I found that uninstalling all knox apps and resetting a private app fixed my problem. I have been restart free for the last 2 days! I suggest using BBS to find out what app is causing wakes and reset them.
nm8 said:
I have just upgraded my firmware to NG8 (UK) and my phone reboots randomly, no matter what I am doing. After receiving a call, using gmaps, etc..
I will try the suggested solution with removing the knox sh*t and report back.
Click to expand...
Click to collapse
wuwinso said:
Yes, same problem here exactly. Any solution to fix this WITHOUT ROOT or reverting back to UGNF ?
Click to expand...
Click to collapse

juzzy16 said:
I found that uninstalling all knox apps and resetting a private app fixed my problem. I have been restart free for the last 2 days! I suggest using BBS to find out what app is causing wakes and reset them.
Click to expand...
Click to collapse
yup same here after reading this thread and removing all knox crap.... phone has not had a self reboot reboot for the day...

Revert
Had to reflash the old XXUFNB9, it was useless with all those restarts. Downgrade went okey, however need to delete the Media Storage `s cache because it will keep crashing. Testing now if it solved the problem.
Update 1: after 2 hours later no restart so far..
I recommend this solution who doesn`t want to loose everything and risking if a factory reset will solve this issue. There is a problem with the KNOX 2.0 update (XXUGNG8) ...
Update 2: Link for the firmware, for whoever choose to do this way: http://www.sammobile.com/firmwares/3/?download=31852

Ok, just a quick update, I have used googlemaps for 2 hours, and tomtom navigator for 1 hour on my S4, made and received a few calls without issue. No REBOOTS.. I think it was definitely the knox crap...

juzzy16 said:
I found that uninstalling all knox apps and resetting a private app fixed my problem. I have been restart free for the last 2 days! I suggest using BBS to find out what app is causing wakes and reset them.
Click to expand...
Click to collapse
nm8 said:
Ok, just a quick update, I have used googlemaps for 2 hours, and tomtom navigator for 1 hour on my S4, made and received a few calls without issue. No REBOOTS.. I think it was definitely the knox crap...
Click to expand...
Click to collapse
Stabil for 3 hours or 2 days - well that's for sure great ....
You both must be joking - take older NB8 and you can have an uptime of > 1 month without any problem,
All newer version are worse -
As s.o. mentioned, there is an Xposed Modul made by Thomas Hofmann that tries to solve this. This is not a Knox problem but seems to be in AOSP itself - although might mainly be triggered by Knox 2.0 (NB8 is still Knox 1.0). In general situation goes worse the more processes are started, i.e. with heavy load. It is said to happen not only with S4 but e.g. also with N3.
As Thomas Hofmann stated: "I figured out that actually the system server process crashed due to an ArrayIndexOutOfBoundsException"
If you want to know details plz have a look at Thomas's blog. With his modul he mainly catches a faulty parameter value that would otherwise cause a certain method to crash. As a result he manages to avoid the reboot but of course the real problem goes deeper, so to fix this for real Google / Samsung are needed.
=> I want a 4.4.4 rom with towelroot fixed, without those ArrayIndexOutOfBoundsExceptions and as solid as NB8 - but I doubt Samsung is able or willing to do this.

I am using STOCK i9505 4.4.2 ROM which is rooted. I don't use towelroot because I don't have to. I also try to stay away from premade Roms and Kernels beause i don't have time to test and tinker with eveything.
After a few days of removing knoxcrap, I can conclude, that it is the issue with my phone. My i9505 is now working perfectly......

Have to agree with you. Since removing all the knox stuff, Haven't had a reboot since! Been over a week now at this stage!
nm8 said:
I am using STOCK i9505 4.4.2 ROM which is rooted. I don't use towelroot because I don't have to. I also try to stay away from premade Roms and Kernels beause i don't have time to test and tinker with eveything.
After a few days of removing knoxcrap, I can conclude, that it is the issue with my phone. My i9505 is now working perfectly......
Click to expand...
Click to collapse

no random rebooting anymore xugng8 firmware
juzzy16 said:
Hi! I recently updated my i9505 to the xugng8 firmware via kies. Ever since, my phone has been randomly rebooting itself. The reboots are quick enough, so it doesn't look like the phone is completely rebooting, more like a half reboot. I have tried formating, but that didn't help. I have the phone rooted but using stock firmware.
Any ideas what could be causing this? Thanks
Click to expand...
Click to collapse
i have sorted my i9505 to the xugng8 firmware by re-installing with latest odin...download fresh stock firmware xugng8 firmware and i re-installed 2 weeks now no reboot ,but make sure before you do these steps usb debuging mode is selected ,rest you all know

nm8 said:
I don't use towelroot because I don't have to.
Click to expand...
Click to collapse
Yes, many think this to be a nice 'feature' to get root, but that rediculous. Towelroot (plus the older Exynos bug - but that was Samsung specific) is the biggest bug in Android since many years. Using a kernel that is not hardened against this (this unfortunately includes the otherwise almost perfect NB8 rom) could mean you couldn't be save anymore from someone taking over your phone unnoticed using root authorization.
---------- Post added at 02:20 PM ---------- Previous post was at 02:08 PM ----------
juzzy16 said:
Have to agree with you. Since removing all the knox stuff, Haven't had a reboot since! Been over a week now at this stage!
Click to expand...
Click to collapse
As said those reboots most certaintly are caused by a bug in AOSP code itself - but in fact they seem to be mainly triggered by Knox 2.0. Otherwise a lot more phones other than S4 or N3 should be involved.
As we will never know fpr sure if and when Google/Samsung will solve the real reason of this problem and "removing" Knox 2.0 seems to help, it would be very nice of you (juzzy16, nm8, sneazy) to perhaps add another comment in 2-3 weeks about reboot behaviour again including the rom version you are using and what exactly of Knox you had removed.:good:

[Q] wifi greyed out after update lollipop

Hello
I'm comming from jellybean and i just did an update with odin to lollipop. I've 2 problems.
1: the wifi is greyed out and i can't turn it on.
2: I can't open the playstore and i can't add my google account in the account setting. I'm getting this message : google play services has stopped.
I did a clean flash ( wiped all data and restored to factory setting. I flashed the original lollipop rom now for the second time and thats not helping.
Does any one now a solution for this?

Did you check update bootloader option in odin?

rakesh5424 said:
Did you check update bootloader option in odin?
Click to expand...
Click to collapse
No i haven't done that. Is that the problem you think?

Think that is the problem reflash with update bootloader option checked and see..

rakesh5424 said:
Think that is the problem reflash with update bootloader option checked and see..
Click to expand...
Click to collapse
Ok I'll try it out and i'll let you now.

rakesh5424 said:
Think that is the problem reflash with update bootloader option checked and see..
Click to expand...
Click to collapse
I can't find : check update bootloader option in odin. I'm using odin v3.09. Sorry for this questions.

dejos123 said:
I can't find : check update bootloader option in odin. I'm using odin v3.09. Sorry for this questions.
Click to expand...
Click to collapse
Never mind i found it

Update google play services. In setting, manager app, wipe data, cache google play, google play services, tap force close. reboot devices.

I have the same problem ..
Have you solved it ?
I already tried reflashing with updating bootloader but still the same ..
flashed some custom kernel (AEL v2, CivZ explorer Rev3.1) but wifi remain grayed ...

Hello
Yes it's working fine now for me. The update bootloader solved the problem for me. Do you have exactly the same problems that i had?

Yes .. have the same problem
what should i do to make it working ?
I ticked the phone bootloader update but it flashed it and booted quickly ..(the first boot Doesn't take time )
I wonder if i made some thing wrong

amged2012 said:
Yes .. have the same problem
what should i do to make it working ?
I ticked the phone bootloader update but it flashed it and booted quickly ..(the first boot Doesn't take time )
I wonder if i made some thing wrong
Click to expand...
Click to collapse
Did you wipe cache and set to factory settings? That's what i did and it worked.

dejos123 said:
Did you wipe cache and set to factory settings? That's what i did and it worked.
Click to expand...
Click to collapse
Before or after flashing ?
I did wipe after flashing but nothing changed wifi remained gray

Stuck like the others
Im having the same issue. Tried flashing the rom multiple times, also my gps no longer locks except when it feel the need. Had a shop look at the gps and they replaced the antenna for the GPS and said it was good to go and gave me an app (GPS Status & Fix) and said it was all free of charge. I feel as if the rom i got from Sam caused this. Any help would be great.

I'm having exact same issue. How did you guys solve it?
Thanks

Hello there! I have a two problems wifi and BT doesn't work or greyed. Any possible things to fix them? These were my issues before on my note 2. I flashed new firmware for note 2 then the issues fixed, so do you think flashing note 4 firmware would actually help or fix the issues for my note 4 now?

This is not Note 4 forum .
Ask in N4 forum .
Sent from my SM-N930F using XDA-Developers Legacy app

[Q] Error - Process com android not responding! Pls. Help!

Hello frnds!
I am using Samsung S3 NEO with Stock ROM and without ROOT but from the last 3 days, I am unable to use the device! Every 5 seconds this error pops up - Process.com android not responding!
I am simply unable to use the device! Can't even call someone!
I tried a factory reset but of no use! This error still prevails but the occurence duration has been reduced! But, still m unable to use the fon as it just hangs up in between anything and everything!
Pls. help me with it's solution asap! What should I do? Pls...
UPDATE - It asked for updating and I updated my device to 4.4.4 (Stock).
But still, the phone still hangs a lot but the error has changed! Earlier, it showed - Process com android not responding!
But now, it shows - Google Play, Google TV, Google Calendar has stopped working!
These types of errors are being displayed and m still unable to use my device! Pls. let me know it's solution!

techie_vintage said:
Hello frnds!
I am using Samsung S3 NEO with Stock ROM and without ROOT but from the last 3 days, I am unable to use the device! Every 5 seconds this error pops up - Process.com android not responding!
I am simply unable to use the device! Can't even call someone!
I tried a factory reset but of no use! This error still prevails but the occurence duration has been reduced! But, still m unable to use the fon as it just hangs up in between anything and everything!
Pls. help me with it's solution asap! What should I do? Pls...
UPDATE - It asked for updating and I updated my device to 4.4.4 (Stock).
But still, the phone still hangs a lot but the error has changed! Earlier, it showed - Process com android not responding!
But now, it shows - Google Play, Google TV, Google Calendar has stopped working!
These types of errors are being displayed and m still unable to use my device! Pls. let me know it's solution!
Click to expand...
Click to collapse
Try to flash the stock firmware via odin. You can download it on sammobile's firmware section

koroveshi said:
Try to flash the stock firmware via odin. You can download it on sammobile's firmware section
Click to expand...
Click to collapse
Have tried this also! Didn't work! The fon simply doesn't respond at all! M unable to use it!!
Any other solution pls??

Thanks to the bad gplay updates, the software is pretty bugged. Just download the stock firmware and check checksums before flash. Or flash custom rom from the section down below.

Dont know if you already tried but did you do a factory reset after the 4.4.4 update. I know OTA updates shouldn't mess stuff but sometimes they do.

koroveshi said:
Try to flash the stock firmware via odin. You can download it on sammobile's firmware section
Click to expand...
Click to collapse
I have tried this but of no help!
mandzo said:
Dont know if you already tried but did you do a factory reset after the 4.4.4 update. I know OTA updates shouldn't mess stuff but sometimes they do.
Click to expand...
Click to collapse
I even did a factory reset but of no use!
MoHuToP said:
Thanks to the bad gplay updates, the software is pretty bugged. Just download the stock firmware and check checksums before flash. Or flash custom rom from the section down below.
Click to expand...
Click to collapse
I had flashed CM12 (5.1.1). It all went well - the flashing & all! But, i cudn't make any calls!
I have installed this ROM on my S3 Neo! But, m unable to make any call (From the SIM 1. Haven't used SIM 2 coz of the Audio prob being faced in the SIM 2 as mentioned in the thread). Whenever I make a call (sim 1), it gives an error - PROCESS SYSTEM ISN"T RESPONDING! Do u want to close it?
Even if i Click WAIT, nothing happens, there;s just a green screen being continuously displayed for about 30 seconds and then automatically, it gets back to the HOME SCREEN~!
I am unable to receive any incoming call also! The fon automatically reboots if a call comes and once it restarts, it shows the log in MISSED CALL!
Pls. Help! How to solve this out?
UPDATE :- I flashed CM11 after this problem thinking it might solve the problem but of no use again! Even, after installing CM11, I am unable to make any calls! The screen just goes blank! And then automatically gets back to the home screen! It's not showing the error of PROCESS SYSTEM NOT RESPONDING as it used to show up in CM12!
Now, pls. some one tell me it's solution at the earliest!! Pls..

techie_vintage said:
I have tried this but of no help!
I even did a factory reset but of no use!
I had flashed CM12 (5.1.1). It all went well - the flashing & all! But, i cudn't make any calls!
I have installed this ROM on my S3 Neo! But, m unable to make any call (From the SIM 1. Haven't used SIM 2 coz of the Audio prob being faced in the SIM 2 as mentioned in the thread). Whenever I make a call (sim 1), it gives an error - PROCESS SYSTEM ISN"T RESPONDING! Do u want to close it?
Even if i Click WAIT, nothing happens, there;s just a green screen being continuously displayed for about 30 seconds and then automatically, it gets back to the HOME SCREEN~!
I am unable to receive any incoming call also! The fon automatically reboots if a call comes and once it restarts, it shows the log in MISSED CALL!
Pls. Help! How to solve this out?
UPDATE :- I flashed CM11 after this problem thinking it might solve the problem but of no use again! Even, after installing CM11, I am unable to make any calls! The screen just goes blank! And then automatically gets back to the home screen! It's not showing the error of PROCESS SYSTEM NOT RESPONDING as it used to show up in CM12!
Now, pls. some one tell me it's solution at the earliest!! Pls..
Click to expand...
Click to collapse
Maybe an EFS error, restore EFS partition and see if permissions are set correctly

sev3n1985 said:
Maybe an EFS error, restore EFS partition and see if permissions are set correctly
Click to expand...
Click to collapse
I have a query! Is EFS only meant for IMEI related probs? Just asking becoz my fon is showing the IMEI Number and i am able to send and receive sms but problem is only with the calling! Can't make or receive any call!!

techie_vintage said:
I have a query! Is EFS only meant for IMEI related probs? Just asking becoz my fon is showing the IMEI Number and i am able to send and receive sms but problem is only with the calling! Can't make or receive any call!!
Click to expand...
Click to collapse
Try with a complete wipe of cache, system, data, dalvik, and internal memory, after that reinstall cm11 rom

sev3n1985 said:
Try with a complete wipe of cache, system, data, dalvik, and internal memory, after that reinstall cm11 rom
Click to expand...
Click to collapse
I just tried this too but the problem still exists!! I am unable to call!!! What should I do now?

"Camera error please restart camera"

I am on stock rom and rooted using the Super SU method. The only things I've flashed are the wifi fix, and edited build.prop to unlock tethering. My camera app will not open, and I get this error every single time. Doesn't work in instagram, snapchat, nothing. Anyone know what may be causing this?

Anyone? I would really like to get my camera working again

had the same problem today. restarted the phone and it worked again

ckret said:
had the same problem today. restarted the phone and it worked again
Click to expand...
Click to collapse
I've restarted several times even gone so far as to install a new OS. I'm thinking about undoing the changes just to fix this.

Try booting in Safe mode

ckret said:
Try booting in Safe mode
Click to expand...
Click to collapse
Camera still doesn't work

your cam may be disconnected from the motherboard. try claiming warranty

Wiped and installed the AOKP ROM and that fixed it.. Could've been the ROM or could've been the wipe, although I wiped several times before and it didn't fix it.

did you get the error again?
I had the same problem and I installed AOKP rom which fixed it at the beginning but after less 1 day the error back again.
now I'm on stock rom .35 (rooted with Magisk) and no camera error so far after 4 days

As far as i know, it is due to custom kernel, you may have installed that.. try flashing stock rom without any custom kernel..

Mayanknagpal.nm said:
As far as i know, it is due to custom kernel, you may have installed that.. try flashing stock rom without any custom kernel..
Click to expand...
Click to collapse
yes, I had custom kernel first time I got the error.
but then I got it also with custom rom.
now I'm on stock rom and stock kernel....but does it mean that I can never flash custom rom/kernel because of that error?

marcol87 said:
yes, I had custom kernel first time I got the error.
but then I got it also with custom rom.
now I'm on stock rom and stock kernel....but does it mean that I can never flash custom rom/kernel because of that error?
Click to expand...
Click to collapse
Custom roms do not have that error... and on stock rom you can use elementalX 2.0 , it is made for the .67.. so the camera issue is resolved.. i think this will help

I had this error on Stoneware .67 (stock based ROM) and resolved it by dirty flashing Stoneware and Magisk v.13 again.

and I had this error also on AOKP rom

I have been having this problem on the Stock ROM, non-rooted, for quite some time now. I have no idea what's causing this error. When I open it sometimes, it just throws an error. If I close it and open it again, it works as it should. It's very annoying.

I had the same thing, flashing roms didnt fix it so i flashed stock via RSD lite and everything was back to normal.

Same issue here, completely stock unrooted. This is not the first Android device I've had that's struggled to connect to the camera consistently... how hard can it be?

Can people getting this error try to disable the image stabilisation in video mode please? One of the errors I see when downloading a bug report refers to the stabilisation code and I've not had the "please restart camera" message since switching it off. Could be coincidence though as it's not like I get it every time the camera loads...

Hello ,
I tried rooting my Moto G5 using Moto G5 toolkit (flashing superSU). t
Then I flashed TWRP and Flashed the WLAN_CUSTOM
Now i get that generic warning screen of unlocked boot loader however My phone is not rooted. and I cant open camera at all , getting error as " Camera Busy - Camera unable to start. If this happens again, please power off your phone and restart."
Can someone help me fix this camera issue? or just help me to revert back as it was previously no root nothing, I guess this TOOLKIT has some bugs in it.
Any help will be appreciated as I am newbie with this android development.

the.MindHacker said:
Hello ,
I tried rooting my Moto G5 using Moto G5 toolkit (flashing superSU). t
Then I flashed TWRP and Flashed the WLAN_CUSTOM
Now i get that generic warning screen of unlocked boot loader however My phone is not rooted. and I cant open camera at all , getting error as " Camera Busy - Camera unable to start. If this happens again, please power off your phone and restart."
Can someone help me fix this camera issue? or just help me to revert back as it was previously no root nothing, I guess this TOOLKIT has some bugs in it.
Any help will be appreciated as I am newbie with this android development.
Click to expand...
Click to collapse
I had the same issue as you after using the toolkit, did you fix it?

Nexus 6P Latest 'O' update Killed messaging & Texting - help

Hey' y'all Color be crazy but....
About 3 days ago I checked for updates OTA, and got a new sequrity patch.
but the last 3 days since...
Phone calls Go right to my voicemail box they dont even ring on my phone....
And my [defualt]texting app constantly shows a little cloud crossed out saying no service
Anywheres I had 4gLTE Is now 3g ONLY and i can only do things on the internet thats it, but its slow as a dog.
Airplane mode on-off doesn't work I dialed that *#*# .. (insertnumbers) #*#* for testing and
switching how my phone recieves signal didn't work,
Factory reset from inside my settings + Hard reset from recovery made 0 difference.
Ill recieve all my texts but cant reply to them by rebooting my phone they all come in at once when my phone turns on but them my message app stops working again
-----------
Called my provider (TOTAL WIRELESS,) They said everything fine on thier end nothing they can do. So I called Huawai, and Verizon... got no where.
So im thinking... Its the update patch, or i need a new sim card.. So where / how Do I get the Nexus 6p's STOCK ROM So I can reinstall and how do i do that?
Should i try that? wait for another patch? or request a new sim.... Because as of right now my phones a brick and i use it for work.

Fluttershy_plays said:
Hey' y'all Color be crazy but....
About 3 days ago I checked for updates OTA, and got a new sequrity patch.
my phones a brick and i use it for work.
Click to expand...
Click to collapse
Your not alone my friend I had the same issue with Aprils update. Just randomly during the day I would stop receiving texts and phone calls. I just assumed I was in some kind of bad zone even though had never happened before. Wasn't until my favorite stock build SuperXe got updated to Mays that I switched and haven't had the problem since. Right now I'm on Lineage 15's June build and wow it has come a long way pretty solid no issues. You will have to do some research on unlocking your bootloader and flashing stock images. You can find them if you search "Google API Nexus 6p." Check out Hiesenbergs tutorials on XDA on returning to stock on the flashing procedure. Its the same for flashing stock images of any month you choose. I got simple fastboot 1.4.3 from XDA as well instead of installing Google's fastboot .

Exodusche said:
Your not alone my friend I had the same issue with Aprils update. Just randomly during the day I would stop receiving texts and phone calls. I just assumed I was in some kind of bad zone even though had never happened before. Wasn't until my favorite stock build SuperXe got updated to Mays that I switched and haven't had the problem since. Right now I'm on Lineage 15's June build and wow it has come a long way pretty solid no issues. You will have to do some research on unlocking your bootloader and flashing stock images. You can find them if you search "Google API Nexus 6p." Check out Hiesenbergs tutorials on XDA on returning to stock on the flashing procedure. Its the same for flashing stock images of any month you choose. I got simple fastboot 1.4.3 from XDA as well instead of installing Google's fastboot .
Click to expand...
Click to collapse
Could you help me find that? not sure 100% on navigation of this website but ill try.

Exodusche said:
Your not alone my friend I had the same issue with Aprils update. Just randomly during the day I would stop receiving texts and phone calls. I just assumed I was in some kind of bad zone even though had never happened before. Wasn't until my favorite stock build SuperXe got updated to Mays that I switched and haven't had the problem since. Right now I'm on Lineage 15's June build and wow it has come a long way pretty solid no issues. You will have to do some research on unlocking your bootloader and flashing stock images. You can find them if you search "Google API Nexus 6p." Check out Hiesenbergs tutorials on XDA on returning to stock on the flashing procedure. Its the same for flashing stock images of any month you choose. I got simple fastboot 1.4.3 from XDA as well instead of installing Google's fastboot .
Click to expand...
Click to collapse
Found his guide but..
I got to step 6 in his guide, rooting. and now my phone wont boot past google logo
--EDIT--
Fixed by going back to stock and starting over.

Fluttershy_plays said:
Found his guide but..
I got to step 6 in his guide, rooting. and now my phone wont boot past google logo
Click to expand...
Click to collapse
Ok first you want to boot up and finish initial setup before rooting. Second you want to root with Magisk 16.0 zip. You don't have to root unless your planning on modifying system files or using a special app. You can fix or unroot by reflashing just the boot.img from the firmwarwe or Rom you are currently running .

Exodusche said:
Ok first you want to boot up and finish initial setup before rooting. Second you want to root with Magisk 16.0 zip. You don't have to root unless your planning on modifying system files or using a special app. You can fix or unroot by reflashing just the boot.img from the firmwarwe or Rom you are currently running .
Click to expand...
Click to collapse
well i got up and running (8.0 no updates yet) and my 4g lte / Texting capabilities ARE BACK!!!!.
Also, Can i still root, APP side? or does it have to be through flash?
thanks for pointing me in the right direction!
Is there a way to report this issue to google so they can fix it?

Fluttershy_plays said:
well i got up and running (8.0 no updates yet) and my 4g lte / Texting capabilities ARE BACK!!!!.
Also, Can i still root, APP side? or does it have to be through flash?
thanks for pointing me in the right direction!
Is there a way to report this issue to google so they can fix it?
Click to expand...
Click to collapse
I'm sure there's a way to root with app but just as easy to flash TWRP and install Magisk. Which has nice easy feature of hiding root and passing safety net. That way you get a certified playstore and still use android pay to name a few. If your interested let me know I can explain the process after flashing Magisk.