Develop Bugs

[ROM] [GPL] Team Villain Presents... FroydVillain 1.7.2 (Based on CM6.1 Final)

Please read post 3 before reporting bugs/issues
FroydVillain 1.7.0
This bit's the introduction. If you're not interested in who we are, or how we got here, or are of the TL;DR mentality, then skip this entire section.
Well folks... It's currently snowy here in Scotland. Got an email to say not to try and commute in this morning, as everything was off, so I set about thinking about things to do I did some work, and then decided it was time to get something out based on CyanogenMod 6.1 (pretty much final) for the hero. Based on the last nightly, here we go...
I applied the usual tweaks to it, as this seems to be a pretty good ROM. And the best bit, no wipe required (though it's still a good idea if you can be bothered) if you are coming from FroydVillain 1.6.x. If you are coming from ANYTHING ELSE, it is required. Maybe some other ROM will work with it, but I have no idea, and don't really want to know So if you have trouble and didn't wipe, please wipe before asking for help. Let me say it again...
If you have problems with the ROM or apps or anything else for that matter, go do a wipe before asking for help. It's the first thing you'll be asked to do anyway, so save yourself the time and get a faster answer
This is based on CM6.1's nightly, which I think is meant to be the stable release for the Hero. It's certainly stable enough for my liking
As for what's new/fixed, look at the CM6.1 changelog.
Overscrolling works, apps that whined about the version string should work now, and there's a new call screen from CM that means you don't put people on hold with your ear, when on a call. Plus everything else from Cyanogenmod that got fixed or improved
Before I go onto the ROM, I would like to thank a fair load of people. First of all, all the Cyanogenmod developers. Without them, this ROM would not exist. Big props out to them for their excellent work. Next, the VillainROM developers, including Ninpo for his ARM optimisations in CM6.1, Kendon for his usual behind the scenes scripts and time in setting things up, DMzda for his dedication in helping me test this ROM in the latter stages, MikeBeecham for his artwork and designs used throughout the ROM, HomerSp for his help taking Mike's bootscreen to life, and everyone else who has been there helping... Particular thanks must go to Shen for helping me get this build out to you while I have been so busy recently. Also, big thanks as usual to Lenny, NPRussell, Mike, RaiderX, RichardTrip, Acolwill, Alankila and sorry if I forgot anyone. Their contributions have been too numerous to mention. But this ain't an Oscar speech, so I must stop now.
Finally big props go to Erasmux, whose FlyKernel 11c has been tweaked slightly for performance. Details of the tweaks below...
So here we go...
FroydVillain 1.7.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NOTES:
Nothing much, but let's proclaim the glory of CyanogenMod again Thanks guys.
INSTRUCTIONS:
1. Boot into recovery
2. Nandroid backup
3. Wipe of data, dalvik and cache (optional, but if you need help, you're gonna need to do this first before asking!)
4. Flash the ROM
5. Reboot. At setup screen, give it time to complete optimisation after boot... Should settle down in about 5 minutes, more if you didn't wipe EXT.
Your download link:
http://www.villainrom.co.uk/forum/showthread.php?3698-FroydVillain-1.7.0-Released!
e989a86d44bea67e0a56499cab009bdd FroydVillain1.7.0-signed.zip
A kitchen is available at http://www.villainrom.co.uk/forum/showthread.php?3698-FroydVillain-1.7.0-Released!
Addon Zips
Some optional things you might want to try installing:
Ubuntu Fonts (flashable zip) - Screenshot 1 - Screenshot 2 (thanks DMzda)
Finally...
Join us on irc for banter (chat.freenode.net : 6667 - #villainrom) for support!
We hope you enjoy the ROM!
Finally, kernel tweaks are exact same as last time, in 1.6.0, so see that thread for info.
Base kernel (cheers, Erasmux, and big props) https://github.com/erasmux/hero-2.6.29-flykernel/tree/flykernel-11c

Optional FroydVillain Update to Re-Enable Trackball LED
Re-enables trackball LED for incoming calls and SMS messages. This is an optional zip for those who want this feature back. Future updates will not depend on this, it is not a required update.
http://www.villainrom.co.uk/forum/s...-Update-Released&p=35279&viewfull=1#post35279
FroydVillain 1.7.2 Update
Fixes voice search and speech support. Flash over 1.7.1. You MUST install 1.7.1 first, or you won't get those fixes. This goes in ADDITION to 1.7.1
http://www.villainrom.co.uk/forum/s...-Update-Released&p=35279&viewfull=1#post35279
FroydVillain 1.7.1 Update
Fixes twitter, HTC IME, a few other apps that are missing from market. Flash over 1.7.0. Then use manage applications to clear market data
http://www.villainrom.co.uk/forum/s...-1.7.0-Released!&p=35118&viewfull=1#post35118

Before Reporting Bugs/Errors/Problems/FCs/etc...
In order to help people sooner, and reduce the number of repeat reports, please observe the following before reporting a bug along the lines of "GPS is broken, HTC_IME mod FCs, it won't boot, it's slow, it's got poor battery, this breaks..."
1) Look in post 2 for any updates. Flash any with a version number, there's no need to flash optional ones unless you want to.
2) Search this thread for a keyword. eg. if gps isn't working, search thread for "GPS". If apps are missing from market, search "market". See if it is fixed, or already reported.
3) If there is no patch or fix, turn off the phone, remove your SD card, and boot the phone with no SD card. Does issue persist? If you need a memory card to test the bug, use a blank, freshly formatted spare, with just one partition.
4) If this cures the problem, you need to clear out your SD card. Back up your apps, and wipe apps2sd partition if you use it (Wipe EXT from recovery). See if problem is cured (with SD card inserted in phone). If it is, stop here, and enjoy the ROM.
5) If issue persists after removing SD, turn off phone, insert SD, boot to recovery, nandroid, wipe Data, cache, Dalvik cache. Reflash ROM and all patches. Turn off phone. Remove SD card. Boot.
6) If issue is solved, try with sd inserted now. Looks like you just needed a wipe. If not, please report the bug using the usual procedures. Mention you got to "step 6" with no resolution.
This will alleviate about 80% of bugs, I would estimate, allowing me to work on the remaining 20% not cured by this.

