Database Users

Wifi tether issue. and some info needed

Phone information.
Sprint Samsung GS4
SPH-l720
Android version
4.2.2
Build number
ends in ---MF9
Kernal ver
3.4.0-953334
Ok, now that I have device specs up lets get to some of the issues or features I cant get to work. I rooted the phone just fine and checked it with the Super user app from the play store. I then tried to do the wifi tether method on YouTube and found three are some issues, 1. I cant seem to get the 2 files to paste into the system\framework folder. It just seems it sits there in a infinite loop and says "copying" . Also I cant seem to find the "WiFi Tether" app on the PLAY Store anymore is there something else to use?
Next how do I do a system backup before I start doing anything other than stock operations. I have an sd card 32gigs, im sure this will be enough to back up a stock system, with just a few PLAY application downloads.
Also can someone show me or point me to what else I can customize on the s4, I was reading about 4.3 is there any difference than 4.2.2.
Thank you

Hotspot here...... http://forum.xda-developers.com/showthread.php?t=2256950
To do a backup you need to have custom recovery installed, search for twrp 2.5.0.2 in tar file, install with odin or download goo manager from playstore and install that way.
I would wait a little to upgrade to mja, mf9 works pretty good and there are still some issues with mja and root and tripping the knox counter voiding your warranty. I used to run triforce rom and loved it, I am running now slimbean and like it as well. Before you do anything to your phone READ and Inform yourself, you don't want to end with a 700 dollar paperweight

[Q] Lock Screen Issue, Remove Safe Strap, and Mobile Hotspot

