Database Users

[UPDATE] CWM flashable ASUS update for ICS -- updated US, TW and WW version

As it says the update for ASUS ICS, but CWM flashable.
*WARNING* If you are rooted, you will need OTA rootkeeper from Market to flash this patch, or flash superuser after rebooting at least once. Currently US and WW ROMs only.
--If someone has an update from another version (CN, etc.) that they want to use, PM me with a link to the file and I can build/edit a script for that too and add it in--
You should be on an odexed stock ROM (rooted of-course) in order for this to work. If you are on a custom ROM, don't bother, it won't work for you. You will need to wait for the dev of your ROM to make a patch or upgrade.
I set this up to only flash the kernal and the patches. Recovery will not be effected. This is confirmed working for me.
The US version -- http://www.mediafire.com/?3aa16qy7sh4t9m4
The WW version -- credit to Lizard -- http://www.mediafire.com/?nw4zgwvl3yug0tw
The TW version -- thanks to wai43 for the files -- http://www.mediafire.com/download.php?cfq6d5lug4q4sd8
I will not be responsible if you brick your tablet. This patch worked fine for me, but may not work for others.

If I'm on stock rooted ics... Should I full wipe? Or just wipe cache and flash over? Thanks
Sent from my Transformer TF101 using Tapatalk

Ep3n3wp said:
If I'm on stock rooted ics... Should I full wipe? Or just wipe cache and flash over? Thanks
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
I didn't wipe anything. It worked fine for me. It works just like a normal update. You may need to be sure to have all the factory installed files though. I did the update from a full stock, rooted ROM. Worked great.

You sir are awesome. Worked perfectly.
For those like mE that edited thier system.
1. I flashed ics full over my set up to restore it without losing my settings.
2. Root keeper to keep root.
3. Flashed this update.
4. Used root keeper to restore root.
5. Profit????

tweaked said:
You sir are awesome. Worked perfectly.
For those like mE that edited thier system.
1. I flashed ics full over my set up to restore it without losing my settings.
2. Root keeper to keep root.
3. Flashed this update.
4. Used root keeper to restore root.
5. Profit????
Click to expand...
Click to collapse
Honestly, I don't know if we can profit from this... lol, but thanks is just fine. I've been dabbling in this crap for years, but I had to go back to the drawing board to get that script to work right. I hope that ASUS has their crap together and don't release a bunch of patches over the next few months, that would suck for all the devs. It is supposed to have some benefits, but I've been playing with this for a few hours and haven't seen anything amazing yet... I'm working on some thing based on this and will release soon.
BTW, for those with random reboot issues, I have yet to have experienced that -- since the original update. Anyway, just my 2 cents.
sent from my ASUS Transformer running modded ICS using Tapatalk

Sharpe351 said:
Honestly, I don't know if we can profit from this... lol, but thanks is just fine. I've been dabbling in this crap for years, but I had to go back to the drawing board to get that script to work right. I hope that ASUS has their crap together and don't release a bunch of patches over the next few months, that would suck for all the devs. It is supposed to have some benefits, but I've been playing with this for a few hours and haven't seen anything amazing yet... I'm working on some thing based on this and will release soon.
BTW, for those with random reboot issues, I have yet to have experienced that -- since the original update. Anyway, just my 2 cents.
sent from my ASUS Transformer running modded ICS using Tapatalk
Click to expand...
Click to collapse
I didn't have the reboot error either. I wasn't even going to install the update. But since you made it easy....

Thanks for the uneventful update.
I HAVE experienced RR on ICS; will see what happens.
The poll in the other thread does not lead me to believe that this update fixes all the problems that lead to random reboots.
Anyway, thanks.
Btw, I tried to capture the update blob but after I renamed it, it disappeared from the /cache
I was just curious as to what you did to the update to defang it.
Is removing the recovery enough?
Does it also carry a bootloader update which you also have to remove?

