Related
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.
6/20/2011 EDIT: Added some links to the assorted mods (and google searches for anything not on XDA, to abide by the rules). Also, goodintentions has a new site up that is VERY helpful for new user questions. It is here: http://viewsonic-gtablet-for-dummies.webs.com (I assume this link is OK to advertise, as it hasn't been pulled by the moderators yet).
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 6/14/11 EDIT: That seems to be changing). 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 (as of 6/16/11) 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
- Gingerbread Rom Collection for Bootloader 1.2 (these are CM7 ROMs ported to the 1.2 bootloader)
The current 1.2 based options NOT hosted on XDA (as of 6/16/11) are:
- Honeycomb for GTAB - Flashback
- Century Eyes (Froyo based "EDEN" port)
- Mountain Laurel (Froyo based "TapnTap" port)
- Brilliant Corners (Froyo based "VEGA"/"Viewpad" port)
- Bottle of Smoke Honeycomb port
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 need to jump to 1.1 from 1.2, I would recommend reading the modder's post to see if there are instructions for 1.2 jumpers.
The current 1.1 based options on XDA (as of 6/16/11) are:
- VEGAn-Tab Froyo Build
- ZPad Clean v3.0 for gTablet
- VEGAn-TAB GingerEdition
- G-Harmony Gingerbread 2.3.4 with Honeycomb elements
- Calkulin's G-Tab [ 3991 l Battery Saver script w/ Profiles ]
- Evervolv | GRJ22/Android 2.3.4
- Gingerbread-gtab-deck
- GtabComb for Bootloader 1.1 Gtablet\Zpad T (this is a zyhong creation and is actually forked from my own HC port)
- TNT Lite Froyo (similar to Calkulin's ROM, and currently retired)
- gADAM Froyo (currently retired, as well)
The current 1.1 based options NOT hosted on XDA (as of 6/16/11) are:
- Cyanogenmod 7.x
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 1.2 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.
Also, gojimi has a post with instructions for 1.2 to 1.1 downleveling: http://forum.xda-developers.com/showthread.php?t=1036956
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?
Hello,
I have a HTC Touch Diamond 100 and I installed the "Froyo FRX06 XDandroid NEW system update" review in the post "[prj] [XDANDROID] [AOSP] [FroYo | GINGERBREAD] [31.03] System Update" and everything works fine except that it doesn't recognize SDcard applications.
There's no Error Message in the screen, is just that the system doesn't recognice anything in the SDcard. I put my apps in the folder: AndroidApps-> Other. I think it's not the common fault that I have read many people have "Waiting for SDCard error. For people who have problems with sdcard message, add this to your startupmsmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave" because for instance the phone let me save the pictures i've take with the camera phone or install and recognice any app from the market.
I 've Format the card with the HP tools after initial installation and then i had restore all the files in the internal storage.
P.S. Sorry for my possible spelling mistakes but English is not my native language
Keep in mind if you put the apk in anything other than the AndroidApps folder you will need to install them yourself. See THIS FAQ for further explanation. As far as the wating on sd card message you get when you are booting into Android, I get those all the time and have no problems with taking pictures. I would suggest that you use the full bundle from THIS post to ensure you have the latest. Unless you know what you are doing
R^7Z said:
Keep in mind if you put the apk in anything other than the AndroidApps folder you will need to install them yourself. See THIS FAQ for further explanation. As far as the wating on sd card message you get when you are booting into Android, I get those all the time and have no problems with taking pictures. I would suggest that you use the full bundle from THIS post to ensure you have the latest. Unless you know what you are doing
Click to expand...
Click to collapse
Oh what A noob mistake xD I didn't know that apps in the "Other" folder doesn't follow the "typical rules" for instaling apps (i've come from previous releases of Android, Eclair specifically, and in that version it was only place in this folder to install apps).
I'm using froyo instead of gingerbread builts because HTC touch Diamond it's quite old and i don't know if the performance would be better or slower than froyo performace but if you recomend me to use that gingerbread bundle i would use it.
Thanks R^7Z.
Honestly, Gingerbread is "better" but it is alpha release at the moment. Yes, this means that there are quite a few more "improvements" to under-go! I only recommend it if you like the idea of Android. The latest releases for FroYo aren't bad but it seems there are a few hard instability hits it has taken since FRX03 (last time I really enjoyed running a FroYo build from the XDAndroid project). Since then, I've been playing around with a few things and builds to include but not limited to this new idea of CWM (clockwork mod/Gingercherry tutorial) which is posted in the neopeek forums. So, unless you've got an idea as to how neopeek variants work, it's suggested to stick with the XDAndroid builds...
R^7Z said:
Honestly, Gingerbread is "better" but it is alpha release at the moment. Yes, this means that there are quite a few more "improvements" to under-go! I only recommend it if you like the idea of Android. The latest releases for FroYo aren't bad but it seems there are a few hard instability hits it has taken since FRX03 (last time I really enjoyed running a FroYo build from the XDAndroid project). Since then, I've been playing around with a few things and builds to include but not limited to this new idea of CWM (clockwork mod/Gingercherry tutorial) which is posted in the neopeek forums. So, unless you've got an idea as to how neopeek variants work, it's suggested to stick with the XDAndroid builds...
Click to expand...
Click to collapse
I see what you say but honestly, right now, I'm looking for stability and performace, if you know that gingerbread build GBX0A have better performance (i supose that it's less stable because it's an alpha) than FRX06 i'll choose Ginger
Thanks again R^7Z.
This is an extremely simple ROM modification to the standard Advent Vega 1.10 system image that only alters a couple of things. These are as follows:
/system partition size increased from 128mb to 155mb. (The reason for this will be explained below)
su and SuperUser.apk added - You can use root apps as standard now.
ClockworkMod Recovery built-in.
Added Pauls simple recovery reboot app to get into CWM recovery.
That's all! No google apps, nothing else, just these simple changes. This isn't intended to be used as an everyday ROM (although there is no reason why you couldn't).
The main reason for this, is to be used as ROM base for VegaComb (and any other ROM you wish to use). I have been struggling with the Vega's default partition sizes while trying to port Honeycomb, and rather than spending tons of time trying to make stuff way smaller than it was ever intended to be, this seems like the better option.
So, flash this in nVflash recovery mode (exactly the same as the stock 1.10 image) and off you go. Done. No need to do anything else. You can use this base with any ROM, the ONLY downside is that 30mb of storage has been re-allocated from /data to /system, which most people won't even notice.
ALL future versions of VegaComb will require that you use this modded system image as a base (as they will require more than 125mb of /system space). To return your partitions back to the way they were, just re-flash the stock 1.10 image from www.myadventvega.co.uk (this is the ONLY way to restore your partition sizes, restoring from a Nandroid backup will NOT change your partition sizes back). You DON'T have to return to stock when you want to switch from using VegaComb, all other ROMs should work perfectly fine on top of this base, including Corvus5 and CM7.
Also, it's handy to have this in case you brick your Vega as CWM is pre-installed
AS ALWAYS MAKE SURE YOU NANDROID BACKUP BEFORE FLASHING ANYTHING!
Download ModdedStock_1.10 v2 Here!
Woo Hoo, good sign for things to come
Good work, Love the idea of a bigger /system..saves a lot of messing around moving apps to /data. Cheers. Paul
Just can't get this to install :-(
Keeps coming up with unknown device found!!
Ooops, forgot to plug the charger in.........sorry :-(
I use ubuntu will this work through wine or would i be better off trying to borrow a windows MC
Flash without usb cable?
Is there a way to flash this ROM without using the USB cable and recovery mode since my VPAD10s is giving a huge pain with windows 7 and the driver so I can not make it work.
Is there a version to be used with rom manager?
Thanks guys.
You need to use your PC because this ROM changes the partition sizes in the internal memory, and you need a PC program (nvflash) for that purpose.
Damn! thanks Logseman, I will keep on trying to get my tablet recognized over w7 can´t believe it´s so hard to make it work. wish me luck
Hope over to the Modaco Vega forum and search for YAUDIG and AUDI. They'll get the drivers installed for you.
simonta said:
Hope over to the Modaco Vega forum and search for YAUDIG and AUDI. They'll get the drivers installed for you.
Click to expand...
Click to collapse
Thanks simonta, already tried AUDI´s soft but no luck.
I´m starting to think that the issue might be with my pc/w7.
Great stuff!
Rgds
Lok
Hi:
Currently using vegacomb 0.6, i want to nandroid backup, install the new Rom base, then nandroid restore, and then upgrade to vegacomb 0.7 via the upgrade patch, in order not to loose all my settings.
So I would like to do a Nandroid backup, but being Android illiterate, i havent found how to do it in vegacomb 0.7.
Another question is , as I have moved most apps to SD, if there would be any problem regarding the base rom change and nandroid bacup-restore
Thanks for any hint/pointer
Which gapps should I use it for this built?
Zebwen said:
This is an extremely simple ROM modification to the standard Advent Vega 1.10 system image that only alters a couple of things. These are as follows:
/system partition size increased from 128mb to 155mb. (The reason for this will be explained below)
su and SuperUser.apk added - You can use root apps as standard now.
ClockworkMod Recovery built-in.
Added Pauls simple recovery reboot app to get into CWM recovery.
That's all! No google apps, nothing else, just these simple changes. This isn't intended to be used as an everyday ROM (although there is no reason why you couldn't).
The main reason for this, is to be used as ROM base for VegaComb (and any other ROM you wish to use). I have been struggling with the Vega's default partition sizes while trying to port Honeycomb, and rather than spending tons of time trying to make stuff way smaller than it was ever intended to be, this seems like the better option.
So, flash this in nVflash recovery mode (exactly the same as the stock 1.10 image) and off you go. Done. No need to do anything else. You can use this base with any ROM, the ONLY downside is that 30mb of storage has been re-allocated from /data to /system, which most people won't even notice.
ALL future versions of VegaComb will require that you use this modded system image as a base (as they will require more than 125mb of /system space). To return your partitions back to the way they were, just re-flash the stock 1.10 image from www.myadventvega.co.uk (this is the ONLY way to restore your partition sizes, restoring from a Nandroid backup will NOT change your partition sizes back). You DON'T have to return to stock when you want to switch from using VegaComb, all other ROMs should work perfectly fine on top of this base, including Corvus5 and CM7.
Also, it's handy to have this in case you brick your Vega as CWM is pre-installed
AS ALWAYS MAKE SURE YOU NANDROID BACKUP BEFORE FLASHING ANYTHING!
Download ModdedStock_1.10 v2 Here!
Click to expand...
Click to collapse
Thanks. one questions. Which gapps should I use for this built?
Thanks again.
hi, can i flashed this rom using CWM?
No, you can only flash it using a pc.
@all
Can someone please tell me how to use the nvflash, cause i'm clueless. I've searched using google but no luck, even on YouTube. I've downloaded nvflash but I can't work it. It keeps telling me about the drivers, although I installed the drivers. Any help would be great.
Thank you in advance.
jayk32 said:
@all
Can someone please tell me how to use the nvflash, cause i'm clueless. I've searched using google but no luck, even on YouTube. I've downloaded nvflash but I can't work it. It keeps telling me about the drivers, although I installed the drivers. Any help would be great.
Thank you in advance.
Click to expand...
Click to collapse
Hi
Switch off your Vega.
Connect it to the PC with the USB Cable.
Hold the power button on the Vega for 2 secs
Hold the back button while still holding the power button for a further 2 secs.
Release the power button but keep holding the back button for a further 2 secs.
You should now have a black screen and the Vega should be recognized on your PC (check in Control panel under USB for Nvidia Harmony or Shuttle)
The above assumes that you have installed the drivers.
Then open Modded Stock v1 or 2 which you should have already downloaded to the PC and it will install on the Vega (Vega will show NV Flash mopde across the top of the screen)
Once Modded stock is installed go to the apps menu and the recovery app is there. If you have already downloaded and put on your SD Card, the Vegacomb 9n Rom run the recovery and it will put you into CWM.
Wipe data, cache and in advanced the Dalvik cache.
Then select install from SD card and select the Rom and it will install.
If you continue to have problems Google Vegatools 4.1 and download and install
and it can do all the hard work.
Hope this helps
Stransky
Hi guys, sorry to hijack the thread an take it slightly off course but........
Buy flashing this stock modded rom, will it reset my touch screen issues? Read that its a pretty common problem.
I've tried the fix at modaco, and it works.......for a very brief period, then back to just half of my landscape screen being recognized?
I've only had my Vega a week, can any other of you more experianced fellows point me towards a fix? It would be much appreciated.
Sent from my VegaComb using xda premium
Thanks for a awesome rom.One questions,having problems with the sensor.Is there a simple solution to this?i have wiped dalvic cache but didnt help.I want to play games like NFS Shift and ather other games with sensor abilities.
Why not use Custom MTD ?
http://forum.xda-developers.com/showthread.php?t=717874
Hey all, buying an XT720 today.
Looking to get it up from 2.1
What is the most stable update at the moment?
I have done CM 6.1 on a HTC Dream, was pretty happy with it.. would like to get up to 2.3 on this..
Suggestions? I am using Wind Mobile in Canada for this phone if it makes a difference.
James
Hi
Their are choices cm6 is very stable
I would try flfalcon cm7.
Their are J.Y.Daddy cm7 these were made for the motorio to use these you would need to apply bootfix.
J.Y.Daddy even ported miui ics 4.01.
You need check out the development page.
Sent from my XT720 using xda premium
I also have a list of most of the ROMs and their +/-'s. Ill find the link and post it. I'm mobile now so can't find it that way.
Im on wind also and i truthfully find bravo the best.... everything is really stable and HD cam and whatnot works
Here is a somewhat dated list but a list nonetheless and here is the thread it came from.
http://forum.xda-developers.com/showthread.php?t=1298208
Woodrube said:
There are a host or ROMs for this phone right now and it is quite hard to narrow down to "The Best". Each as their own +/-'s and while one might be a monster in speed, it might have poor muti-tasking or bad camera. Here are some of the ROMs we have and some of the +/-'s they have (not all, just some +/-'s).
In no particular order other than the top came out first and bottom is the latest.
2.1 Stock - Came with the phone. You can falsh via RSDlite the sbf file for your region.
2.1 Stock~ESB (Eclair Strikes Back) - Same as above, but has aorking app2ext, camera, FM Radio. Still it is 2.1
Dexters 2.2 with MZ patch - First successful attempt to port 2.2 to our phones. All features of 2.2 but camera is sketch and FM radio doesn't work (unless you apply FJfalcon radio patch but then it is still loud), media button doesn't work.
Kahlpower's V2/3/4 - Optimized version of Dexters. Same issues as above but is more stable and generally was the choice as a "home" ROM for many users. I have my wife on this one as we speak. Low maintenance, a good everyday driver. Has App2ext/ Link2sd, native Froyo App2sd.
Cincinnati Bell's "official" 2.2 - More or less a glorified version of Dexters 2.2 but I think the Mioz7AE found a "listening" script that may or may not send info back to developer. I would stay away from this one. Plenty more to choose from.
Wanhu 2.2 (also Wanhu's Kahl's Optimized) - Korean port of 2.2. FM radio and camera does work. Number formatting is off. App2ext works fine as does native Froyo app2sd.
XDA Special/ Hellmonger Edition - This was moveing really well and then Hellmonger's phone crapped out on him and his carrier gave him an HTC Penache, so no more support for this one. But is DOES work and worth a try.
CM6 - our developer Mioze7Ae's masterpiece (for now until he moves on to something else) All the features of CM6, including themer. Has App2ext and Link2sd.
WIPs
Brianlili's Brovo 2.2 - This one is almost done, jsut a few little thing to finish it off.
JYDaddy's CM7 (nightly/ HoNo/ iceandfire...)
FJfalcon's CM7.1 (make massive progress daily on this one as it is being built from source).
Like I said there are +/-'s to each but the are all spelled out for you in the OP of each thread. Plus, unlike other phone forums, we actually answer your questions and dont respond with, "search".
Good luck and remember to always BACK UP.
Click to expand...
Click to collapse
S7icky said:
Im on wind also and i truthfully find bravo the best.... everything is really stable and HD cam and whatnot works
Click to expand...
Click to collapse
Where is this Bravo??
Also I have rooted..
but I have not found a good guide on Openrecovery. (EDIT) got this done, went through ADB shell.
I unzip the the openrecovery to the sd card.. gives me openrecovery.zip a directory and an images directory.
SO then to flash a new rom I just put the .zip file in the updates directory.. and bingo bongo?
Going to try Cyanogenmod 7.1 first.. not sure where to find the brovo? bravo? mentioned.
James
Custom Recovery is here
http://forum.xda-developers.com/showthread.php?t=1242259
Bravo is here
http://forum.xda-developers.com/showthread.php?t=1332410
All ROMs and Mods are in the Dev thread.
I vote for CM6 RC3 / RC4
it's by far the most stable & fast which allows you to run most resources intensive games
AllGamer said:
I vote for CM6 RC3 / RC4
it's by far the most stable & fast which allows you to run most resources intensive games
Click to expand...
Click to collapse
I might give this a try next.. I have bravo tweeked out.. and I like it for the most part.. but there are somethings that dont seem to work as well as my G1.
I will just save my current phone in nand and then I can just reload it all back in - correct??
James
Yes
10chars
this one fjfalcon's CM7 , http://forum.xda-developers.com/showthread.php?t=1350453
Nandroid and battery
I just bought an XT720 (Rooted and unlocked)
Is there any way to change the battery level increments from 10% to something more exact like 5% and how do we create a Nandroid back up?
I also want to install bravo2.2 do I need to do a factory reset before installing this rom?
I am running stock rom 2.1
Well if its Rooted, then you should have Open Recovery on it.
When you boot the phone hold VOL up and it will boot in OR...
or when you power off.. it should give you the option to reboot into RECOVERY.
There are lots of threads on here about OR .. but if you follow the menus you should be fine.. on an XT720 you push the camera button (big one) to accept a selection in the OR menu.
You can back up - which will save EVERYTHING.. a Nandroid backup is the best thing to store away somewhere should you mess up your phone.
YES you will have to loose everything when switching from 2.1 to (anything else)
If you are just updating to a newer build of something you put on.. then no.
You do the RESET and clear caches etc.. in OR.
Do a search its all on here .. usually the first page of whatever rom you want to TRY.
Have fun.
James
Thanks for the reply, time to install some rom's
Hilarious...after wading thru a few hundred pages of replies on this phone and the various roms, I completely missed your thread here James which is about as close to what I'm trying to accomplish as imaginable..
I posted some of my saga over here: http://forum.xda-developers.com/showthread.php?t=1399242
Do you mind me asking James/BikerBob...how did you make out? Anything I should know (if you have a sec read my long winded post lol!)
Did you have 3G/Wifi switching issues with stock, or maybe you didn't bother testing that / noticed it..before rooting I mean..
thnks!
(don't know if mods merge threads in this forum but mine is probably a candidate! sorry!)
racer321 said:
I just bought an XT720 (Rooted and unlocked)
Is there any way to change the battery level increments from 10% to something more exact like 5% and how do we create a Nandroid back up?
I also want to install bravo2.2 do I need to do a factory reset before installing this rom?
I am running stock rom 2.1
Click to expand...
Click to collapse
No, kernal(maybe driver) can't support 5% or 1% percentage battery level.
OK, so I decided that changing the SD card to a class 10 might help app usage ..
I copied the old sd card to the new one.. and if I try and get into OR .. I get the exclimation mark in triangle instead of the OR logo.
What do I need to do to get back into OR? do I need to RE-Root?
James
If you don't have it already, grab Mioze's modded OR for the xt720 & follow the instructions. If that's all you did was to switch sdcards there should be no need to redo everything.
Sorry, never mind the OR issue, my bad.
I have played with this too much.. lol.. get things mixed up..
I had the OpenRecovery.zip from one version mixed with the directory of the other..
Jezz
OR runs from the files on the sdcard (the openrecovery folder & openrecovery.zip) if something is corrupted (or missing) you wont be able to boot into OR.
I installed the rom and i dont have a 4g icon but an H, and there are no apps just basic ones like no market none of that stuff. Does it all have to be downloaded manually or is it supposed to come loaded with some stuff. Iknow i should post this in the WildchildIcE v0.9 section but it wont let me ask any questions cuz im new to the forum
your also supposed to download gapps....i would link you but im on mobile. Check for the gapps download near the regular download.. Im aware that in some cases the H icon will still show and a fix for that will come soon.
ahhh ok dl'ing it now. is there a special way to install gaps
You'll flash gapps zip file from recovery just like the rom.
Sent from my myTouch_4G_Slide using XDA
You will find that the v0.9 version will have the "ROM Control" working wonderfully but the soft keyboard & proximity senser are still borked. If you find those are "deal breakers" for you (and they are for some people) you can flash the 6/19 "nightly" and swap a fix for those two issues for having "ROM Control" FC'ing until XMC has a chance to iron out the issue.
Just my 2 cents.....
....don't forget the gapps
How do I get wifi to work?
I have flashed your v0.9 and followed the installation instructions and I must say it all went very fast and smoothly. However
I'm unable to turn on wifi. It says in the change log that this works. What happens is that when I click on wifi, then go to the wifi screen and touch "on", it quickly moves to on but immediately goes back to off and the screen is stuck saying "turning wifi on". So how do i get this to work?
If it makes any difference I came from another rom, http://forum.xda-developers.com/showthread.php?t=1758767&highlight=v2.
Also, when sending text messages, I use go sms, and for some reason now i no longer have auto correct/spell check.
It actually doesn't recognize about 90 percent of the words I type. It says they're incorrect even though they aren't.
Any thoughts?
Thanks. Awesome work. I'm totally enjoying your roms.
First of all, I would suggest you use ONLY CWM 5.0.2.7 or 5.5.0.4.
Secondly, always do a FULL wipe when coming from another ROM. It's also a known issue with CWM that if you don't do those wipes 2 or 3 times it's very possible to leave bits and pieces behind that may cause glitches like you have described.
Third.....if you have already followed the 1st & 2nd suggestions you may have gotten a few packets corrupted in your DL and should probably at least do another and reflash.
This could make a huge difference and I forgot to even consider it. If you have one of the newer bootloaders you'll need to flash your boot.img file thru ADB after you have flashed your "rom".zip file. You will also want to isolate a copy of your DL and expand the file so that you can copy your boot.img to where you normally flash files from. From what I have personally seen, it is VERY important that it isn't copied directly from your "rom".zip file and flash that because it will remain wholey or partially compressed and have various parts of you ROM disabled just as you described.