how do i get my prop build number back to the original number 1254-1957 as my build prop says 1255-1753 and default prop says 1253-8238 con fussed as i tryied to change in root explorer but is just keeps going back
Save the modified build.prop and reboot, done
Sent from my iPad 2 using Tapatalk
Related
So I flashed the CyanogenMod 6.1 and I love it. Then tried to used the LCD changer to make my desktop like I had it before on the stock ROM. I changed the Value to 200 and now every time I change from Portrait to Landscape view and visa versa I get an error saying "Android.process.acore has stopped unexpectedly" Can anyone help with this? Thanks
I have no idea but should of just change the density in the build.prop using root explorer, really makes it easy...
Sent from my T-Mobile G2 using Tapatalk
Sent from my T-Mobile G2 using XDA App
I've been getting the acore force close a lot too. Not sure if its when changing orientation. Just happens sparatically.
I got the force close also when I set the density between 200 and 210. 190 and 220 both seem to work good so far.
I used the temp root method instead of directly modifying the build.prop file. Setting it at 200 is perfectly fine, had no issues.
Sent from my T-Mobile G2 using XDA App
im having the same problem @ 200...
just out of curiosity, and because im slightly lazy and at work right now, but where is build.prop located?(i dont have my phone with me right now and will have to change it later)
I tried 220 and got the same thing..ill try 190 and see. I will also try to edit the build.prop and see where that gets me
Sent from my T-Mobile G2 using XDA App
jeallen0 said:
im having the same problem @ 200...
just out of curiosity, and because im slightly lazy and at work right now, but where is build.prop located?(i dont have my phone with me right now and will have to change it later)
Click to expand...
Click to collapse
ok i found the build.prop... gonna change it on my break with root explorer and see what happens.
So I wiped and re-installed cyanogenrom6.1 and used lcd changer and tada!! No more force closes! must have just been something weird in the first install of cyanogen.
Sent from my T-Mobile G2 using XDA App
I am experiencing the same issues using 200. I want to change it in build.prop but cant get Root Explorer to mount it as RW...Anyone have any ideas?
I know its a hack...
I used adb to mount -o rw,remount /dev/block/mmcblk0p25 /system
then went in Root Explorer and could make the edits...What can i do to make it permanent?
wpickel said:
I am experiencing the same issues using 200. I want to change it in build.prop but cant get Root Explorer to mount it as RW...Anyone have any ideas?
Click to expand...
Click to collapse
Did you click the button on top of root explorer that says mount at r/w? You have to do that first. Edit then save. It will save a back-up build.prop. Make sure youve done a nandroid backup before this tho cuz if you screw up your build.prop it will be the only was to fix it.
wpickel said:
I am experiencing the same issues using 200. I want to change it in build.prop but cant get Root Explorer to mount it as RW...Anyone have any ideas?
Click to expand...
Click to collapse
yeah, make a copy of default.prop and add this line "ro.secure=0". repush the file with terminal emulator or adb.
Hello.
Can you help me how to change build.prop to bypass activation screen?
cmlusco mention that it is possible to do it.
Thanks
P.S.
cmlusco if your online please help me
gaiger said:
Hello.
Can you help me how to change build.prop to bypass activation screen?
cmlusco mention that it is possible to do it.
Thanks
P.S.
cmlusco if your online please help me
Click to expand...
Click to collapse
I have absolutely no experience with that however, I did a search on Google and this thread popped up. All I searched for was "how to edit build.prop":
http://forum.xda-developers.com/show....php?t=1236732
Anyone feel free to verify/correct me as I have never edited my build.prop before and I don't intend to. This is for anyone who may be looking for an answer. I won't say it is the answer as I've never done this before but hopefully this helps someone get on the proper train of thought.
if you're rooted try removing or renaming the phone.apk in /system/app. Make a copy of the ROM .zip to flag the original first in case something doesn't work ans definitely a backup in cwm. This should disable the activation nag and data phone capabilities. Not a good idea if you want to use it as a phone.
Sent from my Galaxy Nexus using Tapatalk
tiny4579 said:
if you're rooted try removing or renaming the phone.apk in /system/app. Make a copy of the ROM .zip to flag the original first in case something doesn't work ans definitely a backup in cwm. This should disable the activation nag and data phone capabilities. Not a good idea if you want to use it as a phone.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
if you mean i'm using my phone for text and call because i can't use them here in ph. there is no verizon carrier here in ph. sir tiny may i know what will disable after i edit the phone.apk?
Sent from my MT11i using Tapatalk
gaiger said:
if you mean i'm using my phone for text and call because i can't use them here in ph. there is no verizon carrier here in ph. sir tiny may i know what will disable after i edit the phone.apk?
Sent from my MT11i using Tapatalk
Click to expand...
Click to collapse
If you can't use your phone for text,data,and talking, you can disable it as it essentially disables the ROM's use of the cell's radio (wifi should still work).
Couple ways to do it:
1. remove the phone.apk from the zip and transfer new zip to sdcard and wipe system in recovery and re-flash rom.
2. Using root explorer or some kind of app that can write to /system, delete or rename the Phone.apk found in /system/app and reboot. If you get force close messages, just battery pull and boot the phone up again.
And, no there's no editing of the file itself just making the android system not able to find it. Not officially supported by devs to disable the radio but if you're having struggles to skip activation it is definitely worth a shot.
tiny4579 said:
If you can't use your phone for text,data,and talking, you can disable it as it essentially disables the ROM's use of the cell's radio (wifi should still work).
Couple ways to do it:
1. remove the phone.apk from the zip and transfer new zip to sdcard and wipe system in recovery and re-flash rom.
2. Using root explorer or some kind of app that can write to /system, delete or rename the Phone.apk found in /system/app and reboot. If you get force close messages, just battery pull and boot the phone up again.
And, no there's no editing of the file itself just making the android system not able to find it. Not officially supported by devs to disable the radio but if you're having struggles to skip activation it is definitely worth a shot.
Click to expand...
Click to collapse
this would be my last resort. im getting fraustrated because its almost a month finding a solution how to bypass this activation screen. thanks sir tiny you're a great help for me
hmmm... for some reason can i change the phone.apk to default setting?
Sent from my MT11i using Tapatalk
I believe if you just press the home button a TON then it should work
Sent from my ADR6425LVW using XDA App
You're talking about the screen that comes up when you first turn the phone on after you first buy the phone?
There's a way to do it without changing the build.prop, I'll look for it. I actually did it when j first got my phone.
Some people have said if you tap the top left, top right, bottom right, and bottom left corners in that order it bypasses it.
It works for some, the way I did it involved dialing some **number and changing somethings to 0000000
Sent from my ADR6300 using XDA App
---------- Post added at 05:10 PM ---------- Previous post was at 04:36 PM ----------
Here I found a link to where it says how to tap the corners
http://www.androidcentral.com/bypass-activation-screen-your-android-device
And I found the way I was talking about when you call **778 and change the settings
1. Select emergency call and dial ##778.
2. Select edit and enter service password 000000.
3. Select NAM Settings.
4. Change Mobile Directory number to 0000000000 (Ten digits).
5. Change MIN1 to 0000000 (Seven digits).
6. Change Mobile Country Code to 000 (Three digits).
7. As you back out "Commit the Change".
8. The phone will auto reboot in 10 seconds.
#2 works permanently as I remember and it's pretty easy to do.
Just picked up a new T-Mobile Note 2 and getting down to some rooting again, been awhile since Ive ROMd an android. Was hoping to stick to some stockish roms because i like the sammy bloatware (SNote, AllShare, Air View, SVoice, to name a few) and i would like to keep those features while running a custom rom because i also want to use Google Wallet. I was following a guide but i got stuck because I can't edit the build.prop file. I can use root explorer to open it, edit and save it, but when i open it up again, even without reboot, it reverts back to the original build.prop. Does this on rooted stock 4.1.2 and current Jedi Master 13 rom, any suggestions? thanks in advance.
Hi,
Android Version 4.2.2, Build No.KOT49LLS980ZVC, S/W Version LS980ZVC, On the keypad option LG keyboard, the "path input" option is missing. Tried Factory reset still unable to get that option. Any suggestion. O its a rooted device with 32GB storage
Use something to edit your build prop file, look for ime_trace_apply and ime_trace_menu and change both from false to true, save and reboot, should now have the option.
geeksmurf said:
Use something to edit your build prop file, look for ime_trace_apply and ime_trace_menu and change both from false to true, save and reboot, should now have the option.
Click to expand...
Click to collapse
Appreciated geeeksmurf for your reply, since i am a newbie for these kind of edits, can you tell me how to access build prop file?
ad196511 said:
Appreciated geeeksmurf for your reply, since i am a newbie for these kind of edits, can you tell me how to access build prop file?
Click to expand...
Click to collapse
Use an app like ROM Toolbox Lite to edit build.prop. Do a backup before messing with Build.Prop because if you change something incorrectly you can mess things up.
Sent from my LG-LS980
Ascertion said:
Use an app like ROM Toolbox Lite to edit build.prop. Do a backup before messing with Build.Prop because if you change something incorrectly you can mess things up.
Sent from my LG-LS980
Click to expand...
Click to collapse
Your solution was tried and it has been sucessful, Thanx a Ton, Cheers:good::good:
[SOLVED, I got a copy of the mixer_paths file]
I have an ATT LG G3 850(21Q) . The Android version is 5.0.1. The Kernel version is 3.4.0. The build number is LRX21Y.
I rooted it using the latest release from xda forum and was completely fine until I changed the mixer_paths.xml. I rebooted my phone and now I have no sound or microphone. I had made a copy of the file and replaced it. I rebooted and it there is still no sound. SMS/MMS messaging now also keeps popping up with an Unfortunately, Messaging has stopped . Anything I try to use with sound or video either has an error, forces closes, or both. I uninstalled everything and factory reset the phone and it still has a problem. I am thinking that the mixer_paths.xml got messed up or the build.prop was messed up. I only consciously changed the dpi setting which I also tried back at default with no luck. Any chance I could get a copy (file or paste) of one or both of these files? Pretty please with bacon on top?
Thanks in advance!
Are you still in need for the mixer path XML
My Friend have d85021q 5.0.1
You can email me on [email protected]