Database Info

[ROM INFO] CM7 Nightlies Discussion

maxdamage2122 said:
Since "official" nightlys have not been compiling for the g-tablet, I have been compoiling them myself on my personal computer. I'll compile the source every so often and upload it here https://www.dropbox.com/s/w3vhon1u5a2orsk/smb_a1002/kang?v=l. The time stamp in the file name (MMDDYYYY-HHMM) is the time that the repo sync was done.
In the meantime I'm setting up an old computer that I have as a buildbot to automatically compile every night for us. I'll let you guys know when I have it up and running.
Click to expand...
Click to collapse
I thought it might be nice to get a thread going for discussion on the CM7 port for harmony for our gtablet device. There are nightly builds which are starting to incorporate some great things such as video acceleration and the new google release of 2.3.4 could be around the corner. In fact some 2.3.4 code made it into nightly#60.
I am in no way associated with CM7. If someone from CM7 or someone in some way associated with CM7 wants to run this thread or create a similar one please do so.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Rule #1 of CyanogenMod: Don't ask about release dates.
CM7 Harmony Stable Releases
http://mirror.teamdouche.net/?device=harmony&type=stable
CM7 Harmony Nightly Releases
http://mirror.teamdouche.net/?device=harmony&type=nightly
Changelog
http://cm-nightlies.appspot.com/?device=harmony
Tablet Tweaks II (original TT is already incorporated)
http://forum.xda-developers.com/showthread.php?t=1002000
For firsties...
How-To Guide:
(slightly edited from Wiki http://wiki.cyanogenmod.com/index.php?title=Viewsonic_G_Tablet:_Full_Update_Guide)
Before you do anything — Make a backup
Don't forget to back up your data. If you have synced the device with a Google account, then the contacts, calendar, Gmail & select other Google-related data will not be lost and will come back after the next sync. However, you should backup anything you want to keep that is not stored on the SD card:
Bookmarks,
Applications; use Titanium Backup or the Astro File Manager, for example,
Any application data not on the SD card.
It would also be a good idea to backup everything stored on the SD card in the rare case the SD card must be formatted to resolve any major problems.
Backup for Root Users is a free application that can assist with backing up your data.
Installing ClockworkMod Recovery
For this guide, it is not necessary to root the Viewsonic G Tablet in order to flash CyanogenMod. You can simply install ClockworkMod Recovery & continue on.
Warning: Installing ClockworkMod Recovery on the Viewsonic G Tablet will void the warranty.
Download the ClockworkMod package: Download
Unzip the ClockworkMod package & copy the recovery folder & the update.zip to the root of the internal memory (NOT in any folders & NOT to the removable SD card).
Power off the Viewsonic G Tablet and reboot holding the Volume Up button and the Power button until the device is in the stock recovery.
While in the stock recovery, use the Volume buttons to navigate to the apply update.zip & press the Home button to select it.
Once the it the update.zip is applied the Viewsonic G Tablet will have ClockworkMod Recovery. Please continue to the next section.
Flashing CyanogenMod
*******************
adampdx said:
...according to this tweet we're not supposed to flash between the stable releases and the nightlies. ....
Click to expand...
Click to collapse
*******************
jerdog said:
Echoing the above -
DO NOT USE ROM MANAGER ON THE VIEWSONIC GTABLET!!!!! IT WILL BORK YOUR DEVICE 99% OF THE TIME. MAGIC VALUE MISMATCH AND OTHER ASSORTED ERRORS.
We've been dealing with these issues for months now - don't discount because you think you know better because you've used it on XYZ phone.
IT CAUSES ISSUES ON THE GTABLET. PLEASE EDIT YOUR OP TO REFLECT THIS. THERE ARE POSTS ALL OVER HERE DETAILING THIS. PLEASE ALSO POST A LINK TO BEKIT's CWM .8 - THAT IS THE ONE THAT WAS MODIFIED TO WORK WITH THE GTABLET GIVEN THE MULTIPLE QUALITY CONTROL ISSUES ASSOCIATED WITH THE PARTITIONS AND WHAT NOT.
Click to expand...
Click to collapse
Place the CyanogenMod update.zip file on the root of the SD card.
Optional: Place the Google Apps .zip on the root of the SD card also.
Boot into the ClockworkMod Recovery.
Once the device boots into the ClockworkMod Recovery, use the side volume buttons to move around, and either the power button or the trackball to select.
Select the option to Wipe data/factory reset.
Then select the option to Wipe cache partition.
Select Install zip from sdcard.
Select Choose zip from sdcard.
Select the CyanogenMod update.zip.
Optional: Install the Google Apps by performing steps 7 - 9 again and choosing the Google Apps update.zip.
Once the installation has finished, select +++++Go Back+++++ to get back to the main menu, and select the Reboot system now option. The Viewsonic G Tablet should now boot into CyanogenMod.
Having issues with finding your Internal Storage?
Check your fstab. CM has a different paradigm. See below from maxdamage2122
maxdamage2122 said:
This is a flashable zip file that I have created to backup the vold.fstab file and replace it with one that mounts the internal storage as /sdcard.
http://goo.gl/DS8u9
Click to expand...
Click to collapse
Edit: Thanks and props to the CM team and all involved. No thanks to me, I am just a copy/past whore.
Edit: Removed RomManager Method (thanks badfrog and jerdog)
Edit: Added reference to fstab mod. Thanks maxdamages 2122

Do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery

Great job Oozura. Make sure Mad-Murdoch links this thread in his post in the nook forum. I had volunteered to do the same but he didn't get back to me. I'm a long time CM nightlies user on Droid, and now on GTab as well. I'll post as much as I can here.
And that bad frog is right. Use bekit's 0.8 GTab recovery and forget about Rom Manager. You'll just end up having to nvflash...
Thanks!
MC

thebadfrog said:
Do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
Click to expand...
Click to collapse
Are you sure about this? If so I dont mind editing that part of the CM instructions.

Echoing the above -
DO NOT USE ROM MANAGER ON THE VIEWSONIC GTABLET!!!!! IT WILL BORK YOUR DEVICE 99% OF THE TIME. MAGIC VALUE MISMATCH AND OTHER ASSORTED ERRORS.
We've been dealing with these issues for months now - don't discount because you think you know better because you've used it on XYZ phone.
IT CAUSES ISSUES ON THE GTABLET. PLEASE EDIT YOUR OP TO REFLECT THIS. THERE ARE POSTS ALL OVER HERE DETAILING THIS. PLEASE ALSO POST A LINK TO BEKIT's CWM .8 - THAT IS THE ONE THAT WAS MODIFIED TO WORK WITH THE GTABLET GIVEN THE MULTIPLE QUALITY CONTROL ISSUES ASSOCIATED WITH THE PARTITIONS AND WHAT NOT.

Search for the endless threads on hard bricked and soft bricked tabs from using rom manager on the gtab. And before all you fanbois jump in and tell me you had no problems understand this....there are at least 2 different partitioning setups on the Gtab from the factory. Sometimes you can't even boot after flashing Gingerbread roms without nvflash.

MicroChip said:
Great job Oozura. Make sure Mad-Murdoch links this thread in his post in the nook forum. I had volunteered to do the same but he didn't get back to me. I'm a long time CM nightlies user on Droid, and now on GTab as well. I'll post as much as I can here.
Thanks!
MC
Click to expand...
Click to collapse
Been a long time droid, dInc user. I had sent you a PM about half way through the OP but decided what the heck. I hope this helps keeps discussion in one place for our gtab and CM7 (soon to be 7.1)

Oozura said:
Are you sure about this? If so I dont mind editing that part of the CM instructions.
Click to expand...
Click to collapse
Yes, I'm sure he is sure about this. Do NOT use Rom Manager to install any of the roms or to update CWM. Only use bekit 0.8 recovery.
I don't even install Rom Manager on my Gtab.

thebadfrog said:
Search for the endless threads on hard bricked and soft bricked tabs from using rom manager on the gtab. And before all you fanbois jump in and tell me you had no problems understand this....there are at least 2 different partitioning setups on the Gtab from the factory. Sometimes you can't even boot after flashing Gingerbread roms without nvflash.
Click to expand...
Click to collapse
Sounds good to me. I will take it out. As long as the other method works then no need to make anyone cry over a bricked tab.

+10000 I learned this the hard way on day one.
Sent from my CM7 GTablet

Oozura said:
Sounds good to me. I will take it out. As long as the other method works then no need to make anyone cry over a bricked tab.
Click to expand...
Click to collapse
Please - don't just take it out - add a warning about it. And provide the link to the known working CWM (Bekit .8).

RomManager method removed
OP Edited. Thanks.

jerdog said:
Please - don't just take it out - add a warning about it. And provide the link to the known working CWM (Bekit .8).
Click to expand...
Click to collapse
I quoted your post. Link was already there to correct version in the clockwork mod package. thanks.

Thank you. There is something flakey about these devices and they don'y like Rom Manager

So who is using the latest nightly? I'm running 60 and seems stable. I occasionally get a stall on browser apps after a long sleep. But can't find any other issues.
Sent from my ADR6300 using Tapatalk

Oozura said:
So who is using the latest nightly? I'm running 60 and seems stable. I occasionally get a stall on browser apps after a long sleep. But can't find any other issues.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
I am. No issues to report, camera is still grainy. Video playback is still great.
Sent from Desire HD or Inspire 4G or whatever this thing is called via premium XDA app.

Hardware Decoding?
So I installed AOSP the other day (the one in the Dev forum) because it was claiming hardware acceleration. It loaded up and was super laggy, but also didn't play the same video files that Vegan 5 played. I loaded up CM7 today and found the same thing. It's not nearly as laggy as the AOSP build, but still does not play video. I get volume, but no sound. Am I mistaken is thinking that we in fact have hardware acceleration now?

adampdx said:
So I installed AOSP the other day (the one in the Dev forum) because it was claiming hardware acceleration. It loaded up and was super laggy, but also didn't play the same video files that Vegan 5 played. I loaded up CM7 today and found the same thing. It's not nearly as laggy as the AOSP build, but still does not play video. I get volume, but no sound. Am I mistaken is thinking that we in fact have hardware acceleration now?
Click to expand...
Click to collapse
Progress is being made but we aren't there yet. Did you try mobo player? Engage software decoding and you'll be good to go.
Sent from Desire HD or Inspire 4G or whatever this thing is called via premium XDA app.

I've been using RockPlayer and havent had any issues. Most notably for me though was YouTube HD videos now play with no lag.
I think Irs421 is right. Its progress but not complete hardware acceleration until Nvidia releases GB drivers I would guess.

I figured as much. Progress, even slow progress, is good. I'm liking CM7 so far any how.

[Q]Android Revolution HD - Is this ROM really for Asus EeePad Transformer TF101 ?

Hi
I have been reading the "Android Revolution HD™ 1.2.1 | High Quality & Performance | O/C | Legendary" by mike1986.
I have even tried it on my Asus Transformer - and everything seems to be working Ok - but in the first message and the related FAQ for this ROM there are repeated mentions of 'Phone'.
But Asus Transformer TF101 is NOT a phone - and there is mention of HTC as well - am I missing something major here? Is this ROM really for Asus EeePad Transformer TF101 ?

Maybe because he copy/pasted from his other threads where he has phone roms. There is not source so everyone is tweaking the same asus rom.

[Q]Revolution HD and/or Clemsyn Kernel?
I am new to this forum though not new to Android.
I am a Embedded Linux developer actually so I am a bit embarrassed to ask the following question:
Having rooted my Asus TF, I installed this Android Revolution HD - ROM.
But now I understand that to be able to connect my TF using its HDMI port to my Panasonic TV, I should use the kernel from "Clemsyn-Blades-CPAjuste-supercurio OC kernel for 3.2 elite ver 18"
I have read pages and pages of messages of the thread in Dev threads but I am unable to understand how to use this kernel.
Do I overwrite the Revolution HD ROM with what is available as Clemsyn kernel in that thread or do I need to do something more?
I also read that if one is using certain ROMs then some modifications are required to some files in '/system' directory etc.
So I am a bit confused.
What I am looking for is a TF that is rooted and can connect over the HDMI to my Panasonic LCD TV - and presently I used BRK's method to root it and then installed the Revolution HD ROM.
What is my next step please? Please help.

download the kernal and put it onto your microsd card then just flash it using cwm in the recovery menu.
you need to use install zip from sd card option not update zip.
if it doesnt work just reflash the stock kernal or rom.

vlbaindoor said:
I am new to this forum though not new to Android.
I am a Embedded Linux developer actually so I am a bit embarrassed to ask the following question:
Having rooted my Asus TF, I installed this Android Revolution HD - ROM.
But now I understand that to be able to connect my TF using its HDMI port to my Panasonic TV, I should use the kernel from "Clemsyn-Blades-CPAjuste-supercurio OC kernel for 3.2 elite ver 18"
I have read pages and pages of messages of the thread in Dev threads but I am unable to understand how to use this kernel.
Do I overwrite the Revolution HD ROM with what is available as Clemsyn kernel in that thread or do I need to do something more?
I also read that if one is using certain ROMs then some modifications are required to some files in '/system' directory etc.
So I am a bit confused.
What I am looking for is a TF that is rooted and can connect over the HDMI to my Panasonic LCD TV - and presently I used BRK's method to root it and then installed the Revolution HD ROM.
What is my next step please? Please help.
Click to expand...
Click to collapse
To use the Cleysyn kernel just pick the one you want. Say 18b since you probably don't want voodoo support. Download it and put it on your SD card. Then using Clockwork Recovery flash it just like you did the rom. The rom and kernel are 2 different things and flashing the kernel by itself will not remove RevHD rom.
The reason you need the Clemsyn kernel is because he uses the latest nvidia code which has better hdmi support. Also you an overclock the SOC if you want with this rom but it is optional.
If you don't have roaches Clockwork mod installed you may want to consider it.
EDIT: salbalboa beat me too it.

salbalboa said:
download the kernal and put it onto your microsd card then just flash it using cwm in the recovery menu.
you need to use install zip from sd card option not update zip.
if it doesnt work just reflash the stock kernal or rom.
Click to expand...
Click to collapse
So do you mean this Kernel alone itself would replace what was done by installation of Android Revolution HD - ROM.
Or may be I should try this "Revolver 3.2 by Gnufabio [Sept 14] [HC 3.2 - 8.6.5.9] & Revolver Parts 2.7" - which I believe is a completely different ROM itself?
What do you think?
This whole confusion comes because the rest of the file system can remain same while kernel alone is changed - in a standard desktop PC scenario - but if the ROM itself represents the entire File System including the kernel - may be that is how the built in flash is written - erase all in one go and write entirely new stuff?

vlbaindoor said:
So do you mean this Kernel alone itself would replace what was done by installation of Android Revolution HD - ROM.
Or may be I should try this "Revolver 3.2 by Gnufabio [Sept 14] [HC 3.2 - 8.6.5.9] & Revolver Parts 2.7" - which I believe is a completely different ROM itself?
What do you think?
This whole confusion comes because the rest of the file system can remain same while kernel alone is changed - in a standard desktop PC scenario - but if the ROM itself represents the entire File System including the kernel - may be that is how the built in flash is written - erase all in one go and write entirely new stuff?
Click to expand...
Click to collapse
The rom and kernel are seperate in android not like desktop. Android is actually a sandboxed layer running on top of the linux core.
You can run any kernel you want with and rom you want as long as they are for the same version of Honeycomb. For instance I use Revolution HD 1.2.1 and Clemsyn's kernel 18b.
When you flash roms they include the kernel they think you should run, which is typically the stock kernel. But you can go ahead and flash over that with a new kernel whenever you want and it will not touch your files or applications.

Solved - Now using Revolver ROM and Clemsyn's kernel 18b
Bjd223 said:
The rom and kernel are seperate in android not like desktop. Android is actually a sandboxed layer running on top of the linux core.
You can run any kernel you want with and rom you want as long as they are for the same version of Honeycomb. For instance I use Revolution HD 1.2.1 and Clemsyn's kernel 18b.
When you flash roms they include the kernel they think you should run, which is typically the stock kernel. But you can go ahead and flash over that with a new kernel whenever you want and it will not touch your files or applications.
Click to expand...
Click to collapse
salbalboa said:
download the kernal and put it onto your microsd card then just flash it using cwm in the recovery menu.
you need to use install zip from sd card option not update zip.
if it doesnt work just reflash the stock kernal or rom.
Click to expand...
Click to collapse
vlbaindoor said:
So do you mean this Kernel alone itself would replace what was done by installation of Android Revolution HD - ROM.
Or may be I should try this "Revolver 3.2 by Gnufabio [Sept 14] [HC 3.2 - 8.6.5.9] & Revolver Parts 2.7" - which I believe is a completely different ROM itself?
What do you think?
This whole confusion comes because the rest of the file system can remain same while kernel alone is changed - in a standard desktop PC scenario - but if the ROM itself represents the entire File System including the kernel - may be that is how the built in flash is written - erase all in one go and write entirely new stuff?
Click to expand...
Click to collapse
Thanks salbalboa and Bjd223,
I decided to use the Revolver ROM which seemed more tailored for Asus TF and then using the Revolver Parts add on, I installed the Clemsyn's kernel 18b.
Now I am able to connect the TF over the HDMI to my Panasonic LCD TV and it all seems to work - but while HDMI is connected I found that the Wi-Fi connection dropped.
This is a different problem and probably needs looking into seperately.

Rooting 3.0.1 European 3G wich order

Hi,
i have a new Xoom with 3.0.1 from Telekom Germany here and i want to root it but i also would like to have the sd-card slot.
What is the best order?
Root 3.0.1 and then...?
install 3.1 OTA and root 3.1?
and when can i install CWM?
please help me....
thank you...

theslashy said:
Hi,
i have a new Xoom with 3.0.1 from Telekom Germany here and i want to root it but i also would like to have the sd-card slot.
What is the best order?
Root 3.0.1 and then...?
install 3.1 OTA and root 3.1?
and when can i install CWM?
please help me....
thank you...
Click to expand...
Click to collapse
What is the ultimate goal? Will you be flashing a custom Rom or a kernel? I would say that you should get any OTA updates first and then there will be a way to root and get additional features. Check out this guide to help you see a potential order to take, using CWM 3.2.0.0 R4c (recommended as made specifically for Xoom) and the Universal Xoom Root zip which can be used for all Xooms/all updates. http://forum.xda-developers.com/showthread.php?t=1249798
Check out this thread for additional goodies: http://forum.xda-developers.com/showthread.php?t=1209341
Take your time and good luck!

thank you very much
the xoom is now on 3.1 rooted and with cwm
my main purpose is playing videos from my NAS so i flashed the tiamat 1.4.4 kernel
everything is fine i can use the sdcard with es file explorer but when i go to the settings and sd card the settings app crashes
the sd ard also ist show in the stock xoom file explorer...what can i do?
i think about flashing tiamat 2.2.2 but i cant find out if cifs will be working there

also i dont know: when i flash tiamat 2.2.2 do i also have to flash a diff kernel or is it included??

theslashy said:
thank you very much
the xoom is now on 3.1 rooted and with cwm
my main purpose is playing videos from my NAS so i flashed the tiamat 1.4.4 kernel
everything is fine i can use the sdcard with es file explorer but when i go to the settings and sd card the settings app crashes
the sd ard also ist show in the stock xoom file explorer...what can i do?
i think about flashing tiamat 2.2.2 but i cant find out if cifs will be working there
Click to expand...
Click to collapse
Well, the proper kernel is included in the rom. If you are on that update, you could also flash Tiamat Rom one.zero. That was a nice, stable rom.
I'm not sure what you are saying about the sdcard and settings app crashing...could you explain more?

Thats what happens:
When i go to settings-> storage (the place where you can see how much space is used) it crashes.
Can you say anything about cifs.ko in "morey"?
but overall it seems to run good, so i think I'll wait til the problems with the market in 2.2.2 are solved before i flash it.
thx
edit:
i got the same problem as jkumda here(last post):
http://forum.xda-developers.com/showthread.php?t=1088726&highlight=storage+sd+crash

No suggestions??

ICS will load with 1.1 bootloader

for what ever reason i fought with 1.2 bootloader for about 6 days straight with 0 luck loading any ics rom's. so i decided to try the 1.1 bootloader and it works just fine. i have loaded every ics rom i have downloaded and every single one booted with no problems. i followed the process from the frozen ice rom for each of them. i am currently running the g harmony 4.o.4 ics 120 rom and it has been very stable and everything works except the camera and mic which is already a known issue with the ics rom's for the gtab.
jamcar's frozen ice thread
http://forum.xda-developers.com/showthread.php?t=1707503
a little video i made of the bootloader rebooting into ics
http://www.youtube.com/watch?v=7L2KYaiu0OI&list=UUitE779SbBIZKk0EGlnHWVg&index=1&feature=plcp
i don't know if this will work for everyone but it did work very well for me.

Possible other solution.
I had the same experience. Installed ICS bootloader 1.2 just fine. Then couldn't download any apps from anywhere. Went back and researched some more, downloaded 3DGtab-GAppZ- 8.3.zip, installed it the same way as ICS and everything fixed itself. Been using ICS for several weeks. Never going back! :good:

I'm curious about the speed of ICS? I just installed Frozen Ice and it seems that it takes some apps up to 30 seconds to load and the wi-fi has just been horrendous (other users are reporting that as well). Wondering if its just the Frozen Ice build that is doing this or if all the ICS Roms have this problem..
JJewel is the harmony ROM you are running available here?

jjewell said:
for what ever reason i fought with 1.2 bootloader for about 6 days straight with 0 luck loading any ics rom's. so i decided to try the 1.1 bootloader and it works just fine. i have loaded every ics rom i have downloaded and every single one booted with no problems. i followed the process from the frozen ice rom for each of them. i am currently running the g harmony 4.o.4 ics 120 rom and it has been very stable and everything works except the camera and mic which is already a known issue with the ics rom's for the gtab.
jamcar's frozen ice thread
http://forum.xda-developers.com/showthread.php?t=1707503
a little video i made of the bootloader rebooting into ics
http://www.youtube.com/watch?v=7L2KYaiu0OI&list=UUitE779SbBIZKk0EGlnHWVg&index=1&feature=plcp
i don't know if this will work for everyone but it did work very well for me.
Click to expand...
Click to collapse
thats insane!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
for two reasons:
1.) wrong bootloader
2.) the CWM version you have wasnt supposed to be able to flash above froyo but let you have ICS
---------- Post added at 07:48 PM ---------- Previous post was at 07:47 PM ----------
Dymondy2k said:
I'm curious about the speed of ICS? I just installed Frozen Ice and it seems that it takes some apps up to 30 seconds to load and the wi-fi has just been horrendous (other users are reporting that as well). Wondering if its just the Frozen Ice build that is doing this or if all the ICS Roms have this problem..
JJewel is the harmony ROM you are running available here?
Click to expand...
Click to collapse
yes it was the Fr0z3n 1c3 build. it was due to a bad upload so users had a bad download, but it has been fixed

