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

[RK]

I've tried downloading and flashing latest: philz_touch_6.15.4-jflteatt.zip
and each time come up with an error staying that the file is bad.

Sent from my SGH-I337 using Tapatalk

THe latest recovery is here:

http://goo.im/devs/philz_touch/CWM_Advanced_Edition/jflte

 

[RK]

I tried the new 6.17.9 and everything I tried worked perfect. (I did not do restore. Just backup.)

However, I still have the failed to mmap aboot error with auto loki. It happened when I flashed 6.17.9 using 6.16.9.

I have attached another log that shows auto loki failure. As you will see in the log, I used a CWM zip similar to loki-doki right after auto loki failed, and that worked.

I posted these logs before but received no comments. Is this because i am being a noob and am missing something obvious or because you do not know why auto loki is not working on my device? Either ways, its not a big issue. Just wondering why I am the only one who seems to have this problem...

 

[Phil3759]

I tried the new 6.17.9 and everything I tried worked perfect. (I did not do restore. Just backup.)

However, I still have the failed to mmap aboot error with auto loki. It happened when I flashed 6.17.9 using 6.16.9.

I have attached another log that shows auto loki failure. As you will see in the log, I used a CWM zip similar to loki-doki right after auto loki failed, and that worked.

I posted these logs before but received no comments. Is this because i am being a noob and am missing something obvious or because you do not know why auto loki is not working on my device? Either ways, its not a big issue. Just wondering why I am the only one who seems to have this problem...

maybe you updated bootloader and it is now loki proof

 

[RK]

maybe you updated bootloader and it is now loki proof

I did not. If you see this section of the log

Loki'ing Recovery...20480+0 records in
20480+0 records out
10485760 bytes (10.0MB) copied, 0.478882 seconds, 20.9MB/s
[+] loki_patch v2.1
[+] Detected target AT&T Samsung Galaxy S4 build JDQ39.I337UCUAMDB or JDQ39.I337UCUAMDL
[+] Original kernel address: 80208000
[+] Original ramdisk address: 82200000
[+] Output file written to /tmp/loki/recovery.lok

[+] loki_flash v2.1
[+] Loki validation passed, flashing image.
[+] Loki flashing complete!
script result was [1.000000]
Done, reboot recovery...
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:apply_loki_patch set to default (1)
Checking if loki-fying is needed

Install from sdcard complete.

It shows that using a zip file that grabs recovery image and aboot using dd, loki's the recovery and writes the loki'd recovery back using dd, loki works on my device. Your auto loki detects in the end that everything is loki'd.

My bootloader is MDL. I can use loki'd kernels. I can also flash kernels that are not loki'd and then flash loki-doki.zip later to loki them on-device.

The only time I get that error is when using auto-loki.

I am doing the following in your recovery to loki newer versions of your recovery:

1. Flash the recovery (here, auto-loki reports "failed to mmap aboot")

2. Flash a zip that runs the following script:

dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/tmp/loki/aboot.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/tmp/loki/recovery.img
/tmp/loki/loki_patch recovery /tmp/loki/aboot.img /tmp/loki/recovery.img /tmp/loki/recovery.lok || exit 1
/tmp/loki/loki_flash recovery /tmp/loki/recovery.lok || exit 1
rm -rf /tmp/loki
exit 0

This works every time!

 

[Phil3759]

I did not. If you see this section of the log

Loki'ing Recovery...20480+0 records in
20480+0 records out
10485760 bytes (10.0MB) copied, 0.478882 seconds, 20.9MB/s
[+] loki_patch v2.1
[+] Detected target AT&T Samsung Galaxy S4 build JDQ39.I337UCUAMDB or JDQ39.I337UCUAMDL
[+] Original kernel address: 80208000
[+] Original ramdisk address: 82200000
[+] Output file written to /tmp/loki/recovery.lok

[+] loki_flash v2.1
[+] Loki validation passed, flashing image.
[+] Loki flashing complete!
script result was [1.000000]
Done, reboot recovery...
I:Cannot open /data/philz-touch/philz-touch_6.ini
I:apply_loki_patch set to default (1)
Checking if loki-fying is needed

Install from sdcard complete.

It shows that using a zip file that grabs recovery image and aboot using dd, loki's the recovery and writes the loki'd recovery back using dd, loki works on my device. Your auto loki detects in the end that everything is loki'd.

My bootloader is MDL. I can use loki'd kernels. I can also flash kernels that are not loki'd and then flash loki-doki.zip later to loki them on-device.

The only time I get that error is when using auto-loki.

I am doing the following in your recovery to loki newer versions of your recovery:

