Related
First off, hi everyone. This is my first post here after browsing for a few weeks. Yesterday I went ahead and rooted my AT&T s4 with the whole reason for doing so wanting to use wireless hotspot for free, and it isn't working.
Tl;dr I tried the TetheringProvision.apk mod technique and it just crashes my settings menu.
Full story:
After softbricking my phone and having to bring it into att 2 days ago I finally figured out a method of rooting it. I got this phone very recently and it came with the 4.4.2 (NB1) update pre-installed. I used the downgrade/root/safestrap method (using the OTA zip method because the stock with root zip wouldn't get past the att splash screen) and am back on 4.4.2/NB1. Everything is working, root included (verified by successfully changing system file names), but when I try to put in the TetheringProvision.apk file that used to work for the hotspot on my old MK2 phone from some other thread on this forum it just crashes my settings menu. The error I get is a "settings has stopped" popup and it kicks me out right when I move the "mobile hotspot on" slider. I'm really hoping there's a simple solution here, but if worst comes to worst I guess I'll just have to try a different rom? Attached is a screen shot of my about device. I really hope someone will be able to help, thanks in advance.
Ok, so I'm now thinking about backing up this rom in safestrap, and re-flashing the backup I made of the MK2 downgrade that I used to install the root. The problem with that was the wifi not working, but I just found a post about bypasslkm. Only problem is that I don't fully understand how to use bypasslkm and even through search I can't find a good guide on it. Could anyone here walk me through the dumbed down version of how to use it? From what I understand I flash the bypasslkm.zip just like I would any other rom, but I don't really get what to do after that. I'm kind of surprised that I'm the first one to have either of these issues, I couldn't find any good information via search.
TaylarRoids said:
First off, hi everyone. This is my first post here after browsing for a few weeks. Yesterday I went ahead and rooted my AT&T s4 with the whole reason for doing so wanting to use wireless hotspot for free, and it isn't working.
Tl;dr I tried the TetheringProvision.apk mod technique and it just crashes my settings menu.
Full story:
After softbricking my phone and having to bring it into att 2 days ago I finally figured out a method of rooting it. I got this phone very recently and it came with the 4.4.2 (NB1) update pre-installed. I used the downgrade/root/safestrap method (using the OTA zip method because the stock with root zip wouldn't get past the att splash screen) and am back on 4.4.2/NB1. Everything is working, root included (verified by successfully changing system file names), but when I try to put in the TetheringProvision.apk file that used to work for the hotspot on my old MK2 phone from some other thread on this forum it just crashes my settings menu. The error I get is a "settings has stopped" popup and it kicks me out right when I move the "mobile hotspot on" slider. I'm really hoping there's a simple solution here, but if worst comes to worst I guess I'll just have to try a different rom? Attached is a screen shot of my about device. I really hope someone will be able to help, thanks in advance.
Click to expand...
Click to collapse
There is a tethering AddOn in the same NB1_100%_Stock_Rooted_ROM & NB1 KeepRoot OTA zip thread that you can flash in safestrap.
Please post here ALL of what you learned/thoughts/ideas. My goal is to get the Sprint based phone "G900P.04" Virgin Mobile users up and going.
I am not responsible for ANYTHING!!! Try doodling with your phone at your own risk!
THIS IS WHAT I GOT SO FAR:
APN SETTINGS:
Virgin Mobile Samsung Galaxy s5 as all the capabilities of flashing any Sprint based G900P.04 ROM/Tweak. However, once flashed, you will have Sprint based network APN settings/not virgin mobile network APN settings. APN settings is what allows you to call/text/LTE/send receive text/pictures. Currently the Virgin Mobile stock ROM doesn't have the option to manually set APN settings though settings/network connections/more networks. However, once flashed to a Sprint ROM, this option "should" now be available to edit. If ballzy enough to try flashing a Sprint ROM and obtain data capability PLEASE POST YOUR FINDINGS. Virgin Moible APN settings can be found at this address:
Virgin Mobile USA APN Settings
I called Virgin Mobile and told them that my send recieve text doesn't work and ask if i can access APN settings manually to check if there correct. He gave no option to view them manually. He advised to dial ##72786# which he said redoes the hands free activation process and "?may?" fix the APN issue.
Apps like the APN backup & restore is another option "if exhausting all other available options" a thread I found HERE It appears that if you know what your doing, the app will work but nevertheless, people has reported it not restoring APN settings.
ROOTING Virgin Mobile Galaxy s5 Obtain warranty without tripping knox counter:
The CF autoroot though odin I seen threads that it trips the knox counter but the "towelroot" method doesnt trip the knox counter and was easy for me.
How to:
1. Go to settings/system/security/allow 3rd party apps. As long as you know what you download I disabled "verify apps" while I'm their.
2. With your phone, Download towelroot HERE and click the red logo to start download
3. Download a file explore application from Google Play "my favorite is FX File Explorer/has secondary Playstore download for accessing root files" and install the tr-1 .apk you downloaded.
4. Read and click the option to root phone.
5. When it says remove knox I clicked "yes."
6. As mine did also, a lot of users report that the phone didn't complete/auto reset device but hung on the "removing knox process." Personally I waited 5min---pressed the home button---manually reset phone.
7. Go to Play store and download/install SuperSU---update binary's---reset phone
8.Your phone is rooted/complete.
Return to Factory Stock
Reflash the phone with the factory stock ROM with Odin can see instructions HERE
Note: Virgin Mobile users only has the option of the Sprint ROM so im curious if this will bork up APN settings...putting them on Sprint/not Virgin Mobile settings. The hand free activation by dialing ##72786# may/may not work.
Custom Recovery:
All Sprint based recoveries I'm positive will work. Custom Recovery opens up any theme/tweak/ROM capability. However, im reluctant to do so because you will not have the ability to update the OS when it arrives because it requires the stock recovery....where you have to do the Return to Factory Stock option just posted.
I've always used Philz Touch Recovery and was always happy with it. Insturctions HERE
There is a TWRP recovery but even people on the TWRP thread say that they hear good things about Philz Recovery.
Installing a ROM:
As mentioned, only Sprint Based ROMs work because it's a Sprint phone. However, if flashing a Sprint ROM through your custom recovery it should error. This is because the developer Puts a script in the ROM that only allows Sprint not Virgin mobile phones to flash the ROM. To fix this, it requires editing the ROM with NotePad++ and deleting the first few lines of code. Good thread to read how to do this is HERE
Apps/Tweaks:
Im still using stock ROM up until somebody with experience can guarantee I can start flashing ROMs without any mishapps.
..Adaway is working great.
Link HERE Couldn't beileve the amount of ad's is on the Internet...even on XDA. Just open/install with a file explorer like FX File Explorer...make sure under settings/security you check "Unknown sources" so you can install apps outside of play store
Wanam Xposed is amazing
Verified working on my Virgin Mobile Stock ROM. Install Wanam from Playstore and install frame work from HERE Now got my phone all theme'd blacked-out like how I like it. 4-way boot menu working too. NOTE: Wanam website states S-Health conflicts with it...so recommend uninstalling it.
Native Hotspot Enabled:
Install this App HERE GalaxyTools.apk. Click Enable Native Hotspot and reboot phone. "Mine rebooted automatically once enabled." Now I access my Hotspot using a playstore hotspot widget "my perfered is called Elixir 2 from the playstore. " on my home screen.
Debloat Stock ROM:
App Master is small and can go to system files and debloat all dumb apps Samsung/Virgin Mobile put on there. A thread HERE shows what Apps are safe to remove.
PLEASE POST ALL YOUR FINDINGS/THOUGHTS/IDEAS
Rather than restoring a Virgin Mobile phone to a Sprint stock firmware we can use these firmwares instead
G900PVPU1ANE5 STOCK VIRGIN MOBILE
G900PVPU1ANK4 STOCK VIRGIN MOBILE
G900PVPU1BOA6 STOCK VIRGIN MOBILE
G900PVPU2BOD3 STOCK VIRGIN MOBILE
G900PVPU3BOF6 STOCK VIRGIN MOBILE
G900PVPU3BOG1 STOCK VIRGIN MOBILE
Notice the Product Code is VMU, which is for VIRGIN MOBILE!
I'll try to keep this post updated with Virgin Mobile Firmwares in case more are added, for convenience and reference
Here is where I got them from
FIRMWARES | SAMMOBILE | VMU
VM's stock ROMs are on sammobile.
Working are CF auto-root, and Philz recovery (via ODIN).
The latest Sprint NK4 ROM (4.4.4) can be ODIN flashed on top of the VM stuff, and everything keeps working as VM. (Towelroot does not work on 4.4.4.)
I don't believe the VM APN settings posted above are accurate for this phone. But if you do the above (CF auto-root, Philz, Sprint ROM), you should be able to get to them on your own phone.
Presumably there will be a stock VM 4.4.4 ROM released soon regardless.
I don't know that there's a need to do much VM-specific stuff separate from what's done for Sprint.
I've been having two flashable zips that I use when switching to a new AOSP based rom (like CM, PAC, whatever), so rather than doing it manually, for you lazy folk like me, you can boot into Recovery, after having checked that you properly flashed your ROM, and flash these VMU APNs. This is for KK ROMs only! If you flash the file named AOSP_MMS_FIX.zip on lollipop you will get a Bootloop.
I got them a while ago so I forgot where or who made them, if you are reading this however, let me know so that I can give cred
By the way, does anybody know how to get MMS working on lollipop? With lollipop roms I can flash the file Universal_vmu_ApnFix-v.R2.zip to get texting and calls working but it doesnt fix picture messages.
EDIT: The Universal_vmuApnFix-v.R2.zip DOES work on AOSP lollipop roms. Just do not flash the other file.
The Sprint Lollipop 5.0 OA6 stock tar posted at the following does also appear to work for VM. Somehow it does know it's on a VM phone -- VM boot logo and everything:
http://forum.xda-developers.com/showpost.php?p=58662929&postcount=1
No problems with the latest CF Auto-root in that thread. Philz 6.57.8 appears to still work after renewed flashing, too.
boost mobile send the update same day Sprint relesed
Sent from my SM-G900P using XDA Free mobile app
d99x, no APN fix was needed when you flashed that Sprint OA6 onto the VM S5?
TheBritton said:
d99x, no APN fix was needed when you flashed that Sprint OA6 onto the VM S5?
Click to expand...
Click to collapse
Correct. And though APN settings are no longer accessible via "More networks," an S-Finder search for "Access Point Names" still turns up the settings. Confirmed to be VM. Everything's hunky dory automatically. :good:
For what it's worth, I backed everything up via Kies in advance. After all apps re-downloaded from the Play store, a Kies restore did get back most if not all of my settings. It just can't restore apps themselves to the new build.
Anyone know the best way to root with the lollipop update installed?
TheChiZ said:
Anyone know the best way to root with the lollipop update installed?
Click to expand...
Click to collapse
The CF Auto-Root linked in the first post of this thread works, but trips Knox:
http://forum.xda-developers.com/showthread.php?t=2729617
And for what it's worth, the official VM firmware is now up at SamMobile:
http://www.sammobile.com/firmwares/database/SM-G900P/VMU/
d99x said:
The CF Auto-Root linked in the first post of this thread works, but trips Knox:
http://forum.xda-developers.com/showthread.php?t=2729617
And for what it's worth, the official VM firmware is now up at SamMobile:
http://www.sammobile.com/firmwares/database/SM-G900P/VMU/
Click to expand...
Click to collapse
Yeah im on the stock update
TheChiZ said:
Yeah im on the stock update
Click to expand...
Click to collapse
Whats Knox like on this phone coming from the s3, if i trip knox once while rooting, how does that affect me when I want to flash a custom rom?
i just got my virgin mobile galaxy s5. i have yet to root and want to understand this fully before i do what i would like to do as ive had experience with bricked devices and dont want a repeat of the feeling. i want a to make a list of what i think i should do and i would love it if i could get corrections on anything thats wron with my process. i and on the sm-g900p model for VM. baseband: g900pvpuboa6 and android version 5.0 lollipop.
1. (while in download mode) connect s5 to computer
2. open odin 3.9 or 3.7
3. select pda/ap and place CF Auto Root into the slot and let it run until the bar turn bluor green or whatever color means that its good to go.
4. apply a custom recovery (i personaly like PhilZ touch recovery)(i am not sure exactly how to do this. on my s3 i was able to apply the recovery via the stock recovery but i dont know if that is possible with knox and all)
5. go into custom recovery on phone and apply the latest version of supersu
6. in custom recovery apply and deknoxify and debloat zips
7. boot up phone and update supersu and run a root checker
8. do whatever with your new rooted s5
i would love it if someone could tell me if this is a tested method or if i am missing something or doing something wrong. any help would be much appreciated as i really dont want anything to go wrong. i also would love it if someone had a link to philz touch recovery that is properly compatible with my version of s5 (sm-g900p VM)
It's not critical, but the latest ODIN is 3.10.6:
http://forum.xda-developers.com/showthread.php?t=2711451
PhilZ is at the following. You can flash the latest 6.57.8 tar.md5 the same way in ODIN. Remember he's no longer developing or supporting this, but it works for now.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/klte/
You do not need to flash SuperSU via a custom recovery if you don't want to. You can add/update it just fine via the Play store.
You do not need to apply the de-knoxify and debloat zips if you don't want to. If you want, there are other file manager programs out there that you can also use to "freeze" Knox (if it makes you feel better for some reason), and to debloat manually yourself.
If you mess up badly, you can use ODIN to flash the full restore TAR from the following (extract it first). Though it's in a "Sprint" folder there, it recognizes it's on the VM variant of the Sprint phone just fine.
http://rwilco12.com/downloads.php?d...print) (SM-G900P)/Stock ROMs/OA6/Full Restore
thank you. the philz recovery i was using was too outdated and caused me some problems. and cf auto didnt seem to want to work. however the recovery you gave the link to worked flawlessly and allowed me to flash the supersu update and gain root.
my next question is weather or not it is safe to flash a sprint stock android L rom and keep my calling, text and mms, and 4g data seeing as i am on VM and not sprint (i do know they are the same phone internally but coming from a VM s3 i needed to flash a APN fix everytime i flashed a new rom to keep things working)
revins95 said:
thank you. the philz recovery i was using was too outdated and caused me some problems. and cf auto didnt seem to want to work. however the recovery you gave the link to worked flawlessly and allowed me to flash the supersu update and gain root.
my next question is weather or not it is safe to flash a sprint stock android L rom and keep my calling, text and mms, and 4g data seeing as i am on VM and not sprint (i do know they are the same phone internally but coming from a VM s3 i needed to flash a APN fix everytime i flashed a new rom to keep things working)
Click to expand...
Click to collapse
I read somwhere that this may be the case this time around aswell, dont know 100% though
The Sprint stock ROM recognizes it's on a VM phone just fine. What's been issued is identical. On a VM phone, it sets up everything for VM -- boot animation, APN settings, everything. There is no need to flash an APN fix or alter any settings to adapt it to VM. That's why when people have tried to start Virgin Mobile threads here, there's been little to no response. There's virtually no need to do anything unique to VM when it comes to the S5. What works for the contract Sprint, works for the pay-as-you-go Sprint, aka VM.
I have not tested non-Stock ROMS, and don't know what you may run into if you start experimenting with custom Sprint ROMs on the VM phone.
If you want to alter your APN settings (though there should be no need on the stock ROM), you can search "Access Point Names" in S-Finder in the drop down menu once the ROM is installed.
d99x said:
The Sprint stock ROM recognizes it's on a VM phone just fine. What's been issued is identical. On a VM phone, it sets up everything for VM -- boot animation, APN settings, everything. There is no need to flash an APN fix or alter any settings to adapt it to VM. That's why when people have tried to start Virgin Mobile threads here, there's been little to no response. There's virtually no need to do anything unique to VM when it comes to the S5. What works for the contract Sprint, works for the pay-as-you-go Sprint, aka VM.
I have not tested non-Stock ROMS, and don't know what you may run into if you start experimenting with custom Sprint ROMs on the VM phone.
If you want to alter your APN settings (though there should be no need on the stock ROM), you can search "Access Point Names" in S-Finder in the drop down menu once the ROM is installed.
Click to expand...
Click to collapse
I would think that if you were to flash Cm 12 you would have to follow it up with some sort of apn fix
TheChiZ said:
I would think that if you were to flash Cm 12 you would have to follow it up with some sort of apn fix
Click to expand...
Click to collapse
thats more so what i meant. ive realized through a little research that using a sprint rom on my vm in fine. i believe this is so because unlike most other VM phones (such as my previous Galaxy S3 VM) the Galaxy S5 uses a VM sim card. something that i found unusual but suspect is the reason for never haveing to change anything ( please coeect me if you know im wrong on this information because right now im working with this as a hypothesis). however i dont know what will happen when i install CM12, which is something i want to try out. my VM S5 doesnt have a Data Toggle in the notification tray which annoys me to no extent. i cant seem to find a way to fix this nor can i find in the stock lollipop rom that the phone comes with. ive always loved stock lollipop and ran CM12 on my S3 but the community for it on Android Forums was huge as still is, so finding how to change the APNs on the VM locked S3 was easy. this isnt the case with the S5 neither there nor here at XDA. i either want to fix my data toggle on my stock rom so i can keep my fingerprint scanner (which for me works more times than not) or switch to CM12. i dont know which is the better option as far as keeping everything working.
revins95 said:
thats more so what i meant. ive realized through a little research that using a sprint rom on my vm in fine. i believe this is so because unlike most other VM phones (such as my previous Galaxy S3 VM) the Galaxy S5 uses a VM sim card. something that i found unusual but suspect is the reason for never haveing to change anything ( please coeect me if you know im wrong on this information because right now im working with this as a hypothesis). however i dont know what will happen when i install CM12, which is something i want to try out. my VM S5 doesnt have a Data Toggle in the notification tray which annoys me to no extent. i cant seem to find a way to fix this nor can i find in the stock lollipop rom that the phone comes with. ive always loved stock lollipop and ran CM12 on my S3 but the community for it on Android Forums was huge as still is, so finding how to change the APNs on the VM locked S3 was easy. this isnt the case with the S5 neither there nor here at XDA. i either want to fix my data toggle on my stock rom so i can keep my fingerprint scanner (which for me works more times than not) or switch to CM12. i dont know which is the better option as far as keeping everything working.
Click to expand...
Click to collapse
Have you tried MOAR v6.0
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
I've got a S4 AT&T running OK2 with root and it ran my AirVoice Wireless SIM perfectly fine for a month while I researched and got a new phone. I'd now like to use it as a backup phone with a FreedomPOP SIM but it's giving me grief about "SIM network unlock PIN". This is the carrier lock correct? I found a tutorial that has you go into the Service Mode and turn off NETWORK LOCK. This tutorial doesn't seem to work (missing the options) in OK2. Do I have to downflash to 4.2.2 in order to get these options? If so, how do I go about doing that? I put OK2 with root on this phone but that process took 2 days and with all the mixed info out there and different versions, it's confusing to say the least.
My other question is, I tried flashing TWRP (jflteatt) and I believe I ended up with the "software not authorized by AT&T" error. Doing some reading, it looks like this may be due to not using a loki'd TWRP?
Any pointers/tips would be much appreciated. All this Samsung stuff is way over my head despite having rooted, recoveried and rom'd maybe a dozen Android devices. I much prefer LG and Moto
natenkiki2004 said:
I've got a S4 AT&T running OK2 with root and it ran my AirVoice Wireless SIM perfectly fine for a month while I researched and got a new phone. I'd now like to use it as a backup phone with a FreedomPOP SIM but it's giving me grief about "SIM network unlock PIN". This is the carrier lock correct? I found a tutorial that has you go into the Service Mode and turn off NETWORK LOCK. This tutorial doesn't seem to work (missing the options) in OK2. Do I have to downflash to 4.2.2 in order to get these options? If so, how do I go about doing that? I put OK2 with root on this phone but that process took 2 days and with all the mixed info out there and different versions, it's confusing to say the least.
My other question is, I tried flashing TWRP (jflteatt) and I believe I ended up with the "software not authorized by AT&T" error. Doing some reading, it looks like this may be due to not using a loki'd TWRP?
Any pointers/tips would be much appreciated. All this Samsung stuff is way over my head despite having rooted, recoveried and rom'd maybe a dozen Android devices. I much prefer LG and Moto
Click to expand...
Click to collapse
Yeah you're carrier locked. I think you can only downgrade to NB1 from OK2, not sure you can carrier unlock on NB1 or not. As for installing TWRP you can't due to the locked bootloader. You can only use safe strap recovery and boot only custom touch wiz roms. Loki only works on the MDB and MDL bootloaders, once you've upgraded the bootloader past MDL, you can't go back.
If the AT&T phone is like the i337m and m919, you may be able to flash down to 4.4.2, flash a 4.2.2 modem, root, run regionlockaway, upgrade modem back to 4.4.2.
Thanks for the replies. I grabbed NB1 from here: https://forum.xda-developers.com/showthread.php?t=2616221
and flashed it via Odin. All went well but when it came time to follow various instructions I found online, they either yielded no unlock or the options weren't in the menu. I don't think the free unlock trick via the service menu works on 4.4.2/NB1.
I researched a bit more and feel very stupid with one of the results that came up... AT&T offers online unlocking of their devices and you don't even have to be one of their customers! I figured I could go to one of their retail stores but also figured they would deny me since I'm not a customer. I'll be jiggered though, here it is: https://www.att.com/deviceunlock/
Slapped my IEMI in with my e-mail and in less than an hour or so, I got my unlock code for free. AT&T said they would e-mail it but I checked back on the status page and found the code there. Hopefully this helps other people.
So, moving forward now, is OK2 the best I can do with a locked bootloader? I ran it for a while but I found that I burned through my data real quick because when I would leave my WiFi coverage and come back, it would reconnect but for some reason wouldn't actually use WiFi (data was still on, had the 4G icon) until I restarted the phone. Basically, every time I left and came back home, I had to restart my phone. Is this a known issue, did I botch something in the install process? I may make another thread for this.
*EDIT*
Running OK2 for a while, I no longer have the WiFi issues I had before. Doing some thinking, I can only attribute the issue to either incorrectly followed steps the first time around flashing OK2 or the use of the debloater script found in the OK2 downloads thread. I've been using Link2SD to remove system apps and so far haven't removed anything that has affected WiFi.
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.