feisty_noodle said:
Thanks for the uneventful update.
I HAVE experienced RR on ICS; will see what happens.
The poll in the other thread does not lead me to believe that this update fixes all the problems that lead to random reboots.
Anyway, thanks.
Btw, I tried to capture the update blob but after I renamed it, it disappeared from the /cache
I was just curious as to what you did to the update to defang it.
Is removing the recovery enough?
Does it also carry a bootloader update which you also have to remove?
Click to expand...
Click to collapse
I packed only the boot.img in the file. All the other junk is gone. From what I saw in the unpacked boot.img, there appears to be minor changes in the files. Quite possibly updates.
sent from my ASUS Transformer running modded ICS using Tapatalk

Can you just add superuser binary and the app plus busybox to the user script? I'm curious how you could go about further de clawing this update for rooted users.. maybe not wipe the system xbin folder just amend it? I'm out of my element...

luna_c666 said:
Can you just add superuser binary and the app plus busybox to the user script? I'm curious how you could go about further de clawing this update for rooted users.. maybe not wipe the system xbin folder just amend it? I'm out of my element...
Click to expand...
Click to collapse
I backed up su with OTA RootKeeper then rebooted into CWR. I flashed the zip, rebooted and let the update "optimize [my] apps". Once that was done I was greeted with my usual homescreen. A toast notification informed me WebKey was granted SuperUser permission, as always happens on bootup.
Surprised, I launched SuperUser and saw a corresponding new entry in the log. I double checked my current version of su, which was found to be current. I'm assuming that a "No newer version of su available" means su (and thus root) wasn't removed during the upgrade.
I next launched OTA RootKeeper which oddly reported my TF101 was no longer rooted. Nonetheless I hit RESTORE and root is back: or rather OTA RootKeeper is happy now.
--L.

Patch good for Non US Firmware?
I have tried to flash this update but I get an asset failure. Could that be due to the fact that I am running stock WW ICS and not the US version?

error
I got the error in the image I tried a couple of options including the microsd.
https://www.sugarsync.com/pf/D7256720_703_699618527
Sorry I cant get the image to show.

Sharpe351 said:
I didn't wipe anything. It worked fine for me. It works just like a normal backup. You may need to be sure to have all the factory installed files though. I did the update from a full stock, rooted ROM. Worked great.
Click to expand...
Click to collapse
Did you do this in CWM or no? I dont have CWM installed dont really care to bc Im not flashing any ROMs until NVflash works on my sbk version
Sent from my Transformer TF101 using Tapatalk

avasman said:
I have tried to flash this update but I get an asset failure. Could that be due to the fact that I am running stock WW ICS and not the US version?
Click to expand...
Click to collapse
you have to be on a US firmware.
Sent from my Motorola Triumph on CM7 (my custom build) using Tapatalk

lemonoid said:
Did you do this in CWM or no? I dont have CWM installed dont really care to bc Im not flashing any ROMs until NVflash works on my sbk version
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
this is not a ROM. Its a patch from Asus. Yes, it is cwm flashable.
Sent from my Motorola Triumph on CM7 (my custom build) using Tapatalk

carlvk said:
I got the error in the image I tried a couple of options including the microsd.
https://www.sugarsync.com/pf/D7256720_703_699618527
Sorry I cant get the image to show.
Click to expand...
Click to collapse
that is an assert failure. The update isn't happy due to the ROM you're running. if you aren't on a US ROM, it wont update.
Sent from my Motorola Triumph on CM7 (my custom build) using Tapatalk

Sharpe351 said:
that is an assert failure. The update isn't happy due to the ROM you're running. if you aren't on a US ROM, it wont update.
Sent from my Motorola Triumph on CM7 (my custom build) using Tapatalk
Click to expand...
Click to collapse
Aha, that'll be it I'm on ww.
Thanks for the help.

doesn't work for me (us tf).
sth about asusreader. maybe because i've deleted it and other stock apps...

oifi said:
doesn't work for me (us tf).
sth about asusreader. maybe because i've deleted it and other stock apps...
Click to expand...
Click to collapse
you need to be running a full ROM as stated in the OP.
Sent from my Motorola Triumph on CM7 (my custom build) using Tapatalk

