Database Info

Ash as login shell

Hi All,
The Ash shell provides a few advantages over the Android default sh shell such as command history and cursor handling at the prompt. There are other benefits, but these are the first that come in most handy (to me).
The following tutorial will get you ash as the login shell with as yet no ill effects:
Note: that in my case, I'm using my android2sd construct and thus this modification is being done to my active overlay profile setup, thus to undo it I can simply boot into "safe\\normal" mode and undo the changes without possibly locking me out of the console should it have failed (which it didn't) But you can edit the Android /system/bin/sh file in this manner directly.
Ash as Login Shell:
OK, make the /system fs read-write:
mount -o remount,rw /system
Click to expand...
Click to collapse
Note: that the fs type is not needed, and in my case is not yaffs but ext3, Android will figure it out proper.
Next,
cp -a /system/bin/sh /system/bin/sh0
Click to expand...
Click to collapse
(this is for backup purposes and allows us to undo the change if so desired, or delete it if no longer needed).
Note: I'm using JF1.51 roms, so busybox ash is available as /system/xbin/bb/ash, so that is what I am using here; use ash however you are able to access it.
echo "#!/system/xbin/bb/ash">/system/bin/sh
echo "/system/xbin/bb/ash \[email protected]">>/system/bin/sh
Click to expand...
Click to collapse
Please note the use of (redirect\\overwrite)> and (redirect\\append)>>.
This will overwrite sh with a script to load the desired shell, executing any command-line arguments passed, and preserve the permissions of the original sh file. You can manually set the permissions the same as they are for our sh0 backup if the permissions (root.shell)(0755) don't seem to keep.
Finally reset the read-only state of /system:
mount -o remount,ro /system
Click to expand...
Click to collapse
Now if you shell-in\\telnet-in you should get the ash prompt which unlike the Android sh default prompt, includes the present working directory(pwd) ie: '/#' instead of just '#'.
Note: A reboot should not cause the loss of the modification, but if does, copy the new sh script to your /data/local/bin location or something and copy it back via boot script or something.
Shell Scripts:
If you're like me, you discovered that Android didn't need the interpreter declaration comment in scripts, and thus may not have used them...Well, you will need to update your scripts to include them by adding something similar to the following as the first line of your scripts:
#!/system/xbin/bb/ash
Click to expand...
Click to collapse
Again, please note that I am using JF1.51 roms and the location of the busybox ash shell is what I'm listing; put the full location to the shell you intend to use as this location.
Without the interpreter declaration, ash simply complains 'not found' at the first command, as ash doesn't know how to interpret the script, and doesn't seem to default to the login shell.
Hope someone finds this helpful!

sweet. This is going to be very useful

BAM. thats sexy. i just did this on CM3.6.7.1. works like a charm.

scratches head. i'm lost. what does this do and how does this make my g1 better?

temporizer said:
scratches head. i'm lost. what does this do and how does this make my g1 better?
Click to expand...
Click to collapse
im not sure about the other features, but the one i installed it for is to have your working directory in front of ur prompt. ex:
Code:
/# cd /sdcard
/sdcard # cd /system/sd
/system/sd #
etc...
EDIT: Also, if you use ConnectBot, you'll notice with the regular sh, if u scroll up with tracball, you get BS characters on the prompt. with THIS one, when you scroll up, you get last command entered. VERY handy for when you mistype one character on a long-ass command.

I love you

Couldn't you do this?
Code:
mv /system/bin/sh /system/bin/sh0
ln -s /system/xbin/bb/ash /system/bin/sh

great job, i'm going to get ash working on my G1 (CM-3.6.7.1)
Thanks.

kanstin said:
Couldn't you do this?
Code:
mv /system/bin/sh /system/bin/sh0
ln -s /system/xbin/bb/ash /system/bin/sh
Click to expand...
Click to collapse
I tried this and it worked even after a reboot...
Sweet, I love the scroll back with trackball in the terminal!!! Me thinks this should get absorbed into the next Cyan release.

