yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] demlv:
hachamacha, I'm interested in giving this a try, but only after I understand how the 'extra partitions' will affect things.

I presume that the new partitions are taking space from the regular data partition, right?

I think my main concern with the use of nonstandard partitions is that if I ever wanted or needed to go back to a vanilla TWRP or CWM recovery, they might not "see" the nandroid backups created by your enhanced PhilZ Touch. I'm looking forward to see where to you take this.....
[Samsung Galaxy Nexus] hachamacha:
I think your confusion about that is because I forgot that I still had that text in there ^^ ;) Sorry about that. I'll try to explain it correctly and if I do, then I'll edit the post above these where the downloads are:

When I started doing builds a few months back for this recovery (but for another port/device), I had a few people ask me for some extra partitions to show up on:

- the mount (or custom mount) partition list
- the custom backup and restore menu.

So I did that for them. I think the two partitions involved at that time were /persist (where there is important data that usually is static but can be wiped, and also the /firmware partition. All I did was add them for RW access, mount access, and to the backup/restore(custom) menu's. So if someone lost some firmware or one of the WL drivers in the /persist partition, they could restore it from a custom backup. Nothing was taken from a regular backup or restore or from any other partition.

Phil3759 added the ability to use ~5 extra partitions (or partition mount points) without going into major surgery of the code. I allowed /persist to be mounted as /extra_part1, and /firmware as /extra_part2 and the truth is that I think I've reverted it so that it doesn't work that way anymore, at least for this port. So.. Nothing to think about. It is completely "standard" in it's usage of partitions now, and at worst, never caused any grief to anyone doing backups or restores. Just added some extra functionality.

Good question and I'll fix up the other post so it doesn't mention it anymore. Another build should be on the way later on.

Cheers.
[Samsung Galaxy Nexus] drive2droad:
is the version for toro & maguro different ?
[Samsung Galaxy Nexus] DR3W5K1:
Yes
[Samsung Galaxy Nexus] Phil3759:
:good:

I added you as contributor

You can now edit OP as you wish: post direct links to your download pages, updated versions, redirect users to your own thread...

It is up to you to edit as you like, really

Just keep the title so that I can monitor it easily
[Samsung Galaxy Nexus] hachamacha:
As noted by [MENTION=4811700]DR3W5K1[/MENTION]:

Yep. I was checking out the ./device tree of CM11 (which is the building base for this recovery) to make sure there wasn't not some "unified" build for the 3 devices, but there appears not to be. I'll build the other two as well and people that have those devices will have to do the testing and report back here. I suppose it makes more sense for me to put a thread in those device forums but I think they'll all look alike or point to this one for ease of upkeep.

-

---------- Post added at 06:42 AM ---------- Previous post was at 06:37 AM ----------

[MENTION=4666971]Phil3759[/MENTION]:

Thanks. I was wondering if such a thing was doable so now I know. No interest in changing much but I'm curious to know if there's any way I can upload directly to the projects here (link: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/toro that I'm a contributor to?

Or: Should I just use the dev-host I've been using for uploads/downloads?

Much appreciated.

---------- Post added at 07:03 AM ---------- Previous post was at 06:42 AM ----------

Please download from OP. Here's a change log for 6.40.6:
[Samsung Galaxy Nexus] Phil3759:
I asked goo team, but never got a response

Not sure they do not cut off my ftp account if many different ip connections...
[Samsung Galaxy Nexus] hachamacha:
Version : 6.41.5 Stable added

Download from OP:
[Samsung Galaxy Nexus] hachamacha:
Version : 6.41.6 Stable added

Download from OP:
[Samsung Galaxy Nexus] demlv:
I'll try it myself soon enough, but in the meantime I'm just wondering if anyone has had a good (or bad) experience restoring a CWM incremental-style nandroid using Philz recovery......;)

Thanks
[Samsung Galaxy Nexus] Shadow Death:
Philz is CWM based. I've done a few nandroids with CWM in the past and restored them using Philz.
[Samsung Galaxy Nexus] furiyk:
Just wondering, does this recovery have multiple zip flashing too? Or is it more cwm based?
[Samsung Galaxy Nexus] Phil3759:
it has

AND READ MAIN THREAD!!
[Samsung Galaxy Nexus] cujo6801:
Somebody's in a mood... :eek:

Sent from the "DOG" pound
[Samsung Galaxy Nexus] Shadow Death:
I have to side with Phil on this one. I used to see it all the time on the Bolt forums people would ask about a feature that was discussed a few posts up or could be found in the OP. It does get pretty aggravating.
[Samsung Galaxy Nexus] cujo6801:
Normally I would agree with your logic..

but this is a very seldom used thread....

And we know people just don't read..

I guess it just struck me odd...

You know what I mean?

Sent from the "DOG" pound
[Samsung Galaxy Nexus] Shadow Death:
Yup... Phil seems to be a normally cool person... Guess that one just stuck a nerve.
[Samsung Galaxy Nexus] cujo6801:
Agreed....

Sent from the "DOG" pound
[Samsung Galaxy Nexus] demlv:
Deleted.
[Samsung Galaxy Nexus] demlv:
New versions?

The version of Philz recovery that I am running (6.41.6 I think) is working well. But it looks like the Philz code is being revised to separate from CWM. I also see that the last couple of versions in this thread were called "Stable". Will any of the new development on the recovery benefit my now aging phone? Should I care about there ever being a new version of Philz Touch for Toro?
[Samsung Galaxy Nexus] hachamacha:
Version : 6.50.6 added

Download from OP: Please note that I have no Nexus at this time, so can't test the build myself. Good luck.

6.50.6 -

- fix potential failure for TWRP backups (cause scan_mouned_volumes() not called)

- loki_recovery code clean up

- fix potential failure to reboot when checking config file

- never confirm wipe in ors scripts

- always show text in sideload mode

- support wipe_cache and clear_display edify script commands
[Samsung Galaxy Nexus] demlv:
I guess I was one day too early in wondering about updates......:good:
[Samsung Galaxy Nexus] demlv:
I flashed the new zip but I can't get my phone to boot into recovery. Anyone else?
[Samsung Galaxy Nexus] hachamacha:
Have you got log files from /cache/recovery? If so : could you please post them (attach)? I haven't been keep this device up to date but I have one at the moment so will try to do the most recent build for it. It'll be awhile since I need to fetch the latest device-specific source.

Also: I've not kept up to date on where ROMs are at (version-wise with 4.x.x Android), so it would probably make a difference if I'm developing for KK and beyond and the ROMs being used are pre-KK (kernels, etc). At this point, I'm building using the latest CM11 base, which is likely 4.4.2->4.4.4. Anyway, if I can get my nexus charged and try a flash, we'll either have a build up here (6.55.0) in a few hours or I'll try to figure out what's wrong. I may not have had the device last time I posted a build so no testing on that one.
[Samsung Galaxy Nexus] hachamacha:
Version : 6.55.0 added

Please DL From OP:
[Samsung Galaxy Nexus] quickdraw86:
Hmm... Don't see it.
[Samsung Galaxy Nexus] hachamacha:
Bottom of the quoted section under release notes:

like this:

- v6.55.0: toro: img: http://d-h.st/CNW and zip: http://d-h.st/QDe

- v6.50.6: toro: img: http://d-h.st/SWU and zip: http://d-h.st/NqP

- v6.41.6: toro: img: http://d-h.st/SrA and zip: http://d-h.st/l9w

- v6.41.5: toro: img: http://d-h.st/NpH and zip: http://d-h.st/2Dp

- v6.40.6: toro: img: http://d-h.st/prG and zip: http://d-h.st/9i1

- v6.40.1: toro: img: http://d-h.st/i4I and zip: http://d-h.st/ZY0

[/QUOTE]
[Samsung Galaxy Nexus] swarlesbarkely:
Delete
[Samsung Galaxy Nexus] oubeichen:
could you please add f2fs support or publish your device tree source?

It's a great recovery and I don't want to switch to another anymore.

thanks..
[Samsung Galaxy Nexus] hachamacha:
Hi - I was pretty sure one of the changes that had occurred in recent github source was the auto-detection of file-system types and appropriate mounting, but maybe it needs to be put in extra.fstab or a flag set in ./BoardConfig.mk for this device. I've just been building for this device not using one, so could you tell me which FS's you've got that're now f2fs?

Maybe I can get you an test build by next week or sooner. I think all the other devices I build for support f2fs and the recovery does fine with them so it must be a case of the Nexus not having been kept up with in it's(recovery's) device config.
[Samsung Galaxy Nexus] Phil3759:
https://github.com/CyanogenMod/android_kernel_samsung_tuna/blob/cm-11.0/Makefile#L2

