As the title says, I can't get TWRP to mount any useful partitions like /system and /data. It seems to be a common problem according to the issues page on GitHub, but does anyone have any kind of workaround for this?
Matthew98405 said:
As the title says, I can't get TWRP to mount any useful partitions like /system and /data. It seems to be a common problem according to the issues page on GitHub, but does anyone have any kind of workaround for this?
Click to expand...
Click to collapse
Are you on Android 10? There is no TWRP yet, period. Lots of threads and comments in the actual TWRP thread. Besides that, /system is locked down in 10.
Related
I posted this here - http://forum.xda-developers.com/showpost.php?p=18647176&postcount=14 - but never got an answer so I'm posting it to its own thread. I would post to the development section but apparently until I clutter up the place with 10 posts I'm considered a drooling idiot.
I was playing around and I noticed that the problem is with s-on I cannot write to /system meaning no superuser etc. So I remembered from way back when I started linux you could mount over a mounted folder. So I made a small file, put ext3 on on it, transferred it to the sdcard and mounted over /system with
mount -t ext3 -o rw,loop /mnt/sdcard/test.dump /system
it worked and then of course I lost all commands (ls, reboot...) in the shell.
Would it be possible to dump /system with "cat /dev/mtd/mtd3 > /mnt/sdcard/system.img", extract it, put it in an ext3 file, mount it as readable over system and just go to town?
Somebody MUST have tried this in the past. Before I go any further can anyone tell me why this wouldn't work and save me a few hours noodling around lol
baconbacon said:
I posted this here - http://forum.xda-developers.com/showpost.php?p=18647176&postcount=14 - but never got an answer so I'm posting it to its own thread. I would post to the development section but apparently until I clutter up the place with 10 posts I'm considered a drooling idiot.
I was playing around and I noticed that the problem is with s-on I cannot write to /system meaning no superuser etc. So I remembered from way back when I started linux you could mount over a mounted folder. So I made a small file, put ext3 on on it, transferred it to the sdcard and mounted over /system with
mount -t ext3 -o rw,loop /mnt/sdcard/test.dump /system
it worked and then of course I lost all commands (ls, reboot...) in the shell.
Would it be possible to dump /system with "cat /dev/mtd/mtd3 > /mnt/sdcard/system.img", extract it, put it in an ext3 file, mount it as readable over system and just go to town?
Somebody MUST have tried this in the past. Before I go any further can anyone tell me why this wouldn't work and save me a few hours noodling around lol
Click to expand...
Click to collapse
S-on itself got nothing to do with rooting. It just means you can't flash unsigned images as much as I know.
That system is mounted as ro is also at rooted phones the standard behaviour, you have to remount it as rw, but without root it won't accomplish I think.
Cat is for text files not for binaries or whole partitions, to extract the image use the dd command.
Do you have an /dev/mtd folder? My partitions are at /dev/block and there is no /dev/mtd present.
Swyped from my HTC Desire S
Tectas said:
S-on itself got nothing to do with rooting. It just means you can't flash unsigned images as much as I know.
That system is mounted as ro is also at rooted phones the standard behaviour, you have to remount it as rw, but without root it won't accomplish I think.
Cat is for text files not for binaries or whole partitions, to extract the image use the dd command.
Do you have an /dev/mtd folder? My partitions are at /dev/block and there is no /dev/mtd present.
Swyped from my HTC Desire S
Click to expand...
Click to collapse
This issue is that when you remount it as rw you cannot write to it. I want to know if I make my own partitions and mount them after boot if that will work, probably slower but work. This is so lojack I doubt it will work, I just want to know if anyone tried it.
Also "Cat is for text files not for binaries or whole partitions" is wrong, it works fine.
baconbacon said:
This issue is that when you remount it as rw you cannot write to it. I want to know if I make my own partitions and mount them after boot if that will work, probably slower but work. This is so lojack I doubt it will work, I just want to know if anyone tried it.
Also "Cat is for text files not for binaries or whole partitions" is wrong, it works fine.
Click to expand...
Click to collapse
Then it's not rw, because rw stands for read write, but like I said without root...
And no I think no one tried it before, because using an xtc-clip is compared to your solution much less work
But if you want to try it, do it and share your experiences, maybe it helps others
That cat works doesn't mean that it's made for it, you can also hunt for birds with a bazooka
Take a look at cat and dd and choose yourself.
Tectas said:
Then it's not rw, because rw stands for read write, but like I said without root...
And no I think no one tried it before, because using an xtc-clip is compared to your solution much less work
But if you want to try it, do it and share your experiences, maybe it helps others
That cat works doesn't mean that it's made for it, you can also hunt for birds with a bazooka
Take a look at cat and dd and choose yourself.
Click to expand...
Click to collapse
is xtc-clip better? yes, not arguing that. is cat is better then dd? no, I said cat works in this instance the same as dd, the results will be the identical.
I didn't ask this question to argue unrelated linux 101. I'm just going to look into this myself. iow screw you guys, im going home...
Dude, I use Linux too though I'm probably not a guru. I think I understand what you're saying... but if I do, aren't you just talking about editing a copy of /system? How would you mount your edited partition at boot?
Time permitting, I could try a few tricks but I'm not willing to risk bricking my phone though. I'd be stranded without it.
Sent from my HTC Wildfire S A510e using XDA App
First don't blame others, because of things I wrote.
I never said it couldn't work, I just wanted to show you that there are better ways to do it, cause cat also tries to interpret the file and not only copies it, what could mess up your image in some cases.
Also be aware that if your using the same data and cache partition with both of your systems, it could be easy bricked, if you change to much at your 2. system and remember that there aren't many ways left to get it working again cause your still s-on.
I think he wants to mount it himself every time after boot.
If he can root his 2. system (but all by hand, I think) he maybe can mount his 1. system as rw and also root it, but the chance that something goes wrong is pretty high, even mounting itself could freeze the device, cause the first system is still in memory.
I'm also not even close to be a Linux guru.
Swyped from my HTC Desire S
I'd like to be able to check my /sdcard and/or other partitions as well for errors on filesystem.
I'm a little confused which command/partition to use and how, can someone perhaps provide a right syntax?
Thank you in advance.
hi i see in this web site http://novafusion.pl/downloads/# a recovery based on F2FS partition for s3 mini .... if something can modify for our wonder and try a rom f2fs full ...performance increase much.... how i can try to use this recovery for sgw????
I've found this in this thread:
ktulu84 said:
we were trying to use f2fs, but seems we cant... f2fs takes more space to store auxiliary structure of the file system, in /system we can't flash ROM+gapps, it can't fit in there (seems that f2fs takes more than 100MB on /system). we may use it on /data, but we will lose some space, and we don't have too much free room on /data, we don't think is a good idea
Click to expand...
Click to collapse
rabbo3 said:
hi i see in this web site http://novafusion.pl/downloads/# a recovery based on F2FS partition for s3 mini .... if something can modify for our wonder and try a rom f2fs full ...performance increase much.... how i can try to use this recovery for sgw????
Click to expand...
Click to collapse
f2fs needs kernel changes, recovery support is already there, in twrp for sure, and i think even on CWM. the problem, as already reported is that maybe it can give some little performance boost (don't give credit to the ones are saying that it gives a second life to the device, is only a file system) but it will make your phone not usable because of the already limited space
Why limited space???? is a different partion..
There is a guide to convert ROM and kernel to f2fs the trouble is only create a recovery with f2fs support...
rabbo3 said:
There is a guide to convert ROM and kernel to f2fs the trouble is only create a recovery with f2fs support...
Click to expand...
Click to collapse
You don't understand... We have already f2fs support in recovery, the problem is in ROM, using f2fs increase the usage of /system and /data partitions, and we don't have it. I'm talking because we already tried, so i know what i'm saying
OK now i understand
I want to encrypt my OnePlus 3 but every time I hit "encrypt" my phone just reboots.
So I took a look at the logs and it says "Orig filesystem overlaps crypto footer region. Cannot encrypt in place."
So even after spending about 2 hours looking into this issue all I could find is that apparently android needs about 16KB of space at the end of some partition.
I found some how to's but unfortunately the steps are very complicated and I don't know how to follow them on the OnePlus 3.
So does anybody know how to solve this issue? There is an resize option in TWRP but it doesn't give you any options and doesn't solve the problem.
My OP3 already says it is encrypted. That's the way it came out of the box. Yours didn't? That's odd.
Sent from my D5803 using Tapatalk
Yes, it was encrypted out of the box but I installed TWRP and CM13. It seems like the partitioning got messed up somehow while wiping/formatting /data.
anyone23 said:
Yes, it was encrypted out of the box but I installed TWRP and CM13. It seems like the partitioning got messed up somehow while wiping/formatting /data.
Click to expand...
Click to collapse
After flash back OOS and doing a factory reset it will encrypt automatically again.
Planet X said:
After flash back OOS and doing a factory reset it will encrypt automatically again.
Click to expand...
Click to collapse
Yes, of course but I want to keep on using CM13.
Encryption is usually no problem with CM. I've been using CM with encryption on my Nexus 5 for 2 years.
I just don't know how to fix the partitioning.
Okay, after unsuccessfully playing around with the resize2fs command, I found the solution.
As resizing while Android is running doesn't work, I booted into TWRP, unmounted all partitions and then opened a terminal in the advanced menu.
I already knew that the /data partition is the one I needed to shrink and it's called /dev/block/sda15. So I used the command "resize2fs /dev/block/sda15 1xxx..."
On first try I accidentally used a number far too high but in the error message I got, it stated the current size and so I simply subtracted 40 from this value and ran the command again (4 should be enough for 16kb, but I wanted to make sure).
Well, now the encryption was successful.
I still think that this problem occurred after a format using TWRP and it needs be fixed as this is a problem very difficult to diagnose for the average person like me. TWRP seems to format the whole memory for /data but Android needs 16kb of free space for encryption.
I already had the same problem with encryption on a Moto G falcon after a TWRP format a few months ago.
anyone23 said:
Okay, after unsuccessfully playing around with the resize2fs command, I found the solution.
As resizing while Android is running doesn't work, I booted into TWRP, unmounted all partitions and then opened a terminal in the advanced menu.
I already knew that the /data partition is the one I needed to shrink and it's called /dev/block/sda15. So I used the command "resize2fs /dev/block/sda15 1xxx..."
On first try I accidentally used a number far too high but in the error message I got, it stated the current size and so I simply subtracted 40 from this value and ran the command again (4 should be enough for 16kb, but I wanted to make sure).
Well, now the encryption was successful.
I still think that this problem occurred after a format using TWRP and it needs be fixed as this is a problem very difficult to diagnose for the average person like me. TWRP seems to format the whole memory for /data but Android needs 16kb of free space for encryption.
I already had the same problem with encryption on a Moto G falcon after a TWRP format a few months ago.
Click to expand...
Click to collapse
I'm running cm13 with encryption on my OnePlus 3 too. I didn't had to resize my partitions.
While installing anything from TWRP I'm always getting
"Failed to mount /system root /vendor /product (no such file or directory)" message
Already tried too fix it by changing the file system to EXT2 and back. Seems like it has sth to do with "section super" access rights or sth like that.
I'm not really sharp with stuff like that so I'm hoping someone bright minded could help. Thanks in advance!
GORBING said:
While installing anything from TWRP I'm always getting
"Failed to mount /system root /vendor /product (no such file or directory)" message
Already tried too fix it by changing the file system to EXT2 and back. Seems like it has sth to do with "section super" access rights or sth like that.
I'm not really sharp with stuff like that so I'm hoping someone bright minded could help. Thanks in advance!
Click to expand...
Click to collapse
remember to unmount system and vendor, may be is the problem
canteo said:
remember to unmount system and vendor, may be is the problem
Click to expand...
Click to collapse
Thanks for the answer!
Don't wanna sound stupid but what does it mean exactly. What should i do?
Is there such an option in TWRP that i don't know of? Is it the "Disable MTP" button? If so i can't mark these exact 3 to change them
PROBLEM SOLVED!
I reinstalled vanilla ROM and tried again with OrangeFox Recovery in which i had unmount options. It worked!
canteo said:
remember to unmount system and vendor, may be is the problem
Click to expand...
Click to collapse
Thanks a lot man, I was crying until i see your message, xD
GORBING said:
PROBLEM SOLVED!
I reinstalled vanilla ROM and tried again with OrangeFox Recovery in which i had unmount options.
Click to expand...
Click to collapse
Which Vanilla ROM? I have also the same problem. Please reply in details.