I am using Magisk 20.4 and trying to mount /system on a Google Pixel running Android 10.
I have tried using:
Code:
adb shell su -c mount -o rw,remount /system
that gives: me
mount: '/system' not in /proc/mounts
Click to expand...
Click to collapse
The following also do not work:
Code:
adb shell su -c mount -o rw,remount /
'/dev/root' is read-only
Click to expand...
Click to collapse
Code:
adb shell su -c mount -o rw,remount /sbin/.magisk/mirror/system_root
'/sbin/.magisk/block/system_root' is read-only
Click to expand...
Click to collapse
I was also curious whether stuff in /sbin/.magisk/rootdir/system/ can actually override stuff in /system/ but that doesn't seem to be the case..
Has anyone managed to mount /system on Android 10? Is this issue specific to Google Pixel?
Cheers,
Paschalis
Its due to EXT4 dedup filesystem (it's not writable).
This was pointed out by magisk developer john wu, more info: https://mobile.twitter.com/topjohnwu/status/1170404631865778177
So it's impossible? Even with TWRP?
Turns out I don't need to mount /system.
I wanted this so I could ship my modified version of libart.so, libart-compiler.so and dex2oat (which are in APEX), as well some other external compiler libraries and tools.
So I've written some magisk modules, and it works really well. Even for the runtime apex. I'm impressed!
The only reason someone might need to mount /system is if he/she uses an app/tool that needs it.
The only way to make changes to the /system partition is to make a Magisk module that mounts the files you modified instead of the original ones.
Paschalis said:
Turns out I don't need to mount /system.
I wanted this so I could ship my modified version of libart.so, libart-compiler.so and dex2oat (which are in APEX), as well some other external compiler libraries and tools.
So I've written some magisk modules, and it works really well. Even for the runtime apex. I'm impressed!
The only reason someone might need to mount /system is if he/she uses an app/tool that needs it.
Click to expand...
Click to collapse
Well I need to mount because of Link2sd. Is there any way to do it?
jcruzcruz35 said:
Well I need to mount because of Link2sd. Is there any way to do it?
Click to expand...
Click to collapse
No, on Android 10 the /system partition is locked at read only, the only way to make modifications to the /system partition is to make a Magisk module.
JJcoder said:
No, on Android 10 the /system partition is locked at read only, the only way to make modifications to the /system partition is to make a Magisk module.
Click to expand...
Click to collapse
Sht, it has to be especially make it for each smartphone? Or you think there gonna be eventually a Module for everyone?
jcruzcruz35 said:
Sht, it has to be especially make it for each smartphone? Or you think there gonna be eventually a Module for everyone?
Click to expand...
Click to collapse
I'm sure eventually there will either be a universal Module, Or a way to resize the partition and change the file system to make it writable.
JJcoder said:
...Or a way to resize the partition and change the file system to make it writable.
Click to expand...
Click to collapse
Resized works, but how to change the file system to make it writable?
vagyula said:
Resized works, but how to change the file system to make it writable?
Click to expand...
Click to collapse
How did you resize it?
Code:
$ su
# mount --remount / -w
ONLY makes effert to terminal, which means other apps like Solid Explorer, Root Explorer etc are still r/o. Some roms(Pixel Experience tested, including stock) are not working.
hardplastic said:
Code:
$ su
# mount --remount / -w
Only works in terminal
Click to expand...
Click to collapse
It doesn't work on Android 10, you will just get the error:
Code:
'/dev/root' is read only
JJcoder said:
It doesn't work on Android 10, you will just get the error:
Code:
mount: '/dev/root' not user user mountable in fstab
Click to expand...
Click to collapse
Reboot your device and try again, it works both two of my devices in Android 10
hardplastic said:
Reboot your device and try again, it works both two of my devices in Android 10
Click to expand...
Click to collapse
Nope, Same error bcuz it is locked at read only.
JJcoder said:
Nope, Same error bcuz it is locked at read only.
Click to expand...
Click to collapse
That's weird, have you checked your operation is in the terminal? It only makes /system rw to terminal, other apps still r/o .
hardplastic said:
That's weird, have you checked your operation is in the terminal? It only makes /system rw to terminal, other apps still r/o .
Click to expand...
Click to collapse
No, you can't just simply Type a command and have it mount as rw...
If you want to make modifications you have to make a Magisk Module which uses Magic Mount to mount the modified files over the original ones.
I have no idea how u got it to work, I would like to see proof..
JJcoder said:
No, you can't just simply Type a command and have it mount as rw...
If you want to make modifications you would have to make a Magisk Module which uses Magic Mount to mount the modified files over the original ones.
Click to expand...
Click to collapse
Then how do you explain that?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
hardplastic said:
Then how do you explain that?
Click to expand...
Click to collapse
Let me see that u are on stock Android 10
JJcoder said:
Let me see that u are on stock Android 10
Click to expand...
Click to collapse
Related
I got bored so I decided to compile the latest Donut source.
Please make a Nandroid backup before you flash any of this! Just in case.
To add Google apps, check out the Google Stuffer, or similar scripts.
Features:
- Latest Donut source compiled for the HTC-Dream
- Stock (No Google apps whatsoever)
- Otherwise fully working (report bugs if you find any though)
Bugs
- Home key and Phone key not working (I'll try to get them to work)
Instructions
Code:
Unzip "Android-1.6_r1.zip"
fastboot erase userdata
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
Only the system.img and boot.img is needed for the flashing procedure, but I included the other images just in case someone wants to take a look at them.
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download
http://www.mediafire.com/?ntdmo0ulxdr
Enjoy~
Is this a root rom?
Great job now we proved to Google that we don't need them
This does not affect the recovery.img. So if you have Cyanogen's 1.4 recovery.img you will still have root.
Although you won't have apps like SuperUser, since it's Stock.
Good Job!
I want to try this, but I dont ADB (yet) can this be flashed thru recovery??
I used Tmobile contacts backup, so I can see if it will restore my contacts.
Chevy
chevycowboyusa said:
I want to try this, but I dont ADB (yet) can this be flashed thru recovery??
I used Tmobile contacts backup, so I can see if it will restore my contacts.
Chevy
Click to expand...
Click to collapse
Yes you can use the recovery console.
Move the files to the root of your sdcard first though.
Code:
mount sdcard [enter]
mount system [enter]
flash_image system /sdcard/system.img [enter]
flash_image boot /sdcard/boot.img [enter]
reboot
any way you could make this a update.zip. so we can just use cyan recovery to flash the zip?
Only things that I noticed to be not working are the home key and phone key.
I'll investigate further.
is this experimental
i feel i shouldnt be looking at this. its so naked
Yes this is experimental since it's compiled from a non-finalized source.
I know this ROM is naked. But since Google is taking action against the distribution of their closed-source apps, everyone has to release Stock ROMs now.
Bavilo said:
Yes this is experimental since it's compiled from a non-finalized source.
I know this ROM is naked. But since Google is taking action against the distribution of their closed-source apps, everyone has to release Stock ROMs now.
Click to expand...
Click to collapse
i know i know its just so different from what were used to seeing.. but this is the new standard now(unless google changes! ..) so might as well get used to it =/
this looks very interesting. i will probably wait to use this until i see that it works with a few of the scripts that are being developed.
DavidChill said:
this looks very interesting. i will probably wait to use this until i see that it works with a few of the scripts that are being developed.
Click to expand...
Click to collapse
I'm sure someone will create a script that's compatible with Donut. Since we have all of the proprietary files necessary.
Script makers, do your magic please ;D
Weird
I keep getting an invalid argument when trying to mount the system in recovery terminal.
i typed
#mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
and
#mount -o remount,rw /dev/block/mtdblock3 /system
and
#mount -o remount,rw /dev/block/mmcblk0p2 /system
I seem to b having a brain fart.
Can i flash thru terminal emulator? edit: [I figured this one out.... NOPE!]
Chevy
It was VERY hard on my eyes to see an actual "bare bones" ROM already. Use to all the bells and whistles. I guess this is what we will have to work with right now till something is figured out. I really like this idea. Has ANYONE tested this yet with any google apps script. I really dont wanna try this until I know that we can get everything. I'll keep my eye on this though. Thanks for coming up with something so quickly
chevycowboyusa said:
I keep getting an invalid argument when trying to mount the system in recovery terminal.
i typed
#mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
and
#mount -o remount,rw /dev/block/mtdblock3 /system
and
#mount -o remount,rw /dev/block/mmcblk0p2 /system
I seem to b having a brain fart.
Can i flash thru terminal emulator? edit: [I figured this one out.... NOPE!]
Chevy
Click to expand...
Click to collapse
To mount anything in the recovery console you just need to type "mount system" for instance...or mount sdcard.
wow.. this is the start of more freedom... Rebenga!!!!
Weird things
Wow.... Something must have been messed up....
I wiped and reflashed cm 4.1.11.1... then I went to recovery terminal (after booting)
was able to [mount system] [mount sdcard] flashed system and boot imgs.
Rebooted and went thru g1 screen, then black, and then another g1 screen, then automatically went back to recovery.... {Weird!!!}
any advice?
chevycowboyusa said:
Wow.... Something must have been messed up....
I wiped and reflashed cm 4.1.11.1... then I went to recovery terminal (after booting)
was able to [mount system] [mount sdcard] flashed system and boot imgs.
Rebooted and went thru g1 screen, then black, and then another g1 screen, then automatically went back to recovery.... {Weird!!!}
any advice?
Click to expand...
Click to collapse
Yea that is weird. I only tried flashing the images with fastboot, and erasing the userdata.
I'm working on fixing the home and phone key atm.
http://forum.xda-developers.com/showthread.php?t=817528
It works fine. Rename it from signed_YouTube.apk to YouTube.apk and replace with one in /system/app. Make sure that permissions are set when overwriting.
Works like a charm and looks quite good, thanks for this!
qwer23
Sent from my rooted X10i using XDA App
yep great mod
widget works great also.
Is it actually working for you ??
I am getting network error 400, both on GSM/3G and on WiFi...
There's some sort of Log-In bug, basically don't sign into your youtube account while using this mod and you should be fine. Hopefully there will be a fix for that soon.
Thanks, looks much better...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
...and had no trouble signing in. Did those that have uninstall the old app first?
Yeah looks great!
Thanks 4 share
Sent from my X10i using XDA App
XperiaX10iUser said:
Thanks, looks much better...
...and had no trouble signing in. Did those that have uninstall the old app first?
Click to expand...
Click to collapse
XperiaX10iUser: how'd you go about installing it? I'm still a noob when it comes to ADB and such (and yes, I did read your guide ), and want to make sure I'm not going to mess anything up installing this.
also, google geniewidget.apk (news and weather) also works. this one you can install it thru any file manager.
saltorio said:
XperiaX10iUser: how'd you go about installing it? I'm still a noob when it comes to ADB and such (and yes, I did read your guide ), and want to make sure I'm not going to mess anything up installing this.
Click to expand...
Click to collapse
Ok its easy:
Get to adb (shell):
$su
#mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
#rm /system/app/YouTube.apk
Then go to settings -> applications -> find com.android.youtube.apk and uninstall it
Reboot your phone
Then get to adb (shell):
$su
#mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
Install /sdcard/(where the modded .apk is)/signed_youtube.apk /system/app
Reboot phone
I did the permissions with root explorer (rw-r--r--)
How to do that with adb... idk sry
Sent from my X10i using XDA App
saltorio said:
XperiaX10iUser: how'd you go about installing it?
Click to expand...
Click to collapse
This is how I did it, in a command window on the laptop...
cd C:\android-sdk-windows\tools
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb shell rm system/app/YouTube.apk
adb uninstall com.google.android.youtube
adb push Youtube.apk /sdcard/Youtube.apk
adb shell dd if=/sdcard/Youtube.apk of=/system/app/Youtube.apk
...but if your Tools folder is elsewhere just change the first line.
PoTi_96 said:
Ok its easy:
I did the permissions with root explorer (rw-r--r--)
Click to expand...
Click to collapse
That should be:
# busybox chmod 644 <file>
XperiaX10iUser said:
This is how I did it, in a command window on the laptop...
cd C:\android-sdk-windows\tools
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb shell rm system/app/YouTube.apk
adb uninstall com.google.android.youtube
adb push Youtube.apk /sdcard/Youtube.apk
adb shell dd if=/sdcard/Youtube.apk of=/system/app/Youtube.apk
...but if your Tools folder is elsewhere just change the first line.
Click to expand...
Click to collapse
Wonderful. Worked beautifully, and I was able to login to my profile OK as well.
Thanks!
it didnt worked for me, failed to install.
fogozito said:
it didnt worked for me, failed to install.
Click to expand...
Click to collapse
Make sure to put the .apk in C:\android-sdk-windows\tools, and that it's named "YouTube.apk"
saltorio said:
Make sure to put the .apk in C:\android-sdk-windows\tools, and that it's named "YouTube.apk"
Click to expand...
Click to collapse
Thanks for that I didn't think I need them in both places.
Strange, after it worked perfectly for several hours it now force closes on start every time. Any suggestions?
Btw. I installed with root explorer. I just renamed the apk to YouTube.apk, then did overwrite the old one and set the same permissions that were set in the original youtube app. I was able to log in, too.
Sent from my rooted X10i using XDA App
Edit: reinstall did solve the problem for now. Let's see if it'll last
I also installed it successfully and it was running fine for a bit then suddenly now it is force closing a lot. I had to reboot the phone because it was stuck in a FC loop when I used the search function on the widget.
Wiping the data and resigning in seems to fix it. I guess there could be something wrong with account handling.
qwer23 said:
Strange, after it worked perfectly for several hours it now force closes on start every time. Any suggestions?
Btw. I installed with root explorer. I just renamed the apk to YouTube.apk, then did overwrite the old one and set the same permissions that were set in the original youtube app. I was able to log in, too.
Sent from my rooted X10i using XDA App
Edit: reinstall did solve the problem for now. Let's see if it'll last
Click to expand...
Click to collapse
sierratango88 said:
I also installed it successfully and it was running fine for a bit then suddenly now it is force closing a lot. I had to reboot the phone because it was stuck in a FC loop when I used the search function on the widget.
Wiping the data and resigning in seems to fix it. I guess there could be something wrong with account handling.
Click to expand...
Click to collapse
Did you guys sign in to your YouTube profile in the app? I know there is a problem being reported in the original thread related to signing in.
I did sign in, and it was worked fine initially, but now I'm seeing the same issue as you guys are reporting.
I have two separate issues which I believe are caused by the same thing.
1. When I try to alter platform.xml in the /system/etc/permissions folder via ES File Explorer to enable 3rd party apps to have write capability to the SD card, the edit is unsuccessful and my phone reboots. When I pull a copy of the file to my PC, alter it, and then try to push it via ADB, the same thing happens. I previously used the ADB pull/push method to edit my hosts file and had success with that after doing it while in Recovery, but this time around both ways (in recovery and with the device booted up) result in my device rebooting. For the SD card fix, I've also tried the app that does it for you and encounter the same issue.
2. When attempting to update the SuperSU binary, the update fails my device reboots. This happens with either update method - normal and recovery.
So both issues seem to have the same root cause... my phone will not allow any editing of system files. Anyone have any suggestions?
For reference I'm on a Galaxy Note 4 (model SM-N910T) on T-Mobile.
Baseband version N910TUVU1ANJ7
Android version 4.4.4 (stock ROM)
Kernel version 3.10.0-2796035
Build number KTU84P.N910TUVU1ANJ7
I'm also running Wanam Xposed - not sure if that has anything to do with anything but just fyi.
Thanks
Gakuseinozen said:
I have two separate issues which I believe are caused by the same thing.
1. When I try to alter platform.xml in the /system/etc/permissions folder via ES File Explorer to enable 3rd party apps to have write capability to the SD card, the edit is unsuccessful and my phone reboots. When I pull a copy of the file to my PC, alter it, and then try to push it via ADB, the same thing happens. I previously used the ADB pull/push method to edit my hosts file and had success with that after doing it while in Recovery, but this time around both ways (in recovery and with the device booted up) result in my device rebooting. For the SD card fix, I've also tried the app that does it for you and encounter the same issue.
2. When attempting to update the SuperSU binary, the update fails my device reboots. This happens with either update method - normal and recovery.
So both issues seem to have the same root cause... my phone will not allow any editing of system files. Anyone have any suggestions?
For reference I'm on a Galaxy Note 4 (model SM-N910T) on T-Mobile.
Baseband version N910TUVU1ANJ7
Android version 4.4.4 (stock ROM)
Kernel version 3.10.0-2796035
Build number KTU84P.N910TUVU1ANJ7
I'm also running Wanam Xposed - not sure if that has anything to do with anything but just fyi.
Thanks
Click to expand...
Click to collapse
You probably need to remount /system as rw. Use this in a shell:
Code:
mount -o rw,remount rootfs /
ИΘΘK¡€ said:
You probably need to remount /system as rw. Use this in a shell:
Code:
mount -o rw,remount rootfs /
Click to expand...
Click to collapse
I went into the terminal emulator app, typed su and then the command you listed and even after that I'm still having the same problem. Any other ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Gakuseinozen said:
I went into the terminal emulator app, typed su and then the command you listed and even after that I'm still having the same problem. Any other ideas?
Click to expand...
Click to collapse
Yes, try this:
Code:
mount -o rw,remount /system
ИΘΘK¡€ said:
Yes, try this:
Code:
mount -o rw,remount /system
Click to expand...
Click to collapse
No luck after that one either.
Any more ideas?
ИΘΘK¡€ said:
You probably need to remount /system as rw. Use this in a shell:
Code:
mount -o rw,remount rootfs /
Click to expand...
Click to collapse
Did you try uninstalling the root from the unlockroot pro and rooting it again using the [super su update.zip]
try this it might work
instinctblade said:
Did you try uninstalling the root from the unlockroot pro and rooting it again using the [super su update.zip]
try this it might work
Click to expand...
Click to collapse
Are you saying to un-root and root again? Is 'unlockroot pro' an app?
Thanks
Gakuseinozen said:
Are you saying to un-root and root again? Is 'unlockroot pro' an app?
Thanks
Click to expand...
Click to collapse
Yes "Unlock-Root" is a pc software which can Unroot & Root your device
instinctblade said:
Yes "Unlock-Root" is a pc software which can Unroot & Root your device
Click to expand...
Click to collapse
That wasn't the method I used to root in the first place. Does that matter?
Anyone else have any ideas? I tried posting logs in the SuperSU update failure thread, with the logic that if I get that issue fixed my other issue will be resolved also, but Chainfire hasn't responded to any of the requests in a while.
Gakuseinozen said:
Anyone else have any ideas? I tried posting logs in the SuperSU update failure thread, with the logic that if I get that issue fixed my other issue will be resolved also, but Chainfire hasn't responded to any of the requests in a while.
Click to expand...
Click to collapse
Try older version of supersu? Or could it be something inside the supersu setting? Just a thought.
SGs3n SlimKat9.0(Android-Andi)/F_Kernel1.3(Fred6681)/SuperSU2.4?(ChainFire)/BusyBoxX33(MaxIce)
Naimlaaa said:
Try older version of supersu? Or could it be something inside the supersu setting? Just a thought.
SGs3n SlimKat9.0(Android-Andi)/F_Kernel1.3(Fred6681)/SuperSU2.4?(ChainFire)/BusyBoxX33(MaxIce)
Click to expand...
Click to collapse
Don't think an older version would help since i started having this problem with the version I'm currently running. I also went through the SuperSu settings and tried a few different things but nothing helped. I changed Default access from "grant" to "prompt", changed Mount namespace separation to "all root processes share inits mount namespace" and enabled "trust system user".
Not sure what else I could try really.
instinctblade said:
Did you try uninstalling the root from the unlockroot pro and rooting it again using the [super su update.zip]
try this it might work
Click to expand...
Click to collapse
Did you try this method yet? Also can try VoodooOTA rootkeeper.
And/or remove xposed first?
Im a noob in this but just trying to share some idea though.
SGs3n SlimKat9.0(Android-Andi)/F_Kernel1.3(Fred6681)/SuperSU2.4?(ChainFire)/BusyBoxX33(MaxIce)
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 your device as R/W and fully debloat your device and customize your MIUI experience to make it run as smooth as silk!
MIUI 12 is great but it has a little bit too much bloatware.
Be very careful and make lots of backups before messing with your System ! One small error could cause irreversible bootloop!
Enjoy debloating and customizing your fully read/write-able Android device!
NOTE: Before launching this script make sure you've got full read/write (rw) access to the /data partition by first decrypting and then mounting /data partition as r/w !
Visit official project thread
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PS C:\adb> adb shell "ls -Alg /dev/block/by-name | grep 'super'"
lrwxrwxrwx 1 root 16 1970-02-02 16:40 super -> /dev/block/sda23
POCO X3 pro
/
so does this work on x3 pro?
edit, it didnt. threw some devblock warnings about not mounting
@gsser Yes it works! Try latest version! Good luck!
lebigmac said:
@gsser it can work depending on how much effort you decide to put into it.
Click to expand...
Click to collapse
well if it is like that, then why is there even a non complete script when it can be done by the owner...
And since you have already asked how it is on x3 pro im saying it doesnt work.
"I'm looking forward to hearing from the Poco X3 Pro users how the script performs on your device."
It is mostly because of current recoveries for x3 pro doesnt support /data yet, but the script can use sdcard rather than internal storage.
@gsser Thanks for the screenshot and feedback. Please download latest v1.32
Feel free to send me your log files if you get any errors and I'll take a look. Thanks.
lebigmac said:
@gsser Thanks for the screenshot and feedback. Please download latest v1.31 that I uploaded today. And feel free to edit the script with your favorite text editor and change the super image dump path in line #333 to this. Then save file.
Code:
sDumpTarget="/sdcard/super_original.bin"
Feel free to send me your log files if you get any errors so I can take a look. Thanks.
Click to expand...
Click to collapse
Only lines i could find about data were these and i edited the path to my sdcard, flashed it.
Edit just seen you edited your reply. Ill try
I'm not 100% sure if your changes will work properly. Feel free to give it a try.
Keep in mind if you change variables the script might not work as expected.
The reason why the script is installed to /data/local/tmp is because in /scard path you don't have execution permission. That's why it's better to launch script from /data/local/tmp
Poco x3 pro recovery don't have full r/w access to /data/local/tmp ?! That's crazy!
You can try launch script directly from android and it should work as expected.
lebigmac said:
I'm not 100% sure if your changes will work properly. Feel free to give it a try.
You can also use /sdcard path it should be the same thing as what you wrote. Good luck.
Please report back any errors thanks.
Keep in mind if you change LOC variable you must also copy the whole script folder to that new location.
The reason why the script is installed to /data/local/tmp is because in /scard path you don't have execution permission. Is better to launch script from /data/local/path
You don't have full access to /data/local/path in poco x3 pro?
Click to expand...
Click to collapse
This is how the folder looks rightnow. Do i need to do anything about it? Also what is LOC :c
Edit nvm, lol im blind
Not sure what you're trying to do but that path is totally messed up
Just run script in android operating system as described in the instructions if you don't have full read write access to /data/local/tmp from custom recovery
Have you tried manually mounting /data partition in orange fox? Maybe it's not mounted and that's why /data/local/tmp is unavailable.
lebigmac said:
Not sure what you're trying to do but that path is totally messed up
Click to expand...
Click to collapse
Yeah ill just change than only line
lebigmac said:
Not sure what you're trying to do but that path is totally messed up
Just run script in android operating system as described in the instructions if you don't have full read write access to /data/local/tmp from custom recovery
Have you tried manually mounting /data partition in orange fox? Maybe it's not mounted and that's why /data/local/tmp is unavailable.
Click to expand...
Click to collapse
All available recoveries have issue mounting data, some cant even mount mtp.
Ill try android one and see what happens.
If your /data partition is not mounted then you can try manually mounting /data partition before running script.
mount /data
lebigmac said:
LOC is a safety path check feature I had to implement because some folks were launching the script from God knows where and overwriting God knows what with dd lol.
Did you try manually mounting /data partition before running script?
mount -o remount,rw /data
Click to expand...
Click to collapse
Yeah, ill try android version then flash it with fastboot but im a bit confused. Do i execute this command or do i need to do other things? Sorry im a noob at these things
./makesysrw.sh in=./files/super/super_original.bin out=./custom/path/super_fixed.bin size=50
Actually ill stop here since i dont get the whole thing, i dont understand at all :/ once i tried to use linux and it was not fun for me... Im bad with command lines and scripts
After copying script folder into /data/local/tmp/
open command prompt and type this
Bash:
adb shell
su
cd /data/local/tmp/systemrw_1.32
chmod +x ./systemrw.sh
./systemrw.sh size=50
lebigmac said:
After installing script folder into /data/local/tmp/
open command prompt and type this
Bash:
adb shell
su
cd /data/local/tmp/makesysrw_1.31
chmod +x ./makesysrw.sh
./makesysrw.sh size=25
Click to expand...
Click to collapse
now this is what i like
are you sure your bootloader is unlocked?
now do i need to flash the super_fixed.bin in script folder's files folder in fastboot? original super is approx. 8gb and fixed one is nearly half of it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As a part of root today i installed twrp in note 11 pro+ 5g everything works fine but mount storage not showing slider to confirm the action Anyone can help please reply
sachinp81 said:
View attachment 5821791As a part of root today i installed twrp in note 11 pro+ 5g everything works fine but mount storage not showing slider to confirm the action Anyone can help please reply
Click to expand...
Click to collapse
What slider and what for? At this point, it never existed.
arraki said:
What slider and what for? At this point, it never existed.
Click to expand...
Click to collapse
How to mount the system then
sachinp81 said:
How to mount the system then
Click to expand...
Click to collapse
In order to mount logical partitions in RW, you must first transfer the entire system to RW, for example, with this one.
[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
But this is not enough so that you can do something with these partitions in recovery, they will need to be through the terminal, it is located point "advanced", mount manually. To mount systems, you must write in the terminal
mount -o rw / system_root
To mount other partitions
mount -o rw / partition name (product, system_ext, vendor)
arraki said:
In order to mount logical partitions in RW, you must first transfer the entire system to RW, for example, with this one.
[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
But this is not enough so that you can do something with these partitions in recovery, they will need to be through the terminal, it is located point "advanced", mount manually. To mount systems, you must write in the terminal
mount -o rw / system_root
To mount other partitions
mount -o rw / partition name (product, system_ext, vendor)
Click to expand...
Click to collapse
So after this command mount -o rw / system_root i get rw system and can change file from system folder without following arraki thread script
sachinp81 said:
So after this command mount -o rw / system_root i get rw system and can change file from system folder without following arraki thread script
Click to expand...
Click to collapse
No, without transferring the system to RW, nothing can be done in recovery either.
arraki said:
No, without transferring the system to RW, nothing can be done in recovery either.
Click to expand...
Click to collapse
Universal rw zip download link
sachinp81 said:
So after this command mount -o rw / system_root i get rw system and can change file from system folder without following arraki thread script
Click to expand...
Click to collapse
I think that's not gonna work for my phone my storage type is f2fs
sachinp81 said:
I think that's not gonna work for my phone my storage type is f2fsView attachment 5822641
Click to expand...
Click to collapse
He's all like that.What exactly do you not get?
arraki said:
He's all like that.What exactly do you not get?
Click to expand...
Click to collapse
I wanna rw system as you mentioned f2fs support will come in quarter 2023 and my data shows f2fs so i am confused it will work with my device or not
sachinp81 said:
I wanna rw system as you mentioned f2fs support will come in quarter 2023 and my data shows f2fs so i am confused it will work with my device or not
Click to expand...
Click to collapse
And here data?
You don't need it,the script translates super and all the sections in it in RW.
Read carefully.If you flash the script through recavere,then at all will do everything automatically.
Any chance of bootloop or brick i have note 11 pro plus 5g veux, 8,256 gb
With a/b partition
sachinp81 said:
Any chance of bootloop or brick i have note 11 pro plus 5g veux, 8,256
Click to expand...
Click to collapse
No,this script is universal,it does not have binding to a specific model.
If you're so scared, you can make a backup of super section,if something doesn't work,just restore it from the backup.
One more question user data will remain or format after script done
sachinp81 said:
One more question user data will remain or format after script done
Click to expand...
Click to collapse
Nothing will happen to the datа section, and nothing needs to be done with it.
not working for me
sachinp81 said:
View attachment 5823259not working for me
Click to expand...
Click to collapse
That's right, the script is flashing a new super, so after that the recovery writes like that, you can reboot the recovery and it will see everything, or just reboot into the system
arraki said:
That's right, the script is flashing a new super, so after that the recovery writes like that, you can reboot the recovery and it will see everything, or just reboot into the system
Click to expand...
Click to collapse
Tried but not showing anything
sachinp81 said:
Tried but not showing anything
Click to expand...
Click to collapse
Both ways nothing