kernel 3.0 !

f2fs is more than experimental and not implemented in device tree

You'll have to mess with it or use TARGET_PREBUILT_KERNEL
[Samsung Galaxy Nexus] oubeichen:
What does "FS's" mean?

there are some commits in vanir's kernel that provide support for f2fs:

https://github.com/jimsth/vanir_tuna/commits/jim_mr2_exp?page=2

And maybe we could take

https://github.com/PhilZ-cwm6/philz...b/cm-11.0/device/amazon/tate/init.recovery.rc

as an example to create our own recovery.rc

And add f2fs mount in extra.fstab.

I've got a test build by my own yesterday, but don't have time to backup my phone until next weekend..
[Samsung Galaxy Nexus] hachamacha:
Sorry, FS's was meant to be lazy/shorthand for File Systems. There's plenty of f2fs support everywhere but in the kernel, but I don't know anything about vanir's kernel yet but will look around and see if we can use that if it fits the bill.

Other than that I've got the proper entries for a nexus for extra.fstab for /data, (well, and the rest as well if anything else is going to be f2fs, like /cache).
[Samsung Galaxy Nexus] DR3W5K1:
Im currently running /data /system and /cache f2fs fwiw
[Samsung Galaxy Nexus] hachamacha:
So I see you made a version. Does that one include the vanir kernel? Either way: Have you given it a try?
[Samsung Galaxy Nexus] gorillabiscuit:
Flashed it, now I can't boot into recovery... Any special tricks? Nothing fancy and no f2fs. Latest version off Goo
[Samsung Galaxy Nexus] hachamacha:
There's no tricks if it doesn't boot at all (into recovery), but since you only flash recovery.img (or whatever you called it) to the recovery partition, you should be able to boot into the system, and "adb reboot-bootloader", then "fastboot flash recovery {recovery_name_you're_using}", then try rebooting to recovery after "fastboot reboot". Oh wait: Fastboot itself probably lets you choose 'recovery', so 'down, down, up' (down till you get to recovery, then up) (I think this is right, but I don't have a nexus available now). If you can find a build of TRWP or anything that works with your F2FS partitions on a Nexus then use that for now. We'll get this one-off version of Philz Touch for the nexus figured out with one of the kernels that're around.

I didn't think that vanir's was the best choice since it's too close to the original kernel with a backport and mostly because I got a few build errors that seem due to commits about 15 days back. I'm now trying the r53 version of something here: https://github.com/boype/kernel_tuna_kk44.

PS: If you meant "are there build tricks?" then yes: You need to really read page 1, (past the OP, I think post 2 or 3) of the developers thread http://xdaforums.com/showthread.php?t=2201860. At the least there are flag(s) you need to set in $Philz/boardconfig/BoardConfig.mk (for the cm_toro build) and perhaps more. I need to read it again myself.
[Samsung Galaxy Nexus] Phil3759:
enabling f2fs must be done in the kernel first

you must ensure the whole recovery.img file fits recovery partition size as most custom kernels are too huge. I usually enable lzma compression in kernel for these

in recovery, you must just set the f2fs flag in boardconfig and grab the android_system_vold patch from my git
[Samsung Galaxy Nexus] hachamacha:
So far: I've now taken the f2fs folder from another kernel, moved it into the $CM11/kernel/samsung/tuna/fs dir and then modified KConfig in the ./fs dir to make f2fs dependent upon BLOCK. I've imported vold from your git and I'm trying to build that combination now. I've also set the F2FS flag in boardconfig/BoardConfig.mk

Am I missing something obvious?

I'd tried using the TARGET_PREBUILT_KERNEL flag setup to point to my own version of zImage (same size as orig) but with f2fs, but it seems like that either isn't still working like it used to but I don't have time to keep on that without a bit of help.

Thanks.
[Samsung Galaxy Nexus] oubeichen:
Sorry, I can not access with my computer until next weekend.

But here is my own build(CM's kernel with minimal f2fs related commits)

'philz_touch_6.56.2-toro-f2fs.zip': https://onedrive.live.com/redir?resid=6E3D1F5C3B498D95!193&authkey=!AAUtH4S9UeuALH0&ithint=file,zip

I would appreciate it if someone can test it.

We can still flash another rec via fastboot if it wont work
[Samsung Galaxy Nexus] hachamacha:
Hi -

Cool and thanks.

I'm about to give up for the day, but have just finished building my own 6.56.2 also. I'm in recovery now and have so far, backed up /cache as ext4, formatted /cache as f2fs (everything on my old nexus was definitely not f2fs). Anyway, I'm trying to test it and am about to try restoring it onto the f2fs /cache partition. I'm not sure the phone will boot until I fix it up afterward but am not worried about that. (yet)

What I did in this one was backport f2fs from a kernel.org kernel just a little ways up the line from when f2fs appeared there, then added f2fs into system vold and I think the last thing was to use the BoardConfig.mk flag *_F2FS in recovery. I was thinking that the auto-FS detection should figure out the rest so we'll see on the next test.

Update on restore to f2fs cache: Well, not good. Although it appeared to be doing the right things, I couldn't mount the f2fs /cache (if that actually worked), and since I chose cache I'll not be getting a log for the session. Back to the drawing board. I'll get it in fastboot and flash 6.55 for the moment to get things going again.

Update 2: I flashed 6.55 from fastboot, reformatted /cache, did a custom restore from a backup, and it's alive again. Time to mess with it once more.

Before I head out for the night, I tried [MENTION=5208741]oubeichen[/MENTION] build and it boots fine, shows the ext4<->f2fs option, which I could toggle. Trouble is that I don't have time right now to test it much further. I'm just running a backup and a small restore. This is better tested by someone who is using f2fs on their device. It seems to at least be backwards compatible with my old filesystems.!

Thanks [MENTION=5208741]oubeichen[/MENTION].
[Samsung Galaxy Nexus] swarlesbarkely:
I'm currently on f2fs and am comfortable with fastboot, recovery, living dangerously, etc. What do you want me to do? I like philz and wanna see it have f2fs
[Samsung Galaxy Nexus] hachamacha:
Sounds good. Want to try [MENTION=5208741]oubeichen[/MENTION]'s build about 2 posts up? I know it works generally but just see first if it shows any f2fs filesystems as mounted, and if so, get the /cache/recovery/*log* file (last_log is good) and post it.

If it doesn't appear to be unhappy with your f2fs stuff then see if you can do (e.g.) mounts and dismounts on the f2fs filesystems, and finally just do a backup, and if you're really feeling good and this is going OK, maybe a restore of the backup you did back to one of the f2fs filesystems (a custom restore i.e.)

Thanks!

Maybe just so we know what your filesystems look like for debugging (if needed), go into Aroma, open the terminal console (or use adb..) and do a "#mount >> /sdcard/mount.log" and attach or post that too. Then we get to know if the mounting worked, if the mounting parameters match those in extra.fstab, etc...
[Samsung Galaxy Nexus] swarlesbarkely:
Here's what I got. A lot of the log is junk while I set stuff up theme wise. Took a pre and post mount. Did a backup but didn't have time for a restore if it went wrong. Formatted /cache f2fs (already was though). Can do more tomorrow if you want me too. This is just what I could do quick.
[Samsung Galaxy Nexus] hachamacha:
Thanks for the log files. Those look really good. The mount command output shows 3 f2fs systems 2 rw, 1 ro. Let us know how the restore goes. I'm guessing it'll work.
[Samsung Galaxy Nexus] swarlesbarkely:
Just did the restore.. Booted just fine. Will report back with any issues.
[Samsung Galaxy Nexus] hachamacha:
Just wanted to mention that the last and current working build was by [MENTION=5208741]oubeichen[/MENTION] . Since I don't use a nexus these days and since he did a great job, I'm handing over (or suggesting to Phil that he take over) the maintenance of this thread to him. If you want the latest version (with f2fs compatibility), then use the link quoted above. Thanks.
[Samsung Galaxy Nexus] demlv:
Just wondering if anyone capable of maintaining / updating Philz Recovery is still watching this thread. I understand that no major updates will be coming, just hoping that us Toro users will get the benefit of any future bugfixes. Anyone?
[Samsung Galaxy Nexus] JPREMEEE:
This Dead Correct?
[Verizon Samsung Galaxy S III] lazarus0000:
A little background...

I got the S3 a couple months ago and went a little crazy flashing any / every ROM that looked even the slightest bit interesting - all without thought or knowledge of the differences between 4.2.1 & 4.2.2. With 4.2.3 (?) coming out soon, I want to be able to have a totally clean install.

I'm interested in a totally clean wipe BUT not having to re-root, flash CWM, etc... Looking to get rid of the multiple emulated SDs (I think I've got 3 and they are empty when I look @ them in ROM Toolbox), all the other data from apps and start over from (mostly) scratch.

I've got a 64gb external SD that I want to keep intact and am not opposed to backing things up to there. When I had my old OG Moto Droid and with my Charge, I was pretty comfortable doing things like what I'm planning but with this whole "internal" SD, I'm afraid I might screw things up royally.

Anyone have ideas or a thread you can point me to that will allow me to do this safely and start over without all the clutter that I've developed recently?

Any / all help is appreciated! Thanks!

"You live & you learn. Or you don't live long..." - LL
[Galaxy Note GT-N7000 Themes and Apps] rush25:
Galaxy S4 Flare Lockscreen ported to Galaxy Note Stock 4.1.2

​

Features :-

-Flare Lock from S4 4.2.2 to Note 4.1.2

-Works on All Stock Roms [Odexed or Deodexed]

-S4 unlock sounds

Instructions :-

-Download the file

-Copy to sd card

-Reboot in recovery

-Flash the file

-Reboot

Credits :-

-Koulis2000 [Original Thread]

-salesale

-Villain Rom Team

Downloads :-

-Build 1

Mods :-

-Mod 1

Note :-

-You need to disable ripple and ink if you want to see the flare

-If you dont want the white lock icon in center of the flare then flash Mod 1

Please Hit Thanks or Donate to Support​
[Galaxy Note GT-N7000 Themes and Apps] parasverm:
cant able to download link is nt working...
[Galaxy Note GT-N7000 Themes and Apps] mjrifath:
Wow thanks mate.

I was waiting for this when I saw this mod on S2 thread.:)

