Related
I'm not responsible to any damage which is caused by applying any modification listed below to your phone.
Backup
If you made mistake to this file, you phone will not boot in gui, so you should always backup the file before you make any change to it. Just use any file manager to copy the file to your sd card or your pc.
Restore
If you have a Linux machine you can mount the /system partition while plugging in with the purple screen (vol up + vol down + power).
Easiest way: get Ubuntu, put your phone in purple screen, plug in with USB, you will see the system partition at your Ubuntu desktop.
The hard way: if the /system partition is no accessible under purple screen mode (such as in the latest 528 rom), you can use adb push the backup file back, search the web for details about how to use adb.
I'm digging the build.prop, some apps can do some of these tweaks for you, but I prefer typing myself. You need to reboot the phone to take effect.
1. windowsmgr.max_events_per_sec=75
add this new line to make UI more responsive, the bigger the value the more responsive, I've tried 90, too fast, fall back to 75, still quite fast
2. ro.config.hw_menu_unlockscreen=false
change value from "false" to "true" to enable menu key unlocking screen
3. ro.sf.lcd_density=240
change to 225 to increase the resolution of display, as a result, the size of icon on home page and fonts of list (of file manager or contact) become smaller, the smaller the value the smaller size of icon and fonts
4. dalvik.vm.heapsize=24m
increase the value to 32m~48m to increase stability and performance, tested but doesn't see much effect so far
all so if you tried games like nova or brother in arms that have black screen or graphic probs do this they now all work
go to /system/build.prop and edit it to this then close and turn the phone off / on do a build.prop DO A BUILD.PROP BACKUP FIRST ALLWAYS A MUST BEFOR PLAYING AROUND.
once the phone is on go to settings about phone model number and it will say Desire HD.
Then download games for the htc desire hd and it works.
if you want it back to standed just replace it with the backup
i think the suggestions are great!
big thx!!!
thanks for the share
Do I just change the name, where it says build.prop now?
sorry there are still some games that wont work like brother in arms 2 and modern combat black pegasus but all the others work like
splinter cell
sandstorm
n.o.v.a.
and so on
your phone hast to be rooted and use root explorer and go to
/system/build.prop and open and edit the text then reboot your phone
backed up the build.prop and made the changes. On restart it hangs on boot screen (huawei name and logo) I have to remove the battery to switch off. tried connecting to the PC to restore build.prop but it doesnt load the phone memory. Only launches the mobile partner autostart. Also tried updating by adding update.zip to sd card but says signature verification failed. Tried lading general update from huaweidevice.com onto dload directory on sd card, Just shows purple screen on booting with power, vol up and down. Please advice.
adrdsouza said:
backed up the build.prop and made the changes. On restart it hangs on boot screen (huawei name and logo) I have to remove the battery to switch off. tried connecting to the PC to restore build.prop but it doesnt load the phone memory. Only launches the mobile partner autostart. Also tried updating by adding update.zip to sd card but says signature verification failed. Tried lading general update from huaweidevice.com onto dload directory on sd card, Just shows purple screen on booting with power, vol up and down. Please advice.
Click to expand...
Click to collapse
If you have a Linux machine you can mount the /system partition while plugging in with the purple screen (vol up + vol down + power).
Easiest way: get Ubuntu, put your phone in purple screen, plug in with USB, you will see the system partition at your Ubuntu desktop.
Thank you..a mate uses linux so went over and it worked like a charm. I hadn't put the 'm' at the end in 'dalvik.vm.heapsize=24m' but it is sorted now. Thanks again.
Hi there.Is there any value in build.prop file to decrease the time that the screen rotates?I measure that the default time is about 1sec.I want it 500ms or lower.
ive root and root explorer, but when i try to edit the build.prob it says that its read only rom .
whats the problem?
sry for my bad english
In the top right hand corner there is a button which says 'mount r/w' press it and your filesystem will be read/write. Then make the changes to build.prop then press the button again then reboot.
volume headphones?
Where can I find the file corresponding to the volume of the sound through headphones? A similar problem occurred on the ZTE, but was repaired in the new ROM.
Piron said:
Where can I find the file corresponding to the volume of the sound through headphones? A similar problem occurred on the ZTE, but was repaired in the new ROM.
Click to expand...
Click to collapse
/system/etc/hwVolumeFactor.cfg
iamelton said:
/system/etc/hwVolumeFactor.cfg
Click to expand...
Click to collapse
I found the compination of speaker=80 and wired_headset=80 pretty cool.Has anyone found a better setting?
headphone volume
80 is too much. For me the best settings are:
- speaker 75 (default)
- Headphones 70 (higher values will cause the overload of sound)
With this setup is really cool .
Swype
The original ROM is installed Swype keyboard, but not in the Polish language. It is not possible to uninstall Swype and you can not install a new keyboard. Despite the ROOT system does not allow the removal of the keyboard ("cust/hw/ideos_x5/app / "). Does anyone know how to remove the keyboard, or where to replace your dictionary?
adrdsouza said:
Thank you..a mate uses linux so went over and it worked like a charm. I hadn't put the 'm' at the end in 'dalvik.vm.heapsize=24m' but it is sorted now. Thanks again.
Click to expand...
Click to collapse
unfortunately I've got the same problem with you, I changed a file's name in the system/ directory now the phone bricks. I mounted it on mu ubuntu laptop and found that file but it says I have no permission to change it back...what should do now?
edit: never mind, I got it solved with sudo. I am a stupid linux noobie.
I just opened the file, but there's no "windowsmgr.max_events_per_sec" in it, i found the rest (2-4), does someone know why?
Edit: after applying the B160 ROM, i found this line, works great
So the US-version of the Mediapad M3 does not support 5GHz Wifi as stated by Huawei and from my personal experience. Per Huawei's website:
Wi-Fi: IEEE 802.11a/b/g/n/ac at 2.4 GHz & 5 GHz (Products delivered to markets that impose FCC certification requirements do not support 802.11 a/ac at 5 GHz Wi-Fi)
I can't help but think that the hardware is there as I have never heard of a mobile WiFi chip that ONLY supports 802.11 ac at 2.4 GHz. Therefore, is or will there be any way to unlock the 5 GHz band of the WiFi chip assuming the hardware is there?
Well, if you have unlocked bootloader, you may try the following:
1) Get root access.
2) Open /system/build.prop and find ro.config.hw_is_hide_wifi_5g=true and change it to "false". Or to true if it's false.
3) If that doesn't work (cause I really don't know what this option stands for), see below.
4) Go into /cust folder and tell us what's in there. Maybe, there's something like "hw" folder with "eu" folder inside.
5) If there is, edit /data/custom.bin and put "hw/eu" there (without quotemarks), and see, if something has changed.
If you don't have "hw/eu" in /cust, you have two ways:
1) Ask me here to give you "hw/eu" folder, put it into /cust and do (3).
2) Find local.prop file (it's usually in "prop" folder, three folders down from /cust, but folders are those you have, not "hw/eu")
3) There you'll find ro.config.hw_opta and ro.config.hw_optb. Change them to 999 and 156 respectively.
If all that doesn't help, we'll need to find another ways.
Slavon-93 said:
Well, if you have unlocked bootloader, you may try the following:
1) Get root access.
2) Open /system/build.prop and find ro.config.hw_is_hide_wifi_5g=true and change it to "false". Or to true if it's false.
3) If that doesn't work (cause I really don't know what this option stands for), see below.
4) Go into /cust folder and tell us what's in there. Maybe, there's something like "hw" folder with "eu" folder inside.
5) If there is, edit /data/custom.bin and put "hw/eu" there (without quotemarks), and see, if something has changed.
If you don't have "hw/eu" in /cust, you have two ways:
1) Ask me here to give you "hw/eu" folder, put it into /cust and do (3).
2) Find local.prop file (it's usually in "prop" folder, three folders down from /cust, but folders are those you have, not "hw/eu")
3) There you'll find ro.config.hw_opta and ro.config.hw_optb. Change them to 999 and 156 respectively.
If all that doesn't help, we'll need to find another ways.
Click to expand...
Click to collapse
Has anyone been able to try this yet?
the7thson said:
Has anyone been able to try this yet?
Click to expand...
Click to collapse
C'mon, be the first one
Just another caution.
Please, do a backup first.
I had a factory reset after changing region in custom.bin. I don't know, what was the real cause, and now I don't do anything to my tablet, cause everything it setup and works fine.
You, probably, can avoid it in two cases:
1) Your original recovery was replaced by TWRP
2) You don't change the actual region, changing only the content of your region's folder.
the7thson said:
Has anyone been able to try this yet?
Click to expand...
Click to collapse
Changing ro.config.hw_is_hide_wifi_5g=true to "false" didn't do anything for me.
/cust folder contains /hw (subfolders /default, /normal, /oversea, and /usa), /lost+found, /preinstalled, and /special_cust. I haven't messed with any of them.
didn't work.
After unlocking the bootloader and getting root access I did the following:
1. Changed /system/build.prop: ro.config.hw_is_hide_wifi_5g=true to "false".
restarted the tablet but it did nothing
2. went to /cust. it contains the following folders: /hw (subfolders /default, /normal, /oversea, and /usa), /lost+found, /preinstalled, and /special_cust (just like for @neo_1221)
edited local.prop under /Cust/hw/usa/prop/ to ro.config.hw_opta=999 (was 567) and ro.config.hw_optb=156 (was 840).
restarted the tablet but it did nothing
What else can be done?
E.Vogel said:
What else can be done?
Click to expand...
Click to collapse
You may try to flash Chinese firmware. It's Something like BTV-W09C233B0xx or BTV-DL09C233B0xx
I don't have any other ideas, really. If even this doesn't help, then 5GHz is locked by OEMInfo or disabled in hardware.
Firmware can be found with this tool
Am confused by this thread. Are you saying you can only connect to 2.4 networks and cannot see 5ghz networks at all?? That normal only happens when a tablet physically does have a 5ghz radio.
The U.S version of the tablet does not support 5Ghz wi-fi.
We are assuming that there is only one variant of the tablet sold world wide (two actually LTE+wifi and wifi only),
and in order to comply with FCC requirements the 5Ghz wi-fi band was disabled by software and not hardware.
If that is the case than the band can be enabled back by flashing different non-U.S rom.
hopefully
It is WORKING!
I downloaded the latest Chinese version using the tool @Slavon-93 linked, version BTV-W09C233B022 from December 16 2016. I flashed it and after restarting the tablet, I have a Chinese version tablet, with 5Ghz band wi-fi working.
I lost custom recovery and root and may reflash them later.
I got some apps back that I previously removed, but happily all my other apps were still installed and configured.
Thanks @Slavon-93
p.s. I re-flashed TWRP and SU and now have custom recovery and root back
E.Vogel said:
I downloaded the latest Chinese version using the tool @Slavon-93 linked, version BTV-W09C233B022 from December 16 2016. I flashed it and after restarting the tablet, I have a Chinese version tablet, with 5Ghz band wi-fi working.
I lost custom recovery and root and may reflash them later.
I got some apps back that I previously removed, but happily all my other apps were still installed and configured.
Thanks @Slavon-93
p.s. I re-flashed TWRP and SU and now have custom recovery and root back
Click to expand...
Click to collapse
Can you select english as the language?
Yes you can, and since English was my selected language before I flashed the Chinese ROM it stayed as the selected language, so I never got a Chinese welcome screen and had to find out how to change it to English.
So this is a solution to get the "5Ghz band" working on a US WiFi only?
Those, who have a US tablet, could you please upload your entire /cust folder somewhere? If Chinese firmware is a solution, maybe there is something in /cust, that blocks 5GHz wifi? I wanna compare it to Chinese and Russian versions and maybe find something interesting.
@E.Vogel forgive me for being new to Huawei way of doing things. You said you flashed the Chinese ROM. Flashing makes me think of my Nexus 7 where I actually flashed the *.IMG files.
I downloaded the file you mentioned and I have update.app after extraction. I recall reading somewhere about creating a folder and transferring said file to device and restarting it. I'm curious if this is the route you took? I personally prefer fastboot flash but will have to do with what works. Thank you.
jmjm003 said:
@E.Vogel forgive me for being new to Huawei way of doing things. You said you flashed the Chinese ROM. Flashing makes me think of my Nexus 7 where I actually flashed the *.IMG files.
I downloaded the file you mentioned and I have update.app after extraction. I recall reading somewhere about creating a folder and transferring said file to device and restarting it. I'm curious if this is the route you took? I personally prefer fastboot flash but will have to do with what works. Thank you.
Click to expand...
Click to collapse
Forgive me for not being @E.Vogel, but let me explain. Huawei devices are not usual in terms of partition structure. For example, they have 2 recoveries, designed for different things. For a Nexus owner their update structure is also strange. Once upon a time, you could create a "dload" folder in /sdcard or in external SD, choose local update in update utility on your device, select update.app or update.zip, reboot and watch the device updating. Now we don't have an option to choose a local update, so the quickest way to install FULL OTA is from TWRP. You just need to put update.zip (~1.8 Gb) somewhere in /sdcard or other place, reboot into TWRP, press the Install button and select this file. TWRP installs it and you get your Chinese firmware. I recommend to make a backup first, in case something goes wrong. After installing FULL OTA you still get your apps and settings in place, but after a factory reset, you will lose Google Play and other a Google apps, and will have to manually install them from HiApp. Also, you will have to reinstall TWRP, root, xposed and other things you probably have flashed before.
I appreciate the reply all the same @Slavon-93. So creating the dload folder and dropping update.app in it no longer works?
I've not modified anything on my device other than fixing DPI so apps are in tablet mode.
Any idea what each recovery does since it has two of them?
I like to know there's a way out of a screwup if it happens. Nexus 7 was simple to fix.
Thank you.
jmjm003 said:
I appreciate the reply all the same @Slavon-93. So creating the dload folder and dropping update.app in it no longer works?
I've not modified anything on my device other than fixing DPI so apps are in tablet mode.
Any idea what each recovery does since it has two of them?
I like to know there's a way out of a screwup if it happens. Nexus 7 was simple to fix.
Thank you.
Click to expand...
Click to collapse
Huawei devices have two recovery partitions: recovery and recovery2.
Recovery has generally all the same features a typical Nexus recovery has, except it doesn't have an option to apply update.zip and has a touch interface unlike the Nexus recovery.
Recovery2, called eRecovery, also has a touch interface and is designed to make a totally screwed up device great work again. It has a button to download full firmware and install it but on my device it said "No firmware found" after connecting to Huawei servers. People in Russian forum say it works only if you're in China and have a Chinese device. Anyway, if eRecovery does nothing, I considered it totally useless and replaced with TWRP: fastboot flash recovery2 twrp.img
Generally Huawei devices can be restored the same way a Nexus device can. TWRP and fastboot work the same. Personally I prefer to make a total backup of all partitions in device with "dd". I think it will give me more flexibility in restoring if something goes completely wrong. On DL09 model, only modem partitions are the problem. You can find fastboot versions of Chinese ROMS easily, but after installing them, I've lost everything related to phone functions. The only way to fix it was installing Full Chinese firmware in form of update.zip with TWRP.
And about dload folder. I have no idea how it works. I am also a former owner of Nexus 7 and the logic of Huawei is new to me, so I don't know some nuances. On earlier devices there was another option to update: you put update.app to dload folder, dial *#*#2846579#*#*, select Software upgrade -> SDCard Upgrade, the device reboots and installs the update. Again, on my device this trick didn't work and update installation stopped at 5%, saying it's incompatible with my device.
@jmjm003, I also come from a nexus 7 and Huawei devices are different.
First of all there is no formal web site with all factory images and/or OTA to download, I had to use a tool an XDA user developed to find the factory image I needed.
The second change is that the factory image (file update.zip) does not contain *.img files inside like in Google images and contains "update.app" 1.8GB file and some other small files.
To flash the ROM I tried to use ADB sideload but got an error message about the file being unreadable, so I copied the file to the tablet and flashed it using TWRP install function like any other zip file.
@Slavon-93, my /cust/hw folder changed from before and now contains only two sub-folders "cn" and "default"
I uploaded the entire /cust folder to Google drive, use this link to download it.
E.Vogel said:
@Slavon-93, my /cust/hw folder changed from before and now contains only two sub-folders "cn" and "default"
I uploaded the entire /cust folder to Google drive, use this link to download it.
Click to expand...
Click to collapse
Thank you but I know what's inside Chinese /cust folder as I am using Chinese firmware myself. I am interested in untouched /cust of US version of tablet because I think there can be some option in local.prop or somewhere else, that blocks 5GHz Wi-Fi. I can try to look for it by comparing Russian, Chinese and US cust folders.
I have rooted my BTV-W09 model. When I use 'adb shell wm density 320' from my computer terminal, the dpi setting is adjusted correctly, but it doesn't survive a reboot.
I tried to change the dpi setting with a build.prop editor directly on the tablet and with the Textdroider DPI app, but it doesn't work, it goes back to whatever DPI settings was implied by the display settings (from Small-400dpi to Large-480dpi).
Is there a way to permanently change the DPI setting to 320, or at least a way to do it directly from the tablet (without a computer)?
Why you not reading neighbor topics? Install Xposed, install App Settings module from here for example, activate it and setup whatever DPI you wish.
Thanks Slavon, but I'm speaking of a system-wide change, not just app by app. English is not my first language, sorry if it wasn't clear.
Sorry if I was a bit rude. Try "Pimp my rom" utility. Find it on Google Play. I worked for me and now I'm thinking of how to revert
Edit: if I got it right, this utility adds (modifies?) this key in build.prop: ro.sf.lcd_density
Not at all, I understand how it seemed like I was asking a duplicate question without looking in others threads, sorry again
And thanks a lot for the advice, I'll try Pimp my rom right away !
wlausrsker said:
Not at all, I understand how it seemed like I was asking a duplicate question without looking in others threads, sorry again
And thanks a lot for the advice, I'll try Pimp my rom right away !
Click to expand...
Click to collapse
If you just need to change density, you'd better try changing the value in build.prop first. And in case of any problems after, change the value of the key I wrote previously or restore the original build.prop from backup. Good luck.
Slavon-93 said:
If you just need to change density, you'd better try changing the value in build.prop first. And in case of any problems after, change the value of the key I wrote previously or restore the original build.prop from backup. Good luck.
Click to expand...
Click to collapse
I've tried this morning to change ro.sf.lcd_density to 320 in the build.prop and reboot. After reboot, ro.sf.lcd_density is still set to 320 but the display is still at 400dpi.
It's like ro.sf.lcd_density has no impact on the display dpi except for the display mode (tablet, phone, etc.).
Screen settings/Small + ro.sf.lcd_density=320 -> tablet mode in Chrome and 400dpi
Screen settings/Small + ro.sf.lcd_density=400 -> phone mode in Chrome and 400dpi
Screen settings/Large + ro.sf.lcd_density=320 -> tablet mode in Chrome and 480dpi
Screen settings/Large + ro.sf.lcd_density=400 -> phone mode in Chrome and 480dpi
I think maybe the DPI setting from build.prop is replaced during boot with the screen setting (Small:400dpi, Medium:440dpi, Large:480dpi). Could a init.d script could change the value after boot? I'll try tonight if the tablet allows init.d scripts to run.
Well, ok. I only quickly looked through the decompiled code. Change dpi with the app then, it'll make a backup of build. prop and try to compare both files - new and backup. I could have missed something. Just to mention, I didn't like the way tablet had behaved after changing DPI. EMUI is not well-designed for this. It's much better to set DPI for apps and leave it unmodified for system.
@wlausrsker this is covered in the apps running in phone mode thread. I posted there that the adb dpi change settings will stick after rebooting if you run the command "adb shell wm density 340 && adb reboot"*
*Use whatever density works best for you, I have found that 330 works best for me with the view mode and font set to large.
Slavon-93 said:
Change dpi with the app then, it'll make a backup of build. prop and try to compare both files - new and backup. I could have missed something.
Click to expand...
Click to collapse
johje said:
@wlausrskerI posted there that the adb dpi change settings will stick after rebooting if you run the command "adb shell wm density 340 && adb reboot"
Click to expand...
Click to collapse
johje, thanks but I tried it first and it doesn't survive reboot ("./adb shell wm density 320 && ./adb reboot" since I'm on Mac, it reboots in 400dpi).
Slavon, I've compared the files from before and after changing the dpi setting with the app, only ro.sf.lcd_density is changed, so you didn't miss anything.
Since methods successfully used by you and others don't work for me, it must be something I did differently on setting up my tablet. I used greatslon mod of TWRP and then flashed via TWRP the latest SuperSU (v2.79-SR1). Finally, I installed XposedInstaller and got xposed-v87-sdk23-arm64. Did any of you with reboot-surviving custom dpi setting used something different? (like the SRK Tool)
I'm off this weekend but I'll try next week to start over from scratch.
the reason adb change dpi and even build.prop change doesn't work is because huawei has set lcd_density in boot image. check content of /init.6x.rc
these init files are part of boot.img and will be overwritten at every boot. so what u need is a modified boot.img where this set lcd_density line is removed. Once you install that boot, you can set whatever dpi in build.prop and it will work. even adb dpi change will be persistent.
if you are on b026, i can share my edited boot.img
Thanks for the explanation bark1234, I now understand why everything I tried didn't survive reboot!
Thanks also for proposing your edited B026 boot.img but I'm on BTV-W09C100B005 and I can't find any B026 download for BTV-W09. From what I understand from other threads the latest Chinese OTA for the BTV-W09 is the BTV-W09C233B022, so I couldn't use it. Nevertheless, if you could maybe share it for others, it could help someone with the same problem on a BTV-DL09.
I tried to edit my boot.img but I'm a newbie. I've tried to extract my boot.img but I have no result with "cat /proc/mtd", so I extracted mmcblk0boot0 as a best guess. I tried to install abootimg to edit it but there's not blkid.h on Mac OS so I can't build it. If I give you what I extracted, could you maybe edit it like you did with yours? You would save me from applying at random a bunch of tutorials like I just did and hoping it will result in something usable In the meantime, I'll try and learn how to edit a boot.ini with my setup.
bark1234 said:
the reason adb change dpi and even build.prop change doesn't work is because huawei has set lcd_density in boot image. check content of /init.6x.rc
these init files are part of boot.img and will be overwritten at every boot. so what u need is a modified boot.img where this set lcd_density line is removed. Once you install that boot, you can set whatever dpi in build.prop and it will work. even adb dpi change will be persistent.
if you are on b026, i can share my edited boot.img
Click to expand...
Click to collapse
Just as an FYI, the adb dpi change initiated along with the reboot command has stuck for me after multiple reboots.
wlausrsker said:
Thanks for the explanation bark1234, I now understand why everything I tried didn't survive reboot!
Thanks also for proposing your edited B026 boot.img but I'm on BTV-W09C100B005 and I can't find any B026 download for BTV-W09. From what I understand from other threads the latest Chinese OTA for the BTV-W09 is the BTV-W09C233B022, so I couldn't use it. Nevertheless, if you could maybe share it for others, it could help someone with the same problem on a BTV-DL09.
I tried to edit my boot.img but I'm a newbie. I've tried to extract my boot.img but I have no result with "cat /proc/mtd", so I extracted mmcblk0boot0 as a best guess. I tried to install abootimg to edit it but there's not blkid.h on Mac OS so I can't build it. If I give you what I extracted, could you maybe edit it like you did with yours? You would save me from applying at random a bunch of tutorials like I just did and hoping it will result in something usable In the meantime, I'll try and learn how to edit a boot.ini with my setup.
Click to expand...
Click to collapse
If you are rooted, use flashfire app to get ur current boot.img from ur phone. and then copy it out to edit.
The tool i use for editing works on windows. i too have mac only, i have windows on vm in it.
https://www.dropbox.com/s/x46q5nzv49iauwi/Android Image Kitchen.rar?dl=1
Use above link to download tool i use.
unpackimg.bat will unpack boot img.
your init.x files will be in ramdisk, edit it there.
and then use repackimg.bat, it will create new boot.img.
johje said:
Just as an FYI, the adb dpi change initiated along with the reboot command has stuck for me after multiple reboots.
Click to expand...
Click to collapse
bark1234 said:
If you are rooted, use flashfire app to get ur current boot.img from ur phone. and then copy it out to edit.
The tool i use for editing works on windows. i too have mac only, i have windows on vm in it.
https://www.dropbox.com/s/x46q5nzv49iauwi/Android Image Kitchen.rar?dl=1
Use above link to download tool i use.
unpackimg.bat will unpack boot img.
your init.x files will be in ramdisk, edit it there.
and then use repackimg.bat, it will create new boot.img.
Click to expand...
Click to collapse
johje, it won't stuck for me, no matter how I try. Did you root by flashing the latest SuperSU? Did you installed xposed framework?
bark1234, thank you very much for the detailled explanation, I'll use Flashfire app to extract my boot.img and I'll try tomorrow at work on my Windows machine to edit it.
@wlausrsker I have not yet rooted my tablet. Once I got the dpi/phone apps issue fixed, it reduced my urgency for rooting. However, I will be rooting it soon, since a way has been found to enable the 5Ghz wireless adapter for the US version of the tablet. I will let you know if I am able to keep the dpi settings after rooting.
bark1234 said:
If you are rooted, use flashfire app to get ur current boot.img from ur phone. and then copy it out to edit.
unpackimg.bat will unpack boot img.
your init.x files will be in ramdisk, edit it there.
and then use repackimg.bat, it will create new boot.img.
Click to expand...
Click to collapse
Thanks again for the link and the explanation, it was really a painless process.
I used Flashfire app on my tablet to backup my boot.img (it resulted in a boot.lz4 file).
On my Windows machine, in a cmd window:
Code:
lz4 boot.lz4
unpackimg.bat boot
I then opened in Notepad++ the /ramdisk/init.61262.rc file to remove the line setprop ro.sf.lcd_density 560 in the on early-init and on boot sections of the file and saved.
In the cmd window:
Code:
repackimg.bat
rename image-new.img boot.img
I now have an edited boot.img to flash in TWRP. Does it seems to you that I did the editing correctly? The edited boot.img is 13.35Mb (about the same as the boot.lz4) but the extracted boot file before the unpacking was 32.77Mb. Is it normal?
13.9 is correct size. install this boot.img
For those of us following along. Does the edited boot image have to be flashed by TWRP in zip form? Or can we use Fastboot to flash it? or both will work?
I've done the edit's and have what I believe is a flashable zip. I personally like to use fastboot.
I have DPI set and holding by adb as I mentioned before but this is still nice to have.
Thanks
OP - here's a really easy way to change dpi and make it stick: https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi
I'm using it on my MediaPad M3 without issues. PS - 320 is my preferred dpi as well, but I found it caused some issues like Settings would crash. I'm using 322 now without any issue for the last couple weeks. Enjoy
can any 1 guide to restore my serial no, not just put sn file in persist folder, but the whole process
persist folder is a symbolic link and it is readonly, so many things which i cant understand so plz can anyone tell in detail
beinghuman23 said:
can any 1 guide to restore my serial no, not just put sn file in persist folder, but the whole process
persist folder is a symbolic link and it is readonly, so many things which i cant understand so plz can anyone tell in detail
Click to expand...
Click to collapse
It will GONE if you don't backup or remember it.
1. Restore to stock ROM
2. Uninstall modules like: Pixelarity, Oxy-ify, ... Because some will overwrite your SN, IMEI systemlessly. (Can be restore)
Sent from my ZenFone Max Pro M1 using XDA Labs
RedGreenBlue123 said:
It will GONE if you don't backup or remember it.
1. Restore to stock ROM
2. Uninstall modules like: Pixelarity, Oxy-ify, ... Because some will overwrite your SN, IMEI systemlessly. (Can be restore)
Click to expand...
Click to collapse
i am on stock also i knw my serial no how can i put it in my phone
beinghuman23 said:
i am on stock also i knw my serial no how can i put it in my phone
Click to expand...
Click to collapse
Method on the internet:
1. Download files from the attachment.
2. Replace all files to /persist
3. Download AFT 340 ROM from here:
https://cloud.mail.ru/public/iNoC/4VQB1h4sE
4. Go to fastboot mode.
5. Extract the AFT ROM and run flash_all.bat (Win) or flash_all.sh (Linux)
6. Update to Pie (optional)
My persist files in the attachment.
Sent from my ZenFone Max Pro M1 using XDA Labs
thanks for this guide
1 think i want to discuss is the persist folder tells me that its read only
how can i copy files in it? becz i rooted my device and tried changing the permission of the folder but i cant
adb root is also saying cant get this in production rom even i have root access for my terminal.
the persist is a symbolic link to /mnt/vendor/persist.
here in vendor persist folder doesn't exist so i even tried to create a new folder in mnt/vendor and created a symbolic link but after restart the folder goes away.
please guide me through the copying procedure it will be helpfull
beinghuman23 said:
thanks for this guide
1 think i want to discuss is the persist folder tells me that its read only
how can i copy files in it? becz i rooted my device and tried changing the permission of the folder but i cant
adb root is also saying cant get this in production rom even i have root access for my terminal.
the persist is a symbolic link to /mnt/vendor/persist.
here in vendor persist folder doesn't exist so i even tried to create a new folder in mnt/vendor and created a symbolic link but after restart the folder goes away.
please guide me through the copying procedure it will be helpfull
Click to expand...
Click to collapse
chmod 777 /persist/.sn.bin
chmod -R 777 /persist/flag
Try this from terminal and copy agains
Sent from my ZenFone Max Pro M1 using XDA Labs
error folder doesn't exist
beinghuman23 said:
error folder doesn't exist
Click to expand...
Click to collapse
cd /persist
chmod 777 .sn.bin
cdmod -R 777 flag/
Sent from my ZenFone Max Pro M1 using XDA Labs
thats wht the prblm is it tell me persist folder doesn't exist even after i do ls it is showing me it is present there but its not a director its a link
beinghuman23 said:
thats wht the prblm is it tell me persist folder doesn't exist even after i do ls it is showing me it is present there but its not a director its a link
Click to expand...
Click to collapse
Hmm it's working for me.
Try
cd /mnt/vendor/persist
And do chmod
Sent from my ZenFone Max Pro M1 using XDA Labs
Screenshot me ur terminal
Sent from my ZenFone Max Pro M1 using XDA Labs
i am in office right now, i ll get back home and send u the screenshot...thanks
new method:
1. Download new Asus Flash Tool from here: https://drive.google.com/file/d/1-hMp9bXs3ohto48sOzqgXc7TBZW5bz6G/view
2. If you are deleted AFT 340 zip, redownload it, don't extract.
3. Extract Asus Flash Tool
4. Go to fastboot
5. Plug your phone in the computer.
6. In Asus Flash Tool, browse the AFT 340 zip file.
7. Select model (ZB601KL or ZB602KL)
7. Highlight your phone.
8. Double click phone's serial number and replace your new number.
9. Flash (click green arrow)
Hi,
Just upgraded my OP5 to Android 10 official stable version. Rooted successfully with Magisk 20.4
Now I'm trying to do some changes to the system folder but they revert back when I reboot.
1- Trying to replace the emoji with another ttf file, as I always did in Pie but the file gets reverted upon restart.
2- Trying to apply hosts file for ad blocking, same issue the file gets reverted as soon as I restart.
it looks like my system partition is reverting itself for some reason, does anyone know why this happens and how to make the changes stick?
PS: I don't want to enable (Systemless hosts in Magisk) because I'm planning to unroot after doing these changes.
thanks..
medo159 said:
Hi,
Just upgraded my OP5 to Android 10 official stable version. Rooted successfully with Magisk 20.4
Now I'm trying to do some changes to the system folder but they revert back when I reboot.
1- Trying to replace the emoji with another ttf file, as I always did in Pie but the file gets reverted upon restart.
2- Trying to apply hosts file for ad blocking, same issue the file gets reverted as soon as I restart.
it looks like my system partition is reverting itself for some reason, does anyone know why this happens and how to make the changes stick?
PS: I don't want to enable (Systemless hosts in Magisk) because I'm planning to unroot after doing these changes.
thanks..
Click to expand...
Click to collapse
Just forget to change hosts file manualy, use the better Adbloacker Rootless, Blokada
medo159 said:
QUOTE
Click to expand...
Click to collapse
Hi Mate,
Ensure to give proper permissions as follows: rw-r--r-- (0644) to the file. If it is a folder, the permissions are: rwxr-xr-x (0755)
medo159 said:
Hi,
Just upgraded my OP5 to Android 10 official stable version. Rooted successfully with Magisk 20.4
Now I'm trying to do some changes to the system folder but they revert back when I reboot.
1- Trying to replace the emoji with another ttf file, as I always did in Pie but the file gets reverted upon restart.
2- Trying to apply hosts file for ad blocking, same issue the file gets reverted as soon as I restart.
it looks like my system partition is reverting itself for some reason, does anyone know why this happens and how to make the changes stick?
PS: I don't want to enable (Systemless hosts in Magisk) because I'm planning to unroot after doing these changes.
thanks..
Click to expand...
Click to collapse
You can't mount the system partition as rw directly in Android 10. Here's a thread by topjohnwu (slightly technical, but give it a read) on why: https://twitter.com/topjohnwu/status/1259039809361739776