yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Android Development] Phil3759:
This recovery is not supposed to be dual boot guarantied

If it was working previously, maybe it is because of some selinux properties not properly set. Dual boot roms hack some partitions to mount their stuff. However, recovery will assign different permissions depending on where files are. That's called selinux and is now part of all KitKat sources

Your ROM cooker should look at it. If my recovery is affected, then all new CWM recoveries are. This is just a CWM advanced mod

If your ROM maker can tell why it is not compatible with CWM, I can then look at a fix if nothing can be done on his side

Maybe, set_metadata is where he should start to look at

Sadly, I have no time to flash third party ROMs to debug them
[Galaxy S 4 i9505 Android Development] franzyroy:
For my part, I think the problem is that I put the rom SHOStock like secondary rom, it is written in the post OP of DualBoot, that TW Rom are to put preferably like primary rom, to avoid any problems.

Like this:
[Galaxy S 4 i9505 Android Development] Phil3759:
great

problem fixed then?
[Galaxy S 4 i9505 Android Development] franzyroy:
I'll see it tomorrow now. ;)
[Galaxy S 4 i9505 Android Development] Riskytwin:
10 for Philz. This last update has given me the correct date for the first time and 5,3 Gb backup without compression in 10 min.

Thanks a lot Phil!

Risky's my name
[Galaxy S 4 i9505 Android Development] KenHua:
Thanks Philz for the hard work and huge update! I did my usual backup tests for 6.15.4 and the results were great.

The first test was with Nandroid progress and logs hidden; medium compression; no Checksum; default settings for the rest and the result was:

Backup time: 04:27 mn

Backup size: 1443.15Mb

Compression: 40.50%

The second test was with Nandroid progress and logs turned on; and with USB plugged in :silly:, and the result was great too:

Backup time: 05:36 mn

Backup size: 1443.15Mb

Compression: 40.50%

Thanks
[Galaxy S 4 i9505 Android Development] franzyroy:
SHOStock works fine primary installation, just install the second now. I gonna try with the last update.

Edit

:

All works fine now with my DualBoot now

First rom (SHOStock v5.0b3) installed with Philz recovery 6.09.2 (forgot to try with the last :silly:)

Installed Philz recovery 6.15.4

Installed DualBoot switcher

Wipe all data with DualBoot utilities

Installed Second rom (AOSB v1.2.9))

All works fine without issue!!!

Thanks Philz... continue ur great work! ;)

Edit 2

:

I spoke too quickly, after reboot, second rom (AOSB) had lost the IMEI code, it was even written MEID instead of IMEI... so I put again Philz recovery 6.09.2 and install again AOSB like secondary rom with all wipes. All is fine now, even after reboot.
[Galaxy S 4 i9505 Android Development] Phil3759:
Now: one common recovery for all: jflte

The below specific variants are no more updated, use jflte common variant
[Galaxy S 4 i9505 Android Development] störte:
Does it mean that we have now one recovery for all S4 ? I like that
[Galaxy S 4 i9505 Android Development] hanspampel:
Yepp. From Main Thread.

Download
[Galaxy S 4 i9505 Android Development] BillGoss:
Brilliant! I hope this cuts down on your maintenance effort.

Sent from my GT-I9505
[Galaxy S 4 i9505 Android Development] Phil3759:
Sure it does. Mainly that the same was done for d2lte, hlte and falcon variants
[Galaxy S 4 i9505 Android Development] Formhault:
Hope it also cuts down on the ammount of stress new users need to go through by searching for the proper recovery file to flash... :rolleyes:

---------- Post added at 11:42 PM ---------- Previous post was at 11:41 PM ----------

