yashsingh1/xdaforums huggingface dataset:
[Android Software Development] hypnz:
Hello phil at latest version I have very slow restore. Imagine the restore I've done yesterday done at 111mn!!! I forgot to keep a picture or somt!!
[Android Software Development] patch_Adams:
Hello. I just built this recovery for a user over in the ATT note 1 q&a thread. I posted a link for them there, hope that's cool? Strange enough, I didn't change anything. Just used my local cm11 source and device files then used a local manifest to put your source code in the bootable/recovery folder and then ran this:

pa@pa:~/cm11$ make clobber && make -j8 recoveryimage

then copied the recovery image into a flashable zip and it worked out fine.

Thanks!
[Android Software Development] x-dira:
plzz...support asus memo pad 8

Thanks!
[Android Software Development] dams161:
http://xdaforums.com/showthread.php?p=50199630

https://bitbucket.org/Astrali/device_alcatel_ot6034r

Please help me

[MENTION=4666971]Phil3759[/MENTION]
[Android Software Development] notzippy:
Probably dumb question but what are you using for a text editor in the shell ? Most recoveries have vi, but it does not appear to be available. Do you use another ?

thanks

Nz
[Android Software Development] HippoMan:
The file in /data/media/clockworkmod/aromafm should be renamed to aromafm.zip

.​
[Android Software Development] Looki75:
Is this recovery compatible with F2FS file system?

Can it format NAND partitions to this standard?

Thanks
[Android Software Development] Phil3759:
Guess he's fighting this for weeks :crying:
[Android Software Development] aviwdoowks:
Partial fix :rolleyes: !

Now the data/media aroma will not self mount sdcard1. I must choose install zip from sdcard1 before I launch aroma, now.

Swap or not does not matter.
[Android Software Development] Phil3759:
1- you spammed the thread and made me loose a lot of time not being able to correctly read my answers. Ended up revising my sources to find you're just :cyclops:

2- it is a known vold limitation. I will work around it on next updates. For now, mount manually in recovery menus
[Android Software Development] HippoMan:
Hi aviwdoowks. You misspelled "I sincerely apologize, Phil, for continuing to complain in an entitled and immature manner for nearly two weeks without even bothering to try to re-read your instructions, and therefore, for wasting your time."

.​
[Android Software Development] aviwdoowks:
I totally missed the problem. Thanks for pointing it out.

Indeed I am sorry for the all the fuss.

Thank you Phil... I am a diehard fan, thanks for putting up with enthusiastic noobs!
[Android Software Development] seansc144:
Your a genius at this
[Android Software Development] Erahgon:
If I'm not mistaken, the i9000 series of phones have a combined recovery and kernel. Not sure it's possible to patch one without the other. In other words: if Phil chooses to port his recovery over, he will have to add in a kernel as well, which means you will need different versions of the kernel + recovery package for stock based ROMs and AOSP based ROMs.

Unless there's a method that backs up the existing kernel, patches it with the recovery, and then proceeds to flash it.

Either that, or Phil makes his recovery with the stock ramdisk and have other people include it in their custom kernels.

Sorry for the bit of a ramble!

Sent from my GT-I9300
[Android Software Development] shoey63:
Same deal as I9100 and GT-N7000. Phil can do it easily. Just a question of whether he feels it's worth doing on such an ageing device :p
[Android Software Development] ChitownWingMan:
Maybe with a little help Phil could write an application that would extract the necessary information from the stock recovery and merge it with his files and create the new recovery?

This would only work if the Phil's files do not need to be recompiled for each device. I really don't know anything at all about the structure of the recovery image.

Phil, if you are reading this, I am something of a C/C++ hacker (34 years in embedded systems for the most part). Does this idea have any merit? Is there any way I can help?

Thanks...
[Android Software Development] Phil3759:
I already use custom shell scripts to automate conversion from stock zImage to PhilZ. However, i have no time to start another project. No need to c for that. Shell is all you need and available unpack/repack tools
[Android Software Development] thatotherguy..:
this is for sprint htc one
[Android Software Development] Phil3759:
no need to attach custom cwm files.

I only need attachments for stock recovery, if really needed for some features to work, like exfat, aroma on some devices...
[Android Software Development] Phil3759:
S3 T-Mobile variant support added (SGH-T999)

http://xdaforums.com/showthread.php?t=2310081
[Android Software Development] thatotherguy..:
Alright I'll get you stock recovery

http://www.androidfilehost.com/?fid=22909751817929743
[Android Software Development] Phil3759:
HTC One seems to run fine with cm-10.1 device tree. Again, only upload files if I ask for

