DroidForums.net is the original Verizon Android Forum! Registered Users do not see these ads. Please Register - It's Free!
Results 1 to 4 of 4

Thread: root can't write to phone!!!

  1. Droid Newbie
    lpoppe22's Avatar
    Member #
    107115
    Join Date
    Aug 2010
    Posts
    3
    Phone
    Moto Droid Razr MAXX
    #1

    root can't write to phone!!!

    Ok so here's the deal, i rooted my phone, and then unrooted it. The reason i unrooted it was to teach myself the ins and outs of how to fix things if ever need be. Now, I am running in to problems as i go to re-root the device. I have tried Motofail, DroidRazrUtility, and DoomLord and still no luck. I go to root the same way i did before and now says that i can't write to phone, that it is read only, or some jazz like that. I found a root method online somewhere, but have since lost it, that ran the abd and abd shell through the cmd prompt and, i believe, changed permissions. I NEED to find out what went wrong and why it worked perfectly the first time, but now is giving me problems. I looked around on some other threads, but without an definitive answers. can someone help?


    Here's an example of the problem i am encountering:



    --------------------------------------------------------------- Easy rooting toolkit (v4.0)
    created by DooMLoRD
    using exploit zergRush (Revolutionary Team)
    Credits go to all those involved in making this possible!
    ---------------------------------------------------------------
    [*] This script will:
    (1) root ur device using latest zergRush exploit (21 Nov)
    (2) install Busybox (1.18.4)
    (3) install SU files (binary: 3.0.3 and apk: 3.0.6)
    (4) some checks for free space, tmp directory
    (will remove Google Maps if required)
    [*] Before u begin:
    (1) make sure u have installed adb drivers for ur device
    (2) enable "USB DEBUGGING"
    from (Menu\Settings\Applications\Development)
    (3) enable "UNKNOWN SOURCES"
    from (Menu\Settings\Applications)
    (4) [OPTIONAL] increase screen timeout to 10 minutes
    (5) connect USB cable to PHONE and then connect to PC
    (6) skip "PC Companion Software" prompt on device
    ---------------------------------------------------------------
    CONFIRM ALL THE ABOVE THEN
    Press any key to continue . . .
    --- STARTING ----
    --- WAITING FOR DEVICE
    * daemon not running. starting it now *
    * daemon started successfully *
    --- creating temporary directory
    mkdir failed for tmp, File exists
    --- cleaning
    rm failed for *, No such file or directory
    --- pushing zergRush
    1407 KB/s (23060 bytes in 0.016s)
    --- correcting permissions
    --- executing zergRush


    [**] Zerg rush - Android 2.2/2.3 local root
    [**] (C) 2011 Revolutionary. All rights reserved.


    [**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.


    [+] Found a GingerBread ! 0x00000118[*] Scooting ...[*] Sending 149 zerglings ...[*] Sending 189 zerglings ...
    [-] Hellions with BLUE flames !
    --- WAITING FOR DEVICE TO RECONNECT
    if it gets stuck over here for a long time then try:
    disconnect usb cable and reconnect it
    toggle "USB DEBUGGING" (first disable it then enable it)
    --- DEVICE FOUND
    --- pushing busybox
    3301 KB/s (1075144 bytes in 0.318s)
    --- correcting permissions
    --- remounting /system
    mount: permission denied (are you root?)
    --- checking free space on /system
    142 KB/s (439 bytes in 0.003s)
    --- Free space on /system : 212760 bytes
    --- no cleanup required
    --- copying busybox to /system/xbin/
    /system/xbin/busybox: cannot open for write: Read-only file system
    --- correcting ownership
    Unable to chmod /system/xbin/busybox: Read-only file system
    --- correcting permissions
    Unable to chmod /system/xbin/busybox: Read-only file system
    --- installing busybox
    busybox: /system/xbin/su: Read-only file system
    --- pushing SU binary
    failed to copy 'files\su' to '/system/bin/su': Read-only file system
    --- correcting ownership
    Unable to chmod /system/bin/su: No such file or directory
    --- correcting permissions
    Unable to chmod /system/bin/su: No such file or directory
    --- correcting symlinks
    rm failed for /system/xbin/su, Read-only file system
    link failed Read-only file system
    --- pushing Superuser app
    failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
    file system
    --- cleaning
    --- rebooting
    ALL DONE!!!
    Press any key to continue . . .
  2.  
     
     
     
  3. Droid Newbie
    lpoppe22's Avatar
    Member #
    107115
    Join Date
    Aug 2010
    Posts
    3
    Phone
    Moto Droid Razr MAXX
    #2

    not sure if i know how i did it but i DID do it....

    ok so i think my problem might have been that i was trying to execute motofail root exploit through winrar... i had not extracted the files to a folder and when i tried that litterally as my last resort, it worked. rooted perfectly. have super user and everything. so if people are having this problem like i was, try motofail, make sure to extract all the stuff to a folder first, and then run the exploit... ugh. what an experience
  4. Droid Ninja
    jpcalhoun's Avatar
    Member #
    148338
    Join Date
    Dec 2010
    Location
    PA
    Posts
    1,570
    Liked
    183 times
    Phone
    Galaxy S4 Dev Edition
    #3
    Quote Originally Posted by lpoppe22 View Post
    ok so i think my problem might have been that i was trying to execute motofail root exploit through winrar... i had not extracted the files to a folder and when i tried that litterally as my last resort, it worked. rooted perfectly. have super user and everything. so if people are having this problem like i was, try motofail, make sure to extract all the stuff to a folder first, and then run the exploit... ugh. what an experience
    I'm just guessing, but I bet that is the same problem you had when trying to use the Razr Utility...you have to extract the zip to a folder then run the .bat file.
  5. Droid Newbie
    lpoppe22's Avatar
    Member #
    107115
    Join Date
    Aug 2010
    Posts
    3
    Phone
    Moto Droid Razr MAXX
    #4

    yup. you're right

    Quote Originally Posted by jpcalhoun View Post
    I'm just guessing, but I bet that is the same problem you had when trying to use the Razr Utility...you have to extract the zip to a folder then run the .bat file.
    I think that is correct. it was weird though. i think it worked without being extracted the first time though. im not sure, but all utilities work now. i just wish i had figured that out about 12 hours ago, lol. Now at least i have a bunch of help pages bookmarked so if i do have a problem, i can find the, now, haha
    Last edited by lpoppe22; 04-24-2012 at 08:29 PM. Reason: mis-titled the comment

Links

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Similar Threads

  1. Replies: 7
    Last Post: 09-15-2011, 12:49 PM
  2. REPOST! [Fix]EE4 sdcard write protection for root users
    By Raptor007 in forum Droid Charge Development
    Replies: 0
    Last Post: 06-10-2011, 10:01 AM
  3. Write access in Root Explorer?
    By ThirdWheel in forum Droid X Hacks
    Replies: 2
    Last Post: 08-27-2010, 08:47 AM
  4. HOW to ROOT 2.1? any write up available?
    By dfwdroid in forum Android Hacks and Help
    Replies: 4
    Last Post: 05-20-2010, 10:02 PM
  5. To write a Term Paper or To Root, that is thy question
    By Pagaldesi4life in forum Android Hacks and Help
    Replies: 22
    Last Post: 03-09-2010, 05:01 PM

Search tags for this page

/system/xbin/busybox: cannot open for write: read-only file

,
cannot open for write read-only file system android
,
failed to copy files su to /system/bin/su read-only file sys
,
failed to copy files superuser.apk to /system/app/./superuse
,

failed to copy su to '/system/bin/su': read-only file system

,
failed to copy su to /system/bin/su read-only file system
,

failed to copy superuser.apk read-only file system

,
failed to copy superuser.apk to '/system/app/./superuser.apk
,

mkdir failed for tmp file exists

,
rm failed for /system/xbin/su, read-only file system
Click on a term to search our site for related topics.

Tags for this Thread

Find us on Google+