Are these the same? Or what am I missing here?
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o rw,remount /dev/block/stl9 /system
Thanks in advance...
Sorry for the bump, but Guys I ve read a lot of posts about guides and tuts. Thats why I found these two methods, So anyone with a sound knowledge please give me a clarification on this? What is the difference about those?
Where do you want to mount it?
in ADB it's just mount /system. In root explorer it is automatically mounted and you can change between R/O and R/W with a single button.
nagypapi said:
Where do you want to mount it?
in ADB it's just mount /system. In root explorer it is automatically mounted and you can change between R/O and R/W with a single button.
Click to expand...
Click to collapse
Thanks for replying,
I found one in here, the workshop about the ADB
http://forum.xda-developers.com/showthread.php?t=879701
You may need to remount system as writable with:
Code:
mount -o rw,remount /dev/block/stl9 /system
That applies when using chmod as well.
Click to expand...
Click to collapse
mount /system seems pretty self explanatory and I know this guide says "remount" but I am not very clear what remounting Vs mounting the Sys partition means. And why are there two different ADB commands for remounting? Hope you can enlighten me.
Well, I always use adb from the recovery, so the basic mount /system command is enough for me.
But sometimes (depending on the operation) - it requires re-mount. However, I never use the /dev/block/stl9 part, just the mount -o rw,remount /system part, and worked fine all the time.
nagypapi said:
Well, I always use adb from the recovery, so the basic mount /system command is enough for me.
But sometimes (depending on the operation) - it requires re-mount. However, I never use the /dev/block/stl9 part, just the mount -o rw,remount /system part, and worked fine all the time.
Click to expand...
Click to collapse
Okay I got it, Can you also please tell me what is the difference of using ADB from the recovery? I assume that the interference from the other system processes is minimum at the recovery? If so I'd also switch to use ADB from the recovery too.
Well if you are not S-OFF, you can mount the /system partition as R/W only from recovery (phone is not booted).
If I try to boot normally I get stuck on the boot screen. I can go into recovery (Clockwork Mod) but no combination of Flashing partitions seems to do anything. The one thing I've noticed is in Mounts and Storage /system; /data; /firmware/mdm; and /firmware/q6 all can be mounted. I can mount both /system and /data but the 2 /firmware partitions wont mount and if I check the log it reads
mount: mounting /dev/block/mmcblk0p16 on /firmware/q6 failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p16 (No such file or directory)
Error mounting /firmware/q6
I don't know if these 2 partitions would prevent booting up if they fail to load or if its something totally different. I've tried flashing just about everything I can find and nothing seems to take. Any help would be fantastic, if you need more info, just ask and I will do my best to get it for you. Thank You
fischerdave said:
If I try to boot normally I get stuck on the boot screen. I can go into recovery (Clockwork Mod) but no combination of Flashing partitions seems to do anything. The one thing I've noticed is in Mounts and Storage /system; /data; /firmware/mdm; and /firmware/q6 all can be mounted. I can mount both /system and /data but the 2 /firmware partitions wont mount and if I check the log it reads
mount: mounting /dev/block/mmcblk0p16 on /firmware/q6 failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p16 (No such file or directory)
Error mounting /firmware/q6
I don't know if these 2 partitions would prevent booting up if they fail to load or if its something totally different. I've tried flashing just about everything I can find and nothing seems to take. Any help would be fantastic, if you need more info, just ask and I will do my best to get it for you. Thank You
Click to expand...
Click to collapse
I was in a similar situation a few months back. Have you tried flashing a RUU? Preferably the current version or a newer version.
http://forum.xda-developers.com/showthread.php?p=46506621
Can remember if I did or not so probably worth a shot
I'm Downloading now and will let you know how that goes. Thanks.
fischerdave said:
I'm Downloading now and will let you know how that goes. Thanks.
Click to expand...
Click to collapse
Give me a holler of you don't get it booted.
So, a few days ago I managed to root my kindle fire 1st generation. I've been playing around with it, and noticed that it was rather slow. I thought about trying a different ROM for it to see if it would run any faster. Not entirely thinking, I didn't make a recovery with TWRP before I did a wipe. And now I have a kindle with no OS, and it can't flash anything because it doesn't have a root anymore.
I've been hunting down information on what to do for six-ish hours so far, but I haven't had any luck with anything. Can anyone help me?
kingsmaug said:
So, a few days ago I managed to root my kindle fire 1st generation. I've been playing around with it, and noticed that it was rather slow. I thought about trying a different ROM for it to see if it would run any faster. Not entirely thinking, I didn't make a recovery with TWRP before I did a wipe. And now I have a kindle with no OS, and it can't flash anything because it doesn't have a root anymore.
I've been hunting down information on what to do for six-ish hours so far, but I haven't had any luck with anything. Can anyone help me?
Click to expand...
Click to collapse
Do you have twrp?
If so which version?
Sent from my XT907 using Tapatalk
Yes. If I remember correctly, its version 2.6.3.0. It used to have boot loader otterx v2.05, but after some failure with KFU, it has FFF v1.4a.
So, after some more searching, I found that I couldn't mount anything in recovery and they wouldn't mount on their own. So I used adb shell to jump in, and I could manually mount system, data, sdcard, and cache. The only thing that would work was mount /dev/block/mmcblk0p9 , so I had use that on all of them.
After this I could push my ROM and gapps to the sdcard, and install them, but it gives me a new error: error executing updater binary in zip.
And as a bit more info, on first booting into recovery, this is the log:
Unable to mount /sdcard
Unable to recreate and-sec folder
Unable to mount /sdcard
Unable to mount /sdcard
Updating partition details....
Unable to mount /data
Unable to mount /cache
Unable to mount storage
Unable to mount /sdcard during GUI startup
Unable to mount /cache
Running boot script...
Finished running boot script
Unable to mount /cache
Unable to mount /sdcard/TWRP/.twrps when trying to read settings file.
Unable to mount /sdcard
My TWRP version is 2.6.3.1
I hope that helps.
kingsmaug said:
So, after some more searching, I found that I couldn't mount anything in recovery and they wouldn't mount on their own. So I used adb shell to jump in, and I could manually mount system, data, sdcard, and cache. The only thing that would work was mount /dev/block/mmcblk0p9 , so I had use that on all of them.
After this I could push my ROM and gapps to the sdcard, and install them, but it gives me a new error: error executing updater binary in zip.
And as a bit more info, on first booting into recovery, this is the log:
Unable to mount /sdcard
Unable to recreate and-sec folder
Unable to mount /sdcard
Unable to mount /sdcard
Updating partition details....
Unable to mount /data
Unable to mount /cache
Unable to mount storage
Unable to mount /sdcard during GUI startup
Unable to mount /cache
Running boot script...
Finished running boot script
Unable to mount /cache
Unable to mount /sdcard/TWRP/.twrps when trying to read settings file.
Unable to mount /sdcard
My TWRP version is 2.6.3.1
I hope that helps.
Click to expand...
Click to collapse
which partition version is selected OtterX or Amazon?
sd_shadow said:
which partition version is selected OtterX or Amazon?
Click to expand...
Click to collapse
It should be OtterX, but the only way I know of access which it is, via the bootloader, doesn't show up in FFF.
kingsmaug said:
It should be OtterX, but the only way I know of access which it is, via the bootloader, doesn't show up in FFF.
Click to expand...
Click to collapse
You need to flash OtterX twrp and bootloader
Only OtterX twrp can handle OtterX partitions
Only OtterX bootloader can change partitions
See [Video] Flashing TWRP in OtterX bootloader
Sent from my XT907 using Tapatalk
sd_shadow said:
You need to flash OtterX twrp and bootloader
Only OtterX twrp can handle OtterX partitions
Only OtterX bootloader can change partitions
See [Video] Flashing TWRP in OtterX bootloader
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
Ok. I was able to force it into fastboot, and then flash the otterx bootloader. I was able to confirm that they're otterx partitions, but it's still giving me the same startup errors about not being able to mount.
And then I rebooted to bootloader, and realized I forgot to change out of fastboot mode.
Double check the partition, and went into recovery, still getting the error about being unable to mount everything. So I manually mounted everything again.
I realized then that I needed to change TWRP to the otterx version, so I got it back into fastboot and flashed that. Now it'll mount /cache, but nothing else.
The truncated version of the opening log is:
can't mount /data
can't recreate /data/media
updating partition
can't mount /data
can't mount storage
can't mount /data/media during GUI startup
full SELinux support is present
can't mount /data/media/TWRP/.twrps when trying to read settings file
After that, I can manually mount the system in TWRP, but I can't mount data.
kingsmaug said:
Ok. I was able to force it into fastboot, and then flash the otterx bootloader. I was able to confirm that they're otterx partitions, but it's still giving me the same startup errors about not being able to mount.
And then I rebooted to bootloader, and realized I forgot to change out of fastboot mode.
Double check the partition, and went into recovery, still getting the error about being unable to mount everything. So I manually mounted everything again.
I realized then that I needed to change TWRP to the otterx version, so I got it back into fastboot and flashed that. Now it'll mount /cache, but nothing else.
The truncated version of the opening log is:
can't mount /data
can't recreate /data/media
updating partition
can't mount /data
can't mount storage
can't mount /data/media during GUI startup
full SELinux support is present
can't mount /data/media/TWRP/.twrps when trying to read settings file
After that, I can manually mount the system in TWRP, but I can't mount data.
Click to expand...
Click to collapse
Started a Thread [How To] Fix OtterX Install Errors, Partition sizes, Unable to Mount System... with some possible fixes for those having issues since converting to OtterX, with pushing files, failure to mount system errors when installing Lollipop Roms...
Sent from my XT907 using Tapatalk
sd_shadow said:
Started a Thread [How To] Fix OtterX Install Errors, Partition sizes, Unable to Mount System... with some possible fixes for those having issues since converting to OtterX, with pushing files, failure to mount system errors when installing Lollipop Roms...
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
Well, following that worked. Everything got cleared up, and now I'm loading into the ROM. Thank you!
Hello everybody
I have a strange behaviour on my GT-I9195: I cannot write to system partition even if I can mount it as writable. To make changes on my system files I need everytime to reboot in recovery and use TWRP file manager.
The phone is unlocked and rooted, I have TWRP 3.0.3, lombartz CM11 (feb 2016), f4k kernel, xposed installed with a pair of yt tweaks, Mounts2SD to move apps and /sdcard to external partition, lastest busybox binaries, root by CM11, F2FS filesystem for /cache and /data, EXT4 filesystem for /system.
Despite of this, I'm not able to do any change to my system partition from inside android.
What could the problem be?
Thank you
I have the same problem. When I switch the phone on, it stops on a screen written: "Damaged device memory". I've tried to put the original ROM but it stops at a screen with "filed to mount /cache"
As the title says i am unable to mount /system as read/write which makes it so that i cannot modify the build.prop file. is there any way to fix this?
you shouldn't be doing that anyway
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
/system is permanently read only in stock.
As the user above said, you shouldn't be modifying system directly anyways.