Develop Bugs

[Q] root without adb

is it possible to root this phone without using adb?

nighthawk626 said:
is it possible to root this phone without using adb?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=805010
You can try this, I personally did it with adb so I honestly have no idea how well it works. Hell I'm I can't even say it works for sure.
Well good luck

xaodxkevin said:
http://forum.xda-developers.com/showthread.php?t=805010
You can try this, I personally did it with adb so I honestly have no idea how well it works. Hell I'm I can't even say it works for sure.
Well good luck
Click to expand...
Click to collapse
You obviously did not read through that thread, it was shown to not work. That root method doesn't involve the flashing of the engineering bootloader, which is required to be able to flash self signed update packages in recovery, such as clockwork recovery. People ran into errors because they couldn't flash clockwork. They also couldn't flash the engineering build because they were not rooted.
So, in short, to the OP, no, you cannot root without ADB. You CAN download an app that will give you temporary root, but that will only allow you to use applications that require root, it won't allow you to actually flash a custom ROM. For that you need to follow nbetcher's root method, which is in the android dev section, it's a fairly obvious thread in capital letters near the top

[Q] Unrooting with a broken USB connector

My USB connector is broken on my nexus. Amazon has sent me a replacement, which I have at hand. I would like to lock my boot loader on my nexus with the broken USB connector before sending it back to amazon.
Any thoughts as to how I may accomplish this?
If not, can you at the least convince me amazon won't care that my boot loader is unlocked?

EDIT: Never mind, it seems the awesome developers have figured out ways to relock the bootloader.

https://play.google.com/store/apps/details?id=aperture.ezekeel.gladoscontrol
Potentially.
MAYBE.
Just Maybe you can re-lock with this.
I'm not sure if it requires SU or not.
And I haven't given anyone this advice yet, so you'll be the first.
But as the above poster said...
Mobile Odin first.

mt6272 said:
My USB connector is broken on my nexus. Amazon has sent me a replacement, which I have at hand. I would like to lock my boot loader on my nexus with the broken USB connector before sending it back to amazon.
Any thoughts as to how I may accomplish this?
If not, can you at the least convince me amazon won't care that my boot loader is unlocked?
Click to expand...
Click to collapse
Not sure if Amazon will even care if it is locked or not.
Thanks to AdamOutler and a few others, you can re-lock the bootloader without being plugging into a computer, but root (and busybox) is required.
Download the attachment from this post, and extract the files to the root of /sdcard. Then open a terminal emulator on your device and type the following commands:
su
dd if=/sdcard/param.lock of=dev/block/platform/omap/omap_hsmmc.0/by-name/param
That should re-lock your bootloader.
Now you need to make sure you are running a stock ROM and stock recovery.
Once that is done, you can then remove busybox, and finally, you can delete /system/app/Superuser.apk and su.
EDIT: For those that are curious, to unlock your bootloader without wiping, replace the command above with this:
su
dd if=/sdcard/param.unlock of=dev/block/platform/omap/omap_hsmmc.0/by-name/param

efrant said:
Not sure if Amazon will even care if it is locked or not.
Thanks to AdamOutler and a few others, you can re-lock the bootloader without being plugging into a computer, but root (and busybox) is required.
Download the attachment from this post, and extract the files to the root of /sdcard. Then open a terminal emulator on your device and type the following commands:
su
dd if=/sdcard/param.lock of=dev/block/platform/omap/omap_hsmmc.0/by-name/param
That should re-lock your bootloader.
Now you need to make sure you are running a stock ROM and stock recovery.
Once that is done, you can then remove busybox, and finally, you can delete /system/app/Superuser.apk and su.
Click to expand...
Click to collapse
Awesome efrant, thank you.
I'll reference to this later if need be.

efrant said:
Not sure if Amazon will even care if it is locked or not.
Thanks to AdamOutler and a few others, you can re-lock the bootloader without being plugging into a computer, but root (and busybox) is required.
Download the attachment from this post, and extract the files to the root of /sdcard. Then open a terminal emulator on your device and type the following commands:
su
dd if=/sdcard/param.lock of=dev/block/platform/omap/omap_hsmmc.0/by-name/param
That should re-lock your bootloader.
Now you need to make sure you are running a stock ROM and stock recovery.
Once that is done, you can then remove busybox, and finally, you can delete /system/app/Superuser.apk and su.
Click to expand...
Click to collapse
couldnt you take it a step further?
doesnt mobile odin work properly even if the bootloader is locked?

