Database Users

Oh No ...

So, I just picked up my new Nexus 7, dinked around a bit with it, then wanted to unlock and root it for alternative rom support. I went about doing everything, except when I went to begin the root, which looked like it was going smoothly, I realized that I did not enable USB Debugging.
I am not able to put it back to stock, nor am I able to load anything to it. I can get into FastBoot but thats it.
Any help would be appreciated. I have searched, but I could not find anything on enabling USB debugging remotely from a Mac. I am on Mac OS.

You're fine. Just search how to setup fastboot on a Mac. (Couldn't tell you, though I'm sure its close to you'd do it on Linux, and you'll need to find the Mac fastboot binary and new system.IMG(possibly a whole reflash)), then just do these commands-
fastboot oem unlock (if you've already done this skip this step)
fastboot flash system system.img
(If this doesn't work, find the entire flash all package and do)-
./flash-all.sh
(Will be something like this, you'll have to research yourself.)

Your best bet might be to use fastboot to flash the stock recovery back on the device and then use adb sideload from recovery to flash a stock system image. That would take you completely back to stock and then you could start over.
Sent from my Galaxy Nexus using Tapatalk 4

Sorry, I should have been more specific. All of the steps listed for the all of the guides require me to eventually put my tablet into USB Debugging mode. I can't do that. I can't boot into the Android system at all. I get the lovely dead robot with read warning symbol.
Is there any way to enable USB Debugging without system access on the tablet? Is this just a paper weight now? I have rooted and such since my original Nook Color, so I am not dunce. I just don't understand how I can do any of the guides if all of them call for me to put the tablet into USB debugging mode.

You only need debugging enabled to use ADB (in recovery or the OS). Fastboot will still work regardless.

NexusChrist said:
Sorry, I should have been more specific. All of the steps listed for the all of the guides require me to eventually put my tablet into USB Debugging mode. I can't do that. I can't boot into the Android system at all. I get the lovely dead robot with read warning symbol.
Is there any way to enable USB Debugging without system access on the tablet? Is this just a paper weight now? I have rooted and such since my original Nook Color, so I am not dunce. I just don't understand how I can do any of the guides if all of them call for me to put the tablet into USB debugging mode.
Click to expand...
Click to collapse
Ddi11igaf told you wat to do.
Download the full image and reset it to stock. Start again.
You are never bricked if you can get to fastboot.
:good:

Perhaps this will help:
There is currently, for some reason, no OS installed on the tablet. I do not have any roms or a backups saved on the tablet. I just want to go back to stock and start over.
I can't get into the tablet to enable USB debugging.
Is there a way to get a rom onto the tablet without USB debugging? I realize that Fast Boot works, and so does my recovery, but there is no OS installed, and no way for me to put an OS on it if I don't have USB debugging.

We understand, but you're under the false impression that USB debugging needs to be enabled to use fastboot and flash from there. It doesn't. All you have to do is unlock the bootloader (if you didn't do that already) and flash a stock ROM from https://developers.google.com/android/nexus/images. Download the stock ROM to your Mac and use the fastboot commands someone posted above. If it's not working, it's a driver issue with your Mac.

tweaked said:
Ddi11igaf told you wat to do.
Download the full image and reset it to stock. Start again.
You are never bricked if you can get to fastboot.
:good:
Click to expand...
Click to collapse
And how would one go about putting that image on the unit to flash it?
This is what I get when I try to use the one-click method from AndroidRootz:
***************************************************************
This script will: Unroot The New Nexus 7 to Stock 4.3 & Lock your Bootloader
For more details go to AndroidRootz
***************************************************************
Warning! This will delete everything on your device! BACKUP your device!
First make sure your in FASTBOOT MODE!
Press enter to continue
sending 'bootloader' (3911 KB)... OKAY
writing 'bootloader'... OKAY
rebooting into bootloader... OKAY
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-03.14
Baseband Version.....: none
Serial Number........: 07974778
--------------------------------------------
checking product... OKAY
checking version-bootloader... OKAY
sending 'boot' (6880 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (7424 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (603495 KB)... ERROR: usb_write failed with status e00002be
FAILED (data transfer failure (No such file or directory))
Your device is now stock and unrooted
However the bootloader is still unlocked
Let your device boot up, set up your device or skip the set-up
Place your phone in USB debugging mode
Settings > Developer Options > USB Debugging, If you don't have that option
Use this guide:
Connect USB cable if your disconnected
Press enter to relock the bootloader
If I hit enter after that it simply says device not found. Again, it's asking me to put it into USB debugging, but I can't because it failed to put the OS on the device.

Looks like it was working fine, until it went to write the OS (system). Perhaps the system.img is missing or corrupt. Try downloading it direct from the link I posted above and flashing with that.

NHLWil said:
Looks like it was working fine, until it went to write the OS (system). Perhaps the system.img is missing or corrupt. Try downloading it direct from the link I posted above and flashing with that.
Click to expand...
Click to collapse
Thanks, I have it downloaded. And installed ADB and FastBoot on my Mac.
Do you have the specific steps on how to flash a rom from my computer via fastboot?

You should just be able to:
fastboot flash system system.img
If it's not working, then you'll probably need the fastboot executable from the official Android SDK for Mac, as I know someone from work had an issue flashing with one they got from elsewhere.

NHLWil said:
You should just be able to:
fastboot flash system system.img
If it's not working, then you'll probably need the fastboot executable from the official Android SDK for Mac, as I know someone from work had an issue flashing with one they got from elsewhere.
Click to expand...
Click to collapse
I was able to download it, and it sees my device, and I can perform most of the operations, however; As soon as I try to do a flash all this is what I get:
"OTT1-COMM-CK-MBP15-2400:android xxxxxx$ ./fastboot flashall flash-all.sh
error: neither -p product specified nor ANDROID_PRODUCT_OUT set"

So here is what I did, and all went well again until the System part: Run fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-flo-flo-03.14.img
fastboot reboot-bootloader
fastboot -w update image-razor-jss15q.zip
And this was the output:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-03.14
Baseband Version.....: none
Serial Number........: 07974778
--------------------------------------------
checking product... OKAY
checking version-bootloader... OKAY
sending 'boot' (6880 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (7424 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (603355 KB)... ERROR: usb_write failed with status e00002be
FAILED (data transfer failure (No such file or directory))

I just did the same steps on my wife's PC and it worked perfectly.
Maybe something weird with the PC, I'm not sure. But all is well.
Thanks for the help!

NexusChrist said:
So here is what I did, and all went well again until the System part: Run fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-flo-flo-03.14.img
fastboot reboot-bootloader
fastboot -w update image-razor-jss15q.zip
And this was the output:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-03.14
Baseband Version.....: none
Serial Number........: 07974778
--------------------------------------------
checking product... OKAY
checking version-bootloader... OKAY
sending 'boot' (6880 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (7424 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (603355 KB)... ERROR: usb_write failed with status e00002be
FAILED (data transfer failure (No such file or directory))
Click to expand...
Click to collapse
Boot into recovery using Power+VolDown
Then redo your above steps, but skip the erase lines at the beginning.
See if that helps.

NexusChrist said:
So here is what I did, and all went well again until the System part: Run fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-flo-flo-03.14.img
fastboot reboot-bootloader
fastboot -w update image-razor-jss15q.zip
And this was the output:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-03.14
Baseband Version.....: none
Serial Number........: 07974778
--------------------------------------------
checking product... OKAY
checking version-bootloader... OKAY
sending 'boot' (6880 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (7424 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (603355 KB)... ERROR: usb_write failed with status e00002be
FAILED (data transfer failure (No such file or directory))
Click to expand...
Click to collapse
Pretty sure this error was your fastboot binary. You need the one from the SDK for a mac(I guess possibly a problem with your USB port, doubt it though since fastboot was talking to your device)

[Q] writing 'bootloader'... FAILED (remote: (Unknown error code))

My N7 "2012" kept freezing, so I put it in bootloader and tried to do a recovery mode reset to stock. It froze during the process.
Now, the only thing I can do is get it into bootloader mode manually by holding the buttons. It frezes if I choose any of the options from the bootloader screen including restarting the bootloader from the bootloader screen without holding power and volume.
I have tried the Nexus Root Toolkit a bunch of times with the "flash stock + unroot (soft bricked)" feature, testing different factory builds and the best results are below:
Flash Stock + Unroot...
------------------------------------------------------------------
erasing 'boot'...
OKAY [ 2.526s]
finished. total time: 2.526s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.200s]
finished. total time: 0.200s
erasing 'recovery'...
OKAY [ 0.016s]
finished. total time: 0.016s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.015s]
finished. total time: 0.015s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.015s]
finished. total time: 0.015s
sending 'bootloader' (2100 KB)...
OKAY [ 0.264s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 0.402s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.021s
< waiting for device >​
PLEASE HELP! Keep in mind that I am a newb to messing with this stuff.
I have read forums and tried things that people suggested to others in similar situations, but I am pretty lost at this point. Keep in mind that my device is almost certainly wiped and definitely will not boot the OS.

Is your N7 the Wi-Fi or the 3G variant?
What was the name of the factory image you were trying to flash?

brad3626 said:
My N7 "2012" kept freezing, so I put it in bootloader and tried to do a recovery mode reset to stock. It froze during the process.
Now, the only thing I can do is get it into bootloader mode manually by holding the buttons. It frezes if I choose any of the options from the bootloader screen including restarting the bootloader from the bootloader screen without holding power and volume.
I have tried the Nexus Root Toolkit a bunch of times with the "flash stock + unroot (soft bricked)" feature, testing different factory builds and the best results are below:
PLEASE HELP! Keep in mind that I am a newb to messing with this stuff.
I have read forums and tried things that people suggested to others in similar situations, but I am pretty lost at this point. Keep in mind that my device is almost certainly wiped and definitely will not boot the OS.
Click to expand...
Click to collapse
After doing a bit of research, I've found out that there is a BAD version of the N7 2012 bootloader 4.23 floating around. The unsettling thing is that it's being supplied with a couple of the factory images that come straight from from the Google android devolpers page online. Anyway to make a long story short, I would try flashing the working version of the bootloader first off, then go from there with a factory reset. You can download the the working bootloader (bootloader-grouper-4.23.img) HERE --> h t t p : / / g o o . g l / q A D S A z (sorry about the spaces in the url, I'm new to the forum and can't post links yet, just delete the spaces)
BTW, its the same bootloader for N7 wifi OR 3G. md5 = df53028033c9eccf4fe5ba7bc198ce24
Here's how to install using fastboot:
1. Reboot To Your Bootloader On You Nexus 7 (Power off power button and volume down until you see bootloader screen)
2. Connect Your Nexus 7 To Your Computer
3. Open Up Command Prompt or terminal window (not sure if you are using windows/mac/linux)
4. CD to where you downloaded bootloader-grouper-4.23.img
5. Then type:
fastboot devices (to see if your N7 is connected correctly)
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
Then try the factory reset again.
If you don't have fastboot installed your computer you need it. Makes flashing your N7 a breeze... lock/unlock, custom recovery installs, going back to factory stock, all much more easy with fastboot.
You can get it from the android devolper site, h t t p : / / g o o . g l / 2 q p r for windows/mac/linux. All you need is the SDK tools, not the ADT bundle.

adomol said:
After doing a bit of research, I've found out that there is a BAD version of the N7 2012 bootloader 4.23 floating around. The unsettling thing is that it's being supplied with a couple of the factory images that come straight from from the Google android devolpers page online. Anyway to make a long story short, I would try flashing the working version of the bootloader first off, then go from there with a factory reset. You can download the the working bootloader (bootloader-grouper-4.23.img) HERE --> h t t p : / / g o o . g l / q A D S A z (sorry about the spaces in the url, I'm new to the forum and can't post links yet, just delete the spaces)
BTW, its the same bootloader for N7 wifi OR 3G. md5 = df53028033c9eccf4fe5ba7bc198ce24
Here's how to install using fastboot:
1. Reboot To Your Bootloader On You Nexus 7 (Power off power button and volume down until you see bootloader screen)
2. Connect Your Nexus 7 To Your Computer
3. Open Up Command Prompt or terminal window (not sure if you are using windows/mac/linux)
4. CD to where you downloaded bootloader-grouper-4.23.img
5. Then type:
fastboot devices (to see if your N7 is connected correctly)
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
Then try the factory reset again.
If you don't have fastboot installed your computer you need it. Makes flashing your N7 a breeze... lock/unlock, custom recovery installs, going back to factory stock, all much more easy with fastboot.
You can get it from the android devolper site, h t t p : / / g o o . g l / 2 q p r for windows/mac/linux. All you need is the SDK tools, not the ADT bundle.
Click to expand...
Click to collapse
Thank you for the help, unfortunately, it did not work.
I followed the instructions above, but the Nexus displayed "neither up nor cac partitions found" over and over
While cmd displayed:
C:\Users\Brad>fastboot devices
XXX fastboot
C:\Users\Brad>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.281s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 3.213s
C:\Users\Brad>fastboot devices
XXX fastboot
C:\Users\Brad>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.271s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 3.205s​

Erovia said:
Is your N7 the Wi-Fi or the 3G variant?
What was the name of the factory image you were trying to flash?
Click to expand...
Click to collapse
Wi-Fi
I have tried every one that the NRT offered.

Just read this guide and download the latest factory image from here.
Good luck.

Erovia said:
Just read this guide and download the latest factory image from here.
Good luck.
Click to expand...
Click to collapse
I read that guide.
But that guide seems to be written with the assumption that the device can boot into the OS
No ADB device is found because I can only boot into bootloader.

That part is only for the driver installation. You can skip to the "Extract the Factory Image" part and follow it from there.

Erovia said:
That part is only for the driver installation. You can skip to the "Extract the Factory Image" part and follow it from there.
Click to expand...
Click to collapse
Following from "Extract the Factory Image" part, this is what I am getting:
C:\Users\Brad>cd \Users\brad\AppData\Local\Android\android-sdk\platform-tools
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot devices
XXX fastboot
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>adb reboot-bootlo
ader
error: device not found
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot oem unlo
ck
...
FAILED (command write failed (Unknown error))
finished. total time: 0.590s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase bo
ot
erasing 'boot'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase ca
che
erasing 'cache'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase re
covery
erasing 'recovery'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.022s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase sy
stem
erasing 'system'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase us
erdata
erasing 'userdata'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.018s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot flash bo
otloader bootloader-grouper-4.23.img
error: cannot load 'bootloader-grouper-4.23.img': Invalid argument​

On the bootloader screen is your bootloader shown as "locked" or "unlocked" ?

Erovia said:
On the bootloader screen is your bootloader shown as "locked" or "unlocked" ?
Click to expand...
Click to collapse
lock state - unlocked

What's the output of fastboot -w update image-nakasi-kot49h.zip ?

Erovia said:
What's the output of fastboot -w update image-nakasi-kot49h.zip ?
Click to expand...
Click to collapse
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot -w updat
e image-nakasi-kot49h.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
error: out of memory​

I have no idea what this "out of memory" error is. If I were you I would restart my computer, run fastboot from a cmd opened as Admin and try out different usb ports.

Erovia said:
I have no idea what this "out of memory" error is. If I were you I would restart my computer, run fastboot from a cmd opened as Admin and try out different usb ports.
Click to expand...
Click to collapse
I restarted, ran cmd as admin and tried every USB port and got this as the result each time:
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot -w updat
e image-nakasi-kot49h.zip
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: XXX
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.016s]
sending 'boot' (4992 KB)...
OKAY [ 5.460s]
writing 'boot'...
FAILED (remote: (FileWriteFailed))
finished. total time: 8.518s​
The Nexus was frozen at this point and had to be manually forced to restart bootloader.

Do you have a valid warranty for the N7? I'm asking because it seems that your N7's internal memory got corrupted. I might not be right, but that's my best guess.

Erovia said:
Do you have a valid warranty for the N7? I'm asking because it seems that your N7's internal memory got corrupted. I might not be right, but that's my best guess.
Click to expand...
Click to collapse
Thanks for your help
I bought it 13 months ago (perfect timing, coincidentally, right?), so if I could find the receipt I would still be screwed.

I would still try to send it to Asus or Google. Maybe they repair it for a reasonable price.
(But if you plan to do that try to relock you bootloader with fastboot oem lock)

Erovia said:
I would still try to send it to Asus or Google. Maybe they repair it for a reasonable price.
(But if you plan to do that try to relock you bootloader with fastboot oem lock)
Click to expand...
Click to collapse
fastboot oem lock
...
(bootloader) Bootloader is locked now.
OKAY [ 36.032s]
finished. total time: 36.032s​
But then the N7 freezes and after manually restarting in bootloader it is still unlocked.

Then send is as it is. You can't do any more about it.
Good luck.

[HELP] Soft-brick, cannot unlock bootloader

With what seems to be a soft-brick Google Nexus 7 2012 Wi-fi model, I tried going through comminus' tutorial on both my laptop and my desktop, but I end up with the following error message when I try to unlock the bootloader, an essential part to fixing my boot loop/soft-brick problem. I am unrooted, by the way, so TWRP and other custom recoveries are not an option unless there is a way to flash them via fastboot. I cannot access ADB in any way whatsoever.
Code:
android-sdk\platform-tools>fastboot oem unlock
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: (Unknown error code))
finished. total time: XX.XXXs
Of course, any attempt at flashing anything would result in no avail, neither:
Code:
android-sdk\platform-tools>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)
FAILED (remote: Bootloader is locked.)
finished. total time: X.XXXs
android-sdk\platform-tools>fastboot -w update image-nakasi-jwr66y.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
———————————————————————————————————————————————————
Bootloader version...: 4.23
Baseband version.....: N/A
Serial Number........: (insert unique serial here)
———————————————————————————————————————————————————
checking product...
OKAY [ X.XXXs]
checking version-bootloader...
OKAY [ X.XXXs]
sending 'boot' (4896 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: X.XXXs
I have verified that both computers can detect my device correctly via the fastboot devices command.
I do not understand what is wrong with my device at this point. Any pointers or tips would be greatly appreciated.

Bump. I could use some help regarding this issue, preferably before I have to depart for Los Angeles on the 2nd!

RinDunois said:
Bump. I could use some help regarding this issue, preferably before I have to depart for Los Angeles on the 2nd!
Click to expand...
Click to collapse
Have you tried Wug's Toolkit? I have been here myself, checked the softbricked option and even had to flash back as far as 4.4.2. Place your device in fastboot and check the soft brick option let me know where you get with this suggestion.

I just wanted to let you know that the first thing I noticed is the following error:
FAILED (remote: Bootloader is locked.)
This has to be unlocked first before you will be able to flash the OTA. You can use wuget tool to unlock the bootloader and then try to use fastboot. Once that is done, you can relock it if you want.

PapaMag said:
Have you tried Wug's Toolkit? I have been here myself, checked the softbricked option and even had to flash back as far as 4.4.2. Place your device in fastboot and check the soft brick option let me know where you get with this suggestion.
Click to expand...
Click to collapse
That was one of the first things I tried, actually, on suggestion of some friends who have experience with the device. Sadly, none of the driver options worked nor did the softbrick option get me anywhere, so I moved onto doing it manually doing it via cmd instead.
barakisbrown said:
I just wanted to let you know that the first thing I noticed is the following error:
FAILED (remote: Bootloader is locked.)
This has to be unlocked first before you will be able to flash the OTA. You can use wuget tool to unlock the bootloader and then try to use fastboot. Once that is done, you can relock it if you want.
Click to expand...
Click to collapse
I am fully aware that I need to unlock the bootloader before doing anything. I wanted to see if the so called flash all script was going to help AFTER seeing that the unlock bootloader command did not work whatsoever as you can see in the first block of code in my post.

Stuck in Fastboot and Rescue Mode [hifi image error]

Hi everyone, I'm done and out of any ideas. Never before have I bricked my phone . Now I don't know what to do. Played before only with Samsung phones, they were waaay easier to play with.
Let me tell you my story:
1. Got P9 Lite with L21C22B120 rom (brand C22 from Poland)
2. No newer version available, decided to debrand / apply newer - flashed L21C432B161 (~3GB update.app), info showed L21C900B161 - need to change oeminfo etc.
3. [SRK Tool ] Unlocked bootloader and installed TWRP
4. [SRK Tool + TWRP] Built Root method via adb sideload failed, so installed SuperSu via TWRP from another source - success
5. [SRK Tool] Flashed oeminfo C432 Europe - success, but after that info showed C432B161 without L21
6. Flashed once more with the same B161 firmware - perfect info L21C432B161 but UI theme and icons got corrupted like that: https://forum.xda-developers.com/p9-plus/help/wrong-icons-c900-to-c432-failed-im-t3490561 and tried to flash mentioned hw_folder with SRK Tool.
7. [TWRP] Played with wipe / factory reset - couldn't boot anymore, TWRP showed "No OS installed" and "unable to mount /data" (it had 0MB, couldn't wipe it)
8. Then RESCUE MODE showed up and still I can't pass by it - exactly like here: https://forum.xda-developers.com/p8lite/help/stuck-rescue-mode-screen-please-help-t3244872 - only fastboot&rescue available.
What I have tried several times:
1. Flashing firmware C432B161 and C432B120 - failure at 5% (incompatibility)
2. Fastboot flash boot.img, recovery.img, system.img and cust.img (extracted from B120 and B161)- success, still rescue mode loop
3. Locking and unlocking bootloader with SRK Tool, flashing stock recovery and TWRP - success, still unable to load any recovery
4. Fastboot flashing FW_hifi.img - FAILED <remote: command not allowed>
Summary:
1. Looped Rescue mode shows: Please update system again, Func no : 8 (hifi image), Error no : 1 (security verify failed)
2. Fastboot&Rescue mode shows: Phone unlocked, FRP Unlock. Fastboot works.
3. Flashing main images doesn't change enything, can't flash corrupted(?) hifi image.
4. Maybe there is something wrong with my Bootloader? Is it truly unlocked? SRK Tool shows bootloader "unlocked" but many of the fastboot commands (i.e. getvar or oem) return "Failed, remote: command not allowed"
Any ideas in any of your clever or experienced heads? Should I try to flash that magical hifi image somehow or to flash some "compatibile" firmware (don't know which one wouldn't return that error).

Tried some fastboot commands, seems like I have found the reason for ROMs incompatibility:
fastboot getvar rescue_version
rescue_version: rescue0.3
finished. total time: 0.071s
fastboot getvar rescue_phoneinfo
rescue_phoneinfo: VNS-C432B161
finished. total time: 0.011s
fastboot oem get-product-model
...
(bootloader) hi6250
OKAY [ 0.011s]
finished. total time: 0.013s
fastboot oem get-psid
...
(bootloader) SN:BUC4C16929(...)
(bootloader) IMEI:863126032(...)
(bootloader) IMEI:863126032(...)
OKAY [ 0.011s]
finished. total time: 0.012s
fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.010s
fastboot oem check-rootinfo
...
(bootloader) old_stat: SAFE
(bootloader) now_stat: SAFE
(bootloader) change_time: 0000000000
(bootloader) Check System: Decode fail
OKAY [ 0.018s]
finished. total time: 0.020s
fastboot oem get-build-number
...
(bootloader) :VNS-C432B161
OKAY [ 0.012s]
finished. total time: 0.013s
fastboot oem device-info
...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
What happened to L21 model in my build and model number? Is it corrupted?

Install os manually via adb mounting boot system and the other two things (i don't remember all and i don't have any link)

You can go to Twrpmeticulus?

Thanks guys! I flashed Meticulus TWRP - still couldn't enter it but accidentally discovered the (weird) way. I could go to it only with USB cable connected to computer and by pressing Vol+, Vol- and Power simultaneously, releasing them upon Huawei Logo. From there (TWRP) I rooted my device (adb sideload SuperSU 2.65), replaced oeminfo file via this tutorial - https://forum.xda-developers.com/huawei-p9lite/how-to/request-oeminfo-c432-p9-lite-t3427386 - and voila, I could finally flash C432B161 ROM without incompatibility error. Problem solved, hifi error gone of course.

Nexus 10 bootloop without bootloader

Hello Forum,
i've buyed recently a Nexus 10 tablet in order to install a Nethunter distribution on it but on this tablet seems that bootloader is not present. Is it possible?
I've tried to enter it thousand times using buttons power - vol up - vol down but nothing, tablet vibrates but nothing appear on screen.
At the moment mu tablet is on bootloop and i don't know how to fix it without access the bootloader.
I'm continuing trying also with fastboot and adb command.
Do you have any solution?
Regards

LITTLE UPDATE: i'm able to establish a connection using fastboot but i can't flash nothing cause my OEM is locked and if i try to enter fastboot oem unlock nothig appens.
fastboot update image-mantaray-lmy49j.zip
--------------------------------------------
Bootloader Version...: MANTAMF01
Baseband Version.....: no modem
Serial Number........: R32D202YHVP
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Checking 'version-bootloader' OKAY [ 0.000s]
extracting boot.img (4 MB) to disk... took 0.009s
archive does not contain 'boot.sig'
Sending 'boot' (4966 KB) OKAY [ 0.626s]
Writing 'boot' FAILED (remote: 'Locked - Use "fastboot oem unlock" to Unlock')
fastboot: error: Command failed
C:\Users\ShUtDoWn\Downloads\ROOT NEXUS 10\platform-tools_r31.0.0-windows\platform-tools>fastboot devices
R32D202YHVP fastboot