Sweet thanks Pulser another great realese from Team Villain

Awesome!
Sent from my HTC Hero using XDA App

Running it now sweet thanks a lot : )
Sent from my HTC Hero using Tapatalk

wow... that was quick! Thank god for snow hehe..
You say no wipe is required if coming from FV1.6.x, so i wont need to back up call log, sms, app data, backup widget positions etc etc? Just put zip file on SD card and flash?

amazing flashing now!

That's what I did no wipe just flashed and all's good : )
Calico5 said:
wow... that was quick! Thank god for snow hehe..
You say no wipe is required if coming from FV1.6.x, so i wont need to back up call log, sms, app data, backup widget positions etc etc? Just put zip file on SD card and flash?
Click to expand...
Click to collapse
Sent from my HTC Hero using Tapatalk

Many thanks, I will give it a go as soon as possible. Can someone please report about performance, batterylife etc.? I really appreciate your work.
Sent from my HTC Hero using XDA App

Many Thanks pulser_g2, appreciate your diligence!
rustynuts34 said:
That's what I did no wipe just flashed and all's good : )
Click to expand...
Click to collapse
Thanks for the info!

harlequix said:
Many thanks, I will give it a go as soon as possible. Can someone please report about performance, batterylife etc.? I really appreciate your work.
Sent from my HTC Hero using XDA App
Click to expand...
Click to collapse
Performance no worse than 1.6.
No idea about battery, it's a bit soon yet for people to be able to tell. I see no reason it won't be good though

Thanks for this! I'd been flirting with Floyo after being a FV diehard for a few months, but I've just flashed this ROM and it's looking good so far.

ROM runs fine, but Twitter and Tweetdeck 'gone'. Posted a bug report on VR.

UbuntuBhoy said:
ROM runs fine, but Twitter and Tweetdeck 'gone'. Posted a bug report on VR.
Click to expand...
Click to collapse
This one is weird... I will look tomorrow to see, but toiteur is fine here.

Yeah, Seesmic also works fine, just the two I mentioned.

Sorted it.
Download this file
http://db.tt/MUiuogS
And put in /system/etc/permissions
Chmod the file 644, and reboot and twitter will return
Will release as zip tomorrow if nobody else has done so by then

pulser_g2 said:
And put inside it
Code:
Click to expand...
Click to collapse
haha, I don't think that's going to do much my friend.
forgot to paste the code maybe?
and congrats on the new release!

Cheers Pulser, will check in the morning. Far too tired right now.
Sent from my HTC Hero using XDA App

UbuntuBhoy said:
ROM runs fine, but Twitter and Tweetdeck 'gone'. Posted a bug report on VR.
Click to expand...
Click to collapse
pulser_g2 said:
Sorted it.
Download this file
http://db.tt/MUiuogS
And put in /system/etc/permissions
Chmod the file 644, and reboot and twitter will return
Will release as zip tomorrow if nobody else has done so by then
Click to expand...
Click to collapse
thank you, I've got the same issue here.
missing tweetdeck, twicca and twitter for android.

