Related
First...appologies to those who get frustrated with the newb who shouldn't attempt this if they have to ask how....
I am fortunate to own a GTAB that came already loaded with Vegan 5.1.1 and so I have not had the opportunity to do any tinkering myself. I have read the sticky on CWM and the process seems simple enough. I have read through the threads on the various ROMS but have not read of anything that seems complete enough or enough of an upgrade to make me want to switch from Vegan..... until Calkulin.
Of course the ROM I want is the one that seems to stray from the simple use CWM method. Specifically as it relates to backup and recovery. Right now Vegan is very stable and does everything I want it to do. So, why change... because from what I have read, Calkulin's ROM does everything, is stable, and does it with overclocking built in. And I can't help myself.
If my Tab goes all Charlie Sheen with this upgarade, I need to be able to find my way back. I can use CWM to make a backup of my current setup however I am concerned that all the other steps for this ROM ( using Calkulin's format and nvflash) will obliterate my backup and my CWM install for that matter.
I can use a search function. I am not asking to be spoon fed. Vegantab 5.1.1 is arguably one of the most installed ROMS on the GTAB and I'm sure there are many people who will want to take this route to Calkulin. If someone has made this jump, I think that they would be helping out many here by posting a step by step or at the very least, a what to be careful of post.
crutzulee said:
Calkulin's ROM does everything, is stable, and does it with overclocking built in. And I can't help myself.
Click to expand...
Click to collapse
It does not support overclocking, as none of the kernels do at this time (unless that has changed since last night). Honestly, unless you want to tinker for the sake of tinkering, I'd leave Vegan on there.
Um, Calkulin gTab 1.1 doesn't require anything special to flash it. It was about as easy as it gets. Use CWM recovery to run his format all.zip, his rom update.zip, and if you want a custom kernal update.zip. Reboot and you are done.
Make a backup and copy your cwm file to a PC as a backup. I would use the format all if switching from vegan to a tnt lite varient. Also I would invest in titanium backup. It will save all your apps and data that you can back up on PC and restore after a new rom is flashed.
That said, I say stick with vegan. I love to tinker but I always come back to vegan 5.1.1.
Good luck
OK, I totally suck....
My head got turned inside out. I confused Calkulin' s format all zip with the one in this thread:
http://forum.xda-developers.com/showthread.php?t=974422
and started to think that this process was a lot more involved. I guess researching too much is not always a good thing.
@ramerco I suppose you have flashed from Vegan to Calkulin's. I guess his format all.zip doesn't take CWM off like the one from the other post? Is switching back and forth as easy as choosing your backup?
crutzulee said:
OK, I totally suck....
My head got turned inside out. I confused Calkulin' s format all zip with the one in this thread:
http://forum.xda-developers.com/showthread.php?t=974422
and started to think that this process was a lot more involved. I guess researching too much is not always a good thing.
@ramerco I suppose you have flashed from Vegan to Calkulin's. I guess his format all.zip doesn't take CWM off like the one from the other post? Is switching back and forth as easy as choosing your backup?
Click to expand...
Click to collapse
I've been switching from TnT-Lite/VeganB511/Vegan7 GB/Calkuin's multiple times just using CWM backup/restore with no issue.
Remember to do 3 wipes before restore or flashing firmwares:
- Wipe data/factory reset.
- Wipe cache.
- Wipe Dalvik cache
@rickyt63 Are you doing these three wipes instead of Calkulin's format all or in conjunction with it.
Also to those who have tried both Vegan 5.1.1, Vegan 7 and Calkulin can you give your brief comparisons of these three? Pros, cons, which do you prefer? Why?
I also have been doing a lot of switching between 5.1.1 tnt lite vegan ginger experimentals just using CWM like above - you just need to do a factory reset wipe cache and the dalvic cache. I think it helps to wipe dalvik cache again after the ROM is flashed. Calkulins Rom is by far the fastest and when you flash clemsyn's froyo v3 kernel on top of that you get a great result. Titanium backup allows you to easily restore all your apps and settings even after a factory reset
Clemsyn said that he has a new kernel tweaked just for calkulins rom which he may release soon.
Thanks for the clarification, rocky3. The guy I bought the GTAB from used CWM to erased all his user data before he gave it to me but I know that I either have Titanium backup on there or have the .apk in my download folder.
I'm off to learn more. Thanks again!
crutzulee said:
@rickyt63 Are you doing these three wipes instead of Calkulin's format all or in conjunction with it.
Also to those who have tried both Vegan 5.1.1, Vegan 7 and Calkulin can you give your brief comparisons of these three? Pros, cons, which do you prefer? Why?
Click to expand...
Click to collapse
I did not use Calkulin's format when switching roms. Only 3 wipes.
Here are some thoughts about Roms: They're all fast and stable IMO.
1) TnT-Lite V4.2.5: Quadrant score ~ 2400.
- Pro: Fast and stable. Did not delete media from sdcard2.
- Con: boot up seems a little slow due to sdcard2 scanning, but after scanning it's fast.
2) Vegan V1B5.1.1: Quadrant score ~ 2600-2700.
- Pro: Fast and stable. A tad faster than TnT-Lite.
- Con: media delete from sdcard2. fixed: create a ".nomedia" file in sdcard2.
3) Calkulin V1.1: Quadrant score ~ 2600-2700.
- Pro: Fast and stable. A tad faster than TnT-Lite. Monster Madness run flawlessly.
- Con: media delete from sdcard2. fixed: create a ".nomedia" file in sdcard2.
4) Vegan7 Ginger Bread Experimental
- Pro: Fast, Nice Ginger Bread UI
- Con: Audio still clunky, some games don't work properly vs. TnT-Lite/Vegan V1B511
BTW, I use TnT-Lite or Vegan V1B511 as daily driver.
Hope this help.
Rich, thanks so much for your reply! When I look at your evaluation of vegan 5.1.1 and calkulin and I couple that with Butch's advice here and elsewhere, it makes my decision easy. For now, I will stay put with Vegan.
At some point, I will have to nvflash back to stock in order to take a viewsonic update ( I assume this will be the only way to get a honeycomb based rom, if that is even in the cards for the gtab). At this point, it doesn't seem that there is anything out there worth risking what I have now... a perfectly stable rom which does everything I need it to do with a full market.
I still get the itch to change up my tab even though I love where I'm at with VEGAn beta5.1.1, so I started changing themes, bootanimations and boot logos. There are some pretty cool themes made by gto777 that flash with cwm or metamorph. You can find those in the apps and themes thread. Awesome boot animations can also be found there along with instructions on how to load them. If you already know that nvflash is in your future you may want to get a little practice in with it early by changing your boot logo. Nothing made me happier than getting rid of the birds on boot and changing it out for a nvidia tegra2 logo. Its a fun task and there have been people posting their custom boot images for use on the sticky thread in the above mentioned section. Thinking I may re do mine this weekend, saw someone had put their name, number and email on the boot logo. Pretty cool feture as the boot logo survives through rom flashing. Seams pretty handy in cases of loss or theft.
Anyway hope this helps with the flashing itch. Have fun!
OK, so it seems that today's announcement puts honeycreams even further out of our reach.
I can't see myself making changes just for cosmetic purposes. I would only change for either a performance increase or greater compatability with newer software.
It seems that vegantab 5.1.1 will be it for me for a while until maybe the gingerbread version is fully baked.
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
So we are all flashing and re flashing new excellent ROMS that are being developed by the great devoted guys in here. I looked around and beside this I didn't find any TODO list before flashing.
So here is my little contribution,of the tasks I do before every flash to verify that I don't loose any data,but only upgrade my beloved device:
CONTACTS:
Since I'm not using my google account to sync my contacts(I'm a little bit envy of my privacy regarding the people I'm in contact with) - backup contacts using the import function in the contacts section
SMS/MMS:
Backup my sms/mms using any of the much too many apps in the market
APPS(Here is a section that I know will cause a lot of discussion):
I don't use titanium - I tried to use it during my first months with this phone I just didn't like it.I know it could be great to just save everything using it but I found it..hmmm...not suiting my needs and wants so I don't use it.
Instead recently I found a great feature in File expert which lets you backup your APKs(without the data,i.e. scores in games) - I find it very convenient because when I flash I want a clean start where I know exactly what I put back into the phone.
LAUNCHER:
I'm putting not a little effort to make my phone look as awsome as possible(and I'm sure you are too) so in order to save the trouble of configuring your preferred launcher after every flash - just back its settings. most of the used launchers have this option in their settings.
BATTERY:
Be sure you have enough battery life - best practice(which I admit that I'm not always follow)is to fully charge your phone before flashing.
FILES:
I personally always put my current rom zip and the one I'm about to flash on the sdcard to be on the safe side(boot loop for example that can be caused from bad download of the zip)-that way you always have a backup plan.
Also I'm trying to always backup all the content of my sdcard to my computer while I can, who knows what will happen during the flash - maybe you'll have to format your sdcard without any access to the data on it
UTILS:
even if you are just flashing using the CWM be sure to have a setup environment for ODIN:drivers,odin,tars etc.
And last but most important - NANDROID BACKUP:
Always and I repeat Always make a nandroid backup(if you are on the GB kernels I think there is a problem with backup/restore so I heard a solution is to flash the Bali kernel and make a restore with it - search the forum for more details.
That's it - I hope I didn't forget anything.
Please if you have any suggestions/comments don't hesitate to bring them up and I'll update this post if needed.
Enjoy
Thumbs up, bro.
I'm a big fan of Titanium backup though..
I will definately look at file expert to be using up to date supplemental apks when building a ROM.
Sent from me
For apks I just copy the install file from data/app or system/app to my sd card/app. This probably takes a little longer than batch functions. The only problem i encounter with this method is the need to push some apks back to system/app when they won't install properly. I like to reset my launcher after a flash but all of this is just personal preference
Post logs not complaints
Good stuff. Stuff that should be in the wiki Note the issue with CWM & GB is fixed in the later releases (version 5, I think) fixes that problem. I know it's available in bhndven's KJ6 kernels but I'm not sure about elsewhere.
Smells sticky...
Sent from my SGH-T959V using Tapatalk
stephen_w said:
Good stuff. Stuff that should be in the wiki Note the issue with CWM & GB is fixed in the later releases (version 5, I think) fixes that problem. I know it's available in bhndven's KJ6 kernels but I'm not sure about elsewhere.
Click to expand...
Click to collapse
Yes I heard about this but I haven't tried it yet and also I think most (if not all) the ROMs here still use the old CWM so...
alon2 said:
Yes I heard about this but I haven't tried it yet and also I think most (if not all) the ROMs here still use the old CWM so...
Click to expand...
Click to collapse
The ROMs themselves can be flashed from either. It's the Nandroid backups/restores that have an issue
stephen_w said:
The ROMs themselves can be flashed from either. It's the Nandroid backups/restores that have an issue
Click to expand...
Click to collapse
exactly what I meant
OK...Let's get something out of the way before anyone start getting irate with me and saying things they shouldn't be about this thread does not belong here...
THIS IS NOT A ROM...does it have to do with Development? I believe so....
We have always been instructed by every ROM Devs that we have to WIPE Everything in order to get our ROMs stable and running as it should...well this post goes counter to what you've been told by almost any post on XDA-Dev
I am addicted to flashing ROMs to see which best suits my needs, however the pain of having to install my apps (I have more than 150...don't ask) usually kept me from trying as many as I would like to....started thinking about how DT APP2SD work...since it is a partition that is completely separated from where the ROM is flashed...WHY DO WE HAVE TO WIPE IT??? So, I started flashing different ROMs, from ICS, Gingerbread to even Froyo to test my theory. Low and behold...more than 95% of my apps held intact (albeit no DATA - you can use Titanium or MyBackup Root to restore the Apps Data) with no hiccups when running from one ROM to another. I have flashed from AOSP to SENSE to MIUI...same result, my apps remain intact as long as I wipe EVERYTHING EXCEPT the SD-EXT...DALVIK CACHE HAS TO WIPE...even though part of it is on the Extension!!!
The reason why is simple. Any DEVs that baked DT APP2SD into their ROMs essentially call for this partition at boot...and once the ROM call for this partition...all the apps that are located in there still remain and the ROM uses it as if it was part of the ROM.
Also, I have even tested it so extensively that I flashed a Sense, an AOSP and ICS independently - after making sure my ROM was stable, reboot to RECOVERY and plug my phone to my PC running Linux....automatically the SD EXT pops up and I dropped all my apps (again, more than 150) to it...and KABOOM!!! Upon reboot...all my apps started showing up.
Again, I have no intent to take space from the DEVs who are doing a GREAT job supporting our phones....
I am posting this in the hope of helping those who flash often and also the Devs themselves from having to reinstall all their apps everytime they flash a new ROM.
If the MODs feels like this does not belong here...please feel free to move it. I think that it could play an integral role in development to all the Devs out there, hence why I am posting it here.
PS: I am not here every day, I have two little ones and a beautiful wife that I try spend as much time with...so please be patient with me if you PM me for more details on how to do this.
If this helps you in any way, please hit the thanks button...
Again, thanks to all the great works the Devs are doing!!!!
I have done this before and it does work. The only thing that keeps me from doing this is the lack of the ability to do a batch data only restore with titanium. Am I missing something? How do u quickly restore the data to your apps?
do a batch, and at the top, select data only.
lawsonmh15 said:
do a batch, and at the top, select data only.
Click to expand...
Click to collapse
Ooooohhhh......how did I not put 2 and 2 together. Thanks.
Would it not depend on the ROM your flashing?
i've been doing this for awhile, jus thought it was common knowledge. there have been some apps that FC, but i'm a FLASH chronic, and reinstall apps wud suck. ROOT UNINSTALLER is also a great app to do BU's.
I've done the same thing a couple times in the past (between CM and Sense) but always had nagging doubts that I was screwing something up somehow... Good to know that someone has taken the time to confirm that this is actually a reasonably safe process! I just had to do a nightmare manual one-by-one app restore on a ROM I flashed but I'm glad that now I can comfortably use this trick in the future.
Thanks man.
The reason for a full wipe is that most people don't have their sd card partitioned.I myself have partitioned mine and do exactly what you suggested and it does work,i figured this out after wiping the sd-exta few times,1 time i decided not to,i noticed my apps were still there after i installed another rom.Of course if you have a google account,google keeps your apps and contacts backed up.
Would this also apply for those that have partitioned sd and have a Sense 3.0~3.5 ROM installed? Question is because some devs, if not all, set the rom to save part of the rom on sd-ext partition.
I have been doing this all the time for sense and asop roms, works great. Off topic - wiping more than once is BS unless you have bad nand or using bad wiping program.
Happy to see that some of you find this information useful. I just didn't want to get screamed at for posting it here.
It's a little I can help with in contrast to the great work the devs are doing
Sent from my PC36100 using XDA App
dragon_rckr said:
Would this also apply for those that have partitioned sd and have a Sense 3.0~3.5 ROM installed? Question is because some devs, if not all, set the rom to save part of the rom on sd-ext partition.
Click to expand...
Click to collapse
It should have no impact because essentially your app folder is where everything is kept. If the Dev add some system info to the Ext it won't mess with your apps.
Sent from my PC36100 using XDA App
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.