yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Unjustified Dev:
I have my own but okay no direct link but its in here already unpacked its under stock

https://github.com/Romswitchers/Romswitcher-codina-common

I was thinking since I completely changed the init and USB things it wouldn't work
[Android Software Development] CNexus:
Awesome, already done, updated, and relinked to your dev host :thumbup::thumbup:
[Android Software Development] :
Master [MENTION=4666971]Phil3759[/MENTION],

Probably this is my last question in this thread Sir. So please don't be angry. In our port of your recovery, I got the touch working. Now only thing left is backup & restore of boot.img & recovery.img.

I am attaching two images and so can you please tell me which partition are for boot & recovery. I am also attaching my recovery.fstab in the post to check that and I think we can also get this fully working for us.

I hope this time I am not bothering you or disturbing you in your precious work. Thanks a ton for your awesome work Master, Will be waiting for your reply.
[Android Software Development] Unjustified Dev:
It clearly tells you if its correct use dd to dump the boot.IMG if you have the boot.img you can get more info from fstab.device . Weird partitions if you ask me btw your rooted use root browser and copy your fstab and recovery fstab to sdcard

Get cat proc/partitions

Sent from my _______ . You fill in the blank
[Android Software Development] Phil3759:
Please, do not call me master, just phil :)

Your device is Mediatek (MTK) ?

Look here:

https://github.com/ameer1234567890/...To-Gather-Information-About-Partition-Layouts

Currently, cwm sources do not support MTK "partitions"

I could look at it but won't be before end of the year or if a dev owning the device ports it

Look at TWRP code as they added MTK support

Not a big deal, but needs some time and testing. Without the device, it is a pain in the ass
[Android Software Development] Phil3759:
New ported devices threads:

- HTC One V (primou) - credits to [MENTION=5258154]doga.ozkaraca[/MENTION] for providing sources

- i9001 - Galaxy S Plus (ariesve) - thanks to [MENTION=4825267]alireza7991[/MENTION]

- i9082 - Galaxy Grand Duos - credits [MENTION=4532929]chotu222[/MENTION]

- N7100 Sprint (t0ltespr) - Unofficial repack by [MENTION=4645794]CNexus[/MENTION]

- Xperia Z (yuga)

- Acsend P1 U9200 (viva) - credits to [MENTION=5423065]kiprap[/MENTION]
[Android Software Development] :
Thanks for your replies Master. Why I call you masters cause when it comes to Java/ Programming or C++ then I am a complete noob only So in this respect I call you Masters.

Frankly Speaking, MTK itself is weird in terms of modding it. But here is the info I got from fstab of my boot.img

# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK

/emmc@android /system ext4 ro,noatime wait
/emmc@cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc wait
/emmc@usrdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc wait,encryptable=footer

Now if you think its useful then do let me know and if not then just tell which file you need I can provide it as soon as possible.

So Sir, Can I add like this for boot & recovery in recovery.fstab

/boot emmc /dev/block/mmcblk0
/recovery emmc /dev/block/mmcblk0

Will this work or it will damage anything.

Yesterday I ported Cannibal Open Touch Recovery with my working recovery files and recovery fstab files. And So got the touch working in my Philz recovery port also.
[Android Software Development] Phil3759:
I doubt it would work

You can try it though

Just test the backup feature to see if it works. Do not try restore obviously and no damage would occur

But I expect it will fail

Please, take your time and read through TWRP sources for MTK support
[Android Software Development] :
Masters,

I think your information are guiding me towards success. Now using that line I mentioned , I didn't got any error. But it stuck on backing up boot.img.

I am attaching my Ported Recovery in this post will you have a look on that in you spare time. No hurry. But I told you Sir, I am very much noob in understanding these thing and I think so, just a guess, that it will not kill your max time to check this and remedy it as its only a recovery fstab file to correct. Please don't be angry Sir. I know I already given you alot of trouble so please pardon me if it is like that.

Thanks for suggesting these things and now I think I will back to life soon with a working philz recovery on Micromax A110 also.
[Android Software Development] Phil3759:
No need that I look at it

Read the MTK part of the article I linked a few posts above

You have an MTK device and boot+recovery partitions cannot be read the usual way

There is no possibility to fix this until I or someone else adds MTK support to CWM sources
[Android Software Development] Phil3759:
New device:

