Database Users

[Q] Long time no Flash :D

Hey guys,
Its been a very long time since I flashed a rom on my N7. I was busy with the damn uni but now that summer is here I can play with my N7
Let me make this quick, I have unlocked the N7 using the tool kit long time ago and Im not sure if it still exists on my PC
Im currently running - CM10 4.1.2
Modle - GT-I9000
-Bootloader-
HW VERSION - ER3
BOOTLOADER VERSION - 3.34
UNLOCKED
Recovery - i think CMW
Now I want to update to 4.2.2
Can I just flash a ROM with 4.2.2 or I have to do something with bootloader?
And btw just after going to the bootloader today which I didn't see long time ago the N7 didn't boot when I choose start then I held the power button till it rest and it worked but now a random reboot occurred :|

You need to update your bootloader to 4.18 or you may encounter problems. Also flash a new recovery (I recommend TWRP). From there you can just flash cyanogenmod 10.1.0 rc5 + gapps to upgrade (dirty flash).

Westervoort said:
You need to update your bootloader to 4.18 or you may encounter problems. Also flash a new recovery (I recommend TWRP). From there you can just flash cyanogenmod 10.1.0 rc5 + gapps to upgrade (dirty flash).
Click to expand...
Click to collapse
should I use the kit to update the bootloader? will it erase every thing? I want a new clean 4.2.2

mr.dj26 said:
should I use the kit to update the bootloader? will it erase every thing? I want a new clean 4.2.2
Click to expand...
Click to collapse
Just download the latest firmware from your device from Google (or look on this forum for the latest bootloader file). Extract all the contents in your fastboot folder. Open a terminal there and type:
fastboot flash bootloader name-of-bootloader.img
fastboot reboot-bootloader
Extra double check that you flash the correct and appropriate bootloader for your device. A corrupt bootloader might hard brick your device. I prefer to do this myself so therefore I don't use toolkits.
This will not erase anything and your bootloader remains unlocked.
Flashing a new recovery is done by:
fastboot flash recovery name-of-recovery.img
From there you can start wiping everything again and start flashing new roms. TWRP supports usb-otg, so you can use it to wipe the internal memory and install cyanogenmod 10.1.0 (android 4.2.2) from a usb stick. Way better then stock.
If you just want the official stock firmware, or for troubleshooting, then I recommend the sticky for manually flashing the official Google Android firmware.

Westervoort said:
Just download the latest firmware from your device from Google (or look on this forum for the latest bootloader file). Extract all the contents in your fastboot folder. Open a terminal there and type:
fastboot flash bootloader name-of-bootloader.img
fastboot reboot-bootloader
Extra double check that you flash the correct and appropriate bootloader for your device. A corrupt bootloader might hard brick your device. I prefer to do this myself so therefore I don't use toolkits.
This will not erase anything and your bootloader remains unlocked.
Flashing a new recovery is done by:
fastboot flash recovery name-of-recovery.img
From there you can start wiping everything again and start flashing new roms. TWRP supports usb-otg, so you can use it to wipe the internal memory and install cyanogenmod 10.1.0 (android 4.2.2) from a usb stick. Way better then stock.
If you just want the official stock firmware, or for troubleshooting, then I recommend the sticky for manually flashing the official Google Android firmware.
Click to expand...
Click to collapse
Hey there,
thank for the help.
I saw a vid on youtube, he just flashed the zip from recovery and it updated the bootloader.
Anyway, one last thing, can I use this " [BOOTLOADER] [4.2.2] JDQ39 4.18 Now Has Flash able Zip! "
other there are variants versions?

mr.dj26 said:
Hey there,
thank for the help.
I saw a vid on youtube, he just flashed the zip from recovery and it updated the bootloader.
Anyway, one last thing, can I use this " [BOOTLOADER] [4.2.2] JDQ39 4.18 Now Has Flash able Zip! "
other there are variants versions?
Click to expand...
Click to collapse
should work, check the latest comments in the thread to check whether it has been successful
whichever method you use, make sure to verify the md5 of the bootloader.img or zip before you flash it. pretty sure a corrupt bootloader will end up in a brick!

eddiehk6 said:
should work, check the latest comments in the thread to check whether it has been successful
whichever method you use, make sure to verify the md5 of the bootloader.img or zip before you flash it. pretty sure a corrupt bootloader will end up in a brick!
Click to expand...
Click to collapse
okay m8
thank you all for being very helpful ^^

Great im on 4.18
now ill get in to recovery and erase every thing then ill flash a new recovery and a new rom

Stock,unlocked & rooted,updating to 4.3

Probably there is a thread about my problem, but I really need your help.I have the official 4.2.2,(I have removed some system apps like Google current etc), unlocked and rooted with custom recovery(twrp).I recently have received the notice for the ota update.I want to update to 4.3 , hopefully without losing root, but if there is no other way,I don't have problem.so I would really appreciate a step-by-step guide.thank you all in advanced and forgive my bad English
Στάλθηκε από το Nexus 7 μου χρησιμοποιώντας Tapatalk 2