1. Flash the recovery (here, auto-loki reports "failed to mmap aboot")

2. Flash a zip that runs the following script:

dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/tmp/loki/aboot.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/tmp/loki/recovery.img
/tmp/loki/loki_patch recovery /tmp/loki/aboot.img /tmp/loki/recovery.img /tmp/loki/recovery.lok || exit 1
/tmp/loki/loki_flash recovery /tmp/loki/recovery.lok || exit 1
rm -rf /tmp/loki
exit 0

This works every time!

not owning a loki device makes it a bit Chinese for me !

can you explain the issue a bit more precisely:
- try to turn off auto-loki in recovery, then flash my zip files
- else, try to flash the recovery.img without my zip installer (it has a lokifying script for people flashing recovery for the first time)

 

[RK]

not owning a loki device makes it a bit Chinese for me !

can you explain the issue a bit more precisely:
- try to turn off auto-loki in recovery, then flash my zip files
- else, try to flash the recovery.img without my zip installer (it has a lokifying script for people flashing recovery for the first time)

I am sorry i will try to be clear. Here is what happens:

Auto-loki OFF:

After flashing a ROM, I have to flash loki-doki.zip (attached) and it works.
After flashing recovery I have to flash loki-recovery.zip (attached) and it works.

Auto-loki ON:
After flashing a ROM, the recovery correctly identifies that boot.img is not loki'd. The recovery then tries to loki-patch boot.img, but fails with the output

Checking if loki-fying is needed
/dev/block/platform/msm_sdcc.1/by-name/boot needs lokifying.
[+] loki_patch v2.1
E:[-] Failed to mmap aboot.
E:Error loki-ifying the recovery image.

After this, I flash loki-doki.zip, which loki-paches boot.img correctly without errors, and I can boot into the ROM.


After flashing your unified jflte recovery, the recovery correctly identifies that recovery.img is not loki'd. The recovery then tries to loki-patch recovery.img, but fails with the output

Checking if loki-fying is needed
/dev/block/platform/msm_sdcc.1/by-name/recovery needs lokifying.
[+] loki_patch v2.1
E:[-] Failed to mmap aboot.
E:Error loki-ifying the recovery image.

After this, I flash loki-recovery.zip which loki-paches recovery.img correctly without errors.


Both loki-doki.zip and loki-recovery.zip are doing the exact same thing that auto-loki tries to do, i.e., copy aboot.img and boot.img (or recovery.img) to a temporary folder, patch boot.img (or recovery.img) using aboot.img and reflash boot.img (or recovery.img) to the boot (or recovery) partition, and yet, the zips succeed and auto-loki fails.

Hope this helps. As i said, its not a big deal since i have the zips and flashing them is just one extra step..

 

[Phil3759]

I am sorry i will try to be clear. Here is what happens:

Auto-loki OFF:

After flashing a ROM, I have to flash loki-doki.zip (attached) and it works.
After flashing recovery I have to flash loki-recovery.zip (attached) and it works.

Auto-loki ON:
After flashing a ROM, the recovery correctly identifies that boot.img is not loki'd. The recovery then tries to loki-patch boot.img, but fails with the output

Checking if loki-fying is needed
/dev/block/platform/msm_sdcc.1/by-name/boot needs lokifying.
[+] loki_patch v2.1
E:[-] Failed to mmap aboot.
E:Error loki-ifying the recovery image.

After this, I flash loki-doki.zip, which loki-paches boot.img correctly without errors, and I can boot into the ROM.


After flashing your unified jflte recovery, the recovery correctly identifies that recovery.img is not loki'd. The recovery then tries to loki-patch recovery.img, but fails with the output

Checking if loki-fying is needed
/dev/block/platform/msm_sdcc.1/by-name/recovery needs lokifying.
[+] loki_patch v2.1
E:[-] Failed to mmap aboot.
E:Error loki-ifying the recovery image.

After this, I flash loki-recovery.zip which loki-paches recovery.img correctly without errors.


Both loki-doki.zip and loki-recovery.zip are doing the exact same thing that auto-loki tries to do, i.e., copy aboot.img and boot.img (or recovery.img) to a temporary folder, patch boot.img (or recovery.img) using aboot.img and reflash boot.img (or recovery.img) to the boot (or recovery) partition, and yet, the zips succeed and auto-loki fails.

Hope this helps. As i said, its not a big deal since i have the zips and flashing them is just one extra step..

thank you for the details
What is latest recovery version that was working?

 

[RK]

This is the interesting part. 6.07.9 definitely worked. The problem started with 6.08.9. However, now even if I flash back to 6.07.9, the issue persists. I will try some 5.xx versions and report back.

