Database Develop

Unlocking bootloader and installing Custom recovery [Sprout4] [Marshmallow 6.0]

So i have successfully installed a custom recovery on my phone running Marshmallow and also unlocked the bootloader!
Its quite simple actually!
I am not responsible for any damage you make to your phone!
Steps-
1. Download the zip file from the link and extract it.
2. Install both the drivers and then proceed!(The drivers are universal and work for Windows 98,xp,vista,7,8,8.1,10 but in 8,8.1,10 you might need to turn off the digital signature verification-Make good use of google)
3.After installing the drivers , connect your phone in switched on and remember to turn on usb debugging in the dev options!
4. Open the unlock_bootloader_... and run the .bat file and follow the on screen steps( All the data will be formatted so make a backup beforehand)
5.After doing this you will void your warranty so make sure you know what you are doing!
6. Open the one click installer folder and replace the recovery.img with any recovery that you want.
7. Now again connect your phone in switched on mode and usb debugging on and run the .bat file of recovery installer.. and follow the on screen steps!
8.As soon as the the recovery installation is over do not let teh phone reboot just press the vol up button as the installation process stops and then go to recovery!
9.Boom!! Now you have a phone with unlocked bootloader and a custom recovery installed on marshmallow!!
10.Flash custom Kernels,Boot Animations, Logos and root your phone running marshmallow and brag!
Downloads--
Bootloader and Recovery.zip(27.4 MB)
Press Thanks:good: if this helped and if you have any querries just use the section below!

Recovery Kernel?
Hi bro just a quick question did you use the MM kernel in the custom recovery?
On our None AOSP standard Mediatek devices the rom does a Kernel check to ensure both the boot and recovery Kernels are of the same version eg KK boot = KK Recovery LP boot = LP Recovery so I just wondered if the MM Kernel still works in the Philz recovery or are you still using a kernel from a older version of android eg KK or LP.
Hope that makes sense to you :laugh:

How to open the unlock_bootloader ??? There is no such option

how about rooting? what method did you use?

bigrammy said:
Hi bro just a quick question did you use the MM kernel in the custom recovery?
On our None AOSP standard Mediatek devices the rom does a Kernel check to ensure both the boot and recovery Kernels are of the same version eg KK boot = KK Recovery LP boot = LP Recovery so I just wondered if the MM Kernel still works in the Philz recovery or are you still using a kernel from a older version of android eg KK or LP.
Hope that makes sense to you :laugh:
Click to expand...
Click to collapse
Actually i didn't work on the recovery, i just made the one click thing, i inserted any random recovery i found working on 6.0 .

cheeze.keyk said:
how about rooting? what method did you use?
Click to expand...
Click to collapse
i flashed a custom kernel and then the super su beta zip

akash.kotwani said:
How to open the unlock_bootloader ??? There is no such option
Click to expand...
Click to collapse
in the zip you will find a .bat file, open that and follow on screen instructions

How to relock bootloader if I ever want to?

net_freak said:
How to relock bootloader if I ever want to?
Click to expand...
Click to collapse
Well i did not make anything that can do that but you'll probably find it in other threads. You can also flash bootloader.using the stock rom file via sp flash tools to relock it just untick everything else but bootloader!

Unlocking bootloader is necessary? Can I not just do it with it locked bootloader?

net_freak said:
Unlocking bootloader is necessary? Can I not just do it with it locked bootloader?
Click to expand...
Click to collapse
You can but unlocking the bootloader opens up many other things for devs!

divyesh bansal said:
You can but unlocking the bootloader opens up many other things for devs!
Click to expand...
Click to collapse
Will the fastboot method to flash twrp work ? I'm on Android 6.0

net_freak said:
Will the fastboot method to flash twrp work ? I'm on Android 6.0
Click to expand...
Click to collapse
Yes it does, the tool is also all about it. In the one click recovery intaller folder replace the recovery.img with your twrp(you will have to rename twrp.img file to recovery.img) and follow the steps in the first post in this thread!

divyesh bansal said:
Yes it does, the tool is also all about it. In the one click recovery intaller folder replace the recovery.img with your twrp(you will have to rename twrp.img file to recovery.img) and follow the steps in the first post in this thread!
Click to expand...
Click to collapse
Thanks. . can I use all in one tool kit by @Faiyaz5yaz for the same

[Recovery][LG-H960A] TWRP v3.0.2-0 (unofficial)

