Related
I have an unrooted hero I have had since launch day. I am now thinking about rooting my hero with use of the latest Sprint leak. my understanding is if you update to the leak of even the official builld whenever that may come out, it will close all current rooting holes available. I guess that doesn't mean in the future there won't be other possibilities. do these new build give the same sense of stability as the official roms because we can now use an official 2.1 kernal?
so from what I have been reading there appears to be only one Rom that is based on the current 2.1 leak and that is flipz Rom? I have a few questions or statements before I do anything to my phone. one, will this help get rid of the lag when typing? two, I need to make sure Bluetooth is still going to work as I have a home phone that I connect my cell to when I enter the door. if I decided to flash back to the official release, is that possible?
dbldown768 said:
I have an unrooted hero I have had since launch day. I am now thinking about rooting my hero with use of the latest Sprint leak. my understanding is if you update to the leak of even the official builld whenever that may come out, it will close all current rooting holes available. I guess that doesn't mean in the future there won't be other possibilities. do these new build give the same sense of stability as the official roms because we can now use an official 2.1 kernal?
Click to expand...
Click to collapse
As of right now; many people are cautious about testing the latest 2.1 leak; because of the concerns you expressed earlier -- having your phone unrooted by the 2.1 leak when you flash the new update. So, with that said; the current 2.1 ROM's are all pretty stable. This new leak, however probably is as well, but again... I don't know whose all tested it, for fear of loosing root access.
dbldown768 said:
so from what I have been reading there appears to be only one Rom that is based on the current 2.1 leak and that is flipz Rom?
Click to expand...
Click to collapse
No. Damageless ROM's are also based on the latest Sprint leaks. All ROM's you see should tell which ROM they are based off of. Almost all 2.1 ROM's are currently built from any of the Damageless ROM's -- just read the front page of the ROM you're looking into.
dbldown768 said:
I have a few questions or statements before I do anything to my phone. one, will this help get rid of the lag when typing? two, I need to make sure Bluetooth is still going to work as I have a home phone that I connect my cell to when I enter the door. if I decided to flash back to the official release, is that possible?
Click to expand...
Click to collapse
1. Possibly. The lag problem is relative to the person/device. Not everyone experiences this problem. However, turning off "Vibrate when typing" apparently helps with the lag issues. YMMV.
2. Please see first post I made.
Thanks for the quick reply. I'm investigating the best way of rooting my phone. I see there are a few ways listed on the wiki, but then i just ran across Fresh Kitchen (http://geekfor.me/new-release/fresh-kitchen-105)? This is suppose to root your phone for you? Is this a stable way of rooting or should i just use the command line mehods? Also, i have read that you should do a nandroid backup of your phone? Not sure if fresh is doing this for you? The other thing i should mention is that i just have a stock microSD card, so I dont plan on using app2sd, i dont think this is a problem correct?
I also see people load their roms using their microSD card and just putting some update.zip file on there. Is this the standard procedure once you root your phone and get a rom loaded?
Actually, Fresh 2.1, and 2.1.1 are the only ones as of right based off of the newest leak (signed with release keys rather then test), Damageless and Treve are currently working on improving DCUpdater, DConfig, and building a new ROM from the release-keys build.
As far as how to root, I recommend the command line method. While the auto-root methods are nice, actually doing it yourself will give you some experience with things you're gonna be using.
Yes, loading the update.zip to the root of the SDCard is the standard way to flash.
No, not using Apps2SD is not a problem, most people use it because they have a faster SDCard, which gives better performance when loading apps.
A Nandroid backup is something that you will do before you flash any update.zip (At least you're supposed to). It's basically an "Image" of your phone exactly how it was the point in time that you made it, so if you flash something and everything goes horribly wrong, you can restore said nandroid, and it will be like it never happened. (The exceptions are flashing a radio and screwing with the PRL/PRI, nandroid doesn't touch those.)
dbldown768 said:
Thanks for the quick reply. I'm investigating the best way of rooting my phone. I see there are a few ways listed on the wiki, but then i just ran across Fresh Kitchen (http://geekfor.me/new-release/fresh-kitchen-105)? This is suppose to root your phone for you? Is this a stable way of rooting or should i just use the command line mehods? Also, i have read that you should do a nandroid backup of your phone? Not sure if fresh is doing this for you? The other thing i should mention is that i just have a stock microSD card, so I dont plan on using app2sd, i dont think this is a problem correct?
Click to expand...
Click to collapse
Fresh's kitchen will allow you root your phone and yes it's stable. However, it's best you try doing it via ADB commands, as there will come a time when you'll want to create things for the community and wished you had prior experience using it. I recommend you trying to root via this tutorial HERE If you follow the directions, you shouldn't have any problems whatsoever.
Stock card is perfectly fine; you're able to use Apps2sd, but don't have to.
dbldown768 said:
I also see people load their roms using their microSD card and just putting some update.zip file on there. Is this the standard procedure once you root your phone and get a rom loaded?
Click to expand...
Click to collapse
To try out different ROM's -- the process is to download the file (which is a update.zip file in itself), but has been renamed to match the name of the ROM. All you have to do is; copy to your sd card, boot into recovery, flash ROM from the sd card, reboot.
abcdfv said:
Actually, Fresh 2.1, and 2.1.1 are the only ones as of right based off of the newest leak (signed with release keys rather then test), Damageless and Treve are currently working on improving DCUpdater, DConfig, and building a new ROM from the release-keys build.
Click to expand...
Click to collapse
There's your real answer. Thanks.
I'm having a hard time understanding why i would need the flash recover image in this tutorial (http://forum.xda-developers.com/showthread.php?t=583291)? I understand i would want to do a backup of the current phones state, but why would i flash anything before actually making this backup? Maybe i'm not understanding the process correctly, but i just want to get "su" ability and then do the nandroid backup? Is the nandroid backup an app i use?
Nandroid is built into the recovery image you're flashing. Before flashing the recovery image, there is no way for you to nandroid.
thanks! after watching the youtube video posting that mad more sense. So i know there is a chance of bricking your phone during all of this, where does that chance increase? Is it during the flashing of the customs roms, not so much the rooting process?
It is safe to say once the "official" 2.1 android comes out there will always be a custom rom based on it? meaning that if chosen by developers here there could be a build off the "official" 2.1 with the only difference is the rooted user is still allowed? I know that most dev are going to change the build in someway to "improve" on what the official build is done.
The only proven way to brick this phone is by flashing a GSM radio, or by having a failed RUU. I've never heard of anyone getting a "true" brick from rooting/flashing ROMs.
Yes, once the official build is released, all ROMs from then on are most likely going to be based of off it.
Ok, stupid question. I just followed the guide to rooting my phone, doing the nandroid backup and copying the backup to my pc. There are a lot of guide to root, but how to you actually flash the custom rom? I saw something about holding down the 'home' button when starting up? Does this bring you to the recovery image again? Do the roms have to be named something specifically?
Place the ROM in the root of your sdcard, and boot into recovery by holding Home+Power. From then select the "Flash update.zip" option and it will show all of the .zip files in the root of your sdcard. Just pick which one you want to flash.
great! thanks for all the help.
ok, so i decided to load damage's sprint leak that would still give me root access, well it doesnt boot. just goes to the "sprint now" screen and reboots over and over again? any ideas?
Did you wipe data and Dalvik?
Anytime you go from one ROM version to another (1.5 to 2.1, 2.1 to 1.6, 1.6 to 1.5, etc etc) you have to wipe, or if there's major changes between rom versions.
what do you wipe the data? i just picked the flash from zip file from sd card?
In recovery there's a catagory for wipe. Wipe data and Dalvik, then reflash and you'll be fine.
cool. thanks. trying that now.
so everything is working now. So i know one of the main benefits of having a rooted is phone is wifi teathering. Are apps like this in the market place or only on here?
There's Easytether and PDAnet. I haven't tried Easytether, since last I've heard it's x86 only, but PDAnet was a horrible experience. I just flashed an Eris based ROM, broke my PRI, and it enabled the built in USB tethering.
dbldown768 said:
so everything is working now. So i know one of the main benefits of having a rooted is phone is wifi teathering. Are apps like this in the market place or only on here?
Click to expand...
Click to collapse
go to market and download barcode scanner
open up barcode scanner and go here and then just point the camera at the qr code and it'll download to your phone.
remember to check 'unknown sources' > setting > applications
wifitether 1.6. works flawlessly on either fresh or damageless latest 2.1
6/5/2011 EDIT : Going to alter this post for two reasons. First, the information inside is pretty old news and stale for most, and not even very relevant for new users. Second, there is STILL confusion between these two branches that needs to be ironed out, imo.
If you are considering modding your new GTAB, I would suggest reading this. It's going to be a long read, but you'd rather not brick your device, right?
Some Terminology Pre-Reqs to Understand
"Soft-brick". The device is not booting up properly anymore, but is potentially fixable by using a tool called "nvflash".
"APX Mode". The is a low-level mode on the GTablet where you can makes repairs and un-brick the device.
"Nvflash". This is the name of the actual tool you use, when you are in APX mode.
"Clockworkmod". This is an alternate recovery tool. It adds a few things that the 1.1-based stock recovery does not have, such as full image backups, wiping user data and SD repartitioning. The 1.2-based stock recovery is a little better, but clockworkmod still has more options than 1.2 standard recovery
"/data partition". This is the area on the device where all your user data and user apps reside. A factory reset will wipe this area.
"/sdcard partition". This is the area on the device where all your content resides. It's also the area that gets mounted on your PC.
"Data wipe" or "User data wipe". This is a factory reset -- all user apps and data will be erased. Content in the device's /sdcard is not touched.
"SD repartition". This is a data wipe and a wipe of /sdcard. So both areas are erased.
"ROM" as defined for use should be considered a BOOT ROM. This is the base program running on your tablet, like an operating system it is the first line of code to load and while not every rom is a full replacement of the viewsonic operating system only one can be loaded at a time. (thanks mERRIL!)
"Kernel" as used here is the tablets details and settings written out so the software knows how to interact with the hardware. This is where things like overclocking can be done, along with changing the way your backlight or wifi utilizes power. (thanks mERRIL for both of these!)
Two Development Branches, and How to Check which version you have
This is the FIRST thing any new Gtablet user should check imo, before you attempt to mod your device. Viewsonic / US Merchants released a new development branch with a new bootloader and kernel (which they later pulled), and older mods do NOT play nice with it. There have been reports that at least a few TigerDirect users have gotten 4349 OOTB.
So, to check which branch you are on if you are on STOCK: Go to Settings -- About Tablet -- Tapu UI Version. If your firmware starts with "1.1", then you are on the 1.1 (old) branch. If your firmware starts with "1.2", then you are on the 1.2 (new) branch. Also an obvious difference between the two is that the 1.2 branch adds a lockscreen to the tablet.
The "Two Cliffs" analogy
Try to think of these two branches as two cliffs. If you are on either side and want to mod your device, the safest way is to use a mod that is built around the branch you are on. Here on XDA Developers site, most of their mods and custom kernels are based on the 1.1 branch (as of this writing). For 1.2 based mods, there are several options but most of them are not posted here on XDA. So you have options regardless of which branch you are on. There is no advantage of using one over the other, except possibly vendor support - 1.1 is still the ROM offered by the vendor, given that their one released 1.2 ROM was pulled.
It is possible to jump from 1.1 to 1.2, and back again. But think of this as a bridge between the two. I have done extensive tests in the last month on this, and it does work MOST of the time if you follow directions. But even when doing everything right , there is still a small chance that you will "fall of the bridge" and into the abyss (soft-brick). And if you attempt to jump between them with clockworkmod, you will fall for sure, 100% of the time. Think of clockworkmod as a "bridge that is out".
The most sturdy bridge, going on my own testing, is the one based on build 1.1-3588 full stock. This makes sense because this is what Viewsonic would want you to be on, before jumping to 1.2. The reverse (1.2-4349 stock, for example) is also fairly sturdy. But again, it is a higher risk than staying within the same branch.
I'm on a 1.2-based stock ROM. What are my modding options?
If you are on the 1.2 branch, there are actually quite a few options right now. The challange for a user is finding them and understanding that you have to be careful if you try to use a 1.1 mod instead (see the "Two Cliffs Analogy", above).
The current 1.2 based options on XDA are:
- Calkulin+Clemsyn 1.5ghz Froyo Combo VERSION 6
- Beasty's 2.2.1 ROM (Adam) + Clemsyn ver 11 1.5ghz kernel
- Clem / roebeet Honeycomb alpha combo (this is a Clem creation and is actually forked from my own HC port)
- Honeycomb Android Illuminate for The Gtablet
The current 1.2 based options NOT hosted on XDA are:
- Century Eyes (Froyo based "EDEN" port)
- Mountain Laurel (Froyo based "TapnTap" port)
- Brilliant Corners (Froyo based "VEGA"/"Viewpad" port)
- Bottle of Smoke (Honeycomb port, currently is a mashup from the Adam and VEGA devs)
Pershoot and Clem both have 1.2 kernels that you can use, as of this writing. Not all of that information is here, some are on other sites.
I'm on a 1.1-based stock ROM. What are my modding options?
On XDA, there are still a number of mod options and customized kernels, at your disposal. Again, a 1.1 to 1.1 mod should be fairly safe to attempt. If you want to jump to 1.2, I would recommend reading the modder's post to see if there are instructions for 1.1 jumpers. If not, the SAFEST way to jump is to flash back to 3588 stock (including stock recovery) and then flash to 4349 using stock recovery - that will get you onto the 1.2 dev branch.
There are still a lot of 1.1-based options, if you want to stick to that path. To name a few:
- VEGAn-TAB (probably the most popular GTAB mod, so far)
- VEGAn-TAB Ginger Edition
- Cyanogenmod 7.x
- G-Harmony
- Calkulin's G-Tab ROM
- TNT Lite (similar to Calkulin's ROM, and currently retired)
- gADAM (currently retired, as well)
There are also a few custom kernels for 1.1, specifically the ones by Pershoot and Clemsyn, here at XDA.
OK, so I've confirmed that I'm on one dev branch but I want to use a mod that's on another dev branch - what do I do?
My suggestions:
1- Read the modder's first post, for possible instructions.
2- If there are no instructions for branch jumpers, DO NOT assume that it's safe to jump. Ask the modder first, to be sure.
I am generalizing here, but the older 1.1 mods might not have instructions for 1.2 users, as you didn't exist at the time the mod was created. Imo, the SAFEST way to jump to a mod that's on another branch is to use stock. So 3588 stock to 4349 stock (using standard recovery) to go up, and 4349 stock to 3588 stock (using standard recovery) to go down. The main reason why it's the safest is because stock has the bootloader image in there, which is required to jump.
I attempted a 1.1 to 1.2 (or vice versa) jump, and now I'm stuck at the birds. Is this a soft-brick?
Yes, it's a soft-brick if you are stuck at the birds. You'll need nvflash the device to fix it. There is information here on XDA on how to do that, or you can find this on other tablet sites.
I attempted a 1.1 to 1.2 (or vice versa) jump, and now I'm stuck at the GTablet screen, or I'm boot looping. Is this a soft-brick?
Probably not - more likely is that you just need to do a data wipe, or a SD repartition if that does not work.
I have a Hannspad (or an Olipad) - does this apply to me?
I believe that it does, going on what I've read. Both these devices seem to be based on the TapUI, and the 1.2 development branch. So attempting a 1.1 GTAB ROM will likely have the same pitfalls. Also keep in mind that even 1.2-based GTAB ROMs have issues. for example, the Hannspad can boot a 1.2-based ROM (like "Bottle of Smoke") but the side keys won't work because the hardware is different. I don't have these devices myself, but I am going on third-party information.
Roebeet, can I safely install over the 3588 Stock Enhancement and Market Fix? I hate to lose the Market but definitely don't want to deal with a brick right now. Another user indicated he/she installed the update over a similarly configured machine and it worked but then applied the Stock Enhancement and Market fix and soft bricked.
I appreciate all the work you do for other users, including me.
interesting!!!
I love my devs!!! Seriously you guys rock!!!
P.S. I am sticking with Vegan GingerEdition
Great post and good info roebeet - stickied for the immediate future.
MSU_Sparty said:
Roebeet, can I safely install over the 3588 Stock Enhancement and Market Fix? I hate to lose the Market but definitely don't want to deal with a brick right now. Another user indicated he/she installed the update over a similarly configured machine and it worked but then applied the Stock Enhancement and Market fix and soft bricked.
I appreciate all the work you do for other users, including me.
Click to expand...
Click to collapse
I haven't tested all scenarios, as there are just too many of them. I specifically picked VEGAn as I know that's a very popular ROM and I could see new stock users flashing to that.
Rule of thumb: If you are going from a 1.1-based ROM to a 1.2-based ROM (or vice versa) and use clockworkmod, you will soft-brick your device.
Great work! More coffee for Roebeet
I guess ... better stick to TNT Lite 4.4 for now.
I am curious about (not in any hurry tho)
cwm+TnT Lite 4.4 ->fixrecovery.sh -> stock 3588 ->OTA 4349
--
msu_sparty.
I ran 3991 for a good while during the time the Wooters needed help.
I tried to install the Enhancement Pack on 3991 and it semi-bricked my
G-Tablet.
I wouldn't try it until someone tests it for sure -- unless you want to
be the tester!!!???
Rev
cbay said:
Great work! More coffee for Roebeet
I guess ... better stick to TNT Lite 4.4 for now.
I am curious about (not in any hurry tho)
cwm+TnT Lite 4.4 ->fixrecovery.sh -> stock 3588 ->OTA 4349
--
Click to expand...
Click to collapse
cwm+TnT Lite 4.4 ->fixrecovery.sh -> OTA 4349. This might work. Haven't tested it yet, but I will. It worked for build 3991, so it might work with 4349.
EDIT: One test, one success. Again, YMMV.
As a new tab owner where do I find the build number please?
Thank you
roebeet said:
cwm+TnT Lite 4.4 ->fixrecovery.sh -> OTA 4349. This might work. Haven't tested it yet, but I will. It worked for build 3991, so it might work with 4349.
Click to expand...
Click to collapse
Does fixrecovery.sh also add/enable the OTA updater? Or is there a update.zip for 4349 somewhere?
thanks for all the work,
--
Can 3588 enhancement be loaded with gapps for android market?
SoCal2 said:
As a new tab owner where do I find the build number please?
Thank you
Click to expand...
Click to collapse
Just go to settings-about device
butchconner said:
msu_sparty.
I ran 3991 for a good while during the time the Wooters needed help.
I tried to install the Enhancement Pack on 3991 and it semi-bricked my
G-Tablet.
I wouldn't try it until someone tests it for sure -- unless you want to
be the tester!!!???
Rev
Click to expand...
Click to collapse
Can you point me in the right direction to unbrick this thing? It semi-bricked mine, and I don't know where to start.
SoCal2 said:
As a new tab owner where do I find the build number please?
Thank you
Click to expand...
Click to collapse
Settings about
Thank god I was impatient and installed vegan 5.1.1 before this happened! Was waiting for ota 3588 before root as I was on 3389 this morning. I'm sure you guys won't be long figuring out if there anything worthwhile here.
cbay said:
Does fixrecovery.sh also add/enable the OTA updater? Or is there a update.zip for 4349 somewhere?
thanks for all the work,
--
Click to expand...
Click to collapse
No, it does not. All it does is flashes back 3588 recovery which is the recovery needed to flash between a 1.1-based and 1.2-based ROM.
yay! what we all knew to be the case a month ago is finally confirmed.
SoCal2,
The version number etc. is at Setting/About.
Rev
just lou,
A good start would be to read this thread. If you can do this procedure, it will NVFlash you back to stock version 2638 -- which we call bekit 1105 a lot.
http://forum.xda-developers.com/showthread.php?t=861950
Once you get to 2638, you can set up wifi and it will fairly quickly bring you an OTA Update notice and you can move up to 3588 -- and you can go where you want
from there.
Rev
Well best I recall mine was running 3588--whatever upgraded when I got it a couple weeks ago.
Sae the upgrade a few minutes ago, and opted to load it.
Now sits at "home", shows current (working) time, that I have linksys, that it is charged ((86%) and that sound is on.
Nothing else works. Oh yes, there is lower right hand icon showing an open padlock.
This came up after upgrade. I've powered off and on a couple of times.
Any recommendations?
I haven't been around for a while and could not quickly get up to date despite going through thread after thread here. I would appreciate some advice and clarification.
First, you guys are saying that GB won't be available for Vibrant, but this article clearly states that it is already available:
“update news! the android 2.3 gingerbread update for the samsung galaxy S vibrant is good to go. connect to samsung kies to hook it up.”
Could you please clarify? The problem is that I downloaded Keys 2.0, but my phone, which is 2.1 and rooted (nothing else done, no roms, etc), is not being recognized. Keys says that my phone isn't supported.
Could you guys please clarify what is really going on in terms of 2.3? Also, how can I get the update? Assuming that the article is false, many here say that 2.3 roms are battery hogs and it looks like I would have to update to 2.2 and then root it. If so, I'd appreciate a link to a pure 2.2 to be installed via Odin. Reading all these threads doesn't convince me that getting a rom, a modem, or a kernel really does that much to improve our phones.
Thanks!
Thats for the Bell/ Virgin Mobile Vibrant theres a difference ya know...
I thought that the phone is the same so it wouldn't matter or perhaps the devs could use it to create a better ROM. If not, I guess the situation is even worse because Samsung actually released the update for Vibrant but T-mobile is refusing to allow users to have it! Clusterf*ck. Steve Jobs was right about android when he talked about market fractionization last year. Oh well.
Ok, well given the bad news, I would appreciate some help from those of you who have flashed your phones to hell and back. I know there are different ROMs etc with different features. I don't use my phone heavily. Actually, the main feature I care about is 1.Good GPS and 2.Good battery life. I go on long cycling trips and my phone is the only thing I use to track my stats (sometimes five hours or longer).
Based on this info, could you guys tell me if upgrading to Android 2.2 be good enough or do any of the ROMs, kernels, and modems provide a clear advantage over stock 2.2? If so, could you recommend a few? Right now my phone is in a very bad shape - the GPS is often dying in mountains and the battery doesn't last much. At this point I have to upgrade just to clean up my phone, especially since it's not clear if/when 2.3 will be released. I am hoping that at least 2.2 should be very stable by now.
only thing in common is the name and the fact that they are both Galaxy S series phones, the canadian bell Vibrant is different hardware then our Vibrant.
I'd say go with something stable such as Bionix 1.3.1 or Trigger 3.2. If you wanna go with 2.2.1 go with a Darky ROM's port or Bi- Winning 3. All good ROMS I'd recommended. Regardless that's what I prefer pperhaps just play around with all types of ROM's you may like something else its not for me to decide.
Sent from my SGH-T959 using XDA App
i would suggest cm7 if u like gb its almost fully functitioning except gps is weak
Would you guys say that you have seen significant performance improvements (~30% or more) of ROMs over rooted stock 2.2? If so, have you also seen significant improvements by adding a kernel and/or a modem?
I know that it's not supposed to be too hard to flash and find out for myself, but I have never flashed anything and evaluating all the different combos can be quiet time consuming. Given that I work and study so much I barely have enough time to date, I was hoping that I could get some succinct advice that will cut my Android pains in half. I have read the thread about different modems and know that something like KB5 is a pretty good modem (still have no idea what it is or where do you get it and how you flash it); however, that thread missed one key comparison - the actual performance and battery improvement of a given modem (and even a kernel) over stock 2.2/2.3 or even over a ROM like Bionix. I'd appreciate any info/links regarding this.
Thanks.
Stop writing walls of text for no reason ... kernel will make your phone faster, particularly if you enable voodoo lagfix (helluvah lot faster >30% over stock)... modem will not make it faster but may make your data connection faster and battery last longer as well as morr signal ... look for the modem page for dl link....
Now go flash a rom!! All the roms here are amazing and huge improvements over stock, as are the kernels. Suggestions??? Print out all the names, put em on notecards and throw a dart... flash whatever you hit.
Sent from a cell tower to the XDA server to you.
Bell vibrant is completely different from ours ... the 2.3 for them is no help to us.. lol were not lying to you
Sent from a cell tower to the XDA server to you.
None of the Gingerbread roms are anywhere near where some of the Froyo roms are.
Team Whiskey Bionix 1.3.1 is the best I've used. NextGen V2 isnt' bad either. I just tried Simply Honey 5 RC1 and CM7 nightly #84. Out of the 4 roms I just listed, I flashed back to Bionix 1.3.1. It has the best speed and is the most stable I've ever used.
If you don't have the time to read about flashing your phone, I would suggest you either not do it or pay someone to do it for you. Set aside 2-3 hours if you want it done properly otherwise say goodbye to your phone.
I am in SoCal too and wouldn't mind paying someone to do it for me. The problem is then a whole other set of headaches: how do you trust someone to get hold of your private info? What about doing a good job? Arranging a pickup/dropoff, etc, etc. Also have no idea how much people charge for this service. Expensive enough and it might just be worth it to get a new phone, especially after I sell the Vibrant. Maybe that's what many of us need to do.
Im sure you can find someone nearby thatll do it as a favor and let you watch... problem solved
Sent from a cell tower to the XDA server to you.
I would never pay anyone to flash anything for me. Its a simple process.
To figure out what ROM's go good with what Modem I would go to this thread http://forum.xda-developers.com/showthread.php?t=959088 and a good kernel would be Bali or SuperDragonModz both great.
Excelsius said:
I am in SoCal too and wouldn't mind paying someone to do it for me. The problem is then a whole other set of headaches: how do you trust someone to get hold of your private info? What about doing a good job? Arranging a pickup/dropoff, etc, etc. Also have no idea how much people charge for this service. Expensive enough and it might just be worth it to get a new phone, especially after I sell the Vibrant. Maybe that's what many of us need to do.
Click to expand...
Click to collapse
I recommend listening to some of the other folks in the thread and flash bionix 1.3.1. The stock kernel is fine, as is the modem it ships with. Battery life will be as good as just about anything else.
If you really want to flash a custom kernel, go with Bali 1.8.8. Battery life will be similar, but that kernel has some additional features like voodoo sound, which uses the audio hardware more effectively. If that doesn't seem like something you care about I wouldn't worry about it.
The only catch is that you will need to flash bionix through CWM recovery, there are no prepackaged odin files that I am aware of. There are numerous threads to help you getting CWM installed, just check out the stickies.
Don't pay anyone, if your still not comfortable flashing anything, but you still really want to, PM me and I'll help you through it.
Thank you so much for the more precise advice. That's exactly what I needed. It's not that I want to upgrade, but rather that I have to because my phone has become unstable. It freezes almost every time I open Voice or Maps, among other problems.
So I will get the Bionix 1.3.1 and worry about Bali 1.8.8 at a later time. I came across this guide: http://forum.xda-developers.com/showthread.php?t=925400
Is it the guide for CWM? My phone is rooted (ODIN) and has paid version of Root Explorer and BusyBox. I was wondering if I still have to install SuperOneClick or if my root is fine already.
By the way, I'd appreciate a link to some guides that you guys have used to install your Bionix. I read this: http://forum.xda-developers.com/showthread.php?t=732458, but the CWM and Rom Manager points are moot. Like I don't know if installing Rom Manager already includes CWM with it. Here are the steps:
Installation instructions:
1.Download ROM Manager from the Market.
2.Flash Recovery.
3.Choose Vibrant as your phone.
4.Accept the Superuser prompt.
5.On the very FIRST boot of Clockwork, you may need to manually select "reinstall packages" if Clockwork does not start. You should only ever have to do this once. It will be automatic from then on.
6.Watch the backup go!
If this is it, then I'll just do it (after I do a nandroid backup, which will hopefully backup all my paid applications).
I'm in SoCal, running Cyanogen7 nightly 81. (Android 2.3)
I am running Bali, and did both the hardware GPS fix, and the software GPS fix using the terminal scripting.
I get around 10-12 locks, accuracy tends to be in the 12-14 foot range, so the GPS works flawlessly.
I've been a lurker on these forums for a LONG time now, but decided to register and post to kinda give back. In this case, to someone looking to fix up their Vibrant.
If you're interested, PM me. I work for Microsoft, and you're welcome to stop by and I'll show you everything I've done. (Yes, I have an Android phone, and a WP7 phone, both of which I love) If you like what you see, (You will) I'll set your phone up as my way of kinda returning all of the favors other users on this site have done for me, even though they didn't know it.
Excelsius said:
Thank you so much for the more precise advice. That's exactly what I needed. It's not that I want to upgrade, but rather that I have to because my phone has become unstable. It freezes almost every time I open Voice or Maps, among other problems.
So I will get the Bionix 1.3.1 and worry about Bali 1.8.8 at a later time. I came across this guide: http://forum.xda-developers.com/showthread.php?t=925400
Is it the guide for CWM? My phone is rooted (ODIN) and has paid version of Root Explorer and BusyBox. I was wondering if I still have to install SuperOneClick or if my root is fine already.
By the way, I'd appreciate a link to some guides that you guys have used to install your Bionix. I read this: http://forum.xda-developers.com/showthread.php?t=732458, but the CWM and Rom Manager points are moot. Like I don't know if installing Rom Manager already includes CWM with it. Here are the steps:
Installation instructions:
1.Download ROM Manager from the Market.
2.Flash Recovery.
3.Choose Vibrant as your phone.
4.Accept the Superuser prompt.
5.On the very FIRST boot of Clockwork, you may need to manually select "reinstall packages" if Clockwork does not start. You should only ever have to do this once. It will be automatic from then on.
6.Watch the backup go!
If this is it, then I'll just do it (after I do a nandroid backup, which will hopefully backup all my paid applications).
Click to expand...
Click to collapse
If you already have ROM manager, and have "Flashed Recovery" then you have Clockwork Mod. At this point, should be able follow the Bionix instructions after the CWM point.
Nandroid backs up EVERYTHING, including the Android OS version you are running. If you want to back up just your apps, use Titanium Backup, the premium version lets you do a "One touch" batch restore of all user apps. One thing to remember about Titanium: do NOT back up system data. Easiest rule of thumb for it, "Menu--> Batch--> backup all user apps" then let it do it's thing. flash your ROM, then go into Titanium (Almost positive the free version is part of Bionix) "Menu--> Batch--> Restore missing apps with data" If you have the premium version, you can restore them all with no further input, if you have the free version, you will have to accept and install each app as you go, but they all come back with your saved data.
If you are going to do a FULL wipe (Format storage so the phone is empty) first connect to USB Storage, and move your "Titanium Backup" folder from the root of your internal SD card to your PC. Then, before you run titanium for the first time after wiping, reverse the process. Apps are back.
Excelsius said:
Thank you so much for the more precise advice. That's exactly what I needed. It's not that I want to upgrade, but rather that I have to because my phone has become unstable. It freezes almost every time I open Voice or Maps, among other problems.
So I will get the Bionix 1.3.1 and worry about Bali 1.8.8 at a later time. I came across this guide: http://forum.xda-developers.com/showthread.php?t=925400
Is it the guide for CWM? My phone is rooted (ODIN) and has paid version of Root Explorer and BusyBox. I was wondering if I still have to install SuperOneClick or if my root is fine already.
By the way, I'd appreciate a link to some guides that you guys have used to install your Bionix. I read this: http://forum.xda-developers.com/showthread.php?t=732458, but the CWM and Rom Manager points are moot. Like I don't know if installing Rom Manager already includes CWM with it. Here are the steps:
Installation instructions:
1.Download ROM Manager from the Market.
2.Flash Recovery.
3.Choose Vibrant as your phone.
4.Accept the Superuser prompt.
5.On the very FIRST boot of Clockwork, you may need to manually select "reinstall packages" if Clockwork does not start. You should only ever have to do this once. It will be automatic from then on.
6.Watch the backup go!
If this is it, then I'll just do it (after I do a nandroid backup, which will hopefully backup all my paid applications).
Click to expand...
Click to collapse
The steps you listed are correct. You also of course need to have downloaded the bionix 1.3.1 zip file and placed it somewhere on your SD card (I make a ROMS folder on mine). As the instructions noted, you'll have to do reinstall packages twice (ie you do it once and the phone reboots into recovery and it looks like nothing happened, you do it again and go immediately to CWR recovery where you can select "install ROM from SD" or similar). From this point on you won't have to worry about CWR recovery, it will always be there. As StarGazer mentioned, when you flash this it will wipe your phones settings and all the apps (but not the SD card). There are a variety of backup apps that can help restore them, but I usually don't mind starting fresh once in a while, especially if your contacts are stored on Google.
Finally, once the bionix finishes flashing and the phone reboots for the first time, expect to hear a voice start talking to you about backing up partitions, estimated times, etc. This is the "voodoo lagfix" being applied, which is converting internal phone partitions from the Samsung RFS to ext4, which noticeably reduces lag on the phone when opening apps and so forth. Good luck
Thank you for your help, everyone. I was able to dedicate a few hours and just take care of it since it didn't feel right to waste someone else's time. Please note that I haven't PMed anyone and if there are readers here who are technologically challenged, perhaps they can take my place and get help from some of the generous people who offered help here.
I currently have Bionix 1.3.1, Bali 1.8.8, and KB5.
To give back to the community, I wanted to post benchmarks. I have some amazing results:
Android 2.1 (everything stock, rooted) - Quadrant benchmark 852 (average of 2 tests)
Bionix 1.3.1 (with stock kernel) - 1504 (average of 3 tests). That's a 43% improvement! Now this is likely due to Android 2.2 rather than Bionix. It's definitely worth going from 2.1 to 2.2.
Bionix 1.3.1 + Bali 1.8.8 (after adding the kernel) - 1852 (average of 3 tests). That's 19% more than stock 2.2 and 54% more than 2.1! This isn't 30%+ improvement that some people here think kernels provide, but ~20% is still not bad, considering that battery life is also very important.
Now as far as the KB5 modem goes, I saw no improvements using GPS Test and Speed Test. My GPS is still at about 50ft accuracy and internet speed is 6000x2300kbps. The real test will come during my 60 mile ride on Saturday.
Right now I am only hoping that the battery will last at least as long or more than on 2.1, despite the kernel.
Question: before flashing with Bionix I had applied the software GPS fix to my phone a year ago. Do I have to do it again or does Bionix already include the software tweak?
Once again, thanks everyone.
P.S: My clock on the phone is off by two minutes from the atomic clock. I noticed that the "Autoupdate" of date and time message doesn't appear when I start the phone. Is there a time syncing issue with Bionix?
I bought it and it appears to have ICS because the Android version is 4.0.3 but that is all I really know right now. I expect that it was never updated OTA though because the guy I bought it off had it for 2 months and he was not the one who rooted it. I was going to leave it as is because I bought it for my 10 year old daughter...but the camera takes very blurry, kind of grainy looking pictures.
I am not afraid to root because I had a Samsung Fascinate and I loved the custom roms I downloaded to it. It had been over a year since i had the Fascinate so i am a little rusty when it comes to all if this. My problem is not knowing where to start with this A500 because I am unsure what has already been done to it.
The guy who sold it to me said he did a factory restore, but when I ran the check root app it does state that it's rooted and I figured it was because there is a app called superuser on the device. I don't know what kernal it has. I don't know if it has a bootloader and/or the version number. I don't know if it has CWM and/or the version. number.
What is the best way to proceed? By the way, the tablet is very clean with absolutely no scratches anywhere. Not a bad buy for $175 with a leather case...
Setting > About tablet. That should tell you quite a bit of info about it no?
download the acer recovery app , it will tell you what Bootloader you have and what recovery
Thanks for the replies! When I get home I will check. I don't want to brick the thing. I ordered a micro SD today and I will get it in 2 days so there is no hurry for me to proceed. Is it worth it to keep it rooted? Is the OTA ICS good enough? I don't think my daughter cares if the tablet is overclocked but if the roms are much better than stock than I would keep it rooted and then download a preferred rom.
Vintage144, in another post you specified that there is a Acer recovery beta...will I need that or would I just get the one from google play? Also when I find out which version of recovery and bootloader I have...I am not sure what to do with the information. Could AfterOta help me accomplish what I want if my goal is to try and fix her camera issue...either by going back to stock or updating the kernal and rom.
I don't want to seem like a noob but my only rooting experience was with my Fascinate which I did everything from stock. Now that I am not coming from stock, I am unsure where to go with what I have. It's like trying to get to a goal but not sure what step to start at. If I was starting from stock I could follow some of the threads here but it's not stock.
What info will I need to post here to let you guys know what is in my A500? I know that the Android version is 4.0.3 , what else will I need to post?
well the beta copy I believe is at thors tegra forum , but its by euclids brother (thats his name on xda) anyway if you've upgraded your BL it will tell you version you have and might give you accurate Recovery as well, if the device is only for your daughter and she's too young to really do anything I would stick with a stock rom and realistically I would upgrade the boot loader , why be left behind?
Theres no reason to root if you dont plan on doing anything major with it,that being said you wont be able to get a newer Boot Loader or custom recovery without it, and custom recovery is well worth the effort!
You guys are the pros so I will take your advise. I don't mind it being rooted and if there are some really nice roms I expect my daughter would like the different looks...it would seperate hers from others.
Android
4.0.3
Kernel version
2.6.39.4+
Image version
Acer_AV041_A500_RV16RB02_WW_GEN1
Build number
KJY2010lcylicious
Anything else I will get when I get home.
I would like to know how to get through all this in case I decide to get myself a A500 it's a really nice tablet.
Okay
Recovery Version: Revamped for Iconia 3.16
Bootloader Version: 3.01
With all the above information what would be my next step?
Sorry
Recovery Version: RA Revamed for Iconia 3.16
Damn auto correct!!!
You're already running an older custom rom...
You have root - your words not mine...
You can download another custom rom, put it on the sd card/ internal memory and reboot into recovery. You need to wipe cache, dalvik cache and do a data wipe(factory reset) after which you can install zip from sd card. Go to the rom zip file you put there and install...
Wait until it boots...
I don't know if you're running the new ICS bootloaders or not.
BEFORE FLASHING - make a nandroid backup. If things go bad then you can go back and restore the tab to before the flash...
It's worth getting your CPUID and keeping it safe somewhere and you might think about installing the ICS bootloaders (I'd do it just to be sure I have them) but thats you're choice...
Good luck...
ultramag69 said:
You're already running an older custom rom...
You have root - your words not mine...
You can download another custom rom, put it on the sd card/ internal memory and reboot into recovery. You need to wipe cache, dalvik cache and do a data wipe(factory reset) after which you can install zip from sd card. Go to the rom zip file you put there and install...
Wait until it boots...
I don't know if you're running the new ICS bootloaders or not.
BEFORE FLASHING - make a nandroid backup. If things go bad then you can go back and restore the tab to before the flash...
It's worth getting your CPUID and keeping it safe somewhere and you might think about installing the ICS bootloaders (I'd do it just to be sure I have them) but thats you're choice...
Good luck...
Click to expand...
Click to collapse
Probably want to hold off on flashing roms a second.
He's running an HC Bootloader. I'm 99% sure of this. Reason, RA Revamped 3.16 doesn't work with ICS Bootloaders. So you can install an ICS Rom, but, it has to be an ICS Rom for the HC Bootloader. And the performance under HC BL is not near as good as ICS BL.
I would do like UltraMag mentioned as far as install steps and such. It's how we install roms.
Check this thread;
http://forum.xda-developers.com/showthread.php?t=1622425 (steps 1-6)
, and install an unlocked ICS Bootloader and a CWM 7 or 7.2 recovery. Then install one of the Roms made for the ICS Bootloader.
I know AfterOTA will do some of this for you. But this thread gives a good idea of what's going on.
Thanks for your help. I will be getting my micro sd card on Friday. In the mean time I will do a bunch of reading about the things you guys told me to do...again thanks a lot. I really appreciate the help.
I am the kind of person that really wants to know what I am doing...I don't expect all the answers, I just don't want to brick this device.
Forstir9,
Moscow Desire is a great dev on this board, his information about updating the bootloader is dead on. I recommend reading the entire OP in that thread, and then re-read section listed as Automated Flashing Tools, it really helps tremendously if you are a person familiar with root, but not extremely dynamic with making these changes.
I've rooted several BN Nooks and my A500 many many times and love it. I had the Honeylicious ROM that you listed prior to what I'm currently running. KYJ had a great HC ROM with that one! Personal preference currently for me on the ICS ROM is FLEXREAPER from Civato, poster of the referenced article from MD above, you can find that ROM info here: http://forum.xda-developers.com/showpost.php?p=22964651&postcount=1 Lots of cool features and step by step directions, which are what UltraMag69 listed in their post. There are many many different options though and I recommend reviewing several and then settling in on one when you find the one that fits your (or your daughter's) preferences best.
If you enjoy doing this and playing with the tablet your daughter may not keep it and may end up getting something different, because you may have too much fun with it...good luck, have fun, don't be scared to try things and ask questions (after you read first), and most importantly BACKUP BACKUP BACKUP...
Good luck,
-DB
Let me get this straight then.
1) boot into recovery and make a nandroid backup.
2) within that backup I should be able to find the CPUID on my sdcard...I will want to write this down and the write it down again somewhere else...out this number on my phone and computer...pretty much don't lose this number.
3) follow steps 1-6 from the link that Moscow Desire posted.
I am going to go with the Flexreaper rom...should I go with the extreme one or is there another Flexreaper rom that isn't extreme?
4) I think the 6 steps above will install a ICS bootloader
5) find and install the newest recovery
I only have 2 questions
How many of these steps does the Afterota app get Rid of?
Should I use the Acer recovery app to install the bootloader and/or the recovery?
forstir9 said:
Let me get this straight then.
1) boot into recovery and make a nandroid backup.
2) within that backup I should be able to find the CPUID on my sdcard...I will want to write this down and the write it down again somewhere else...out this number on my phone and computer...pretty much don't lose this number.
3) follow steps 1-6 from the link that Moscow Desire posted.
I am going to go with the Flexreaper rom...should I go with the extreme one or is there another Flexreaper rom that isn't extreme?
4) I think the 6 steps above will install a ICS bootloader
5) find and install the newest recovery
I only have 2 questions
How many of these steps does the Afterota app get Rid of?
Should I use the Acer recovery app to install the bootloader and/or the recovery?
Click to expand...
Click to collapse
First off. Thanks for thinking I am the "God" of the 501". Yeah, I know it pretty well.
Second, Ultramag, is is one of my right hand men. So I suggest you heed his advice well. I always trust his judgement. Am sure he has puled my arse out of the wringer a few times. Well, maybe not, but you get the picture. Some of us on XDA, support each other. That's how it is. I just noticed the bootloader version, And being one who likes flashing experimental code, well, I noticed.
So;
1. ALWAYS make a recovery backup. Then, restore it to make sure it works. (lots of people don't do this and they get fubar'd later).
2. UID. Seriously. Ok, the link on the many ways to get it. You don't want to get it, well... your;e pretty much fubar'd
http://forum.xda-developers.com/showthread.php?t=1624645
3. He has the normal, and one with a kernel you can overclock. Your choice. Really, if you don't OC, then you run the same as the original. Please don't ask me the names of Civatos roms. The extreme will be fine for you. Just don't overclock it if you don't want to. Only difference is the kernel. Not the OS.
4. Yes.
5. For recovery, I would say CWM 1.7.2. Should work for you. 1.7.0 is also ok. Publick recovery is ok too.
6. Never ran After OTA. But hear it is good when you already have ICS.
Forget AcerRecovery. You will already have bootloaders and recovery installed.
MD
Know I'll probably get a bashing out of this but there's a V1.7.3 recovery on the site that must not be named (cough, tegraowners, cough) that supports the Aroma installer - on Thor's ICS rom anyway...
Just thought I'd throw that in too...
I am ready to do a backup...it's asking me what I want to backup...it has a (X) next to the following...
Boot
System
Data
Cache
Flexrom
Is this correct the way it is?
EDIT: ignore this post I didn't see page 2 -_-
Sorry that I didn't post this in Friday...but I really want to thank everyone for their help. It went very easy and it want too much different than my fascinate.
The camera still takes grainy pictures and a few apps has sounds issues but she really likes the rom a lot.
Thanks again for the help.
So I am new to the whole Root and ROM Android arena. And I came up with a few questions that hopefully you guys can help me with.
1. I read people saying they lost their ROOT after an update from 4.1 to 4.2 or 4.2.1 to 4.2.2? How did this happen for them?
Do you have to Un-root and flash to stock before updating to a different build (Such as 4.1 to 4.2 or 4.2.1 to 4.2.2)?
2. Right now I am using a custom ROM on Android Version 4.2.2.... if a new Custom ROM with a new android version released (Let's say 4.2.3) can I flash from one Rom to the other with just wiping Cache/Factory wipe and Dalvik Cahce or is there something else I would need to do because of the Android version update?
Sorry those two questions above are very similar but I wanted to ask them both ways.
3. If I were to get bored of the Custom ROM I am currently on. Are there any Best Practices "rules" I should know about when switching from one custom ROM to another?
4. Last if I am on a custom ROM with a nightly build..... is it more common to update to every nightly build that releases? Or is it more common people to only pick and choose choice nightly build versions. And if people do update to every new Nightly build.... can you update too much and destroy your device?
Sorry guys I know these seem like very basic questions..... and Yes I did search the forums. However while I found some very basic answers nothing went into great depth in explanation. All the answers seemed to be very vague.
does anyone have some suggestions on where to find these answers?
1. If you are on stock, rooted, and you update versions of the OS, you are essentially UPDATING the /system partition. That is how you lose 'root' when upgrading. If you modify any system files while rooted, you have to either revert to stock or change those modified files back to the original before running the update.
2. Just run FACTORY RESET in your custom recovery and flash the new custom rom. No need to wipe any caches (/cache is wiped during a factory reset anyway). It doesnt matter what version to what version. Sometimes new versions might require new bootloaders, but you will be bombarded with that information here if that becomes the case.
3. See number 2. Its the same thing. backup your apps with Titanium Backup, do a Factory Reset in custom recovery and flash new rom....done.
4. doesnt matter. you can update as much or as little as you like. some people prefer stability over new shiny, but then others are just crack-flashers....and will literally flash ANYTHING posted to see what happens
Pirateghost said:
1. If you are on stock, rooted, and you update versions of the OS, you are essentially UPDATING the /system partition. That is how you lose 'root' when upgrading. If you modify any system files while rooted, you have to either revert to stock or change those modified files back to the original before running the update.
2. Just run FACTORY RESET in your custom recovery and flash the new custom rom. No need to wipe any caches (/cache is wiped during a factory reset anyway). It doesnt matter what version to what version. Sometimes new versions might require new bootloaders, but you will be bombarded with that information here if that becomes the case.
3. See number 2. Its the same thing. backup your apps with Titanium Backup, do a Factory Reset in custom recovery and flash new rom....done.
4. doesnt matter. you can update as much or as little as you like. some people prefer stability over new shiny, but then others are just crack-flashers....and will literally flash ANYTHING posted to see what happens
Click to expand...
Click to collapse
Thanks I really appreciate the response. :good: You'd be surprised how many "Tiny Parts" of answers you get from searching. Very rarely the whole answer you need.
I am glade to hear that Question 2 only requires you to just factory rest. From the misinformation gathered on other forums... I was starting to think you had to flash back to stock before updating to another Custom ROM Build.
@20mmrain
You've probably looked at a number of posts by confused newbs. For better or worse, this site is nothing like a moderated wiki, so you find treasure mixed in with trash.
Rooters fall into four broad classes:
(a) Those that "root & modify" stock ROMs
(b) Those that abandon stock and use custom ROMs and kernels
For each of the above cases, there are diligent and careful users who make full (nandroid) backups... and lazy idiots who do not. It is almost always the lazy idiots you observe coming in here in a panic, independent of whether they are in class (a) or (b).
Beyond that, newbs taking approach (a) seem to perpetually labor under the false impression that their modified versions of a stock ROM should be able to be upgraded by the OTA process - when in fact that there is absolutely no reason to believe that. The OTAs carefully check hundreds of different files before they perform any changes; if even a single one of them has been altered, the OTA aborts without making any changes.
It is *possible* that if none of those hundreds of files are changed that an OTA will succeed on a "nearly stock" ROM. When this happens though, it is quite typical that:
- the "su" binary (part of a root kit) in either /system/bin or /system/xbin gets its' setuid permissions reset by a recursive permission-setting command in the OTA
- the custom recovery can possibly be overwritten by the new stock recovery.
Folks tend to refer to either of the above as "losing root". True in principle, but they are trivially fixed up - if the user actually understands how Android rooting works. (With fastboot, you simply reflash the custom recovery, boot into that and reflash the same root kit originally used).
It's too bad that folks who put together rooting guides seem to neglect putting an emphasis on making backups. They give you both security and freedom.
Bottom line: whatever you choose to do, make nandroid backups. You don't need to keep them all on the tablet - but for convenience reasons, you should have at least one known good ROM as a backup available to be restored.
good luck
Wow that is a really in-depth explanation and that is exactly what was looking for! Since I have been working in the IT world for years I will say with pride that I am an individual who believes in safety first and always back up any important project I am working on! So I am happy to hear I made the right decision there.
I guess a great deal of my questions also stem from working in a windows based world for so long ....that I am still learning Linux/android.
Right now I do keep a nandroid backup on my nexus 7 but only one. How backups do you have? And do you just keep the rest on a thumb drive?
Sent from my Nexus 7 using xda app-developers app
20mmrain said:
Right now I do keep a nandroid backup on my nexus 7 but only one. How backups do you have? And do you just keep the rest on a thumb drive?
Click to expand...
Click to collapse
At the moment I have 6 on the tablet - all generated in the last 60 days. Two in the last two days (one a rooted stock/jdq39, another a cm10.1 nightly). Plus recent TiBu market app & data backups. 32 GB model, so I have plenty of room.
That doesn't reflect any particular strategy or goal. I hook it up to a PC every once in a while and at that time either copy off any backups worth saving or delete them. Most of the those I have on the PC will eventually be deleted as well without ever being used. You could use a USB key if you want to. Really you only need to keep one on the tablet - mostly as a convenience in case you wedge your daily driver ROM with some random mod: you can restore a working ROM right from your tablet rather than having to find a USB key or return to your PC to get the tablet booting again.
There is one type of ROM backup that I think is very useful to keep a permanent copy of - a pure stock ROM. The reason for that is that any radio images (tilapia) or bootloader upgrades that are *sometimes* delivered by OTA can be trivially installed by:
- make a backup of the current ROM
- restore a pure stock ROM backup (including the stock recovery! ***)
- take the OTA
- ***soft-boot a custom recovery and make a backup of the NEW stock ROM (including its' recovery!)
- hard-flash the custom recovery to the tablet
- restore the backup from the first step above.
Doing things this way is the safest possible way to install either a bootloader or a radio image. Not only that, but for folks that prefer to mod stock ROMs, it gives them a backup archive of /system to recover arbitrary (stock) files from.
*** soft-booting a recovery is the most convenient way to capture a stock recovery as part of a nandroid backup. I.E.
Code:
fastboot boot recoveryimagefile.img
If you hard-flash a custom recovery before you make a nandroid backup of a stock ROM, you lose the opportunity to get a copy of the stock recovery along with the rest of the stock ROM.
good luck