Hi all.
I have a poco x3 pro 8/256gb with global miui 13(stock).
Since I'd like to have more volume steps I founded this guide.
Anyone knows if it's possible and safe with MIUI 13 stock rom?
Mi target is to achieve this result. Thank you.
MezzaLuna said:
Hi all.
I have a poco x3 pro 8/256gb with global miui 13(stock).
Since I'd like to have more volume steps I founded this guide.
Anyone knows if it's possible and safe with MIUI 13 stock rom?
Mi target is to achieve this result. Thank you.
Click to expand...
Click to collapse
Try and error.
Some kernel apps can modify build props like franco kernel manager and toggle it to apply on boot.
This way if you modify build props and had problem booting into system, unroot Magisk (flash original matching boot image), go into MIUI and uninstall the kernel apps, then you can get Magisk back again.
You can also try manually modify the build.prop or default.prop if either exist. If the prop does not work with the system, most likely the system will just ignore that line and has nothing changed to the system.
Still do a data backup manually, so in case if it's not possible to rescue, you can recover some of it.
There is a way to modify props file frome the device?
MezzaLuna said:
There is a way to modify props file frome the device?
Click to expand...
Click to collapse
Personally would not recommend to modify manually for safety reasons.
First you need to make System read/write-able
[GUIDE] How to make your System RW / Super R/W read/write-able
Welcome to the one and only, the original, universal SystemRW / SuperRW feat. MakeRW / ro2rw by lebigmac This script removes the read-only lock of all partitions embedded in the super partition of your stock firmware. This allows you to mount...
forum.xda-developers.com
Related
Hi everyone, as our mi pad has the OV13855 sensor like some Mido (RN4) versions I simply installed the suggested apk from mido thread and I managed to have hdr+ working using Pixel 2 XL settings in the apk. You are free to try other combination anyway.
Here's the link from 'official' page: Download
I have it working on 25/12 Mokee, don't know if it works in Miui or other Pie roms.
sacca25 said:
Hi everyone, as our mi pad has the OV13855 sensor like some Mido (RN4) versions I simply installed the suggested apk from mido thread and I managed to have hdr+ working using Pixel 2 XL settings in the apk. You are free to try other combination anyway.
Here's the link from 'official' page: Download
I have it working on 25/12 Mokee, don't know if it works in Miui or other Pie roms.
Click to expand...
Click to collapse
I'm on Xiaomi.eu's MIUI10 8.12.13 Rom, and app crashes on launch. My suspicions is because MIUI10 does not support/enable Camera2 api. I should be rooted, so I'm gonna try tinkering with the build.prop to get it enabled and report back.
Havoc Os 2.0 build 28-12-2018 crashes
Works on my los 16.
@pan_droid
Try add in /vendor build.prop line :
Code:
persist.camera.HAL3.enabled=1
and use this one: https://androidfilehost.com/?fid=11410932744536985628
Andro_Nicus said:
@pan_droid
Try add in /vendor build.prop line :
Code:
persist.camera.HAL3.enabled=1
and use this one: https://androidfilehost.com/?fid=11410932744536985628
Click to expand...
Click to collapse
I flashed official build of Havoc Os 2.0 31-12-2018, enable camera2 api and camera work normal.
Andro_Nicus said:
@pan_droid
Try add in /vendor build.prop line :
Code:
persist.camera.HAL3.enabled=1
and use this one: https://androidfilehost.com/?fid=11410932744536985628
Click to expand...
Click to collapse
Thanks!
Confirming this also works on xiaomi.EU 9.1.3 weekly.
Enabling camera2api via build. Prop does break the stock miui cam though, it'll crash when launched.
Not that that's a big loss...
Hello,
I have the latest version of xiaomi.eu installed on my mipad 4, is this compatible with it?
Yes
on latest xiaomi.eu I can't get it to work. With magisk 19.2, I can't directly edit the /vendor build.prop (although I give root permission), so I tried systemless with MagiskHide props config module. I supposedly add persist.camera.HAL3.enabled=1 but nothing happens... gcam doesn't work and stock cam continues to work ok. does anyone know what am I doing wrong?
vogiasf said:
on latest xiaomi.eu I can't get it to work. With magisk 19.2, I can't directly edit the /vendor build.prop (although I give root permission), so I tried systemless with MagiskHide props config module. I supposedly add persist.camera.HAL3.enabled=1 but nothing happens... gcam doesn't work and stock cam continues to work ok. does anyone know what am I doing wrong?
Click to expand...
Click to collapse
1. You can edit system build.prop or vendor build.prop, not both.
1a. Copy build.prop to any folder, edit, save.
2. Reboot to twrp, mount system or vendor.
2a. Twrp, advanced, file manager. Rename original build.prop to build.prop.bak, copy edited into system or vendor.
3. Reboot.
dzidexx said:
1. You can edit system build.prop or vendor build.prop, not both.
1a. Copy build.prop to any folder, edit, save.
2. Reboot to twrp, mount system or vendor.
2a. Twrp, advanced, file manager. Rename original build.prop to build.prop.bak, copy edited into system or vendor.
3. Reboot.
Click to expand...
Click to collapse
Thanks! I tried with vendor and it worked! if anyone else tries dont forget to chmod 644 otherwise stuck on boot
its working on my Mi Pad 4 Plus Lte with SuperiorOS. no build.prop editing is required. Thank you.
There is a much simpler method without involving editing any build.prop. Requires magisk. Connect the pad to PC with usb debugging enabled. Type:
adb shell
su
setprop persist.camera.HAL3.enabled 1
setprop persist.camera.eis.enabled 1
by order on PC. Check your tab and accept anything pop up. Reboot and it's good to go.
Works great on the latest Havoc Rom, rooted with Magisk. It also has video stabilization at 1080p! this is awesome! thank you!
I'm in pixel experience rom, and didn't work, I don't know what to do. I am not an expert.
Jagoflo said:
I'm in pixel experience rom, and didn't work, I don't know what to do. I am not an expert.
Click to expand...
Click to collapse
Works fine here, Pixel Experience Plus with Mi Pad 4 no build.prop editing required.
FYI, Urnyx's Gcam 7.3, including night mode, works out-of-the-box on Carbon ROM Pax (Android 10).
Hello people,
I have unlocked my phone yesterday and installed Magisk and root explorer.
I would like to replace the files in /system/fonts to change the default fonts. I tried to flash a twrp zip with new fonts and also manually tried to replace the fonts. But the system cannot be mounted as r/w in root explorer even after granting root permissions and flashing twrp zip does nothing. Is there any way to overcome this issue to mount system as r/w?
I mean what is the point of rooting if we cannot modify system!
Thanks!
Normal ... This is a new Android 10 restriction ... The system partition can no longer be mounted for writing, even with root!
On my old Redmi Note 4 (Rom Havoc Android 10), I had managed to change the fonts by copying the file from TWRP.
Many modifications are starting to be systemlessly. Like viper4android and others. The worst is not being able to flash system/vendor images in recovery.
wopr33 said:
Normal ... This is a new Android 10 restriction ... The system partition can no longer be mounted for writing, even with root!
On my old Redmi Note 4 (Rom Havoc Android 10), I had managed to change the fonts by copying the file from TWRP.
Click to expand...
Click to collapse
Thanks for the information. I tried to copy file in TWRP but it is giving an error. Could you please let me know how you have done it?
I don't know how TWRP works for the Poco X3, but for the Redmi Note 4 I copied the file using the built-in explorer, with no errors.
I think you need to activate the system partition in R/W in TWRP.
htcmusic said:
Thanks for the information. I tried to copy file in TWRP but it is giving an error. Could you please let me know how you have done it?
Click to expand...
Click to collapse
Sadly nothing will work for you rn. As far as i know, all devices launching with Android 10 use "dynamic partitions" wherein all partitions are inside Super.img and /system, /vendor, /product no longer writeable (Read only).
IMHO you're better off learning how to make a Magisk module yourself. Look at this guide from topjohnwu: https://topjohnwu.github.io/Magisk/guides.html
Slim K said:
Sadly nothing will work for you rn. As far as i know, all devices launching with Android 10 use "dynamic partitions" wherein all partitions are inside Super.img and /system, /vendor, /product no longer writeable (Read only).
IMHO you're better off learning how to make a Magisk module yourself. Look at this guide from topjohnwu: https://topjohnwu.github.io/Magisk/guides.html
Click to expand...
Click to collapse
Thank you for the info.
I finally was able to change the font using magisk modules as mentioned here: https://github.com/nongthaihoang/custom_font_installer
htcmusic said:
Thank you for the info.
I finally was able to change the font using magisk modules as mentioned here: https://github.com/nongthaihoang/custom_font_installer
Click to expand...
Click to collapse
I am very interested (to replace emojis).
I looked at the Magisk module page, it talks about flashing the ZIP, so I need TWRP ? For the moment, I didn't install it.
wopr33 said:
I am very interested (to replace emojis).
I looked at the Magisk module page, it talks about flashing the ZIP, so I need TWRP ?
Click to expand...
Click to collapse
You don't need twrp to install a Magisk module. You can do that through the Magisk Manager just as easily.
wopr33 said:
I am very interested (to replace emojis).
I looked at the Magisk module page, it talks about flashing the ZIP, so I need TWRP ? For the moment, I didn't install it.
Click to expand...
Click to collapse
I just installed the magisk module with custom fonts in internal storage as mentioned in the github page. It was magical, I was trying to replace the fonts for the whole day and it didn't work. Somehow this magisk module does the job.
Android 10 has this messed up file system that does not allow any writing of the system files. While I have root neither Root Explorer or any other third party apk can force it over. I also cannot install any application with Root Explorer. What's the good of root if we can't actually mod our own system files?
Also, since debloating everything and removing google everything, I can't use instacart anymore. It says I need Google Play Services. This NEVER was an issue on my Moto G7 Power.
At the very least is there a tool where I can unpack Super.Sparsechunk files and then repack them so I can flash them as stock via fastboot. All I want to do is delete the stock ringtones on this phone and replace them with my own .ogg files (as I've done on every Moto I've ever had). Thanks.
You have to root it before using R/W
One Ace is easy to root though
Unlock bootloader and patch boot.img with Magisk app, and flash it
mingkee said:
You have to root it before using R/W
One Ace is easy to root though
Unlock bootloader and patch boot.img with Magisk app, and flash it
Click to expand...
Click to collapse
I did all that. It still will not go to R/W. This seems to be an Android 10 issue.
Here you go my friend. Enjoy!
lebigmac said:
Here you go my friend. Enjoy!
Click to expand...
Click to collapse
Your method as of now is not working.
It's working fine on my Xiaomi (which is A slot only device) but you are right. The current version is not as universal yet as I'd like it to be. There seems to be an lpmake error at the very end of the script for those with A/B slot device.
Don't worry I am working very hard on identifying and fixing the error.
Soon your system shall be RW!
Hey guys,So um i am using redmi note 10 miui 12.5.3 global and i pulled the stock miui camera and gallery apk using adb pull commands. I plan to install pixel experience custom rom. How would i install these in that rom?
Would require this custom ROM gets rooted, phone's bootloader gets permanently unlocked, phone's Android's AVB permanently gets disabled, as also phone's Android's SELinux permanently gets disabled.
can i find links for tutorial on how to do this?
and even if I managed to do all these,what do i do after that? would the apk install just like that?
ahmed6392 said:
and even if I managed to do all these,what do i do after that? would the apk install just like that?
Click to expand...
Click to collapse
If the APKs are of type
system-app
then you've to mount device's /system partition
user-app
then you've to mount device's /data partition
as RW before installing the APKs.
i've done the three steps. i didnt understand the last thing.How do i install the apks? do i need a seperate installer or a custom recovery? could you please explain and the apks are of system-app
You simply install them by means of ADB
Code:
adb devices
adb install <LOCATION-OF-APK-FILE-ON-PC-HERE>
Dear All,
I am using the Pixel 5 with Android 13 Build No: TQ1A.230105.001 and I rooted by flashed the image from Magisk app through ADB.
I checked and the phone said ROOTED and I cant grant access to apps but when I change font by any app, it isn't work and I copy in Root Explorer, I can't change the button "MOUNT R/W".
What can I do now? Should I re-root or flash again???
Thank you and waiting for your help.
Some new versions of android restrict it, and you have to do so through recovery.
Arealhooman said:
Some new versions of android restrict it, and you have to do so through recovery.
Click to expand...
Click to collapse
can I install TWRP on Andoird 13???
dpn025 said:
can I install TWRP on Andoird 13???
Click to expand...
Click to collapse
Yes. You Amy be able to set your system to rw through stock recovery, take a look if you can mount it.
Arealhooman said:
Yes. You Amy be able to set your system to rw through stock recovery, take a look if you can mount it.
Click to expand...
Click to collapse
please help me, I can't understand it.
do you have atock recovery? Or TWRP?
Arealhooman said:
do you have atock recovery? Or TWRP?
Click to expand...
Click to collapse
I'm still stock recovery.
Boot into stock recovery. Take a photo for me. If you can’, just tell me if there’s a option that starts with “mount” and what does it say?
From Android 10 and above, the system has changed to one Super Partition. This means that the system cannot be mounted as R/W as it's Read-only by nature.
There is a tool Universal SystemRW that supposedly converts the Read-only to R/W. I haven't tried it personally but it looks very promising.
swangjang said:
From Android 10 and above, the system has changed to one Super Partition. This means that the system cannot be mounted as R/W as it's Read-only by nature.
There is a tool Universal SystemRW that supposedly converts the Read-only to R/W. I haven't tried it personally but it looks very promising.
Click to expand...
Click to collapse
No, TWRP can mount too. And stock recovery for some devices
Root explorer is screwed up for some pixel ROMs including lineage so I don't know about stock. It will crash when trying to read many files, specifically text files you should normally be able to read or edit. It's working on the latest pixel experience ROM but crashed on two other roms I was trying
dpn025 said:
please help me, I can't understand it.
Click to expand...
Click to collapse
use material file manager. It's the only one that seems to be working right now