Zepius said:
couldnt you take it a step further?
doesnt mobile odin work properly even if the bootloader is locked?
Click to expand...
Click to collapse
Yeah, he could use mobile odin to flash to stock (and thus, no need to remove custom recovery, root, etc.), but mobile odin will not re-lock his bootloader.

efrant said:
Yeah, he could use mobile odin to flash to stock (and thus, no need to remove custom recovery, root, etc.), but mobile odin will not re-lock his bootloader.
Click to expand...
Click to collapse
ah i figured you could still use mobile odin to restore to stock with the bootloader already locked when you first run it.
ive never used it so i guess i didnt understand completely what it did.

Zepius said:
ah i figured you could still use mobile odin to restore to stock with the bootloader already locked when you first run it.
ive never used it so i guess i didnt understand completely what it did.
Click to expand...
Click to collapse
No, you're right. You CAN use mobile odin with a bootloader already locked. However, you need root to use it.

efrant said:
No, you're right. You CAN use mobile odin with a bootloader already locked. However, you need root to use it.
Click to expand...
Click to collapse
so you could then change the param file, which locks the bootloader, then use mobile odin to go back to 100% stock and still have a locked bootloader.

Zepius said:
so you could then change the param file, which locks the bootloader, then use mobile odin to go back to 100% stock and still have a locked bootloader.
Click to expand...
Click to collapse
Yes. That's what I was trying to say in my earlier post, but I guess it wasn't clear. Mobile Odin will not change the lock state of the bootloader, but will work in either a locked state or an unlocked state, assuming you have root.

More details on my phone: It is rooted, running aokp m5 & franco m3. It sounds like there is a solution to my problem contained within this thread - however, things are a bit hazy to me when it comes to what order to perform these operations and which apps to use when.
My thanks to the first person who compiles a step-by-step (albeit brief and concise) guide to unrooting, re-locking the bootloader, and restoring to stock WITHOUT being connected to the computer!

I don't know how you have broken USB, but my friend had it broken - it didn't want to charge longer than few seconds, connection to PC was extremely inconsistent...
Samsung told him that it happens on SGNs sometimes and that it is caused by oxidation of USB. It isn't covered by warranty.
But he solved it very simply - you can clean the USB by soft toothbrush and it works like a charm again. Hope this helps you.

mt6272 said:
More details on my phone: It is rooted, running aokp m5 & franco m3. It sounds like there is a solution to my problem contained within this thread - however, things are a bit hazy to me when it comes to what order to perform these operations and which apps to use when.
My thanks to the first person who compiles a step-by-step (albeit brief and concise) guide to unrooting, re-locking the bootloader, and restoring to stock WITHOUT being connected to the computer!
Click to expand...
Click to collapse
It is not that difficult, and I'm sure you do not need a step by step.
I haven't tried this on my device, as I don't really feel like wiping, but:
1) Lock your bootloader as per my post above. EDIT: I just looked at Mobile Odin, and it seems that Chainfire has implemented flashing the param partition as well in his app, so you can skip this step and go straight to step two.
2) Download the param file from the same post mentioned in step 1, and extract it to the root of your /sdcard.
3) Rename the param.lock file to param.img
4) Download version of the stock ROM for your device from here, e.g., if you have a GSM device, download the maguro factory image, if you have a Verizon device, download the toro factory image.
5) Extract the system, boot, userdata and recovery images from within and place them on the root of your /sdcard.
6) Buy Mobile Odin Pro from the Play Store. [You can use get the free version from the XDA thread here, but it needs setting up, and I'm not going to guide you through that.]
7) Run Mobile Odin Pro and follow the instructions here. It should be pretty obvious what you need to do.

I'm running AOKP 4.2, their latest release. I, too, have a failed USB connection. I downloaded the latest recovery from the link for my Verizon Toro. When I used the paid version of Mobile Odin, it says "partition could not be found in file". I tried the older, ICS image, but it just factory reset my AOKP install, not reflash to stock. So far, I've locked the boot loader, but I can't get rid of AOKP. I think it is because Mobile Odin doesn't reflash the bootloader, which I learned after my attempt, and I attempted to Odin back to factory ICS, which is a different bootloader. My other thought was to get into TWRP and flash an older AOKP ICS build, which flashes the older bootloader(right??), and try again, but I have no recovery, stock or otherwise after my Mobile Odin attempt. Any advice at this point? Should I just send it to Verizon as-is and let the chips fall where they may?

