Database Users

So I somehow managed to break my touchwizz, now what?

I did something stupid. I used BK package disabler to disable a lot of stuff, including beaconmanager, aaaservice, push service, and a few more which I didn't know the function off. I thought if something breaks after restart, I'll just undo it.
Problem is, I didn't restart.
Then I got an update. It updated, and restarted.
Long story short, lots of settings were strange, like vibration feedback was off, and more small stuff.
More importantly, 2 things have broken: NFC is totally broken, it always makes the sound that the tag doesn't work.
And also, my notification tray is broken. The settings gear, and the down arrow don't work, but the switches do.
No notifications show, at all. None.
I really don't want to factory reset. Is there a way to fix this? I hope so.
andiling said:
Can't you enable the packages again?
Click to expand...
Click to collapse
Probably should have mentioned I did that, and also restarted a dozen times. I guess the update combined with the off packages broke something?
Edit, solution found!!!
http://forum.xda-developers.com/showpost.php?p=69837145&postcount=25

Can't you enable the packages again?

andiling said:
Can't you enable the packages again?
Click to expand...
Click to collapse
Probably should have mentioned I did that, and also restarted a dozen times.
I guess the update combined with the off packages broke something?

What if you try to uninstall the app? If it's possible

You need to flash your firmware again.
Sent from my SM-G935F using XDA-Developers mobile app

RuffBuster said:
You need to flash your firmware again.
Sent from my SM-G935F using XDA-Developers mobile app
Click to expand...
Click to collapse
Will that not reset my phone to stock settings?

Delano.888 said:
Will that not reset my phone to stock settings?
Click to expand...
Click to collapse
Yep. But you'll get a working phone...

Well, factory resetting is basically not an option right now. Living without notifications, and nfc is also not great. Is there nothing else I can do? Like re flashing the firmware while keeping app settings?

Reable and odin the firmware. Should keep data, but clean up system

Delano.888 said:
Well, factory resetting is basically not an option right now.
Click to expand...
Click to collapse
OK. Enjoy your paperweight.
Flash something that works or look at a brick.

B3311 said:
OK. Enjoy your paperweight.
Flash something that works or look at a brick.
Click to expand...
Click to collapse
So you know for sure flashing is not possible without wiping? So xile6 is wrong?

Btw it's not a brick right now. It looks like a software problem. And those can be fixed, right?

Delano.888 said:
Btw it's not a brick right now. It looks like a software problem. And those can be fixed, right?
Click to expand...
Click to collapse
Try to flash only cp bl and ap file trough odin just in case flash home csc if its possible not the normal cscs make sure it is home csc.

Delano.888 said:
So you know for sure flashing is not possible without wiping? So xile6 is wrong?
Click to expand...
Click to collapse
Of course I don't. Neither do you. I don't know what you disabled, neither do you. No idea what your original firmware was, your exact S7E model, CSC, bootloader, modem, the update you mentioned, what flashing method you're planning on using etc etc. If you know you're keeping it secret. Presume you're not rooted but you haven't said.
The only info you've given is that you bust your phone doing something you shouldn't have but don't know what, and don't want to do a factory reset
Not very helpful.
In short, how can we help when you don't give any info and you admit yourself you don't know what you disabled that caused your problem?
Flashing stock FW will work (99.999% certain). Give more info and maybe it's not necessary, who knows? We're not telepathic.

B3311 said:
Of course I don't. Neither do you. I don't know what you disabled, neither do you. No idea what your original firmware was, your exact S7E model, CSC, bootloader, modem, the update you mentioned, what flashing method you're planning on using etc etc. If you know you're keeping it secret. Presume you're not rooted but you haven't said.
The only info you've given is that you bust your phone doing something you shouldn't have but don't know what, and don't want to do a factory reset
Not very helpful.
In short, how can we help when you don't give any info and you admit yourself you don't know what you disabled that caused your problem?
Just downloaded a clean push service apk, didn't change anything.
Flashing stock FW will work (99.999% certain). Give more info and maybe it's not necessary, who knows? We're not telepathic.
Click to expand...
Click to collapse
Sorry I'm not trying to be super unhelpful, I was typing via mobile. I'm on a PC now.
I'm not rooted. It's a stock S7edge from the Netherlands (GSM). The update which caused my device to restart was a security update, I think it had the date Nov 22 or something like that.
The packages I disabled before the update and restart were:
AAAservice, Beaconmanager, Briefing, Email, Facebook, Facebook app installer, Facebook app manager, GEARVR 3x, Health service, Instagram, Kies application BnR, Mmsservice, Nearby service, Onedrive, Print spooler, Remote controls, Samsung billing, Samsung Cloud, Samsung Gear, Samsung Mirrorlink, Samsung Print service, Samsung Push service, Samsung Setup wizard, Screen mirroring, Smartcardmanager, Smartcardservice (those 2 probably broke NFC) UIBCVirtualsoftkey (that broke the home button until I re enabled them), voice service & voice wake up.
Anyway, I guess push service broke the notification tray and the smartcardservices probably broke NFC. So, how might I fix those?
BTW just installed a clean push service apk, didn't change anything.