Thank You
Sharpe thank you for this zip. I have a US B80 and the stupid update would start to install and then after getting about a 1/4 of the way it would freeze on the android with the exclamation point. Your zip solved that problem and so far no reboots or any weirdness. I do have one question about the update though, how do I stop the tablet from trying to take the OTA(it is persistent).
Thanks

US ICS OTA file?

Could someone post up the US ICS OTA file? I don't see it available on Lenevo's download site yet: http://download.lenovo.com/slates/think/tablet1/

It is on the Lenovo FTP
ftp://slatesftp:[email protected]/ThinkPadTablet_A310_03_0069_0130_US.zip

mandrsn1 said:
It is on the Lenovo FTP
ftp://slatesftp:[email protected]/ThinkPadTablet_A310_03_0069_0130_US.zip
Click to expand...
Click to collapse
upload it if you have it please the link is down now
Sent from my ThinkPad Tablet using Tapatalk 2

ker2gsr said:
upload it if you have it please the link is down now
Sent from my ThinkPad Tablet using Tapatalk 2
Click to expand...
Click to collapse
That link is still working for me. I don't have a service i can upload to right now.

mandrsn1 said:
That link is still working for me. I don't have a service i can upload to right now.
Click to expand...
Click to collapse
from your tablet or PC? no dropbox?
Sent from my ThinkPad Tablet using Tapatalk 2

ker2gsr said:
upload it if you have it please the link is down now
Sent from my ThinkPad Tablet using Tapatalk 2
Click to expand...
Click to collapse
Here a dropbox till its on the http:
http://dl.dropbox.com/u/11001249/ThinkPadTablet_A310_03_0069_0130_US.zip

US needs two update files if going the FTP site download route.....~A310~(291M) and ~A400~(4.9M).

eldata said:
US needs two update files if going the FTP site download route.....~A310~(291M) and ~A400~(4.9M).
Click to expand...
Click to collapse
I was able to download both from the FTP here: ftp://slatesftp:[email protected]/slates/think/tablet1/
Now the question I am wondering is... Is it worth it? Potentially sacrificing root and CWR? I have been running 0.0.7.3 CM9 build for many months now and am curious to what you all think.
Pros/Cons? I've heard battery life is terrible, which is odd because I feel like I have good battery life on the CM9 Port. Also... Is root completely gone? Does OTA Rootkeeper help? My biggest concern (I'd probably even lose root if it is fixed), does the pen work as advertised? Or is the infamous 'pen wonk' bug still present?
Pen wonk = writing notes for ~10-15 minutes, pen is suddenly not responsive. Sleep/waking the device fixes it usually. This has been present in every stock Honeycomb build as well as all the CM9 Port builds so I am very curious if this is fixed because I believe it is a hardware issue (Lenovo please prove me wrong). Any info would be much appreciated.

obscure.detour said:
Now the question I am wondering is... Is it worth it? Potentially sacrificing root and CWR? I have been running 0.0.7.3 CM9 build for many months now and am curious to what you all think.
Pros/Cons? I've heard battery life is terrible, which is odd because I feel like I have good battery life on the CM9 Port. Also... Is root completely gone? Does OTA Rootkeeper help? My biggest concern (I'd probably even lose root if it is fixed), does the pen work as advertised? Or is the infamous 'pen wonk' bug still present?
Pen wonk = writing notes for ~10-15 minutes, pen is suddenly not responsive. Sleep/waking the device fixes it usually. This has been present in every stock Honeycomb build as well as all the CM9 Port builds so I am very curious if this is fixed because I believe it is a hardware issue (Lenovo please prove me wrong). Any info would be much appreciated.
Click to expand...
Click to collapse
I was able to go from a rooted, CWM'd device (US 64GB) to a fully rooted device without CWM.
After a few painful steps to get an old busybox file restored and stock recovery enabled, the upgrade process was very simple and so far it is working very well with ICS. There hasn't been enough time to judge battery life yet....
Make sure you follow the instructions that other's have posted about using RootKeeper. That is the only thing I needed to use to restore root perfectly.

armondole said:
After a few painful steps to get an old busybox file restored and stock recovery enabled, the upgrade process was very simple and so far it is working very well with ICS.
Click to expand...
Click to collapse
I updated with CWR rather than reverting to stock recovery. Everything worked fine. However, it did get rid of the stock recovery.