You should change the [jfltexx] tag in [jflte][NOOB-PROOF IF YOU DON'T GET IT RIGHT GET YOUR BRAIN CHECKED] or something like that.
[Galaxy S 4 i9505 Android Development] Phil3759:
LoL

What ever I put, they will come and ask where is the latest
[Galaxy S 4 i9505 Android Development] Formhault:
Put up a folder named "jflte-latest" then :silly: lmao
[Galaxy S 4 i9505 Android Development] davidwilson83:
Flashing issue

Hi [MENTION=4666971]Phil3759[/MENTION]

I have been using your touch recoveries since the SGSII days and they are fantastic. After rooting a ROM that is always the first thing I add to the phone. Just recently however I faced an issue I had never come across before and I can't see anywhere in the pages of this thread that anyone else has, so I thought that I would bring it to your attention.

Regularly I will flash a stock firmware through Odin and then root it, make a deodexed version of the firmware and then flash it with your recovery with never any problems. I always use the latest version of your recovery that's available at the time.

In the last few weeks I flashed the NA5 leaked 4.4.2 KK firmware and rooted and installed your recovery which I think was version 6.12.4 or 6.12.5 without any issues. I created a deodexed version of the stock firmware as I usually do, and flashed it... no signal, Baseband was Unknown in Settings - About Device and IMEI was null/null. I was a bit worried. I restored the Nandroid backup and it all came back perfect. I tried a number of things, redownloaded the stock firmware, rebuilt the ROM, flashed it and same issue again - no signal, Baseband Unknown and IMEI null/null.

I didn't know what to do so I updated your recovery to version 6.15.4 and tried but I still had the same issues. Then I saw this other custom ROM thread in I9505 Android Development forum which said that in order to flash their ROM, the user had to downgrade their PhilZ Recovery version to 6.07.9 because the later recoveries had issues with flashing. So this is what I did. I flashed the 6.07.9 version of your recovery, then I flashed the ROM I had built and it all came up perfectly. Good signal, Baseband was correct and IMEI was fine.

So I don't know what the differences between the versions are, but 6.07.9 works perfectly and I suspect that the later versions like 6.11, 6.12 and 6.15 will not.

Thanks again for your great recovery and all the best,

Dave
[Galaxy S 4 i9505 Android Development] Phil3759:
does the script produces errors during flash?

Does it try to mess with these:

/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4
/dev/block/platform/msm_sdcc.1/by-name/apnhlos /firmware vfat
/dev/block/platform/msm_sdcc.1/by-name/mdm /firmware-mdm
[Galaxy S 4 i9505 Android Development] davidwilson83:
No errors whatsoever. It flashes perfectly.

Nope it doesn't touch them. There is no kernel in the ROM. Just the system folder.

Sent from my PurifieD Domination S4
[Galaxy S 4 i9505 Android Development] Phil3759:
Does your script correctly uses set_metadata info?

If not, recovery will apply its own selinux default permissions that could be not compatible with new stock kernel

Try to get the correct selinux permissions from the files you flash while on stock ROM then fix your updater-script accordingly
[Galaxy S 4 i9505 Android Development] hawkerpaul:
I would get this if I restored a nandroid backup with the selinux option set.

When unsetting this option, the nandroid would restore and get the baseband back.

Since then I always unset selinux option. Not sure exactly what the dangers of this are, but touch wood, I've had no problems up to now.

I doubt if this would impact your flash however.
[Galaxy S 4 i9505 Android Development] cdzo72:
Same goes here... I keep SE LINUX application unchecked because if not I have no signal and no wifi... restore nandroid again with it unchecked and all good
[Galaxy S 4 i9505 Android Development] Phil3759:
I will look into it
[Galaxy S 4 i9505 Android Development] brojoe11:
jfltecsp-error 7

Hi Phil. Just tried to flash your recovery on my C Spire S4. I get an error 7. It list all the other variants and says not compatible. Could jfltecsp be added to the list so it would work? Thanks for considering. I loved your recovery on my other devices.
[Galaxy S 4 i9505 Android Development] Phil3759:
it should be I think

Can you post this from your main ROM:

terminal console:

getprop ro.bootloader

and post the output
[Galaxy S 4 i9505 Android Development] brojoe11:
Sure.

R970XWWUEMK6

u0_a278@jfltecsp:/ $

Hope that's what you need.
[Galaxy S 4 i9505 Android Development] Phil3759:
Are you using latest jflte?

I doubt as it looks like it should perfectly work:

https://github.com/CyanogenMod/andr...6220343e28ec9e3d2ef0cba/init/init_jflte.c#L77
[Galaxy S 4 i9505 Android Development] brojoe11:
I pretty sure but I'll check. May need to odin back to clean MK6. Thought that was the latest. I'll do some checking and get back to you. Thanks for looking into it.
[Galaxy S 4 i9505 Android Development] brojoe11:
I may see the issue. The version you posted the url to is for 4.2.2. MK6 is the latest and it is 4.3

Could that be the issue? Sorry to be so much trouble. I even odined back to pure stock and the latest updates are already applied on MK6. But it is android 4.3
[Galaxy S 4 i9505 Android Development] jeboo:
I dealt with this same issue after the CWM patch was added to institute the new updater binary. It's definitely a bug in the new binary, as it not supporting backwards compatibility (set_perm..) 100%. For now I disabled that feature.
[Galaxy S 4 i9505 Android Development] Phil3759:
Update 6.16.8

This is the first build using the new independent libtouch source code

There are no changes kernel and other things wise, just a massive code cleaning, many bug fixes at compiler level and potentially on run time and moving all touch source to dedicated separate files

Next updates will progressively bring a prebuilt libtouch support. I will upload to git at that time, once all done

I just need you to flash and test if all settings/features are still fine, as they were :good:
[Galaxy S 4 i9505 Android Development] ranger4740:
Just reporting backup speeds for 6.16.8

Backup to sdcard1 (EXTERNAL)

3700Mb

12 minutes

No compression

Same backup but to sdcard (INTERNAL)

3700Mb

6 minutes

No compression.

No faults found so far.

Thank you Phil.
[Galaxy S 4 i9505 Android Development] Phil3759:
Update 6.16.9

More code cleanup: ready for libtouch
[Galaxy S 4 i9505 Android Development] Formhault:
Well, looks like it's Coding Sunday :D. Just kidding. Really impressed by your work, mate. Keep up the :good: work!

What does this new libtouch bring? Improvements to the touch engine (which I thought is pretty good already)?
[Galaxy S 4 i9505 Android Development] Phil3759:
Nothing for end users

But now, developers won't need me to build the full version

Porting to devices is no more something no one else than me can do

The prebuilt libtouch can be freely used to compile full version

I can breath and focus on recovery sources
[Galaxy S 4 i9505 Android Development] Formhault:
Oh, so this is something under the hood, to enable more people to port your awesome recovery to other devices with more ease... Nice!
[Galaxy S 4 i9505 Android Development] cyberspaceguy:
I didn't find 6.16.9 version in download folder jtltexx something is changed?
[Galaxy S 4 i9505 Android Development] davidwilson83:
Try jflte folder

Sent from my PurifieD Domination S4
[Galaxy S 4 i9505 Android Development] phileasx:
updated to 6.16.9, thanks for the great work,

just like to check if there is a guide for the Philz setting part? It's getting comprehensive now. :D

also noticed the time zone setting is reset when on this ver.
[Galaxy S 4 i9505 Android Development] triathlete66:
see first post and thread title.
[Galaxy S 4 i9505 Android Development] cdzo72:
Just like to say for those that may see this issue and freak out...

I flashed the 6.16. 9 and booted right back into recovery and my time read back in 1970 and hour was off by 6 hours when I set timezone. I manually adjusted and rebooted recovery and it went back to its erroneous hour... well at that point I was pretty upset... so I decided to boot in to Android and then boot back into PhilZ recovery and now the time is ok without any input from me
[Galaxy S 4 i9505 Android Development] kaott:
hi,can i install this recovery in top of rooted 9505 4.3 MKF knox firmware?
[Galaxy S 4 i9505 Android Development] franzyroy:
Yes, U can.
[Galaxy S 4 i9505 Android Development] Phil3759:
Many settings are changed. You need to go through them and see what must be reconfigured

In final version I will force upgrade of config file probably to avoid issues and complaints
[Galaxy S 4 i9505 Android Development] Phil3759:
Update 6.17.9

This went a heavy code review to fix ALL compiler warnings and potential bugs, mainly in closed source parts

It is a final build that should be same functionality as before
[Galaxy S 4 i9505 Android Development] Formhault:
So no more updates for a while? Time for a break, I guess :good:
[Galaxy S 4 i9505 Android Development] Phil3759:
No,

I really wanted to push the libtouch as it should be very easy now that I separated the code

However, I have terrible news: my i9505 seems to be dying

Since a few weeks, it constantly reboots / turn off by its self and goes into bootloops until I pull battery or plug in charger

Now, I tried to wipe everything, installed latest 4.3 and kept all pure stock, no apps, not even market play accounts or downloads

Well, it still randomly reboots on its own

Seems hardware failing somewhere and with random crap that after sale will probably let it play a yo yo without ever fixing it

This sucks hard. Phone was from users donations and less than 6 month old, yet it went terrible flashing cycles (+1000 I guess from my internal build history...)
[Galaxy S 4 i9505 Android Development] Joery1983:
Sounds like your battery check if it's slightly swolen.

Verstuurd vanaf mijn GT-I9505 met Tapatalk
[Galaxy S 4 i9505 Android Development] davidwilson83:
Dude that sucks big time. Have you tried replacing the battery? Apparently the batteries from stock can swell and cause that issue. Maybe give that a try?
[Galaxy S 4 i9505 Android Development] franzyroy:
It is an impression? Or the last recovery is faster?
[Galaxy S 4 i9505 Android Development] cdzo72:
Yes I saw all that and went through it all... my point was that I may have been hasty... Instead of flashing the new recovery and just rebooting right back into it... boot the phone first to make sure time sticks... Although the fact that the date was at 1970 and the time was off by six hours does mean something is causing that because the time was right before flashing the new recovery
[Galaxy S 4 i9505 Android Development] Phil3759:
Yes, it is a bit swolen

Can it be really the cause?

Well, the code is drastically optimized / revised and fixed. Faster I am not sure, but better it is no doubt. I went through code and fixed warning by warning

Wanted to start super clean before building the libtouch
[Galaxy S 4 i9505 Android Development] Joery1983:
It is the problem. It's a warranty issue they'll replace it free of charge whiteout looking to your phone they'll just check the serial number of your battery . Just head over to a service center.

Verstuurd vanaf mijn GT-I9505 met Tapatalk
[Galaxy S 4 i9505 Android Development] franzyroy:
OK... Thanks 4 ur great work! ;)
[Galaxy S 4 i9505 Android Development] Formhault:
Yep. If you place it on a flat surface and it wobbles around (swolen)... seek replacement. The S4's battery is rumored to suck when it comes to longevity... Some users experience problems with it ~6 months late.

