Database Users

[Q] Setting up ADB/Fastboot on a cm7 device

Hi, I was going to setup adb on my froyo MT4G, but I didn't...now I am trying to setup fastboot and ADB on my computer, but I can't figure it out. It seems like guides are written for android 2.2 when it comes to the MT4G and ADB. I have cm7 on my phone, so how do I setup ADB for it? I am trying to find it, but I don't know enough to know what would work, have tried certain guides, but once I get to a point where there is a disclaimer I tend to shy away since, I am not sure what guide I should be following for my weird situation and trying to setup adb for it..Please, thank you.

Just go to android.com and get the sdk stuff. There's intructions on the site and on here. The only difference for cm7 is your gonna need to go through the sdk and avd manager and download the stuff for 2.3. PM me after you get everything downloaded and I'll help you through any part you get stuck on.

Hmmm might be awhile before I can try this but I will
jbrew78 said:
Just go to android.com and get the sdk stuff. There's intructions on the site and on here. The only difference for cm7 is your gonna need to go through the sdk and avd manager and download the stuff for 2.3. PM me after you get everything downloaded and I'll help you through any part you get stuck on.
Click to expand...
Click to collapse
Sent from my MT4G running Gingerbread

Honestly, I think your long term fix is ubuntu. A lot of people don't want to hear that, but it's easier than you think. You can run a dual boot, or set up a virtual machine on your current computer. You can download vmware here:
http://www.vmware.com/products/player/
And ubuntu here:
http://www.ubuntu.com/desktop/get-ubuntu/download
Then install adb, fastboot, etc. and never have any driver issues again. Problem solved.

Android SDK for ADB:
http://developer.android.com/sdk/index.html
I think the executable file installs so you can run the commands from dos prompt without the difficulties of making it executable.
Fastboot:
http://developer.htc.com/adp.html
You'll need to save it to the same folder the sdk tools are in to use it in dos prompt.
Then it's reading on how to do all the necessary things to root/flash/etc.

Thank you. I am downloading the sdk files right now, I wish I had a computer so I could read more about developing and stuff...right now I just have to use my GFs when im over here, but I have to avoid things once I start getting interested otherwise I will be sucked into an abyss of knowledge for hours, and snap out of it, and then have to figure out why she is mad at me, hahhaha... so I have a generic question though... is fastboot basically like terminal? And you can get into it from hboot right? Don't need to have your computer connected to it or anything right?
foxdl99 said:
Android SDK for ADB:
http://developer.android.com/sdk/index.html
I think the executable file installs so you can run the commands from dos prompt without the difficulties of making it executable.
Fastboot:
http://developer.htc.com/adp.html
You'll need to save it to the same folder the sdk tools are in to use it in dos prompt.
Then it's reading on how to do all the necessary things to root/flash/etc.
Click to expand...
Click to collapse

fastboot has 2 components: one on the computer for entering commands onto the phone while it is in fastboot mode (the second thing). So yes, it has to be on the computer to enter commands like flashing recoveries. There are alternate methods for everything, you can flash recoveries using flash_image from the phone as well, for example.

foxdl99 said:
fastboot has 2 components: one on the computer for entering commands onto the phone while it is in fastboot mode (the second thing). So yes, it has to be on the computer to enter commands like flashing recoveries. There are alternate methods for everything, you can flash recoveries using flash_image from the phone as well, for example.
Click to expand...
Click to collapse
Wait so I have to connect my phone to my computer to use fastboot cmds on my phone?
So if I have fastboot setup, and I am walking around with my phone in my pocket and I pull it out and check xda and see a new splash screen I want. I can reboot into bootloader, and then enter fastboot and type some kind of command like.. fastboot splash3 google.img and that will work? Or your saying I have to have it plugged into the computer?...because if that is the case then whats the difference between ADB and fastboot?

fastboot is for messing with the boot section of the phone while in fastboot mode on the phone, whereas adb messes with the os itself. And you do have to have it connected to your pc to use. As to the boot images or animations, you can install some of those with root explorer by putting them in the appropriate place in the file system. For instance, boot animations go in /system/media/bootloader.zip. But some modders put out a .zip flashable file that you can flash in recovery. Confusing, huh? If you find one you want to try, the dev should let you know how to install it.
I think what you're looking for though is root explorer, which will allow you to modify certain areas on the fly from the phone. It's a paid app.
Edit: with the splash screen, i think you may have to use fastboot because it goes in the bootloader section which I don't think you can access any other place. But I'm not sure.