Quick update: I used Goomanager from the market to instantly flash TWRP. BAM! Recovery restored! I just finished flashing AOKP Jellybean Milestone 1, which is 4.1.2. I also figured out my JRO030 issue. It was a bad .tar file. When I browsed it with Winrar, it containted another file with the same name and no extension. I found another .tar file with the entire file structure inside. I'm currently booting into AOKP M1 as I type. I'll attempt to Mobile Odin with the JRO030 factory image (4.1.1) over 4.1.2 and then update this thread again. I hope I can save others some heartache.

The JRO030 update said something about "unable to extract update script". So I gave up on Jelly Bean and went futher back. I found an old AOKP ICS build, Milestone 6, flashed to that and used the monster 470 mb 4.0.2 update file that was linked to in a galaxynexusforums post with Mobile Odin. TADA! It worked like a charm. No root. Stock software. The only downside is that recovery is broken. It shows an Android guy with a red exclamation point over his belly. Whatever. I'm on 4.0.2 stock VZW software. That's all I care about. Let me know if anyone needs help with this.

scubamike said:
Snip
The only downside is that recovery is broken. It shows an Android guy with a red exclamation point over his belly. Whatever. I'm on 4.0.2 stock VZW software. That's all I care about. Let me know if anyone needs help with this.
Click to expand...
Click to collapse
That IS the stock recovery.
Sent from my Nexus 4 using Tapatalk 2

efrant said:
That IS the stock recovery.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I thought it was too, but, just for the heck of it, I tried taking the OTA. It rebooted and stuck on the android guy with the red exclamation. I had to pull the battery.

It is the stock recovery and no, you did not have to pull the battery. The Android with the red triangle is the main screen of the stock recovery . To access the menu from the main screen, hold power and press volume up. This is covered in at least 2 of the stickies in the General section.
Sent from my Nexus 4 using Tapatalk 2

[Q] Flash bootics.img on Xperia Play

Start by saying I'm very new about Android and smartphone in general.
Four days ago I got my first smartphone, a Xperia Play model R800i and some friends suggested me to install ICS. I searched on the internet and I have found the Xperia Play Development forum. There, I found a really interesting ROM called "New Express ICS".
I downloaded all the files and I started to follow the guide. I'm stuck at the second point (I believe this is ridiculous): I can't get into the Recovery Mode and I didn't get if I can flash the custom kernel (bootics.img) on flash tool.
I haven't rooted my phone, it's 100% virgin, yet.
Can someone explain me what to do? I'm searching answer here and on google for three days and I'm getting even more confused.
Sorry if my english is not perfect, it isn't my first language.

You need to unlock bootloader before fastboot a kernel (bootics.img)
WARNING: THIS VOIDS WARRANTY. YOU HAVE BEEN WARNED.

jeff7424 said:
You need to unlock bootloader before fastboot a kernel (bootics.img)
WARNING: THIS VOIDS WARRANTY. YOU HAVE BEEN WARNED.
Click to expand...
Click to collapse
Thank you very much, I'm going to do this. Is this a good guide?
After that what I have to do? How I will flash the rom? Sorry for all these newbie questions.

You should read all his guides.
http://forum.xda-developers.com/showthread.php?t=1836530
First read root, then unlock bootloader, then install custom roms.
Sent from my R800i

eksasol said:
You should read all his guides.
http://forum.xda-developers.com/showthread.php?t=1836530
First read root, then unlock bootloader, then install custom roms.
Sent from my R800i
Click to expand...
Click to collapse
Thanks for the link, it's very useful! Just a question: what do you mean with "read the root"? I have to root the phone?

I rooted my phone and I found the superuser app on this. Then, I unlocked the bootloader and the superuser app disappered, is it normal?
One more thing, how I flash the custom kernel and the ROM, now?
EDIT: Fail, Superuser is installed, yet, I didn't notice that
EDIT2: Why I can't get into the recovery mode?

unlock bootloader here http://www.xperiagamer.com/Beginners-Guides/unlock-the-bootloader-ramge.html
im not responsible for any damage:good:

Gianmark said:
I rooted my phone and I found the superuser app on this. Then, I unlocked the bootloader and the superuser app disappered, is it normal?
One more thing, how I flash the custom kernel and the ROM, now?
EDIT: Fail, Superuser is installed, yet, I didn't notice that
EDIT2: Why I can't get into the recovery mode?
Click to expand...
Click to collapse
I see you unlock your bootloader, good job! Place the ROM zip into your SD card first. Next, to get into recovery mode, just fastboot the kernel you want.
-Power off phone.
-Hold search button while connecting to PC via USB
-Open flashtool, click the thunderbolt icon, select fastboot
-Select kernel to flash (select your kernel bootics.img)
-Wait for 2 seconds and voila!
After that, power on your phone, when blue LED lights up with a vibration, spam volume button / back button (depends on kernel) then you'll be able to enter recovery

