Develop Bugs

[ROOT][UNROOT][CWM RECOVERY][STOCK KERNEL][STOCK RECOVERY] Google ADT-1 Android TV

Hello All,
Root
If on stock, uprooted (ever), go to method 1. If not, keep reading.
Now, in the latest Molly CF-AutoRoot, it flashes a modified kernel to gain root that causes OTA updates (i.e. impending 5.0.1) to fail, this was due to the fact that until a couple days ago, the modified kernel was necessary. Chainfire found a way to fix it without modifying the kernel and implemented it in SuperSU 2.37. If you are rooted, used CF-Auto Root, and wish to retain root, but regain the stock kernel for OTA's, simply follow root method 2.
Method 1
To Root from stock LPX13D, Download the following attached files and place them on your desktop (important):
- CWR_MOLLY_LPDX13D.img
- UPDATE-SuperSU-v2.37.zip
1. Install ADB on your system using: http://forum.xda-developers.com/showthread.php?t=2588979
2. Plug in your USB Keyboard to the back of your ADT-1
3. Enter the settings app on your ADT-1, go to "About" ==> "Build Number", and tap multiple times until it says "No need, you are already a developer. Exit this menu and you should now see a "Developer Options" menu, select it and check "Enable USB Debugging" and confirm your choice.
4. Go to Settings ==> Security, and check allow apps from unknown sources, confirm your choice.
5. (On PC) Plug in your ADT-1 and open a PowerShell (or CMD Prompt) and issue the command "Adb devices, and verify that your ADT-1 shows up as "device" and not "offline", if offline, reinstall ADB/Check your USB connection, then run "cd desktop"
6. Now run the command "adb reboot bootloader"
7. Run "Fastboot devices" to verify your ADT-1 is connected.
8. Here you have an option... if you want to be able to unroot and take OTA's, Run "Fastboot boot cwm_molly_recovery_lpx13d.img", as this will just boot CWM once, leaving the stock recovery in place or if you want a permanent custom recovery, run "fastboot flash recovery cwm_molly_recovery_lpx13d.img", but beware, no OTA's without stock recovery!
9. (On the ADT-1) Using your USB keyboard, use the down arrow key to select "install zips"
10. Select "Install Zip from sideload"
11. (On PC) run "adb sideload UPDATE-SuperSU-v2.37.zip"
12. (On ADT-1) Select "**Go Back**"
13. Select "Reboot to system"
14. Select "No" when asked to restore Root, as this's feature does not work yet.
15. Profit!
Method 2
To Root from CF-auto rooted LPX13D and regain stock kernel (This will not restore Build.prop and other system changes!), Download the following attached files and place them on your desktop (important):
- CWR_MOLLY_LPDX13D.img
- UPDATE-SuperSU-v2.37.zip
- stockbootlpx13d.img
1. Install ADB on your system using: http://forum.xda-developers.com/showthread.php?t=2588979
2. Plug in your USB Keyboard to the back of your ADT-1
3. Enter the settings app on your ADT-1, go to "About" ==> "Build Number", and tap multiple times until it says "No need, you are already a developer. Exit this menu and you should now see a "Developer Options" menu, select it and check "Enable USB Debugging" and confirm your choice.
4. Go to Settings ==> Security, and check allow apps from unknown sources, confirm your choice.
5. (On PC) Plug in your ADT-1 and open a PowerShell (or CMD Prompt) and issue the command "Adb devices", and verify that your ADT-1 shows up as "device" and not "offline", if offline, reinstall ADB/Check your USB connection, then run "cd desktop"
6. Now run the command "adb reboot bootloader"
7. Run "Fastboot devices" to verify your ADT-1 is connected
8. Run "fastboot flash boot stockbootlpx13d.img"
9. Here you have an option... if you want to be able to unroot and take OTA's, Run "Fastboot boot cwm_molly_recovery_lpx13d.img", as this will just boot CWM once, leaving the stock recovery in place or if you want a permanent custom recovery, run "fastboot flash recovery cwm_molly_recovery_lpx13d.img", but beware, no OTA's without stock recovery! Then you must run "fastboot reboot recovery"
10. (On the ADT-1) Using your USB keyboard, use the down arrow key to select "install zips"
11. Select "Install Zip from sideload"
12. (On PC) run "adb sideload UPDATE-SuperSU-v2.37.zip"
13. (On ADT-1) Select "**Go Back**"
14. Select "Reboot to system"
15. Select "No" when asked to restore Root, as this's feature doe snot work yet.
16. Profit!
Unroot
Requirements:
- stockbootlpx13d.img
- recovery.img
1. Enter the SuperSU app, and go to Settings ==> Full Uproot, and verify your choice. (Stop here if you didn't use CF-auto root)
2. Plug your ADT-1 into your PC and run the command "cd desktop", then "adb reboot bootloader", then "fastboot flash boot stockbootlpx13d.img"
3. Run "fastboot flash recovery recovery.img"
4. Then "fastboot reboot"
5. Un-Profit!
To take an OTA Update
If you followed this guide correctly, just unroot from within SuperSU as shown in Step 1. Of the unroot section. It will leave you 100% stock. Then take the OTA.
Downloads
Stock Boot Image LPX13D (stockbootlpx13d.img): https://www.dropbox.com/s/vayt67s513v9z8u/stockbootlpx13d.img?dl=0
Stock Recovery Image LPX13D (recovery.img): https://www.dropbox.com/s/yqu6lhuvzcz2rsu/recovery.img?dl=0
CWM Recovery Img (cwm_molly_recovery_lpx13d.img): https://www.dropbox.com/s/8evaum04mv843dp/cwm_molly_recovery_lpx13d.img?dl=0
SuperSU 2.37.zip: http://download.chainfire.eu/636/SuperSU/UPDATE-SuperSU-v2.37.zip
Optional: Install Leanback Launcher from here to allow launching sideloaded apps: https://play.google.com/store/apps/details?id=eu.chainfire.tv.sideloadlauncher&hl=en
Happy Modding!
Credits:
Chainfire: The super amazing SuperSU, and the awesome CF-Auto Root, thank him!
GTAVHacker: Used CWM Recovery Image as a base, thank him!
Myself: Stock Images, and the guide.

npjohnson said:
CWM Recovery (cwr_molly_recovery_lpx13d.img): https://www.dropbox.com/s/yqu6lhuvzcz2rsu/recovery.img?dl=0
Click to expand...
Click to collapse
Thanks for this! Should the file on dropbox be named cwr_molly...? When I go to the download it simply says recovery.img.

good work
This is awesome, thanks for sharing, I'd really like to see TWRP ported as well, they allow OTA installs/mtp, adb sideloads & more, this is a great step in the direction of seeing custom roms

OP download links updated. My apologies.

Well, TWRP didn't have mouse/keyboard support last I checked. So I'll work with it. But Philz Touch recovery or cannibal open touch should be both cool and doable.
Edit: TWRP has mouse & keyboard support and is possible, but requires a bit more work than is worth it right now.
CWM also has iffy support for OTA's I am finding, hit or miss, try at your own risk.
CWM also has the ADB sideload ability...... that's how you have to flash the SuperSU mentioned in the OP

I cant seem to get this to work. I tried using just the boot option and it just reboots into the bootloader. I tried the flash as well and recovery never boots. Any chance the problem is that this is for the ADT1 (molly) and not the Nexus Player (Fugu)?

The title of the post indicates ADT-1. You need to make sure any modification you do is appropriate for the device you have. The ADT-1 uses and Android processor/chip set while the Nexus Player uses an Intel processor/chip set.

Is there not a subforum for the adt1?

hmmmm CWM

jscat1 said:
Is there not a subforum for the adt1?
Click to expand...
Click to collapse
No there is not! I know, it sucks, but until that changes, looks like we are setting up shop on the fugu forums. XD

thanks so much for this. the ADT-1 needs more love on xda

twrp
if you guys could work on twrp that would be awesome, I plan on working on a rom with my kernel soon, for now check out my kernel and let me know how it runs in origin dev section

defconoi said:
if you guys could work on twrp that would be awesome, I plan on working on a rom with my kernel soon, for now check out my kernel and let me know how it runs in origin dev section
Click to expand...
Click to collapse
Thanks man. TWRP is actually gonna be more than it is worth. CWM should work just fine, it actually has better support for keyboard.
I'll mess with it. Did you build the kernel with the ADT-1 and x86 architecture in mind?

defconoi said:
if you guys could work on twrp that would be awesome, I plan on working on a rom with my kernel soon, for now check out my kernel and let me know how it runs in origin dev section
Click to expand...
Click to collapse
might work on getting twrp for for the adt-1 with mouse and keyboard support.
just received mine tuesday.
has anyone created repos for this device yet?

mkaymuzik said:
might work on getting twrp for for the adt-1 with mouse and keyboard support.
just received mine tuesday.
has anyone created repos for this device yet?
Click to expand...
Click to collapse
Haha. Sadly no. I had a partially working tree until gtvhacker posted a fully functional CWM. I gave up after that. You should pry ask him, if he gives you access could you shoot the links over to me? My partially working tree has been the only reason I haven't built CM yet. It fails mid way through compilation.

npjohnson said:
Haha. Sadly no. I had a partially working tree until gtvhacker posted a fully functional CWM. I gave up after that. You should pry ask him, if he gives you access could you shoot the links over to me? My partially working tree has been the only reason I haven't built CM yet. It fails mid way through compilation.
Click to expand...
Click to collapse
im working on a new tree. open to anyone to contribute and add things. created a github organization for this purpose
https://github.com/adt1-dev
PS: im new to this and learning on the way.
Edit: are your sources on github?

npjohnson said:
Haha. Sadly no. I had a partially working tree until gtvhacker posted a fully functional CWM. I gave up after that. You should pry ask him, if he gives you access could you shoot the links over to me? My partially working tree has been the only reason I haven't built CM yet. It fails mid way through compilation.
Click to expand...
Click to collapse
If you're referring to the builds I released on GTVHacker forums for CWM recovery on the ADT-1, I didn't build the kernel or use any Android TV or ADT-1 source (it wasn't even available when I had started). I just used generic CM Android 4.4, reused the kernel and fstab from the stock ADT-1 recovery, and made a few changes to the default generic BoardConfig.mk.

Any plans on making recovery for nexus player? Just curious

Can someone direct me to a stock copy of a (full) build.prop from LRX22G? I think my build.prop is incorrect (long story, let's just say the LRX22G OTA did not go smoothly for me) and I want to just flush it and replace it with a "clean" one?
Thanks

illuminerdi said:
Can someone direct me to a stock copy of a (full) build.prop from LRX22G? I think my build.prop is incorrect (long story, let's just say the LRX22G OTA did not go smoothly for me) and I want to just flush it and replace it with a "clean" one?
Thanks
Click to expand...
Click to collapse
You can just download the factory image and extract it. Here is a little tutorial if you are unsure how to extract.

Working method to root the LG G4S (Model H735 / "LG G4 Beat")

Root your LG G4S (Model H735)
Tested on Andriod 5.1.1.
Thanks goes to @konsolen for sharing the method to open up the port (see appendix in this post) and to @dominik-p for his guide to determine dd parameters (you won't need this to root with the method described, but you can back up your phone if you're worried). And most importantly, thanks to the author of SuperSU for his excellent script updater-binary which worked pretty much out of the box, with only a few workarounds needed (which is what the instructions below do).
First, a few general notes:
The supersu.zip included in this package is version 2.46.
SuperSU can be downloaded here: http://download.chainfire.eu/supersu
If you want to use a new version, just put the zip file in this directory and rename it to "supersu.zip" (delete the old one in this package first of course).
The busybox binary in this package was used successfully to unzip in the LG G4s H735 (Android 5.1.1).
Some time it should maybe be ensured that this is the newest version. Same holds for Send_Command.exe and adb.exe (and attached libraries).
This script uses the "update-binary" script of the SuperSU package to install it on your phone.
The scripts I attached prepare for it to be called (hopefully) successfully.
Instructions to root
Preparation
You MAY want to create a backup of your system beforehand, in case things go wrong.
This is optional, so if you don't want to do this, you may still rely on the .kdz file (see Appendix below) to restore your phone if things go wrong.
You need to calculate the dd parameters and then backup your system partition into a .img file.
There is an excellent guide by @dominik-p for how to determine your individual dd parameters:
http://forum.xda-developers.com/g4/help/how-to-determine-dd-parameters-lg-g4-t3184867
Keep a copy of your system.img somewhere safe, you can use it to restore
your system if something goes wrong.
Enabling developer options and getting the tools
First, enable developer / debugging mode on your phone:
Navigate to Settings > About Phone > scroll to the bottom > tap Build number seven (7) times.
You'll get a short pop-up in the lower area of your display saying that you're now a developer.
Then, go back and now access the Developer options menu, check 'USB debugging' and click OK on the prompt.
Note: You have to enable USB debugging before plugging your device in to the computer. Unplug device then try to enable USB debugging.
On your computer, install Install and Use ADB (the Android Debug Bridge Utility). Also, download LG Flash Tool.
You can find out how to do both by searching google for it.
Step 1.
Connect your phone via USB (not in download mode yet, just normal).
Then, run Init_Root.bat in order to copy the essential files over to internal storage.
You may do this either by 1) double clicking the file, or 2) executing it from the windows command line.
For Option 2): Open a command line in the folder where you extracted this package. To do this, hold shift while right clicking in the folder opened in the Windows Explorer and select "Open command window here". Then, type
Init_Root.bat
Step 2.
Reboot your phone in download mode and ensure it has opened the port to send commands in download mode.
The port is open if it's displayed on the phone's screen in green letters, like
COMX
(with a number instead of X).
On my LG H735 it was necessary to use "LG Flash Tool 2014" http://lgflashtool.com/ to open the port. So if you don't have the green letters, see instruction pasted below (appendix) on how to open the port.
Step 3.
Open a command line in the folder where you extracted this package. To do this, hold shift while
right clicking in the folder opened in the Windows Explorer and select "Open command window here".
Open a command shell to your phone by typing (replace X with the number displayed on your phone) by typing:
Send_Command \\.\COMX
You should be set to root if the following works:
Typing "ls" returns a long list of file and folder names.
Typing "id" should give you someting like that:
uid=0(root) gid=0(root) context=u:r:recovery:s0
The important bits are the "(root)" uid and gid.
If any of the above is not the case, it will not work, you may search for help in the forum.
Step 4.
Execute the commands below (without the numbering of course).
1. mv /data/local/tmp/busybox /sbin/busybox
2. chmod 755 /sbin/busybox
3. mkdir /tmp
4. mkdir /tmp/supersu
5. /sbin/busybox unzip /data/local/tmp/supersu.zip -d /tmp/supersu
6. mv /data/local/tmp/supersu.zip /tmp/supersu/
7. sh /tmp/supersu/META-INF/com/google/android/update-binary dummy 1 /tmp/supersu/supersu.zip
(Note: Not all commands above may be needed, but this is the conservative approach)
Recommended:
Do sanity checks to see if it's doing its job as expected.
After command 2, type the command ls -l /sbin/busybox to check for sanity.
It must return a line like this (with your own date and time):
-rwxr-xr-x shell shell 1048328 <date> <time> busybox
Command 5 must print several lines containing "inflating" messages, similar to this:
Archive:
inflating: META-INF/MANIFEST.MF
...
Command 7 prints lines like this, and other status messages afterwards:
**************
SuperSU installer
**************
...
Step 5.
Your phone should now be rooted if it all worked ok.
You may now type
LEAVE
to reboot your phone.
Happy rooting!
Troubleshooting
If it doesn't work, for example you phone may be stuck on the boot process displaying the LG logo, then you can use Flash Tool to restore your phone. Use instructions below (how to boot the phone into download mode), but don't pull the USB cable, and just let it run its course. This should restore your phone.
If for some reason this hasn't worked, you may try to "dd" back your system .img which you may have created in the preparation step.
Appendix
How to boot the phone into download mode and open the port
a) Boot the LG G4s in download mode. To do this, first switch it off completely and disconnect USB cable. Then, hold the Volume Up button, and while you keep holding it, plug in the USB cable.
b) Start the LG Flash tool and load the .kdz for your phone. We won't actually complete the flashing, you only need it to start the process, but you should use the kdz for your phone nonetheless.
You can check for your kdz on this link, pasting your IMEI instead of YOUR-IMEI in the link below.
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=YOUR-IMEI
I did not find any for mine there, but I did find it on
http://devtester.ro/projects/lg-firmwares/
Which brought me to this link where I could find mine:
http://pkg02.azure.gdms.lge.com/dn/downloader.dev?fileKey=FW703UV132GQAUP7A0ED99N/H73510c_00.kdz
c) Now this is very important: Watch your phone while the .kdz is being flashed by the flash tool.
(the flash tool may complain about error connecting to the update server, but you can ignore this with "ok").
As soon as the green letters show up, UNPLUG THE USB CABLE!
The percentage on your phone has to be 0% still (never mind about percentage in the flash tool, it may not even display it).
Then, kill the Flash Tool with the Windows Task Manager (Ctrl+alt+delete).
When it's closed, you can plug your phone back in.
It's now in download mode with open port.