This is an unofficial TWRP port for LG-H960A.
Thanks to @KAsp3rd and @GROGG88
I DON'T TAKE ANY RESPONSIBILITY. YOU DO EVERYTHING AT YOUR OWN RISK.
READ EVERYTHING and MAKE A BACKUP BEFORE YOU START.
Instructions:
1. You must be on newest stock Marshmallow: H960A20a_00_0316.kdz
You can use LG Bridge to install official update, or download .kdz file HERE
2. You need to have bootloader ulocked.
Official instructions are here: ( Unlocking the Bootloader @ LG Developer )
Remember that this will completely WIPE YOUR DATA, you will LOSE WARRANTY and this operation is IRREVERSIBLE.
3. Flash TWRP.
I assume you got ADB and FASTBOOT drivers working and adb is paired (it should be if you completed step 2).
Connect your phone to your pc, open command prompt and reboot to bootloader:
Code:
adb reboot bootloader
Your phone should reboot and you should be welcomed by Fastboot Mode screen.
Now download the recovery file (below) to your pc, unpack (to get .img) and rename it to recovery.img and put it in folder where you got command prompt open and:
Code:
fastboot flash recovery recovery.img
4. Boot to TWRP.
As on Marshmallow some fastboot commands are not working and LG is restoring recovery on every boot (so you cant use "adb reboot recovery" right now) you need to use one trick.
DO NOT REBOOT YOUR PHONE.
When still in fastboot from step 3 you need to turn off your phone completely. You can do that by holding power button or if that is not working take the battery out.
Now (put the battery in) and press POWER + VOL DOWN buttons. When you see LG logo release the POWER button (while still holding VOL DOWN) and press POWER button again.
You should see a screen which is asking you if you want to factory reset your phone. Don't worry - if you made everything correctly it should not wipe your phone.
Use volume and power buttons to choose YES (twice) - and you should see a TWRP screen (after a while)
WARNING: IF YOU REBOOTED YOUR PHONE AFTER FLASHING RECOVERY THIS STEP WILL REALLY ERASE ALL DATA. You need to flash recovery again (step 3)
5. (optional) flash SuperSU to get root.
Get SuperSU from official thread and put it in your phone.
While in TWRP from step 4 your phone should be recognized by ADB. Use below to move file to sdcard.
Code:
adb push BETA-SuperSU-v2.74-2-20160519174328.zip /sdcard/supersu.zip
Now in TWRP click Install, go to /sdcard/ and chooose supersu.zip. Follow instructions. After install you should choose to wipe cache/dalvik and reboot to system.
Your phone should be rooted now.
Download:
twrp-3.0.2.0-0-h960a.img.zip
(unpack .zip to get flashable .img)
Issues:
- Layout is wrong, status bar is being drawn on second screen.
- Date/time is wrong.

broken url

OK, now if we have recovery, is it possible to dump rooted system and pack it to .tot file for people who don't want to lose warranty?

11868 said:
broken url
Click to expand...
Click to collapse
Oh, true. Fixed.
rascal0pl said:
OK, now if we have recovery, is it possible to dump rooted system and pack it to .tot file for people who don't want to lose warranty?
Click to expand...
Click to collapse
Maybe.

Thank You it worked!

Great. Just bought it 2 days ago for good price. Will try it.
Sent from my LG-H955 using Tapatalk

Hi,
that's just great, thanks a lot.
As root is now possible has anyone tried to install xposed on th H960A?
I'm wondering if the second screen fix for the Telekom V10 also works with the H960A.
What about Viper4Android and AdAway?

rudi666 said:
This is an unofficial TWRP port for LG-H960A.
Thanks to @KAsp3rd and @GROGG88
I DON'T TAKE ANY RESPONSIBILITY. YOU DO EVERYTHING AT YOUR OWN RISK.
READ EVERYTHING and MAKE A BACKUP BEFORE YOU START.
Instructions:
1. You must be on newest stock Marshmallow: H960A20a_00_0316.kdz
You can use LG Bridge to install official update, or download .kdz file HERE
2. You need to have bootloader ulocked.
Official instructions are here: ( Unlocking the Bootloader @ LG Developer )
Remember that this will completely WIPE YOUR DATA, you will LOSE WARRANTY and this operation is IRREVERSIBLE.
3. Flash TWRP.
I assume you got ADB and FASTBOOT drivers working and adb is paired (it should be if you completed step 2).
Connect your phone to your pc, open command prompt and reboot to bootloader:
Code:
adb reboot bootloader
Your phone should reboot and you should be welcomed by Fastboot Mode screen.
Now download the recovery file (below) to your pc, unpack (to get .img) and rename it to recovery.img and put it in folder where you got command prompt open and:
Code:
fastboot flash recovery recovery.img
4. Boot to TWRP.
As on Marshmallow some fastboot commands are not working and LG is restoring recovery on every boot (so you cant use "adb reboot recovery" right now) you need to use one trick.
DO NOT REBOOT YOUR PHONE.
When still in fastboot from step 3 you need to turn off your phone completely. You can do that by holding power button or if that is not working take the battery out.
Now (put the battery in) and press POWER + VOL DOWN buttons. When you see LG logo release the POWER button (while still holding VOL DOWN) and press POWER button again.
You should see a screen which is asking you if you want to factory reset your phone. Don't worry - if you made everything correctly it should not wipe your phone.
Use volume and power buttons to choose YES (twice) - and you should see a TWRP screen (after a while)
WARNING: IF YOU REBOOTED YOUR PHONE AFTER FLASHING RECOVERY THIS STEP WILL REALLY ERASE ALL DATA. You need to flash recovery again (step 3)
5. (optional) flash SuperSU to get root.
Get SuperSU from official thread and put it in your phone.
While in TWRP from step 4 your phone should be recognized by ADB. Use below to move file to sdcard.
Code:
adb push BETA-SuperSU-v2.74-2-20160519174328.zip /sdcard/supersu.zip
Now in TWRP click Install, go to /sdcard/ and chooose supersu.zip. Follow instructions. After install you should choose to wipe cache/dalvik and reboot to system.
Your phone should be rooted now.
Download:
twrp-3.0.2.0-0-h960a.img.zip
(unpack .zip to get flashable .img)
Issues:
- Layout is wrong, status bar is being drawn on second screen.
- Date/time is wrong.
Click to expand...
Click to collapse
Are there any other known issues? I don`t need to install any custom roms. I need it only for root and xposed on Marshmallow. Is there something that can surprise me?

Hi,
"OK, now if we have recovery, is it possible to dump rooted system and pack it to .tot file for people who don't want to lose warranty? "
Ohh, thats sounds nice if this realy possible.
i love my v10.

orbitandre said:
hi,
"ok, now if we have recovery, is it possible to dump rooted system and pack it to .tot file for people who don't want to lose warranty? "
ohh, thats sounds nice if this realy possible.
i love my v10.
Click to expand...
Click to collapse
+1 ??

cyvr1 said:
As root is now possible has anyone tried to install xposed on th H960A?
I'm wondering if the second screen fix for the Telekom V10 also works with the H960A.
What about Viper4Android and AdAway?
Click to expand...
Click to collapse
Didn't try xposed but I think it should work (if it's working on other V10 models - they are not that different). I just recently bought V10 and was disappointed in dpi, so I needed root to patch second screen to be dpi-independent.
Also: why would you want things like Viper4Android when you got really good sounding hifi dac onboard?
fixxxer102 said:
Are there any other known issues? I don`t need to install any custom roms. I need it only for root and xposed on Marshmallow. Is there something that can surprise me?
Click to expand...
Click to collapse
For sure it's enough to flash packages and get root. Xposed is independent from recovery so I can't say anything about that.
Testing are up to you guys. Don't be afraid as this phone is not easy to brick.