---------- Post added at 11:37 PM ---------- Previous post was at 11:32 PM ----------

I think the S4's NAND is pretty good :D. It should be able to withstand more than 1000 FULL cycles (entire memory wipe/flash)... And I don't think you did that many FULL cycles. :confused:
[Galaxy S 4 i9505 Android Development] HaTrED_:
Yes, it is, for sure! It's a well known issue in S4 (unfortunately)!

As stated before, it should be solved without any questions at all, it's a simple battery replacement! ;)

And your NAND should keep up with your flash pace!!!
[Galaxy S 4 i9505 Android Development] phileasx:
Updated, I love 'super clean' codes. :D

Thanks a lot for all the great work
[Galaxy S 4 i9505 Android Development] sachs:
Where???
[Galaxy S 4 i9505 Android Development] phileasx:
under the folder 'jflte', now it's common version for all.
[Galaxy S 4 i9505 Android Development] Socim:
Be careful. I have heard some news regarding S4 battery explosion. Really dangerous.
[Galaxy S 4 i9505 Android Development] fabiienb:
Voltage ?

Envoyé de mon GT-I9505 en utilisant Tapatalk
[Galaxy S 4 i9505 Android Development] Phil3759:
Yes, the battery is really significantly swollen. I was surprised because since a few weeks it can discharge completely in a few minutes getting extremely hot for no reason

