Galaxy S7 Edge force closing apps after debrand! - Samsung Galaxy S7 Edge Questions and Answers

Hi everyone, it can't explain what's happened to my phone.
My phone was WIND BRANDED and then i flashed a NO BRAND ROM (ITV) just after the unboxing. Odin said that everything was fine but after i booted it up every apps was force closing and this doesn't let me finish the startup configurations, it's so unstable and after some crashes the phone is rebooting.
I've tried a lots of italian's roms even with some PIT files that i have founded online and also with both Odin 3.12.3 and 3.11.1 but nothing worked, even after a Smart Switch recovery mode.
I thought that it's an hardware problem but when i was able to skip every configuration's step i have installed through an APK some apps for testing RAM, Memory, CPU and everything seems to working fine without problems.
I wish someone could help me because i need to find a solution, otherwise i have to apply the warranty for a refund or something but that will takes a lot of time.
Thank you so much.

Related

Phone rebooting, can't flash modem, other problems

I have some related problems with my phone which started happening a couple of days ago after updating Google Maps and a few other programs from the Play Store (Twitter also). That may not be relevant.
It's an Australian i9505 from Telstra. I'm on an old version of Omega ROM - v12 - with Adam Kernel 3.4.0. It's the latest that (the currently stalled) jKay can run on.
The main issue is that the phone reboots frequently. It seems like a "soft reboot" - the uptime reported in System Settings - > About device -> Status doesn't reset, but the time reported by Battery, for instance, does (and the whole UI reloads, programs, widgets etc)
This can happen in my pocket, or can be pretty reliably triggered by uninstalling a program, sometimes installing/updating, and sometimes from using Google Maps (embedded or the program itself).
The first time it happened was after the programs updated on the 5th of Feb.
Related issues:
I can't update the modem in Odin or Mobile Odin.
I tried upgrading to the latest pre-KitKat version, v19, which requires updating the modem.
Flashing the modem I already have did succeed, but that doesn't prove much.
I can update the recovery though - but I haven't tried installing a new rom because of the modem problem.
Rebooting into Recovery or Download mode from software fails - i.e. any of the "boot menu" programs/features. The phone shuts down but then stays turned off.
I can boot into them using the hardware buttons though.
Things I've tested:
It's not the SD card - it happens with it removed.
It's not the battery - I've got 3 batteries, none of which suffer from bloat, and it happens with all.
It's not water damaged - the nearest it got to rain was a couple of days earlier
From what I can tell, rolling back Google Maps, clearing data/cache for Google Services Framework or Google Play Services, all don't fix it.
Any suggestions?
Is my phone toast? Is there a rom I can install with included modem, perhaps?
Or should I at try unrooting and going back to stock? Triangle Away currently fails too, so I'm concerned that if it's a hardware problem Samsung won't fix it for me anyway.
frogworth said:
I have some related problems with my phone which started happening a couple of days ago after updating Google Maps and a few other programs from the Play Store (Twitter also). That may not be relevant.
It's an Australian i9505 from Telstra. I'm on an old version of Omega ROM - v12 - with Adam Kernel 3.4.0. It's the latest that (the currently stalled) jKay can run on.
The main issue is that the phone reboots frequently. It seems like a "soft reboot" - the uptime reported in System Settings - > About device -> Status doesn't reset, but the time reported by Battery, for instance, does (and the whole UI reloads, programs, widgets etc)
This can happen in my pocket, or can be pretty reliably triggered by uninstalling a program, sometimes installing/updating, and sometimes from using Google Maps (embedded or the program itself).
The first time it happened was after the programs updated on the 5th of Feb.
Related issues:
I can't update the modem in Odin or Mobile Odin.
I tried upgrading to the latest pre-KitKat version, v19, which requires updating the modem.
Flashing the modem I already have did succeed, but that doesn't prove much.
I can update the recovery though - but I haven't tried installing a new rom because of the modem problem.
Rebooting into Recovery or Download mode from software fails - i.e. any of the "boot menu" programs/features. The phone shuts down but then stays turned off.
I can boot into them using the hardware buttons though.
Things I've tested:
It's not the SD card - it happens with it removed.
It's not the battery - I've got 3 batteries, none of which suffer from bloat, and it happens with all.
It's not water damaged - the nearest it got to rain was a couple of days earlier
From what I can tell, rolling back Google Maps, clearing data/cache for Google Services Framework or Google Play Services, all don't fix it.
Any suggestions?
Is my phone toast? Is there a rom I can install with included modem, perhaps?
Or should I at try unrooting and going back to stock? Triangle Away currently fails too, so I'm concerned that if it's a hardware problem Samsung won't fix it for me anyway.
Click to expand...
Click to collapse
Hi,
A couple of things that you might try:
1. Look HERE
This should help with the flashing of the modem.
2.Do you have the knox-pox?
Check in download mode.
Is there anything about knox?
malybru said:
Hi,
A couple of things that you might try:
1. Look HERE
This should help with the flashing of the modem.
2.Do you have the knox-pox?
Check in download mode.
Is there anything about knox?
Click to expand...
Click to collapse
Hi there,
Thanks - I'll try that, although I've attempted flashing the modem a number of times. I'll uncheck autoreboot, but it never gets there because it fails during Download Mode.
I don't have knox - I'm still on an earlier bootloader.
frogworth said:
Hi there,
Thanks - I'll try that, although I've attempted flashing the modem a number of times. I'll uncheck autoreboot, but it never gets there because it fails during Download Mode.
I don't have knox - I'm still on an earlier bootloader.
Click to expand...
Click to collapse
Hi,
If that fails , and you want to get back to stock, Google for the MGA firmware.
This is the knox-free version.
Bear in mind that this will wipe your phone clean.
It is flashed in odin , and will replace your ROM,kernel ,modem and recovery.
Triangle Away should also work and you could then send in your phone for repair.
One thing if you do that , they will probably upgrade your phone to the latest knox-pox version.
Good luck
I'm trying to flash the modem again, but I'm noticing this error:
There is no PIT partition.
Is it worth flashing with a .pit file?
Or can you *only* flash a pit file when flashing firmware, not modems or recoveries?
frogworth said:
I'm trying to flash the modem again, but I'm noticing this error:
There is no PIT partition.
Is it worth flashing with a .pit file?
Or can you *only* flash a pit file when flashing firmware, not modems or recoveries?
Click to expand...
Click to collapse
Hi,
I would go for the stock MGA firmware flash.
Back up your stuff first.
If you still get errors , post your questions HERE
samersh72 is the expert in pit files.
UPDATE: so, at home I only have a Mac and I do my Odin stuff in VMware. 99% of the time it's fine, but updating my modem in order to flash the latest Omega ROM wasn't working.
At work, I plugged in my Samsung cable to one of the back USB ports, and had no problem flashing modem and pit file.
The problem with rebooting (into download, recovery or whatever) via software has gone away - *phew*
Then I installed latest Omega, same problem.
So I tried installing with full wipe - and from what I can see, it wasn't randomly rebooting - I could use Maps and remove Play Store apps with no problems.
Unfortunately upon restoring apps & settings with Titanium Backup, the problem returned. But I'm confident now that it's settings, so I won't need to restore to stock and take it back to Samsung at least!
I'll wipe again and post here when I resolve where the problem lies. Next attempt will be to restore user apps + data but not system data, or vice versa, and to be more selective... I'll crack this
I've now reinstalled the ROM again with a full wipe, didn't allow Google to reinstall my apps but instead got Titanium Backup to restore only non-system apps and data.
Of system data I've restored SMS/MMS messages, accounts, and WiFi access points only I think. I've redone the settings for everything else.
So far, all systems go - no reboots.
Oh and conversely, restoring ONLY system apps/data immediately brought the problem back.
I'm not that keen to keep restoring system data till I encounter the problem, since for now I seem to be back in business. W00t! :laugh: :good:
I have had similar issues. It seems like the internal sd has been formatted incorrectly. So i Google the I9505 pit file for Odin and stock firmware Knox free and everything worked straight away. Odin will format the internal sd with the pit file and then it will begin to flash stock firmware and you will have fresh s4 to work with.
Sent from my GT-I9505 using XDA Premium 4 mobile app
glennd said:
I have had similar issues. It seems like the internal sd has been formatted incorrectly. So i Google the I9505 pit file for Odin and stock firmware Knox free and everything worked straight away. Odin will format the internal sd with the pit file and then it will begin to flash stock firmware and you will have fresh s4 to work with.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks - yes, I did flash a pit file for i9505 and it did help the problem with booting into recovery/download mode via software.
But the crashing problem comes back anytime I restore all the system settings, so it's some weird bug with some buried setting - it's not Google Play Services or Google Maps, even though it's related to them. I've just stayed away from restoring practically any system settings and it's working for me.

