Database Users

[Q] I've inherited an original (broken?) Nexus 7

Apologies if I'm asking anything blatantly obvious, I'm relatively new to all things Android..
The Nexus 7 I have won't boot it just displays the Google logo & an open padlock.
I've been advised to try the Nexus Root Toolkit & it's Soft-Bricked/Bootloop option.. unfortunately this doesn't work:
erasing 'boot'
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
erasing 'cache'...
erasing 'recovery'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
erasing 'system'
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
erasing 'userdata'
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
sending 'bootloader' (3911 KB)
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
archive does not contain 'boot.sig'
error: out of memory
Any help would be greatly appreciated
Thanks.

If the padlock is opened chances are there is a custom recovery see if u can boot into it. Hold volume up and down together and power
Sent from my SGH-T679 using Tapatalk

...Awesome... said:
If the padlock is opened chances are there is a custom recovery see if u can boot into it. Hold volume up and down together and power
Sent from my SGH-T679 using Tapatalk
Click to expand...
Click to collapse
Nope, I can't do that.. it just starts the bootloader & I can't select anything when it's on
The bootloader screen info is as follows:
FASTBOOT MODE
PRODUCT NAME - grouper
BOOTLOADER VERSION - 3.34
LOCK STATE - Unlocked

you might be able to soft-boot it (that is, have it boot a custom recovery without actually flashing it to the eMMC chip) as in:
Code:
C:\blech> fastboot boot eg-custom-recovery-imagefile-of-your-choice-goes-here.img
and have a look using adb at the kernel boot messages from that custom recovery's boot log (once it has finished booting)
Code:
C:\blech> adb shell dmesg > dmesg_log.txt
my guess (because fastboot erases are failing) is that it might boot but will not recognize any valid partition tables - you will see messages to that effect in the kernel log.
If that's the case, there is nothing you can do to fix it.

[ADB & FASTBOOT] Problem with flashing TWRP FAILED (remote: Command not allowed)

Hi Guys! After brick, my p9l have red "menu" at start and text "Failed verificatnion" or smth like this.
I can't flash TWRP because of FAILED (remote: Command not allowed).
Bootloader & FRP unlocked.
Adb isn't working at bootloader, only fastboot is working.
I want to rollback to 6.0. I have dload with file on my sdcard but i can't flash oeminfo without twrp.
How to fix it?
Code:
E:\tele\SRKToolHuawei-STABLE-V1.3-20160619>FASTBOOT flash recovery EliteTWRP.img
target reported max download size of 471859200 bytes
sending 'recovery' (24452 KB)...
OKAY [ 0.618s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.632s
I want to say sorry for my english :/

Try to flash TWRP with P9 lite toolkit

[Q] Nexus 7 (2012) cannot get into recovery mode

Hello all,
I wanted to flash stock + unroot my device with the Nexus Root Toolkit from WugFresh but obviously something went wrong.
target didn't report max-download-size
sending 'bootloader' (2100 KB)...
OKAY [ 0.312s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 0.453s
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.036s
< waiting for any device >
Now the only thing i can do is to boot into the bootloader mode manually. Usb debugging is not enabled and I have no idea how to do that with the device in this state.
fastboot devices gives me the following output:
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot devices
015d3c269c3bf404 fastboot
I can also boot into TWRP:
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot boot twrp-3.2.3-0-grouper.img
downloading 'boot.img'...
OKAY [ 1.229s]
booting...
OKAY [ 0.021s]
finished. total time: 1.254s
In this state I can also enter adb commands:
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>adb devices
List of devices attached
015d3c269c3bf404 recovery
But here I am stuck and I cannot mount the partitions. I tried to repair the file system, i.e. wipe -> advanced wipe -> select partitions to wipe (e.g. system) -> swipe to wipe gives the following output:
Failed to mount '/system' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
If I select in TWRP reboot to bootloader the screen stays black. The only thing left is to press the power button + volume down and then I am again back in the bootloader mode.
fastboot reboot-bootloader does not bring me back in the bootloader mode.
I tried to flash the boot partition with NRT and get the following output:
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
015d3c269c3bf404 fastboot
+ Fastboot Device Connected
Flashing Stock Kernel to BOOT partition...
fastboot flash boot "C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Stock_Kernel\stock_kernel_nakasi_5.1.1_LMY47V.img"
Rebooting your device...
Done!
adb devices
fastboot devices
???????????? fastboot
Is there any hope that I get this device working again? I have no more idea what to do and I would appriciate any help.

Twrp error

Can someone help me with getting the twrp recovery system on my moto. i keep getting the error
PS C:\Users\Avery\Desktop\platform-tools> ./fastboot boot C:\Users\Avery\Downloads\twrp-installer-3.5.2_10-0-river.zip
creating boot image...
creating boot image - 19036160 bytes
Sending 'boot.img' (18590 KB) OKAY [ 0.398s]
Booting FAILED (remote: '')
fastboot: error: Command failed
I am trying to root my phone but i need to get twrp working in order to do that.
Can someone help me?

oh and my bootloader is unlocked

Error when trying to Flash twrp on my P8 Lite 2017

When i try to Flash twrp on my Device (unlocked bootloader) i always get this error:
Warning: skip copying recovery image avb footer (recovery partition size: 0, recovery image size: 27711488).
Sending 'recovery' (27062 KB) OKAY [ 0.684s]
Writing 'recovery' FAILED (remote: 'partition length get error')
fastboot: error: Command failed
idk how to fix that. Can someone help?