Database Users

[HowTo] Update Your Transformer Without Problems

How many of you have tried updating to a new firmware and you got the yellow exclamation mark?
Well, you probably have a combination of these modifications:
Custom Kernel
ClockworkMod Recovery
Rooted
If you have any of these, this is what you should do.
First, download and run this ONLY FOR INSTALLING/UNINSTALLING STOCK/CLOCKWORKMOD RECOVERY. - Thread
Read the instructions on how to boot into APX Mode.
Backup your /data with CWM.
After you have backed up your data, you should restore the STOCK ROM of your device.
When you get an update, it /should/ complete without any errors.
DO NOT DO ANYTHING TO THE ROM AT THIS POINT.
Alright. So at this point, you should have a completely stock, updated ROM.
Here are the next steps.
DO NOT ROOT YOUR ROM. DO NOT CHANGE A KERNEL.
Boot into APX Mode.
Make a backup of the STOCK Recovery. (Download From Linked Thread If You Haven't.)
Reboot into APX Mode.
Install ClockworkMod Recovery. (Using Brk's RootKit Script.) Once again. Without Rooting. Without changing the kernel.
Update ClockworkMod Recovery to 3.2.0.1. - Thread
Make a backup of EVERYTHING. (boot, system, data, cache, sd-ext).
After the backup is complete, you can ROOT and install a custom Kernel.
When You Get A New Update: DO NOT INSTALL. DO NOT POSTPONE.
Boot into ClockworkMod Recovery.
Restore the stock Boot.
Restore the stock System.
Boot into APX.
Restore stock recovery. (Using Brk's RootKit Script.)
Now everything should be back to stock.
Your data should still be intact.
When you apply the update, it should complete without a hitch.
Complete these steps again to be ready for the next update.
Cheers.

Thanks !! This did the trick for me. Had previously un-rooted and lost the update. Couldnt get it back until I did this !

I have a question.
I used the root method mentioned above a few weeks ago and everything went perfectly. I did not install CWM, only root.
I used the Netflix hack but managed to erase the original lib file.
I received the update and got the yellow exclamation point.
Last night I used BRK's pure root method and attempted to restore boot image and recovery image hoping it would return my lost lib file. I did not attempt to unroot.
When you mention "stock rom", where do I find the stock US rom?
I have an Epic 4G and run custom roms but I think the Transformer is fine and honestly don't care about root now that Netflix and ad-hoc appear to be working. I would like to end up with a stock Transformer that receives regular updates.
Is this the method for me, or something else?
Thanks

bmcgarry67 said:
I have a question.
I used the root method mentioned above a few weeks ago and everything went perfectly. I did not install CWM, only root.
I used the Netflix hack but managed to erase the original lib file.
I received the update and got the yellow exclamation point.
Last night I used BRK's pure root method and attempted to restore boot image and recovery image hoping it would return my lost lib file. I did not attempt to unroot.
When you mention "stock rom", where do I find the stock US rom?
I have an Epic 4G and run custom roms but I think the Transformer is fine and honestly don't care about root now that Netflix and ad-hoc appear to be working. I would like to end up with a stock Transformer that receives regular updates.
Is this the method for me, or something else?
Thanks
Click to expand...
Click to collapse
You should go here: http://tabletroms.com/forums/transf...stock-3-2-recovery-roms-unbricking-tools.html
Make sure you backup your data for your applications and the internal sdcard. They will be erased.
Install the 8.4.4.5.
Then you should go here and update to the latest version they have available.
Follow the instructions for this.
http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#download
Select Android and download your firmware.
Then you should get your update working after that.
Use this guide, then restore your data using clockworkmod.

Thanks and follow up
The Dark Lestat said:
You should go here:
Make sure you backup your data for your applications and the internal sdcard. They will be erased.
Install the 8.4.4.5.
Then you should go here and update to the latest version they have available.
Follow the instructions for this.
Select Android and download your firmware.
Then you should get your update working after that.
Use this guide, then restore your data using clockworkmod.
Click to expand...
Click to collapse
I just had a couple of questions?
You mentioned updating to 8.4.4.5, them updating to 8.6.5.6.
They have the NVFlash with 8.6.5.6. Has that changed since you advised me or should I do it in 2 steps?
Do I download the Asus Rom to the transformer or download to computer, then copy to SD card to install?
Now, I just noticed that 8.6.5.9US is available from Asus. Does this change my procedure?
Thanks again

bmcgarry67 said:
I just had a couple of questions?
You mentioned updating to 8.4.4.5, them updating to 8.6.5.6.
They have the NVFlash with 8.6.5.6. Has that changed since you advised me or should I do it in 2 steps?
Do I download the Asus Rom to the transformer or download to computer, then copy to SD card to install?
Now, I just noticed that 8.6.5.9US is available from Asus. Does this change my procedure?
Thanks again
Click to expand...
Click to collapse
When I NVFlashed to 8.6.5.6, I could not receive the update.
Since I used the file from Asus to update, it enabled FOTA somehow.
Anyways, the guide is the same.
If 8.6.5.6 is available, then you can NVFlash 8.6.5.6, then download and update to 8.6.5.9

Thank you.
I NVFlashed to 8.6.5.6 and wiped everything.
The FOTA arrived immediately and updated flawlessly.
Thanks again

Is this update even worth unrooting then root again?

it does fix the issue with browser shortcuts. You no longer have to rotate the screen.

I have not played with it. But it is said to allow Netflix and adhoc without root and patches. Those were the 2 reasons that I rooted.

Why jump through all these hoops?
Step 1: Download the clockworkmod update posted.
Step 2: Flash it.

daoist said:
Why jump through all these hoops?
Step 1: Download the clockworkmod update posted.
Step 2: Flash it.
Click to expand...
Click to collapse
Because if you do that, for some reason, FOTA doesn't enable.
AND you will have to wait for a flashible zip to become available.
Not hoops.
I've already tested that route. It didn't work for me.

bmcgarry67 said:
I have not played with it. But it is said to allow Netflix and adhoc without root and patches. Those were the 2 reasons that I rooted.
Click to expand...
Click to collapse
Has this been verified?

pigskins said:
Has this been verified?
Click to expand...
Click to collapse
Verified.
Netflix and Adhoc work WITHOUT root.
No need to root for those two options.
I personally root because of Titanium Backup.
Even if I have CWM installed.

The Dark Lestat said:
Verified.
Netflix and Adhoc work WITHOUT root.
No need to root for those two options.
I personally root because of Titanium Backup.
Even if I have CWM installed.
Click to expand...
Click to collapse
TY!
Did you root after getting the update and if so, how? Did you follow the steps in this thread?

pigskins said:
TY!
Did you root after getting the update and if so, how? Did you follow the steps in this thread?
Click to expand...
Click to collapse
Yes. The thread that I posted has all the updated CWM and Root methods. You can use those to root.

The Dark Lestat said:
Because if you do that, for some reason, FOTA doesn't enable.
AND you will have to wait for a flashible zip to become available.
Not hoops.
I've already tested that route. It didn't work for me.
Click to expand...
Click to collapse
Why do you want FOTA enabled?
Why be bothered when a release that won't work (without jumping through hoops) is available?
The whole point of installing CWM is that you're going to be managing your tablet rather than letting ASUS do it. If you're going to unroot, FOTA, and reroot every time, just leave it unrooted.

I had successfully update my transformer through OTA without doing all those steps. I just had to root it again after update is done.

daoist said:
Why do you want FOTA enabled?
Why be bothered when a release that won't work (without jumping through hoops) is available?
The whole point of installing CWM is that you're going to be managing your tablet rather than letting ASUS do it. If you're going to unroot, FOTA, and reroot every time, just leave it unrooted.
Click to expand...
Click to collapse
You don't have to root to use CWM. FOTA won't work with CWM.
I use Root only for setCPU and Titanium.
I like getting the update as soon as possible. Not waiting a couple days for it.
Sei911 said:
I had successfully update my transformer through OTA without doing all those steps. I just had to root it again after update is done.
Click to expand...
Click to collapse
If you just rooted and did not make any changes to the system, then in theory, it should work. Depending on the root method.

[Q] Wont root after manual update?

I just pushed the new 4.2 update via adb,
I then tried re-rooting as I lost root in the project.
I used WugFreshs at first, which said successful. I tried root check and titanium backup which both said no root access.
I then tried mikes toolkit and chose root and install busybox, all that wen through great and said successful, so I retried Tibackup and rootchecker again, both were denied root access.
This time round, rootcheck said "System Running Slow" whilst checking for root access.
What should I do?
Re-boot into recovery and clear cache etc?
Factory reset?
Both?
For some reason superuser is installed not supersu if that makes a difference?
Any help appreciated.

Wilks3y said:
I just pushed the new 4.2 update via adb,
I then tried re-rooting as I lost root in the project.
I used WugFreshs at first, which said successful. I tried root check and titanium backup which both said no root access.
I then tried mikes toolkit and chose root and install busybox, all that wen through great and said successful, so I retried Tibackup and rootchecker again, both were denied root access.
This time round, rootcheck said "System Running Slow" whilst checking for root access.
What should I do?
Re-boot into recovery and clear cache etc?
Factory reset?
Both?
For some reason superuser is installed not supersu if that makes a difference?
Any help appreciated.
Click to expand...
Click to collapse
I apply the update by doing fresh install:
-always backup your data
Then I use wug's nexus root toolkit:
-flash stock + unroot 4.1.2 jzo54k
-flash zip stock + unroot 4.2 jop40c
-change the model type to "NAKASI: Android *.*.* Any build"
-apply root

gesitkumara said:
I apply the update by doing fresh install:
-always backup your data
Then I use wug's nexus root toolkit:
-flash stock + unroot 4.1.2 jzo54k
-flash zip stock + unroot 4.2 jop40c
-change the model type to "NAKASI: Android *.*.* Any build"
-apply root
Click to expand...
Click to collapse
I applied the update over the top of 4.1.2, wiped cache and then restarted.
I then used Wug's toolkit to root, which didn't work.
So I tried Mikes, which also didnt work.
Both report the Root as being succesful, but they arent.
If I change the model to all types on Wug's, would that make a difference?
Is it worth trying a manual root?

I use the Google Nexus 7 Toolkit which was great in fixing the problems after upgrade. Flashing the previous version bootloader (I think that is what it was) solved the root problem. The hints and guidance in this application are great and have always solved my problems. No offence meant to Wug here, I just find the other application suits me better.
Sent using Tapatalk 2

Waxwrong said:
I use the Google Nexus 7 Toolkit which was great in fixing the problems after upgrade. Flashing the previous version bootloader (I think that is what it was) solved the root problem. The hints and guidance in this application are great and have always solved my problems. No offence meant to Wug here, I just find the other application suits me better.
Sent using Tapatalk 2
Click to expand...
Click to collapse
As already said, both Toolkits have been attempted and both report that its rooted, but my device tells me otherwize, as do Titanium Backup.
Can someone just give me a step by step for what I should do to gain Root again?!

Wilks3y said:
As already said, both Toolkits have been attempted and both report that its rooted, but my device tells me otherwize, as do Titanium Backup.
Can someone just give me a step by step for what I should do to gain Root again?!
Click to expand...
Click to collapse
Hi, are you using the fully updated version of Toolkit (updated to include the 4.2 stuff. When I did mine I was told to go ahead but if it didn't work the next step was to flash the 4.1 bootloader? as it was compatible with 4.2
The root with the 4.2 bootloader didn't give me root so I flashed the 4.1 bootloader and rooted again. This was successful for me. The Toolkit application gives you step by step instructions as you request as long as it is updated to do 4.2 and follow the advice you should have no problem.
I don't think you can do the full updates in the application unless you are a donater. If I remember correctly you cannot update the application unless you use the donater version. The update for 4.2 came out at almost the same time as 4.2 was being pushed to devices.
You sound cluey enough to know you must use USB debugging but many users don't realise this or the tapping on the build trick to get the developer options available so you can select USB debugging.
Sent using Tapatalk 2

Waxwrong said:
Hi, are you using the fully updated version of Toolkit (updated to include the 4.2 stuff. When I did mine I was told to go ahead but if it didn't work the next step was to flash the 4.1 bootloader? as it was compatible with 4.2
The root with the 4.2 bootloader didn't give me root so I flashed the 4.1 bootloader and rooted again. This was successful for me. The Toolkit application gives you step by step instructions as you request as long as it is updated to do 4.2 and follow the advice you should have no problem.
I don't think you can do the full updates in the application unless you are a donater. If I remember correctly you cannot update the application donate version. The update for 4.2 came out at almost the same time as 4.2 was being pushed to devices.
You sound cluey enough to know you must use USB debugging but many users don't realise this or the tapping on the build trick to get the developer options available so you can select USB debugging.
Sent using Tapatalk 2
Click to expand...
Click to collapse
Hey mate, thanks for your reply !
I downloaded both ToolKits yesterday, so I'm guessing they are the newly updated ones?
Yes my tablet has usb debugging enabled, and is put into the Camera Mode.
I will have another go tonight, and try a different way, including using the "All Models" choice you mentioned.
If this doens't work, whereabouts in the ToolKit(Wug's) if the option to downgrade HBOOT in order to try the Root method you attempted which was successful.
Again, thanks mate !

Wilks3y said:
Hey mate, thanks for your reply !
I downloaded both ToolKits yesterday, so I'm guessing they are the newly updated ones?
Yes my tablet has usb debugging enabled, and is put into the Camera Mode.
I will have another go tonight, and try a different way, including using the "All Models" choice you mentioned.
If this doens't work, whereabouts in the ToolKit(Wug's) if the option to downgrade HBOOT in order to try the Root method you attempted which was successful.
Again, thanks mate !
Click to expand...
Click to collapse
I don't use Rug's Toolkit but Mike's Toolkit (only because it is easier to follow and use because it tells you what to do at all stages). You can see if it is updated by checking whether it has functions for 4.2 - I always use it for flashing the latest roms as well as the unlocking, root, recovery, etc, all of which the Toolkit guides you through. It even downloads the roms for you.
My only question is why did you put it in camera mode, change it back.
Sent using Tapatalk 2

Just install the 4.2 that is already Stock rooted, de-odexed apps.
Install the ROM as already Stock rooted, de-odexed apps.
Here is the link for the download: http://www.scottsroms.com/downloads.php?do=file&id=288
Thanks to Scott's post http://forum.xda-developers.com/showthread.php?t=1991157

[Q] Lost Root after OTA update. How to properly re-root without messing the system?

Hello everyone,
I noticed that this is a common problem and I realize just not that I shouldn't have just updated without informing myself.
Anyway, I checked and the root seems to be gone (checked with Root Checker, although the SU app is still there [but not working]).
I checked the fastbook and it says 'unlocked', which is good, I don't have to lose data.
How do I re-root properly?
I am using OS X at the moment and I have access to adb but, if needed, I can access a Windows computer again and use Nexus Root Toolkit again (that's what I used the first time I rooted).
I have CWM-SuperSU-v0.98.zip and recovery-clockwork-6.0.1.9-manta.img.
I checked the bootloader and it says 'no command' but it still has:
- reboot system now
- apply update from ADB
- wipe data...
- wipe cache...
Thanks in advance for any help

First thing - Nearly always you will lose root after applying an OTA - at least lately so that's not really a big deal.
Second - Get and always use the Latest version of root zip from chainfire: http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip
Or you can also just apply SuperSU from google play and you will prompted to reboot to update binaries etc. after you apply the OTA.
His blog on latest version: https://plus.google.com/+Chainfire/posts/QhrEdeJ3nqQ

I got the same problem.
I solved it by just by downgrading and upgrading back to the latest version of Cyanogenmod.
lg Darcade

I have the same problem...
I have the same problem, I have installed the 4.4.3 OTA and now SuperSU stopped working.
Any advice?

Easily got my root back using Wugfresh toolkit.

Only the paid for version of SuperSU - "Pro" will attempt to keep root after an OTA update. It worked perfectly for me on a 5, 7 and 10.

[Lemmy] said:
I have the same problem, I have installed the 4.4.3 OTA and now SuperSU stopped working.
Any advice?
Click to expand...
Click to collapse
Don`t use toolkits, just boot into TWRP in fastboot and reflash the latest superSU.zip and you`re rooted.

gee2012 said:
Don`t use toolkits, just boot into TWRP in fastboot and reflash the latest superSU.zip and you`re rooted.
Click to expand...
Click to collapse
thats what I did by now, just with CWM instead of TWRP.

[Lemmy] said:
thats what I did by now, just with CWM instead of TWRP.
Click to expand...
Click to collapse
Well done mate , toolkits suck and you have no control over them. Flashing with adb gives you full control and you learn something

gee2012 said:
Well done mate , toolkits suck and you have no control over them. Flashing with adb gives you full control and you learn something
Click to expand...
Click to collapse
...after having to go through this over and over again with every single update I'm starting to think that having root is definitely not worth the pain.

If you switch to TWRP using its built in SuperSU install makes re-rooting a breeze.
Sent from my SM-T800 using XDA Premium HD app

[ROOT] 23.0.1.A.0.167 [LOCKED BL] No recovery needed

Hello,
I just wanted to share how I have rooted my device today, and it was way easier than the methods I have been reading about so far.
My device: Xperia Z2 , C6543.
How I did it:
1- I updated my flashtool to the latest version, downloaded the 7.1.2.A.0.314 ftf for my region and flashed like instructed in the post. (Note that If you don't have flashtool installed, you have to go inside it's drivers folder and install the Z2 driver so it can communicate to the phone).
http://forum.xda-developers.com/showthread.php?t=2759934
2- After the downgrade to the 7.1.2.A.0.314 version mentioned above, I went to the flashtool menu (My 65XX -> Root -> Force towelroot)
When prompted to, I have choosen the SuperSU option.
Then the towelroot app showed in the phone's screen, I've tapped on "make it rain" and let it run.
After that the phone restarted and it was rooted.
3. Okay, now that the 7.1.2.A.0.314 is rooted, an OTA update notification showed up to update to the same version (lol). Well, I just let it update, and the root was there (I confirmed by restoring some data in titanium backup).
4. After that, another OTA update showed up to update to 23.0.1.A.0.167. Again, I let it download and install.
Well, that's what it took for me to root my z2 in it's latest version with only one downgrade and no manual adb commands, no manual rootkit downloads, pretty similar to the way I've always rooted my ZQ (R.I.P - it drowned lol).
The credits are due to the hard-working people who made all the mentioned tools, I am only doing my part by sharing an easier method than what i've seen around. Feel free to share your toughts.
Laters!

Sorry to be noob! Will it break anything like camera x reality or anything? And for warranty, can I claim it by just unrooting it(it's in the su) ?

Did not break anything for me. Now I can use foldermount and transfer heavy apps to the external sd. Wonderful. As for the warranty, since there is no recovery installed and no bootloader unlocked, it is as easy as doing the step 1 in the procedure described. It will flash the unrooted system back.

But ist same method, if u use this or this tool.

This post doesnt deserve an original development section!

thanks. I will follow this guide as i had root, upgraded and lost it. But i've have been itching to flash stuff lol.

But ist same method, if u use this or this tool.
Click to expand...
Click to collapse
I am not sure I understand what you mean, but if you are talking about the xperiarootkit compared to the "force towelroot" from flashtool, I checked the scripts in advance and they seem to be the same thing yes. The only shortcut to what I did was not having to flash recovery, and creating customized ftf, etc.

This post doesnt deserve an original development section!
Click to expand...
Click to collapse
I am sorry you feel that way man, that comment was a great way to add value to the conversation, thank you.

remydlc said:
thanks. I will follow this guide as i had root, upgraded and lost it. But i've have been itching to flash stuff lol.
Click to expand...
Click to collapse
Did you tried ota survival in Supersu?

rjshrjndrn said:
Did you tried ota survival in Supersu?
Click to expand...
Click to collapse
not before applying the OTA. Perhaps that would have helped. I have the app installed, but it says the binaries are not installed, to consult the forums for re-rooting

remydlc said:
not before applying the OTA. Perhaps that would have helped. I have the app installed, but it says the binaries are not installed, to consult the forums for re-rooting
Click to expand...
Click to collapse
I think you have to do all the stuff one again and root device. Then check the option for its root survival and do ota updates. I think you'll be fine with the updates.

Question, /System RW? (don't confuse it with a TA Restore, as it could only be restoring to the /Data partition).

Moscow Desire said:
Question, /System RW? (don't confuse it with a TA Restore, as it could only be restoring to the /Data partition).
Click to expand...
Click to collapse
I doubt you'll have system RW access as sony ric should still be running, but if root is working fine flashing nut's recovery should fix this easily.

root achieved and kept
Nice one thanks for the info worked well and updated to .167 ota and kept root.

Going to give this a try. Thanks

Thanks for the info, OP.
I used flashtool to downgrade my D6503 to .55, tried to use towelroot, no luck. used the CVE root exploit and got root, but after that update center failed the verification to .314.
Your method works, so cheers!

Will the Phone be wiped during this root method

ecolupo said:
Will the Phone be wiped during this root method
Click to expand...
Click to collapse
flashtool will wipe your phone unless you unselect data partition (not recommended). The rooting part is non-destructive so no that part won't your phone.

ptmaniac said:
I doubt you'll have system RW access as sony ric should still be running, but if root is working fine flashing nut's recovery should fix this easily.
Click to expand...
Click to collapse
Tried to install nut's recovery with supersu option but all the apks in the script could not be written into system folder. Also could not install xposed installer. May have to downgrade again and avoid this method
update: no need to downgrade again. sony_ric prevents r/w to system folder even with root, so I just used ric killer by forty two: http://forum.xda-developers.com/xperia-z2/general/4-4-4-sony-ric-killer-t2953141
afterward I was able to install xposed installer via normal method.

Thank you for the tutorial. It worked fine for me.
What will happen if I do a factory reset via settings-menu? Will root be gone? Do I have to downgrade again or can I install SuperSU to get root back?
Sent from my D6503 using XDA Free mobile app

Nvidia SHIELD Portable Root

Hi everyone!
This morning I woke up to find my SHIELD with the so waited notification of Lollipop update. I'm really happy to finally have lollipop running on my device, but sadly I found a problem after the update. I was trying to re-root my device, but neither the SHIELD RAM tool or Root Genius could do the trick. But I didn't gave up, I searched in Google any way to root my SHIELD with the still fresh update, and found that the Kinguser app can root it without trouble.
You just need to download the apk, install it on your SHIELD and open it.
Btw, the old recovery isn't working anymore, you can flash it with the RAM tool, but the device will reflash the stock recovery.

Downloaded and it's says shield portable android 5.1 not supported...
Sent from my SM-N910P using Tapatalk

kenmacker said:
Downloaded and it's says shield portable android 5.1 not supported...
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
You need to turn on USB Debugging, and then run the app.

USB debugging is now turned on but it says root access is unavailable
Sent from my SM-N910P using Tapatalk

work great
thanks

Old recovery is working for me - it's CWM 6.0.4.4.
I had to flash it twice, first time it was reflashed to stock.
PS: TWRP 2.8.5.0 (unofficial) is working too.

kenmacker said:
USB debugging is now turned on but it says root access is unavailable
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Look if you have your SHILD's bootloader unlocked, that may be causing the problem.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.

I wanted a full restore/clean version of the ROM without waiting for the factory image to be updated.
I flashed the 101 Factory Image from here. I notice that 103 is there now so just skip this step and flash that now.
I noticed that after flashing the latest SuperSU the device would never boot.
So I had to use KingRoot but for me the apk method never worked so I went with the desktop version.
To get Root I went to KingRoot's XDA page and downloaded the Desktop version.
When running the program it is all in Chinese but is thankfully idiot proof with its one big button on it. Just make sure that USB Debugging is turned on and wait for it to finish, it will reboot during the process.
KingRoot installs its own version of a Super User advisor so it will prompt when something needs root access and for most people that would be enough but I prefer SuperSU, Thankfully KingRoot has a set of instructions, follow these to the letter and it will guide you through removing KingRoot and installing SuperSU. During that process you will get a lot of errors saying that files are no longer there, just ignore them, that means the initial uninstall got the files.
Once I was able to ensure that SuperSU and Root where staying after a reboot I re-installed TWRP (for some reason I couldn't get CWM to stick after a reboot but oh well I like TWRP more >_>) and made a backup of my stock rooted device.
I then went to this page and grabbed the Unofficial Xposed 5.1 .zip and went to this page and grabbed the Xposed Installer.
Rebooted and waited for the App Cache to re-build as the Xposed framework nukes it then installed my mods as normal.
Took a little bit longer than normal to update but oh well, Everything is working smoothly and I'm happy with it.

Rooted my Shield two times wth CWM without problems.

astuermer said:
Old recovery is working for me - it's CWM 6.0.4.4.
I had to flash it twice, first time it was reflashed to stock.
PS: TWRP 2.8.5.0 (unofficial) is working too.
Click to expand...
Click to collapse
Which cmw did you use and where did you get it? I tried using flashify with twrp and it says boot failed when booting into recover.
astuermer said:
Rooted my Shield two times wth CWM without problems.
Click to expand...
Click to collapse

Give me a few mins. I will upload my Recovery package...
Here we go. I've flashed and rooted my SHIELD successfully after OTA upgrade - and today again after flashing the clean 103 factory Image.
SHIELD-Portable-Recoveries.zip
Update: I've attached a ZIP file with 4 different recoveries. Simply execute the Batch file I've included (if you're on Windows) and select 1-4.
stock KitKat recovery (from update 101)
stock Lollipop recovery (from update 103)
ClockworkMod recovery (CWM) 6.0.4.4 (somewhere from XDA, but couldn't find the link)
TWRP recovery 2.8.5.0 (from here)

From @Steel01 The TWRP located here may give people problems and we should be using the one in the MultiROM TWRP located here.
Source here.
EDIT: I will test tonight and see what happens when you image with the factory image and just install MultiROM's TWRP and then try SuperSU's latest BETA.
I was trying to use the other TWRP before and could never boot which is why I did the KingRoot method.

If you wanted to change Kinguser to SuperSU all you have to do is download any "Control Rotation App" and set it as Portrait Mode (if it didn't work make sure that the Nvidia Shield Portable is in a sitting position and flip it , It should work , If not try installing other apps), Install "Super-Sume" , Then touch the big blue button , After that wait until the process is done , You should see SuperSU, In the other hand Kinguser has already vanished (I'm not sure if SuperSU will open automatically or not), Install the binary, Reboot, Done.
Have a nice day