I will try to replace it quickly, but seems no stocks anywhere

Will try an RMA too

Thank you all for the tips
[Galaxy S 4 i9505 Android Development] Joery1983:
Isn't there a service centre near by? It is a warranty issue so you should get a new one for free.

Edit: overread RMA.... :)

Verstuurd vanaf mijn GT-I9505 met Tapatalk
[Galaxy S 4 i9505 Android Development] shoey63:
It can't be from just flashing.

usually EMMC used in these devices knows a write limit of 1.000.000 or more.
[Galaxy S 4 i9505 Android Development] aHcVolle:
I think formhault's 1000 write cycles sound more realistic than your 1mio.

Even industrial NANDs have a guarantee of ~10k write cycles... the 1mio are marketing only...
[Galaxy S 4 i9505 Android Development] gerardo87:
So from now we need to see under jflte folder for this and the next updates?
[Galaxy S 4 i9505 Android Development] Formhault:
1000 FULL cycles. Meaning Odin'ing 1000 times, lol, since that re-writes the ENTIRE NAND.
[Galaxy S 4 i9505 Android Development] aHcVolle:
if wear leveling works good then you should be correct.
[Galaxy S 4 i9505 Android Development] Formhault:
Wear leveling?!
[Galaxy S 4 i9505 Android Development] kaott:
just a quick report