Gianmark said:
One more thing, how I flash the custom kernel and the ROM, now?
EDIT: Fail, Superuser is installed, yet, I didn't notice that
EDIT2: Why I can't get into the recovery mode?
Click to expand...
Click to collapse
Again, read his guide on flashing kernel and roms: http://forum.xda-developers.com/showthread.php?t=2054512
Which kernel you flash is depended on the rom you want to use it with, you need to flash a GB kernel if you want to use GB rom, ICS kernel for ICS, etc, although some kernel are compatible with both ICS and JB. Search the development section for kernels and roms. If you flash a rom and it fail to boot, it mean the kernel currently installed is not compatible with that rom.
About ClockworkMod Recovery:
If you flash a custom kernel, it will likely have ClockworkMod Recovery included. Or if you are using stock Sony firmware, use the "CWM installer version 5" from this link to install CWM. Sometimes you will get a status 7 error when you try flashing a rom, it might mean you have to use a different version of ClockworkMod to flash that rom successfully.

First of all, thank you both!
Can I flash bootics.img in the Flashtool? The fma965's tutorial speaks about a "*.zip" file besides a "*.img" file.
Also, he says to use fastboot package that I have already used to unlock the bootloader.
EDIT: I need Busybox? What is it? I didn't get it.

Gianmark said:
First of all, thank you both!
Can I flash bootics.img in the Flashtool? The fma965's tutorial speaks about a "*.zip" file besides a "*.img" file.
Also, he says to use fastboot package that I have already used to unlock the bootloader.
Click to expand...
Click to collapse
Flash boot.img in Flashtool/Fastboot as instructions above from jeff7424:good:Zip files are what you put on your sd card and flash with cwm recovery, these can be either roms, updates to roms,zip files to change appearance, performance tweaks, too many to mention.
So .img and .ftf files use in Flashtool/Fastboot and zip files use on SD card to flash with CWM recovery.
Not to complicate it too much sometimes the boot.img comes in a .zip file you need to extract this to use in flashtool/fastboot with winra/7z unzip programs
Edit; Busybox download it with Superuser app on your phone or download a app from store to update your busybox
What is it?http://en.wikipedia.org/wiki/BusyBox

But I don't need busybox to flash kernel and ROM, right?

You can get busybox from Play Store, just search Busybox installer, install it, open the app and install busybox.

jeff7424 said:
You can get busybox from Play Store, just search Busybox installer, install it, open the app and install busybox.
Click to expand...
Click to collapse
I didn't get if I need it to flash kernel and ROM.

Root your phone with zergrush, that will give you busybox too.

jeff7424 said:
Root your phone with zergrush, that will give you busybox too.
Click to expand...
Click to collapse
http://puu.sh/1VV8Q
In that case, I've already installed it.
EDIT: What I have to click? http://puu.sh/1VVgK
"Select Kernel to flash"?
EDIT2: I don't need a custom firmware?

Yeah select kernel to flash. Nope you just need an unlocked bootloader.

I DID IT.
But I'm a bit disappointed because Crash Bandicoot disappered...
Thanks everyone, by the way.
For the future update, the phone will format again?

WARNING: Do not use SEUS to update or repair your phone since you have an unlocked bootloader, if not you'll brick your phone.

jeff7424 said:
WARNING: Do not use SEUS to update or repair your phone since you have an unlocked bootloader, if not you'll brick your phone.
Click to expand...
Click to collapse
SEUS?

[Q] Keeping Root with OTA Update

As far as I know, there is no way to keep root if you get the OTA 4.3 update, right? I want to just get the OTA and not deal with the roms. Unlocked bootloader here...
According to Voodoo OTA Rootkeeper, it doesn't work with the 4.3 update: http://forum.xda-developers.com/showthread.php?t=1241517&page=6
That's a true bummer.