ROM Factory v1.7.1[May/12/2012]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And thank you all for your Ad clicking and donations. You guys are awesome!
Android Market Link [free]
ROM Factory​
What is ROM Factory?
Its a tool that will allow the user to create a picture perfect .img from your boot and system partition. It will then create an update.zip from it.
What is a "Fruit Cake"?
A fruit cake is the finish product, a self contain rom, already ready for installation, already inside an update.zip.
So really what does it do?
It allows a bootloader unlocked user to create a full copy of their boot and system partition. All of it, including mods and changes done to either one of those partitions.
Can this be use for easier rom development?
Yes! Beyond just its normal capabilities! After installing the resources you can modify the script and add things to it in *sdcard* /fcm/workdir! Once you are done adding and changing things in there, press "Create ROM".
Supported Devices:
olympus (atrix), sunfire (photon), triumph, WX435, fb0 (triumph), p999 (lg g2x), p990 (lg o2x), p970 (lg optimus black), ace (htc desired hd), pyramid (htc sensation), galaxys2, GT-I9100, GT-I9100M, GT-I9100T, SGH-I777, SGH-I727, hercules, crespo (nexus s), crespo4g (nexus s 4g), toro (cdma galaxy nexus), maguro (gsm galaxy nexus)
Experimental Support:
umts_jordan(defy), wingray, stingray (xoom)​
Your phone must be rooted!
Step One: Press the Install Resources button on screen.
Patience this step could take up to 5 minutes.
Step Two: Press the Create Fruit Cake button on the screen.
Patience this step could take up to 5 minutes.​
You use this application at your own risk, I am in no way responsible for any damage this application causes.​

Oficial Support for Galaxy S2
Back Up mode = Further information is needed to enable back up mode for this device

Am I right to understand that this is an alternative to taking Nandroid backup?.

hacksome said:
Am I right to understand that this is an alternative to taking Nandroid backup?.
Click to expand...
Click to collapse
no 10 xchar

So it will create an update.zip which is CWM flashable? How about generating a .tar.md5 for Odin?
Anyways, great work! Looking forward to this!

hacksome said:
Am I right to understand that this is an alternative to taking Nandroid backup?.
Click to expand...
Click to collapse
Sounds like it, looks cool non the less.
Sent from my GT-I9100 using XDA App

Kingybear said:
Sounds like it, looks cool non the less.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Afaik a nandroid backup is everything including data folder. This one i think is a little less than that. As op said it copies the rom so devs can pass them to their beta testers etc. A nandoid backup is including ur personal settings like bookmarks or last viewed webpages and contacts etc. And a nandroid backup is recovery dependant. Afaik a nandroid from a cwm v4 base wont be suitable for a phone with a cwm v5 phone.
Sent from my GT-I9100 using Tapatalk

FCM RC3 v1.4.4
FCM RC3 v1.4.4(Current Release)
Release Notes
Added Reset Option Menu.
Re-write the engine that configures the phone install!
fixed a bug on photon 4g.
fixed the force close of doom bug.
fixed sgs2att issues
fixed sgs2att install script
fixes to various bugs
Added support for latest ics
GUI Touch Ups
Added Experimental Support:
triumph, WX435, fb0, p999, p990, p970, ace, pyramid, galaxys2, GT-I9100, GT-I9100M, GT-I9100T, SGH-I777, SGH-I727, hercules, crespo, crespo4g, toro, maguro

#FCM RC4 v1.5(Current Release)
-GUI Enhancements
Multiple Screen Size support
Tablet Support
A new themed layout
NO MORE ADS
-Script Engine Enhancements
Options, ie: Dev name, rom name, save rom preferences.
-Performance
Complete Re-write of the install and create methods (faster performance)
The reset button is bye bye! The app will now erase the workdir as it creates the rom!

Hello Guys
Is anyone experiencing issues, someone msg me about some installation issues, but did not really offer any info. If you are an user and you are suffering from install issues, let me know!

guys for latest info always check http://fcm.x10.mx/joomla/

1.6 - The update that took a month. Will be release today. This will be amazing. I'm just waiting on testers.
Advance Mode
Apps Mode
Back Up Mode
New look
Open Source components
New site, new forums, new devices.
The update will be made available late tonight or early tomorrow. Depends on how tire I am after i get off work.
We are alive and kicking. Since release, Fruit Cake Maker has been downloaded 1,956 times. We are 556 active developers. A total of 12 bugs have been crushed. We currently work on 20+ devices and devices variants.
Nightlys and experimental.
Starting Feb 1st or 2nd. My build bot will begin auto compiling nightlys for those who want to experiment with the latest changes. Nightlys will be compile each night and made available no later than midnight.
An experimental build will begin to be compile mid Feb. the build will be compile every friday at 6pm. The experimental build will feture a different preference screen, and will require the user to specify all the variables. ie: boot location, system location, storage, mode. so on. This build aims at enthusiast who wish to use the tool on a non supported device.
FCM now has requirements. Busybox must be installed to use the back up mode.
Thank guys for your support.

I think it's great personally, used it on DHD also with ease.
I'm surprised this project doesn't receive more attention.
It certainly deserves it.
Many thanks

Wow. If I get it well, it create a flashable zip image of your current installation, with apps etc?
Wow. That will be a lot easier to share beta ROMs in the future.
Many many thanks.
Envoyé depuis mon GT-I9100 avec Tapatalk

I'm currently waiting on Google.
I submitted the new version into the market, but somehow i ended up with an older version being available for download. hopefully this issue will be solved soon. I'm sorry for the inconvenience.