I have root explorer... hmm I guess I have been missing what fastboot is all about... well maybe ill just get it all setup and play with it to figure it out.. thanks for your help I'm going to sleep for now.
foxdl99 said:
fastboot is for messing with the boot section of the phone while in fastboot mode on the phone, whereas adb messes with the os itself. And you do have to have it connected to your pc to use. As to the boot images or animations, you can install some of those with root explorer by putting them in the appropriate place in the file system. For instance, boot animations go in /system/media/bootloader.zip. But some modders put out a .zip flashable file that you can flash in recovery. Confusing, huh? If you find one you want to try, the dev should let you know how to install it.
I think what you're looking for though is root explorer, which will allow you to modify certain areas on the fly from the phone. It's a paid app.
Edit: with the splash screen, i think you may have to use fastboot because it goes in the bootloader section which I don't think you can access any other place. But I'm not sure.
Click to expand...
Click to collapse
Sent from my MT4G running Gingerbread

[3g STOCK .IMG] VZ WIRELESS MX600 5/3/2011

Here are the .IMG files that Motorola has posted on their MOTODEV site. .
ATTENTION: DO NOT ATTEMPT TO FLASH THIS FILE ON ANYTHING BUT THE VERIZON WIRELESS MOTOROLA XOOM Z600 (3G MODEL) OR YOU WILL HAVE A SHINEY PAPER WEIGHT!!!!
These files are from Motorola's Development site but I take no liability with anything that happens with your device if something goes wrong.
Official HRI39 Motorola .IMG files:
http://www.multiupload.com/9XP1B8LSWC
Official HRI66 Motorola .IMG files:
http://www.multiupload.com/POUDJY1255
The following are the steps from the MOTODEV site
1. Extract files into android sdk /tools folder.
2. Start command prompt/ terminal from the android sdk tools folder. (How this is done on Mac I do not know, Windows: shift+left click and select "open command window here")
3. adb reboot bootloader
4. fastboot flash boot boot.img
5. fastboot flash system system.img
6. fastboot flash recovery recovery.img
7. fastboot flash userdata userdata.img
8. fastboot erase cache
9. fastboot oem lock
The device will lock and reboot.
You are now back to out of box state. However I do not know if it is still detectable by VZ Moto if you have unlocked the device after doing this.
Also fyi the sbf file is still an option but you will have to go in and do the fastboot oem lock after it completes

u mispelled cache

Fixed. Thanks had a long day and missed that at proof reading

Thanks for the files, does seem a lot simpler to just use the sbf file though.

bwcorvus said:
Thanks for the files, does seem a lot simpler to just use the sbf file though.
Click to expand...
Click to collapse
Its always good to have more options and the Xoom gives us many and hopefully soon sdcard support will provide the final key piece, the CM recovery!
In the meantime it is very good to have all of the official files at our disposal.
If anyone is wondering what the the reflash file from the first leak is, it is an SBF format installation of the stock boot image and a blank user data image to wipe data and return to stock via RSD Lite without touching the system partition.
This provides yet another way to reset that should be examined, especially if it works over a modified system partition.
We also may be able to use any or all of these files to build our own SBF files and other one step solutions for recovering and or modifying the Xoom. This can be very valuable and must also be thoroughly explored along with the NVM so we can really start to tak better control of the radio functions.
Lots to look at...

I am in love with fastboot. I am so use to the days of the OG Droid where the bootloader wasnt locked but you didnt have fastboot as an option. I can see a lot of easier days in the Dev community coming.

jmc2543 said:
I am in love with fastboot. I am so use to the days of the OG Droid where the bootloader wasnt locked but you didnt have fastboot as an option. I can see a lot of easier days in the Dev community coming.
Click to expand...
Click to collapse
Yea having these images is one BIG step...now we just need sdcards

Just finished doing this. I'm back at stock. Of course no I'll b the last to get an update. And by the same time tomorrow I'll be unlocking and re-rooting.

by doing this does it erase everything on your xoom?

bishop72 said:
by doing this does it erase everything on your xoom?
Click to expand...
Click to collapse
Yes it would. Itll bring it back to what it was like when you first bought it.

For those that updated, were you able to reroot?

17akota said:
Yes it would. Itll bring it back to what it was like when you first bought it.
Click to expand...
Click to collapse
I saw multiple threads about Titanium backup not working with the Xoom. Are there alternative apps that will save all my configuration like home screen layout etc? It was a lot of work B-)
Sent from my Xoom using Tapatalk

