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?
It's been ages since I rooted anything and find it hard for me to get back on board with everything/lingo/acronyms..etc! (ok did use autonooter back in the day but reverted back to stock and changed to dual boot with CM7 on SD card). I use the BN Read to Me capability with the kids.
I have a few questions.
1. How can I determine what version CM7 I have? I am assuming it is 7.0.3 based on the below information I get from it (and sorry can't remember when I made the SD card)
*version CM7 07022011 nightly encore
*Android 2.3.4
*Kernel 2.6.32.9 [email protected] #103
2. If I have 7.0.3, is there really any purpose for 7.1.0? I use my NC for web browsing, reading, some games, and hopefully some basic video watching. I read the change log but most of it went over my head---I didn't think I saw anything critical for Common or Encore but I could have missed something. I am patient enough to wait for a stable CM9 with ICS but just need issue #3 resolved since everything else is working fine!
3. Back when I made the SD card Netflix was not working....I didn't care as I was a Blockbuster user....but now I have made the switch and would like it. I tried to get it from the market but it tells me my device isn't compatible for the application. Can someone tell me how to get it? I tried searching but most of the results came up regarding the recent BN update. ***ok...got this one fixed***
4. And lastly, if I boot using EMMC my NC automatically will update to the BN 4.1.0 version right? If so will this mess up my dual booting? I tried to find answers to this but after trying various search strings I never found a clear answer. I am almost positivethe answer to the first question is yes, but my real concern is the second question. I do not want to block the update as I would actually like to have some of the new features...especially since I am a fan of Marvel comics....
5. Ok...lastly...lastly....I know I can switch where NC boots from with pressing the n button, but sometimes I forget how..or miss it and have to reboot...are there any options out there to just have it ask you what you want when you reboot/restart/power on? Not when coming out of sleep...I understand that is not possible.
TIA!!!
1. How can I determine what version CM7 I have?
Open up CM7, go to Settings/About Tablet/Mod Version
2. If I have 7.0.3, is there really any purpose for 7.1.0?
If you're ok with battery life, and everything works, probably not. I'm still on 7.0.2, waiting either for ICS or 7.2 final (it's at RC status). There may be some annoyances and things that would invovle a lot of work (HBO Go, for example) that might be easier in 7.2, but there are other things like the Sleep of Death (should be fixed in 7.2) that showed up in the 7.1 stable/nightly releases.
3...you have it fixed, but I'm still using this http://forum.xda-developers.com/showthread.php?t=1078123&highlight=netflix to avoid the "device not compatible" problem. Then again, I'm on an old CM7
4. Really depends on how you root. I think using CWL blocks the update, so you'd probably have to remove that, but I'll defer to those who root (I boot from SD for CM7).
5. I think that's fixed in the later version (7.2 RC), but if you want to stay for now on 7.0.3, check out this thread: http://forum.xda-developers.com/showthread.php?t=962708
Also, this thread really is useful...it's a long one now, but lots of information here (it's the method I've used to dual boot CM7): http://forum.xda-developers.com/showthread.php?t=1000957
And don't forget to thank Verygreen!
I am curently running my nooks eemc as stock for reading and is upgraded to 1.4.1 non rooted to keep the warrenty going, and i have setup two sd cards. The first is a 16gb, set up with cm7 nightly 253. Runs stable and have netflix working great with the market app. the 2nd is an 8gb sd and is set up the dualboot cm7 and cm9 you can get from development section. cm9 runs ok but video is not working yet with this rom yet.
Hey guys. Hope that someone can help me out here, I'm stuck trying to load a new ROM on a friends Iconia A500.
I searched the internet for a simple rooting tool. Came across Blackthunder, used it to root the Iconia. Rooted without any problems. Afterwards I download the Acer Recovery tool from the market. Flashed with CWM.
Problem is that when I reboot into recovery it keeps on saying "booting recovery kernel image", nothing happens. On my own Transformer I just boot into CWM and flash with whatever I'd like.
Can someone please guide me to a step by step tutorial, or explain what I did wrong here?
Cheers!
ldeijkva said:
Hey guys. Hope that someone can help me out here, I'm stuck trying to load a new ROM on a friends Iconia A500.
I searched the internet for a simple rooting tool. Came across Blackthunder, used it to root the Iconia. Rooted without any problems. Afterwards I download the Acer Recovery tool from the market. Flashed with CWM.
Problem is that when I reboot into recovery it keeps on saying "booting recovery kernel image", nothing happens. On my own Transformer I just boot into CWM and flash with whatever I'd like.
Can someone please guide me to a step by step tutorial, or explain what I did wrong here?
Cheers!
Click to expand...
Click to collapse
Well, the big question...Which version of android do you currently run?
Which version of CWM did you try to flash?
Second question, which bootloader are you currently on? To find out, just run the acer recovery app and it will tell you when it starts.
And finally, which rom are you trying to install.
Then we can give you a more precise answer.
MD
Thanks. I managed to make a few steps in the right direction.
New problem though. I managed to get CWM working correctly. It feels a bit buggy, with some backbuttons not responding. Downloaded Lightspeed 4.7., seems like the fastest rom out for the Iconia.
Factory reset + /system format. Installed the zip, everything looks ok.
When I boot up the tablet the first few seconds the screen looks fubar'd. Like a really nasty system crash, with white lines running all over the screen. Afterwards you get a standard boot animation & ICS loads up. If you put the tablet on standby though it goes into deep sleep after about 10 minutes.
I downloaded Taboonay just to be sure it's something in the rom. Taboonay works, but feels significately slower.
ldeijkva said:
Thanks. I managed to make a few steps in the right direction.
New problem though. I managed to get CWM working correctly. It feels a bit buggy, with some backbuttons not responding. Downloaded Lightspeed 4.7., seems like the fastest rom out for the Iconia.
Factory reset + /system format. Installed the zip, everything looks ok.
When I boot up the tablet the first few seconds the screen looks fubar'd. Like a really nasty system crash, with white lines running all over the screen. Afterwards you get a standard boot animation & ICS loads up. If you put the tablet on standby though it goes into deep sleep after about 10 minutes.
I downloaded Taboonay just to be sure it's something in the rom. Taboonay works, but feels significately slower.
Click to expand...
Click to collapse
Glad you made some steps.
You still didn't answer my questions about bootloader.
The reason you got the screwy screen on boot, is because that rom you tried to install, used a "hacked" kernel so that ICS could run on an HC bootloader. It's perfectly normal. The deep sleep you refer to, is called SOD, (sleep of death) and usually you have to reboot.
This is why I asked which bootloader you were currently running. Because it makes a big difference since the release of ICS. Acer changed the playing rules.
Once again I ask you, to run AcerRecovery, and just get the version bootloader you are currently running. Upgrading to the ICS Unlocked bootloader makes things a whole lot smoother.
MD
Hmmm, thought it had something to do with that.
Installed Acer Recovery Installer. Am on bootloader version 0.03.11-ICS
Recovery version CWM rev1.7 (v5.5.0.x). Asus Transformer has it's fair share of SOD's, but those are random. With the Lightspeed rom I tried it was like clockwork.
Should i upgrade the bootloader to a newer version? Do you have any idea what's causing the SOD's?
ldeijkva said:
Should i upgrade the bootloader to a newer version? Do you have any idea what's causing the SOD's?
Click to expand...
Click to collapse
Moscow Desire said:
The reason you got the screwy screen on boot, is because that rom you tried to install, used a "hacked" kernel so that ICS could run on an HC bootloader. It's perfectly normal. The deep sleep you refer to, is called SOD, (sleep of death) and usually you have to reboot.
Upgrading to the ICS Unlocked bootloader makes things a whole lot smoother.
MD
Click to expand...
Click to collapse
nuff' said,.
ldeijkva said:
Hmmm, thought it had something to do with that.
Installed Acer Recovery Installer. Am on bootloader version 0.03.11-ICS
Recovery version CWM rev1.7 (v5.5.0.x). Asus Transformer has it's fair share of SOD's, but those are random. With the Lightspeed rom I tried it was like clockwork.
Should i upgrade the bootloader to a newer version? Do you have any idea what's causing the SOD's?
Click to expand...
Click to collapse
If you plan on running ICS correctly now, and in the future, it is highly advisable to upgrade your bootloader to an ICS Unlocked version.
Civato posted a guide for doing just that (dev forums). It has all the info you need.
The reason SOD happens, is that in order to get a good root, and have an unlocked bootloader, certain things have to be done (hacks). With them. Remember, ICS kernel and bootloader communicate with each other. The hack to the kernel, resulted in the screwy display on boot. Also, SOD's can happen also (power management issue with wake loks). But at the time, in the beginning, it was a good method for getting ICS to run on a HC bootloader.
The unlocked ICS bootloader is the way to go. Every Dev's rom (made for ICS BL) has the kernel modified so that you not only get full root with no issues, you rarely get SOD anymore. Also some other enhancements have been added such as GPS tweaks for example.
If you get SOD, as I said, it happens so rarely now days that most can't remember that maybe they shut their tab off!
Most of the dev's (myself included) have quit support for HC BL based ICS roms. No reason for it.
Also remember, Acer is just starting to push ICS to the tabs a little. So builds will change on a regular basis. And the early builds will not be 100% stable. 95% probably. The rom you install today, may have a new version in a week. Who knows.
MD
or nightly versions ,sometimes its hard to keep up , I think ICS not only changed the rules but the "skys the limit" now and Devs see stuff and change it quickly!
Hello...
I've spent about a good week and a half trying to root and install ICS on the A500 at where I work. My goal is to get ICS or higher on this device so that it can be used for testing purposes. I was able to root and install CWM but have not been able to flash ICS or JB. Am hoping you guys can point me in the right direction.
I have tried to flash cm-10-20121027-UNOFFICIAL-a500.zip and cm-9-20121221-NIGHTLY-a500.zip but what I get in both cases is my device hanging on the Acer logo. My last attempt I left the device like that over the weekend and this morning it was still displaying the logo.
The CM9 nightly wouldn't install at first until I came across a post that said to remove the first line of the install script, which I did, and the install seemed to happen but as I mentioned the device hung up at the Acer logo.
No idea how to move forward here... there are hundreds of posts and updates on the topic but quite frankly there are terms that I've never heard of, all sorts of caveats, specific recoveries that need to be used, dead links, etc... am making no progress.
I do have a backup up of HC, so am able to revert easily via CWM.
Current Android is 3.2.1, build is Acer_A500_7.014.02_COM_GEN2
@eyepoker..... I honestly don't see where your problem is provided you are prepared to load a custom ICS rom from any of the Developers in thread #3. Without picking out a favorite I would suggest any of "Civatos" FLEXxxxx ..... SHELLshock..... roms will give you a highly customized ICS Rom.
Be aware that you will have to load first an ICS Bootloader..... you cannot run these custom roms on a HC Bootloader, but in "Civatos" posts there are links to tutorials on how to do this.
The issue is that i can't flash a rom, it doesn't work. The device hangs with the Acer logo displayed and advances no farther after a flash and reboot.
Should my take away be that the latest CM nightly and the unofficial don't work? Should i not bother with CM? Is ClockworkMod old now - is there something else I should be looking for?
I'll look at the bootloader stuff you mentioned.
@eyepoker..... With respect you know your tab better than I, however unless you have bricked it (you don't say it is nor does anything you say about it suggest that is the case) then there is no earthly reason why you cannot load a ICS rom onto it. Now I am not going to say that there is a problem with the NIGHTLY updates of CM roms but is it possible that an app that you have previously installed is causing a problem with CM?
To prove to yourself that your tab can run ICS why don't you try the following.....
1) Follow the instructions in Civato's thread to load an unlocked ICS Bootloader..... I would recommend "v.8"
2) Download one of his ShellShock or Flex roms and put the zip file onto your External SD card - DON'T unzip the file leave it in it's zipped state.
3) Boot into CWM Recovery - do the necessary "wipes"
4) From within CWM install the zip from your SD Card
I am quite certain that the rom will install.
If the above doesn't work then I think there is far more wrong with your tab than it being unable to flash a rom.