Can't create file: Read-only file systemHow do I remount a filesystem as read/write?Why does Ubuntu refuse to execute files from an NTFS partition?External HDD mounted as read only fat32My ext HHD is READ-ONLY! Posted attempts to correct same confused me and made matters worst!Android adb no permissionUbuntu 14.04/15.10 - Android file access issueNot able to write to pendriveNFS mount. Permission issue?Creating disk images as a normal userPen drive turned read onlyCannot mount ext4 with user permissions

Why, precisely, is argon used in neutrino experiments?

Method to test if a number is a perfect power?

Why not increase contact surface when reentering the atmosphere?

How to pronounce the slash sign

Increase performance creating Mandelbrot set in python

How can I get through very long and very dry, but also very useful technical documents when learning a new tool?

A particular customize with green line and letters for subfloat

Do sorcerers' subtle spells require a skill check to be unseen?

How to Reset Passwords on Multiple Websites Easily?

Is a stroke of luck acceptable after a series of unfavorable events?

Sequence of Tenses: Translating the subjunctive

How do I extract a value from a time formatted value in excel?

How do we know the LHC results are robust?

What happens if you roll doubles 3 times then land on "Go to jail?"

System.debug(JSON.Serialize(o)) Not longer shows full string

Proof of work - lottery approach

What is the difference between "behavior" and "behaviour"?

For a non-Jew, is there a punishment for not observing the 7 Noahide Laws?

Gears on left are inverse to gears on right?

Escape a backup date in a file name

Type int? vs type int

How easy is it to start Magic from scratch?

India just shot down a satellite from the ground. At what altitude range is the resulting debris field?

Opposite of a diet



Can't create file: Read-only file system


How do I remount a filesystem as read/write?Why does Ubuntu refuse to execute files from an NTFS partition?External HDD mounted as read only fat32My ext HHD is READ-ONLY! Posted attempts to correct same confused me and made matters worst!Android adb no permissionUbuntu 14.04/15.10 - Android file access issueNot able to write to pendriveNFS mount. Permission issue?Creating disk images as a normal userPen drive turned read onlyCannot mount ext4 with user permissions













4















I was trying to recover files from android phone using adb shell and test disk. But I am getting a read only filesystem error, even though the permissions to write is granted to the user.



adb devices


list the device attached.
After I ran the following commands



adb shell


Inside the shell I did the following



user:/ $ su
user:/ # adb shell "stty raw; cat </dev/block/mmcblk0p56" > data.img
sh: can't create data.img: Read-only file system


How to solve this?



Update



Trying the proposed solutions:



 $ sudo adb shell "stty raw; cat /dev/block/mmcblk0p56" > /home/user/android-backup/data.img
stty: tcgetattr standard input: Not a typewriter
cat: /dev/block/mmcblk0p56: Permission denied


Mounting code:



$ sudo mount -o remount,rw /dev/block/mmcblk0p56 /tmp
mount: /tmp: mount point not mounted or bad option.









