Database Users

[GUIDE] Root Stock N using jcadduono's Recowvery tool. H830.

Using the following method I was able to successfully ROOT my H830 running stock 20A NOUGAT. With this root method you will get TWRP Recovery and SuperSU. This method WILL wipe your internal storage, so please BACKUP!​
Your warranty is now void. I am not responsible for bricked devices, dead SD cards, or lost photographs.
Please do some research if you have any concerns about root!​
I used jcadduono's method which he describes on the V20 forum [Easy Recowvery ALL CREDITS TO THE AUTHOR. PLEASE GO RATE HIS THREAD AND CLICK THANKS IF THIS WORKS FOR YOU!] https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594​
1. Bootloader Unlock
For this method to work you must have an unlocked bootloader. Despite the fact that I already had an unlocked bootloader, after the upgrade to stock N, jcadduono's script failed to work initially and gave me an error message saying my bootloader was locked. To fix this I had to manually relock and unlock my bootloader one more time. Unlocking/Locking your bootloader will wipe the internal storage of the devices so backup before this step. If you however, already have an unlocked bootloader, feel free to skip this step and go on, although in the end you might have to return to it if you get a "bootloader locked" message in the Recowvery script. If you do skip these steps, don't forget to download the LG Drivers from below.
1. Download and install the latest LG Drivers from HERE
2. Download the minimal adb and fastboot tool from HERE. I recommend the portable version, which you can extract to your desktop.
3. On your phone, go to Developer Options and turn on Enable OEM Unlock.
4. Enter fastboot mode: Turn off your device, press and hold the volume down button, while holding the volume down button connect your phone to your computer by USB, continue holding the volume down button until your device enters into fastboot mode.
5. On your computer go to the folder which you extracted in step 2. Open a command window by holding down SHIFT, right clicking with you mouse inside the folder, and selecting "Open command window here"
6. In the command window type "fastboot oem unlock" to unlock your bootloader, this will erase all of your data.
7. Type "fastboot reboot" to reboot to system.
2. Installing TWRP using Recowvery
Prior to this step I HIGHLY recommend factory resetting your device, if you just unlocked your bootloader, your device was automatically factory reset so you are good to go. Once your phone turns on after a factory reset, I suggest signing into your google account and setting up your phone as if you are going to use it, we will not be factory resetting after this step. However do not download any apps or mess with the settings yet, you can do that later, once your device is successfully rooted.
1. On your computer, download Recowvery from HERE and extract the folder to your desktop.
2. Now on your phone enable USB Debugging in Developer Options.
3. Connect your phone to the computer and make sure File Transfer is chosen in the "Use USB connection for" pop-up.
4. On your computer, download the latest version of TWRP: H830 or H850
5. Rename the downloaded file to "recovery.img" and place it on your phone's internal storage [/storage/emulated/0]
6. On your computer, open the Recowvery folder you extracted in step 1, and click on EasyRecowvery.
7. Once there, type option "5" and "ENTER", in the "Extras and Advanced Tools Menu" disable integrity verification by typing option "7" and "ENTER". Return to the main Menu of Recowvery by typing option "0" and "ENTER"
6. After disabling integrity verification, run the exploit by choosing option "1"
7. Follow the prompts in Recowvery, your phone should reboot about two times in the process.
8. DO NOT Wipe Cache while in TWRP.
8. Once finished, your device should reboot to system and will have TWRP recovery, instead of the stock recovery. The only thing left now is to install SuperSU.
3. Installing SuperSU through TWRP
Although Recowvery does give you an option to install SuperSU through its interface, doing so caused problems in my case. Therefore I recommend manually booting into TWRP and installing SuperSU from there.
1. Download the latest version of SuperSU from HERE and place the .ZIP file on your phone's internal storage.
2. To boot into TWRP, go into the adb and fastboot folder, which I described in the very first steps of this tutorial. There, once again open a command window and type "adb reboot recovery".
3. You should now be in TWRP, there select Install, find the .ZIP file of SuperSU in the file explorer, and install it. DO NOT Wipe Cache after the installation.
4. Reboot to sytem, you should now have a rooted LG G5 with TWRP and SuperSU installed!
Credits:
jcadduono - Recowvery
RealPariah - Compiled Recowvery zip for LG G5
shimp208 - Minimal ADB
TWRP
SuperSU​