steliosamos said:
Probably there is a thread about my problem, but I really need your help.I have the official 4.2.2,(I have removed some system apps like Google current etc), unlocked and rooted with custom recovery(twrp).I recently have received the notice for the ota update.I want to update to 4.3 , hopefully without losing root, but if there is no other way,I don't have problem.so I would really appreciate a step-by-step guide.thank you all in advanced and forgive my bad English
Στάλθηκε από το Nexus 7 μου χρησιμοποιώντας Tapatalk 2
Click to expand...
Click to collapse
Hi, steliosamos....
If you've removed any system apps (like Currents), then there's a good chance the OTA will fail, as it expects to find them in order to update them. It does this by running a checksum test on all files in system. If even one fails that test (either due to modification or it's absence), the OTA will abort, with no changes made.
So you need to restore any missing system apps first... but this might be tricky. It largely depends on the extent of your modifications to system... what apps you've removed, and other changes you may have made.
If they are considerable, and you can't either remember them in order to reverse them, or you can't remove those modifications for other reasons, you may be left with little alternative but to fastboot flash the full factory image for your device... available here, https://developers.google.com/android/nexus/images.
Anyway... upon successful updating via the OTA, you will likely loose TWRP... and you will certainly have to re-root again. This is because root under JellyBean 4.3 works completely differently than 4.2.2. So, you will loose root (and even if, by some unlikely miracle you didn't, it wouldn't work anyway).
Unlike under pre-4.3 versions of JellyBean, where root was just a 'static' su binary dropped into /system/xbin, root is now a 'dynamic' process, called a daemon, specifically, 'sudaemon'.
--------------------------------
You can the get UPDATE-SuperSU-v1.51.zip from here.
Fastboot flash TWRP (for 'Grouper'/WiFi or 'Tilapia'/3G, make sure you get the correct one for your device)... and then using TWRP, flash the SuperSU root package.
Good luck.
Rgrds,
Ged.

Yes,Ged,i really cant remember which system apps i have removed,so as far i understand the safer way is flashing the factory image and returning to official 4.2.2.Then i can update to 4.3 OTA and later to flash again the twrp and root it one more time.Do i understand right?The first time when i unlocked my nexus and root it,i used sdk tools.I am thinking this time to use nexus root toolkit,hoping that it will be more safe and quick.Do you agree?Thanx either way for your responce and help

steliosamos said:
Yes,Ged,i really cant remember which system apps i have removed,so as far i understand the safer way is flashing the factory image and returning to official 4.2.2.Then i can update to 4.3 OTA and later to flash again the twrp and root it one more time.Do i understand right?The first time when i unlocked my nexus and root it,i used sdk tools.I am thinking this time to use nexus root toolkit,hoping that it will be more safe and quick.Do you agree?Thanx either way for your responce and help
Click to expand...
Click to collapse
Hi, steliosamos...
Yeah... you pretty much have it right. There are two ways you could go...
1) Flash 4.3 straight off.
2) Flash 4.2.2 and then take the 4.3 OTA update.
Practically, there is no difference regarding the end result... you'll have a Nexus 7 running Jellybean 4.3.
But the second way is safer... the reason why revolves around the bootloader.
Jellybean 4.3 will update the bootloader from v4.18 to v4.23. Theoretically, there should be no difference in how this is accomplished... but updating via fastboot, flashes the bootloader directly to the bootloader partition... which is an inherently risky procedure. And if anything goes wrong (bad USB connection, some glitch with your PC, etc) you have a dead Nexus 7, generally known as a hardbrick... from which there is no known recovery.
However, updating via an OTA update, the bootloader is updated differently.
As I explained previously, an OTA will run a checksum on files in system to ensure everything is present and correct (no modifications and/or absences). The OTA then 'patches' them, meaning it updates them. The last thing the OTA does is it drops a file called BOOTLOADER.RAW into a temporary holding partition called USP/Staging. Upon automatic reboot after the OTA has completed, this new bootloader is then copied to the bootloader partition proper, presumably after running a similar checksum to compare it with the old(current) bootloader... and it inherits the crypto-signed data that the old bootloader holds and is unique to your specific device. This seems to me a safer way of upgrading the bootloader, than fastboot flashing it directly.
You mention in your post, you might use a toolkit. Well, I've never used one - so I'm unable to give advice on their use. And personally, I don't recommend them. With toolkits, you relinquish control on how a factory image is flashed. With fastboot you have complete control (you can 'pick' and 'mix' which elements you want to flash.. eg., boot.img, system.img, etc), and you also have greater transparency.
Now, coming back to your specific case...
Here's what I would do. (The following assumes you're using Windows and have a WiFi only Nexus 7).
Download the factory image for Jellybean 4.2.2 for your device from here.
Unzip it accordingly...
Edit the flash-all.bat to remove the line fastboot flash bootloader bootloader-grouper-4.18.img. There's no point in needlessly re-flashing a bootloader that you already have (with the risks that entails).
So, after editing, you should have the following in the flash-all.bat file...
Code:
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot reboot-bootloader
ping -n 10 127.0.0.1 >nul
fastboot -w update image-nakasi-jdq39.zip
echo Press any key to exit...
pause >nul
exit
You can of course, just type all of this in manually (with the exception of the ping command, which just pauses everything while the bootloader reboots).
From a fully shut down condition, boot your Nexus 7 into the bootloader (in fastboot mode), by pressing VOL DOWN and hold, whilst holding, press the POWER BUTTON. Open a command prompt window on whichever folder you have downloaded and unzipped the factory image files to.
First type....
Code:
fastboot devices
You should expect to see something like this...
Code:
015dxz2oxxxxx fastboot
Your device's unique serial ID followed by the word 'fastboot'. This is essentially diagnostic, and confirms you have a working fastboot connection. If you don't see this, you likely have a driver problem which needs to be attended to before you can proceed.
You're now ready to run the flash-all.bat file or manually type in the commands it contains.
----------------------------------------
Another possibility/option that occurs to me (although I've never tried it myself)...
You might able to get away with just fastboot flashing the system.img file (extract it from image-nakasi-jdq39.zip), and flash as follows...
Code:
fastboot erase system
fastboot flash system system.img
As I say, I've never tried this, so I've no idea if it will work... but it seems a logically easier way of restoring all your system apps with minimal hassle.
One last point about system.img... in my experience, it can (but not always) be notoriously fussy/difficult (a bloody pain in the ar#*!:' actually) when 'sending'. If this happens, just disconnect the USB lead from your PC, reconnect to another port, and reboot the bootloader and try again. It should take no more than 2 minutes to go across... any longer than 3 minutes and you've probably lost your fastboot connection. Once you see 'Writing system...', you know it's worked. You can check the integrity of your fastboot connection at any time by opening another command prompt window and typing fastboot devices. If you DON'T see a serial number, then the fastboot connection has died.
----------------------------------------
Right... all things being equal... you should now be be running stock JellyBean 4.2.2 and ready to accept the 4.3 OTA update (assuming a WiFi connection)... and which you will get pestered with every time you turn on the device.
Accept it... the update should go smoothly (although with tech, one can never be sure until after the event - (...and the new bootloader v4.23, safely ensconced in the bootloader partition).
The bootloader being still unlocked, it's now a relatively trivial matter to fastboot flash TWRP (or CWM if you prefer), and then root via Chainfire.
Good luck.
Rgrds,
Ged.

i got a question here
i hav a nexus 7 3g 32gb. was running stock rom rooted with twrp recovery and few days bak i got the 4.3 update and i chose to update and after the update it was stuck at the boot logo never switched on. i tried factory reset also but it never worked probably something went bad in the OTA update or it happened cuz i was rooted with unlocked bootloader and custom recovery i donno.. anyways i had no choice i used the N-cry toolkit for nexus ( http://forum.xda-developers.com/showthread.php?t=2171401 ) and flashed the factory image and got it bak to life and with the same toolkit i rooted it n flashed custom recovery so right now i hav a nexus 7 running android 4.3 stock rooted with custom rom n unlocked bootloader. everything was fine until i started getting a notification for 4.3 update again even though i hav 4.3 on the device. i havent done much to it other than rooting and having a custom rom so my system apps are intact so updating with the OTA shouldnt be a problem for me. but i wanted to know what caused the problem the first time! i dont want my tablet to die again after the update!
Does OTA update mess up if we are rooted with unlocked boot loaders and custom recoveries??
and as far as i know OTA update will remove root so i can just reroot after the update? probably by using the toolkit or is there any better way? and even twrp recovery... u gave the link for the file but how do i flash the recovery? i know how to flash the root files via twrp but how to get twrp.

forgot to attach the screenshots

GedBlake said:
Yeah... you pretty much have it right. There are two ways you could go...
1) Flash 4.3 straight off.
2) Flash 4.2.2 and then take the 4.3 OTA update...
Click to expand...
Click to collapse
Thank you for this excellently-written tutorial. I learned something about bootloaders that I didn't know.
Sent from my Nexus 7 using xda app-developers app

Update fails - want to flash custom rom - need some advice

Now here's the situation:
I'm still on an older ROM version (4.2.1 - see attachment)
A while ago my tablet told me there was an update. I wanted to get it, it downloads but it always fail to apply the update.
What I've done to the device so far is that I've used motochopper to root the device and got rid of some ASUS apps.
So since it refuses to update, I've decided to unlock it, flash a custom recovery and get myself a custom rom.
But I've read a lot about people bricking their devices and I doubt it'll be as easy as it was on Nexus 4 and Nexus 7 - so I need some advice on how exactly to do it.
Recently I found the thread that enables us some sort of nvflash although being on JellyBean. They were talking about a specific version of bootloader and I'm not certain if I have this bootloader since I'm on an older JellyBean version. Of course I would like to use this bricksafe as well - just in case
Can someone lead me to a guide or instruct me how to do it? I don't want to brick this device
Thx in advance

l33ch0r said:
Now here's the situation:
I'm still on an older ROM version (4.2.1 - see attachment)
A while ago my tablet told me there was an update. I wanted to get it, it downloads but it always fail to apply the update.
What I've done to the device so far is that I've used motochopper to root the device and got rid of some ASUS apps.
So since it refuses to update, I've decided to unlock it, flash a custom recovery and get myself a custom rom.
But I've read a lot about people bricking their devices and I doubt it'll be as easy as it was on Nexus 4 and Nexus 7 - so I need some advice on how exactly to do it.
Recently I found the thread that enables us some sort of nvflash although being on JellyBean. They were talking about a specific version of bootloader and I'm not certain if I have this bootloader since I'm on an older JellyBean version. Of course I would like to use this bricksafe as well - just in case
Can someone lead me to a guide or instruct me how to do it? I don't want to brick this device
Thx in advance
Click to expand...
Click to collapse
This THREAD has all the info you need to do NVFlash. It's based on 10.6.1.15 something bootloader which I believe is the same as the latest Asus official. If you're on 4.2 rom, you can flash the flatline img. and generate the necessary files from there. Once that done, you can use either the provided CWM or the latest 4.2 TWRP to flash any compatible custom rom (4.3). Have fun.

graphdarnell said:
This THREAD has all the info you need to do NVFlash. It's based on 10.6.1.15 something bootloader which I believe is the same as the latest Asus official. If you're on 4.2 rom, you can flash the flatline img. and generate the necessary files from there. Once that done, you can use either the provided CWM or the latest 4.2 TWRP to flash any compatible custom rom (4.3). Have fun.
Click to expand...
Click to collapse
First of: thanks for your reply
Guide says something about bootloader 10.6.1.15.3 - I still have an even older one (10.6.1.8...) - will it still work?

l33ch0r said:
First of: thanks for your reply
Guide says something about bootloader 10.6.1.15.3 - I still have an even older one (10.6.1.8...) - will it still work?
Click to expand...
Click to collapse
Yes, that version will work because it is on the 4.2 bootloader.
Sent from my TF300T using xda app-developers app

Only works on unlocked device?
Ok I'll try like this
These are the steps I would do: (I pray someone to look over these steps and correct me if I'm wrong )
1.) Go to asus site and download unlock_v8 and run it so to unlock my tablet.
2.) I go to androidroot.mobi and download flatline_tf300.img and nvflash-tools-win32.zip (win32? Hope that does not stand for 32-bit and hope it will work on 64-bit)
3.) I reboot my device into Fastboot (don't know exactly what that means "Please note that for transformer tablets the fastboot command might require the option "-i 0x0b05"" - at this stage the device is already connected to the pc and just in case it's not in fastboot I should run this command?)
4.) I use cmd.exe to type in these commands. In which directory? In the directory where I unzip the files from nvflash-tools-win32.zip? The guide is not too specific on that.
5.) I type in "$ fastboot flash recovery flatline_device.img" (I know for device I use tf300) which will flash the recovery.
6.) I reboot my device (let android boot?) and reboot again into recovery. (power + vol down?)
7.) I select "Advanced - Wheelie" and Step 1: Flash AndroidRoot BL and find myself with a custom bootloader.
8.) It says the device will power off. Automatically? However, I boot into android and after that reboot again into recovery mode.
9.) I choose Step 2 which will generate wheelie blobs
10.) I follow the on screen prompt to retrieve my blobs (anyone has a screenshot of that? Or is it self-expalantory?)
All this time the device is connected to pc via usb?
11.) Now I reboot my tablet into APX mode - after Step 10: am I still in recovery or booted to Android?
12.) If my tablet is recognized I type "$ wheelie --blob blob.bin" into cmd
13.) Then I will type in the commands to obtain the backups
Still got a few questions though. The device is connected to PC throughout this whole procedure, right? Where to start cmd (do I have to put the files from nvflash-tools into a specific folder from where I start cmd.exe?)
And after this procedure is done do I need to flash anything else? Or will I be then equipped with a working recovery that allows me to flash custom roms?
Thanks in advance for anyone who's taking time to answer my maybe uninformed questions but I'm kind of having troubles following the guide