- Galaxy Exhibit - SGH-T599N (codinamtr) - credits to [MENTION=4911249]Unjustified Dev[/MENTION]
[Android Software Development] Unjustified Dev:
I can't stay out of recovery now lol . Thanks for your hard work.
[Android Software Development] Phil3759:
I uploaded new neon and non neon aroma file manager 1.91

It fixes touch better now and no more hangs on changing theme. Big thanks [MENTION=402300]amarullz[/MENTION]

http://d-h.st/users/philz_touch/?fld_id=20650#files

I also uploaded latest sources to v5.15.0

https://github.com/PhilZ-cwm6/philz_touch_cwm6/commits/cm-10.2

Enjoy and try to port to other devices the open source version and let me know
[Android Software Development] Phil3759:
Updated i9100/n7000 to v5.15.0

I also restored the bootloop workaround for these by swapping init binary
[Android Software Development] praderj:
Brother.. mine is an mt device.. and I tried both the neon and non neon versions of your recovery v1.90 and 1,91.. both are not working brother... but the v1.80 is working fine..
[Android Software Development] dhinesh77:
thanks for reply. i have builded recovery from sources mentioned in this thread.. here I am attaching the device tree and my recent build of philz recovery .. waiting for full features , thanks in advance .

device tree : http://www.mediafire.com/download/hp2cc9opxqwasp6/device.tar.gz

recent build of recovery from above source : http://www.mediafire.com/download/xy9tquq1na612h0/philzrecovery.img
[Android Software Development] monyozt:
yeah,, waiting for note 3 recovery by philz
[Android Software Development] Phil3759:
What device it is and from where you forked?

Use github please so that I can easily check sources. Do not provide tar releases this way
[Android Software Development] Rittik:
My friend Somcom3x introduced me to this amazing invention By You. So thanks for this at first.

I have now bought a new device recently the Samsung Galaxy Mega 5.8(GT-i9152)(code-crater) I have compiled the original stock CWM with a graphic.c from galaxy grand(everyrthing same with Mega except screen resolution) but there is graphics glitches everywhere which make it impossible to use. The grand uses a WVGA graphic.c and My mega uses a qHD graphic.c. I would like to ask for a bit help here. Can someone here provide me some knowledge about what should I change so that the graphical glitches stop occuring. Would like a help ASAP

Thanks all.
[Android Software Development] monkteo:
man what happened ? I just installed the last version and I can't start the recovery anymore !

how much time I must press the 3 buttons to start philz ?
[Android Software Development] FlemishDroid:
Hold volume up + power + home button until you see the samsung s3 logo. So you have to push and hold them some time.
[Android Software Development] starbucks2010:
No need to press the Home button, only Power and Vol Up.
[Android Software Development] dhinesh77:
Sorry for providing sources in tar format .. here is one from github

https://github.com/TeamNinjaLive/a57_device_folder_for_cwm

device: Micromax A57
[Android Software Development] Ryuinferno:
That is a weird device tree...you would want to put all the .mk files in the top directory...refer to this: https://github.com/CyanogenMod/android_device_samsung_i9100g

If there are extra files to be copied to the final ROM, use the PRODUCT_COPY_FILES flag instead of doing it manually...
[Android Software Development] Phil3759:
I'll look at it

By the way, I put an img file for i9100g at root of dev host for your usual repacking. It is a cm-10.1 kernel repack
[Android Software Development] icoolguy1995:
But we have CWM build from source by [MENTION=4309448]varun.chitre15[/MENTION]
[Android Software Development] Ryuinferno:
It's basically a cm-10.1 boot.img right? Thanks btw...:)
[Android Software Development] Phil3759:
Yes, exactly
[Android Software Development] dhinesh77:
Thanks
[Android Software Development] Phil3759:
sources?

Working backup of boot and recovery partitions?
[Android Software Development] icoolguy1995:
I have given you device tree way before and dont know about source will ask him
[Android Software Development] icoolguy1995:
Here is the source build recovery of MTK and this recovery i have ported to my mobile.

http://xdaforums.com/showthread.php?t=2393986
[Android Software Development] praderj:
Me too ported this and its working fine in my mt device.. [MENTION=5186178]carliv[/MENTION] made a lot of modification to make it work in mt devices...
[Android Software Development] Phil3759:
Thank you a lot

I probably missed your post

I forked his repo and will try to merge the changes

Will probably spare me hours of work