6.15.6jflte.tar.md5 worked OK on sgs4 9505 MKF thru sgs4 flasher.
[Galaxy S 4 i9505 Android Development] ranger4740:
Backup Speed report for 6.17.9

Oh my lord this version is flying like a NASA rocket!!!!!!!!!!

Backup to sdcard 1 (external)

10:50 min

2525.38 Mb

34.64% Compression (fast mode)

Sdcard (internal)

6.33 min

2520.99 Mb

34.68% (fast mode)

I think this is the fastest version of backup I've used.

You've out done yourself phill!
[Galaxy S 4 i9505 Android Development] Formhault:
Phil, do you happen to know what are the average read/write speeds of the internal memory?
[Galaxy S 4 i9505 Android Development] Phil3759:
Update 6.18.7 Final

This will be the final version, using redistributable libtouch_gui library

This was a rally run :D
[Galaxy S 4 i9505 Android Development] www1:
Download link?

Inviato dal mio GT-I9505 con Tapatalk 4
[Galaxy S 4 i9505 Android Development] Chelonee:
Here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/jflte

You can find it in the opening post, too. :)
[Galaxy S 4 i9505 Android Development] franzyroy:
Still fast.

Thanks! ;)
[Galaxy S 4 i9505 Android Development] daniello8:
Could someone pls share his paths for internal external in Zipinstaller with the current recovery .. since the new version is out it doens't work well for me.
[Galaxy S 4 i9505 Android Development] kalitza:
Hi guys. I just got an i9505 and tried to root it some times already and it doesnt work for me :S

I flashed via odin(tar) and via sd cart (zip), the odin says Ok and pass, the phone reboot and when entering recovery mode, it goes into original one.

When flashing thru zip file, it says CSC: (my carrier). and reboots.

Any ideia how to root it and flash recovery?

THanks
[Galaxy S 4 i9505 Android Development] zeus85:
First of all what firmware are you on
[Galaxy S 4 i9505 Android Development] kalitza:
4.3. Just tried with CF-Auto-root and was able to root the phone.

I would love to have the philz but for what i searched, on 4.3 i guess only CF works - even so, the recovery is stock (searching now how to flash a rom on stock :P).

Thanks for the reply!!!!

cheers
[Galaxy S 4 i9505 Android Development] zeus85:
Download .md5 packaged recovery and flash using Odin that will replace stock recovery with recovery of your choice I highly recommend latest philz recovery its fast reliable and easy to use

