I just tried to add variables on Android /etc/mkshrc file but I get an error:
Read-only file system
Click to expand...
Click to collapse
Further, I have tried to use adb remount, but it says inaccessible or not found.
I tried to use the following:
mount -o remount,rw /
Click to expand...
Click to collapse
But it says '/dev/block/dm-10' not user mountable in fstab.
Phone is Pixel 6
xracerx123 said:
I just tried to add variables on Android /etc/mkshrc file but I get an error:
Further, I have tried to use adb remount, but it says inaccessible or not found.
I tried to use the following:
But it says '/dev/block/dm-10' not user mountable in fstab.
Phone is Pixel 6
Click to expand...
Click to collapse
Hello and good morning, @xracerx123
Prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
and the others. I've moved your thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
what was your search result for Pixel 6 mount rw Read-only file system?
https://twitter.com/i/web/status/1170404631865778177
https://blog.esper.io/android-dessert-bites-25-erofs-in-android-13-47987123
Related
I have been attempting to apply a work around from tjayz thread for restoring recovery. In the CWD folder we are supposed to search for 5) Navigate to clockworkmod/download/download.clockworkmod.com/recoveries/
There you will see some two files - recovery-clockwork-4.0.0.4-p7100.img and recovery-clockwork-4.0.0.3-p7100.img
I only see files with names like -2110140792 and -21108160.
Does anyone know if you can rename these files as described in his post?
Thanks
Please use the Q&A Forum for questions Thanks
Moving to Q&A
I backed up my ROM before flashing UnNamed rom. I need to flash back to stock. When I go to Restore in ClockworkMod Recovery, no files are found. I can see my backup file on the sd card but not when I choose "Restore". I have the file also zipped on SD card and I've put it in the main directory on phone. If I try to load it from zip file, it starts but then says "installation aborted" after a few seconds.
Is there a certain place this recovery file is supposed to be located?
Or is there something I'm missing? Any help would be appreciated. I have the backup file and CWM is working fine, just can't seem to get the two together.
Thanks
supposed to be in
sd card/clockworkmod/backup/2011-xx-xx.xx.xx.xx
MOD ACTION: Thread moved to Q&A since this is not a development thread...
jconfus said:
supposed to be in
sd card/clockworkmod/backup/2011-xx-xx.xx.xx.xx
Click to expand...
Click to collapse
Thanks, that was it. I must have inadvertently moved or cut it. Put it back and I'm back in business. Thanks again.
Red5 said:
MOD ACTION: Thread moved to Q&A since this is not a development thread...
Click to expand...
Click to collapse
Sorry about that.
Suggestion: As you have written next to the other forums, put a qualifier in parenthesis after the Development Forum to help people narrow down where they should post when in doubt. eg After the General Forum you have (general chat, tips & tricks, etc).
Hi,
I've got a Motorola Flipout, just yesterday night I was copying and moving files to /system/bin (having root).
Lik this:
Code:
cp /sdcard/binaries/iptables-save /system/bin
But then I have did something wrong, typed something like this instead.
Code:
cp /sdcard/binaries/rfkill/system/bin
That throws me an error (normal) but then everything was screewed up.
The files and folders have been dissapeared to `ls` command.
`ls /` shows / doesn't exist.
`ls` shows nothing.
Every explorer (like root explorer) show nothing, when i enter to accounts it reboots, doesn't detect sdcard partition...
I do a rollback with a partial backup from 30 days ago, and still appear nothing.
It's like the partition system have been screewed up.
This can solved reflashin again with sbf_flash ?
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Device: Realme GT Explorer Master Edition (rmx3366). Android - 11 stock (RUI2.0_A.15). Bootloader - unlock. Root - Magisk_canary_92546e8a (patched boot.img).
1. Backup super.img by Partitions Backup & Restore or Universal Mount SystemRW.
2. Flash stock super.img without any changes
fastboot flash super super.img
3. Device does not boot into the system. Stays in fastboot mode.
Can anyone advise which way to dig?
The goal is to make the system partition writable. The problem is that it is not possible to write a super.img back, even without making any changes.
diogen78 said:
Device: Realme GT Explorer Master Edition (rmx3366). Android - 11 (RUI2.0_A.15). Bootloader - unlock. Root - Magisk_canary_92546e8a (patched boot.img).
1. Backup super.img by Partitions Backup & Restore or Universal Mount SystemRW.
2. Flash stock super.img without any changes
fastboot flash super super.img
3. Device does not boot into the system. Stays in fastboot mode.
Can anyone advise which way to dig?
The goal is to make the system partition writable. The problem is that it is not possible to write a super.img back, even without making any changes.
Click to expand...
Click to collapse
@diogen78
Prior to your next posting please read the guidances that are stuck on top of every forum like
[ATTN] : Read before posting - Any questions posted here will be MOVED or CLOSED
Please read the below before posting. Any questions not development related will be moved or closed. Forum Searching | Posting | The Basics: (Make sure you've read them before starting a new thread) Forum Rules Forum Search Google Forum...
forum.xda-developers.com
I've moved the thread to Q&A.
Regards
Oswald Boelcke
Senior Moderator
Hi everyone, I hope you're doing great
So, I'm currently trying to debloat some XOS ROMs which is Infinix's official firmware.
I have a problem repacking product.img since it doesn't have file_contexts which is required by the tools that repack .img files
IJoseph23 said:
Hi everyone, I hope you're doing great
So, I'm currently trying to debloat some XOS ROMs which is Infinix's official firmware.
I have a problem repacking product.img since it doesn't have file_contexts which is required by the tools that repack .img files
Click to expand...
Click to collapse
Hello and good afternoon, @IJoseph23
Welcome to XDA! I hope you'll always get the support you require.
However, prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
and the others. I've moved your thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
these kind of img files are partition images of linux file systems, sometimes sparsed with simg2img to reduce file size.
usually, partition images can mounted in linux only, same as partitions. windows is not capable of mounting linux file systems natively.
"extracting" linux images on windows is just some nasty hack and not intended for "repacking", because windows file system (NTFS) cannot handle linux file names and its metadata (like permissions, uid/gid, secontext)
the proper way is to mount (EXT4) partition image on linux, delete files, and unmount it.
additionally it might need img2simg/simg2img (not for dynamic partitions on super partition)