I am releasing HTC One Sprint and TMO

Just updated the source and compiling them now
[Android Software Development] eushaun99:
Hi there!

Any plans for a possible port for Samsung galaxy tab 10.1(P7500)?

Here is the stock recovery.img taken from the latest Czech ROM ICS 4.0.4. http://db.tt/qCxUK3cZ

Thanks! :)
[Android Software Development] Phil3759:
New devices support: HTC One variants

- HTC One T-Mobile (m7tmo)

- HTC One Sprint (m7spr)
[Android Software Development] wpkwolfseye:
Hi. I didnt read all 25 pages but I searched the topic and do I assune right that PhilZ CWM isn't compatible with the N8010 yet? I saw other posts on google for the N8000 and the N8020 but not the 8010, is that correct?

Thanks in advance.

Wolfseye
[Android Software Development] danarama:
Following the N8xxx link in post 1 ....looks like 8000, 8013, 8020
[Android Software Development] Phil3759:
There is one report of N8010 being compatible with N8000/N8013

However, if you want to be sure, upload here a recovery.img from your 8010 ROM (download from sammobile.com, rename tar.md5 to tar and extract the recovery.img with winrar, upload it here)

I will know if it is compatible. If not, I will release a 8010 variant
[Android Software Development] wpkwolfseye:
Whats weird, I just checked on Sammobile and it says there the last Firmware for the 8010 is N8010XXUCMD2 (PDA) from April 2013. We bought our N8010 in May 2013 and after unpacking we went to Software Update and there was nothing. When I check on my Note, it says the following Firmware:

N8010XXUCMA8

How comes my N8010 was running an as it appears older Version of 4.1.2 but didn't notify of any update after unboxing? Of course by now its rooted and has some other CWM Version installed, so I cant officialy update anymore with OTA. What would be the best way now? Complete fresh install of original N8010 Rom with the latest Build via Odin and then go and install CWM again?

Wolfseye

Gesendet von meinem GT-N8010 mit Tapatalk 2
[Android Software Development] Phil3759:
Just upload the recovery.img of whatever firmware you like :rolleyes:
[Android Software Development] wpkwolfseye:
Yes but I wonder if I should make it all from scratch first so it actually is the latest Firmware before I ask you to check if yoir CWM works with the latest recovery.img. Instead of using an older recovery.img from thr it seems older Firmware I am running right now.

Gesendet von meinem GT-N8010 mit Tapatalk 2
[Android Software Development] Phil3759:
It doesn't matter for recovery. I only need to read what's in it
[Android Software Development] denzel09:
About lg p760 l9 is there a possibility?
[Android Software Development] Phil3759:
As said earlier, for now, no new devices except conditions i enumerated and variants for already supported devices
[Android Software Development] Phil3759:
6.15.4 (13.02.2014)

Most devices will be updated

Note

I am actually extremely busy as you see from that change log

There are also huge changes to device trees on going to use universal device for many variants like d2, hlte and jflte

Also a lot of work to commit to gerrit

Planning to use re-distributable lib touch

...

To all devs waiting for something: sorry, but for now, I am really overbooked
[Android Software Development] HippoMan:
Thank you for rising to the occasion. Phil has no doubt worked hard on this excellent recovery module, and especially to help those of us who have had issues with it. At a bare minimum, he deserves our thanks for his efforts.

.​
[Android Software Development] ameinild:
Looks pretty massive - good things take time :) :good:
[Android Software Development] Phil3759:
List of phones that got the update:

Most are uploaded and the rest is in the way

If you feel a device must get an update for some valid reason (see the change log), feel free to request.

I will be working on merging the unified device tree for d2lte, jflte and hlte variants which is some work, but will make maintenance easier with much less devices to work on
[Android Software Development] hypnz:
Phil any chance to take New build optimus g pro so can solve the slow backup/restore procedure?
[Android Software Development] Phil3759:
Is backing up slow to internal or to external storage?

What are the times (average) ?
[Android Software Development] HippoMan:
aromafm issue in 6.15.4

Thank you for this upgrade.

I just performed the upgrade of my apexqtmo to 6.15.4, and now I have an issue with aromafm that I didn't have in 6.12.8.

I can only run aromafm once per recovery session. I have to exit from recovery and reboot back into recovery each time I want to run aromafm.

The following scenario illustrates the problem:

1. Boot into recovery.

2. Select PhilZ Settings -> Aroma File Manager

3. aromafm properly comes up. Do whatever I want using aromafm (including doing nothing).

4. Select Menu -> Exit from aromafm, followed by Yes.