Jamcar.. It seems to be running great for me now.. much faster speeds in both wi-fi and opening apps...

jamcar said:
thats insane!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
for two reasons:
1.) wrong bootloader
2.) the CWM version you have wasnt supposed to be able to flash above froyo but let you have ICS
Click to expand...
Click to collapse
There's something definitely puzzling here but those 2 are not the reason for puzzlement.
As for point #1: yes, the TeamDRH 2.6.39.x kernel works on both the 1.1 and 1.2 bootloaders--it definitely was a surprise. This is what nVidia/ViewSonic should've done with their older 2.6.32.x kernels also when they updated the bootloader.
Point #2 is not puzzling either: Recovery (we're discussing only CWM here) mode consists of 2 components both of which are build when you compile CWM:
a) the /sbin/recovery program proper which puts up the menus and performs the tasks chosen by the user, and,
b) (for installation only) a program called (for Froyo onwards) META-INF/com/google/android/update-binary in the installation zip file.
It is this update-binary program which is responsible for reading and executing a META-INF/com/google/android/updater-script file which is where the steps required to install a ROM are written. Ie. it is not the recovery program which does the installation. So, as long as you have an update-binary program which understands the updater-script in the installation zip file, all CWM versions > 2.5.x will be able to do the job.
The only puzzling thing is how the 1.1 bootloader was put back.
If it was using one of the 1.1 nvflash packages we have floating around on this board, then the "system" partition would have been shrunk back to 200 MB. This means that during the ICS ROM install, some apps/programs wouldn't have been written--/tmp/recovery.log should show a lot of file copy failures during installation due to "no space left on device" errors. That file will also show which files were not copied. And depending on which files were not copied, it could or, could not--in this case--adversely affect the final ROM install.