You may also be interested in optimizing your storage & memory after you have rooted:
http://forum.xda-developers.com/general/general/moving-apps-to-sd-optimize-memory-phone-t3248125

LG-H731 Vigor from Videotron/Virgin Mobile
jen.magnolis said:
Root your LG G4S (Model H735)
Tested on Andriod 5.1.1.
Click to expand...
Click to collapse
Also work on phone listed in title:
LG-H731 (LG G4) Vigor from Videotron/Virgin Mobile
Happy rooting
If you need help, don't hesitate to contact me: [email protected] or here =

Hi
jen.magnolis said:
Root your LG G4S (Model H735)
Tested on Andriod 5.1.1.
Thanks goes to @konsolen for sharing the method to open up the port (see appendix in this post) and to @dominik-p for his guide to determine dd parameters (you won't need this to root with the method described, but you can back up your phone if you're worried). And most importantly, thanks to the author of SuperSU for his excellent script updater-binary which worked pretty much out of the box, with only a few workarounds needed (which is what the instructions below do).
First, a few general notes:
The supersu.zip included in this package is version 2.46.
SuperSU can be downloaded here: http://download.chainfire.eu/supersu
If you want to use a new version, just put the zip file in this directory and rename it to "supersu.zip" (delete the old one in this package first of course).
The busybox binary in this package was used successfully to unzip in the LG G4s H735 (Android 5.1.1).
Some time it should maybe be ensured that this is the newest version. Same holds for Send_Command.exe and adb.exe (and attached libraries).
This script uses the "update-binary" script of the SuperSU package to install it on your phone.
The scripts I attached prepare for it to be called (hopefully) successfully.
Instructions to root
Preparation
You MAY want to create a backup of your system beforehand, in case things go wrong.
This is optional, so if you don't want to do this, you may still rely on the .kdz file (see Appendix below) to restore your phone if things go wrong.
You need to calculate the dd parameters and then backup your system partition into a .img file.
There is an excellent guide by @dominik-p for how to determine your individual dd parameters:
http://forum.xda-developers.com/g4/help/how-to-determine-dd-parameters-lg-g4-t3184867
Keep a copy of your system.img somewhere safe, you can use it to restore
your system if something goes wrong.
Step 1.
Connect your phone via USB (not in download mode yet, just normal).
Then, run Init_Root.bat in order to copy the essential files over to internal storage.
You may do this either by 1) double clicking the file, or 2) executing it from the windows command line.
For Option 2): Open a command line in the folder where you extracted this package. To do this, hold shift while right clicking in the folder opened in the Windows Explorer and select "Open command window here". Then, type
Init_Root.bat
Step 2.
Reboot your phone in download mode and ensure it has opened the port to send commands in download mode.
The port is open if it's displayed on the phone's screen in green letters, like
COMX
(with a number instead of X).
On my LG H735 it was necessary to use "LG Flash Tool 2014" http://lgflashtool.com/ to open the port. So if you don't have the green letters, see instruction pasted below (appendix) on how to open the port.
Step 3.
Open a command line in the folder where you extracted this package. To do this, hold shift while
right clicking in the folder opened in the Windows Explorer and select "Open command window here".
Open a command shell to your phone by typing (replace X with the number displayed on your phone) by typing:
Send_Command \\.\COMX
You should be set to root if the following works:
Typing "ls" returns a long list of file and folder names.
Typing "id" should give you someting like that:
uid=0(root) gid=0(root) context=u:r:recovery:s0
The important bits are the "(root)" uid and gid.
If any of the above is not the case, it will not work, you may search for help in the forum.
Step 4.
Now you have two options:
#Step 4, Option 1 (recommended to try)
Just run the script and you should be done.
Type:
sh root_lgh735.sh
The script contains all commands I (and other people) used to successfully root the phone.
However we have all used option (2) below, so the script itself has not been tested yet,
though it's very simple (feel free to open it with a text editor to look at it).
You can try to run it, and if it's not doing what's expected you can still go to Option 2
and fix things up.
It will have worked if:
It prints several lines containing "inflating" messages, similar to this:
Archive:
inflating: META-INF/MANIFEST.MF
...
It prints 3 lines like this, and other status messages afterwards:
**************
SuperSU installer
**************
....
If it has done that, reboot your phone and you should be set.
If not, do the commands manually as in Option 2.
Please: If the script worked for you, report it in this thread, so I can simplify these instructions here! Thanks for your help :cyclops:
#Step 4, Option 2:
Execute the commands directly (proven to work on several phones).
Type the commands below (without the numbering of course).
1. mv /data/local/tmp/busybox /sbin/busybox
2. chmod 755 /sbin/busybox
3. mkdir /tmp
4. mkdir /tmp/supersu
5. /sbin/busybox unzip /data/local/tmp/supersu.zip -d /tmp/supersu
6. mv /data/local/tmp/supersu.zip /tmp/supersu/
7. sh /tmp/supersu/META-INF/com/google/android/update-binary dummy 1 /tmp/supersu/supersu.zip
(Note: Not all commands above may be needed, but this is the conservative approach)
Recommended:
Do sanity checks to see if it's doing its job as expected.
After command 2, type the command ls -l /sbin/busybox to check for sanity.
It must return a line like this (with your own date and time):
-rwxr-xr-x shell shell 1048328 <date> <time> busybox
Command 5 must print several lines containing "inflating" messages, similar to this:
Archive:
inflating: META-INF/MANIFEST.MF
...
Command 7 prints lines like this, and other status messages afterwards:
**************
SuperSU installer
**************
...
Step 5.
Your phone should now be rooted if it all worked ok.
You may now type
LEAVE
to reboot your phone.
Happy rooting!
Troubleshooting
If it doesn't work, for example you phone may be stuck on the boot process displaying the LG logo, then you can use Flash Tool to restore your phone. Use instructions below (how to boot the phone into download mode), but don't pull the USB cable, and just let it run its course. This should restore your phone.
If for some reason this hasn't worked, you may try to "dd" back your system .img which you may have created in the preparation step.
Appendix
How to boot the phone into download mode and open the port
a) Boot the LG G4s in download mode. To do this, first switch it off completely and disconnect USB cable. Then, hold the Volume Up button, and while you keep holding it, plug in the USB cable.
b) Start the LG Flash tool and load the .kdz for your phone. We won't actually complete the flashing, you only need it to start the process, but you should use the kdz for your phone nonetheless.
You can check for your kdz on this link, pasting your IMEI instead of YOUR-IMEI in the link below.
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=YOUR-IMEI
I did not find any for mine there, but I did find it on
http://devtester.ro/projects/lg-firmwares/
Which brought me to this link where I could find mine:
http://pkg02.azure.gdms.lge.com/dn/downloader.dev?fileKey=FW703UV132GQAUP7A0ED99N/H73510c_00.kdz
c) Now this is very important: Watch your phone while the .kdz is being flashed by the flash tool.
(the flash tool may complain about error connecting to the update server, but you can ignore this with "ok").
As soon as the green letters show up, UNPLUG THE USB CABLE!
The percentage on your phone has to be 0% still (never mind about percentage in the flash tool, it may not even display it).
Then, kill the Flash Tool with the Windows Task Manager (Ctrl+alt+delete).
When it's closed, you can plug your phone back in.
It's now in download mode with open port.
Click to expand...
Click to collapse
Have twpr or cwm recovery to install xposed??