rudi666 said:
Also: why would you want things like Viper4Android when you got really good sounding hifi dac on board?
Click to expand...
Click to collapse
Quite simple answer. The onboard Hifi DAC only works with cable headphones. Viper4Android also supports Bluetooth devices.

rudi666 said:
I just recently bought V10 and was disappointed in dpi, so I needed root to patch second screen to be dpi-independent.
Click to expand...
Click to collapse
Could you write a small guide about the dpi change (I prefer 540-580)?
Thanks in advance.

cyvr1 said:
Quite simple answer. The onboard Hifi DAC only works with cable headphones. Viper4Android also supports Bluetooth devices.
Click to expand...
Click to collapse
Ah, you are right, that makes perfect sense. Sorry, I forgot about that.
paschalism said:
Could you write a small guide about the dpi change (I prefer 540-580)?
Click to expand...
Click to collapse
There is still a long way, right now second screen FCs are fixed, but layouts are still wrong. I don't know if I can fix it to be truly dpi-independent but I think 560 is optimal value for this screen.

Is this working with
H960a
V20a-AME-xx??

1k views and only 11 "thanks"??? Really? Guys! We need support devs! Big THANK YOU for ur hard work @rudi666. I haven't try ur method yet but I am happy with the fact that something is beginning to happen with v10
Wysłane z mojego LG-H960 przy użyciu Tapatalka

asmoroth said:
I haven't try ur method yet but I am happy with the fact that something is beginning to happen with v10
Click to expand...
Click to collapse
I did try his method and it worked like a charm. Ok, you'll have to reflash TWRP if you want to use it but I'm sure it's just a matter of time until we have permanent TWRP like th T-Mobile V10 obviously has.
Thanks to rudi666 I have root, xposed, adaway and viper4audio up and running on my V10. And as there are no interesting custom roms to flash in my opinion it does not matter that I'd need to reflash TWRP. If you plan your flashing in advance you can flash all zip files in one go. No real need for TWRP afterwards.

Thanks guys. Unfortunately I see there is not much going on in V10 scene, and it's a shame.
cyvr1 said:
Ok, you'll have to reflash TWRP if you want to use it but I'm sure it's just a matter of time until we have permanent TWRP like th T-Mobile V10 obviously has.
Click to expand...
Click to collapse
Hm.. if you follow instructions you should get permanent TWRP, just try "adb reboot recovery" to test it if you don't want to risk clearing data when using button combination. There is a file called /system/boot-from-recovery.p which is 'restoring recovery' on every boot (that's why there is an info in instruction about not rebooting your phone the first time), but after all the steps this file will be patched. I don't remember if the first use of TWRP or flashing SuperSU does it, but you should get permanent recovery. If not you can always rename this file manually.

rudi666 said:
Hm.. if you follow instructions you should get permanent TWRP, just try "adb reboot recovery" to test it if you don't want to risk clearing data when using button combination. There is a file called /system/boot-from-recovery.p which is 'restoring recovery' on every boot (that's why there is an info in instruction about not rebooting your phone the first time), but after all the steps this file will be patched. I don't remember if the first use of TWRP or flashing SuperSU does it, but you should get permanent recovery. If not you can always rename this file manually.
Click to expand...
Click to collapse
Hi,
I will try that again and see if I can get permanent TWRP. But as I said currently there is no real requirement for that. I flashed SuperSU and both files for xposed when I first booted into recovery and that is all I need at the moment.

i cant enter bootloader
h960A
after adb reboot booloader it keeb restart to soft

[ZE601KL] Official Marshmallow WW_V21.40.1220.1698 ROOT and TWRP install

