1. Download our Official Android App: Forums for Android!

Root [AT&T] assert failed get prop....+ no superuser capabilities

Discussion in 'Android Devices' started by LIVE2LEARN, Jul 17, 2013.

  1. LIVE2LEARN

    LIVE2LEARN Lurker
    Thread Starter

    Currently on phone:
    CWM recovery v5.5.0.4
    stock rom (AT&T)
    superuser

    I keep running into the same errors. "assert failed:get prop("ro .product.device)" as well as the errors from root checker pro. I am trying to have my phone fully rooted. not half rooted as it seems to be.

    I've come across multiple solutions for this and after attempting to resolve multiple times I've had no success.(remove the get prop from the script)(update Recovery to latest version)

    I've also purchased root checker pro. Below are the results from there.

    Root Access is not properly configured or was not granted.

    Super User Applications Status:
    Superuser application - version 3.0.7 - is installed!
    SuperSU application - version 1.41 - is installed!

    System File Properties for Root Access:
    Standard Location
    Check Command: ls -l /system/bin/su:
    Result: -rwsr-sr-x root root 22364 2008-08-01 07:00 su
    Analysis: Setuid attribute is present and root user ownership is present. Root access is correctly configured for this file! Executing this file can grant root access!


    Standard Location
    Check Command: ls -l /system/xbin/su:
    Result: /system/xbin/su: No such file or directory
    Analysis: File /system/xbin/su does not exist.

    Alternative Location
    Check Command: ls -l /sbin/su:
    Result: /sbin/su: Permission denied
    Analysis: File system permissions restricted and denied access.

    Alternative Location
    Check Command: ls -l /system/xbin/sudo:
    Result: /system/xbin/sudo: No such file or directory
    Analysis: File /system/xbin/sudo does not exist.

    Root User ID and Group ID Status:
    SU binary not found or not operating properly

    System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin

    ADB Shell Default User:
    ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1

    Results provided on your SAMSUNG-SGH-I747 device by Root Checker Pro version 1.3.3 from joeykrim in the Android Market - h-ttp: //goo- .gl/Ncn Hn




    I've also attempted to upgrade CWM recovery to 6.0.3.1 ( i think) but after a pass from odin i reboot into recovery to the same version as before 5.5.0.4



    I've been researching and attempting to fix on my own for the past month. A few hours a week are solely dedicated to this.
     

    Advertisement

  2. MercilessLTD

    MercilessLTD Member

    Well, let me hope we can figure this out.

    First of all, the assert() method in recovery is used to make sure that the equality or inequality being calculated is correct. Given that it is calling getprop("ro.product.device"), there should be something else after that, such as == "d2att".

    If this assert is failing to match the device, you may have downloaded the wrong ROM. Typically this assertion is done to ensure the device being flashed is intended for the ROM downloaded. Flashing an incorrect ROM can cause unwanted side effects, possibly bricking the device.

    As for your SU issue, it seems you have the apps installed, but the binaries are not there. The apps are only for management, they are not the actual executables that allow elevated privileges. There is a binary executable that is stored in one of the locations (the locations listed in your post where they could not be found) and this is what is used to give applications the access they seek. It seems that you need to attempt to root once again.
     
  3. SprintS5guy

    SprintS5guy Member

    id re-root it with odin. thats the thermonuclear way of doing it, but its pretty much error proof so long as you do it right ;)
     
Loading...

Share This Page

Loading...