armondole said:
I was able to go from a rooted, CWM'd device (US 64GB) to a fully rooted device without CWM.
After a few painful steps to get an old busybox file restored and stock recovery enabled, the upgrade process was very simple and so far it is working very well with ICS. There hasn't been enough time to judge battery life yet....
Make sure you follow the instructions that other's have posted about using RootKeeper. That is the only thing I needed to use to restore root perfectly.
Click to expand...
Click to collapse
That is good news about the ability to keep root. At least in keeping root, we should theoretically be able to restore CWR.
mandrsn1 said:
I updated with CWR rather than reverting to stock recovery. Everything worked fine. However, it did get rid of the stock recovery.
Click to expand...
Click to collapse
How were you able to update using CWR?

obscure.detour said:
That is good news about the ability to keep root. At least in keeping root, we should theoretically be able to restore CWR.
How were you able to update using CWR?
Click to expand...
Click to collapse
I commented out the lines of the update script that checked for "indigo" in build.prop.

so you're now on official ISC with Root AND CWM ??
it's a great news !

quyTam said:
so you're now on official ISC with Root AND CWM ??
it's a great news !
Click to expand...
Click to collapse
No, when ICS installed, it got rid of CWM.

mandrsn1 said:
I commented out the lines of the update script that checked for "indigo" in build.prop.
Click to expand...
Click to collapse
Do you mind posting how you did the whole install process? Thanks.

bigsnack said:
Do you mind posting how you did the whole install process? Thanks.
Click to expand...
Click to collapse
I did not have CWR to start.
I downloaded the update through the "update" menu on the device.
Update failed due to gps.conf being modified.
Reverted to what I thought was old gps.conf, update still failed.
Install CWR
Try update through CWR
Still fail, due to indigo being required in build.prop (this error is caused by CWR)
Commented out the Indigo lines in the update-script in the update
Flashed again
Still failed for gps.conf.
Commented out each line in update-script mentioning gps.conf
flashed again, it worked.

I take you flashed 310 first then 400?
Where is the script located?

bigsnack said:
I take you flashed 310 first then 400?
Where is the script located?
Click to expand...
Click to collapse
The update-script is in the META-INF/com/google/android folder in the zip. a # sign will comment out any line.

Do I put the number sign in the front?

bigsnack said:
Do I put the number sign in the front?
Click to expand...
Click to collapse
Here is the file i used
http://dl.dropbox.com/u/8479005/updater-script

New User - Problem with Update after rooting

I'm sorry for having to post here, I'm a new XDA member and I've just started using my tablet and found out I can't post in the dev section. I'm not sure how else to get help and a previous boyfriend told me the xda-developers community was a great place so I thought I would try here.
I have the Nexus 7 (2013 edition) and I used WUG's method of rooting - everything went perfectly, but now I'm getting a notification that there is an update (an OTA update - I think that's what they are called?) and it doesn't apply. I'm not sure if I should have, but I did the bootloader unlock and installed a new recovery (TWRP - I think that's how it's spelled?. sorry again)...
Anyway.... At this point my tablet is working great, but I constantly see this notification for an update and I'm not sure what to do.. It says "touch to install" and I've done that but it just boots into my new recovery. If anybody has access to WUG in the dev forum, could you please ask him what I should do?
Thanks!!!!!!!!!!!!!!

BarbaraG said:
I'm sorry for having to post here, I'm a new XDA member and I've just started using my tablet and found out I can't post in the dev section. I'm not sure how else to get help and a previous boyfriend told me the xda-developers community was a great place so I thought I would try here.
I have the Nexus 7 (2013 edition) and I used WUG's method of rooting - everything went perfectly, but now I'm getting a notification that there is an update (an OTA update - I think that's what they are called?) and it doesn't apply. I'm not sure if I should have, but I did the bootloader unlock and installed a new recovery (TWRP - I think that's how it's spelled?. sorry again)...
Anyway.... At this point my tablet is working great, but I constantly see this notification for an update and I'm not sure what to do.. It says "touch to install" and I've done that but it just boots into my new recovery. If anybody has access to WUG in the dev forum, could you please ask him what I should do?
Thanks!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Do you have the WiFi only version or the LTE version? Also, under your settings -> about phone, what build number are you currently on? Since you have rooted and installed a custom recovery, OTA updates will not install correctly. You have a couple of options in this regards, and I or someone will go over them once we figure out what version you are running.

railed said:
Do you have the WiFi only version or the LTE version? Also, under your settings -> about phone, what build number are you currently on? Since you have rooted and installed a custom recovery, OTA updates will not install correctly. You have a couple of options in this regards, and I or someone will go over them once we figure out what version you are running.
Click to expand...
Click to collapse
ThankYou so much for the help... It's the WiFi only version. The build number is: JSS15J

http://forum.xda-developers.com/showthread.php?t=2404833

BarbaraG said:
ThankYou so much for the help... It's the WiFi only version. The build number is: JSS15J
Click to expand...
Click to collapse
Thanks for that:
Here's what you can do to install the update.
1) go to this thread and download either the odexed or deodexed version.
2) Reboot to recovery
3) Wipe Cache/Dalvik Cache
4) Flash the .zip file you just downloaded
5) Reboot your updated tablet.
OR
You can read here and try this.

