Database Develop

[Tutorial] How To Root Nexus 5 Lollipop 5.0.1

Hi Everyone, I am Pushkar Dua just wanted to share a rooting guide for Nexus 5 Android 5.0.1
As many people Reported that Root has stopped working after the 5.0.1 Update or previous Binaries lead device to Boot Loop,
Please Download Latest Binaries That i am providing here: http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip
And flash it with TWRP recovery..
Please Use TWRP Version 2.8.1.0 as people reported some problems in latest 2.8.2.0 version.
Downlaload TWRP 2.8.1.0
Please note: if you're having a problem with twrp 2.8.1.0 asking for password..
Please use twrp 2.0.4.5
just reboot to system and you will have root access..
Watch the video for more info and Please Hit thanks or subscribe me on youtube to support me! every bit will be strongly appreciated!
Please Leave your questions BY QUOTING ME
Thanks
Thanks To @Chainfire for making this!
Original Thread for SuperSU : http://forum.xda-developers.com/showthread.php?t=1538053 Root Nexus 5 Lollipop 5.0.1

Hey!
Thanks a lot. Really helped solve my problem!

No problem

This doesn't belong in Development.

Actually i am not sure where should this be.. I'd request modders to please move it to the correct board!

Thanks man!

Delete

Since you've probably lost your custom recovery upgrading to 5.0.1, you can grab the TWRP images for Nexus 5 here: http://techerrata.com/browse/twrp2/hammerhead
I believe you need to use 2.8.1.0 since 2.8.2.0 either doesn't work or is causing problems for many users.

CF-Auto-root is still OK. I just tried

wondertx said:
CF-Auto-root is still OK. I just tried
Click to expand...
Click to collapse
Isn't CF-Auto root adding files from the 5.0 release over the 5.0.1 ? Isn't it safer to wait for a 5.0.1 autoroot?

wondertx said:
CF-Auto-root is still OK. I just tried
Click to expand...
Click to collapse
How did you update from a rooted (with CF-Auto Root) 5.0 to 5.0.1 you just received the OTA and installed it without any problems ?
I like to know because i am on 5.0 stock just rooted with CF_Auto root.

So no more need for CF-Auto?
Just flashing SuperSU zip with TWRP is enough?

I flashed a Custom Rom Using TWRP which doesn't have any root permission...

MrKaon said:
So no more need for CF-Auto?
Just flashing SuperSU zip with TWRP is enough?
Click to expand...
Click to collapse
Yes... Just Flashing with TWRP Is Enough!

Guys, i installed the 5.0.1 update by fastboot flashing system, boot and radio. I lost my custom recovery tho (CWR). I now tried to install TWRP, but after flashing the recovery image, the recovery still hasnt changed. Could i just flash CRW or should i use TWRP for this version?

Ubichinon said:
Guys, i installed the 5.0.1 update by fastboot flashing system, boot and radio. I lost my custom recovery tho (CWR). I now tried to install TWRP, but after flashing the recovery image, the recovery still hasnt changed. Could i just flash CRW or should i use TWRP for this version?
Click to expand...
Click to collapse
have you tried wugfresh's nexus toolkit to flash TWRP recovery???
maybe that works........ waiting for ur response... let me know..

pushkardua said:
have you tried wugfresh's nexus toolkit to flash TWRP recovery???
maybe that works........ waiting for ur response... let me know..
Click to expand...
Click to collapse
This. I flash with it here since 4.4.4 and it did everything just fine. Not only it is an app to automatically root, but it gives very good hints, and provides lots of others features like installing Apks, getting a adb prompt, and so much more. Greatest third party Android app I have tried. Highly recommended, didn't even had to wait they update it for 5.0.1, as soon I got the 5.0.1 OTA notification, Nexus Root Toolkit was already ready for it.