kanstin said:
Couldn't you do this?
Code:
mv /system/bin/sh /system/bin/sh0
ln -s /system/xbin/bb/ash /system/bin/sh
Click to expand...
Click to collapse
Yes, I reckon you could. Though I had done a few experiments where the symlink failed, but I'm fairly sure it was do to the link: /system/xbin/bb/ash -->../busybox and /system/bin/../busybox not existing...so I did it via script. Many ways to skin a cat they say.

Thank you all... this is fricken awesome!!

temporizer said:
scratches head. i'm lost. what does this do and how does this make my g1 better?
Click to expand...
Click to collapse
It gives a more advanced shell for when you use the command line interface or telnet into your G1. If you don't use the command line a lot, it won't help you.
As for specific benefits to the advanced version, it was listed in the first post.

Hi,
imho this is rather a hack that exposes you to the risk at least on CM to loose your
shell during boot as xbin.sqf the compressed squashfs filesystem containing
busybox is mounted rather late in the boot process. A cleaner solution would be to
move busybox to system/bin and link it to sh. That way you ensure that sh will
always be accessible during boot and also later on, thus not interfering with
further developments. A alternative could be to compile a standalone version
of busybox containing only ash (for size reasons, as size in /system/bin is precious)
copy that to /system/bin and link sh to it.

Seems to work fine on Dude's. Not really sure how it should open, but I type "ash" at the prompt and I get the /$ and /# if superuser. I also get the command history by rolling the trackball, which is a very nice feature.

Can i install this without using my PC?

temporizer said:
Can i install this without using my PC?
Click to expand...
Click to collapse
Should work using terminal.

Tried it on JACHero 2.7.1
I tried the hard link one and I get a read only fs error on the first move command. What should I chmod to get past that?

mugafuga said:
I tried the hard link one and I get a read only fs error on the first move command. What should I chmod to get past that?
Click to expand...
Click to collapse
Do this first before the mv and the symlink.
mount -o remount,rw /system

farmatito said:
Hi,
imho this is rather a hack that exposes you to the risk at least on CM to loose your
shell during boot as xbin.sqf the compressed squashfs filesystem containing
busybox is mounted rather late in the boot process. A cleaner solution would be to
move busybox to system/bin and link it to sh. That way you ensure that sh will
always be accessible during boot and also later on, thus not interfering with
further developments. A alternative could be to compile a standalone version
of busybox containing only ash (for size reasons, as size in /system/bin is precious)
copy that to /system/bin and link sh to it.
Click to expand...
Click to collapse
Is this in any way accurate? I dedicate my g1 to cyan's roms and wouldn't want anything to hinder any of the goodness that is cyanogenMod. Advice?

Load ash when terminal is started?
temporizer said:
Is this in any way accurate? I dedicate my g1 to cyan's roms and wouldn't want anything to hinder any of the goodness that is cyanogenMod. Advice?
Click to expand...
Click to collapse
Safest method will be to change to ash shell once terminal app is started (same as typing "ash" to switch shell from sh to ash). I don't know how to do it in android (in linux you could add it to your login script).
So if someone knows how to execute a command when we login using the terminal app, then switching to ash shell would work without fear of breaking any other functionality.

[APP] Zipalign binary and script - Optimize installed applications

