yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Q&A, Help & Troubleshooting] Sam.rosar:
nothing...it just simply reboot and stay like i said..with log on on...and if i unplug it and leave it like this...it just stay on till battery goes down.
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
It sounds like the kernel cannot boot the system, so only splash screen appears. What did you exactly do with your tablet? Is your bootloader unlocked?

tetakpatalked from N7100
[Nexus 7 Q&A, Help & Troubleshooting] Sam.rosar:
yes it WAS unlocked...but now nothing happen when i press start button and volume down..only splash screen show up..is there anyway to replace kernel if it doesen't enter bootloader mode and it doesen't list on listed devices on adb?

p.s: like i said i runned nexus toolkit on it i wanted to add 4.4.4 from 5.1...
[Nexus 7 Q&A, Help & Troubleshooting] 45rpm:
[MENTION=5051515]tetakpatak[/MENTION] Yes, I also made several attempts to flash manually and it continues to fail into boot loop at the "starting apps" dialog. Soon after this message appears reboot occurs. I am unable to determine which app or start process is running at the time. Growing frustrated on identifying the issue here.
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
If I remember well, your fastboot flashing process went fine, right mate? In such case, try a trick with factory reset in recovery mode. I honestly have no remeberance on how Nexus 7's stock recovery looks like, so if there is no such option just flash any recent custom recovery in bootloader mode. Then boot into the recovery and format /data, /cache and dalvik/ART cache. Then reboot into the system.

tetakpatalked from Nexus 7 flo
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
Nope, kernel can be flashed only through bootloader mode via fastboot. At the end, your tab should be fine if bootloader hasn't got damaged amd no hardware issue occured, like defective flash memory or similar.

I must honestly say that I really don't trust toolkits and prefer by all means to enter one by one command manually. But it is just my personal opinion.

tetakpatalked from Nexus 7 flo
[Nexus 7 Q&A, Help & Troubleshooting] Sam.rosar:
ok..but any advices ..well...if you can...what to do next now?:(
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
Well, I think the best is if we try upon a simple checklist... maybe we figure out a simple error in your workflow.

It was more than 2 years ago when I flashed your device (I own a successor model: Nexus 7 flo, 2013), but as all Nexus devices are really similar in this matter, I will describe you what happens here and I hope it can help you further:

Note: using button combos means to press two buttons at the same time and keep them both pressed. The USB cable should be disconnected at that moment

Outgoing point: the tablet is turned off

Combo power button & volume down button need to be constantly kept pressed down about 5 sec here to boot my flo directly into the bootloader mode (no splash screen appears)

Combo power button & volume up button need to be pressed until splash screen appears second time, then the power button should be released while volume button must remain pressed down, the tablet boots into the recovery mode after few seconds

Did you try both options exactly that way? Any of the modes would be really good outgoing point for further unbricking....

tetakpatalked from Nexus 7 flo
[Nexus 7 Q&A, Help & Troubleshooting] Sam.rosar:
i did both....instead of showing bootloader ..splash show up
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
Can you please post which method exactly did you follow and what exactly happened then?

Possibly you have flashed an uncompatible bootloader (made for another device) which would be quite bad, but it is hard to say without knowing what you exactly did.

tetakpatalked from 1+One
[Nexus 7 Q&A, Help & Troubleshooting] Sam.rosar:
i used step by step this https://www.androidpit.com/how-to-downgrade-a-nexus but for nexus 7. didn't worket..and after twrp-2.8.7.0-tilapia ( chosed tilapia cause in bootloader it was same version original ) after i did it . it auto disconect from pc...and...brick.
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
Dear mate, I suppose that was the problem! As you have flashed recovery image of the Nexus 7 3G on your Nexus 7 WiFi only, it could definitely be a reason for the bricking.

While I am not 100% sure about Nexus, I know that the recoveries versions for some other tablets (like Samsung) differ quite a bit between 3G and WiFi models, mainly because the SIM-card versions consist also a "radio" option.

I suppose it will be the best if you use Google search and some patience and figure out how it is possible to inforce the tablet to boot into the bootloader mode on some method. Maybe some other people had the same problem and were able to solve it.

Some devices by Samsung could habe been forced to boot into the "download mode" (which is similar like booloader mode) by using a USB jig. But I have no idea about Nexus, as I never bricked it. Actually I've flashed over 200 different models of tablets and smartphones and never hard-bricked any, but I also never flashed any wrong files: for example like system files done for different device (which you did here).

Don't forget, even in the worst case, Asus service will can repair your tablet for some $$€€

Good luck mate! :good::fingers-crossed:
[Nexus 7 Q&A, Help & Troubleshooting] kader85:
hauwei ascend Y530-U00 plzzzzzzzzzzzzzzzzzzzzzzzzzz
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
You are here in totally wrong thread, for Nexus 7

tetakpatalked from N7100
[Nexus 7 Q&A, Help & Troubleshooting] MrBratka:
Have you tried to recover your device using Nexus Root Toolkit. It is a simple tool with solutions to most problems that you can encounter on nexus device. Also you can use this to flash any version image that is avaialable on your tilapia
[Nexus 7 Q&A, Help & Troubleshooting] martman:
Easy

Excellent how to, Decided to bring some life into my old nexus 7 after ones woman treated us to a new tablet at christmas so shes having this one

Made the mistake of upgrading the nexus to lolipop and it killed it performance wise very sluggish horrendous boot time and now back on 4.4.4 and its back to how it used to be

cheers comminus
[Nexus 7 Q&A, Help & Troubleshooting] Sam.rosar:
the tablet isn't recognized by the pc anymore...seems i distroyed its boot image by used nexus root toolkit in 1st place . now when i connect it to pc it only stay on ..but the pc don't even show it as a device or atleast as a unknown device or smth....it's like it isn't even plugged to it..so ....will keep it there as a mirrow :))
[Nexus 7 Q&A, Help & Troubleshooting] nexforce:
for some reason I don't have the Google usb-driver option in the details folder in the Android SDK Manager.