Mate download link not working. Appreciate if you fix it.

Will report after check this :thumbup:

Cheers.
[Galaxy Note GT-N7000 Themes and Apps] rush25:
devhost is not working..i am uploading :D
[Galaxy Note GT-N7000 Themes and Apps] mindfck1337:
the link is not working :D cant wait to download :D

edit: nevermind :x
[Galaxy Note GT-N7000 Themes and Apps] rush25:
links up..please test and report also post a screenshot :D
[Galaxy Note GT-N7000 Themes and Apps] tomascr7:
Gonna test.. Would be awesome if that is the original one from s4 ? :)
[Galaxy Note GT-N7000 Themes and Apps] mindfck1337:
works fine on JonRom V8 :)

cant take a screenshot on lockscreen :/
[Galaxy Note GT-N7000 Themes and Apps] tomascr7:
So it works but its not like the s4 lockscreen.. When i want to open it, the flare isn't going the trail of my finger, it just stands still and when i swipe it just opens normally like the lockscreen with the lock icon..

Or i do i need to install the mod, to make it not staying at one place when swiping ?
[Galaxy Note GT-N7000 Themes and Apps] rush25:
mod will remove lock icon and make more look like s4...its the same like on s4 ..it follows your finger with ripple and i have not found anyway to enable it with ripple..
[Galaxy Note GT-N7000 Themes and Apps] tomascr7:
Ok, gonna test it :)..