1.6 finally!
Some of the testers are reporting errors with the new modes, but changing storage location seem to be working quit good. I will be writing a tutorial on how to properly use all the new modes. Regardless, this new version requires Busybox for app mode, and back up mode. It must be installed on /system/xbin << same location used by cm7 and cm9. I will be releasing a new version tomorrow or Thursday, to fix some of the new mode woes.
Again, sorry for the inconvenience.

Very good work!

Awesome! keep the good work, I will try it tonight from home.

Sounds Great
Hello,
The ROM Factory sounds like a great Idea, im not a developer but i can see why its great for devs,
Question is, will it be useful for just a user like I am?
if i am to use it to back up, how does it differ from Titanium and CWM NAND backup?
Thanks

Go read post #7

[DEV][WIP][ROM] CM10.2 Development thread - CALLING ALL DEVELOPERS

THIS ISN'T A PUBLIC ROM RELEASE. THIS IS FOR DEVELOPMENT ONLY. THE ROM DOES NOT BOOT. FOR MORE INFO READ THE ENTIRE POST
I've been working on bringing our device onto par with a build of Android 4.3. I've set up a GitHub organization just for our device and it has everything we need to build for the device. Now I've been somewhat quiet with what I've been doing lately and I really don't have time to list everything I've done. @bradthomas127 and I have been communicating back and forth about building. I'd say he's done just about as much work as I've done trying to get 4.3 building. Well now, after some tips from him, I've got it building. It's using, in my opinion, the best up-to-date trees there are for our hardware. I am opening this project up to anyone that can help get it BOOTING. I don't need testers as right now I feel like I myself am the best tester for now because getting adb working on a device that sticks at a blank scree is a pain in the a**. So PLEASE I encourage anyone that knows how to maintain a GitHub and can compile and do a little coding to try to help us. The more people we can get, the faster and better we can get 4.3 actually running on our device.
Here is the GitHub:
https://github.com/Primo-Dev
If you feel you are capable of helping us dev this please PM me and I may add you to the GitHub so you can contribute.
Here is the latest build:
http://d-h.st/JSo
Logcat can be downloaded here:
http://d-h.st/SYz
Now, some basic rules for this forum:
1. DON'T ASK FOR ETA OR UPDATES - This kind of stuff is hard and takes time
2. Don't ask to test - I'll open this up for testing if we ever get it to boot
3. To all other people who aren't devs: Don't post here as this is for development only. I've made this thread in hopes of finding more devs to try to help with this, not open this up as a public ROM.
What needs attention:
I'll post bits and pieces of logcat here that shows things that need to be worked on
Code:
I/auditd ( 99): Starting up
E/auditd ( 99): Failed on audit_set_pid with error: Protocol not supported
I/auditd ( 99): Exiting
W/dalvikvm( 161): PR_SET_NO_NEW_PRIVS failed. Is your kernel compiled correctly?: Invalid argument

I did not even notice this till you posted the logcat, libgenlock is not even building.
Code:
E/libEGL ( 1327): load_driver(/system/lib/egl/libEGL_adreno200.so): dlopen failed: could not load library "libgenlock.so" needed by "libEGL_adreno200.so"; caused by library "libgenlock.so" not found

Based on the logs, you'll need a kernel that has SELinux support. That is the major failure you are having. I am not sure if there will be a way to disable it.

robaho said:
Based on the logs, you'll need a kernel that has SELinux support. That is the major failure you are having. I am not sure if there will be a way to disable it.
Click to expand...
Click to collapse
That's what I've been thinking. All the devices that have been updated to cm10.2 have SELinux. Only problem is I'm not much of a kernel dev, but I can see what I can do. Also, if you take the main hardware libs from RhythmicRom and put them in cm10.2 you can get to the bootanimation.
Sent from my HTC One V using xda app-developers app

I just made a build with libgenlock.so in it, have not tried it yet.
I had to cherry pick this for SELinux support: GitHub That goes in primoc_defconfig and should take care of "audit_set_pid" & "PR_SET_NO_NEW_PRIVS" Errors.
To get libgenlock.so to build i had to bring in android_hardware_qcom_display-legacy because everything else is going ION now. display-legacy is "not" to replace qcom_display though we are already calling it in BoardConfigCommon.mk with this "TARGET_QCOM_DISPLAY_VARIANT := legacy", I used Icebox's but it is the same one we have in primo-dev <= lots of build errors though.
Edit: No boot, led blinks a couple times now. If anyone knows how to pull a logcat on 4.2+ on boot and would like to give it a try, it would be much appreciated.
cm-10.2-20130822-UNOFFICIAL-primoc.zip
-

