Galaxy S4/Note 3/Mega - Update Profile/PRL/HFA Fix for Sprint/Boost/Virgin Mobile/etc - Sprint Samsung Galaxy S 4 General

Please DO NOT QUOTE this post in your reply. Just post your questions or comments if you have any. I DON'T CHECK OR RESPOND TO PM'S.
Proof of Concept:
Sprint Samsung Galaxy S4's & Note 3's that have been flashed to Sprint legacy accounts such as SERO or Sprint MVNO's such as Boost, Virgin Mobile, Ting, etc. suffer from the fact that you can't launch Update Profile / Update PRL unless the phone has been previously activated in a Sprint LTE account. If the phone has been factory reset using ##786#, the user will also lose the ability to run Update Profile/PRL. As a side effect, you will also get a Hands Free Activation nag each time you turn on/reboot your phone. Disabling/freezing certain apk's to fix the HFA nag unfortunately breaks the phone's ability to run Update Profile & PRL as well. The fix below gets rid of the HFA nag and enables Update Profile & PRL on flashed Sprint Samsung Galaxy S4 & Note 3 phones.
If you'd like to thank me, please click on the "Thanks" button instead of posting a thank you note. Let's save storage and bandwidth. And please, please, please...DO NOT QUOTE THIS POST IN YOUR REPLY JUST TO THANK ME! Again for those who don't know me, I do not accept personal donations. Instead I encourage you to donate to the American Cancer Society, to your local church, or any other not for profit charities.
What good is running Update Profile anyway?
1) This will automatically correct your MDN and MIN settings on your phone if they were flashed incorrectly.
2) This will automatically correct the Profile 1 (or Profile 2) username and AAA key to get your 3G working.
This fix assumes the following:
1) You have a rooted phone. I've only tested on a TouchWiz-based rooted ROM (Sacs Custom ROM based on Android 4.3 on the S4 and stock rooted 4.3 on the Note 3). Post #44 reports that this doesn't work on Android 4.4.2.
2) You have access to another Sprint Galaxy S4 or Note 3 in which Update Profile/PRL already works. Let's call this phone "SOURCE". In theory once you have the appropriate files from "SOURCE", you can use these same files over and over.
3) You're looking to get Update Profile/PRL to work on another phone that is already flashed to Sprint (or Sprint MVNO). This will not work for any other provider! Let's call this phone "TARGET".
4) You have a spare microSD card to transfer files between "SOURCE" and "TARGET" phones.
5) You have flashed your "TARGET" phone's MDN and MIN using DFS, CDMA Workshop, etc.
6) You have flashed your "TARGET" phone's Profile 0 and Profile 1 using DFS, CDMA Workshop, etc.
7) Profile 0 must be accurately flashed. Profile 1's username can be flashed using a bogus value such as "[email protected]" if you do not know the actual username.
8) If you removed/disabled/froze system apk's / apps in your phone to get rid of the Hands Free Activation nag previously, make sure you put these back in their original state.
9) You have the ability to reflash your S4 or Note 3 back to Boost, Ting, Virgin Mobile, etc. in case your flash gets wiped out cuz you didn't follow the directions closely.
Steps to fix Update Profile / Update PRL: (idea is to copy SOURCE phone's /carrier directory to TARGET phone)
1) Use a root-enabled file explorer app such as Root Explorer or ES File Explorer to backup the /carrier directory from your "TARGET" phone to a microSD card.
2) Rename this /carrier folder in the microSD card to something like /carrierBackup.
3) Use the file explorer app to copy the /carrier directory from your "SOURCE" phone to the microSD card as well. Insert this microSD card to your "TARGET" phone.
4) Copy the contents of /carrier directory from microSD card to your "TARGET" phone. Overwrite the files that may already exist in your "TARGET" phone's /carrier directory.
5) Reboot the "TARGET" phone.
6) Run "Update Profile" or "Update PRL".
7) Done.
OR...Instead of doing steps 3 and 4, simply use ES File Explorer to unzip contents of attached carrier-GS4.zip OR carrier-Note3.zip file in /carrier so that the files/folders would look like the attached screen shots.
Pay attention to the content in the screenshots as well as file/folder permissions to make sure they match!
WARNING: DO NOT USE WINDOWS TO COPY/EXTRACT FILES TO/FROM PHONE. IT WILL OMIT THE HIDDEN FILE CHAMELEON.HASH. YOUR BOOST/TING/VIRGIN MOBILE/ETC FLASH WILL GET WIPED OUT IF THE CONTENTS OF YOUR /CARRIER FOLDER DON'T MATCH THE SCREENSHOTS BELOW.
Reboot the phone and perform an Update Profile.
The screen shots attached are contents of /carrier folder of "SOURCE" Sprint Galaxy S4 phone.
Give it a try and let me know if it worked for you and what phone(s) you used.
If you'd like to thank me, please click on the "Thanks" button instead of posting a thank you note. Let's save storage and bandwidth. And please, please, please...DO NOT QUOTE THIS POST IN YOUR REPLY JUST TO THANK ME! Again for those who don't know me, I do not accept personal donations. Instead I encourage you to donate to the American Cancer Society, to your local church, or any other not for profit charities.