I can confirm is working on LG G4 LG-H735P (Latin America version), thanks!

anyone tried updating? just got a system update notification from my phone lol dk if i should update now or not

Good question! I didn't try it yet. Think it should be ok, but if it isn't, you can just root again I guess

jen.magnolis said:
Good question! I didn't try it yet. Think it should be ok, but if it isn't, you can just root again I guess
Click to expand...
Click to collapse
oh.. it wont like brick or anything? :/

dclarkg said:
I can confirm is working on LG G4 LG-H735P (Latin America version), thanks!
Click to expand...
Click to collapse
I could not root my phone, what kdz file did you use??

Backup problems
Hello,
Coming from a Nexus 4, I bought a G4S last month.
I want to do my first root in order to manage the storage, like jen.magnolis talked about.
In case of a problem (bootloop or brick), I need to be able to restore. I don't really mind about restoring my datas, a factory reset would be enough.
But I don't undestand how i can get the system.img without being rooted ? It seems that I can get a "backup.ab" file using adb. Will it be enough to restore in case of brick ?
I also looked about kdz files, but mine doesn't seem to be available. I have a LGH735 (buyer = FRA, suffix = AFRATS, ...). Will it work if I use the one you provided in your post ?
Thanks for your help !

dclarkg said:
I can confirm is working on LG G4 LG-H735P (Latin America version), thanks!
Click to expand...
Click to collapse
I got the same model phone, but I can't find the .KDZ file for it anywhere. Could you post a link to the one you used please?

