I want to edit thermal file to get better results in benchmarks but I dont find the correct file. (I'm rooted)
Related
I have the stock rom for the Galaxy S6 Cricket variant... I am having trouble in getting the build.prop from the system.img. I have tired many methods from other threads but none seem to work. Any suggestions or working ways to extract the build.prop from the system.img or any way to open up the .img file.
I am doing this to post the rom in the ROM WIP section for the root.
gmx1994 said:
I have the stock rom for the Galaxy S6 Cricket variant... I am having trouble in getting the build.prop from the system.img. I have tired many methods from other threads but none seem to work. Any suggestions or working ways to extract the build.prop from the system.img or any way to open up the .img file.
I am doing this to post the rom in the ROM WIP section for the root.
Click to expand...
Click to collapse
Try the tools in this thread . I used them last week to extract a build prop.
Just load up the system.IMG and drag the file from the system folder to your desktop.
gmx1994 said:
I have the stock rom for the Galaxy S6 Cricket variant... I am having trouble in getting the build.prop from the system.img. I have tired many methods from other threads but none seem to work. Any suggestions or working ways to extract the build.prop from the system.img or any way to open up the .img file.
I am doing this to post the rom in the ROM WIP section for the root.
Click to expand...
Click to collapse
The tar file for Cricket has already been posted in the general section of ATT
Sent from my SAMSUNG-SM-G920AZ
daniel4653 said:
The tar file for Cricket has already been posted in the general section of ATT
Sent from my SAMSUNG-SM-G920AZ
Click to expand...
Click to collapse
I already downloaded that file.... I just need to extract the build.prop from the system.img which I already have. The thing is I am having trouble getting the build.prop
Sent from my SAMSUNG-SM-G920AZ
gmx1994 said:
I have the stock rom for the Galaxy S6 Cricket variant... I am having trouble in getting the build.prop from the system.img. I have tired many methods from other threads but none seem to work. Any suggestions or working ways to extract the build.prop from the system.img or any way to open up the .img file.
I am doing this to post the rom in the ROM WIP section for the root.
Click to expand...
Click to collapse
I got your PM. Sorry for the late reply. I'm posting here in case someone else needs the info.
Download Ext2explore.
Extract to your PC.
Run as administrator.
In app: go to file - open image - (find your system image) and open
It will display your image in tree and folder view
Use either one (depending on your preference) (but your build.prop will be in the first view as its in the root of the system).
Right click the file/s you want to extract
Select save
Save your file.......profit
Hope this helps
tiboric said:
I got your PM. Sorry for the late reply. I'm posting here in case someone else needs the info.
Download Ext2explore.
Extract to your PC.
Run as administrator.
In app: go to file - open image - (find your system image) and open
It will display your image in tree and folder view
Use either one (depending on your preference) (but your build.prop will be in the first view as its in the root of the system).
Right click the file/s you want to extract
Select save
Save your file.......profit
Hope this helps
Click to expand...
Click to collapse
When I try to open the file the program just closes and i go to the log and this is what it says.
Error Opening \\.\PhysicalDrive1. Error Code 2
No of disks 1
Scanning \\.\PhysicalDrive0
index 0 ID 7 size 976769024
Partition Table Error on C:/Users/giovany/Desktop/New folder (2)/system.img
Invalid End of sector markerBad Super Block. The drive is not ext2 formatted.
Drive is not right formatted.
solution for img extraction/fix here
Hi guys, i have a question...
Is possible create a custom rom (remove vendor apps) from XXXXXXXX.tar.md5 file downloaded from sammobile and make your own tar.md5 flasheable Odin file?
For example:
Original firmware:
XXXXXX.tar.md5
1.5 Gb
Removing vendor apps:
XXXXXX_my_firm.tar.md5
800 mb
I am interested in doing this without custom recovery, not zip flashable file, and not root.
xTxMIGUELxTx said:
Hi guys, i have a question...
Is possible create a custom rom (remove vendor apps) from XXXXXXXX.tar.md5 file downloaded from sammobile and make your own tar.md5 flasheable Odin file?
For example:
Original firmware:
XXXXXX.tar.md5
1.5 Gb
Removing vendor apps:
XXXXXX_my_firm.tar.md5
800 mb
I am interested in doing this without custom recovery, not zip flashable file, and not root.
Click to expand...
Click to collapse
Yes, you can do this, but things have changed a bit since this guide was written, you'll have to do some research to see what things have changed in this process from kit kat up to the current available android version. There have been some stock security changes that this guide doesn't cover and won't work with these new securities, but you should be able to figure out how to make this work with those securities if you learn to look in the right places.
https://www.rwilco12.com/forum/showthread.php?tid=92
This will help you create the .tar, you'll just have to figure out how to make the changes you want to make. You'll mostly be working with your system.img once you get it extracted.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Hello Guys,
I have the european Version of the Honor 6x. After flashing a custom rom I wanted to come back to Stock Emui. But now I have a few problems with my Honor device. In the settings it isn't called Honor 6x any more, but generic-a15.
A huge part of the build.prop got lost so many things like f.e. the camera or the loudspeekers do not work any more.
Could someone maybe share the stock build.prop with me, so that I can solve at least one of the problems?
Thanks
In this case, the build.prop won't be helpful. You gotta flash the version.img of your actual firmware through fastboot or TWRP.
You can extract the version.img file with Huawei Update Extractor tool. You have to pull it out from the biggest update package that weights something like 1,49GB, usually "update.zip".
RedSkull23 said:
In this case, the build.prop won't be helpful. You gotta flash the version.img of your actual firmware through fastboot or TWRP.
You can extract the version.img file with Huawei Update Extractor tool. You have to pull it out from the biggest update package that weights something like 1,49GB, usually "update.zip".
Click to expand...
Click to collapse
Yeah the thing is, huawei wont publish the firmware online anymore, if you try to find the img in the net you cannot find it at all
Huawei did that, true, but luckily there is another site on which all the update packages are uploaded. Just look for yours here http://pro-teammt.ru/firmware-database/ you only have to write your build number and grab the file.
I messed up my build.prop with some "tweaks" (Thanks Zack. They don't work at all.). so could somebody else provide an original build.prop for BLN-L21? Thanks in advance.
Hi there,
Does anyone have a stock build.prop file from Android N (or O) that they can upload for me? I'm trying to pass SafetyNet on a custom ROM and I believe I need one, and I can't seem to extract it from the stock ROM that I have downloaded. Thanks.
Mouse acceleration comes from libinputreader.so being hard coded to having a pointer acceleration of 3 with no way to change it. In order to change it on a rooted device you need to edit your libinputreader.so file and make a magisk module out of it.
On my LE2115 running LOS 19.1 this file can be found in /system/lib64/libinputreader.so.
Based on your luck one of the three methods should work for you:
1. Just straight up use the magisk module I made. This will ONLY work if your AOSP build is similiar enough to mine, if not it may very well send you into a bootloop. (I will upload this file later when I finish this within the week.)
2. Get a hex editor and search for the following bytes in your own libinputreader.so file - (will finish later adding bytes to search for). put the modified file in a magisk module and flash it to your phone, follow this guide here: https://topjohnwu.github.io/Magisk/guides.html
3. If all else fails you could do what I did originally to find this information- build the AOSP yourself from a linux desktop, edit the input.aidl file that holds the pointer acceleration value, one with no acceleration, another with acceleration, and view the differences between the 2 files spat out in a hex editor. change the corresponding values in your own libinputreader.so to disable mouse acceleration.