[DEV][CWM][LockedBootloader][FULL] AOKP ClockWorkMod 6.0 - Sony Xperia P, U, Sola, Go

This is cwm for your xperia u with locked bootloader, but this is beta version
FILES FOR XPERIA U
recovery.fstab
Code:
# mount point fstype device [device2] fstype2
/cache ext4 /dev/block/mmcblk0p12
/data ext4 /dev/block/mmcblk0p11
/system ext4 /dev/block/mmcblk0p10
/sdcard vfat /dev/block/mmcblk0p14
/boot emmc /dev/block/mmcblk0p9
fstab
Code:
/cache ext4 /dev/block/mmcblk0p12
/data ext4 /dev/block/mmcblk0p11
/system ext4 /dev/block/mmcblk0p10
/sdcard vfat /dev/block/mmcblk0p14
/boot emmc /dev/block/mmcblk0p9
bootrec
Code:
#!/sbin/sh
# trigger button-backlight
echo '255' > /sys/class/leds/r-key-blue/brightness
echo '255' > /sys/class/leds/m-key-red/brightness
echo '255' > /sys/class/leds/l-key-green/brightness
cat /dev/input/event2 > /dev/keycheck&
sleep 3
# trigger button-backlight
echo '0' > /sys/class/leds/r-key-red/brightness
echo '0' > /sys/class/leds/l-key-red/brightness
echo '0' > /sys/class/leds/m-key-red/brightness
kill -9 $!
fi
if [ -s /dev/keycheck -o -e /cache/recovery/enterrecovery ]
then
rm /cache/recovery/enterrecovery
mount -o remount,rw rootfs /
# shifting to "umount -l /partition" to avoid mounting issues in recovery
stop cspsa
stop tad
killall -9 cspsa-server
killall -9 logwrapper
killall -9 chargemon
killall -9 tad
umount -l /system
umount -l /data
umount -l /cache
umount -l /sdcard
umount -l /mnt/sdcard
rm -r /sdcard
rm -r /not/sdcard
mkdir /sdcard
mkdir /tmp
rm /etc
mkdir /etc
cp /recovery.fstab /etc/recovery.fstab
mount /dev/block/mmcblk0p14 /sdcard
/sbin/recovery &
/sbin/ps >/sdcard/ps.log
# DooMLoRD - enable USB Mass Storage mode - thanks to Napstar
echo 1 > /sys/devices/virtual/usb_composite/usb_mass_storage/enable
/sbin/recovery &
/sbin/adbd_rec recovery
fi
IM INTEGRATE THIS IN MY AOKP
works
everythings
mount /data
mount /cache
mount /sdcard
mount /usb
CHANGELOG:
BETA 1
FIXED MOUNT DATA AND USB
BETA 2
THE BAR LIGHTS IS ON IN RECOVERY MOD NICE!!!
FOR NOW THIS HAVE SOME BUGS
BETA 3
FIXED SOME ISSEUES
BUGS: ONLY MOUNT SYSTEM
BETA 4
NEW AOKP LOGO
NOW YOU CAN FORMAT /SYSTEM....BUT NOT FLASH ROMS
BETA 5
FIXED MOUNT /SYSTEM (From bootrec from Atis112)
FIXED Bootrec
Fixed Bootrec-Device
Fixed Bootrec-devce-fs
ITS MY CWM... NOT CWM MODIFY FROM ATIS112
IM ADD SOME FEATURES TO THISS CWM
INSTALLATION
RENAME TO recovery.tar AND PUT IN SYSTEM/BIN AND CHANGE PERMISSIONS
DOWNLOAD: HERE

maybe you need to check if the recovery is gaining access to root, check the mountpoint, etc...

xperiafan13 said:
This is cwm for your xperia u with locked bootloader, but this is beta version
bugs:
Cant mount system
I NEED TO FIX MOUNT SYSTEM... PLEASE HEELP ME!!!!
IM INTEGRATE THIS IN MY AOKP
works
everythings
mount /data
mount /cache
mount /sdcard
mount /usb
Click to expand...
Click to collapse
Wait my next rom.
Sent from my Xperia U using xda premium

THANKS
atis112 said:
Wait my next rom.
Sent from my Xperia U using xda premium
Click to expand...
Click to collapse
BUT IM MAKE MI CUSTOM RAMDIZK AND RECOVERYS FOR MY ROM,I'm about going on holiday, and now if I can give more time to ANDROID

