Results 1 to 4 of 4
  1. Thread Author  Thread Author    #1  

    Default Problems with Rooting S3 after Stock Restore

    Hi, I recently returned to factory defaults (4.1.1) after trying out CM on my Galaxy S3. I am now trying to root my phone (and eventually create a backup), but I am having problems with Rootdebugfs (superuser and superSU). Here is the output of the superSU version:



    Step 1 - Setup...

    Copying chainfire's SU files:

    Copying chainfire's SU:
    failed to copy 'su' to '/data/local//su': Permission denied

    Copying debugfs:
    failed to copy 'debugfs' to '/data/local//debugfs': Permission denied

    Copying debugfsinput:
    failed to copy 'debugfsinput' to '/data/local//debugfsinput': Permission denied

    ...done copying files.


    Linking /system to tmp...
    failed on '/data/local/tmp' - Permission denied
    link failed File exists
    ...done linking /system


    Rebooting...


    rm: File not found by ext2_lookup while trying to resolve filename

    This just means there wasn't an existing root/SU found on your phone.


    Press any key to continue . . .
    * server not running *


    Unable to chmod /data/local/debugfs: No such file or directory
    /system/bin/sh: can't open /data/local/debugfsinput: No such file or directory



    Cleaning up...

    Restoring tmp...
    rm failed for /data/local/tmp, Permission denied
    failed on '/data/local/tmp.bak' - No such file or directory
    ...done restoring tmp

    Removing files...
    rm failed for /data/local/su, No such file or directory
    rm failed for /data/local/debugfs, No such file or directory
    rm failed for /data/local/debugfsinput, No such file or directory
    ...done removing files.

    Rebooting...



    Testing chainfire's SU file installation...
    /system/bin/sh: /system/xbin/su: not found

    uid and gid should both be 0.
    Are they? (y/n): n

    ------------------------------------------------------------------------

    Does anyone know why I'm missing those /system files?
  2. #2  

    Default

    Quote Originally Posted by Joseph Myers View Post
    Hi, I recently returned to factory defaults (4.1.1) after trying out CM on my Galaxy S3. I am now trying to root my phone (and eventually create a backup), but I am having problems with Rootdebugfs (superuser and superSU). Here is the output of the superSU version:

    I understand that debugfs does not work for 4.1.1.

    Step 1 - Setup...

    Copying chainfire's SU files:

    Copying chainfire's SU:
    failed to copy 'su' to '/data/local//su': Permission denied

    Copying debugfs:
    failed to copy 'debugfs' to '/data/local//debugfs': Permission denied

    Copying debugfsinput:
    failed to copy 'debugfsinput' to '/data/local//debugfsinput': Permission denied

    ...done copying files.


    Linking /system to tmp...
    failed on '/data/local/tmp' - Permission denied
    link failed File exists
    ...done linking /system


    Rebooting...


    rm: File not found by ext2_lookup while trying to resolve filename

    This just means there wasn't an existing root/SU found on your phone.


    Press any key to continue . . .
    * server not running *


    Unable to chmod /data/local/debugfs: No such file or directory
    /system/bin/sh: can't open /data/local/debugfsinput: No such file or directory



    Cleaning up...

    Restoring tmp...
    rm failed for /data/local/tmp, Permission denied
    failed on '/data/local/tmp.bak' - No such file or directory
    ...done restoring tmp

    Removing files...
    rm failed for /data/local/su, No such file or directory
    rm failed for /data/local/debugfs, No such file or directory
    rm failed for /data/local/debugfsinput, No such file or directory
    ...done removing files.

    Rebooting...



    Testing chainfire's SU file installation...
    /system/bin/sh: /system/xbin/su: not found

    uid and gid should both be 0.
    Are they? (y/n): n

    ------------------------------------------------------------------------

    Does anyone know why I'm missing those /system files?
    ☆ ★ | ROM | [JellyBean][4.3] BeanStalk Build 4.3.1001 - [04 OCT] |★ ☆



  3. #3  

    Default Re: Problems with Rooting S3 after Stock Restore

    What method are you using to root? Also are you running 4.1.1?

    Sent from my SCH-I535 using Android Central Forums
  4. Thread Author  Thread Author    #4  

    Default Re: Problems with Rooting S3 after Stock Restore

    Well, I took it into the Verizon store and convinced them I needed a new phone. It took almost four hours, but I think it was worth it. I may try flashing CM again once Android 4.2 is stable.

Similar Threads

  1. Problem with some apps after root.
    By Tyler08Gee in forum Inspire Rooting, ROMs, and Hacks
    Replies: 1
    Last Post: 05-10-2011, 11:38 PM
  2. Problems with rooting HTC
    By Mr.Verizon in forum Incredible Rooting, ROMs, and Hacks
    Replies: 4
    Last Post: 10-12-2010, 09:21 AM
  3. problems with music player after update
    By highbloodsugar in forum Verizon Droid Incredible
    Replies: 6
    Last Post: 09-30-2010, 10:51 AM
  4. Problems with rooting
    By Matt_8900 in forum Google / HTC Nexus One
    Replies: 3
    Last Post: 08-15-2010, 05:28 PM
  5. Problems with Google Sync after 2.1 update
    By adervaes in forum HTC Droid Eris
    Replies: 1
    Last Post: 05-17-2010, 07:02 AM

Posting Permissions

B