Something broke during SuperSu based Rooting process


Last Updated:

  1. pontifikas

    pontifikas Member This Topic's Starter

    Joined:
    Feb 10, 2013
    Messages:
    10
    Likes Received:
    0
    After following the guide, I run into the following problem.
    Whenever I open Super Su I get a message that th Binary file must be updated. If I press cancel super su closes. If I press ok, another message appears informing me that update has failed and then the phone cold-reboots. I cannot uninstall SuperSu and I don't know how to reverse the rooting process.
    Actually, up to today, whereupon I installed the latest update of SuperSu, my phoned appeared to be rooted (I used some application that checks that). However, if I tried to access the filesystem (e.g. I wanted to install Avast root enabled functionality), I would again get a cold-reboot. So it was obvious that the rooting process was incomplete or broken.
    Is there a way I get rid of the SuperSu application, unroot, and try to start over the process?

    Thank you in advance.
    Giorgos
     

    Advertisement
  2. agentc13

    agentc13 Daleks Über Alles VIP Member

    Joined:
    Aug 31, 2011
    Messages:
    7,916
    Likes Received:
    5,482
    Did you make a nandroid before flashing the root binaries?
     
  3. pontifikas

    pontifikas Member This Topic's Starter

    Joined:
    Feb 10, 2013
    Messages:
    10
    Likes Received:
    0
    If you are referring to the step you describe at the end of the Guide Post "Installing ClockworkMod Recovery" then, I'm afraid I did something wrong there. I made a back up using the software provided by my phone(Settings->Back up and Reset), not through the fastboot mode.
     
  4. agentc13

    agentc13 Daleks Über Alles VIP Member

    Joined:
    Aug 31, 2011
    Messages:
    7,916
    Likes Received:
    5,482
    I was referring to making a backup through the custom recovery.
    It's always good to have a nandroid backup you can restore to fix issues. If you made one like suggested, I would restore that and flash the superuser binaries or reflash the SuperSU binaries.

    If you didn't make a nandroid, then I would suggest relocking the bootloader then running a RUU to return to stock. You can then Unlock the bootloader again and flash the superuser binaries or the SuperSU binaries. You will need the correct RUU for your device/carrier in order to do this.
     
  5. pontifikas

    pontifikas Member This Topic's Starter

    Joined:
    Feb 10, 2013
    Messages:
    10
    Likes Received:
    0
    Thank you for the reply. I already started downloading the RRU (though I have no idea what that is...) from the link you provide (by the way the xda-developers link is invalid), and I found I guide on how to re-lock.
    I will report if this solved my problem.
     
  6. agentc13

    agentc13 Daleks Über Alles VIP Member

    Joined:
    Aug 31, 2011
    Messages:
    7,916
    Likes Received:
    5,482
    The RUU is a windows .exe file (a program you can run in windows) with your phone connected via USB in order to return it to stock. You have to relock the bootloader before running one. You just have to make sure you have the correct one for your carrier/software version. ;)
     
  7. pontifikas

    pontifikas Member This Topic's Starter

    Joined:
    Feb 10, 2013
    Messages:
    10
    Likes Received:
    0
    Hang on. How do I figure out which file matches my phone? Where do I find the numbers displayed on the files you listed? My phone is not from some carrier btw.
     
  8. pontifikas

    pontifikas Member This Topic's Starter

    Joined:
    Feb 10, 2013
    Messages:
    10
    Likes Received:
    0
    I relocked the phone. But I don't know how to locate the correct RRU.
    My baseband version is 1.11.50.05.28.
     
  9. agentc13

    agentc13 Daleks Über Alles VIP Member

    Joined:
    Aug 31, 2011
    Messages:
    7,916
    Likes Received:
    5,482
    Is your phone a S3 processor of S4? (I assume S4, since you said something about CWM recovery). Also, is it carrier branded or the unlocked international version? And lastly, what software version is it? (1.53, 1.84, 2.35, etc not the baseband)
     
  10. pontifikas

    pontifikas Member This Topic's Starter

    Joined:
    Feb 10, 2013
    Messages:
    10
    Likes Received:
    0
    Yes I have an S4 phone. And I don't think it is carrier branded. I see no logo on startup or anywhere.

    Since none of the numbers you reference resembles the ones I see under software info, I will write what I figure it might be relevant:
    In fastboot:
    HB00T-2.15.0000
    RADIO - (see my previous post)
    OpenDSP - v31.1.0.45.0815

    In phone info:
    SW Number - 3.16.401.8
    Android Version - 4.1.1
    Kernel Version - 3.4.10
     
  11. agentc13

    agentc13 Daleks Über Alles VIP Member

    Joined:
    Aug 31, 2011
    Messages:
    7,916
    Likes Received:
    5,482
    Can you boot into bootloader, make sure you are in fastboot mode and type "fastboot getvar all"?

    Then copy that info here? Just leave out the serialno and imei. I'm pretty sure I have the right RUU, but that will help to make sure.

    I think I found the OTA zip, but having some trouble finding the RUU that I think it is.
     
  12. agentc13

    agentc13 Daleks Über Alles VIP Member

    Joined:
    Aug 31, 2011
    Messages:
    7,916
    Likes Received:
    5,482
    It might be this one, but let's wait to see what you get when entering that command before jumping in.
     
  13. pontifikas

    pontifikas Member This Topic's Starter

    Joined:
    Feb 10, 2013
    Messages:
    10
    Likes Received:
    0
    Again thank you for your time. Here is the output of the command you wrote:
    (bootloader) version: 0.5
    (bootloader) version-bootloader: 2.15.0000
    (bootloader) version-baseband: 1.11.50.05.28
    (bootloader) version-cpld: None
    (bootloader) version-microp: None
    (bootloader) version-main:
    (bootloader) version-misc: PVT SHIP S-ON
    (bootloader) serialno: ****************
    (bootloader) imei: ******************
    (bootloader) product: vle
    (bootloader) platform: HBOOT-8960
    (bootloader) modelid: PJ4010000
    (bootloader) cidnum: HTC__102
    (bootloader) battery-status: good
    (bootloader) battery-voltage: 3976mV
    (bootloader) partition-layout: Generic
    (bootloader) security: on
    (bootloader) build-mode: SHIP
    (bootloader) boot-mode: FASTBOOT
    (bootloader) commitno-bootloader: dirty-64bedd38
    (bootloader) hbootpreupdate: 11
    (bootloader) gencheckpt: 0

    I will try the files you gave me and let you know.

    EDIT: Err...how do I use the OTA file?
     
  14. pontifikas

    pontifikas Member This Topic's Starter

    Joined:
    Feb 10, 2013
    Messages:
    10
    Likes Received:
    0
    It appears that the RUU worked!
    Thank you very much. I will now retry to root the phone(and perform a proper backup...)
    :D
     
  15. agentc13

    agentc13 Daleks Über Alles VIP Member

    Joined:
    Aug 31, 2011
    Messages:
    7,916
    Likes Received:
    5,482
    Good. Definitely make a n android backup before rooting (but after flashing the recovery ;)).
     
    pontifikas likes this.
  16. razvan06

    razvan06 Well-Known Member

    Joined:
    Jun 5, 2010
    Messages:
    696
    Likes Received:
    89
    What you have there happened to me before...it's from the root patch, that's faulty !

    Since you have a unbranded phone, any Europe_X.X.401.X RUU will work [be advised that you cannot downgrade if you have JB !] at least from what experiments i've done with my HOX at the time...

    You can :

    -Either RUU the device again if something fails...
    -Or install a rooted ROM, i have a "self-made" ASBS [Android Sense Best Stock] ROM right now and i'm pretty happy with it AND i can install SuperSU or Superuser on it !
     
  17. JesusHasADroid

    JesusHasADroid Member

    Joined:
    Jul 22, 2010
    Messages:
    11
    Likes Received:
    1
    can someone lead me to the ruu for my tmo htc one s

    (bootloader) version: 0.5
    (bootloader) version-bootloader: 1.14.0005
    (bootloader) version-baseband: 1.13.50.05.25
    (bootloader) version-cpld: None
    (bootloader) version-microp: None
    (bootloader) version-main:
    (bootloader) version-misc: PVT SHIP S-ON
    (bootloader) serialno: HT24AW400591
    (bootloader) imei: 359902040700928
    (bootloader) product: vle
    (bootloader) platform: HBOOT-8960
    (bootloader) modelid: PJ4011000
    (bootloader) cidnum: T-MOB010
    (bootloader) battery-status: good
    (bootloader) battery-voltage: 4125mV
    (bootloader) partition-layout: Generic
    (bootloader) security: on
    (bootloader) build-mode: SHIP
    (bootloader) boot-mode: FASTBOOT
    (bootloader) commitno-bootloader: 8be28a51
    (bootloader) hbootpreupdate: 11
    (bootloader) gencheckpt: 0
    all: Done!
    finished. total time: 0.074s
     
  18. razvan06

    razvan06 Well-Known Member

    Joined:
    Jun 5, 2010
    Messages:
    696
    Likes Received:
    89

    I think this one should do the trick : Androidfiles RUU

    ...if not, it will just fail before installing, so... no worries :)

    - remember to have your bootloader locked
    - RUN and intall RUU in bootloader mode !
     
  19. Jamie10023

    Jamie10023 New Member

    Joined:
    Mar 12, 2014
    Messages:
    1
    Likes Received:
    0
    It happened with me aswell but this was a few months after I got it and then I wasn't able to download some things via the internet that I could before and then on that same day my google play store stopped working. What should I do?
     

Share This Page

Loading...