Gt-I9505_Cm11_Nightly
[Galaxy S 4 i9505 Android Development] kalitza:
zeus85 , really, thanks a lot!!!! dammit so easy but i found nowhere these steps to get all to work.

Cheers and a great day for u ;)
[Galaxy S 4 i9505 Android Development] Tamsy:
What do you mean by "[...] it goes into original one." Do you mean the phone simply boots into Android without going into Recovery mode?

If this is the case try the following to go into Recovery:

- Switch off you phone.

- Push (and hold, all at the same time) the buttons 'Power ON' + 'Volume Up' + 'Home'.

- As soon as the phone vibrates and the little blue letters on the upper left corner are showing up, just release the 'Power On'-button while still pressing the 'Volume Up' + 'Home'-buttons.

- Wait a little while. This should bring you into PhilZ Recovery.

- Release 'Volume Up' + 'Home'-buttons...

Hope this helps.
[Galaxy S 4 i9505 Android Development] kalitza:
Thanks a lot for the help. It wasn't a problem getting into recovery, the problem was after flashng a new recorevy, when entering the recovery mode it wont get to new recovery only to stock. Now it all works fine. Needed to root first with CF-Auto_root and then flash the Philz recovery.

Thanks guys, really appreciate it!! ;)
[Galaxy S 4 i9505 Android Development] zeus85:
No problem mate enjoy your rooted s4 :)

Gt-I9505_Cm11_Nightly
[Galaxy S 4 i9505 Android Development] Phil3759:
You can root from within recovery

I just tried it on latest 4.3 and bootloader: it works

It is in PhilZ Settings, you get latest SuperSU from Chainfire
[Galaxy S 4 i9505 Android Development] MatteoB92:
[MENTION=4666971]Phil3759[/MENTION]: So, the development of this awesome recovery is stopped forever?

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Android Development] Phil3759:
:cyclops:

why?
[Galaxy S 4 i9505 Android Development] aHcVolle:
i guess he misunderstood the "final" version
[Galaxy S 4 i9505 Android Development] nomenore:
Hello my friend I want to ask a question my bootloader FNB8 4.4.2 but i want back to 4.3 bootloader bcause i flash miui rom but give me error status 7 solution for this problem ?

thank you
[Galaxy S 4 i9505 Android Development] Bejda:
It could be due to many reasons but probably not related to bootloader.

What is the exact status 7 error? Any details? (If you can't read it go to recovery advance settings right after the zip installation fails and use show log option or report error one to get a philz_recovery.log file under /sdcard/clockworkmod/ )

Which MIUI version is it? The Touchwiz based one or aosp/CM10.1.3?

Which Philz version did you use? Latest?
[Galaxy S 4 i9505 Android Development] HaTrED_:
Yes, there is!

Under install zip menu untick the option that is available and which name at the moment i cant remember!

Sent from my S4, another Galaxy!
[Galaxy S 4 i9505 Android Development] nomenore:
The latest version philz touc recovery and miui verison tw 4.2

---------- Post added at 03:51 PM ---------- Previous post was at 03:43 PM ----------

this
[Galaxy S 4 i9505 Android Development] nomenore:
This file my log :) probably
[Galaxy S 4 i9505 Android Development] Bejda:
Follow HaTrED advice above,go into install zip menu>untick "don't allow old update-binary" option and try again please.
[Galaxy S 4 i9505 Android Development] phileasx:
updated again, because i really like this ver number. :D
[Galaxy S 4 i9505 Android Development] MatteoB92:
Exactly, i misundestood its meaning, giving it my previous explanation : but obviously it's better this way :D

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Android Development] nomenore:
error gave the same error again

writestry try fixing some assert errors
[Galaxy S 4 i9505 Android Development] HaTrED_:
I've done that in similar situations without an issue!

Flash an older version of Philz's recovery like 6.08.7 and it should be sufficient!

http://goo.im/devs/philz_touch/CWM_Advanced_Edition/jfltexx/philz_touch_6.08.7-jfltexx.zip