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
Related
If coming from the original JellyBean and have not updated your custom recovery since, you will need to install the recovery provided below. This step only needs to be performed once to support the newer updates.
Recovery Update
Boot into bootloader mode, connect the USB cable, and from a terminal window or command prompt type:
Code:
fastboot flash recovery recovery.img
To root an OTA, the procedure is pretty simple.
Code:
Copy the OTA from the cache folder to the sdcard.
Move the OTA zip somewhere it can be opened and unzip it
Go to system/etc/ to find the file named recovery and delete it
(extension may vary, but it is always named recovery)
Open the META-INF/com/google/android/updater-script
Delete all of step 1 and step 3 so that all that is left is the large middle portion without any steps
That's it. You have made the same files you find here.
Download the desired package below and copy it to your sdcard, along with the SuperSU recovery package.
Boot into recovery, select install from sdcard, and choose the update. Go back and repeat the install for SuperSU.
KitKat Update 98
KitKat Update 99
Lollipop Update 110
XDA:DevDB Information
Nvidia Root-Friendly Updates [No Wipe], ROM for the Nvidia Shield
Contributors
twistedumbrella
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Created 2014-11-08
Last Updated 2018-07-05
twistedumbrella said:
The new update has a few things that require updating the recovery, but since a recovery is not officially developed, updating the kernel of the existing recovery will do the trick. Flash this first.
Recovery Update
The install requires removing the assert checks since there is an error that the device is a Thor but looking for a Roth (same thing, right?). Install this from the new recovery.
KitKat Update
Immediately after installing the update, install the SuperSU recovery package to restore root and you're all set.
http://download.chainfire.eu/supersu
Click to expand...
Click to collapse
So install the first zip in your current recovery and then reboot recovery. After that, flash the next two back to back?
NapalmDawn said:
So install the first zip in your current recovery and then reboot recovery. After that, flash the next two back to back?
Click to expand...
Click to collapse
Recovery first, then the two back to back. The old recovery won't flash it properly because of new metadata commands
twistedumbrella said:
Recovery first, then the two back to back. The old recovery won't flash it properly because of new metadata commands
Click to expand...
Click to collapse
Currently my shield is 4.3, rooted and has a kernel of 3.4.10. When I boot to recovery, I get the broken android guy with the red triangle. I think if I remember right, when I was rooting it, I had issues getting a working recovery on there since mine was fairly new when I got it. So what is thebest way to install that first zip? Would I be doing it via fastboot?
NapalmDawn said:
Currently my shield is 4.3, rooted and has a kernel of 3.4.10. When I boot to recovery, I get the broken android guy with the red triangle. I think if I remember right, when I was rooting it, I had issues getting a working recovery on there since mine was fairly new when I got it. So what is thebest way to install that first zip? Would I be doing it via fastboot?
Click to expand...
Click to collapse
First off I want to say thanks umbrella, for coming up with this method.
Bit off topic but I figured I would throw it out there, when you get the broken android guy, your recovery is doing exactly what it's supposed to. It's working, dont quote me here but I think pressing home and back simultaneously will get the menu to come up. I could be wrong on the button combo but there is a combination of button's to get the stock recovery menu to come up. If I remember right my droid X was the same way.
KitKat Update Without Complete Re-root
hexitnow said:
First off I want to say thanks umbrella, for coming up with this method.
Bit off topic but I figured I would throw it out there, when you get the broken android guy, your recovery is doing exactly what it's supposed to. It's working, dont quote me here but I think pressing home and back simultaneously will get the menu to come up. I could be wrong on the button combo but there is a combination of button's to get the stock recovery menu to come up. If I remember right my droid X was the same way.
Click to expand...
Click to collapse
Quite possible. I stripped out the recovery in the update and used fastboot on recovery for this one. I rushed through it a bit lol.
If I remember right, I think it's by-name/SOS and the update uses it to install the system before flashing the recovery to the partition. I didn't update it, though, just in case that wasn't a secondary partition.
twistedumbrella said:
Quite possible. I stripped out the recovery in the update and used fastboot on recovery for this one. I rushed through it a bit lol.
If I remember right, I think it's by-name/SOS and the update uses it to install the system before flashing the recovery to the partition. I didn't update it, though, just in case that wasn't a secondary partition.
Click to expand...
Click to collapse
Ahh I gotcha. Well that's good to know. I haven't had a chance to really look at many of the files yet. Do you know if nvidia released the factory recovery packages yet?
EDIT:
Nevermind looks like 72 is out now.
Yeah, they are pretty good about that. It may be nearing the last update for this version, though
hexitnow said:
First off I want to say thanks umbrella, for coming up with this method.
Bit off topic but I figured I would throw it out there, when you get the broken android guy, your recovery is doing exactly what it's supposed to. It's working, dont quote me here but I think pressing home and back simultaneously will get the menu to come up. I could be wrong on the button combo but there is a combination of button's to get the stock recovery menu to come up. If I remember right my droid X was the same way.
Click to expand...
Click to collapse
Shield+home at the broken android guy brought up a menu.
What is the best way to install the recovery update file? Is this something that is done by booting the shield into the bootloader and then doing it via fastboot on the PC?
NapalmDawn said:
Shield+home at the broken android guy brought up a menu.
What is the best way to install the recovery update file? Is this something that is done by booting the shield into the bootloader and then doing it via fastboot on the PC?
Click to expand...
Click to collapse
Exactly
twistedumbrella said:
Exactly
Click to expand...
Click to collapse
Awesome. Thank you. Alternatively, I could accept the OTA and then push SU back to it again like I did the first time it was rooted right?
Last question-we have a working CWM recovery for the shield I believe. Are there any recoveries that work with the shield while running KitKat?
NapalmDawn said:
Awesome. Thank you. Alternatively, I could accept the OTA and then push SU back to it again like I did the first time it was rooted right?
Last question-we have a working CWM recovery for the shield I believe. Are there any recoveries that work with the shield while running KitKat?
Click to expand...
Click to collapse
The OTA will restore the stock recovery. This way updates it to one compatible with KitKat.
KitKat Update Without Complete Re-root
OTA 98 has been added. No recovery update is needed coming from 72. Flash the build and SuperSU and off you go. No data wipe necessary, either.
Link to the Recovery is not working :crying:
I am trying to install with the CWM Recovery and getting Status 7 errors, I try in stock recovery and get errors for Signature Verifications.
Neoistheone2000 said:
Link to the Recovery is not working :crying:
I am trying to install with the CWM Recovery and getting Status 7 errors, I try in stock recovery and get errors for Signature Verifications.
Click to expand...
Click to collapse
Updated
twistedumbrella said:
Updated
Click to expand...
Click to collapse
Thanks, that worked a treat
Yeah, to clarify, in recovery, you must press and hold Shield and Home buttons for a second, then release to bring up the menu. Then use X and Y to navigate, A to select. Don't understand why the bootloader or recovery don't use the D-pad at all. They're weird. Anyway, downloading this now, and will report back in a few minutes. This is just sideloaded via the stock recovery, right? I hope so, that's how I'm doing it right now.
EDIT: Nope. Failed again.
E:footer is wrong
E:signature verification failed
Installation aborted.
Click to expand...
Click to collapse
I think I'll try that new recovery (funny, because I had flashed the one included in the original update archive, still had issues). I shouldn't have to use that one, I was on update 92 already.
EDIT 2: Oh, I'm dumb. Here I thought this was still being done with the STOCK recovery. Didn't realize this would flash in CWM. Awesome. Flashed SuperSU 2.16 while I was at it. Rebooted, and it's at .98, with root access. You ROCK, @twistedumbrella!
Did you do this with update 99 yet? Just came out today.
GuyInDogSuit said:
Did you do this with update 99 yet? Just came out today.
Click to expand...
Click to collapse
I don't even have it yet. I usually wait for it to come through on the device instead of going to the site. Faster to copy than download again.
twistedumbrella said:
I don't even have it yet. I usually wait for it to come through on the device instead of going to the site. Faster to copy than download again.
Click to expand...
Click to collapse
Hmmm. It started downloading as soon as I turned mine on. I'm just gonna do the usual process.
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
I have a rooted XT1068 and there is an official OTA update to 5.0.2, should I install it? Do I lose my root access?
egwktm said:
I have a rooted XT1068 and there is an official OTA update to 5.0.2, should I install it? Do I lose my root access?
Click to expand...
Click to collapse
You have to "Full unroot" in SuperSU settings and restore the stock recovery. Otherwise OTA will fail. After the OTA is installed, You can easily return to TWRP and flash SuperSU.
okay thanks! also instead of twrp could I use chainfire again?
Unfortunately, i tried to install OTA and now every time i turn on my phone it reboots and tries to install 5.02 only to get an error and it stays at twrp menu. So what can i do now?
lol after many reboots phone decided to tell me that update was unsuccessful so it works again.
more details pls for a beginner
I made the same mistake trying to flash OTA 5.02 over rooted device 4.4.4 . I got out of the loop by moving the download zip from system/cache to external sd...
just wanting to make sure I do all the right things and in order:
so in Super SU I go the FULL UNROOT
how do I then restore stock recovery?
Once I I have restored it what are the steps for the zip and install via stock recovery?
sorry about the boring questions - it's still a bit of a jungle for a beginner
egwktm said:
okay thanks! also instead of twrp could I use chainfire again?
Click to expand...
Click to collapse
Sure. But why? Twrp is superior in every aspect. It's like deliberately crippling your toaster so that only one slice fits.
Will I be able to install ota updates with stock recovery and after unroot if I do changes to /system?
dpdp73 said:
Will I be able to install ota updates with stock recovery and after unroot if I do changes to /system?
Click to expand...
Click to collapse
No
doppelhelix said:
Sure. But why? Twrp is superior in every aspect. It's like deliberately crippling your toaster so that only one slice fits.
Click to expand...
Click to collapse
Nice imagination.
But why do I often read that TWRP will be overwritten by Lollipop with custom recovery when rebooting the phone? Some people therefore recommend the Chainfire CF-Auto-Root instead.
So after unlocking bootloader can I flash TWRP in fastboot mode and superSU afterwards without those kind of problems?
Wolfcity said:
Nice imagination.
But why do I often read that TWRP will be overwritten by Lollipop with custom recovery when rebooting the phone?
Click to expand...
Click to collapse
It's a "feature" introduced by google for their nexus. I will quote the twrp website:
The stock ROM will automatically replace TWRP with the stock recovery. To prevent the stock ROM from replacing TWRP, boot TWRP, go to the mount menu and mount system, press the home button, then press Advanced ->File Manager. Browse to /system and select the file named recovery-from-boot.p then choose to rename the file to recovery-from-boot.bak
Or you flash the SuperSU.zip. That will prevent the override too.
doppelhelix said:
It's a "feature" introduced by google for their nexus. I will quote the twrp website:
The stock ROM will automatically replace TWRP with the stock recovery. To prevent the stock ROM from replacing TWRP, boot TWRP, go to the mount menu and mount system, press the home button, then press Advanced ->File Manager. Browse to /system and select the file named recovery-from-boot.p then choose to rename the file to recovery-from-boot.bak
Or you flash the SuperSU.zip. That will prevent the override too.
Click to expand...
Click to collapse
Thx a lot for your explantion.
This was one of the things that irritated me right from the start when I was checking out the possibilities of custom recovery/root within 5.0.
I heard about the file-renaming thing but didn´t realize that superSu will do the job too and that it is a Nexus "feature" at all.
Helped me very much!
ATTENTION!
You MUST read all the guide BEFORE doing it, if you do it without reading all of it first you may ends up bricking your phone!
Prerequisites:
Asus ZE500KL (may work on ZE500KG, but haven't tested, do it on your own risk) on Marshmallow, NOT LOLLIPOP!
Also, it must have fully booted AT LEAST one time, otherwise, you'll soft-brick it.
If your phone is not on Marshmallow, you can use THIS guide insteadDownload and put the unlocker zip file and the SuperSu zip file in the phone
How To:
1 - Install adb and fastboot driver (follow THIS guide)
Now you can connect the phone to your computer2 - Reboot in fastboot mode with one of the following method:
a -Volume Up while booting upb -With adb, after enabling USB debugging in developer settings, using:
Code:
adb reboot bootloader
Now that you are in bootloader, you have to boot in TWRP,
download THIS recovery (is the twrp one) and boot in to it, using this command:
IMPORTANT: DON'T FLASH IT OR YOU WILL GET BOOTLOOP!!!
Code:
fastboot boot TWRP-x-x-x-x.img
(Obviusly the recovery name must be the one you downloaded)
IMPORTANT: DON'T FLASH IT OR YOU WILL GET BOOTLOOP!!!
It should automaticaly enter in recovery.
Now you MUST flash FIRST ZE500KL_BootloaderUnlock.zip, otherwise you'll brick your phone
Btw, the recovery will mount your phone's memory, so you can put now the files in the phone, if you forgot to do it before
AFTER you installed the unlocker zip, you can install the SuperSu zip
When the install is complete, clear the cache and reboot your phone, now you can enjoy your root!
Downloads:
Latest @MiauLightouch TWRP - 3.0.0.2 Mirror
Latest SuperSu zip - 2.65 Mirror
Bootloader Unlocker (from @MiauLightouch original post) - Mirror
Credits:
@MiauLightouch for pretty much everything
@LuK1337 , @luca020400 and everyone on #titandev for being awesome
So.. I'm thinking of buying a ZE500KL and I've been doing some reading on this phone on the forums.. did it really just get unlocked like yesterday? does that mean custom roms from now on?
MuzgontarAco said:
So.. I'm thinking of buying a ZE500KL and I've been doing some reading on this phone on the forums.. did it really just get unlocked like yesterday? does that mean custom roms from now on?
Click to expand...
Click to collapse
I would recommend Z00L/T, you will get cm13, official unlock at least.
You Say " May Work On ZE500KG" Is ze500kg already receive Marshmallow Update?
MiauLightouch said:
I would recommend Z00L/T, you will get cm13, official unlock at least.
Click to expand...
Click to collapse
thanks for the advice but my choices are poor with about 5 phones in this price range with this one looking waay better.. getting it via contract so yeah..
How to install supersu zip? Tia.
Working! Have you tried to flash Viper4Android? On lollipop this will break Call recording and FM Radio, maybe this will not be a problem on MM?
Seanjhon027 said:
How to install supersu zip? Tia.
Click to expand...
Click to collapse
Inside TWRP there is a big "Install" button, press it and select the zip
what is the meaning of booted
mohamedelkholy said:
what is the meaning of booted
Click to expand...
Click to collapse
context?
until you saw the lock screen, that's what "booted".
stuck waiting for device
C:\Users\Clynt\Desktop\Android M>adb reboot bootloader
C:\Users\Clynt\Desktop\Android M>fastboot boot twrp.img
< waiting for device >
Ok I don't know where I get wrong but I got this error.
Img file name is ok because I renamed it.
Drivers were installed already.
Developers mode is enabled already.
Windows 7 64bit
Tried rooting this using lollipop and everything went well.
thanks!
UPDATE: i got it. it has something to do with the drivers.
Without opening the bootloader.
Notice. I have not tried it.
http://www.asus-zenfone.com/2016/05/how-to-root-asus-zenfone-2-laser-ze50kl-marshmallow.html?m=1
thanl you man i have rooted my zenfone 2 laser
Thanks very much for this guide and your work.
Can I install the new update v13.10.7.1 when I opened bootloader.
The twrp recovery is temporary or permanent? If permanent how to go back to stock recovery? Tia
thanks
thks TS
now my phone its rooted
Muminek111 said:
Without opening the bootloader.
Notice. I have not tried it.
No... when trace a perequisite link Given..
you really need to unlock bootloader first
wulfe13 said:
The twrp recovery is temporary or permanent? If permanent how to go back to stock recovery? Tia
Click to expand...
Click to collapse
i think isnt permanent, this step is needed to boot into twrp then flashing a unlockBL..
to make permanent.. the command must "fastboot flash recovery twrp_X.X.X.X.img"
but make sure to unlock bootloader first...
CMIIW
Click to expand...
Click to collapse
Is it me or everytime I reboot the device after rooted, it's going back to unrooted?
Root is a success tho, great job, OP!
Edit: okay, not every reboot, but after several reboots, then it went back unrooted
Just successfully installed Supersu 2.81 (2.81 because the guide I used said it's the most stable version) when my phone rebooted the playstore promted me to update Supersu so. being the clueless noob that I am I updated it. Now it keeps failing when it's trying to update binaries. I can still use supersu and still have root access though. It's just annoying seeing that message to update binaries.
I have the same problem, I've even tried flashing the SuperSU .zip manually using TWRP! It reboots my phone before it finishes the flashing process. Does anyone know how to update it?
fajner said:
I have the same problem, I've even tried flashing the SuperSU .zip manually using TWRP! It reboots my phone before it finishes the flashing process. Does anyone know how to update it?
Click to expand...
Click to collapse
I already fixed mine.
blitzball said:
I already fixed mine.
Click to expand...
Click to collapse
How did you fix it?
fajner said:
How did you fix it?
Click to expand...
Click to collapse
Open Supersu, navigate to the settings, scroll down and do a full unroot. Your phone will reboot so make sure you activate twrp before your phone boots fully otherwise you'll have to reinstall twrp again via adb cause your phone will overwrite twrp after it boots.
Download Supersu 2.82 here (the one I have is the no additive version just root) and just flash it with twrp. Done. Easy.
https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
blitzball said:
Open Supersu, navigate to the settings, scroll down and do a full unroot. Your phone will reboot so make sure you activate twrp before your phone boots fully otherwise you'll have to reinstall twrp again via adb cause your phone will overwrite twrp after it boots.
Download Supersu 2.82 here (the one I have is the no additive version just root) and just flash it with twrp. Done. Easy.
https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
Click to expand...
Click to collapse
Sorry for late reply, I've tried uninstalling supersu/unrooting but neither did work or help. I finally ended up rebranding my phone to AL10 and installing the Chinese Oreo rom which works great.