Sent from my SGH-I337 using Tapatalk

 

[Phil3759]

This is the interesting part. 6.07.9 definitely worked. The problem started with 6.08.9. However, now even if I flash back to 6.07.9, the issue persists. I will try some 5.xx versions and report back.

Sent from my SGH-I337 using Tapatalk

Well, then, definitely not related to my sources
Will look at it later

 

[RK]

Well, then, definitely not related to my sources
Will look at it later

EDIT. Did some testing. 6.00.8 works 6.07.9 does not. Please disregard last post.

Logs:

https://www.dropbox.com/sh/8b45dcyl9todxr7/CapR0UG-13

The only visible difference is that the auto-loki with version 2.1 fail. The older ones work.

EDIT: to be clear 6.00.8 and everything before work, 6.07.9 and everything after does not. Nothing between 6.00.8 and 6.07.9 was released for jflteatt so can't test those.

Sent from my SGH-I337 using Tapatalk

 

[Phil3759]

EDIT. Did some testing. 6.00.8 works 6.07.9 does not. Please disregard last post.

Logs:

https://www.dropbox.com/sh/8b45dcyl9todxr7/CapR0UG-13

The only visible difference is that the auto-loki with version 2.1 fail. The older ones work.

EDIT: to be clear 6.00.8 and everything before work, 6.07.9 and everything after does not. Nothing between 6.00.8 and 6.07.9 was released for jflteatt so can't test those.

Sent from my SGH-I337 using Tapatalk

thank you a lot :good:
Will look at it when I have time

 

[buggerritt]

THe latest recovery is here:

http://goo.im/devs/philz_touch/CWM_Advanced_Edition/jflte

Yes. That is exactly where I downloaded 6.18.7 several times. Each time I try to flash the zip, it fails. With an error saying that the file is bad. I'm currently using 6.00.8 and haven't had an issue with anything. Just wanting to get with the latest.

Sent from my GT-I9505 using Tapatalk

 

[RK]

Yes. That is exactly where I downloaded 6.18.7 several times. Each time I try to flash the zip, it fails. With an error saying that the file is bad. I'm currently using 6.00.8 and haven't had an issue with anything. Just wanting to get with the latest.

Sent from my GT-I9505 using Tapatalk

Weird I downloaded and flashed from there yesterday without issues..

Sent from my SGH-I337 using Tapatalk

 

[buggerritt]

Weird I downloaded and flashed from there yesterday without issues..

Sent from my SGH-I337 using Tapatalk

What recovery did you use to flash it with? Or, did you Odin flash?

Sent from my GT-I9505 using Tapatalk

---------- Post added at 08:43 AM ---------- Previous post was at 08:42 AM ----------

What recovery did you use to flash it with? Or, did you Odin flash? Maybe I should download it from my PC and transfer.

Sent from my GT-I9505 using Tapatalk

Sent from my GT-I9505 using Tapatalk

 

[RK]

What recovery did you use to flash it with? Or, did you Odin flash?

Sent from my GT-I9505 using Tapatalk

---------- Post added at 08:43 AM ---------- Previous post was at 08:42 AM ----------





Sent from my GT-I9505 using Tapatalk

I used philz

Sent from my SGH-I337 using Tapatalk

 

[buggerritt]

I used philz


Please disregard all my previous talk on the subject. I downloaded via PC and it flashed just fine. My bad.

Sent from my SGH-I337 using Tapatalk

Please disregard all my previous talk on the subject. I downloaded via PC and it flashed just fine. My bad.

 

[Phil3759]

Update 6.19.3

Hope it flashes your loki thing fine now
I activated back the loki script in zip installer

 

[buggerritt]

Update 6.19.3

Hope it flashes your loki thing fine now
I activated back the loki script in zip installer

I just flashed it and when i try to reboot into recovery, I get the at&t triangle. What to do now?

Sent from my GT-I9505 using Tapatalk

 

[buggerritt]

I just flashed it and when i try to reboot into recovery, I get the at&t triangle. What to do now?

Sent from my GT-I9505 using Tapatalk

Well, i got twrp from goo manager and flashed the previous working philz but now i have the Samsung custom nag screen when i boot. Is there a way to get rid of that without odin back to stock or triangle away?

Sent from my SGH-I337 using Tapatalk

 

[RK]

Well, i got twrp from goo manager and flashed the previous working philz but now i have the Samsung custom nag screen when i boot. Is there a way to get rid of that without odin back to stock or triangle away?

Sent from my SGH-I337 using Tapatalk

Not that I know of. Triangle away works like a champ tho..

Sent from my SGH-I337 using Tapatalk