Excellent step-by-step guide. Should set an example for other "step-by-step guides" which exclude crucial information ("everybody knows lösfhgaeilurhg has to by typed between these steps here, I shall not mention it" )
Thanks a ton Worked on my LG G4S a.k.a H735 like a charm.
Cheers!

dreamnoob said:
anyone tried updating? just got a system update notification from my phone lol dk if i should update now or not
Click to expand...
Click to collapse
jen.magnolis said:
Good question! I didn't try it yet. Think it should be ok, but if it isn't, you can just root again I guess
Click to expand...
Click to collapse
"phone appears to be rooted, will not be updated" - Hiding root did not help, any simple suggestions but total unrooting?
Wanted to upgrade from 10c to 10d...
Cheers!

Doubts.
Hi everyone!
I just cant find my .kdz file! The phone i want to root its a G4 H735AR, im wondering if there are some compatible .kdz that i can use. Im affraid it might get bricked or something...
BTW i¨ve tried the rootworm.bat method and it didnt work. And when i try to open the COMX port, the lg flash tool always crushes and shuts down.

Works!
ascfzz said:
Hi everyone!
I just cant find my .kdz file! The phone i want to root its a G4 H735AR, im wondering if there are some compatible .kdz that i can use. Im affraid it might get bricked or something...
BTW i¨ve tried the rootworm.bat method and it didnt work. And when i try to open the COMX port, the lg flash tool always crushes and shuts down.
Click to expand...
Click to collapse
So, i made it! It works in the H735AR!! The problem with the flash tool was that i was trying to use it without any KDZ file!! I've used @konsolen .kdz and achieved to open ports, and then continue with the rest of the tutorial without trouble.
Thank you so much! Its a great phone, but with so little internal memory is a waste.

