[jflteatt][jflte][CWM Advanced Edition] PhilZ Touch

Phil3759

Inactive Recognized Developer
May 30, 2012
9,557
33,049
0
yup.. Its better if you are running a stock Samsung kernel. Although I have used it just fine with custom kernels too..
I think I found the bug for failing of auto-loki. Thanks to your log, I could track it

Anyone interested in trying and help in debugging auto-loki for next versions?
Obviously, you should know how to get out of a bad flash trouble!
 

RK

Senior Member
Feb 8, 2012
867
441
0
I think I found the bug for failing of auto-loki. Thanks to your log, I could track it

Anyone interested in trying and help in debugging auto-loki for next versions?
Obviously, you should know how to get out of a bad flash trouble!
Yup I'll test..
 
  • Like
Reactions: Phil3759

Phil3759

Inactive Recognized Developer
May 30, 2012
9,557
33,049
0
I am quiet sure of the issue
It is an fstat on partition to get its size.

I am working right now on a proper way
Maybe this night

You can test it by flashing it then try to flash my previous jflte non lokifying installer
 
  • Like
Reactions: emmanueldmc

RK

Senior Member
Feb 8, 2012
867
441
0
I am quiet sure of the issue
It is an fstat on partition to get its size.

I am working right now on a proper way
Maybe this night

You can test it by flashing it then try to flash my previous jflte non lokifying installer
Will do sir as soon as you post it..

Sent from my SGH-I337 using Tapatalk
 

buggerritt

Senior Member
Jan 16, 2009
2,067
711
0
Grand Rapids, MI
yup.. Its better if you are running a stock Samsung kernel. Although I have used it just fine with custom kernels too..
Worked perfect with talexop kernel. It took me a couple days before i got the balls to commit. I must've gotten to the part where it says you might brick your device and backed out at least 30 times. LOL

Sent from my SGH-I337 using Tapatalk
 

Phil3759

Inactive Recognized Developer
May 30, 2012
9,557
33,049
0
@RK and others that will to help

v6.19.4 Loki ALPHA Fix

*** Do not use if you don't know how to come out of a bad flash ***

I did my best to debug it, but I have no loki device to test it
Get it from attachment

- flash it (it has the lokifying script in installer, so no issues there)
- reboot into recovery
- enable auto loki in settings
- try to flash philz_touch_6.18.7-jflte.zip or any boot/recovery non lokified installer
philz_touch_6.18.7-jflte.zip was missing the lokifying script in zip installer
Enabling auto loki should be able to flash it in new 6.19.4 version
 

Attachments

Last edited:

buggerritt

Senior Member
Jan 16, 2009
2,067
711
0
Grand Rapids, MI
@RK and others that will to help

v6.19.4 Loki ALPHA Fix

*** Do not use if you don't know how to come out of a bad flash ***

I did my best to debug it, but I have no loki device to test it
Get it from attachment



philz_touch_6.18.7-jflte.zip was missing the lokifying script in zip installer
Enabling auto loki should be able to flash it in new 6.19.4 version
Doesn't work for me. I flashed it and can't get into recovery. Instead, get the yellow triangle screen.

Sent from my SGH-I337 using Tapatalk

---------- Post added at 05:25 PM ---------- Previous post was at 05:24 PM ----------

Doesn't work for me. I flashed 6.19.4 and can't get into recovery. Instead, get the yellow triangle screen.

Sent from my SGH-I337 using Tapatalk


Sent from my SGH-I337 using Tapatalk
 

Phil3759

Inactive Recognized Developer
May 30, 2012
9,557
33,049
0
Doesn't work for me. I flashed it and can't get into recovery. Instead, get the yellow triangle screen.

Sent from my SGH-I337 using Tapatalk

---------- Post added at 05:25 PM ---------- Previous post was at 05:24 PM ----------





Sent from my SGH-I337 using Tapatalk
6.19.4 should boot perfectly

Once you follow exact steps, provide a log if auto-loki the unpatched image fails. Else no need to try it at all
 
  • Like
Reactions: RK

Phil3759

Inactive Recognized Developer
May 30, 2012
9,557
33,049
0
Up it:

@RK and others that will to help

v6.19.4 Loki ALPHA Fix

*** Do not use if you don't know how to come out of a bad flash ***

I did my best to debug it, but I have no loki device to test it. I tried it though and it passed the mmap aboot image error, so it should really work now
Get it from attachment

- flash it (it has the lokifying script in installer, so no issues there)
- reboot into recovery
- enable auto loki in settings
- try to flash philz_touch_6.18.7-jflte.zip or any boot/recovery non lokified installer
- if auto-loki fails here, provide a log
philz_touch_6.18.7-jflte.zip was missing the lokifying script in zip installer
Enabling auto loki should be able to flash it in new 6.19.4 version
 
  • Like
