Related
So just right now as I'm sitting in the ****ter I got an OTA update for my voicemail.. didnt even give me a description of what it contained .. does anyone know what this is about? Do you think its going to lose root access ?
sent through my Special Edition White HTC EVO 4g while in the ****ter
ins0dus said:
So just right now as I'm sitting in the ****ter I got an OTA update for my voicemail.. didnt even give me a description of what it contained .. does anyone know what this is about? Do you think its going to lose root access ?
sent through my Special Edition White HTC EVO 4g while in the ****ter
Click to expand...
Click to collapse
Here's something you could do. Install it and you will find out.
...No, you won't lose root.
My wife's phone is asking for this update. I told her to update it, but it will not install. It will download the file and ask to install, but thats it "application not installed". Any way to install this or get this popup to go away?
This update FUBARed my VM. I had to wipe all data to get it to work again, and if I apply the update, it breaks again. Any way to get rid of the "Mandatory Update" prompt?
Update - Just got off of the phone with Sprint. Tier 2 escalations support manager syas they have seen several EVOs loose VVM and VM indicator after applying the "Mandatory Update". Rep told me to not apply it and ignore the message. Also said there is no way to remove the message.
Sounds like a good reason to use Google Voice for our voicemail instead of the Sprint app.
ETA: Then you can just remove the VVM apk from your phone and never worry about it again.
colorado_al said:
This update FUBARed my VM. I had to wipe all data to get it to work again, and if I apply the update, it breaks again. Any way to get rid of the "Mandatory Update" prompt?
Update - Just got off of the phone with Sprint. Tier 2 escalations support manager syas they have seen several EVOs loose VVM and VM indicator after applying the "Mandatory Update". Rep told me to not apply it and ignore the message. Also said there is no way to remove the message.
Click to expand...
Click to collapse
I complained about this today, and received a $10 credit.
I posted this solution in another thread also. My friends phone is rooted and running Fresh 1.0.1. I'm assuming that its because Fresh signed this ROM so the signature doesnt match for the new mandatory VM update. Try this and see if it works:
A friend of mine's phone did this today also. It kept giving an error when he tried to update Visual Voicemail. I ended up enabling "Unknown Sources" to make it work . . . He is running Fresh 1.0.1. (Yes, way behind I know - He agreed to let me update it after our Thanksgiving break)
Menu > Settings > Applications > Check 'Unknown Sources'. This fixed his.
BTW: Happy Thanksgiving!!!
Click to expand...
Click to collapse
Feel free to uncheck this after the update, or if the update still fails. (If you are paranoid about having that enabled)
Thanks, but that isn't the fix to my problem. I always allow unknown sources for install. The VVM update will install, it just won't authenticate with the server.
Not sure if this is the same update i had months ago, but it allows you to turn on Sprints version of voice mail to text, it wiped my VM data as well.
Speaking of voice mail to text, I discovered somethin g the other day that's kind of neat. If you send an SMS to a land line number, it will ring the phone and, if answered, a computer voice will read the SMS. If the phone goes to voice mail, the same voice reads the SMS to voice mail. Pretty cool...and I don't think there is a fee for the service.
I had no problems with my update... Always use the default msg, so I don't know if it would have wiped VM info, but I still have all my old VM msg's...
Sent from the MATRIX while plugged into an EVO... from a galaxy far-far away.......
Won't even download
Has anyone else had my symptom? Refuses to download when I tell it to: "VoiceMail > Settings > Check for upgrade". It goes online to check, then says "A mandatory upgrade is now available. Includes FREE Trial to Voicemail-to-Text". Pushing the "Upgrade" button immediately complains "General failure. Please try again at a later time".
It won't download the upgrade image at all. Anyone else?
(Perhaps it's because I'm still running 2.1; refused OTA upgrade to 2.2 so far, keeping rooted 2.1)
Sprint EVO 4G/HTC SuperSonic
Running rooted "stock" OTA 1.47.651.1 (Android 2.1)
via SimpleRoot
tgi007 said:
Has anyone else had my symptom? Refuses to download when I tell it to: "VoiceMail > Settings > Check for upgrade". It goes online to check, then says "A mandatory upgrade is now available. Includes FREE Trial to Voicemail-to-Text". Pushing the "Upgrade" button immediately complains "General failure. Please try again at a later time".
It won't download the upgrade image at all. Anyone else?
(Perhaps it's because I'm still running 2.1; refused OTA upgrade to 2.2 so far, keeping rooted 2.1)
Sprint EVO 4G/HTC SuperSonic
Running rooted "stock" OTA 1.47.651.1 (Android 2.1)
via SimpleRoot
Click to expand...
Click to collapse
dude update to a stock rooted froyo 3.29 base you will never look back belive me
I installed Rooted 3.30.651.3 stock build, and PRI 1.77_003.
Installed the update and all works now.
Upgrade to 3.29 didn't help
Jbcarrera said:
dude update to a stock rooted froyo 3.29 base you will never look back belive me
Click to expand...
Click to collapse
Well, that "sounds just fine on paper", but after upgrading to exactly that, a "stock rooted Froyo 3.29 base", I've still got the Messages (SMS) app reminding me via Notification that "A mandatory update is now available", and it still gets the same "General failure" error.
Sigh.
HTC Supersonic / Sprint EVO 4G
Running rooted "stock" 3.29.651.5 (Android 2.2)
via myn.
You really should sit "on" the ****ter and not "in" the ****ter.
Sent from my PC36100 using Tapatalk
Okay so I have a Samsung Galaxy S4 from sprint, I love the phone it’s great. I was on the mdl update stock rooted and everything was working fine with wifi. Then I did a factory reset updated to mf9 (the latest update) and then rooted it still stock. Now my phone will connect to wifi if I manually connect to it and works fine, however, if I disable and reenable wifi or restart the phone or leave my house and come back, it will not reconnect to my network automatically, I have to select it myself and put the security key in everytime. When I disable and reenable my wifi it will show “secured” under my network, making it seem as if it never tried to save the network in the first place, So it won't automatically connect like it use to on the mdl update, because it seems as if it forgets it when it disconnects.
I tried even connecting and then forgetting the network and then connecting again to see if that would fix it but it didn’t.
The weird thing is that at my work it remembered the network and connects automatically and when I’m in range. And when I’m away from work I can see it saying “not in range”. Why isn’t my home network doing the same thing, and how do I fix this? (btw I really don’t want to do another factory reset if I don’t have to.)
-I have a 2wire 3800HGV-B router.
kickstand03 said:
Okay so I have a Samsung Galaxy S4 from sprint, I love the phone it’s great. I was on the mdl update stock rooted and everything was working fine with wifi. Then I did a factory reset updated to mf9 (the latest update) and then rooted it still stock. Now my phone will connect to wifi if I manually connect to it and works fine, however, if I disable and reenable wifi or restart the phone or leave my house and come back, it will not reconnect to my network automatically, I have to select it myself and put the security key in everytime. When I disable and reenable my wifi it will show “secured” under my network, making it seem as if it never tried to save the network in the first place, So it won't automatically connect like it use to on the mdl update, because it seems as if it forgets it when it disconnects.
I tried even connecting and then forgetting the network and then connecting again to see if that would fix it but it didn’t.
The weird thing is that at my work it remembered the network and connects automatically and when I’m in range. And when I’m away from work I can see it saying “not in range”. Why isn’t my home network doing the same thing, and how do I fix this? (btw I really don’t want to do another factory reset if I don’t have to.)
-I have a 2wire 3800HGV-B router.
Click to expand...
Click to collapse
Okay well I fixed it by unrooting and using odin to go back two updates prior to mf9, then did 2 ota's back to mf9 and rooted again. all is working fine, also fixed the phone's getting too hot problem and battery last longer than ever.
it's your kernel that was causing this...for future reference, if you're on mf9 with the stock mf9 kernel and do not want to have to wipe your phone to fix this, you can use ShabbyPenguin's kernel...i had this issue before on my s4 and this worked for me...why the rooted stock rom doesnt like the stock kernel for wifi blows my mind...lol
How was it going on? Do you still have the problem with the wifi?
Perhaps you can try this: http://forum.xda-developers.com/show...56&postcount=2 (Greatly appreciated and high credit to dajumper's work.)
This works on my I337 NI1 Unlocked Rooted. I uses ES Explorer with Root Explorer enabled.
I went to the "system " folder in the device, scrolled down until I found "build prop" then edited using ES Explorer Note Editor.
yhendra said:
How was it going on? Do you still have the problem with the wifi?
Perhaps you can try this: http://forum.xda-developers.com/show...56&postcount=2 (Greatly appreciated and high credit to dajumper's work.)
This works on my I337 NI1 Unlocked Rooted. I uses ES Explorer with Root Explorer enabled.
I went to the "system " folder in the device, scrolled down until I found "build prop" then edited using ES Explorer Note Editor.
Click to expand...
Click to collapse
the link you refere to, is not properly linked, can u fix it please? having the same issue
Neikosr0x said:
the link you refere to, is not properly linked, can u fix it please? having the same issue
Click to expand...
Click to collapse
I am sorry for the belated response. I think the link might change to http://forum.xda-developers.com/showthread.php?t=2685519
I do apologize for this inconvenience. Good luck.. :good:
So I unlocked, rooted and flashed my fiancé's moto x pure, and she didn't like the ROM (from 5.1 to 6.0, also flashed modem) She didn't like either of the ROM's so I converted back to stock 5.1 using the the return to stock tool located on the forum. Problem is...
Hotspot is suddenly not working. It doesn't do anything at all. If we click the toggle, it remains grey like it knows we pressed it, but it won't come on. Furthermore, it never checks for permissions. We have Verizon Unlimited so it will usually prompt a permission authentication. This is, only if Verizon patched somewhere along the line because before we could use it without it validating.
If it will help anyone, I'll provide a log cat.
DroidsOnRoids said:
So I unlocked, rooted and flashed my fiancé's moto x pure, and she didn't like the ROM (from 5.1 to 6.0, also flashed modem) She didn't like either of the ROM's so I converted back to stock 5.1 using the the return to stock tool located on the forum. Problem is...
Hotspot is suddenly not working. It doesn't do anything at all. If we click the toggle, it remains grey like it knows we pressed it, but it won't come on. Furthermore, it never checks for permissions. We have Verizon Unlimited so it will usually prompt a permission authentication. This is, only if Verizon patched somewhere along the line because before we could use it without it validating.
If it will help anyone, I'll provide a log cat.
Click to expand...
Click to collapse
I'm having the exact same issue except I am Rooted on 6.0.1
Was just about to flash to stock but won't now seeing it hasn't helped you. I also have verizon unlimited. Not sure there is a connection but it doesn't hurt to mention.
Also, just realized wifi is not working at all.
themufferman said:
I'm having the exact same issue except I am Rooted on 6.0.1
Was just about to flash to stock but won't now seeing it hasn't helped you. I also have verizon unlimited. Not sure there is a connection but it doesn't hurt to mention.
Also, just realized wifi is not working at all.
Click to expand...
Click to collapse
I had this same problem with my Nexus 5x. Check this out and see if it helps. In this guide it is left out that "adb shell settings put global tether_dun_required 0" command must be done after you reboot the phone and have USB debugging enabled.
https://www.androidfilehost.com/?fid=24459283995315346
Link to February's updated modem. Fixed everything!
So, I'm having a particularly strange issue here. I recently got this Sprint Note 4 and activated it. However, there appears to be a missing option under settings. Tethering and Hotspot is straight up gone. To clarify, I have pictures attached showing the item listing, and one without it.
Clarifications of troubleshooting I've tried so far:
I have attempted a factory reset of the device
I have attempted to do a reset with ##72786#
I have tried updating Profile, PRL,
I am using a DeOdexed PH4 6.0.1 ROM. I have tried reflashing per instruction (triple wiping Cache, Dalvik, Internal, System, etc)
I have tried flashing a STOCK OTA PH4 ROM to see if it would show up there. It does not.
I called Sprint technical support to reprovision my phone. They pushed out a a reprovisioning that I accepted. No change.
At one point, Wanam/Xposed was attempted to be installed. I checked for system/csc/features.xml. It was not there
http://forum.xda-developers.com/note-4-sprint/development/rom-stock-ph4-bloated-deodexed-t3473610/ is the custom ROM i'm using. However, it doesn't seem like a ROM specific issue.
If I use Activity Launcher or itools, i can access the actual wifi hotspot MENU (the toggle off and on, LAN settings, etc). I can enable it and the system will broadcast the SSID. However, if I try connecting to it, no devices are able to successfully connect.
here is the Activity Launcher referenced, for other readers:
http://forum.xda-developers.com/showpost.php?p=66713935&postcount=7
but anyways, regarding devices not being able to connect, sometimes the data connectivity (through hotspot only, not for the entire phone) will go dead if you don't start using it immediately after first unlocking and activating tether.
in my experiences, if you keep data alive by immediately connecting a device after your first time turning tether on (after unlock) by downloading a large file or somewhat frequently reloading web pages (on the connected device!) -- anything that will keep data sending and receiving -- it will stick, and the data service to connected device issues will stop.
it's not foolproof, it's not a silver bullet, but this is the method to the madness I have learned and worked for me many times when changing roms and even getting new phones.
it's been a couple months since I had to fiddle with it last, so I can't remember if it was necessary to re-unlock after a failed attempt at keeping data alive. you might only have to toggle data off then back on for another attempt.
when I had the problem of connected devices losing internet access, it would only happen after having worked for a few seconds to a few minutes. it'd work then abruptly stop, and this is my "fix"
My issue seems more in line with the devuces failing to validate to begin with. Not losing connection.
I had something like this before, I vaguely recall it having to do with using Odin vs. OTA stock. So did you try wiping your phone completely then Odin the stock PH4 tar, or did you OTA to PH4?
beezar said:
I had something like this before, I vaguely recall it having to do with using Odin vs. OTA stock. So did you try wiping your phone completely then Odin the stock PH4 tar, or did you OTA to PH4?
Click to expand...
Click to collapse
The very very very first time, I OTA'd to PH4. The next two tries were wiping completely and using the PH4 tar file. So both methods have been attempted.
I was referring to loss of internet connection, not signal related. I thought that was clear, sorry
Sterist said:
I was referring to loss of internet connection, not signal related. I thought that was clear, sorry
Click to expand...
Click to collapse
I thought you meant loss of internet connection in the sense of anti-tether provisioning from Sprint. My phone's LTE never goes down (and I am able to still browse the internet from the mobile device while tethering).
The connected devices never successfully "connect". They aren't listed as connected devices under the mobile hotspot. My other Android phone (without mobile data) is forever connecting. My macbook claims it has an assigned IP but is "unable to access the internet". So I'm not sure what the hell is going on with that.
At this point, I have restored my Note 3 as my active device until I get this resolved. I'm willing to re-write everything down to the barest metal I can.
Somebody in another topic mentioned something about PIT. I don't know anything about that sort of thing. My knowledge extends about as far as installing recovery and flashing ROMs.
I'm confident I could follow procedure, but could use a guiding hand on where to go from here.
sounds like the tether unlock method you used was not done correctly, whether by whoever made it or yourself
method 2 in Galaxy Tools should work just fine. there are several threads in the Sprint note 4 seconds that contain the apk or ppl that will pm it to you. the author discontinued the public/free version of the app and now chargers $35+ per person for a 1 time use lol once you get a copy of the free one, make copies and store on multiple devices forever.
it's primarily for Sprint Sammy devices, so you prob won't see much if anything about it here in the collective note 4 forum.
may work on some boost or even tmo, but yeah.
edit:
you'll want either 3.1.5, easy install n msl read broken on MM and less features
or 3.1.8, troublesome install with msl read working but unreliably, more features.
Sterist said:
sounds like the tether unlock method you used was not done correctly, whether by whoever made it or yourself
method 2 in Galaxy Tools should work just fine. there are several threads in the Sprint note 4 seconds that contain the apk or ppl that will pm it to you. the author discontinued the public/free version of the app and now chargers $35+ per person for a 1 time use lol once you get a copy of the free one, make copies and store on multiple devices forever.
it's primarily for Sprint Sammy devices, so you prob won't see much if anything about it here in the collective note 4 forum.
may work on some boost or even tmo, but yeah.
edit:
you'll want either 3.1.5, easy install n msl read broken on MM and less features
or 3.1.8, troublesome install with msl read working but unreliably, more features.
Click to expand...
Click to collapse
Came back around to this, as I am running a multi-rom and am still encountering this issue. I never attempted any hotspot unlockers. The hotspot was missing from the get-go.
Gamemaster1379 said:
Came back around to this, as I am running a multi-rom and am still encountering this issue. I never attempted any hotspot unlockers. The hotspot was missing from the get-go.
Click to expand...
Click to collapse
Just a thought and question: when you Odin stock tar to recover from this condition, are you using the rooted extended power menu to boot to download mode? Or, do you prevent the auto reboot of stock tar flash with Odin options?
A noted developer, @idone from Galaxy Tool app, once shared with me that rooted shortcut or preventing auto reboot can prevent the normal flash of Odin booting to recovery momentarily to set csc options. csc options flashed may not restore on any boots if you skip that initial auto boot.
The suggested method is to power down and pull battery for 30 seconds our more before reinserting battery and manually booting to downloaded mode. And do not uncheck auto reboot or pull battery but use Odin defaults and let phone auto boot. Doing this allows the phone to boot into recovery to do its thing briefly before booting system. I usually just let it perform the setup wizard and didn't activation just in case.
I rarely do the the data profile update or PRL because if letting the phone setup this way and phone prompts to reboot later, I believe this all done. But since this may allow ItsOn to bootstrap initialize, after flashing TWRP and backing up, I wipe internal memory and factory reset before flashing a custom ROM. Data format is optional; I don't always do that.
But if you do all that and don't see hotspot in Settings of stock, that's a problem. Maybe from dead stock, try KIES or Smart Switch to restore latest stock and check again?
Sent from my SM-N920P using Tapatalk
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.