chw9999 said:
"phone appears to be rooted, will not be updated" - Hiding root did not help, any simple suggestions but total unrooting?
Wanted to upgrade from 10c to 10d...
Cheers!
Click to expand...
Click to collapse
ya u just update thru lg bridge.. once updated it will be unroot tho so u have to root it back same method as u did before.. and if you use link2sd it dosent matter after root ur link2sd can just reboot and re-read ur partition without needing to wipe and re-partition

It's working in H736P! Thank you só much!
Enviado de meu LG-H736 usando Tapatalk

For people in Brazil that has H736P, to open ports, is necessary the kdz file to use in LG Flash Tool.
Galera do Brasil, consegui rootear o LG G4 Beat usando esse tutorial porém tive que baixar o arquivo kdz pro H736P pra executar o LG Flash Tool. Cuidado ao usar o LG Flash Tool, assim que aparecer a porta COM na tela do telefone, arranca o cabo USB do computador.
Enviado de meu LG-H736 usando Tapatalk

friend you are from argentina?¿

maxiret said:
friend you are from argentina?¿
Click to expand...
Click to collapse
Brasil.
Enviado de meu LG-H736 usando Tapatalk

[ROOT - ZS570KL] ZenUtil + everything you need to root the Z016D quickly and easily!

ZenUtil was created for use with the Zenfone 3 Deluxe Special Edition ONLY.
Hello everyone my name is Sandman45654. I would like to share a little root utility I put together in my free time over the last couple of weeks. After not having much luck with the root packages/images I found here on XDA and the internet in general I decided to create my own solution! ZenUtil was created specifically for the Zenfone 3 Deluxe Special Edition (SD821) and has been tested on seven different computers. Four physical and three virtual machines. Operating systems from Windows 7 through the latest Windows 10 build have all been tested. Two machines even had fresh Windows installations with no prior ADB driver installations and Wi-Fi set to disabled to ensure drivers were in fact installing and not downloading! This package includes EVERYTHING to get the job done quickly and easily!
Screenshots:
View attachment 4270854 View attachment 4270855 View attachment 4270856
View attachment 4270857 View attachment 4270859 View attachment 4270860
Features:
1. Completely menu driven CMD file! Typing or remembering commands is not required.
2. ZenUtil is able to create a support files (help/uninstaller/log files) dynamically.
3. Install Asus ADB Drivers. Fastboot drivers are also installed but not enabled by default. Instructions below.
4. Install the Asus UnlockTool v1.1 onto your phone.
5. Push the SuperSU 2.82 zip file into \sdcard\ in preparation for rooting.
6. Push just about any file or folder, even over network shares into \sdcard\. Supports drag & drop too!
7. Able to boot TWRP 3.1.1-0 without flashing.
8. Able to boot included stock Asus recovery image (v5.15.44.2562) without flashing. Boots upside down for some reason but works.
9. Reboot into the recovery that is currently installed.
10. Reboot into Fastboot mode.
11. Exit out of Fastboot mode. No more holding for power button for days!
12. Able to flash TWRP 3.1.1-0
13. Flash/restore stock Asus recovery image. It does not boot upside down when flashed.
14. Remove any lock screen PIN/Password/Pattern. Useful after restoring a Nandroid and getting "Incorrect PIN" error.
15. ADB transfers are check and verified as either successful or failed.
16. ADB transfers are also logged with date/timestamps and shown automatically on error.
17. The ADB log file is deleted on each launch to keep it small, clean, and simple.
18. Confirms before any "permanent" actions are completed. (Flash / Pin Removal / Uninstall)
19. Maybe more to come...
ZenUtil will be updated with the latest image files for the foreseeable future regardless.
Included files and versions with notes.
ADB Files = 1.4.2 Minimal (Preferred for logging)
Asus Stock Recovery = Z016_1-WW-5.15.44.2562_recovery.img
Asus UnlockTool v1.1 = UnlockTool-9.0.0.29_ZS570KL_PRO.apk
TWRP = twrp-3.1.1-0-Z016-20170826.img
NO LAG ON BOOT with this version of TWRP!!! I was also able to create, wipe, and restore without the issues of previous versions. Might this be the one?!
Finishing Fastboot driver installation.
Your phone must be connected and in fastboot mode before you are able to install the drivers.
1. Right click on the start button and select "Device Manager" or WinKey+R>devmgmt.msc>enter
2. Right click on "Android" with a yellow ! next to it and select "Update driver".
3. Click "Browse my computer for driver software"
4. Click "Let me pick from a list of available drivers on my computer"
5. Select "ASUS Android Device" and click next.
6. Select "ASUS Android Bootloader Interface Version: 8.0.0.3 [3/16/2015]" and click next.
7. Click "Yes"
8. Click "Close"
A HUGE thank you goes out to Judago for creating CmdMenuSel!
Downloads:
Download ZenUtil v1.0
Fastboot Help Files (with pics)

hello
I have the ASUS Zenfone 3 Deluxe ZS570KL (Z016S)
but I can not do it ROOT
if it does HELP

alkis68 said:
hello
I have the ASUS Zenfone 3 Deluxe ZS570KL (Z016S)
but I can not do it ROOT
if it does HELP
Click to expand...
Click to collapse
According to the page below that phone has the Snapdragon 820 and not the 821. So there is high likelihood that this would fail. If the included Twrp is compatible across both phones you could install the bootloader unlock tool from Asus website and then finish rooting with Zenutil. I cannot however say for certain that Twrp would be compatible.
https://www.mobosdata.com/asus-zenfone-3-deluxe-z016s#

Any chance of getting this uploaded again, it's no longer available

Samsung Galaxy Tab 3 7.0 SM-T210 problem