Will look at this later
[Android Software Development] cantenna:
Best recovery! Its the only recovery I trust! Thank you!
[Android Software Development] tuannghia1985:
Phil3759: Please i messed up with Nand erase all in Odin 3.

My phone is SHV-E250S

My phone is able to flash rom but doesn't recognize the internal memory card.

In "My files" i can't create any folder. Camera got message "Memory full" ...

Also in "My files/sdcard0/" i can't see any folder (also EFS folder).

I wonder it's partition error on my phone. I tried CWM Philz recovery/advanced/ partition internal sdcard/ then it said: can't partition non vfat volume.

So does my phone corrupted internal SDcard? or partition?

If i need PIT file, then where could i obtain that?

Please help me. I really need my Note 2 - Korea (SHV-E250S) back.
[Android Software Development] Unjustified Dev:
[MENTION=4666971]Phil3759[/MENTION]

Used cwm builder to create some dummy source then added in device specifics

https://github.com/Team-Exhibit/android_device_philz_codina-common
[Android Software Development] shoey63:
[MENTION=4666971]Phil3759[/MENTION]

Check PM :)
[Android Software Development] Phil3759:
Saw it. Thank you a lot. Will let you through pm

Are usb problems fixed?
[Android Software Development] Qwerty__-:
Really nice recovery, maybe the best !

Thanks a lot.
[Android Software Development] Fishawy:
+1,000,000 :good: :)
[Android Software Development] lalec:
I recommend searching your device specific forum for those answers. It is really a good idea to already have a working kernel, ROM and recovery ready to save you before you start messing around in recovery. Many Samsung devices can be resuscitated with Odin but you should research carefully before you do anything else. Good luck.
[Android Software Development] Phil3759:
Sure

I am slowing down on devices support to start working on v5

I ask first people to build from source for their device

After that, we can look at a port

Once v5 done, porting to other devices will be first on my todo list
[Android Software Development] hatememarkz:
Can u support us gs2 guys
[Android Software Development] DorkyDev:
What's that Multiboot screenshot all about? Now ya really got my hopes up!!!
[Android Software Development] assassinoid:
Thanks buddy, keep it up
[Android Software Development] Phil3759:
New version

http://xdaforums.com/showthread.php?t=2254530
[Android Software Development] pilotn:
Philz,

Do you think is possible to get your recovery for Asus transformer tf101?
[Android Software Development] Ibiza101:
Hi Philz, where i can download the Last version of your kernel for my 9100? I check the other topic but it is stock to 4.93.6

***Inviato dal mio fagiolo magico***
[Android Software Development] NFleck:
Any chance this is compatible with the lg p930 (nitro hd), or possible to get a port?

We're quite popular still and are officially supported by CM10.1 and several devs. I think it would be worth while, and I would absolutely love to try this out. Looks amazing.

Sorry if this has been asked. On my phone and too lazy to do a search :o
[Android Software Development] Phil3759:
Ask one of your devs to compile open source project and then get in touch with me with a feedback
[Android Software Development] ttibbetts83:
What would you need to add this to cm10.1 for n7000
[Android Software Development] Phil3759:
Sorry, no plans. cm kernels update nightly, it is a no end user request. Dad n7000/i9100 don't have a dedicated recovery partition for that

However, they can use this recovery mod, ;)
[Android Software Development] Phil3759:
PhilZ Touch v5.00.4

Brings mainly a completely revised and more portable touch code

A true scrolling touch GUI

A lot of fixes and optimizations

Change log
[Android Software Development] eRPeeX:
Nice
[Android Software Development] Kung-Fu-Tse:
nice color + work :highfive:

question:

PhilZ Touch v5.x: can we test it or download somewhere?
[Android Software Development] Phil3759:
List of currently supported devices in OP

These will be updated in the next hours/days
[Android Software Development] Choristav:
So I tried installing v5 on my i9300 (using v4.93.6) and an error showed up:

"script aborted: assert failed: getprop("or.product.device") == i9300"

|| getprop("ro.build.product") == "i9300"