Where do I find the usb drivers?
[Nexus 7 Q&A, Help & Troubleshooting] recicchini:
Pixel C/Android N

I am trying to do this on a Pixel C to revert from Android N to Marshmallow. This guide is essentially the same as the one linked to on Google's page. However when I get to fastboot tries update I get the following:

fastboot -w update image.zip

target reported max download size of 268435456 bytes

archive does not contain 'boot.sig'

archive does not contain 'recovery.sig'

failed to allocate 1899001172 bytes

error: update package missing system.img

I know in the guide it says not to worry about these messages but when my devices boots back up it is still in Android N. Yes, I have already tried opting out of the beta program, it has been almost two weeks now and no OTA update. Any help would be greatly appreciated!
[Nexus 7 Q&A, Help & Troubleshooting] bvramana:
"Superb Info"

Thanks a lot for this valuable info/guide,:good: would like to thank again for sharing this "very useful and detailed information":svetius:
[Nexus 7 Q&A, Help & Troubleshooting] dave297:
Grateful Thanks!!

Following your guidance I have just restored my Nexus7 2012 to 'as new' condition using KitKat 4.3! Goodbye all the lag and crashes for Lollipop 5.1.1!!!! Thanks for taking the time and trouble to make the procedure available on this forum!:D
[Nexus 7 Q&A, Help & Troubleshooting] C-Fu:
I'm trying to find ways to use the fastboot flashall command.

for example:

fastboot.exe is in c:\minimal adb and fastboot folder

the extracted fastboot image is in d:\mi4i\romname\images\ folder (boot.img, cache.img, recovery.img, etc)

so how do I use it?
[Nexus 7 Q&A, Help & Troubleshooting] tankcsabee:
Downgrade Factory Image

Hello Guys, I need a little help with my Nexus 7 (2012) WiFi Only. I want to downgrade from 5.1.1. Lollipop to 4.2 or 4.3 Jelly Bean. I went through the guide and stuck really close to the end with this error message: target didn't report max-download-size - sending bootloader FAILED

Now I tried with several PC-s, different versions between 4.1 and 4.4 Android with the same result:

