NOTICE: This content was originally posted to Google+, then imported here. Some formatting may be lost, links may be dead, and images may be missing.
This is mostly a bugfix release for Android 4.3.
The CPU spike thing should be resolved. At least, the cases I was able to reproduce have been fixed, which does not mean there may not still be different cases out there that can cause this behavior. If you run into it, please let me know. The origin of the spike is root-using apps closing the su session in new and unexpected ways (some devs are really inventive with this).
The su binary for the moment also symlinks /storage/emulated/<uid> to /data/media/<uid> . This might fix some issues with some apps. However, the authors of said apps should still put the time in and fix this properly. This is a temporary(!) band-aid solution. I will post some more about this problem and mounts in general in a separate post aimed more at techs and devs.
I do recommend an upgrade to this version if you are currently on 1.41, as no root app dev will want to deal with the quirks of 1.41 in daemon-mode for the long term.
Also, please note this release actually breaks Triangle Away (update ASAP), and may break some other things that might use install-recovery.sh to do magic. That sucks, but until we come up with a better way of installing this, that's how it's going to be. If you're building a custom ROM, you should replace the install-recovery.sh method of launching the daemon with a proper init service.
The TWRP flashable ZIP is here: http://download.chainfire.eu/342/SuperSU/UPDATE-SuperSU-v1.43.zip
If you're using a recovery that asks you if it should disable flashing the stock recovery, answer no.
EDIT#1: CF-Auto-Root's for Galaxy Nexus, Nexus 4, Nexus 7 and Nexus 10 have been updated with SuperSU v1.43 for Android 4.3 - http://autoroot.chainfire.eu/
EDIT#2: SuperSU has been updated on the Play Store (will take a few hours to propagate), but if you're going from 4.2 to 4.3, you still need to re-root "manually" by using the ZIP file or CF-Auto-Root. Just updating the app is not enough to make 4.3 work.
Thanks, hurrahs, declarations of love (or hate), etc can go here. For meaningful discussion, go to the thread on XDA developers:
I will not comment in-depth on G+ !
Daemon: code/security mini-audit by +Joshua J. Drake
Daemon: cwd is now respected
Daemon: auto-daemon feature
Deamon: fixed cpu spike issue
Daemon: symlinks sdcard (temporary)
TWRP-based update: fixed script error
GUI: Added 4.3 update notice
GUI: Removed full content logging global warning
Updated language files
It finally works :) Thank you so much!
I just had the CPU spike thing happen. You mention the zip is TWRP-flashable, does it also work in CWM?
+Jonathan Berry I flashed it using CWM. Works fine. Just answer "No" if asked to disable flashing the stock recovery after selecting to reboot the device.
Thank you so much Chainfire, testing in Nexus 4 with Stock Deodexed JB 4.3 ...
Question: how do I install TWRP on Android 4.3? Can it still be installed through goo manager?
Thanks!!! Not work on cmw?
+Alex Willis Just by using fastboot flash recovery openrecovery-twrp-188.8.131.52-grouper.img
+Alex Willis Either run cmd.exe (if using Windows) oder enter Terminal (if using Linux). Then type fastboot flash recovery openrecovery-twrp-184.108.40.206-grouper.img
Maybe you first have to download Android SDK from Google.
Is grouper nexus 7?
Thank you very much! Updated my Nexus 4 via Factory Image to 4.3, installed TWRP, SuperSU and BusyBox and everything runs smoothly.
Keep up the great work!
You've done it +Chainfire . was having the CPU issue with 41 version but 43 via twrp has done the job. All rooted on 4.3 here. Thank you. Nexus 4 btw.
Thanks man! Amazing job as always! Noticed it said TWRP flashable zip. Will it work with CWM as well?
Thanks, worked perfectly in my Gnex.
i have 1.41 already. will i just flash this over? no extra steps? thanks
Thanks! Android just inst the same without you..hehe
thank you so much
Thank you, all done
Thank you so much! I needed this badly since many kernels are already 4.3-updated but their control apps needed root!
thanks. i didnt have any problem with 1.41 but i flashed the update anyway. looking good so far.
Hey Chainfire or anyone, what's the best way to root? Is cf-auto root the best option?
CF-Auto-Root's have been updated!
+Chainfire so first cf-auto root, then twrp then supersu?? Do you use Odin to flash cf-auto root like on the Samsung galaxies? Sorry mate first time nexus user.
You only need to root once. If you've already rooted, you don't need to root again. So if you've used the ZIP, you don't need to use CFAR, and vice versa.
+Chainfire so the attached super su includes root, right?
Thanks, i only install this zip whit cwm. Working on nexus 7 3g
Thanks chainfire, all good here
Works great on the Galaxy Nexus, thank you so much +Chainfire
Thanks for this!! Works like a charm on my Nexus 4
Works like a charm. Thanks!
Thank you very much! !!
If I've already rooted using the 1.41 beta previously posted, can I simply update through the Play Store?
Works on my GNex now as well, epic :-)
Works as intended with the Nexus 4. Kudos to you Chainfire!
Mine shows 1.44. Is it right?
v1.44 is latest from the play store, so that's perfect.
Thanks for the new version, works perfectly.
When I tried to flash the zip TWRP said it couldn't open the zip file. Any help?
I just updated in the play store to 1.44. Does that sound right?
yes, playstore already 1.44, is it safe to update from playstore from this zip?
Yes, it is safe to update to 1.44 (at least in my N4). Here's a flashable zip of 1.44 - including a modified updater-script to ensure to also remove old apks that were installed in /data/app: https://plus.google.com/110937633080014620803/posts/795g2Jy1AX3
Sorry, but I'm unclear on the Triangle Away issue. It the issue present in the newest release? Should I just not use triangle away for now?
I have an issue, I dont know if i'm the only one that use su from command line but when I execute su it's impossible to return, e.g. with exit, the proccess get stuck. Even 'su -h' get stuck. Same behaviour for v 1.41 1.43 1.44.
EDIT: seems ok from adb shell but not from Terminal Emulator
EDIT2: the issue only occur when using a shell other than /system/bin/mksh
+David Flamand Have you tried installing the Zip that I posted here: https://plus.google.com/110937633080014620803/posts/795g2Jy1AX3 ?
So...I'd like you to make a prediction, if you have more experience with it: When my Nex7 nakasi 4.3 update eventually gets here, would I have to do anything, or do you think it'll be operational after it's done? I have the donate version, so I have engaged "protect root against OTA update" (or whatever it's called). No big deal if it DOES get crunched, I leave my bootloader unlocked, and all I'll have to do is download your update zip, boot TWRP with fastboot, and do adb sideload. But I'm just curious about what my expected experience will be.
I cant root my s3 using Android 4, 1, 2 ?
Any chance to get the .zip fot 1.44 +Chainfire ???
+Carlos Rodríguez If you don't mind that it's not packed by Chainfire..
I unzipped the 1.43 Zip from his server, removed the Apk, added the 1.44 Apk (that I pulled from my device after SuperSU was updated via Play Store), added a few lines to the updater-script to remove existing Apks in /data/app (Btw, why is this not in your updater-script, +Chainfire!?), zipped it again and signed it.
Here's the flashable Zip of 1.44: http://d-h.st/Hhw
Note: Same as usual. When installing through CWM, make sure to select "No" when CWN asks you to prevent stock recovery flash!
Titanium Backup still doesn't work for me, it doesn't even start, so I can't change the backup path as described in other comments.
It just says: Unfortunately, Titanium Backup has stopped.
In settings > developer options > show cpu usage, it used to constantly have "su" show up in v1.41. Glad to report that it's gone now in v1.43/44, likely due to the fixes to su daemon. Also not sure if placebo, some of the lag in 4.3 (quick settings, recents, etc.) have lessened and in the case of notification to quick settings, completely disappeared.
Is it possible to flash this by renaming it to update.zip in stock recovery on new Nexus 7 ? Don't have any PC to start via fastboot...
+Jeremy Piguet I don't think it's possible in the direct way. Stock recoveries require the update.zip to be signed with the platform keys that were generated with your build (someone correct me if I'm wrong here). But what you can try..
1.) Download this zip: http://d-h.st/Hhw
2.) Install this Apk: https://play.google.com/store/apps/details?id=kellinwood.zipsigner2&hl=en
3.) Open the App and use the following values: http://i.imgur.com/tO0Oygb.png
4.) Click "Sign the file"
Now you can reboot in stock recovery and you'll see if it works.
+Stephan Schmitz when I boot recovery, displays "ni command"
+Jeremy Piguet Try to hold Power and press Vol-Up a few times. (Via http://forum.xda-developers.com/showpost.php?p=34696894&postcount=1 & http://www.androidpolice.com/2013/02/12/download-the-android-4-2-2-update-jdq39-for-the-nexus-7-and-nexus-10-right-now/#comment-799598041)
If that doesn't help, the other tip that I found requires a computer again. :-( Can't imagine why, but someone reported that connecting to N7 to the PC did actually solved the "no command" issue. (http://gametipcenter.com/how-to-hard-reset-the-google-nexus-7-tablet#comment-46982)
No answers for me :/ !!!
No matter what I do, twrp won't root my gnex with 4.3. The installation goes ok, but after reboot supersu won't be there (and rootchecker shows no root is present).
can't download superSU from http://download.chainfire.eu/342/SuperSU/UPDATE-SuperSU-v1.43.zip
Any news about Titanium Backup crashing at launch?
It works with the free market version of TB but crashes with the pro version.
can i flash the zip file via gnex toolkit using the sideload option without flashing a custom recovery?
Can I root my Nexus7 4.3, without wipe /data, (I want keep my /data and setting)?
I unzip the CF-Auto-Root-grouper-nakasi-nexus7.zip, and see the root-linux.sh, it do
sudo chmod +x tools/fastboot-linux
sudo tools/fastboot-linux oem unlock
sudo tools/fastboot-linux boot image/CF-Auto-Root-grouper-nakasi-nexus7.img
when it do oem unlock, is that mean my Nexus7 will reset factory default and the /data will lose?
+John Wong I think that the bootloader unlocking will make you force wiping in order to proceed, but you can use maybe Helium to backup your data beforehand. Also save the content of /sdcard.
+Dominik Klöß, if you have set up your computer to use fastboot, yes. You can use fastboot on your computer to boot an alternate image, such as TWRP. You may need superuser permissions to access the USB port into which your device is plugged though (either Administrators group on Windows, or sudo or su access on Linux, not sure about Macs). My computer is Linux, so I use sudo; if on Windows, you might need to do something like:
runas /user:administrator cmd
provide the password for Administrator, and run your commands from the cmd window that opens.
It's been a long time since I've had to do this, so details may be fuzzy. The downside may be (here's where I do not remember well) that it may require you to unlock your bootloader:
sudo fastboot oem unlock
That, unfortunately, will wipe all your user data (the /data partition). It's possible you may be able to back up (most if not all) your data with a non-root backup program such as Helium. (I run Titanium, and that requires root, which would be a catch-22 for you.)
Assuming your bootloader needs to be unlocked and is unlocked, you can boot whatever system you'd like with something like the following (I downloaded the grouper (Nexus 7) image of TWRP):
sudo fastboot boot teamwin-recovery-grouper.img
So that means you don't have to flash Team Win to your recovery partition or anything; it just boots once.
+John Wong, yes, the fastboot oem unlock step will force a delete/reformat/wipe of your /data partition. If you don't have a backup, I might suggest Helium (formerly known as Carbon), which is a backup program not requiring root. A lot of people seem to like it; I use Titanium personally.
It just occurred to me...why is it backup app writers seem to prefer chemical element names for the name of their app?
command write failed :(
I updated to SuperSU 1.45 and after a reboot, I have lost root. No matter how many times I go into recovery and root the phone, I can't get rooted. I uninstalled 1.45 and went back to 1.43, that fixed the problem. (Nexus 4).
Doesn't work for me, SuperSU app stays stuck on loading, titanium backup waits forever during "Asking for root rights"... On Nexus 4, android 4.3