I recently found my old tablet and it had kingoroot installed and then I flashed stock rom to my tablet but now it randomly restarts and every time i try to setup it i got error "Unfortunately, the process com.android.systemui has stopped" and "settings has stopped"
Here is the tutorial I followed:
Code:
The following instructions are for Windows only. Please don't use a virtual machine as these can cause problems communicating with the device. There is an alternative method for Linux or macOS. Just tell me if you aren't on Windows, I can easily change the instructions. Please make sure you have Windows set to display all file extensions. This can really help for debugging purposes.
First we need to download the tool that downloads the stock firmware. It's called SamFirm and it downloads it using Samsung's servers. You can download the latest version [here](http://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462). Please also make sure you have the [Microsoft Visual C++ 2008](https://download.microsoft.com/download/1/1/1/1116b75a-9ec3-481a-a3c8-1777b5381140/vcredist_x86.exe) and [Microsoft Visual C++ 2010](https://download.microsoft.com/download/5/B/C/5BC5DBB3-652D-4DCE-B14A-475AB85EEF6E/vcredist_x86.exe) x86 Redistributable packages installed. Now to download the tool that flashes to the devices different partitions. On most devices you use a tool called fastboot, but Samsung devices aren't like most devices (excluding the Galaxy Nexus). This tool is called Odin, it's Windows only and leaked from Samsung so you need to get it from a trusted source. You can download the latest version [here](https://build.nethunter.com/samsung-tools/Odin_3.12.3.zip). Extract the "Odin_3.12.3.zip" file. You should now have a folder called "Odin_3.12.3". Treat this as your working directory and download all other files to this folder. While you're here, extract the contents of "SamFirm_v0.3.6.zip" into this folder.
Now to download the stock firmware. Open "SamFirm.exe" and make sure "Auto" is checked and "Manual" and "Binary Nature" isn't checked. In "Model" put `SM-T210` and in "Region" put `BTU`. Click "Check Update" and wait for it to find the firmware on the server. Now check "Check CRC32" and "Decrypt automatically". Then click "Download" and save it. Let it finish downloading, checking, and decrypting. Once it finishes you can now close SamFirm. Extract the zip file it gave you. You should now have a single file ending in `.tar.md5` (you may also have `.dll` file, ignore it). This tar.md5 file is your firmware. Do not modify it. If you have more than one .tar.md5 file, tell me.
Now shutdown the device and then hold the Volume Down, Home/Bixby, and Power buttons. This should put the device into download mode. Accept any warnings then plug the device in. Open "Odin.exe" from the "Odin_3.12.3" folder. In the log, it should say `Added!` and have a blue COM thing near the top, meaning it detected your device. If it didn't detect it, then you may need to configure drivers (you can ask me for the drivers if you need them). Click the "Option" tab and make sure "F. Reset Time" and "Auto Reboot" is enabled. Also check the checkbox next to the "AP" button and then click the button. Select the tar.md5 file. Now click "Start" in Odin.
It should now reboot and go to the boot animation. If it doesn't boot in 15 minutes, shutdown the device. Then hold the Volume Up, Home/Bixby, and Power buttons. Then use the keys to select "Factory reset". Please note this will wipe all user data. Once it finishes you can select "Reboot" and now it should boot correctly.
I have been battling with this problem so long I only wanted to root my tablet to have some fun with root required apps
Any help with the problem? I only need to root the device or get it to work with stock rom

Noob Bootloader Unlock Guide: Answers to several questions and solutions to problems.

***Warning: I am not responsible for bricked or broken devices, warranties, computers, etc. This is your phone and your free will to follow the below steps and you bare the full burden of any consequences.***
A note for the Moderators: I am aware that the information I am about to provide exists outside of this thread. The purpose of this is not for redundancy or to clutter the forum. I am making this thread because I had to go to SEVERAL different sources to find these solutions and pull pieces from each. Hopefully, this is comprehensive enough to help someone who may have been in the same boat I was in. This is truly Noob friendly and intended for someone just beginning in the Android community, because of this it is painfully detailed. Hopefully, you will allow it to stay up.
The purpose of this thread is to address several issues I ran into while attempting to unlock my bootloader as well as address questions I personally had that I couldn't find answers to by using myself as the test dummy. Those items are as follow:
1) ADB was not functioning properly with Windows 10.
2) My Windows 10 laptop could recognize my OneTouch 7t in ADB devices but could not recognize it in Fastboot. Windows 10 wouldn't let me install the drivers that come pre-loaded on the OnePlus 7t.
3) After Unlocking the bootloader I hit a "checking info" loop with Google.
4) Does unlocking a bootloader on the OnePlus 7t cause any Safety Net Issues?
5) What does a SafetyNet failure result in?
6) Will every app work with an unlocked bootloader?
Solutions and answers:
1) This is going to be a detailed process but in the end, you'll have universal ADB and fix your windows issues:
If you decide to unlock the bootloader IT WILL WIPE EVERYTHING. This includes photos, apps, music, etc. So start by doing a backup:
-Settings>search "switch">OnePlus Switch>Backup & Restore> New Backup
-Copy that backup folder to your computer by plugging the phone into the computer> settings>search "USB">USB preferences>select file transfer>On your computer open up HD1905>internal shared storage>copy the "opbackup" folder to your computer (this will take a while)
Now to get Developer options:
-On your phone>settings>about phone>Tap build number until it says you are a developer
-Settings>system>developer options>turn on USB debugging
Getting ADB set up on your computer:
-Download and install SDK Platform-Tools for Windows: https://developer.android.com/studio/releases/platform-tools
-on Windows>Open up Command Prompt (run>cmd>enter)>Type sysdm.cpl> hit enter
-Go to the advanced tab in the window that pops up> environment variables>path>new>browse.
-Now find where you installed the SDK platform-tools and select the folder that says "platform-tools"
click ok>ok>ok
Testing ADB:
-Open a new Comand Prompt in Admin mode. To do this Open run type "cmd" and then hit Ctl+Shift+Enter and click ok to the pop-up
-Plug your phone into the computer
-In Command Prompt type "adb devices" and hit enter
-You should now see your phone ID
-Type "adb reboot bootloader" and hit enter
-Your phone will reboot into bootloader
-Type "fastboot devices" and hit enter
-If your ID does not show up go to step 2 without changing anything (ie. stay in Command Prompt with the phone plugged in at the bootloader menu)
2)-This step fixes the driver issue that likely causes problem #1.
Get the newest Android drivers:
-Download and install Android Studio: https://developer.android.com/studio
-Launch Android Studio
-Configure>SDK Manager>SDK Tools>Google USB Driver>Apply>Ok
-At the top, it will say SDK path I highly suggest you copy that or write it down you will need it soon.
-Click Finish and close Android Studio
Installed drivers for fastboot:
-Open any folder and then select "view" at the top of the window and check the box that says hidden files then close the window.
-windows key+x>device manager>right click on the phone with the orange exclamation point>update drivers>browse my computer>browse>go to the folder location>next>finish
If that doesn't work and you get "Windows was unable to install driver" error do the following:
-click search for updated drivers on windows update>a new window will come up> Update and restart your computer
-Once back on and updated>windows key+x>device manager>right click on the phone with the orange exclamation point>update drivers>browse my computer>let me pick from a list>Android Bootloader interface>next>once finished, close the window.
To Test if this fixed the issue:
open an Admin Command Prompt and type "fastboot devices" and hit enter, you should now see your phone's ID.
WARNING: IF YOU DO THE NEXT STEP YOUR PHONE WILL BE FULLY WIPED. ENSURE YOU MADE A BACKUP!!!
Now to unlock the bootloader:
-In Admin Command prompt type "fastboot oem unlock" and hit enter
-On your phone use the volume keys to select "unlock the bootloader" then use the power key to select it.
Congrats your bootloader is now unlocked. Now for the problems you may face once it's back on
3) If you hit the "checking info" Google loop follow these steps:
-Go to Settings> Battery> Battery Saver>Turn off when fully charged>Select OFF,
-Go Settings> Apps&notifications>See All ## Apps>3 Dot menu>Reset app preferences> reset Apps,
-Go Settings> Apps&notifications>See All ## Apps>3 Dot menu>Show System
-----Select Google play store >Storage & cache>Clear Storage
-----Press Back
-----Select Download manager> Storage & cache>Clear Storage
-----Press Back
-----Select Google play services> Storage & cache>Clear Storage>Clear All Data
-Go to Settings >Accounts> Google Account name/ Names> 3 Dot Menu> Remove ALL Accounts
-Restart device
-Connect to Wifi
-Go to Settings >Accounts>Add Account>Google
4) Yes, unlocking your bootloader on the OnePlus 7t results in a "CTS Profile Match=false" failure in SafetyNet
5)From what I can tell this SafetyNet failure doesn't really cause too many issues but time will tell and I will update this accordingly.
6) I tested the known problem children ie. Google pay, PokemonGo, and Snapchat. All were good. The only exception I ran into was Netflix. It will not work with an unlocked bootloader. There may be ways to resolve this but I haven't tried them yet as this is all without Root. I will update this post when I find solutions.
Again I know that most of this can be found but it took me a decent amount of digging. More importantly, a lot of the stuff was implied knowledge that many of us already have but a newcomer wouldn't. Hopefully, this is useful to the new and old alike feel free to ask questions below as I will be continuing to test stuff further.

