Can't create file: Read-only file system Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)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

Dominant seventh chord in the major scale contains diminished triad of the seventh?

What causes the vertical darker bands in my photo?

Did Xerox really develop the first LAN?

How do I mention the quality of my school without bragging

Why is "Consequences inflicted." not a sentence?

Gastric acid as a weapon

Is it true that "carbohydrates are of no use for the basal metabolic need"?

Stars Make Stars

How to deal with a team lead who never gives me credit?

How do I stop a creek from eroding my steep embankment?

If 'B is more likely given A', then 'A is more likely given B'

Did Kevin spill real chili?

Do you forfeit tax refunds/credits if you aren't required to and don't file by April 15?

Why are there no cargo aircraft with "flying wing" design?

Is there a service that would inform me whenever a new direct route is scheduled from a given airport?

Why was the term "discrete" used in discrete logarithm?

Using et al. for a last / senior author rather than for a first author

Does surprise arrest existing movement?

Check which numbers satisfy the condition [A*B*C = A! + B! + C!]

How does a Death Domain cleric's Touch of Death feature work with Touch-range spells delivered by familiars?

How widely used is the term Treppenwitz? Is it something that most Germans know?

Is there a concise way to say "all of the X, one of each"?

Output the ŋarâþ crîþ alphabet song without using (m)any letters

Center align columns in table ignoring minus signs?



Can't create file: Read-only file system



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)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



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








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 Mar 26 at 8:58







      supremum

















      asked Mar 26 at 6:03









      supremumsupremum

      6182716




      6182716




















          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
            Mar 26 at 7:53











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

            – pa4080
            Mar 26 at 8:00











          • 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
            Mar 26 at 8:07











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

            – supremum
            Mar 26 at 9:02











          • @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
            Mar 26 at 10:08


















          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























            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
              Mar 26 at 7:53











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

              – pa4080
              Mar 26 at 8:00











            • 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
              Mar 26 at 8:07











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

              – supremum
              Mar 26 at 9:02











            • @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
              Mar 26 at 10:08















            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
              Mar 26 at 7:53











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

              – pa4080
              Mar 26 at 8:00











            • 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
              Mar 26 at 8:07











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

              – supremum
              Mar 26 at 9:02











            • @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
              Mar 26 at 10:08













            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 Mar 26 at 7:12









            pa4080pa4080

            14.8k52873




            14.8k52873












            • 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
              Mar 26 at 7:53











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

              – pa4080
              Mar 26 at 8:00











            • 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
              Mar 26 at 8:07











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

              – supremum
              Mar 26 at 9:02











            • @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
              Mar 26 at 10:08

















            • 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
              Mar 26 at 7:53











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

              – pa4080
              Mar 26 at 8:00











            • 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
              Mar 26 at 8:07











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

              – supremum
              Mar 26 at 9:02











            • @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
              Mar 26 at 10:08
















            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
            Mar 26 at 7:53





            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
            Mar 26 at 7:53













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

            – pa4080
            Mar 26 at 8:00





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

            – pa4080
            Mar 26 at 8:00













            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
            Mar 26 at 8:07





            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
            Mar 26 at 8:07













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

            – supremum
            Mar 26 at 9:02





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

            – supremum
            Mar 26 at 9:02













            @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
            Mar 26 at 10:08





            @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
            Mar 26 at 10:08













            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



























              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

























                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













                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












                share|improve this answer



                share|improve this answer










                answered Mar 26 at 7:33









                EdwinEdwin

                263




                263



























                    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

                    How should I support this large drywall patch? Planned maintenance scheduled April 23, 2019 at 00:00UTC (8:00pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?How do I cover large gaps in drywall?How do I keep drywall around a patch from crumbling?Can I glue a second layer of drywall?How to patch long strip on drywall?Large drywall patch: how to avoid bulging seams?Drywall Mesh Patch vs. Bulge? To remove or not to remove?How to fix this drywall job?Prep drywall before backsplashWhat's the best way to fix this horrible drywall patch job?Drywall patching using 3M Patch Plus Primer

                    random experiment with two different functions on unit interval Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 23, 2019 at 00:00UTC (8:00pm US/Eastern)Random variable and probability space notionsRandom Walk with EdgesFinding functions where the increase over a random interval is Poisson distributedNumber of days until dayCan an observed event in fact be of zero probability?Unit random processmodels of coins and uniform distributionHow to get the number of successes given $n$ trials , probability $P$ and a random variable $X$Absorbing Markov chain in a computer. Is “almost every” turned into always convergence in computer executions?Stopped random walk is not uniformly integrable

                    Lowndes Grove History Architecture References Navigation menu32°48′6″N 79°57′58″W / 32.80167°N 79.96611°W / 32.80167; -79.9661132°48′6″N 79°57′58″W / 32.80167°N 79.96611°W / 32.80167; -79.9661178002500"National Register Information System"Historic houses of South Carolina"Lowndes Grove""+32° 48' 6.00", −79° 57' 58.00""Lowndes Grove, Charleston County (260 St. Margaret St., Charleston)""Lowndes Grove"The Charleston ExpositionIt Happened in South Carolina"Lowndes Grove (House), Saint Margaret Street & Sixth Avenue, Charleston, Charleston County, SC(Photographs)"Plantations of the Carolina Low Countrye