bradthomas127 said:
I just made a build with libgenlock.so in it, have not tried it yet.
I had to cherry pick this for SELinux support: GitHub That goes in primoc_defconfig and should take care of "audit_set_pid" & "PR_SET_NO_NEW_PRIVS" Errors.
To get libgenlock.so to build i had to bring in android_hardware_qcom_display-legacy because everything else is going ION now. display-legacy is "not" to replace qcom_display though we are already calling it in BoardConfigCommon.mk with this "TARGET_QCOM_DISPLAY_VARIANT := legacy", I used Icebox's but it is the same one we have in primo-dev <= lots of build errors though.
Edit: No boot, led blinks a couple times now. If anyone knows how to pull a logcat on 4.2+ on boot and would like to give it a try, it would be much appreciated.
cm-10.2-20130822-UNOFFICIAL-primoc.zip
-
Click to expand...
Click to collapse
I'll logcat. I'll also post instructions on how I logcat on 4.2+.
Sent from my HTC One V using xda app-developers app

Hey @awidawad just an FYI the Incredible S has released CM10.2 and source is on Github. I figured it might help you guys somehow.
Sent from my LG Optimus F7 using xda app-developers app

reV17 said:
Hey @awidawad just an FYI the Incredible S has released CM10.2 and source is on Github. I figured it might help you guys somehow.
Sent from my LG Optimus F7 using xda app-developers app
Click to expand...
Click to collapse
Hmm thanks I'll do some research on github later. It has almost the same specs so it will be useful.
BTW: To anyone waiting for logcat instructions I'm trying to find a simplest way to do it with the little time I have between work and football, and school coming up.

Alright guy's i finally got it past the black screen of death but i am stuck in a bootloop, if you know how to get a logcat from a non booting ROM on 4.2+ i really need to know how or get a logcat posted on this.
cm-10.2-20130924-UNOFFICIAL-primoc.zip

bradthomas127 said:
Alright guy's i finally got it past the black screen of death but i am stuck in a bootloop, if you know how to get a logcat from a non booting ROM on 4.2+ i really need to know how or get a logcat posted on this.
cm-10.2-20130924-UNOFFICIAL-primoc.zip
Click to expand...
Click to collapse
Hey man I'll post how to when I get home
Sent from my C525c using Tapatalk 4

You need to enable adb and disable secure. If you use the eng (engineering) build. Otherwise you would need the GUI up so you can allow access from the computer due to the new security constraints.
Sent from my One V using xda app-developers app

Lucky CDMA people with half working 4.3 o-o

robaho said:
You need to enable adb and disable secure. If you use the eng (engineering) build. Otherwise you would need the GUI up so you can allow access from the computer due to the new security constraints.
Click to expand...
Click to collapse
I added ro.adb.secure=0 to the default.prop a couple days ago making the ramdisk/default.prop look like this now.
Code:
ro.adb.secure=0
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=adb
I've also tried moving adbkey.pub to data/misc/adb/pub_keys in TWRP but it gets erased as soon as i boot.

Is the USB driver working, that is, can you.see a USB device using your system devices view - varies by OS
Sent from my One V using xda app-developers app

This is how I logcat on 4.3:
First off, you're going to need a WORKING android device running 4.2+
Now:
1. Plug the device into your PC
2. Go to Settings>Development and enable adb
3. When the dialogue comes up asking to trust the computer tap yes. If it doesn't appear run "adb devices" on your PC.
4. Get a root file explorer
5. In the explorer, go to \data\misc\adb and copy adb_keys to your PC. (Copy adb_keys to your Sdcard, mount phone storage, then copy to PC.)
6. Download THIS and extract all files on your PC
7. Open up the extracted directory.
8. Place adb_keys in \data\misc\adb and then run the "Run_to_build_zip.bat" file.
9. Download THIS and flash in recovery on the device you're going to logcat.
10. Copy the zip that was just created on your PC to your sdcard and flash in recovery. (Zip will be named "adb_hack_step2_**.**.**@**_**.zip" )
Reboot, adb should now be enabled and work on the PC you used.

awidawad said:
This is how I logcat on 4.3:
First off, you're going to need a WORKING android device running 4.2+
Now:
1. Plug the device into your PC
2. Go to Settings>Development and enable adb
3. When the dialogue comes up asking to trust the computer tap yes. If it doesn't appear run "adb devices" on your PC.
4. Get a root file explorer
5. In the explorer, go to \data\misc\adb and copy adb_keys to your PC. (Copy adb_keys to your Sdcard, mount phone storage, then copy to PC.)
6. Download THIS and extract all files on your PC
7. Open up the extracted directory.
8. Place adb_keys in \data\misc\adb and then run the "Run_to_build_zip.bat" file.
9. Download THIS and flash in recovery on the device you're going to logcat.
10. Copy the zip that was just created on your PC to your sdcard and flash in recovery. (Zip will be named "adb_hack_step2_**.**.**@**_**.zip" )
Reboot, adb should now be enabled and work on the PC you used.
Click to expand...
Click to collapse
Not working for me, messed with it a couple times.

bradthomas127 said:
Not working for me, messed with it a couple times.
Click to expand...
Click to collapse
Strange... I've used that method multiple times in ubuntu.
Sent from my C525c using Tapatalk 4