share|improve this question




























    4















    I was trying to recover files from android phone using adb shell and test disk. But I am getting a read only filesystem error, even though the permissions to write is granted to the user.



    adb devices


    list the device attached.
    After I ran the following commands



    adb shell


    Inside the shell I did the following



    user:/ $ su
    user:/ # adb shell "stty raw; cat </dev/block/mmcblk0p56" > data.img
    sh: can't create data.img: Read-only file system


    How to solve this?



    Update



    Trying the proposed solutions:



     $ sudo adb shell "stty raw; cat /dev/block/mmcblk0p56" > /home/user/android-backup/data.img
    stty: tcgetattr standard input: Not a typewriter
    cat: /dev/block/mmcblk0p56: Permission denied


    Mounting code:



    $ sudo mount -o remount,rw /dev/block/mmcblk0p56 /tmp
    mount: /tmp: mount point not mounted or bad option.









    share|improve this question


























      4












      4








      4








      I was trying to recover files from android phone using adb shell and test disk. But I am getting a read only filesystem error, even though the permissions to write is granted to the user.



      adb devices


      list the device attached.
      After I ran the following commands



      adb shell


      Inside the shell I did the following



      user:/ $ su
      user:/ # adb shell "stty raw; cat </dev/block/mmcblk0p56" > data.img
      sh: can't create data.img: Read-only file system


      How to solve this?



      Update



      Trying the proposed solutions:



       $ sudo adb shell "stty raw; cat /dev/block/mmcblk0p56" > /home/user/android-backup/data.img
      stty: tcgetattr standard input: Not a typewriter
      cat: /dev/block/mmcblk0p56: Permission denied


      Mounting code:



      $ sudo mount -o remount,rw /dev/block/mmcblk0p56 /tmp
      mount: /tmp: mount point not mounted or bad option.









      share|improve this question
















      I was trying to recover files from android phone using adb shell and test disk. But I am getting a read only filesystem error, even though the permissions to write is granted to the user.



      adb devices


      list the device attached.
      After I ran the following commands



      adb shell


      Inside the shell I did the following



      user:/ $ su
      user:/ # adb shell "stty raw; cat </dev/block/mmcblk0p56" > data.img
      sh: can't create data.img: Read-only file system


      How to solve this?



      Update



      Trying the proposed solutions:



       $ sudo adb shell "stty raw; cat /dev/block/mmcblk0p56" > /home/user/android-backup/data.img
      stty: tcgetattr standard input: Not a typewriter
      cat: /dev/block/mmcblk0p56: Permission denied


      Mounting code:



      $ sudo mount -o remount,rw /dev/block/mmcblk0p56 /tmp
      mount: /tmp: mount point not mounted or bad option.






      command-line permissions read-only adb






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited yesterday







      supremum

















      asked yesterday









      supremumsupremum

      6132716




      6132716




















          2 Answers
          2






          active

          oldest

          votes


















          2














          You can try to remount the file system with read and write permissions (source):



          sudo mount -o remount,rw /partition/identifier /mount/point


          Or in your case you just can tray to redirect the output to a file located in a directory where you must be able to write:



          adb shell "stty raw; cat </dev/block/mmcblk0p56" > /tmp/data.img





          share|improve this answer























          • I would add 'writing to / is always a bad idea (not related if possible or not)'. But your suggestion to use /tmp covers the solution already.

            – LupusE
            yesterday











          • Hi, @LupusE, why it is a bad idea?

            – pa4080
            yesterday











          • There is something called FSH (en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard) to define what data should be stored in which directory. ... It is very important if you've got different partitions for different purposes. For example: Avoid to put /var/log on a flash storage. Much read/write will kill it ... It is the same if you store everything on C: in windows. Maybe good for the moment, but don't show anyone.

            – LupusE
            yesterday











          • @pa4080 Is /partition/identifier in this case /dev/block/mmcblk0p56? Also, what should be the mount point?

            – supremum
            yesterday











          • @supremum, yes I think it should be /dev/block/mmcblk0p56, but can't be sure. You can list the attached drives/devices by the command sudo lsblk.

            – pa4080
            yesterday


















          1














          Are you trying to copy the block device to an image file on your local computer? If so, try:




          adb shell su -c '"stty raw; cat < /dev/block/mmcblk0p56"' > data.img





          share|improve this answer








          New contributor




          Edwin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.



















            Your Answer








            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "89"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader:
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            ,
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













            draft saved

            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1128734%2fcant-create-file-read-only-file-system%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            2














            You can try to remount the file system with read and write permissions (source):



            sudo mount -o remount,rw /partition/identifier /mount/point


            Or in your case you just can tray to redirect the output to a file located in a directory where you must be able to write:



            adb shell "stty raw; cat </dev/block/mmcblk0p56" > /tmp/data.img





            share|improve this answer























            • I would add 'writing to / is always a bad idea (not related if possible or not)'. But your suggestion to use /tmp covers the solution already.

              – LupusE
              yesterday











            • Hi, @LupusE, why it is a bad idea?

              – pa4080
              yesterday











            • There is something called FSH (en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard) to define what data should be stored in which directory. ... It is very important if you've got different partitions for different purposes. For example: Avoid to put /var/log on a flash storage. Much read/write will kill it ... It is the same if you store everything on C: in windows. Maybe good for the moment, but don't show anyone.

              – LupusE
              yesterday











            • @pa4080 Is /partition/identifier in this case /dev/block/mmcblk0p56? Also, what should be the mount point?

              – supremum
              yesterday











            • @supremum, yes I think it should be /dev/block/mmcblk0p56, but can't be sure. You can list the attached drives/devices by the command sudo lsblk.

              – pa4080
              yesterday















            2














            You can try to remount the file system with read and write permissions (source):



            sudo mount -o remount,rw /partition/identifier /mount/point


            Or in your case you just can tray to redirect the output to a file located in a directory where you must be able to write:



            adb shell "stty raw; cat </dev/block/mmcblk0p56" > /tmp/data.img





            share|improve this answer























            • I would add 'writing to / is always a bad idea (not related if possible or not)'. But your suggestion to use /tmp covers the solution already.

              – LupusE
              yesterday











            • Hi, @LupusE, why it is a bad idea?

              – pa4080
              yesterday











            • There is something called FSH (en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard) to define what data should be stored in which directory. ... It is very important if you've got different partitions for different purposes. For example: Avoid to put /var/log on a flash storage. Much read/write will kill it ... It is the same if you store everything on C: in windows. Maybe good for the moment, but don't show anyone.

              – LupusE
              yesterday











            • @pa4080 Is /partition/identifier in this case /dev/block/mmcblk0p56? Also, what should be the mount point?

              – supremum
              yesterday











            • @supremum, yes I think it should be /dev/block/mmcblk0p56, but can't be sure. You can list the attached drives/devices by the command sudo lsblk.

              – pa4080
              yesterday













            2












            2








            2







            You can try to remount the file system with read and write permissions (source):



            sudo mount -o remount,rw /partition/identifier /mount/point


            Or in your case you just can tray to redirect the output to a file located in a directory where you must be able to write:



            adb shell "stty raw; cat </dev/block/mmcblk0p56" > /tmp/data.img





            share|improve this answer













            You can try to remount the file system with read and write permissions (source):



            sudo mount -o remount,rw /partition/identifier /mount/point


            Or in your case you just can tray to redirect the output to a file located in a directory where you must be able to write:



            adb shell "stty raw; cat </dev/block/mmcblk0p56" > /tmp/data.img






            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered yesterday









            pa4080pa4080

            14.7k52872




            14.7k52872












            • I would add 'writing to / is always a bad idea (not related if possible or not)'. But your suggestion to use /tmp covers the solution already.

              – LupusE
              yesterday











            • Hi, @LupusE, why it is a bad idea?

              – pa4080
              yesterday











            • There is something called FSH (en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard) to define what data should be stored in which directory. ... It is very important if you've got different partitions for different purposes. For example: Avoid to put /var/log on a flash storage. Much read/write will kill it ... It is the same if you store everything on C: in windows. Maybe good for the moment, but don't show anyone.

              – LupusE
              yesterday











            • @pa4080 Is /partition/identifier in this case /dev/block/mmcblk0p56? Also, what should be the mount point?

              – supremum
              yesterday











            • @supremum, yes I think it should be /dev/block/mmcblk0p56, but can't be sure. You can list the attached drives/devices by the command sudo lsblk.

              – pa4080
              yesterday

















            • I would add 'writing to / is always a bad idea (not related if possible or not)'. But your suggestion to use /tmp covers the solution already.

              – LupusE
              yesterday











            • Hi, @LupusE, why it is a bad idea?

              – pa4080
              yesterday











            • There is something called FSH (en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard) to define what data should be stored in which directory. ... It is very important if you've got different partitions for different purposes. For example: Avoid to put /var/log on a flash storage. Much read/write will kill it ... It is the same if you store everything on C: in windows. Maybe good for the moment, but don't show anyone.

              – LupusE
              yesterday











            • @pa4080 Is /partition/identifier in this case /dev/block/mmcblk0p56? Also, what should be the mount point?

              – supremum
              yesterday











            • @supremum, yes I think it should be /dev/block/mmcblk0p56, but can't be sure. You can list the attached drives/devices by the command sudo lsblk.

              – pa4080
              yesterday
















            I would add 'writing to / is always a bad idea (not related if possible or not)'. But your suggestion to use /tmp covers the solution already.

            – LupusE
            yesterday





            I would add 'writing to / is always a bad idea (not related if possible or not)'. But your suggestion to use /tmp covers the solution already.

            – LupusE
            yesterday













            Hi, @LupusE, why it is a bad idea?

            – pa4080
            yesterday





            Hi, @LupusE, why it is a bad idea?

            – pa4080
            yesterday













            There is something called FSH (en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard) to define what data should be stored in which directory. ... It is very important if you've got different partitions for different purposes. For example: Avoid to put /var/log on a flash storage. Much read/write will kill it ... It is the same if you store everything on C: in windows. Maybe good for the moment, but don't show anyone.

            – LupusE
            yesterday





            There is something called FSH (en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard) to define what data should be stored in which directory. ... It is very important if you've got different partitions for different purposes. For example: Avoid to put /var/log on a flash storage. Much read/write will kill it ... It is the same if you store everything on C: in windows. Maybe good for the moment, but don't show anyone.

            – LupusE
            yesterday













            @pa4080 Is /partition/identifier in this case /dev/block/mmcblk0p56? Also, what should be the mount point?

            – supremum
            yesterday





            @pa4080 Is /partition/identifier in this case /dev/block/mmcblk0p56? Also, what should be the mount point?

            – supremum
            yesterday













            @supremum, yes I think it should be /dev/block/mmcblk0p56, but can't be sure. You can list the attached drives/devices by the command sudo lsblk.

            – pa4080
            yesterday





            @supremum, yes I think it should be /dev/block/mmcblk0p56, but can't be sure. You can list the attached drives/devices by the command sudo lsblk.

            – pa4080
            yesterday













            1














            Are you trying to copy the block device to an image file on your local computer? If so, try:




            adb shell su -c '"stty raw; cat < /dev/block/mmcblk0p56"' > data.img





            share|improve this answer








            New contributor




            Edwin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.
























              1














              Are you trying to copy the block device to an image file on your local computer? If so, try:




              adb shell su -c '"stty raw; cat < /dev/block/mmcblk0p56"' > data.img





              share|improve this answer








              New contributor




              Edwin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.






















                1












                1








                1







                Are you trying to copy the block device to an image file on your local computer? If so, try:




                adb shell su -c '"stty raw; cat < /dev/block/mmcblk0p56"' > data.img





                share|improve this answer








                New contributor




                Edwin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.










                Are you trying to copy the block device to an image file on your local computer? If so, try:




                adb shell su -c '"stty raw; cat < /dev/block/mmcblk0p56"' > data.img






                share|improve this answer








                New contributor




                Edwin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.









                share|improve this answer



                share|improve this answer






                New contributor




                Edwin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.









                answered yesterday









                EdwinEdwin

                112




                112




                New contributor




                Edwin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.





                New contributor





                Edwin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.






                Edwin is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.



























                    draft saved

                    draft discarded
















































                    Thanks for contributing an answer to Ask Ubuntu!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid


                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.

                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1128734%2fcant-create-file-read-only-file-system%23new-answer', 'question_page');

                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Sum ergo cogito? 1 nng

                    419 nièngy_Soadمي 19bal1.5o_g

                    Queiggey Chernihivv 9NnOo i Zw X QqKk LpB