FAQ (Frequently Asked Questions):
Q: My phone is already rooted. How do I configure ES File Explorer to show hidden files and allow writes to system partition?
A: Do the following:
1) Install the latest version of ES File Explorer from the Play Store. Launch it.
2) On the upper left hand corner, there's a blue icon that looks like a phone superimposed on a globe. Click on that icon.
3) Expand the Tools section.
4) Scroll down and find "Show hidden files". Turn that on.
5) Scroll down and find "Root Explorer". Turn that on.
6) Grant root access.
7) Press on the word "Root" on "Root Explorer".
8) Choose "Mount R/W"
9) Look for "/system" and choose "RW"
10) Press OK button.
11) Done.
Q: I have just done a ##786# or ##7286# to factory reset the phone. The Update Profile fix didn't work for me. Are there extra steps I need to do?
A: Yes! Read post #1. See "This fix assumes the following:". Read assumption #5, 6, 7, and 8!

reserved #2

reserved #3

You're the man. I've been looking for a Note 3 HFA loop fix. Figured since the carrier partition got corrupted on the Sprint Note 2 phones that it'd be doing the same on the Note 3.
Is there any chance of posting a zip with the carrier partition/folder? Or is there sensitive information in there?
Sent from my SPH-L900. Please hit the thanks button if I helped you out!

ecs87 said:
You're the man. I've been looking for a Note 3 HFA loop fix. Figured since the carrier partition got corrupted on the Sprint Note 2 phones that it'd be doing the same on the Note 3.
Is there any chance of posting a zip with the carrier partition/folder? Or is there sensitive information in there?
Sent from my SPH-L900. Please hit the thanks button if I helped you out!
Click to expand...
Click to collapse
I believe there are a couple or so sensitive info in the properties.db when I took a look at it using SQL Lite. I'll see if I can change the values a bit to make it more generic. I'm thinking though that the .chameleon.hash is an MD5 hash of the entire contents of /carrier. If a file is changed manually, the hash won't match and it won't work. In fact to see if this is the case, I put a different .chameleon.hash yesterday just to play around with it. After I rebooted the phone, MDN, MIN, and Profile 1 got wiped out and I had to reflash the phone again. The /carrier folder also got reverted back as if you did a ##786# on the phone.

I just attached carrier.zip in the first post. Enjoy.
Unzip contents of zip file in /carrier so that the files/folders would look like the attached screen shots in the first post.
Please give it a try and let me know if it works for you.
Thanks.

The .zip method alpine man posted worked like a charm man thank you this will save some flashers alot of time

AlpineMan said:
I just attached carrier.zip in the first post. Enjoy.
Unzip contents of zip file in /carrier so that the files/folders would look like the attached screen shots in the first post.
Please give it a try and let me know if it works for you.
Thanks.
Click to expand...
Click to collapse
Thanks so much for uploading the carrier zip. You saved my phone! It mostly worked, in that after ##72786# and then entering my mdn and msid I was able to finally get my s4 on boost to update my prl and profile. However, it is still trying to do the hfa and has not completed that. And every time I reboot it tries to activate. Also, I now have data back, but only 1x. When I was on the phone with Boost last night they said there might be some problems in my area, so all of the remaining issues might be due to that. I will post an update if/when something changes.
In any case, thank you so much for saving my phone!

Genius pure genius!
Sent from my SPH-L900 using XDA Premium 4 mobile app