railed said:
Thanks for that:
Here's what you can do to install the update.
1) go to this thread and download either the odexed or deodexed version.
2) Reboot to recovery
3) Wipe Cache/Dalvik Cache
4) Flash the .zip file you just downloaded
5) Reboot your updated tablet.
OR
You can read here and try this.
Click to expand...
Click to collapse
Oh railed, thankyou so much - I was not sure if I would be able to get any more updates. If I do that, will it delete everything on my tablet? It did that when I did the change to an unlocked bootloader, and I had to reload everything.

BarbaraG said:
Oh railed, thankyou so much - I was not sure if I would be able to get any more updates. If I do that, will it delete everything on my tablet? It did that when I did the change to an unlocked bootloader, and I had to reload everything.
Click to expand...
Click to collapse
All your data will be preserved. Only Wipe the Cache/Dalvik Cache, not the Data. Before you install go to Wipe -> Advance -> Check only Cache and Dalvik Cache.
Typically when an update comes out, someone will post a flashable update within a couple of hours so we can install them as well. Hope it helps.
Edit: As always before flashing anything, make a backup, by rebooting into recovery and selecting Backup (i check all the boxes).

BarbaraG said:
Oh railed, thankyou so much - I was not sure if I would be able to get any more updates. If I do that, will it delete everything on my tablet? It did that when I did the change to an unlocked bootloader, and I had to reload everything.
Click to expand...
Click to collapse
Also.... If I just load the latest cyanogenmod on it, will that take care of it. I have the same old phone from my previous boyfriend and it's running cyanogenmod.. It will update the OS whenever a new version comes out and I don't lose the data like I did with the unlock bootloader thing?

BarbaraG said:
Also.... If I just load the latest cyanogenmod on it, will that take care of it. I have the same old phone from my previous boyfriend and it's running cyanogenmod.. It will update the OS whenever a new version comes out and I don't lose the data like I did with the unlock bootloader thing?
Click to expand...
Click to collapse
I believe so, Cyanogenmod usually merges the updates pretty quickly into the code and you won't get any update notifications from Google directly any more. There are only nightly releases so far for this device if you feel like going that route.

railed said:
I believe so, Cyanogenmod usually merges the updates pretty quickly into the code and you won't get any update notifications from Google directly any more. There are only nightly releases so far for this device if you feel like going that route.
Click to expand...
Click to collapse
Thank You! Very Much!!!
Do you think I should go the cyanogenmod route?
I've really liked cyanogenmod on the phone on barnes&noble device they are on, but I've been scared to update this tablet since we've broken up and I don't have anybody that can help.

