I have the same issue as reported here: http://forum.xda-developers.com/showpost.php?p=64003605&postcount=108
I can't see the former poster got an reply, but is there a way to fix this? TWRP reports it cannot mount system due to it being read-only. Unchecking read-only on system mount within TWRP does not work.
ksjoet said:
I have the same issue as reported here: http://forum.xda-developers.com/showpost.php?p=64003605&postcount=108
I can't see the former poster got an reply, but is there a way to fix this? TWRP reports it cannot mount system due to it being read-only. Unchecking read-only on system mount within TWRP does not work.
Click to expand...
Click to collapse
I'm sure it's fixable, but it needs some device-specific knowlegde. The thing here is that the Z4T's TWRP build is a custom one by AndroPlus with the help of dl12345. I have asked them for help in the AndroPlus kernel thread.
I'm looking into possible workarounds. Maybe we can backup/restore using adb, or boot another custom recovery from fastboot that does the job.
Related
So a quick catch up is needed: I accidentally wiped my system in TWRP recovery. I have now been able to push the ROM back to TFP via ADB. All seems to be ok.
Issues:
1) When flashing the rom zip I got a failed message after TWRP checked partitions, anyone know what to do with this?
2) TWRP only will allow me to install from /data directory, is this normal and will this hinder rom flash?
Any insights or knowledge of existing threads with answers would be really appreciated. Thanks for reading this too btw, I'm new so anything will be helpful.
Thanks again.
tstern0112 said:
So a quick catch up is needed: I accidentally wiped my system in TWRP recovery. I have now been able to push the ROM back to TFP via ADB. All seems to be ok.
Issues:
1) When flashing the rom zip I got a failed message after TWRP checked partitions, anyone know what to do with this?
2) TWRP only will allow me to install from /data directory, is this normal and will this hinder rom flash?
Any insights or knowledge of existing threads with answers would be really appreciated. Thanks for reading this too btw, I'm new so anything will be helpful.
Thanks again.
Click to expand...
Click to collapse
I haven't personally used TWRP but I've seen in the buglist that sometimes it could mess up with particularly large ROM files. However, I have not tested this firsthand because I know my prime is sort of like a moribund insect; you touch it, it dies.
Sent from my tf9001 with XDA XD.
tstern0112 said:
So a quick catch up is needed: I accidentally wiped my system in TWRP recovery. I have now been able to push the ROM back to TFP via ADB. All seems to be ok.
Issues:
1) When flashing the rom zip I got a failed message after TWRP checked partitions, anyone know what to do with this?
2) TWRP only will allow me to install from /data directory, is this normal and will this hinder rom flash?
Any insights or knowledge of existing threads with answers would be really appreciated. Thanks for reading this too btw, I'm new so anything will be helpful.
Thanks again.
Click to expand...
Click to collapse
The /data directory is the only partition I have ever flashed a ROM from. /data is just internal memory Where does ADB push put the file by default, at the root?
It sounds like you may need to re-partition your device. I guess when you wipe /system in twrp, it doesn't create a new /system partition? Or maybe it wiped everything? The TWRP thread can probably answer these questions, but my guess is that you just need to create a new partition(s) or if the partitions are okay just adb push the file to the right spot. I've never done that before in ADB, hopefully it isn't complicated? Good luck man, ask the Team Win thread if you have questions, I bet they can help!
Komodo Rogue said:
The /data directory is the only partition I have ever flashed a ROM from. /data is just internal memory Where does ADB push put the file by default, at the root?
It sounds like you may need to re-partition your device. I guess when you wipe /system in twrp, it doesn't create a new /system partition? Or maybe it wiped everything? The TWRP thread can probably answer these questions, but my guess is that you just need to create a new partition(s) or if the partitions are okay just adb push the file to the right spot. I've never done that before in ADB, hopefully it isn't complicated? Good luck man, ask the Team Win thread if you have questions, I bet they can help!
Click to expand...
Click to collapse
Thanks so much.. Yeah I've been reading up on this and of course there's always more to the story haha I talked to an old linux engineer and he agrees with you that there is probably something going on with partitions. I'll head over to TWRP and see if they have any ideas. Thanks for your help.
Hey everyone,
A few days ago, I decided to downgrade from AICP 11 back to 10 (Android 6.0.1 to 5.1.1), wiped everything but internal storage. When flashing, I got an error, saying that the /vendor partition was missing, and indeed, while it existed, I could only mount it forcefully, because the device was busy.
This lead to a complete wipe, as after a reboot, TWRP asked for an encryption password, which I didn't set. Here, I did a factory reset & wiped everything. After that, I tried flashing again (5.1.1), but after it was completed, I got a line, which said "Couldn't unmount /system", which is true, as it's already unmounted. But when I mount it, all the files that are supposed to be installed seem to be there.
When I reboot the device, it gets stuck on the Google logo.
Frankly, I'm afraid to even flash back to stock, so I was hoping that someone more experienced could help me out.
It should be noted, that I still have access to fastboot, and TWRP.
Thanks in advance,
DecentM
How did you force mount /vendor?
Can you clarify where you are seeing these problems? (TWRP or within Android)
Do you have any nandroid backups to test and see if they work?
dmantilal said:
How did you force mount /vendor?
Can you clarify where you are seeing these problems? (TWRP or within Android)
Do you have any nandroid backups to test and see if they work?
Click to expand...
Click to collapse
I used mount -f and umount -f in the TWRP terminal
I see all these problems in TWRP, since I can't boot/get past the initial Google logo.
I do have a nandroid backuip on my laptop (as I had to wipe the tablet clean), but that's currently unavailable for me to use, I'll reply back when I tried it.
I doubt it will work, because it just extracts data to a predefined path, which seems like the same thing an installer zip does.
DecentM said:
I used mount -f and umount -f in the TWRP terminal
I see all these problems in TWRP, since I can't boot/get past the initial Google logo.
I do have a nandroid backuip on my laptop (as I had to wipe the tablet clean), but that's currently unavailable for me to use, I'll reply back when I tried it.
I doubt it will work, because it just extracts data to a predefined path, which seems like the same thing an installer zip does.
Click to expand...
Click to collapse
Why did you need /vendor mounted in TWRP?
I thought flashing used dd (command) or similar to copy the *.img file to the partition (or, more accurately, the block device). If /vendor is mounted during *.img copy, that would most likely cause errors.
dmantilal said:
Why did you need /vendor mounted in TWRP?
I thought flashing used dd (command) or similar to copy the *.img file to the partition (or, more accurately, the block device). If /vendor is mounted during *.img copy, that would most likely cause errors.
Click to expand...
Click to collapse
I mounted it, because when I initially restored the 5.1.1 rom, I got an error, saying that the /vendor partition wasn't mounted.
DecentM said:
I mounted it, because when I initially restored the 5.1.1 rom, I got an error, saying that the /vendor partition wasn't mounted.
Click to expand...
Click to collapse
You are sure it was complaining about "unmounted", rather than "mounted"?
Do these roms include a vendor.img? You may need to flash the stock 5.1.1 vendor.img.
Either way, unless you mkfs'ed or resize2fs'ed the partitions, they should be fine. Full wipe & go.
dmantilal said:
You are sure it was complaining about "unmounted", rather than "mounted"?
Do these roms include a vendor.img? You may need to flash the stock 5.1.1 vendor.img.
Either way, unless you mkfs'ed or resize2fs'ed the partitions, they should be fine. Full wipe & go.
Click to expand...
Click to collapse
I'm not sure.
I already did a full wipe, but it still had issues. I'll try again tomorrow, and report back on how it went.
DecentM said:
I'm not sure.
I already did a full wipe, but it still had issues. I'll try again tomorrow, and report back how it went.
Click to expand...
Click to collapse
Having a mismatched vendor.img could be your problem.
No ROM I know of includes a vendor.img. I think it is a legal issue, like including GApps with a ROM.
dmantilal said:
Having a mismatched vendor.img could be your problem.
No ROM I know of includes a vendor.img. I think it is a legal issue, like including GApps with a ROM.
Click to expand...
Click to collapse
I don't think that the issue is with the vendor image anymore, but with the partitions in general. I always had a mismatched vendor image, as it only results in a modal box after boot.
My problem is again, with the /system partition not being visible to flashable zip files.
Mismatched vendor.img can also cause bootloops and other quirks like battery-charge percentage inaccuracies.
What's up, guy
I can't flash Lineage rom package into my Honor 5A. Like the following
could not detect filesystem for /Dev/block/platform/mtk-msdc.0/by-name/system, assuming ext4 mount:failed to mount /Dev/block/platform/mtk-msdc.0/by-name/system at /system at /system: No such file or directory
unmount of /system failed; no such volume
Updater process ended with signal: 11
Error installing zip file '/emmc/lineage-14.1-20170730-nightly.zip'
TWRP version is 3.0.2-0 and have unlocked BL before.
And when I changed the other Rom like RR, the error appear the same.
What's wrong happened? How to fix it?
Thanks
Matt0618 said:
What's up, guy
I can't flash Lineage rom package into my Honor 5A. Like the following
could not detect filesystem for /Dev/block/platform/mtk-msdc.0/by-name/system, assuming ext4 mount:failed to mount /Dev/block/platform/mtk-msdc.0/by-name/system at /system at /system: No such file or directory
unmount of /system failed; no such volume
Updater process ended with signal: 11
Error installing zip file '/emmc/lineage-14.1-20170730-nightly.zip'
TWRP version is 3.0.2-0 and have unlocked BL before.
And when I changed the other Rom like RR, the error appear the same.
What's wrong happened? How to fix it?
Thanks
Click to expand...
Click to collapse
I want this ROM。where do you found it.Thx
Matt0618 said:
What's up, guy. I can't flash Lineage rom package into my Honor 5A. Like the following...
Click to expand...
Click to collapse
RB14_ojbk said:
I want this ROM。where do you found it.Thx
Click to expand...
Click to collapse
I don't have this device but, the following thread may be helpful for what you are looking for and need that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3621252
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
As the title says, i want the figure out which firmware version is installed on my phone. OnePlus 9 Pro.
I am currently in a bootloop and try to reflash the boot.img to minimize the data loss. tried a few versions without success. (thread calling for help for that is here).
To break down the problem i want to flash the correct boot img, but need to know which one.
I can boot twrp temporarily with fastboot and access some data. I couldnt find build.props file as suggested.
Is there any other possibility to find the firmware version?
thanks in advance!
Speaka said:
(...) I couldnt find build.props file as suggested.
Is there any other possibility to find the firmware version?
(...)
Click to expand...
Click to collapse
In TWRP, you need to mount the system to see the content.
What do you mean with mount? Menu entry "mount" in twrp means mounting it to the usb connection, as far as i know....
In twrp menu advanced->file manager i can see the root directory and /system (and more).
Where do i have to look?
TWRP -> Mount -> (mark the square) System
Only then will File Manager see the contents of the system partition.
Ah okay. This was a misconception. it is mounted. unter /system is se bin,etc,lib64 and usr. Browsing araound i did not find build.props.
Can I boot to the root filesystem using fastboot and edit the file from there?
I wanted to edit:
/etc/mkshrc
xracerx123 said:
Can I boot to the root filesystem using fastboot and edit the file from there?
I wanted to edit:
/etc/mkshrc
Click to expand...
Click to collapse
It is generally not possible to perform file changes through fastboot/bootloader. To do so, you need to have a runtime environment such as TWRP. Bootloader/fastboot generally only handles partition images.
V0latyle said:
It is generally not possible to perform file changes through fastboot/bootloader. To do so, you need to have a runtime environment such as TWRP. Bootloader/fastboot generally only handles partition images.
Click to expand...
Click to collapse
Unable to edit /etc/mkshrc
I just tried to add variables on Android /etc/mkshrc file but I get an error: Read-only file system 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 /...
forum.xda-developers.com
Do refer to the above thread, it is sort of related to this topic.
Is it possible, to edit right on the /etc itself? without going through twrp?
Is there any tools that can help?
xracerx123 said:
Unable to edit /etc/mkshrc
I just tried to add variables on Android /etc/mkshrc file but I get an error: Read-only file system 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 /...
forum.xda-developers.com
Do refer to the above thread, it is sort of related to this topic.
Click to expand...
Click to collapse
It mentions using ADB, which can only be used either through system or recovery.
xracerx123 said:
Is it possible, to edit right on the /etc itself? without going through twrp?
Click to expand...
Click to collapse
Not through bootloader or fastboot. You can dump an image, edit it, and reflash it, but this would all be much more complicated than using TWRP, which would allow you to mount the partition as r+w so you can effect the edit you want.
xracerx123 said:
Is there any tools that can help?
Click to expand...
Click to collapse
Yes...TWRP.
V0latyle said:
It mentions using ADB, which can only be used either through system or recovery.
Not through bootloader or fastboot. You can dump an image, edit it, and reflash it, but this would all be much more complicated than using TWRP, which would allow you to mount the partition as r+w so you can effect the edit you want.
Yes...TWRP.
Click to expand...
Click to collapse
I am using Pixel 6A, currently there is no TWRP. https://twrp.me/Devices/
xracerx123 said:
I am using Pixel 6A, currently there is no TWRP. https://twrp.me/Devices/
Click to expand...
Click to collapse
Details like this are beneficial when asking questions.
The short answer to your original question is no, what you want to do is not possible.
is your bootloader even unlockable?
https://www.xda-developers.com/how-to-unlock-bootloader-root-magisk-google-pixel-6a
xracerx123 said:
I am using Pixel 6A, currently there is no TWRP.
Click to expand...
Click to collapse
but there is Evolution X custom recovery at least
https://forum.xda-developers.com/t/4514881