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}
Related
https://github.com/ShqipLewis/Xiaomi_Kernel_OpenSource/tree/andromeda-p-oss
https://github.com/ShqipLewis/device_xiaomi_andromeda
https://github.com/ShqipLewis/vendor_xiaomi_andromeda
https://github.com/Inkypen79/device_xiaomi_andromeda
If anyone wants to build a custom rom possibly lineage i have found the trees hopefully this does help, lineage is the easiest so yeah
Current lead Dev is @Inkypen, if anyone else has any idea or wants to contribute here is the group chat
https://t.me/mimix3_5G
How I can help with this?
ZigmaInvader said:
How I can help with this?
Click to expand...
Click to collapse
honestly edit the respitory because so far they dont work i have made few files but keep in mind i literally borrowed them all from the perseus device tree since our device is pretty much identical apart from battery, if you do wanna make changes please know what your doing because i have no clue lol , and hopefully we can get this to boot ONLY edit files in the lineage path because the other paths need to be untouched okay thank you
Quantumkk123 said:
honestly edit the respitory because so far they dont work i have made few files but keep in mind i literally borrowed them all from the perseus device tree since our device is pretty much identical apart from battery, if you do wanna make changes please know what your doing because i have no clue lol , and hopefully we can get this to boot ONLY edit files in the lineage path because the other paths need to be untouched okay thank you
Click to expand...
Click to collapse
there also another difference is processor
Sorry guys I can't lie I think it's a complete mess I will be building a device tree for this device I just need A LOT of time and then I will try building some ROMs for this device reason why it will take so long is because I am learning myself and this will be the first time I am doing it hope it goes successfully for me
Hi guys! I've being making ROMs for the original Mi Mix and decided to take the plunge and get a Mix 3 5G. I've built up these skeleton trees and made LineageOS, but I haven't received my new device yet so I can't test it. It's horribly unoptimised and still has a lot of bloat from unnecessary drivers (hence the 1gb size) and I have no idea if this will even boot but here is the initial build if anyone is brave enough to install it. https://drive.google.com/open?id=1WOsXzgpdA8qTP6QWHi1gNW131dqgdDIC
This is an engineering build to help track down bugs so ADB debugging is enabled as standard. Any logs would be appreciated.
Inkypen said:
Hi guys! I've being making ROMs for the original Mi Mix and decided to take the plunge and get a Mix 3 5G. I've built up these skeleton trees and made LineageOS, but I haven't received my new device yet so I can't test it. It's horribly unoptimised and still has a lot of bloat from unnecessary drivers (hence the 1gb size) and I have no idea if this will even boot but here is the initial build if anyone is brave enough to install it. https://drive.google.com/open?id=1WOsXzgpdA8qTP6QWHi1gNW131dqgdDIC
This is an engineering build to help track down bugs so ADB debugging is enabled as standard. Any logs would be appreciated.
Click to expand...
Click to collapse
Ok I will try it aha can you send me these please because it will save me time from building another lineage device tree lol, my email is [email protected] please accept as I have ubuntu running on my pc now and I will try to fix a few things if that's okay?
Quantumkk123 said:
Ok I will try it aha can you send me these please because it will save me time from building another lineage device tree lol, my email is [email protected] please accept as I have ubuntu running on my pc now and I will try to fix a few things if that's okay?
Click to expand...
Click to collapse
I didn't realise that I didn't have link sharing on, should be ok to download now. I haven't uploaded my tree to GitHub yet, but once I do it will be available at https://github.com/Inkypen79/device_xiaomi_andromeda
Inkypen said:
I didn't realise that I didn't have link sharing on, should be ok to download now. I haven't uploaded my tree to GitHub yet, but once I do it will be available at https://github.com/Inkypen79/device_xiaomi_andromeda
Click to expand...
Click to collapse
Oh aha that's fine man , didn't realise this was android 10 good job man
Quantumkk123 said:
Oh aha that's fine man , didn't realise this was android 10 good job man
Click to expand...
Click to collapse
Don't get too excited yet lol. This LineageOS build is pie, once I know that's stable then I can move to ten. I brought up the original Mi Mix to ten so I have an idea of what's required.
Inkypen said:
Don't get too excited yet lol. This LineageOS build is pie, once I know that's stable then I can move to ten. I brought up the original Mi Mix to ten so I have an idea of what's required.
Click to expand...
Click to collapse
Lmao I realized when it said 16.0 aha that's fine tho still a lot more progress than me
I keep getting this error when trying to flash...the suggestion was to update twrp but 3.3.1-0 is the only one we have available ....
E: String resource 'zip_compatible_err' not found.
Using default value
Zip Treble compatibility error!
Invalid zip file format!
Any suggestions?
i think its my fault lemme just factory reset my phone install stock and see what happens. Yep our twrp is broken as after install it bricks whole device , and I know this isn't from the ROM because basically twrp bricked my phone from reloading to fastboot, it's very broken , but no one has been able to test that out because there hasn't been much to flash recently. Therefore @Inkypen will build some twrps for me to try and flash and see if his builds do work , fingers crossed they will
Quantumkk123 said:
i think its my fault lemme just factory reset my phone install stock and see what happens. Yep our twrp is broken as after install it bricks whole device , and I know this isn't from the ROM because basically twrp bricked my phone from reloading to fastboot, it's very broken , but no one has been able to test that out because there hasn't been much to flash recently. Therefore @Inkypen will build some twrps for me to try and flash and see if his builds do work , fingers crossed they will
Click to expand...
Click to collapse
Seems interesting. I have got mi mix 3 5g, just waiting on unlocking and will sure help it
ptlsajan said:
Seems interesting. I have got mi mix 3 5g, just waiting on unlocking and will sure help it
Click to expand...
Click to collapse
Sure there's a group chat where more info is posted there...updates etc https://t.me/mimix3_5G
I also have a mi mix 3 5g on the way, will be happy to test once i get it, thx alot for you work!
So far I have built a working version of Orange Fox recovery. Still waiting for my device to arrive, then some real work can start
https://www.androidfilehost.com/?fid=4349826312261670861
I should be getting my Mix 3 5G this week, the parcel is allegedly with my local post office already. I'd love to help out to get LineageOS working on it. I have minimum experience having flashed custom ROMs onto my current phone (Mi Max helium) as well as that of my Mrs (Mi 6 sagit), but I'd love to get more involved if possible. I don't need it to be my daily driver immediately, so I just need enough confidence in what we'll be doing here so as not to turn it into an expensive, cute brick The chassis being ceramic, it's already half way there right off the bat, but let's not get any closer please
Please generate LineageOS android 10 from Mi Mix Andromeda
ZigmaInvader said:
Please generate LineageOS android 10 from Mi Mix Andromeda
Click to expand...
Click to collapse
Join the telegram chat if you want any requests
So I'm trying to get halium working for tab 2 (we can get ubuntu touch and maybe even plasma mobile with help of it) and I get this error
Code:
arch/arm/boot/compressed/atags_to_fdt.o: In function `merge_fdt_bootargs':
atags_to_fdt.c:(.text+0x20c): undefined reference to `__stack_chk_fail'
atags_to_fdt.c:(.text+0x210): undefined reference to `__stack_chk_guard'
It seems to be a toolchain error any help?
"It would appear that the -mstack-protector-guard option is only for backwards compatibility with how the stack protector worked in the past. In the past the canary was in a global variable. Later it was switched to TLS. It would appear that the operating system / libc you use either removed or never had support for the global variable canary, so only TLS works.
Don't touch the -mstack-protector-guard option and everything should work. The default should be fine when you use -fstack-protector-all."
"Provide __stack_chk_guard with a random value in c file, avoid using regular values like all zero's or FF's because the stack can easily get these values during any memory operation. Wiki on providing magic number implementation. This __stack_chk_guard will be placed at the top and bottom of the stack, which will be checked during every stack access. Any change in the value implies a corrupted stack and returns with error providing the stack protection.
unsigned long __stack_chk_guard;
void __stack_chk_guard_setup(void)
{
__stack_chk_guard = 0xBAAAAAAD;//provide some magic numbers
}
void __stack_chk_fail(void)
{
/* Error message */
}// will be called when guard variable is corrupted "
"There are two ways to remove this error: 1. From the compiler option disable(comment out) the "stack guard".
Define __stack_chk_guard in you c file.
When you define __stack_chk_guard make sure you provide random value to it. For providing random value you need to pass as an argument to the random function.
For any further detail you can refer to the compiler manual."
"For those that get this error in bare metal software development with a custom linker script, make sure to pass the option -nostdlib option:
gcc -nostdlib
since Ubuntu 16.04 for example enables the stack protection by default on the compiler. man gcc says:
NOTE: In Ubuntu 14.10 and later versions, -fstack-protector-strong is enabled by default for C, C++, ObjC, ObjC++, if none of -fno-stack-protector, -nostdlib, nor -ffreestanding are found.
-fno-stack-protector also solved it for me, but you should likely tell your poor compiler that you are doing baremetal stuff to prevent other such problems.
I'm guessing this is because the feature relies on symbols which are normally defined if a linker script is not given? But TODO I found no mention of those symbols by dumping the default linker script with:
aarch64-linux-gnu-gcc -Wl,-verbose main.c
so I'm not sure.
I grepped GCC 6.4.0 source code and it suggests that the symbol comes from libgcc2.c at gcc/doc/tm.texi:
The default version of this hook creates a variable called @samp{__stack_chk_guard}, which is normally defined in @file{libgcc2.c}."
Click to expand...
Click to collapse
source: https://stackoverflow.com/questions/27290086/gcc-canaries-undefined-reference-to-stack-chk-guard
i cant wait to use this and your other project (sailfishos)!
wizzer48 said:
i cant wait to use this and your other project (sailfishos)!
Click to expand...
Click to collapse
Yes even I can't wait for both as there is no latest development for our tab !!!
Arc android said:
Yes even I can't wait for both as there is no latest development for our tab !!!
Click to expand...
Click to collapse
Halium doesnt seem to work i tried but to no avail
Mithil17 said:
Halium doesnt seem to work i tried but to no avail
Click to expand...
Click to collapse
Its OK at least you tried to build it !!
Hey I have a great idea Mithil17, can you try to build MIUI 7 for galaxy tab 2? There was an attempt to build it earlier but it wasn't successful.
Arc android said:
Hey I have a great idea Mithil17, can you try to build MIUI 7 for galaxy tab 2? There was an attempt to build it earlier but it wasn't successful.
Click to expand...
Click to collapse
MIUI ??? Why do you wanna china bloadware sooo badly?? what's wrong with LOS or any other bloadware free ROMs?
Plus it's gonna be laggy as h3ll... done and forgotten.
drnightshadow said:
MIUI ??? Why do you wanna china bloadware sooo badly?? what's wrong with LOS or any other bloadware free ROMs?
Plus it's gonna be laggy as h3ll... done and forgotten.
Click to expand...
Click to collapse
Yeah I know it's Chinese but it looks beautiful. You'll know it if you have tried mini 5 for tab 2.
Arc android said:
Yeah I know it's Chinese but it looks beautiful. You'll know it if you have tried mini 5 for tab 2.haha
Click to expand...
Click to collapse
Haha, no thank you! I'm happy with LOS and RR ROMS. I own redmi note 5 pro but never used MIUI [email protected], I unlocked bootloader and installed LOS asap. I like to have privacy in my hand and I hate when OS wanna rape my privacy. My privacy isn't on sale.
drnightshadow said:
Haha, no thank you! I'm happy with LOS and RR ROMS. I own redmi note 5 pro but never used MIUI [email protected], I unlocked bootloader and installed LOS asap. I like to have privacy in my hand and I hate when OS wanna rape my privacy. My privacy isn't on sale.
Click to expand...
Click to collapse
If you actually want this much privacy, here's something for you : https://androidfilehost.com/?fid=17248734326145705104
An unofficial /e/os build for your device. Just trying to help you in case you didn't know this. That's all !
Arc android said:
If you actually want this much privacy, here's something for you : https://androidfilehost.com/?fid=17248734326145705104
An unofficial /e/os build for your device. Just trying to help you in case you didn't know this. That's all !
Click to expand...
Click to collapse
whyred = Redmi Note 5. Not SGT2
Are you sure? It can brick device
levider said:
whyred = Redmi Note 5. Not SGT2Are you sure? It can brick device
Click to expand...
Click to collapse
Note 5/pro = whyred that's what Google says.
Also in the above link, it is made for redmi note 5 pro
Official /e/ forum link : https://www.google.com/url?sa=t&sou...FjACegQIBBAC&usg=AOvVaw1iyAyl2Ur__Xid-tw1cRCz
I hope I am not doing anything wrong
Arc android said:
Note 5/pro = whyred that's what Google says.
Also in the above link, it is made for redmi note 5 pro
Click to expand...
Click to collapse
Dude, this is not Redmi Note 5 thread.
Update: It boots now, Sources are in https://github.com/Halium/projectmanagement/issues/238 no ui still
Mithil17 said:
Update: It boots now, Sources are in https://github.com/Halium/projectmanagement/issues/238 no ui still
Click to expand...
Click to collapse
So we can install it now ???? !!!!!
Arc android said:
So we can install it now ???? !!!!!
Click to expand...
Click to collapse
Well you can just install it, it just boots, no ui/display
Mithil17 said:
Well you can just install it, it just boots, no ui/display
Click to expand...
Click to collapse
So it means even if I install it, it can't be operated. Why some things are way too difficult for tab 2 ?? I mean miui7, sfos, treble, Oreo and now haloum are ported to other devices too that are mostly similar to ours but running them on tab 2 is a bit more difficult.
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
Does anyone know if there is any custom ROM out yet for Oneplus 10 pro?
batterylifesucks said:
Does anyone know if there is any custom ROM out yet for Oneplus 10 pro?
Click to expand...
Click to collapse
if they don't, buy another phone.
Kosta26 said:
if they don't, buy another phone.
Click to expand...
Click to collapse
HAHHAH, ok thanks
There's potentially a few in development, but it's moving along slowly.
The clear answer is "no" and I don't see any signs of that changing any time soon (if at all). Someone started working on it, but it looks like they lack the expertise to see it through, so don't count on any custom ROMs.
However, this seems to be an issue that is more widespread, not just OnePlus phones are affected. I would actually be interested if there are any new Android phones that have custom ROMs readily available. All the official Lineage OS devices seem to be older.
Too much thing is missing guys.released kernel source has missing scripts and header files.any custom rom group don't have linaro waipo built in sources.Just relax and give time to developers.
metrixx02 said:
Too much thing is missing guys.released kernel source has missing scripts and header files.any custom rom group don't have linaro waipo built in sources.Just relax and give time to developers.
Click to expand...
Click to collapse
hows that coming along?
eviling said:
hows that coming along?
Click to expand...
Click to collapse
Issue is that developers don't have a free and secure way of recovering their devices if it bricks. The MSM tool requires authentication with OnePlus which have deemed the tool as internal use only.
We're stuck until either someone cracks it or OnePlus makes the MSM tool public.
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.