Develop Bugs

[Q] cm7 intallation failure

When installing CM7 in cwm I get the folowing error:
assert failed: getprop("ro.product.device")=="
R800x" || getprop(ro.build.product") == "R800x"
|| getprop("ro.build.product") == "R800x " ||
getprop ("ro.product.board") =="R800x" ||
getprop ("ro.build.product") == "zeusc" ||
p("ro.product.board") ==zeusc"
E:Error in /sdcard/update-cm-7.1.0-RC1-XperiaPla
y-R800x-KANG-signed.zip
(Status 7)
Installation aborted.
I downloaded the zeusc_beta_FXP025 archive twice, and it extracted multiple tmes as well, to be sure it want user error, sounds like a corrupt download, but two in a row? Others seem not to have this issue...
Any thoughts?
I miss CM7

You can always try opening the update .zip and deleting the get .prop lines from the update script
Sent from my R800i using Tapatalk

AndroHero said:
You can always try opening the update .zip and deleting the get .prop lines from the update script
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
thanks, I'll try that when I get my new play. the old one got bricked... hit the ok for ota by accident.

I think this guy can help you ---> http://forum.xda-developers.com/showthread.php?t=1252038

cosvel said:
I think this guy can help you ---> http://forum.xda-developers.com/showthread.php?t=1252038
Click to expand...
Click to collapse
Sorry it took so long to update this post, I've been super busy, and unable to reply. Just to let every body know, Alejandrissimo did me right he got me fixed up and back to normal (unlocked and functional) in about 5 minutes. If any body has trouble with a soft brick (i.e. no fastboot) Alejandrissimo is your man.

AndroHero said:
You can always try opening the update .zip and deleting the get .prop lines from the update script
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
AndroHero, I some how managed to get it figured out just by folowing the directions (Imagine that) on the FXP post. Running 41 goodness now.
Moderators please close thread.

I'm getting the same error when trying to install and it's driving my head in.

Scottish Husky said:
I'm getting the same error when trying to install and it's driving my head in.
Click to expand...
Click to collapse
Use the link in this post:
http://forum.xda-developers.com/showpost.php?p=18378348&postcount=80
The original 7.1.0 release seems to have been bugged, this is 7.1.0.1. Seems to be fixing any install issues.

blindingshadow said:
Use the link in this post:
http://forum.xda-developers.com/showpost.php?p=18378348&postcount=80
The original 7.1.0 release seems to have been bugged, this is 7.1.0.1. Seems to be fixing any install issues.
Click to expand...
Click to collapse
I'm getting the same error but with the .1 update... this is too weird

AndroHero said:
You can always try opening the update .zip and deleting the get .prop lines from the update script
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
Where do I find that?

This question is being asked quite a lot, it should probably be a sticky. Anyways follow this using Notepad++ to fix error status 7:
http://forum.xda-developers.com/showpost.php?p=20003695&postcount=1773

[Q] Problem - install PAC 4.1.2 or MIUI

Hello, i have Xperia S (26i) rooted. I download and install CWM, copy files of new rom to internal SDcard, reboot in recovery and make all steps, but process stops and error message appears:
assert failed: getprop("ro.product.device") == "LT26i" I I getprop(ro.build.product") == "LT26i" ==getprop(ro.product.device") ==nozomi I I getprop(ro.buil.product) == nozomi
I think the problem is conflict with lt26i and nozomi. It´s correct ? How i do to change ?
Thanks and sorry... my english is very bad..... lol

Is your bootloader unlocked?
Sent from my Xperia S using xda app-developers app

Fastboot advanced stock kernel first then try again
Sent from my JB Xperia S

I have Locked B. But try to install MIUI and error came again, the same.
Using Google i found xda link and resolution is edit build.prop and change "nozomi" to "LT26I". I try to do this :
Unzip ROM, edit build.prop and zip.
But now i have another error. I think MD5 maybe is the key..... I do no if "rom zip file" have signature or other Type of file confirm.....
Sent from my LT26i using xda app-developers app

Nvm.