Ubichinon said:
Guys, i installed the 5.0.1 update by fastboot flashing system, boot and radio. I lost my custom recovery tho (CWR). I now tried to install TWRP, but after flashing the recovery image, the recovery still hasnt changed. Could i just flash CRW or should i use TWRP for this version?
Click to expand...
Click to collapse
This is lollipop security, custom recover wouldn't stick, after each reboot it will replaced with stock one, of course there is a way to make it sticky just search the forum.
Sent from my Nexus 5 using Tapatalk

MrKaon said:
So no more need for CF-Auto?
Just flashing SuperSU zip with TWRP is enough?
Click to expand...
Click to collapse
That's always been enough. You can use Cf's auto root if you don't want to use a custom recovery.

Molitro said:
That's always been enough. You can use Cf's auto root if you don't want to use a custom recovery.
Click to expand...
Click to collapse
I had similar discussion with Chainfire:
MrKaon said:
So guys for rooting lollipop on Nexus 5 stock all I need is flashing latest zip with TWRP?
No more need to flash modified kernel?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Chainfire said:
Initial root requires using CFAR. You can update using TWRP afterwards.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Get Root after Update to Lollipop on T-800 (WIFI)

Here is what I had to do to get ROOT on Lollipop.
-
Upgrade to Lollipop ( I did it the ODIN method but shouldn't matter if you do OTA)
- ODIN Flash CF-AutoRoot from the first thread. http://forum.xda-developers.com/show...34&postcount=1
- Let Device Reboot
- Go to Download Mode Again
- ODIN flash the latest TWRP. http://twrp.me/devices/samsunggalaxytabs105.html
- Let device reboot.
- Download latest SuperSU here and store it in your device. http://download.chainfire.eu/696/Sup...erSU-v2.46.zip
- Go into Recover by Power+Home+Volume Up.
- Instal the SuperSU zip you downloaded.
You should be good.
Took me a while to get this figured out so just sharing what i found.
If this helped please hit the thanks button.

dadanepal said:
Here is what I had to do to get ROOT on Lollipop.
-
Upgrade to Lollipop ( I did it the ODIN method but shouldn't matter if you do OTA)
- ODIN Flash CF-AutoRoot from the first thread. http://forum.xda-developers.com/show...34&postcount=1
- Let Device Reboot
- Go to Download Mode Again
- ODIN flash the latest TWRP. http://twrp.me/devices/samsunggalaxytabs105.html
- Let device reboot.
- Download latest SuperSU here and store it in your device. http://download.chainfire.eu/696/Sup...erSU-v2.46.zip
- Go into Recover by Power+Home+Volume Up.
- Instal the SuperSU zip you downloaded.
You should be good.
Took me a while to get this figured out so just sharing what i found.
If this helped please hit the thanks button.
Click to expand...
Click to collapse
I can confirm that this process does work. It's the method I went through when I upgraded my Tab S.

Tbh that is a long winded way to achieve something much easier. The Cf-autoroot step was totally unnecessary. It only does what the supersu zip does or twrp does itself.
Just flash TWRP from the first post. It will root your device with the latest binary.
http://forum.xda-developers.com/galaxy-tab-s/development/test-twrp-2-8-60-recovery-mod-t3066372

ashyx said:
Tbh that is a long winded way to achieve something much easier. The Cf-autoroot step was totally unnecessary. It only does what the supersu zip does or twrp does itself.
Just flash TWRP from the first post. It will root your device with the latest binary.
http://forum.xda-developers.com/galaxy-tab-s/development/test-twrp-2-8-60-recovery-mod-t3066372
Click to expand...
Click to collapse
Thanks for the update. Are you going to keep up with every new SU updated binaries and update TWRP every time the binaries are update. That would be great if you are willing to do that. I rather rely on the actual TWRP and SuperSU Developers to give me the zips etc. and flash my self as long winded as that may seem but people can choose.

Twrp is updated more often than the super su binary, but team win never seem to update the binary, so I'll just update it myself with each release. Not only that, each new twrp release has the same problems as mentioned in my original post.
I'm also looking for a way to get MTP working properly as that is the only issue now.
Regarding cf-autoroot. I don't think people realise there is nothing special about how it roots.
It basically does the same thing that twrp does itself or flashing a super su zip.
Cf-autoroot simply installs a modified stock recovery which runs a script to Install root then flashes back stock recovery.
If someone intends to install a custom recovery anyway then there is no point in running cf-autoroot.
Twrp will do exactly the same thing and so does installing a super su zip.
They all accomplish the same thing using a slightly different method.
The only difference will be that chainfire may keep each cf-autroot updated with the latest binary.
The reason chainfire created it is for people who want to stick with stock recovery instead of custom

ashyx said:
Twrp is updated more often than the super su binary, but team win never seem to update the binary, so I'll just update it myself with each release. Not only that, each new twrp release has the same problems as mentioned in my original post.
I'm also looking for a way to get MTP working properly as that is the only issue n
So i tried the auto root no luck, what mode do i flash twrp in odin?
Click to expand...
Click to collapse

deno24 said:
ashyx said:
Twrp is updated more often than the super su binary, but team win never seem to update the binary, so I'll just update it myself with each release. Not only that, each new twrp release has the same problems as mentioned in my original post.
I'm also looking for a way to get MTP working properly as that is the only issue n
So i tried the auto root no luck, what mode do i flash twrp in odin?
Click to expand...
Click to collapse
Mode? Just load it and flash it.
Click to expand...
Click to collapse

ashyx said:
deno24 said:
Mode? Just load it and flash it.
Click to expand...
Click to collapse
yeah in AP mode?
im trying to root this
Click to expand...
Click to collapse

deno24 said:
ashyx said:
yeah in AP mode?
im trying to root this
Click to expand...
Click to collapse
That's the one.
Click to expand...
Click to collapse

ashyx said:
deno24 said:
That's the one.
Click to expand...
Click to collapse
cool so i flash twrp and ill have root? been a cpl oif years since ive done this last root was note2
Click to expand...
Click to collapse

Just flash twrp, boot into it then hit reboot. Twrp will give you the option to root.
If doesn't then you are already rooted and probably just need to update the super su app.

ashyx said:
Just flash twrp, boot into it then hit reboot. Twrp will give you the option to root.
If doesn't then you are already rooted and probably just need to update the super su app.
Click to expand...
Click to collapse
I did that and I can't boot into twrp, samsung recovery is shown. Looks like it can't rewrite the original recovery. Used your version from 30th March with Odin 10.6.
Thanks

d3xtr0 said:
I did that and I can't boot into twrp, samsung recovery is shown. Looks like it can't rewrite the original recovery. Used your version from 30th March with Odin 10.6.
Thanks
Click to expand...
Click to collapse
That's a feature of lollipop. It overwrites with stock recovery. Happens on many devices. You need to boot into recovery immediately after flashing twrp, twrp will then patch it so stock recovery can't replace it.
When flashing uncheck auto reboot in odin. When it finishes flashing hold power + vol down + home. As soon as the screen goes blank hold power +vol up + home to boot into recovery.

Thanks for the information, but now I've flashed your new package root+twrp and it's working great
Thanks again.
Sent from my MI 4W

Whith this method, what is the knox value?

Knox is one ( .. )
Newer thread opened yesterday.
Edit:
http://forum.xda-developers.com/showthread.php?t=3079488
[ROOT][RECOVERY] [ALL IN ONE] Cf-Autoroot-twrp-T800-T805 [Tab S 10.5 ]
Sent from my MI 4W

Help rooting 5.1.1 925T

I installed 5.1.1 via smart switch and lost root. I enabled allow OEM unlock and tried the CF autoroot technique. It flashed fine but it gets stuck on the Galaxy S6 splash screen with the message "bootloader is not SEandroid enforcing" (duh....) I found another thread that said to try the 920t cf autoroot which I did and it had the same result. I have since recovered my phone back to stock 5.1.1 but I would really like to join the club and get root working once again. Is there a current solution for this or is it just a waiting game now?
thanks for any help.

If you are on stock 5.1.1 all you have to do now is either flash the 5.1.1 unikernel (in unified development section) or flash the rooted stock debloated rom posted in the Looper thread. If that was confusing just let me know lol I'll try to help you locate

Odin flash the new 2.8.7.1 TWRP and you'll be all set.

guyd said:
Odin flash the new 2.8.7.1 TWRP and you'll be all set.
Click to expand...
Click to collapse
Does this and or the kernel go into the PA box? PA is what used to be labeled PDA correct?

guyd said:
Odin flash the new 2.8.7.1 TWRP and you'll be all set.
Click to expand...
Click to collapse
Odin flashing just twrp does not root
the phone. If you do it that way, and don't flash the rooted kernel before booting, you will boot and stock recovery will replace twrp
badtoy1986 said:
Does this and or the kernel go into the PA box? PA is what used to be labeled PDA correct?
Click to expand...
Click to collapse

So, flash TWRP then flash the kernel with TWRP?

badtoy1986 said:
So, flash TWRP then flash the kernel with TWRP?
Click to expand...
Click to collapse
Correct. First make sure you're on 5.1.1 already. Then flash twrp in odin. Then immediately boot into twrp and flash the unified kernel for 5.1.1

Nexus 6 mmra58n 6.0: Troubling With Rooting

Nexus Root problem. Marshmallow android 6.0 mmra58n
I just have tried everything.
I have a Nexus 6 with marshmallow, and I follow this thread guide http://forum.xda-developers.com/nex...mallow-6-0-t3241976/post64008696#post64008696 to root my phone, but everything goes wrong.
I flash the boot.img and there's no problem at the boot time, then I flash the recovery, and the same, when i reboot it works like a charm.
But everything goes wrong when i flash with twrp the supersu beta v2.52 or v2.56, when i reboot, it doesn't boot...
My phone continue on the first bootanimation (before flash this file it boot then says android, request my pincode and start booting, but no this time, just still doing the [email protected] bootanimation. I am kind of desperate, can somebody help me plz?
DONE, I re-flash system and do it again, thanks for everyone

dont use supersu 2.52, use supersu 2.51 instead http://www.apkmirror.com/apk/chainfire/supersu/supersu-2-51-android-apk-download/

I just flash then the 2.51 with twrp?

Fabiano91 said:
I just flash then the 2.51 with twrp?
Click to expand...
Click to collapse
yes. but you will need that boot.img or any other custom marshmallow kernel as well for root. btw, a boot.img is a kernel. also, you can flash boot.imgs with twrp now too, you just have to select the ability to flash it in twrp.

simms22 said:
yes. but you will need that boot.img or any other custom marshmallow kernel as well for root. btw, a boot.img is a kernel. also, you can flash boot.imgs with twrp now too, you just have to select the ability to flash it in twrp.
Click to expand...
Click to collapse
Ok dude, I will do it now, five minutes more and i write the update here. thanks!!!
It didn't work! I'm stuck!

How to root z3+ nougat version

Please help me

Download the latest Superuser Zip and flash it using TWRP Recovery (Unlocked bootloader is required for rooting)

[email protected] said:
Download the latest Superuser Zip and flash it using TWRP Recovery (Unlocked bootloader is required for rooting)
Click to expand...
Click to collapse
Is there any way to flash it via flashtool?
My bootloader is unlocked.

Holydao said:
Is there any way to flash it via flashtool?
My bootloader is unlocked.
Click to expand...
Click to collapse
I dont know the other way.
If you already unlocked the bootloader, flash TWRP Recovery using Fast Boot Command and then flash SU Zip using TWRP.

[email protected] said:
I dont know the other way.
If you already unlocked the bootloader, flash TWRP Recovery using Fast Boot Command and then flash SU Zip using TWRP.
Click to expand...
Click to collapse
Thank you very much, I''ll try asap.

[email protected] said:
I dont know the other way.
If you already unlocked the bootloader, flash TWRP Recovery using Fast Boot Command and then flash SU Zip using TWRP.
Click to expand...
Click to collapse
Which version of TWRP should I use for Z3+ (E6553) on nougat (32.3.A.0.372_R3D_Customized RU_1295-0592)?

Holydao said:
Which version of TWRP should I use for Z3+ (E6553) on nougat (32.3.A.0.372_R3D_Customized RU_1295-0592)?
Click to expand...
Click to collapse
Check this step by step guide: https://forum.xda-developers.com/xperia-z4/general/guide-safe-bootloader-unlock-restore-t3386915

[email protected] said:
Check this step by step guide: https://forum.xda-developers.com/xperia-z4/general/guide-safe-bootloader-unlock-restore-t3386915
Click to expand...
Click to collapse
I don't know why but I just couldn't make it, I got soft brick everytime and I flashed to "32.3.A.0.372_R3D_Customized RU" for hundred times. I quit trying that.
Now I'm trying to root my E6553 (on 32.2.A.0.224), stiil couldn't make it either. It stucks on SONY logo or endless boot loop. I just want to root it for once, not to flash twrp but to boot on twrp and flash SU. Isn't that what we call "root"? Am I wrong?
My device bootloader is unlocked, on stock MM rom "32.2.A.0.224". I just want to boot it on TWRP and flash SU, that's all. Isn't that enough for rooting? After that I want to use some apps that only works on rooted devices.
Anyway, thank you for your help, I really apreciate that but I still need help more than ever, each post that I followed to root my device ended in a bad way.
I have essential drivers, my bootloader is unlocked. What is wrong with my device? I tried lots of boot.img's, recovery.img and twrp1.img's but nothing changed...

Holydao said:
I don't know why but I just couldn't make it, I got soft brick everytime and I flashed to "32.3.A.0.372_R3D_Customized RU" for hundred times. I quit trying that.
Now I'm trying to root my E6553 (on 32.2.A.0.224), stiil couldn't make it either. It stucks on SONY logo or endless boot loop. I just want to root it for once, not to flash twrp but to boot on twrp and flash SU. Isn't that what we call "root"? Am I wrong?
My device bootloader is unlocked, on stock MM rom "32.2.A.0.224". I just want to boot it on TWRP and flash SU, that's all. Isn't that enough for rooting? After that I want to use some apps that only works on rooted devices.
Anyway, thank you for your help, I really apreciate that but I still need help more than ever, each post that I followed to root my device ended in a bad way.
I have essential drivers, my bootloader is unlocked. What is wrong with my device? I tried lots of boot.img's, recovery.img and twrp1.img's but nothing changed...
Click to expand...
Click to collapse
Sorry bro, forgot to tell you that you also need a patched stock kernel (with DM Variety & Sony RIC disabled and DRM fixed). After that only you can flash SU Zip. Else it will be boot looped. Check guide link for making patched kernel of you choice of version with one little tool. You can also flash custom Kernel like Zach Kernel, Andro Plus Kernel... etc instead of patched stock kernel to avoid bootloop after SU flash.
AND MY XPERIA OPTION TO BE TURNED OFF else also will in boot loop.
Now the steps are as follows:
Flash Stock ROM
Flash patched kernel
Flash TWRP Recovery
Flash SU Zip
That's it
More info Patched Kernel and DM Variety & Sony RIC disabled and DRM fixed: LINK

I did it at last
One of the kernels didn't create a bootloop after I tried aprox. 128 times and after that SU was flashed. Now I have substratum on MM, thanks again
E6553 cihazımdan Tapatalk kullanılarak gönderildi

Holydao said:
I did it at last
One of the kernels didn't create a bootloop after I tried aprox. 128 times and after that SU was flashed. Now I have substratum on MM, thanks again
E6553 cihazımdan Tapatalk kullanılarak gönderildi
Click to expand...
Click to collapse
Ohhhhh... Great...
But tried 128 times??? OMG... You have to spend some time on reading all TECH and FAQ posts before attempting the 3rd atleast bro.... :laugh::good:

I spent my whole time after work and slept at 3 am for 4 days, spent aprox 30 hours... I read every discussion about root 5 times on forum. ?
Why is it so hard to find a proper kernel to root?
E6553 cihazımdan Tapatalk kullanılarak gönderildi