• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM] CM7 TG-Reloaded (Final: 03-25)

So, I just grabbed the 2-18 (from today) build, and flashed it (from a new stock triumph), and I've flashed the gapps-signed zip from the SD card using CW, but I don't have any gapps.

The gtalk .apk zip worked just fine though. Any thought? I've tried re-flashing it a few times, to no avail.
 
So, I just grabbed the 2-18 (from today) build, and flashed it (from a new stock triumph), and I've flashed the gapps-signed zip from the SD card using CW, but I don't have any gapps.

The gtalk .apk zip worked just fine though. Any thought? I've tried re-flashing it a few times, to no avail.

Here's the steps you should've done (or need to redo):

1. Download ROM.zip, gapps.zip, gtalk.zip from post #1 & put on /sdcard.
2. Boot into CWM, FACTORY RESET
3. flash ROM.zip, then gapps.zip, then gtalk.zip one right after another without rebooting
4. Reboot.
 
Yup, did that and it didn't work. re-Flashed Rom, and didn't reboot before installing gapps/gtalk this time and that seemed to do the trick. For whatever reason, the market warning for downloading the gapps came up for me the first time, I clicked ok, but nothing happened, it was in a "stuck" state or something. Since I just flashed, reflashing was easiest, and I got a do-over, and the second time around it didn't get stuck and actually downloaded the apps :)

Thank you!

Edit: This is an awesome rom, and I'm really enjoying it. Thanks for all the hard work :)
 
I am on 2/16 build with 2/08 kernel. Where I am staying days the 2_18 build is too large to download. Am I missing anything of just flash the 2/18 kernel or is that basically what the new build is?
 
Hey, this rom touch drivers are not seem's to working with other fig_fbo devices.
i think edowar also included this driver in cm9 update that's why touch is not working on device's. so he given a patch with older touch driver's...!!
I like your rom, that's why i ported your rom to my CSL-MI410 but touch is not working with your's boot.img, but with edowar cm7 boot.img touch started to working...!!
Is there any think you can do it to work with other device's ??
 
I am on 2/16 build with 2/08 kernel. Where I am staying days the 2_18 build is too large to download. Am I missing anything of just flash the 2/18 kernel or is that basically what the new build is?

No need to upgrade if you have 2/16 with 2/08 kernel already.

Hey, this rom touch drivers are not seem's to working with other fig_fbo devices.
i think edowar also included this driver in cm9 update that's why touch is not working on device's. so he given a patch with older touch driver's...!!
I like your rom, that's why i ported your rom to my CSL-MI410 but touch is not working with your's boot.img, but with edowar cm7 boot.img touch started to working...!!
Is there any think you can do it to work with other device's ??

The only thing changed is the capacitive button order will be detected correctly on other devices. If it has never worked on that device, then someone else will have to look into it, but edowar has gotten it to work with his ROMs. I just made sure the touchscreen source code recognizes other devices like originally.
 
Anyone noticing that the gallery isn't showing the bottom/right part of images? Not sure since when it's been happening, but I cleared dalvik-cache/cache and it's still happening. Haven't done a factory reset.
 
Anyone noticing that the gallery isn't showing the bottom/right part of images? Not sure since when it's been happening, but I cleared dalvik-cache/cache and it's still happening. Haven't done a factory reset.

Just checked and no issue's on my end.

On another note,

Love the CM9 Boot Animation but no yet so much on the actual CM9. Decided today to grab the bootanimation.zip out the system/media folder from the CM9 Rom using 7zip and overwrite the corresponding file in CM7's corresponding directory and it worked like a charm, I love that animation. Also set the permissions to what was set on the CM7 bootanimation.zip file after overwriting it with the CM9 bootanimation.zip file. Sorry if this has been previously discussed. Otherwise is very easy and much more pleasing then my little blue skateboarding friend.



Permissions of original file, ___________ xx#
X=box that should be checked,_______ x##
#=box that should not be checked.___ x##
 
I currently have CM7, 02-02 build. I would like to use the latest build (02-18). Do I flash like Im installing a new rom and if I have to do that, then I take it I have to back up my apps then with tb and then restore?? Or, if I dont flash, then how exactly do I install the latest build?? Is there is another way of intalling without flashing, how do I do it with keeping my apps then?? Thanks
 
I currently have CM7, 02-02 build. I would like to use the latest build (02-18). Do I flash like Im installing a new rom and if I have to do that, then I take it I have to back up my apps then with tb and then restore?? Or, if I dont flash, then how exactly do I install the latest build?? Is there is another way of intalling without flashing, how do I do it with keeping my apps then?? Thanks

Simply boot into recovery mode, wipe cache & dalvik-cache, flash the new ROM, and your apps & settings will still be there. More details in the installation instructions on post #1 & the link in there. (Flashing & wiping cache doesn't erase apps settings. Factory Reset does, but that's not required when coming from an older CM7 build)
 
Anybody have issues with market not running?
I wiped cache and dalvik, installed v 2-18, every app and setting stayed except for market.
When I launch market it asks to setup an account with a yes or no button, but both buttons quit market.
 
I know headphone works, but with build 2-16 with 2-8 kernel

headphone mic not working, but can hear other party

anyone having same issue?
 
Just had a third SOD since flashing the latest build. Had to pull battery to reset. I am using the interactive governor with my frequency setting 245 and 1024. Anyone having a similar experience?
 
Last night I installed Build 2012-02-18, coming from the original stock OS. The screen backlight no longer dims a few seconds before the screen goes black like it did on stock, and like it does on my Optimus V that is also running CM7, and on another Optimus V that is stock.

How do I get the pre-timeout dimming back? I find it very useful.

And, not as important, since I like my brightness set at about 30% most of the time, and I can adjust it manually if necessary, but is there a way to get the auto-brightness to act more like stock: When I had auto-brightness on in CM7, it seemed to vary brightness very often, which was distracting, and it was a lot more subtle on stock. In any case, I generally only need 3 levels: Lowest, when it's totally dark; 30% most of the time; and 100% in bright sunlight, so if there is a way to set that up, please let me know.

PS: Touch-screen/soft-button response seems a lot better than stock, which is one of the reasons I installed CM7. Thanks.
 
I know headphone works, but with build 2-16 with 2-8 kernel

headphone mic not working, but can hear other party

anyone having same issue?
I have had this issue for a while. My headset used to work on build 1-14 i believe then it doesnt on 2-2. I havent updated in a long while.


~ Sent from my Triumph using Tapatalk ~
 
Back
Top Bottom