PaulOBrien

Superboot - Nexus 4 root solution

36 posts in this topic

Hi all, has anyone used this method lately? Am getting a Nexus 4 tomorrow and just wanted to confirm that everything is working.

Also, I assume that I need to install the Android SDK to get all the right drivers etc?

0

Share this post


Link to post
Share on other sites
Hi all, has anyone used this method lately? Am getting a Nexus 4 tomorrow and just wanted to confirm that everything is working.

Also, I assume that I need to install the Android SDK to get all the right drivers etc?

Think I used the wugfresh toolkit (should be linked to in my signature) at xda - made it super simple - but I'm sure Paul's superboot should be fine too

0

Share this post


Link to post
Share on other sites

Paul, any chance of an update to Superboot with the SuperSU version that works with 4.3 ?

0

Share this post


Link to post
Share on other sites

Paul, any chance of an update to Superboot with the SuperSU version that works with 4.3 ?

Hah. Wish I'd seen this before trying the old one.

Seconded... :P

EDIT: I've just tried modifying the boot.superboot.img with the latest su and SuperUser.apk from Koush, but although it's installed, I still don't seem to have root. I wonder if that's related to the fact that the OTA Rootkeeper did not, in fact, keep a copy of root.

Edited by Mr.Clark
0

Share this post


Link to post
Share on other sites

OTA RootKeeper didn't keep root for me, though after trying the old Superboot the "Device Rooted" box is now ticked though the "Root permission granted" box still is not.

I tried booting TWRP/CWM/PhilZ custom recoveries (as opposed to flashing them permanently), but none would boot to the point of letting me flash a zip (all stopped at a blank screen), so i could not flash the latest SuperSU package.

0

Share this post


Link to post
Share on other sites

there's a SuperSU package intended for the leak whick works sort of reliably, but TB really doesnt work for restoring backups..... ATM i've gone back to MCMCR until everything is working

0

Share this post


Link to post
Share on other sites

If anyone wants root on stock, I had to flash CWM Recovery and install the latest SuperSU package (the one specifically designed for 4.3). Looks like Google have figured out how to properly break "traditional" root - the new SuperSU uses some whacky daemon thing to do it's work.

That said, it does work, so you can have root until one of the SU guys fixes what Google broke.

Now to figure out how to get stock recovery back...

0

Share this post


Link to post
Share on other sites

If anyone wants root on stock, I had to flash CWM Recovery and install the latest SuperSU package (the one specifically designed for 4.3). Looks like Google have figured out how to properly break "traditional" root - the new SuperSU uses some whacky daemon thing to do it's work.

That said, it does work, so you can have root until one of the SU guys fixes what Google broke.

Now to figure out how to get stock recovery back...

That's where I got to, I don't want a custom recovery at this point, so I thought I'd be cheeky and see if Paul felt kind enough to update his Superboot ;)

0

Share this post


Link to post
Share on other sites

That's where I got to, I don't want a custom recovery at this point, so I thought I'd be cheeky and see if Paul felt kind enough to update his Superboot ;)

As a mate just pointed out, the original recovery.img is in the image-occam-jwr66v.zip file, so you can have your cake and eat it. :)

Just a single run of Superboot is easier, of course, but I think that the changes that Chainfire has made to get root to work means it could be a bit more complicated to get Superboot working than just updating a few files.

0

Share this post


Link to post
Share on other sites

As a mate just pointed out, the original recovery.img is in the image-occam-jwr66v.zip file, so you can have your cake and eat it. :)

Just a single run of Superboot is easier, of course, but I think that the changes that Chainfire has made to get root to work means it could be a bit more complicated to get Superboot working than just updating a few files.

Ok, I gave in, I flashed TWRP 2.6.0.0 recovery, flashed SuperSU 1.41, then flashed the original recovery.img back. It's a good job I always unlock the bootloader before I do any updates really, usually leave it locked because I have the BootUnlocker tool installed. I also did the TitaniumBackup fix of changing the backup directory from /storage/emulated/0/TitaniumBackup to /storage/emulated/legacy/TitaniumBackup. If Superboot is updated though then I'll happily revert to test, having asked the question in the first place ;)

EDIT : SuperSU has been updated to 1.43 to deal with some of the bugs, ZIP linked below, update also live in the Play Store

SuperSU 1.41 download : http://download.chai...130625-1.41.zip

SuperSU 1.43 download : http://download.chainfire.eu/342/SuperSU/UPDATE-SuperSU-v1.43.zip

TWRP 2.6.0.0 download : http://techerrata.co....6.0.0-mako.img

BootUnlocker for Nexus Devices download: https://play.google....11.bootunlocker

TitaniumBackup fix walkthrough :

Edited by englishpunk
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2016. MoDaCo uses IntelliTxt technology.