[OTA] 5.0.2 XT1032 Retail US

https://yadi.sk/d/v93-GFXngmcbq

Hi ,
Can i restore stock US retail 4.4.4 and update this OTA.
thanks

eugineprakash said:
Hi ,
Can i restore stock US retail 4.4.4 and update this OTA.
thanks
Click to expand...
Click to collapse
Yes thats how it usually works!

Are there any issues with upgrade?
AgentChaos said:
Yes thats how it usually works!
Click to expand...
Click to collapse
Are there any issues with upgrade?bcos iam currently in cm12.1 my bootloader version 41.19
I am planing to restore 4.4.4 us retail without downgrade my bootloader after that i am going upgrade from OTA in above thread.
Are there any issues with upgrade?Please guide me if i wrong.
Thanks,

eugineprakash said:
Are there any issues with upgrade?bcos iam currently in cm12.1 my bootloader version 41.19
I am planing to restore 4.4.4 us retail without downgrade my bootloader after that i am going upgrade from OTA in above thread.
Are there any issues with upgrade?Please guide me if i wrong.
Thanks,
Click to expand...
Click to collapse
I have been unable to install the update. Was with custom recovery and root and tried to install it and failed. Did factory reset, install stock recovery, download again the OTA from phone an try to install it and did not work.
Used the guide to go back to the stock firmware (though I already had it)
Try to install it using stock recovery, threw and error. (books.apk blabla).
Don't know what problems could yo be facing but man, this has been tough.
EDIT:
Just figured it out! The problem was exactly that I was already using the stock ROM and deleted some system APKs.
After trying going back to the really stock one once again (first I did not flash system images) it is installing correctly!
Btw this is my mirror for those who prefer using MEGA servers.
https://mega.co.nz/#!qJIE0SAY!u5-ezdk4o9OWfEKWVAJtW1KKQrV82NhiG1-myqlwOJ4