Hey everyone,
wesgarner said:
Zip Align reduces the amount of RAM used during processing running for a major speed increase in running the apps: http://developer.android.com/guide/developing/tools/zipalign.html
Click to expand...
Click to collapse
I had been messing about with a script to pull apks off my phone, zipalign them and then push them back, but then I saw wesgarner's CM build with a binary and script for use on your phone. I don't really want to mess round with flashing a ROM just for that though, so I've ripped them out and uploaded them below. Another reason is I want to run this manually (with GScript) rather than on boot (as it does in wesgarner's ROM).
I take no credit for this, the binary and script were both taken from wesgarner's CM buiild.
To "install" this, just adb push the two files in the zip below onto your phone with:
Code:
adb shell mount -o remount,rw /system
adb push zipalign /system/bin
adb push zipalign_apks /system/sd/zipalign_apks.sh
adb shell chmod 755 /system/bin/zipalign /system/sd/zipalign_apks.sh
adb shell mount -o remount,ro /system
Then anytime you want to run the script just do:
Code:
adb shell sh /system/sd/zipalign_apks.sh
Or in terminal:
Code:
su
sh /system/sd/zipalign_apks.sh
Has been tested on CM 4.2.7.1

ZipAlign
senab said:
Hey everyone,
I had been messing about with a script to pull apks off my phone, zipalign them and then push them back, but then I saw wesgarner's CM build with a binary and script for use on your phone. I don't really want to mess round with flashing a ROM just for that though, so I've ripped them out and uploaded them below. Another reason is I want to run this manually (with GScript) rather than on boot (as it does in wesgarner's ROM).
I take no credit for this, the binary and script were both taken from wesgarner's CM buiild.
To "install" this, just adb push the two files in the zip below onto your phone with:
Code:
adb shell mount -o remount,rw /system
adb push zipalign /system/bin
adb push zipalign_apks.sh /system/sd
adb shell chmod 755 /system/bin/zipalign /system/sd/zipalign_apks.sh
adb shell mount -o remount,ro /system
Then anytime you want to run the script just do:
Code:
adb shell /system/sd/zipalign_apks.sh
Or in terminal:
Code:
su
sh /system/sd/zipalign_apks.sh
Has been tested on CM 4.2.7.1
Click to expand...
Click to collapse
i do not even know what zipalign does .. but i did add this to my script
# lucid -z
so .. what does it do exactly?

Sweet... Thanks...
I was surprised that more than half of the Apps I have were already ZipAligned...

LucidREM said:
i do not even know what zipalign does .. but i did add this to my script
# lucid -z
so .. what does it do exactly?
Click to expand...
Click to collapse
APKs (as you probably already know) are just zip files. zipalign simply aligns the APK on 4-byte boundaries which Android is more efficient wrt memory access.
You can read more from Jean-Baptiste Queru at http://android-developers.blogspot.com/2009/09/zipalign-easy-optimization.html

Vermithrax said:
Sweet... Thanks...
I was surprised that more than half of the Apps I have were already ZipAligned...
Click to expand...
Click to collapse
Since the 1.6 SDK was released, the ADT does this automatically on APK export. Therefore any app which has been updated since ~September (and was developed using the ADT Eclipse plugin) will be zipalign'd. I was more surprised that 12 out of the 43 apps on my phone weren't aligned!

ZipAlign
senab said:
APKs (as you probably already know) are just zip files. zipalign simply aligns the APK on 4-byte boundaries which Android is more much efficient wrt memory access.
You can read more from Jean-Baptiste Queru at http://android-developers.blogspot.com/2009/09/zipalign-easy-optimization.html
Click to expand...
Click to collapse
that's awesome .. thanks for the link .. i hadn't read about that

Thanks much for this!
Here is a simple gscript to install zipalign after a wipe or new build flash.
You must first create directory /sdcard/zipalign and place zipalign from the zip in the OP there. Path to the file should now be /sdcard/zipalign/zipalign.
Place this script in your gscript folder (after removing .txt from the name) and load it in gscript with su permissions.
I also find it easier to run the script in the zip from the OP in Gscript as well. Instead of placing it in /system/sd run this (assumes zipalign_apks.sh is at root of C:\)
Code:
adb remount
adb push C:\zipalign_apks.sh /sdcard/gscript/zipalign_apks.sh
Then just load it into Gsrcipt with su permissions as with the other script.
Easiest of all may just be to use the commands within Lucid's script. But, I'm comfortable with Gscript, and I can make it 2 clicks away.
EDIT: First execution, you may want to run the original way, because guess what? Gscript isn't zipaligned. But it worked fine just the same.