sr_redhot said:
I have Locked B. But try to install MIUI and error came again, the same.
Using Google i found xda link and resolution is edit build.prop and change "nozomi" to "LT26I". I try to do this :
Unzip ROM, edit build.prop and zip.
But now i have another error. I think MD5 maybe is the key..... I do no if "rom zip file" have signature or other Type of file confirm.....
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
There's your problem, you have a locked bootloader, YOU NEED A UNLOCKED BOOTLOADER to install PAC, I dont know about miui, but anything with custom kernel YOU NEED UNLOCKED BOOTLOADER. So first unlock you bootloader then it should work perfectly fine. You seriously need to read the requirements to install a custom Rom.
Sent from my Xperia S using xda app-developers app

I know if a lot of custom roms needs unlocked bootloader. In PAC V19 i do no, But MIUI are ok with Locked bootloader. I try muiu first, But when error appears i try PAC. Im thinking if i really want to unlock bootloader.....
But thanks for that.
Sent from my LT26i using xda app-developers app

sr_redhot said:
I know if a lot of custom roms needs unlocked bootloader. In PAC V19 i do no, But MIUI are ok with Locked bootloader. I try muiu first, But when error appears i try PAC. Im thinking if i really want to unlock bootloader.....
But thanks for that.
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
flash stock rom first.. preferably using flashtool, use fw .50 or below (as long as it's ics one), root it, and install cwm. then u can flash miui.

m1st3r1 said:
flash stock rom first.. preferably using flashtool, use fw .50 or below (as long as it's ics one), root it, and install cwm. then u can flash miui.
Click to expand...
Click to collapse
I try all :
-Format
-unlock BL
-Install FW .55
But the same error appears. I really thing : in some moment custom rom say "nozomi" and my cell say"LT26i" and stopped instalation.
Now i´m downloading more ROMs to testing instalation,

sr_redhot said:
I try all :
-Format
-unlock BL
-Install FW .55
But the same error appears. I really thing : in some moment custom rom say "nozomi" and my cell say"LT26i" and stopped instalation.
Now i´m downloading more ROMs to testing instalation,
Click to expand...
Click to collapse
Updated:
TurboROM installed..... But MIUI and PAC get the same error

WTF. No one ever gave right advice. Wow.
Well, I've got sometimes the same error.
There is one solution:
Unzip installation file.
Delete this line inside META-INF/com/google/android/updater-script:
Code:
assert(getprop("ro.product.device") == "LT26i" || getprop("ro.build.product") == "LT26i" ||
getprop("ro.product.device") == "nozomi" || getprop("ro.build.product") == "nozomi");
Then zip this file back to it's place in archive. Try to install, and BOOM - it's fine now!

Dr.Alexander_Breen said:
WTF. No one ever gave right advice. Wow.
Well, I've got sometimes the same error.
There is one solution:
Unzip installation file.
Delete this line inside META-INF/com/google/android/updater-script:
Code:
assert(getprop("ro.product.device") == "LT26i" || getprop("ro.build.product") == "LT26i" ||
getprop("ro.product.device") == "nozomi" || getprop("ro.build.product") == "nozomi");
Then zip this file back to it's place in archive. Try to install, and BOOM - it's fine now!
Click to expand...
Click to collapse
I follow you tip,
Download new files from PAC and MIUI
Unzip, make changes, zip, copy to sd reboot into recovery, make all steps in PAC tutorial and nothing done:
"Finding update package
Opening update package
Installing update
Instalation aborted"
I do know what´s gonna hell ........
So hard to do one simple thing.... :crying:

sr_redhot said:
I try all :
-Format
-unlock BL
-Install FW .55
But the same error appears. I really thing : in some moment custom rom say "nozomi" and my cell say"LT26i" and stopped instalation.
Now i´m downloading more ROMs to testing instalation,
Click to expand...
Click to collapse
Try flash advanced kernel first. Then try flash Miui. Wipe all (wipe data, format system and dalvik cache).
I'm in relocked bootloader, using .55 kernel, got no problem flashing miui.maybe u did something wrong in the first steps...
Dr.Alexander_Breen said:
WTF. No one ever gave right advice. Wow.
Well, I've got sometimes the same error.
There is one solution:
Unzip installation file.
Delete this line inside META-INF/com/google/android/updater-script:
Code:
assert(getprop("ro.product.device") == "LT26i" || getprop("ro.build.product") == "LT26i" ||
getprop("ro.product.device") == "nozomi" || getprop("ro.build.product") == "nozomi");
Then zip this file back to it's place in archive. Try to install, and BOOM - it's fine now!
Click to expand...
Click to collapse
Is the wtf really necessary? Ofc, I know this solution, but I don't think it is a good solution. As you know this phone is lt26i with nozomi as its codename, and the rom op want to flash is built for lt26i, so in my opinion, it's kinda wrong change something that supposed to be working.
Sent from my LT26i using Tapatalk 2

m1st3r1 said:
Try flash advanced kernel first. Then try flash Miui. Wipe all (wipe data, format system and dalvik cache).
I'm in relocked bootloader, using .55 kernel, got no problem flashing miui.maybe u did something wrong in the first steps...
Sent from my LT26i using Tapatalk 2
Click to expand...
Click to collapse
GREAT !!! Now it´s working !!! MIUI installed. And next step is testing PAC.
Tks !!:laugh:

[Q] Need help with trying to update CWM...

Alright i'm in a pickle, tonight I was about to flash to CM 10.1.2 however when I rooted my phone I didnt update to the latest CWM. I've already wiped Data/ factory reset but when try to flash to CM 10.1.2 I get assert failed: getprop("ro.product.device") == "d2att' ||getprop("ro.build.product") == "d2att" (Status 7)
I understand I need to update CWM but how can I if I have no rom on the device currently. Whenever I try to reboot I just get the andrid guy with the red triangle on top of him and it sends me back to CWM.
Should I just pull the battery and put it in Download mode to update CWM? I don't even know if i'd be able to get into download mode 0.0 please help.
Thanks

Do you have an external SD card? If you do, simply load the new cwm zip there, insert it in your phone, and flash in cwm. It'll overwrite the old cwm.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4

Domoo said:
Do you have an external SD card? If you do, simply load the new cwm zip there, insert it in your phone, and flash in cwm. It'll overwrite the old cwm.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4
Click to expand...
Click to collapse
Do you know where I can find the Zip download?

Here you go:
http://forum.xda-developers.com/showthread.php?t=2152769
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4

khep24 said:
Do you know where I can find the Zip download?
Click to expand...
Click to collapse
clockworkmod com
you can download latest CWM from here.

[Q] Status 7, cannot overcome

Hello,
I own the wind variant of the Galaxy SIII Model T-999v
For the last...forever... I have relentlessly been trying to have Cyanogenmod 10.1.2 running on my device
I have taken every precaution, followed every method, read every thread
Lets rule out the basics...
I have:
Made sure CM is of the T-Mobile variant
Updated CWM to the latest version (6.0+) using the .img file available from their webpage and terminal emulator
Flashed the device in CWM prior to trying to install from zip
The phone is rooted and SuperSU is available
Ive tried using the in-fw version of CWM
Ive tried reverting my OS to stock 4.04 (launch date) in odin and rerooting and reapplying the latest bootloader because one thread suggested i should downgrade the baseband version from the one available in jellybean
Ive even used updated the bootloader from the link available in this thread:
http://forum.xda-developers.com/showthread.php?t=2290118
g-apps installs fine, superSU installs fine, everything with the exception of the main piece.
If anybody has any form of input into the matter it would be greatly appreciated. Cheers

Edit the update script to include your bootloader or remove the asserts. The T999v isn't officially supported by 10.1.2.

Aerowinder said:
Edit the update script to include your bootloader or remove the asserts. The T999v isn't officially supported by 10.1.2.
Click to expand...
Click to collapse
I now receive a status 6 error (it's a little humbling to see at least some progress).
The follwing was removed from META-INF->com->google->android->updater-script:
assert(getprop("ro.product.device") == "d2tmo" || getprop("ro.build.product") == "d2tmo");
assert(getprop("ro.bootloader") == "T999UVDLJA" ||
getprop("ro.bootloader") == "T999UVDLJC" ||
getprop("ro.bootloader") == "T999UVDMD5" ||
getprop("ro.bootloader") == "T999VVLDLL1");
Do I need to modify these lines to correspond with my device's bootloader specifically? If so how where I obtain that information?
Thanks

voxmaris said:
I now receive a status 6 error (it's a little humbling to see at least some progress).
The follwing was removed from META-INF->com->google->android->updater-script:
assert(getprop("ro.product.device") == "d2tmo" || getprop("ro.build.product") == "d2tmo");
assert(getprop("ro.bootloader") == "T999UVDLJA" ||
getprop("ro.bootloader") == "T999UVDLJC" ||
getprop("ro.bootloader") == "T999UVDMD5" ||
getprop("ro.bootloader") == "T999VVLDLL1");
Do I need to modify these lines to correspond with my device's bootloader specifically? If so how where I obtain that information?
Thanks
Click to expand...
Click to collapse
Status 6 is syntax error. Means you messed something up If using CWM, there is a show log under advanced. That will tell you what line in the script the syntax error can be found.

Aerowinder said:
Status 6 is syntax error. Means you messed something up If using CWM, there is a show log under advanced. That will tell you what line in the script the syntax error can be found.
Click to expand...
Click to collapse
I: using /data/media for /sdcard/0/clockworkmod/.recovery_version
I: using /data/media for sdcard/clockworkmod/.recovery_version
I: Can't partition non-vfat: datamedia
I: Can't partition non-vfat: auto
I: Can't format unknown volume: /emmc
This is all it spat out after running show log after re-attempting a CM installation.

Did you delete signatures? In the meta-information folder it's the 3 files there.
You could also try TWRP. I don't know about CWM, but TWRPs recovery log often tells you exactly which line and which column (character) it encountered the error.
Also check if you didn't leave a semi colon or something behind when deleting the asserts.
This one does support the T999V, but they haven't changed the script to include the newest boot loader. VLDMF2 I think. DLL1 is the older one.
Sent from my SGH-T999L using XDA Premium 4 mobile app

DocHoliday77 said:
Did you delete signatures? In the meta-information folder it's the 3 files there.
You could also try TWRP. I don't know about CWM, but TWRPs recovery log often tells you exactly which line and which column (character) it encountered the error.
Also check if you didn't leave a semi colon or something behind when deleting the asserts.
This one does support the T999V, but they haven't changed the script to include the newest boot loader. VLDMF2 I think. DLL1 is the older one.
Sent from my SGH-T999L using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ive deleted the three signature files as well. The error remains identical. I've double checked the assert file and there's no rogue discrepancies between the lines. If the bootloader was previously updated does that mean I wouldn't be able to install cfw?

If the asserts are on the script, and you are on build MF2, then it will not flash. But that's the 7 error.
Try using the original script and replace T999VVLDLL1, with T999VVLDMF2. Check in Settings to make sure I'm remembering the new build number right.
Sent from my SGH-T999L using XDA Premium 4 mobile app
---------- Post added at 06:53 PM ---------- Previous post was at 06:49 PM ----------
You could also try mine. Go to my T999L thread linked in my Sig. Post 6 has the Rom I think you want. When I edited it for the T999L, I also did so for yours.
Sent from my SGH-T999L using XDA Premium 4 mobile app

DocHoliday77 said:
If the asserts are on the script, and you are on build MF2, then it will not flash. But that's the 7 error.
Try using the original script and replace T999VVLDLL1, with T999VVLDMF2. Check in Settings to make sure I'm remembering the new build number right.
Sent from my SGH-T999L using XDA Premium 4 mobile app
---------- Post added at 06:53 PM ---------- Previous post was at 06:49 PM ----------
You could also try mine. Go to my T999L thread linked in my Sig. Post 6 has the Rom I think you want. When I edited it for the T999L, I also did so for yours.
Sent from my SGH-T999L using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I replaced that line in updater-script that references T999VVLDLL1 with T999VVLLE6, still status 6. It seems that any modification to the zip archive will spit out status 6.

Don't forget to delete the signatures too. But also, check the recovery log. As aerowinder pointed out, 6 is a syntax error. 7 is when it fails the asserts check. So you probably forgot a semi colon, or something like that. Make sure there is no empty first line too. Not sure if it has any effect, but I might.
Also, you may want to update your firmware anyway. LE6 is O.L.D.!
Sent from my SGH-T999L using XDA Premium 4 mobile app

So which one am I carrying then? My baseband is LE6, yet my build is MF2. I've reverted back to jelly bean and the baseband didn't update from LE6.
Sent from my SGH-T999V using XDA Premium 4 mobile app

Oh ok, then you don't want to put LE6 in the asserts. If your build is MF2 you are on the latest. Don't go by the baseband. That's just telling you which build your modem is from.
Sent from my SGH-T999L using XDA Premium 4 mobile app

I changed the last line of code from that sequence to MF2 and removed the three files in meta.inf and still receive the same error.
Sent from my SGH-T999V using XDA Premium 4 mobile app

Ok, did you enter it like this: T999VVLDMF2?
Is it giving you the Status 7 or 6 error?
You can attach your updater-script and I can look at it for you. But also, after flashing, copy log to sd, then attach the log as well.
You are trying to flash CM 10.1.2? Did you try the one in my T999L thread? Its linked in my sig, and is currently at the top of the Q&A section. Post 6 has this ready to flash for you already.

DocHoliday77 said:
Ok, did you enter it like this: T999VVLDMF2?
Is it giving you the Status 7 or 6 error?
You can attach your updater-script and I can look at it for you. But also, after flashing, copy log to sd, then attach the log as well.
You are trying to flash CM 10.1.2? Did you try the one in my T999L thread? Its linked in my sig, and is currently at the top of the Q&A section. Post 6 has this ready to flash for you already.
Click to expand...
Click to collapse
I suspect he is making his edits with Notepad; CRLF instead of LF for new lines. We haven't seen the code, so have no way of knowing for sure. Best guess, though.
You should be using Notepad++ for this job. Anyhow, delete the signature files:
META-INF/com/android - entire folder
META-INF/CERT.RSA
META-INF/CERT.SF
META-INF/MANIFEST.MF
And overwrite the script (META-INF/com/google/android/updater-script) in the archive with this one http://db.tt/RDCDYS0z
Or just flash Doc's. He already repacked it for people not comfortable with editing the packages.

Aerowinder said:
I suspect he is making his edits with Notepad; CRLF instead of LF for new lines. We haven't seen the code, so have no way of knowing for sure. Best guess, though.
You should be using Notepad++ for this job. Anyhow, delete the signature files:
META-INF/com/android - entire folder
META-INF/CERT.RSA
META-INF/CERT.SF
META-INF/MANIFEST.MF
And overwrite the script (META-INF/com/google/android/updater-script) in the archive with this one http://db.tt/RDCDYS0z
Or just flash Doc's. He already repacked it for people not comfortable with editing the packages.
Click to expand...
Click to collapse
Beautiful, it worked. You've both been too awesome, can't thank you enough.

[ls970][CWM Advanced Edition] PhilZ Touch

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
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
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
Download links
Last version can be found here:
LG Optimus G Sprint (ls970)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse

Thanks!

Wow seems cool I'll give it a spin
Sent from my LG-LS970 using xda app-developers app

sharkboy0901 said:
Wow seems cool I'll give it a spin
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
+1 as soon as they release ReVolt I am all over it and this.

Phil3759 said:
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
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
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
Download links
Last version can be found here:
Click to expand...
Click to collapse
assert failed: getprop("ro.product.device") == "ls970"
|| getprop("ro.build.product") == "ls970"
E:Error executing updater binary in zip ' /sdcard/Download/philz_touch_5.
Error flashing zip
Updating partition details...
That's what i get when i try and flash it, May it be that i need to redownload it or something else?

desert54 said:
assert failed: getprop("ro.product.device") == "ls970"
|| getprop("ro.build.product") == "ls970"
E:Error executing updater binary in zip ' /sdcard/Download/philz_touch_5.
Error flashing zip
Updating partition details...
That's what i get when i try and flash it, May it be that i need to redownload it or something else?
Click to expand...
Click to collapse
If you open it on your computer without extracting it go to the updater script and remove that line should be good to go after that.
Sent from my LG-LS970 using xda app-developers app

sharkboy0901 said:
If you open it on your computer without extracting it go to the updater script and remove that line should be good to go after that.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
ui_print(" ###################### ");
ui_print("");
ui_print("");
show_progress(1.000000, 0);
assert(getprop("ro.product.device") == "ls970"
|| getprop("ro.build.product") == "ls970");
ui_print("Flashing Recovery...");
set_progress(0.100000);
package_extract_file("recovery.img", "/dev/block/platform/msm_sdcc.1/by-name/recovery");
set_progress(1.000000);
So i assume all of that line that has the ls970, Delete it, And ill be fine? The script will run as intended after?

Only this: assert(getprop("ro.product.device") == "ls970"
|| getprop("ro.build.product") == "ls970");
Then it will flash.
Looks really nice haven't gotten a chance to flash a anything tho but will do tomorrow
Sent from my LG-LS970 using xda app-developers app

Can't install with Xionia recovery.

+1
Sent from my LG-LS970 using XDA Premium 4 mobile app

Flashed with fastboot. Kicking butt
Sent from my Optimus G using xda app-developers app

I have a version I installed around Dec last year. (6.07.9) Is that the most recent?

Nay. Goeth ye to your Internet. Have ye times of merth and merriment as the link in the OP is clickéd, and surely clicks shall follow. Go that way. Recover what lies there.
May ye not be borked.
Sent from my LG-LS970 using xda app-developers app
---------- Post added at 11:01 PM ---------- Previous post was at 11:00 PM ----------
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/ls970
Here go
Sent from my LG-LS970 using xda app-developers app

Thank ye matey! Ya know what a pirate's favorite letter is?

Wondering if previous "regular" cwm backups will still be recognized with this recovery. I'm assuming they will be but wanna make sure. Thanks
Sent from my LG-LS970 using xda app-developers app

I think it recognized my old ones if I'm not mistaken. They're long gone as I'm a neat freak with memory. I've never used more than half the 32G this phone has, but it's nice to know I have it.

Cannot seem to boot to recovery to install this!
I read that for the Optimus G ls970, you hold Vol-up, Home, and Power to boot to recovery so you can install this zip, but it's not working for me at all. the screen just stays black, and I am at 90+% charged. I have tried a dozen times now. Is the stock boot to recovery just different?

agentjonnyb said:
I read that for the Optimus G ls970, you hold Vol-up, Home, and Power to boot to recovery so you can install this zip, but it's not working for me at all. the screen just stays black, and I am at 90+% charged. I have tried a dozen times now. Is the stock boot to recovery just different?
Click to expand...
Click to collapse
I always just go into recovery from goomanager. Get it on the play store and it will reboot u right into recovery
Sent from my LG-LS970 using xda app-developers app

agentjonnyb said:
I read that for the Optimus G ls970, you hold Vol-up, Home, and Power to boot to recovery so you can install this zip, but it's not working for me at all. the screen just stays black, and I am at 90+% charged. I have tried a dozen times now. Is the stock boot to recovery just different?
Click to expand...
Click to collapse
As far as I know this can't be flashed from stock recovery. Root your lg, install freegee from the play store, use it to unlock your bootloader and install one of the given recoveries, I used nandroid manager to boot to recovery but if goo manager has that option too then go for it, but once in your new custom recovery select install zip (from SD card) and choose the philz zip you downloaded. Follow the prompts to complete the install, then select reboot recovery. It will then load to philz. It works. That's exactly how I did it. Don't forget you need to be rooted before using freegee. Framaroot works for that on this phone.