DROID BIONIC Jelly Bean Update

[SamuriHL]

Thanks for the recommendation. I'll take a good look at Koush's. Wasn't real impressed with SuperSU. Now Voodoo looks for Superuser to be installed. Is that a problem or is there a workaround for that?

Sent from my DROID BIONIC using Tapatalk 2

It's not an issue. Koush's is called Superuser.apk

 

[Erievon]

Don't cry. I just spent an hour with DJRBliss. What's this I see? Is that supersu granting root permissions to apps on my phone? I think it might be!

A parting gift from both of you. NOW I may cry

 

[johnejo]

It's not an issue. Koush's is called Superuser.apk

I uninstalled Superuser and installed Koush's. I then went back to Voodoo to make sure everything is okay and it indicates Superuser is not installed and prompts me to go to Google Play to get it. Voodoo did get root access through Koush's, however, but doesn't recognize it as the app it's looking for. Just want to make sure this isn't going to be a problem for protecting root.

Thank you.

Sent from my DROID BIONIC using Tapatalk 2

 

[MikeSaya]

That's because you uninstalled SuperUser first. You need to install SuperSU, get root permissions first then u can uninstall SuperUser.

 

[MikeSaya]

I uninstalled SuperuserKoush's and installed Koush's. I then went back to Voodoo to make sure everything is okay and it indicates Superuser is not installed and prompts me to go to Google Play to get it. Voodoo did get root access through Koush's, however, but doesn't recognize it as the app it's looking for. Just want to make sure this isn't going to be a problem for protecting root.

Thank you.

Sent from my DROID BIONIC using Tapatalk 2

Reinstall superuser, get root permissions for Koush's, then uninstall superuser.

 

[SamuriHL]

If anyone used the House of Bionic to install Voodoo, please uninstall it and reinstall it from the play store. There appears to be something wrong with it. I'm updating HoB to version 10.1 which has a fixed apk shortly but just a heads up for those that already used the HoB to install it.

 

[johnejo]

Reinstall superuser, get root permissions for Koush's, then uninstall superuser.

Okay. Just did what you said with same results. Oh, well.

Thank you.

Sent from my DROID BIONIC using Tapatalk 2

 

[SamuriHL]

[ROOT] Motoshare 2: Old Bug, New Exploit - DroidRzr News and Reviews - DroidRzr.com

Go get em.

 

[BigTeeGolfer]

BTW, I mentioned this in the HoB thread and I'll mention it here, as well. ChainDD's Superuser is the most widely used super user app. However, ALL of the people that I'm aware of that had problems restoring root after the JB update were using it. Those who used SuperSU or Koush's Superuser apps did not run into restore problems. I'm hereby recommending that everyone switch to either SuperSU or Koush's Superuser so that you don't have problems going forward. Koush's is open source which is a VERY good thing. CM has recently switched to it. I may switch from SuperSU to Koush's Superuser myself. I very well may update the HoB one last time and switch is so any stragglers who were waiting to upgrade to JB can switch. Just my opinion. Take it as you will.

First off, thanks Sam for all you do. I tracked the ICS update thread for weeks, prior to this one. I rooted through HOB and have ChainDD's superuser. I was able to keep root through the update, but I did not wait for the OTA. Perhaps one difference I did was I first updated binaries from within superuser as was suggested before protecting root, however I also noticed that play store said there was an update for superuser, so I did that update, and again updated binaries from within superuser. This did get me a newer version of the binaries than the original update had. I then deleted my backup through voodoo and created a new one. After that all was good and I was able to get root back from the backup after the update.

 

[moonlightinwhite]

Reinstall superuser, get root permissions for Koush's, then uninstall superuser.

Before I make a mistake that I regret, I just want to double-check this, even though the answer seems obvious: I'm already rooted in JB and using ChainsDD's Superuser (https://forums.androidcentral.com/e...ils?id=com.noshufou.android.su&token=ZLww43wU)...in order to switch to Clockworkmod's (Koush's) Superuser (https://forums.androidcentral.com/e...?id=com.koushikdutta.superuser&token=e3E_Ikrn), I should:

1.) Download and install Koush's Superuser from the Play Store
2.) Run, update the binaries, and grant it permissions using the existing SU app
3.) Uninstall old (ChainsDD) Superuser

...and I shouldn't lose root, right? I don't want to have to do the more involved re-rooting if I mess this up

 

[SamuriHL]

Before I make a mistake that I regret, I just want to double-check this, even though the answer seems obvious: I'm already rooted in JB and using ChainsDD's Superuser (https://forums.androidcentral.com/e...ils?id=com.noshufou.android.su&token=y11yCMwn)...in order to switch to Clockworkmod's (Koush's) Superuser (https://forums.androidcentral.com/e...?id=com.koushikdutta.superuser&token=xr8n0GZc), I should:

1.) Download and install Koush's Superuser from the Play Store
2.) Run, update the binaries, and grant it permissions using the existing SU app
3.) Uninstall old (ChainsDD) Superuser

...and I shouldn't lose root, right? I don't want to have to do the more involved re-rooting if I mess this up