working confirm Thanks
Joandvg6 said:
I have been unable to install the update. Was with custom recovery and root and tried to install it and failed. Did factory reset, install stock recovery, download again the OTA from phone an try to install it and did not work.
Used the guide to go back to the stock firmware (though I already had it)
Try to install it using stock recovery, threw and error. (books.apk blabla).
Don't know what problems could yo be facing but man, this has been tough.
EDIT:
Just figured it out! The problem was exactly that I was already using the stock ROM and deleted some system APKs.
After trying going back to the really stock one once again (first I did not flash system images) it is installing correctly!
Btw this is my mirror for those who prefer using MEGA servers.
http s:/ / mega . co . nz/ #!qJIE0SAY!u5-ezdk4o9OWfEKWVAJtW1KKQrV82NhiG1-myqlwOJ4
Click to expand...
Click to collapse
working confirm Thanks

Where can I get the stock 4.4 so I can upgrade? I need stock recovery too.

I have problems to update too. XT1032, Retail US. As a first information, I have KK 4.4.4
I managed to download the update from my mobile (zipfile Blur_Version.210.12.61.falcon_umts.Retail.en.US, I already transferred to my PC thanks to Root Explorer), but when I go to "install now" and reboot, trying to install from zip file, pops a message from my recovery (PhilzTouch) Error Status 7. My phone is rooted by SU v2.46
So, what are the exactly step-by-step guide. I will appreciate that. Greetings from Chile

tifossi88 said:
I have problems to update too. XT1032, Retail US. As a first information, I have KK 4.4.4
I managed to download the update from my mobile (zipfile Blur_Version.210.12.61.falcon_umts.Retail.en.US, I already transferred to my PC thanks to Root Explorer), but when I go to "install now" and reboot, trying to install from zip file, pops a message from my recovery (PhilzTouch) Error Status 7. My phone is rooted by SU v2.46
So, what are the exactly step-by-step guide. I will appreciate that. Greetings from Chile
Click to expand...
Click to collapse
Change your recovery por el Stock Recovery for Kitkat 4.4.4

newellj79 said:
Where can I get the stock 4.4 so I can upgrade? I need stock recovery too.
Click to expand...
Click to collapse
This is the 4.4.4 Retail US (Last Build released)
https://mega.co.nz/#!ZIxQGJSJ!dnHim2zF3vDIenrvw24NeTDAeneA8m5BEidoD6hz4_k
That's the one I flashed following the guide to flash stock firmware in this forum and then updated with the OTA I posted before (I suppose the one of the topic is the same)

Finally, it's out!

kykemejia said:
Change your recovery por el Stock Recovery for Kitkat 4.4.4
Click to expand...
Click to collapse
Followed your steps:
- Flashed my phone (XT1032) with Retail US 4.4.4 Stock (RETAIL_XT1032_4.4.4_KXB21.14-L1.61_cid9_CFC.xml) using CMD, fastboot, typing list of files, etc.
- Updated some Motorola apps. Noticed Super SU is already included and installed by default, no way to uninstall it.
- Downloaded to my computer the OTA file (Blur_Version.210.12.61.falcon_umts.Retail.en.US), then moved OTA file to SD Card
- Turn off mobile
. Reboot in stock recovery, with the robot and the exclamation sign.
- Try to apply update from SD card with the file previously loaded on it (Blur_Version.210.12.61.falcon_umts.Retail.en.US)
- At verifying update package, update stops popping a message. The message in yellow is:
Package expects build fingerprint of motorola/falcon_retuglb/falcon_umts:4.4.4/KXB21.14-L1.61/62:user/release-keys or motorola/falcon_retuglb/falcon_umts:5.0.2/LXB22.99-36/35: user/release-keys; this device has motorola/falcon_retuglb/falcon_umts:4.4.2/KXB
Installation aborted.
Click to expand...
Click to collapse
What should I do in that case? Feel free to answer me in spanish for PM.

Is this any different from the February Canada release?