[IMG="Android Toolkit"]https://nct7kg-dm2305.files.1drv.com/y3mMIEIbOlDtuDkTDR-da1ChNYeaiUYd126DMSVsmdtRDDxHVfhV6I6hGaMjPzhzAvmKrBQyfgyzM46sqEfSFcp00I_3u7Mg6H7bCV2giV8hQM30PLawZBAfHY6_ly2fF-ET9MTPZrHu0o0RiJ6XW0ZcnoxMldYznAxPbaQO4A5Jn4?width=692&height=389&cropmode=none[/IMG]

I hope anybody have any idea what I'm doing wrong.
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
I dislike toolkits. Your toolkit has no connection to your tablet, I would say.
[Nexus 7 Q&A, Help & Troubleshooting] dejan16v:
I guess you have unlocked bootloader.

First I recommend do create complete backup (by TWRP). Then use fastboot command and flash complete image file of desired OS previously downloaded from Google developers page for your Nexus 7. Then you should be fine.
[Nexus 7 Q&A, Help & Troubleshooting] emanuelnj:
I do not get unlocked the bootloader

I do not get unlocked the bootloader, give me the option but when i accept i do not reset. Do you have a solution? Could i orientate thank you?
[Nexus 7 Q&A, Help & Troubleshooting] tetakpatak:
There is no way to unlock the bootloader without performing a factory reset.
[Nexus 7 Q&A, Help & Troubleshooting] lucasbottaro:
Sorry, i posted in the wrong place.
[Nexus 7 Q&A, Help & Troubleshooting] WelshPatriot:
Backing up

The easiest way is surely to sync to the cloud, Google account is easy but many are available at playstore, AVG include a good one.
[Nexus 7 Q&A, Help & Troubleshooting] papagalus:
Nexus 7 (2012) HiFi tablet issue

At startup the tablet locks and shows the colored X sign.

I press the Sound Down + Power keys and train in Bootloade and then in Recovery Mode.

Unfortunately I do not have a custom Recovery installed, so I press the Sound Up + Power keys to enter Android System Recovery.

I choose the Wipe data / Factory reset option and I choose the Delete all user data option. After a while I get the message that the data has been deleted and returned to the factory settings.

I restart the tablet and the result is the same: it freezes in the phase that appears in the first image.

How can I fix this problem since I can't access the tablet settings to check USB Debugghing and I don't have a Recovery custom installed on it.

I mention that:

1. The battery is good, it charges and it lasts quite a long time (about 10 hours).

2. The Windows 10 laptop does not recognize the tablet and does not install the appropriate drivers.

3. I installed Universal ADB Driver on the laptop and it was still not seen by the adb devices command.

4. I still have a tablet identical to this one that works flawlessly. Can I use a backup of this tablet to repair the damaged one?
[Nexus 7 Q&A, Help & Troubleshooting] pekayatt:
I DO have a PC, but unfortunately any system that I try to connect my N7 it doesn't even recognize it... I am not sure what have happened, but when it is OFF and I connect it to the AC Charger it shows that is charging. Sometimes when it is on and I connect to an USB or to the AC it shows charging, but sometimes not.

I could not make the ADB or fastboot to see it using "adb devices" or "fastboot devices", even Windows do not recognize it as a device in device manager... Really running out of options here, I am from Brazil and my dad has bought it in USA, so no Google support either... already have opened it and removed the battery, but the problem persist :/...
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
Are you using the USB cable that came with the device? Have you tried using different ports on your computer? If you have device manager open and plug in the N7 do you notice any changes, unknown device or otherwise?
[Nexus 7 Q&A, Help & Troubleshooting] pekayatt:
Yes, same cable, in fact the Asus cable that came with it.

Have tried in at least 3 computers, all ports, no changes :/..

No changes at Device Manager, is almost as the device have been only connected to a power supply, but even it says Charging (USB)...

Anyother ideas? Unfortunately I happened before I could get my root, so even wi-fi ADB is not possible..
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
Try installing the USB drivers from this thread http://xdaforums.com/showthread.php?t=1996051.
[Nexus 7 Q&A, Help & Troubleshooting] kykara4a502:
Very helpful guide, thank you
[Nexus 7 Q&A, Help & Troubleshooting] JJkoU:
Excellent work comminus