Kids these days. LMAO.

o) Install Voodoo OTA Rootkeeper from the play store (not the HoB version as it's fubar)
o) Protect root
o) Install Koush's Superuser
o) Run Koush's Superuser...it will ask for SU permissions. Grant it.
o) It will prompt about updating the su binary. Allow it to do so
o) Uninstall ChainDD Superuser
o) Verify root is working
o) Delete protected su backup in Voodoo
o) Create new protect su backup in Voodoo

 

[moonlightinwhite]

Kids these days. LMAO.

o) Install Voodoo OTA Rootkeeper from the play store (not the HoB version as it's fubar)
o) Protect root
o) Install Koush's Superuser
o) Run Koush's Superuser...it will ask for SU permissions. Grant it.
o) It will prompt about updating the su binary. Allow it to do so
o) Uninstall ChainDD Superuser
o) Verify root is working
o) Delete protected su backup in Voodoo
o) Create new protect su backup in Voodoo

I "uninstalled" ChainDD's via ROM Toolbox because it's set as a system app...uninstall was successful according to Toolbox (it no longer shows up in the app list), but it's still showing up in the app drawer. Weird. Upon a reboot, it automatically updates itself (and shows up in Toolbox again). It's like it's only uninstalling updates. Should I try converting ChainDD's to a non-system app?

 

[SamuriHL]

Yea, it gets pushed to /system/apps so you could remove it from there once you have su working with Koush's Superuser. I updated the root exploit to stop doing that.

 

[moonlightinwhite]

Well, I didn't use HoB...I preserved root when I updated, so it was a system app before (which, perhaps, is why I didn't have to do anything special, despite having partial root after update). Anyway, converting it to a user app definitely fixed the problem.

How do I convert the new Superuser to a system app? When I try, it fails...and then, upon reboot, it's completely gone (ie. it doesn't show up in the drawer, in Toolbox, or as installed when I view it in the Play Store). When I download and reinstall it, though, it remembers settings and the apps I've already granted permission to AND I don't have to restore anything through Voodoo...all of which is interesting, IMO.

 

[SamuriHL]

Leave it as a user app. That's how I've got mine set. If you do an FDR for whatever reason, you'll have to reinstall it but that's kinda the point of an FDR. su itself won't go away during an FDR so you'll still have root.

 

[jimbarr]

Kids these days. LMAO.

o) Install Voodoo OTA Rootkeeper from the play store (not the HoB version as it's fubar)
o) Protect root
o) Install Koush's Superuser
o) Run Koush's Superuser...it will ask for SU permissions. Grant it.
o) It will prompt about updating the su binary. Allow it to do so
o) Uninstall ChainDD Superuser
o) Verify root is working
o) Delete protected su backup in Voodoo
o) Create new protect su backup in Voodoo

SamuriHL, once again, you ROCK! Worked like a charm. Thanks!

 

[AllPurposeRadio]

Ok I downloaded and installed the the JB update last Monday from the file Sam posted. No issues whatsoever until say last Thursday when I started some serious lag & lockups. Decided to do a factory reset on Saturday. That went fine & things working as smooth as ever with the exception that I periodically am seeing somekind of weird error message related to the wifi connection. The wifi is working fine. Any solution to getting the message to go away? I did try forgetting the connection and reconnecting several times to no avail.

Sent from my Kindle Fire using Android Central Forums

 

[ZwRaven]

Ok I ran the root exploit from linux and this is what I got, what am I doing wrong?
zach@ubuntu:/tmp/share$ sudo chmod 755 run.sh
zach@ubuntu:/tmp/share$ sudo /run.sh
sudo: /run.sh: command not found
zach@ubuntu:/tmp/share$ sudo ./run.sh
./run.sh: line 30: ./adb.linux: No such file or directory
[+] Waiting for device...
./run.sh: line 33: ./adb.linux: No such file or directory
[+] Device found.
[+] Pushing exploit...
./run.sh: line 38: ./adb.linux: No such file or directory
./run.sh: line 39: ./adb.linux: No such file or directory
./run.sh: line 40: ./adb.linux: No such file or directory
./run.sh: line 42: ./adb.linux: No such file or directory
./run.sh: line 43: ./adb.linux: No such file or directory
[+] Rooting phone...
[+] Your phone may appear to reboot. Please ignore this and continue with the exploit.
./run.sh: line 49: ./adb.linux: No such file or directory
[+] Please press any hardware button on your phone.
[+] Don't worry if the phone is unresponsive at this time.
[+] Press enter to continue once you have pressed a hardware button.

[*] Cleaning up...
./run.sh: line 58: ./adb.linux: No such file or directory
./run.sh: line 59: ./adb.linux: No such file or directory
./run.sh: line 60: ./adb.linux: No such file or directory
[*] Exploit complete. Press enter to reboot and exit.



ANY help would be awesome! Thanks.

 

[SamuriHL]

64 bit issues. Switch to a 32 bit linux distro or figure out how to run 32 bit apps in your 64 bit linux install.

 

[ZwRaven]

Cool thanks. I will do that.