davidl1986 said:
Thanks so much for uploading the carrier zip. You saved my phone! It mostly worked, in that after ##72786# and then entering my mdn and msid I was able to finally get my s4 on boost to update my prl and profile. However, it is still trying to do the hfa and has not completed that. And every time I reboot it tries to activate. Also, I now have data back, but only 1x. When I was on the phone with Boost last night they said there might be some problems in my area, so all of the remaining issues might be due to that. I will post an update if/when something changes.
In any case, thank you so much for saving my phone!
Click to expand...
Click to collapse
You must do assumptions #5 thru #7 before applying the fix. I ran into HFA if I didn't do those steps. Manually entering MDN and MIN via ##phone's MSL# didn't work for me. Had to flash it. Same with Profile 0 and 1. Used DFS.
BTW, Update Profile works via WiFi I believe. So connect your phone to WiFi to test. This way you're not dependent on the strength of Sprint signal wherever you are.
For those who got it working,which phone(s) did you get it to work? I'd like to take a survey so I can update the original post.
Sent from my SM-N900V using Tapatalk

Thanks for this! Worked like a charm on my s4!
Sent from my SPH-L720 using Tapatalk

davidl1986 said:
Thanks so much for uploading the carrier zip. You saved my phone! It mostly worked, in that after ##72786# and then entering my mdn and msid I was able to finally get my s4 on boost to update my prl and profile. However, it is still trying to do the hfa and has not completed that. And every time I reboot it tries to activate. Also, I now have data back, but only 1x. When I was on the phone with Boost last night they said there might be some problems in my area, so all of the remaining issues might be due to that. I will post an update if/when something changes.
In any case, thank you so much for saving my phone!
Click to expand...
Click to collapse
Somehow I haven't encountered a problem on the S4 phones. Have you tried filling in the MDN and MIN in DFS after repairing the MEID? That ALWAYS fixes it for me. I've only had an issue on the Note 3. Figures...seeing as how the Note 2 has the exact same issue.
Sent from my SPH-L900. Please hit the thanks button if I helped you out!

I'm on Sprint Samsung Note 3 model SM-N900P, Flashed to Boost Mobile.
I replaced the folder. The HFA went away. The Update Profile and Update PRL button is active again, but when trying to do an update, I get:
------------------------------------------------------------------------------------------------------
Error
The PRL update could not be completed. Please try again later.
If the problem persists, you may need to contact Customer Service.
Error: Connection Error (6621)
------------------------------------------------------------------------------------------------------
I tried both under Wifi only and 3G only, without any luck, same error.
ALSO: Don't put your /carrier folder elsewhere. Not the microsd card. For some reason, after a reboost. The one I copied from the /carrier out automatically got erased from the microsd. It's like I never made a backup. Thanx god it didn't brick.

Update PRL didn't work... How about Update Profile?
You can zip your original /carrier folder for backup purposes. Not sure why your /carrier folder you copied in SD card would get wiped out. I put mine in a sub folder in external SD card (not internal SD card) ... something like /ROM/carrier.
Anyone else have issues with update PRL?
Sent from my SM-N900V using Tapatalk

Same thing, Update Profile also didnt work.
It work in a sense that it popped up and tried to connect to the network. But then it say the exact error as mentioned above.
AlpineMan said:
Update PRL didn't work... How about Update Profile?
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse

Let's wait until another Sprint Note 3 user provide feedback. I don't have a Sprint Note 3 to test.
In the meantime, try reflashing your MDN, MIN, and Profile 1 as described in the steps in post #1. Reboot the phone and try the update again.
Thanks.
Sent from my SM-N900V using Tapatalk

AlpineMan,
You said you have a fix for the NO SIM situation too?
I got 8 Sprint Note 3 to play around with. 3 of them have no problem with NO SIM situation. The other 5 keep erroring out the SIM and the NO SIM would pop up

Look in my flashing thread. No SIM fix is in the FAQ.
Sent from my SM-N900V using Tapatalk

TTmaster99 said:
Same thing, Update Profile also didnt work.
It work in a sense that it popped up and tried to connect to the network. But then it say the exact error as mentioned above.
Click to expand...
Click to collapse
Are you able to do Update Profile in the "original" phone?
Sent from my SM-N900V using Tapatalk

Related

[Q] Samsung Apps "updated", now I cannot access it

