Android 10 can not modify build props?
i try build.prop edit ( product model change pixel 3 but failed to fix
Do you have any success?
Related
I thought it was very easy porting rom, with a kitchen tool. Just choose 0 and 19, and follow what is. and finally select 99. finished.
however, until I tried it myself .
Bug, bug, bug, and bug. oh my Good.
I 'll tell you a little about my experience porting rom. maybe you have the same problem with me.
Here, I tried porting rom from Samsung Galaxy Ace Duos (S6802) to Samsung galaxy y duos (S6102).
Description :
1 . [ Base ] Rom S6102 (240 x 320 pixels , 127 ppi pixel density)
2 . [ Port ] Rom S6802 (320 x 480 pixels , 165 ppi pixel density)
Then I tried to do it with Kitchen Tool .
Kitchen Tool : http://forum.xda-developers.com/showthread.php?t=633246
Guide: https://docs.google.com/file/d/0Bwidle8N7kRRMEhXeEZsTzlRNVU/edit?usp=sharing
And after I finished, so I tried to flash "GT-S6102_signed.zip" with CWM, then what happens :
1 . Error sdcard open GT-S6102_signed.zip (status 0).
- Open the "META-INF\com\google\android\"
- I replace the "update-binary" from those in [base] rom.
- Try again .
2 . Error sdcard open GT-S6102_signed.zip (status 6).
- Open the "META-INF\com\google\android\"
- Check updater-script, open with notepad++.
- Usually in this line :
mount ("rfs" , "EMMC", "/dev/block/stl19", "/system") ;
replace the line, with the line of the script is in [ base ] rom .
3 . Error with pixel density.
- Open build.prop with notepad++.
- At this line : ro.sf.lcd_density=xxx, replace xxx with the pixel size in [base] rom.
4 . Error camera can not be used .
- I tried to replace all the files in the folder "cameradata/"
- And in the folder "lib/" : libarccamera.so, libcamera.so, libcamera_client.so, libcameraservice.so. with a file that is in the [base] rom.
5 . Error sdcard not detected, or force close "process android.process.media stopped"
- I tried to edit "vold.fstab" in the folder "etc/"
6 . Error, can not change wallpaper, or Force Close TwWallpaperchooser.apk.
- I tried to replace the file "Vold" in the folder "bin/".
7 . Error if charge phone .
- I tried to replace all existing files in the folder "media/", with the files in the [base] rom .
- Also change the file "charging_mode" in the folder "bin/" .
8. Error, Logcat. Unable to open log device "/dev/log/main".
- Check all file in the folder "etc/init.d/", open with notepad++
- Remove this line : "rm /dev/log/main"
That bit of my experience, about porting rom with Kitchen Tool.
Maybe you have other experience, and have to overcome .Please share here.
Sorry if I'm wrong, and soory for my English.
Please don't forget to use LOGCAT to debug the rom..... And Press "Thanks" if I help you.
very helpful.....Cool
Hello. I want to change the language of software oupeng 10 android to English . But when I edit and sign it with signapk but this software will not open and crash. I think this soft have sign detection system is invalid. How can this go around and edite this. Try it and see you can edit it to change its language from Chinese to English?
download linke of oupeng 10 android : http :// dl.oupeng. com/next/w/oupeng 10.0.1.82018 .apk
I am waiting for a response you.
tnx
saber-partizan
Hahaha... manam khastam oupeng 10 & 11 ro edit konam, ke ba hamin. moshkel movajeh shodam
Hello there , i've an unloked Honor 10 with last 8.1 EMUI and rooted... I try play with dalvik.vm.heapsize=512m value located in build.prop. With 1024m i've a infinite bootloop...What's the maxium valid value without a bootloop ?
Hello,
I want to use LG G3 Lineage OS 17.1 and download Wild Rift from Google Play, my phone is incompatible with Google Play, I have build.prop with "ro.product.model = SM-G610F", "ro.product.brand = samsung" and changed it to "ro.product.manufacturer = Samsung" and it succeeded, in the settings it says Model: SM-G610F No correspondence on Google Play but unfortunately. I tried changing the Magisk MagiskHide Props Configuration but again the result is the same. What's the solution?
[SOLUTION] Solution Find and select the fingerprint of the model you changed in Magisk Hide Props Config (option 1) and restart it.
[SOLUTION] Solution Find and select the fingerprint of the model you changed in Magisk Hide Props Config (option 1) and restart it.
[SOLUTION] Solution Find and select the fingerprint of the model you changed in Magisk Hide Props Config (option 1) and restart it.
I have a somewhat strange problem and trying to describe it.
Currently I am on stock ROM 9.1.0.132
I am using Outlook and O365. When I log in to O365 account, the webview sends the useragent:
Browser: Mozilla/5.0 (Linux; Android 12; ANE-LX1 Build/HUAWEIANE-L21; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/107.0.5304.105 Mobile Safari/537.36 PKeyAuth/1.0
If Android "9" or if HUAWEI is in the text of the useragent my company blocks the access.
Some time ago I was using an EMUI ROM greater than 9.1.0.132 and I was able to change the text entry "HUAWEIANE-L21" in one of the build.props
Android "9" I was able to change to "12" (ro.build.version.release=12).
In Stock ROM 9.1.0.132, unfortunately I can't find "HUAWEIANE-L21" in the biuld.props anymore and I don't remember how I changed it back then.
Can someone please look in the build.props in /system and /vendor at Stock ROM > 9.1.0.132
Or does anyone have a tip, where the webview takes the useragent information from.
I'm on Magisk root and i dont want to update > 9.1.0.132
I found the solution in Magisk Module MagiskHideProps. If this module installed, the default /system/build.props will ignored.
Set "ro.build.id" by MagiskHideProps command in terminal -> "props ro.build.id Samsung" (Usage: props NAME VALUE)
https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/README.md
This will change the default "ro.build.id=HUAWEIANE-L21" to ""ro.build.id=Samsung"
Can check by "getprop | grep ro.build.id
UserAgent is changed now.