Thanks, you are awesome.. ! :)
[Galaxy Note GT-N7000 Themes and Apps] fazdnoah:
Not working on Superbean :(

But i like the lock & unlock sound :)
[Galaxy Note GT-N7000 Themes and Apps] tomascr7:
The mod just removed the lock icon and the flare doesn't follows my swipe, it just stands still where i touched it :(
[Galaxy Note GT-N7000 Themes and Apps] rush25:
mod will remove lock icon and make more look like s4...its the same like on s4 ..flare follows your finger with ripple but i have not found anyway to enable flare with ripple..
[Galaxy Note GT-N7000 Themes and Apps] abidalisayyed:
Which file do i need to flash?

Both one?

I am on stock xxlt4 odex rom
[Galaxy Note GT-N7000 Themes and Apps] weng_cas:
Not working on galactus rom
[Galaxy Note GT-N7000 Themes and Apps] wjlung:
Working on my Note with stock 4.1.2 LT4 deodexed rom.
[Galaxy Note GT-N7000 Themes and Apps] XxPixX:
Thanks for this MOD, I have been waiting for this. Just one thing I noticed it says prepare for a s4 lockscreen experience on your siiinothing wrong with that of course.

Working on GalactusMod v3 XXLT5
[Galaxy Note GT-N7000 Themes and Apps] galaxynote2:
Bootloop here. Pristine XXLT5, i will try wiping cache and dalvik

