Database Users

Can we flash on Mac or with an app.Is att's 2.2update avaliable more questions

I have steves 1.53 rom stored on my sd idk if theres a flashin app that can flash it from the sd on to the att Dell streak (non branded streak). Or away to flash on a mac and im having trouble with my windows xp flash!? Idk why, if someone can walk me through it. Im used to flashing HTC windows phones and even built my own version windows roms and also Iphone apps and I.OS ice built my own.... Come to think of it is there away to actually put a full fledged os on the streak or dual boot even to alow to get as much use out of this unit? Or even overclock it and how to over clock if you could walk me through it!?
Sent from my Dell Streak using XDA App

There are unix parameters for fastboot, that means that there must be a unix SDK that can be used in Mac OSX.
I have not seen any dual boot solutions.
And most of your questions are answered in this forum.
Try: Guide to Upgrading and Downgrading the Streak
Or the combination of:
NEW StreakMod Recovery
and
StreakDroid 1.6.0 ( aka Install-o-Rama ) Release Post

Yes you can do everything with a mac (i actually find it easier on a mac as you don't have to deal with drivers like you do on windows).
Go to developer.android.com and download the SDK for mac. Get the Fastboot file for mac (attached cuz i'm feeling nice) and drop that in your SDK/Tools folder.
Add the full path of the sdk/tools folder to your bash profile (search on google) so you can use the fastboot-mac, adb, etc commands from the tools folder in Terminal without being in that directory.
Once you got that, you have to know a couple terminal commands, basicly just how to navigate to the folder where you downloaded the streakmod recovery (google for "mac terminal commands cheat sheet" and you might find something useful.
Once you know how to navigate via terminal its as simple as flashing the StreakMod recovery. Put your device in bootloader mode (search or see the wiki) then in terminal it should be something along the lines of:
Code:
fastboot-mac -i 0x413c flash recovery recovery.img
Then to get into the recovery youd reboot your device after the flash
Code:
fastboot-mac -i 0x413c reboot
hold the volume up and down buttons, select option 2 (flash update.pkg or whatever) and that'll take you into the StreakMod recovery [if you get the dell logo with an exclamation mark in a triangle and nothing is showing, press the power button]
From streakmod recovery select Flash update.zip from sd card then select "select .zip from sd card" and then use volume up/down to scroll up/down and camera button to select and voila you are flashing a rom with your mac :S
Also before you flash the rom you might want to do a full nandroid backup incase your update messes up you can do a full restore and be exactly at the point before you attempted to flash your device.
Nandroid is under the Advanced option in the streakmod recovery.
Good luck
OH p.s.
EVERYTHING you need to know is on the forums/wiki/etc.
Please do a search, i know you have to read through a bunch of crap but its worth it. you'll learn a ton

i enjoy how he called it an ATT non-branded dell streak.

I followed ur guide an all but im trying to install clockwork on my streak (2.2 stock 318) and it gets stuck at <waiting for device>
anyone know how to get past this?

iphonepimp said:
I followed ur guide an all but im trying to install clockwork on my streak (2.2 stock 318) and it gets stuck at <waiting for device>
anyone know how to get past this?
Click to expand...
Click to collapse
I always had to install the ADB drivers manually, before fastboot mode worked.
Here you can download a manual on how to install the drivers.

peppi.nl said:
I always had to install the ADB drivers manually, before fastboot mode worked.
Here you can download a manual on how to install the drivers.
Click to expand...
Click to collapse
I didn't think on a mac you had to install drivers

peppi.nl said:
I always had to install the ADB drivers manually, before fastboot mode worked.
Here you can download a manual on how to install the drivers.
Click to expand...
Click to collapse
I'm running on a mac... I must be blind cuz i can't find a mac guide to install drivers...

First download android sdk from
http://developer.android.com/sdk/installing.html
install the application and then
then copy all the files in platform-tools to tools
export PATH=${PATH}:/Users/drgopoos/Desktop/Android/android-sdk-mac_86/tools
when u do this commands u can use wthout ./
open terminal
and cd the directory of the installation folder ( /Android/android-sdk-mac_86/tools )
this is the command for flashing
./fastboot -i 0x413c flash recovery recovery.alt.img

iphonepimp said:
I followed ur guide an all but im trying to install clockwork on my streak (2.2 stock 318) and it gets stuck at <waiting for device>
anyone know how to get past this?
Click to expand...
Click to collapse
Is your device in fastboot mode? Power off, power on holding camera button, when you get the white screen tap on fastboot on top left, then plug in streak to mac.
Sent from my Dell Streak using XDA App

[IMAGES] HMJ37 (USA WiFi 3.1) & HTJ85B (USA WiFi 3.2)

Here it is, Un-Official USA WiFi 3.1 & 3.2 Stock images. These are pulled from a clean USA WiFi 3.1 (stock 3.0.1 updated through the Official update). 3.2 is pulled from a clean USA WiFi 3.2 (stock 3.0.1 updated through the Official updates).
Commands:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
THESE IMAGES ARE FOR FIXING PROBLEMS AND WILL NOT WORK WITHOUT THE 3.1 BOOTLOADER
I AM NOT RESPONSIBLE IF YOU BRICK YOUR DEVICE, FOLLOW THE DIRECTIONS 100%
DO NOT TRY AND OEM LOCK YOUR DEVICE WITH THESE IMAGES​
Download links: HMJ37 USA WiFi 3.1 & Mirror
Download links: HTJ85B USA WiFi 3.2 & Mirror
Mirrors provided by Berzerker

Thank you Sir.
Sent from my HTC HD2

Thx B 10chars

Awesome .. thanks for posting.. still scared to root my WiFi Xoom though.. been through OG DROID, DROID x and HTC thunderbolt. But not sure if I want to cross the line with the Xoom.. I've had to use the sbf before on the DROID x..

May I ask how you do the backup of stock images?
Thanks.

khtdev said:
May I ask how you do the backup of stock images?
Thanks.
Click to expand...
Click to collapse
As far as I know, there are two methods. One is through CWR which I haven't really looked at. The other way is through Linux on a semi rooted Xoom. In that case you just have to use the dd or cat command on the proper device. If you type "mount" from Linux, you'll see where system is. Go to that "by-name" directory and you'll see the links for the boot and recovery partitions as well.

khtdev said:
May I ask how you do the backup of stock images?
Thanks.
Click to expand...
Click to collapse
As Scourge1024 said the easiest way on the xoom is to oem unlock, then load CWM. Do a nand backup, you have the system and boot img. This will not get you the userdata or recovery though. To get recovery, you have to load a rooted boot.img and just pull it with adb commands. Getting the userdata will never happen on the xoom (by an end user). The problem is that when you pull it, it pulls the entire partition regardless of how much is in use. You can not backup a 30gb partition on a 30gb partition

Yup. To grab the recovery, you need to sacrifice the boot partition. Or have a system image with su and Superuser.apk injected into it already. With putting in a new kernel, you'll have root through adb. With the su/Superuser.apk method, you can get root through terminal emulator. And just use the dd command from either methods.

It is safe to use oem lock with files bwcorvus?

gerald410 said:
It is safe to use oem lock with files bwcorvus?
Click to expand...
Click to collapse
As it says in the first post, DO NOT try and lock with these files. I tried 3 times, softbricked all 3 times. You need official files from Motorola to lock. If you need to lock, grab the files from my other sticky for stock wifi and use them.

bwcorvus said:
As it says in the first post, DO NOT try and lock with these files. I tried 3 times, softbricked all 3 times. You need official files from Motorola to lock. If you need to lock, grab the files from my other sticky for stock wifi and use them.
Click to expand...
Click to collapse
Duh how could I miss that in big red letters no less! thx for the confirmation

bwcorvus said:
As it says in the first post, DO NOT try and lock with these files. I tried 3 times, softbricked all 3 times. You need official files from Motorola to lock. If you need to lock, grab the files from my other sticky for stock wifi and use them.
Click to expand...
Click to collapse
While on unlocked/rooted 3.1 can you use the official 3.0.1 (HWI69) images to get back to stock/locked mode safely or do we have to wait for Motorola to release the HMJ39 images to do that ?

lazarost said:
While on unlocked/rooted 3.1 can you use the official 3.0.1 (HWI69) images to get back to stock/locked mode safely or do we have to wait for Motorola to release the HMJ39 images to do that ?
Click to expand...
Click to collapse
You can back safety, only way to lock as of right now.
Sent From My Evo

I have a completely stock Canadian Wifi Xoom MZ604.
If I unlock my xoom, wiping everything clean, can I then use these files to update it to 3.1? Would this effectively convert my xoom into a US model MZ604?

great dude keep it on

Thanks,
These may save my Xoom one day. Good to know.

Damn, it really works ...
bwcorvus said:
Here it is, Un-Official USA WiFi 3.1 Stock images. These are pulled from a clean USA WiFi 3.1 (stock 3.0.1 updated through the Official update). I have flashed all four twice now just to make sure it works.
Commands:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
THESE IMAGES ARE FOR FIXING PROBLEMS AND WILL NOT WORK WITHOUT THE 3.1 BOOTLOADER
I AM NOT RESPONSIBLE IF YOU BRICK YOUR DEVICE, FOLLOW THE DIRECTIONS 100%
DO NOT TRY AND OEM LOCK YOUR DEVICE WITH THESE IMAGES​
Download link: HMJ37 USA WiFi 3.1
Click to expand...
Click to collapse
It's working like a charm ...
What I did ...
0. I've root my Xoom WiFi (which I think wasn't a required step).
1. I've unlocked my Xoom using "fastboot" tool (please check if usb debugging was turn on if can't detect device)
2. I've got the file "HMJ37(USA_WiFi_3.1).zip", extracted and just flash those images ...
3. as the 1st post said, DO NOT lock it using fastboot!!!
steps:
> adb reboot bootloader
> fastboot oem unlock
# it will reboot after successful unlock process
> fastboot flash boot boot.img
# ... etc as quoted command
> fastboot erase cache
> fastboot reboot
4. got a taste of the new Android 3.1 on my Xoom
Gee bwcorvus, thanks again for sharing!!!

sweet good to have

HI, yes iam a noob, I have a similar problem to Masterslacker above.
My MZ604 Xoom has a build no. that says it's Latin America, in addition it's a Demo model bought in the US from Walmart. My question is, can i change the Build from H.6.2-21- demo 1301358186, to the US version, HWJ 37 (USA Wifi 3.1)??

Reflashing the Xoom
Ok, I have been looking around the site for the directions to reflash my Xoom. Can't find them. Can someone point me in the right direction.

[Q] Doomlord for dummies

Hi,
Sorry if this has been asked elsewhere but is there a dummies guide / video for installing Doomlord kernel onto my play? the full process i.e. how to unlock your bootloader, to the app and images you need to download, and then the process.
A nice youtube video would be great. TIA
neil

Am busy,but there are lots of videos on how to unlock your bootloader for xperias.I think it was by androidsoul community? If you type in Unlockbootloader for Play,you gonna get e-z results.
Whats your model too?Use the very same fastboot ,the one you used to unblock bootloader,to get DK3

Hi, I have unlocked my bootloader. there was a video on youtube using fastboot.
I have a r800I,
2.3.2
build 3.0.a.2.184
What next?

Alright.
Grab a flashtool 2.9.1 ,install gordons gate drivers 22 found in the flashtool Drivers Folder.
Grab this Firmware : http://forum.xda-developers.com/showthread.php?t=1255095
you may get a bootloop if you dont wipe user data.
Flash it with the X10Flashtool.exe
Follow the instructions zactly.
Then use Fastboot to flash boot the DK3.img

HI, I have flashed back to Uk generic many times, so think I can do the first part.
I do not understand this bit sorry
Then use Fastboot to flash boot the DK3.img

Alright.
After you have the 4.0.A (2.3.3 ,not 2.3.2) you drag the DoomKernel3 img to fastboot folder,shift +rightclick and type this in
fastboot flash boot doomkernel3.img (or in your case its boot.img)

Ok, just so I have it straight.
donwload image. Flash the new image just like a did the old UK Generic. (i.e. using flash tool, then pressing back button connected to PC)
Do I let it boot normally? Or do I go straight to removing battery then boot up holding the Search key (blue light) and doing the flash boot command?
so many thanks for this

nelly_boy said:
Ok, just so I have it straight.
donwload image. Flash the new image just like a did the old UK Generic. (i.e. using flash tool, then pressing back button connected to PC)
Do I let it boot normally? Or do I go straight to removing battery then boot up holding the Search key (blue light) and doing the flash boot command?
so many thanks for this
Click to expand...
Click to collapse
No you use a cmd window on your pc and 'cd' /to/the/path/of/fastboot or open your fastboot folder and in an empty space, ctrl+shift - open in cmd - then type the command issued 'fastboot flash boot boot.img'. You need to hold search button while connecting the usb, when the phone is off to get into fastboot mode. Done correctly the blue light should appear.
Regards Dousan...

confused then...
"Grab a flashtool 2.9.1 ,install gordons gate drivers 22 found in the flashtool Drivers Folder.
Grab this Firmware : http://forum.xda-developers.com/show....php?t=1255095
you may get a bootloop if you dont wipe user data."
Flash it with the X10Flashtool.exe --- this means doing it with the back button right????
---- This is where I was asking if you let it boot normally first (i.e. like you would after Uk genric
Follow the instructions zactly.
Then use Fastboot to flash boot the DK3.img - understand this bit but need to know when to do it

nelly_boy said:
confused then...
"Grab a flashtool 2.9.1 ,install gordons gate drivers 22 found in the flashtool Drivers Folder.
Grab this Firmware : http://forum.xda-developers.com/show....php?t=1255095
you may get a bootloop if you dont wipe user data."
Flash it with the X10Flashtool.exe --- this means doing it with the back button right????
---- This is where I was asking if you let it boot normally first (i.e. like you would after Uk genric
Follow the instructions zactly.
Then use Fastboot to flash boot the DK3.img - understand this bit but need to know when to do it
Click to expand...
Click to collapse
Sorry my bad mate I misread your post (I need some sleep or glasses lol).
Yes you're right flash the UK generic with flashtool and then doomlords kernel with fastboot command. I'm not sure if you need to boot before you flash the kernel. I would boot just to be safe
Regards Dousan...

all working thanks guys. you the best. shame I just saw 2.3.4 guessing that wont work with doomlord kernel?
Man it boots quick hopefuly setcpu will make my ps1 games run better.
thanks again

DK4 soon will be availibile

Nexus S Official factory images for 9020t & 9023

http://code.google.com/android/nexus/images.html#yakju
https://groups.google.com/forum/?fromgroups#!topic/android-building/b50nY_onbP4

^Thanks.
This can be flashed via CWM recovery ?
(after a 'fastboot oem lock/unlock' ?)

No. They are fastboot images. If you're not sure what these are and how to use them then I would not mess with them.

^ gotcha
can someone please put up a tutorial/guide to do this.
I really want to try this.

The shell script gives you the exact fastboot commands to run if you want to do it manually. And it will restore your phone to a true factory state with 4.0.4.

if i will use the factory img the baseband version in bootloader will be change? i see now i9020xxkl1 but my nexus is i9023?

I was wondering the same .. In the zip it says :require board=herring
require version-bootloader=I9020XXJK1|I9020XXKA3|I9020XXKI1|I9020XXKL1
require version-baseband=I9020XXJK8|I9020XXKB1|I9020XXKD1|I9020XXKF1|I9020XXKI1|I9020UCKB2|I9020UCKD1|I9020UCKF1|I9020UCKJ1|I9020KRKB3|M200KRKC1
So it should be okay , because when I reboot into the bootloader of my phone it says :
Bootloader version: I9020XXKL1
Baseband version : I9020XXKI1
My phone actually is a I9023 so I gues the images are okay to flash on a I9023

Just noticed that the full ROM version for Nexus S is 4.0.4 IMM76D. Wouldn't be better to flash this complete rom instead of the partial patch OTA which is clearly giving troubles?

HELPPPPP
can someone please put up a tutorial/guide to do this.
I really want to try this.

i wrote a guide
http://forum.xda-developers.com/showthread.php?t=1572307

goldy_rocky said:
can someone please put up a tutorial/guide to do this.
I really want to try this.
Click to expand...
Click to collapse
(No time to write a full tutorial right now but...) I'd say...
Pls wait for someone experimented to confirm what I say because I couldn't try it to confirm it works right now... And also try it at your own risk...
If your bootloader is not unlocked, follow PART 1 & PART 2 of this tutorial. (you will loose data)
(Note that ADB is not in tools folder anymore but in /platform-tools so that's where the part2 cmd as to be runned from)
Then if windows (I guess you would know what to do if on Linux) use 7zip to extract (2 times) all files from the archive.
Then copy the files to the /platform-tools folder.
The open a command prompt in that folder (shift+right click>open a command prompt here).
Then use the commands provided in the .sh script to flash all files (you can read it easily with Notepad++ for instance) one by one...
Note I don't think you can run the "sleep 5" cmd manually but you can of course wait 5' manually .
Code:
fastboot flash bootloader bootloader-crespo-i9020xxkl1.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-soju-imm76d.zip
I'm not really sure if bootloader will be locked at this time but my guess is no so just reboot the bootloader ("fastboot reboot-bootloader" or shut down the device then "Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button" and look for the "LOCK STATE - LOCKED" or "LOCK STATE - UNLOCKED").
If "LOCK STATE - UNLOCKED" you may want to lock the bootloader again, just follow part2 again and replace "fastboot oem unlock" by "fastboot oem lock"
EDIT :
ale.landra91 said:
i wrote a guide
http://forum.xda-developers.com/showthread.php?t=1572307
Click to expand...
Click to collapse
You just made me feel so useless ...

First of all, the credits goes to "a2b". I am only put his work here via a link.
Secondly, PLEASE KEEEP IN YOUR MIND THAT NEITHER ME OR "a2b" IS RESPONSABLE FOR ANY LOSS OF YOURS IF YOUR PHONE GET BRICKED.
The thrid, I have tried the method on my Nexus i9023. It works perfectly for me. BUT, I cannot gurentee it works for everyone.
Okay, I just flashed the factory img according to a2b's tutorial for Galaxy Nexus. But for me I just needed to change the names for few files. If you cannot figure out what to change, I suggest you follow albundy2010's advice on post #3
Good luck!
http://androidtobe.blogspot.com/2011/12/galaxy-nexus-installing-ics-402-from.html

Seems most are not familiar with doing this so here are some things you should know.
Doing this will wipe EVERYTHING off your phone. Yes, everything including /sdcard.
Do not be a fool and flash these images to the 4g.
I am not certain about this and if you it and your phone gets messed up do not blame me.
The 9020a should be able to run this factory image. Check to see what version of the bootloader you have. If it matches one of the bootloaders in the .sh script you should be fine. I would NOT flash the bootloader included in this factory image myself. Since I do not know for sure if they are the same for both GSM models. If you follow the guide minus the parts where you flash the bootloader and the radio image I believe it will work.
Again if you try this and it breaks your phone that is on you. I am not responsible for it. I do not have a 9020a to test this on and verify it. I am fairly certain it will work perfectly. If anybody tries it let me/us know the outcome.

is there any specific advantage in flashing the factory image as opposed to flashing the incremental update ? I successfully flashed 4.0.4 using CWR over a full rom installation of 4.0.3 back from December. I wonder if there may be some subtle differences that maybe make it a bit better option to install the factory image ?

mindwalkr said:
is there any specific advantage in flashing the factory image as opposed to flashing the incremental update ? I successfully flashed 4.0.4 using CWR over a full rom installation of 4.0.3 back from December. I wonder if there may be some subtle differences that maybe make it a bit better option to install the factory image ?
Click to expand...
Click to collapse
No
Sent from my Nexus S using XDA App

I used the flash-all.sh script from the factory image file and it didn't wipe the sdcard. Backed it up beforehand anyway just in case. Recovery was broken on reboot. Flashed CWM recovery and all good. i9023.

Bricked while trying to install Full Android rom.. Now Boot loop into twrp. Pls help.

Well,
basically subject says all.
I tried to install zulu99 Full android rom 2.1.
basically 'fastboot flash system system.img worked' but 'fastboot -w' failed ('no space left' error).
So I rebooted hoping to reflash a nandroid backup but now the box keeps on rebooting into twrp trying to wipe cache and data but failing. after a while it stops and black screen appears.
I attach the screen it presents when reboots.
Please tell me I didn't trash 220 euros.
Thanks.

puppinoo said:
Well,
basically subject says all.
I tried to install zulu99 Full android rom 2.1.
basically 'fastboot flash system system.img worked' but 'fastboot -w' failed ('no space left' error).
So I rebooted hoping to reflash a nandroid backup but now the box keeps on rebooting into twrp trying to wipe cache and data but failing. after a while it stops and black screen appears.
I attach the screen it presents when reboots.
Please tell me I didn't trash 220 euros.
Thanks.
Click to expand...
Click to collapse
Theres a hardware method to boot into the bootloader, this i think you can test, just to see if you can at least get into bootloader.....nothing more
Details in the official nvidia link
http://nv-tegra.nvidia.com/gitweb/?...ob_plain;f=README_SHIELD;hb=rel-22r18-partner
There's a thread here on the "questions" thread with users reporting that the timing of the hardware method can be a pain in the you know where.............might be worth looking into that thread for their experiences in booting the bootloader using the hardware method
Disclaimer:If your brave enough to risk a brick, read on
I suspect this might be the 2.1 stock/twrp issue........current twrp, or current stock dont play nice
Its a good sign that SOMETHINGS loading, rather then NOTHING booting, but dont know if theirs a solution
My analysis of the situation, of what little i know, the -w (wipe) command was expecting a stock recovery but instead got twrp, which is why your in this situation.........maybe, i stress maybe, if you could reflash stock again, you might be able to boot into android stock again and try full android again, leaving out twrp, until a twrp fix is found
Edit
Saying that, if the bootloader is, as i suspect, now using twrp to flash things, then you might be boned....... im no expert on bootloaders, stock "recoveries" and how they work, so i might be wrong on that
Reports around here say that 1.3 stock firmware is the recommended back to stock firmware, apparently, flashing any other firmware versions, bring their own issues.............
From 1.3 stock, use nvidias official OTA to upgrade from 1.3 stock, to 2.1 stock, then try 2.1 full android again...........note, i dont think you can skip firmwares i.e. you have to upgrade to 1.4, then to 2.0, then to 2.1, alot of downloading.......the OTA does'nt give you any other choice
Before doing anything that ive suggested, wait till someone with more experience to come along........i dont want to be responsible for you fully bricking your shield..........just wanna give you an idea of what i think has happened
If worse comes to worse, if you have warrenty, get a replacement
Gd luck........remember, this is an analysis of your predicament of what i THINK might of happened, and what steps, i likely might of entertained.......after looking into it more thouroughly, knowing that i could get a replacement if it went downhill.........so your mileage might vary
Edits
Crappy grammer, further musings, clarifications

Thanks.[/QUOTE]
puppinoo said:
Well,
basically subject says all.
I tried to install zulu99 Full android rom 2.1.
basically 'fastboot flash system system.img worked' but 'fastboot -w' failed ('no space left' error).
So I rebooted hoping to reflash a nandroid backup but now the box keeps on rebooting into twrp trying to wipe cache and data but failing. after a while it stops and black screen appears.
I attach the screen it presents when reboots.
Please tell me I didn't trash 220 euros.
Thanks.
Click to expand...
Click to collapse
I had something similar about... shield goes booting in recovery and trying delete some cache and keeps repeat and repeat
Hardware boot in fastboot / bootloader mode
Accessing Bootloader via Hardware
Unplug power from the Shield Android TV. *
Wait a few seconds.
Hold down the power button.
Plug in power
Count to three
Release the power button
You should see the bootloader screen.
If you hold it down too long or not long enough, it simply doesn’t work.
Restore Shield Android TV to Stock
P.s. Personally me I followed this instructions and kind of magically got it in bootloader mode. First done by instruction and then just gave up and pressed randomly and fastboot screen appear. Thanks God I had to done only once, if I would do again I wouldn't had patients
Good luck with this, hope you will get sorted
Here will be link about where I got instructions about hardware boot
http://nvidiashieldzone.com/index.php/shield-android-tv/root-shield-android-tv/
Sent from my Nokia 3310 using free xda app

Thanks a lot fro your help.
I was able to put the box in fastboot mode.
Since I'm not that expert can you tell me where and which rom I have to download (I have a french 16gb version of the box).
Then I'd need to know exactly what commands to performs (even a link to a tutorial is fine).
I really appreciate your help. It seems I can (hopefully) save the box.
EDIT: The fastboot command gave me a (not enough space) when I bricked the box. Is there a risk it could happen again while flashing stock? No idea how much space I have left on the box really.
EDIT2: I found this page: https://developer.nvidia.com/shield-open-source
and I'm downloading this rom called nv-recovery-image-shield-atv-upgrade2_1.zip
and Intend to follow these instructions: http://developer.download.nvidia.co...TV/Upgrade-2.1/HowTo-Flash-Recovery-Image.txt
Can anyone please confirm I'm doing right?

EDIT with joy : I followed all the steps using that rom and it seems everything worked. I reconfiguring the box now. Thanks for help.
basically the procedure I intend to follow is this part (please confirm it's ok):
To flash this recovery image to your SHIELD, run the following commands from
the directory where you extracted the recovery image package. If this is the
first time you have done this procedure, you must unlock the bootloader. Get
DTB file name to use for flashing for your product(see below):
P.s. maybe Since past fastboot commands failed and I only flashed system from zulu99 I could skip the 'fastboot flash boot boot.img' command so if it fails again I still can attempt the fastboot process again?
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb <DTB file name>

puppinoo said:
Thanks a lot fro your help.
I was able to put the box in fastboot mode.
Since I'm not that expert can you tell me where and which rom I have to download (I have a french 16gb version of the box).
Then I'd need to know exactly what commands to performs (even a link to a tutorial is fine).
I really appreciate your help. It seems I can (hopefully) save the box.
EDIT: The fastboot command gave me a (not enough space) when I bricked the box. Is there a risk it could happen again while flashing stock? No idea how much space I have left on the box really.
EDIT2: I found this page: https://developer.nvidia.com/shield-open-source
and I'm downloading this rom called nv-recovery-image-shield-atv-upgrade2_1.zip
and Intend to follow these instructions: http://developer.download.nvidia.co...TV/Upgrade-2.1/HowTo-Flash-Recovery-Image.txt
Can anyone please confirm I'm doing right?
Click to expand...
Click to collapse
You are on the right way with those links
P.s. You can do manual one by one entering or paste and copy those commands or (I'm doing) drag and drop file "flash-all.bat" on cmd previous opened there where you have abd/fastboot etc files and extracted RIGHT FIRMWARE (like shift and right click mouse "open command prompt here"
And after this all sit down and relax
Anyway you are on the right way.
P.s. Hope you download adb fastboot drivers somewhere from Internet !?!
Sent from my Nokia 3310 using free xda app