5. aromafm properly exits, and I'm back at the PhilZ Settings menu.

6. Select Aroma File Manager again.

7. aromafm fails to come up, with the following error message: No clockworkmod/aromafm/aromafm.zip in storage paths.

8. Reboot into recovery again.

9. Select PhilZ Settings -> Aroma File Manager

10. aromafm now comes up properly, once again.

I checked for the existence of clockworkmod/aromafm/aromafm.zip, and it indeed exists, and therefore, it never was deleted.

I'm guessing that exiting from aromafm somehow changes the states of the mounts so that clockworkmod/aromafm/aromafm.zip no longer is accessible until recovery is exited and re-entered.

Does anyone else see this problem?

.​
[Android Software Development] Phil3759:
1- did you know that you can launch aroma fm with just a double tap on screen outside menu?

2- did you know that you can change it to be another gesture action?

3- I tried to reproduce your issue with menu and gestures, by putting aroma fm in internal then external storage, and I have no issues

---> Post a log once it fails on you
[Android Software Development] Phil3759:
All those devices are now online

Refresh goo in a while if not :p
[Android Software Development] Teufel Hunden:
Woohoo first for t0lteatt lol

Big dogs on the block, NOTE 1&2
[Android Software Development] HippoMan:
Thank you for looking into this. The problem is now solved, but I'm not sure why.

First of all, I hadn't tried the gestures before. However, I had the same behavior as described above both when invoking aromafm via the menu and via gestures.

I then looked for a phllz_recovery.log file to send you, as well as just plain recovery.log, but I couldn't find either of those anywhere. I guessed that there was some sort of problem with my clockworkmod directories, so I renamed clockworkmod to clockworkmod.save, both on /sdcard and on /mnt/extSdCard.

Then, I reinstalled the 6.15.4 recovery and booted into it. This recreated a new /sdcard/clockworkmod directory. I then rebooted to the OS, created an aromafm subdirectory within /sdcard/clockworkmod, and reinstalled aromafm.zip therein.

Finally, I rebooted into recovery, and now, aromafm works fine. I can exit and restart it as many times as I like, and I can invoke it both via the menu and via gestures.

The only reason I can think of for my problem is that there might have been something wrong with the earlier contents of clockworkmod, either on /sdcard or on /mnt/extSdCard, because recreating /sdcard/clockworkmod from scratch fixed everything.

Of course, whatever might have been wrong didn't affect 6.12.8 -- only 6.15.4. But anyway, as long as it's working now, I don't think I need to do any more investigation.

So ... all's well that ends well. Thank you again for your help.

.​
[Android Software Development] Unjustified Dev:
[MENTION=4666971]Phil3759[/MENTION] is screenshot code open? If so can you link me to the commit.
[Android Software Development] Phil3759:
The most is open

It is fb2png folder and just a shell script
[Android Software Development] Unjustified Dev:
Can I get the script or is it included with closed code?
[Android Software Development] Phil3759:
It is in read.me from fb2png

Let me know if you need more details
[Android Software Development] Unjustified Dev:
Ok , I will take a look thanks. What about official support for tab 3 7.0? I can update code for cm-11.0 in minutes if need be

http://xdaforums.com/showthread.php?t=2468441

https://github.com/gr8nole/device_lt02wifi
[Android Software Development] Phil3759:
When you are ready, just ask

Fix any stock cwm issue before please
[Android Software Development] Phil3759:
Also, when back, i will send you the screen shot snippet if you still need it
[Android Software Development] Unjustified Dev:
Thanks it's 3am fighting the sleep . I will check back later.
[Android Software Development] HippoMan:
By the way, in case this helps anyone else, the reason I couldn't find philz_recovery.log during my earlier investigation is that I had forgotten about invoking this from within recovery:

Advanced -> Report Error

This creates the philz_recovery.log file within the clockworkmod directory.

.​
[Android Software Development] Phil3759:
Else, they are all in /cache/recovery when you reboot
[Android Software Development] Phil3759:
FAQ Updated:
[Android Software Development] Phil3759:
Added a few more devices to 6.15.4 Update

I will upload them by the end of the day
[Android Software Development] trancoss2:
Thanks for your work.;)

Enviado desde mi GT-I9300 mediante Tapatalk
[Android Software Development] tvm2487:
I was wondering if you can build the full touch version for the d710 device i'm built the version from your github and it built and worked perfect so i would really like to see how the full version is
[Android Software Development] Phil3759:
See op and provide needed links to repos
[Android Software Development] hypnz:
Both! Last time I make restore, restoring lasted 112 minutes!!!
[Android Software Development] Phil3759:
I am uploading e980

