Related
Hi all,
I think I just toasted my Nexus 7 3G while trying to upgrade the radio/bootloader, but before I toss it in the trash I wanted to see if many someone had any ideas I have yet to try.
Thanks in advanced to anyone who can help me!
The Problem:
Nexus 7 wont boot and is stuck on the Google logo with the unlocked bootloader icon. Cant boot to boot loader using Power + Volume Down. When I do Power + Both Volume Up and Down the screen goes black after showing the Google logo and my PC detects the device but cant find drivers and dont get anything out of fastboot commands. Power + Volume up does nothing.
Because the unlocked bootloader icon I doubt I could get away with sending it back.
What I did:
I was running CM10.1 with Bootloader unlocked
I installed the following 4.3 ROM - http://forum.xda-developers.com/showthread.php?t=2381991
Rebooted <-- Everything was fine but running on older Radio/Bootloader
I started following the following instructions to upgrade radio + bootloader - http://forum.xda-developers.com/showthread.php?t=2175086
I used TWRP to install the Recovery zip
Rebooted to bootloader
Fastboot Flashed bootloader
<<Forgot to Flash Recovery>>
Rebooted <-- everything was working
Rebooted to bootloader
Fastboot Flashed Radio
Rebooted << TWRP launched instead of stock recovery
Rebooted to bootloader
Fastboot Flashed bootloader
Fastboot Flashed recovery << Did not reflash recovery zip first >>
Rebooted <-- seemed ok
Rebooted to bootloader
Fastboot Flashed radio
Rebooted <<No Recovery Showed Up>>
Stuck with Google logo with unlocked bootloader icon and cant get back into bootloader
Hi Mazeri,
I having the same issue as I explained in the original thread.
I was flash the bootloader recovery and radio. Recovery and Bootloader flashes seemed to be ok but the radio flash run ok but when the n7 rebooted got stuck in the google logo.
I have tried all kind of key combinations with no success.
Here is the transcript of my flash commands:
Code:
~/Downloads ⮀ fastboot flash bootloader bootloader-tilapia-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.258s]
writing 'bootloader'...
OKAY [ 4.140s]
finished. total time: 4.399s
~/Downloads ⮀ fastboot flash recovery Recovery_Stock_Tilapia_4.3.img
sending 'recovery' (10240 KB)...
OKAY [ 1.223s]
writing 'recovery'...
OKAY [ 2.453s]
finished. total time: 3.676s
~/Downloads ⮀ fastboot reboot
rebooting...
finished. total time: 0.020s
~/Downloads ⮀ fastboot devices
015d2XXXXXX0d fastboot
~/Downloads ⮀ fastboot flash radio radio-tilapia-1231_0.18.0_0409.img
sending 'radio' (16384 KB)...
OKAY [ 1.943s]
writing 'radio'...
OKAY [ 4.760s]
finished. total time: 6.702s
~/Downloads ⮀ fastboot reboot
rebooting...
finished. total time: 0.020s
~/Downloads ⮀ fastboot devices
~/Downloads ⮀ fastboot devices
How do you detect the device in your pc? What command are you running?
Im on a mac os x. If I do a fastboot reboot recovery, I get a 'waiting for device' message but there is no information for any combination of key presses.
If you are on a PC, have you tried any toolkit? I've read in a couple of thread that Wug's toolkit have worked to unbrick some devices with issues with the bootloader.
All I did was hold power until the screen goes black, then press and hold both volume up and down. The Google logo shows up and then the screen goes black. Windows then detects a device... but is unable to install a driver for it and it shows up as an unknown device.
Mazeri said:
All I did was hold power until the screen goes black, then press and hold both volume up and down. The Google logo shows up and then the screen goes black. Windows then detects a device... but is unable to install a driver for it and it shows up as an unknown device.
Click to expand...
Click to collapse
Also, I tried with the Nexus 7 tool kit and it failed to detect ADB. Fastboot also does not see the device.
Wug Toolkit also does not seem to work as it requires ADB or Fastboot to be working.
If I could get the device driver to kick in that might work... but something we did while flashs is making the device show up without details such as no device name and no mfg info... so Windows just shuts it down and calls it unknown.
I've got the same prolem Wug or Nexus toolkits cannot detect my N7 .... hix
I just flash the radio and my N7 stuck at Google logo....
amakaru said:
I've got the same prolem Wug or Nexus toolkits cannot detect my N7 .... hix
I just flash the radio and my N7 stuck at Google logo....
Click to expand...
Click to collapse
Maybe we should check what do ourt n7's have in common... It's strange that the flash worked for other n7 but not for ours.
Maybe that radio file is intended for certain devices (?).
Mine is a EU Nexus7 3G bought in early January this year. I guest is in warranty yet but because of the unlock icon in the start screen, the warranty is void
But I think this is not a problem related with the bootloader since the google logo appears and the unlock icon (so the n7 bootloader detects that it is unlock).
The flashing worked with the bootloader but it crashed when the radio was flashed for the three of us, so it is something related with the baseband. The OS installed should not be related since the bootloader and radio baseband are independent from the OS (Maybe you can get a soft brick, stuck in the colored X logo but bootloader should work).
I'm going to try to work finding a solution... but personally Im not feeling very optimistic
Now when I use three button (hold down power & vol + & vol - ) my computer show in device manager : "Android devices/ASUS Transformer APX Interfaces"
Sorry to say, but unless you can get your devices to fastboot mode, I think you're out of luck. It sounds like it doesn't get completely into the bootloader, which is problematic.
It was discussed a while back, and APX mode is a programming mode, but we lack the proper drivers and software to be able to recover anything on the N7 from that. Sorry.
I have a US Nexus 7 3G, got it right when they went on sale.
ameinild said:
Sorry to say, but unless you can get your devices to fastboot mode, I think you're out of luck. It sounds like it doesn't get completely into the bootloader, which is problematic.
It was discussed a while back, and APX mode is a programming mode, but we lack the proper drivers and software to be able to recover anything on the N7 from that. Sorry.
Click to expand...
Click to collapse
Bummer news :'( but I was expecting as much. If we don't find a fix, can we replace the main board to fix or is this problem beyond that point? Don't think selling a bricked device is worth it unless we have 0 options.
adb/fastboot commands
Another one bites the dust.
I should have followed the thread more closely. One of the steps (noticed this after the fact) is to "fastboot reboot", unfortunately this does not reboot the bootloader.
I should've noticed this yesterday after the initial fastboot reboot when I flashed the recovery image. Anywho, I believe the last step after flashing the radio should be "fastboot reboot-bootloader" not "fastboot reboot"? Maybe someone with more adb/fastboot experience could verify? Thanks.
bootloop after radio update!!!
my nexus 3g is from poland!!!
please, help!!!
Still no update guys, and no luck also
Right now I am thinking we will need to replace the main board, but I want to get that confirmed before buying a replacement.
I think that radio and bootloader must flashed first before upgrade to 4.3 . I do that with my N7 3G and now it works fine
my radiobands for device is for Poland Region
i hate myself
the only way is to flash radiomodule via APX, i have installed drivers, but have not .cfg and other parameters to flash Nvidia chip.
sambistt said:
my radiobands for device is for Poland Region
i hate myself
the only way is to flash radiomodule via APX, i have installed drivers, but have not .cfg and other parameters to flash Nvidia chip.
Click to expand...
Click to collapse
There isn't a place to know the parameters or whatever we need?
What can we change physically (motherboard, or any specific chip) to solve this problem?
If we return it to Asus or Google can it be repeaired? How much does it cost? Assuming the warranty is void because of the unlock icon..
---------- Post added at 01:25 PM ---------- Previous post was at 12:31 PM ----------
eternal70 said:
I think that radio and bootloader must flashed first before upgrade to 4.3 . I do that with my N7 3G and now it works fine
Click to expand...
Click to collapse
That was not the reason. I didnt upgrade to 4.3 before flashing the bootloader and the radio and I got the same result. The bootloader is not connected to the OS, but the OS is connected to the bootloader. I mean that it doesnt matter the OS in order the bootloader to run. But maybe it is possible to have the n7 soft bricked if the bootloader installed is not compatible with your OS.
Softbricked is when you are stuck in the OS logo (in case of the stock version is the colored X). This is very easy to fix, just runt in fastboot mode and flash the new OS and that's all. Everyone has experienced this situation eventually.
Our n7 are hard bricked. This mean that the bootloader or the radio (or both) are corrupted or bad flashed. In our case is the radio band (since we can see the google logo that is the bootloader). The weird thing is that while the bootloader is running (we can see the google logo and the unlock icon), we can't enter in the fastboot mode. Since we cant put the n7 in fastboot mode then we cannot flash anything (not os, not radio, not bootloader).
For now, the only way to flash bootloader and radio chip of the n7 is via APX. the problem is the APX configuration to flash the nvidia chips has not been released (as far as I understand, correct me if im wrong), so there is no way to know how to do it.
The only hope is changing this chips physically. Because everything is integrated, that means to change the motherboard, my guess (you can find tutorials in iFixit). What's the downside? The motherboard is basically the N7 so if you change it you change everything (the storage, the 3G, etc). You can check for motherboards in ebay easily just with search: Nexus 7 Motherboards. Range price varies from 20$ for 8GB to 140$ for 3G . Another question is if we can put a 8GB or 16 GB motherboards in our 3G N7, but I think so... it would not be a problem.
Everything I said a personal opinions and I can be wrong, so correct me if I'm wrong.
I have to say, I still have a very very very little hope that could be a fix for this, since we can see the google logo. But I'm thinking in ordering a 8G motherboard just in case
i`m thinking to give my n7 3g to my brother for parts and never buy tablet anymore, only ultrabooks.
My brother had the same problem and he managed to flash 4.2.1 with the nexus 7 toolkit.
The device got back to life again and then took the 4.3 OTA.
Sent from my Galaxy Nexus using xda app-developers app
There isn't a place to know the parameters or whatever we need?
Click to expand...
Click to collapse
no and never`ll be
easyflash only for transformer pad
i think to easy buy new nexus 7 2 gen or never buy tablet anymore
347 $ in trash
the new PS4 console is selling ~ 399$ - i think, it better to purchase new console that tablet
---------- Post added at 01:52 PM ---------- Previous post was at 01:44 PM ----------
DomieMic65 said:
My brother had the same problem and he managed to flash 4.2.1 with the nexus 7 toolkit.
The device got back to life again and then took the 4.3 OTA.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
really? your brother flashed radio module?
sambistt said:
no and never`ll be
easyflash only for transformer pad
i think to easy buy new nexus 7 2 gen or never buy tablet anymore
347 $ in trash
the new PS4 console is selling ~ 399$ - i think, it better to purchase new console that tablet
---------- Post added at 01:52 PM ---------- Previous post was at 01:44 PM ----------
really? your brother flashed radio module?
Click to expand...
Click to collapse
I don't know. Sorry.
I just mentioned this in case it may give you a clue.
I will ask and report.
Sent from my Galaxy Nexus using xda app-developers app
*** Returned my N7 (2012) as faulty and swapped with a 2013. Thread Ended. ***
I've been having trouble with my N7 (2012) for a while now.. Ever since the 4.3 update.. Slow response, hangs, and so on.
The latest 4.3 update would not install. Just a lying down droid with '!'.
My tablet was rooted using Wugfresh toolkit and was perfect before 4.3.
So i thought i'd go back to the start and use the toolkit to go back to root and flash stock+unroot.
Went through all instructions, it got to the part where it says ' You tablet will now reboot a few times. Please wait.'
Waited for 30 mins and nothing..
Now got a tablet with the google name and the unlock symbol. Options available are start, bootloader, recovery, off
All bring back to same screen.. Bootloader option displays -
Fastboot mode
PRODUCT NAME - tilapia
VARIANT = tilapia
HW VERSION - PR
BOOTLOADER VERSION - 4.13
BASEBAND VERSION - 1231_0.18.0_0409
SERIAL NUMBER - 015d88ffa8540a1c
SIGNING - not defined yet
LOCK STATE - UNLOCKED
During the flash boot to stock it wiped all directories etc so I now have an empty tablet..
Any ideas what I can do now? I would prefer to go back to stock 4.2 if possible... but if not, any help would be nice...
filking said:
I've been having trouble with my N7 (2012) for a while now.. Ever since the 4.3 update.. Slow response, hangs, and so on.
The latest 4.3 update would not install. Just a lying down droid with '!'.
My tablet was rooted using Wugfresh toolkit and was perfect before 4.3.
So i thought i'd go back to the start and use the toolkit to go back to root and flash stock+unroot.
Went through all instructions, it got to the part where it says ' You tablet will now reboot a few times. Please wait.'
Waited for 30 mins and nothing..
Now got a tablet with the google name and the unlock symbol. Options available are start, bootloader, recovery, off
All bring back to same screen.. Bootloader option displays -
Fastboot mode
PRODUCT NAME - tilapia
VARIANT = tilapia
HW VERSION - PR
BOOTLOADER VERSION - 4.13
BASEBAND VERSION - 1231_0.18.0_0409
SERIAL NUMBER - 015d88ffa8540a1c
SIGNING - not defined yet
LOCK STATE - UNLOCKED
During the flash boot to stock it wiped all directories etc so I now have an empty tablet..
Any ideas what I can do now? I would prefer to go back to stock 4.2 if possible... but if not, any help would be nice...
Click to expand...
Click to collapse
Hi, filking...
I have no experience with toolkits, so I can only advise you to download the Factory Image for your 'tilapia'/'nakasig' Nexus 7, and fastboot flash it.
Using fastboot isn't that difficult, and I'm at a loss to understand why toolkits have become so popular, when fastboot is so easy to use. Maybe people don't like command line interfaces...??
Anyway, there's a thread here which explains it all in detail.
Good luck.
Rgrds,
Ged.
Hi, thanks for the reply.
I think, in the world it is now, everyone is used to menus/mouse clicks to perform functions.
Anyway, I have read that thread already and my problem is when I get to the commands. All 'adb' commands don't work.
'adb devices' shows nothing.
I've tried in bootloader mode and recovery mode... All show a droid lying down. Fastboot mode shows the above message. Rest show, 'boot failed'
Help.....
filking said:
Hi, thanks for the reply.
I think, in the world it is now, everyone is used to menus/mouse clicks to perform functions.
Anyway, I have read that thread already and my problem is when I get to the commands. All 'adb' commands don't work.
'adb devices' shows nothing.
I've tried in bootloader mode and recovery mode... All show a droid lying down. Fastboot mode shows the above message. Rest show, 'boot failed'
Help.....
Click to expand...
Click to collapse
You don't need ADB to flash a stock image. ADB only works with a fully booted Android tablet. Indeed, if you have no bootable OS on your tablet, ADB is redundant and will not work.
You need to use fastboot...
What do you see when you type fastboot devices? (whilst the N7 is booted into the bootloader).
Rgrds,
Ged.
An update....
I went through wugs full driver setup part and deleted existing drivers. Installed the drivers again...
The device is detected on my PC.. But, seeing as it is stuck on the bootloader screen and I can't get into the system to turn on debugging, no adb commands work.
Device is listed as an 'unknown' android device when plugged in..
Seen a few other posts similar, but a lot say, 'it's ok, i've fixed it' without saying how.
anyone?
sorry, our posts must've been at same time..
Fastboot devices shows
015d88ffa8540a0c fastboot
*EDIT* Looks like i've misread the instructions in the post linked to above...
It got to the part where is said 'type in adb devices'... I read that, it didn't work, and I stopped.
BUT, I was already in bootloader mode, so didn't need that bit..
My error. (it's been a hot day!!! is that a good enough excuse.)
Continuing with the fastboot commands now... I'll update how it goes..
Thanks for replies.....
Update. All resolved.
I tried with the 4.3 img, but for some reason, it went through all the steps correctly. fastboot reboot resulted in the bootloader screen again.
Weird I thought, so I downloaded the 4.2.2 img and tried that and it worked perfectly..
Many thanks all who did, and it's a reminder to all. Re-read instructions..
:highfive::good:
Hi there
@bftb0 : yet another victim of the corrupt bootloader .img ! (see thread #2573015)
bftb0 said:
The versions distributed with JWR66Y and KOT49H* Google factory images are INVALID.
Click to expand...
Click to collapse
Device : Nexus 7 2012 wifi (grouper), stock 4.4.4 KTU84P, never rooted before
Symptoms : black screen, not booting at all even to bootloader. :crying:
Only faint light of hope is that my PC is still reacting to plugging the Nexus in with USB.
Windows beeps and shows an "unknown usb device" error then fails finding a driver.
Windows Device manager shows "APX" with yellow sign below "Other devices".
Question : bricked or any hope left ? Pleeease what can I do ?
How I got there :
NRT hung when flashing bootloader while reinstalling stock 4.4.0 (nakasi-krt16s-factory-da7dee49).
The story, going from bad to worse :
It started with a sudden reboot for not appearent reason (incidentally while an Avast routine scan was running).
Then endless reboot, with the 4 color balls shaking indefinitely (power plugged in or not).
Looked at forums... Reboot into bootloader. Recovery mode, wiped cache. Got plenty of error msg "E:failed to mount /cache"
Bootloop! Sometimes showing just the white Google logo, sometimes showing the rolling colors for a few seconds.
Recovery mode, erase user data (no backup, hate this thing). Again plenty of error msg "E:failed to mount /cache"
Could the missing /cache be related to Avast since the first reboot occurred while it was running? Maybe the theft protection is overly proctective?
Installed Nexus Root Toolkit 1.8.4 (extremely well done utility btw, ***huge congrats*** :good on Win 7 64bits. Installed drivers #1.
Tried flashing a clean 4.4.4 (nakasi-ktu84p-factory-76acdbe9).
FAILED (remote: Bootloader is locked.)
Successfully unlocked bootloader with NRT. Restart with an open lock below the white Google logo. So far so good.
Try flashing 4.4.4 again, same image.
writing 'bootloader'... FAILED (remote: (InvalidState))
What the heck ?!
Found the thread #2573015 I was quoting above on corrupt bootloader .img files from Google.
As it turns out, the bootloader MD5 is also WRONG in KTU84P.
Managed somehow to restart into bootloader again in spite of the bad bootloader...
Maybe the old one was not completely replaced yet?
Quick quick, let's try flashing another bootloader that works !
This time use the latest available with a non-corrupt bootloader .img : 4.4.0 (nakasi-krt16s-factory-da7dee49)
erasing 'boot'... blahblah
sending 'bootloader' (2100 KB)... OKAY [ 0.281s]
writing 'bootloader'... *** STUCK ***
Wait and wait until lost hope
Tried rebooting but nothing happens, just black screen, I end up with the symptoms I described upfront.
When plugged into the pc, keeping power button down makes windows beep, and the "APX" unknown device comes and goes in win device manager. Adding the vol+ or vol- buttons (or both) produces identical results.
Uninstalled APX device from PC. Power button down. Windows beeps "unknown usb device". "APX" shows up again in device manager... And so on.
Screen still pitch black.
Any other USB driver I can try to regain a working connection?
Worth looking into other remedies, like nkFlash?
GedBlake said:
If you corrupt, or erase the bootloader... the Nexus 7 is dead, from which there is known recovery. Although it's been speculated that an nvFlash tool could flash a new bootloader.
Click to expand...
Click to collapse
Thanks for reading me so far, I know it's long, but if you've read to this point maybe you can help?
What a similar story
this is such a coincidence as I have also had the dreaded bad to worse stage as my story started off here http://forum.xda-developers.com/showthread.php?t=2783631 and then got much worse and it continues here http://forum.xda-developers.com/showthread.php?t=2798181 .
I have been searching on the internet for the last month and so far there does not seem to be any general solution (which does not require hardware device surgery) to this particular type of problem as it is not something Google appear to have expected. I found that a lot of people seem to say its hypothetically possible to repair this thing via software means as that is how it was rendered inoperable in the first place and they also say it is not practically possible to hard brick any device through software means although with the nexus 7 there seems to be some kind of issue with crypto-signing which makes it a nightmare to access the hardware through nvflash unless there was some blob file made before hand
I am currently discussing the situation in this thread and you could join it to keep up to date
http://forum.xda-developers.com/showthread.php?t=2798181&page=2
Hey guys!
I've been scouring these forums for two days now making sure my specific issue hasn't been discussed and, from what I've seen, I've won some sort of "annoying issue" lottery.
I was handed a Nexus 7 (ME370T) a few days ago and told "if you can fix it, it's yours."
I can get to the bootloader no problem but not the actual OS. Here's the data from the bootloader:
Fastboot Mode
Product Name - grouper
Variant - grouper
HW Version - ER3
Bootloader Version - 4.23
Baseband Version - N/A
Serial Number - xxxxxxxxx
Signing - not defined yet
Lock State - Locked
Long story short, I've installed the Android SDK and when I plug the tablet into my PC, I can see it as "Google Nexus 7 Bootloader Interface"
When I use fastboot devices, it sees the tablet just fine.
When I use adb devices, it doesn't see the tablet.
I've tried fastboot oem unlock and I get a FAILED (remote: (Unknown error code)) error.
I can run the unlock feature through the Nexus Root Toolkit but it reboots to a black screen (my device manager sees it as "Asus Transformer Prime APX Interface")
When I finally get the thing rebooted to the bootloader (manually powering off and then back on), it's still locked.
I have no idea if USB Debugging was turned on or not. I keep reading that, to flash a partition to a new file, the bootloader doesn't need to be unlocked but every single time I try to fun fastboot, i get Failed, Bootloader is locked.
Am I nuts? I know I'm new to this but I'm fairly certain I've done everything right! You guys seem super knowledgeable and I hope you can help me out!
Thanks!
Hey guys,
I have a nexus 10 that I was using wugs nexus ten kit to flash a older version so back to 5.0 instead of 5.1.1. Everything was going good the black screen on wugs came up and I was watching it when the screen just said finished but did not boot the tablet back up or say hit any key. now the tablet just goes into the boot loader where we flash rooms. it is the picture of android with service port open. I have tried other roms and the tablet will only go into this mode. I have no idea what happened. Any ideas?
Thanks
Joe
I have fast boot status of ok but no matter what rom i flash on wugs it finishes in .03 seconds.
fastboot devices
R32F200CG8X fastboot
Connectivity Status: Fastboot Device Connected
+ Confirmed: Bootloader Unlocked.
fastboot getvar product
product: manta
finished. total time: -0.000s
Launching flashstock.bat
jfed said:
Hey guys,
I have a nexus 10 that I was using wugs nexus ten kit to flash a older version so back to 5.0 instead of 5.1.1. Everything was going good the black screen on wugs came up and I was watching it when the screen just said finished but did not boot the tablet back up or say hit any key. now the tablet just goes into the boot loader where we flash rooms. it is the picture of android with service port open. I have tried other roms and the tablet will only go into this mode. I have no idea what happened. Any ideas?
Thanks
Joe
Click to expand...
Click to collapse
Hi there,
it happened to me too two days ago, wanted to use the toolkit to go back to stock, as I already did a few months back with no trouble at all.
But this time my N10 is stuck on the bootloader screen, exactly the same as you.
Can't do anything, can't flash anything.
This is what happens when using Nexus Root Toolkit v2.0.6 to restore stock.
My cable works fine, I've tried another one (both works when plugging my lgg2 to my computer) and I get the same result:
Nexus Root Toolkit v2.0.6
Masterlists:
- LatestToolkitFiles.ini 3085
- AndroidDeviceListFull.ini 3085
- AndroidDeviceListFlash.ini 3085
CUSTOM ROM (Wi-Fi Tablet) - KK
Live log initiated [2015-11-11]:
Information: Getting Device Properties...
Nexus Root Toolkit v2.0.6
Masterlists:
- LatestToolkitFiles.ini 3085
- AndroidDeviceListFull.ini 3085
- AndroidDeviceListFlash.ini 3085
MANTARAY-MANTA: Android *.*.* - Any Build
Live log initiated [2015-11-11]:
Analyzing factory image; please be patient...
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
R32D1035MVF fastboot
Connectivity Status: Fastboot Device Connected
+ Confirmed: Bootloader Unlocked.
fastboot getvar product
product: manta
finished. total time: 0.001s
Launching flashstock.bat
Click to expand...
Click to collapse
Try not to use the Root Kit.
Flash the stock rom maually via fastboot.
XxM4tzexX said:
Try not to use the Root Kit.
Flash the stock rom maually via fastboot.
Click to expand...
Click to collapse
Annnnnd you're right!
Couldn't do anything with the Root Kit.
So I learnt something today (well, yesterday...), I learnt how to use fastboot to flash stuff manually...
First step was making sure my drivers were updated and installed ADB and Fastboot on my computer.
Then when I managed to wake up my Nexus 10 (which wouldn't turn on easily) I flashed the bootloader I extracted from an official Android factory image.
At that time I guess my battery died, which slowed down the next steps for unbricking my tablet.
Then I flashed stock Android, and restarted the tablet, AND IT WORKED !!!
So I flashed a recovery, TWRP, and then rooted my Nexus 10 and after checking everything worked fine, I flashed a custom ROM.
It took me so much time to do something that simple, but, well, that's part of the learning process.
Fortunately, I just had made a backup of my apps with Titanium Backup before using the Nexus Root Kit, and secured my files on my computer, so I didn't lose anything (except my precious precioussss time...)
This video helped a lot:
on YouTube, search for "How To Unroot/Unbrick Nexus 10 Android Tablet!" uploaded by "nexus10root"
(I didn't flash the "radio file" he's talking about, and couldn't manage to use fastboot to reboot the bootloader, but I guess this is where my battery dying made things more difficult than it should have)
Same thing this morning, stops at Launching flashboot.bat I'm stuck. Is the new version of Wugfresh the problem?
Well, it's the first time ever that this Tool Kit let me down, and it just happened after an update...
Thing is, I have no idea what went wrong, so I can't possibly point fingers at anyone.
I learned to use fastboot and ADB, and my tablet is fine now, so even if it's some bug with the update, well, it didn't break anything beyond repair, which is a relief.
Forced me to learn fastboot, updated my tablet, added twrp and rooted. Took me a while but I did it, sure miss the ease of using the toolkit.