It is just Android 3.0
3.0.1 is HRI66

Do I need to do this if I have rooted, just unlocked? Can I just "fastboot oem lock" and be good to go?

Aaron636r said:
Do I need to do this if I have rooted, just unlocked? Can I just "fastboot oem lock" and be good to go?
Click to expand...
Click to collapse
Oh no. I did the "fastboot oem lock" and now I get "Failed image LNX 0x0002". Cant boot past Dual Core logo screen.

Ok, re-unlocking it fixed it.

Ok so we have the original flash so we can get the OTA thats great. And Moto confirmed on their forum they will upgrade devices that have been unlocked and rooted. If they cannot install the software they will ship it back with just the new hardware. Can't wait to see what people can really start doing now.

For those of you that are like me and hate having to using mega upload and crap to download things here is a direct link on my web server to the file released by Moto.
DMCA Noticed by Moto
This was taken directly from the Moto Dev site myself.
If you browse the directory, which I think I left on for this one... There is also the sbf archive and RSD there to download. If anyone needs a place to store some files let me know. I have unlimited storage and bandwidth. When some of the OG Droid releases came out I was pumping over 11GB a week in downloads with no issues. It's the least I can do to help the community.

I got to be honest I don't know what the hell i should do to get the update and what will cause me to either have a clean install or lose root

All reports so far indicate it will not break root and rooted users have been getting the notification. They are also probably doing a controlled rollout if you have not yet gotten the notification. My XOOM is at home right now which sucks I won't be able to get my hands on it for about 6 hours and see what I can all do.

Help an idiot flash a factory image

So i decided a few days ago to try and flash a factory image for kitkat on my N7. But i downloaded the image for the wrong device. the script has wiped recovery and system etc. The N7 now just boots to bootloader.
i got the proper factory image to flash, but i cannot get the device recognized on the pc running Windows 7 now. its showing as Other Devices / Android. I did install the drivers from the SDK and it now appears as Android ADB Interface. However ADB is still not recognizing it. I have done adb devices but nothing is found.
Any help, it is fixable isnt it??

You can't use adb commands in fastboot. You should use fastboot commands and flash the factory image
Sent from my Nexus 5

Tones1971 said:
So i decided a few days ago to try and flash a factory image for kitkat on my N7. But i downloaded the image for the wrong device. the script has wiped recovery and system etc. The N7 now just boots to bootloader.
i got the proper factory image to flash, but i cannot get the device recognized on the pc running Windows 7 now. its showing as Other Devices / Android. I did install the drivers from the SDK and it now appears as Android ADB Interface. However ADB is still not recognizing it. I have done adb devices but nothing is found.
Any help, it is fixable isnt it??
Click to expand...
Click to collapse
Well, I had a serious issue with something similar, after trying to update (not flash the factory image) to KitKat it produced an error and now it's bootlooping and, worse, my computer won't recognize the device, so I can't flash the factory image whatsoever. Your problem is much more light, as your computer is actually recognizing the device. What I'd suggest is using the Nexus Root Toolkit by WugFresh. Yes, I know, a lot of people here don't like using it but it's extremely useful when you have drivers issues.
It's actually a pretty straight forward procedure, you install the toolkit and it will ask you for your device model, android version, etc., then take you through the process of updates and stuff. Then, on the main window, you have this wizard "Full Driver Installation Guide" that will give you 4 ways to get your device working. You can find the Toolkit here: http://www.wugfresh.com/nrt/. Good luck!

I vote we ban all talk of toolkits. 99.9% of the help threads around here start with, "I was using/used x toolkit and now my device won't boot."
What happened to people learning about their devices?
How about learning how to fix your problems, rather than compound them by not understanding what you are doing? How about if you don't have the capacity to learn it, you leave it the F alone?
Sent from my Nexus 5