tifossi88 said:
Followed your steps:
- Flashed my phone (XT1032) with Retail US 4.4.4 Stock (RETAIL_XT1032_4.4.4_KXB21.14-L1.61_cid9_CFC.xml) using CMD, fastboot, typing list of files, etc.
- Updated some Motorola apps. Noticed Super SU is already included and installed by default, no way to uninstall it.
- Downloaded to my computer the OTA file (Blur_Version.210.12.61.falcon_umts.Retail.en.US), then moved OTA file to SD Card
- Turn off mobile
. Reboot in stock recovery, with the robot and the exclamation sign.
- Try to apply update from SD card with the file previously loaded on it (Blur_Version.210.12.61.falcon_umts.Retail.en.US)
- At verifying update package, update stops popping a message. The message in yellow is:
What should I do in that case? Feel free to answer me in spanish for PM.
Click to expand...
Click to collapse
In the SU menu you can find a way to delete the root, but I don't think that is causing the error.
Can you please tell me the version of recovery your phone have? You may have installed a kit kat 4.4.2 recovery or one with a different build number and that's causing the error.
IKXB21.14-L1.61
In the recovery menu, you should see the .61. I got the same problem as you and was using .32.
Did full factory reset, and installed stock again (w/o updating anything at all), when I checked the recovery, it was .61 and it updated perfectly.
In case you are really sure you got the actual last kitkat update firmware, you can try to extract the recovery.img and flash it using moto tool,
(rename it to StockKitkatrecovery.img and replace the one it brings with this one)

Joandvg6 said:
In the SU menu you can find a way to delete the root, but I don't think that is causing the error.
Can you please tell me the version of recovery your phone have? You may have installed a kit kat 4.4.2 recovery or one with a different build number and that's causing the error.
IKXB21.14-L1.61
In the recovery menu, you should see the .61. I got the same problem as you and was using .32.
Did full factory reset, and installed stock again (w/o updating anything at all), when I checked the recovery, it was .61 and it updated perfectly.
In case you are really sure you got the actual last kitkat update firmware, you can try to extract the recovery.img and flash it using moto tool,
(rename it to StockKitkatrecovery.img and replace the one it brings with this one)
Click to expand...
Click to collapse
I solved my problem by myself, thanks anyway. The issue for me, was updating some apps once in 4.4.4. You should not to do it.
Explanation for dummies, as me, in order to get Lollipop 5.0.2:
1) Flash your phone (XT1032) with Retail US 4.4.4 Stock (RETAIL_XT1032_4.4.4_KXB21.14-L1.61_cid9_CFC.xml), as it follows:
A) Extract the Retail US 444. Stock zip file (475 MB)
B) Download this file too: (1,5 MB) https://www.dropbox.com/s/nlbrn71wfqyup4u/mfastboot-v2.zip?dl=0 , and unzip it inside the same folder as you extracted Retail US Stock zip file. All files together in the same path.
C) Put your phone on fastboot (turn off, and then press Vol-and Power 3 secs, and release both buttons). Connect your phone to USB port.
D) Inside the folder containing all all these files, press **** + right click and choose "open file command", and a CMD window will open.
E) Once in CMD window, execute one by one:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
F) After reboot, unplug phone from USB port.
G) Done, you have now Stock Retail US 4.4.4 installed on your phone, Turn it on and set all things in order to go to home screen. ​
2)Once in the main screen , don't update your apps, no matter if they are even from Google or Motorola, don't do it
3) Download to your PC the OTA file (372 MB) Blur_Version.210.12.61.falcon_umts.Retail.en.US
4) Connect again your phone to USB port , and move OTA file to your phone SD Card
5) Once done previous step, go to Stock Recovery Mode. It is:
A)Turn Off your phone
B) Press Power and Vol- for 3 secs, then release
C) Select with vol- recovery option, and confirm it with vol+ button
D) Android Robot with exclamation sign will show up on the screen
E) Press vol+ and vol- for 5 secs, then press power once and release all the 3 buttons at the same time
F) Recovery Stock will appear you now.​
6) Apply update from SD card with the file previously loaded on it (Blur_Version.210.12.61.falcon_umts.Retail.en.US). Select OTA file on "apply update from zip file".
7) Process will take up to 10-15 minutes aproximately. Voilá, you will have Lollipop 5.0.2 on your RetailUS mobile.
Hope it will be useful for dummies, like me. Thanks.
Greetings from Chile.

Perfect
I had same issue and after all these steps my phone updated perfectly.
Many thanks.:good:

Really great help. Many thanks :victory:

Can anyone give me the link of IKXB21.14-L1.61 recovery?
Anyways, I downloaded and now uploading only the IKXB21.14-L1.61 recovery.
Link of IKXB21.14-L1.61 Recovery

eugineprakash said:
Are there any issues with upgrade?bcos iam currently in cm12.1 my bootloader version 41.19
I am planing to restore 4.4.4 us retail without downgrade my bootloader after that i am going upgrade from OTA in above thread.
Are there any issues with upgrade?Please guide me if i wrong.
Thanks,
Click to expand...
Click to collapse
You cannot downgrade the 41.19 bootloader to the 41.13. If you try to do that you WILL hardbrick your phone. However you can downgrade from Lollipop to Kitkat 4.4.4 (I know because I am on the 41.19 bootloader and was on cm 12.1 but restored to 4.4.4 successfully).
You have to flash the firmware for your phone except for the gpt.bin and motoboot.img. Flash all the other files in the firmware for your phone without those two and you should be fine.
xt1028 Moto G

I'll never flash stuffs with Motorola recovery! Today I did a factory reset with the stock recovery and damn! it deleted all my files in the internal SD! IT would have never happened if I would have factory reset with TWRP!
I'll wait for lost101's zip!

[Complete Guide] SHIELD Tablet K1 Root, Custom Rom and Xposed Framework

