Develop Bugs

[Recovery][TWRP][P930 / SU640] TeamWin Recovery Project 2.6.0.0 [2013-07-30]

{
"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"
}
P930 and SU640 now officially supported by TWRP team. I will no longer be building recoveries for these devices. However I will keep this thread updated to the best of my ability.
Team Win Recovery Project, or twrp for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. 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.
Click to expand...
Click to collapse
If you want more information about twrp please go to this page.
Phone look:
CHANGE LOG: http://www.teamw.in/project/twrp2
DOWNLOAD:
P930: http://www.teamw.in/project/twrp2/162
SU640: http://teamw.in/project/twrp2/167
Installation Methods:
1 - GooManager (Android App)
Code:
Download the GooManager app from either location:
[URL="https://market.android.com/details?id=com.s0up.goomanager"]Market Link[/URL]
[URL="http://goo.im/devs/s0updev/gooinsideme"]Direct Download[/URL]
Install the app and open it.
Tap menu then hit Install OpenRecoveryScript.
Tap Yes.
Verify that the filename displays your device's code name and hit Yes.
The file will download and your device will reboot and install the recovery automatically.
2 - ADB
Code:
adb push openrecovery-twrp-*.img /sdcard/
adb shell
su
dd if=/sdcard/openrecovery-twrp-*.img of=/dev/block/mmcblk0p13
3 - Terminal Emulator
Copy openrecovery-twrp-*.img to root of SD card then in your terminal emulator type the following:
Code:
su
dd if=/sdcard/openrecovery-twrp-*.img of=/dev/block/mmcblk0p13
BUGS:
If you have found a bug, please consider posting it here,possibly with a recovery.log. It's very hard to keep up with multiple threads for multiple devices. Please search the issues list first. Your issue may have already been reported.
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
DISCLAIMER:
I take no responsibility for bricked devices, nuclear wars or such things.
CREDITS:
TeamWin for making the recovery.
CyanogenMOD team for the device tree.
Goo.im for file hosting.
Thanks to Dees_Troy and TweakerL from twrp IRC for their help and guidance.

can 640 use it?thx for ur work
Sent from my LG-SU640 using xda premium

范凯爱西西 said:
can 640 use it?thx for ur work
Sent from my LG-SU640 using xda premium
Click to expand...
Click to collapse
maybe. like p930's cwm recovery?

范凯爱西西 said:
can 640 use it?thx for ur work
Sent from my LG-SU640 using xda premium
Click to expand...
Click to collapse
TBH I don't know and have no way of testing but my guess is that it should work. However if you are going to test make sure to use all the precautions you can and that you have time to unbrick if needed. Plus this is still in beta stages and not fully functional.
Let me know if you try and it works. Good luck.

OK I WILL TEST FLASH IT TOMORROW IN MY SU640.....THX FOR UR WORK....HOPE MORE WORK FOR P930.....Sorry for my bad English....谢谢。

nexwave-mat said:
TBH I don't know and have no way of testing but my guess is that it should work. However if you are going to test make sure to use all the precautions you can and that you have time to unbrick if needed. Plus this is still in beta stages and not fully functional.
Let me know if you try and it works. Good luck.
Click to expand...
Click to collapse
Hmm, I suspect it won't work. There are separate CWM builds for SU640 and P930. I assume there is some reason for that.

drumist said:
Hmm, I suspect it won't work. There are separate CWM builds for SU640 and P930. I assume there is some reason for that.
Click to expand...
Click to collapse
Could you please link the CWM .img for the SU640? I checked CWM's site and was unable to find it. I would like to compare the two.

nexwave-mat said:
Could you please link the CWM .img for the SU640? I checked CWM's site and was unable to find it. I would like to compare the two.
Click to expand...
Click to collapse
Ok,i sent these in your mail:[email protected]!!! If u complete,plz upload it.....i first use it...haha....thank u...sorry for my bad english...

范凯爱西西 said:
Ok,i sent these in your mail:........THX!!! If u complete,plz upload it.....i first use it...haha....thank u...sorry for my bad english...
Click to expand...
Click to collapse
I never got the email. Can you please edit your post to remove my email address? I don't want to spam bots to find me! Thanks.