worked great thanks.

Thanks. I didn't want to flash whole ROM to zipalign apps, so script was very handy.
Actually I've zipaligned only 2 apps, one of them was everybody loved Linda

so anyone wanna bless me with a terminal code to install the script?

garz said:
so anyone wanna bless me with a terminal code to install the script?
Click to expand...
Click to collapse
Read, its on the first post....xD

ZipAlign
garz said:
so anyone wanna bless me with a terminal code to install the script?
Click to expand...
Click to collapse
# lucid -z

yeah so su? then #lucid -z? cause that did nothing for me...

LucidREM said:
i do not even know what zipalign does .. but i did add this to my script
# lucid -z
so .. what does it do exactly?
Click to expand...
Click to collapse
I put a quick explanation of my script on my ROM page: here ya go (rough explanation)
Zip Align reduces the amount of RAM used during processing running for a major speed increase in dex-opt and running the apps, along with the RAM hack and a CC (or your userinit) boots speeds incredibly and better usability of apps (boot and system) in Android: http://developer.android.com/guide/d.../zipalign.html
Most developers have not used this yet (CM does ZipAlign his apps), but this does for the system apps provided from the now old Google Apps
Click to expand...
Click to collapse

senab said:
Since the 1.6 SDK was released, the ADT does this automatically on APK export. Therefore any app which has been updated since ~September (and was developed using the ADT Eclipse plugin) will be zipalign'd. I was more surprised that 12 out of the 43 apps on my phone weren't aligned!
Click to expand...
Click to collapse
Agreed. The Market won't let non-zipaligned apps be uploaded.

AndroidAppCritic said:
Agreed. The Market won't let non-zipaligned apps be uploaded.
Click to expand...
Click to collapse
it will really, it doesn't detect the diff
Also, SDK4 didn't really include an enforced ZipAlign like SDK5 (eclair) does
Plus I built the ZipAlign from source from eclair - so this script may not update them all perfectly

garz said:
yeah so su? then #lucid -z? cause that did nothing for me...
Click to expand...
Click to collapse
Unzip the files to your SD Card, then:
Code:
su
mount -o remount,rw /system
mv /sdcard/zipalign /system/bin
mv /sdcard/zipalign_apks /system/sd/zipalign_apks.sh
chmod 755 /system/bin/zipalign /system/sd/zipalign_apks.sh
mount -o remount,ro /system

Post deleted becoz it was redundant

can someone make a script for windows or a bat file that can zipalign a batch of apks? I am not that ofay with line commands and when i create a new theme (which i often do), i then have to go and zipalign every single apk i have altered 1 at a time..... i do:
Code:
zipalign -f -v 4 E:\app\theapp.apk E:\app\theapp.apk.out

senab said:
Unzip the files to your SD Card, then:
Code:
su
mount -o remount,rw /system
cp /sdcard/zipalign /system/bin
cp /sdcard/zipalign_apks.sh /system/sd
chmod 755 /system/bin/zipalign /system/sd/zipalign_apks.sh
mount -o remount,ro /system
Click to expand...
Click to collapse
This isnt working for me bc of the .sh after zipalign_apks .. do i rename the zipalign_apks to zipalign_apks.sh after unzipping?
edit:that worked THANKS!

Is there a way to fix all permissions on init.d script ?

Hi,
I am trying Beta 3.1 SMS KJ6 kernel.
I went to General Section -> "random reboots" after having some, and was told
that it was caused due to inability to write to system, so i was told to add
systemctl init.d script this line :
mount -oremount,rw /dev/block/stl9 /system
just before line
sysctl -p
Other than that i need to "fix permissions".
but doing this once did not prevent further reboots.
My question is : Is there a way to fix all permissions on init.d script,
so it will be done on every boot ?
will it even help ?
Thanks.

