Database Users

Stock or custom?

I am getting tired of waiting for the stock 3.1 rom now so I am starting to think about using one of the custom roms.
Have there been any performance and function comparisons between the stock rom and the custom roms?
Or do you have any good arguments either way?

The two most popular appear to be Virtuous Picasso and Virtuous Galaxy. I have been using the 1.08 version of the former for sometime and have had no issues. I thether, have gps, bluetooth, WiFi all w/out issue. If your rooted, get wild and flash them both; see which you Luke better.

I like virtuous galaxy for the the touchwiz, but there were too many broken things. Exchange didn't work, couldn't access files on my external sd card (although apps like google music seemed to be able to) and my usb keyboard didn't work. Virtuous galaxy seems to work without any issues.

I've tried them all so far, and they all have pro's and con's. They also all have bugs, which is only to be expected.
Currently, I'm running stock and, to be honest, kinda prefer it. Though I *have* rooted and added a few tweaks...

willyampz said:
I like virtuous galaxy for the the touchwiz, but there were too many broken things. Exchange didn't work, couldn't access files on my external sd card (although apps like google music seemed to be able to) and my usb keyboard didn't work. Virtuous galaxy seems to work without any issues.
Click to expand...
Click to collapse
You started off saying virtuous galaxy had too many broken things, then went on to say virtuous galaxy seems to work without issues? Maybe it's too early and I'm reading it wrong in my barely awake state, but could you clarify please? Lol

vanisleguy1976 said:
You started off saying virtuous galaxy had too many broken things, then went on to say virtuous galaxy seems to work without issues? Maybe it's too early and I'm reading it wrong in my barely awake state, but could you clarify please? Lol
Click to expand...
Click to collapse
I don't mean to speak for willy but I think what he was saying is that at first, Virtuous Galaxy was nice but had too many broken features but after the release this past weekend, most of the bugs are fixed.
I am using Primee which is the Asus Transformer ROM with some of the Acer items left intact. I have tried Virtuous Galaxy and UI is beautiful but I was getting a barely perceptible lag opening and closing the app drawer even after OC to 1500 and it was bugging me. I think the problem could have been one of the Samsung widgets.
I normally recommend loading a custom rom if you feel comfortable. I rooted my HTC Magic back in the early days of Android and have never looked back.