New beta aviable
This is in progress, not flly working, is oly for development.....
The light bar is on in recovery

Delete.

HELLO
This is my personnel recovery, this is not a copy of CWM of Atis112, eh I repaired the system assembly from its bootrec, keeping the light bar is always turned on, I will initiate my own projects, this is different from CWM of Atis112, thank him for the fix, likewise warn my AOKP version will have a new morning, I no longer have tested and reboots ...
some new things will
Enabled 2D acceleration
LED repaired
Greater stability guaranteed
No more delays on lockscreen
Posted AndyX modules, activatable Romcontrol
All applications updated
Based on FXP 148
AND MORE

What are the main diferences between your cwm and attis ?

Related

[REF] Mount points for Nook Color

I have not seen these mount points posted anywhere for handy reference...
These are mount points for CWM and ADB
•mmcblk0p1 - Boot (vfat)
•mmcblk0p2 - Rom
•mmcblk0p3 - Device specific files (serial number, etc) and Factory.zip (flashable zip that returns NC to factory settings)
•mmcblk0p4 - Logical Partition (Nothing of use here)
•mmcblk0p5 - System
•mmcblk0p6 - Data
•mmcblk0p7 - Cache (vfat)
•mmcblk0p8 - Media (vfat)
These are mount points for Nooter .2
•mmcblk0p1 - SDCARD
•mmcblk1p1 - Boot (vfat)
•mmcblk1p2 - Rom
•mmcblk1p3 - Device specific files (serial number, etc) and Factory.zip (flashable zip that returns NC to factory settings)
•mmcblk1p4 - Logical Partition (Nothing of use here)
•mmcblk1p5 - System
•mmcblk1p6 - Data
•mmcblk1p7 - Cache (vfat)
•mmcblk1p8 - Media (vfat)
Lol, I thought this thread said "moot" points
modembug said:
I have not seen these mount points posted anywhere for handy reference...
Click to expand...
Click to collapse
Besides here, you mean?
Your info is wrong. mmcblk0 is the emmc. mmcblk1 is the sdcard.
Also, the stock file system types are ext2 for system, ext3 for data. Gingerbread uses ext4 for both.
dangit i suck! I looked on nook devs last night for that list and didnt find it!
I have updated the mount points to reflect both nooter and adb/cwm...
fattire said:
Besides here, you mean?
Your info is wrong. mmcblk0 is the emmc. mmcblk1 is the sdcard.
Also, the stock file system types are ext2 for system, ext3 for data. Gingerbread uses ext4 for both.
Click to expand...
Click to collapse
In the guide modembug linked on AndroidCentral (see here: http://forum.androidcentral.com/bar...how-install-nookie-froyo-internal-memory.html), it says to do this:
Code:
mount -o remount,rw /dev/block/mmcblk1 /
mkdir tmpfolder
mount /dev/block/mmcblk0p5 tmpfolder
cd tmpfolder
rm -r *
cd ..
mount /dev/block/mmcblk0p6 tmpfolder
cd tmpfolder
rm -r *
cd ..
umount tmpfolder
rmdir tmpfolder
Why is this necessary? Specifically, why the remount to rw of /, when you could just create a directory in /data for this purpose?
Also, why is it apparently not necessary to delete the contents of /boot (mmcblk0p1) but it is for /system and /data?
starkruzr said:
In the guide modembug linked on AndroidCentral (see here: http://forum.androidcentral.com/bar...how-install-nookie-froyo-internal-memory.html), it says to do this:
Code:
mount -o remount,rw /dev/block/mmcblk1 /
mkdir tmpfolder
mount /dev/block/mmcblk0p5 tmpfolder
cd tmpfolder
rm -r *
cd ..
mount /dev/block/mmcblk0p6 tmpfolder
cd tmpfolder
rm -r *
cd ..
umount tmpfolder
rmdir tmpfolder
Why is this necessary? Specifically, why the remount to rw of /, when you could just create a directory in /data for this purpose?
Also, why is it apparently not necessary to delete the contents of /boot (mmcblk0p1) but it is for /system and /data?
Click to expand...
Click to collapse
Boot gets overwritten data and system leave remnants i.e. dalvik cache which causes boot issues
Sent from my PC36100 using XDA App

[MULTIBOOT] Mini pro All-in-one recovery pack

STILL TESTING!
This is made by nobodyAtall, ported to work on mini pro, and added features
Guys, so this is a new attempt to multiboot. I need testers from all kind of SD's
Features
*Multiboot (More info) - CM6 & CM7 Only (I think, but it's possible...)
*Dual Recovery (More info) - All ROM's
*Data encryption (More info) - CM6 & CM7 Only
How to install
1. Flash .zip for AIO recovery pack (CWM recovery)
2. Go to CWM recovery (back button, middle button (home) it's for xrecovery) and choose Multiboot
3. Select Create boot option from zip
4. Choose any ROM that can be installed with CWM recovery (Needed 400MB on SD for this)
5. Choose Flash Zip to boot option, and flash the correspondent multiboot package (ROM's devs need to provide this)
6. Choose select default boot option, and select your last created
7. Choose boot into selected option, and enjoy!
NOTE: For multiboot with CyaNoComb, you can flash this, till I get our ramdisk good for multiboot. Credits to nAa for the ramdisk.
Cheers, D4.
Dev Info:
Final Chargemon
Code:
#!/system/bin/busybox sh
#
# Unified X10 mini pro multiboot script / dualrecovery
# Devs who worked on this project:
# D4rKn3sSyS, DooMLoRD, nobodyAtall, Owain94, Slade87, puppet13th
#
# keychecks
cat /dev/input/event0 > /dev/keycheck&
sleep 3
kill -9 $!
keypressed=`cat /dev/keycheck`
if [ "$keypressed" != "${keypressed/ž/}" ]
then
echo "recovery" > /data/local/tmp/bootrecovery
else
if [ "$keypressed" != "${keypressed/f/}" ]
then
echo "xrecovery" > /data/local/tmp/bootrecovery
fi
fi
# DualRecovery
if [ -s /data/local/tmp/bootrecovery ]
then
boot=`cat /data/local/tmp/bootrecovery`
rm -f /data/local/tmp/bootrecovery
# remount rootfs rw
mount -o remount,rw rootfs /
# Umount MTDs
umount -l /dev/block/mtdblock1
umount -l /dev/block/mtdblock2
umount -l /dev/block/mtdblock3
# Mount recovery partition
cd /
rm -r /sbin
rm -f etc
tar -xf /system/bin/"$boot".tar
# Umount /system
umount -l /dev/block/mtdblock0
# chroot
chroot / /init
fi
# offline charging
/system/bin/charger
rm -f /data/multiboot.log
# nobodyAtall - Multiboot hack
if [ -h /system/bin/multiboot_default ]
then
echo "Multiboot on" >> /data/multiboot.log
mkdir -p /sdcard
/system/bin/fsck_msdos -y /dev/block/mmcblk0p1
if [ $? -ne 0 ]
then
/system/bin/fsck_msdos -y /dev/block/mmcblk0p1
fi
mount -t vfat -o rw,noatime,nodiratime /dev/block/mmcblk0p1 /sdcard
if [ $? -eq 0 ] && [ -f /system/bin/multiboot_default/system.img ] && [ -f /system/bin/multiboot_default/data.img ] && [ -f /system/bin/multiboot_default/cache.img ]
then
echo "Good to multiboot" >> /data/multiboot.log
losetup /dev/block/loop1 /system/bin/multiboot_default/system.img
losetup /dev/block/loop2 /system/bin/multiboot_default/data.img
losetup /dev/block/loop3 /system/bin/multiboot_default/cache.img
if [ -f /system/bin/e2fsck ]
then
/system/bin/e2fsck -y /dev/block/loop1
/system/bin/e2fsck -y /dev/block/loop2
/system/bin/e2fsck -y /dev/block/loop3
fi
# Umount /system, data and cache
umount -l /dev/block/mtdblock0
umount -l /dev/block/mtdblock3
umount -l /dev/block/mtdblock1
mount -t ext2 -o rw,noatime,nodiratime /dev/block/loop1 /system
if [ -f /system/bin/ramdisk.tar ]
then
tar -xf /system/bin/ramdisk.tar
# nobodyAtall - Reboot Fix
mkdir -p /minicm
cd /minicm
tar -xf /system/bin/ramdisk.tar
sync
umount -l /system
umount -l /cache
umount -l /data
sleep 1
rmdir /system /data /cache /mnt
mkdir -p /minicm/system /minicm/data /minicm/cache
mount -t ext2 -o rw,noatime,nodiratime /dev/block/loop1 /minicm/system
mount -t ext2 -o rw,noatime,nodiratime,nosuid,nodev /dev/block/loop2 /minicm/data
mount -t ext2 -o rw,noatime,nodiratime,nosuid,nodev /dev/block/loop3 /minicm/cache
sleep 1
chroot /minicm /init
else
umount -l /system
umount -l /cache
umount -l /data
sleep 1
mount -t ext2 -o rw,noatime,nodiratime /dev/block/loop1 /system
mount -t ext2 -o rw,noatime,nodiratime,nosuid,nodev /dev/block/loop2 /data
mount -t ext2 -o rw,noatime,nodiratime,nosuid,nodev /dev/block/loop3 /cache
sleep 1
/system/bin/qmuxd &
sleep 1
exit
fi
fi
fi
echo "Multiboot off" >> /data/multiboot.log
# CM & Stock compatibility
if [ -f /system/etc/CHANGELOG-CM.txt ]; then
# for cyanogenmod
# remount rootfs rw
mount -o remount,rw rootfs /
chmod 0777 /dev -R
chown 0.2000 /dev/oncrpc -R
cd /
rm init*
rm logo.rle
rm default.prop
tar -xf /system/bin/ramdisk.tar
# nobodyAtall - Fix
mkdir -p /minicm
cd /minicm
tar -xf /system/bin/ramdisk.tar
sync
# Umount /system, data and cache
umount -l /dev/block/mtdblock0
umount /dev/block/mtdblock3
umount /dev/block/mtdblock1
rmdir /system /data /cache /mnt
# Mount /system to /minicm/system
/sbin/mount_system
sleep 1
chroot /minicm /init
else
#for stock
# Continue booting
exit
fi
Changelog:
29th July 2011
First release, for testing
I will test as soon as I'm home as I'm away now and only have limited net I am ona 4gb card not sure of the class is the only available rom to multiboot cyanocomb so I could have slades cm7 as main and cyanocomb as secondary?
Sent from my U20i using XDA App
First attempt bricked but boot without sd will boot back into main not sure if it is because my SD is only class 2 would that explain being on SE screen for a while?
Sent from my U20i using XDA App
x10man said:
First attempt bricked but boot without sd will boot back into main not sure if it is because my SD is only class 2 would that explain being on SE screen for a while?
Sent from my U20i using XDA App
Click to expand...
Click to collapse
Same what happened to mine but I never took out the sd card to see if it boots back to original state. Im using 4gb class 2.
Sent from my U20i using XDA Premium App
Also when choosing the boot into selected option option my phone. Shuts down then when I boot again it boots my internal cm7 v15
Sent from my U20i using XDA App
Yes, it seems to be incompatible with some SD cards, that's why i need testers
F*ck u man! Ur awesome I still wonder why u didnt get thats recognised developer tag!
how to know class of SD card ?
its not writen any where on card
If you don't know the class it may be class 0 which was before there were classes the default card is class 2 I will try the default card when I'm home and find it
Sent from my U20i using XDA App
galvic said:
F*ck u man! Ur awesome I still wonder why u didnt get thats recognised developer tag!
Click to expand...
Click to collapse
I think I got it galvik show me how later on facebook
kormatoes said:
I think I got it galvik show me how later on facebook
Click to expand...
Click to collapse
Sure but i'm still looking for a class 10 sdcard, u know that my sdcard has 0kb free and lol i'm tired of deleting my music
galvic said:
Sure but i'm still looking for a class 10 sdcard, u know that my sdcard has 0kb free and lol i'm tired of deleting my music
Click to expand...
Click to collapse
I was looking in town today and they all said they did not know what I mean so is there a certin make to look out for
kormatoes said:
I was looking in town today and they all said they did not know what I mean so is there a certin make to look out for
Click to expand...
Click to collapse
If i'm not worng then better the class better will be the result of multiboot!
x10man said:
First attempt bricked but boot without sd will boot back into main not sure if it is because my SD is only class 2 would that explain being on SE screen for a while?
Sent from my U20i using XDA App
Click to expand...
Click to collapse
Booting will take longer on lower SD class, that's the why on SE screen.
tomorow i will test this with sandisk class 4
maybe you could add in first post that is recommended to have minimum 400MB free space on SD card
and great work
So... Let's say I have installed stock in internal, next step is to install CyaNoComb in SD and boot it and afterwards exactly install ramdisk patch? When we boot from SD the Recoverys are booted from SD ROM too and any changes (regarding system and data) affect only SD? I am kinda confused, please heeeeelp!
leajian said:
So... Let's say I have installed stock in internal, next step is to install CyaNoComb in SD and boot it and afterwards exactly install ramdisk patch? When we boot from SD the Recoverys are booted from SD ROM too and any changes (regarding system and data) affect only SD? I am kinda confused, please heeeeelp!
Click to expand...
Click to collapse
No, recovery will keep being main ROM recovery. in fact ROM's on SD, don't need chargemon or recoverys. I think. Anyway I haven't tested this myself, because my SD don't like multiboot.
EDIT: Corrected info, CyaNoComb should multiboot right
Btw, my new SD it's coming soon, so I could test this, and fix isues if exist.
D4rKn3sSyS said:
No, recovery will keep being main ROM recovery. in fact ROM's on SD, don't need chargemon or recoverys. I think. Anyway I haven't tested this myself, because my SD don't like multiboot.
EDIT: Corrected info, CyaNoComb should multiboot right
Btw, my new SD it's coming soon, so I could test this, and fix isues if exist.
Click to expand...
Click to collapse
Lighter rom+better sdclass=perfect multiboot throw some light on how to create multiboot package, i'll try with GingEricsson...

[DEV][PORT] Port CM9 for LockedBootloaders [W.I.P]

Hello guys, im working to boot any CM9 Rom in stock kernel with Bootloader Locked
The Fix, requires a number of changes in the Ramdizk, this Ramdizk is obtained through the kernel, the ramdizk is that the system starts.
This file consists of the following
Ramdizk .... obtained from the kernel
chargemon .... modified to start the ramdizk
charger ... for charging the phone
sh .... responsible for early in the phone
Chargemon
Code:
#!/system/xbin/sh
# Chargemon script for Xperia NEO by Xperiafan
# Boot to CWM
cat /dev/input/event2 > /dev/keycheck&
sleep 3
kill -9 $!
if [ -s /dev/keycheck -o -e /cache/recovery/boot ]
then
rm /cache/recovery/boot
# remount rootfs rw
mount -o remount,rw rootfs /
# Umount eMMCs
umount -l /dev/block/mmcblock0p10
umount -l /dev/block/mmcblock0p11
umount -l /dev/block/mmcblock0p12
# Mount recovery
cd /
rm -r /sbin /sdcard
rm -f etc init* uevent* default*
if [ -f /system/bin/recovery.tar ]
then
tar -xf /system/bin/recovery.tar
fi
# Umount /system
umount -l /dev/block/mmcblk0p10
# chroot
chroot / /init
fi
# Ramdizk
# remount rootfs rw
mount -o remount,rw rootfs /
# Umount eMMCs
umount -l /dev/block/mmcblock0p10
umount -l /dev/block/mmcblock0p11
umount -l /dev/block/mmcblock0p12
# Mount ramdisk
cd /
rm -r /sbin /sdcard
rm -f etc init* uevent* default*
tar -xf /system/bin/ramdisk.tar
# Fix permissions
mount -o remount,rw rootfs /
umount -l /system
umount -l /data
umount -l /cache
umount -l /mnt/sdcard
umount -l /sdcard
rm -r /mnt/sdcard
mkdir /tmp
# chroot
chroot / /init
To use these files, you need to put them in the following path
Ramdizk system/bin
Chargemon system/bin
Charger system/bin
sh system/xbin
I have not got this phone, please appreciate your comments, you need to put these files on those routes the rom, and erase the file boot.img​
Downloads
Ramdizk Beta Here
Chargemon Done Here
Charger Done Here
SH Done Here
We need custom wifi modules, right?
Sent from my MT15i using xda app-developers app
Its nice that we'll be having CyanogenMod for locked bootloaders.
Keep up the good work dev!
Anyone having locked bl
Tried his efforts?
Sent from my MT11i using xda premium
I tried it, but i doesnt boot, just stuck at sony logo... I will try to manually extract the ramdisk from the latest get.cm and it seems we will have aosp roms on locked bootloader
Sent from my MT15i using xda app-developers app
I will try to make a build what at least boots succesfully
Sent from my MT15i using xda app-developers app
it would be nice if anyone try to make this work i realised that we have mtdblocks not mmcblocks ... lets see if i can get it to work
Im work in this.... But first im make a new ramdizk for xperia u and later for neo and others
Sent from my ST25i using xda app-developers app

i need help to Ext2internalse on Cyanogenmod

i need help i dont know how transpose this mod for cyanogenmod (PAC-rom)
code:
#!/system/bin/sh
SU
busybox mount -o remount,rw /
busybox mount -t vfat -o umask=0000 /dev/block/vold/179:61 /storage/sdcard0
busybox mount -t exfat -o umask=0000 /dev/block/vold/179:61 /storage/sdcard0
if busybox mount | busybox grep vold/179:61; then
busybox mount -o bind /data/media /storage/external_SD
chmod -R 0777 /storage/external_SD
fi
Help me please :laugh:
raukas said:
i need help i dont know how transpose this mod for cyanogenmod (PAC-rom)
code:
#!/system/bin/sh
SU
busybox mount -o remount,rw /
busybox mount -t vfat -o umask=0000 /dev/block/vold/179:61 /storage/sdcard0
busybox mount -t exfat -o umask=0000 /dev/block/vold/179:61 /storage/sdcard0
if busybox mount | busybox grep vold/179:61; then
busybox mount -o bind /data/media /storage/external_SD
chmod -R 0777 /storage/external_SD
fi
Help me please :laugh:
Click to expand...
Click to collapse
AFAIK, this mod will not work with CM10.1 / 10.2.
There is no easy means to switch between emulated storage and external sdcard since JB(4.2.2).
The only way to disable internal sd emulation is to recompile the rom with this commit included.
(correct me if im wrong)
nfs1mw said:
AFAIK, this mod will not work with CM10.1 / 10.2.
There is no easy means to switch between emulated storage and external sdcard since JB(4.2.2).
The only way to disable internal sd emulation is to recompile the rom with this commit included.
(correct me if im wrong)
Click to expand...
Click to collapse
You are correct. OP use mateo1111 PAC (if p760-p768) or any of the p769 ports.
They have the fake internal SD removed.
Sent from my LGMS769 using XDA Premium 4 mobile app

Android 9 (Pie) unable to unlock /system from read-only mode

Hi all,
Just upgraded my Mi8 with the new Miui 10 based on Android P.
I've TWRP-3.2.3-0918 as recovery and rooted with Magisk-v17.1
As root, in the same condition until the previous version (Android Oreo) i was able to remount the /system with
# mount -o rw,remount /system
but in this version i get an error
'/dev/block/platform/soc/1d84000.ufshc/by-name/system' is read-only
i've tried many ways but nothing ... i'm unable to remount the /system for writing ... see below my failed attempts
# l /dev/block/platform/soc/1d84000.ufshc/by-name/system
lrwxrwxrwx 1 root root 16 Jun 4 1970 /dev/block/platform/soc/1d84000.ufshc/by-name/system -> /dev/block/sde48
# l /dev/block/sde48
brw------- 1 root root 259, 38 Jun 4 1970 /dev/block/sde48
# mount -o rw,remount /dev/block/sde48 /system
mount: '/system' not in /proc/mounts
# mount -o rw,remount /dev/block/platform/soc/1d84000.ufshc/by-name/system /system
'/dev/block/platform/soc/1d84000.ufshc/by-name/system' is read-only
home # mkdir mio
home # mount -t ext4 /dev/block/platform/soc/1d84000.ufshc/by-name/system mio
mount: '/dev/block/platform/soc/1d84000.ufshc/by-name/system'->'mio': Device or resource busy
# mount -o remount,rw,bind /system /data/data/berserker.android.apps.sshdroid/home/mio <
mount: '/data/data/berserker.android.apps.sshdroid/home/mio' not in /proc/mounts
home # cat /proc/mounts | grep system
/dev/block/platform/soc/1d84000.ufshc/by-name/system /system ext4 ro,seclabel,relatime,discard,data=ordered 0 0
/dev/block/platform/soc/1d84000.ufshc/by-name/system /sbin/.core/mirror/system ext4 ro,seclabel,relatime,discard,data=ordered 0 0
home # mount -o remount,rw,bind /dev/block/platform/soc/1d84000.ufshc/by-name/system /data/data/berserker.android.apps.sshdroid/home/mio
mount: '/data/data/berserker.android.apps.sshdroid/home/mio' not in /proc/mounts
home # mount -o remount,rw,bind /dev/block/platform/soc/1d84000.ufshc/by-name/system /system
'/dev/block/platform/soc/1d84000.ufshc/by-name/system' is read-only
home # mount -o remount,rw /dev/block/platform/soc/1d84000.ufshc/by-name/system /system
'/dev/block/platform/soc/1d84000.ufshc/by-name/system' is read-only
home # getenforce
Enforcing
home # setenforce 0
home # getenforce
Permissive
home # mount -o remount,rw /dev/block/platform/soc/1d84000.ufshc/by-name/system /system <
'/dev/block/platform/soc/1d84000.ufshc/by-name/system' is read-only
i'm out of idea
Someone have some try to suggest ?
Thank you
*Bump*
i'm the only one that is trying to mount RW the /system on Pie ?
adb root
adb disable-verity
adb reboot
adb root
adb remount
doesn't work for me , disable-verity not found
poloolop said:
adb root
adb disable-verity
adb reboot
adb root
adb remount
Click to expand...
Click to collapse
Hi poloolop,
i thank you for the try but ...
1) i have already the dm-verity disabled
2) i need to remount the /system from the shell command line inside the smartphone and not from the adb connected from a pc
hope that someone can solve this question ...
Thorezz said:
Hi poloolop,
i thank you for the try but ...
1) i have already the dm-verity disabled
2) i need to remount the /system from the shell command line inside the smartphone and not from the adb connected from a pc
hope that someone can solve this question ...
Click to expand...
Click to collapse
Hi Thorezz,
I had the same problem with my Mi8 on Android Pie. Flashing recovery twrp-3.2.3-0908.img sloved this problem. Warn you, i had the first start of recovery in Chinese.
Hi Rallbomban,
rallbomban said:
Hi Thorezz,
I had the same problem with my Mi8 on Android Pie. Flashing recovery twrp-3.2.3-0908.img sloved this problem. Warn you, i had the first start of recovery in Chinese.
Click to expand...
Click to collapse
thanks for trying but ... i've the problem with the twrp-3.2.3-0918 so it's a twrp newer than yours ... i also I noticed that the adway apk is able to mount and change the hosts file using some function of magisk (that i already have in my rooted system) so it's possibile to do but i'm unable to find how to do !
waiting for someone that have this knowledge
I had problem with newer recovery and only flashing older recovery solve it. But in my situation even Adaway couldn't change hosts file.
mount -o rw,remount /
mount -o rw,remount /dev/root
all geany is simply
No sry that doesn't work.. You have to flash the dm-verity-zip
Hi A.S._id
A.S._id said:
mount -o rw,remount /
mount -o rw,remount /dev/root
Click to expand...
Click to collapse
for sure you haven't read my question ...
1) the /etc it's in the system partiontion
2) on the n failed try that i've done (and that you can read on top of the thread) there is also "mount -o rw,remount /system" exactly as your answer ... and this don't work
anyway thank you for the try
Hi LUKI508,
LUKI508 said:
No sry that doesn't work.. You have to flash the dm-verity-zip
Click to expand...
Click to collapse
in my magisk manager the flag "keep AVB 2.0/dm-verity" is unchecked ... it'snt the same ?
Thank you
Thorezz said:
Hi A.S._id
for sure you haven't read my question ...
1) the /etc it's in the system partiontion
2) on the n failed try that i've done (and that you can read on top of the thread) there is also "mount -o rw,remount /system" exactly as your answer ... and this don't work
anyway thank you for the try
Click to expand...
Click to collapse
for sure you haven't read my answer
mount point of system in android 9 Pie now in root, so mount must have isn't /system, but root "/"...
And I'm tried it in my tv box x96 max android 9 Pie...
Hi A.S._id,
A.S._id said:
for sure you haven't read my answer
mount point of system in android 9 Pie now in root, so mount must have isn't /system, but root "/"...
And I'm tried it in my tv box x96 max android 9 Pie...
Click to expand...
Click to collapse
Doh ...
At first i thinking that you was joking ... i have done an ssh connection to my MI8 and i checked if the things are as you write and ... not ... i can confirm that the /etc is a symlink to /system/etc and /system is an autonomous mount point as you can see below
Code:
:/ # l -d /etc
lrwxrwxrwx 1 root root 11 Jan 1 1970 /etc -> /system/etc
1|:/ # mount | grep system
/dev/block/sde48 on /system type ext4 (ro,seclabel,relatime,discard,data=ordered)
so this confirm what i told you (and you can see that this is mounted RO) but ... i've done a try and ....
Code:
:/ # mount -o rw,remount /
no errors !
but if i try to create a file in /etc
HTML:
:/etc # touch thorezz
touch: thorezz: Read-only file system
1|:/etc # >thorezz
/system/bin/sh: can't create thorezz: Read-only file system
so the remount of / work but the /etc that it's in the /system don't become RW
and i can confirm that your suggestion don't work ...
thank you
P.S: all this with user root and /etc in writable by root ... just in case you think about this
Code:
:/etc # l -d .
drwxr-xr-x 27 root root 4096 Mar 21 14:38 .
@Thorezz
console:/ # mount -o rw,remount /
[ [email protected]] EXT4-fs (mmcblk0p18): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr,acl
console:/ # mount -o rw,remount /dev/root
[ [email protected]] EXT4-fs (mmcblk0p18): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr,acl
ps. your fstab
that has into /system/vendor/etc/fstab.qcom and etc has into /system/vendor/ too :yes:
and i think for you mount must have
Code:
[B]mount -o rw,remount /vendor[/B]
A.S._id said:
@Thorezz
console:/ # mount -o rw,remount /
[ [email protected]] EXT4-fs (mmcblk0p18): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr,acl
Click to expand...
Click to collapse
this work but don't solve the problem
console:/ # mount -o rw,remount /dev/root
[ [email protected]] EXT4-fs (mmcblk0p18): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr,acl
Click to expand...
Click to collapse
this don't work because in my phone does not exist /dev/root
ps. your fstab
that has into /system/vendor/etc/fstab.qcom and etc has into /system/vendor/ too :yes:
and i think for you mount must have
Code:
[B]mount -o rw,remount /vendor[/B]
Click to expand...
Click to collapse
my /system/vendor/etc/fstab.qcom is like your with a little difference only in this line
yours
Code:
/dev/block/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,noauto_da_alloc latemount,wait,check,reservedsize=128M,fileencryption=ice,quota
mine
Code:
/dev/block/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,noauto_da_alloc latemount,wait,check,reservedsize=128M,encryptable=ice,quota
i think that the parameter "fileencryption" and "encryptable" are synonyms
Code:
:/ # mount -o rw,remount /vendor
:/ # cd /etc
:/etc # >testfile
/system/bin/sh: can't create testfile: Read-only file system
nothing to do ... thank you for trying to help
any updates ?
---------- Post added at 09:41 PM ---------- Previous post was at 09:31 PM ----------
Try
mount -o rw,remount -t ext4 /full/path/to/modify
lapwat said:
any updates ?
Click to expand...
Click to collapse
nothing ... someone know the answer but take for self the correct procedure...
mount -o rw,remount -t ext4 /full/path/to/modify
Click to expand...
Click to collapse
[/QUOTE]
adding the filesystem type don't change the result ... the filesystem is autorecognized and re-mounted but without the write permission
thank you for the try
Thorezz said:
nothing ... someone know the answer but take for self the correct procedure...
adding the filesystem type don't change the result ... the filesystem is autorecognized and re-mounted but without the write permission
thank you for the try
Click to expand...
Click to collapse
I did
mount -o rw,remount /system/app/NQNfcNci
And it worked. Specify full path not only /system.
And you are right, ext4 option is not needed.
I found the solution
I know I am a bit late, but I was having issues modifying stuff in the /system/priv-app folder and every attempt of any mount call described up until now did NOT work.
BUT I found the solution: since I am using magisk (and you do too), the /system partition is somewhat "remapped" to /system_root.
So the solution is easy: just mount /system_root and you will be good to go:
Code:
mount -o rw,remount /system_root

Categories

Resources