assert failed: getprop(r.product.device") == "i9300" || getprop("ro.build.product") == "i9300".

E: error in /sdcard/philz_touch_5.00.5-i9300.zip (status 7)

Installation aborted
[Android Software Development] eRPeeX:
Take a look at the S3 thread. I used mobile Odin to avoid this error. It works.

On the other S3 I used Odin.

New version isn't a problem
[Android Software Development] zard:
Looks very nice. Will be trying the N7105 version shortly. It looks like the tilapia is not one of the supported device. Will it be supported in the near future?
[Android Software Development] wsdyleon:
can someone add multi-languages to this recovery?(theme methods also are okay)
[Android Software Development] Phil3759:
The source is there

It is possible, but needs a lot of work obviously. Personally, I have no time for that

But, the open source part is there for anyone interested

I will add in the future some basic theme saving options, that's it for me

I prefer to focus on functions, now that GUI is ok
[Android Software Development] Unjustified Dev:
It should be working now I removed the incorrect usb id . It worked regardless but it broke the adb on the rom itself . Also external sdcard is not working have not yet figured it out. :) I'll repack it again today. Reboot to recovery still isn't working regardless of the recovery if you have any input on this issue I am all ears.
[Android Software Development] Phil3759:
My god, hope you know what you were doing!!

1 - is your device a /data/media phone? If no, then what's this?

/sdcard datamedia /dev/null

2 - Do you have a dedicated recovery partition or it is sharing same with boot as I see recovery.rc file?

In that case, int.rc is for your ROM and should remain stock, thus your ROM adb breaking issue

3- If you do not own /data/media, you were mixing it all: below code needed and your fstab as in 1 is wrong

export SECONDARY_STORAGE /emmc
export EXTERNAL_STORAGE /sdcard

Finally, you cannot mount /data/media as USB storage!

So, I really believe you are mixing it all together
[Android Software Development] Unjustified Dev:
Usb mout doesnt show in cwm but everything else works this is how its suppose to look Im a variant of the s3 mini

you will see all of our stuff the same lol

https://github.com/OliverG96/android_device_samsung_golden-common/blob/cm-10.1/recovery/recovery.rc

but I got data/media from team-win we have same parttions . I can use their source and it works just need my blobs and kernel
[Android Software Development] Phil3759:
Well, still seems a bit confusing

You really have to be sure of the points I told you above

cwm in cm-10.1 sources only recognizes these:

/ external_sd

/emmc

/sdcard

Often, /data/media devices will be /sdcard and /external_sd

Other non /data/media: /emmc (internal) and /sdcard (external)

We can still force in recovery.fstab to /sdcard and /external_sd for non datamedia devices

However, this should be really clarified in your init files and recovery.fstab

Now, if your kernel is somehow only accepting export to the paths you showed, still you need to specify /data/media or not in recovery.fstab

You'll also have to symlink storage paths to recovery mount points if really needed

The int rc files for recovery should be clarified too.

Sorry, I do not port from scratch devices I do not own, would take me ages and I have no time at all

I'd advise you port a stock CWM and have all working

Once you move to Advanced CWM mod, open source, you shouldn't have issues if they were fixed in stock CWM

After that, I can compile a full version

Now that I compiled the full version anyway, you could probably fix everything by editing needed parts in ramdisk

Hope this post and previous one give you some light on where are your issues
[Android Software Development] Unjustified Dev:
I will see the issue for me was stupid Samsung didn't specify internal and external in recovery fstab . that mount point was only for external sdcard so data media worked for me but I will test oliver recovery.rc since USB works now.
[Android Software Development] tuannghia1985:
Sir, i do google many times.T_T before i recognize that i really need PIT file a hundreds time.

A Single file about 2,60Kb contain information of Nand.
[Android Software Development] Unjustified Dev:
https://github.com/Team-Exhibit/and...mmit/be58fd6ba4a4cd9e35079c26d168c889dd0e7f2a

Fixed external sdcard .

USB mounting may be wrong probably lun file issue now , but does telling you only mtp works help?

probably should be this

/sys/class/android_usb/android0/f_mass_storage/lun0/file
[Android Software Development] Phil3759:
If phone is datamedia, you cannot mount internal storage on pc
[Android Software Development] Unjustified Dev:
Its OK for me I have my files ready before I go into recovery. Just glad things work now
[Android Software Development] Phil3759:
So, it is completely fixed?

mount usb storage: mounts external sd on pc?

adb shell is ok?

main rom is ok?

If these 3 are ok, then please link me to your released recovery.img so that I can merge it in my next repacks when ever I update recovery
[Android Software Development] Unjustified Dev:
Rom works ok , still issues on my side. Mtp works on rom too.

adb works on rom and recovery

external and internal sdcard mount properly in rom and recovery

So yes it works just as expected. Thanks for everything
[Android Software Development] Phil3759:
Great to hear