My "Samsung Apps" app updated last night, when I went into it afterwards it said it needed a SIM card and then closed.
I don't use a SIM card in my Tab, never have and never will, I have no need for it, I own a phone for that sort of thing (and it's a phone with WiFi hotspot).
It worked fine before, but now there's no access
any ideas of a way round it or a way to "upgrade" to the previous version?
cheers
mmace said:
My "Samsung Apps" app updated last night, when I went into it afterwards it said it needed a SIM card and then closed.
I don't use a SIM card in my Tab, never have and never will, I have no need for it, I own a phone for that sort of thing (and it's a phone with WiFi hotspot).
It worked fine before, but now there's no access
any ideas of a way round it or a way to "upgrade" to the previous version?
cheers
Click to expand...
Click to collapse
I had some issues with this app myself, even though I have a SIM installed. Launched it and it requested to update. But it kept on failing during the update process. Luckily I had a backup of the apk file so thought I'd just push that to the device and run the install. But that failed too. Then I decided to just push the file to /system/app. Rebooted the device and it started working. It now shows the new app store layout (which is basically a poor imitation of Marketplace, but still better than the previous samsung one). I guess I must still be on the original version code wise, but at least it works again...
I've attached the file if you want to give it a try. You'll need to have rooted your device to make /system rw. Or you could copy to sd card and try installing it.
paulshields said:
I had some issues with this app myself, even though I have a SIM installed. Launched it and it requested to update. But it kept on failing during the update process. Luckily I had a backup of the apk file so thought I'd just push that to the device and run the install. But that failed too. Then I decided to just push the file to /system/app. Rebooted the device and it started working. It now shows the new app store layout (which is basically a poor imitation of Marketplace, but still better than the previous samsung one). I guess I must still be on the original version code wise, but at least it works again...
I've attached the file if you want to give it a try. You'll need to have rooted your device to make /system rw. Or you could copy to sd card and try installing it.
Click to expand...
Click to collapse
brilliant, will give it a go tonight, cheers
You can try advice from http://forum.xda-developers.com/showthread.php?t=981503 ( about market enabler )

[MOD] PRL Write Enabler for Sprint Galaxy S4 [MDC][MDL][MJA]