Huge problem S4 not working anymore..

So this is my sad story..
I bought a second hand Samsung S4 (i337M Telcel) Unlocked, the day i got it, i tested in front of the seller everything was nice and smooth.. So i payed..
I was very excited and i proceed to make the Root proccess, at beginning i was having issues with the drivers and Odin, then i was able to fix it..
Anyways long story short i ended up with the ROOT, CYANOGENMOD CM11, and PHILZ 6.. The first day was working fine my cellphone.. (I must say i rooted in my life at least 4 devices even an S4 i9500 all of then with success and not a single problem.. Using them form months and even gears.. The latest was a Moto E..)
Ok so the i337M was working good since the first morning with the root, but in the afternoon it just turned off one time.. Was weird but i didnt pay much atention..
The second day i was listening music and suddenly it turned off, and since then the cellphone is not able to keep on for more than 10min..
Some times i can load the complete OS and ofter 2 min it turn off sometimes at the Samsung S4 logo turn off something i must say is that the Device every single time i turn it on, on the Samsung S4 screen says "kernel is not seandroid enforcing" in red letters, some people say it happens when the root process is not made correctly some says it normal because its rooted..
I already installed from Odin the Stock ROM from SamMobile, and the problem is exactly the same.. A friend of mine told me it could be the Logic Card AKA Motherboard.. But i want to believe its just a software problem.. Cuz' before i rooted cellphone was working..
- Download mode: Works like a charm not a single problem and basically its the only way i keep trying different options to install on the phone..
- Discovery mode: With CWM sometimes works good, sometimes it just turn off, with Philz runs good not turning off or something and its how i was able to wipe data, cache, dalvik, factory reset to the cellphone..
Im thinking in starting over like pretending i didnt do anything to the cellphone, try again the root, the rom, the PHILZ (dont know how to call it).. and hope for the best..
Any advice or reliable links where i can download the correct files for my S4 i337M.. You are basically the last reliable source i have to fix my S4 if you give up with me, then i must admit my cellphone has passed away ..
Hope you can help me thanks in advance and have an excellent day!!:laugh::good:
The first troubleshooting step (to determine if the issue is hardware or firmware related) is to flash back to stock with Odin. Since you have completed this step and find that the problem is still present, this suggests that it is a hardware problem.
I have seen a custom kernel cause sleep of death, which makes the phone appear to have turned off. But in those cases, flashing the stock kernel fixed the problem.
Perhaps you should see if you can return the phone to the seller for a full refund.
creepyncrawly said:
The first troubleshooting step (to determine if the issue is hardware or firmware related) is to flash back to stock with Odin. Since you have completed this step and find that the problem is still present, this suggests that it is a hardware problem.
I have seen a custom kernel cause sleep of death, which makes the phone appear to have turned off. But in those cases, flashing the stock kernel fixed the problem.
Perhaps you should see if you can return the phone to the seller for a full refund.
Click to expand...
Click to collapse
Thanks for your reply.. I still dont know how but with Philz recovery, i was able to make a full wipe, i mean it deletes everything every single folder previously made was erased, and i can tell you that because i have a folder called ROOM where i places my ROM, Kernel, etc.. So i can flash them in discovery..
So i erased everything and then proceeded to install via Odin the Stock Rom and guess what it works like a charm, not a single problem.. So, so far the cellphone is ok.. I tested for two hrs.. Now i tried to install a custom ROM and its doesnt load from the Samsung S4 screen jaja... But im still having acces to discovery and download mode so thats ok..
Just two advices.. Never ever download files from Youtube ****y links.. Always go to the source.. Youtubers are assholes.. Real help and information comes from real people that knows what they are talking about like this forum and also updated and real ROM's come from the main source not Mega o Linkbucks...
Other advice embrace your self to do it.. Study every single question you have in Android, from KERNEL to ROM and ROOT.. Isn't that difficult..
One more question, Which ROM with Lollipop would you suggest to install i have the i337M?
SUNDR1V3R said:
So i erased everything and then proceeded to install via Odin the Stock Rom and guess what it works like a charm, not a single problem.. So, so far the cellphone is ok.. I tested for two hrs.. Now i tried to install a custom ROM and its doesnt load from the Samsung S4 screen jaja... But im still having acces to discovery and download mode so thats ok..]
Click to expand...
Click to collapse
May I make a suggestion? Now that you have the phone working, can you possibly just use it for a week without doing anything to it? Don't try to root it or do anything other than text, make phone calls, and install a few programs. This will establish a baseline of behavior for your device, so you'll be able to tell when its behavior is out of the ordinary.
I understand your desire to make it your own. I got my S4 brand new from AT&T and said that I would wait at least a month before rooting it or changing roms, in case there was a problem and needed to return it. I had good intentions, but I couldn't stand it anymore and rooted it after only 3 days! It will take a lot of patience, but you really need to use it for more than a few hours to make sure that the hardware is okay.
I agree take baby steps, week stock, week root, week recovery. Figure out if its hardware or one of the steps is causing it.

