adbd Insecure updated to v2.00 - Lollipop support
Posted on 2014-11-10, 25 comments, 355 +1's, imported from Google+/Chainfire

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.

Just uploaded v2.00 to the Play store, which will start updating in a few hours. You can buy a copy there, or grab a copy from XDA here:

This update brings Android 5.0 Lollipop support, nothing more, nothing less. Enjoy!

Michael Lambert commented on 2014-11-10 at 15:42:

Good job +Chainfire

Gokul Balram commented on 2014-11-10 at 15:52:

Where would we be hadn't you been here?

Juan B commented on 2014-11-10 at 16:00:

Woo-hoo! Thanks mang. =D

Haidar Zali commented on 2014-11-10 at 16:35:

+Gokul Balram where would be what?

David Knust commented on 2014-11-10 at 17:23:

What would we do without you...

Michael Woods commented on 2014-11-10 at 18:42:

Hello Sir Chainfire I hear you are the best at what you do. Well I have a problem unlocking my t mobile note 3 to be used on another network. I was just wonder if you could help me with that. Thank you for hearing me out

Subodh Narasimhan commented on 2014-11-10 at 18:51:

Its not available in India...

Kyle Null commented on 2014-11-10 at 20:46:

+Michael Woods

I don't think Chainfire can do anything about that.  Installing SuperSU is typically only possible after the device has an unlocked bootloader, which isn't even the same as carrier unlocking.

Ādi-Kartā Dāsa commented on 2014-11-10 at 21:21:

+1'000.000 again.

Michael Woods commented on 2014-11-11 at 00:53:

Thank you I'll try that

Gokul Balram commented on 2014-11-11 at 01:19:

+Haidar Zali we*. Sorry, typo error xD

HonG W commented on 2014-11-11 at 05:15:

May I ask you a question? My note 4 sm-n910s used the CF-root to root. However, after reboot my device, the su file disappear automatically. Is it only temp. root or any wrong with my device?

praba nathan commented on 2014-11-11 at 11:39:

Chainfire i cant acesss into clash of clan after install superSU but the "X" appeard in the screen....

yassine Xman commented on 2014-11-11 at 18:33:

Fain azain

Hiku Kirika commented on 2014-11-11 at 19:39:

So if I'm on Kitkat, I must not update to v2.0?

Richard Bohannon commented on 2014-11-11 at 21:29:

+Kyle Null​ I'm on AT&T G900A S5 locked bootloader, rooted flashing custom T/W Roms utilizing SafeStrap. I have SuperSu installed. The locked bootloader just prevents me from flashing custom AOSP Roms or custom kernels. 

Fooby小贝 commented on 2014-11-12 at 00:08:

Did you can root XiaoMi2 on Android5.0?

Conor sean commented on 2014-11-12 at 04:45:

Thanks. We can not losse u.

Ta'Sean Grice commented on 2014-11-12 at 21:30:

Is the root ready for the official android L yet? I just flashed the new image and getting everything set up.

Philip Peake commented on 2014-11-12 at 23:32:

Purchased - thank you.

Hopefully won't be needed when the L update hits, but better safe than sorry.

Kylin Allen commented on 2014-11-13 at 00:28:

Root Access is not properly configured or was not granted.

Super User Application Status:

SuperSU application - version 2.01 - is installed!

System File Properties for Root Access:

Standard Location

Check Command: ls -l /system/bin/su:

Result: /system/bin/su: No such file or directory

Analysis: File /system/bin/su does not exist.

Standard Location

Check Command: ls -l /system/xbin/su:

Result: /system/xbin/su: No such file or directory

Analysis: File /system/xbin/su does not exist.

Alternative Location

Check Command: ls -l /sbin/su:

Result: /sbin/su: Permission denied

Analysis: File system permissions restricted and denied access.

Alternative Location

Check Command: ls -l /system/xbin/sudo:

Result: /system/xbin/sudo: No such file or directory

Analysis: File /system/xbin/sudo does not exist.

Root User ID and Group ID Status:

SU binary not found or not operating properly

System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin

ADB Shell Default User:

ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user -

Results provided on your Z970 - Android 4.4.2 device by Root Checker Pro version 1.3.7 from joeykrim in the Android Market -

What does this mean? I'm trying to root my zte zmax tmobile for a good week now I've tried everything...

yassine Xman commented on 2014-11-16 at 20:07:


Arif Ariyanto commented on 2014-11-23 at 03:12:

We root my phone using key root master 100% sucses.

Ahmed Lasheen commented on 2015-02-19 at 10:14:

is there a position independent executables fix for n9005

Константин С commented on 2015-05-28 at 13:14:

dos not work on 5.0.2

This post is over a month old, commenting has been disabled.