Reactions: RK

buggerritt

Senior Member
Jan 16, 2009
2,067
711
0
Grand Rapids, MI
Up it:

@RK and others that will to help

v6.19.4 Loki ALPHA Fix

*** Do not use if you don't know how to come out of a bad flash ***

I did my best to debug it, but I have no loki device to test it. I tried it though and it passed the mmap aboot image error, so it should really work now
Get it from attachment



philz_touch_6.18.7-jflte.zip was missing the lokifying script in zip installer
Enabling auto loki should be able to flash it in new 6.19.4 version
Am i missing a new step or something? I downloaded 6.19.4, copied to sd card, flashed it by using 6.15.4 jflteatt, and tried to boot but, had to go through download mode, due to triangle.


Sent from my SGH-I337 using Tapatalk
 

RK

Senior Member
Feb 8, 2012
867
441
0
Up it:

@RK and others that will to help

v6.19.4 Loki ALPHA Fix

*** Do not use if you don't know how to come out of a bad flash ***

I did my best to debug it, but I have no loki device to test it. I tried it though and it passed the mmap aboot image error, so it should really work now
Get it from attachment



philz_touch_6.18.7-jflte.zip was missing the lokifying script in zip installer
Enabling auto loki should be able to flash it in new 6.19.4 version
SUCCESS!!
 

Attachments

  • Like
Reactions: Vcolumn

RK

Senior Member
Feb 8, 2012
867
441
0
Not sure what I did wrong. But, now recovery doesn't install via goomanager. It downloads the file but when i reboot to recovery, i get the triangle of death. Do I need to Odin back to mdl stock?

Sent from my SGH-I337 using Tapatalk
are you trying to install TWRP via goomanager? if yes, make sure that your build.prop shows your phone as SGH-I337. (This will not be so if you are using a GE or i-9505 based ROM.) That is, make sure that your phone says SGH-I337 in settings->about phone->Model number)

If your phone says GT-I9505 or GT-I9505G, then goomanager will install a version of TWRP that is NOT loki'd and hence the yellow triangle.. In that case, get any build.prop editor from market and edit these four lines from

FROM:
ro.product.model=XXXXXXX
ro.product.name=XXXXXXXX
ro.product.device=XXXXXXX
ro.build.product=XXXXXX

TO
ro.product.model=SGH-I337
ro.product.name=jflteuc
ro.product.device=jflteatt
ro.build.product=jgedlte

Reboot, and install TWRP using goomanager and then install whichever version of philz you want.

You will still have the custom boot screen but that goes away if you use triangle away
 
Last edited:

buggerritt

Senior Member
Jan 16, 2009
2,067
711
0
Grand Rapids, MI
are you trying to install TWRP via goomanager? if yes, make sure that your build.prop shows your phone as SGH-I337. (This will not be so if you are using a GE or i-9505 based ROM.) That is, make sure that your phone says SGH-I337 in settings->about phone->Model number)

If your phone says GT-I9505 or GT-I9505G, then goomanager will install a version of TWRP that is NOT loki'd and hence the yellow triangle.. In that case, get any build.prop editor from market and edit these four lines from

FROM:
ro.product.model=XXXXXXX
ro.product.name=XXXXXXXX
ro.product.device=XXXXXXX
ro.build.product=XXXXXX

TO
ro.product.model=SGH-I337
ro.product.name=jflteuc
ro.product.device=jflteatt
ro.build.product=jgedlte

Reboot, and install TWRP using goomanager and then install whichever version of philz you want.

You will still have the custom boot screen but that goes away if you use triangle away
Yeah. My build.prop is set. I was able to do this earlier today. I wonder if it's not installing because i chose the option to not allow recovery to flash after flashing this alpha?

Sent from my SGH-I337 using Tapatalk
 

RK

Senior Member
Feb 8, 2012
867
441
0
Yeah. My build.prop is set. I was able to do this earlier today. I wonder if it's not installing because i chose the option to not allow recovery to flash after flashing this alpha?

Sent from my SGH-I337 using Tapatalk
Idk as a last resort, I would try installing a recovery via dd.

Download this file

https://copy.com/SSpeJBaDK1di3nz

To your internal SD and run in android terminal emulator:

su

dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21

Make certain that you get this command right. *Typing the wrong number could result in a brick!

The file is pre-loki'd TWRP.

Then download this:

http://d-h.st/dMX

Reboot to TWRP and flash latest philz and the Loki_recovery.zip above and you will be on latest philz again..

Sent from my GT-I9505G using Tapatalk

---------- Post added at 12:08 AM ---------- Previous post was at 12:06 AM ----------

@Phil3759 the alpha is working perfect on my device.. :)

Sent from my GT-I9505G using Tapatalk
 
  • Like
Reactions: buggerritt