[Q] sgh 1337 UN stuck on Samsung splash screen (safe strap broken)

So, I have gotten myself in a bit of a pickle I however think I can get out of it by sideloading using EXT. SD, Im not sure what to flash to solve the dillemma however. So this is the situation. I have a (had) a rooted Galaxy s4 (sgh-i337 ucufnc1) with 4.4.2 android. It had safestrap installed and back ups of everything else in sd card and other locations just in case. The phone was acting buggy, so I formatted the phone with safestrap, the problem persisted, ill get into the issue a bit further down. So I booted back into safestrap, and did a complete wipe, however my sd card must've bumped out, because it didnt delete any media files or so it said, and then after the wipe it crashed. and refuses to boot into safestrap or even past the splash logo. I can get into download mode, but usb debugging isnt on anymore since i wiped it, I can get into the other mode as well ( cant for the life of me remember the name of it atm although i use it frequently) with some luck. I also happen to have all .md5 files from a backup i did about 4 months ago in tact, I cannot for the life of me get them to convert properly to apply them to the phone without safestrap however, if anyone has any insight to this please let me know also.
I can/will list any other information I have if anyone needs it, and if anyone can help it would safe a life!
The reason i reformatted it to begin with, was because media would stall, and when i plugged in the audio jack it'd freeze the entire app using it, then the whole phone would freeze. I believe it was due to lucky patcher but im unsure. The issue began when I altered the auto update file, and even after i rectified it, it persisted. At this time i have a phone soft bricked because it didnt delete all the media files and I assume something bugged onto the kernel image but Im not sure. If I can simply try to restore it to stock kernel then im fine with that.
Ghujii said:
So, I have gotten myself in a bit of a pickle I however think I can get out of it by sideloading using EXT. SD, Im not sure what to flash to solve the dillemma however. So this is the situation. I have a (had) a rooted Galaxy s4 (sgh-i337 ucufnc1) with 4.4.2 android. It had safestrap installed and back ups of everything else in sd card and other locations just in case. The phone was acting buggy, so I formatted the phone with safestrap, the problem persisted, ill get into the issue a bit further down. So I booted back into safestrap, and did a complete wipe, however my sd card must've bumped out, because it didnt delete any media files or so it said, and then after the wipe it crashed. and refuses to boot into safestrap or even past the splash logo. I can get into download mode, but usb debugging isnt on anymore since i wiped it, I can get into the other mode as well ( cant for the life of me remember the name of it atm although i use it frequently) with some luck. I also happen to have all .md5 files from a backup i did about 4 months ago in tact, I cannot for the life of me get them to convert properly to apply them to the phone without safestrap however, if anyone has any insight to this please let me know also.
I can/will list any other information I have if anyone needs it, and if anyone can help it would safe a life!
The reason i reformatted it to begin with, was because media would stall, and when i plugged in the audio jack it'd freeze the entire app using it, then the whole phone would freeze. I believe it was due to lucky patcher but im unsure. The issue began when I altered the auto update file, and even after i rectified it, it persisted. At this time i have a phone soft bricked because it didnt delete all the media files and I assume something bugged onto the kernel image but Im not sure. If I can simply try to restore it to stock kernel then im fine with that.
Click to expand...
Click to collapse
UPDATE: I resolved the issue, by rooting, safestrapping, ripping the image files, from another galaxy s4 with alike descriptions. then i managed to side load it, then it booted properly, i then reformatted it completely back to 100% factory everything. Now my original problem persists, and i cant help feel that google services is causing it. (examnples of issues" proccess.gapps has stopped. anotrher process error code. phone calls can be made, but not recieved as it seems the server is too busy to n otice it, massive battery drain, audio takes several seconds to play, while video continues to play fine, audiojack is mostly unresponsive, phone calls that are made cannot recieve or send audio during call session, phone may freeze at unlock screen, or any time during operation, may even reboot from process overloading" now keep in mind. i removed every system file and app that the natural reformat will allow. so nothing applied by the user is on the phone, other than natural factory applications. Im digging a bit into the phone as i can but its a slow process whenit starts freezing. if anyone has any idea of what can be causing this, or how to fix this please inform me lol.
Ghujii said:
UPDATE: I resolved the issue, by rooting, safestrapping, ripping the image files, from another galaxy s4 with alike descriptions. then i managed to side load it, then it booted properly, i then reformatted it completely back to 100% factory everything. Now my original problem persists, and i cant help feel that google services is causing it. (examnples of issues" proccess.gapps has stopped. anotrher process error code. phone calls can be made, but not recieved as it seems the server is too busy to n otice it, massive battery drain, audio takes several seconds to play, while video continues to play fine, audiojack is mostly unresponsive, phone calls that are made cannot recieve or send audio during call session, phone may freeze at unlock screen, or any time during operation, may even reboot from process overloading" now keep in mind. i removed every system file and app that the natural reformat will allow. so nothing applied by the user is on the phone, other than natural factory applications. Im digging a bit into the phone as i can but its a slow process whenit starts freezing. if anyone has any idea of what can be causing this, or how to fix this please inform me lol.
Click to expand...
Click to collapse
The best solution must be installing the stock firmware via odin. Since you are on NC1 , You can installed the stock NB1.
Here is guide explaining you using odin, installing NB1, root with towel root, updated NC1, install the safestrap. The guide was not specifically written for that but you can find those steps in the guide.
I will attempt to do this, since nothing since has work. I am about to get a new logic board for the system in the next 2 weeks. Towel root DOES typically work on this system, however the last time I attmpted it it failed to work outright. Im not sure what has changed with the device, but i believe reflashing stock is the best method. The phone now, will boot up, then skip the lock screen and go straight to the home screen, which is black with no pull down bar, or with no signal and there is no way to rectify it. Even if there were, it boots back down and launches back up and becomes locked at the ATT logo.
After a fair bit of messing with it, and recovery mode it will sometimes boot normally where it tells me that processes has failed and askes me to cancel the ''app''. This is the best option to update the phone and attempt root, but getting it here is so difficult because it reboots itself and the mode is rare to acquire. This problem either is due to the kernel, or the rom i believe. I also am to believe the powercell may have some issue, as i replaced the battery a few weeks back and it worked fine for about 1 week.
Booting into safemode doesnt work either as it skips over the lock screen straight to the home screen. Outsidce of replacing the logic board, or attempting another flash im at the end of the short rope i was already on in terms of options.
sway8966 said:
The best solution must be installing the stock firmware via odin. Since you are on NC1 , You can installed the stock NB1.
Here is guide explaining you using odin, installing NB1, root with towel root, updated NC1, install the safestrap. The guide was not specifically written for that but you can find those steps in the guide.
Click to expand...
Click to collapse
UPDATE: I found therein two methods to flashback to stock. I did so, then proceeded to attempt to flash from nb1 to nj4. Progress stopped there when it flung an error 7 at me. So this means either something in my phone is corrupted or the file i downloaded from the above mentioned forum is corrupted. I also attempted flashfire, but seen as it STILL crashes at random due to process errors thats almost impossible to attempt.

SM-N910G Stock - Contently freezing, restarting to download mode and data lose

Hey all,
I found few similar threads, but none of the solutions worked for me. So here's my situation
Problem : N910G Singapore Starhub, used for more than 1 and half years without major issues. Suddenly started to randomly freeze and then restart.
Got worse very quickly. Started to get freezed at Samsung logo. Most of the time had to remove the battery to re-try booting.
What I've done so far:
Cache cleared -> Didn't work
Factory reset -> Was ok with less lag (Freezing) for sometime, then same again
Installed TWRP. Flashed PIT file. Following an XDA post, flashed Samsung stock Android 6 released to India -> Was ok for couple days, was better than 5.1 in terms of responsiveness and battery life. After few days, again freeze. restart
Flashed with stock 5.1 released for the correct region. -> freezing, restarts. Wifi passwords are not getting saved (Have to re-enter upon restart). Restarts end up in download mode. very rarely passes the Samsung logo
Rooted and tried to change build prop ro.securestorage.support (or something similar) and see whether passwords are getting saved -> Still passwords are not getting saved. /efs is accessible.
Now the device never boots properly. Some apps are missing after restarts. Always ends up in download mode. Recovery is working fine though.
You guys have any idea what else I should try before throwing this away?
Thanks in advance.
cyclo.sl said:
Hey all,
I found few similar threads, but none of the solutions worked for me. So here's my situation
Problem : N910G Singapore Starhub, used for more than 1 and half years without major issues. Suddenly started to randomly freeze and then restart.
Got worse very quickly. Started to get freezed at Samsung logo. Most of the time had to remove the battery to re-try booting.
What I've done so far:
Cache cleared -> Didn't work
Factory reset -> Was ok with less lag (Freezing) for sometime, then same again
Installed TWRP. Flashed PIT file. Following an XDA post, flashed Samsung stock Android 6 released to India -> Was ok for couple days, was better than 5.1 in terms of responsiveness and battery life. After few days, again freeze. restart
Flashed with stock 5.1 released for the correct region. -> freezing, restarts. Wifi passwords are not getting saved (Have to re-enter upon restart). Restarts end up in download mode. very rarely passes the Samsung logo
Rooted and tried to change build prop ro.securestorage.support (or something similar) and see whether passwords are getting saved -> Still passwords are not getting saved. /efs is accessible.
Now the device never boots properly. Some apps are missing after restarts. Always ends up in download mode. Recovery is working fine though.
You guys have any idea what else I should try before throwing this away?
Thanks in advance.
Click to expand...
Click to collapse
If you know how, I'd use Odin to restore the factory image if you're running the factory software. Performing a hard reset is always the best way to go, however if you're still having problems then I'd download the latest firmware from Samsung's firmware site and then Odin.
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button. *
Android.Ninja said:
If you know how, I'd use Odin to restore the factory image if you're running the factory software. Performing a hard reset is always the best way to go, however if you're still having problems then I'd download the latest firmware from Samsung's firmware site and then Odin.
Click to expand...
Click to collapse
Thanks for the reply Android Ninja. As the last resort, I did flash the correct stock firmware which I downloaded from Sammobile. But it didn't really fix the issue. So should I unroot and use Kies instead? Because I can't find a way to download the fireware from Samsung, if that's what u meant. thanks

G935A Bootloops every 1-2 weeks after un-rooting

This is a pretty weird one, so I'm gonna cut to the chase...
Several weeks ago I got my a new phone (Galaxy s7 Edge, AT&T, Qualcomm) and everything was fine. I'd never rooted a phone before and wanted to try it out, even though the Edge was still pretty new. After about 2-3 weeks of owning my phone, I followed a guide to root. The root only worked after a factory reset, so I lost my apps and pictures, but it wasn't a big deal because it was just a couple weeks' worth of stuff. Everything works fine for a month or so, and then most of the apps started crashing. Some, like Google Chrome or Spotify would work, but most didn't. All the services on my phone also stopped. I figured it was a problem with the root and said oh well and factory reset my phone. I set it up normally again and all was well. But then things got weird.
Now, after about 1 week, my phone will do the same thing as when rooted. First Snapchat stops working, followed by a multitude of other apps. Google Play store stops opening, I'm unable to install apps, and several core features of the phone just freeze up. If i try rebooting (how I discovered the issue), my phone gets stuck in a bootloop and I have to factory reset to work again. My phone did this again today after a few times so finally I'm coming here for help. I also recently discovered that factory resetting my phone from the settings app did nothing, as soon as I rebooted it went into a bootloop. So the only way to recover my phone is to factory reset from the recovery mode. It may also be worth noting that I used ODIN to flash the AP, BL, CP, and CSC stock firmware (G935AUCU1APB5 etc...) after I wanted to unroot. I have absolutely no clue what's wrong and any fixes or even an explanation would be greatly appreciated.
go into recovery and try cleaning the caches, there maybe stray bits of old code floating around.
Cosmic Blue said:
go into recovery and try cleaning the caches, there maybe stray bits of old code floating around.
Click to expand...
Click to collapse
Yeah I've done that a couple times. I went ahead and did it just now though so we'll see

Categories

Resources