Related
I created a new thread for this because the old one was for development, and there's no more development
I finally decoded all the information GPS is providing, and updated the drivers to provide full GPS support.
Rootfs link below for those running from SD or NAND
This thread is for people who want the latest and greatest! As ROM builders integrate these libraries into their ROMs, you shouldn't have to come back here. GPS 5.0 is likely to stay, as I don't foresee any bugs.
Check out the old thread as well. Shidell put some work into an ADB how-to:
http://forum.xda-developers.com/showthread.php?t=616436
Rootfs with libgps5.0already pushed in (fixed some file permissions in this version and verified libgps is in there):
http://dl.dropbox.com/u/58383/rootfs-libgps5.0.zip
NBH (thanks jamezelle!):
http://5d698f86.linkbucks.com/
zImage and libgps.so attached! Rootfs above!
INSTRUCTIONS (SD): Replace your zImage and rootfs.img with the ones provided and reboot! (Put them in the android directory).
INSTRUCTIONS (NAND): Flash the new NBH. Then either flash the new rootfs.img, or adb push the library to your /lib/donut, /lib/eclair, and /lib directories.
Bugs remaining (I don't feel like hunting them down):
* Satellite reporting is finicky (this is an issue with the gps messages themselves). Satellites disappear and come back randomly. Only way to fix this is put in a state machine that combines satellite messages over multiple seconds. Also you'd need to prune satellites that are old. I implemented one, but had crashing issues so I ditched it.
* [Fixed] After booting, the first time you try to use GPS with Google Maps/Nav, it will fail. Exit out and re-enter and it will always work from then onward.
Changes:
-2.2: Fixed 'no position in maps/nav on first try after reboot'
-5.0: Fixed issue with negative altitudes, also rebaselined versioning to match versioning inside the software
For maximum compatibility, make sure you're running a 3.42.50 radio (CDMA):
http://forum.ppcgeeks.com/showpost.php?p=389964&postcount=8
Radio-only nbh that won't mess up your NAND.
Most newer NoMoRootfs (andboot) builds should already have this cooked in!
Kaiser zImage:
http://dl.dropbox.com/u/58383/kaiser_zImage.zip
(also any of dzo's newer zImages work)
i was using the previous zimage from 1/23/10 with rootfs 1/26/10 through sd card ext2. worked great. before that, I used the 1.4 version (the one before 1.5) without any problem (pushing the libgps.so).
however, with the 2.1 zimage and rootfs, the sattelite does not appear at all, after entering and exiting maps/gpstest numerous times and rebooting. any clue? going to try a few things (maybe will try pushing the libgps instead, or the old zimage) to see if I can sort it out.
You can try this one that uses a constant accuracy like the old ones to see if that fixes it. You'll have to push it.
The new lib uses 64-bit location values, which are much more accurate than the other things (this isn't causing your issue). The new one also uses different accuracy reporting, which android may not like.
Others: The above files definitely work, please don't use the attached.
Edit: Looks like I wasn't actually pushing libgps.so into rootfs! Don't use the below, it fakes the accuracy.
[Removed file]
I may have figured out what's causing the "no position lock on first try after reboot" problem. I put a fix together, it worked, but crashed the phone. I'll debug it later.
Tatnai's problem may be related. I'm assuming AGPS isn't working on his phone and that's causing the issue.
So with the new zImage, just drop that, along with your rootfs into the android folder, and that's it, right?
JacenSolo2001 said:
So with the new zImage, just drop that, along with your rootfs into the android folder, and that's it, right?
Click to expand...
Click to collapse
Yup, just put it in the android directory.
ok, done, and if GPSTest just sits there and never even gets 1 bar, is there an obvious reason or something that's messed up?
JacenSolo2001 said:
ok, done, and if GPSTest just sits there and never even gets 1 bar, is there an obvious reason or something that's messed up?
Click to expand...
Click to collapse
Whoops, I think my script was never actually pushing libgps to rootfs. I just looked and the timestamp is old. It may have been storing it in data.img. This means you're probably actually using the old libgps + new kernel = does not work.
I'm removing it for now. Either:
1) Go back to an old zImage/rootfs (I'll post a new one later)
2) Push it into android using shiddell's instructions: http://forum.xda-developers.com/showthread.php?t=616436
I'd appricate it if you'd do #2, so I can get testers to work out bugs (there shouldn't be any). However, I'll be putting out a libgps-2.2 later that fixes the "failed first lock on fresh reboot" bug, so I understand if you'll want until then for a new rootfs.
I may try the push tonight when i get in from work.
LOL, i had thought this was fairly "idiot proof", as you intended, so i was feeling like an idiot
Thanks again for all you're doing !
JacenSolo2001 said:
I may try the push tonight when i get in from work.
LOL, i had thought this was fairly "idiot proof", as you intended, so i was feeling like an idiot
Thanks again for all you're doing !
Click to expand...
Click to collapse
If you have ASTRO in your app tray, can you go to /lib and click-hold the libgps file. Hit details. What timestamp is it?
I don't have a /lib folder, i do have the file in my root directory for android, i just placed it there earlier when I got the zip file. The date for that is Jan 24
JacenSolo2001 said:
I don't have a /lib folder, i do have the file in my root directory for android, i just placed it there earlier when I got the zip file. The date for that is Jan 24
Click to expand...
Click to collapse
I'm talking about when android is booted (not /lib on the sdcard). It mounts the rootfs.img as a file system.
If you don't have a /lib directory, then it has to go in /system/lib
LD_LIBRARY_PATH usually only looks in /lib, then /system/lib
So it's possible I was pushing it into rootfs.img properly, and the modified timestamps aren't being updated.
Jan 26 2010
JacenSolo2001 said:
Jan 26 2010
Click to expand...
Click to collapse
Did you download the rootfs.img, or just put the libgps.so in the /sdcard/android directory.
Jan 26 is yesterday's update (libgps-1.6). Today's should be Jan 27th.
I'll include clearer directions when I push out a new libgps one last time that includes the latest bugfixes.
jnadke said:
Did you download the rootfs.img, or just put the libgps.so in the /sdcard/android directory.
Jan 26 is yesterday's update (libgps-1.6). Today's should be Jan 27th.
I'll include clearer directions when I push out a new libgps one last time that includes the latest bugfixes.
Click to expand...
Click to collapse
im going to make nbh's for the NAND flashers which files should i use
EDIT NVM seen your remark in post 3, im going to make nbh files with 2.1 zImage
jamezelle said:
im going to make nbh's for the NAND flashers which files should i use
EDIT NVM seen your remark in post 3, im going to make nbh files with 2.1 zImage
Click to expand...
Click to collapse
Thanks. This saves me from resizing my VMWare image to install Wine + LinuxPPCKitchen.
The zImage-2.1 should be final.
I'll be coming out with a libgps-2.2 which fixes the 'maps/nav no GPS first try after reboot' issue.
Apparently you need to set the HAS_ACCURACY flag all the time. I was trying to not set it if accuracy was 0.0. Apparently the flag not being there causes Maps/Nav to crash if position is reported. I did come out with a zImage-2.2 that checks if accuracy isn't 0 before sending a message to libgps, but this triggered random reboots (looks like it doesn't like this). Right now it just checks if a gpstime is being reported (which isn't right because it should report that even if no position lock is present).
I'm not sure what the proper method for Android GPS is to gracefully indicate GPS is lost, but the libgps-2.2 version on my phone seems to work with zImage-2.1.
jnadke said:
Thanks. This saves me from resizing my VMWare image to install Wine + LinuxPPCKitchen.
The zImage-2.1 should be final.
I'll be coming out with a libgps-2.2 which fixes the 'maps/nav no GPS first try after reboot' issue.
Apparently you need to set the HAS_ACCURACY flag all the time. I was trying to not set it if accuracy was 0.0. Apparently the flag not being there causes Maps/Nav to crash if position is reported.
Click to expand...
Click to collapse
here you go ppl use the rootfs in the first post!!! this contains all 3 resolutions for vogue only right now
NAND NBH FILES 2.1 "240 428 and 480"
btw jnadke im not getting a lock with this in 2.1(2.1 eclair btw) not sure if it is compatible
EDIT: pulled up maps and it rebooted phone ill try again
EDIT2: 10 min not one sat, so i backed out fof GPS Test and it rebooted phone
EDIT3: ok so im an idiot and didnt use your rootfs and pushed the lib to /lib and my init points to /system/lib lol so i fixed it all is well it works just fine
So does the rootfs.img file still need to be matched to the NBH file in some way? Is rootfs.img where the /lib directory is?
dmulligan said:
So does the rootfs.img file still need to be matched to the NBH file in some way? Is rootfs.img where the /lib directory is?
Click to expand...
Click to collapse
use the rootfs in the first post and the nbh's in my post on this page
i can confirm a lock
jamezelle said:
use the rootfs in the first post and the nbh's in my post on this page
i can confirm a lock
Click to expand...
Click to collapse
jnadke removed that file this morning.
I have been reading about "Fixing permissions" and I can see that ROM Manager on my Nook (running Phiremod v5.2 with CM7) has that function.
But what exactly does "Fixing permissions" mean?
When do I need to do that?
And what are the consequences?
Hope anyone can explain it to me - or guide me to a "ROM Manager/Fixing Permissions for Dummies"
http://en.wikipedia.org/wiki/Filesystem_permissions
Fixing Permissions does exactly what it says really. It fixes the file system access permission to the correct settings if for some reason they aren't set right which seems to happen from time to time. As far as I know there are no issues or consequences to running the script outside of wasting a few minutes while it runs since it's basically restoring things back to how they should of been.
Thanks for the reference and the answer.
Regarding the Nook, what interests me is why this is necessary from time to time. But maybe I shouldn't think about it too much
Caspar...as you add new apps or change ROMS, the filesystem permissions often get changed. sometimes they get changed to values that are detrimental(like a file getting set to read only when it needs to be writable). That's why the need for fixing the permissions.
If you don't do this, you sometimes end up with a scenario where an app expects to be able to write some information and can't. This generates an error, which if the app isn't able to handle it, crashes the app.
A well written app will have thought of this already, but most times developers just expect the proper permissions and don't add in error handling code, saving themselves work and the program some size.
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...
Hello!
So I have become a crazy cat collector with Nougat. But I recently switched roms so I dont have my beautiful cats anymore. :crying: What files can I copy from my old rom to get them back into my new one?
I found this article:
https://www.reddit.com/r/Android/comments/4tualq/what_i_know_about_cats_the_android_nougat_easter/
It didn't specifically say that cats can be restored but i tried copying the xml file from directory below. But it was a no-go
/root/data/data/com.android.egg/shared_prefs/mprefs.xml
Is there anyway I can be reunited with my cats. Please let me know.
God Bless
-The Cat Lady
You could try backing up the android easter egg app in tibu and restoring data when you flash the rom. I haven't tried it, so if you feel like taking a risk go for it.
CollinsB said:
Hello!
So I have become a crazy cat collector with Nougat. But I recently switched roms so I dont have my beautiful cats anymore. :crying: What files can I copy from my old rom to get them back into my new one?
I found this article:
https://www.reddit.com/r/Android/comments/4tualq/what_i_know_about_cats_the_android_nougat_easter/
It didn't specifically say that cats can be restored but i tried copying the xml file from directory below. But it was a no-go
/root/data/data/com.android.egg/shared_prefs/mprefs.xml
Is there anyway I can be reunited with my cats. Please let me know.
God Bless
-The Cat Lady
Click to expand...
Click to collapse
This might work but it also might crash your phone. Proceed at your own risk.
I was wondering if you ever figured out a way. I'm using a Nexus 5X so it's only a matter of time before the bootloops plague my device. Was hoping to back them up before then.
EDIT:
Would using ADB work?
Code:
adb backup -f "C:\CatsBackup20161229.ab" -apk com.android.egg
EDIT 2:
I was so close. Thanks to this Reddit post, I have used the following in a Windows Batch File to backup my Cats with a timestamp. Hope this helps any Googlers.
Code:
adb root
adb backup -f C:\CatsBackup_%date:~-4,4%%date:~-10,2%%date:~-7,2%.ab com.android.egg -system
What I'd done was long press the cat when one came up then just shared it to my Drive folder. I've also found duplicates will most likely come up (number of the cat) but the cat will be different color.
I've personally flashed numerous different nougat ROMs and different versions (7.0, 7.1, 7.1.1) in no particular order, and the Easter egg cat collection got backed up and restored on each and every ROM I've tried and used.
The way I go about this is, before I decide to switch ROMs or update using clean flash, I use titanium backup to backup the Easter egg app. Once I clean install an update or a different nougat ROM, I first unlock the nougat Easter egg in settings (tap the Android version a bunch and long press on the N animation to find the cat icon). Then head over to quick toggles, hit edit, find the cat toggle and add it to a desired slot. Finally, in titanium backup, find the Easter egg app, hit restore. It will ask what to restore, make sure you select "data only," do NOT restore "app + data," this may or may not cause system UI issues.
Requirements: Nougat ROM of your choice (any version) and root access.
This method works for restoring chrome tabs and possibly a few other system apps' data. Restoring system app(s) + data, however, will usually break things, so make sure to only restore the respective system apps' data only.
okay so i got the easteregg.ab file to back up onto my local disk, but i cannot get my phone to restore the .ab file through ADB.
ADB will say that i must unlock my device and allow the restore to complete however the phone is completely unresponsive to the request to restore, it as if nothing is happening.
what am i missing here :
adb backup -f easteregg.ab com.android.egg -system
(that puts an easteregg.ab file into c\users\xxxx)
then : adb restore c\users\xxxx
(adb then tells me "Now unlock your device and confirm the restore operation)
.....but nothing has happened and it asks for nothing on my phone and the cats are not loaded =(
Permissions. Were they set on the file when you restored it?
Strephon Alkhalikoi said:
Permissions. Were they set on the file when you restored it?
Click to expand...
Click to collapse
im not sure if i know which permissions your refering too, but the easteregg.ab file permissions are currently set to allow full control for the System, Administrator and the User.
How do i ensure the permissions are correct ?>
The permissions were likely completely stripped from the file when it was sent via ADB. You'll need to root and do one of the following.
*Use a terminal app to set permissions.
*Use a file manager with root access, navigate to the file's location, and set permissions manually.
The correct permissions are likely rw-r--r--, which uses the number 644.
Strephon Alkhalikoi said:
The permissions were likely completely stripped from the file when it was sent via ADB. You'll need to root and do one of the following.
*Use a terminal app to set permissions.
*Use a file manager with root access, navigate to the file's location, and set permissions manually.
The correct permissions are likely rw-r--r--, which uses the number 644.
Click to expand...
Click to collapse
My s7 edge is not rooted.
Is there anyway to restore the easteregg kitties with out root ? i thought that was possible.
Did you downgrade from a Nexus 6 to a S7? Sorry to hear that if true, because the S7 has a locked bootloader. The file likely never transferred to where you wanted it to go, as the locked bootloader would prevent that. Thus you need to unlock the bootloader to even transfer the file. ADB may have commands to set file permissions, but my recollection on that is hazy. It would also be irrelevant if the bootloader cannot be unlocked.
Strephon Alkhalikoi said:
Did you downgrade from a Nexus 6 to a S7? Sorry to hear that if true, because the S7 has a locked bootloader. The file likely never transferred to where you wanted it to go, as the locked bootloader would prevent that. Thus you need to unlock the bootloader to even transfer the file. ADB may have commands to set file permissions, but my recollection on that is hazy. It would also be irrelevant if the bootloader cannot be unlocked.
Click to expand...
Click to collapse
oh wow! i pulled up this thread last night and didn't even realize i was on the nexus 6 groups forums haha, boooooo on me =(
no i didnt down grade lol, i never had the nexus, i am just a s7 edge owner who doesn't want to loose their kitties in a phone swap =(
and yeah i had some real difficulties getting the .ab file to even save to my computer after messing around with a bunch of variations on commands through adb.
now im getting depressed again
..hey i REALLY appreciate all this help btw =\
Sorry to hear that. But unfortunately, unless you can unlock the bootloader, you're not going to be able to use ADB to transfer the file back. With a locked bootloader you can pull files, but not push them.
I shoulda realized that cause im not new to the rooting process at all and i hate having a phone with a locked bootloader but i really do like the s7 edge, it grew on me,....... alas my kittens will have to wait till the bootloader becomes available.....
Check the S7 Edge forums. I'm sure they have something that may help.
[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).