Related
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.
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
I am looking forward to have all 3 Roms at one time. I want the Sense ROM to be the Base ROM with options to add MIUI and CM7 having multiple boots using Boot Manager..
If I possibly do it, my applications will install separately or it will have common location ? And where will the mods our themes for each ROM go independently?
jjdoctor said:
I am looking forward to have all 3 Roms at one time. I want the Sense ROM to be the Base ROM with options to add MIUI and CM7 having multiple boots using Boot Manager..
If I possibly do it, my applications will install separately or it will have common location ? And where will the mods our themes for each ROM go independently?
Click to expand...
Click to collapse
Alright jjdoctor, since you helped me out a lot from before with the volume mod which you can still help me with this one I have attached, I will help you out with Boot Manager.
Just so you know it works flawless with MIUI and CM7. Alright now to the point.
Each SD ROM creates an IMG. file on your SD Card in the Boot Manager directory. Though when you install stuff, everything will virtually be inside that .IMG file. So if you have another ROM all your stuff will go in that .img file. I'm not sure if I am answering correctly but ask me again if anything.
You will just install it through ROM using Boot Manager. Although when you install a them, do not wipe any boxes =D
Team Win Recovery Project 2.2, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG (for 2.2.2.0 compared to 2.2.0.0):
Mostly bugfixes:
Significantly improved sd-ext handling (ext partitions on sdcards)
Changes to kinetic scrolling in file selectors
Fixed a problem with using periods in backup names
Fixed problems in XML layouts with mounting system and USB storage
Fixed a problem with unmounting a partition before formatting during restore
Add Jelly Bean decrypt support
Updated 320x480 theme to match others (thanks to Llewelyn)
Improve "symlinking" of /data/media to either /sdcard or /emmc
Added sanitizing of device IDs for invalid characters (thanks to bigbiff)
Fixed free space calculation when switching backup devices on /data/media devices
Fixed a problem with using OpenRecoveryScript to create a backup without providing a backup name
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
NOTE: If you're coming from another build of TWRP, you may need to go into settings and tap reset defaults to reset the storage paths so that you can see your zip files.
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
thank you for this, ill test asap
if anyone wants a flashable zip, lemme know. i already have it done
edit: works good. only thing is i was flashing a rom (attempting to anyway) and somehow my zip got corrupted and unreadable. never had that happen before. any thoughts? (it was fine when i put it on my sd card, was flashing a 2nd time, so zip had worked previously and all other files on my sd are fine)
Going to flash this now and give it a try. Hopefully it works out good.
whoshotjr2006 said:
if anyone wants a flashable zip, lemme know. i already have it done
Click to expand...
Click to collapse
Throw it up brother!
thanks, always wanted a touch recovery and this one is great, if i could make a recovery touch it would be like this one again thanks
I flashed this a week or two ago and been working awesome! I love it.
i have been using cw recovery all time and always wanted to have a touch screen recovery and this one is sick, my only thing i have found is when i go to restore a backup it cannot find it,(one from cwm recovert). is it that it just cant restore those or did i miss something? no big deal to me ,just wanted to put it out there.
again thanks for this
they are in different folders on the SDCARD, im not even sure they are compatible.
ok cool im trying to do differant things and ill update you either way
would you know off hand where twrp folder would be? im looking if i get it before a reply ill post it
i got it twrp folder
alsp cani get the twrp 2220 in a zip format?
will this recovery work with firerats? on heroc?
dankdank11 said:
will this recovery work with firerats? on heroc?
Click to expand...
Click to collapse
Yes, Firerats has nothing to do with the recovery. Firerats just resizes your data/system/cache portion of the system really so you can install more apps.
I am using it and love it and works awesome on my Hero. :good:
thanks im trying it now, love the use of touch
I am going to leave the automated GooManager install for the Hero on version 2.2.2.0 due to the age of the device and the problems with recovery API 3 and older zips. TWRP 2.3.0.0 does work fine on the HeroC but I'm willing to bet that most zips are using old update binaries that will not install on the new version. If anyone wants to try, you're welcome to download and flash the newer versions manually:
http://techerrata.com/browse/twrp2/heroc
I was going to give 2.3.0.0 a try but like you stated, and someone in IRC said, that most of the zips online for the old Hero are prob all older so going to stick with 2.2.0.0 I think. Thanks for the update though.
Does TWRP require any particular hboot version, or will it function with any of them? I know you need to be on Android 2.3 in order to install TWRP, but I'm wondering... does it also mean that if you flash back to a stock ROM that TWRP won't work properly?
EDIT: My question was obviously stated with some knowledge missing. Recovery is obviously not dependent upon the ROM, as the ROM is loaded after the recovery program is done! But... I'm curious to know, if I made a nandroid backup with TWRP 2.2.2.0, will TWRP2 be able to restore it?
* DELETE *
There has been a small oversight with the GooManager route of distribution and the original post for this particular phone. You must have a PC or have a phone that can flash .zips or has a 2.3 or up ROM installed so it can run GooManager, even though this phones last OTA was Android 2.1, so it probably should have a .zip posted instead.
For example, I have a stock but rooted HTC Hero from Sprint as my backup with the latest OTA. So I can't use this method of install for this recovery without flashing a different recovery first, and then either flashing it as a .zip or upgrading my ROM to a 2.2 or 2.3 based ROM. In reality, I think most will just stick with whatever recovery must be flashed first in this situation as I will, even though I wanted TWRP. That said I think most of the users that use this will just want a .zip.
But there is no .zip posted for the guys that can flash it. This also makes it an overly cumbersome option if the handset is in stock state. As I said, I probably won't bother re-flashing, I kind of like sticking to one recovery on a phone and prefer to do minimal NAND writes.
DizturbedOne said:
There has been a small oversight with the GooManager route of distribution and the original post for this particular phone. You must have a PC or have a phone that can flash .zips or has a 2.3 or up ROM installed so it can run GooManager, even though this phones last OTA was Android 2.1, so it probably should have a .zip posted instead.
That said I think most of the users that use this will just want a .zip.
But there is no .zip posted for the guys that can flash it. This also makes it an overly cumbersome option if the handset is in stock state. As I said, I probably won't bother re-flashing, I kind of like sticking to one recovery on a phone and prefer to do minimal NAND writes.
Click to expand...
Click to collapse
As stated a couple of posts before you:
Dees_Troy said:
I am going to leave the automated GooManager install for the Hero on version 2.2.2.0 due to the age of the device and the problems with recovery API 3 and older zips. TWRP 2.3.0.0 does work fine on the HeroC but I'm willing to bet that most zips are using old update binaries that will not install on the new version. If anyone wants to try, you're welcome to download and flash the newer versions manually:
http://techerrata.com/browse/twrp2/heroc
Click to expand...
Click to collapse
Sent from my SCH-I535 using xda app-developers app
Hippie459MN said:
Yes, Firerats has nothing to do with the recovery. Firerats just resizes your data/system/cache portion of the system really so you can install more apps.
I am using it and love it and works awesome on my Hero. :good:
Click to expand...
Click to collapse
That's good to know. I think I'll give it a shot.
Just wanted to share this for those not in the know - mostly noobs like me.
With the exception of Alliance ROM, practically all custom JB Roms here are using Philz kernel with Philz's CWM Touch Recovery. There is of course Speedmod kernel but without the Touch recovery interface. If you are having issues with any of the above kernels and/or recoveries, maybe you would like to try Robbie's awesome AllianceROM but if you prefer to use another ROM or are using your own custom ROM like I do and would like to try Alliance custom kernel with TWRP recovery - also touch-based interface like Philz's kernels - without having to download the whole AllianceROM and extract the kernel zimage file and trying to figure out how to flash it, then the easiest way to get and flash/install it is:
Requires a rooted TW JB 4.1.2 ROM:
1. Install ROM Customizer app from Play Store
2. Run Rom Customizer and grant superuser/root permissions.
3. Click on "Browse OTA Content" and there you will see the kernel, modems and various bootanimations compatible for most JB 4.1.2 TW Roms. (I tried it with LSZ, LSC, LM5, LSF & LSE and it works great.)
4. Just browse thru the kernel category, choose "Alliance-XXLSZ" and click start to download.
5. After download, click the disk button/icon at the top right corner
6. then on the next page click on the arrow button/icon at the top right corner and it will ask you to flash
7. just click YES and it will install the kernel with TWRP recovery
8. after install, app will ask to reboot, just click reboot and you are done.
9. To check how TWRP looks like and if it was installed, just boot into Recovery mode using Rom Customizer or via Extended Power Menu.
10. Enjoy a so far no-bootloop (for me) with great a very simple touch interface recovery.
11. You can always go back to Philz or speedmod kernels/recovery if you want by flashing their respective files.
BIG THANKS to ficeto.
I think xperiacle addresses some moot issues specially in connection with our Touchwiz JB experiences and shows us alternatives.
Stay Hungry. Stay foolish as always
yep stay hungry stay foolish
good going..
by the way anyone can give me a method for reverse of the same..
i mean kernel with TWRP change to same kernel with CWM, with touch options like slim bean 2.5 in note if possible.
sorry for the troll question but since it relates to me, i asked.
regards