I was wondering if i change the default network in build.prop from global to cdma, would it stick on reboot? I set it to cdma to conserve batt....but it defaults to global on reboot.
suzook said:
I was wondering if i change the default network in build.prop from global to cdma, would it stick on reboot? I set it to cdma to conserve batt....but it defaults to global on reboot.
Click to expand...
Click to collapse
extract the build.prop file open it in text editor and start hunting. ;-) you can use CTRL-F to look for key words like Global. Just dont go crazy changing things until someone comes up with a recovery to backup your system, unless your comfy with ADB commands to push a stock build.prop file back into place. If you mess with the wrong setting in there your phone may not turn on all the way.
Yes, i have a backup. I see it...it says global. Do i just replace that with cdma? I know the risks, thanks.
ro.telephony.default_network=4 is cdma mode
build.prop is rather well commented. >_>
Good tip - mine is set to UMTS/CDMA which I think is network 2 , but FC's on restart of the phone im guessing to auto change from global to UMTS/CDMA modes.
Not game enough to change this yet tho.
-smc
suzook said:
I was wondering if i change the default network in build.prop from global to cdma, would it stick on reboot? I set it to cdma to conserve batt....but it defaults to global on reboot.
Click to expand...
Click to collapse
Odd. I set mine to CDMA as well but it has stayed on CDMA mode after multiple reboots.
snowblind64 said:
Odd. I set mine to CDMA as well but it has stayed on CDMA mode after multiple reboots.
Click to expand...
Click to collapse
Mine has never changed back, either.
hi!
could somone make a good tutorial how to get to that build.prop???
please...
and is it even posible to edit it on original droid3 that is not rooted?
i found a thread with info how to fix bad network on xt862 but cant find how to get to that file!!
SO PLEASE help me..
my network connection is realy abd in UK using three... but on previous phone it was exelent...
I tried setting it to 3 because that's what the XT860 has.. (so I assume its GSM mode)... but I didn't notice any differences. I assume it's just the default value when you first turn on the phone or reset setting
miciic said:
hi!
could somone make a good tutorial how to get to that build.prop???
please...
and is it even posible to edit it on original droid3 that is not rooted?
i found a thread with info how to fix bad network on xt862 but cant find how to get to that file!!
SO PLEASE help me..
my network connection is realy abd in UK using three... but on previous phone it was exelent...
Click to expand...
Click to collapse
Use adb(android debugging bridge) google where to find it and then use these.commands
adb pull /system/build.prop (replace this with a chosen directory on your computer)
For example I would put
adb pull /system/build.prop /home/endo/"Android stuff"
You can then edit the build.prop with a text editor. When done restore it with
adb push (your directory) /system/build.prop
If you get an error about /system being read.only use
adb shell
busybox mount -o remount,rw /system
Make sure to save a unedited copy on your computer just in cass
xt860, android 2.3.5, Eclipse 1.1.1
DoubleYouPee said:
I tried setting it to 3 because that's what the XT860 has.. (so I assume its GSM mode)... but I didn't notice any differences. I assume it's just the default value when you first turn on the phone or reset setting
Click to expand...
Click to collapse
3 defaults to GSM/WCDMA indeed. But it only matters after hard reset.
Sent from my XT860 using Tapatalk
I've noticed that I have to clear data and cache after pushing a new build.prop sometimes. ro.telephony.default_network= 0 for wdcma only, 3 for gsm/wcdma, 4 for cdma
Willis111 said:
I've noticed that I have to clear data and cache after pushing a new build.prop sometimes. ro.telephony.default_network= 0 for wdcma only, 3 for umts/wcdma, 4 for cdma
Click to expand...
Click to collapse
I wonder if that's why I couldn't get your.modded build.prop to fix my fc on cm7. Il have to give that a try
xt860, android 2.3.5, Monster rom
Endoroid said:
I wonder if that's why I couldn't get your.modded build.prop to fix my fc on cm7. Il have to give that a try
xt860, android 2.3.5, Monster rom
Click to expand...
Click to collapse
I made a custom cm7 build.prop for the xt860 using Hashcodes cm7 build.prop as a base and just importing bell specific/umts vars but didn't have any luck with data. It did fix the phone fc loop. I'll dig around and post it when I come across it. If you start importing libs from the stock rom you'll start fcing again so make sure adb is enabled on boot and it's handy to have the cm7 libs extracted somewhere so you can push them back to your phone and get voice/text, easier than reflashing or anything if you want to start over. If you check the radio log (logcat -b radio) you can see data trying to .connect but complaints about HSPA being unsupported. It could be just some little setting we're missing or the libs aren't supporting our connection. I did make a quick edit to enable dual radio operation before posting, lemme know if you have any luck Feel free to repost it in your xt860 roms thread, I'm not going to link it anywhere but this post unless I have a full solution.
Re-uploaded cm7build.prop, edited a few settings and gave it a once over against the build.prop from the brazil retail, I come right online with that. As far as I can tell this version is 100% w/motorolas umts build.props for our phones as far as umts/wcdma
If you install cm7, push this to /system/build.prop (after remounting rw), wipe data/factory reset and then boot you should have no issues with the phone force crashing but still no data.
Related
For those of you having trouble seeing protected apps, I modified our fingerprint in the build.prop. What this does is spoofs the market into thinking its seeing a Droid 2 (with Froyo) It worked for me, let me know if it does for you.
1. Put build.prop into your AndroidSDK\TOOLS folder
2. Connect via USB.
3. CD (Navigate) in CMD to your tools folder
Mount your /system (adb remount) works for me
Copy and paste this
4. adb remount
5. adb push build.prop /system/build.prop
6. adb reboot
To test if you need this before you push the build.prop fix, search the market for Us Bank. If only 2 or 3 show up, you are not getting the full market. After this fix, you should see 10 items listed when you search for Us Bank.
Hope this helps.
2.2 Market Fix Build.Prop -- WITH STAGEFRIGHT=TRUE
This can also be done via Root Explorer.
Edit: Here is a "clean" build.prop for those of you who do not want the stagefright fix (which breaks video playback) Sorry, I was not aware it did that. Thank you.
Non Stagefright Build.prop -- WITH STAGEFRIGHT=FALSE
For everyone flipping out about Birdmans tweet and you want the stock build.prop, here ya go
Stock Build.prop -- WITH NOTHING! STOCK!
You only need the stock one if you ever plan on doing a factory reset. But, you also cant do a factory reset if you have removed or renamed apps so I feel that should be mentioned. If you've done any modding and you are planning on upgrading, your best bet is to always use the SBF anyway. I dont think birdman realizes the panic he sets in with one little tweet. Factory resets suck anyway. But then again... "you decide..."
Thanks to Jcase for giving me the original idea way back when. I just basically applied his Eris Market Fix to work with our phones.
This created several problems for me.
First, the build.prop file is a read-only system file and doing a push did not work for me.
I had to copy it to my sdcard and then in shell:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.
When I activated wi-fi, it worked fine, and did let me into the market.
I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.
Update:
restored my build.prop and still no go.
update2:
tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.
I'm starting over with SBF, update, FROYO, etc.
I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions
Found a fix
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Zaphod-Beeblebrox said:
This created several problems for me.
First, the build.prop file is a read-only system file and doing a push did not work for me.
I had to copy it to my sdcard and then in shell:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.
When I activated wi-fi, it worked fine, and did let me into the market.
I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.
Update:
restored my build.prop and still no go.
update2:
tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.
I'm starting over with SBF, update, FROYO, etc.
I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions
Click to expand...
Click to collapse
Firstly, I figured ppl would know how to use adb.
if you cant push the file, use "adb remount" and it will work.
Secondly,
Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.
I posted over at another thread, and it worked for everyone.
Check it.
http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html
elkniwcire said:
i must say i take no responsibility if this causes problems but this worked for me. Do a search in the market for "eris market fix." it was designed for the eris but works just fine on my droid x. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but i assume most everyone on froyo already is rooted.
Click to expand...
Click to collapse
yes this worked for me aswell thank you
Yes this method definitely works. I have market working now and can search for protected apps etc.
elkniwcire said:
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Click to expand...
Click to collapse
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.
Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.
he was just explaining where the idea comes from i think... You'd have to be crazy to use the eris market fix app on a droidx, just simply edit the build.prop fingerprint line.
I just used the root explorer meathod and now it wont boot.
I downloaded the file.
renamed my build.prob to build.prob/bak
placed the new build.prob in the system folder
rebooted and now after the M screen it just goes to a black screen with the backlight lit. Wont boot up. Im learning adb so this may be a noob question but can I access adb if the phone wont boot all the way up. That way I could change the build.prob back
Edit Delete Post: Im just retarted haha .prop not .prob :/
Could you plz give us some details on doing this with root explorer. Thanks
Prolly simple but I did try moving current build file then renaming and pasting yours without success doing us bank search. Also rebooted cleared cache and market history prior to search. Appreciate any help with doing this via root explorer.
LexusBrian400 said:
Firstly, I figured ppl would know how to use adb.
if you cant push the file, use "adb remount" and it will work.
Secondly,
Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.
I posted over at another thread, and it worked for everyone.
Check it.
http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html
Click to expand...
Click to collapse
LexusBrian400 said:
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.
Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.
Click to expand...
Click to collapse
I took a brief look at each file and I really don't understand how I got into trouble. As I said, I had not yet started doing any mods, just trying to install a few apps.
While I'm no computer or phone neophyte, I don't profess to be up to speed on Android yet. I do typically read through instructions pretty well, and search out multiple sources/explanations so I have a better 'understanding' of what I'm doing, rather than just "parrotting" the steps.
Having said that, I would like to know the difference between using 'adb remount' and the instructions I used in my first post. Is that just the difference in doing this via a shell command and not? ie, they perform the same action, just from a different starting point?
As for the Eris file, I did download that and all seems to be OK right now.
Sorry ahead of time for a possibly stupid question but I just wanted to be sure. Do you have to be rooted to do this fix?
Yes, it requires an edit to a file that you can only be edited when rooted
elkniwcire said:
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Click to expand...
Click to collapse
This works for me...thanks!
OP has been updated with original build.prop
Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input
will2live said:
Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input
Click to expand...
Click to collapse
Just use the non-stagefright one.
Just like the post says, stagefright breaks HD video playback for SOME people. However some people dont care and just want higher quadrant scores, so they use the stagefright=true build.prop
Use the =false version for better stability.
Thanks for the reply.
I'm aware this is better suited in the android development section, however I can't post there yet.
So I'm in an area where I can only get data with data roaming turned on. Liberty lacks the option to turn it on, and that was a killer for me. So I figured out how to turn it on!
First, you'll need a program called notepad++. Google it, its free.
You'll now need liberty rom. You should know where to get it.
Once its downloaded, open the rom. I used winrar, no need to extract the zip with it. Open the system folder and you'll find the build.prop. Open it with your newly installed notepad++. Once open, add. "ro.com.android.dataroaming=true" to the build prop. I added it to the bottom but I believe it doesn't matter where you add it. Click save and your done! Just flash it like normal and enjoy that sweet, sweet data.
I tried this and I still get the "Data Connectivity Lost - Data Roaming is turned off" notification.
Any thoughts?
Did you use NotePad++? And did you wipe data? Tell me the exact process you used.
danielkuhlman said:
Did you use NotePad++? And did you wipe data? Tell me the exact process you used.
Click to expand...
Click to collapse
Wiping data made the difference!
I figured coming from the same ROM I wouldn't have to worry about that, but apparently you do. I guess I'm still a bit confused on how exactly the build.prop file is used by the OS.
Thanks for the help!!!
i know people have said they couldnt edit build.prop in liberty, but i was able to edit it with root explorer, save it, reboot and it took effect. i didnt make the changes youre describing but i changed the build name
I tried editing build.prop and rebooting without success.
I copied build.prop to my SD card.
Edited the file with Notepad++ (obviously from my computer)
renamed build.prop in the System folder to build.prop.bak
copied build.prop from my SD card to the System directory
reset build.prop permissions
rebooted
The data roaming setting never took affect when I tried this. I have no idea what I did wrong.
blkwlf said:
I tried editing build.prop and rebooting without success.
I copied build.prop to my SD card.
Edited the file with Notepad++ (obviously from my computer)
renamed build.prop in the System folder to build.prop.bak
copied build.prop from my SD card to the System directory
reset build.prop permissions
rebooted
The data roaming setting never took affect when I tried this. I have no idea what I did wrong.
Click to expand...
Click to collapse
I was running monster rom, I downloaded liberty and changed the build.prop as described and worked like a charm. Possibly, since you tried changing the build.prop without wiping data and dataroaming was already disabled, it saved it like that. Much like when you enable usb debugging. If you flash a rom with it enabled without wiping, it stays enabled...
Hmmmm... you'd think changing the build prop would automatically change any stored settings. I'll look into this
danielkuhlman said:
Hmmmm... you'd think changing the build prop would automatically change any stored settings. I'll look into this
Click to expand...
Click to collapse
Exactly! I still think I must have been doing something wrong... probably messed up one of the mundane details. I always do that
I'll try recreating the steps you went through when I've a bit more time and a fully charged phone. Maybe I can learn something else useful
is this for the CDMA radio? i need to verify GSM with Liberty 2.0
I'm not sure, there's no gsm service around here (hardly cdma). You can try and see if it works.
Sent from my DROID3 using XDA App
I wrote this up to remove all the Rogers software, boot image and APNs
To use this you first need to flash the Rogers V20C firmware and root it, you don’t need to install Clockwork but I would suggest doing this and also performing a backup before running this.
Procedure
Make sure you have the latest LG drivers
Make sure you have USB Debugging turned on
Extract files to a folder
Run the batch file run.bat
Pick what you want to remove
Select 4 from the batch file to exit as this will reboot your phone which is required
After the phone is rebooted go to you APN list and select the “Reset to default”, it could take a few minutes for the reset to complete.
You will notice that the icon for data would will change from 4g to represent the true data connection. If you are unsure about this try a data speed check before running this patch and after.
The batch file is easy to follow so have a read and see what it is doing, you
might find you only want it to do only certain parts.
Any issues just re-flash or restore you backup.
Link to files: http://www.mediafire.com/?o8beibt207og33r
Please note there is an issue with setting your time if you have the "Use network-provided value", this causes a force close if you try to set the time. If you don't have this set then the force close doesn't occur. Quick update on this, it is the section that pushs the VPN, if you don't run this then you won't get this bug. After looking at the logs they are pointing to the Manifest.xml file but as I've never had an issue like this before it will take some time to repair.
Works. Perfect.
Default is the Rogers apn right. Or did your bat file change that? Just wondering. I have att us and never could get consistent data speeds.
Sent from my LG-P925 using XDA
Default is the Rogers apn right
Click to expand...
Click to collapse
, corret. In the batch file the flexprovider.apk, apns-conf.xml and flex.xml files all are replaced.
If you still have bad speeds after replacing these you could manually alter the flex.xml file to provide the carrier etc. there
<?xml version="1.0" encoding="utf-8"?>
<Flexinfo>
<Flexinfo
FLEX_COUNTRY_CODE="US"
FLEX_OPERATOR_CODE="ATT"
FLEX_MCC_CODE="310"
FLEX_MNC_CODE="410"
FLEX_REGION_CODE="0"
FLEX_SIMLOCK_ON="0"
FLEX_MODEL_CODE="0" />
</Flexinfo>
Taken from this post http://forum.xda-developers.com/archive/index.php/t-1293947.html
Thanks man. Will try later tonight.
Sent from my LG-P925 using XDA
Let me know how you get on akwhite23, as I just tried a quick test of taking these files from the stock ATT 2.2 rom, I had to manually add my local APN but it got the H+ and I was able to use data.
Maybe another option if your data is unstable??
Anyone know how to remove or change the rogers shutdown animation
Sent from my LG-P925g using xda premium
You will need to edit Poweroff.apk,or use the tool in this thread
How about if someone were to pull the poweroff.apk from a diff rom and installing it
Sent from my LG-P925g using xda premium
This is a great tool but it would be nice if you gave us options as to what we wanted to delete from this rom.
Confirmed just copying and replacing the Poweroff.apk from another rom works just set permissions reboot and good to go thanks for the advice
Sent from my LG-P925g using xda premium
teray0n said:
This is a great tool but it would be nice if you gave us options as to what we wanted to delete from this rom.
Click to expand...
Click to collapse
The file you run is a batch file, just use a text editor and "rem" the lines you don't wont. I have tried to break the batch file up into logical chunks.
If really needed I can add Press 1 for this, Press 2 for this etc.
Lets see what I people want.
Also
Yes to the Roggers shutdown image is in the Poweroff.apk, if you just replace it with another rom you might not get any logo when shutting down, if that is the case has a look at the script as if will show you where to place the shutdown images.
Thanks for the reply and yes using the options of yes or no or 1 or 2 would be great this way people in my opinion would have and enjoy more control over there phone. Again great script.
Sent from my LG-P925g using xda premium
Thanks for this package. Ran as stated and works perfectly. Many, many thanks!
Script has been changed to allow users to pick what they would like to remove
*Remove Rogger preloaded applications
*APN to Generic
*Remove Roggers start up and shutdown logo
Enjoy
Great job thanks.
Sent from my LG-P925g using xda premium
I have noticed that after using this, alot of apps in the market will no longer download due to incompatibility issues that were not there before. Apps such as Rom Toolbox, Advanced Task Killer and many more. I have reflashed and done this process twice to test and confirm. Removing the Rogers apps with this process seems to have caused a break somewhere.
johnw230873 said:
, corret. In the batch file the flexprovider.apk, apns-conf.xml and flex.xml files all are replaced.
If you still have bad speeds after replacing these you could manually alter the flex.xml file to provide the carrier etc. there
<?xml version="1.0" encoding="utf-8"?>
<Flexinfo>
<Flexinfo
FLEX_COUNTRY_CODE="US"
FLEX_OPERATOR_CODE="ATT"
FLEX_MCC_CODE="310"
FLEX_MNC_CODE="410"
FLEX_REGION_CODE="0"
FLEX_SIMLOCK_ON="0"
FLEX_MODEL_CODE="0" />
</Flexinfo>
Taken from this post http://forum.xda-developers.com/archive/index.php/t-1293947.html
Click to expand...
Click to collapse
do you still need to replace the phone dialer and contact apks like the link states to do?
Sent from my LG-P925g using xda premium
rebel1699, unsure what is happening as I have just tested the applciations in your post and they work fine for me???? This is the procedure I used on my phone to flash
Using LG flash software Flashed V20C
I then flash the V20C
booted up the rom applyed Dan root application
Applied CWM
Next I went into CWM and wiped data / factory & wipe cache Partition
I then booted up the phone and applied by script.
Up to now I hadn't signed in the market place.
A think the problem could be some bad data in your market place, could you try this for me
Under Manage Applications could you
find Market and Force Stop, Clear Data and Clear Cache
find google Services Framework and Force Stop, Clear Data
If this has work you should get a server error if you try to access the Market Place. Reset your phone and the market should come back.
Let me know how this goes
Markyzz
No it isn't a good idea to copy the phone.apk and contacts
Ok I have one problem after I do the match my time changes and then I go to settings and try and change it and it force closes
Sent from my LG-P925g using xda premium
i apologise for being a noob, i am from india and i recently purchased a droid 3, when i unlocked my droid 3 i was able to make calls and send text messages with all the GSM sims but none had data available in them, after some research i got to know that xt862 rom doesn't provide gsm data support internationally and i will have to install a Chinese xt882 rom for it to work. well at the start i didn't any idea of whatsoever ROM or root or safestarp ment but after a lot of research and reading i was able to root and safestrap my phone but when i tried installing xt882 rom using safestrap it came with an error. can any one please help me with this as i would really love to use my phone daily. i don't want it to end up as expensive music player
shantan said:
i apologise for being a noob, i am from india and i recently purchased a droid 3, when i unlocked my droid 3 i was able to make calls and send text messages with all the GSM sims but none had data available in them, after some research i got to know that xt862 rom doesn't provide gsm data support internationally and i will have to install a Chinese xt882 rom for it to work. well at the start i didn't any idea of whatsoever ROM or root or safestarp ment but after a lot of research and reading i was able to root and safestrap my phone but when i tried installing xt882 rom using safestrap it came with an error. can any one please help me with this as i would really love to use my phone daily. i don't want it to end up as expensive music player
Click to expand...
Click to collapse
You have to get the correct APN (Access Point Name) for your provider to make data/MMS to work, you should not require the XT883 firmware. Just try google with your SIM provider followed by APN settings.. such as "Orange UK APN Settings" or check their website, or give them a call for the correct APN settings. Some SIMs have the APNs locked into the SIM, some of them do not include APNs (You might check a phone from the SIM provider for the APN).
When you find the correct settings, go to Settings > Wireless & Network settings > Mobile Networks > Access Point Names
Create a new APN and enter the info you found. Also check Battery & Data Manager > Data delivery to ensure data is enabled.
Skreelink said:
You have to get the correct APN (Access Point Name) for your provider to make data/MMS to work, you should not require the XT883 firmware. Just try google with your SIM provider followed by APN settings.. such as "Orange UK APN Settings" or check their website, or give them a call for the correct APN settings. Some SIMs have the APNs locked into the SIM, some of them do not include APNs (You might check a phone from the SIM provider for the APN).
When you find the correct settings, go to Settings > Wireless & Network settings > Mobile Networks > Access Point Names
Create a new APN and enter the info you found. Also check Battery & Data Manager > Data delivery to ensure data is enabled.
Click to expand...
Click to collapse
i got the access point name from my provider but when i go in to Settings > Wireless & Network settings > Mobile Networks > Access Point Names the APN screen shows up blank with no functions to create or edit APN
shantan said:
i got the access point name from my provider but when i go in to Settings > Wireless & Network settings > Mobile Networks > Access Point Names the APN screen shows up blank with no functions to create or edit APN
Click to expand...
Click to collapse
Tap the menu softkey at the APN screen and tap add APN.
Skreelink said:
Tap the menu softkey at the APN screen and tap add APN.
Click to expand...
Click to collapse
cheers for the help, one last favour as i am new to ROMs can you suggest a good and easy ROM that i can put in to an sd card and install it with safestrap without any hassle
shantan said:
cheers for the help, one last favour as i am new to ROMs can you suggest a good and easy ROM that i can put in to an sd card and install it with safestrap without any hassle
Click to expand...
Click to collapse
I personally use MavRom (Maverick Rom) version 4.0, as version 4.5 has a battery drain issue with the overclock script. It's based on 906 with modifications and tweaks.
Skreelink said:
I personally use MavRom (Maverick Rom) version 4.0, as version 4.5 has a battery drain issue with the overclock script. It's based on 906 with modifications and tweaks.
Click to expand...
Click to collapse
so i was going through this thread http://forum.xda-developers.com/showthread.php?t=1406812 for flashing xt883 radio on my phone as the reception is very bad i had a few doubts
1) do you connect your phone to the pc while doing this
2) do you download root explorer on your phone from the app store and are there any free ones
3) and how do you go about doing this ( Use root explorer to push the build.prop into the system folder )
i am very sorry for being such a noob, its my first android phone
shantan said:
so i was going through this thread http://forum.xda-developers.com/showthread.php?t=1406812 for flashing xt883 radio on my phone as the reception is very bad i had a few doubts
1) do you connect your phone to the pc while doing this
2) do you download root explorer on your phone from the app store and are there any free ones
3) and how do you go about doing this ( Use root explorer to push the build.prop into the system folder )
i am very sorry for being such a noob, its my first android phone
Click to expand...
Click to collapse
On Stock and Blur based roms, there's a little line in the build.prop that Verizon snuck in.. that makes any GSM network appear to have bad reception (only 1~2 bars) but if you check under status, the reception is actually good. You can fix that by editing this line in build.prop;
ro.mot.phonemode.vzwglobalphone=1
Change the 1 to 0 and save, then reboot, this should fix the 'reception issue'
A free root browser would be JRummy's Root browser lite, or ES File Explorer (you can enable root browsing in settings).
Build.prop is in /system
IF YOU INSIST ON FLASHING XT883 (Only required for using AT&T/T-Mobile/Other USA GSM networks)
Open a root browser; copy the build.prop you have to the SDCard or somewhere safe. Copy the build.prop (after you edit the line I mentioned before on the PC, you can use notepad). After you put it in /system MAKE SURE YOU FIX THE PERMISSIONS. Most root browsers just long-press build.prop, then tap permissions (ES is Properties > permissions) Check only Read (on all three, user, other, etc) and Write on Owner ONLY.
Then use the fastboot instructions to flash the XT883 radio. THIS WILL BREAK VERIZON CDMA.
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...