First off this work is based on Digiblur's PRL Write Enabler from the Sprint Galaxy S3 forum. I simply modified it & packaged it for our Sprint Galaxy S4 devices.
Here is the original S3 post that this was found in... http://forum.xda-developers.com/showthread.php?t=2159054
Also, post #8 below provides additional info.
I tested it by flashing with TWRP and it worked on my stock, rooted S4 with the MDC and MDL releases.
If you're on a stock rooted Rom and not using TWRP, you can just copy the HiddenMenu.apk from inside the zip file downloaded into /system/app/ and overwrite the one that's there. (You'll need a root enabled file browser to do this of course).
Thanks to Unknownforce here is a version for MJA...
http://www.androidfilehost.com/?fid=23212708291676468
Enjoy!!
This certainly will save me from having to use CDMA WS to switch like I just did yesterday. 55014 was not working well for me in my market so I switched back to 25014.
What is write enabler?
Keeps aborting for me
THEGAMEPLAY94 said:
Keeps aborting for me
Click to expand...
Click to collapse
You mean the install of the zip?
If so, you can pull the APK out of the zip and replace HiddenMenu.apk in the system folder (make a backup first). You may want to also set the permissions to rw-r-r after replacing the system app. Reboot, then you should be good to go.
@ChadH42,
I know it seems like I'm harping on you but I'm really not..
You need to update the OP on - 1. What is this? 2. What does this do? 3. Why is this in the Development Section.. ?
A good OP leads to less questions.. Development Sections aren't for information. That would be considered a Discussion Thread that belongs in General.
Let's keep the Dev section clean from the start.
My suggestion - Edit the OP on the What's/Why's?/How To's and you won't get posts like mine.
To the OP, updated your title as [WIP], and I suggest you provided additional information so that folks aren't bricking their new devices.
I will check in, if you need anything, let me know.
What this MOD does (in case the OP takes a little while to chime in)
What this MOD does is modifies our ##DATA# (select View) menu to allow for the PRL Write option to appear and function. With this menu option, the user can change their PRL on the fly from the device itself by placing a copy of the desired PRL in the root directory of Internal Storage and name it "test.prl" (no quotes), dial ##DATA# (choose View), tap Write PRL, tap the sub-menu option Write PRL ---wait--- and then the device reboots with the test.prl PRL applied upon reboot. Not every PRL works and sometimes it takes a couple of tries.
A tip for multiple PRL options is to, of course, keep a folder of the PRLs you like and keep them labeled in there. Copy the desired PRL to proper place as needed and just remember to rename the copy to "test.prl". Switch back and forth as you please. I hope this helps clear some confusion and helps some find purpose with the MOD like I have.
For a clear set of instructions that I did not want to just copy verbatim, check the link below. Also, if you are having issues with the zip not installing in CWM, just extract the APK from the ZIP (inside the system/app folder), use Root Explorer or your favorite root-access file explorer to place the APK in the APP folder, apply the proper permissions and reboot.
Ref from the GS3: http://forum.xda-developers.com/showthread.php?t=1748516
So I unzipped the file, replaced the hidden menu original apk with the new one, then set permissions, rebooted, then tried ##3282# and the view and edit options do not appear.. .. It just blanks out the items I just entered
Sent from my SPH-L720 using Tapatalk 2
jayjay7411 said:
So I unzipped the file, replaced the hidden menu original apk with the new one, then set permissions, rebooted, then tried ##3282# and the view and edit options do not appear.. .. It just blanks out the items I just entered
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
Did you clear Cache when you rebooted?
What ROM are you using?
ChadH42 said:
Did you clear Cache when you rebooted?
What ROM are you using?
Click to expand...
Click to collapse
+1...same thing is happenening to me...Im on force rom. when i type in the dialer code it just blanks out.
lilmikeyv said:
+1...same thing is happenening to me...Im on force rom. when i type in the dialer code it just blanks out.
Click to expand...
Click to collapse
I just tried this mod with the Force ROM and it did the same thing (blank options). The only thing I can think of is that it works with the odex version of the stock ROM so maybe its a problem with deodex ROMs of which Force is one.
O okay. Its currently not a necessary thing for me at the moment, just nice for when I travel to Alabama. Hopefully later on someone gets it working on deodex.
Sent from my Nexus 4 using Tapatalk 2
ChadH42 said:
I just tried this mod with the Force ROM and it did the same thing (blank options). The only thing I can think of is that it works with the odex version of the stock ROM so maybe its a problem with deodex ROMs of which Force is one.
Click to expand...
Click to collapse
I am actually running it on the Rooted Stock DeOdexed ROM. So I don't think it is an Odex/DeOdex issue...might be a Force ROM issue.
Also, moot point for Force ROM (1.0+) anyway because the PRL Write mod is already included with that.
I'm also having this problem and I'm pretty sure it was working this morning. I haven't flashed anything since then.
edit-- I tried:
1. wiping both cache's
2. killing background process "OIThiddenmenu"
neither fixed it.
I reinstalled the stock odex ROM and flashed this again and it worked.
Just an FYI, OP, I get Error Status 6 when trying to flash this via recovery, which indicates one of two things. Either the format of the file is incorrect or there is a syntax error. The syntax looks fine, but opening in basic Notepad shouldn't "look pretty" like it currently does. So it's likely it was edited with a non-Unix-compatible text editor like Notepad or MS-Word...
To make modifications to an updater-script (or just about any Android/Linux files like this) you need something like Notepad++ or gVim.
Anyways, I did a quick test with this, and it does in fact not work on my ROM as it is, but I see why it's failing, but I don't know what exactly it's trying to reference yet. (It fails with an id number instead of a name, so I'll have to de-compile some things to find it.)
I'm not sure it's a ROM issue or a MOD issue yet. (meaning it might have to be updated for each custom ROM, depending on how they are configured) But I'll track it down and update when I can.
Unknownforce said:
Just an FYI, OP, I get Error Status 6 when trying to flash this via recovery, which indicates one of two things. Either the format of the file is incorrect or there is a syntax error. The syntax looks fine, but opening in basic Notepad shouldn't "look pretty" like it currently does. So it's likely it was edited with a non-Unix-compatible text editor like Notepad or MS-Word...
To make modifications to an updater-script (or just about any Android/Linux files like this) you need something like Notepad++ or gVim.
Anyways, I did a quick test with this, and it does in fact not work on my ROM as it is, but I see why it's failing, but I don't know what exactly it's trying to reference yet. (It fails with an id number instead of a name, so I'll have to de-compile some things to find it.)
I'm not sure it's a ROM issue or a MOD issue yet. (meaning it might have to be updated for each custom ROM, depending on how they are configured) But I'll track it down and update when I can.
Click to expand...
Click to collapse
Thanks for all your help here..
I had the error status 6 problem in the beginning and thought I fixed it. You are correct that I used MS WordPad to edit the files.
ChadH42 said:
Thanks for all your help here..
I had the error status 6 problem in the beginning and thought I fixed it. You are correct that I used MS WordPad to edit the files.
Click to expand...
Click to collapse
I think TWRP can read the non Unix type characters, which is why it works on a different recovery.
I'm hoping it's a mod issue and I can just modify the mod to work universally regardless of the rom. But we'll see.
Sent from my SPH-L720 using xda app-developers app
fails in recovery for me.
says error executing updater binary in zip
in stock rooted...