rajeevvp said:
There's something definitely puzzling here but those 2 are not the reason for puzzlement.
As for point #1: yes, the TeamDRH 2.6.39.x kernel works on both the 1.1 and 1.2 bootloaders--it definitely was a surprise. This is what nVidia/ViewSonic should've done with their older 2.6.32.x kernels also when they updated the bootloader.
Point #2 is not puzzling either: Recovery (we're discussing only CWM here) mode consists of 2 components both of which are build when you compile CWM:
a) the /sbin/recovery program proper which puts up the menus and performs the tasks chosen by the user, and,
b) (for installation only) a program called (for Froyo onwards) META-INF/com/google/android/update-binary in the installation zip file.
It is this update-binary program which is responsible for reading and executing a META-INF/com/google/android/updater-script file which is where the steps required to install a ROM are written. Ie. it is not the recovery program which does the installation. So, as long as you have an update-binary program which understands the updater-script in the installation zip file, all CWM versions > 2.5.x will be able to do the job.
The only puzzling thing is how the 1.1 bootloader was put back.
If it was using one of the 1.1 nvflash packages we have floating around on this board, then the "system" partition would have been shrunk back to 200 MB. This means that during the ICS ROM install, some apps/programs wouldn't have been written--/tmp/recovery.log should show a lot of file copy failures during installation due to "no space left on device" errors. That file will also show which files were not copied. And depending on which files were not copied, it could or, could not--in this case--adversely affect the final ROM install.
Click to expand...
Click to collapse
wait then why does cm9 require that you CWM 5.x.x.x ( the one koush made for ICS)?

