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.

I was trying to boot into recovery without unlocking bootloader. but failed why?

fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.663s]
booting...
FAILED (remote: not allowed)
finished. total time: 0.669s
after unlocking bootloader this problem persists.and getting this again.
Earlier i was stuck in bootloop after flashing twrp. and also loading supersu update.zip.
please help me to boot into recovery. and also the safe way to Root this phone.

L5 E610 - bricked - only fastboot - Secure booting error

Hello out there,
I get a used L5 for my little son, tryed to clear all data (factory reset) and it just partically worked, some data always survied.
I thougt, no prob, then I use recovery. when I tried to boot the recovery mode I saw the Message:
Secure booting error! Cause: boot certification verifiy
HM!
OK Lets try to install a custom recovery (first rooted with kingo, then install twrp 3 with dd)
Jet I only get the Message on booting nothing else is possible. fastboot is available.
Update the ROM with KDZ updater dosn`t work " No connection to phone"
I need *.img files that I can use with fastboot. I tryed to convert a kdz with two tools I found ( a python script and a tool developed for the G series) but that dosn`t work.
Is there a simple way to convert a ZIP to a IMG?
I tryed "fastboot boot recovery.img" and to flash it, but that also dosn`t work (orig. and TWRP)
I also get this:
Code:
C:\Users\mariu>fastboot erase userdata
erasing 'userdata'...
FAILED (status read failed (Too many links))
finished. total time: 2.489s
C:\Users\mariu>fastboot erase cache
erasing 'cache'...
FAILED (status read failed (Too many links))
finished. total time: 2.487s
C:\Users\mariu>fastboot -w
Erase successful, but not automatically formatting.
File system type not supported.
Erase successful, but not automatically formatting.
File system type not supported.
erasing 'userdata'...
FAILED (status read failed (Too many links))
finished. total time: 2.476s
C:\Users\mariu>fastboot flash boot C:\Temp\L5\boot.img
sending 'boot' (4864 KB)...
OKAY [ 0.463s]
writing 'boot'...
OKAY [ 1.330s]
finished. total time: 1.800s
THX for help

oops need help

dont know how ive done it but removed everything of the phone :crying: all i can do is get into bootloader
twrp is giving me this
fastboot boot twrp-3.2.3-1-fajita.img
downloading 'boot.img'...
OKAY [ 0.698s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.714s
cant sideload
any ideas im out of them
thanks

Msmdownload see in guide news section select the one fitted for your model

Fastboot flash recovery stuck at Sending Recovery

Hi. Can someone assist me. I am not able to flash twrp in my Realme 2 Pro. It is stuck in Sending Recovery or it shows error as "FAILED (remote: 'unknown command')" ; "FAILED (Write to device failed (Invalid argument))"
Code:
PS C:\platform-tools> fastboot boot twrpr2p.img
Sending 'boot.img' (29304 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
PS C:\platform-tools> fastboot flash recovery twrpr2p.img
Sending 'recovery' (29304 KB) FAILED (remote: 'unknown command')
fastboot: error: Command failed
PS C:\platform-tools> fastboot flash recovery twrpr2p.img
Sending 'recovery' (29304 KB)

Never mind. It was just issue with my Windows 10 laptop. Works fine when using Linux.