Hello im trying to port twrp from the G8 plus but for now im stuck with the twrp.fstab and the stock fstab, so they can't mount properly, specialy /system, also i have no idea how to make the touch screen to work, other than that everything seems to work, you can mount /data /mnt /cache /metadata etc, adb works. (you can use otg usb mouse to navigate through the recovery)
Can anyone help me please, this is the first time doing this.
this is the link to the recovery
mega.nz/file/rthTgRBY#vl0G_Z3Hue_M0MVBl4wHCYJGcSrUZmO6rmATWCRImCM
krissrmus said:
Hello im trying to port twrp from the G8 plus but for now im stuck with the twrp.fstab and the stock fstab, so they can't mount properly, specialy /system, also i have no idea how to make the touch screen to work, other than that everything seems to work, you can mount /data /mnt /cache /metadata etc, adb works. (you can use otg usb mouse to navigate through the recovery)
Can anyone help me please, this is the first time doing this.
this is the link to the recovery
mega.nz/file/rthTgRBY#vl0G_Z3Hue_M0MVBl4wHCYJGcSrUZmO6rmATWCRImCM
Click to expand...
Click to collapse
I'm not an expert for this but I noticed that other fstab files for Moto Gs contain "discard" as an additional flag in recovery.fstab:
Code:
/dev/block/bootdevice/by-name/system / ext4 ro,barrier=1,discard wait,slotselect
WoKoschekk said:
I'm not an expert for this but I noticed that other fstab files for Moto Gs contain "discard" as an additional flag in recovery.fstab:
Code:
/dev/block/bootdevice/by-name/system / ext4 ro,barrier=1,discard wait,slotselect
Click to expand...
Click to collapse
well this are my twrp.fstab
# mount point fstype device device2 flags
/boot emmc /dev/block/bootdevice/by-name/boot defaults flags=slotselect
/system ext4 /dev/block/bootdevice/by-name/system ro,barrier=1,discard flags=slotselect
/data f2fs /dev/block/bootdevice/by-name/userdata noatime,nosuid,nodev,barrier=1, data=ordered,noauto_da_alloc flags=fileencryption=ice:aes-256-cts
/firmware vfat /dev/block/bootdevice/by-name/modem flags=slotselect;display="Firmware";mounttodecrypt;fsflags=ro
/misc emmc /dev/block/bootdevice/by-name/misc defautls
/modem emmc /dev/block/bootdevice/by-name/modem flags=slotselect;backup=1;display="Modem"
/bluetooth emmc /dev/block/bootdevice/by-name/bluetooth flags=slotselect;backup=1;subpartitionof=/modem
/dsp emmc /dev/block/bootdevice/by-name/dsp flags=slotselect;backup=1;subpartitionof=/modem
/efs1 emmc /dev/block/bootdevice/by-name/modemst1 flags=backup=1;display=EFS
/efs2 emmc /dev/block/bootdevice/by-name/modemst2 flags=backup=1;subpartitionof=/efs1
/efsc emmc /dev/block/bootdevice/by-name/fsc flags=backup=1;subpartitionof=/efs1
/efsg emmc /dev/block/bootdevice/by-name/fsg flags=backup=1;subpartitionof=/efs1
/persist ext4 /dev/block/bootdevice/by-name/persist flags=display="Persist"
/sdcard vfat /dev/block/mmcblk1p1 nosuid,nodev flags=display="SdCard";slotselect,avb,wait,defaults
/recovery emmc /dev/block/bootdevice/by-name/recovery defautls
# Removable storage
/usbstorage vfat /dev/block/sdg1 /dev/block/sdg flags=fsflags=utf8;display="USB Storage";storage;wipeingui;removable
/sdcard1 auto /dev/block/mmcblk1p1 flags=display="MicroSD";storage;wipeingui;removable
and this is my recovery.fstab
#device mount point fstype [device2] [length=] flags
/dev/block/bootdevice/by-name/system / ext4 ro,barrier=1 wait,slotselect,avb
/dev/block/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc wait,check,encryptable=footer
/dev/block/mmcblk1p1 /sdcard vfat nosuid,nodev wait
/dev/block/bootdevice/by-name/boot /boot emmc defaults defaults
/dev/block/bootdevice/by-name/recovery /recovery emmc defaults defaults
/dev/block/bootdevice/by-name/misc /misc emmc defaults defaults
and this is my recovery.log
mediafire.com/file/bpkupivtjm3a2o2/recovery.log/file
i think that maybe the dm-verasity is not letting me to mount system but who knows, help again any idea
@Augustoandro
Nice to see you are trying to port twrp , i recomend you to open a telegram account and ask for help in oficial moto g8 group
krissrmus said:
i think that maybe the dm-verasity is not letting me to mount system but who knows, help again any idea
@Augustoandro
Click to expand...
Click to collapse
You should read this
https://source.android.com/devices/tech/ota/dynamic_partitions/implement
WoKoschekk said:
You should read this
https://source.android.com/devices/tech/ota/dynamic_partitions/implement
Click to expand...
Click to collapse
yes that is a problem now
You have to insmod the touchscreen driver from the vendor partition to get it working. Check the bin files in twrp for a load modules script and edit it to suit your device. Or give me the twrp image and I'll work on it. I don't have your device so I'll need someone to run a command via termux or adb at some point.
Spaceminer said:
You have to insmod the touchscreen driver from the vendor partition to get it working. Check the bin files in twrp for a load modules script and edit it to suit your device. Or give me the twrp image and I'll work on it. I don't have your device so I'll need someone to run a command via termux or adb at some point.
Click to expand...
Click to collapse
Which command?
WoKoschekk said:
Which command?
Click to expand...
Click to collapse
Give me a few. I gotta check the script in my twrp and I need to pull it apart on device because I'm lacking a pc right now.
---------- Post added at 08:35 PM ---------- Previous post was at 08:20 PM ----------
WoKoschekk said:
Which command?
Click to expand...
Click to collapse
Code:
cat /sys/devices/virtual/graphics/fb0/panel_supplier
Spaceminer said:
Give me a few. I gotta check the script in my twrp and I need to pull it apart on device because I'm lacking a pc right now.
---------- Post added at 08:35 PM ---------- Previous post was at 08:20 PM ----------
Code:
cat /sys/devices/virtual/graphics/fb0/panel_supplier
Click to expand...
Click to collapse
Output:
Code:
auo
---------- Post added at 02:42 AM ---------- Previous post was at 02:41 AM ----------
I don't have a G8! My phone is a G6+.
WoKoschekk said:
Output:
Code:
auo
---------- Post added at 02:42 AM ---------- Previous post was at 02:41 AM ----------
I don't have a G8! My phone is a G6+.
Click to expand...
Click to collapse
Why are you concerned about the output of the display driver if you don't have the device in question? This does not make any sense or serve any purpose except wasting my time. I'm not trying to sounds harsh or anything but that is some baffling sh*t to be honest. This is akin to asking an aviation mechanic to fix your plane, and bringing him a car instead.
@Spaceminer
1. for MOTO G8:
boev
inxr
2. take a look into his log. This would solve problem 1/20. There is still a big problem to mount super.img
And I still don't have a Moto G8. To get this information a simple download of the firmware zip would have been enough.
WoKoschekk said:
@Spaceminer
1. for MOTO G8:
boev
inxr
2. take a look into his log. This would solve problem 1/20. There is still a big problem to mount super.img
And I still don't have a Moto G8. To get this information a simple download of the firmware zip would have been enough.
Click to expand...
Click to collapse
"2. take a look into his log. This would solve problem 1/20. There is still a big problem to mount super.img"
Who's log, and what "super.img" ? - Are you okay, seriously? You're not making much sense at all. These are the kind of responses I'd expect from someone who doesn't know what they're talking about, has mental health issues that need addressed, or someone who's using illicit substances. Your replies raise some red flags with me. Send me a PM if you need to.
Spaceminer said:
"2. take a look into his log. This would solve problem 1/20. There is still a big problem to mount super.img"
Who's log,
Click to expand...
Click to collapse
Post #3...
Spaceminer said:
and what "super.img" ?
Click to expand...
Click to collapse
Nothing...
- Are you okay, seriously? You're not making much sense at all.
Click to expand...
Click to collapse
I'm fine, thanks! You? What we are talking about here? Cars? Xbox? Oh no... Moto G8 with sth called... wait... ah, dynamic partitions! Should I explain it?
YOU SHOULD READ AT LEAST ONE OF THESE POSTS HERE BEFORE ANSWERING THIS WAY!
---------- Post added at 07:28 AM ---------- Previous post was at 07:24 AM ----------
Here, A SECOND TIME in this thread:
https://source.android.com/devices/tech/ota/dynamic_partitions/implement
krissrmus said:
Hello im trying to port twrp from the G8 plus but for now im stuck with the twrp.fstab and the stock fstab, so they can't mount properly, specialy /system, also i have no idea how to make the touch screen to work, other than that everything seems to work, you can mount /data /mnt /cache /metadata etc, adb works. (you can use otg usb mouse to navigate through the recovery)
Can anyone help me please, this is the first time doing this.
this is the link to the recovery
mega.nz/file/rthTgRBY#vl0G_Z3Hue_M0MVBl4wHCYJGcSrUZmO6rmATWCRImCM
Click to expand...
Click to collapse
I'll work on it tonight. It'd be helpful if you can link the stock recovery.img or stock boot.img instead if you don't have an actual recovery partition. It'd also be great if you can pull /vendor/etc/fstab.qcom and attach that. (Rename .qcom to .txt and xda will allow the attachment.) It would save me a bunch of time. I have WiFi but it's slow, so I really don't want to download the entire firmware if I don't need to. I should have all the info I need in the thread to fix it up.
Any chance that the twrp.img had a dtbo.img built along with it? If so I also need that so I can append it to twrp. If not then don't worry about it. I'll probably have it working by the morning. I've had to do this so many times already, it's practically a cake walk at this point.
Spaceminer said:
I'll work on it tonight. It'd be helpful if you can link the stock recovery.img or stock boot.img instead if you don't have an actual recovery partition. It'd also be great if you can pull /vendor/etc/fstab.qcom
Click to expand...
Click to collapse
https://mega.nz/file/NiIkRSJK#SmgBH5s_NTlRgOKq3s78XgDt-0PbFaHBJLyR8d9XZdg
WoKoschekk said:
https://mega.nz/file/NiIkRSJK#SmgBH5s_NTlRgOKq3s78XgDt-0PbFaHBJLyR8d9XZdg
Click to expand...
Click to collapse
Sweet!
We're almost there! Someone who has a Moto G8 needs to run the following command from either termux, or adb shell.
Code:
ls /sys/devices/virtual/touchscreen
This will give you a folder name. Then you need to run the following command and give me the result. Pay attention to where the folder name goes in this next command.
Code:
cat /sys/devices/virtual/touchscreen/"folder-name-here-no-quotes"/vendor
I need that result. This will be the name of the module we need to insmod to get the touchscreen working. I'll need that to fix up the scripts that load your drivers.
Spaceminer said:
Code:
cat /sys/devices/virtual/touchscreen/"folder-name-here-no-quotes"/vendor
Click to expand...
Click to collapse
Why the first command?
Code:
cat /sys/devices/virtual/touchscreen/*/vendor
---------- Post added at 05:07 PM ---------- Previous post was at 05:03 PM ----------
If you like you can download all single images (zip compressed) of the firmware here:
https://mega.nz/folder/Rz5nXKwZ#x7UbIuCkfMhxX4R9iJ9awQ
I uploaded them yesterday, just in case they were needed.
Code:
cat /sys/devices/virtual/touchscreen/*/vendor
Output: focaltech
Inside the attached zip you find the corresponding files from /vendor partition
Related
How to make an Odin flashable ROM
This is just a small guide I want to share with anyone who's interested in the commands I personally use. Feel free to correct me or give better commands / instructions.
@Moderators:
If this thread is in the wrong section or already present at XDA, PM me.
This needs a UNIX compatible OS - like Linux or Mac OS X.
On Windows, you can use "Cygwin".
Click to expand...
Click to collapse
Use the dd (datadump) command to make the .rfs files
Of course you need to connect your phone via USB and have ADB prepared on your computer.
# Get Root access first
Code:
su
# Do this first to mount the /system R/W
(thanks to scheichuwe for the simplified command)
Code:
mount -o remount,rw /dev/block/stl9 /system
# Dump the needed data / partitions to your /sdcard
Code:
dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096
dd if=/dev/block/stl11 of=/sdcard/cache.rfs bs=4096
dd if=/dev/block/bml7 of=/sdcard/zImage bs=4096
dd if=/dev/block/bml12 of=/sdcard/modem.bin bs=4096
# Make the tar ball
Code:
tar -H ustar -c factoryfs.rfs cache.rfs modem.bin zImage > darky.tar
# MD5 it for a security check
Code:
md5sum –t darky.tar >> darky.tar
# Rename the tar file
Code:
mv darky.tar darky.tar.md5
Optional:
Make your own pit file
The pit file is used to set the partition layout (Partition Information Table).
# Dump the pit
Code:
dd if=/dev/block/bml2 of=/sdcard/darky.pit bs=4096
I hope I could help you with that
- darkyy.
Nice
Yeah first
Oh and one more thing:
If someone is gonna rate this thread 1 star, please explain here why.
So this means I can make an Odin rom of my current installed config? Or am I missing something?
If you then flash your tar + pit, you have your kernel and rom restored? This would be an awesome way to backup a good config, no?
VenQWish said:
So this means I can make an Odin rom of my current installed config? Or am I missing something?
If you then flash your tar + pit, you have your kernel and rom restored? This would be an awesome way to backup a good config, no?
Click to expand...
Click to collapse
Exactly - these commands will dump the data directly from your current phone.
And yes, you'll have a 1 to 1 Backup.
That is actually VERY useful! I'm constantly switching between a modded Insanity and CM7, and constantly reverting to stock, flashing custom kernels and flashing nandroids is getting quite annoying now.
Don't have access to a linux machine now, I'll try this asap, thanks!
Wow, dasch mal nützlich ville dank^^
Neat. Thank you!
Quipeace said:
That is actually VERY useful! I'm constantly switching between a modded Insanity and CM7, and constantly reverting to stock, flashing custom kernels and flashing nandroids is getting quite annoying now.
Don't have access to a linux machine now, I'll try this asap, thanks!
Click to expand...
Click to collapse
Well you can install cygwin, just remember to install bash terminal when cygwin setup is running.
Sent from my GT-P1000 using Tapatalk
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
Galaxy S is running on yaffs2? Interesting
Code:
mount -o rw,remount /system
That should work too...
Is this the same as this?
http://forum.xda-developers.com/showthread.php?t=943588
Mackzen said:
Is this the same as this?
http://forum.xda-developers.com/showthread.php?t=943588
Click to expand...
Click to collapse
No:
The instructions from drakyy create a flashable ROM from the phone.
The Application from bohdans creates a flashable ROM from files on your computer
scheichuwe said:
Galaxy S is running on yaffs2? Interesting
Code:
mount -o rw,remount /system
That should work too...
Click to expand...
Click to collapse
Thanks - gonna change it in the first post
Verified?
Cool stuff Darkyy,
is this working without any issues, any testers?
mr_at_sgs said:
Cool stuff Darkyy,
is this working without any issues, any testers?
Click to expand...
Click to collapse
It's what we used for the Darky's Resurrection Edition
Damn. Left my laptop charger at work. Just when I need battery also.
Great thread. Thank you.
Tricky103 UltraSlim Essential Rom on DamianGTO Ultimate kernel
I have a problem. When tryign to create the tar-file i get:
cannot create jesper.tar: read-only file system.
What to do?
Does this also work when the partitions are NOT RFS.
Like all in ext4?
Will Odin be able to flash that image?
I somehow doubt it...
zurchpet said:
Does this also work when the partitions are NOT RFS.
Like all in ext4?
Will Odin be able to flash that image?
I somehow doubt it...
Click to expand...
Click to collapse
Good question..... I'd like to know this too..
Although even if having to disable lag fix to create it the apply again after flashing is still a quicker way to toggle between your current rom and cm7..
Neat Darky
but can i do these dumps on the phone without a pc or adb
Sent from my GT-I9000 using XDA App
Perhaps some could write a script to do this at the phone
Sent from my GT-I9000 using XDA App
I'm currently trying to use adb to push a ROM to my sdcard on my Verizon Galaxy Nexus. However, it keeps failing due to /sdcard being a read-only filesystem.
When I adb shell into the phone and type mount, i get this (among others):
Code:
/dev/block/mmcblk0p12 on /sdcard type ext4 <ro,relatime,barrier=1,data=ordered>
Attempting to mount /sdcard as read-write is not proving fruitful:
Code:
mount -o remount rw /sdcard
Can anyone help? I'm just trying to get a rom on there so i can install it. Unfortunately, the phone never leaves the google screen when i try to boot, so recovery and fastboot are my only options.
mount -o rw,remount /dev/block/mmcblk0p12 /sdcard
try that
DonDizzurp said:
mount -o rw,remount /dev/block/mmcblk0p12 /sdcard
try that
Click to expand...
Click to collapse
Thanks for the help. It now mounts as rw. However, when i try to
Code:
adb push C:\rom.zip /sdcard/rom.zip
It fails and i get a Fil I/O error.
ttremblay said:
Thanks for the help. It now mounts as rw. However, when i try to
Code:
adb push C:\rom.zip /sdcard/rom.zip
It fails and i get a Fil I/O error.
Click to expand...
Click to collapse
To make things easier, copy the .zip file to the folder where you have ADB then try
adb push ./rom.zip /sdcard/rom.zip
I never could get things to push to sdcard while in recovery mode no matter what I tried.
adb sideload was how I always did I
---------- Post added at 04:52 AM ---------- Previous post was at 04:51 AM ----------
Or maybe instead of using "/sdcard" use "/data/media"?
Hello there, my samsung galaxy s2 i9100's internal sdcard suddenly became read-only shortly after updating it to 4.1. I've tried using the command: ''mount -o remount, rw /sdcard'' which works until i reboot or connect it to an external usb storage device. I'm kindly asking if anyone knows a permanent solution to my problem. P.S- I'm a bit new to this android thing so make your explanations as easy as possible. Please help
So last night i finally decided to install JetiX20. Installation ran smoothly until reboot.
hmm ... stuck on Samsung galaxy note 2 logo for over 45 mins.
Reboot into clockworkMod recovery v6.0.4.3
Code:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Cant open /cache/recovery/last_log
So.. i tried to wipe data/factory reset and cache partition....
Code:
--wiping data--
formatting /data...
error mounting /data!
skipping format...
formatting /cache...
E: format_volume:make_extf4fs failed on /dev/block/mmcblk0p12
formatting /sd-ext...
formatting /sdcard/.android_secure...
E: unknown volume "/sdcard/.android_secure"
data wipe complete
So, now i move to adb:
[email protected]:~$ adb devices
List of devices attached
42f7410e7bc79f3f recovery
Code:
~ # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 67.1 GB, 67108864000 bytes
4 heads, 16 sectors/track, 2048000 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 2048000 65535992 83 Linux
~ #
Code:
# mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,mode=775,gid=1000)
Some how i manage to corrupt my mobile's partition?
I tried Odin, Heimdall, fastboot and adb as per recommended on the forum.
Is there anything else i could try?
Thanks for any advices.
You should re-flash the stock ROM of Samsung Galaxy Note 2 through ODIN.
I did, still getting the very same error.
May need to fix partitions by flashing a PIT file...
Zen Arcade has a pit thread in the development section...
Read EVERYTHING before flashing a PIT....g
gregsarg said:
May need to fix partitions by flashing a PIT file...
Zen Arcade has a pit thread in the development section...
Read EVERYTHING before flashing a PIT....g
Click to expand...
Click to collapse
I sure will read up on it. thanks
http://forum.xda-developers.com/showthread.php?t=2609871
There they are...
Again....I cannot stress enough the importance of reading every word Zen posted on the subject...
And remember....the PIT may not be your issue....so evaluate carefully...
I bid you good luck....g
Hello again
So sadly I'm still having the same issue, looks like everything install/runs ok but at reboot the phone still at bootloop when I try to pull the logs from the device all I get is can't mount mmcblk0p12.
Are you getting a "cannot mount sd card " in that error message ??
That error would indicate a failed partition on the emmc..
This is not looking good.....g
No just can't mount/open /cache/recovery.
But on wipe data/factory reset one of the lines say "E: unknown volume "/sdcard/.android_secure".
I can't find anything else that will give me that error.
Okay ...please post the link to the stock rom you are trying to flash....and also tell us what bootloader version you have..g
gregsarg said:
Okay ...please post the link to the stock rom you are trying to flash....and also tell us what bootloader version you have..g
Click to expand...
Click to collapse
Hi greg, this is the link http://forum.xda-developers.com/galaxy-note-2-att/development/rom-att-i317-ucucne5-mj4-stock-odex-t2802189 and i am pretty sure NE5.
at first i though it was the actual external sd card, but then after some more careful reading, mmcblk0p12 is a partition of my internal storage correct?
Yep....emmc
And if those permanent partitions are whacked ....then it's bye bye phone....
No PIT will fix the emmc...it would be a chip replacement or new phone..
The emmc is essentially the boot sector of the device...g
gregsarg said:
Yep....emmc
And if those permanent partitions are whacked ....then it's bye bye phone....
No PIT will fix the emmc...it would be a chip replacement or new phone..
The emmc is essentially the boot sector of the device...g
Click to expand...
Click to collapse
Well thats a shame is there another way to verify the status of the emmc or this is pretty much it?is just strange how i try to install the JediX20 rom before and installed ok still boot, i would figure it will give errors installing and hang.
Oh well... ill try a few more times before i decide to move onto hardware
thanks greg.
Hello again everyone
So doing some more reading last night about my issue and found this:
****@****:~$ adb shell cat /sys/block/mmcblk0/device/manfid
0x000000
Will this confirm the issue to be with the chip?
thanks. \m/
One last attempt here...
Format your external SD CARD to FAT32 on a PC....then reload it into the device and reflash your rom....g
Omg Greg I was just about to do that lmao. Thanks working on it
While this is formatting I have a question. I just noticed that I can only see mmcblk0 when the external card is in. Why would that be?
Thanks.
I hope this doesn't come up twice. External SD formatted to fat32... Try installing ucune5.. Odin said it pass but still stuck on logo after reboot
Chamo709 said:
While this is formatting I have a question. I just noticed that I can only see mmcblk0 when the external card is in. Why would that be?
Thanks.
Click to expand...
Click to collapse
Because your device is trying to mount the storage block....and the mmcblk0 is the address...
I'm hoping it's an external error and not internal...because the emmc will give similar errors....g
---------- Post added at 05:08 PM ---------- Previous post was at 05:07 PM ----------
Chamo709 said:
I hope this doesn't come up twice. External SD formatted to fat32... Try installing ucune5.. Odin said it pass but still stuck on logo after reboot
Click to expand...
Click to collapse
Wipe data....factory reset in recovery...g
Ok... So no bueno still getting the same exact error ... What a shame really. I guess next step is getting a new board?
trying lots but ab shell say system is read only ??
Krprem said:
trying lots but ab shell say system is read only ??
Click to expand...
Click to collapse
#1 you need to be rooted, if you're not this won't work
Mount system RW: mount -o rw,remount,rw /system
Mount system RO: mount -o ro,remount,ro /system
dicksteele said:
#1 you need to be rooted, if you're not this won't work
Mount system RW: mount -o rw,remount,rw /system
Mount system RO: mount -o ro,remount,ro /system
Click to expand...
Click to collapse
i try its work but when i reboot modifiy file gone away ...??
any premanet fix bro ??
thank u in advance
Krprem said:
i try its work but when i reboot modifiy file gone away ...??
any premanet fix bro ??
thank u in advance
Click to expand...
Click to collapse
You must not have saved it right or something.
Find a file manager in playstore that can do root privileges.
Or since you know adb. Pull the file, edit it then push it back.
Adb pull /system/build.prop
Edit the file
Adb push /system/build.prop
Bro can u give me step by step instruction about adb push and pull
Can i edit my efs folder because i lost my csc code and sn number
I am trying to add new folder in efs
Has anyone been able to remount /system as rw? FX File Explorer says it's successful but then switches automatically back to read only
I'm also trying to remount /system as rw. It seems that the patched Magisk boot file provided in this post preserves dm-verity, which disallows system partition modifications and makes it unable to remount as rw. The mount command will complain that '/dev/block/dm-8' is read-only.
Having tried repatch the boot image with unchecked 'preserve AVB 2.0/dm-verity' in the Magisk app, but resulted in a crash during boot (QUALCOMM CrashDump Mode). Can succesfully boot with that option checked. It would be fine if dm-verity can be disabled in other ways.
ichimei said:
I'm also trying to remount /system as rw. It seems that the patched Magisk boot file provided in this post preserves dm-verity, which disallows system partition modifications and makes it unable to remount as rw. The mount command will complain that '/dev/block/dm-8' is read-only.
Having tried repatch the boot image with unchecked 'preserve AVB 2.0/dm-verity' in the Magisk app, but resulted in a crash during boot (QUALCOMM CrashDump Mode). Can succesfully boot with that option checked. It would be fine if dm-verity can be disabled in other ways.
Click to expand...
Click to collapse
Have you tried fastboot?
fastboot oem disable_dm_verity
If it causes problems, replace disable with enable to get back to current state, but it shouldn't
I don't like to disable dm verity for performance concerns, but for now it would be okay until a new root method comes out
Josh McGrath said:
Have you tried fastboot?
fastboot oem disable_dm_verity
If it causes problems, replace disable with enable to get back to current state, but it shouldn't
I don't like to disable dm verity for performance concerns, but for now it would be okay until a new root method comes out
Click to expand...
Click to collapse
FAILED (remote: 'unknown command')
Finished. Total time: 0.004s
Click to expand...
Click to collapse
It was worth a shot
blackknightavalon said:
It was worth a shot
Click to expand...
Click to collapse
Are you able to flash with TWRP by any chance?
Josh McGrath said:
Are you able to flash with TWRP by any chance?
Click to expand...
Click to collapse
TWRP doesn't mount /system at the moment on anyone's devices
Correct me if I'm wrong,but devices released with Android 10 out if the box will not allow making changes to the system( i.e it will remain read-only only)
WillSmith89 said:
Correct me if I'm wrong,but devices released with Android 10 out if the box will not allow making changes to the system( i.e it will remain read-only only)
Click to expand...
Click to collapse
That's what I'm working on. I tried a workaround but got this
mount -o rw,remount /
'/dev/block/dm-8' is read-only
Click to expand...
Click to collapse
I'm trying other things as I think of them, and I have a few ideas
blackknightavalon said:
That's what I'm working on. I tried a workaround but got this
I'm trying other things as I think of them, and I have a few ideas
Click to expand...
Click to collapse
Do you know if stock Oneplus recovery will flash unsigned zips?
Not sure. Got one I can flash via Fastboot?
blackknightavalon said:
Not sure. Got one I can flash via Fastboot?
Click to expand...
Click to collapse
Maybe, let me go through my old files cause I think I have dmverity disabler for stock recovery zip
Okay, I'm getting closer. Typing in
mount -o rw,remount /system
Click to expand...
Click to collapse
as usual gives me the "not in /proc/mounts" thing, but typing in
mount -o rw,remount /product
Click to expand...
Click to collapse
gives me the "/product is read only" error.
What we need is a kernel that'll let us mount /product in order for us to REALLY start playing with this device
------------------------------------------------------------------------------------
Okay, here's the Terminal results of my latest attempts. Maybe someone can have better luck than me
OnePlus7T:/ $ su
OnePlus7T:/ # mount -o rw,remount /sbin/.magisk/block/system_root
'/sbin/.magisk/block/system_root' is read-only
OnePlus7T:/ # mount -o rw,remount /dev/block/dm-11
'/dev/block/dm-11' is read-only
OnePlus7T:/ # mount -o rw,remount /dev/block/dm-9
'/dev/block/dm-9' is read-only
OnePlus7T:/ # mount -o rw,remount /dev/block/dm-8
'/dev/block/dm-8' is read-only
OnePlus7T:/ # mount -o rw,remount /dev/block/dm-8 /system
mount: '/system' not in /proc/mounts
1|OnePlus7T:/ # mount -o rw,remount /dev/block/dm-8 /system/product
mount: '/system/product' not in /proc/mounts
1|OnePlus7T:/ # mount -o rw,remount /product
'/dev/block/dm-9' is read-only
OnePlus7T:/ # mount -o rw,remount /super
mount: '/super' not in /proc/mounts
1|OnePlus7T:/ # mount -o rw,remount /product
'/dev/block/dm-9' is read-only
OnePlus7T:/ # ls -l /dev/block/by-name/super
lrwxrwxrwx 1 root root 16 1970-01-12 02:43 /dev/block/by-name/super -> /dev/block/sda15
OnePlus7T:/ # mount -o rw,remount /dev/block/sda15
mount: '/dev/block/sda15' not in /proc/mounts
1|OnePlus7T:/ # mount -o rw,remount /dev/block/by-name/super
mount: '/dev/block/by-name/super' not in /proc/mounts
1|OnePlus7T:/ # mount -o rw,remount /init
mount: '/init' not in /proc/mounts
1|OnePlus7T:/ # mount -o rw,remount /system/etc/init
'/sbin/.magisk/block/system_root' is read-only
OnePlus7T:/ #
Click to expand...
Click to collapse
Okay, I have an idea but I'll have to wait for the next official build to test it
Any news on this? Really want to uninstall Google Pay and install an older version of it.
blackknightavalon said:
Okay, I have an idea but I'll have to wait for the next official build to test it
Click to expand...
Click to collapse
I'm not much help but wanted to throw some ideas out thee. have you also tried changing read/write via fastboot or terminal emulator with (I think) chmod 777?
Josh McGrath said:
I'm not much help but wanted to throw some ideas out thee. have you also tried changing read/write via fastboot or terminal emulator with (I think) chmod 777?
Click to expand...
Click to collapse
Tried it through Terminal commands via Terminal Emulator AND ADB. Haven't tried it through fastboot. I'm downloading the OTA now (been in Florida on vacation, leaving back for NYC this afternoon)
I tried to change font, but I cant remount system. any idea? ( the mogule font_changer has remove of programmer, my device is root without twrp.
You cant mount system as r/w because android 10 is read only