Hi i have a at&T LG OPTIMUS G E970 ROOTED AND I HAVE STOCK ROM JELLY BEAN
I found a way to swich between 2g and 3g but i doesntwo
I use the method with root explorer and edit build.prop file but it doesn't work it just create another file build.prop.bak and anything else.
Build.prop permission are rw-r--r--
Pliz help i need more battery life i just get 14 hours en hdspa+ where i live theres no lte 4g i just want 2g pliz!!!
Thanks in advance
On your dialer type in *#*#4636#*#* then select phone info and about two thirds of the way down that screen should be a drop down menu for network mode.
adfurgerson said:
On your dialer type in *#*#4636#*#* then select phone info and about two thirds of the way down that screen should be a drop down menu for network mode.
Click to expand...
Click to collapse
I tried but i cant see theoption
I am not on stock but assumed it would be the same. The build prop with .bak is a backup. After making changes with root explorer did you reboot? I would try changing build the build prop again, select save and exit, reboot, then try dialer code.
Edit... After reboot it may show up in settings without needing to use dialer. I believe it did on ICS anyways.
adfurgerson said:
I am not on stock but assumed it would be the same. The build prop with .bak is a backup. After making changes with root explorer did you reboot? I would try changing build the build prop again, select save and exit, reboot, then try dialer code.
Edit... After reboot it may show up in settings without needing to use dialer. I believe it did on ICS anyways.
Click to expand...
Click to collapse
I did everything you said and nothing :\
radhames3048 said:
I did everything you said and nothing :\
Click to expand...
Click to collapse
Sorry it didn't work. If I can come up which anything else I will post it here.
Related
And any tips to what change in it?
FelipeRRM said:
And any tips to what change in it?
Click to expand...
Click to collapse
Use root explorer. Go to /system and press and hold the build.prop file and then select open in text editor. Make sure you mount r/w in root explorer.
Thanks, and there it goes more money on Android Market =[
Edit: If I wanna add anything just add it to the end, save and reboot? This thing does need a search function to see if the line's already in there somewhere. Does it harm to add a line in the end if it is already there somewhere, working like botton lines overriding the top ones?
Any suggestions to add? And what's dalvik heapsize, head some talk about it.
would strongly suggest that you read and learn before making any changes.
FelipeRRM said:
Thanks, and there it goes more money on Android Market =[
Edit: If I wanna add anything just add it to the end, save and reboot? This thing does need a search function to see if the line's already in there somewhere. Does it harm to add a line in the end if it is already there somewhere, working like botton lines overriding the top ones?
Any suggestions to add? And what's dalvik heapsize, head some talk about it.
Click to expand...
Click to collapse
2nd post http://forum.xda-developers.com/showthread.php?p=10536952#post10536952
rendeiro2005 said:
2nd post http://forum.xda-developers.com/showthread.php?p=10536952#post10536952
Click to expand...
Click to collapse
Thanks, but I tried setting the dalvik to 12, as I use only light apps, to see if it would perfom any better (as you said it could be from 12 to 40), and the phone entered an endless loop from boot screen to "Sony Ericsson" screen. Had to re-flash, thankfuly xRecovery still worked and I had a zip in the SD card.
FelipeRRM said:
Thanks, but I tried setting the dalvik to 12, as I use only light apps, to see if it would perfom any better (as you said it could be from 12 to 40), and the phone entered an endless loop from boot screen to "Sony Ericsson" screen. Had to re-flash, thankfuly xRecovery still worked and I had a zip in the SD card.
Click to expand...
Click to collapse
that happen because you didn`t use the right permissions.
from what you`ve described i presume you edit build.prop and then copy paste to system, right?
do this:
enter on system folder, press and hold build.prop file select permitions and then check all. Now copy your new file to system and repeat the proccess (check all permitions).
reboot.
No, I had already changed it from 24 to 28 before, without errors, the only thing I did different in the first time was to "mount r/w". Maybe that's what happened lol.
Edit: Tried again, now mounting the r/w thing, like I did in the first time, but still got the boot loop.
I didn't change the permsions, I'm doing it directly through Root Explorer. click and hold, open in text editor.
i am on rooted stock ATT 2.2 firmware. I have busybox installed. Tried LCD density changer app from market but everytime i try to adjust the setting, the phone freezes and the only way to start back is by removing the battery. phone starts back up fine at 160 dpi again.
i have tried 180, 200, and 220 all with same results. any ideas what the problem is?
If you are using a rooted phone browser to build.prop, mount it R/W (root explorer e.g), and edit it.
You should be able to change it there manually.
In the /system/build.prop file, add this:
ro.sf.lcd_density=XXX (where XXX is the density number you want 160/240/etc)
Save, restart your phone and there you go.
MySeLfPT said:
If you are using a rooted phone browser to build.prop, mount it R/W (root explorer e.g), and edit it.
You should be able to change it there manually.
In the /system/build.prop file, add this:
ro.sf.lcd_density=XXX (where XXX is the density number you want 160/240/etc)
Save, restart your phone and there you go.
Click to expand...
Click to collapse
yeh, i saw that manual method but was afraid to try because i wasn't sure i'd be able to easily recover if there was a problem.
fortunately, i found a different app on the market "LCDDensity!" that works just fine. There is no preview and you have to reboot to make the change, but it does a fast reboot and it works flawlessly.
Thanks for the Help!
mongofrye said:
yeh, i saw that manual method but was afraid to try because i wasn't sure i'd be able to easily recover if there was a problem.
fortunately, i found a different app on the market "LCDDensity!" that works just fine. There is no preview and you have to reboot to make the change, but it does a fast reboot and it works flawlessly.
Thanks for the Help!
Click to expand...
Click to collapse
Tried it n it worked but after a full reboot, it reverts back to normal 160 density
MySeLfPT said:
If you are using a rooted phone browser to build.prop, mount it R/W (root explorer e.g), and edit it.
You should be able to change it there manually.
In the /system/build.prop file, add this:
ro.sf.lcd_density=XXX (where XXX is the density number you want 160/240/etc)
Save, restart your phone and there you go.
Click to expand...
Click to collapse
I cant seem to find this line in my build.prop
im using AWS 345 build rooted and Ive done this before with previous phone so im familiar with it but ive looked at least 5 times for that line but its nowhere to be found..
is there any other way???
ducehlmg said:
Tried it n it worked but after a full reboot, it reverts back to normal 160 density
I cant seem to find this line in my build.prop
im using AWS 345 build rooted and Ive done this before with previous phone so im familiar with it but ive looked at least 5 times for that line but its nowhere to be found..
is there any other way???
Click to expand...
Click to collapse
If the line doesn't exist, just add it. For some reason many of the stock Streak build.prop's don't have it in there. But, just add it and then you can tweak to your heart's content. That's what I did, and I'm on LCD=200 now.
mellojoe said:
If the line doesn't exist, just add it. For some reason many of the stock Streak build.prop's don't have it in there. But, just add it and then you can tweak to your heart's content. That's what I did, and I'm on LCD=200 now.
Click to expand...
Click to collapse
yea i figured that out but thanks for the tip... i set mine to 190 & i also grabbed ur wallpaper from the Screenshot thread.. so thanks for that too
MySeLfPT said:
If you are using a rooted phone browser to build.prop, mount it R/W (root explorer e.g), and edit it.
You should be able to change it there manually.
In the /system/build.prop file, add this:
ro.sf.lcd_density=XXX (where XXX is the density number you want 160/240/etc)
Save, restart your phone and there you go.
Click to expand...
Click to collapse
What did you use to edit the file?
mid_life_crisis said:
What did you use to edit the file?
Click to expand...
Click to collapse
Root Explorer. That's what I use. It is a paid app, but the best file explorer I've found. I'm a big fan.
mellojoe said:
If the line doesn't exist, just add it. For some reason many of the stock Streak build.prop's don't have it in there. But, just add it and then you can tweak to your heart's content. That's what I did, and I'm on LCD=200 now.
Click to expand...
Click to collapse
Worked for me. On 345 with density=180! Thanks mellojoe!
Try font changer if you don't want to meddle with build.prop.
Hey guys recently bought a Verizon Droid Razr XT912 The Problem is i live in India the problem is the ussd codes doesnt working with any network is there any way to fix ussd codes are important for me if i install custom rom will ussd codes work again? thanks and waiting for replies
L7iharsha said:
Hey guys recently bought a Verizon Droid Razr XT912 The Problem is i live in India the problem is the ussd codes doesnt working with any network is there any way to fix ussd codes are important for me if i install custom rom will ussd codes work again? thanks and waiting for replies
Click to expand...
Click to collapse
Have you resolved the issue? I am experiencing a quite similar problem with my Motorola XT912. The thing is that it works on some ROMs but it doesn't on just a few.
nook_lover said:
Have you resolved the issue? I am experiencing a quite similar problem with my Motorola XT912. The thing is that it works on some ROMs but it doesn't on just a few.
Click to expand...
Click to collapse
sorry for really late reply some times works some time not works
L7iharsha said:
sorry for really late reply some times works some time not works
Click to expand...
Click to collapse
Today I tried LiquidSmooth 2.2 kexec-based ROM and I am having the issue.
nook_lover said:
Today I tried LiquidSmooth 2.2 kexec-based ROM and I am having the issue.
Click to expand...
Click to collapse
after few days of started this thread my razr stolen so bought new one 2 days back still its also having issues i dunno what to do
L7iharsha said:
after few days of started this thread my razr stolen so bought new one 2 days back still its also having issues i dunno what to do
Click to expand...
Click to collapse
You can try Batakang ROM. It's working for me.
Fixing the ussd code problem
try this solution
Make sure your device is rooted.
Once you are done, install the root browser app from the PLAY STORE.
Enter the root browser app and scroll down till you see the SYSTEM folder.
Enter the SYSTEM folder and click on the build.prop option and select RB text editor, or any other text editor you may have to edit the build.prop folder.
Now make the following changes
telephony.lteOnCdmaDevice must be set to 0.
ro.mot.phonemode.vzwglobalphone must be set to 1
ro.telephony.gsm-routes-us-smsc must be set to 0
ro.cdma.home.operator.isnan must be set to 0
Once you make these changes, Save the build.prop
Exit the app and reboot.
thanks problem solve
:good:
theDroidHacker said:
try this solution
Make sure your device is rooted.
Once you are done, install the root browser app from the PLAY STORE.
Enter the root browser app and scroll down till you see the SYSTEM folder.
Enter the SYSTEM folder and click on the build.prop option and select RB text editor, or any other text editor you may have to edit the build.prop folder.
Now make the following changes
telephony.lteOnCdmaDevice must be set to 0.
ro.mot.phonemode.vzwglobalphone must be set to 1
ro.telephony.gsm-routes-us-smsc must be set to 0
ro.cdma.home.operator.isnan must be set to 0
Once you make these changes, Save the build.prop
Exit the app and reboot.
Click to expand...
Click to collapse
thanks man.
theDroidHacker said:
try this solution
Make sure your device is rooted.
Once you are done, install the root browser app from the PLAY STORE.
Enter the root browser app and scroll down till you see the SYSTEM folder.
Enter the SYSTEM folder and click on the build.prop option and select RB text editor, or any other text editor you may have to edit the build.prop folder.
Now make the following changes
telephony.lteOnCdmaDevice must be set to 0.
ro.mot.phonemode.vzwglobalphone must be set to 1
ro.telephony.gsm-routes-us-smsc must be set to 0
ro.cdma.home.operator.isnan must be set to 0
Once you make these changes, Save the build.prop
Exit the app and reboot.
Click to expand...
Click to collapse
This solution worked and saved me a lot of trouble. Just made this account to thank you.
Hi guys and gals. after many attempts, i have working cricket mms on my evo 3d
So... you root and research a good custom rom for you. You flash it, all goes well, it looks cool, feels nice you are on top of the world... (like I was) then you find your mms does not work...
here you go
1. make sure you have es file explorer downloaded
2. open your es file explorer
3. go to settings and select Root settings
4. check all the boxes and grant for superuser
now you are looking at the files on your sd card
5. click the "slash" icon on the top left
now you are looking at the whole phone
6. scroll down and select "system"
7. scroll down and select " build.prop"
it will ask you which program to use. I used the es note editor
NOTE you will be changing the build properties of you rom from sprint values to Cricket values
BE CAREFUL NOT TO CHANGE ANYTHING ELSE!!!
9. scroll down slowly you will see ro.build.fingerprint=Sprint
delete Sprint and change it to cricket
10. scroll down about 1/2 of the way down and you will see additional build properties
you will be looking for 4 lines
gsm.sim.operator.alpha=(change to Cricket)
gsm.sim.operator.numeric=(change to 310016)
gsm.operator.alpha=(change to Cricket)
gsm.operator.numeric(change to 310016)
and about 3/4 fof the way down
ro.cdma.home.operator.alpha=(change to Cricket)
ro.cdma.home.operator.numeric=(change to 310016)
back out and SAVE
REBOOT TWICE!!!!!!!!
11. now go into you es file explorer again this time to system
12. select etc
13. scroll down to a file called apns-conf.xml
delete it!
download this one and edit it with your phone number with notepad+ on your computer
edit the second one, not the value 45
https://www.dropbox.com/s/mqixefjs829t7jg/apns-conf.xml
put the file on your sd card and copy it to your system/etc folder
REBOOT TWICE!!!
16. using the voice dialer say "open apn"
17. delete the one you see
18. select reset to default
now you should see 2 apns and a little circle beside both
click the circle beside "cricket"
REBOOT TWICE AND WAIT FOR THE SYSTEM TO CATCH UP
download this mms.apk (this is not mine.. i found it for the evo 4g somewhere)
https://www.dropbox.com/s/iq42wk65ifolv8u/Mms.apk
using es file explorer, delete your old mms.apk under system/apps
remember, you have to mount es as root rw every time you reboot
roboot and move the new mms.apk to the system/apps and install
next reboot
go back into es file and (set root rw again)move to the new mms.apk.
long press it and chose permissions.
set your permissions like the screenshot in at the bottom
this has been proven on my evo3d
NOTE. if you are a flashaholic, you will store the mms.apk and the apns-config.xml on your sd card so you can do this with every flash
if this helped you, press the thanks button please!!!
I use cricket and I have never changed the build.prop to get mms working. I change the apn and if it is a jellybean rom the mms.apk.
do you know how to fix mms on htc evo 3d with virgin mobile?
jlmancuso said:
I use cricket and I have never changed the build.prop to get mms working. I change the apn and if it is a jellybean rom the mms.apk.
Click to expand...
Click to collapse
i tried to leave the sprint settings and got it to work (sometimes) it always works for me this way
bosshoss14 said:
do you know how to fix mms on htc evo 3d with virgin mobile?
Click to expand...
Click to collapse
nope... sorry. I only have cricket. but if you search for the apn settings for virgin and put them in, it may work
jaredl45600 said:
nope... sorry. I only have cricket. but if you search for the apn settings for virgin and put them in, it may work
Click to expand...
Click to collapse
Ok thanks :good::good:
Ok so for anyone wondering how to fix mms on virgin mobile/ sprint/ boost follow these instructions provided in this thread http://forum.xda-developers.com/showthread.php?t=1794956
jaredl45600 said:
Hi guys and gals. after many attempts, i have working cricket mms on my evo 3d
So... you root and research a good custom rom for you. You flash it, all goes well, it looks cool, feels nice you are on top of the world... (like I was) then you find your mms does not work...
here you go
1. make sure you have es file explorer downloaded
2. open your es file explorer
3. go to settings and select Root settings
4. check all the boxes and grant for superuser
now you are looking at the files on your sd card
5. click the "slash" icon on the top left
now you are looking at the whole phone
6. scroll down and select "system"
7. scroll down and select " build.prop"
it will ask you which program to use. I used the es note editor
NOTE you will be changing the build properties of you rom from sprint values to Cricket values
BE CAREFUL NOT TO CHANGE ANYTHING ELSE!!!
9. scroll down slowly you will see ro.build.fingerprint=Sprint
delete Sprint and change it to cricket
10. scroll down about 1/2 of the way down and you will see additional build properties
you will be looking for 4 lines
gsm.sim.operator.alpha=(change to Cricket)
gsm.sim.operator.numeric=(change to 310016)
gsm.operator.alpha=(change to Cricket)
gsm.operator.numeric(change to 310016)
and about 3/4 fof the way down
ro.cdma.home.operator.alpha=(change to Cricket)
ro.cdma.home.operator.numeric=(change to 310016)
back out and SAVE
REBOOT TWICE!!!!!!!!
11. now go into you es file explorer again this time to system
12. select etc
13. scroll down to a file called apns-conf.xml
delete it!
download this one and edit it with your phone number with notepad+ on your computer
edit the second one, not the value 45
https://www.dropbox.com/s/mqixefjs829t7jg/apns-conf.xml
put the file on your sd card and copy it to your system/etc folder
REBOOT TWICE!!!
16. using the voice dialer say "open apn"
17. delete the one you see
18. select reset to default
now you should see 2 apns and a little circle beside both
click the circle beside "cricket"
REBOOT TWICE AND WAIT FOR THE SYSTEM TO CATCH UP
download this mms.apk (this is not mine.. i found it for the evo 4g somewhere)
https://www.dropbox.com/s/iq42wk65ifolv8u/Mms.apk
using es file explorer, delete your old mms.apk under system/apps
remember, you have to mount es as root rw every time you reboot
roboot and move the new mms.apk to the system/apps and install
next reboot
go back into es file and (set root rw again)move to the new mms.apk.
long press it and chose permissions.
set your permissions like the screenshot in at the bottom
this has been proven on my evo3d
NOTE. if you are a flashaholic, you will store the mms.apk and the apns-config.xml on your sd card so you can do this with every flash
if this helped you, press the thanks button please!!!
Click to expand...
Click to collapse
why the hell hasn't more people been to directed to this thread with unbeatable mms problems with cricket just changing apn settings DOES NOT WORK for alot of cricket users.
Edit: guess i shoulda seen that it was done on a evo3d as it didn't work for my evo 4g i shoulda known when two lines were missing from the build prop. as soon as i got to the voice dialer with the apns there were no apns listed and hitting reset to default brough nothing. back to the battery sucking no blue tooth everything cricket rom. Ive tried litterally hundreds of roms and mustve edited apns 1000 times and still cant get mms to work except for one rom.
The mms.apk was found on a evo 4g site somewhere. Maybe there is something else. Or maybe it was a 4g LTE. I don't remember now, but I know it will not work on stock versions of sprint ROMs. I tried.....
Sent from my PG86100 using xda premium
There are some lengthy conversations about this so I thought I would shorten things up a bit. This is what "I" did after reading for a an hour or so...
Doesn't work with CM and I had to have root access in order to do what I did. I'm pretty sure there's a non rooted method in the 1st link.
**** I Always do a nandroid/system backup via custom recovery before doing things like this . I'm not responsible for you jacking up your phone. I'm only relaying what I did to my phone so proceed at your own risk.
1) Do a backup in custom recovery
2) I used a file manager, Root Explorer, & confirmed hiddenmenu.apk was in /system/app
3) I used text editor in Root Explorer and navigated to /efs/carrier/HiddenMenu. Changed OFF to ON
4) reboot
5) I viewed LTE band by dialing *#0011#
6) I forced band 4 by dialing *#27663368378# then followed these steps umts>debug>phonecontrol>Network control>band>LTE
7) I reverted the band 4 force by dialing *#27663368378# then followed these steps umts>debug>phonecontrol>Network control>band>automatic. I had to go to sytem settings and get back on LTE & CDMA...menu soft key>system settings>connections>tethering and networks>mobile networks>network mode>LTE/CDMA.
***Now if you don't have the Hidden menu app (.apk) then below is a zipped copy. You will also find a copy of my carrier file which is the parent folder to Hidden menu (file/folder that contains the Hidden menu) . Use the carrier file if you cant get the OFF to ON change to persist (stay ON)
1) First do a backup in your custom recovery.
2) rename your carrier file to carrier.bak
3) copy my carrier file to your efs file
4) ) reboot system
5) profit
***OR***
1) Do a backup in custom recovery
2) rename your hiddenmenu to hiddenmenu.bak
3) copy my hiddenmenu to your carrier file
4) reboot system
5) profit
Credit for steps 1-3 goes to vacaloco...http://forum.xda-developers.com/showthread.php?t=2303905
Credit for step 4 goes to lynyrd65 here post #4...http://forum.xda-developers.com/showthread.php?t=2502716&highlight=aws
Credit, I "think", for step 5 goes to Nhawk here in post #138 http://forum.xda-developers.com/showthread.php?p=47142892...thanks for the tip Bait-Fish.
Your first link doesn't work. Can you please dumb it down for me, because I really need to get my phone working. Im on MetroPCS with this phone and cant get it to work.
czarcas7ic said:
Your first link doesn't work. Can you please dumb it down for me, because I really need to get my phone working. Im on MetroPCS with this phone and cant get it to work.
Click to expand...
Click to collapse
Did you follow the 4 steps? The links are for the purpose of giving credit and for those needing more info...
http://forum.xda-developers.com/showthread.php?t=2303905
OP link updated too...
ups2525 said:
Did you follow the 4 steps? That's for the purpose of giving credit and those needing more info...
http://forum.xda-developers.com/showthread.php?t=2303905
OP link updated too...
Click to expand...
Click to collapse
I know this is a stupid question but where do I get this hiddenmenu.apk?
czarcas7ic said:
I know this is a stupid question but where do I get this hiddenmenu.apk?
Click to expand...
Click to collapse
Not at all a stupid question. I'll update the OP. Thanks for asking.
Use a file manager (Root Explorer, Solid Explorer are what I use) and go to system/app and check for it there...
How would you go back to band 13 after forcing band 4?
Sent from my SCH-I545 using xda app-developers app
stuckintheskull said:
How would you go back to band 13 after forcing band 4?
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Again thanks for asking. I updated the OP so check out step 6...let me know if that does it...:good:
Just a note, step 4 can be done by simply going to settings/more/about phone/status/mobile network type
Sent from my SCH-I545 using XDA Premium 4 mobile app
joshm.1219 said:
Just a note, step 4 can be done by simply going to settings/more/about phone/status/mobile network type
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I always love it when a heavy hitter chimes in. So cool...thanks for sharing!
Thanks for posting this....very easy way to enable the hidden menu. I suspected my area was very recently update to support band 4 and just confirmed it. I'm getting 31 mbps (weak signal) and my wifes s3 is getting less than 10.
What is the purpose of doing this ? What is in the hidden menu ?
Sent from my SCH-I545 using Tapatalk
loco63 said:
What is the purpose of doing this ? What is in the hidden menu ?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Recent interest in the Samsung Hidden Menu is due to the new band 4 LTE that is producing the blazing fast speeds. Critical/important info can be viewed as well as other features can be changed in the Hidden Menu too. Some examples are your IMEI can be found by enabling the Sammy Hidden Menu and you can change your LTE band from 13 to band 4...
ok....i'm stuck. When I navigate to the file and change off to on, I save the file. But then when I return to view the file again, it has been switched back to off.
What am I doing wrong ? I am saving it. In fact, I get the message "You have made changes to this file, do you want to save before exit? " I choose yes. I must be missing something.....
loco63 said:
ok....i'm stuck. When I navigate to the file and change off to on, I save the file. But then when I return to view the file again, it has been switched back to off.
What am I doing wrong ? I am saving it. In fact, I get the message "You have made changes to this file, do you want to save before exit? " I choose yes. I must be missing something.....
Click to expand...
Click to collapse
U rooted?
What file manager are you using?
ups2525 said:
U rooted?
What file manager are you using?
Click to expand...
Click to collapse
yes, i am rooted. i am using root explorer. Android 4.3
its strange, like i said.....everytime i switch it to "on", it automatically switches it back to "off".
loco63 said:
yes, i am rooted. i am using root explorer. Android 4.3
its strange, like i said.....everytime i switch it to "on", it automatically switches it back to "off".
Click to expand...
Click to collapse
I just went back via RootExplorer and started from stock/OFF. Everything persisted. Try this app...
https://play.google.com/store/apps/details?id=com.speedsoftware.rootexplorer&hl=en
Once you enable the hidden menu what is it your wanting to do? When you change OFF to ON, save/exit, and immediately open the file back up what does it read?
ups2525 said:
I just went back via RootExplorer and started from stock/OFF. Everything persisted. Try this app...
https://play.google.com/store/apps/details?id=com.speedsoftware.rootexplorer&hl=en
Once you enable the hidden menu what is it your wanting to do? When you change OFF to ON, save/exit, and immediately open the file back up what does it read?
Click to expand...
Click to collapse
I really want to turn off the wifi power saving mode. I have been haveing persistant wifi problems after the 4.3 update and i wanted to give this a try.
I will try the suggested explorer. However, using root explorer, when i change the off to on, save and exit, when i return to the file, it is back to off.
here's a zip of my carrier/hiddenmenu file
1) First do a backup in your custom recovery.
***Here's a copy of my carrier file containing a hiddenmenu (set to OFF) and a hiddenmenu.bak.
2) rename your carrier file to carrier.bak
3) copy my carrier file to your efs file
4) reboot system
5) profit
***OR***
1) Do a backup in custom recovery
2) rename your hiddenmenu to hiddenmenu.bak
3) copy my hiddenmenu to your carrier file
4) reboot system
5) profit
That was super kind of you.
Thanks a million !! :good:
interesting post