P/S: Im sorry if im against this XDA or forums rules. Its my first time to post something. If i done something wrong kindly let me know.
Condition: You have Official Marshmallow WW_V21.40.1220.1698 installed on your ZE601KL (I forgot to mention that Im coming from CM13, that makes it need bootloader unlock n root probably?)
TWRP install:
-go into fastboot mode (shut down your phone. press VOL UP + POWER at the same time until it vibrates and release)
-download and install adb (can get it here i guess. credit to @snoop005 )
-download twrp here (credit to maintainer @LuK1337) and put it in the ADB folder
-in ur pc hold shift + right click and click "open command window here" in ADB folder
-type in "fastboot device" and make sure ur device is detected
-type in "fastboot flash recovery recovery.img" (recovery.img must be the same name with the twrp that u hv downloaded eg:fastboot flash recovery twrp-3.0.2-4-Z00T.img )
-type in "fastboot boot recovery.img" (recovery.img must be the same name with the twrp that u hv downloaded eg:fastboot boot twrp-3.0.2-4-Z00T.img )
-look at ur phone and it should be installed
Root install
-download SuperSU (credit to @Chainfire) (thanks to @Cr0ssL1nk for notify me about the updated SuperSU! )
-boot to recovery (shut down your phone. press VOL DOWN + POWER at the same time until it vibrates and release)
-select install and browse for the .zip file location
-wait for the installation done and ure good to go

It works on my ZE601KL!!!
Thank you very much xyexiaoyuer in your first post

I would assume this process is the same for any of the variants for which the bootloader is already unlocked and assuming you use the correct TWRP image.
If nothing else, it should work for any Z00T phone. I'll try it on my ZE551KL tonight.

xyexiaoyuer said:
P/S: Im sorry if im against this XDA or forums rules. Its my first time to post something. If i done something wrong kindly let me know.
Condition: You have Official Marshmallow WW_V21.40.1220.1698 installed on your ZE601KL
TWRP install:
-go into fastboot mode (shut down your phone. press VOL UP + POWER at the same time until it vibrates and release)
-download and install adb (can get it here i guess. credit to @snoop005 )
-download twrp here (credit to maintainer @LuK1337) and put it in the ADB folder
-in ur pc hold shift + right click and click "open command window here" in ADB folder
-type in "fastboot device" and make sure ur device is detected
-type in "fastboot flash recovery recovery.img" (recovery.img must be the same name with the twrp that u hv downloaded eg:fastboot flash recovery twrp-3.0.2-4-Z00T.img )
-type in "fastboot boot recovery.img" (recovery.img must be the same name with the twrp that u hv downloaded eg:fastboot boot twrp-3.0.2-4-Z00T.img )
-look at ur phone and it should be installed
Root install
-download SuperSU ive tested SuperSU Root BETA v2.67.zip credit to them (help me credit them as i dont know who to tag)
-boot to recovery (shut down your phone. press VOL DOWN + POWER at the same time until it vibrates and release)
-select install and browse for the .zip file location
-wait for the installation done and ure good to go
Click to expand...
Click to collapse
On the "fastboot boot recovery.img", I first got it to successfully transfer over something, then the second line said that it failed.
I continually did this and got the same results and my phone continued to say "fastboot" in the corner, so I wasn't sure if anything had happened.
I finally "gave up" and pulled the battery but I booted into the Recovery (Vol down + Power) and found that TWRP actually was installed and from there I flashed over SuperSU and was rooted in minutes.
Great job, and thanks! I may be a bit rusty with all this since this is my first Android device in about 3 years.

Joxefo said:
It works on my ZE601KL!!!
Thank you very much xyexiaoyuer in your first post
Click to expand...
Click to collapse
wooot~ npnp bro..thank god it works for you too!!

rczrider said:
I would assume this process is the same for any of the variants for which the bootloader is already unlocked and assuming you use the correct TWRP image.
If nothing else, it should work for any Z00T phone. I'll try it on my ZE551KL tonight.
Click to expand...
Click to collapse
i forgot to mention the bootloader bro. sorry about that. already edited in my 1st post. So how was ur phone? does the method work on your ZE551KL?

ndh777 said:
On the "fastboot boot recovery.img", I first got it to successfully transfer over something, then the second line said that it failed.
I continually did this and got the same results and my phone continued to say "fastboot" in the corner, so I wasn't sure if anything had happened.
I finally "gave up" and pulled the battery but I booted into the Recovery (Vol down + Power) and found that TWRP actually was installed and from there I flashed over SuperSU and was rooted in minutes.
Great job, and thanks! I may be a bit rusty with all this since this is my first Android device in about 3 years.
Click to expand...
Click to collapse
good to hear that bro!! probably it failed because of bootloader? hv u unlock it before? im sorry didnt mention it on my first post. my bad my bad

Boot twrp, not flash it to root?
Does anyone know if it his possible to just boot twrp from adb/ fasboot( not actually flash it), flash SuperSU to root my device, then reboot to stock to keep stock recovery ? My bootloader is unlocked.

long2ski said:
Does anyone know if it his possible to just boot twrp from adb/ fasboot( not actually flash it), flash SuperSU to root my device, then reboot to stock to keep stock recovery ? My bootloader is unlocked.
Click to expand...
Click to collapse
hi broo..you can always flash stock recovery after u flash superSU using twrp =)

xyexiaoyuer said:
hi broo..you can always flash stock recovery after u flash superSU using twrp =)
Click to expand...
Click to collapse
Thanks, but I am pretty sure Flashing twrp writes over stock recovery and unless someone else has the stock image, you can't get it back. I don't know how to make a backup of stock recovery, that's why I wondered if only booting twrp will work.

