Q&A for build.prop files from ATT_H810b & H810PRa for comparison
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for build.prop files from ATT_H810b & H810PRa for comparison. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
phineous said:
I've changed these settings, but not noticed any difference (H810pr settings in ()):
Code:
ro.build.target_operator=ATT (GLOBAL)
ro.build.target_country=US (COM)
telephony.lteOnCdmaDevice=0 (1, commented out in ATT)
Click to expand...
Click to collapse
i changed these settings on my h810pr to what you stated and the phone got stuck at bootup logo. had to reflash.
justnotonehere said:
i changed these settings on my h810pr to what you stated and the phone got stuck at bootup logo. had to reflash.
Click to expand...
Click to collapse
How did you edit the build.prop file and save it to your phone? I would guess it was a permissions problem rather than from those changes, unless you included the information inside the ().
phineous said:
How did you edit the build.prop file and save it to your phone? I would guess it was a permissions problem rather than from those changes, unless you included the information inside the ().
Click to expand...
Click to collapse
how would i know if it was a permissions problem? i copied it to my computer, searched the terms and changed it just as you had it written, parentheses and all, saved it as build.prop and replaced it in the original location. went to reboot it and just got stuck at the logo.
justnotonehere said:
how would i know if it was a permissions problem? i copied it to my computer, searched the terms and changed it just as you had it written, parentheses and all, saved it as build.prop and replaced it in the original location. went to reboot it and just got stuck at the logo.
Click to expand...
Click to collapse
Please do not edit your build.prop file till you know what you are doing.
Thank you!
phineous said:
Please do not edit your build.prop file till you know what you are doing.
Thank you!
Click to expand...
Click to collapse
thanks for the advice but that doesn't really help. im following the suggestions of others on different potential solutions to a problem im having. i have no problem having to reflash, reinstall or do whatever to my phone. I'm asking what other ways are you able to get your LTE settings to work? i attempted the solution that was given regarding changing those certain items, and that didnt work. so now what?
justnotonehere said:
thanks for the advice but that doesn't really help. im following the suggestions of others on different potential solutions to a problem im having. i have no problem having to reflash, reinstall or do whatever to my phone. I'm asking what other ways are you able to get your LTE settings to work? i attempted the solution that was given regarding changing those certain items, and that didnt work. so now what?
Click to expand...
Click to collapse
The solution to your problem is here in the forums and it's very easy to find, but I want you to find it yourself.
You will find many posts that don't apply to your problem, but if you read them you will learn more about troubleshooting your device.
Related
I seem to have temporarily bricked my gtab. When attempting to nvflash restore all goes well until I unzip the .bat file that is needed. When unzipped it seems to change the format of the file and it won't run. I've done a search on this and have heard of other people having this problem so I know it is solvable, but I just can't seem to get it to work.
Any help would be much appreciated.
Thanks!
deadeye,
Roebeet's original 5.0.0 thread in Developer Forum has a bunch of info as well as several links to posts others of us have put together about dealing with this problem.
There also is another post near the top of Developer I put together on the USB .zip files needed and where to get them.
And I know I have written a bunch of help messages with detailed info to other
folks with your problem.
Check these out and let us know if you have questions. I'm sure it can be brought back, but may take some research and learning.
Rev
got it
Thanks for your response!!!
Hi,
I have Motorola Atrix 2 AT&T on Android 2.3.6, And I had removed the Few Stock Apps:
AABsync.apk
Cmas.apk
Cmas.odex
Do any one with a same phone can post those files here or send them to eobender at gmail.com
They are located on /system/app , and you can get them or with Root Explorer or with Titanim Bacup.
Any Help will be Appreciated , and many many thanks will be given , without those files I can't upgrade to ICS
eobender said:
Hi,
I have Motorola Atrix 2 AT&T on Android 2.3.6, And I had removed the Few Stock Apps:
AABsync.apk
Cmas.apk
Cmas.odex
Do any one with a same phone can post those files here or send them to eobender at gmail.com
They are located on /system/app , and you can get them or with Root Explorer or with Titanim Bacup.
Any Help will be Appreciated , and many many thanks will be given , without those files I can't upgrade to ICS
Click to expand...
Click to collapse
Well, here's half of your request (I don't have the Cmas.apk/odex until I get home later): https://dl.dropbox.com/u/61960599/AABSync.zip
I checked the sha1's with the OTA updater-script.. they should work fine.
eobender said:
Hi,
I have Motorola Atrix 2 AT&T on Android 2.3.6, And I had removed the Few Stock Apps:
AABsync.apk
Cmas.apk
Cmas.odex
Do any one with a same phone can post those files here or send them to eobender at gmail.com
They are located on /system/app , and you can get them or with Root Explorer or with Titanim Bacup.
Any Help will be Appreciated , and many many thanks will be given , without those files I can't upgrade to ICS
Click to expand...
Click to collapse
Here you go. download the attachment
Why not just use the 2.3.6 fxz.That really is prolly the safest and fastest way to get you to a "good" point for an OTA to ICS.
jimbridgman said:
Why not just use the 2.3.6 fxz.That really is prolly the safest and fastest way to get you to a "good" point for an OTA to ICS.
Click to expand...
Click to collapse
Well, that's just not as fun..
alteredlikeness said:
Well, that's just not as fun..
Click to expand...
Click to collapse
LOL
Thank you very Much
jm2k7 said:
Here you go. download the attachment
Click to expand...
Click to collapse
Thank you very Much,
Thank you very Much,
Thank you very Much,
Thank you very Much,
:laugh::good::good::good::good::laugh:
very cool
jm2k7 said:
Here you go. download the attachment
Click to expand...
Click to collapse
That was very nice of you to help him out!
Hope you all don't mInd me posting under same thread. I'm missing android android2.3.6 stock apk which is called userdictionaryprovider.apk as well as its corrisponding odex. Thanks for your time. Ill bookmark this page to keep track if anyone has this for me to pickup.
ok, I see that there is a demand for files system/app,
download what you need on this page, there are all the files in the official rom 2.3.6 AT&T:
http://www.4shared.com/rar/--yN5Riz/SYSTEM_GB_236.html
well I hope you have been helpful. :good:
jm2k7 said:
ok, I see that there is a demand for files system/app,
download what you need on this page, there are all the files in the official rom 2.3.6 AT&T:
well I hope you have been helpful. :good:
Click to expand...
Click to collapse
Thank you so very much!! Replacing these files didn't fix my problem unfortunately. Makes me curious if Verizon has different version of these or is there something else i need to be looking for as to the reason my settings > user dictionary keeps force closing when i try to use it.
You've been a big help, i was looking for days for those files. I changed the permissions on them as well in a attempt to stop the force closing. they are now set to read only and only user can write, just like the rest of the files in there. I don't know what STSystem.apk is but it has all permissions enabled.
Maybe I didn't break this by deleting those files and i just noticed it being broken now. I'll post here later about how I fixed it, if anyone seems curious. Thanks for the help!!!
guated said:
Thank you so very much!! Replacing these files didn't fix my problem unfortunately. Makes me curious if Verizon has different version of these or is there something else i need to be looking for as to the reason my settings > user dictionary keeps force closing when i try to use it.
You've been a big help, i was looking for days for those files. I changed the permissions on them as well in a attempt to stop the force closing. they are now set to read only and only user can write, just like the rest of the files in there. I don't know what STSystem.apk is but it has all permissions enabled.
Maybe I didn't break this by deleting those files and i just noticed it being broken now. I'll post here later about how I fixed it, if anyone seems curious. Thanks for the help!!!
Click to expand...
Click to collapse
We must check that all permits are in 644 to all files have been copied to the system folder, there should be no loose ends, all at 644, then at the end, you have to reboot into recovery mode and do the wipes, then restart again and wait for the phone to resume the system, double check that everything works and that's it, if not, with regard to whether the files are from another operator due to different bloatware may be true that you can fail again.
jm2k7 said:
We must check that all permits are in 644 to all files have been copied to the system folder, there should be no loose ends, all at 644, then at the end, you have to reboot into recovery mode and do the wipes, then restart again and wait for the phone to resume the system, double check that everything works and that's it, if not, with regard to whether the files are from another operator due to different bloatware may be true that yoou can fail again.
Click to expand...
Click to collapse
I appreciate the fast reply and extensive knowledge. I don't understand what a 644 is nor what to wipe. I'm still using stock ROM and unaltered as far as flashing or anything more than rooting. I used SDmaid to move the files back into system/app as well as changing permissions. I will look into what a 644 is along with information about rebooting into recover mode if need be.
I would rather steer clear of having to reset the phone to stock, though I've done it before when i had to return a phone for defective hardware and didn't want to leave obvious super user and root on it. I left the whole setup of the CD image etc on the computer. I just don't want to depend on backups to recover my different game progress among other things.
Sorry for pretty much hi-jacking this thread. I didn't think it would be this hard and go this far. Thank you everyone for your patients.
Hey Guys,
I'm having a couple of issues with setting up adb on my Linux Box (Xubuntu 12.04) I downloaded Android SDK and installed Platform-Tools. I've tried most of the methods on XDA but when I "./adb devices" I get nothing. I have a Micromax A87 which is a rebranded version of Mito A78 (Anybody heard of it???).
I would like help with another issue too. I recently got into theming, I edited some .pngs (not 9s) and compiled it, then signed it and zipaligned it but when I put it in /system/app and rebooted, it worked only partially. The one's with the default mode as RGB work, but the one's with the default mode "indexed" didn't. Does Anybody have any Ideas???
BTW, I use Gimp and I change the mode to RGB before editing them.
Thanks in Advance...
JasonKZLY said:
I would like help with another issue too. I recently got into theming, I edited some .pngs (not 9s) and compiled it, then signed it and zipaligned it but when I put it in /system/app and rebooted, it worked only partially. The one's with the default mode as RGB work, but the one's with the default mode "indexed" didn't. Does Anybody have any Ideas???
Click to expand...
Click to collapse
Might be worth reading this before starting another thread - [GUIDE] - XDA New User Guide - Getting started on XDA, I know you're new, you're obviously eager to do something based on your other thread, but keep this in mind, nothing you've got to ask (which so far) hasn't been asked or discussed many a time before, so if themeing is what you want to get into, click the second link in my sig, read it, bookmark it then try and put into practice what it is you're trying to learn, and if at first you don't succeed, starting a new thread to ask a question that you'll probably figure out the answer to whilst you wait for someone to reply with an answer you could have probably found by typing your thread title into Google, isn't going to speed things up or help you learn.
There are some links to using apktool with Linux in my guide btw which should be of help.
THANKS, XPERIENCED!!!
I already read your theming guide and about 5 others on XDA Forums and I decided to get a better understanding of Themes.
I still face an issue, I can't setup ADB! I've tried most of the methods on XDA Forums and everything I can think of, it isn't working. I did use Google, most of them simply don't work. My question is not "How do I set-up ADB on my Linux?", It's "I can't setup ADB, can anybody help me?"
*sigh* Can anybody please help me???
EDIT: Solved it, adb working now!
Samsung Galaxy Note Edge Developer Edition 4.4.4 vzw
I use FM pro with root option checked.
I noticed that APN was not editable or add'able. Then looked into ways of fixing. I read somewhere to use BuildProp Editor and make a backup of build.prop, then edit it.
I installed BP editor and tried to make the backup, it failed. So I thought maybe it's not getting access, so I tried making it a system app, then tried the backup again, failed again. Then I made it a user app again and tried the option in FM pro to make system folders writable, then tried the BP backup again, success. At that point I just decided to back out of BP editor and check with FM pro to find the backup file, upon entering I found only the backup file on emulated 0, When normally it shows both 0 and legacy within emulated. I couldn't find legacy at all freaked out and deleted the backup made by BP, then I reloaded FM pro, still not showing legacy, got panicky at that point because lots of stuff is GONE off to visit Elvis and all the greats. Now I'm in the black, I try uncheck in the root and writable option in FM pro and legacy along with 0 are showing together again with matching files as is the norm, rechecked options and poof GONE again, only an empty 0 dir.
Reboot did nothing, runs as normal, boots and goes good. No noticeable issues with any apps or system. But I'm dumbfounded as to WTF is happening here. I made no changes to the actual build.prop. Also I noticed the re'entering BP Editor the backup was not showing up that's when I checked into FM Pro to find said backup, saw it and deleted it.
Any help would be greatly appreciated.
Vorridor said:
Samsung Galaxy Note Edge Developer Edition 4.4.4 vzw
I use FM pro with root option checked.
I noticed that APN was not editable or add'able. Then looked into ways of fixing. I read somewhere to use BuildProp Editor and make a backup of build.prop, then edit it.
I installed BP editor and tried to make the backup, it failed. So I thought maybe it's not getting access, so I tried making it a system app, then tried the backup again, failed again. Then I made it a user app again and tried the option in FM pro to make system folders writable, then tried the BP backup again, success. At that point I just decided to back out of BP editor and check with FM pro to find the backup file, upon entering I found only the backup file on emulated 0, When normally it shows both 0 and legacy within emulated. I couldn't find legacy at all freaked out and deleted the backup made by BP, then I reloaded FM pro, still not showing legacy, got panicky at that point because lots of stuff is GONE off to visit Elvis and all the greats. Now I'm in the black, I try uncheck in the root and writable option in FM pro and legacy along with 0 are showing together again with matching files as is the norm, rechecked options and poof GONE again, only an empty 0 dir.
Reboot did nothing, runs as normal, boots and goes good. No noticeable issues with any apps or system. But I'm dumbfounded as to WTF is happening here. I made no changes to the actual build.prop. Also I noticed the re'entering BP Editor the backup was not showing up that's when I checked into FM Pro to find said backup, saw it and deleted it.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Hello and thank you for using XDA Assist.
Sorry to hear about your trouble but fortunately there is an XDA area dedicated to the Samsung Galaxy Note Edge at http://forum.xda-developers.com/note-edge . Because your issue might be related to root and permissions matters specific to the VZW variant, I suggest you post your question with all relevant details in the Verizon subforum there at http://forum.xda-developers.com/note-edge/verizon-note-edge-android-development where the experts familiar with your device will be best able to guide you.
Good Luck!
Mike B. said:
Hello and thank you for using XDA Assist.
Sorry to hear about your trouble but fortunately there is an XDA area dedicated to the Samsung Galaxy Note Edge at http://forum.xda-developers.com/note-edge . Because your issue might be related to root and permissions matters specific to the VZW variant, I suggest you post your question with all relevant details in the Verizon subforum there at http://forum.xda-developers.com/note-edge/verizon-note-edge-android-development where the experts familiar with your device will be best able to guide you.
Good Luck!
Click to expand...
Click to collapse
Thank you, I did post in that area, and no hits yet. I posted here in hopes that it would get more attention to a possibly wide scale issue in newer models of android OS, as only a few people have this particular variant of the device. I'm not sure but it's probably not carrier specific.
Again thank you for your time in reading this and would be greatfull for any further technical input you or others may have.
Vorridor said:
Thank you, I did post in that area, and no hits yet. I posted here in hopes that it would get more attention to a possibly wide scale issue in newer models of android OS, as only a few people have this particular variant of the device. I'm not sure but it's probably not carrier specific.
Again thank you for your time in reading this and would be greatfull for any further technical input you or others may have.
Click to expand...
Click to collapse
No member can respond to you in this XDA Assist area as explained in the "Purpose of XDA Assist" thread at http://forum.xda-developers.com/showthread.php?t=2764768.
Because Verizon devices often have restrictions, such as locked bootloaders, not found on other models, the VZW Forum might be your best bet, but you might need to wait longer than a mere six or seven hours before anybody finds time to comment on your posts.
Thread closed.
Hi every one
just need to confirm from professional people here , i need to edit build.prop on my A9 device without rooting so that i could make some connection with my car screen (stupid screen accept only Samsung and LG) , Is that possible?
amro ibrahim said:
Hi every one
just need to confirm from professional people here , i need to edit build.prop on my A9 device without rooting so that i could make some connection with my car screen (stupid screen accept only Samsung and LG) , Is that possible?
Click to expand...
Click to collapse
First, this question gets asked A LOT so a simple search here or google will show numerous others asking this and their findings. It doesn't matter if its not specifically referring to HTC A9 or in this specific forum either.
That being said....to answer your question.....NO! ^_^ You will most likely need root to even access the system root folder where your build prop. You may find it using some app possibly that doesn't require root, open it and change values, HOWEVER, you will never be able to save these changes without root, sorry.
If you are knowledgeable on unpacking system images or have firmware.zip/tar etc that you can dig through and find the build prop, edit it on windows/linux/mac repack or rezip and flash it successfully....thats one way.
Another way would be to use ADB to pull what you want and push it back to system afterwards.....but not to sure as my phone(s) usually are rooted and never tried to use ADB unrooted. Somethings tells me that this too won't work but go for it.
mcbright80 said:
First, this question gets asked A LOT so a simple search here or google will show numerous others asking this and their findings. It doesn't matter if its not specifically referring to HTC A9 or in this specific forum either.
That being said....to answer your question.....NO! ^_^ You will most likely need root to even access the system root folder where your build prop. You may find it using some app possibly that doesn't require root, open it and change values, HOWEVER, you will never be able to save these changes without root, sorry.
If you are knowledgeable on unpacking system images or have firmware.zip/tar etc that you can dig through and find the build prop, edit it on windows/linux/mac repack or rezip and flash it successfully....thats one way.
Another way would be to use ADB to pull what you want and push it back to system afterwards.....but not to sure as my phone(s) usually are rooted and never tried to use ADB unrooted. Somethings tells me that this too won't work but go for it.
Click to expand...
Click to collapse
Actually i searched a LOT but i have found the TWO answers "Yes you can" AND "No you can not" , also people says yes you can giving steps i have no idea about it like this one
1. Make a process which executes "getprop" from the "/system/bin/getprop" directory and initialize the String which we want to get (ro.board.platform in example).
2. Make a BufferedReader which gets the value (String) by retrieving the data from a inputStreamReader().
3.Convert the BufferedReader to String.
. That is why i asked here again to get clear answer which i get it and many thanks for you
amro ibrahim said:
Actually i searched a LOT but i have found the TWO answers "Yes you can" AND "No you can not" , also people says yes you can giving steps i have no idea about it like this one
1. Make a process which executes "getprop" from the "/system/bin/getprop" directory and initialize the String which we want to get (ro.board.platform in example).
2. Make a BufferedReader which gets the value (String) by retrieving the data from a inputStreamReader().
3.Convert the BufferedReader to String.
. That is why i asked here again to get clear answer which i get it and many thanks for you
Click to expand...
Click to collapse
LOL i understand the frustration. I also spend a ridiculous amount of time scouring forums and any other place online for the many questions i need help with only to get fractured/incomplete answers or conflicting ones like you stated where it seems like the answer is both yes and no or whatever....its a real pain. Truthfully, I said you wouldn't be able to do this without root due to the level of difficulty of the other options trying without root. Creating bufferedreader etc is all Java Programming. You will need a decent working knowledge of java programming to be able to do what that guide was talking about.....i figured you might not have that so I said that NO to your question here. I know some of what that guide was explaining enough to create some of that they described but still not enough to feel comfy attempting. Your best option, i think, will be to extract the build prop from a stock.img and repack the system.img after editing the build.prop. Use 7zip to unzip/rezip the system.img and notepad++ to open/edit the build.prop and flash image in your recovery. You could also use Android Kitchen if you can. Plenty of tutorials on this. I linked two below for ya though. '
What were you looking to edit in the Build.prop anyhow? I assume you are disinclined to root/unlock bootloader for warranty issues correct?
BTW, sorry for such a late response...I am not always here for days at a time usually so.....
dsixda's Android Kitchen - http://forum.xda-developers.com/showthread.php?t=633246
Super-Rs - http://forum.xda-developers.com/chef-central/android/kitchen-superrs-kitchen-t3202296
mcbright80 said:
LOL i understand the frustration. I also spend a ridiculous amount of time scouring forums and any other place online for the many questions i need help with only to get fractured/incomplete answers or conflicting ones like you stated where it seems like the answer is both yes and no or whatever....its a real pain. Truthfully, I said you wouldn't be able to do this without root due to the level of difficulty of the other options trying without root. Creating bufferedreader etc is all Java Programming. You will need a decent working knowledge of java programming to be able to do what that guide was talking about.....i figured you might not have that so I said that NO to your question here. I know some of what that guide was explaining enough to create some of that they described but still not enough to feel comfy attempting. Your best option, i think, will be to extract the build prop from a stock.img and repack the system.img after editing the build.prop. Use 7zip to unzip/rezip the system.img and notepad++ to open/edit the build.prop and flash image in your recovery. You could also use Android Kitchen if you can. Plenty of tutorials on this. I linked two below for ya though. '
What were you looking to edit in the Build.prop anyhow? I assume you are disinclined to root/unlock bootloader for warranty issues correct?
BTW, sorry for such a late response...I am not always here for days at a time usually so.....
dsixda's Android Kitchen - http://forum.xda-developers.com/showthread.php?t=633246
Super-Rs - http://forum.xda-developers.com/chef-central/android/kitchen-superrs-kitchen-t3202296
Click to expand...
Click to collapse
Thanks again for your replay , actually i still trying to proceed your way .. i think i am too close to do it , but you know after one or two hour of Trying&searching i say to my self let us unlock this phone and finish this matter .. any way i am using the Android Kitchen and i hope i could do it