Guys, i'm going crazy! I have a Rooted Xiaomi 11T Pro, with Unlocked Bootloade, TWRP installed and everytime when i try to Uninstall System apps with Root Uninstaller Pro, the app display this message.
I already grant Magisk Permmission for Root Uninstaller Pro, but still not able to Uninstall System Apps.
I'm on Miui 13 btw
I don't know how to grant permmissions for this app so i can Uninstall system apps. Any help would be awesome!
This is a restriction from A12 or A13 on devices with A/B partitions.
You must use a script for this.
See LEBIGMAC's posts.
Example:
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com
NOSS8 said:
This is a restriction from A12 or A13 on devices with A/B partitions.
You must use a script for this.
See LEBIGMAC's posts.
Example:
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you bro! There is no other way of dealing with this RW mount?
I saw in TWRP an option! Mount System as RW!
Is this ok, to avoid installing almost 8GB in my phone because of Lebigmac script?
I saw in TWRP an option! Mount System as RW!
I would be surprised if this works!
There is another less known way. The traditional way of using termux stopped working, but this is a another way that may work
Code:
su
mount -o rw,remount /
I suggest you change it back to RO when done. You can also uninstall apps using termux
Code:
ADB shell pm uninstall [package name]
Dynamic partitions usually have deduplicated blocks, you can't just mount rw because the file system is designed ro. either convert partition and create your own super.img with one of the different scripts they all do the same, or find other method to debloat without touching system at all.
https://forum.xda-developers.com/t/...shing-our-modifications.4196625/post-84739021
filip_pine said:
Thank you bro! There is no other way of dealing with this RW mount?
I saw in TWRP an option! Mount System as RW!
Is this ok, to avoid installing almost 8GB in my phone because of Lebigmac script?
Click to expand...
Click to collapse
yes its working , i always use this option with miui 13 and twro by skkk
thugsalah said:
yes its working , i always use this option with miui 13 and twro by skkk
Click to expand...
Click to collapse
I also use the TWRP Version skkk and it dosen't work, neigher in Miui 13 or 14...
filip_pine said:
I also use the TWRP Version skkk and it dosen't work, neigher in Miui 13 or 14...
Click to expand...
Click to collapse
IN MIUI 13 IT WORKING FINE
thugsalah said:
IN MIUI 13 IT WORKING FIN
Click to expand...
Click to collapse
thugsalah said:
We need video, otherwise what you say is not true! I'm on MIUI 13 now and it gives error when try to mount system as RW! Stop spreading misleading information here on xda
Click to expand...
Click to collapse
look install the latest twrp skkk
boot in the recovery
advanced -- make the system partition rw
for me it work only in miui13 not miui13
thugsalah said:
look install the latest twrp skkk
boot in the recovery
advanced -- make the system partition rw
for me it work only in miui13 not miui13
Click to expand...
Click to collapse
This is not working and has been confirmed already several times! An admin should really look into this matter, cuz you're spreading misleading information here on xda!
filip_pine said:
This is not working and has been confirmed already several times! An admin should really look into this matter, cuz you're spreading misleading information here on xda!
Click to expand...
Click to collapse
what wrong with u man, it work with me in miui 13 ,and i do this several time, if you can do a video to see what wrong with your procces
thugsalah said:
what wrong with u man, it work with me in miui 13 ,and i do this several time, if you can do a video to see what wrong with your procces
Click to expand...
Click to collapse
It dosen't matter what MIUI Version it is! Xiaomi dosen't allow to mount system as RW in new Xiaomi devices unless you flash the Lebigmac Script!
Again, this is a lie and you know this! I see you are a senior member here, i don't really know why you are trying to spread misleading information here! You are the only one in the world to manage to mount system as RW on 11T Pro from TWRP! Is kinda funny, but hey, that's a nice try!
Xiaomi can have different Android versions for the same MIUI versions.
For example one of their device on MIUI13 can have the Android OS version 9, another Xiaomi device may have also MIUI13 and the Android OS 11. So they have the same MIUI13 but totally different underlying Android OS, hence the above confusion about why TWRP read/write works on the same MIUI version, but with different Android OS version
The confusion is mainly due to users who talk about Mui for the Twrp when the important thing is the system version, A12/13,etc, and/or who post on a thread concerning the Xiaomi 11 t pro (vili) when they have another device and don't specify it.
Related
Dear developer for the LS ROM,
dear p880 community,
I really like the LS Rom and tried many times to install the new nightlies from @laufersteppenwolf, but it's not possible for me to keep the F2FS format at the p880. I use the special TWRP recovery from @laufersteppenwolf and tried some ideas from other users (formating seven times and unmount cache / data).
I saw that the download page isn't available anymore. Is there any new recovery which I can use? Do anyone has an idea how I can install the new LS 3.2 nightlies without using another kernel?
Thanks & Best,
HDSteff
@Demetris told me he will get back to LS.
Yes, I read this as well. But I'm wonderning why @laufersteppenwolf is compiling new builts on regular base, if no one can use it? So it seems that it should run somehow?! But how and with which recovery?
But thanks for your answer!
Steff
Delete boot.img from zip and flash cyanodak after rom
Rudjgaard said:
Delete boot.img from zip and flash cyanodak after rom
Click to expand...
Click to collapse
Thanks Rudjgaard for your answer!
I've two questions regarding this:
1. Do you have a link for me?
2. Do I use the ext4 format with cyanodak?
Last time I tryed the IODAK kernel, sure it works but actually I'd like to try the new F2FS format.
Best,
Steff
HDSteff said:
Thanks Rudjgaard for your answer!
I've two questions regarding this:
1. Do you have a link for me?
2. Do I use the ext4 format with cyanodak?
Last time I tryed the IODAK kernel, sure it works but actually I'd like to try the new F2FS format.
Best,
Steff
Click to expand...
Click to collapse
Yes, obviously using this method you keep the standard ext4
Tbh i'm one of those who believe there's no advantage in using f2fs outside of a server environment
Disclaimer :
Code:
I am not responsible for any damage to your device!
Use this mod at your own risk!
What's this?
This mod increases the audio bitrate on video recording from a disgraceful 96kbps to a respectable 320kbps. Thus, giving a richer, more pleasing audio quality.
Still confused? Click here for a better explanation
Requirements :
- A rooted phone with magisk installed
- An opened mind (important!)
Contributors :
@Jt380p
@Slim K
* NOTES * (READ) :
- Not all ROMs are compatible with this mod, you might end up in a bootloop. YOU HAVE BEEN WARNED!
Download :
https://drive.google.com/file/d/1wr-p7puOL8nYb1wj1AyVbh9XmMp5kRKI/view?usp=sharing (Flash with magisk manager)
Source :
https://forum.xda-developers.com/Mi-9/themes/magisk-audio-bitrate-increase-t3927810
Audio files provided by @Slim K
Thanks to :
@Slim K
@topjohnwu for Magisk
Created : 7/11/2020
Last updated : 7/11/2020
reserved
Just tried it on stock MIUI with stock camera and Gcam. Works like a charm. Ty :good:
Slim K said:
Just tried it on stock MIUI with stock camera and Gcam. Works like a charm. Ty :good:
Click to expand...
Click to collapse
For me it works on Stock, but not on Urnyx05 GCam. Thanks Dev.
Lineage android 11 will benefit from it, or that is already implemented in them?
So which ROMs are not compatible?
Aki-to said:
So which ROMs are not compatible?
Click to expand...
Click to collapse
This mod uses magisk module template to replace a file in vendor folder. A tip for beginners using such a mod is to inspect it to know what it does. For example in the root of the module zip you will find the folder system, which has the needed folders/files path for replacement. If you open install.sh in text viewer, you would read the line :
Bash:
set_perm $MODPATH/system/vendor/etc/media_profiles_vendor.xml 0 0 0644
That should tell you which file it is and their permissions. Now open the same path on your ROM and look for that file, if it exists, then it should work. Although not every camera app (e.g gcam) uses that file.
Slim K said:
This mod uses magisk module template to replace a file in vendor folder. A tip for beginners using such a mod is to inspect it to know what it does. For example in the root of the module zip you will find the folder system, which has the needed folders/files path for replacement. If you open install.sh in text viewer, you would read the line :
Bash:
set_perm $MODPATH/system/vendor/etc/media_profiles_vendor.xml 0 0 0644
That should tell you which file it is and their permissions. Now open the same path on your ROM and look for that file, if it exists, then it should work. Although not every camera app (e.g gcam) uses that file.
Click to expand...
Click to collapse
Thanks, this was very helpful.
Indeed, it seems like a very easy set of scripts, did not expect that. However, the only thing I could not find is where the default functions are actually called, though I assume these are generic functions that are always called by Magisk, no matter which module is being installed.
This mod is also so extremely tiny, you could pretty much make these changes manually. Just take care of permissions and replace the file, that's it. It's even less complicated than working with /etc/fstab, it seems.
Perhaps I should release a couple of mods myself, if mod devs are getting such a Magisk Module template thing, anyway, which pretty much does all the work, already.
Aki-to said:
Thanks, this was very helpful.
Indeed, it seems like a very easy set of scripts, did not expect that. However, the only thing I could not find is where the default functions are actually called, though I assume these are generic functions that are always called by Magisk, no matter which module is being installed.
Click to expand...
Click to collapse
You assume correctly. The path to the functions can be usually found in /data/adb/magisk/util_functions.sh on your device.
Perhaps I should release a couple of mods myself, if mod devs are getting such a Magisk Module template thing, anyway, which pretty much does all the work, already.
Click to expand...
Click to collapse
Why write code twice when it already exists and works for everyone.
Hello, could someone please confirm if it works on firmware xiaomi eu 12.0.4. stable, thank you very much.
nike1973 said:
Hello, could someone please confirm if it works on firmware xiaomi eu 12.0.4. stable, thank you very much.
Click to expand...
Click to collapse
Yes it works
Thank you. Works on MIUI EU 12.0.6.
Eu 12.0.6, super stabilization (on stock camera) crashes when module is active.
I flashed it to the phone. The stock camera app still records audio at 127kbps. Does not save with 320kbps!.I use Indonesian stable miui 12/android 10. please Help!
Anyone tried on Xiaomi.eu rom?
Running 12.0.8.
Hi!
gkhnkaanyrtc said:
I flashed it to the phone. The stock camera app still records audio at 127kbps. Does not save with 320kbps!.I use Indonesian stable miui 12/android 10. please Help!
View attachment 5272691View attachment 5272693
Click to expand...
Click to collapse
Hi! I have the same problem ... Did you fix it? I use Miui 12.0.1 with Android 11
320kbps should be the default, I wonder why the f**k Xiaomi gives us 96kbps.
Does it work in Pixel Experience rom on Surya?
If not, anyone can make a bount?
matheus_sc said:
If not, anyone can make a bount?
Click to expand...
Click to collapse
Surely they are already working on it. But it just takes some time. At the moment everything is working optimally despite fastboot. Even root is possible.
pittrich said:
Surely they are already working on it. But it just takes some time. At the moment everything is working optimally despite fastboot. Even root is possible.
Click to expand...
Click to collapse
I know i use xiaomi eu already. Only update is pain to ass
wait for it
Rumour has it some chinese dev is working on it
Any news?
matheus_sc said:
Any news?
Click to expand...
Click to collapse
Still no sign.... Orangefox also quiet...
The guy who made lots of xiaomi TWRP recoveries stopped developing.
... are kernel (or device/vendor) repos released for it?
This would help.
Do we have TWRP and/or released kernel sources from other Qualcom 888 based devices out there?
raupe said:
... are kernel (or device/vendor) repos released for it?
This would help.
Do we have TWRP and/or released kernel sources from other Qualcom 888 based devices out there?
Click to expand...
Click to collapse
This?
Xiaomi Mi 11 kernel source code is out, the device is codenamed "venus" - Gizmochina
Yesterday, Xiaomi announced Mi 11 as the world’s first smartphone powered by Qualcomm Snapdragon 888. The handset already went for pre-order soon after the launch and is set to go on sale for the first time on January 1. Ahead of its sale, the company has even released this device’s kernel...
www.gizmochina.com
I read on Xiaomi.eu somewhere that there are issues with how the partitions are made and TWRP is very difficult to make for this. They said it's gonna take either a very long time before a recovery is made, or maybe not even at all.
Danacy said:
I read on Xiaomi.eu somewhere that there are issues with how the partitions are made and TWRP is very difficult to make for this. They said it's gonna take either a very long time before a recovery is made, or maybe not even at all.
Click to expand...
Click to collapse
Yeah they changed everything over to GKI 1.0 and no one seems to be supporting it, although they found somewhere on a Chinese site a recovery that works (TWRP) if you boot it (don't flash it) and unencrypts the data. It's in the XDA forums now.
[TWRP] [venus] TWRP Recovery for Mi 11
REMOVED! Use this instead : https://forum.xda-developers.com/t/recovery-11-official-teamwin-recovery-project.4374109/
forum.xda-developers.com
mslezak said:
[TWRP] [venus] TWRP Recovery for Mi 11
REMOVED! Use this instead : https://forum.xda-developers.com/t/recovery-11-official-teamwin-recovery-project.4374109/
forum.xda-developers.com
Click to expand...
Click to collapse
*justintime* said:
Still no sign.... Orangefox also quiet...
The guy who made lots of xiaomi TWRP recoveries stopped developing.
Click to expand...
Click to collapse
Yeah Mauronofrio is out, too much work for no return. He was pretty much the last standing open-source TWRP dev out there for tons of devices. The ones from China never get source released... Which would mean that someone would have to pickup the TWRP project and re-engineer it to fit the new GKI 1.0 then 2.0 platforms that run off that ACK. That's a lot of work. I'm talking about keeping the TWRP project open-source. It would very nice if Google stepped in since they are experts on the new format, but no such luck.
mslezak said:
Yeah they changed everything over to GKI 1.0 and no one seems to be supporting it, although they found somewhere on a Chinese site a recovery that works (TWRP) if you boot it (don't flash it) and unencrypts the data. It's in the XDA forums now.
Click to expand...
Click to collapse
Interesting, that would explain also the lack of custom ROMs? But I read that the source code is released, even before the device was launched. Isn't there GKI-support to be found in there?
Danacy said:
Interesting, that would explain also the lack of custom ROMs? But I read that the source code is released, even before the device was launched. Isn't there GKI-support to be found in there?
Click to expand...
Click to collapse
Yes they released source there are just no instructions anywhere on how to build the kernel #1 and the GKI modules #2 and combine into a build.
The new Xiaomi.eu weekly includes TWRP for Venus (Mi11) as well as Star (Mi 11 Lite 5G, Mi 11 Pro, Mi 11 Ultra, MIX FOLD) (it's a bootable TWRP, but persists after installation). Seems last week's has added Alioth (Mi 10S, Redmi K40). So I would expect a TWRP for Haydn to show up soon in the weekly Xiaomi.eu releases. Seems they forgot the haydn doesn't have TWRP yet so you can't actually install it! Tried the updater app no go, it can't boot to recovery because they don't have one yet, even though on Xiaomi.eu they say it's available, can't find it anywhere.
BTW the only TWRPs I can actually find are for Venus and Star.
haydn TWRP is not working: https://androidfilehost.com/?fid=14943124697586336730 remember: fastboot boot twrp-3.5.1-haydn.img ... although I tried everything, this TWRP just doesn't work - you boot right into the system after the fastboot boot step. Tried everything I can think of, always boots to system. Guess it's still a waiting game...
mslezak said:
Yes they released source there are just no instructions anywhere on how to build the kernel #1 and the GKI modules #2 and combine into a build.
Click to expand...
Click to collapse
Just one more question since this has been bothering me; what would be needed from Xiaomi? Instructions on how to build the kernel? Have they ever done this before about something like this? Like, is it a reasonable thing to ask them to release instructions? I know some people working there, I could forward the request.
Well I've run this by many many devs.
The issue with the GKI 1.0 and ACK is that you must download the entire AOSP build environment and make sure it works with the separate ACK (Android Common Kernel) and then properly loads the GKI modules from a separate build step. Together they make 1 kernel. This ACK per Linux Version and across vendors should be AOSP and identical. Therefore, a single build should work across all Linux 5.4 based kernels.
But... most devs are just skipping AOSP and inlining the GKI modules so they can have 1 build step. Not exactly what Google intended, but way less storage, and you can use Clang or GCC or whatever you want.
I think what OEMs are posting is merely the entire combined source code, no 2 step build process. Only a single file for the QGKI config portion. Which won't build your GKI modules as it comes. A build script for this (Q)GKI portion would be extremely beneficial.
If any OEM walks through the build steps 1) how to create only the QGKI modules and 2) how to assemble them into 1 kernel with the ACK, that would be great for devs. It just hasn't happened. So we get hacked kernels for the 888 running Linux 5.4.
The Generic Kernel Image (GKI) project | Android Open Source Project
source.android.com
mslezak said:
Well I've run this by many many devs.
The issue with the GKI 1.0 and ACK is that you must download the entire AOSP build environment and make sure it works with the separate ACK (Android Common Kernel) and then properly loads the GKI modules from a separate build step. Together they make 1 kernel. This ACK per Linux Version and across vendors should be AOSP and identical. Therefore, a single build should work across all Linux 5.4 based kernels.
But... most devs are just skipping AOSP and inlining the GKI modules so they can have 1 build step. Not exactly what Google intended, but way less storage, and you can use Clang or GCC or whatever you want.
I think what OEMs are posting is merely the entire combined source code, no 2 step build process. Only a single file for the QGKI config portion. Which won't build your GKI modules as it comes. A build script for this (Q)GKI portion would be extremely beneficial.
If any OEM walks through the build steps 1) how to create only the QGKI modules and 2) how to assemble them into 1 kernel with the ACK, that would be great for devs. It just hasn't happened. So we get hacked kernels for the 888 running Linux 5.4.
The Generic Kernel Image (GKI) project | Android Open Source Project
source.android.com
Click to expand...
Click to collapse
OK, I see. Thank you for your reply. I am going to see how far I can get this. Tnx again!
Is there a work around for this no storage space error I'm getting
Android 11 pixel 5
ghost9640 said:
Android 11 pixel 5
Click to expand...
Click to collapse
Did you make your stock read-only System RW yet with the one and only , the original SystemRW / SuperRW feat. MakeRW by lebigmac ? No I'm not talking about one of the dubious copycat tools that are floating around nowadays but I'm talking about the one and only, the original (see link in my signature below!)
Usually out of space error means you must run my script again with larger custom size. I'd recommend size=25 or size=50. Good luck
Don't worry brand new version of my script which will be released in the next 2 weeks already has fully working auto-resize feature!
lebigmac said:
Did you make your stock read-only System RW yet with the one and only , the original SystemRW / SuperRW feat. MakeRW by lebigmac ? No I'm not talking about one of the cheap copycat tools that are floating around nowadays but I'm talking about the one and only, the original (see link in my signature below!)
Usually out of space error means you must run my script again with larger custom size. I'd recommend size=25 or size=50. Good luck
Don't worry brand new version of my script which will be released in the next 2 weeks already has fully working auto-resize feature!
Click to expand...
Click to collapse
str8 G, appreciate you
Hi guys! I recently rooted via magisk on my t11 pro. but trying to write on the "system" folder gives me an error and I can only "read" it on the forum I tried to look for a solution but nothing to do. Could some good soul help me? Thanks again!
I have the global rom 13.0.15.0 (SKDEUXM)
ANDROID
12 SKQ1.211006.001
extramac said:
Hi guys! I recently rooted via magisk on my t11 pro. but trying to write on the "system" folder gives me an error and I can only "read" it on the forum I tried to look for a solution but nothing to do. Could some good soul help me? Thanks again!
I have the global rom 13.0.15.0 (SKDEUXM)
ANDROID
12 SKQ1.211006.001
Click to expand...
Click to collapse
You can't mount logical partitions as read, write because of dynamic partitions.
so what? is there no way to fix this?
NOSS8 said:
You can't mount logical partitions as read, write because of dynamic partitions.
Click to expand...
Click to collapse
extramac said:
so what? is there no way to fix this?
Click to expand...
Click to collapse
It is not a problem but a function.
You can try creating a Magisk module.
But without knowing you go towards the brick.
https://source.android.com/docs/core/ota/dynamic_partitions/implement
Universal Mount SystemRW / SuperRW featuring MakeRW (read/write)
ounila said:
Universal Mount SystemRW / SuperRW featuring MakeRW (read/write)
Click to expand...
Click to collapse
Will not work on A12.
A12 https://forum.xda-developers.com/t/...er-read-writable-again.4483933/#post-87464023
there is therefore no way to write to the system folder? not even changing ROM type lineages os?
NOSS8 said:
Will not work on A12.
A12 https://forum.xda-developers.com/t/...er-read-writable-again.4483933/#post-87464023
Click to expand...
Click to collapse
Lol did you see how that guy from that thread that you're referring to just shamelessly recycled my original descriptions and some binaries from my old SystemRW/SuperRW feat. MakeRW release without even mentioning the original author? Only added me after I caught him red handed. Manners nowadays...
@NOSS8 That's not 100% true. Some talented folks got my old script to work just fine in Android 12 simply by disabling the checkSDK() function inside the script...
It all depends on your hardware and software really. Of course newer Android versions will have new annoying read-only restrictions. That's normal. Having read/write access to your own device is a HUGE security vulnerability in itself
I am still working on updating my old script if any talented developers want to contribute please send me a PM thanks! I am still happy with my old Xiaomi Poco X3 NFC running Android 10 / 11 and that's why my SystemRW/SuperRW feat. MakeRW script has also been frozen in time so to speak. I think once I get my hands on one of those next-gen Samsung or brand new Xiaomi devices it should be much easier to adapt my old script to the new read-only mechanisms. Are there any good next-gen devices that you would recommend in the 350 € range? Thanks! I kind of feel like the Poco X4 Pro isn't really a worthy successor to the X3 Pro
lebigmac said:
That's not 100% true. Some talented folks got my old script to work just fine in Android 12 simply by disabling the checkSDK() function inside the script...
It all depends on your hardware and software really. Of course newer Android versions will have new annoying read-only restrictions. That's normal. Having read/write access to your own device is a HUGE security vulnerability in itself
I am still working on updating my old script if any talented developers want to contribute please send me a PM thanks! I am still happy with my old Xiaomi Poco X3 NFC running Android 10 / 11 and that's why my SystemRW/SuperRW feat. MakeRW script has also been frozen in time so to speak. I think once I get my hands on one of those next-gen Samsung or brand new Xiaomi flagships it should be much easier to adapt my old script to the new read-only mechanisms. Are there any good devices that you would recommend? I'm too poor for flagship. It shouldn't cost more than 350 € Thanks!
Click to expand...
Click to collapse
I'm sorry I'm unfortunately a newbie, otherwise I would have helped you. but maybe if you tell me what I can do I will help you, even just by sending you the logs of my phone. PS: but is your script compatible with magisk? Or only with TRWP?
lebigmac said:
Are there any good next-gen devices that you would recommend in the 350 € range? Thanks! I kind of feel like the Poco X4 Pro isn't really a worthy successor to the X3 Pro
Click to expand...
Click to collapse
Xiaomi 10T , Xiaomi redmi k40, Xiaomi redmi-note 11 pro 5 G
Poco F3.
lebigmac said:
Lol did you see how that guy from that thread that you're referring to just shamelessly recycled my original descriptions and some binaries from my old SystemRW/SuperRW feat. MakeRW release without even mentioning the original author? Only added me after I caught him red handed. Manners nowadays...
@NOSS8 That's not 100% true. Some talented folks got my old script to work just fine in Android 12 simply by disabling the checkSDK() function inside the script...
It all depends on your hardware and software really. Of course newer Android versions will have new annoying read-only restrictions. That's normal. Having read/write access to your own device is a HUGE security vulnerability in itself
I am still working on updating my old script if any talented developers want to contribute please send me a PM thanks! I am still happy with my old Xiaomi Poco X3 NFC running Android 10 / 11 and that's why my SystemRW/SuperRW feat. MakeRW script has also been frozen in time so to speak. I think once I get my hands on one of those next-gen Samsung or brand new Xiaomi devices it should be much easier to adapt my old script to the new read-only mechanisms. Are there any good next-gen devices that you would recommend in the 350 € range? Thanks! I kind of feel like the Poco X4 Pro isn't really a worthy successor to the X3 Pro
Click to expand...
Click to collapse
LoL I visit your posts every week
Anyways at your request of a good cheap device. I recommend Realme Q5 pro which is the very cheap Chinese version of GT neo 3T (basically the same hardware). Buy it and use GT neo 3T rom and it'll just works the same. Just about 330$ or even cheaper. I'm having it right now and it's good in almost every aspect except camera and bad stock firmware. Just do a swap and set swappiness at 100 and it runs fine )
Good morning, what rom do you have? Have you rooted it, but do you have custom recovery (TWRP or OrangeFox?
I have a Zip, which is flashed by recovery, which solves the reading problem, and converts the system to writing.
You will tell me
lebigmac said:
Are there any good next-gen devices that you would recommend in the 350 € range?
Click to expand...
Click to collapse
The Poco F4 looks very interesting and is a solid phone.
Spillunke said:
The Poco F4 looks very interesting and is a solid phone.
Click to expand...
Click to collapse
But do you have custom recovery?
https://dl.akr-developers.com/?dir=skkk/TWRP/A12/v6.3_A12
https://dl.akr-developers.com/?file...iK40S-POCOF4_v6.3_A12-munch-skkk_a36e4c33.zip
Joche88 said:
But do you have custom recovery?
Click to expand...
Click to collapse
There is one for the F4, but that wasn't the question. I think a few "next-gen Samsung" and "brand new Xiaomi devices" still have no custom recovery yet.
Spillunke said:
There is one for the F4, but that wasn't the question. I think a few "next-gen Samsung" and "brand new Xiaomi devices" still have no custom recovery yet.
Click to expand...
Click to collapse
I know this wasn't the question, but in order to use the zip I have to fix the problem, you need custom recovery to flash it.
Thanks for those suggestions above!
The question is : which 'special feature' is preventing you from mounting your device as read/write?
Bash:
adb shell
su
mount -o remount,rw /
if you get read-only error, then immediately after the remount command run dmesg and look for an error related to that mount command you just did. It should give you further info about what exactly is preventing your device from mounting as rw
Also to check if your / (system) partition has the infamous shared_blocks read-only feature you can run this code:
for i in `seq 0 5`; do tune2fs -l /dev/block/dm-$i && echo; done
Joche88 said:
I know this wasn't the question, but in order to use the zip I have to fix the problem, you need custom recovery to flash it.
Click to expand...
Click to collapse
What zip you talking about? systemrw_1.32_flashable.zip? You can extract it and run the script manually inside Android (or in recovery) as long as you're rooted
lebigmac said:
Lol did you see how that guy from that thread that you're referring to just shamelessly recycled my original descriptions and some binaries from my old SystemRW/SuperRW feat. MakeRW release without even mentioning the original author? Only ................................
Xiaomi devices it should be much easier to adapt my old script to the new read-only mechanisms. Are there any good next-gen devices that you would recommend in the 350 € range? Thanks! I kind of feel like the Poco X4 Pro isn't really a worthy successor to the X3 Pro
Click to expand...
Click to collapse
I have successfully mount Super as R/W with your script v1.32.
ROM = 13.0.15.0 SKDEUXM.
ounila said:
I have successfully mount Super as R/W with your script v1.32.
ROM = 13.0.15.0 SKDEUXM.
Click to expand...
Click to collapse
Are you kidding me? My old systemrw_1.32 script still works even in Android 12? I can't believe it! What device are you using? MIUI 13.0.15.0 you said? Thanks for the heads up I will try it
{Mod edit: Inappropriate language removed. Regards Oswald Boelcke}