Let me know
[Android Software Development] dams161:
[MENTION=4666971]Phil3759[/MENTION]

please a little help for me probleme

I can not find

my knowledge is overfilling

http://xdaforums.com/showpost.php?p=50315912&postcount=371
[Android Software Development] Phil3759:
All above devices updated

Next update will concern ALL devices, but now, working on sources for unified device tree on some devices.
[Android Software Development] tvm2487:
https://github.com/MoKee/android_device_samsung_d710/tree/kk_mkt Device Tree

https://github.com/MoKee/android_kernel_samsung_d710 Kernel

https://github.com/MoKee/android_device_samsung_d710-common Common Files

https://github.com/MoKee/android_vendor_samsung_d710/tree/kk_mkt Vendor Common

That should be everything you need
[Android Software Development] Learnerspermit:
Noob trying to muddle through this, so apologizes in advance.

running the following in adb with phliz touch 6.15.4-d801 (for my T-Mobile LG G2)

adb push loki_flash /data/local/tmp/loki_flash

adb push recovery.img /data/local/tmp/recovery.img

adb shell

su

cd /data/local/tmp

chmod 777 loki_flash

./loki_flash recovery /data/local/tmp/recovery.img

At this point it says this isn't a loki image, so I referred back to this:

How to lokify before flashing:

In Advanced Menu / Toggle Loki Support : enable auto loki

Flash the zip file and you are done

and unfortunately that's were my noobness kicked in. What advanced menu? Or is there another program you're referring to?
[Android Software Development] iamsuperuser:
[Request]

[MENTION=4666971]Phil3759[/MENTION]

Can you please compile PhilZ Recovery for my Samsung Galaxy Note 3 SM-N900 Exynos ha3g version

Here is the Stock recovery.img
[Android Software Development] Phil3759:
Does the Galaxy S II Epic 4G Touch (d710) have a shared recovey/boot partition please?

If it is the case, you won't be able to flash my builds on a stock kernel until someone repacks it. It will only run on cm-11.0
[Android Software Development] tvm2487:
Im not really sure i dont think so cause i have a build of twrp recovery and theres no boot.img its an inject twrp file and a ramdisk-recovery.img inside the flash able zip,,,i also plan to use it on cm-11.0 type builds
[Android Software Development] Phil3759:
Seems it is the case sadly

So, it will be only for AOSP/CM kitkat ROMs, until someone repacks it
[Android Software Development] tvm2487:
Ok that's fine I'll try and figure out how to repack it,,, I'm on my MoKee 4.4.2 build anyway so it will work for me lol thanks for making it available for this phone
[Android Software Development] Phil3759:
Update 6.15.6

- All Galaxy S4 variants now use one common recovery: jflte

It will properly enable loki on variants that need it and not on others
[Android Software Development] tetakpatak:
[MENTION=4666971]Phil3759[/MENTION] can you please just create an Odin flashable package of the recovery for galaxysmdt (i9000)? I'm not sure if pawitp has meanwhile merged the very new CM11 kernel also for the i9000 or not. Did you wait for if?
[Android Software Development] Ripshock:
Could you provide an update for galaxy tab 3 7 sm-t210r?

Thanks in advance

Sent from my SM-T210(R)ocketTab 3.1 $up€R_f@$T
[Android Software Development] danarama:
All supported devices are being updated. Please try to keep up-to-date
[Android Software Development] Ripshock:
Mmmm about that, it's not supported in this thread it's supported in galaxy tab 3 7 android development in a thread made by gr8nole :D but I am running it on my tab (SM-T210R) but v2 :/

Sent from my SM-T210(R)ocketTab 3.1 $up€R_f@$T
[Android Software Development] danarama:
Unofficial port?
[Android Software Development] Ripshock:
Exactly

Sent from my SM-T210(R)ocketTab 3.1 $up€R_f@$T
[Android Software Development] Phil3759:
No news since 6 months :p

https://github.com/CyanogenMod/android_device_samsung_galaxysmtd/commits/cm-11.0

If you have an alternate repo to suggest, let me know
[Android Software Development] sythe179:
Can you please support HTC desire 300.

If you need a build.prop for device info I can supply it.

Probably easier if you msg me.
[Android Software Development] Phil3759:
Update 6.15.6 and 6.15.7

All devices from one variant use the same recovery image

credits to CM team for this crazy job
[Android Software Development] mholloway:
Nice, thank you.every time I try to down load d2lte the mdsum is 8e2a. ......etc