BarbaraG said:
Thank You! Very Much!!!
Do you think I should go the cyanogenmod route?
I've really liked cyanogenmod on the phone on barnes&noble device they are on, but I've been scared to update this tablet since we've broken up and I don't have anybody that can help.
Click to expand...
Click to collapse
That's completely up to you and what you prefer... I like the stock android experience so far, but there are many options out there for custom ROMs besides CM. Take a look here and here and figure out if a ROM in there has something you want... the great thing about this is if you don't like it, flash something else until you find exactly what you like... that's how I plan to do it, once the ROMs get more stable with the 4.3 updates.

railed said:
Thanks for that:
Here's what you can do to install the update.
1) go to this thread and download either the odexed or deodexed version.
2) Reboot to recovery
3) Wipe Cache/Dalvik Cache
4) Flash the .zip file you just downloaded
5) Reboot your updated tablet.
OR
You can read here and try this.
Click to expand...
Click to collapse
I've been reading through all of the links you sent and some others I've found. Should I go with the odexed or deodexed version?

BarbaraG said:
I've been reading through all of the links you sent and some others I've found. Should I go with the odexed or deodexed version?
Click to expand...
Click to collapse
I use deodexed, as do a lot of people who like to customize. There's not a lot of difference between the two. Here is an article that explains it pretty well: Odexed vs Deodexed

railed said:
I use deodexed, as do a lot of people who like to customize. There's not a lot of difference between the two. Here is an article that explains it pretty well: Odexed vs Deodexed
Click to expand...
Click to collapse
Thank You, I now know the difference between them. I think I'll go with the Deodexed version also.
Thanks again for all of your help!!!!!

New OTA LIVE OTA2.3

Just Received The New OTA 2.3 (77 mb)
Now Installing It ....
Change Log
-Fixed localization
-Improved touch responsiveness
-updated stock apps
-miscellaneous bug and security fixes

Screenies
Wait Uploading Screenies

Deepak Vishnu said:
Wait Uploading Screenies
Click to expand...
Click to collapse
I'm rooted please can you tell me how to install it?
Thanks

nixey55 said:
I'm rooted please can you tell me how to install it?
Thanks
Click to expand...
Click to collapse
didn't you get the ota ???

Deepak Vishnu said:
didn't you get the ota ???
Click to expand...
Click to collapse
Yes I got the notification but I'm worried that if I install it on a rooted device it will brick my tablet.

nixey55 said:
Yes I got the notification but I'm worried that if I install it on a rooted device it will brick my tablet.
Click to expand...
Click to collapse
I doubt it'll brick your device, but it'll almost definitely remove root access, and it's also possible that it'll break whatever methods there are for obtaining root again.

rchrdcrg said:
I doubt it'll brick your device, but it'll almost definitely remove root access, and it's also possible that it'll break whatever methods there are for obtaining root again.
Click to expand...
Click to collapse
I wonder if I Could just flash the stock recovery, then apply the OTA then flash CWM and SU

its patching the kernel first looking at it,
tried it on mine just and it errors out, doesn't "brick it" oh I hate that expression, and errors before making any other changes.
Guess I'll need to restore a stock kernel/recovery before flashing it

Interesting..
375 is ota 2_1
not seen 389
Code:
"Package expects build fingerprint of nvidia/tn7_114gp/tegranote:4.4.2/KOT49H/16492_375.9410:user/release-keys or nvidia/tn7_114gp/tegranote:4.4.2/KOT49H/17785_389.4427:user/release-keys;

fards said:
Interesting..
375 is ota 2_1
not seen 389
Code:
"Package expects build fingerprint of nvidia/tn7_114gp/tegranote:4.4.2/KOT49H/16492_375.9410:user/release-keys or nvidia/tn7_114gp/tegranote:4.4.2/KOT49H/17785_389.4427:user/release-keys;
Click to expand...
Click to collapse
I Personally Found this to be actually good update it fixes all the unresponsiveness of the tegra and makes it again a beast luvin it
and I had to edit the updater script to get it working on the tegra note rooted and dirty flashed with cwm
I Like It Dirty

Deepak Vishnu said:
I Personally Found this to be actually good update it fixes all the unresponsiveness of the tegra and makes it again a beast luvin it
and I had to edit the updater script to get it working on the tegra note rooted and dirty flashed with cwm
I Like It Dirty
Click to expand...
Click to collapse
Sounds quite complicated.