Hello Guys,
At first a little background story:
I bought the Tablet 3 Month ago. I have got the Update to Android 6.0 in January and unfortunately, I applied it.
So If you don't want to apply a custom rom do not update to 6.0, because 5.1.1 is much better.
I am not responsible if anything goes wrong.
Ok, so let's get started:
At first you must install Minimal ADB and Fastboot on your PC/Laptop/Mac.
Windows: https://forum.xda-developers.com/showthread.php?t=2588979
Linux/Mac: http://rootmygalaxy.net/install-adb-and-fastboot-on-mac-or-linux/
Here is the link for all OSs: http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
Before you can Root or flash a Custom Rom you must flash the recovery:
You will need:
-Nvidia Family Drivers(Extract it in a folder of your choice): http://nvidiashieldzone.com/files/shieldtv/shieldfamilydriver.zip not working anymore, official link:
http://developer.download.nvidia.com/mobile/shield/SHIELD_Family_WHQL_USB_driver_201801.zip
-As many of you are experiencing problems with my previously mentioned TWRP 2.8.7.3 version I am replacing the link with the official TWRP Shield Tablet Download Site. Just take the newest stable version: https://dl.twrp.me/shieldtablet/ (Put the file into the ADB+Fastboot Folder)
-TWRP 2.8.7.3 Recovery(Put the file into the ADB+Fastboot Folder): Download URL: https://www.androidfilehost.com/?fid=24269982087009777
Developer Post: http://forum.xda-developers.com/shi...recovery-twrp-2-8-7-0-touch-recovery-t3257172
Install the Drivers
Connect your Tablet to your PC
Windows:
Open your Device Manager
If there Is a device with a yellow ! klick on it and update the Drivers Manually(select the Folder where you extracted the Family Divers)
Linux:
You don't need any drivers
(For every fastboot command in ADB+Fastboot you will need a "sudo" in front of it...)
Mac:
You also don't need any drivers
(For every fastboot command in ADB+Fastboot you will need a "./" in front of it...)
Flash Recovery
1. Open Minimal ADB and Fastboot
2. Type in
Code:
adb devices
if you get a long term of numbers and letters your drivers are correctly installed, If this command does not bring up a device, check your cable connection and/or update your drivers again.
3. Now you must enable developer options on your SHIELD Tablet K1
3.1 Go to your Setting, scroll all the way down and choose Info(or similar)
3.2 Tap seven times on the Build Number
3.3 Now go back and now there is a new menu point Developer Options
3.4 Open them and Enable USB Debugging
4. Now type
Code:
adb reboot bootloader
EDIT: 4.1 To enable the fastboot protocol, you must select "Fastboot mode" on the Tablet. After that type
Code:
fastboot devices
in order to check if fastboot is enabled.
5. Before you can do anything you must unlock the Bootloader
5.1 Type in
Code:
fastboot oem unlock
5.2 Follow the Instructions on the Terminal(On your tablet: press the volume down button and then the power button)
6. Now you are ready to flash the recovery
6.1 Type in
Code:
fastboot flash recovery twrp-x.x.x-x-shieldtablet.img
6.2 Wait until it is finished then navigate with the volume buttons through the Menu on your Tablet and choose the option recovery mod with you power button
7. You are now in a custom Recovery on this point you must decide what you want to do:
-Do you only want to root your Device
-Or do you want to install a custom rom
Custom Rom
If you want to be on the safe side you should consider wiping the /data partition (Troubleshoot section at the end of the Post)
1. You can access your tablet from your PC
2. Now move your Custom rom to your internal or SD Card Storage
2.1 Download your custom rom of your choice.
2.1.1 Cyanogenmod 12.1 (Android 5.1.1) and BlissPop v4.0.3 https://www.androidfilehost.com/?w=files&flid=150249
2.1.2 Cyanogenmod 13.0 (Android 6.0) https://androidfilehost.com/?w=files&flid=27600&sort_by=date&sort_dir=DESC
2.1.3 Nvidia Shield Tablet Resurrection ROM (Android 6.x) https://androidfilehost.com/?w=files&flid=60681&sort_by=date&sort_dir=DESC
2.1.4 BlissPop
2.2 Download Google Apps (Gapps) (ARM Device)
2.2.1 Android 5.1 http://opengapps.org/?api=5.1&variant=stock
2.2.2 Android 6.0 http://opengapps.org/?api=6.0&variant=nano
2.3 Download Nvidia Apps (You still need to install Nvidia Shield HUB from the Play Store)http://forum.xda-developers.com/shield-tablet/development/shield-apps-cyanogenmod-12-t3070116
3. In TWRP click on Backup and Swipe to Back Up
3.1 Now go to Wipe. For a dirty flash you will only need to wipe the Dalvik and Cache for a full wipe select Dalvik, System, Data, Cache
4. After it has finished Click on Install and choose the .zip of your Custom Rom
4.1 To install the Google Apps click on Add More Zips and select the GApps zip
4.2 And again click on Add More Zips and select nvsystemservices.zip
4.3 now you can Swipe to Confirm Flash
Root
Download the Latest Stabel SuperSU file: http://download.chainfire.eu/supersu-stable and copy it to the internal or SD Card Storage
For Android 7.0 (Nougat) the SuperSU r4 2.78 version is confirmed working.
1. Open Minimal ADB and Fastboot
2. Type in
Code:
adb reboot recovery
to enter the recovery mode
3. In TWRP click on Backup and Swipe to Back Up
4. After it has finished Click on Install and choose the UPDATE-SuperSU-v2.65-20151226141550.zip (or similar) and Swipe to Confirm Flash
5. Restart you Tablet and now a new App SuperSU is Installed
Xposed Framework
Download the Xposed Framework Zip file, take the newest version:
(The Shield Quad Core has a 32 bit arm architecture, so you need the framework for arm)
SDK21 for Android 5.0: http://dl-xda.xposed.info/framework/sdk21/arm/
SDK22 for Android 5.1: http://dl-xda.xposed.info/framework/sdk22/arm/
SDK23 for Android 6.0: http://dl-xda.xposed.info/framework/sdk23/arm/
and the apk: https://forum.xda-developers.com/attachment.php?attachmentid=3921508&d=1477916609
and move them to you Tablet.
Developer Thread (for the uninstaller): https://forum.xda-developers.com/showthread.php?t=3034811
Go to Recovery with Root
1. Now that you have root you don't need you PC anymore. Go to the Play store and download Quick Boot
2. Open Quick Boot and klick on Recovery
3. Allow Root rights and the Tablet should boot into recovery
Go to Recovery without Root
1. Shut down your Tablet
2. Press and hold the Vol down button and the Power button until the Bootloader screen appears
3. Navigate with the volume buttons through the Menu on your Tablet and choose the option recovery mod with you power button
Install Xposed Framework
1. In the TWRP Recovery (Optionally you can make a Backup) select Install and choose the xposed-v80-sdk22-arm.zip file
2. When you get an Error let me know
3. Now Restart you Tablet and install the .apk file normally
4. In the App Press Framework and now there should be a green writing saying: Xposed Framework version 80 is active
5. Here is a list of very useful programs for the Xposed Framework: http://forum.xda-developers.com/android/general/best-xposed-modules-android-t3103027
Please Leave a post if you are getting errors or something isn't clearly explained! And if I could help you, consider giving me a Thanks
Troubleshoot
If you are stuck in a Bootloop:
Without data loss(e.g. when you installed Xposed framework zip and its stuck in a bootloop)
1. flash the stock rom boot image BUT ONLY IF YOU DONT USE A CUSTOM ROM (it will probably loose root). go to https://developer.nvidia.com/gameworksdownload#?search=SHIELD Tablet K1&tx=$additional,shield and download the latest NVIDIA SHIELD Tablet K1 Recovery OS Image
2. Unpack the zip file and flash it to your Tablet
Code:
fastboot flash boot boot.img
If something went wrong while flashing a custom rom (after that you will need to flash the custom/stock rom again)
wipe the /data partition. It could be encrypted from the previous rom. Be aware that you need to reinstall the rom, therefore loose all your data. Troubleshot guide by agentbob123
-Toby
Credits:
@xsquid mac support
@agentbob123 suggestion to mention to wipe the /data partition as a solution for being stuck in a bootloop
@champs777 suggested the newest TWRP
@grävling mentioned importance of waiting until the recovery flash is finished