awidawad said:
Strange... I've used that method multiple times in ubuntu.
Click to expand...
Click to collapse
Getting boot now, just boot loops every min.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
:highfive:

bradthomas127 said:
Getting boot now, just boot loops every min.
:highfive:
Click to expand...
Click to collapse
You might need Simon's battery fix in the kernel???
Sent from my One V using xda app-developers app

robaho said:
You might need Simon's battery fix in the kernel???
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
Do you mean this one? https://github.com/bradthomas127/an...mmit/9af6efa20ece323155a853ff508563a87670e2f0
Rukin added it 4 months ago.
You did just open my eyes though, i thought i commited the SELinux stuff but just noticed i didn't on this kernel, maybe why i am having reboots and SD card is not mounting (reason for no screen shot). Thanks :good:

TWRP Touch recovery - 2.6.3.0

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​ For Latest Download Link Click Here
full SELinux support
Features:
Tested and Working
Backup / Restore
ROM Flashing (of course :good: )
Mounting partitions (and SD via USB to PC)
Screen Timeout - Lock / Unlock (double tap to wake or use power - change timeout in settings)
adb sideload
Clock
Battery
Log
File Manager
Advanced Reboot Options
when powered off and you plug in phone it auto boots to recovery, maybe nice for someone with a broken power button? (so not really a feature...)
Haven't Tested
Fix Permissions
[*]Terminal
[*]Themes
[*]Partition SD Card
let me know if you can confirm these working, my vision is out on loan to a friend an can not test - thanks!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
*broken
SD-ext wipe/backup/restore - still working on this one, hopefully wont take too much longer to fix
anyone who wants to test will be rewarded with praise from me! should be safe, has been for me, but I guess I should say the whole I'm not responsible for xyz... but you're on xda, you know this
Just Some Random Screen Shots Of TWRP, Not From This Phone
​*oh and I have some new clockwork recoveries if you all want these too, they appear fine with the minimal test I've done, if you all want I can upload these too - built from newest source something like 6.0.4.6? cant recall the versions and am lazy now, but built for kitkat roms

For sure gonna try this out if I have some free time tomorrow. It's getting late or else I would already be testing it out now

demkantor as you advised me first i just booted the recovery .. works well
flashed recovery works as expected
i dont have sdcard so you know the broken section is not for me

Working ADB sideload confirmed
Mind sharing how did you fix that?
My idea is that the problem is in fstab.recovery, but I'm not entirely sure on that. Could you please share "device-related" changes for TWRP?

Sure thing, I hope have some time in front of a PC this next week, I'll put up a new build with sd-ext fix and post a github link and clean up the op. Sorry just haven't had like ant quality PC time in the past few months
Sent from my Nexus 7 using XDA Premium 4 mobile app

Alright, finally got around to flashing this. All the basic functionality I used CWM for, works perfect in TWRP. Pretty awesome

Man, this is awesome! I was using some old TWRP 2.2.0 version i found on some weird chinese site after failing to build it myself. Thanks fr thins man! :laugh:

awesome job demkantor
and i can gladly take all the credits for this tool :d LoL