Pirateghost said:
I vote we ban all talk of toolkits. 99.9% of the help threads around here start with, "I was using/used x toolkit and now my device won't boot."
What happened to people learning about their devices?
How about learning how to fix your problems, rather than compound them by not understanding what you are doing? How about if you don't have the capacity to learn it, you leave it the F alone?
Sent from my Nexus 5
Click to expand...
Click to collapse
It's also difficult when trying to assist somebody... they're using the vocabulary of toolkits (which I'm not familiar with)... and I'm going on about fastboot... which they don't understand. It's like there are now two different languages... TOOLKIT and FASTBOOT.
Makes it very difficult to assist people.
Maybe I should have a tinker with Wugfresh... if for no other reason than to at least get an insight into how these things work.
Rgrds,
Ged.

The concept of the toolkit is great. It's the implementation and use of it that is horrible.
I think a toolkit should walk you through the actual steps and force you to type in the commands. You select an option of what you want it to do, it tells you what to type step by step to achieve said goal, and checks that you don't type in the wrong thing for the option you selected.
Unfortunately I don't think there is a market for that when you can get everything 'one clicked' for you.
Sent from my Nexus 5

Pirateghost said:
The concept of the toolkit is great. It's the implementation and use of it that is horrible.
I think a toolkit should walk you through the actual steps and force you to type in the commands. You select an option of what you want it to do, it tells you what to type step by step to achieve said goal, and checks that you don't type in the wrong thing for the option you selected.
Unfortunately I don't think there is a market for that when you can get everything 'one clicked' for you.
Sent from my Nexus 5
Click to expand...
Click to collapse
So an edit box where you could be prompted to type in things like fastboot flash recovery recovery.img... interesting idea... sort of walks you through the process, but doesn't obsessively hold your hand, where you don't learn anything.
I suspect most people just have problems with drivers, because, let's face it, fastboot and ADB aren't exactly difficult to use... unless people have difficulty understanding command lines in these GUI driven days, where everything is a simple menu or button click away... kind of sad really.
Rgrds,
Ged.

GedBlake said:
So an edit box where you could be prompted to type in things like fastboot flash recovery recovery.img... interesting idea... sort of walks you through the process, but doesn't obsessively hold your hand, where you don't learn anything.
I suspect most people just have problems with drivers, because, let's face it, fastboot and ADB aren't exactly difficult to use... unless people have difficulty understanding command lines in these GUI driven days, where everything is a simple menu or button click away... kind of sad really.
Rgrds,
Ged.
Click to expand...
Click to collapse
Basically yeah.
I have a feeling a good portion of the hesitation comes from the command line being scary to most people.
Sent from my Nexus 5

In the tgz file you download there is a 'flash-all.bat' file that does everything for you. If you open it in notepad, you see exactly what it does and in what order.
Yes, drivers are probably the issue, they were for me at least. I ended up using NRT (wugs toolkit) to install drivers (and root later, but that's a new topic)
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
ping -n 10 127.0.0.1 >nul
fastboot -w update image-nakasi-jwr66y.zip
echo Press any key to exit...
pause >nul
exit
This is a Google way to flash the factory image.
---------- Post added at 10:02 PM ---------- Previous post was at 09:59 PM ----------
Pirateghost said:
The concept of the toolkit is great. It's the implementation and use of it that is horrible.
I think a toolkit should walk you through the actual steps and force you to type in the commands. You select an option of what you want it to do, it tells you what to type step by step to achieve said goal, and checks that you don't type in the wrong thing for the option you selected.
Unfortunately I don't think there is a market for that when you can get everything 'one clicked' for you.
Sent from my Nexus 5
Click to expand...
Click to collapse
The idea is great, try writing it
I'm sure it'll be greeted with appreciation.

Tones1971 said:
So i decided a few days ago to try and flash a factory image for kitkat on my N7. But i downloaded the image for the wrong device. the script has wiped recovery and system etc. The N7 now just boots to bootloader.
i got the proper factory image to flash, but i cannot get the device recognized on the pc running Windows 7 now. its showing as Other Devices / Android. I did install the drivers from the SDK and it now appears as Android ADB Interface. However ADB is still not recognizing it. I have done adb devices but nothing is found.
Any help, it is fixable isnt it??
Click to expand...
Click to collapse
As long as you can still boot into bootloader mode, it is still fixable. Try reinstalling fastboot drivers.

Pirateghost said:
I vote we ban all talk of toolkits. 99.9% of the help threads around here start with, "I was using/used x toolkit and now my device won't boot."
What happened to people learning about their devices?
How about learning how to fix your problems, rather than compound them by not understanding what you are doing? How about if you don't have the capacity to learn it, you leave it the F alone?
Sent from my Nexus 5
Click to expand...
Click to collapse
Yeah, because that was really helpful to him. I didn't tell him to use the toolkit to flash, root, unlock, or anything of the sort. For drivers issues, I do recommend (and will continue to do so) using the toolkit when official drivers don't work, because it has helped me a lot in the past, but I haven't used it to flash anything.

Download the image for your device and extract it into a folder
Download the zip below and move the files into the folder you created above
http://forum.xda-developers.com/showthread.php?t=1484407
Switch device off. Hold volume down and turn it back on, so it's in fastboot mode
Plug device into computer
Run "flash-all.bat" in the system image folder you extracted first

Want to thank everybody for their replies. Have had a family emergency so havent had a chance to try any suggestions, but didnt want to just ignore the thread i started.

[Q] Droid Razr M not fully booting: Help Please

Hello,
Problem:
factory reset my Droid RAZR M with the hope to resolve in-call audio problems (very low ear piece volume at full). When I rebooted the phone the Welcome screen appeared asking for a language choice. Chose english US. The Message: "Please wait, This may take a few minutes" appeared with a spinning icon. But nothing else ever happens. The phone never moves beyond this selection.
I have android-sdk (Linux setup) installed on my computer in order to use the suite of tools like fastboot and adb. The tools work, in that I can see the phone, pull data, upload to the phone and even get a command shell on the phone. However in order for adb to recognize the phone I have to put the phone in "BT Tools" mode. In "AP fastboot" mode fastboot sees the phone. As far as I remember USB debugging was turned on.
I do not have a recovery image installed.
The phone has Kitkat 4.4.2 ver 183.46.10 and is rooted with TowelRoot. I just unlocked the bootloader today via motoapocalypse package. Status of the phone is unlocked Code 3
I also removed some unused apps - like NFL and a few other space and bandwidth consuming apps that I will never use.
I'd like to get this phone to work again. Is there any hope?
Please advise and thanks for reading.

You can flash custom recovery via fastboot and then custom ROM or flash stock ROM via RSD. Guide is in first thread in general section.
http://forum.xda-developers.com/showthread.php?t=2869432
[GUIDE][FAQ][DIY][KK] How to Root, Boot Unlock & More

Thanks for the pointer. I gather that RSD is a Windows based app. At the present time I do not have a Windows computer. So I took a shot at the job using fastboot, adb and all as found in the android-sdk. Did the steps as described in the flashing post. Now all I ever see is the "Bootloader unlocked warning message" and the phone never progresses beyond the warning. I disassembled the phone, to disconnect the battery -- hoping for a reset miracle. No change after reassembly. Given the latest state of the phone as described above, is there any chance of reviving this phone now that it's stuck at the bootloader warning?
(I read a post about a Motorola Factory Cable -- and if I understand the factory cable puts the phone in a special mode for flashing looking into this option).
I am out to learn and am not afraid of poking around -- so at this point I have no more to lose.
Would the Windows computer make the difference? Using linux mint atm.
Klen2 said:
You can flash custom recovery via fastboot and then custom ROM or flash stock ROM via RSD. Guide is in first thread in general section.
http://forum.xda-developers.com/showthread.php?t=2869432
[GUIDE][FAQ][DIY][KK] How to Root, Boot Unlock & More
Click to expand...
Click to collapse

diordnAMRZAR said:
Thanks for the pointer. I gather that RSD is a Windows based app. At the present time I do not have a Windows computer. So I took a shot at the job using fastboot, adb and all as found in the android-sdk. Did the steps as described in the flashing post. Now all I ever see is the "Bootloader unlocked warning message" and the phone never progresses beyond the warning. I disassembled the phone, to disconnect the battery -- hoping for a reset miracle. No change after reassembly. Given the latest state of the phone as described above, is there any chance of reviving this phone now that it's stuck at the bootloader warning?
(I read a post about a Motorola Factory Cable -- and if I understand the factory cable puts the phone in a special mode for flashing looking into this option).
I am out to learn and am not afraid of poking around -- so at this point I have no more to lose.
Would the Windows computer make the difference? Using linux mint atm.
Click to expand...
Click to collapse
You can try using SBF_FLASH or mFastboot-v2 (which has a linux version) to flash the system.img .

SOLVED: [Q] Droid Razr M not fully booting: Help Please
That worked. Thanks! So the difference between the SDK fastboot and the one in the link provided (mfastboot-V2): the linux-fastboot seems to be smarter about uploading the larger image files to the flashable device (guessing). I am sure I did "flashboot flash system system.img" with the flashboot util from the SDK.
@ATTACK do you have the source for that version of fastboot or patches? Would like to have a look.
Thanks again! Got an unlocked rooted working Droid RAZR M!

diordnAMRZAR said:
That worked. Thanks! So the difference between the SDK fastboot and the one in the link provided (mfastboot-V2): the linux-fastboot seems to be smarter about uploading the larger image files to the flashable device (guessing). I am sure I did "flashboot flash system system.img" with the flashboot util from the SDK.
@ATTACK do you have the source for that version of fastboot or patches? Would like to have a look.
Thanks again! Got an unlocked rooted working Droid RAZR M!
Click to expand...
Click to collapse
Your guess is correct, mfastboot allows you to flash larger system.img's that wont otherwise flash in fastboot.
As for sources... I have no idea who created mfastboot or where it came from. It's just one of those things that get's passed around the internet.

ATTACK said:
Your guess is correct, mfastboot allows you to flash larger system.img's that wont otherwise flash in fastboot.
As for sources... I have no idea who created mfastboot or where it came from. It's just one of those things that get's passed around the internet.
Click to expand...
Click to collapse
Well I'm happy to have the utility that works. Can thank you enough -- or the creators. Found it also on goggle code after a properly crafted search string. All this for an in-call audio problem that only worsened after I took the phone apart. Still works on speaker mode though so that's good enough -- at low volume. And I learned a few things. One interesting thing: The shell prompt got rewritten to say ${USER}@scorpion_mini/ after flashing the system.img. Pretty sure it only said android prior to re-flashing . And the getprop helper app is a new thing for me.
Feel like a kid all over again exploring this little device.

Idiots Guide (video) to installing the FULL Android!??

Is there a simple vid tutorial going on how to flash the shield with FULL android? ? The main thread on the developer section has about 120 pages but it is not idiot proof. I dont want to brick my new shield
Thanks in advance!!!

If its your 1st time flashing an android device head over to youtube and spend some time there. Once you get the idea of flashing via stock recovery/twrp come back to the full android rom thread

Ive flashed a zillion android boxes. But this is not yer average android box. How difficult would it be for someone to put up a very simple guide?
This is from the main thread explaining how to do it...
"Installation:
Put the device in fastboot mode:
Connect the Shield Tv to PC via micro usb cable
Enable usb debugging in development settings of Shield TV
In the command prompt of your PC type:
adb reboot bootloader
The bootloader must be unlocked before all others operations with the command:
fastboot oem unlock
When the bootloader is unlocked, In the command prompt type:
1) fastboot flash system system.img
2) fastboot -w
3) fastboot reboot
All others parts of the firmware can be stock for now and are already installed.
"
Talk about confusing!!!!!