Deepak Vishnu
Do you think you can explain how to modify the updater script to be able to flash the new update using cwm.
Do you lose root and cwm if you do it this way?
Thanks for your help.
Cheers,
Drc.

Installation seems to work with cwm. Still on the go for me, but no errors yet, and i got through the "Verifying current system" step.
E: nope. gets till the end, but quits with an error (no error message though)
E2: got it now. Update is AWESOME! Tab is faster and responsivenes did really improve. love it!

cars10k said:
Installation seems to work with cwm. Still on the go for me, but no errors yet, and i got through the "Verifying current system" step.
E: nope. gets till the end, but quits with an error (no error message though)
E2: got it now. Update is AWESOME! Tab is faster and responsivenes did really improve. love it!
Click to expand...
Click to collapse
New OTA 4.4.2 2.3 made into a rom for CWM recovery check it out. flash in recovery then flash supersu for root.
http://rootjunkysdl.com/?device=Tegra Note 7&folder=Rom Stock 4.4.2-2.3

They have removed art from the developer options. That's annoying
Sent from my TegraNote-P1640 using Tapatalk

fards said:
They have removed art from the developer options. That's annoying
Sent from my TegraNote-P1640 using Tapatalk
Click to expand...
Click to collapse
I've installed it but cant' see any obvious changes. Does anyone know what the improvements are supposed to be?

Tomsgt said:
New OTA 4.4.2 2.3 made into a rom for CWM recovery check it out. flash in recovery then flash supersu for root.
http://rootjunkysdl.com/?device=Tegra Note 7&folder=Rom Stock 4.4.2-2.3
Click to expand...
Click to collapse
Very nice Tom. I will have to check this out. I will be deployed on an exercise on Tuesday for a couple of months, so its nice to get this just before I go! My Tegra Note 7 has been running great so far...

Tomsgt said:
New OTA 4.4.2 2.3 made into a rom for CWM recovery check it out. flash in recovery then flash supersu for root.
Click to expand...
Click to collapse
Is your server having any bandwidth issues? I've had quite a bit of trouble downloading the rom in the past 12 or so hours, with the max speed capping at 15-16kb/s and two dropouts.
That said, It seems to have come good in the last hour though. Thankyou for the effort of putting this up :good:

I updated my TN7 first to 4.4.2 and the previous OTA (2.2 i assume), then used the SuperTool 2.2 from the other thread to unlock and root the tablet with no problems.
Next day this OTA was avaiable and it installed without problems. Root is still active.
I wanted to say i have a EVGA one, but after trying to confirm this, i'm not so sure anymore. Will ask in other thread to find out.

I tried ART with mine and had tons of issues... anything involving the stylus support just went totally wonky. Shame, cuz it certainly zipped along!
---------- Post added at 02:53 PM ---------- Previous post was at 02:52 PM ----------
DC-TeaAge said:
I updated my TN7 first to 4.4.2 and the previous OTA (2.2 i assume), then used the SuperTool 2.2 from the other thread to unlock and root the tablet with no problems.
Next day this OTA was avaiable and it installed without problems. Root is still active.
I wanted to say i have a EVGA one, but after trying to confirm this, i'm not so sure anymore. Will ask in other thread to find out.
Click to expand...
Click to collapse
If it was the EVGA one, there would be a big EVGA logo on the back

4.4.3 GPE update DO NOT UPDATE (edit:Fixed)

The camera won't connect anymore, Wi-Fi won't turn on and the SD card wont mount. How did this get approved by google??
Edit:
To get the OTA to work properly and flash the correct kernal, your CID must be changed to GOOGL001. If you have the GPE device, you don't need to do anything, but if you have a converted GPE then you must change your CID if you want OTA's. This was not made clear in the RUU thread, it was mentioned that changing your CID was optional if you had one of the listed CID's, but it is not optional, but a requirement if you want the OTA's to work.
Everyone that has changed there CID's reflashed the OTA and everything flashed fine, whereas anybody that had not modified there CID had the problem with the kernal.