Can you post a link to your latest recovery.img repack?
[Android Software Development] Unjustified Dev:
As soon as I get home still in high school :crying:
[Android Software Development] Arinio:
Dear Sir, [Phil3759]

This is to inform you that for the last two days I tried to build an Advanced CWM Mod for Samsung Galaxy Grand Quattro (GT-I8552). However confusion arise in the last two stages i.e. Compressing the files back into the ramdisk and secondly Combining new ramdisk with original kernel to form bootable image.

Regarding the first case some tutorials suggest to go for mkbootfs ramdisk | gzip > ramdisk-new.gz and some other suggest to go for find . | cpio -o -H newc | gzip > ../newramdisk.cpio.gz

Regarding the second issue several tutorials shows different arguments for mkbootimg.

I tried all the possible ways however the resulting image stuck in Nand Write.

I will be ever grateful to you if you please build an Advanced CWM Mod for GT-I8552.

If possible also please guide me regarding the last two stages. By profession I am a Linux System Administrator. Mostly I work in SuSE and RedHat/Fedora.

If you permit then only I will send you the recovery.img and zImage.

Regards
[Android Software Development] CNexus:
Use these tools: http://xdaforums.com/showthread.php?t=2319018
[Android Software Development] Arinio:
Thank You, CNexus. Definately I will try this tomorrow evening.

Regarding arguments of mkbootimg and umkbootimg I am mostly confused. Will you kindly help me there?

Regards
[Android Software Development] Unjustified Dev:
Lol I use those thanks
[Android Software Development] Unjustified Dev:
[MENTION=4666971]Phil3759[/MENTION]

Repacked version

http://goo.im/devs/Unjust/Codinamtr/repacked_philz_touch_5.15.0-codinamtr.zip
[Android Software Development] bartdeli:
Link for HTC One X version not working. Can anyone post mirror?

Wysłane z mojego HTC One X za pomocą Tapatalk 4
[Android Software Development] FireWall123:
Dev-host is having some issues , it seems...

So be patient :)

Vocaloid fan? Check out this thread!

http://xdaforums.com/showthread.php?t=2376692
[Android Software Development] Phil3759:
I only use exact cm command lines

You see them at end of script

Just remove the hide command from the core makefile to see the exact syntax

Stock kernels should be repacked with their own cmdline though. Just change it

You can provide sources and stock recent recovery.img files here
[Android Software Development] Arinio:
My earnest thanks and regards to you.

As from yesterday night dev-host is taking too long to respond as soon as it will be ok I will send you those two files i.e. zImage and recovery.img.

However please note that at the time of umkbootimg the output.txt shows 'The Warning' -- sure you understand. So in this case please suggest me what to upload? Should I upload the file ramdisk.cpio.gz?
[Android Software Development] Phil3759:
I need

Device tree, phone name, bootable_recovery with your changes to add support for your phone and stock SAMSUNG recovery.img

All in one post
[Android Software Development] icoolguy1995:
Any update of recovery on mediatek?
[Android Software Development] Arinio:
Dear Sir,

I will be able to fulfill all your needful information and files except the bootable_recovery as I am still unable to create the image file.

Please do not get annoyed for my failure.

Today after returning from office I will read about Device tree and definitely after studying I will be able to inform you.

Last Saturday I tried to lend books regarding android from the Kolkata British Council however I am unfortunate enough to find any basic books. As myself not a developer but an admin I am searching basic android books to start with. Often I thought to ask you many questions regarding android os, but they are so silly you will simply laugh at. In Kolkata there are several Linux Forums but unfortunately we have no android forums here where we can meet and discuss, most of us are busy playing games or chatting/networking. I am fortunate enough to find you in this forum and yesterday whole night I gone through your works, untar your 9505 CWM and studied (within my limited scope) how you added extra commands to support external sd-card, create an ascii image, keep the koush.png file (Mr. Kaushik Dutta is also a Bengali like myself), created some new type mount point (I am unable to understand those) and many more.

Take all my respect.
[Android Software Development] dragon36:
Verizon Galaxy S3

Here is a repack from the d2tmo for the Verizon Galaxy S3 (d2vzw)

https://db.tt/FRLOZF8s
[Android Software Development] Phil3759:
5.15.9 (26.09.2013)

Not all devices are updated

These were mainly added to fix touch on Xperia Z

Other touch fixes are probably not a main issue for most