long2ski said:
Thanks, but I am pretty sure Flashing twrp writes over stock recovery and unless someone else has the stock image, you can't get it back. I don't know how to make a backup of stock recovery, that's why I wondered if only booting twrp will work.
Click to expand...
Click to collapse
if ure using ze601kl, i think the stock recovery can be downloaded here .. download according to your version of firmware of course =) let me know if its work for you. the last time im coming from cm13 to Lollipop im using recovery from there to write off twrp. hope this helps =)

Thanks, that's a great resource! I kind of hijacked this thread since I have the ze551kl. Even though its a zoot model, I'm reluctant to flash anything that is not the exact model firmware. Will the 601 image work for the 551?

long2ski said:
Thanks, that's a great resource! I kind of hijacked this thread since I have the ze551kl. Even though its a zoot model, I'm reluctant to flash anything that is not the exact model firmware. Will the 601 image work for the 551?
Click to expand...
Click to collapse
i dont think so..better dont as i only tested this with ze601kl =( buttttt the stock recovery for your model probably can be downloaded here not sure it will work though..proceed at ur own risk.
sorry bro if its not being helpful

xyexiaoyuer said:
i forgot to mention the bootloader bro. sorry about that. already edited in my 1st post. So how was ur phone? does the method work on your ZE551KL?
Click to expand...
Click to collapse
Yep, worked fine on the ZE551KL.
long2ski said:
Does anyone know if it his possible to just boot twrp from adb/ fasboot( not actually flash it), flash SuperSU to root my device, then reboot to stock to keep stock recovery ? My bootloader is unlocked.
Click to expand...
Click to collapse
long2ski said:
Thanks, that's a great resource! I kind of hijacked this thread since I have the ze551kl. Even though its a zoot model, I'm reluctant to flash anything that is not the exact model firmware. Will the 601 image work for the 551?
Click to expand...
Click to collapse
You can boot into TWRP without overwriting your stock recovery using:
HTML:
fastboot boot twrp.img
That would allow you to install SuperSU without actually installing TWRP. If you want to replace stock recovery with TWRP, you would use:
HTML:
fastboot flash recovery twrp.img

xyexiaoyuer said:
P/S: Im sorry if im against this XDA or forums rules. Its my first time to post something. If i done something wrong kindly let me know.
Condition: You have Official Marshmallow WW_V21.40.1220.1698 installed on your ZE601KL (I forgot to mention that Im coming from CM13, that makes it need bootloader unlock n root probably?)
TWRP install:
-go into fastboot mode (shut down your phone. press VOL UP + POWER at the same time until it vibrates and release)
-download and install adb (can get it here i guess. credit to @snoop005 )
-download twrp here (credit to maintainer @LuK1337) and put it in the ADB folder
-in ur pc hold shift + right click and click "open command window here" in ADB folder
-type in "fastboot device" and make sure ur device is detected
-type in "fastboot flash recovery recovery.img" (recovery.img must be the same name with the twrp that u hv downloaded eg:fastboot flash recovery twrp-3.0.2-4-Z00T.img )
-type in "fastboot boot recovery.img" (recovery.img must be the same name with the twrp that u hv downloaded eg:fastboot boot twrp-3.0.2-4-Z00T.img )
-look at ur phone and it should be installed
Root install
-download SuperSU ive tested SuperSU Root BETA v2.67.zip credit to them (help me credit them as i dont know who to tag)
-boot to recovery (shut down your phone. press VOL DOWN + POWER at the same time until it vibrates and release)
-select install and browse for the .zip file location
-wait for the installation done and ure good to go
Click to expand...
Click to collapse
Are you sure your phone is truely rooted and that apps needing root really works ?
Because in the official SuperSU page on XDA: http://forum.xda-developers.com/showthread.php?t=1538053 , the developpers says your phone must already be rooted before flashing SuperSU.
Also, change the 2.76 Beta's link you gived for SuperSU in your tutorial to the 2.76 Stable version from my link to the official SuperSU XDA page.

Cr0ssL1nk said:
Are you sure your phone is truely rooted and that apps needing root really works ?
Because in the official SuperSU page on XDA: http://forum.xda-developers.com/showthread.php?t=1538053 , the developpers says your phone must already be rooted before flashing SuperSU.
Also, change the 2.76 Beta's link you gived for SuperSU in your tutorial to the 2.76 Stable version from my link to the official SuperSU XDA page.
Click to expand...
Click to collapse
Welp! now that i check back using "root check" apps it seems that the app hv some trouble to detect whether the phone is rooted. the last time everything was okay except for busybox. Perhaps because i rebooted the device? nvrtheless i will update the link and test the stable supersu given in the link

xyexiaoyuer said:
Welp! now that i check back using "root check" apps it seems that the app hv some trouble to detect whether the phone is rooted. the last time everything was okay except for busybox. Perhaps because i rebooted the device? nvrtheless i will update the link and test the stable supersu given in the link
Click to expand...
Click to collapse
I don't think rebooting caused this.
The thing that makes me worry is that Busybox was not okay the first time you rooted your phone, because it must be one of the first thing that must be ok when you root a phone.
Have you got any updates on your side about making root really working ?

Cr0ssL1nk said:
I don't think rebooting caused this.
The thing that makes me worry is that Busybox was not okay the first time you rooted your phone, because it must be one of the first thing that must be ok when you root a phone.
Have you got any updates on your side about making root really working ?
Click to expand...
Click to collapse
Hi Brooooo, im happy to report that the SuperSU is still intact even if the device has been rebooted several times. thx a lot broooo and busybox is installed correctly toooo. already put thumbnails attachment at the 1st post for proof

xyexiaoyuer said:
Hi Brooooo, im happy to report that the SuperSU is still intact even if the device has been rebooted several times. thx a lot broooo and busybox is installed correctly toooo. already put thumbnails attachment at the 1st post for proof
Click to expand...
Click to collapse
No problem, proofs are just great ! :highfive:
Also, check this post: http://forum.xda-developers.com/showpost.php?p=67978015&postcount=8
Because you also must allow SuperSU in ASUS' Autostart Manager, that may be the problem you also got.
But please remember: Do not post something that seems to work but is not, a Beta or something not stable to other people without a lot of checking first

rczrider said:
Yep, worked fine on the ZE551KL.
You can boot into TWRP without overwriting your stock recovery using:
HTML:
fastboot boot twrp.img
That would allow you to install SuperSU without actually installing TWRP. [/HTML]
Click to expand...
Click to collapse
Thanks to everyone's help and ideas and especially to @rczrider. On my ze551kl, I successfully booted the twrp.img in fastboot, did a backup through twrp, then installed supersu zip, and successfully rooted. No overwrite of stock recovery with all the root privileges. Perfect.

[Guide][No Root]Enable Camera2API in stock rom with Locked bootloader, OTA compatible

This Guide Can Also Be Used For Unlocking & Relocking Bootloader, Installing TWRP & Rooting
If Any Ota Messes With The Implementation Then Whole Procedure Needs To Be Redone
To mitigate the problem requesting developers for making a hack for Relocking Bootloader Without Wiping Data PM me if Interested
Data Will Be Wiped So Make Backup First
What Will We Be Doing: Unlocking Bootloader, Installing TWRP,Flashing Camera2api Enabler, Installing Back Stock Recovery, Relocking Bootloader
Procedure:
1. Download this rar and you'll get 2 folders namely unlock and ASUS_Android_USB_drivers_for_Windows
2. Install the drivers according to your OS (happens Automatically In Most Cases) and open the unlock folder
3. Reboot your phone to fastboot mode by pressing volume up + power on at the same time.
4. Connect it to pc and open unlock.bat in unlock folder
5. Long Press Power Button & Reboot. A wiping Data screen will appear followed by an encrypting sceen then the phone will reboot (A warning of unlocked bootloader will show up initially)& then the initial setup screen will show up don't add any thing & skip the setup(there will be another wipe).
6. Download Cam2Api & copy it to sd card or internal storage of phone. Then switch off the phone once again & reboot in fastboot mode once more.
7. Download TWRP from here & Install Minimal ADB to root of C drive.
8. Copy the twrp to the adb folder in your C drive.
9. Open the 'cmd-here.exe' the adb window will open
10. With the phone connected in fastboot mode type in adb "fastboot flash recovery twrpasus.img" & press enter then type "fastboot boot twrpasus.img" & hit enter.
11. Switch Off the phone & boot in twrp by pressing vol down+power, opening TWRP will take time
12. A decryption popup will open in twrp skip it.
13. Select Install Zip & slect the storage where you have kept the cam2api.zip & flash it, then select reboot system.
14. Download Gcam from here (Arnova v8 is best) & copy it to phone and install it, check if it works, dont configure it. Reboot your phone to fastboot mode
15. Download stock asus recovery from here & copy it to the adb folder.
16. Again open the adb & type "fastboot flash recovery recovery.img"
17. Download Zenfone_Max_M1_Pro_Relock.zip and extract it.
18. Open the directory where you extracted the file
19. In that directory, open a file named relock_bl.cmd
20. A Command (CMD) prompt will do the rest of the work for you.
Let the phone restart.
21. It will then erase all the data on your phone once again (excluding Micro SD card).
23. Reboot
22. Now the phone won’t show the “bootloader unlocked” warning that was displayed after you unlocked the bootloader. Now setup the phone and install the Gcam downloaded earlier also all manual camera apps will work fine too.
Done! You Have Successfully Relocked Bootloader & Enabled Camera 2 api in stock rom. As the bootloader is locked & we have'nt rotted our phone you have your warranty and ota updates work well. If any kind of future ota breaks the camera2api then you have to redo the procedure once again.
Installing Magisk Or SuperSU while twrp is installed will root your phone (breaks ota updates though)
Credits to:
@Sudeep Duhoon : For Original Unofficial unlock & Camera2api Enabler script
@Shivam Kumar Jha For Unofficial TWRP
@style2345 For Providing ASUS Stock Recovery
@myapky For Relocking Script
Hit Thanks If This Helped You!

Ok, I have got stuck. Have a windows 10 machine so was unable to apply the drivers since they were automatically installed. When I tried to install manually, I got an error message that driver is not compatible. Rest of the steps when fine till Step 10. But thereafter TWRP was not installed and the phone went into default recovery with options and th botton of the screen showing an error showing E: couldn't load bitmap fill_ball (error -7). What could have happened?

mehtasu said:
Ok, I have got stuck. Have a windows 10 machine so was unable to apply the drivers since they were automatically installed. When I tried to install manually, I got an error message that driver is not compatible. Rest of the steps when fine till Step 10. But thereafter TWRP was not installed and the phone went into default recovery with options and th botton of the screen showing an error showing E: couldn't load bitmap fill_ball (error -7). What could have happened?
Click to expand...
Click to collapse
You need to uninstall the drivers & redo the process most times we dont need to manually install the drivers. We install drivers only if flashing doesnt occur(you did the opposite) after installing twrp make sure to clear data(factory reset through it)

AstroBiswas said:
You need to uninstall the drivers & redo the process most times we dont need to manually install the drivers. We install drivers only if flashing doesnt occur(you did the opposite) after installing twrp make sure to clear data(factory reset through it)
Click to expand...
Click to collapse
Oh I found my way into TWRP. Am i supposed to keep it read only or accept swipe to allow modifications?

mehtasu said:
Oh I found my way into TWRP. Am i supposed to keep it read only or accept swipe to allow modifications?
Click to expand...
Click to collapse
Swipe to allow modifications ofcourse how would we change anything without that permission

Thankyou, the guide works perfectly. Just to add when installing twrp, boot directly into recovery, otherwise twrp won't install. Just wanted to put it here so that people don't have to go through other threads.

1. Ask before using someone else's stuff in your guide without providing op links or at least give credits
2. Did you test it before posting if the ota will flash fine? As i highly doubt that

Sudeep Duhoon said:
1. Ask before using someone else's stuff in your guide without providing op links or at least give credits
2. Did you test it before posting if the ota will flash fine? As i highly doubt that
Click to expand...
Click to collapse
Thanks for reminding, credits given to each hardworking dev who made this guide possible
Yup I Did Test May Security Patch arrived via ota & it installed fine, didnt break the api.

AstroBiswas said:
Thanks for reminding, credits given to each hardworking dev who made this guide possible
Yup I Did Test June Security Patch arrived via ota & it installed fine, didnt break the api.
Click to expand...
Click to collapse
The June Security Patch is arrived via OTA now?
Sent from my [device_name] using XDA-Developers Legacy app

The Wolf Dark said:
The June Security Patch is arrived via OTA now?
Click to expand...
Click to collapse
No actually my phone has just arrived I Did this procedure on the day itself

AstroBiswas said:
Thanks for reminding, credits given to each hardworking dev who made this guide possible
Yup I Did Test June Security Patch arrived via ota & it installed fine, didnt break the api.
Click to expand...
Click to collapse
Last update was on june 14 with may security patch. I highly doubt this method works without losing ota

Aftab_khatri said:
Last update was on june 14 with may security patch. I highly doubt this method works without losing ota
Click to expand...
Click to collapse
Oh my bad they provided may patch in june update.
We havent done any kind of detectable large system modification so ota's work

Sudeep Duhoon said:
1. Ask before using someone else's stuff in your guide without providing op links or at least give credits
2. Did you test it before posting if the ota will flash fine? As i highly doubt that
Click to expand...
Click to collapse
Thankyou. I had to search for your thread to take care of some troubleshooting. Also, will surely have to follow the guide to go stock/relock to get furture OTA updates. Never the less a big thank you to you and the other developers for their contributions for this phone. Makes this divice so very worthwhile.

Well its working as mentioned by OP.......
Well done !!!

What if we use the command fastboot boot revovery.img and flash the cam 2 api zip when it boots to twrp or is it necessary to use the command flastboot flash recovery recovery.img

pranavsree00 said:
What if we use the command fastboot boot revovery.img and flash the cam 2 api zip when it boots to twrp or is it necessary to use the command flastboot flash recovery recovery.img
Click to expand...
Click to collapse
I had tried it. It didnt work

AstroBiswas said:
I had tried it. It didnt work
Click to expand...
Click to collapse

pranavsree00 said:
Click to expand...
Click to collapse
if you already have twrp installed then you just have to flash the cam2.zip thats all ...........
& if you don't have twrp then you have to first install twrp using the command by OP & then flash cam2.zip as mentioned it original thread .

Anyone who has done this, please reply to this post if they get the next OTA when released, and installed it without any issues. So that I can perform it without any trouble on updates and warranty...

Amal Prabhakaran said:
Anyone who has done this, please reply to this post if they get the next OTA when released, and installed it without any issues. So that I can perform it without any trouble on updates and warranty...
Click to expand...
Click to collapse
Well just follow the give procedure or steps one by one & relock the bootloader at last and you would be good to go .....
Well I didn't relocked the bootloader & I frequently change my ROMS & regarding updates well there is none after 309 so whenever there would be an update I will give it a try then but for now everything is working fine so you can give it a go .........

Question???

I was wondering is there any RP2 ROMS like Lineage os or other ROMS? Or not yet or it's not possible to make for this kind of phone or maybe i didn't search more to know what's going on??

No specific ROM for RP2 but you can install GSI ROM after unlocking your bootloader.
Peace

chris5s said:
No specific ROM for RP2 but you can install GSI ROM after unlocking your bootloader.
Peace
Click to expand...
Click to collapse
Okay Thanks for the info, But i'm trying to root my phone on mr2 i can't find any thread that shows how to root mr2 with steps ??

I'm on MR 2 as well. Follow these steps :-
Unlock bootloader.
Flash Arter's kernel from bootloader mode. Then boot into TWRP recovery (comes with Arters kernel) and from there flash latest Magisk zip to get root.
Peace

chris5s said:
I'm on MR 2 as well. Follow these steps :-
Unlock bootloader.
Flash Arter's kernel from bootloader mode. Then boot into TWRP recovery (comes with Arters kernel) and from there flash latest Magisk zip to get root.
Peace
Click to expand...
Click to collapse
Doesn't work on MR2 December realeas i tried and it bricked my phone any other way?

AssyrianHero said:
Doesn't work on MR2 December realeas i tried and it bricked my phone any other way?
Click to expand...
Click to collapse
Yes it does you have to flash the global version NOT the AT&T version.
https://s3.amazonaws.com/cheryl-factory-images/aura-p-release-3123-user-full.zip

JDBarlow said:
Yes it does you have to flash the global version NOT the AT&T version.
https://s3.amazonaws.com/cheryl-factory-images/aura-p-release-3123-user-full.zip
Click to expand...
Click to collapse
Yes this is what i'm flashing "aura-p-release-3123-user-full" its global version and i think i'm doing something wrong can you explain step by step instructions? cause i'm new to RP2 and i'm used to old simple root method

Have you tried flashing Arter's kernel then reboot into system before trying to root?
If that works then maybe it's the rooting that's bricking the phone?
Which version of Magisk are you trying to flash?

chris5s said:
Have you tried flashing Arter's kernel then reboot into system before trying to root?
If that works then maybe it's the rooting that's bricking the phone?
Which version of Magisk are you trying to flash?
Click to expand...
Click to collapse
The problem there is no steps that shows what to do I'm just using my own steps, and I'm not using any Magisk I'm just trying to flash Arter's kernel.

Maybe explain what steps you are doing and what errors you are getting then?
Can you put the phone into bootloader mode? Is it unlocked? Do you have adb and do you know how to use it?
Peace.

AssyrianHero said:
Yes this is what i'm flashing "aura-p-release-3123-user-full" its global version and i think i'm doing something wrong can you explain step by step instructions? cause i'm new to RP2 and i'm used to old simple root method
Click to expand...
Click to collapse
Honestly it's easier to root phones today than it ever has especially the RP2.
If you are truly unlocked this should only take you minutes to do.
First things first. Open a terminal where you have ADB / FASTBOOT installed or if you setup the attributes properly just open a terminal.
Type adb devices and it should give you your serial number of your phone. If not adb isn't installed properly.
If so, type adb reboot bootloader and phone will boot to bootloader.
Type fastboot devices and again it should give you the phones ID. If not fastboot isn't installed properly.
If so, type fastboot flash boot and the name of your arter97 file.img this will also install TWRP.
After installation from bootloader menu scroll down to reboot recovery and it should boot to TWRP.
Click cancel then swipe to allow modifications. In TWRP menu select INSTALL then choose where you've saved the magisk 20.3 file on your SD or internal drive.
After installation reboot system then install magisk manager if not already installed. At this point you're rooted. Have a great weekend!!
Good luck! :good:

Make sure you have unlocked your phone, suggest following razer official instruction.(new xda user cant post outside link, search it)
1.Unlock the Bootloader 2.Unlock the Bootloader Critical Partitions 3.Flash official System Image
And please note unlock will erases all user data on the Phone!
After unlocked your phone you can flash arter97 kernel or f(x)THaxxorX TrinityKernel. Both of them contain TWRP, install Magisk Manager and flash Magisk in TWRP. Get rooted.

chris5s said:
Maybe explain what steps you are doing and what errors you are getting then?
Can you put the phone into bootloader mode? Is it unlocked? Do you have adb and do you know how to use it?
Peace.
Click to expand...
Click to collapse
The bootloader is unlocked i do have adb and i i know how to use it I've been rooting all my phones HTC M9 Samsung S7-8-9 and OnePlus 7 I've rooted too many phones but this one is little bit different than others i tried my own steps like i used to do:
I reboot my phone into bootloader and type fastboot devices and it gives me the Serial number and i then i type fastboot boot boot.img i don't know if this command works with this phone it actually worked with other phones this one not..

finixs said:
Make sure you have unlocked your phone, suggest following razer official instruction.(new xda user cant post outside link, search it)
1.Unlock the Bootloader 2.Unlock the Bootloader Critical Partitions 3.Flash official System Image
And please note unlock will erases all user data on the Phone!
After unlocked your phone you can flash arter97 kernel or f(x)THaxxorX TrinityKernel. Both of them contain TWRP, install Magisk Manager and flash Magisk in TWRP. Get rooted.
Click to expand...
Click to collapse
How to unlock the Bootloader Critical Partitions? I think i missed this step i have the bootloader unlocked..

Look on the Razer website for the specific instructions to unlock bootloader/critical.
The fastboot command to flash a boot img is
fastboot flash boot boot.img
Peace

AssyrianHero said:
How to unlock the Bootloader Critical Partitions? I think i missed this step i have the bootloader unlocked..
Click to expand...
Click to collapse
"fastboot flashing unlock" unlock bootloader
"fastboot flashing unlock_critical" unlock the bootloader critical partitions

Also, make sure you're using the Razer recommended USB cord and ADB/Fastboot.
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Cables
When connecting your Razer Phone to a computer for any development, it is advised by Razer to not use the in-box USB Type-C to Type-C charging cable for flashing. The supplied cable is specifically engineered for fast power delivery, not for data transfer. Razer recommends you use a USB 3 Type-A to Type-C spec-compliant cable for any device flashing.
Click to expand...
Click to collapse
Upgrade your ADB/Fastboot here.