Gbcue said:
As far as I know, there is no way to keep root if you get the OTA 4.3 update, right? I want to just get the OTA and not deal with the roms. Unlocked bootloader here...
According to Voodoo OTA Rootkeeper, it doesn't work with the 4.3 update: http://forum.xda-developers.com/showthread.php?t=1241517&page=6
That's a true bummer.
Click to expand...
Click to collapse
If your bootloader is unlocked then it's easy... you just flash SuperSU in recovery after the update. No ROMs to deal with. On a Nexus device with an unlocked bootloader root is never an issue.

phazerorg said:
If your bootloader is unlocked then it's easy... you just flash SuperSU in recovery after the update. No ROMs to deal with. On a Nexus device with an unlocked bootloader root is never an issue.
Click to expand...
Click to collapse
Even with stock recovery this is possible? I don't want to re-root and lose data.

Gbcue said:
Even with stock recovery this is possible? I don't want to re-root and lose data.
Click to expand...
Click to collapse
Not with stock recovery. But if you have an unlocked bootloader it's still no problem. You can boot to a custom recovery without even having to actually flash it if you want to keep stock recovery. So you just let the OTA install as normal then use fastboot to boot CWM or TWRP and flash SuperSU and you're done and rooted.
If your bootloader is unlocked, you might as well take advantage of it even if you want to remain mostly stock

Just keep in mind that SuperSU runs a daemon all the time can result in 70% cpu usage peaks. Don't blame 4.3 for it.

madd0g said:
Just keep in mind that SuperSU runs a daemon all the time can result in 70% cpu usage peaks. Don't blame 4.3 for it.
Click to expand...
Click to collapse
Do we have any idea what triggers that? Thankfully I haven't had that experience and haven't had any extra CPU usage before or after flashing 4.3 yesterday.

phazerorg said:
Do we have any idea what triggers that? Thankfully I haven't had that experience and haven't had any extra CPU usage before or after flashing 4.3 yesterday.
Click to expand...
Click to collapse
No, it seems fairly random so far. I have seen it once but can not reproduce it.
Chainfire is working on the issue though.

Questions in the Q&A, this is the general forum..
Read the rules sticky..
Beamed from my Maguro.

GldRush98 said:
No, it seems fairly random so far. I have seen it once but can not reproduce it.
Chainfire is working on the issue though.
Click to expand...
Click to collapse
SuperSU 1.43 update

add3421 said:
So is there a like guide on how to keep root when doing a system update? I have STOCK 4.2 Rooted and it is saying I should download an update. I do have TWRP installed. Is there another stock already rooted 4.3 I can download? Any help would be great so I dont have to factory reset.
Thanks!
Click to expand...
Click to collapse
Why even bother with this crap, flash the update, boot, flash custom recovery after and flash new SuperSU. You would be done before even typing this post.

I used the Nexus Root Toolkit by WugFresh to root my Galaxy Nexus on 4.3, and didn't lose any data...

All I did as usual was:-
1) Flash the update
2) Boot into TeamWin recovery (I keep the stock recovery installed)
3) Flash SuperSU 1.43
Simple, no issues.

If I have CMW Touch recovery can I install the OTA? I have received the notification but I don't know if I will be able to install it. Is there any way to revert back to Google's recovery just like installing a custom recovery? I mean not loosing data or having to so a factory reset.
Enviado desde mi Galaxy Nexus

str355 said:
All I did as usual was:-
1) Flash the update
2) Boot into TeamWin recovery (I keep the stock recovery installed)
3) Flash SuperSU 1.43
Simple, no issues.
Click to expand...
Click to collapse
How do you boot into twrp without flashing it? I know "fastboot flash recovery twrp.img" permanently overrides the built in recovery, but how would you boot into it just once?

AMKhatri said:
I used the Nexus Root Toolkit by WugFresh to root my Galaxy Nexus on 4.3, and didn't lose any data...
Click to expand...
Click to collapse
Which version of the toolkit?

krackers said:
How do you boot into twrp without flashing it? I know "fastboot flash recovery twrp.img" permanently overrides the built in recovery, but how would you boot into it just once?
Click to expand...
Click to collapse
This is the command you want "fastboot boot twrp.img"
---------- Post added at 08:45 PM ---------- Previous post was at 08:41 PM ----------
add3421 said:
ok cool, do you happen to have a link to the exact update i can download? for some reason when i click install it says restarting now.. but never does.
Click to expand...
Click to collapse
I used the link in this thread --> http://forum.xda-developers.com/showthread.php?t=2377390
SuperSU.zip from here (v1.45 now) --> http://forum.xda-developers.com/showthread.php?t=1538053