itzik2sh said:
Hi,
I am trying Beta 3.1 SMS KJ6 kernel.
I went to General Section -> "random reboots" after having some, and was told
that it was caused due to inability to write to system, so i was told to add
systemctl init.d script this line :
mount -oremount,rw /dev/block/stl9 /system
just before line
sysctl -p
Other than that i need to "fix permissions".
but doing this once did not prevent further reboots.
My question is : Is there a way to fix all permissions on init.d script,
so it will be done on every boot ?
will it even help ?
Thanks.
Click to expand...
Click to collapse
You can if you know what all permissions are 'fixed' when CWM does that. I'm sure by looking at CWM source we could figure it out then add the necessary commands after the mount and before the sysctl -p line.

itzik2sh said:
Hi,
I am trying Beta 3.1 SMS KJ6 kernel.
I went to General Section -> "random reboots" after having some, and was told
that it was caused due to inability to write to system, so i was told to add
systemctl init.d script this line :
mount -oremount,rw /dev/block/stl9 /system
just before line
sysctl -p
Other than that i need to "fix permissions".
but doing this once did not prevent further reboots.
My question is : Is there a way to fix all permissions on init.d script,
so it will be done on every boot ?
will it even help ?
Thanks.
Click to expand...
Click to collapse
You can try putting this into a script and calling it in your init.d
http://forum.xda-developers.com/showthread.php?t=1221591
Although I believe permissions shouldn't be lost when you reboot, so your problem is likely something else.

ignacioxd said:
You can try putting this into a script and calling it in your init.d
http://forum.xda-developers.com/showthread.php?t=1221591
Although I believe permissions shouldn't be lost when you reboot, so your problem is likely something else.
Click to expand...
Click to collapse
+1 to that.

Hi
I saw that post...
Unlike mounting system as read/write, which is really easy to validate,
how can i know it was actually performed ?

You can manually changea file you know is supposed to be fix in the script b4 running it, than run it and see if it changed back
Sent from my SGH-T959V using XDA App

Thanks mate, I'll give it a try...
Sent from me

Welcome :-D
Sent from my SGH-T959V using XDA App

itzik2sh said:
Hi,
I am trying Beta 3.1 SMS KJ6 kernel.
I went to General Section -> "random reboots" after having some, and was told
that it was caused due to inability to write to system, so i was told to add
systemctl init.d script this line :
mount -oremount,rw /dev/block/stl9 /system
just before line
sysctl -p
Other than that i need to "fix permissions".
but doing this once did not prevent further reboots.
My question is : Is there a way to fix all permissions on init.d script,
so it will be done on every boot ?
will it even help ?
Thanks.
Click to expand...
Click to collapse
Doesnt Valhalla Final already do that? i checked whitehawkx OP and that is included in the features.

How to remount system using SuperSU

- I already rooted my device using supersu but my device won't boot because I changed some files in system framework.
- Have access in adb and there's a su binary
- I tried to copy files to /system/app but it requires permission.

some stock recovery have mount /system

ineedroot69 said:
some stock recovery have mount /system
Click to expand...
Click to collapse
unfortunately I can't boot to recovery..
I tried to adb reboot recovery but it won't go to the recovery ui

You via ADB can run any command as superuser:
Code:
adb devices
adb shell "$(which 'su') -c '<YOUR_SHELL_COMMAND_HERE>'"