Psosmith82 said:
The camera won't connect anymore, Wi-Fi won't turn on and the SD card wont mount. How did this get approved by google??
Click to expand...
Click to collapse
maybe you had a bad download?

HRodMusic said:
maybe you had a bad download?
Click to expand...
Click to collapse
I used the download linked from the discussion thread. Put on phone storage, rebooted into recovery and applied the update from phone storage.

Same results with OTA.
Sent from space.

Psosmith82 said:
I used the download linked from the discussion thread. Put on phone storage, rebooted into recovery and applied the update from phone storage.
Click to expand...
Click to collapse
Checked the MD5 before?

Extremer2903 said:
Checked the MD5 before?
Click to expand...
Click to collapse
Used the OTA provided by graffixnyc

Extremer2903 said:
Checked the MD5 before?
Click to expand...
Click to collapse
The signature verification wouldn't apply the update if it saw mismatches.

Archon810 said:
The signature verification wouldn't apply the update if it saw mismatches.
Click to expand...
Click to collapse
Odd.. I had no problems using the OTA zip.. Did you guys try wiping data?

graffixnyc said:
Odd.. I had no problems using the OTA zip.. Did you guys try wiping data?
Click to expand...
Click to collapse
I tried wiping data, still had the same problem. I am reflashing the RUU and will try the ota again. If it doesn't work after the 2nd try, i will just wait for google to send the OTA to me. Wiping data sucks, have to redo everything

Psosmith82 said:
The camera won't connect anymore, Wi-Fi won't turn on and the SD card wont mount. How did this get approved by google??
Click to expand...
Click to collapse
I wonder if this is also being experienced by any other users or if this is specific to your software config and/or some glitch while writing the firmware. I assume you haven't yet tried wiping your /data partition, right?

willverduzco said:
I wonder if this is also being experienced by any other users or if this is specific to your software config and/or some glitch while writing the firmware. I assume you haven't yet tried wiping your /data partition, right?
Click to expand...
Click to collapse
I wiped data and still had problems. I'm working on starting over right now

Then problem should be wiped/not wiped, I think. Anyway, trying with this error stuff is always an excited challenge with me, try to deal with it like that to reduce percentage of throwing your devices away .

Also you need to be FULLY stock.. that includes the stock kernel. If you are running a custom kernel some kernels flash libs and modules. EVERYTHING NEEDS TO BE STOCK

graffixnyc said:
Also you need to be FULLY stock.. that includes the stock kernel. If you are running a custom kernel some kernels flash libs and modules. EVERYTHING NEEDS TO BE STOCK
Click to expand...
Click to collapse
Mine is fully stock. I have an unlocked HTC one, and i flashed the GPE conversion RUU. Does the CID need to be changed to the Google CID

Psosmith82 said:
Mine is fully stock. I have an unlocked HTC one, and i flashed the GPE conversion RUU. Does the CID need to be changed to the Google CID
Click to expand...
Click to collapse
that's a really good question Psosmith

Only thing I can think of on my example is I had 'CF.lumen' installed... Other than that, I had (your) completely stock GPE conversion.
Troubleshooting...
Sent from space.

Is the problem from the update zip or ota+
Sent from my HTC One_M8 using XDA Premium 4 mobile app

Android The Greek said:
Is the problem from the update zip or ota+
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I figured out the problem. I flashed the new RUU that graffix posted with 4.4.3. The Kernal in the OTA is not updating like it should, it stays on the kernal that was made in March. The new Kernal has a date of Thursday May 22nd. So for whatever reason, the OTA is not flashing the new Kernal, which is why all those things were broken. If you use the RUU update, it will flash the new kernal, and everything works as it should.
You'll know right off the bat at first boot. With the OTA, the boot animation hangs and it hangs on the home screen. With the RUU flash, everything is buttery smooth.

Something tells me this problem is occurring for people who actually have a retail M8 that they dirty-flashed using a GPE RUU.
Does anyone with an honest-to-God GPE that was purchased from Google have this problem? If so, this is huge.

Android The Greek said:
Is the problem from the update zip or ota+
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The update worked fine on my device and I used it for the conversion RUU. odd.. I used that very same OTA file. very odd...