Related
Hi Guys,
I'm sure some of you may have heard about this error before.
Well, here's my sad sad story.
After trying to root my s7 edge,
Everything seems fine.
One day when i re-format my phone, and after which downloaded a few apps, there wasn't any issue at all
However when i restarted my phone, i saw the error msg : Custom Binary block by FRP Lock
And after which it can't boot up anymore.
Anyone of you guys able to help me ?
It'll be much appreciated!
Flash the stock firmware with ODIN
Envoyé de mon SM-G935F en utilisant Tapatalk
Thanks for the reply,
Sorry but I'm new. How do i do that?
pr0cupid said:
Thanks for the reply,
Sorry but I'm new. How do i do that?
Click to expand...
Click to collapse
What model? Country
Sent from my Blackberry Bold
Model : SM-G935FD
Country : Singapore
frp lock s7 edge
pr0cupid said:
Hi Guys,
I'm sure some of you may have heard about this error before.
Well, here's my sad sad story.
After trying to root my s7 edge,
Everything seems fine.
One day when i re-format my phone, and after which downloaded a few apps, there wasn't any issue at all
However when i restarted my phone, i saw the error msg : Custom Binary block by FRP Lock
And after which it can't boot up anymore.
Anyone of you guys able to help me ?
It'll be much appreciated!
Click to expand...
Click to collapse
i have same issue here, did you find any solutions ?
AFAIK when you factory reset your phone etc. if rooted you must remember to go back into Developer Options and re enable OEM Unlocking. This depends on the method you used to root, if you flashed dm-verity then you "May not" have this issue but cannot say for sure.
If it is already too late for you then I think you need to flash stock via Odin, plenty of threads out there on where to find the firmware (SamMobile) and how to do it. Even a quick google of the error gave me plenty of results...
One thing I have read is that you may have to keep trying to get your phone into download mode as the timing is much stricter with this error message.
I've the same problem with my g935x blocked on FRP when ii treid to root if any one can help .plz
https://drive.google.com/file/d/0B4sLrKlVs0CPQTBaamduLXdNYW8/view?usp=sharing
wHEN THE PHONE INICIALIZES PUT THIS FILE IN A OTG pendrivve install and do the reset by the menu of the phone.
djluisbento said:
https://drive.google.com/file/d/0B4sLrKlVs0CPQTBaamduLXdNYW8/view?usp=sharing
wHEN THE PHONE INICIALIZES PUT THIS FILE IN A OTG pendrivve install and do the reset by the menu of the phone.
Click to expand...
Click to collapse
@djluisbento This method seems to be interesting. But would you please clarify more about it. How to install the apk file on official recovery? Or it's enough to have the pendrive connected? And if yes, when this step should take place, after flashing the official ROM or when?
I'm stuck in a boot loop into recovery mode with dm-verity error, and unfortunately I have the FRP locked, so I can't install TWRP to flash the no-dm-verity.zip file to skip it.
Appreciate your suggestions.
I have the same issure. stock firmware wont install either. im just stuck on the FRP screen, cant even get into recovery
Same issue here, please help
Everything was fine with rooting and installing TWRP. after that did a restart/ attempt to goto twrp recovery, from then the s7 edge is stuck at "Custom Binary Blocked By FRP" and doesnt boot. please help!!
Have you do a Wipe then Format Data.
Then flash the no-verity-opt-encrypt zip in TWRP
Only if you want internal storage or data to work in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Go to [Reboot] -> [Recovery].
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you only want a bootable system partition or writable data in TWRP:
Download the latest dm-verity and force encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
Click to expand...
Click to collapse
just quoting from the original thread by jcadduono.
Had that problem with a brand new phone, just wanted to get into download mode to see if the phone was tampered with and boom, flash screen with the red warning, flashed stock KSA (phone original CSC) , worked and phone was formatted, another surprise was faced, google did not accept my gmail account, had to shut down phone for 72 hours as read in my google search for people encountering same issue, once the 72 hours passed I was able to sign in and using my phone again.
maxkento said:
Have you do a Wipe then Format Data.
Then flash the no-verity-opt-encrypt zip in TWRP
just quoting from the original thread by jcadduono.
Click to expand...
Click to collapse
taiseer999 said:
Had that problem with a brand new phone, just wanted to get into download mode to see if the phone was tampered with and boom, flash screen with the red warning, flashed stock KSA (phone original CSC) , worked and phone was formatted, another surprise was faced, google did not accept my gmail account, had to shut down phone for 72 hours as read in my google search for people encountering same issue, once the 72 hours passed I was able to sign in and using my phone again.
Click to expand...
Click to collapse
Yes, flashed both Zips in recovery. I used my regular google account during the initial set up. If i wait for 72 hours, will the phone just boot back online just fine? Still, how do i make sure it wont goto the FRP lock again while trying to reboot or reboot to TWRP?
Solved,
Flashed with stock firmware, logged in with same google account, rooted with TWRP, installed Zubi's sound mod. Made sure to keep the 'OEM Unlock' stay turned on.
anoopgopalpt said:
Flashed with stock firmware, logged in with same google account, rooted with TWRP, installed Zubi's sound mod. Made sure to keep the 'OEM Unlock' stay turned on.
Click to expand...
Click to collapse
Helo
But U did this after 72 hours?
There are several methods depending on firmware version installed on your phone. Basically you have to enter in your phone, launch chrome, install an app which gives you the possibility to log into your google account from chrome and not set-up program.
I used successfully the Bluetooth method. Search for with google. You need a bluetooth headset and follow the steps described on youtube.
BTW. My phone was brand new and I flashed different official samsung firmware ( csc). I had to change google password in between and that resulted in FRP lock....
The wait time is 24 hours as is stated in google docs from site
Sent from my SM-G935F using XDA-Developers mobile app
Hello I have a related problem, opened a new thread, but my thread was closed, because my problem is related to this one, but more complicated. I have the same problem with FRP lock as described here, I can turn on the download mode but it wont be recognized by my computer. I tried different usb cables, drivers, even computers, it wont help. I cant flash it with odin, smartswitch, kies, no matter what I try. If I go to recovery mode it says `dm-verity verification failed...`and if I choose `apply update from ADB or SD card` it says `update from external storage disabled`. I dont know what to do anymore Its a new phone
FRP Block - no Dev Tools enabled
Hey guys,
you're my last resort, I've tried everything I happened to come across, to no avail.
First off, I did something incredibly stupid, don't even ask me why, as I have no idea what the heck drove me to do this in the first place.
Anyways, I was using the stock ROM on my S7 Edge, not tweaked or tinkered with besides the usual CF-Auto_Root. It never caused any trouble whatsoever. But for no reason at all this morning I decided to disable USB debuggin and OEM unlock. A short while later I rebooted my phone, which ended up in "Custom binary blocked by FRP Lock".
I gave a factory reset a try, but that obviously didn't change a thing. So I went to sammobile.com and downloaded the latest official stock ROM for my device and tried flashing it with Odin. Unfortnately Odin always fails with "Complete(Write) operation failed.", which I assume is because I messed with the settings in dev mode.
Next stop: ADB. I've never used that thing before, but I thought I should possibly be able to get it done following a simple guide. Unfortunately ADB won't even list my device when typing "adb devices". It's just an empty list.
So please guys, give me some tipps on how I can bring my phone back to life.
Tuesday
306sh activated with MVNO, SA300 firmware, rooted, with TWRP recovery,
working fine for past 2 months.
For unknown reasons, it decided last friday (at home, none to low signal) to do a system update
(from SA300 to S7232). Phone - on the desk- just "dinged" and msg came up "updating
system software". I attempted to cancel, but it didn't respond. Less than a minute later, "Update Successful" msg. Didn't reboot, anything, settings showed S7232 firmware. (SA300 before,
i had done my weekly backup earlier that morning).
Since then, phone constantly reboots at the "Aquos" screen; after an average 8 hours of rebooting, it will boot to setup, the talking setup screen. Works perfect for about an hour then rebooting starts again. Let battery die last nite, tried again this am - same thing rebooting.
TWRP backups don't fix problem- weekly backup, i have 6 i've tried, factory reset doesn't fix, if i try to Software Update, it checks, tells me, "up to date".
I turn on wi-fi to use the phone from home, , guessing it did a ? hit & miss ? ota update since the
wi-fi was off when it attempted the update. Home is a very minimal signal area.
Any way to force it to take the S7232 update again?
(I could update over wi-fi if i had wanted, only i didn't want the update anyhow).
thanks, rik
I can give you a link for a backup with latest firmware, you will have to wipe data tho
https://mega.nz/#!fkommKgJ!fkiaT_p8ZFOBzyJpUdNAqOZlTWpt-5hNuQ-2vvA5tSQ
This is a full backup from newest firmware but you need to wipe data before boot
sent from rooted 306sh
Stick firmware updates are not compatible with custom recoveries
sent from rooted 306sh
Just home, thanks
Hi,
Thanks for the help, just home from work (rough), so i will plug the
Aquos in tonite and hopefully be able to try the file tomorrow,
(that 8 hour boot thing), just downloaded your file, i'm ready.
This is my take-to-work personal phone, sprint zone, and i missed it today.
Your help is really appreciated.
rik
Final note
thought i'd just post to let you know the phone obviously had big problems
-- it failed to start today -- just buzz on buzz off -- even after 4 hours charging,
all i could get was the battery dead screen, wouldn't come on at all.
Guess the real problem was with hardware, i laid it away in the junk phone box
in the attic, end of Aquos Crystal.
rik
I downloaded this backup and yesterday to restore the firmware, works great, huge thank you , you saved me. :хорошо:
can you help me?
badbadri said:
I downloaded this backup and yesterday to restore the firmware, works great, huge thank you , you saved me. :хорошо:
Click to expand...
Click to collapse
can you help me dude? :crying:
im already download this firmware and confuse how to restore it
im looking for how to root my phone but always confuse
and finally i installed supersu on playstore and reboot
im waiting for 5 minutes and not booting, and im plug my phone to pc and the computer request for formating all my storage
and my phone can enter the recovery mode and i go to wipe data & factory reset, and still not work
can you send to my email?
my email is [email protected]
thx ..
Question: My 306SH would not update (still at S8216). Could use your back up to update my firmaware?
After 306SH ph was acting weird, did a hard reset & saw system Software updtd to S7232, & unk file in Misc (.eCtcQjbu1dgnvtFnvnr6yepTp1M=) I then installed Malwarebytes & scan detects this S7232 software update as malicious malware Android/PUP.RiskyTool.Agent.ay (dm.redbend) "/system/priv-app/fotaClient.apk". When going to System to do an manual update, Malwarebytes popups w/same msg every scan "Software App", even aft reboot 2days ago 7/12/2017. And phone wont let me create new google acct. An error that "google account mgr not working" popup & I see that same unk file reappears. Ph not rooted -XDA says "there's no root for 306SH that works">see XDA blog 'Root for Aquos Crystal 306SH ONLY'.
Go to the Sharp USA website for the 306SH firmware, and see what firmware you are on.
Download the firmware from the versions higher than yours, and if there is a repeat, notably "kernel.img", download the most latest version of it.
Then, plug your device into your computer, make sure you have the proper drivers installed for the Sharp Aquos Crystal installed on your computer. Boot your device into bootloader. Go to a terminal, cd to the directory where you downloaded your .img's from the website, and do
fastboot flash kernel kernel.img
Ex.
fastboot flash foo foo.img
And you can flash all the latest updates. When done, exit the terminal, make sure the device is unmounted, unplug from computer, and reboot your Crystal.
Hooray, it should be updated!
turkbot said:
I can give you a link for a backup with latest firmware, you will have to wipe data tho
(Mega-nz link expired)
This is a full backup from newest firmware but you need to wipe data before boot
sent from rooted 306sh
Click to expand...
Click to collapse
Turkbot, I hate to beg on my first XDA post, but is there any chance that you still have that ROM and is there any chhance that it's not TextNow loaded? I've got TWRP, Busybox, SuperSU, Xposed, and I've tried every which way to edit the prop, tweak it with modules, unlock etc (it even works with my Sprint MSL, but crashes when I try to manually set my MDN and MSID) It just says no SIM/no service and refused to give me any signal except for GPS and WIFI without one. Countless 'techs' over the phone and 3 different Sprint repair stores claim they don't have the stock firmware and Sharp actually claims that the reason they can't help me with the firmware is their contract with Sprint forbids it.. If you still have the file or a TWRP / Titanium etc backup you would be my savior.
hey guys,
i think i made something really stupid.
-unlocked bootloader
-installed TWRP
-rooted
everthing was fine B161.
installed apps2sd and did something there so my phone was stuck in bootloop.
now the stupid part:
i wiped everything in TWRP... system, internal storage everything... i am such a douchebag!
I tried to recover with eRecovery and install stock firmware B161. Update process was successful and i can start my phone again.
but everytime i start the setup wizard i am stuck after wi-fi+ service (enhanced internet expierence) the screen shows "checking data.." for 1 second and switched back to wi-fi+ service.
is there anything i can do? guys help me please i am starting to freak out.
is my guarantee voided after i unlocked my phone?
fastboot shows
-phone locked
-frp locked
THANKS FOR ANY HELP!
khajiit said:
hey guys,
i think i made something really stupid.
-unlocked bootloader
-installed TWRP
-rooted
everthing was fine B161.
installed apps2sd and did something there so my phone was stuck in bootloop.
now the stupid part:
i wiped everything in TWRP... system, internal storage everything... i am such a douchebag!
I tried to recover with eRecovery and install stock firmware B161. Update process was successful and i can start my phone again.
but everytime i start the setup wizard i am stuck after wi-fi+ service (enhanced internet expierence) the screen shows "checking data.." for 1 second and switched back to wi-fi+ service.
is there anything i can do? guys help me please i am starting to freak out.
is my guarantee voided after i unlocked my phone?
fastboot shows
-phone locked
-frp locked
THANKS FOR ANY HELP!
Click to expand...
Click to collapse
did you do factory reset? I had some weird stuff going on after recovery, so I booted back to factory reset (vol + and power), after that it worked OK.
Once you requested the bootloader unlock key, your warranty might be void from that point (depends on country). The bootloader gets locked after flashing official firmware via eRecovery though.
yes i did a factory reset, still can't proceed after wi-fi+ configuration.
is there anything else i can do?
I have one question: is it possible with
-frp locked
and
-phone locked
to downgrade via eRecovery? (to b130 or something..)
I have the exact same problem.
I bought it 3 days ago, and suddenly yesterday downloaded Apps (from the Play Store) stopped working. So someone told me to hard reset it. I got into EMUI and did it. Then I rebooted it and now it stuck there. Can't complete the setup wizard.
I found no solution to my problem after reading google & xda-forum for 3 days. Tried everything... nothing worked. Sent it back and (luckily) got a new one. Now i'm more careful for sure.
The store I bought it from claimed that they had numerous similar complaints about the 3gb version. Which is the one I have. They told me I should take it back and that they will give me a new 2gb version along with any difference in money. We will see.
Exact same thing with me stuck at setup wizard so had to send it off for warranty and got a brand new phone yesterday
Sent from my HUAWEI VNS-L31 using XDA-Developers mobile app
Help please my Huawei P9 cannot proceed afta WiFi setting it is stuck on "Checking info "and Reply saying "Couldn't sign in"
The problem is Android System Webview, it's not a system app in this rom and when you reset your phone it deletes it, happened the same to me, I had to go to a huawei center, they menaged to skip the initial setup and I've installed the apk from apk mirror. Without this app the phone can't login in your google account, so if you don't install it your gapps won't work
Maxai94 said:
The problem is Android System Webview, it's not a system app in this rom and when you reset your phone it deletes it, happened the same to me, I had to go to a huawei center, they menaged to skip the initial setup and I've installed the apk from apk mirror. Without this app the phone can't login in your google account, so if you don't install it your gapps won't work
Click to expand...
Click to collapse
Hello,
does ist really work? Is it just installing the androidsystemview.apk and the phone works fine again?
huawei p9 lite bricked ...please i need a help
my phone stoped in fastboot...
phone locked
frp lock
i can´t enter on recovery mode and he not pass the huawei icon ...
please i need help
i do not connect phone to pc ....
contact me to solve the problem
I'm having exact problem with my mate 8 NXT-L09, after i had to factory reset when update from firmware finder failed. Anyway to bypass this problem? Do you have a way of add Android System View into the mate 8 during the bootup process. I love this mate 8 phone and 5 days now i has been torture.
logjam said:
I'm having exact problem with my mate 8 NXT-L09, after i had to factory reset when update from firmware finder failed. Anyway to bypass this problem? Do you have a way of add Android System View into the mate 8 during the bootup process. I love this mate 8 phone and 5 days now i has been torture.
Click to expand...
Click to collapse
Reflash the rom you were on using the "dload" method
dariomrk said:
Reflash the rom you were on using the "dload" method
Click to expand...
Click to collapse
Sorry, dont have the previous ROM, I boiught it off someone and they probably did the first update. The factory reset should reset to huawei original but i think this is where my problem sits.
HARDWARE VERSION=NEXT_L09_VN2
BOOTLOADER VERSION=NXT-C900B120_FASTBOOT
KERNEL VERSION=NXT-C900BB140_BOOT
AP VERSION=NXT-C900B140_SYSTEM
CP VERSION=21.750.08.00.010(balong)
Parameter Version:
P-00.00.000 G-17.V271.371 E-40.01.000
does anyone have an international rom for this or any version that can work.
The way i was able to factory reset was
1. going to huawei site. "consumerDOThuaweiDOTcomSLASHjmSLASHsupportSLASHdownloadsSLASHindexDOThtm"
change slash to / and dots to .
2. Select options for your phone, mine was NXT-L09. Will show "HUAWEI Mate 8 Firmware(NXT-L09, Android 6.0, EMUI 4.0, C605B100, Latin America, Channel-Others)"
3. Download, extract onto sdcard in dload folder, restart phone using vol up & vol down & power.
4. phone will complete boot restart but will then loop the boot process.
5. Do factory reset again
6. After huawei logo, different options show and you are then ok to proceed to login to your google account and setup refreshed phone.
Now on NXT-L09C900B100 build, if anyone has nougat rom for this, please share.
For future reference, if anyone gets stuck with this on P9 lite, indeed the instructions provided by Huawei point to VNS-L11C432B161, which doesn't include Android webview and therefore initial setup cannot proceed. The solution is to flash B210 on top of B161:
update.hicloud.com:8180/TDS/data/files/p3/s15/G1164/g104/v80562/f1/full/update.zip
which allows you to pass setup as the bug has been fixed. No root/unlock/twrp required.
I already opened an RMA for the phone but they have no stock so I figured I'll take another shot at it.
The short version is that my gf messed up and updated the system while transferring her data from her old phone with the tapNgo thing.
I've done multiple facory resets, downloaded the rom from ZTE support, put it on SD, flashed it from recovery and deleted cache and nothing helps.
I don't have the exact error log anymore since I don't have the phone with me now but it reads something along the lines of
loading /proc/devices/audio/sound------ cannot find file/directory.
I looked it up and after a lot of Googling it seems like the symlink to the actual driver folder is missing and I have no idea why.
Does anyone know if i can fix this with an ADB shell?
Alternatively, I tried to follow some of the many guides out there to put the phone in EDL mode and relfash it with XiamiFlash utility but after trying 3-4 downloads and 900 versions of misflash all I ever get is "reading hello packet... unable to communicate to com4"
Haaaalp please?
*edit* this is pretty much exactly the same as what I'm getting: https://forum.xda-developers.com/android/help/sound-card-detected-t3379736
The problem with the phone is it makes no sounds?
gpz1100 said:
The problem with the phone is it makes no sounds?
Click to expand...
Click to collapse
the sound drivers for the OS is missing completely, no sound no microphone.
The syslog looks like this(this is from another phone its its the exact same problem):
AudioDaemon: Opening sound card state : /proc/asound/card---/state
AudioDaemon: Open /proc/asound/card---/state failed : No such file or directory
AudioDaemon: Sleeping for 100 ms
Strange issue indeed. Which model do you have? Which specific firmware file are you flashing to it?
I would think flashing the full unmodified factory firmware using the stock recovery will wipe the phone completely, including the /data partition.
Everything worked before? Help me understand the order of events. What is tapngo?
While in the midst of transferring information to or from the phone, a software update appeared and she accepted/installed it?
Its the A2017U model.
I had tried the 1.1.0 B15 firmware from SD card as well as the 1.0.0 B29 older firmware.
Right now its on B17 Nougat 7.1.1, the phone runs and works perfectly just has no audio hardware.
I wasn't there for the exact procedure but basically she powered it on, it asked for sim, she inserted that, tapped the "transfer my data" and then held the two phones together to get the NFC process started. That starts the bluetooth transfer process and it takes a really long time where it transfers all data and apps from the old phone.
At this point the phone still made sounds when adjusting the volume etc.
Somewhere in that process the "update available" notification came up and she pressed the option to install it.
After I got home I tried to figure out what is wrong, first i thought the phone wasn't registered on the cellphone network but then after a bit i figured out the audio is the issue, then i did a factory reset both from the phone UI and tried again from recovery mode, both times chose the "erase all data" option but neither time did it help at all.
I don't really know enough about phones but i think its the bootloader/something very early on thats messed up. Either that or the audio chip really just did fry.
My hope was to get the full factory image for everything that you need to install with the EDL mode thing but I can't find any good reliable guides for that.
It's the first thread in the development section.. Stickied even.
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Get this package - B15-NEW_FULL (Nougat)
I really don't understand zte's numbering scheme. Newer versions get lower numbers. Makes no sense. That's the full firmware except for the fastboot which passes commands. At this point it's a non issue given the issue you're having.
So I don't need to load TWRP on it, I can still keep it just stock with unlocked bootloader?
I tried that miflash thing before, i had it connected un usb download mode but nothing worked for me, I'll try doing this guide when i get home step by step again.
Their firmware numbers is based on numbers and letters 1.0a-z and then 1.1a-z so 1.0z1 is less that 1.1a1
Ok I have an update
Did miflash, nothing changed.
Ulocked bootloader and miflashed the bootloader from the sticky thread.
The phone made the startup sound and audio worked for a few seconds after android started up and then stopped again
*edit*
ok so after it showed signs of life i re-locked the bootloader, and did the OTA updates to 7.1.1 and the audio seems to be working for good now!!
Conclusion seems to be the bootloader was the key to get it working again. Hope this helps others if it comes to it.
I have had my Essential Phone for almost two years now and one day last week when I turned the phone on I saw the following error message.
You device is corrupt. It can't be trusted and may not work property.
Visit this link on another device:
gc.o/ABH
Press Power Key to Continue
There is a red exclamation point at the top that looks like this <!>. I contacted Essential Support and they told me the only way that message gets displayed is when someone has unlocked the bootloader at some point. I have never connected my phone to a USB cable for anything other then charging it with a power outlet and I have certainly never heard of ADB before this error occurred.
I would like to know how this error has happened if all I do is install a few apps from the Play Store and install OS updates when the are officially available OTA. Essential Support has said its my fault and will not help.
I tried to reset the phone back to factory settings several times. I have used the reset from within the Settings, I have used ADB to side-load the latest OTA OS from Essentials website and I have also tried some kind of flashing reset but no matter what I did I could not get this error to go away. These methods are described on the Essential site linked below.
Here is the link to Essentials website that I used. Since this is my first XDA post it will not let me post the whole URL. (essential.com/developer/current-builds)
I eventually ran the following command which did remove the error.
Code:
adb reboot "dm-verity enforcing"
From what I can tell this just prevents the error message from being displayed, correct? If the reason for the error is still there then what are my options? Should I worry about this error? Is it possible for me to reset the phone in someway to get this error message to go away and put the phone back into a secure and safe state? I don't care about any user data on the phone. The whole thing can be erased, which I think I have done sever times already trying to fix this.
Any suggestions would be greatly appreciated because beyond trying to fix this error I have no experience with ADB or modifying a phone in anyway.
Thanks,
-eric
Is there anyone who can offer help?
EricAndroid said:
Is there anyone who can offer help?
Click to expand...
Click to collapse
You can unlock your bootloader and unlock critical partitions than flash the latest bts (back to stock) from the link below. Make sure to read the directions and use a quality type c USB 3.0 or 3.1. you basically download the zip and unzip it, then run the flash-all-wipe.bat from fastboot mode. This will fix the actual problem. Good luck and make sure to ask in that thread if you get stuck.
Almost forgot, make sure to download the Essential Window's drivers(from thread below as well). You don't need to worry about setting up adb and fastboot because it's Automatic when you run the commands from the zip you download. Also make sure you first uninstall any instance of adb or fastboot that may already be on your computer.
https://forum.xda-developers.com/es...ment/stock-7-1-1-nmj20d-t3701681/post74437484