jwoegerbauer said:
You via ADB can run any command as superuser:
Code:
adb devices
adb shell "$(which 'su') -c '<YOUR_SHELL_COMMAND_HERE>'"
[
[/QUOTE]
Click to expand...
Click to collapse
Hi, thanks for the reply!
I already tried in shell, su -c 'mount -o remount,rw /system' but still it didn't change into rw

iluvtorock26 said:
unfortunately I can't boot to recovery..
I tried to adb reboot recovery but it won't go to the recovery ui
Click to expand...
Click to collapse
you are rooted?
this is kinda sound stupid but it might work download "fx file explorer" from playstore then give it root permission then access this directory from fx file explorer "System (Root) > System" then while on that folder access upper right options then change to rw

just be careful with fx file explorer... one wrong move and you might accidentally delete whole partition lmao

ineedroot69 said:
you are rooted?
this is kinda sound stupid but it might work download "fx file explorer" from playstore then give it root permission then access this directory from fx file explorer "System (Root) > System" then while on that folder access upper right options then change to rw
Click to expand...
Click to collapse
Yes, I used SuperSU to root my device.
My device hanging in the bootloop so running an app is not possible.

iluvtorock26 said:
Hi, thanks for the reply!
I already tried in shell, su -c 'mount -o remount,rw /system' but still it didn't change into rw
Click to expand...
Click to collapse
Maybe SELinux is enforced, also maybe AVB 1.0 and/or AVB 2.0 is enabled ( AKA bootloader is locked ): both deny to operate on /system partition

jwoegerbauer said:
Maybe SELinux is enforced, also maybe AVB 1.0 and/or AVB 2.0 is enabled ( AKA bootloader is locked ): both deny to operate on /system partition
Click to expand...
Click to collapse
Sorry I'm newbie to rooting the file, so I'm not familiar in SELinux or AVB.

iluvtorock26 said:
Sorry I'm newbie to rooting the file, so I'm not familiar in SELinux or AVB.
Click to expand...
Click to collapse
Then you should familiarize yourself with these Android security mechanisms as soon as possible.

jwoegerbauer said:
Then you should familiarize yourself with these Android security mechanisms as soon as possible.
Click to expand...
Click to collapse
Do you have any idea on how to fix the bootloop?

iluvtorock26 said:
Yes, I used SuperSU to root my device.
My device hanging in the bootloop so running an app is not possible.
Click to expand...
Click to collapse
you should have said that in the beginning that you are on bootloop

ineedroot69 said:
you should have said that in the beginning that you are on bootloop
Click to expand...
Click to collapse
Sorry about that, I just want to fixed it by replacing the correct jar file in the system framework.

iluvtorock26 said:
Do you have any idea on how to fix the bootloop?
Click to expand...
Click to collapse
Start a new thread titled "How to fix bootloop on <YOUR_DEVICES_BRAND / MODEL>"

S
jwoegerbauer said:
Start a new thread titled "How to fix bootloop on <YOUR_DEVICES_BRAND / MODEL>"
Click to expand...
Click to collapse
Sure.. thank you!

How To Guide Mount System read/write

My native language is not English.
I am sorry, but I do not understand native English.
This operation is very dangerous.
Enables writing to "/".
All at your own risk.
Devices preinstalled with android 10 or later are
Even if you root the device, it will still be r/o and you will not be able to edit it at all.
By running this script, you can r/w the system itself.
We will use makeSystemRW and makesysrw_repair created by lebigmac.
You will need a linux system to run makesysrw_repair.
[SCRIPT][Android 10+] Universal Mount System read write R/W
I would like to thank lebigmac for creating this script.
1. After unlocking the boot loader and becoming root, disable all vbmeta.
Code:
fastboot -–disable-verity -–disable-verification flash vbmeta vbmeta.img
fastboot -–disable-verity -–disable-verification flash vbmeta_system vbmeta_system.img
2. Copy makeSystemRW to /data/local/tmp of edge s.
3. Run makeSystemRW.
Code:
adb shell
su
chmod +x /data/local/tmp/makesysrw_1.31/makesysrw.sh
setenforce 0
./data/local/tmp/makesysrw_1.31/makesysrw.sh size=20
An error will occur here and it will fail.
You need to use makesysrw_repair.
4. Run makesysrw_repair.
Copy makesysrw_repair, open a terminal at the location where you copied it, and run the code.
Code:
sudo bash makesysrw_repair.sh
We have confirmed that this command is executable on Ubuntu.
5. Finish.
You are now done.
You can mount it with r/w using the root explorer.
Make sure that you can create new files and folders.

Would like to do this but why hasn't anyone else posted on this thread regarding success or fails?

nexus7lte said:
Would like to do this but why hasn't anyone else posted on this thread regarding success or fails?
Click to expand...
Click to collapse
I guess no one tried it, or they did and never commented

Thank you for your interest in my SystemRW/SuperRW feat. MakeRW project.
Yes I got the project thread closed while I was enjoying the summer holidays. Everyone needs a well deserved break every once in a while. I'll have it reopened as soon as I'm ready to publish the new version of my script. Hopefully soon
It's looking like a fall release rather than a summer release though... Time flies...
The old version 1.32 works in A10, A11 and some folks even got it to work in A12 simply by disabling the sdkCheck() function
The new version should have A13 support straight out of the box if everything goes according to plan. Wish me luck! Thanks!
Cheers

i would like to try this just to get rid of the annoying Android 12 update message.
Evan after disabling google play services notifications and freezing the OTAs, I still cant stop
com.motorola.ccc.ota and I assume thats because its on a read only portion, right? ADB commands didnt work.

My error in adb or terminal is_
u
:/ # pm disable com.motorola.ccc.ota
Exception occurred while executing 'disable':
java.lang.SecurityException: Cannot disable a protected package: com.motorola.ccc.ota

Hi @nexus7lte
Did you get my SystemRW/SuperRW feat. MakeRW script to work on your Android 12 device?
Is it the Motorola Moto G100 ? How do you like it?
Yeah disabling those protected system packages can be tricky sometimes. I'm sure it's possible somehow.
On Xiaomi devices we also got this Xiaomi security app and I can't disable it even as root with full rw access but I'm sure a true expert could do it

lebigmac said:
Hi @nexus7lte
Did you get my SystemRW/SuperRW feat. MakeRW script to work on your Android 12 device?
Is it the Motorola Moto G100 ? How do you like it?
Yeah disabling those protected system packages can be tricky sometimes. I'm sure it's possible somehow.
On Xiaomi devices we also got this Xiaomi security app and I can't disable it even as root with full rw access but I'm sure a true expert could do it
Click to expand...
Click to collapse
Well... I tried your script on my new Realme GT Neo 3T android 12. It booted but seems like nothing changed. Mounting system still says "mount: '/system' not in /proc/mounts"

Vipxpert said:
Mounting system still says "mount: '/system' not in /proc/mounts"
Click to expand...
Click to collapse
Hi. That's a nice device you've got!
Are you sure you're calling the command as root?
Usually you get this error message if you try to remount something as shell user...
Or you're trying to remount the wrong path. Try mount -o remount,rw /
Without seeing any screenshots or at least your log it's very difficult to tell what's wrong on your device from here. Did you check if my script successfully removed the infamous shared_blocks read-only feature from your phone?
Bash:
adb shell
su
for a in /dev/block/dm-*; do tune2fs -l $a | grep -e "feat" -e "vol"; done

lebigmac said:
Hi. That's a nice device you've got!
Are you sure you're calling the command as root?
Usually you get this error message if you try to remount something as shell user...
Or you're trying to remount the wrong path. Try mount -o remount,rw /
Without seeing any screenshots or at least your log it's very difficult to tell what's wrong on your device from here. Did you check if my script successfully removed the infamous shared_blocks read-only feature from your phone?
Bash:
adb shell
su
for a in /dev/block/dm-*; do tune2fs -l $a | grep -e "feat" -e "vol"; done
Click to expand...
Click to collapse
Here I have flashed it through EX kernel manager since there's no TWRP for Neo 3T or even a forum yet. Do u need a full log somewhere though?

lebigmac said:
Hi. That's a nice device you've got!
Are you sure you're calling the command as root?
Usually you get this error message if you try to remount something as shell user...
Or you're trying to remount the wrong path. Try mount -o remount,rw /
Without seeing any screenshots or at least your log it's very difficult to tell what's wrong on your device from here. Did you check if my script successfully removed the infamous shared_blocks read-only feature from your phone?
Bash:
adb shell
su
for a in /dev/block/dm-*; do tune2fs -l $a | grep -e "feat" -e "vol"; done
Click to expand...
Click to collapse
Ah here I found

Also I tried copy-paste your code. It gives a bunch of nonsenses hmm...

Same this result for me even with your command
adb shell
su
for a in /dev/block/dm-*; do tune2fs -l $ etc
Or if i flashed rw fixed_super.bin
Device not able to boot anymore

Hi @Vipxpert thanks for your log and for the screenshots!
I don't understand why the script didn't detect your shared_blocks read-only feature...
Are you saying the script didn't do anything and you flashed the resulting super_fixed.bin to your super partition and phone still boots in read-only mode?
Oh yeah right I forgot that OnePlus devices usually have dozens of useless pseudo (cow) partitions in its partition table...
To find out if your device has got the infamous shared_blocks read-only feature please try this updated code. Good luck!
Bash:
adb shell
su
for a in /dev/block/dm-*; do tune2fs -l $a | grep -e "feat" -e "vol" -e "mounted on"; done
Or like this:
Bash:
adb shell
su
for a in `seq 0 5`; do tune2fs -l /dev/block/dm-$a | grep -e "feat" -e "vol" -e "mounted on"; done
@Mr Hassan bootloops are always very sad . Do you have any idea why it happened?
Try to boot into TWRP and pull any log files to find out reason for error and then reflash original stock super.img and phone should boot again Good luck!

lebigmac said:
Hi @Vipxpert thanks for your log and for the screenshots!
I don't understand why the script didn't detect your shared_blocks read-only feature...
Are you saying the script didn't do anything and you flashed the resulting super_fixed.bin to your super partition and phone still boots in read-only mode?
Oh yeah right I forgot that OnePlus devices usually have dozens of useless pseudo (cow) partitions in its partition table...
To find out if your device has got the infamous shared_blocks read-only feature please try this updated code. Good luck!
Bash:
adb shell
su
for a in /dev/block/dm-*; do tune2fs -l $a | grep -e "feat" -e "vol" -e "mounted on"; done
Or like this:
Bash:
adb shell
su
for a in `seq 0 5`; do tune2fs -l /dev/block/dm-$a | grep -e "feat" -e "vol" -e "mounted on"; done
@Mr Hassan bootloops are always very sad . Do you have any idea why it happened?
Try to boot into TWRP and pull any log files to find out reason for error and then reflash original stock super.img and phone should boot again Good luck!
Click to expand...
Click to collapse
I even try stock super but device wont boot until flash back stock
And hes oneplus have somekinda cow partitions etc
I see when i try flash its asked to delete all cow parts
Don't know what's this

Yeh I did flash it with "fastboot flash super super-fixed.bin" and that took no effect ://
Anyways here're the results of your 2 commands. They seem not to end up well

@lebigmac mention mention

Well it looks like your /product partition does indeed have the infamous shared_blocks read-only feature.
I know that's a stupid feature but this is actually good news. This means new upcoming version of my script should be able to do the job

lebigmac said:
Well it looks like your /product partition does indeed have the infamous shared_blocks read-only feature.
I know that's a stupid feature but this is actually good news. This means new upcoming version of my script should be able to do the job
Click to expand...
Click to collapse
Yess!! U're the hero thanks so much now I can debloat, fake Google daydream service, add AR supports, edit mixer_path.xml for volume and tons of stuffs. Oh I miss those time a lot ^^^

lebigmac said:
Well it looks like your /product partition does indeed have the infamous shared_blocks read-only feature.
I know that's a stupid feature but this is actually good news. This means new upcoming version of my script should be able to do the job
Click to expand...
Click to collapse
any any estimate of days or release date