EDIT: No, doesnt work.
[Galaxy Note GT-N7000 Themes and Apps] radoslavm:
Works on Ultimate v. 6
[Galaxy S III Mini Q&A, Help & Troubleshooting] mastasanuh:
Hi,

I've just installed setcpu ver 3.0.9. I encounter 2 issues.

1) I can't set the min & max cpu frequency, it seems that the slide setting is not working.

2) Error message:

"Could not setcpu custom config. Reverting to default. Is your sdcard unmounted from pc?". The funny thing is I haven't set any custom config.

Please help...tq

I'm on rooted stock rom.

Jb 4.1.2
[Galaxy S III Mini Q&A, Help & Troubleshooting] samersh72:
install busybox and trickster mod from market.
[Galaxy S III Mini Q&A, Help & Troubleshooting] mastasanuh:
Thanks buddy. :)
[MDA II, XDA II, 2060 ROM Development] adamms:
Hi

I have problem with unlock my pocket qtek 2020.

Radio 1.17

d 1.72.00WE

How can I do it ?

Greetings from Warsaw :))
[MDA II, XDA II, 2060 ROM Development] Motard69:
Where did you find that upgrade with 1.17 radio version? Where i can download?

Thank You
[MDA II, XDA II, 2060 ROM Development] adamms:
I buy new phone with new software and I can`t unlocking my mda :(

Greetings from Warsaw :)