Why switch?
Hey @demkantor,
great work again, I guess, thanks. We vision users are lucky to have folks like you still working on our device.
One overarching question--why switch recoveries, and if I do, to this TWRP or your (or Nevergone's?) CWM? I have used 4EXT (I think at your suggestion, in fact) ever since I rooted my phone in August, 2012, and no problems. I have kept up with all the latest ROMs in the Flinny line (and a few others) including 11.0, though I have now stepped back to his last 10.1 build while KitKat needs fixing. My needs are pretty basic, I suppose...I just flash the occasional new ROM, make backups, occasionally restore them (like in going from 11.0 back to 10.1.) I rarely touch adb...it just hasn't been necessary. I am perfectly happy with my phone, and marvel at its longevity!
So, stick with the latest 4EXT, or jump to something newer?
Thanks,
p-d
ps still at the U? Go to Al's for me sometime, I miss breakfast there.

Thanks!
In truth I still prefer 4ext myself, its my favorite recovery but development on it has slowed over the past year. The only reason I bothered to make this was for @AYEHAN who has a broken SD tray and needed to be able to sideload a ROM, currently 4ext is lacking this feature. So if your current recovery is still working for you then I would suggest to stick with it, TWRP is nice and I use it on most my devices (as 4ext isn't available) but if it ain't broke don't fix it!
Yeah last few days of brake before the new semester begins, and for sure will go to Al's, best whole in the wall there is!
Sent from my Nexus 7 using XDA Premium 4 mobile app

One major bug I came across, is it will no longer flash roms. Like, regardless of what the rom is it just won't flash it, it spits out
assert failed: get prop("ro.product.device") == "
E:Error executing updater binary in zip '/sdcard ,
and I know these roms all work since it was flashing them beforehand. Just thought I'd let you know
*Edit*
So any rom other than G2Slim won't flash for me. CM10.1, Flinny's CM11, etc. It's so odd
*Edit 2*
I installed CWM v5 again just to make sure it wasn't a problem with the roms themselves or my sd card, and things install fine, so it must be a random bug with twrp, hopefully a very rare one at that

I just tried and found a similar result, without looking into it much I see there are a couple update-binaries used with various ROMs and this build works for one and not the other, at least that's what I see so far as I'm coaching my friend on how to do this as the phone is with him on the other side of town right now.
I'll look into a fix for this as it would be nice to be able to flash all Roms not just some, thanks for the bug report!
Sent from my Nexus 7 using XDA Premium 4 mobile app

Fix permissions and terminal work fine, I'll try a theme if I can work out how to do it but I don't have a spare SD card I can test partitioning on. All in all great work

Thanks for running those tests, with school and not having my g2 in front of me I haven't had a chance to pick up this project, but I should have my phone back shortly. One of the things I was planning to do (after all functions are 100%) was make a few themes, which is quite easy if your interested
http://www.teamw.in/twrp2-theme-guide
It surprising how customizable and fun a recovery can be so if you get around to it I will for sure link any you make and hopefully will have a few of my on in due time
Sent from my Nexus 7 using XDA Premium 4 mobile app

demkantor said:
Thanks for running those tests, with school and not having my g2 in front of me I haven't had a chance to pick up this project, but I should have my phone back shortly. One of the things I was planning to do (after all functions are 100%) was make a few themes, which is quite easy if your interested
http://www.teamw.in/twrp2-theme-guide
It surprising how customizable and fun a recovery can be so if you get around to it I will for sure link any you make and hopefully will have a few of my on in due time
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Just tried a theme, works fine. I would make some but I have no working PC right now. Might be able to unpack and edit an existing one on device though

Needed to get a recovery compatible with SELinux support in order to install latest CM11 Alpha 3 (Flinny's).
Works fine. None of the errors above when installing CM11 and gapps.
Great work!

tried this alot of times , plus flash the recovery 3 times but could not sideload an image :/
e:/ sdcard not found something error

sorry for that, I'm sure it's a stupid question, but just to be sure...
there is no different way except flashing this .img using a pc...right? I tried using TWRP app last night but it wants to know which device is and it's not listed
thank you a lot
Alex

If you want I'll make you a flashable.zip or you can use a terminal emulator on your phone, just download to SD card and name it recovery.img
Then open up emulator
su
flash_image recovery /sdcard/recovery.img
Sent from my Nexus 4 using XDA Premium 4 mobile app

[GUIDE] Modifying 4.4.x based rom's updater-script to install in TWRP 2.5.0.0

MODIFY A 4.4.x BASED ROM'S UPDATER-SCRIPT TO FLASH WITH TWRP 2.5.0.0!
WARNING
This is a disclaimer: While this has been tested I am not responsible for ANY damage done to your device. I take no responsibility for bootloops, soft bricks, hard bricks, living brick monsters, your phone proving an omnipotent being fallible(thus negating all existence), your great aunt smoking bath salts, flying monkeys, hot pockets, obamacare, dingleberries, carnivorous dingleberries or Sundays. Use at your own risk!!
Secondary disclaimer: If you have carnivorous dingleberries then you have bigger problems to worry about - but for any phone related questions feel free to message me on here either privately or in the thread.
In honor of my 300th post here on xda I thought I should do my first guide. I decided to make this guide because some people have had issues with TWRP 2.6.x which is the version you need to flash kit kat roms. However TWRP 2.5.0.0 has been beyond stable for me and everyone I know who has used it on our wonderful ls970. So how do you flash 4.4 based roms from TWRP 2.5.0.0?! Edit the updater-script, ofcourse!!!!
Now keep in mind, the screenshots I supply will be on Linux because it is what I use - the steps should be the same for Windows, however the programs used will probably be different(Archive Manager vs 7zip/WinRar for instance). If anyone wants to do this on Windows and take screenshots I will gladly post them or give OP privileges so that you can add them yourself.
Are there any downsides to installing roms this way?
Yes - it will essentially break OTA updates for the roms. 4.4 roms built from source will always have an updater-script meant for the newer recovery versions and will not flash in 2.5.0.0. So if you want to dirty flash an update to the rom you are using, you will have to modify that updater-script as well.
Well, let's get down to business!
Things you will need:
A flashable zip file for your rom of choice(I use Vanir for this guide)
An archive manager(7zip/Winrar for Windows)
A text editor(I use gedit but Windows users will want to use Notepad++)
A working brain
Step 1: Open the flashable zip file with an archive manager
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 2: Navigate to the updater-script found in META-INF/com/google/android/
Step 3: Open the updater-script from within the archive manager. Keep the archive manager open during this process. I'm using Linux Mint 15 so it opens in gedit. Once open, scroll down until you see a bunch of lines that say 'set_metadata' and 'set_metadata_recursive'. These are the lines we need to edit.
Step 4: Now everywhere you see 'metadata' in these lines, you want to replace 'metadata' with 'perm' like in the images below.
Step 5: After replacing metadata with perm, we need to re-organize things a bit to look more like a 4.3 updater-script. After the parentheses you will see directories/files in quotation marks like in the picture below.
We need to move all of these to the end of the parentheses like so.
Step 6: The next thing we need to do is delete everything else in the parentheses EXCEPT the numbers. The numbers and quotations we just moved will be the only things left in parentheses when we are done. Also keep in mind that '0x0' will also be removed.
So - everything highlighted below, needs to go!
When you are done, it will look like this:
And when you are done with ALL of it, here is what it will look like!
Step 7: Remove asserts. This isn't always needed but it also won't hurt. The asserts placed in flashable zips are to protect you from installing a rom that isn't compatible with your device. The problem we lgog users frequently have is that our phone is called many things(ls970, geehrc4g, geespr, etc). If you've ever gotten a "Flash failed this isn't a geespr" error in TWRP, it's because that particular version of TWRP doesn't recognize your device as a geespr(even though it is). So as long as you know the rom was built for your device, it is safe to delete these lines. They are found at the very top of the updater-script like shown below.
Step 8: Save and update! Once you are done editing, simply hit save in the text editor and your archive manager should give you a warning similar to this one below.
Hit the update button and the updater-script will save inside the flashable zip!
And that's it! Your 4.4 based rom will now flash on TWRP 2.5.0.0!!
Just be careful that you edit it exactly, pay attention to the punctuation. This is not difficult but can be time consuming. Using your text editor's "Replace" function properly will help speed up the process!
So why go through all of this?
Certain users here on the lgog forums have experienced a problem with TWRP 2.6.x that essentially bricks the device. Randomly and mysteriously, the phone won't boot into the system. When trying to boot into TWRP, it will ask for a password - even though the user never supplied one in the first place. If you cancel the password, TWRP loses all functionality.
Users in other threads(specifically the nexus4 and nexus5 users) have experienced the same problem but not to the extent our lgog users have. In most cases it is because the data partition became corrupt/encrypted. The solution is to format your data partition(So best case scenario, you lose EVERYTHING). Nexus users seem to still be able to do this after cancelling the password - some lgog users haven't been as fortunate. When they cancel the password, nothing mounts, so nothing works. Even using LGNPST to revert back to stock gives an error so the phone is essentially a paperweight.
What is the cause of this?
It still isn't certain however it may be a bad emmc chip. Can't an emmc chip go bad using TWRP 2.5.0.0? Ofcourse, so this may all be superstition. It may just be a coincidence that a person's emmc chip fried while using the updated versions of TWRP. But until someone has this issue on TWRP 2.5.0.0(None have been reported as far as I know, if it happens to you, please prove me wrong), I'm going to err on the side of caution and stick with what I know works.
For most users it will just be easier to flash a different recovery like Clockworkmod but I personally wanted to stick with one recovery. Using this method, TWRP 2.5.0.0 can flash everything from stock to 4.4.x! You can look here in the lgog forums for working recoveries and their uses/limitations. But at the very least I hope this guide helped you to understand updater-scripts a bit better and the role they play in flashing roms.​
QUESTIONS?
Feel free to ask me any questions you may have. If it doesn't flash, get a recovery log(from TWRP go to advanced->copy log to sd, then boot back into your system and it will be on your internal memory as recovery.log) and send it to me. Or open the recovery log yourself and look for E: (For error) around where the flash failed. Usually you will see a syntax error and it will tell you what line it was on - that means the edit wasn't done properly but you will atleast know where it went wrong.
Thanks
@xboxfanj - for showing me how to do this in the first place
@engine95 - for all of his guides here in the threads

For Windows, use 7zip and notepad++. They work good.
Nice guide for those of us that prefer TWRP. Thanks.
Edit. That info was in the spoiler. My bad.
Sent from my LG-LS970 using XDA Premium 4 mobile app

engine95 said:
For Windows, use 7zip and notepad++. They work good.
Nice guide for those of us that prefer TWRP. Thanks.
Edit. That info was in the spoiler. My bad.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks man(out of daily thanks again) - I thought that's what Windows users should use but wasn't 100% sure.

Awesome work brother!
Sent from my Optimus G using xda app-developers app

PartimusPrime said:
Awesome work brother!
Sent from my Optimus G using xda app-developers app
Click to expand...
Click to collapse
Ditto on that!

PartimusPrime said:
Awesome work brother!
Sent from my Optimus G using xda app-developers app
Click to expand...
Click to collapse
Code-Craft said:
Ditto on that!
Click to expand...
Click to collapse
Thanks guys! My laptop is so old I cant even attempt to build anything worthwhile(damn you 32 bit!) so I can only modify stuff but will pass on what I learn to you all. As soon as I get a new computer I will be learning how to build so stay tuned.

Good job man!! Hell yeah!
Sent from my LG-LS970 using XDA Premium 4 mobile app