lanzarote1000 said:
Talk about confusing!!!!!
Click to expand...
Click to collapse
Very confusing. I wrote it down here http://forum.xda-developers.com/showpost.php?p=64572084&postcount=1244

gnoober said:
Very confusing. I wrote it down here http://forum.xda-developers.com/showpost.php?p=64572084&postcount=1244
Click to expand...
Click to collapse
Brilliant. Thanks!!!

I didnt like it either for some reason. I've followed instructions from a million xda OP's and flashed about as many ROMs but something about the way the dev chose to introduce his ROM and flashing instructions gave me a vibe l didnt like so I havnt tried it
*edit* I remember now he casually instructs you to run a command that wipes all user data (including internal storage) without the least bit of warning about potential loss of data or reason why its necessary... or making a simple statement about not supporting dirty flashing like I've seen some devs do. Anyway, other than that, it looks all good, and a lot of people seem to be enjoying it but thats funnyness if you ask me.

If it's your first time flashing on your shield then you will need to unlock the boot loader, which will wipe your device, then install a custom recovery, then flash the system image with his fast boot commands, which includes a wipe as well as his rom is very different from the stock one. You could try a dirty flash but doubt it would work. This is all from memory. I got it working fine but missed the stock rom and went back lol
Sent from my HTC One M9 using Tapatalk

The instructions are pretty straightforward aside from the usual language barrier issues. If you can't follow them, then I would suggest not even trying to flash it. Hell if you want to cheat and have a 1click solution, just download the recovery from NVIDIA, and replace the system.img in their file with @zulu99's and follow NVIDIA's instruction... Thier batch file essentially runs the commands for you so you don't have to do all that tedious typing.

hey I have tried all the guides to root my nvidia shield tv but without any luck, could any one please make me and other noobs a step by step guide ?