[Reserved]

I'll try this later tonight, I spent the whole night yesterday trying that. Thanks in advance. ???

Didn't work for me. Thanks for this though. The script actually made it's way through this time (multiple times at this point), but whenever I try to adb reboot recovery I get the "No Command" screen (which I believe is still the stock recovery?). Success all the way through. Don't know what I could be missing.
Also tried manually pushing the recovery image via adb thinking there might be an "Internal Storage" (as seen by pc) vs "/storage/emulated/0" on the phone. No dice either way.

Dumboguy03 said:
Didn't work for me. Thanks for this though. The script actually made it's way through this time (multiple times at this point), but whenever I try to adb reboot recovery I get the "No Command" screen (which I believe is still the stock recovery?). Success all the way through. Don't know what I could be missing.
Also tried manually pushing the recovery image via adb thinking there might be an "Internal Storage" (as seen by pc) vs "/storage/emulated/0" on the phone. No dice either way.
Click to expand...
Click to collapse
To me it seems like your recovery is not flashing, make sure to download the latest version of TWRP, rename it "recovery.img", and place on the internal storage of the device. If still doesn't work, try a complete clean start. Relock and unlock your bootloader again.

To be safe, I would remove "others try at your own risk" as it will not work and could possibly brick any model other than the H830 and H850. All other models are bootloader locked and I have tested myself; it won't work on anything else.

It worked! Thank you so much.

It worked! Thank you!!!👍👍👍
Sent from my LG-H830 using XDA-Developers mobile app

If you however, already have an unlocked bootloader, feel free to skip this step and go on, although in the end you might have to return to it if you get a "bootloader locked" message in the Recowvery script.
What do you mean with thiz sentence? We cant unlock our bootloader its not supported, can we still try this method?

Will this trigger some flag or fuse? Or with the flash of the firmware though lgup and locking the bootloader will create a Perfect stock device?

Can someone confirm it works on H850

yken said:
If you however, already have an unlocked bootloader, feel free to skip this step and go on, although in the end you might have to return to it if you get a "bootloader locked" message in the Recowvery script.
What do you mean with thiz sentence? We cant unlock our bootloader its not supported, can we still try this method?
Click to expand...
Click to collapse
No, you have to have an unlocked bootloader. I meant if you already unlocked your bootloader, you can skip this step. Possibly it will work once we get bootloader unlocks for other variants of the G5.

Do I have driver issues? Adb recognizes phone when turned on. When in fastboot only waits for device to connect.
Sent from my LG-H830 using Tapatalk

Tinbender418 said:
Do I have driver issues? Adb recognizes phone when turned on. When in fastboot only waits for device to connect.
Sent from my LG-H830 using Tapatalk
Click to expand...
Click to collapse
The drivers in the post should work for both fastboot and adb. What do you mean, "when in fastboot only waits for device to connect"? You can run the "fastboot devices" command there to see if the device is recognized.

Will not let me run any commands. Just says waiting for device. Crazy, I know.
Sent from my LG-H830 using Tapatalk

Looks like hd on pc is going.
Sent from my LG-H830 using Tapatalk

adb and fastboost not recognizing my phone even after installing drivers

Finally got root back. My problem was getting adb to work but I had no problems with minimal adb and fastboot. Thanks for the tutorial.

Will we be able to flash the current roms that our out?
Sent from my LGE LG-H830 using XDA Labs