jamcar said:
wait then why does cm9 require that you CWM 5.x.x.x ( the one koush made for ICS)?
Click to expand...
Click to collapse
Is it a "hard" requirement or a "soft" recommendation? Because CWM works as I've described for user-driven zip file installs.

I used gtab.nvflash.1.2.branch.20110508 with cwmv3028 To go to BL 1.2 and then flashed G_Harmony_ICSv1.5(120)(SuperCharged)
It went smooth, works great, and I am very happy with my GTAB

rajeevvp said:
Is it a "hard" requirement or a "soft" recommendation? Because CWM works as I've described for user-driven zip file installs.
Click to expand...
Click to collapse
For cm9 I'm honestly not 100% sure, but in cm7 you had to have CWM v3.x.x.x it was a hard requirement. It wouldn't install if you weren't on v3.x.x.x
Sent from my SPH-D710 using xda app-developers app

jamcar said:
... but in cm7 you had to have CWM v3.x.x.x it was a hard requirement. It wouldn't install if you weren't on v3.x.x.x
Click to expand...
Click to collapse
Check this again: Official CM7 installs just fine with 2.x for these 2 reasons:
1. All official CM7 releases (even the latest 7.2) come with a kernel built for a 1.1 bootloader. This means that they expect to run on a 1.1 bootloader, which, in turn, means that recovery image must also necessarily have a 1.1 kernel.
2. All the versions of CWM v3.x that I've seen on this board have a 1.2 kernel in the recovery image.
This means that if you were planning to install any of the official CM7 builds, then you would not be able to do it by using any of the CWM-v3.x versions built by roebeet--CWM-v3.x just wouldn't boot. You would need to be running one of the 2 CWM versions for a 1.1. bootloader: CWM-v2.5.1.x or CWM-4.0.1.5.
Note:
CWM >= 3.x officially dropped support for "Amend" scripting. CWM-2.5.x supports both the old "Amend" and the newer "Edify" scripting.
There are unofficial CM7 repacks and RCs which have a 1.2 kernel and so will run on the 1.2 bootloader.
You could also insert a 1.1 kernel into a 1.2-based recovery image and get more choices of CWM versions--I'm running CWM-5.5.0.4Beta15 on my 1.1 right now, for instance.
These last 2 are the exceptions rather than the rule-- but, really, there's no need for any ambiguity in any of this. The fact that ICS ROMs and CM7.x can be installed using any version of CWM >= 2.5.1.x can easily be checked.