wahlis said:
I am getting tired of waiting for the stock 3.1 rom now so I am starting to think about using one of the custom roms.
Have there been any performance and function comparisons between the stock rom and the custom roms?
Or do you have any good arguments either way?
Click to expand...
Click to collapse
You should go for 3.1 stock (official acer update), works like butter and fixes problems that custom roms still have (like cell stanby) unless they are based on 3.1 stock (I'm still waiting )
Update to 3.1 stock Acer Official Update
No wipe needed or acer recovery/cwm, you don't lose your data, but it's highly recommended to backup and use recovery/cwm, through again not necesary.
Here is a change log (what's new/changed) to see if it's worth, if you do update please share with me in that thread what's new and changed so we can inform, share and encourage pleople to update to 3.1, plus if you do it now you get new OTA Acer_ A500_4.010.30_COM_GEN1 (I sound like a salesman ) who knows for how long they will keep the update

Justray said:
You should go for 3.1 stock (official acer update), works like butter and fixes problems that custom roms still have (like cell stanby) unless they are based on 3.1 stock (I'm still waiting )
Update to 3.1 stock Acer Official Update
No wipe needed or acer recovery/cwm, you don't lose your data, but it's highly recommended to backup and use recovery/cwm, through again not necesary.
Here is a change log (what's new/changed) to see if it's worth, if you do update please share with me in that thread what's new and changed so we can inform, share and encourage pleople to update to 3.1, plus if you do it now you get new OTA Acer_ A500_4.010.30_COM_GEN1 (I sound like a salesman ) who knows for how long they will keep the update
Click to expand...
Click to collapse
My question is,after read almost all pages of the threads about this;does this go for all devices?I have a emea_gen3..sorry if i'm being a Noob now.
Sent from my A500 using Tapatalk

Thanks for all the advice. I think I'll wait a while longer for the stock now. It doesn't sound like the custom roms are the kind of miracle upgrades I got to my Hero and Desire phones yet.
Sent from my A500 using Tapatalk

booze78 said:
My question is,after read almost all pages of the threads about this;does this go for all devices?I have a emea_gen3..sorry if i'm being a Noob now.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Yes it works, I went from EMEA_GEN3 to COM_GEN1, everything works fine, updated from .22 to .30 from OTA.
wahlis said:
Thanks for all the advice. I think I'll wait a while longer for the stock now. It doesn't sound like the custom roms are the kind of miracle upgrades I got to my Hero and Desire phones yet.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Actually the update posted IS official, Acer one, right now those with that version are getting OTA .30 update, so as far as I know that's stock unless you mean out-of-the-box as stock.

i meant to say virtuous picasso seems to work without issues and tried to edit it after.

Justray said:
Yes it works, I went from EMEA_GEN3 to COM_GEN1, everything works fine, updated from .22 to .30 from OTA.
Actually the update posted IS official, Acer one, right now those with that version are getting OTA .30 update, so as far as I know that's stock unless you mean out-of-the-box as stock.
Click to expand...
Click to collapse
Yessss,it worked.Lost root only..
Sent from my A500 using Tapatalk

booze78 said:
Yessss,it worked.Lost root only..
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
and you can re-root
Please post here anything new you find, new issues, fixed issues, software and experience related please

Just don't forget to back up!

@Justray, you say : "Yes it works, I went from EMEA_GEN3 to COM_GEN1, everything works fine, updated from .22 to .30 from OTA."
How do you procede to go from EMEA_GEN3 to COM_GEN1?
My machine is COM_GEN1 so I'm happy. My sister who got hers in Denmark is EMEA_GEN3 and is still stuck with firmware 1.x (Android 3.0.1)... Is there a step-by-step instructions for going to COM_GEN1 for her machine?
I suspect I can then download the latest firmware manually from : code.google.com/p/acer-a500/downloads/list or use OTA like my machine?
Thanks,
Gilles.

ggravier said:
@Justray, you say : "Yes it works, I went from EMEA_GEN3 to COM_GEN1, everything works fine, updated from .22 to .30 from OTA."
How do you procede to go from EMEA_GEN3 to COM_GEN1?
My machine is COM_GEN1 so I'm happy. My sister who got hers in Denmark is EMEA_GEN3 and is still stuck with firmware 1.x (Android 3.0.1)... Is there a step-by-step instructions for going to COM_GEN1 for her machine?
Click to expand...
Click to collapse
I too went from EMEA_GEN3 to COM_GEN1. Here is the basic low-down as to how I went about it:
* Install Acer Recovery from Market and use it to install clockworkmod.
* Download the COM_GEN1 ROM from http://forum.xda-developers.com/showthread.php?t=1176632 thread.
* Use Acer ROM Decrypter to decrypt the .zip file and extract the update.zip from there.
* Rename the update.zip to something like e.g. AcerROMcomgen1.zip and copy it on your SD card. It's important that it is on the SD, not internal storage.
* Turn off your tablet, then turn it on while keeping the volume button pressed down until you see white text appear on the tablet screen's top-left corner.
* Use clockwordmod to first make a full backup for just-in-case. I really mean it: do a full backup. You never know if you might need it later!
* Then format cache, format data/factory reset, then install zip from SD.
* Reboot.
As for navigating in clockwordmod: you use the volume button to go up or down in menus, and power button to select the menu item.

[Q] K1 rooted 14_14 ROM

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!

[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

[Q] Problem with my Nexus 7

Hi
I recently bought a Nexus 7 that came with 4.1.1. I updated ota to 4.1.2 then rooted with a toolkit. For reasons I can't remember I then un-rooted and locked back bootloader. Now, games like dead trigger tell me my device is incompatible with them, even though they ran well on 4.1.1.
What can I do ? Flash another stock version of 4.1.2 ?
Thank you

I don't think there is any link between your root status and software compatibility, you could flash the 4.1.2 stock image to be sure, but I think it more likely that your game needs to be updated.
Rooting does not change your build.prop fingerprint, but the update to 4.1.2 does. This is what the market uses to judge what software will run on your device along with your locale.

adstraylight said:
I don't think there is any link between your root status and software compatibility, you could flash the 4.1.2 stock image to be sure, but I think it more likely that your game needs to be updated.
Rooting does not change your build.prop fingerprint, but the update to 4.1.2 does. This is what the market uses to judge what software will run on your device along with your locale.
Click to expand...
Click to collapse
flashed stock rom. working fine now.
topic can now be closed
thank you

alexzlx said:
Hi
I recently bought a Nexus 7 that came with 4.1.1. I updated ota to 4.1.2 then rooted with a toolkit. For reasons I can't remember I then un-rooted and locked back bootloader. Now, games like dead trigger tell me my device is incompatible with them, even though they ran well on 4.1.1.
What can I do ? Flash another stock version of 4.1.2 ?
Thank you
Click to expand...
Click to collapse
There's a lot of things that aren’t compatible with 4.1.2. I'm still running them. You can make a back up the next time to keep the apps. Or use app back up and restore to make a apk and install it on your N7.
Sent from my SAMSUNG-SGH-I747 using xda premium

Apocalypse487 said:
There's a lot of things that aren’t compatible with 4.1.2. I'm still running them. You can make a back up the next time to keep the apps. Or use app back up and restore to make a apk and install it on your N7.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Actually rooting 4.1.2 with the toolkit changed a setting and thus making the n7 incompatible with tegra 3 games

alexzlx said:
Actually rooting 4.1.2 with the toolkit changed a setting and thus making the n7 incompatible with tegra 3 games
Click to expand...
Click to collapse
Like you can’t install those tegra 3 games from unknown sources?
I have dead space for GB and it doesn't work on ICS or JB, but I backed up the game into a apk and installed it. It worked after that.
Sent from my SAMSUNG-SGH-I747 using xda premium