Manual Update not working was missing kindleupdates folder

Hi. I followed the directions off amazon website for manual update but it doesn't work and their instructions are by "corporate standards" lol. I am running 11.3.1.0_user_310084920 and I just downloaded update-kindle-7.4.8_D025_4849020.bin the latest from the amazon website.
Amazons website didn't say anything about a specific folder to put the update into it just said put it into the main drive folder. so I looked it up and there is supposed to be a folder called "kindleupdates" <hopefully case sensitive like this. I just created the folder on the drive and put the .bin into it then i went to the device menu and selected system updates then I click check now cause that is the only option available. after it runs it says last updated failed with a retry button now. when i click the retry button it doesnt work at all just flashes the text of last update failed.
I did this without creating the kindleupdates folder and also with it. nothing happens. and it only wants to connect to wifi if it is disconnected.
adb is working with my device fine if there is anything else i can do. I didn't push the file with adb though, i used gmtp to transfer the file and it is there.
for right this second i am just wanting to get this thing back to full stock since I have it rooted and i have multiple small issues with it like the status bar gone and chaning the build.prop for it doesn't work then work with anything else after since I have uninstalled to many system apps.
i dont have a fastboot cable but i seen and heard from stunts that it may not be needed because of buffer size.
i also unrooted this tablet and factory reset it and all to try the update as well. the root exploit is nice and quick lol
thanks to anyones help
You don't have the right version for your Kf. If you try to flash v7.x.x over your 11.x.x you will brick it.
Sent from my SCH-I545 using XDA Free mobile app
This is the page you need to download the update from.
http://www.amazon.com/gp/help/customer/display.html?nodeId=201357170
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Thanks guys can't believe I overlooked version but once I downloaded the other version it did the same thing. Grand pc Google page showed how to add it and that's the way I went. Successful. Now like new gonna watch closer what I do with root

How to: AT&T EPTT push to talk working on any rooted ATT Android model phone.

EDIT: I have figured out how to make the EPTT work on any rooted android phone. Skip to post #6 for the tutorial and proof.
ProStreetCamaro said:
I have rooted and installed SU. I have tried Helium to backup the app on my old S3 then install the app on my new S5. It wont register that way. I tried Device spoofer to make it look like an S3 and it still wont register. I found an older thread where the guy said it worked with both above mentioned methods on his Note 3. But they dont seem to work on the S5. Anybody have any other ideas? Is the network possibly seeing the S5 sim card and simply going NOPE not happening or does it read the device info instead? If it is the sim maybe they can reactivate my S3 sim and maybe I can get it working that way?
Any thoughts or help would be greatly appreciated.
Click to expand...
Click to collapse
Try using Titanium Backup and doing the exact same thing; back up the app on your S3 to your SD card, move the card to your S5, restore the app. Should work fine. I've never worked with Helium.
cmerlyn said:
Try using Titanium Backup and doing the exact same thing; back up the app on your S3 to your SD card, move the card to your S5, restore the app. Should work fine. I've never worked with Helium.
Click to expand...
Click to collapse
I will give that a try. It seems like helium backs everything up except for the registration data and the network even when i spoof it still knows it is an S5. They told me at the store they expect eptt to be updated to work with the S5 soon but how long is "soon"? A week or two is no big deal but any longer becomes a real issue. I use it all the time. Luckily I have a paid subscription to titanium so when i get home I will give her a whirl and see what happens.
Same issue. It tries to activate on the network and it wont allow it.
You have to fix your sd permissions use this app.
https://play.google.com/store/apps/details?id=nextapp.sdfix
Ok guys here is the way to do it if anybody else ever runs into this situation. Device spoofer does work but it makes everything on the screen super small and after you activate EPTT and get it up and working then switch back to the stock profile it then stops working again.
In order to get the EPTT app to work on all non supported ATT android phones you must change the phones model number. I followed this tutorial and it worked perfectly. You must be rooted.
http://www.skytechblog.com/2013/01/change-mode-number-to-galaxy-s4-or.html
"Requirements:- A rooted Android device, Root explorer & patience
So let's Start..!! Video Tutorial
1. Start the Root Explorer app.
2. Go to System folder its in the root if the device
3. Make sure that System is in Read/Write from the top right
corner.
4. Look for a file named
build.prop in system folder.
5. Long press it for Options and then choose Text editor.
7. Search the line as followed ro.product.model= and then change the text after = sign to whatever you like your Model number to be displayed.
8. Press back and hit Save.
9. Exit the app and Reboot or simply Power off and on it.
That's it...its done now check the edited name in Settings>About phone> Model number
To get back to the original:- Just delete the build.prop and rename the build.prop.bak again to build.prop and reboot "
I changed mine to an S4 which is supported. The registration network looks for the Model number to verify it is being used on a supported device. Simply change it to the name of a supported device and waaa laaaa working EPTT.
As you can see by the icon at the top left I am signed in to EPTT and it does work great on the S5.
I know very few use this but for those that do and want a newer phone then here is your 100% working answer if you are willing to root your phone.