That's interesting. Wish I knew that before I switched over to 1.2
Sent from my VS910 4G using xda premium

[Q] Questions about CROMi-Xenogenesis 4.6 First-time Install

Hi, I hope this post is in the right section (please move if not).
I have lots of experience rooting and installing custom ROMS on my Samsung i9000 phone, but this will be my first time installing a custom ROM on my TF700T. The tablet is unlocked and rooted and has the latest Android JB version and bootloader (4.2.1, 10.6.1.14.4). I also have TWRP 2.5 installed and working. However, I have a few questions before I start - sorry if these seem really noob.
1. My current SKU in Taiwanese (TW) - do I just use the WW edition without making any changes?
2. I've never used DATA2SD before - do I need to format the SD card and add the /Data/ directory manually, or does the CROMi installation do this for me?
3. The tablet is currently setup for two users (myself and my wife). Does CROMi-Xenogenesis 4.6 support mutli-user?
4. If I back up all the current settings using Titanium, do I need to do it in both profiles? Or should I simply do a simgle backup from root?
Any help would be much appreciated.
Cheers, R

rich110 said:
Hi, I hope this post is in the right section (please move if not).
I have lots of experience rooting and installing custom ROMS on my Samsung i9000 phone, but this will be my first time installing a custom ROM on my TF700T. The tablet is unlocked and rooted and has the latest Android JB version and bootloader (4.2.1, 10.6.1.14.4). I also have TWRP 2.5 installed and working. However, I have a few questions before I start - sorry if these seem really noob.
1. My current SKU in Taiwanese (TW) - do I just use the WW edition without making any changes?
2. I've never used DATA2SD before - do I need to format the SD card and add the /Data/ directory manually, or does the CROMi installation do this for me?
3. The tablet is currently setup for two users (myself and my wife). Does CROMi-Xenogenesis 4.6 support mutli-user?
4. If I back up all the current settings using Titanium, do I need to do it in both profiles? Or should I simply do a simgle backup from root?
Any help would be much appreciated.
Cheers, R
Click to expand...
Click to collapse
1. Yes just use the WW. It really dont make a difference but I wouldnt use the US rom unless you are in the US.
2. I have never used DATA2SD but by what I have read, you must use GParted to format the SDcard a certain way in order for the Mod in the CROMiX installer to see it. You MUST use GPARTED, you cannot use any other without risk of more problems.
3. Yes CROMiX supports multi-user. CROMiX is just the stock ROM, but de-bloated and extra tweaks.
4. Titanium will backup all apps. Though I do not use other users, I would think if you back it up from the Owner User, it would back up everything, but I do not know if the owner can access other users info though.
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