Reflashing should be unnecessary since the tool works without root and system should be untouched.
If enabling doesn't work I guess you're out of luck avoiding factory reset.

andiling said:
Reflashing should be unnecessary since the tool works without root and system should be untouched.
If enabling doesn't work I guess you're out of luck avoiding factory reset.
Click to expand...
Click to collapse
So there's simply no way to fix, in the software, what I did to break it?
Guess I'm never going near package disable apps ever again.

You may ask the developer for an idea...
Due to the sandbox system in Android you simply can't access the areas the apps mess around with if you don't have root. In addition those disablers use Knox..

Hi,
- BK Disabler did recommend all customers enable all disabled packages before system upgrade (OTA)
- BK Disabler is using Samsung SDK to work, it means if you uninstall BK Disabler app, it will reset to default (all packages will be enable). So, try to uninstall BK Disabler app, restart your phone and try to update firmware again!
- If it still not work well, backup all your data (copy to PC, Laptop...) before go Setting -> Backup and Reset ->Reset Factory
Contact with the developer at [email protected] to get more support

I mailed him, basically he can't help ATM.
How do I download the firmware (G935FXXU1BPJG) again? I found basically only this working link:
https://samsung-firmware.org/download/Samsung Galaxy S7 Edge/d804/PHN/G935FXXU1BPJG/G935FPHN1BPK1/
But it's going to take 8 hours.
Are there no official Samsung links? So where do these files come from?

Android Pay not working.

I Haven't rooted my phone yet but it keeps telling me this when I open android pay, when I first got my phone I set my up my card but now it saying that phone is either rooted or bootloader unlocked which isn't the case.
On Vodafone UK, before this I used my OP3 with Magisk with Android Pay but I haven't used that since I've got my s8 so I'm not sure what the issue could be.
Any insight to this?
Besides the usual factory reset.

same here EE UK S8 not rooted (yet) but comes up with same error message. It worked fine on my rooted and hidden with magisk S6
edit - oh and factory reset doesn't work as I already tried that. I thought it might have had something to do with bringing over magisk app from my google backup but I specifically didnt install that the 2nd time around. Knox hasn't been tripped so its not that

I'm having the same issue on a Galaxy S8 via Tmobile. I've never rooted it, have no clue if the bootloader is unlocked and I'm stock since I reset the phone the first time I got the error. Still getting the error and Android pay help chat was not useful.

Same issue here, on Voda UK. I used Package Disabler pro and thinking I might have disabled something I need.

So since I had OEM unlock enabled after disabling it, it passes and safetynet now.

I had no problems adding cards, but a few days later when I wanted to add more cards, I get the error. I can't remember what I did in between that would've caused this, but definitely not rooting! I turned developer option to off and still get the error.
My S7 is rooted and TWRPed and have no problems adding cards!!!!???

Very weird. Working just fine on my rooted s8+ with magisk.

I'm on T-Mobile with a S8 and Android Pay connected to my PayPal is getting card read error everywhere I try to use it.
Safety net says everything is ok too. Not sure what's going on. I have the newest update and not rooted.
Sent from my SM-G950U using Tapatalk

I installed different Samsung Pay Framework apk and now I want to revert back and downgrade to another version to make Spay work.. when I click uninstall updates it wont let me. (Gives message that App is needed by system administrator.. when I open sys admin nothing there. hidden app)
Any ideas or suggestions on how to downgrade Samsung Pay Framework?
Thank you in advance,
Joe

