Database Develop

[GUIDE] Marshmallow Root Guide for ZE500KL

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 instead​Download 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 computer​2 - Reboot in fastboot mode with one of the following method:
a -Volume Up while booting up​b -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

[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.

[ROOT] J7 prime - CF AUTO ROOT [ SM-G610F - SM-G610M]

Here we have root for stock rom Thanks to the Chainfire Team.
Everything done by them so all thanks and credits are for them
Download
https://download.chainfire.eu/1036/CF-Root/CF-Auto-Root/CF-Auto-Root-on7xelte-on7xeltedd-smg610f.zip
Installation
-Enable USB debugging and OEM unlocking in the settings
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue
-Flash the CF-Auto-Root package as AP in ODIN(Comes within the zip file), and your device should reboot into a modified recovery (signified by a large red Android logo) and it will install SuperSU for you and restore the stock recovery, and reboot back into Android.
I tested it on my device and it worked normally
I will not be responsible for any damage to your device, but following the steps will normally work normally
I just tested with ROM stock 6.0.1 with security patch from 1 July 2017
.

Hayleyw2 said:
Here we have root for stock rom Thanks to the Chainfire Team.
Everything done by them so all thanks and credits are for them
Download
https://download.chainfire.eu/1036/CF-Root/CF-Auto-Root/CF-Auto-Root-on7xelte-on7xeltedd-smg610f.zip
Installation
-Enable USB debugging and OEM unlocking in the settings
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue
-Flash the CF-Auto-Root package as AP in ODIN(Comes within the zip file), and your device should reboot into a modified recovery (signified by a large red Android logo) and it will install SuperSU for you and restore the stock recovery, and reboot back into Android.
I tested it on my device and it worked normally
I will not be responsible for any damage to your device, but following the steps will normally work normally
I just tested with ROM stock 6.0.1 with security patch from 1 July 2017
.
Click to expand...
Click to collapse
Hi will it work for version 7.0 also

it's working fine for me
i have "G610FDDU1BRF2" with android version 7.0 and it gets installed successfully
thanks

How to change Supersu with Magisk?

Razortm said:
it's working fine for me
i have "G610FDDU1BRF2" with android version 7.0 and it gets installed successfully
thanks
Click to expand...
Click to collapse
How to restore stock recovery

Ryan.XM said:
How to restore stock recovery
Click to expand...
Click to collapse
Flash the cf auto root and it will automatically change your recovery into stock.

bjpp21 said:
Flash the cf auto root and it will automatically change your recovery into stock.
Click to expand...
Click to collapse
Ok thanks

I have J7 prime [SM-G610F] with stock andriod 8.1, samsung experience 9.5 and 1 November 2018 security patch will it still work?

I don't think so. I think the J7 with 8.1 is impossible to root? I can't seem to find an answer on this.

lordbaal19 said:
i don't think so. I think the j7 with 8.1 is impossible to root? I can't seem to find an answer on this.
Click to expand...
Click to collapse
its not impossible to root j7 on oreo..just search here in xda and you will find the impossible is really possible.

Well the TWRP thread has no real answers and this method doesn't work either.

I have done it
LordBaal19 said:
Well the TWRP thread has no real answers and this method doesn't work either.
Click to expand...
Click to collapse
yes, I have made root in my SM-G610m with Android 8.1 and it was with TWRP, and I have learned it from YouTube and in Spanish language.
For now I do not have available Super User. I think this post will work for me

ernestoi said:
yes, I have made root in my SM-G610m with Android 8.1 and it was with TWRP, and I have learned it from YouTube and in Spanish language.
For now I do not have available Super User. I think this post will work for me
Click to expand...
Click to collapse
Found a way:
LordBaal19 said:
Which one do you recommend? At which point do I have to install it and then I don't need to install no-verity-opt-encrypt-6.0?
EDIT: I think I finally got it. I did it like this:
1. Ok, so the phone as a fresh 8.1.0 system (just flashed the 7.0 and then it updated OTA in a matter of minutes). I enter the phone, enable the developer mode, enable OEM Unlocking and USB Debug.
2. Then I put the phone on download mode, flash the TWRP recovery disabling the auto-reboot on Odin so it doesn't boot to system automatically. This seem important since otherwise the recovery goes back to stock.
3. Then, to get out of download mode I press vol. down and power keys at the same time and the phone turn off. Then I turn on the phone into recovery mode, once in there I swipe into write mode and go to Wipe and select Format Data, type down yes and it says it's done. I go back to TWRP main menu.
4. I connect the cellphone to the PC and in storage I select Mount USB. Then drag the Magisk-v18.0.zip file into the storage that pops up on Windows. Then I saftely remove the device in Windows and go back to the main TWRP menu on the phone. I select Install and install the .zip file without selecting Signature verification or Reboot after is complete. It says is done installing and no errors seems to occur. I employ the button to wipe Cache and Dalvik.
5. I go back again o Wipe and select Format Data, type down yes and it says it's done, again.
5. Then I try to reboot to System, and choose to Do Not Install the TWRP app, and... SUCCESS!! The phone starts again, I config everything and then Magisk is there in the apps. I tried with an app that requires SU and it works!
Thanks for the help.
Click to expand...
Click to collapse
For the files and details check the OP on that thread.

LordBaal19 said:
Found a way:
For the files and details check the OP on that thread.
Click to expand...
Click to collapse
That's the way I have done it. But if you go on Z3X, select the device (SM-G610M), and you perform some activity like repair IMEI, Z3X detects the root, but it does not detect the Super User.

[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 .........

[Easy_Root/Unroot][Any_Oreo/Nougat_Firmware_V4_Bootloaders][Tmp_Twrp_Recovery]

EASY ROOT/UNROOT FOR S7 OR S7E ALL NOUGAT OR OREO STOCK ROMS
THANKS @klabit87 FOR OREO ROOT
TEMPORARY TWRP RECOVERY VIA ADB THANKS TO @afaneh92​
This is for AT&T, T-Mobile and Verizon and Sprint running V4 bootloaders only!​
This tool will allow you too easily root any stock rom allowing you to make any modifications you might want then easily unroot for better performance
This will Also give you a fully functional TWRP recovery that can be accessed via adb. TWRP is fully functional on OREO Roms but is limited on Nougat roms
The initial setup does require a data wipe.​
S7 G935T Edge Odin Factory FIrmware Downloads
G935TUVU4CRI2_8.0_4File_USA (T-Mobile).rar
ADB_Root Temporary Twrp Tool Download
S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z
S7 G935 Edge Root/Unroot Odin Files Downloads
These Files Are Needed To Unroot Your Phone
SM_G935_EDGE_OREO.7z
SM_G935_EDGE_NOUGAT.7z
S7 G930 Flat Root/Unroot Odin Files Downloads
These Files Are Needed To Unroot Your Phone
SM_G930_FLAT_OREO.7z
SM_G930_FLAT_NOUGAT.7z
Instructions
1. Download S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z and your model and version you want from above
2. Unzip S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z to S7_S7E_ROOT_UNROOT_ADB_TOOLS folder
3. Unzip the Model/Version file you downloaded and copy the files to the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder and place them in the Odin folder
4. Prepare your phone for a data wipe
5. Reboot your phone to download mode and flash the AP_ROOT_G93*.tar in the Odin AP slot and reboot your phone to recovery
6. Once phone is in recovery run the Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder
7. Now in the cmd window make sure your device is connected and choose Option (1) Launch TWRP
8. Your phone should launch TWRP leave phone plugged in and command window open on computer
9. Now In Twrp choose wipe and choose format data. Type yes in the box when it ask
10. Now in cmd window choose Option(8) Push Root.zip to Phone
11. Now in TWRP choose install and select the Root.zip
12. After zip is installed reboot and go through setup.
13. Once through setup make sure you are rooted
To Unroot Your Phone
1. In the Root Control app choose phone settings and unroot phone make sure phone is connected to computer
2. Now depending on the type of root you choose your phone will reboot to download if you chose system root or stock recovery if you chose systemless root. If your phone reboots to download mode skip to number 5
3. If your phone reboots to recovery once your phone is in recovery run the Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder
4. In cmd window choose Option(3) Unroot phone will reboot too download mode
5. In Odin BL slot choose the BL_G93*_DELETE_CACHE.tar and flash phone will reboot to recovery and say processing update then get an error and strart rebooting recovery
6. Let recovery bootloop at least once thin force phone back to download mode
7. In Odin AP slot flash BL_ENTER_ENG_RECOVERY_G93*.tar and flash phone will reboot to recovery with a bunch of red cache errors
8. In recovery choose wipe cache then reboot back to bootloader from recovery
9. In Odin BL slot choose BL_OREO_STOCK_G93*.tar for Oreo or BL_RESET_DM_VERITY_G93*.tar for Nougat and flash
10. This is important as soon as odin is done flashing and phone powers off immediately hold buttons to force phone to recovery
11. When phone reboots to recovery you will get no command error then when phone shows recovery options in black box at very botton it should say Successfully verified. If it says unsuccessful or failed then start at number 5 again. If successful and on oreo you are done.
12. If on Nougat and successful from recovery reboot to bootloader in Odin BL slot flash BL_NOUGAT_STOCK_G93*.tar
To Reroot Your Phone
1. Reboot to download in Odin AP slot flash AP_ROOT_G93***.tar
2. Phone will reboot then will reboot one more time and you will be rerooted
To Enter TWRP When Rooted
Remember with Nougat TWRP cannot mount data because of encryption so some zips wont work
1. Manually reboot phone to recovery launch Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder and choose Option(1) Launch TWRP
2. To Exit TWRP simply choose reboot
To Enter TWRP When Unrooted
Remember with Nougat TWRP cannot mount data because of encryption so some zips wont work
1. Put phone in download mode In Odin AP slot flash AP_ROOT_G93***.tar force phone to reboot to recovery. If you let phone boot it will reroot and you will have to run the unroot from the root control app.
2. In recovery launch Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder and choose Option(1) Launch TWRP.
3. Do whatever you need too do
4. To exit Twrp choose reboot to Download
5. In Odin BL slot choose the BL_G93*_DELETE_CACHE.tar and flash phone will reboot to recovery and say processing update then get an error and strart rebooting recovery
6. Let recovery bootloop at least once thin force phone back to download mode
7. In Odin AP slot flash BL_ENTER_ENG_RECOVERY_G93*.tar and flash phone will reboot to recovery with a bunch of red cache errors
8. In recovery choose wipe cache then reboot back to bootloader from recovery
9. In Odin BL slot choose BL_OREO_STOCK_G93*.tar for Oreo or BL_RESET_DM_VERITY_G93*.tar for Nougat and flash
10. This is important as soon as odin is done flashing and phone powers off immediately hold buttons to force phone to recovery
11. When phone reboots to recovery you will get no command error then when phone shows recovery options in black box at very botton it should say Successfully verified. If it says unsuccessful or failed then start at number 5 again. If successful and on oreo you are done.
12. If on Nougat and successful from recovery reboot to bootloader in Odin BL slot flash BL_NOUGAT_STOCK_G93*.tar

Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good

Thank you sir. Amazing is you, works great much better than safestrap and much easier to get into and out of. I hope one day im able to return the favor and help you out with something to make your life easier as you have done with countless people, much appreciated

Thank you so much for all the work you have done here and for injecting this phone with a much needed revitalization.
Now for the first dumb question, what can be flashed? ROMs? Custom Kernel? (Nethunter?) Any idea would ve helpful. Thanks again!

how to know that which version v4 or v8 on are we?

Rehan Ul Hsaan said:
how to know that which version v4 or v8 on are we?
Click to expand...
Click to collapse
The bootloader version is the 5th to last number in the build version
G935XXXX4XXXX
Sent using some kind of device I modified

gdfdedh8d said:
Thank you so much for all the work you have done here and for injecting this phone with a much needed revitalization.
Now for the first dumb question, what can be flashed? ROMs? Custom Kernel? (Nethunter?) Any idea would ve helpful. Thanks again!
Click to expand...
Click to collapse
No custom boot.img can be flashed
Sent using some kind of device I modified

jrkruse said:
The bootloader version is the 5th to last number in the build version
G935XXXX4XXXX
Sent using some kind of device I modified
Click to expand...
Click to collapse
i thinks i updated to "G935TUVS8CRJ1" can i be flash on it?

Quick question. I just used this method to root my phone (v4 bootloader, CRI2 firmware if I'm reading it right). I had been looking at the post [Rom][ALL+CARRIERS_CRF1][Stock_Oreo_Hybrid][Safestrap_Preinstalled]. That one seemed like a good deal because of the followup post on Safestrap flashable zips, like Xposed framework, Extreme Debloater, Dual Speaker, etc....
I didn't consider that ROM because of the big warning Must Be On Stock CRF1, whereas I'm on CRI2 and this looked nicer anyway.
So, just to be sure I understand, now that I've used this method to root my phone I can install all those things and more by using this technique to get into TWRP on my phone. Correct? Further, I can use TWRP in this way to flash anything except a custom bootloader. Yes?
More specifically, all those ROMs listed over in the general Tools Samsung Galaxy S7 Edge ROMs, Kernels, Recoveries, & Other Development forum that say "for G9350 only", I can use this TWRP to flash those on my G935T ?? Is that right?

Rehan Ul Hsaan said:
i thinks i updated to "G935TUVS8CRJ1" can i be flash on it?
Click to expand...
Click to collapse
Nope that's v8

jrkruse said:
Nope that's v8
Click to expand...
Click to collapse
My bad luck ?

Rehan Ul Hsaan said:
My bad luck
Click to expand...
Click to collapse
Should have been aware of what you are flashing a bootloader update is always an attempt to patch something. Usually root related. It is never to benefit the user. The first indication to me would have been a 4 version jump in bootloader versions all in one shot. I warned people all along that a bootloader change would come one of these days and kill root. Sprint seen it months ago. Tmobile and Sprint can now have there cozy little relationship with one another. I feel bad for you tmobile people. Remember when tmobile was the friendly carrier in the dev community along with sprint as well now they are the most unfriendly carrier in the dev community.

SailorJoe6 said:
Quick question. I just used this method to root my phone (v4 bootloader, CRI2 firmware if I'm reading it right). I had been looking at the post [Rom][ALL+CARRIERS_CRF1][Stock_Oreo_Hybrid][Safestrap_Preinstalled]. That one seemed like a good deal because of the followup post on Safestrap flashable zips, like Xposed framework, Extreme Debloater, Dual Speaker, etc....
I didn't consider that ROM because of the big warning Must Be On Stock CRF1, whereas I'm on CRI2 and this looked nicer anyway.
So, just to be sure I understand, now that I've used this method to root my phone I can install all those things and more by using this technique to get into TWRP on my phone. Correct? Further, I can use TWRP in this way to flash anything except a custom bootloader. Yes?
More specifically, all those ROMs listed over in the general Tools Samsung Galaxy S7 Edge ROMs, Kernels, Recoveries, & Other Development forum that say "for G9350 only", I can use this TWRP to flash those on my G935T ?? Is that right?
Click to expand...
Click to collapse
Twrp gives you no more options than you had before. You cannot just magically go flashing anything you want just because you have twrp. You can run a stock rom and mod it a little and that is it

How do you know what bootloader you're running?

i can not install this metod .
i have problem with sw. rev check faiL device, can any dody help me & please
i use OS G935TUVS8CRJ1

Does this require the fixes for lag/battery life?

jrkruse said:
Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good
Click to expand...
Click to collapse
im exactly onthis s7 verizon heroltevzw sm g930v latest firmware oreo8.0
v8 bootloader locked:laugh:
can i downgrade and follow your path,s?
if no f9vk it
then time to move on upgrade, please can you recomend me some decent device better/much better than s7 that i can root without bricked it down to paperweight?
thankyou
much appreciated
cheers

omgaruda said:
can i downgrade and follow your path,s?
if no f9vk it
then time to move on upgrade, please can you recomend me some decent device better/much better than s7 that i can root without bricked it down to paperweight?
Click to expand...
Click to collapse
No, if your build number indicates that you're on the v8 bootloader, you're screwed for now. If you like the S7's features, you can grab an Exynos. Those you can root and modify to your heart's content. Plenty of custom ROMs available. It's not too expensive either. It's what I'm going to upgrade to, since I'm tired of this bull with the bootloader, and my glass is cracked anyway. Would probably cost nearly as much to repair as to just buy an Exynos.

S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z this is a trojan

Ihavetodothis said:
S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z this is a trojan
Click to expand...
Click to collapse
That's a false positive by a single antivirus program. VirusTotal gives it clean on 54 out of 56 antivirus programs, and one of those is merely "suspicious," probably because it's a rooting tool.