Running in normal exploit mode
Press any key to continue . . .
- - - Making sure we're good to go - - -
Checking permissions in the EasyRecowvery directory...Checking that the exploit files exist...SUCCESS!
Locating adb.exe... SUCCESS!
Looking for ADB device...
This device doesn't look like a T-mobile V20. Proceed anyway? (DANGEROUS!)
(Y/N) y
Checking unlock status... error: device '*' not found
FAILED!
Your device does not appear to be unlocked.
Please boot into fastboot mode and run:
fastboot oem unlock
From your computer, then try again.
http://i.imgur.com/2BhNatP.png
Press any key to continue . . .
so this is what i am running into. I know with 100% certainty that the device is oem unlocked. I get the whole, "your device software can not be checked for corruption" screen and everything.
i started the process completely stock, with oem locked. I unlocked it as per your instructions and followed everything closely as far as I can tell. i have tried to re-lock oem . reboot and then unlock it again twice, as well as rebooting pc and G5 multiple times. usb debugging is turned on, and usb options are set to file transfer. still same result.
Any ideas?
EDIT: i will leave the whole post up in case some one makes the same mistakes i did and this helps them out. What i needed to do to fix this was simply set "use usb connection for " to photo transfer instead of file transfer.
Now i am stuck on :\Users\test\Desktop\LgG5 RooT\minimal_adb_fastboot_1.4.1_portable>adb reboot recovery
error: no devices/emulators found like another person before me. hopefully this will be figured out soon
EDIT#2: used adb reboot recovery command with phone turned on and on main screen of launcher, not fast boot, like i was trying at first. and twrp loaded up fine.
dont have a sd card to put superuser.zip on and it seems like i can't reach the internal storage download folder through twrp, or atleast i could not find it, so i ended up sideloading it by going to sideload in twrp and typing "adb sideload SR1-SuperSU-v2.79-SR1-20161221223537.zip"
into it.
i hope that documenting all my mistakes and solutions for everyone to see will help someone running into the same problems i was.

nexus 6p doesn't boot, with error when trying to unlock

Greeting,
My nexus 6P, suddenly while having a phone call, got freeze, then rebooted,
Then it keeps rebooting, showing Google “in white” while booting, then off, restart again “by itself”, and same in loop
Started the device into fastboot mode, selected recovery mode
Again same issue, restart, shows Google “in white” then restart again
Tried to follow the instructions, at [GUIDE] Unlock/Root/Flash for Nexus 6P
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Commands and results are here
C:\nexus6p\angler-n4f26o>adb version
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android
C:\nexus6p\angler-n4f26o>adb devices
List of devices attached
<Notice no result returned>
C:\nexus6p\angler-n4f26o>fastboot devices
8XV7N16126000082 fastboot
Please note, I checked those points
ADB and fastboot, downloaded from the link provided in the guide, as well I downloaded it from Google directly
USB driver, updated with latest from google
Java, updated
And of course, I cannot run the device, to do any required configuration on it
And here is a copy of the device details

malibusa said:
Greeting,
My nexus 6P, suddenly while having a phone call, got freeze, then rebooted,
Then it keeps rebooting, showing Google “in white” while booting, then off, restart again “by itself”, and same in loop
Started the device into fastboot mode, selected recovery mode
Again same issue, restart, shows Google “in white” then restart again
Tried to follow the instructions, at [GUIDE] Unlock/Root/Flash for Nexus 6P
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Commands and results are here
C:\nexus6p\angler-n4f26o>adb version
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android
C:\nexus6p\angler-n4f26o>adb devices
List of devices attached
<Notice no result returned>
C:\nexus6p\angler-n4f26o>fastboot devices
8XV7N16126000082 fastboot
Please note, I checked those points
ADB and fastboot, downloaded from the link provided in the guide, as well I downloaded it from Google directly
USB driver, updated with latest from google
Java, updated
And of course, I cannot run the device, to do any required configuration on it
And here is a copy of the device details
Click to expand...
Click to collapse
If you can get into bootloader mode then maybe try fastest flashing things like stock recovery. If you manage to get stock recovery then boot into it and adb sideload a stock OTA from Google Developer website. Other than that I'm not too sure, you might need to contact Google/Huawei if that or anything else doesn't work.
---------- Post added at 08:43 PM ---------- Previous post was at 08:35 PM ----------
Okay, in bootloader mode try flashing the stock bootloader image from their OTA by typing fastboot flash bootloader (drag bootloader image here) then type fastboot reboot-bootloader. After that type fastboot flash radio (drag radio image here). Then type fastboot reboot-bootloader again. After that you can try booting up. If you are somehow able to get into recovery mode whether you can boot up normally or not then you can simply adb sideloading the stock OTA. If nothing I have said gets you into recovery or to boot up the device then you are probably screwed to be honest. Good luck