nexwave-mat said:
Could you please link the CWM .img for the SU640? I checked CWM's site and was unable to find it. I would like to compare the two.
Click to expand...
Click to collapse
http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.1.0-su640.img
(It's listed under LG Optimus LTE on their site.)

Delete post

slg1119 said:
I think
TWRP for P93X have bug
it have...
Unmount/mount Bug!
Thx to your job~
Sent from my LG-SU640 using XDA
Click to expand...
Click to collapse
This should be fixed in beta4.
On another note I will work on an SU640 version as soon as my schedule frees up.

nexwave-mat said:
This should be fixed in beta4.
On another note I will work on an SU640 version as soon as my schedule frees up.
Click to expand...
Click to collapse
I don't think it is fixed.
I get a bunch of lines in the log saying:
E:Unable to mount /sdcard (Invalid argument)
Click to expand...
Click to collapse
I'm on Paranoid Android/CM10 Hybrid ROM

mattman86 said:
I don't think it is fixed.
I get a bunch of lines in the log saying:
I'm on Paranoid Android/CM10 Hybrid ROM
Click to expand...
Click to collapse
Ya that is another minor bug in twrp itself but in no way a show stopper. Its caused by the fact that our device has 2 different ways of mounting SDcards. When the first fails you get the error message then it tries the second.
I've already reported this bug to the twrp team. They said version 2.3.0.0 should resolve this.
Beta4 should be fully usable however I kept it in beta stage in order to have it tested by a wider audience so please make a backup first

nexwave-mat said:
Ya that is another minor bug in twrp itself but in no way a show stopper. Its caused by the fact that our device has 2 different ways of mounting SDcards. When the first fails you get the error message then it tries the second.
I've already reported this bug to the twrp team. They said version 2.3.0.0 should resolve this.
Beta4 should be fully usable however I kept it in beta stage in order to have it tested by a wider audience so please make a backup first
Click to expand...
Click to collapse
It seems like it is a show stopper because I cant use it for it's intended purpose because it can't backup/restore because it doesn't have anything to backup/restore to/from.

mattman86 said:
It seems like it is a show stopper because I cant use it for it's intended purpose because it can't backup/restore because it doesn't have anything to backup/restore to/from.
Click to expand...
Click to collapse
Go into the install menu first. That should force a mount. Then go right back out and do your backup.
Once you have done this could you provide your recovery log please?
Thanks,

nexwave-mat said:
Go into the install menu first. That should force a mount. Then go right back out and do your backup.
Once you have done this could you provide your recovery log please?
Thanks,
Click to expand...
Click to collapse
It tells me that the backup was successful and shows the log.
At the bottom of the log, it says:
-- Could not mount: /sdcard.
-- Aborting.
Click to expand...
Click to collapse

mattman86 said:
It tells me that the backup was successful and shows the log.
At the bottom of the log, it says:
Click to expand...
Click to collapse
Can you supply your full log please? Run this command while in twrp to copy the log file to your PC.
Code:
adb pull /tmp/recovery.log
Thanks

nexwave-mat said:
Can you supply your full log please? Run this command while in twrp to copy the log file to your PC.
Code:
adb pull /tmp/recovery.log
Thanks
Click to expand...
Click to collapse
http://pastebin.com/LdGuWbUM

mattman86 said:
http://pastebin.com/LdGuWbUM
Click to expand...
Click to collapse
Very particular, could you please test with another sdcard or reformat the one you have on a PC and try again?
Thanks
Sent from my LG-P930 using xda app-developers app

[rom] [jan 23, 2013] boot2gecko crespo4g [FLASHABLE ZIP]

{
"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"
}
This is a boot2gecko (firefoxOS) rom created by myself from source for Nexus S 4g (crespo4g)
Installation instructions:
download rom
boot into cwm (twrp is untested)
FULL WIPE!!!! (data, cache, system, boot and dalvik cache!! this MUST all be done or you WILL have problems. 100% guaranteed!! b2g isn't compatible with android)
flash the zip
reboot
enjoy!
so....without further ado, I present you guys with boot2gecko for Nexus S 4g
Download:
https://www.dropbox.com/s/54miur3pozke44q/b2g-hp420-crespo4g.zip
mirror:
http://d-h.st/iIm
Broken/not working:
wireless data/mms (sms works) (APN settings need to be manually entered for data/mms)
Working:
voice calls
sms
wifi
settings (except data-related)
all apps, market, etc
anything not mentioned in the broken section
**To take a screenshot hold power while pressing home**
PS...I'm more than happy to share any & all files uploaded here with anyone who needs them...just please give credit to me if you use my files

Album link:
there are many more screenshots in the album not posted here!!
http://s1357.beta.photobucket.com/user/hp420/library/FirefoxOS
Screenshots:
(thanks darthn8ers)

So what works and what doesnt?

I'm still trying to figure that out, but from what I can tell so far, everything should work. I had to run out to do some errands after flashing it myself so I haven't had very much time to play around yet.

So I've never messed around with fastboot before, I'm looking up tutorials now. Will this wipe my sd card too or just the phone storage? And will this mean I would have to reroot if I wanted back on android? Thanks for all of your help man.

DjGeraldo said:
So I've never messed around with fastboot before, I'm looking up tutorials now. Will this wipe my sd card too or just the phone storage? And will this mean I would have to reroot if I wanted back on android? Thanks for all of your help man.
Click to expand...
Click to collapse
no, it won't wipe your SD card. You will have the exact same effect you would if you flashed a rom in recovery. This will replace android on your system, so if you want to go back to android you will have to reflash your rom. When you flash these img files you will lose all your device data (again....not the sd card data) just as if you've installed an android rom in recovery after a full wipe.

Does mobile data work?

abdielmix13 said:
Does mobile data work?
Click to expand...
Click to collapse
If you have the correct APN info to enter, it will. I'm currently in the process of trying to find that info.

Got a nexus 4 activated on Tmobile a few weeks ago. Now i have something cool to use my NS4G for
i'll let you know how it goes

pardonmyownage said:
Got a nexus 4 activated on Tmobile a few weeks ago. Now i have something cool to use my NS4G for
i'll let you know how it goes
Click to expand...
Click to collapse
can we start a development thread on this I would love to help out!

lamaboy99 said:
can we start a development thread on this I would love to help out!
Click to expand...
Click to collapse
a thread for what? boot2gecko? This is a development thread. If you have some help to offer, please offer away!
I've been having a lot of trouble getting wireless data running. It appears that all anyone should need is the proper apn settings to input for it to activate....but I haven't had any luck finding a good deal of the necessary info I need. I even went as far as to contact tier 2 tech support at sprint, and they couldn't help me either.
after about a week of searching, calling, emailing, chatting, etc. I threw the project to the side burner for the time being. I decided to spend some time learing about compiling aosp, cm, etc...maybe the issue is in there somewhere. Since I'm a linux n00b I did a good amount of messing my system up several times...but I finally got it right. I formatted the whole hard drive, installed ubuntu, set up the boot2gecko environment immediately after installing, and only the b2g environment. I flashed a factory image to my phone for the proprietary blobs, just in case that was the problem, then I re-synced the repo and built b2g from source again. I sill have the exact same problem I did with the first build. Wireless voice works, wifi works....wireless data does not.
If you can help any, I would really appreciate it. I know ns4g has to be fully supported since it's in the list both on mozilla's site and in the ./config.sh list of devices.

Added some screenshots here:
http://forum.xda-developers.com/showpost.php?p=36665317&postcount=2
(thanks darthn8ers)

updated the rom
new build, same bugs....but a flashable zip install with cwm (twrp untested)

Test
Edit: Finally it is letting me comment. Yay!!
I sent you a PM hp420. A couple actually, sorry. I have tried the new ZIP and I am still not able to get voice to work, so I can't try anything APN wise with any hope of success. Are you doing anything special to get it going?
Also, in researching this, and my own experience. It seems it is required to manually wipe /system before installing the ZIP to boot properly.
Sent from my Nexus S 4G using xda premium

I tried the zip, wouldnt boot and it was using my old roms boot animation.

DjGeraldo said:
I tried the zip, wouldnt boot and it was using my old roms boot animation.
Click to expand...
Click to collapse
You must not have wiped at all or you missed a partition

I didn't even think about my issue possibly being I am on an mvno, Ting. It shows as Sprint in android though. Might be my voice issue.
From android, try putting "*#*#3282#*#*" in the dialer. View>data profile. Maybe that username will help? Mine is different as I am on Ting.
Sent from my Nexus S 4G using xda premium

Wow this looks interesting
Sent from my Nexus S 4G using xda app-developers app

hp420 said:
You must not have wiped at all or you missed a partition
Click to expand...
Click to collapse
I wiped everything I always do, do I need to do something special for this?

DjGeraldo said:
I wiped everything I always do, do I need to do something special for this?
Click to expand...
Click to collapse
And what do you always wipe?
Sent from my Nexus S 4G using xda app-developers app

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

[RECOVERY][jactivelte] CWM 6.0.5.1 - PhilZ Touch 6.57.9

Main thread + features + install instructions (don't follow) + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Last version can be found here:
https://drive.google.com/folderview?id=0ByEZDplbxwxJVW54a1QzNHVXZ3c&usp=sharing
How to flash
Download tar file from download link
Download odin (3.07 recommended ) just search for it on xda
Open odin
do whats here
{
"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"
}
connect device to download mode and hit start

Thanks for this :good::good::good:
This make the Modding more easyer
Downloaded
Installed
Works fine (Install ZIPs, Backup to internal SD Card tested)
Nice Work

Is installation only possible with this Windows tools? Even when an older CWM-based Recovery is installed?

defim said:
Is installation only possible with this Windows tools? Even when an older CWM-based Recovery is installed?
Click to expand...
Click to collapse
I could make recovery installers but m lazy to do so you can take the recovery out of the tar ball and flash it with heimdall if you are using linux

mythi said:
I could make recovery installers but m lazy to do so you can take the recovery out of the tar ball and flash it with heimdall if you are using linux
Click to expand...
Click to collapse
Finally we've full operational recovery.
Thanks.

The Screenshoots works in the Recovery.... but in the Aroma Installer it is not working. Do you know how i can make Screenshoots from the Aroma Installer?

Darkman said:
The Screenshoots works in the Recovery.... but in the Aroma Installer it is not working. Do you know how i can make Screenshoots from the Aroma Installer?
Click to expand...
Click to collapse
did you place aroma installer zip on the correct place on the phone

mythi said:
I could make recovery installers but m lazy to do so you can take the recovery out of the tar ball and flash it with heimdall if you are using linux
Click to expand...
Click to collapse
Thanks, I've a Windows but the USB is a little unstable...

The Aroma Installer works fine
I want only make Screenshoots from the Aroma Installer

I have to say, this is very good, still concerned that it is an unsupported recovery now, though I did see that Philz updated sources today with a fixed lib file. Good work @mythi. Are you going to update this or does it matter?

Pkt_Lnt said:
I have to say, this is very good, still concerned that it is an unsupported recovery now, though I did see that Philz updated sources today with a fixed lib file. Good work @mythi. Are you going to update this or does it matter?
Click to expand...
Click to collapse
Yeah ... Sure when the weekend comes :~)

mythi said:
Yeah ... Sure when the weekend comes :~)
Click to expand...
Click to collapse
Good, I get errors in Philz now second time using it. Here is a link to the post.
http://forum.xda-developers.com/showpost.php?p=55842367&postcount=5567

Pkt_Lnt said:
Good, I get errors in Philz now second time using it. Here is a link to the post.
http://forum.xda-developers.com/showpost.php?p=55842367&postcount=5567
Click to expand...
Click to collapse
Should be fixed on next release but m not facing issues with it anyway .. Twrp is gonna be updated to latest version too

@Pkt_Lnt the latest version doesn't boot no matter what i do , the libguitouch.a is a binary file which cannot be edited easily atleast through hex-editing , i will look on to some help but i don't gurntee it booting as Mr Philz dropped the support :crying:

mythi said:
@Pkt_Lnt the latest version doesn't boot no matter what i do , the libguitouch.a is a binary file which cannot be edited easily atleast through hex-editing , i will look on to some help but i don't gurntee it booting as Mr Philz dropped the support :crying:
Click to expand...
Click to collapse
Why would he post the fact that it needs fixed and the fix in that thread then? I know he stopped support due to work, but then he must feel it important enough to post about it?

Hi guys. Does anyone know if backup and restore works on 4.4.2 kitkat with this recovery?

I'll answer my own question. Yes it does, as I did a restore from my backup last night making it, imho the best recovery for our device.
Sent from my GT-I9295 using Tapatalk 2

dazzawill said:
I'll answer my own question. Yes it does, as I did a restore from my backup last night making it, imho the best recovery for our device.
Sent from my GT-I9295 using Tapatalk 2
Click to expand...
Click to collapse
CWM is very outdated, brain dead (it will kill root on zip flashes) and unsupported. Philz is a better choice if you like that kind of recovery, but it is abandoned as well. TWRP is a better choice if you grab the one from the Multi-ROM thread. http://forum.xda-developers.com/gal...mod-multirom-v30-multirom-twrp-i9295-t2962492

philz touch builds are currently broken on cm12 so there isnt much todo on cm12 , will see if its same on cm11

Am i the only one with following problem?
When i turn off the phone and plug in the power cable, the Stock charging animation appears but its freezed. After 15 seconds a smaler charging animation appears. Next thing is: During this, i cant use the power button to power on the phone. The phone restarts, but it will go back into the charging animation. I must unplug the power cable to boot the phone into android.
I think this is a problem of CWM/PhilZ ?!
PhilZ Touch 6.57.9 CWM 6.0.5.1 with CM12 official nightly.