[GUIDE] How to fix "Domestic Roaming" on Sprint (and other) Nougat (and other) ROMs

[GUIDE] How to fix "Domestic Roaming" on Sprint (and other) Nougat (and other) ROMs
One of the issues with running the latest Nougat ROMs on this device is that they all say "Domestic Roaming" instead of "Sprint" and also display an R instead of 3G, 1x, etc on the signal display. After much research, I've found out it's that the phone doesn't recognize the tower as a Sprint tower and thus assumes you're roaming. The fix for that is in a little file called eri.xml. What I did was take the file from this OP (all credit goes to him) and modify it a little to get it working properly (it only had three of the four needed Roaming Indicators). I've attached my modified version to the OP of this thread, but here are the steps if you want to create your own. Note that this can be done on a PC or on your phone directly. You will need root! (but since you are most likely needing this for a custom ROM, you probably have it).
If you are just using my file directly:
Download the file and copy to phone if not downloading from there.
Copy and paste the eri.xml file to /data using the file manager of your choice (must be able to browse using root).
Change the permissions on the file to 777 (ie to Read Write eXecute for Owner, Group, and Others).
Reboot phone.
If you are going to make adjustments:
Download the file.
Unzip the file and then open eri.xml in a text editor.
Open up this list of Roaming Indicators from this Github eri.xml source
On that site, use your browser's find feature to search for your carrier. For Sprint, there are four of them (0, 1, 99, 123).
In your text editor, edit RoamingIndicator="#" to match your carrier's roaming indicator number and edit EriText="Sprint" to match your carrier's name. Note that you can change the name to whatever you want and it will scroll if it's too long (or so I've read).
Repeat step 5 for all the roaming indicator numbers for your carrier.
If you need to add extra ones, use copy and paste to do so.
Make sure that NumberOfEriEntries="#" matches the number of entries you have when you finish.
Save eri.xml and copy it to your phone if it's not already there.
Copy and paste file to /data using the file manager of your choice (must be able to browse using root).
Change the permissions on the file to 777 (ie to Read Write eXecute for Owner, Group, and Others).
Reboot phone.
At this point, you should see Sprint as your carrier and no more R on the network meter in the status bar.
I almost didn't create a new thread as I didn't do much, but I wanted to keep all the Q&A and troubleshooting in one place and not clutter the other threads. Plus, I wanted to expand upon some of the steps on what you have to do. If you have any questions or need help, please let me know.
Credits:
snandlal for his eri.xml file and tutorial to get me started (give the man a thanks!)
Hexagon ROM guys for displaying their source on Github
Works for me, thanks a ton!
Tried this; got "Changing permissions was not successful. Please note that some file systems do not allow permission changes." Please help!
clarkkentdroid said:
Tried this; got "Changing permissions was not successful. Please note that some file systems do not allow permission changes." Please help!
Click to expand...
Click to collapse
The only time I see something like that is if the file manager isn't root capable, it doesn't get root permissions somehow, or the phone isn't rooted. What file managing app are you using? I did this successfully using Solid Explorer File Manager, although I'm sure any other one that gets root would do.
coal686 said:
The only time I see something like that is if the file manager isn't root capable, it doesn't get root permissions somehow, or the phone isn't rooted. What file managing app are you using? I did this successfully using Solid Explorer File Manager, although I'm sure any other one that gets root would do.
Click to expand...
Click to collapse
I used root browser on Resurrection Remix. It has Privacy Guard which asked if I wanted to grant root browser access, and I granted it. Root browser asked me to install busybox, which I did. I moved the file to /data successfully. However, it still didn't gain permission successfully.
clarkkentdroid said:
I used root browser on Resurrection Remix. It has Privacy Guard which asked if I wanted to grant root browser access, and I granted it. Root browser asked me to install busybox, which I did. I moved the file to /data successfully. However, it still didn't gain permission successfully.
Click to expand...
Click to collapse
Hmm... I looked and that's the exact ROM I tested it on. You'll find my post on the first page and yours is on the second. I don't think I installed a different su program like SuperSU. Two ideas:
1. Make sure you give Root Browser permanent root access.
2. Try a different file manager. I used Solid Explorer with no issue. If you don't want to buy it, try other free ones first. I think MiExplorer (I think that's its name) is free on XDA and is nice.
Thanks for the suggestions. I used solid explorer and it seemed like it worked. Permissions were still 777 after reboot, but I still don't get mobile data. My network says "Sprint" instead of "Domestic Roaming", at least.
Changing roms doesn't help, correct?
clarkkentdroid said:
Thanks for the suggestions. I used solid explorer and it seemed like it worked. Permissions were still 777 after reboot, but I still don't get mobile data. My network says "Sprint" instead of "Domestic Roaming", at least.
Changing roms doesn't help, correct?
Click to expand...
Click to collapse
Not getting mobile data is different than what this file does. This just fixes the displaying Domestic Roaming issue - it's just cosmetic.
I had no data issues on that ROM. The One m7 lacks some of Sprint's LTE bands and well it's Sprint, but that's not a ROM issue. Maybe try flashing back to a Sense ROM and updating Profile and PRL and then flash back to RR.
Your GitHub link to the list of roaming indicators seems to 404.
Yankee14 said:
Your GitHub link to the list of roaming indicators seems to 404.
Click to expand...
Click to collapse
Thanks! I've fixed the link to a similar one. The original link was the same file as this one and both only seemed to include Sprint. But, you can find Verizon there as well. As for others, you may need to search to get the right numbers.
coal686 said:
Hmm... I looked and that's the exact ROM I tested it on. You'll find my post on the first page and yours is on the second. I don't think I installed a different su program like SuperSU. Two ideas:
1. Make sure you give Root Browser permanent root access.
2. Try a different file manager. I used Solid Explorer with no issue. If you don't want to buy it, try other free ones first. I think MiExplorer (I think that's its name) is free on XDA and is nice.
Click to expand...
Click to collapse
AFter having a similar issue, and switching to Solid Explorer, I was able to change the permissions on the file, however it's still showing up as "Domestic Roaming". File is in /data and shows permissions as "777 -rwxrwxrwx"
Any help or ideas?
Thanks
TalyWhackin said:
AFter having a similar issue, and switching to Solid Explorer, I was able to change the permissions on the file, however it's still showing up as "Domestic Roaming". File is in /data and shows permissions as "777 -rwxrwxrwx"
Any help or ideas?
Thanks
Click to expand...
Click to collapse
Are you on Sprint? Also, what ROM are you running?
Yes I'm on Sprint. Just installed Resurrection remix 5.8.2
TalyWhackin said:
Yes I'm on Sprint. Just installed Resurrection remix 5.8.2
Click to expand...
Click to collapse
I think I tested on that one and it worked. If you followed the steps completely (restarted?), then I'm not sure why it's still telling you "Domestic Roaming" unless you truly are roaming.
Problem is, my m7 isn't activated anymore, so I can't really verify that nothing's changed with the ROMs since I tested things. Although they shouldn't have since I don't think they've been updated (I'm pretty sure I tested on 5.8.2 or RR).

Categories

Resources