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

Root rerooting after Android 4.3 OTA update issue

Discussion in 'Android Devices' started by MarmiteX1, Jul 27, 2013.

  1. MarmiteX1

    MarmiteX1 Well-Known Member
    Thread Starter
    Rank:
    None
    Points:
    48
    Posts:
    105
    Joined:
    Dec 27, 2010

    Dec 27, 2010
    105
    10
    48
    Software Engineer
    Hi there,

    I am not sure what i should do.

    I rooted my n4 back in March of this year and been running stock android 4.2.2.

    Today i installed Android 4.3 OTA and i forgot to accept the settings which CWM ask you after its installed e.g Yes” if it asks you for root fix or recovery fix.

    So therefore eventhough i have all my apps, my rooted apps don't work any longer as the SU binary can't be found according to SuperSu app.

    Everytime i open SuperSu installed i keep getting the error:
    "There is no SU binary Installed and SuperSu cannot install it".

    Also my CWM has been replaced with the stock recovery after the update.

    Now i booted my phone into bootloader and it says the following:
    SECURE BOOT - enabled
    LOCK STATE - unlocked

    The boot animation "Google" shows a unlocked padlock.

    If i want to install CWM and Su binary do i need to the following?:

    1. Copy latest SuperSU zip file to the device
    2. Open command prompt/shell and navigate to the folder where the latest adb and fastboot.exe and recovery image exists.
    3. Backup all the data from the phone to be safe. i used adb backup -apk -all -f nameofthebackup.ab
    4. Install Custom recovery image
    5. Flash the zip file
    6. Reboot
    7. Choose the option "Yes- to disable stock recovery"
    8. Check if i have #Su back?
    Any advice would be appreciated.

    ****UPDATE****
    For anyone else having the same issue as i did. I managed to resolve the issue by following the steps outlined above. Before flashing anything make sure you have the latest adb.exe and fastboot.exe. Backup the data before doing anything! The version of adb i used was 1.0.31 to be exact. Worked like a charm!

    I flashed the recovery image and then flashed the latest SuperSu file which supports 4.3. I went back into the SuperSu app and it didnt throw an error.
     

    Advertisement

  2. suparuss

    suparuss Member
    Rank:
    None
    Points:
    16
    Posts:
    65
    Joined:
    Jul 26, 2011

    As the update above - you need to flash SU via the recovery method
     
Tags:

Share This Page

Loading...