Saved
Update:
How to fix SafetyNet failure:
Get Root
-Follow this link: https://forum.xda-developers.com/oneplus-7t/how-to/magisk-auto-root-tool-oneplus-7t-pro-t4079355#post82221323
This is hands down the easiest root method I have ever seen for any device. HUGE shoutout to @daxiaamu and @mauronofrio for this!
Install Magisk Manager
On Your phone go to https://github.com/topjohnwu/Magisk/releases/
and download the latest version of Magisk Manager.
Allow unknown sources> install
Update Magisk
Once in Magisk Manager it will prompt you to install some updates for our phone. Install them and let it reboot.
Install Magisk Hide
Open Magisk>Three lines in top left corner>Downloads>MagiskHide Prop Config>download>install
Test
Once your phone has rebooted open Magisk>SafetyNet Check Status>Prosper!
Thank you to the Magisk team for making this hands down the easiest experience I have ever seen on Android and to @daxiaamu for making a truly one-click install that works flawlessly!

This should be pinned, but I have ctsProfile: false.
Is that expected?

lucfig said:
This should be pinned, but I have ctsProfile: false.
Is that expected?
Click to expand...
Click to collapse
If you have the bootloader unlocked, yes. Magisk won't be able to hide the lock/root status from SafetyNet once Google fully rolls out their updates to SafetyNet/Play Services.
https://twitter.com/topjohnwu/status/1251712525843918853
Signing ROMs with custom keys and relocking may be a possibility, but I haven't tested anything on the 7T, and I'm staying locked until official support ends since the days of passing SafetyNet with root/unlocked bootloaders appears to be over.

lucfig said:
This should be pinned, but I have ctsProfile: false.
Is that expected?
Click to expand...
Click to collapse
Thank you, it took a while to write was a little discouraged with the lack of response lol. To fix cts error:
Open Magisk>settings>turn off magisk hide
Magisk>Downloads>MagiskHide Props Config> Download and reboot
Magisk>Settings>Turn on MagiskHide
Test again should be good

C4sp3R911 said:
Thank you, it took a while to write was a little discouraged with the lack of response lol. To fix cts error:
Open Magisk>settings>turn off magisk hide
Magisk>Downloads>MagiskHide Props Config> Download and reboot
Magisk>Settings>Turn on MagiskHide
Test again should be good
Click to expand...
Click to collapse
Hope it gets more visibility, is the most detailed and easy to follow instructions.
I figured that out. Without riru or edxposed the Magisk hide works great.

otto888 said:
If you have the bootloader unlocked, yes. Magisk won't be able to hide the lock/root status from SafetyNet once Google fully rolls out their updates to SafetyNet/Play Services.
https://twitter.com/topjohnwu/status/1251712525843918853
Signing ROMs with custom keys and relocking may be a possibility, but I haven't tested anything on the 7T, and I'm staying locked until official support ends since the days of passing SafetyNet with root/unlocked bootloaders appears to be over.
Click to expand...
Click to collapse
We were able to fix it through MagiskHide. Both methods above worked.

Hey guys, I just received my OP7T today (upgrading from the 5T), and I see that there's no official TWRP yet. I've been looking around to see if it's worth it to root the phone already.
Is the rooting already stable enough, or should I wait a couple more months for full modded roms to come out? 'cause I really enjoy having the root features that some apps offer, but I also definitely need MagiskHide to work so my bank app won't have any issues with the unlocked bootloader.
If the guide above is up to date and working like C4sp3R911 posted, I'd be down to try it today.

Could I still use the the following command if OEM Unlocking is grayed out in Settings? Thanks.
"fastboot flashing unlock"
or
"fastboot OEM unlock"

What?... You need to learn a bit more before messing with bootloader unlocking, fastboot flashing unlock is not a command and will do nothing... Check yourself before you wreck yourself as the saying goes,
If it's greyed out doesn't that mean the BL is already unlocked?