Hi,
thanks for your reply,
let me make sure, that i understood you clearly,
when i boot into bootloader, and select the recovery mode,
it get rebooted, shows Google “in white” then restart again, and again in same loop exactly as if i booted normally, not into the bootloader
as i read in other posts, i should expect the device to show me a confirmation message, or something similar,
but in my case, nothing at all, restart, and keep restarting
The options i have with bootloader are
1- Start
2- Reboot bootloader
3- Recovery mode
4- Power off
5- Barcodes

malibusa said:
Hi,
thanks for your reply,
let me make sure, that i understood you clearly,
when i boot into bootloader, and select the recovery mode,
it get rebooted, shows Google “in white” then restart again, and again in same loop exactly as if i booted normally, not into the bootloader
as i read in other posts, i should expect the device to show me a confirmation message, or something similar,
but in my case, nothing at all, restart, and keep restarting
The options i have with bootloader are
1- Start
2- Reboot bootloader
3- Recovery mode
4- Power off
5- Barcodes
Click to expand...
Click to collapse
In bootloader mode, not recovery try flashing the bootloader and radio like I said.

Hi... RMA your phone... Contact google or Huawei depending where you bought your N6P.
Check this link. A lot of people seem to be in the same situation at the moment:
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528

You're in the same boat as a few of us.
Phone is stuck in a bootloop, won't go to recovery. Only boots to fastboot, but your bootloader is locked so you cannot boot/flash any zips, even official ones. That means no recovery access, which means no adb commands. ADB commands *might* be useful to reboot into EDL mode for QFIL flashing, or for wiping partitions. Problem is - if that bootloader wasn't unlocked, it's not going to be. You need to check "Allow OEM unlocking" in settings BEFORE the phone dies, otherwise you will not be able to unlock the bootloader and thereby reflash the phone.
In a perfect world - we could use EDL mode (or something) to use QFIL/MiFlash to completely rewrite the partitions and MAYBE bring the phone back to life, but the stock bootloader does not allow access to EDL. (tried the custom fastboot.exe meant to send the reboot-edl command, didn't work). If someone can figure out the JTAG pins, we might be able to move forward by purposely bricking it to QHUSB_BULK mode.
The thing is - we don't know why the phones started bootlooping in the first place. For some people, a simple cache wipe/factory reset fixes the loop and away they go. HOWEVER, those of us stuck in fastboot mode with a locked bootloader have no way to erase/wipe/format/write partitions, and even if we could, there's no guarantee it was a software issue that caused the loop in the first place.
TL/DR - You have a locked bootloader and cannot access recovery mode, this means you won't be able to flash/wipe/format partitions or images. Best bet is to contact Huawei/Google, but you'll need the original receipt. If that's not an option for you, you're gonna have to wait until the XDA geniuses out there grant us some answers.
Here's a related thread with some deep info:
https://forum.xda-developers.com/nexus-6p/general/qpst-qfil-answer-to-issues-t3455779

singularoctopi said:
You're in the same boat as a few of us.
Phone is stuck in a bootloop, won't go to recovery. Only boots to fastboot, but your bootloader is locked so you cannot boot/flash any zips, even official ones. That means no recovery access, which means no adb commands. ADB commands *might* be useful to reboot into EDL mode for QFIL flashing, or for wiping partitions. Problem is - if that bootloader wasn't unlocked, it's not going to be. You need to check "Allow OEM unlocking" in settings BEFORE the phone dies, otherwise you will not be able to unlock the bootloader and thereby reflash the phone.
In a perfect world - we could use EDL mode (or something) to use QFIL/MiFlash to completely rewrite the partitions and MAYBE bring the phone back to life, but the stock bootloader does not allow access to EDL. (tried the custom fastboot.exe meant to send the reboot-edl command, didn't work). If someone can figure out the JTAG pins, we might be able to move forward by purposely bricking it to QHUSB_BULK mode.
The thing is - we don't know why the phones started bootlooping in the first place. For some people, a simple cache wipe/factory reset fixes the loop and away they go. HOWEVER, those of us stuck in fastboot mode with a locked bootloader have no way to erase/wipe/format/write partitions, and even if we could, there's no guarantee it was a software issue that caused the loop in the first place.
TL/DR - You have a locked bootloader and cannot access recovery mode, this means you won't be able to flash/wipe/format partitions or images. Best bet is to contact Huawei/Google, but you'll need the original receipt. If that's not an option for you, you're gonna have to wait until the XDA geniuses out there grant us some answers.
Here's a related thread with some deep info:
https://forum.xda-developers.com/nexus-6p/general/qpst-qfil-answer-to-issues-t3455779
Click to expand...
Click to collapse
I'm stuck with a black screen and QFIL and XiaoMiFlash won't work. My bootloader is unlocked but I can't get to fastboot. Screen is always black but Quallcomm HS-USB QDLoader 9008 appears in device manager. No red light or vibration when connecting the phone.

vcharette said:
I'm stuck with a black screen and QFIL and XiaoMiFlash won't work. My bootloader is unlocked but I can't get to fastboot. Screen is always black but Quallcomm HS-USB QDLoader 9008 appears in device manager. No red light or vibration when connecting the phone.
Click to expand...
Click to collapse
Have you read this thread: https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
Maybe try asking here, explaining the things you tried.

No system, no recovery, bootloader unlocked, FRP locked

After some problems (corrupted data partition and sticking in bootloop after reboot) on LineageOS 14.1 and PA 7.2.2, I decided to reflash the EMUI. That didn't work and through a series of my mistakes I have no recovery, no system and can't flash anything.
Fastboot gives me the "remote: command not allowed" error whatever I try to do except for "fastboot reboot" and "fastboot oem get-bootinfo" (which says the bootloader is unlocked). The fastboot screen says : Phone Unlocked, FRP Lock.
I can connect to adb after a few minutes of waiting at the "Your device is booting now..." screen that also shows 3 options. But I have nothing in /system/, which means /system/bin/sh doesn't exist so I can't get a shell into the phone. "adb ls" does work, though (don't know how).
I've also tried to push at least a shell into /system/ with "adb push", but it says that the partition is mounted read-only. Is there a way to mount it read-write without using "adb shell"?
Is my phone recoverable or is it bricked beyond repair? Any suggestions on how to repair it without changing the motherboard?
Thanks in advance!

CanIHelp said:
After some problems (corrupted data partition and sticking in bootloop after reboot) on LineageOS 14.1 and PA 7.2.2, I decided to reflash the EMUI. That didn't work and through a series of my mistakes I have no recovery, no system and can't flash anything.
Fastboot gives me the "remote: command not allowed" error whatever I try to do except for "fastboot reboot" and "fastboot oem get-bootinfo" (which says the bootloader is unlocked). The fastboot screen says : Phone Unlocked, FRP Lock.
I can connect to adb after a few minutes of waiting at the "Your device is booting now..." screen that also shows 3 options. But I have nothing in /system/, which means /system/bin/sh doesn't exist so I can't get a shell into the phone. "adb ls" does work, though (don't know how).
I've also tried to push at least a shell into /system/ with "adb push", but it says that the partition is mounted read-only. Is there a way to mount it read-write without using "adb shell"?
Is my phone recoverable or is it bricked beyond repair? Any suggestions on how to repair it without changing the motherboard?
Thanks in advance!
Click to expand...
Click to collapse
https://forum.xda-developers.com/huawei-p9lite/how-to/unified-help-thread-huawei-p9-lite-t3649152
Post 5. Unbricking EMUI 5. Don't take for granted it will work, but considering FRP is locked, this is the only way not needing a unlocked bootloader.

Doesn't work. It's still stuck at the "Your device is booting now..." under the vmall link screen.
Isn't the 3-button method counting on the original recovery being in the recovery partition?
I only have the second recovery working (that eRecovery which only lets you "download and install the latest recovery and system"...and doesn't do anything).
Is there a way to override the frp lock? I saw a couple of tools online claiming to do that, but none worked. I haven't tried DC-Unlocker. If I'm gonna pay for it, might as well go to a service

Dload method uses the secondary recovery, It should be there if you press all three buttons.
From what i have heard, DC-Unlocker works.

Plug your phone on computer.
You see yellow advice? Appears automatically.
Juste after this advice, tip "fastboot reboot bootloader".
After, unlock your bootloader again "fastboot oem unlock YOUR_OEM_CODE"
Ok now shutdown and hold buttons for boot to TWRP recovery, if not appears, flash it on "fastboot flash recovery recovery.img"
Warning command not allowed on fastboot is 90% time du at bootloader unlocked (even if he says it's good)

dariomrk said:
Dload method uses the secondary recovery, It should be there if you press all three buttons.
From what i have heard, DC-Unlocker works.
Click to expand...
Click to collapse
It did boot in the secondary recovery (had to hold onto the 3 button for 3-4 minutes continuously). But it said that "Software install failed/ Incompatibility with current version. Please download the correct update package."
I'm now trying the B160 image in that thread. Wish me luck!
EDIT: It worked. The B160 image flashed using the three button method. I'm now at the setup screen. And the keyboard is there. (Also had the problem where I'd only have the voice input keyboard)
Thank you very much!

CanIHelp said:
It did boot in the secondary recovery (had to hold onto the 3 button for 3-4 minutes continuously). But it said that "Software install failed/ Incompatibility with current version. Please download the correct update package."
I'm now trying the B160 image in that thread. Wish me luck!
EDIT: It worked. The B160 image flashed using the three button method. I'm now at the setup screen. And the keyboard is there. (Also had the problem where I'd only have the voice input keyboard)
Thank you very much!
Click to expand...
Click to collapse
No problem mate, nice to hear you did it without problems.

Unlock Bootloader Just Hangs...

Just recently purchased a "broken" Nexus 10 off ebay for nearly nothing. Seller showed that it just hangs at "Google" upon startup. Bought it as a project to see what I could do...
So, after a few hours of trying everything I could with NRT I am unable to unlock the bootloader. When I press vol + and then the power button to select it to unlock, it just stays there...it doesn't do anything and freezes until I hard reset it. No love lost if this is a bricked device, I'd only be out $20. Anyone have any ideas? Thanks ahead of time!

Slight update after playing with it for a while this morning... I was able to get it to show the TWRP splash screen, before it fully loads TWRP, in NRT. But, as always it just hangs there while NRT is "Rebooting your device into bootloader mode..." I'm starting to think it has a bad emmc? I'm not too well versed on hardware, but I've tried nearly every option possible I think. Anyone have any other ideas?

CKrzacz said:
Slight update after playing with it for a while this morning... I was able to get it to show the TWRP splash screen, before it fully loads TWRP, in NRT. But, as always it just hangs there while NRT is "Rebooting your device into bootloader mode..." I'm starting to think it has a bad emmc? I'm not too well versed on hardware, but I've tried nearly every option possible I think. Anyone have any other ideas?
Click to expand...
Click to collapse
If you are using the official TWRP app you then you should use the customized version. The omnirom thread got one you can download: https://forum.xda-developers.com/nexus-10/orig-development/rom-t3045066
Direct link: https://androidfilehost.com/?w=files&flid=205355

So I used NRT to attempt to flash 3.1.1 onto the tablet, it froze on the TWRP flash screen showing version 3.0.2-0. I'm wondering now if the recovery that was on it before I purchased went corrupt? I

Update: Did a manual "fastboot boot "PATH TO 3.1.1-0-manta.img" and same thing....it just gets to the splash screen and freezes....

Another update.... "adb devices" shows it in recovery....yet it just shows the splash screen still. This makes NO sense to me lol.... This is the first I've been able to get adb to recognize it, but the bootloader is locked, nor will it unlock (it freezes), so I feel that it's useless that I've got it this far and yet nothing. Ugh...

Update the bootloader (from google's official images) to latest. then TWRP will boot

Pushing "perm-recovery-signed.zip" to your device:
adb push "C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Root_Files\perm-recovery-signed.zip" "/sdcard/!ReadyToFlash/Root_Files/perm-recovery-signed.zip"
100% /sdcard/!ReadyToFlash/Root_Files/perm-recovery-signed.zip
Hash verifying file transfer:
f63500d8c095c0e749cd78851ba409f8 = Local Hash
f63500d8c095c0e749cd78851ba409f8 = Device hash
+ Verified!
Pushing "openrecoveryscript" to your device:
adb push "C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Root_Files\openrecoveryscript" "/cache/recovery/openrecoveryscript"
100% /cache/recovery/openrecoveryscript
Hash verifying file transfer:
7c02d031e244df4f5a47a7cd3297e53f = Local Hash
7c02d031e244df4f5a47a7cd3297e53f = Device hash
+ Verified!
Rebooting your device into bootloader mode...
adb reboot bootloader
Here's the NRT log. It just hangs with the TWRP splash screen still (after reinstalling the bootloader, then reinstalling TWRP) and won't go back into bootloader. When I hard reboot it, it's back to square one with not being able to boot into recovery (locks up at google logo) or allow oem unlock to process (locks up on the unlock screen when I press power button on "yes").

I know this thread is a few years old, but have you been able to solve the problem? I'd like to use my old Nexus 10 as a WiFi picture frame, but it is bricked in the same way as yours. I cannot get past the google splash screen, bootloader unlock won't work even though it is recognized via fastboot. Flashed latest image and bootloader from google, but did not change anything.

Moto E4 (woods) Bootloop

Hi all,
I had recently unlocked my bootloader on my moto e4 (woods), installed twrp, and install magisk, and everything was going smoothly. Until recently, where i had a OTA update for the device. Me not thinking, i installed the update and then my device refused to boot to system, and only rebooted to twrp. I tried everything to get it to boot, but it just didn't.
I today, found on another thread, that you could reinstall the stock firmware onto the device, and followed the instructions, which were basically just running 'fastboot erase ----' and 'fastboot flash ----'. Everything was going well, until i came to system, which failed to install. I then tried restarting the device (because i wasn't thinking properly), and now the device will show the boot screen for approx 10 seconds then loop again. It has the message of ">device unlocked" at the bottom of the screen, and the moto logo and "powered by android writing on it". I have tried to access the recovery and bootloader on the device by using the hardware buttons, but there was no luck when i was doing it. It would just carry on with it's bootloop. I also tried plugging the device into a windows system, and ran 'adb devices', and 'fastboot devices' but nothing was being picked up. I also checked device manager, and no new devices were being shown.
I am 99% sure that i have indeed hard bricked the device, but i am turning to the amazing people of XDA devs for any help or tips that they can give to possibly get the device back and running.
Anything will be useful, since i can't make the device any less usable now anyway.
Thank you to anyone that replies

just Google the model number and get the original stock firmware and use SP flash tools and the scatter file took a hit to the latest firmware then use fastboot commands to unlock the bootloader flash custom recovery and root the device