Database Users

rooted. latest recovery yet cant flash.

ok so heres the deal. i bricked my last gt540 but was able to bring it to the store and swap it out.
lol so here we are on the new one and i have it rooted, latest recovery i can find 3.0.2.4...i managed to flash mur4ik's cm7 2.3.3 but now it seems as if im stuck with it. whether i try and flash from clockwork or rom manager i always get a failed attempt. once i noticed it was cause the rom wasnt signed so i toggled the option to off and still it failed. any help would be awesome.
thanks gents!

any help would be super!

try flashing roms using the fastboot method

lol it seems like a major task for me. cant seem to figure out how to do.

ive similar problem,
installed euro 2.1 build using KDZ image. recovery comes up.
If i try to restore zip from sd using update-cm-7.0.2-GT540-MUR4IK-signed.zip i keep on getting:
Installing update
assert failed: getprop("ro.product.device" == "swift" || "ro.build.product" == "swift" || "ro.product.board" == "swift" ||
E:Error in /sdcard/clockworkmod/backup/update-cm-7.0.2-GT540-MUR4IK-signed.zip
(Status 7)
Installation aborted
anyone ?

tmuehlhoff said:
ive similar problem,
installed euro 2.1 build using KDZ image. recovery comes up.
If i try to restore zip from sd using update-cm-7.0.2-GT540-MUR4IK-signed.zip i keep on getting:
Installing update
assert failed: getprop("ro.product.device" == "swift" || "ro.build.product" == "swift" || "ro.product.board" == "swift" ||
E:Error in /sdcard/clockworkmod/backup/update-cm-7.0.2-GT540-MUR4IK-signed.zip
(Status 7)
Installation aborted
anyone ?
Click to expand...
Click to collapse
i used the same method. sounds like the same issues. i think we need some help lol.

kdm212 said:
i used the same method. sounds like the same issues. i think we need some help lol.
Click to expand...
Click to collapse
ive read about different hardware used in gt540/swift types.. .maybe thats the issue here?!

so then what should we do? where did you read this stuff?

dunno- therere millions of threads out there. maybe someone feels like and gives us a hint what to do....

ok so i managed to figure out fastboot via cmd. i was overthinking it. anyway i get to the step where i need to send and write the fastboot flash boot boot.img. it sends it but fails to write to the phone.
(remote: flash write failure)
any suggestions?

Have you tried downloading the files again. Sometimes the download is corrupt which will cause a fail in the recovery. I have had it a few times myself. After downloading the file again (often from another source) the recovery completes itself succesfully.

i have tried to redownload. im actually going to bring the phone all the way back to stock and see what happens. kinda start from scratch.

Try this way go to market and Download bt file manager and seleact the update package and extract to a folder then try install zip from sD method try and rply
Sent from my GT540 using XDA Premium App

kdm212 said:
i have tried to redownload. im actually going to bring the phone all the way back to stock and see what happens. kinda start from scratch.
Click to expand...
Click to collapse
Get in emergency mode and reflash boot.img via CMD with fastboot commands and you will get the same error probably, but you just reboot it, let it boot it will work
Sent from my GT540 using XDA App

[Q] unable to update my n7 3g to android 4.2.2

when i try to upgrade my n7 3g using OTA or manual update i will give me a message
'assert failed: getprop("ro.product.device") == "tilapia" ll getprop("ro.build.product") == "tilapia" E : Error in /sdcard/0/357318e165a8.signed-nakasig-JDQ39-from JPO40D.357318e1.zip (status 7) Installation aborted.
i used 4.2.1 stock rom
locked bootloader
unroot.

Hmmm, I notice you said "unroot"
stock recovery or custom?
That assert is there to insure that it is only flashed to a tilapia/nakasig (3g) N7
The getprop values in question are being read from the *recovery*, not the installed ROM... so, the most reasonable conclusion is that you have a custom recovery or stock recovery from a grouper device installed on your (tilapia) 3g N7.
Flash the stock tilapia recovery there and try again.
This would be an unreasonable hypothesis for a never-rooted tab, but you did say "unrooted"

bftb0 said:
Hmmm, I notice you said "unroot"
stock recovery or custom?
That assert is there to insure that it is only flashed to a tilapia/nakasig (3g) N7
The getprop values in question are being read from the *recovery*, not the installed ROM... so, the most reasonable conclusion is that you have a custom recovery or stock recovery from a grouper device installed on your (tilapia) 3g N7.
Flash the stock tilapia recovery there and try again.
This would be an unreasonable hypothesis for a never-rooted tab, but you did say "unrooted"
Click to expand...
Click to collapse
Hi!
im having the same problem, Nexus 7 3G is rooted with custom recovery...
is there a way to install the 4.2.2 update with custom recovery or do i have to return to stock?
thank you!

R: [Q] unable to update my n7 3g to android 4.2.2
You are maybe using a recovery for grouper. Just flash the right tilapia recovery and all should works.
Nexus 7 3G - Tapatalk

Hum... I had this kind of problem, I guess.
I searched many threads when I rooted and unlocked my Nexus 7 3g, to avoid this "status 7" problem.
I chose Wug´s nexus toolkit, unlocked and rooted my device. After that, I installed, via toolkit, the TWRP recovery.
When I received the system update notification, my device asked me to reboot, then a screen of TWRP appeared to me. I just rebooted the system and now, without update, I don´t even get the message again.
I assume that the Wug´s toolkit flashed a grouper version of TWRP. What I have to do now ? I would like to do the things manually. Maybe flash a factory image from here with this method.
I´m very noob with this kind of thing, because I still have a old milestone 2 with a locked bootloader. The method to flash ROM in milestone 2 is quite different...
Anybody can help me ?

mouse100 said:
You are maybe using a recovery for grouper. Just flash the right tilapia recovery and all should works.
Nexus 7 3G - Tapatalk
Click to expand...
Click to collapse
thank you , ill flash it as soon as i get home and check if it works!

azfarmiera said:
when i try to upgrade my n7 3g using OTA or manual update i will give me a message
'assert failed: getprop("ro.product.device") == "tilapia" ll getprop("ro.build.product") == "tilapia" E : Error in /sdcard/0/357318e165a8.signed-nakasig-JDQ39-from JPO40D.357318e1.zip (status 7) Installation aborted.
i used 4.2.1 stock rom
locked bootloader
unroot.
Click to expand...
Click to collapse
hey there.i get the solution.i just flash stock recovery and wait until OTA update notification on phone and it will update 4.2.2.thank for your help

bisco said:
thank you , ill flash it as soon as i get home and check if it works!
Click to expand...
Click to collapse
just flashed openrecovery-twrp-2.4.1.0-tilapia.img recvery file but update still does not work

bftb0 said:
Flash the stock tilapia recovery there and try again.
Click to expand...
Click to collapse
Is just the stock recovery posted somewhere? I can't seem to find it.
Sent from my SGH-I777 using xda app-developers app

rthisp said:
Hum... I had this kind of problem, I guess.
I searched many threads when I rooted and unlocked my Nexus 7 3g, to avoid this "status 7" problem.
I chose Wug´s nexus toolkit, unlocked and rooted my device. After that, I installed, via toolkit, the TWRP recovery.
When I received the system update notification, my device asked me to reboot, then a screen of TWRP appeared to me. I just rebooted the system and now, without update, I don´t even get the message again.
I assume that the Wug´s toolkit flashed a grouper version of TWRP. What I have to do now ? I would like to do the things manually. Maybe flash a factory image from here with this method.
I´m very noob with this kind of thing, because I still have a old milestone 2 with a locked bootloader. The method to flash ROM in milestone 2 is quite different...
Anybody can help me ?
Click to expand...
Click to collapse
Found how? Same here with cwm... Chose reboot and now still on 4.2.1 and no more ota update available... Even when I check for updates.

theBeachBoy said:
Found how? Same here with cwm... Chose reboot and now still on 4.2.1 and no more ota update available... Even when I check for updates.
Click to expand...
Click to collapse
finally I found it. took so long I almost abandonned
I had to use stock recovery and adb sideload the zip file, it would not work with CWM eveb if I manually edit the script to skip that assert line, it would crash later in the modem part of the update.
Also, if you have a 3G version you need to use nakasig instead of nakasi, I have used the link from there to get the zip file: http://forum.xda-developers.com/showthread.php?t=1745781

[Q] Nexus 4 won't upgrade to 4.2.2 in any way

[Q] OTA failed and displayed dead Android saying Error! Tried to sideload the zip file using Toolkit 1.6.8 and it didn't go through. Tried to load it using TWRP and this is what I get:
Code:
Verifying current system...
assert failed: apply_patch_check("/system/build.prop". "5a778d005448ec19
E:Error in /sdcard/de8b8...zip
(Status 7)
Error flashing zip '/sdcard/de8b8...zip
I'm running rooted stock ROM, never tried anything else so I don't know how I could have messed up something.
Thanks for any ideas!

domi_niku said:
[Q] OTA failed and displayed dead Android saying Error! Tried to sideload the zip file using Toolkit 1.6.8 and it didn't go through. Tried to load it using TWRP and this is what I get:
Code:
Verifying current system...
assert failed: apply_patch_check("/system/build.prop". "5a778d005448ec19
E:Error in /sdcard/de8b8...zip
(Status 7)
Error flashing zip '/sdcard/de8b8...zip
I'm running rooted stock ROM, never tried anything else so I don't know how I could have messed up something.
Thanks for any ideas!
Click to expand...
Click to collapse
Flash a stock rom and install the OTA through adb sideload with adb and not by a toolkit, worked for me. After that reroot. Also read this thread well http://forum.xda-developers.com/showthread.php?t=2145848.

gee2012 said:
Flash a stock rom and install the OTA through adb sideload with adb and not by a toolkit, worked for me. After that reroot.
Click to expand...
Click to collapse
I'm gonna try the stock 4.2.2 ROM, thanks.
It still doesn't the answer the following question: what's wrong?

domi_niku said:
I'm gonna try the stock 4.2.2 ROM, thanks.
It still doesn't the answer the following question: what's wrong?
Click to expand...
Click to collapse
Did you try a different kernel in the past? ie Franco's kernel?

harpo1 said:
Did you try a different kernel in the past? ie Franco's kernel?
Click to expand...
Click to collapse
No, never. I just wiped the phone and installed stock 4.2.2 using the Toolkit and now it won't boot.
EDIT: I guess that's because the Toolkit doesn't support 4.2.2. Oh well just flashed it using ADB. Hope I can get all my app data back...

[Q] Secure Booting Unsuccessful; Standard issue, but confused and stuck...

So I've searched and read for about the last 4 hours, and I'm only more confused than before.
Using a Verizon VS980:
1.Took the OTA (to VS96012B) when I first got the phone
2. Rooted using ioroot script
3. installed latest twrp (2.6.3.3) using Freegee
4. Downloaded CM10.2 stable directly from Get.cm as well as appropriate GAPPS
5. Rebooted into TWRP
6. Wiped (but did not backup since I didn't care about keeping user data...did this wipe the factory OS too then?)
7. Attempted to flash CM10.2 and got the following error:
"Skipping MD5 check: no MD5 file found.
assert failed: run_program("/system/bin/loki.sh
E:Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/download/cm-10.2.0
8. Attempted to reboot into stock since CM flash had failed and got "secure booting unsuccessful" error message
Why would the CM10.2 install be failing under the above messages? And did I blow away my factory ROM? I just used the generic TWRP 2.6.3.3 "factory reset option"??
Dear lord help me. I've read so many threads, but I've ended up much more confused.
In theory, the stock ROM should still be installed since the CM10.2 flash failed, what do I need to do to A.)Be able to successfully flash the CM10.2 without getting the "error executing updater binary in zip" problem, or B.) Be able to at least boost back into stock LG image?
Thanks,
-A

Planning on using this to go back to how it shipped stock, and then re-rooting, and re-installing TWRP and taking another shot at a ROM. Can someone please tell me if this is the right direction?
http://forum.xda-developers.com/showthread.php?t=2449670

After going back to stock I would go this route if u take 12b OTA.
http://forum.xda-developers.com/showthread.php?t=2587296
Sent from Verizon logo plastered G2 bastard

Thanks for the reply! I've edited the OP for a little additional detail/clarity. I'm trying to figure out at this stage why my CM10.2 install failed first and foremost. I'd like to be able to avoid going all the way back to stock if possible?
Any suggestions on why I was getting the below message during attempting to install?
"
Attempted to flash CM10.2 and got the following error:
"Skipping MD5 check: no MD5 file found.
assert failed: run_program("/system/bin/loki.sh
E:Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/download/cm-10.2.0
"

amazonparrot said:
Thanks for the reply! I've edited the OP for a little additional detail/clarity. I'm trying to figure out at this stage why my CM10.2 install failed first and foremost. I'd like to be able to avoid going all the way back to stock if possible?
Any suggestions on why I was getting the below message during attempting to install?
"
Attempted to flash CM10.2 and got the following error:
"Skipping MD5 check: no MD5 file found.
assert failed: run_program("/system/bin/loki.sh
E:Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/download/cm-10.2.0
"
Click to expand...
Click to collapse
It seems like the recovery u flashed from freegee was not properly loki'd for the 12b firmware. It allowed u to overwrite the stock recovery but not flash any ROMs. U could try pushing the patched Loki img and recovery in the thread I posted earlier using adb. U can follow the same instructions in the thread u linked just use the updated patched files.
When u wiped prior to flashing cm10.2, if u wiped system then u have no ROM on ur device to boot into. Always make a backup just in case. That way if u have a bad download or the ROM just won't boot, u gotta plan B.
Sent from Verizon logo plastered G2 bastard

truckroot said:
It seems like the recovery u flashed from freegee was not properly loki'd for the 12b firmware. It allowed u to overwrite the stock recovery but not flash any ROMs. U could try pushing the patched Loki img and recovery in the thread I posted earlier using adb. U can follow the same instructions in the thread u linked just use the updated patched files.
When u wiped prior to flashing cm10.2, if u wiped system then u have no ROM on ur device to boot into. Always make a backup just in case. That way if u have a bad download or the ROM just won't boot, u gotta plan B.
Sent from Verizon logo plastered G2 bastard
Click to expand...
Click to collapse
If I just used the standard TWRP Wipe/factory reset, (which I did) my factory system ROM should be still there, but for whatever reason I'm unable to boot it.
I'm assuming the threads and methods you referenced will work with ADB sideload?
Thanks again

amazonparrot said:
If I just used the standard TWRP Wipe/factory reset, (which I did) my factory system ROM should be still there, but for whatever reason I'm unable to boot it.
I'm assuming the threads and methods you referenced will work with ADB sideload?
Thanks again
Click to expand...
Click to collapse
Yeah. I would try pushing the patched Loki img via adb, then try flashing the cm10.2 ROM. Otherwise u can sideload a stock ROM and flash that.
Sent from Verizon logo plastered G2 bastard

Managed to get back to stock!
Re-rooted, and used Freegee to install latest CWM ths time. Attempted to install CM10.2 again (fresh download) and it STILL gives the error:
Attempted to flash CM10.2 and got the following error:
"Skipping MD5 check: no MD5 file found.
assert failed: run_program("/system/bin/loki.sh
E:Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/download/cm-10.2.0
Why am I still unable to flash a ROM?

amazonparrot said:
Managed to get back to stock!
Re-rooted, and used Freegee to install latest CWM ths time. Attempted to install CM10.2 again (fresh download) and it STILL gives the error:
Attempted to flash CM10.2 and got the following error:
"Skipping MD5 check: no MD5 file found.
assert failed: run_program("/system/bin/loki.sh
E:Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/download/cm-10.2.0
Why am I still unable to flash a ROM?
Click to expand...
Click to collapse
Read that some are having issues using Freegee/Flashify to install a working loki'd recovery with 12b OTA. ADB seems to work best. Glad to hear u were able to get back to stock though.
Sent from Verizon logo plastered G2 bastard

I'm actually on 11A :-/
I was planning on using CM10.2 since I just want a 4.3 or 4.4 ROM thats actually stable, but maybe its just the particular ROM I'm trying? I'll try doing ADB to push a different recovery just in case.
Any recommendations on a good stable ROM?

amazonparrot said:
I'm actually on 11A :-/
I was planning on using CM10.2 since I just want a 4.3 or 4.4 ROM thats actually stable, but maybe its just the particular ROM I'm trying? I'll try doing ADB to push a different recovery just in case.
Any recommendations on a good stable ROM?
Click to expand...
Click to collapse
The unofficial cm 4.4.2 is a good one. OP has good directions on getting ROM to run perfectly with kernel settings.
If ur on 11a u should have zero issues flashing, def try a different ROM.
Sent from Verizon logo plastered G2 bastard

Same error... kinda freaking out now #FML
I am so lost and confused. Definately in over my head right now. I usually depend on the one click methods to flash, and this time I'm bricked. Same problem as post #1 on the thread. Not very familiar with adb. Is anyone with experience in this area able/willing to remote into my mac or even over the phone to help a brother out? I'm willing to compensate you for your time.
Thanks,
Vinnie

New OTA break root?

Just got a notification for OTA to 5.0.1. Anyone know if this will break root? And if it will install with CWM custom recovery?

Hello, I tried to install in my WiFi model and rooted and I got and error during the installation, so I'm waiting for the opinion of other users. ?
Sent from my SHIELD Tablet using XDA Free mobile app

I kiddy got it too, I'll wait for the zip file lol.

Ya think it is really better to install from the zip file?
Sent from my SHIELD Tablet using XDA Free mobile app

I'll be the guinea pig

I downloaded the OTA but can't find where is the ota file. Any idea where is it?
Sent from my SHIELD Tablet using XDA Free mobile app

Get an error in cwm . shucks

Does someone can post change log please?

Gilbot said:
Get an error in cwm . shucks
Click to expand...
Click to collapse
Same. My bootloader is locked and tried flashing via cwm and got error. Pls teach me how to update?
Sent from my SHIELD Tablet using XDA Free mobile app

Judge584 said:
Does someone can post change log please?
Click to expand...
Click to collapse
Android Central has the log change. It's bug fixes really.
Also, in this thread a user states that apparently only with the full 5.0.1 can you install it with CWM.
http://forum.xda-developers.com/shi...p-nvidia-shield-tablet-ota-android-5-t2982677
You will lose root and CWM after the reboot but those took about 3 minutes to get back .. easy peasy. I'm now at 5.0.1 on my shield with root and CWM.
Cheers.

Hello aegern,
deletes the full update all the data? can you give me the recovery and root attach files?
Thanks

Gilbot said:
Get an error in cwm . shucks
Click to expand...
Click to collapse
This should help. Let me know if it works:
http://forum.xda-developers.com/shield-tablet/general/5-0-1-ota-rooted-shield-tablets-dl-t2983104

d4m45cuz said:
This should help. Let me know if it works:
http://forum.xda-developers.com/shield-tablet/general/5-0-1-ota-rooted-shield-tablets-dl-t2983104
Click to expand...
Click to collapse
:crying: Does not work for me. I tried locking it again, unrooting my tablet and neither with OTA or CWM flash. Any light?

GMrMadrigal said:
:crying: Does not work for me. I tried locking it again, unrooting my tablet and neither with OTA or CWM flash. Any light?
Click to expand...
Click to collapse
So here's what I did:
Download the full OTA then reboot to CWM (assuming your rooted + recovery) and unmount system partition ( I believe all others were unmounted) and then delete system, data, cache partitions respectively. Then flash the OTA zip followed by latest supersu.
Just tested this method and I have a rooted 5.01 32GB LTE US model working flawlessly. Even managed to take out the top spot in Hwbot Prime for the Shield (woops to newb for links I see lol)

l0ud_sil3nc3 said:
So here's what I did:
Download the full OTA then reboot to CWM (assuming your rooted + recovery) and unmount system partition ( I believe all others were unmounted) and then delete system, data, cache partitions respectively. Then flash the OTA zip followed by latest supersu.
Just tested this method and I have a rooted 5.01 32GB LTE US model working flawlessly. Even managed to take out the top spot in Hwbot Prime for the Shield (woops to newb for links I see lol)
Click to expand...
Click to collapse
I really appreciate your advice but I get the same error
-- Installing: /storage/sdacrd1/lte-full-5.0.1.zip
Finding update package...
Opening update package...
Installing update...
This package is for "shieldtablet" device; this is a "ardbeg".
E:Error in /storage/sdacrd1/lte-full-5.0.1.zip
(Status 7)
Installation aborted.
I've tried with a few zip updates through in xda but nothing. I guess is because the CWM recovery image but Im not an expert on this and cant be sure if flashing the stock recovery will let me make the OTA successfully. But neither i have found the stock recovery image

GMrMadrigal said:
:crying: Does not work for me. I tried locking it again, unrooting my tablet and neither with OTA or CWM flash. Any light?
Click to expand...
Click to collapse
GMrMadrigal said:
I really appreciate your advice but I get the same error
-- Installing: /storage/sdacrd1/lte-full-5.0.1.zip
Finding update package...
Opening update package...
Installing update...
This package is for "shieldtablet" device; this is a "ardbeg".
E:Error in /storage/sdacrd1/lte-full-5.0.1.zip
(Status 7)
Installation aborted.
I've tried with a few zip updates through in xda but nothing. I guess is because the CWM recovery image but Im not an expert on this and cant be sure if flashing the stock recovery will let me make the OTA successfully. But neither i have found the stock recovery image
Click to expand...
Click to collapse
Look in this thread: [.zip] Nvidia Shield Tablet OTA Android 5.0.1, first page posted by user SeVIIn.
Use that zip file, no issues with it.

l0ud_sil3nc3 said:
Look in this thread: [.zip] Nvidia Shield Tablet OTA Android 5.0.1, first page posted by user SeVIIn.
Use that zip file, no issues with it.
Click to expand...
Click to collapse
Nice, I'm going to download it, and I'll tell if it work! :fingers-crossed:

GMrMadrigal said:
Nice, I'm going to download it, and I'll tell if it work! :fingers-crossed:
Click to expand...
Click to collapse
So, did it work for you? I've tried the file in both this link and the official update and get the same thing with both. I'm still on KK and I can't install either the 5.0 or the 5.01 updates. I get the same "this is an ardbeg" error with any update I try to flash, and I'm flashing the full files, not the incremental updates. In fact, I have two tablets (both lte) and I updated the first one to 5.0 a week ago, no problem, but the new one I just bought, I can't even though I'm using the same files (cwm and update). I'm stumped.
Bah. nm. I went back and reinstalled the recovery from here again, http://forum.xda-developers.com/shi.../recovery-cwm-recovery-nvidia-shield-t2848064. Flashed 5.01 just fine. Not sure where I got the other recovery.

dgjenkins said:
So, did it work for you? I've tried the file in both this link and the official update and get the same thing with both. I'm still on KK and I can't install either the 5.0 or the 5.01 updates. I get the same "this is an ardbeg" error with any update I try to flash, and I'm flashing the full files, not the incremental updates. In fact, I have two tablets (both lte) and I updated the first one to 5.0 a week ago, no problem, but the new one I just bought, I can't even though I'm using the same files (cwm and update). I'm stumped.
Bah. nm. I went back and reinstalled the recovery from here again, http://forum.xda-developers.com/shi.../recovery-cwm-recovery-nvidia-shield-t2848064. Flashed 5.01 just fine. Not sure where I got the other recovery.
Click to expand...
Click to collapse
Hi dgjenkins, sorry answer so late. So, answering you first, not, it did not work for me. I actually did give up, the bad was that I tried so many ways to do it that I freezed the tablet and did not start again. Well, looking out there, I found this amazing video who saved my tablet of bust it again the wall and start from the original firmware.
https://www.youtube.com/watch?v=GsMo1tPlIFU
I did intal the Minimal ADB and Fastboot
Copy the image files in to the Minimal ADB and Fasboot directory c:\Programs Files (x86)\Minimal ADB and Fastboot
Ope Minimal ADB and Fastboot
-Type: fastboot flash recovery recovery.img
-Type: fastboot flash boot boot.img
-Type: fastboot flash system system.img
-Type: fastboot flash userdata userdata.img
-Type: fastboot flash staging blob
-Type: fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb
And done . I can now install the updates from the stock firmware. Maybe I will root it again once a stable way to root the shield tablet appear out there. :cyclops:
Happy Holidays and Thanks for the interest! :good:

Nvidia updates definitely trump Android ones. These days, Google is in the habit of pretending that a nexus 5 camera bug is worthy of a new Android version (that was KitKat) or that an update is a great place to break functionality (App Ops, also with KitKat). Anything that's not a minor version with updates you know you want... Avoid on a non Nexus unless you have a great reason for it.
Manufacturers besides Google, see, they do this thing I like to call quality control. They generally release an OS that is ready for the hardware and software*. Crazy, right?
* unless that hardware is, say, the pen