I can answer the 2nd question, You need to do all the partitioning and formatting on your PC (under Linux preferably) with GParted, CROMi does not do the preparation. As noted in the following thread http://forum.xda-developers.com/showthread.php?t=1962507.

rich110 said:
Hi, I hope this post is in the right section (please move if not).
I have lots of experience rooting and installing custom ROMS on my Samsung i9000 phone, but this will be my first time installing a custom ROM on my TF700T. The tablet is unlocked and rooted and has the latest Android JB version and bootloader (4.2.1, 10.6.1.14.4). I also have TWRP 2.5 installed and working. However, I have a few questions before I start - sorry if these seem really noob.
1. My current SKU in Taiwanese (TW) - do I just use the WW edition without making any changes?
Click to expand...
Click to collapse
No problem, as long as you have adequate command of the English language, which you do seem to have.
2. I've never used DATA2SD before - do I need to format the SD card and add the /Data/ directory manually, or does the CROMi installation do this for me?
Click to expand...
Click to collapse
Just make the two partitions, and follow the prcedures to the letter. Your ROM will do the rest.
3. The tablet is currently setup for two users (myself and my wife). Does CROMi-Xenogenesis 4.6 support mutli-user?
Click to expand...
Click to collapse
I haven't tested this, but since it is based on Android 4.2 it should work (it provides exactly the same functionality as the stock ROM, so if stock does it, CROMI(-X) does it, too).
4. If I back up all the current settings using Titanium, do I need to do it in both profiles? Or should I simply do a simgle backup from root?
Click to expand...
Click to collapse
I have no idea, so I'd better shut up here.
Any help would be much appreciated.
Cheers, R
Click to expand...
Click to collapse