Toby9 said:
Hello Guys,
At first a litte background story:
I bought the Tablet 3 Month ago. I have got the Update to Android 6.0 in January and unfortunately i applied it.
So If you don't want to apply a custom rom do not update to 6.0, because 5.1.1 is much better.
Ok, so let's get started:
I am not responsible if anything goes wrong.
At first you must install Minimal ADB and Fastboot on your PC/Laptop/Mac.
Here is the link for all OSs: http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
Before you can Root or flash a Custom Rom you must flash the recovery:
You will need:
-Nvidia Family Drivers(Extract it in a folder of you choice): http://nvidiashieldzone.com/files/shieldtv/shieldfamilydriver.zip
-TWRP 2.8.7.3 Recovery(Put the file into the ADB+Fastboot Folder):
Download URL: https://www.androidfilehost.com/?fid=24269982087009777
Developer Post: http://forum.xda-developers.com/shi...recovery-twrp-2-8-7-0-touch-recovery-t3257172
Install the Drivers
Connect your Tablet to your PC
Windows:
Open your Device Manager
If there Is a device with a yellow ! klick on it and update the Drivers Manually(select the Folder where you extracted the Family Divers)
Linux:
You dont need any drivers
(For every fastboot command in ADB+Fastboot you will need a sudo in front of it...)
Mac:
2016/02/16 Please leave a post if you how to do this
1. Open Minimal ADB and Fastboot
2. Type in
Code:
adb devices
if you get a long term of numbers and letters your drivers are correctly installen, If this command does not bring up a device, check your cable connection and/or update your drivers again.
3. Now you must enable developer options on your SHIELD Tablet K1
3.1 Go to your Setting, scroll all the way down and choose Info(or similar)
3.2 Tap seven times on the Build Number
3.3 Now go back and now there is a new menu point Developer Options
3.4 Open them and Enable USB Debugging
4. Now type
Code:
adb reboot bootloader
5. Before you can do anyting you must unlock the Bootloader
5.1 Type in
Code:
fastboot oem unlock
5.2 Follow the Instructions on the Terminal(On your tablet: press the volume down button and then the power button)
6. No you are ready to flash the recovery
6.1 Type in
Code:
fastboot flash recovery twrp-2.8.7.3-shieldtablet.img
6.2 Wait until it is finished then move with the volume buttons through the Menu on your Tablet an choose the option recovery mod with you power button
7. You are now in a custom Recovery on this point you must decide what you want to do:
-Do you only want to root your Device
-Or do you want to install a cutom rom
Custom Rom
1. You can access your tablet on your pc
2. Now move your Custom rom to your internal or SD Card Storage
2.1 Download your custom rom of your choice. I decided to use Cyanogenmod 12.1 (Android 5.1.1) http://forum.xda-developers.com/shi...-cyanogenmod-12-shield-tablet-lte-na-t3055043
2.2 Download Google Apps (Gapps) (ARM Device) http://opengapps.org/?api=5.1&variant=stock
2.3 Download Nvidia Apps (You still need to install Nvidia Shield HUB from the Play Store)http://forum.xda-developers.com/shield-tablet/development/shield-apps-cyanogenmod-12-t3070116
3. In TWRP click on Backup and Swipe to Back Up
4. After it has finished Click on Install and choose the .zip of your Custom Rom
4.1 To install the Google Apps click on Add More Zips an select the GApps zip
4.2 And again click on Add More Zips and select nvsystemservices.zip
4.3 now you can Swipe to Confirm Flash
Root
Download the Latest Stabel SuperSU file: http://download.chainfire.eu/supersu-stable and copy it to the internal or SD Card Storage
1. Open Minimal ADB and Fastboot
2. Type in
Code:
adb reboot recovery
to enter the recovery mode
3. In TWRP click on Backup and Swipe to Back Up
4. After it has finished Click on Install and choose the UPDATE-SuperSU-v2.65-20151226141550.zip (or similar) and Swipe to Confirm Flash
5. Restart you Tablet and now a new App SuperSU is Installen
Please Leave a post if you are getting errors or someting isn't clearly explaned!
-Toby
Click to expand...
Click to collapse
My tablet just keeps rebooting to the lock screen whenever I try to go to recovery mode... Somehow twrp doesn't stick... It did when I was on Lollipop. I have already tried to flash the recovery, do a full reboot before trying to get in twrp but without success.

On mac
You dont need any drivers
(For every fastboot command in ADB+Fastboot you will need a ./ in front of it...)
example being ./fastboot oem unlock

xsquid said:
On mac
You dont need any drivers
(For every fastboot command in ADB+Fastboot you will need a ./ in front of it...)
example being ./fastboot oem unlock
Click to expand...
Click to collapse
Thank you I added this in guide

nielsscholte said:
My tablet just keeps rebooting to the lock screen whenever I try to go to recovery mode... Somehow twrp doesn't stick... It did when I was on Lollipop. I have already tried to flash the recovery, do a full reboot before trying to get in twrp but without success.
Click to expand...
Click to collapse
Try other TWRP versions like 2.8.7.0 or 2.8.7.1 i think the 3.0.0.0 is for Andoid 6.0 devices so if you are currently in the newest version of the Android OS try this one out
The 3.0 versionof TWRP was unstabel on my device so you should flash it wipe the storage and flash one of the older ones

