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
Related
Hi
To be able to bypass the process of a flash to v13_13, open the backdoor, flash to 14_14 etc. can anyone point me to a rooted 14_14 rom?
In particular "K1_A301_14_14_120109_US"
Thanks
http://rootzwiki.com/topic/13407-alpha-ideapad-k1-cwm-stock-rooted-rom-120109-build/
Although still in the alpha stage, I switched from using timmydean's rom to this one specifically so I could successfully run the 14_14 rom and keep my root. Nothing against timmydean and his work, this just worked easier and faster. Also this rom add cwm which is the only rom out currently that does this for the k1, from what I've seen.
Just reemeber that this is still just an alpha, so be sure to read the post fully. Hope this helps!
Thanks for posting the link Dueces99. I compiled the CWM and ROM that Deuces99 linked to. I just wanted to add that there is nothing alpha about the ROM, just CWM. The ROM is stock and rooted and has no bugs (Other than the ones the stock ROM has).
The reason I left the Alpha status is because backup/restore don't work in CWM, and there is currently no key combination to boot into recovery. You must boot to recovery using the included app/widget
Right, there is no physical key combo. associated to booting into Recovery, the rom atleast provides the means to boot into recovery (widget/app) which atleast leaves the option. I personally, have not had any issues at all with this rom, and love the fact that all the bloatware misc. 3rd party apps and some Lenovo apps were removed, which made the rom seem that much more responsive upon first boot IMO.
Glad to hear that was of some help to you, kinda surprised there hasnt been anyother spinoff roms from this, regardless of its released stage. Just how cut and dry it is with flashing the 2nd newest update with root, then simply flashing the 14_14 update through CWM and keeping root. That was my biggest hurdle following timmydean's guide (and still is) was keeping root once taking the update from Lenovo.
Just my 0.02
so all i need is to flash alpha 3 and latest update 120109 in order to be on a rooted 14_14 build? can someone confirm?
Sent from my K1 using xda premium
prfstrkr said:
so all i need is to flash alpha 3 and latest update 120109 in order to be on a rooted 14_14 build? can someone confirm?
Sent from my K1 using xda premium
Click to expand...
Click to collapse
Correct. After that you will be up to date and rooted.
Right, confirming with khanning88 flashing alpha 3 would be the 13_13 update. After flashing that, reboot into recovery via the Reboot Recovery app/widget included in the ROM, follow the instructions from there provided by the rootzwiki post and you'll be good to go with the latest 14_14 update. By far, the most cut-n-dry rooted ROM out there as far as I know. IMHO kinda deceiving that the ROM is listed as an Alpha (for CWM understandably) only because it's been extremely stable for me with nada one FC.
Wierd how an alpha build ROM is more stable than the OS that the K1 comes with...
Dueces99 said:
Wierd how an alpha build ROM is more stable than the OS that the K1 comes with...
Click to expand...
Click to collapse
From what I understand, it's the same firmware as the stock Lenovo, so maybe a little bit of a placebo effect? The CWM ROM does take out all the built-in non-Google apps, so maybe that has something to do with it.
I hope Lenovo gets its act together and shares out the proper source code so that some good samaritan out there can build a stock Android ROM to run on the K1. I've been using it a bit on the 14_14 CWM firmware, and it's still not as good as the firmware I've experienced on the ASUS Transformer TF101 or the Acer Iconia A500. The biggest issue I've found with the Lenovo firmware is that there is a lag closing out of apps and going back to the launcher, sometimes to the point that a forceclose-wait window pops up. I've not experienced that on the Honeycomb ROMs of any of those other two devices, so I wonder if it's because of Lenovo's customizations to Honeycomb, like the ability to close apps from the multitasking sidebar. In that case, maybe a more vanilla version of Honeycomb won't have that problem. Don't get me wrong; I think it's a great feature that Lenovo added to the taskswitcher. But I'd rather not have it than have the operating system lag. I trust Android's memory management enough to not really need to go manually closing apps.
Right, im sure all the bloatware taken out from Lenovo had to have some effect on overall performance. As far as stability between the two, maybe I meant to say "Wierd how an alpha build ROM feels more stable than the OS that the K1 comes with..."
But placebo effect or not, I've experienced zero issues with this rom even though I probably don't do near as much as other K1 owners with their tab. Lenovo does need to fix this, or preferably just provide full source to all...
khanning88 said:
Correct. After that you will be up to date and rooted.
Click to expand...
Click to collapse
Thank you so much! I am finally rooted with 14_14 with all the bloatware removed
prfstrkr said:
Thank you so much! I am finally rooted with 14_14 with all the bloatware removed
Click to expand...
Click to collapse
Welcome, glad you like it.
P.S. I should have an update ready in a couple of days....... and this one is a BIG update
I'm glad I remembered to check back on my thread!
I'll be a rooting tomorrow morning
Thanks Dueces99
omg ... plz tell me it's ICS
Sent from my Xoom using xda premium
khanning88 said:
Welcome, glad you like it.
P.S. I should have an update ready in a couple of days....... and this one is a BIG update
Click to expand...
Click to collapse
Thank you so much, khanning, for all of your efforts. As I mentioned in this thread http://forums.lenovo.com/t5/IdeaPad-Slate-Tablets/K1-not-booting-after-update/td-p/548285 , your CWM firmware is the only effective workaround at the moment for those of us whose K1's are inexplicably locking up with "unrecoverable bootloader" errors to get onto the latest firmware.
We still aren't completely out of the woods though. In post 44 of your rootzwiki thread http://rootzwiki.com/topic/13407-al...-120109-build/page__view__findpost__p__390175 and post 47 http://rootzwiki.com/topic/13407-al...-120109-build/page__view__findpost__p__392343 , the users kennethrkennedy and aig787 both confirm that the "unrecoverable bootloader error" can still come back with updates, even through your CWM recovery. With your Alpha3 and your 120109.zip update, you managed to avoid updating whatever it is that causes the "unrecoverable bootloader error." This is my long rambling plea that, whatever you did there, you will continue to do for the latest update you are working on, so that those of us with these K1's that are prone to the "unrecoverable bootloader errors" can join the fun too. Thanks!
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
Hello TPT community,
I Just got this tablet mainly because of the included digitizer and was wondering if anyone could give me a guideline on how to speed things up for this tablet. The tablet came with honeycomb 3.1 included and I am finding it pretty sluggish and unresponsive in general tasks. I went into settings to do a software update but it seems there is no 4.0 update available. There doesn't seem to be a toggle for pen only input in the settings either. Is the normal process for flashing a new Rom to root, then install CWM, and flash Roms?
I'm kind of a n00b here, but that is the right process in general.
For you, there should be a 4.0 update, but you might have to try a few times. After you are running ICS (4.0) you can root and load Koshu's JB rom.
Aren't there problems with rooting ICS?
Sent from my ThinkPad Tablet using xda app-developers app
Absolutely no problms rooting ics
Sent from my Micromax A50
Okay well I went into settings, about tablet, system updates, check for updates. It always says "your system is up to date" even though I know I'm on 3.1
Sent from my ThinkPad Tablet using xda app-developers app
Lets see if we can figure out why it won't update. In settings -> about tablet, what is listed for model number, android version, and kernel version?
Edit:
Found this - http://forums.lenovo.com/t5/ThinkPa...ystem-updates-OTAs-not-installing/ta-p/713571
It might help... I'm also searching for a manual download for ota3 or ota 3.5 from lenovo that you can load in recovery.
Edit 2:
Sorry, I need more coffee...
Is this a wifi only tablet or a 3g tablet? What region is it?
I attached the info in a picture. I dont know how to find out what region or wifi/3g it is though. I don't have a sim to test it. I got it from here: http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=7473177&CatId=6845
It is wifi only, also found this interesting thread - http://forums.lenovo.com/t5/ThinkPad-slate-tablets/thinkpad-1839-update/td-p/975085
Apparently the Tiger Direct refurb is a custom SKU and is SUPPOSEDLY not upgradeable... tho I would think there are ways around that. At least now I know what we are working with here.
da_reeseboy said:
It is wifi only, also found this interesting thread - http://forums.lenovo.com/t5/ThinkPad-slate-tablets/thinkpad-1839-update/td-p/975085
Apparently the Tiger Direct refurb is a custom SKU and is SUPPOSEDLY not upgradeable... tho I would think there are ways around that. At least now I know what we are working with here.
Click to expand...
Click to collapse
So any ideas on how to update to ICS? The ROM in android development section says it requires me to have ICS first.
Unfortunately no... sorry. I'm still a n00b with android devices. Maybe someone with a little more knowledge will chime in now that we know what we are dealing with.
You can root your tablet and go straight to Jelly Bean 4.1.1 or 4.1.2. It's fast and cool! The only little bug is with wifi!
Gesendet von meinem CM10 0.8.1 overclocked Jelly Bean 4.1.1 Thinkpadtablet
troemer said:
You can root your tablet and go straight to Jelly Bean 4.1.1 or 4.1.2. It's fast and cool! The only little bug is with wifi!
Gesendet von meinem CM10 0.8.1 overclocked Jelly Bean 4.1.1 Thinkpadtablet
Click to expand...
Click to collapse
A wifi bug is pretty big. The only connectivity mine has is wifi
I tried to install the adb drivers so I can root it but it says the driver has been tampered with so I can't install. I am on windows 8
Sent from my ThinkPad Tablet using xda app-developers app
@troemer: Not sure if you noticed it or not, but in Koshu's cm10 thread it says:
Requirements
This build uses the Lenovo ICS kernel, you need to upgrade to stock ICS first (Make sure you keep root!)
Click to expand...
Click to collapse
This is why he is trying to get the ICS update.
Daedalus_ said:
A wifi bug is pretty big. The only connectivity mine has is wifi
I tried to install the adb drivers so I can root it but it says the driver has been tampered with so I can't install. I am on windows 8
Sent from my ThinkPad Tablet using xda app-developers app
Click to expand...
Click to collapse
The wifi bug actually isn't that big, just set wifi to always on like suggested. As far as the tampered drivers error, you will probably have to : a) search for a way to install unsigned drivers on win8
or b) use a winxp/win7 pc.
Be careful tho... flashing after having stock ICS is needed for a reason.
Flashing what?
Daedalus_ said:
Flashing what?
Click to expand...
Click to collapse
Based on this:
Daedalus_ said:
A wifi bug is pretty big. The only connectivity mine has is wifi
Click to expand...
Click to collapse
I was worried you were gonna try to just jump straight to JB.
Hey there,
well one way is to try flashing the upgrade directly but like da_reeseboy already mentioned, there is a high possibility that it will fail. Only other way would be to flash the bootloader directly (that most likely the part, that keeps the JB kernel from booting on non ICS kernels) but there is a high bricking chance and eventually the firmware for some of the hardware needs to be updated, too, to work properly.
It looks like there's hope - this guy has the same weird software version as you - http://forum.xda-developers.com/showpost.php?p=37487649&postcount=6. He used the directions in that thread to upgrade to ICS.
Edit -
Full thread: http://forum.xda-developers.com/showthread.php?p=37487649#post37487649
Koshu said:
Hey there,
well one way is to try flashing the upgrade directly but like da_reeseboy already mentioned, there is a high possibility that it will fail. Only other way would be to flash the bootloader directly (that most likely the part, that keeps the JB kernel from booting on non ICS kernels) but there is a high bricking chance and eventually the firmware for some of the hardware needs to be updated, too, to work properly.
Click to expand...
Click to collapse
Just trying to think outside the box (noob style), what if he:
1. Installed CWM
2. Restored a clean 0075 nandroid from someone here on xda
3. Restored stock recovery
4. Checked for OTA to ICS
In my mind the software version is what is holding him back from updates, so I'm thinking that restoring an 0075 nandroid will put him in a position to get the update correctly... but I am still new to this so I could be WAY off.
da_reeseboy said:
Just trying to think outside the box (noob style), what if he:
1. Installed CWM
2. Restored a clean 0075 nandroid from someone here on xda
3. Restored stock recovery
4. Checked for OTA to ICS
In my mind the software version is what is holding him back from updates, so I'm thinking that restoring an 0075 nandroid will put him in a position to get the update correctly... but I am still new to this so I could be WAY off.
Click to expand...
Click to collapse
Thanks for still helping! Do I need a special CWM? I just root and install CWM from the market? Honeycomb is really annoying because some apps I use are only for newer androids such as Hulu plus.
Hi folks,
Anyone in the know, please correct me if I'm wrong or close this thread or whatever. I just wanted to share some stuff I've seen as well as my personal experience with the new 4.2 update.
Be warned: There doesn't seem to be a surefire way to root and/or install a custom recovery yet.
This is based on advice I saw on this post:
http://forum.xda-developers.com/showthread.php?p=38992986&highlight=sit+tight#post38992986
I know this has been stated in existing threads but I figure that in the excitement to flash, some folks may grab the update and then look to older 4.1-based guides on how to root and install custom recoveries only to realize that they can't. I thought it might be beneficial to post a big fat thread right up front to serve as an easily viewable cautionary note.
I would normally say that I was burned by this excitement, but in fact I don't really mind because right now I'm mostly just using it to read books and Pocket-ized webpages. Others should take note though.
MrCHUPON said:
Hi folks,
Anyone in the know, please correct me if I'm wrong or close this thread or whatever. I just wanted to share some stuff I've seen as well as my personal experience with the new 4.2 update.
Be warned: There doesn't seem to be a surefire way to root and/or install a custom recovery yet.
This is based on advice I saw on this post:
http://forum.xda-developers.com/showthread.php?p=38992986&highlight=sit+tight#post38992986
I know this has been stated in existing threads but I figure that in the excitement to flash, some folks may grab the update and then look to older 4.1-based guides on how to root and install custom recoveries only to realize that they can't. I thought it might be beneficial to post a big fat thread right up front to serve as an easily viewable cautionary note.
I would normally say that I was burned by this excitement, but in fact I don't really mind because right now I'm mostly just using it to read books and Pocket-ized webpages. Others should take note though.
Click to expand...
Click to collapse
Good idea to this topic friend, I also ran to install the new update and now I badly need root permissions, excuse my English.
MrCHUPON said:
Hi folks,
Anyone in the know, please correct me if I'm wrong or close this thread or whatever. I just wanted to share some stuff I've seen as well as my personal experience with the new 4.2 update.
Be warned: There doesn't seem to be a surefire way to root and/or install a custom recovery yet.
This is based on advice I saw on this post:
http://forum.xda-developers.com/showthread.php?p=38992986&highlight=sit+tight#post38992986
I know this has been stated in existing threads but I figure that in the excitement to flash, some folks may grab the update and then look to older 4.1-based guides on how to root and install custom recoveries only to realize that they can't. I thought it might be beneficial to post a big fat thread right up front to serve as an easily viewable cautionary note.
I would normally say that I was burned by this excitement, but in fact I don't really mind because right now I'm mostly just using it to read books and Pocket-ized webpages. Others should take note though.
Click to expand...
Click to collapse
I actually did install TWRP successfully. Boots to recovery but partitions must be changed as someone else mentioned. I can't see anything on internal or external SD card. I'm going to keep messing with.
We will just have to wait. This topic is a good warning for everyone that isn't reading all the stuff that is going on the foruns.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I've just flashed TWRP from this post:
http://forum.xda-developers.com/showpost.php?p=39056433&postcount=548
Everything (except external sdcard mounting) seems to be working
How did you flash the recovery without the USB icon on the bootloader?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Bootloader is now automatically going into fastboot mode.
joelalmeidaptg said:
How did you flash the recovery without the USB icon on the bootloader?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
Fastboot is the "default mode", so you don't need to enter the USB icon. I just installed TWRP successfully.
eye69 said:
Fastboot is the "default mode", so you don't need to enter the USB icon. I just installed TWRP successfully.
Click to expand...
Click to collapse
That's what I though, thanks!
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
eye69 said:
Fastboot is the "default mode", so you don't need to enter the USB icon. I just installed TWRP successfully.
Click to expand...
Click to collapse
Good to know. Would you say it's safe to "downgrade" to a previous version or even a different ROM then, or would the changed partition structure screw with the ability to do a clean wipe? Apologies if this is a n00b-sounding question.
Locked, Rooted, Factory reset, 4.2.1 OTA flashed, Still have root
I was locked and rooted on 4.1 with OTA root keeper installed and did a factory reset folowed by the 4.2.1 OTA and root keeper restored root. I have been rooted since ICS. This seems to be the only way right now to have rooted 4.2.1 on the TF300T.
bads3ctor said:
I was locked and rooted on 4.1 with OTA root keeper installed and did a factory reset folowed by the 4.2.1 OTA and root keeper restored root. I have been rooted since ICS. This seems to be the only way right now to have rooted 4.2.1 on the TF300T.
Click to expand...
Click to collapse
So you have a rooted 4.2.1 Asus ROM?? I wonder if OTA Root keeper would work with installing the update via fastboot. Or wait, how did you install the OTA 4.2.1? If you are rooted you must be unlocked, thus, not receiving the OTA update and having to download the blob from asus website.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
elesbb said:
So you have a rooted 4.2.1 Asus ROM?? I wonder if OTA Root keeper would work with installing the update via fastboot. Or wait, how did you install the OTA 4.2.1? If you are rooted you must be unlocked, thus, not receiving the OTA update and having to download the blob from asus website.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
I rooted ICS on a locked TF300T when I first received it. Yes....it was possible to root locked ICS at that time. Then with OTA root keeper, I kept root when 4.1 OTA happened. Then OTA 4.2.1 came and I retained root again with OTA root keeper....I am still locked so I still receive Asus OTA updates.
With new twrp 2.4.4.0, you guys now can install root and custom recovery. It is tested by me and other people :good:
tritran18518 said:
With new twrp 2.4.4.0, you guys now can install root and custom recovery. It is tested by me and other people :good:
Click to expand...
Click to collapse
Plus one...See this thread. I'm on 4.2.1 update, unlocked, twrp installed, rooted, and TB installed.
nick1313 said:
Plus one...See this thread. I'm on 4.2.1 update, unlocked, twrp installed, rooted, and TB installed.
Click to expand...
Click to collapse
+2... Just awaiting the ROM updates to roll out now :cyclops:
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