Hi,
About two days ago I posted a forum topic about upgrading a relative's AT&T S4 here in Canada (Rogers Wireless). After a while, I was finally able to upgrade the bloody phone to 4.4 from 4.3 by following these two threads: I337UCUFNB1_100%_Stock_Rooted_ROM & I337_MK2toNB1_KeepRoot_OTA.zip and
I337_NB1toNC1_KeepRoot_OTA.zip & I337UCUFNC1_100%_Stock_Rooted_ROM(4/24/2014)
However I now have a problem with the Lock Screen Options, Removing Safestrap, and the Mobile Hotspot. First, when I go to set a PIN for the lockscreen, I only have the two options Swipe and PIN (which doesn't work at all but is an available option) while the rest have this message under them "disabled by administrator encryption policy, or credential storage". I've tried googling a fix but none of the fixes seem to work. It is said in the first thread posted above, that the MK2 bootloader users will experience a lockscreen settings issue but I can't apply the other bootloader provided that resolves the issue as it is stated that it may cause a hardbrick to the phone since I'm on the NC1 bootloader. I'm not sure what can fix the lock screen problem.
My second problem is removing Safestrap. Stated in the second thread above, there is a known issue that Safestrap will force close after updating to NC1, but Safestrap will continue to function normally after. I tried the method of manually uninstalling it by using ES File Explorer and tried deleting the safestrap folder under system/etc/ and the e2fsck file under system/bin/e2fsck, but I get an error that those files/folders can't be deleted even though I gave ES File Explorer root permission.
My third and final problem is the Mobile Hotspot that comes with the phone from AT&T. I tried to run the mobile hotspot today, but I get a message saying that Mobile data not available or Invalid SIM. I'm assuming since this is an AT&T Phone and AT&T is using their own software to override the System Default Hotspot Tether program, It doesn't let you run it without having a AT&T SIM. Is there someway to restore the System Default one that Samsung ships with it's phones and remove or disable the AT&T one?
Thanks.

Bump?

Monkeymo13 said:
Hi,
About two days ago I posted a forum topic about upgrading a relative's AT&T S4 here in Canada (Rogers Wireless). After a while, I was finally able to upgrade the bloody phone to 4.4 from 4.3 by following these two threads: I337UCUFNB1_100%_Stock_Rooted_ROM & I337_MK2toNB1_KeepRoot_OTA.zip and
I337_NB1toNC1_KeepRoot_OTA.zip & I337UCUFNC1_100%_Stock_Rooted_ROM(4/24/2014)
However I now have a problem with the Lock Screen Options, Removing Safestrap, and the Mobile Hotspot. First, when I go to set a PIN for the lockscreen, I only have the two options Swipe and PIN (which doesn't work at all but is an available option) while the rest have this message under them "disabled by administrator encryption policy, or credential storage". I've tried googling a fix but none of the fixes seem to work. It is said in the first thread posted above, that the MK2 bootloader users will experience a lockscreen settings issue but I can't apply the other bootloader provided that resolves the issue as it is stated that it may cause a hardbrick to the phone since I'm on the NC1 bootloader. I'm not sure what can fix the lock screen problem.
My second problem is removing Safestrap. Stated in the second thread above, there is a known issue that Safestrap will force close after updating to NC1, but Safestrap will continue to function normally after. I tried the method of manually uninstalling it by using ES File Explorer and tried deleting the safestrap folder under system/etc/ and the e2fsck file under system/bin/e2fsck, but I get an error that those files/folders can't be deleted even though I gave ES File Explorer root permission.
My third and final problem is the Mobile Hotspot that comes with the phone from AT&T. I tried to run the mobile hotspot today, but I get a message saying that Mobile data not available or Invalid SIM. I'm assuming since this is an AT&T Phone and AT&T is using their own software to override the System Default Hotspot Tether program, It doesn't let you run it without having a AT&T SIM. Is there someway to restore the System Default one that Samsung ships with it's phones and remove or disable the AT&T one?
Thanks.
Click to expand...
Click to collapse
The manual method of removing ss is only for older versions, but good try. (I tried the same thing, myself)
Given the lockscreen and safestrap issues, rather than try and troubleshoot, I recommend starting fresh. It will be easier than troubleshooting. I'm not sure what method you used in the first place, but I've never seen safestrap fc after initial install. Try these steps and see if you have better luck... http://forum.xda-developers.com/showthread.php?p=51130818
***Note - The settings for safestrap are stored in the TWRP folder on your extsdcard. To get get the clean install, you will want to delete that folder before odin back to stock. (If you have any backups stored in there, you'll want to copy them out first.)
As for the hotspot issue, I am not in your situation (ATT phone on another carrier), so I cannot verify if these will work, but they sound good...
1. Do nothing. Maybe Odin back to stock fixed issue
2. http://forum.xda-developers.com/showthread.php?p=53509265#post53509265
3. Following your own advice of moving off ATT software, flash one of the roms in post 2 here that are i9505 based (or Maple Leaf, the Canadian based ROM)... http://forum.xda-developers.com/showthread.php?p=53758259

Tutorial: How to get data working on sprint g900p S5 GSM

WARNING: DO THIS AT YOUR OWN RISK , I AM NOT RESPONSIBLE FOR BRICKED DEVICES OR LOOPING DEVICES , IF YOU ARE GOING TO TRY THIS BE SURE TO KNOW WHAT YOU'RE DOING BEFORE ATTEMPTING
First of all this is my very first post on the community, i dont usually post here but since i have been on here since the times of the motorola droid 2 i might as well post this thing that i did to help me sort the problem with the data on the galaxy s5
Things that i used:
TWRP Recovery installed via TWRP Manager from playstore
Galaxy s5 4.4.2 already rooted via kingoroot ( You can use any other method that you prefer)
Shohat ROM V5 http://forum.xda-developers.com/showthread.php?t=2719386 (All credits go directly to Shohat for this amazing rom)
Build prop editor (You can get it from playstore)
cm-11-20140919-UNOFFICIAL-klte (This is available for download at androidhost here http://d-h.st/niU , all credits go to Albinoman887 for uploading that file and to cyanogen for making that build)
SSU.APK http://forum.xda-developers.com/spr...print-samsung-unlocker-unlock-sprint-t2928250 (All credits go to aalyatim for making this wonderful app)
Patience
Lets begin
First off all you got to root the phone , i used kingoroot as its one of the fastest and easiest method to root your device , it even gives you on screen steps for doing the rooting process
Next once the device has been successfully rooted we are going to go on ahead and download TWRP Manager from playstore, install it and install the recovery on your phone ( If you already have it or if you have a diferent method to install it theres not a problem)
Next once the recovery has been installed we are going to unlock the phone by using SSU.apk and just installing the app and running it (If you have already unlocked the phone there is no need to install the unlock again)
Next once the phone has been successfully unlocked we are going to be doing the next step, download build prop editor from playstore , give root priviliges to it , go to the edit option ( Small pencil located at the bottom right of the screen ) and scroll down all the way to the bottom, once here type in the following:
ril.sales_code=LOL
ro.csc.sales_code=LOL
Once you have that in , we are going to save it by going to the top right and clicking the floppy disk and waiting for it to save build prop
Next step will be turning off device and entering recovery mode ( You can google how to access recovery mode ) , once inside recovery we are going to be doing the following , since im using TWRP i went to WIPE, then FACTORY RESET , after that i went to ADVANCED WIPE , and checked dalvik cache , system, data, cache i got an error on trying to write something but thats normal
Next step was installing the cm-11-20140919-UNOFFICIAL-klte that you previously downloaded on the steps below , install gapps if you want but it wont be necessary , once thats install and the phone boots you will be able to see the H+, 3g or the connection that you have on your area based on your gsm provider
Now in case you want to stop here and stay with cyanogen you can do it , but if you want to have the stock fresh look of S5 TouchWiz then we are going to do next steps
Once thats done we are going to be accessing recovery once more , once inside we are going to be doing the exact same process that we did before i went to WIPE, then FACTORY RESET , after that i went to ADVANCED WIPE , and checked dalvik cache , system, data, cache i got an error on trying to write something but thats normal
Next we will be installing the rom Shohat ROM V5 once it begins, it takes a while for it to finish , do not restart your device until its done even if it appears its not doing anything , once install reboot the device , you will wait a moment for it to load, once loaded you will be getting the samsung galaxy welcome screen , complete all of the steps to finish the setup and youre done , if you dont see the H+ sign or the signal , just check that your apn are there and were done
I Have tried with AT&T and with a foreign carrier in mexico and it worked great
I have attached pictures with proof , i took it with my camera so it doesn look edited or anything , i hope this helps you out as it helped me

work for s5 sprint g900p??
This may enable the sprint samsung galaxy s5 version G900P get signal H +????

lololo619 said:
I Have tried with AT&T and with a foreign carrier in mexico and it worked great
Click to expand...
Click to collapse
Are you saying the phone picked up signal with an AT&T SIM here in the US...?

As far as I know, this doesn't work on the G900P for domestic use. It probably worked for the OP because he's in Mexico (or I've just molested my G900P so much it's not picking up any GSM networks).

ecs87 said:
As far as I know, this doesn't work on the G900P for domestic use. It probably worked for the OP because he's in Mexico (or I've just molested my G900P so much it's not picking up any GSM networks).
Click to expand...
Click to collapse
Bahaha - better get on that
I figured it was a super long shot, just asking him to clarify. I'm subscribed to every thread on Sprint Samsung unlocking, and from your posts (and others'), it's clearly deeper than ROM level. A guy can dream though ^__^

Doesn't work for t-mobile

DimVim said:
Doesn't work for t-mobile
Click to expand...
Click to collapse
Duh
@lololo619 might wanna put a disclaimer about US GSM use in the OP

I hope the OP sees this.
Did you have problems with the "Unable to establish a wireless data connection LTE: ESM-29 EMM-X" with correct APN before and this fixed it? Thanks for posting

Your Solution Worked!!!
Thank you so much.
I can confirm that this WORKS!!!
I was heart broken after I unlocked the phone and could not get data on Digicel Dominica (in the Caribbean) even with the correct APN settings. I googled for some time until I found your post. After reading the comments on this post, I did not have much hope but as they say "nothing beats a try" and so I followed your instructions and VOILA...
Thanks again Bro...:good:

iBowToAndroid said:
Bahaha - better get on that
I figured it was a super long shot, just asking him to clarify. I'm subscribed to every thread on Sprint Samsung unlocking, and from your posts (and others'), it's clearly deeper than ROM level. A guy can dream though ^__^
Click to expand...
Click to collapse
I got on it. Restored the efs data partitions And performed the note 3 domestic unlock steps and dest's (sorry buddy, I only remember your original username!) international unlock app. I then modified the build.prop as much as I could to the Verizon build (G900V). I can see T Mobile and AT&T networks when searching with a valid T Mobile SIM in, but cant connect obviously. The invalid SIM notification would have to be legitimately removed before one could even consider registering onto the network. I...just want to take a peek at nv item 10124
Sent from my LGLS990 using XDA Free mobile app

ecs87 said:
I got on it. Restored the efs data partitions And performed the note 3 domestic unlock steps and dest's (sorry buddy, I only remember your original username!) international unlock app. I then modified the build.prop as much as I could to the Verizon build (G900V). I can see T Mobile and AT&T networks when searching with a valid T Mobile SIM in, but cant connect obviously. The invalid SIM notification would have to be legitimately removed before one could even consider registering onto the network. I...just want to take a peek at nv item 10124
Sent from my LGLS990 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah I remember seeing 10124 mentioned. It'll be interesting to see what form DSU takes. It's obviously still an OTA process instead of a code but I'm curious as to how different it is from the current international method

iBowToAndroid said:
Yeah I remember seeing 10124 mentioned. It'll be interesting to see what form DSU takes. It's obviously still an OTA process instead of a code but I'm curious as to how different it is from the current international method
Click to expand...
Click to collapse
Its just another IPC command called over RIL I bet. If you followed the ORIGINAL author of the international unlock's post he drops the hint on what IPC command was called. I was able to decompile his app, change the IPC command and relock the phone, confirming that the phone is indeed locked using this method instead of directly accessing the nv items over the QC diag port. We are able to log the international unlock process if you know how to set the debugging levels high enough. With a domestic unlock on the horizon via OTA, it shouldn't be long before the domestic unlock back is public.
Sent from my LGLS990 using XDA Free mobile app

Hi, hope you're doing fine.
lololo619 said:
WARNING: DO THIS AT YOUR OWN RISK , I AM NOT RESPONSIBLE FOR BRICKED DEVICES OR LOOPING DEVICES , IF YOU ARE GOING TO TRY THIS BE SURE TO KNOW WHAT YOU'RE DOING BEFORE ATTEMPTING
First of all this is my very first post on the community, i dont usually post here but since i have been on here since the times of the motorola droid 2 i might as well post this thing that i did to help me sort the problem with the data on the galaxy s5
Things that i used:
TWRP Recovery installed via TWRP Manager from playstore
Galaxy s5 4.4.2 already rooted via kingoroot ( You can use any other method that you prefer)
Shohat ROM V5 http://forum.xda-developers.com/showthread.php?t=2719386 (All credits go directly to Shohat for this amazing rom)
Build prop editor (You can get it from playstore)
cm-11-20140919-UNOFFICIAL-klte (This is available for download at androidhost here http://d-h.st/niU , all credits go to Albinoman887 for uploading that file and to cyanogen for making that build)
SSU.APK http://forum.xda-developers.com/spr...print-samsung-unlocker-unlock-sprint-t2928250 (All credits go to aalyatim for making this wonderful app)
Patience
Lets begin
First off all you got to root the phone , i used kingoroot as its one of the fastest and easiest method to root your device , it even gives you on screen steps for doing the rooting process
Next once the device has been successfully rooted we are going to go on ahead and download TWRP Manager from playstore, install it and install the recovery on your phone ( If you already have it or if you have a diferent method to install it theres not a problem)
Next once the recovery has been installed we are going to unlock the phone by using SSU.apk and just installing the app and running it (If you have already unlocked the phone there is no need to install the unlock again)
Next once the phone has been successfully unlocked we are going to be doing the next step, download build prop editor from playstore , give root priviliges to it , go to the edit option ( Small pencil located at the bottom right of the screen ) and scroll down all the way to the bottom, once here type in the following:
ril.sales_code=LOL
ro.csc.sales_code=LOL
Once you have that in , we are going to save it by going to the top right and clicking the floppy disk and waiting for it to save build prop
Next step will be turning off device and entering recovery mode ( You can google how to access recovery mode ) , once inside recovery we are going to be doing the following , since im using TWRP i went to WIPE, then FACTORY RESET , after that i went to ADVANCED WIPE , and checked dalvik cache , system, data, cache i got an error on trying to write something but thats normal
Next step was installing the cm-11-20140919-UNOFFICIAL-klte that you previously downloaded on the steps below , install gapps if you want but it wont be necessary , once thats install and the phone boots you will be able to see the H+, 3g or the connection that you have on your area based on your gsm provider
Now in case you want to stop here and stay with cyanogen you can do it , but if you want to have the stock fresh look of S5 TouchWiz then we are going to do next steps
Once thats done we are going to be accessing recovery once more , once inside we are going to be doing the exact same process that we did before i went to WIPE, then FACTORY RESET , after that i went to ADVANCED WIPE , and checked dalvik cache , system, data, cache i got an error on trying to write something but thats normal
Next we will be installing the rom Shohat ROM V5 once it begins, it takes a while for it to finish , do not restart your device until its done even if it appears its not doing anything , once install reboot the device , you will wait a moment for it to load, once loaded you will be getting the samsung galaxy welcome screen , complete all of the steps to finish the setup and youre done , if you dont see the H+ sign or the signal , just check that your apn are there and were done
I Have tried with AT&T and with a foreign carrier in mexico and it worked great
I have attached pictures with proof , i took it with my camera so it doesn look edited or anything , i hope this helps you out as it helped me
Click to expand...
Click to collapse
Is there a way I can go back to a Stock Rom and keep my data working?
Btw, thanks for this excellent post. Works very finee!!!:good::good::good:

cm-11-20140919-UNOFFICIAL-klte.zip (226.23 MB) link not working .. another link please
---------- Post added at 08:35 PM ---------- Previous post was at 08:28 PM ----------
Download now button not working
Download button downloads a virus

Data working now on CM11
ShohatRom_S5_G900F_V5 not working on NK4 bootloader ( 4.4.4 ) .. what touchwiz ROM should i use ?

aamszia said:
Data working now on CM11
ShohatRom_S5_G900F_V5 not working on NK4 bootloader ( 4.4.4 ) .. what touchwiz ROM should i use ?
Click to expand...
Click to collapse
I dropped to NE (4.4.2) to get it to work. It has everything I want expect wifi calling. I have the same question if there a 4.4.4 touchwiz rom (or 4.4.2 with wifi calling) that works with this.
Thanks OP!

is fingerprint working in shohat rom? mine is not working, NFC either...
Thanks!

shohat rom working on 4.4.4 ( NK4 ) ? i only got black screen ...

I can confirm that this really works.
Thanks bro for this wonderful job.
Sent from my SM-G900F using XDA Free mobile app

This really works, thanks. I can confirm that the method work in 4.4.4 using cm11 but shohatrom don't work so if you want touchwiz you should use xtrestolite rom (that one works)

[Q] Quick Question If Someone Has a Moment, Please

I just swapped from my Amaze 4g, to a used Note 3, and I'm a little lost as far as where I should start.
It says that it's on 4.4.2, and that I cannot update due to a modified system.
Basically, I would like to get updated to 5.1.1 (or as close as is official for the Note 3), and root it.
I'm afraid I'm not familiar with Samsung devices, and because I purchased this from ebay, I don't know how to tell the exact state that the former user put it in (I expected they would return it to stock prior to selling).
It's currently a T-Mobile branded, SM-N900T, on 4.4.2, build is KOT49H, security software MDF v1.0 release 2. Kernel is 3.4.0-660648.
It is supposedly unlocked for carriers, though I have not attempted a SIM card use yet, until I can tell that what I have is a valid device and the IMEI is checked out.
Any thoughts on how to validate the IMEI, and sort out how to get my new phone up to date would be appreciated. As I stated, I expected the vendor would have returned it to stock, but that is clearly not the case, so I don't want to accidentally boot loop it by doing something I shouldn't. I have not owned a Samsung before, so I want to be careful on how it differs from my Nexus 7, Amaze 4g, and Droid X, as they're all obviously very different in the OS area.
Thank you for the help1

Download tbe stock 4.4.2 rom and use odin to install. Then you will get the OTA updates.
Sent from my SM-N900P using Tapatalk

There is no stock 5.1.1 for note 3, only cm12.1/ aosp. Latest is 5.0 and you can use odin to flash. Maybe it's rooted that's why you can't update.

bladebarrier said:
I just swapped from my Amaze 4g, to a used Note 3, and I'm a little lost as far as where I should start.
It says that it's on 4.4.2, and that I cannot update due to a modified system.
Basically, I would like to get updated to 5.1.1 (or as close as is official for the Note 3), and root it.
...
Thank you for the help1
Click to expand...
Click to collapse
Some apps to install from Play Store...
Phone INFO Samsung - this will tell you all about your phone and the firmware etc.
Root Checker Basic - tells you if you are rooted or not.
SuperSU - this is so valuable you should buy the Pro licence. Chainfire does some great work for our phones.
TWRP - I have the zip version on my extSDCard and an Odin version on PC in case I have to rebuild from a Stock firmware. CWN works OK but most ROM builds seem to be for TWRP I think and a backup from one will not work on the other.
I don't know your previous phone so you probably need Odin v3.09 - this sits on PC and lets you flash firmware to the phone. (connected by USB)
For which you need Samsung USB drivers so the PC will recognise the phone. Install on PC before connecting phone.
Then do some browsing and find the processes to root your phone and install the ROM you want. If you just want Stock and access to all your phone, you can root it after flashing the original v5.0 download (from Sammobile or similar site - note on Sammobile you need a free account to DL) and then install Custom recovery (if wanted - it WILL trip the Knox flag but that may not matter given it's 2nd hand and might already be tripped anyway)
Read, make SURE you understand what is being said BEFORE you do anything - ask if you don't.
Good luck...

N9005 Lollipop brick
Hi All, just need a huge help here, a friend of mine has been using a N9005 which was auto restarting, she went online and downloaded this firmware...N900AUCUEOC1_N900AATTEOC1_N900AUCUEOC1_HOME.tar.md5....2.5GB in size...and flashed it, but the phone is stuck in boot loop even after recovery wiping data and cache, the phone can boot into download mode but re flashing the firmware always fails.....is there a solution for this.....please help

Thank you all for the info, especially the detailed info from Journyman16. I checked, and it is flagged as custom, which is fine, so I'm going to go ahead and try to return to mostly stock, update it, and root it.

Ok, everything went well. I had to do two attempts at rooting, but I think it's just one of those things where sometimes it doesn't restart into the process every time.
All seems good. I'm on 5.0, rooted, busyboxed, and smooth sailing.
Thank you all, again, for the tips. The Note 3 is running very well. Thank you to all of the devs that have made this process so refined. I've donated to you before, and did so again today. It's outstanding to have such well versed coders, on XDA, helping out the community.

mjmbirige said:
Hi All, just need a huge help here, a friend of mine has been using a N9005 which was auto restarting, she went online and downloaded this firmware...N900AUCUEOC1_N900AATTEOC1_N900AUCUEOC1_HOME.tar.md5....2.5GB in size...and flashed it, but the phone is stuck in boot loop even after recovery wiping data and cache, the phone can boot into download mode but re flashing the firmware always fails.....is there a solution for this.....please help
Click to expand...
Click to collapse
You have never learned not to ask in others posts? What does your problem has to do with this topic at all?
When you need help. Just click on Q&A then Create a new thread. How hard is it?

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.