xeathpk said:
Very weird. Working just fine on my rooted s8+ with magisk.
Click to expand...
Click to collapse
Hi Can you let me know how you managed to root with Magisk and get Android pay etc to work?
My phone:
Model: SM-G955F
SW: G955FXXU1AQF7
I tried rooted and couldn't get it working, and now recovered to official ROM and still can't get it to work?!?

Dont you people know anythin?
All EU(exynos) S8 and other galaxies come with unlocked bootloaders. Thats causing the problem
Lock it

Hi all,
I already posted a question in the Official stock upgrade but it got lost in the other comments, so I'm trying my luck again.
I had an italian branded SM-G950F (OMN), I wanted to remove all the Vodafone stuff, so I installed a MULTI-CSC as per the official stock firmware upgrade thread, when I did it I had my Australian sim card in and I got a weird UK CSC (the multi CSC didn't have australia in it), after installing everything I noticed that Android Pay didn't work, so I did a factory reset with my italian sim card in and still Android Pay was complaining that my firmware was modified or rooted.
I decided to use an australian specific firmware so I downloaded an XSA firmware and did the procedure again.
At this stage Secure Folder and Samsung Pay work (the phone is NOT rooted, this update has been the only "mod" I have done) but Android Pay is still saying that my rom may be modified or rooted so it doesn't open.
It is pretty important for me because my back supports android pay but not samsung pay
The phone is not rooted, if I reboot the phone in download mode the warranty void bit is 0 (which is good).
If I use Root Checker Pro, under safety net tab, I get CTS profile match as FAIL, I was thinking this could cause Android Pay to fail.
any idea?

start to uninstall suspicious apps, then restart . worked with my un-rooted S8. OEM unlock: OFF

degsyh said:
same here EE UK S8 not rooted (yet) but comes up with same error message. It worked fine on my rooted and hidden with magisk S6
edit - oh and factory reset doesn't work as I already tried that. I thought it might have had something to do with bringing over magisk app from my google backup but I specifically didnt install that the 2nd time around. Knox hasn't been tripped so its not that
Click to expand...
Click to collapse
Does rooting in UK\Europe void our warranty?

mariuscrist said:
start to uninstall suspicious apps, then restart . worked with my un-rooted S8. OEM unlock: OFF
Click to expand...
Click to collapse
Hi mariuscrist,
I'm not sure what app can be suspicious, I have reinstalled the apps I had before the firmware update and I could use android pay then. I'll see what it can be, probably it could be worth to do a factory reset and test android pay before anything else?

SM-G935F Bootloop after JUST TWRP

hey-o, So i wanted to root my phone quick and easy just afew ahours ago, after i odin'd in TWRP on my S7 Edge, it couldn't read data, i was pretty confused, i restarted my phone, told me verfication had failed, and in base, the entire OS has basicly went corrupt, am really not sure how, but has anyone else had this problem? SM-G935F EE UK, need more info i can provide.
Correction, I installed the EE firmware AFTER i had to fix my phone due to what TWRP did, My phone is actualy BTU Firmware.
Knox has been tripped.
Video visualization: https://youtu.be/o-9aKxWXaG8

Minerspark said:
hey-o, So i wanted to root my phone quick and easy just afew ahours ago, after i odin'd in TWRP on my S7 Edge, it couldn't read data, i was pretty confused, i restarted my phone, told me verfication had failed, and in base, the entire OS has basicly went corrupt, am really not sure how, but has anyone else had this problem? SM-G935F EE UK, need more info i can provide.
Correction, I installed the EE firmware AFTER i had to fix my phone due to what TWRP did, My phone is actualy BTU Firmware.
Knox has been tripped.
Video visualization: https://youtu.be/o-9aKxWXaG8
Click to expand...
Click to collapse
Update: After serveral attempts, i finaly got it running a CFW, i had to flash the OFFICAL firmware, and leave download and reenter it before the phone even boots and then flash TWRP, and i installed magiskmanager and everythings looking alright from here, i'll update if i have any problems.

3rd update, i offical cannont find the firmware this phone was on, it WAS SIM-FREE when i bought it, now i installed this version every app crashes on launch, am pretty lost myself. anyone know a way i can get or know the Very first firmware?

Considering i've got literly no help, this thread can be closed, i installed some random stock firmware and i suppose i will have to put up with broken settings menu and a barly working keyboard for now.

Minerspark said:
Considering i've got literly no help, this thread can be closed, i installed some random stock firmware and i suppose i will have to put up with broken settings menu and a barly working keyboard for now.
Click to expand...
Click to collapse
If you are US flash the smg935u as it works for every carrier

U System firmware on BLv5/6 Phone

1. Thanks to @FP_XDA and GSMZambia for the great directions found here
2. The other stuff and ideas:
The above method does put the U firmware on your phone. I had trouble getting it to connect to the network. I did try different combinations of files in the AP tar; CP; and CSC, but it would either not connect after a factory data reset or loop with the message about my SIM has changed, please restart.
I tried just flashing the following combinations through flashfire, but maybe this is a Sprint SIM issue and it works on other SIM cards; however, I have Sprint.
The U firmware seemed to work fine on the software. Including boot.img in flashfire would take away the eng_boot and root. I just had trouble connecting to the Sprint network.
Do you need to use the v5 combo file and flash a certain CP/CSC before going through the rooting steps? The U firmware CSC file is different in size, so is it a partition (PIT) issue since that will write the cache.img.ext4 file and those vary in size from stock to the U? Is there a certain order to flash in flashfire to get it to work properly?
Anyway, I downloaded several U CSC firmwares (XAA, XAS, SPR (last two are sprint)), but ran into some network issue every time. The operating system seemed stable, but the lack of connection and some random entries under settings make it so close, but yet so far.
I don't mind the Sprint firmware, but can you unlock additional LTE bands if you use the stock sprint firmware on another carrier?
Thanks for any help!

Here is more info about the Settings submenu options:
Here is some more detailed info:
The submenus under settings give me options like K twophoneservice; T roaming; Giga LTE. I think it is CSC related as those carriers are Korean based. I think this may be my issue along with a few others I've seen on reddit. Just wondering why it says that though. I used the G930U version, so not sure why this would appear.
Any help or suggestions?
Thanks

Bootloop
Did you get Oreo working while running on v5? Have followed steps in that video but the phone always gets stuck in a boot loop. I extracted the latest Oreo files from the AP file and every seems to flash right but gets stuck in a boot loop after flashfire reboots. Have tried multiple times with same result. Would rather not upgrade to v6 but was trying to get Oreo working.

Aggiedude said:
Did you get Oreo working while running on v5? Have followed steps in that video but the phone always gets stuck in a boot loop. I extracted the latest Oreo files from the AP file and every seems to flash right but gets stuck in a boot loop after flashfire reboots. Have tried multiple times with same result. Would rather not upgrade to v6 but was trying to get Oreo working.
Click to expand...
Click to collapse
I didn't try Oreo, but I didn't have any success getting Nougat to work. It would install and run fine, but I never got it to connect to a network. I tried flashing different imgs and making zip files with additional files to add to the system and same result. I do have additional LTE bands unlocked (12,13,17), but since I still have sprint, I have no way to test it.
I assume that everything would work normal except for VoLTE, but I think you could add that with root.

lvpre said:
I didn't try Oreo, but I didn't have any success getting Nougat to work. It would install and run fine, but I never got it to connect to a network. I tried flashing different imgs and making zip files with additional files to add to the system and same result. I do have additional LTE bands unlocked (12,13,17), but since I still have sprint, I have no way to test it.
I assume that everything would work normal except for VoLTE, but I think you could add that with root.
Click to expand...
Click to collapse
You have to follow the other guide on here about disabling packages. The only problem: you can't disable packages anymore with the apps from the play store. Samsung stopped that. There are system level applications that are blocking you from connecting to sprints network after flashing eng_boot. My guess is you flashed eng_boot, phone booted, then shutdown and reboot, now no network connection? This happens with the binary 4 version as well. I have been on nougat rooted using U firmware for a good while. I once had to re-install everything and when I went to disable the apps, I couldn't. There is a way to disable them via ADB but its not easy and requires patience. But once those packages are disabled, you will have a perfectly running phone with root.
Here are the packages:
XMayhem2099 said:
7. Disable the following packages via bk or adhell
Chameleon
Sprint OMADM
Sprint OMADM Phone Interface
MDMApp
SecurityLogAgent
Security Policy Updates
Security Storage
Click to expand...
Click to collapse
I came here looking to see if the same eng_boot works on Oreo. Guess I will just have to go ahead and try it myself

elesbb said:
You have to follow the other guide on here about disabling packages. The only problem: you can't disable packages anymore with the apps from the play store. Samsung stopped that. There are system level applications that are blocking you from connecting to sprints network after flashing eng_boot. My guess is you flashed eng_boot, phone booted, then shutdown and reboot, now no network connection? This happens with the binary 4 version as well. I have been on nougat rooted using U firmware for a good while. I once had to re-install everything and when I went to disable the apps, I couldn't. There is a way to disable them via ADB but its not easy and requires patience. But once those packages are disabled, you will have a perfectly running phone with root.
Here are the packages:
I came here looking to see if the same eng_boot works on Oreo. Guess I will just have to go ahead and try it myself
Click to expand...
Click to collapse
The version used by GSMZambia includes a boot.img file, which removes the eng_boot and root after a factory reset. It sounds like you are actually still b4 for everything. This version is for people on b5/6 and want to install the U firmware. However, you are correct about disabling those packages when rooting on the U firmware. You lose root and eng_boot by flashing the stock boot.img in flashfire. The point is to have the U firmware without root on a b5/6 Sprint S7/Edge.
Maybe it would work if you flash the eng_boot again and disable, but then you are stuck on the eng_boot. Plus it messes with Knox, so I'm not sure if something like SABS or Adhell would even work.

lvpre said:
The version used by GSMZambia includes a boot.img file, which removes the eng_boot and root after a factory reset. It sounds like you are actually still b4 for everything. This version is for people on b5/6 and want to install the U firmware. However, you are correct about disabling those packages when rooting on the U firmware. You lose root and eng_boot by flashing the stock boot.img in flashfire. The point is to have the U firmware without root on a b5/6 Sprint S7/Edge.
Maybe it would work if you flash the eng_boot again and disable, but then you are stuck on the eng_boot. Plus it messes with Knox, so I'm not sure if something like SABS or Adhell would even work.
Click to expand...
Click to collapse
But from what I read in the original post is that BEFORE using flashfire to flash the original boot.img, you are running the eng_boot.img. Is this correct? Btw, flashfire NEEDS root. So you ARE rooted at some point. Therefore, this is why you are being kicked from the network. Thus, disabling those packages will prevent that. But SABS and Adhell no longer work, at least I couldn't get them to. I even paid for the one and used it once. So I'm a bit annoyed with that. But yes, I am still on binary 4 for the BL. It was a requirement when purchasing my phone on Craigslist xD
But, what you are after may not be feasible. This is what you want: 100% U firmware on Sprint Binary > 4 WITHOUT eng_boot?
I always thought the whole point of being on U firmware was for root access though. But anyhow, once you get the U firmware flashed, which BL version is on the device? Is this an exploit that allows for older Binary to be flashed?
I'm intrigued by this method for other reasons. I would really REALLY love for a custom boot.img to be allowed but you can't. If this method is a way to block checking of BL, AP, etc hash checks, then the similar method should be possible for a custom recovery and custom kernel. I miss my kernel.

elesbb said:
But from what I read in the original post is that BEFORE using flashfire to flash the original boot.img, you are running the eng_boot.img. Is this correct? Btw, flashfire NEEDS root. So you ARE rooted at some point. Therefore, this is why you are being kicked from the network. Thus, disabling those packages will prevent that. But SABS and Adhell no longer work, at least I couldn't get them to. I even paid for the one and used it once. So I'm a bit annoyed with that. But yes, I am still on binary 4 for the BL. It was a requirement when purchasing my phone on Craigslist xD.
Click to expand...
Click to collapse
AdHell 3 still works on Nougat at least. You have to get the newer version because Samsung changed their SDK keys program. I'm not on Oreo, so I'm not sure if it will work. But if you are rooted, you have better options. If you need the new version of AdHell3, I'll post a link.
But, what you are after may not be feasible. This is what you want: 100% U firmware on Sprint Binary > 4 WITHOUT eng_boot?
Click to expand...
Click to collapse
Basically, when you finish. You'll have the U firmware on the phone, but the BL with still be 5/6. So some things like Knox, System Updates, etc..won't work because of the conflict and will say the phone has been compromised. Also, the phone doesn't bootloop because of those items you need to disable, because you did it before using flashfire.
It works fine after applying the changes after rooting, but it is after the flashfire flash and factory reset that doesn't. Modem you can flash, but the CSC files mostly get erased because parts of them are install to the system with the rom. When you check, the phone has no CSC setup available. Which is why it probably displays Korean carrier settings since that is the default with CSC files present.
I always thought the whole point of being on U firmware was for root access though. But anyhow, once you get the U firmware flashed, which BL version is on the device? Is this an exploit that allows for older Binary to be flashed? .
Click to expand...
Click to collapse
The original point of U firmware was to get rid of carrier bloatware and the ability to use most carriers easily with most addons (VoLTE) available.
I'm intrigued by this method for other reasons. I would really REALLY love for a custom boot.img to be allowed but you can't. If this method is a way to block checking of BL, AP, etc hash checks, then the similar method should be possible for a custom recovery and custom kernel. I miss my kernel.
Click to expand...
Click to collapse
So in conclusion, you have the U4 firmware running on a Sprint S7 with b5/6 installed without root. Since the phone runs fine with the U firmware, something is causing connection issues to Sprint. I assume he is in Africa (Zambia) and by using a GSM only sim card, it will work.
Unless you want to upgrade to b5/6 and try it, that's probably the only true way to test it. Plus, who wants to be on b4 anyway?

lvpre said:
AdHell 3 still works on Nougat at least. You have to get the newer version because Samsung changed their SDK keys program. I'm not on Oreo, so I'm not sure if it will work. But if you are rooted, you have better options. If you need the new version of AdHell3, I'll post a link.
Click to expand...
Click to collapse
Yeah I am currently rooted with the U firmware BL4. I want to upgrade to Oreo, hoping for performance improvements, better battery, etc. But I guess since the Oreo U firmware is still BL4, I can just downgrade if I can't get root back.
Basically, when you finish. You'll have the U firmware on the phone, but the BL with still be 5/6. So some things like Knox, System Updates, etc..won't work because of the conflict and will say the phone has been compromised. Also, the phone doesn't bootloop because of those items you need to disable, because you did it before using flashfire.
Click to expand...
Click to collapse
I never mentioned a bootloop? Is this about something else? The point I am trying to address is the loss of Sprint connectivity after flashing eng boot. This is because of the packages that need to be disabled.
It works fine after applying the changes after rooting, but it is after the flashfire flash and factory reset that doesn't. Modem you can flash, but the CSC files mostly get erased because parts of them are install to the system with the rom. When you check, the phone has no CSC setup available. Which is why it probably displays Korean carrier settings since that is the default with CSC files present.
Click to expand...
Click to collapse
So you flash everything, eng boot, and are currently rooted. You then flash the provided file via flash fire, factory reset, and now you no longer are able to connect to Sprint network? When you say "can't connect to Sprint network", are you referring to data or to Sprint network entirely? If you go under your "about phone" section, what does your IMEI and phone number display? Don't actually type it here, but it should be something comprehensible. It shouldn't say "unknown" or a bunch of zeros, etc. [/quote]
The original point of U firmware was to get rid of carrier bloatware and the ability to use most carriers easily with most addons (VoLTE) available.
Click to expand...
Click to collapse
True..
So in conclusion, you have the U4 firmware running on a Sprint S7 with b5/6 installed without root. Since the phone runs fine with the U firmware, something is causing connection issues to Sprint. I assume he is in Africa (Zambia) and by using a GSM only sim card, it will work.
Unless you want to upgrade to b5/6 and try it, that's probably the only true way to test it. Plus, who wants to be on b4 anyway?
Click to expand...
Click to collapse
I do. A lot of people want to be back to BL4. There is NO difference in the newer bootloaders EXCEPT a special "key" type of thing that prevents downgrading. That is the only thing different. This is why the U firmware is still on BL4 despite having an Oreo update. Sprint changes the BL version just so people like us have extra hurdles to overcome when we want something different. Its very stupid tbh.
But, I would like to help you guys out, however, I AM NOT upgrading to the BL5/6. Noway nohow.

It actually shows a crossed out circle for the signal strength in the status bar. I'm pretty sure I tried it by flashing just the system and system with boot, which removes the root. Even entering apn info had slight issues.
I was hoping someone with more knowledge and a b5\6 phone would give this a whirl. If you get bored, maybe it would be like you flashing the U firmware with b2.
My wife's phone is still b4, so at least one of us didn't get the Sprint screw.

lvpre said:
It actually shows a crossed out circle for the signal strength in the status bar. I'm pretty sure I tried it by flashing just the system and system with boot, which removes the root. Even entering apn info had slight issues.
I was hoping someone with more knowledge and a b5\6 phone would give this a whirl. If you get bored, maybe it would be like you flashing the U firmware with b2.
My wife's phone is still b4, so at least one of us didn't get the Sprint screw.
Click to expand...
Click to collapse
Hmm. That's weird. What does your about phone section say for IMEI and phone number? Everything good? I wonder if something is affecting the PRL. Try updating that via settings menu before you flash the firmware and factory reset. The CSC shouldn't really affect that part. I have changed mine multiple times to just eff around and see what/if anything changed. Its more for the phone to know what menu options are available and such. For instance, call recording shows up when its not a US branded carrier.
Sadly I will never flash the newer BL. But I will definitely keep trying via the thread and if you would like to discord or something similar I would be down. School starts in about 2 weeks so I'm basically free till then

sim boot loop
I have the same issue. I can install the g930u Nougat firmware on my BLv5 Sprint phone (you seem to need BLv6 for Oreo), however, the phone will not connect to the sprint network. I flashed the cache.img file and it does the same thing. It forces you to reboot to finish setup then errors out on the blue sim card screen in recovery. I removed the AutoPreconfig app through adb shell to bypass the forced reboot and tried to just select Sprint as the network under connection settings where you can search for available carriers. That too failed...it just sat there for a while then said that it couldn't connect and shows the emergency calls only as the network up top and low signal bars.

Aggiedude said:
I have the same issue. I can install the g930u Nougat firmware on my BLv5 Sprint phone (you seem to need BLv6 for Oreo), however, the phone will not connect to the sprint network. I flashed the cache.img file and it does the same thing. It forces you to reboot to finish setup then errors out on the blue sim card screen in recovery. I removed the AutoPreconfig app through adb shell to bypass the forced reboot and tried to just select Sprint as the network under connection settings where you can search for available carriers. That too failed...it just sat there for a while then said that it couldn't connect and shows the emergency calls only as the network up top and low signal bars.
Click to expand...
Click to collapse
Thanks for posting this!!! I'm glad that I wasn't the only having this issue. I tried it again using a different method and still got the SIM boot loop. This method probably works great if you have anything other than Sprint or Sprint MVNO, but something is conflicting like it does during a typical root of the G930P. Anyway, hopefully, someone else will be able to figure this out.

No voicemail notifications S10+ no root

Just got the S10+ yesterday. No root and no plan to root at present (it's my husbands phone and he's weird lol)
His voicemail isn't giving him a notification. Nothing on the icon on the home screen and nothing when I open the app. I've cleared cache and data, app is up to date, rebooted phone, searched sprint and searched XDA and can't find an answer.
Anyone have any ideas what I need to do?

Have you tried updating the phone via the OTA updates? You might need to do a factory data reset or flash the latest stock firmware with Odin if all else fails.

StoneyJSG said:
Have you tried updating the phone via the OTA updates? You might need to do a factory data reset or flash the latest stock firmware with Odin if all else fails.
Click to expand...
Click to collapse
I'll double check to see if an OTA was done or not. I was thinking my next step would be to do a factory reset. Weird thing is my note 10+ doesn't have VM either. It's not activated yet so I didn't know if that could be why.
I also tried to download the app from the play store (on my husbands phone) and it would get to downloading 2%, say it was installing then give an error of "this application cannot be installed"

Sounds like you need a factory reset and if that fails reflash the firmware with Odin. I have voicemail on my S10+ here running the AT&T firmware. Some firmware like Version or others might have visual voicemail. I have the icon for it on my phone, but never use it.

StoneyJSG said:
Sounds like you need a factory reset and if that fails reflash the firmware with Odin. I have voicemail on my S10+ here running the AT&T firmware. Some firmware like Version or others might have visual voicemail. I have the icon for it on my phone, but never use it.
Click to expand...
Click to collapse
I have no idea what I did but it just suddenly started working. Thank you so much!