Thanks Though!!!!:fingers-crossed:
[Nexus 7 Q&A, Help & Troubleshooting] pekayatt:
Have tried, but my device manager do not even show the device there.

Today for the first time I could see it just after booting in fastboot mode for the first time, tried to install this driver and even tried to run that N7Toolkit, but none of then could get it to be seen in adb devices or fastboot devices

Any other ideas?
[Nexus 7 Q&A, Help & Troubleshooting] Balinov:
sorry if you tried this one, but have you enabled USB Debugging in the developer mode?
[Nexus 7 Q&A, Help & Troubleshooting] pekayatt:
Of course :D, and dont worry I know all plp just want to help!

I have enabled USB Debuging, and also, I am trying to connect in FASTBOOT MODE, botting my n7 holding the vol up key, even like this I could not find the device...

Maybe I will try later in Linux...
[Nexus 7 Q&A, Help & Troubleshooting] Balinov:
strange, I've never used ADB before, but following step-by-step this guide it was working like a charm under .win7 x64
[Nexus 7 Q&A, Help & Troubleshooting] pekayatt:
Of course, but my case is a change, I had a problem connecting my N7 at a Car charger, and AFTER that it started to have a very strange behavior.. I posted some pages back....

Bad lucky for me :(
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
IMHO Linux is definitely the way to go. If you're using Ubuntu you may need to define some udev rules. In that case try this, courtesy of codeworkx:

$ sudo nano /etc/udev/rules.d/51-android.rules

SUBSYSTEM==”usb”, ATTR{idVendor}==”0502″, MODE=”0666″, GROUP=”plugdev”
SUBSYSTEM==”usb”, ATTR{idVendor}==”0B05″, MODE=”0666″, GROUP=”plugdev”
SUBSYSTEM==”usb”, ATTR{idVendor}==”413C”, MODE=”0666″, GROUP=”plugdev”
SUBSYSTEM==”usb”, ATTR{idVendor}==”0489″, MODE=”0666″, GROUP=”plugdev”
SUBSYSTEM==”usb”, ATTR{idVendor}==”091E”, MODE=”0666″, GROUP=”plugdev”
SUBSYSTEM==”usb”, ATTR{idVendor}==”18D1″, MODE=”0666″, GROUP=”plugdev”
SUBSYSTEM==”usb”, ATTR{idVendor}==”109B”, MODE=”0666″, GROUP=”plugdev”
SUBSYSTEM==”usb”, ATTR{idVendor}==”0BB4″, MODE=”0666″, GROUP=”plugdev”
SUBSYSTEM==”usb”, ATTR{idVendor}==”12D1″, MODE=”0666″, GROUP=”plugdev”
SUBSYSTEM==”usb”, ATTR{idVendor}==”24E3″, MODE=”0666″, GROUP=”plugdev”
SUBSYSTEM==”usb”, ATTR{idVendor}==”2116″, MODE=”0666″, GROUP=”plugdev”
SUBSYSTEM==”usb”, ATTR{idVendor}==”0482″, MODE=”0666″, GROUP=”plugdev”
SUBSYSTEM==”usb”, ATTR{idVendor}==”17EF”, MODE=”0666″, GROUP=”plugdev”
SUBSYSTEM==”usb”, ATTR{idVendor}==”1004″, MODE=”0666″, GROUP=”plugdev”
SUBSYSTEM==”usb”, ATTR{idVendor}==”22B8″, MODE=”0666″, GROUP=”plugdev”
SUBSYSTEM==”usb”, ATTR{idVendor}==”0409″, MODE=”0666″, GROUP=”plugdev”
SUBSYSTEM==”usb”, ATTR{idVendor}==”2080″, MODE=”0666″, GROUP=”plugdev”
SUBSYSTEM==”usb”, ATTR{idVendor}==”0955″, MODE=”0666″, GROUP=”plugdev”
SUBSYSTEM==”usb”, ATTR{idVendor}==”2257″, MODE=”0666″, GROUP=”plugdev”
SUBSYSTEM==”usb”, ATTR{idVendor}==”10A9″, MODE=”0666″, GROUP=”plugdev”
SUBSYSTEM==”usb”, ATTR{idVendor}==”1D4D”, MODE=”0666″, GROUP=”plugdev”
SUBSYSTEM==”usb”, ATTR{idVendor}==”0471″, MODE=”0666″, GROUP=”plugdev”
SUBSYSTEM==”usb”, ATTR{idVendor}==”04DA”, MODE=”0666″, GROUP=”plugdev”
SUBSYSTEM==”usb”, ATTR{idVendor}==”05C6″, MODE=”0666″, GROUP=”plugdev”
SUBSYSTEM==”usb”, ATTR{idVendor}==”1F53″, MODE=”0666″, GROUP=”plugdev”
SUBSYSTEM==”usb”, ATTR{idVendor}==”04E8″, MODE=”0666″, GROUP=”plugdev”
SUBSYSTEM==”usb”, ATTR{idVendor}==”04DD”, MODE=”0666″, GROUP=”plugdev”
SUBSYSTEM==”usb”, ATTR{idVendor}==”0FCE”, MODE=”0666″, GROUP=”plugdev”
SUBSYSTEM==”usb”, ATTR{idVendor}==”2340″, MODE=”0666″, GROUP=”plugdev”
SUBSYSTEM==”usb”, ATTR{idVendor}==”0930″, MODE=”0666″, GROUP=”plugdev”
SUBSYSTEM==”usb”, ATTR{idVendor}==”19D2″, MODE=”0666″, GROUP=”plugdev”

#Save it! CTRL+O. CTRL+X
$ sudo chmod +x /etc/udev/rules/51-android.rules
[Nexus 7 Q&A, Help & Troubleshooting] cognus:
apologies in advance - I'm having terminology problems.

I'm just trying to get the SDK installed properly, and get the adb drivers etc installed so I can do the rest.

In the list of instructions I'm told to "Run the SDK Manager" - could someone please tell me the exact syntax of the [presumed] *.exe I am looking for, and it it is not an exe, a bat or whatever. I don't want to just be executing blindly and don't see anything in the tools with that name.

Also, is "Fastboot Mode" the condition of the Nexus 7 with the 'droid image laid out for 'surgery' and the "Start" flag at the top ? In that mode, windows 7 cannot load the normal driver and I'm ASSUMING that

is proper/appropriate

at this stage... I just wasn't sure if this is the right condition that is so frequently referred to.... I'm supposed to be in FASTBOOT mode, then connect it to the USB cable.

thanks
[Nexus 7 Q&A, Help & Troubleshooting] Balinov:
I can only answer the 1st question, cognus, but you're looking at an executable file, stored in the root directory of your Android SDK folder (where you've installed it. It should look alike something like in the screenshot I've attached.

hope this helps

cheers
[Nexus 7 Q&A, Help & Troubleshooting] cognus:
thank you. this is the simplest problem: your image is apparently of one screen of the "SDK and AVD Manager" which I see referred to all over the place but my brain needs to know the exact name of the file that I'm needing to execute - the file that runs the "SDK and AVD Manager"

Its quite tantalizing to see that image! that's what I'm wanting to see magically appear on my screen so I can unpack/install the usb adb drivers!!

they are in hiding somewhere....

Note that I just downloaded the Android SDK fresh this morning [this is Wednesday Dec.12], and within the folders is "adb_has_moved.txt" file, that file reads as follows: "The adb tool has moved to platform-tools/ If you don't see this directory in your SDK,

launch the SDK and AVD Manager (execute the android tool) and install "Android SDK Platform-tools".

Please also update your PATH environment variable to include the platform-tools/ directory, so you can

execute adb from any location."

again, I don't see anything executable that is called "SDK and AVD Manager.something" and I note the writer says "(execute the android tool)" which I would really like to do if I could just identify the executable to execute :silly:

also if someone could pls tell me how to "update the PATH environment variable".

I'll also go web hounding again to see if i can just find the raw adb driver... I know how to install drivers really well if I can just find the files somewhere...
[Nexus 7 Q&A, Help & Troubleshooting] Balinov:
my best guess would be to use total commander, navigiate to the SDK installation folder and search for files with *.exe file extension. Sure you'll find it straight.
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
At the time of writing the OP, the Android SDK download page provided an installer by default rather than the entire ADT bundle. I've updated the OP with a new link to the SDK installer - http://dl.google.com/android/installer_r21-windows.exe. With that installed, you can run the SDK Manager from the start menu and you'll be able to follow the rest of the instructions in the guide.
[Nexus 7 Q&A, Help & Troubleshooting] jmac335:
Guide Works Great for Us Stuck with JRO03S Builds

Hello All

I recently purchased a Nexus 7 32GB and was receiving upgrade errors. My build was JRO03S. Obviously I was stock and unrooted. It would identify an upgrade was available but failed to install. I searched the web for answers and turned to this guide for resolution.

I Followed all the steps, (I grabbed the latest 4.2 from google), with the following caveat under step 4 of flashing the ROM

> fastboot erase boot

> fastboot erase cache

> fastboot erase recovery

> fastboot erase system

> fastboot erase userdata

> fastboot flash bootloader bootloader-grouper-4.13.img

> fastboot reboot-bootloader

> fastboot -w update image-nakasi-jop40d.zip

The first time I tried it I did not add the command line in to reboot the bootloader and it failed, stating I was still on 3.39.

What bugged me the most is that the build JRO03S is not listed under the Nexus 7 at all on googles site for the factory images

Good Luck and many thanks to comminus for the guide!

I hope this helps others in the same situation and if anyone knows why I had to do this in the first place that would be a bonus.
[Nexus 7 Q&A, Help & Troubleshooting] Wrixituz:
Hey and really nice tutorial thx alot! used it to downgrade to 4.1.2 but upgraded after a while to 4.2.1 and now i want to downgrade again (yes cant really decide haha) but this time it failes to downgrade bootloader..

So, erasing bootloader OKEY. its sending bootloader, writing and then Okey, next step.. installing system.. now when its checking for version-bootloader:

"Checking version-bootloader....

FAILED

Device version-bootloader is '4.13'

Update requires '3.41' . "

but im installing 4.2.1 without any problems.. any suggestions?

/Wrix
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
After flashing the bootloader you must reboot the device in order to load the bootloader you just flashed.

Use this command:

fastboot reboot-bootloader

Then continue the process as usual.
[Nexus 7 Q&A, Help & Troubleshooting] Wrixituz:
Thx very much! that worked great :good:
[Nexus 7 Q&A, Help & Troubleshooting] benhidalgo:
thanks

thanks for the help, great guide on my contender journey :D
[Nexus 7 Q&A, Help & Troubleshooting] darkgandhi05:
Intro: I'm using Windows 8. My N7 cannot boot up because of a failed ROM install. I was installing MoDaCo 4.2 and I was on SmoothROM 4.1.2. My bootloader version is 3.34. I unlocked the bootloader & rooted when I had Windows 7 a few months ago and I used a toolkit to do it. Also, I'm unable to boot into recovery from the bootloader screen because after I select "Recovery Mode", I get stuck on the Google image and have to turn off/get back to bootloader. So since I can't get into recovery mode, it looks like I have to use fastboot, which I've never done before.

Question: I installed the drivers as instructed...but I'm not sure it worked properly. When I do the "adb devices" command I get no devices listed. But when I do the "fastboot devices" command I can see my device! I don't want to break my device...so I wanted to make sure if I can go ahead and enter these commands:

> fastboot erase boot

> fastboot erase cache

> fastboot erase recovery

> fastboot erase system

> fastboot erase userdata

> fastboot flash bootloader bootloader-grouper-4.13.img

> fastboot -w update image-nakasi-jop40d.zip

Question #2: Do I need to upgrade my bootloader to a newer version before flashing a 4.2 ROM? Or does that second to last command install the newest bootloader already?

Question #3: Can I go ahead and install the 4.2 stock image or do I need to install 4.1.2 first?

Thanks a whole lot! I thought my device was a goner when I couldn't get into recovery.
[Nexus 7 Q&A, Help & Troubleshooting] Mach3.2:
Adb will only work in recovery and android. Fastboot will only work in fastboot mode..

Just run the flash-all.bat..

Beamed from my Maguro.