But the download file the mdsum is d2. ....etc....or something.but if my download is corrupted would the mdsum be the same 3 times in a row?

EDIT : download md sum is correct now.
[Android Software Development] Mike B.:
No trouble at all here downloading, installing and using the latest d2lte (6.15.7). The "unified" approach makes life much easier for all. Nice job!
[Android Software Development] mholloway:
With this recovery can I flash aosp roms with out removing the asserts? I have the s3 for boost mobile.
[Android Software Development] HippoMan:
P51xx?

Is the 6.15.4 release for the Galaxy Tab 2 10.1 (P51xx) scheduled for upload any time soon? If not, could it be added to your list of future uploads?

No rush or pressure, because 6.12.8 is still working fine on my P5110.

Thank you very much.

.​
[Android Software Development] hypnz:
Phil u did great job! Until now no slow restores!
[Android Software Development] chraso:
Hey Phil, thanks for making this.

I want to port it to my Samsung Galaxy 5(gt-i5500).

Its an armv6-ldpi phone.

Tried to compile your recovery and it did. I suppose.

Here is the recovery.img

It currently doesn't works properly bcos of the init.gti5500board.rc. But I will rename & repack it.

Can u please add your resource, so I can test it first.

http://d-h.st/bhb
[Android Software Development] Phil3759:
I need full github device tree under cm-11.0
[Android Software Development] chraso:
Its not supported officially.

But the identical device Samsung Galaxy Ace aka cooper is.

This device uses modified to run for ldpi androidarmv6 sources.

https://github.com/androidarmv6/android_device_samsung_galaxy5/tree/cm-11.0

And thanks for supporting too many devices.
[Android Software Development] Bhargav97:
Thank you very much Phil3759,

Hope you would add the Galaxy 5 to your supported Device list. If you need any more info on this device or any help on this device, you can always ask me here or in the device-specific thread.

Even there is a huge community specially devoted to this device here:-

http://www.madteam.co

If you need any developer's help for this device, you can visit this forum.

Thanks chraso for initiating the request for this recovery and your work.

I am a big fan of philz recovery and wanna see this in my galaxy5. :)
[Android Software Development] Phil3759:
what are those :

ifdef BUILD_WITH_30X_KERNEL
[Android Software Development] Bhargav97:
Sorry for late reply. Our phone has been running on 2.6.35 kernel, maybe that's why.

I would strongly suggest you that you contact this person:- psyke83

Here is his xda profile:-

http://xdaforums.com/member.php?u=3877378

He is not any ordinary/casual developer. He's is the one who has kept this device alive. This device got CM7, CM9, CM10, CM10.1, CM10.2, CM11, Regular updated CWM and...a long list. He's the one who can tell you each and every small thing about this device.

I will explain him the scenario right now and you can then ask him if you get stuck at anything related to this device.

You can even contact him at MADTEAM (the link I gave in previous reply).

EDIT: Here's the mountpoints fixed recovery.img by chraso...he compiled just now & was busy so I posted it, just in case if you want to see. [TESTED BY ME, ALL WORKING EXCEPT GUI OPTIONS AND TOUCH]

http://d-h.st/y4b

Thanks...
[Android Software Development] HippoMan:
Long backup bundle names truncated.

I'm running on a handheld device with a narrow screen, and when I try to do a Restore or a Delete of a backup, the long names of the backup bundles extend past the right side of my screen and get truncated, and I sometimes can't tell which one is which.

Is it possible for us to have one or more of the following new capabilities?

1. The ability to scroll the long file names horizontally?

2. The ability to override the generated name for a given backup bundle at the time of backup?

3. The ability to change the default template used for generating backup bundle names?

... or am I missing an already existing feature which can help me see the full backup names?

Thank you very much in advance.

.​
[Android Software Development] Phil3759:
1 and 2: not for now

3: read first page and edit needed build.prop entries
[Android Software Development] HippoMan:
Ah! I guess you're talking about this:

nandroid backup path auto-renamed with current ROM id from build.prop (ro.modversion, then ro.romversion, then ro.build.display.id)

However, right now, the format of the backup bundles looks like the following on my device, without "ro.romversion" nor "ro.build.display.id". In my build.props, "ro.romversion" isn't even set, although "ro.build.display.id" does indeed appear in my build.props.

YYYY-MM-DD.HH.MM.SS_[ro.modversion]

I'd like to see it this way: [ro.modversion]_YYYY-MM-DD.HH.MM.SS

I guess I'm out of luck. Oh well. I can manage by renaming the backup files via "adb shell" or by using "Root Explorer" after rebooting.

Thank you for your help and explanations.

.​