I flashed a couple rom's on my MT3G (currently on JACxRom) And noticing that under the model number is G1. I remember reading about typing something in terminal to fix this naming but cannot find it. Can anyone help? thanks!
nolimit78 said:
I flashed a couple rom's on my MT3G (currently on JACxRom) And noticing that under the model number is G1. I remember reading about typing something in terminal to fix this naming but cannot find it. Can anyone help? thanks!
Click to expand...
Click to collapse
I don't know if this causes any problems, but you can pull build.prop and edit the ro.product.model value to be whatever you want.
in a command window type:
Code:
adb pull system/build.prop build.prop
edit build.prop
Change the ro.product.model value from G1 to whatever you want and save the file.
Exit the editor.
Now type:
Code:
adb remount
adb push build.prop system/build.prop
adb reboot
Hope this helps.
I had been using HBO Go and Max Go on my Nook Color forever. Now, all of a sudden I get the message that these apps are no longer supported. Does anybody have a work around?
assuming you are using cm7 I had the same thing happen. to get it working again I had to change the resolution off of 180 to 185 to get it working again. As soon as it was working again I was able to change it back to 180 and make it work fine.
I don't have cm9 but I've been told the HBO go is not compatible with ICS on tablets. However it works fine on cm7.
Hope this helps
Any other thoughts?
Tried the kindle fire (1.5) version w.o. success.
Wish I had a pre 1.4 version to roll back to.
Probably moot once HBO supports tablets, but I used a combination of multiple build.prop files, shell scripts, and script manager app & widget.
Basically, one version of build.prop has default 160 lcd density
2nd version (named build.prop.hbo) has 185 lcd density
shell script hbo.sh (created by ES File Manager inside sdcard/scripts):
mount -o remount,rw /system
mv /system/build.prop /system/build.prop.bak
mv /system/build.prop.hbo /system/build.prop
reboot
in script manager, marked the script as favorite and su (run as superuser)
on home screen, added script manager widget to hbo.sh
to change density back, shell script hboback.sh:
mount -o remount,rw /system
mv /system/build.prop /system/build.prop.hbo
mv /system/build.prop.bak /system/build.prop
reboot
again, use script manager to mark favorite and su, then script manager widget to add shortcut to home screen - see http://forum.xda-developers.com/showthread.php?t=1509030
I wanted to start an official thread on performing build.prop edits on KFHD since no one has of yet. I have tinkered for several hours yesterday trying to get one that allows Google Play apps to install that show "unsupported device". I have had zero luck unfortunately, and am hoping some others want to take up the challenge and find a solution.
I suggest you get busybox before attempting this, it makes copying files easier. Get it in the GooglePlay store:
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
Make sure you back up your file first!!! I did these steps:
Code:
# adb shell
# su
# mount -o remount,rw /system
# cp /system/build.prop /system/build.prop.orig (cp comes with busybox see link above)
# cp /system/build.prop /sdcard/build.prop.orig
# exit
NOTE: If you didn't install busybox, then you can do the cp commands as below:
Code:
# cat /system/build.prop.orig > /system/build.prop
Word of caution, I have managed to get my Kindle into a boot loop several times through this, but fortunately have been able to recover (details below). I cannot guarantee that you won't damage your Kindle in the process, and prevent it from booting.
I am also attaching a copy of the stock build.prop in case you manage to damage yours. I can't guarantee you will be able to put it back if you get in a boot loop, but you should be able to at minimum "vi" the existing one and manually enter everything to fix you up.
Here are my recovery steps if you manage to get stuck in a boot loop (I notice this happens a lot if you modify the ro.product.board entry). All credit for saving my bacon (and showing us how to root) goes to jcase and sparkym3. One note, you cannot use "su" if you get in this state, you get some exception and the binary errors out about you not being fully booted.
Code:
# adb shell
# echo 'ro.kernel.qemu=1' > /data/local.prop
# exit
# adb reboot
# adb shell
# mount -o remount,rw /system
# cp /system/build.prop.orig /system/build.prop (cp comes with busybox see link above)
# rm /data/local.prop
# exit
# adb reboot
Your device "should" boot after this.
nvrmore100 said:
I wanted to start an official thread on performing build.prop edits on KFHD since no one has of yet. I have tinkered for several hours yesterday trying to get one that allows Google Play apps to install that show "unsupported device". I have had zero luck unfortunately, and am hoping some others want to take up the challenge and find a solution.
I suggest you get busybox before attempting this, it makes copying files easier. Get it in the GooglePlay store:
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
Make sure you back up your file first!!! I did these steps:
Code:
# adb shell
# su
# mount -o remount,rw /system
# cp /system/build.prop /system/build.prop.orig (cp comes with busybox see link above)
# cp /system/build.prop /sdcard/build.prop.orig
# exit
NOTE: If you didn't install busybox, then you can do the cp commands as below:
Code:
# cat /system/build.prop.orig > /system/build.prop
Word of caution, I have managed to get my Kindle into a boot loop several times through this, but fortunately have been able to recover (details below). I cannot guarantee that you won't damage your Kindle in the process, and prevent it from booting.
I am also attaching a copy of the stock build.prop in case you manage to damage yours. I can't guarantee you will be able to put it back if you get in a boot loop, but you should be able to at minimum "vi" the existing one and manually enter everything to fix you up.
Here are my recovery steps if you manage to get stuck in a boot loop (I notice this happens a lot if you modify the ro.product.board entry). All credit for saving my bacon (and showing us how to root) goes to jcase and sparkym3. One note, you cannot use "su" if you get in this state, you get some exception and the binary errors out about you not being fully booted.
Code:
# adb shell
# echo 'ro.kernel.qemu=1' > /data/local.prop
# exit
# adb reboot
# adb shell
# mount -o remount,rw /system
# cp /system/build.prop.orig /system/build.prop (cp comes with busybox see link above)
# rm /data/local.prop
# exit
# adb reboot
Your device "should" boot after this.
Click to expand...
Click to collapse
Do you means that if we get stuck in the boot loop, we can try the third code to recovery?
It should let you get back to the device if you are in a loop like you would experience with the build.prop edit. Meaning you can still use adb shell to access the system even though its not entirely booted up, and you can't use SU.
No one willing to try more build.prop edits? I spent another few hours at this, I'm still no farther. I am able to trick play.google.com into thinking I have a different system (Nexus S in this case) but the play store on the kindle doesn't allow me to install several apps. If I tell it to download via the web site, it does not push them down to my device. Also, if I try to do a combination of website / play store app at various stages of the process, I can get all the way to install portion and then it tells me its not compatible...
Does anyone ever try to change DPI to 160 or lower?
Sent from my KFHD rooted
Yes, with a lower dpi, the normal android lock screen returns, however, the keyboard gets seventy messed up and becomes unusable. This was at 130 dpi.
Sent from my KFTT using XDA Premium HD app
Has any progress been made on installing incompatible apps from the play store?
Sent from my KFTT using xda app-developers app
madddoggj said:
Has any progress been made on installing incompatible apps from the play store?
Sent from my KFTT using xda app-developers app
Click to expand...
Click to collapse
use market unlocker.its ok.
madddoggj said:
Has any progress been made on installing incompatible apps from the play store?
Sent from my KFTT using xda app-developers app
Click to expand...
Click to collapse
Yes, when Google says no, I go look for the apk and download it anyways. So far nothing has crashed. But I try to stick with things for ICS.
I messed with the ro.product.board entry... and now when reboot it got stuck at "Kindle is Upgrading... Starting application..."
Tried adb but device not attacked.
Is there a way to boot it up again?
dexd, http://forum.xda-developers.com/showthread.php?t=1930656
nvrmore100 said:
Here are my recovery steps if you manage to get stuck in a boot loop (I notice this happens a lot if you modify the ro.product.board entry). All credit for saving my bacon (and showing us how to root) goes to jcase and sparkym3. One note, you cannot use "su" if you get in this state, you get some exception and the binary errors out about you not being fully booted.
Code:
# adb shell
# echo 'ro.kernel.qemu=1' > /data/local.prop
# exit
# adb reboot
# adb shell
# mount -o remount,rw /system
# cp /system/build.prop.orig /system/build.prop (cp comes with busybox see link above)
# rm /data/local.prop
# exit
# adb reboot
Your device "should" boot after this.
Click to expand...
Click to collapse
Worked like a charm on 7.2.1 jcase and sparkym3 are brilliant. I have no idea how this code works or what makes sense about it, but it's fantastic. Also, since this code lets you copy files without root, could this be another method for rooting my device?
Yuretz said:
dexd, http://forum.xda-developers.com/showthread.php?t=1930656
Click to expand...
Click to collapse
I followed the guide and got myself this factory cable and I can boot it up again
My build.prop
Quadrant 2450
No need to block accelerometer in games
Fast worm program start
Suddenly deleted strings about fast restart and unlock, will add tomorrow. Issue's is cold start takes a sec but it doesnt bother
Thank you for your post, this thread may be quite useful for who has had a bricked device.
Yuretz said:
My build.prop
Quadrant 2450
No need to block accelerometer in games
Fast worm program start
Suddenly deleted strings about fast restart and unlock, will add tomorrow. Issue's is cold start takes a sec but it doesnt bother
Click to expand...
Click to collapse
I don't know what the other two things mean, but the "No need to block accelerometer in games" is something I need! Are you sing a Kindle Fire HD 7"? If so, I'm definitely doing this!
macravin said:
I don't know what the other two things mean, but the "No need to block accelerometer in games" is something I need! Are you sing a Kindle Fire HD 7"? If so, I'm definitely doing this!
Click to expand...
Click to collapse
Yes, I'm KFHD 7 user. DPI 160!!! Stock launcher won't be usable.. If U have so, need to change string about dpi to 260, if i'm not mistaken.
On ADW Launcher or any other sideloaded everything work like a charm.. APPS switch to TABLET mode if support
Yuretz said:
Yes, I'm KFHD 7 user. DPI 160!!! Stock launcher won't be usable.. If U have so, need to change string about dpi to 260, if i'm not mistaken.
On ADW Launcher or any other sideloaded everything work like a charm.. APPS switch to TABLET mode if support
Click to expand...
Click to collapse
So you can download apps from marked which are marked as "incompatible device" with stock build.prop ? Thank you for your answer! :fingers-crossed:
Yuretz said:
Yes, I'm KFHD 7 user. DPI 160!!! Stock launcher won't be usable.. If U have so, need to change string about dpi to 260, if i'm not mistaken.
On ADW Launcher or any other sideloaded everything work like a charm.. APPS switch to TABLET mode if support
Click to expand...
Click to collapse
I did this, but the dpi made my keyboard unuseable (the keyboard doesn't fit on screen idk why it became big when everything else became small)... does anyone know of a fix for this? That would be really great!
Does this work on Kindle Fire HD 8.9?
Yuretz said:
My build.prop
Quadrant 2450
No need to block accelerometer in games
Fast worm program start
Suddenly deleted strings about fast restart and unlock, will add tomorrow. Issue's is cold start takes a sec but it doesnt bother
Click to expand...
Click to collapse
Ok I am very excited.I saw this possible solution to my problem, as I would like to download NBA Jam for android (that I modded with Jordan in it that I have working on my rooted Kindle Fire with CM10 linaro on it, but what I wonder is if this will work for a rooted Kindle Fire HD 8.9 as well as a Kindle Fire HD 7? Thank you in advance.
I'm trying to edit the build.prop file on the G2 803 model. It's rooted and unlocked on a stock Bell Rom. The phone has the wi-fi forgetting problem. everytime I reboot it I have to reset the wifi password. I've tried editing the build.prop file to change the wifi.lge.patch line to=false but I can't seem to enter more than 4 characters after the = on that line. Am I missing something?
Use build prop editor free on playstore
_____________________________________Read more write less and be smart
siggey said:
Use build prop editor free on playstore
_____________________________________Read more write less and be smart
Click to expand...
Click to collapse
Thanks, I tried that but the changes don't appear to stick.
Fraggle_Shamy said:
Thanks, I tried that but the changes don't appear to stick.
Click to expand...
Click to collapse
Reason 1: Some build.prop values get their values from the ramdisk on each boot, so that's why some values wont stick.
Reason 2 (requires root): build.prop is located in /system. Your /system may be read-only, we want it to be read-write to make changes, so.. run the following command in a Terminal Emulator downloaded from the play store. Run the following commands,
Code:
su
mount -o rw,remount /system
Now make your build.prop changes. Once finished run the following command to get your system back to how it was,
Code:
mount -o ro,remount /system
If the app isnt helping you, download a file explorer such as ES and navigate to /system/build.prop, open the file and edit the values you want.
Note: It's nice to hit the "Thanks" button under our posts if you indeed are thankful. Saying thanks and not hitting the thanks button is a slap in the face .
Thanks for the suggestion, but the emulator didn't help. I'm guessing it's because it's locked to the boot rom (your first suggestion)? Any way around this? I have anohter 803 that doesn't have this issue. Can I copy the ROM from that phone to the problematic one?
Fraggle_Shamy said:
Thanks for the suggestion, but the emulator didn't help. I'm guessing it's because it's locked to the boot rom (your first suggestion)? Any way around this? I have anohter 803 that doesn't have this issue. Can I copy the ROM from that phone to the problematic one?
Click to expand...
Click to collapse
Try this. (Pretty much the same as a previous suggestion, doubt it will work)
Get a root capable browser. Jrummy has one that's free, I think it's called Root Browser.
Browse to /system there should be a button to mount it r/w, if not it may prompt you when you go to edit the file... Long click the file, and try to open for editing. (it may be some other combination, I don't have my phone handy right now). Make the a change or two, reboot and see if they stick.
Or the other thing you cna do is:
The other thing you can try is to do is check if they're being set on boot.
adb pull /*.rc
which will pull all of the ramdisk's initialization scripts into your current folder on your computer. Look through them and see if the values are indeed being set by the boot image. If they are, you'll need something like AIK (android image kitchen) to extract the ramdisk, either change or delete those lines, rebuild the boot.img and flash it (using flashify or manually using adb and dd). You have to rebuild them into the boot.img, any changes you make to them directly on the phone will never stay as they get re-created every boot. It's a pretty roundabout way to do it, but it's entirely possible to do.
A much easier, and less likely to cause you issues would simply be to create an init.d script that sets it. This will occur after whatever is setting it in your boot.img so there would be no need to recreate that.
create a file in /etc/init.d called something like... "Set_wifi_pass" set the permissions so that it can be executed and read by everyone.
Then enter the following:
Code:
[B][I]#!/system/bin/sh[/I][/B]
setprop wifi.lge.patch = WifiPassword
You can check that it worked by going through adb shell with
adb shell
getprop wifi.lge.patch
which should return that value you set. Same thing that build.prop is ultimately doing, just in a different way.
Hope that helps.
HI , im new here but i know a long time ago about this community, anyway, someone can help me uploading a build.prop of the moto g5 plus, i modify it and well... :/ i try to fix it whit a adb on the command promp but my phone still stuck on the boot, and i sorry about this topic maybe can help on the future
Which model do you have? What build are you on? Are you running a custom ROM?
It would probably be easier to post your build.prop and see if someone will look at it and give you some advice as to what is wrong.
willclein said:
Which model do you have? What build are you on? Are you running a custom ROM?
It would probably be easier to post your build.prop and see if someone will look at it and give you some advice as to what is wrong.
Click to expand...
Click to collapse
Thanks in advance for the reply, i can solve the problem flashing the firmware beacuse i have some troubles on the console using adb, but this happening beacuse i dont give it the correctly permisons, but i want share the way to fix that problem as well, therefore i bring the solution on the command prompt on windows, the solution is very simply but helpfull
step by step, there are been taked on the siteweb TAS beacuse i'm a new user and i cant post url's of the other sites
///
Setup ADB and Fastboot on your PC.
Boot your Android device into TWRP recovery.
Select Mount » and then select System from the list of partitions to mount the system partition and then go back.
Connect your device to the PC with an authentic USB cable.
Open a command window on the PC and issue the following command to pull build.prop file from the device:
adb pull /system/build.prop
The above command will download the build.prop file to your PC in the same directory where your command prompt is running from.
└ Tip: Make a copy of the build.prop file before you edit it so that you’ve a backup of the original file.
Download and install Notepad++ software on your PC.
Open the build.prop file on your PC using the Notepad++ program.
Edit the build.prop file as per your requirement and save it on the PC after making the changes.
Once you’ve saved the edits to the build.prop file, push it back to the device using the following command:
adb push build.prop /system/
Now set the correct permissions for the build.prop file with following commands (issue them one-by-one):
adb shell
cd system
chmod 644 build.prop
Once you’ve set the correct permission for build.prop file, reboot your device to system from TWRP’s Reboot » System option.
thanks and i hope this can help someone else
The number one issue I see with people modifying build.prop (myself included) is forgetting to fix the permissions once you are done. My preferred method for editing it is using BuildProp Editor. It makes editing easy as well as makes setting the permissions extremely easy without having to use ADB. Best part is you can do this on the fly instead of having to use your PC.