nielsscholte said:
My tablet just keeps rebooting to the lock screen whenever I try to go to recovery mode... Somehow twrp doesn't stick... It did when I was on Lollipop. I have already tried to flash the recovery, do a full reboot before trying to get in twrp but without success.
Click to expand...
Click to collapse
3.0.0.0 wasn't out yet when I did mine but it was doing the same thing and this worked perfectly:
fards said:
Try deleting recoveryonboot.p in /system
Click to expand...
Click to collapse
Credit to fards.

xsquid said:
3.0.0.0 wasn't out yet when I did mine but it was doing the same thing and this worked perfectly:
Credit to fards.
Click to expand...
Click to collapse
How can I remove this file without root ?

SonicDBZFan07 said:
How can I remove this file without root ?
Click to expand...
Click to collapse
Try your normal command line for flashing recovery except change flash to boot. It doesn't flash it, just boots to it.
In other words, if you are using:
1. Fastboot Flash recovery recoveryname.img
Do instead:
2. Fastboot boot recovery recoveryname.img
While in recovery (make sure the supersu zip is on the sd card or wherever you normally flash files from first) flash supersu. You should now be rooted but without a recovery.
Go then to delete the file and then reboot, flash the recovery as normal (#1), reboot and then it should be good to go. It was for me.

rooted device no need to unlock bootloader it will unlock for ittself
just go to playstore and dowload twrp manager
choose the name of your device
and choose one of the two versions available
for shield tablet the version 3.0.0.0 doesnt work well it spilts the screen but wthe other version Works great
the link is twrpmanager on play.google
this way you dont need to connect your tablet to your pc

Great work!

Thank you for the awesome guide. Besides deleting the TegraOTA apk, is there any other app/service that I should disable to prevent OTA updates?

Followed the guide after screwing my device up with official firmware. Thanks for nothing Nvidia, why are you offering OTA that cause the device to stop working correctly.
Nothing happened other than appearing to boot itself to the "powered by android" (kernel) screen over and over.
Held down power + volume UP ...
And it factory reset itself.
Somehow.
Did I mention that Nvidia is a terrible company?
Edit: Fixed using TWRP v3.0.0 - this guide should be updated to reflect this particuarly as people who screw their device up after trusting Nvidia OTA MM will be using it.

diji1 said:
Followed the guide after screwing my device up with official firmware. Thanks for nothing Nvidia, why are you offering OTA that cause the device to stop working correctly.
Nothing happened other than appearing to boot itself to the "powered by android" (kernel) screen over and over.
Held down power + volume UP ...
And it factory reset itself.
Somehow.
Did I mention that Nvidia is a terrible company?
Edit: Fixed using TWRP v3.0.0 - this guide should be updated to reflect this particuarly as people who screw their device up after trusting Nvidia OTA MM will be using it.
Click to expand...
Click to collapse
I'm sorry that you had that problem but this guide is a general guide and not an screw nvidia (besides they are awesom giving us a really good tablet for 200 Buck, but jea?) guide. TWRP v3.0.0 has his bugs so generally when you have finished deleting the stock rom you should flash TWRP 2.8.7.3 works the most stabel.

Trafalgar Square said:
Great work!
Click to expand...
Click to collapse
Thanks, i appreciate that

Add TWRP to M image (Shield 1.1)
Folks,
Just received Nvidia Shield K1 and OTA immediately upgraded it to M (Shield 1.1) and I unlocked bootloader no problem. However when I go to flash or temp boot twrp 2.x or 3.x it flashes OK, but when I reboot (either via fastboot or hard off/start to recovery manually) it appears it is overwriting the recovery partition and it just boots normally.
Is there a limitation to flashing twrp bootloader in M, and do I have to downgrade to L to flash recovery partition?
I seem to be happy w/ stock (limited stick time), I just want to root at this point and install my favs. Once I get this running will supersu pro preserve root, or do I need to turn off nvidia OTA process.
Also I see optimization for chrome, does this do anything X1 optimizations)?
Thanks

psychic99 said:
Folks,
Just received Nvidia Shield K1 and OTA immediately upgraded it to M (Shield 1.1) and I unlocked bootloader no problem. However when I go to flash or temp boot twrp 2.x or 3.x it flashes OK, but when I reboot (either via fastboot or hard off/start to recovery manually) it appears it is overwriting the recovery partition and it just boots normally.
Is there a limitation to flashing twrp bootloader in M, and do I have to downgrade to L to flash recovery partition?
I seem to be happy w/ stock (limited stick time), I just want to root at this point and install my favs. Once I get this running will supersu pro preserve root, or do I need to turn off nvidia OTA process.
Also I see optimization for chrome, does this do anything X1 optimizations)?
Thanks
Click to expand...
Click to collapse
After you flash twrp reboot to recovery. I may be wrong, but I think the stock ROM overwrites the custom recovery at reboot. If you reboot to twrp first after flash, twrp will disable this.
Sent from my SHIELD Tablet K1 using Tapatalk

Rooting
Hi everyone,
Yesterday got my new Nvidia Shield Tegra K1 and upon using it I noticed it's a great tablet for it's price range and will do my job easier while flying my Phantom 4. To be honest it's seems very stable and solid but was thinking about rooting it. I have some questions regarding the process wince I haven't rooted anything since my HTC Fire, log time ago that was. What are the benefits of rooting this device ? Will I still be able to update the Shield with its official updates ? Will I be able to roll back to an unrooted tablet should I need too ? I wasn't planning on flashing a custom rom but if I'll do what are the pros and cons of doing so ? I know that maybe searching this forum I would find all the answers needed but since there is so much information and threads I'm lost as from were to start from.
Would be nice to guide me about how to properly root my device with all the necessary links. My tab is running on Android 6.0.
I thank you so much guys for the hard work you all do in providing such information. I know it takes a lot of time and patience.

I just got a Shield K1. I like it a lot but I wanted to root it. Then I saw how confusing it is to distinguish between it and the previous model. My guess is whatever is out there that says Shield Tablet means the old one not the K1. I also updated mine to MM cause I'm using and 128GB micro sd card for internal storage. I guess I'll just have to wait until more support comes out for this tablet such as a stable TWRP 3.0 Recovery and the ability to gain root access and custom ROMs like CM 13.

do you recommed to install all OTAs before install custom recovery and custom roms or is it better to install twrp-2.8.7.1 out of the box and then go for the custom stuff ?

I would install all updates to get the latest bootloader. Do not install twrp 2.8.7.1. Install the official 3.0.x from the official site.