C4sp3R911 said:
***Warning: I am not responsible for bricked or broken devices, warranties, computers, etc. This is your phone and your free will to follow the below steps and you bare the full burden of any consequences.***
A note for the Moderators: I am aware that the information I am about to provide exists outside of this thread. The purpose of this is not for redundancy or to clutter the forum. I am making this thread because I had to go to SEVERAL different sources to find these solutions and pull pieces from each. Hopefully, this is comprehensive enough to help someone who may have been in the same boat I was in. This is truly Noob friendly and intended for someone just beginning in the Android community, because of this it is painfully detailed. Hopefully, you will allow it to stay up.
The purpose of this thread is to address several issues I ran into while attempting to unlock my bootloader as well as address questions I personally had that I couldn't find answers to by using myself as the test dummy. Those items are as follow:
1) ADB was not functioning properly with Windows 10.
2) My Windows 10 laptop could recognize my OneTouch 7t in ADB devices but could not recognize it in Fastboot. Windows 10 wouldn't let me install the drivers that come pre-loaded on the OnePlus 7t.
3) After Unlocking the bootloader I hit a "checking info" loop with Google.
4) Does unlocking a bootloader on the OnePlus 7t cause any Safety Net Issues?
5) What does a SafetyNet failure result in?
6) Will every app work with an unlocked bootloader?
Solutions and answers:
1) This is going to be a detailed process but in the end, you'll have universal ADB and fix your windows issues:
If you decide to unlock the bootloader IT WILL WIPE EVERYTHING. This includes photos, apps, music, etc. So start by doing a backup:
-Settings>search "switch">OnePlus Switch>Backup & Restore> New Backup
-Copy that backup folder to your computer by plugging the phone into the computer> settings>search "USB">USB preferences>select file transfer>On your computer open up HD1905>internal shared storage>copy the "opbackup" folder to your computer (this will take a while)
Now to get Developer options:
-On your phone>settings>about phone>Tap build number until it says you are a developer
-Settings>system>developer options>turn on USB debugging
Getting ADB set up on your computer:
-Download and install SDK Platform-Tools for Windows: https://developer.android.com/studio/releases/platform-tools
-on Windows>Open up Command Prompt (run>cmd>enter)>Type sysdm.cpl> hit enter
-Go to the advanced tab in the window that pops up> environment variables>path>new>browse.
-Now find where you installed the SDK platform-tools and select the folder that says "platform-tools"
click ok>ok>ok
Testing ADB:
-Open a new Comand Prompt in Admin mode. To do this Open run type "cmd" and then hit Ctl+Shift+Enter and click ok to the pop-up
-Plug your phone into the computer
-In Command Prompt type "adb devices" and hit enter
-You should now see your phone ID
-Type "adb reboot bootloader" and hit enter
-Your phone will reboot into bootloader
-Type "fastboot devices" and hit enter
-If your ID does not show up go to step 2 without changing anything (ie. stay in Command Prompt with the phone plugged in at the bootloader menu)
2)-This step fixes the driver issue that likely causes problem #1.
Get the newest Android drivers:
-Download and install Android Studio: https://developer.android.com/studio
-Launch Android Studio
-Configure>SDK Manager>SDK Tools>Google USB Driver>Apply>Ok
-At the top, it will say SDK path I highly suggest you copy that or write it down you will need it soon.
-Click Finish and close Android Studio
Installed drivers for fastboot:
-Open any folder and then select "view" at the top of the window and check the box that says hidden files then close the window.
-windows key+x>device manager>right click on the phone with the orange exclamation point>update drivers>browse my computer>browse>go to the folder location>next>finish
If that doesn't work and you get "Windows was unable to install driver" error do the following:
-click search for updated drivers on windows update>a new window will come up> Update and restart your computer
-Once back on and updated>windows key+x>device manager>right click on the phone with the orange exclamation point>update drivers>browse my computer>let me pick from a list>Android Bootloader interface>next>once finished, close the window.
To Test if this fixed the issue:
open an Admin Command Prompt and type "fastboot devices" and hit enter, you should now see your phone's ID.
WARNING: IF YOU DO THE NEXT STEP YOUR PHONE WILL BE FULLY WIPED. ENSURE YOU MADE A BACKUP!!!
Now to unlock the bootloader:
-In Admin Command prompt type "fastboot oem unlock" and hit enter
-On your phone use the volume keys to select "unlock the bootloader" then use the power key to select it.
Congrats your bootloader is now unlocked. Now for the problems you may face once it's back on
3) If you hit the "checking info" Google loop follow these steps:
-Go to Settings> Battery> Battery Saver>Turn off when fully charged>Select OFF,
-Go Settings> Apps&notifications>See All ## Apps>3 Dot menu>Reset app preferences> reset Apps,
-Go Settings> Apps&notifications>See All ## Apps>3 Dot menu>Show System
-----Select Google play store >Storage & cache>Clear Storage
-----Press Back
-----Select Download manager> Storage & cache>Clear Storage
-----Press Back
-----Select Google play services> Storage & cache>Clear Storage>Clear All Data
-Go to Settings >Accounts> Google Account name/ Names> 3 Dot Menu> Remove ALL Accounts
-Restart device
-Connect to Wifi
-Go to Settings >Accounts>Add Account>Google
4) Yes, unlocking your bootloader on the OnePlus 7t results in a "CTS Profile Match=false" failure in SafetyNet
5)From what I can tell this SafetyNet failure doesn't really cause too many issues but time will tell and I will update this accordingly.
6) I tested the known problem children ie. Google pay, PokemonGo, and Snapchat. All were good. The only exception I ran into was Netflix. It will not work with an unlocked bootloader. There may be ways to resolve this but I haven't tried them yet as this is all without Root. I will update this post when I find solutions.
Again I know that most of this can be found but it took me a decent amount of digging. More importantly, a lot of the stuff was implied knowledge that many of us already have but a newcomer wouldn't. Hopefully, this is useful to the new and old alike feel free to ask questions below as I will be continuing to test stuff further.
Click to expand...
Click to collapse
Just bought the op7t pro and followed your guide step by step, but still fastboot devices does not show nothing to me
Tried in 2 different windows pc with same results, don't know how to do now

Having trouble getting adb setup on my computer. Specifically here:
-Now find where you installed the SDK platform-tools and select the folder that says "platform-tools"
click ok>ok>ok-
In "Environment Variables" popup, I select "path" in the top field, then click "new". The next popup is "New User Variable". Here, I've clicked "Browse Directory", as well as "Browse File", but each time I click platform-tools and click OK, the OK in the "New User Variable" popup is greyed out. I've tried even clicking on a subfolder to platform-tools, just to see if that 2nd OK would be active, but it isn't. Any help is much appreciated.

doncheadlesdriveway said:
Having trouble getting adb setup on my computer. Specifically here:
-Now find where you installed the SDK platform-tools and select the folder that says "platform-tools"
click ok>ok>ok-
In "Environment Variables" popup, I select "path" in the top field, then click "new". The next popup is "New User Variable". Here, I've clicked "Browse Directory", as well as "Browse File", but each time I click platform-tools and click OK, the OK in the "New User Variable" popup is greyed out. I've tried even clicking on a subfolder to platform-tools, just to see if that 2nd OK would be active, but it isn't. Any help is much appreciated.
Click to expand...
Click to collapse
Great. Thanks for the help.