@ Tylorw1, mbamberg, MartyHulskemper
Wow. Thanks very much for the very quick replies. I'll use your info and get installing today.
Thanks again!

You may find this useful. It discusses backing up multiple user accounts in 4.2 with superuser (assuming ChainsDD but could be CWM) and TB. How this works with other superuser apps (superSU, superuser X) is TBD. Here is the key finding:
sbE said:
Non-Primary Users CAN get root access. I used superusers multi-user Mode (owner controlled) and TiBa gets root access on my secondary users. Without superusers multi-user feature TiBa doesn't get root rights...i tried it...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2105659

I was also wondering about DATA2SD. OP did you format your SD card and get it to work? When you install ChromiX it asks you if you want to install Data2SD. Will that option not work if you dont have your external SD card formatted correctly?

wl123 said:
I was also wondering about DATA2SD. OP did you format your SD card and get it to work? When you install ChromiX it asks you if you want to install Data2SD. Will that option not work if you dont have your external SD card formatted correctly?
Click to expand...
Click to collapse
Yes, you have to correctly format and partition your external SD with Gparted for Data2SD to work.
Read the forums before you do this. Data2SD can be a mine field and does not give you the performance boost it once did IMHO.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

For the love of God use GPARTED to partition it seems a long effort to go but using any other will and has done to me broke my micro SD.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app