Gbcue said:
Which version of the toolkit?
Click to expand...
Click to collapse
1.6.4 after running update.
FWIW: Even though I've successfully used this kit a dozen times on four different devices, root was not working correctly (no su binary found) for me so I had to load the app via twrp which did correctly load from the toolkit after the kit installed 4.3.

Gbcue said:
Which version of the toolkit?
Click to expand...
Click to collapse
1.6.4 and it worked perfectly for me

[Q] [IMPORTANT] Is there any way I can root htc one m8 Lolipop 5.0?

Someone if you know and tested it, can I root my htc one m8 device having the new firmware updated 5.0.1 lolipop??
Please anwser and if there is a way please send a link
THANKS A LOTTT!!

It's exactly the same as before.
Look for how do I root here,
http://forum.xda-developers.com/showthread.php?t=2711073
You unlock bootloader. Flash a custom recovery... I suggest twrp. It will ask you when you exit if you want to root. Say yes.
Boot into android, install supersu if it or superuser aren't there already. (from play store)
Or just flash recovery . Install a rom , likely rooted already.
?

Darth said:
It's exactly the same as before.
Look for how do I root here,
http://forum.xda-developers.com/showthread.php?t=2711073
You unlock bootloader. Flash a custom recovery... I suggest twrp. It will ask you when you exit if you want to root. Say yes.
Boot into android, install supersu if it or superuser aren't there already. (from play store)
Or just flash recovery . Install a room, likely rooted already.
Click to expand...
Click to collapse
thanks for that but when I did it in my phone it says su binary out of date! what can I do now?

Can you explain everything you did, beginning to end. And exactly when/where you get that message?

I had already TWRP in my phone so I download your files. Opened the recovery and I did from there (install). When it finished rebooted the device and after that when i did a root check it said root access not properly install or sometihing

Koukosftw said:
I had already TWRP in my phone so I download your files. Opened the recovery and I did from there (install). When it finished rebooted the device and after that when i did a root check it said root access not properly install or sometihing
Click to expand...
Click to collapse
Open the SuperSU app, and it will prompt you to install the binaries. Select yes, of course.

i did that too nothing happened :/

xunholyx said:
Open the SuperSU app, and it will prompt you to install the binaries. Select yes, of course.
Click to expand...
Click to collapse
This ^^^^
If it asks to update with a "normal" and "twrp/cwm" option... Try normal first. The other option if that doesn't work.

Darth said:
This ^^^^
If it asks to update with a "normal" and "twrp/cwm" option... Try normal first. The other option if that doesn't work.
Click to expand...
Click to collapse
I tried the normal it didnt work, how I do the second, I pressed it but nothing happened!

I don't think you have twrp installed anymore, or not properly. You've flashed it with fastboot, since updating to lollipop? How did you update to lollipop?

Normal, I never had root before. Upgraded my phone to 5.0 and then i tried to root it

Rooted fine here with normal method. Just had to update super su.

OK, can you please walk us through exactly what steps to Root you took. From the beginning. And we'll see what happened.
?

i havent been able to find the option to disable fast boot so i havent even tried yet but if anyone has let me know

chinkyarmour said:
i havent been able to find the option to disable fast boot so i havent even tried yet but if anyone has let me know
Click to expand...
Click to collapse
Settings > Power > Fast boot

xunholyx said:
Settings > Power > Fast boot
Click to expand...
Click to collapse
its not in lollipop
but i did it just now and rooted anyway
https://www.youtube.com/watch?v=WuHFcGvUjwA
followed this method again no problem

chinkyarmour said:
its not in lollipop
but i did it just now and rooted anyway
https://www.youtube.com/watch?v=WuHFcGvUjwA
followed this method again no problem
Click to expand...
Click to collapse
They must have taken the option out. It didn't boot any faster for me anyways. Not since 4.4.2

chinkyarmour said:
its not in lollipop
but i did it just now and rooted anyway
https://www.youtube.com/watch?v=WuHFcGvUjwA
followed this method again no problem
Click to expand...
Click to collapse
SO GUYS, ITS ME THAT I CREATED THIS THREAD! PROBLEM SOLVED. I ALREADY HAD TWRP AND DOWNLOADED THE Update-supersu file from the above youtube video (links) and I did it with recovery mode. I DONT KNOW BUT THE PREVIOUS supersu I installed couldnt update the su binary. This one did it. PROBLEM SOLVED AND I ROOTED MY 5.0.1 LOLIPOP DEVICE.
THANKS GUYS FOR EVERYTHING REALLY HELPFUL!!!