wl123 said:
I was also wondering about DATA2SD. OP did you format your SD card and get it to work? When you install ChromiX it asks you if you want to install Data2SD. Will that option not work if you dont have your external SD card formatted correctly?
Click to expand...
Click to collapse
Hi, sorry for the late reply... I haven't been checking back on this post. To answer your question... in the end I chose not to install DATA2SD option. I did successfully install CROMi-X 4.6.1 and everything is working really well - browsing with Chrome is amazingly fast compared to stock!!!
The only problem I've found so far is with some of my Play Store Apps not being able to load - there were a couple of apps that installed just fine on Stock Asus JB (latest version 4.2.1) but under CROMi-X they say they are incompatible with my device. I guess it probably has something to do with the DPI being used (I used the 213 DPI which was default selection during the CROMi-X installation). Might check this out in the developer thread.
Cheers, R

I've updated the boot loader in the first post of the CROMi-X thread to include the latest TW boot loader now.
Also it seems the multi-dpi version of the play store I am using has some issues showing all compatible apps. I have an alternative version to test which will hopefully resolve this and then I can release a patch.

sbdags said:
I've updated the boot loader in the first post of the CROMi-X thread to include the latest TW boot loader now.
Also it seems the multi-dpi version of the play store I am using has some issues showing all compatible apps. I have an alternative version to test which will hopefully resolve this and then I can release a patch.
Click to expand...
Click to collapse
Thanks for the heads up... just updating now. Thanks for all your great work with this ROM.