• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Philz touch recovery

OK I took some time and I build the recovery for or device this is the last version 6.55 if someone want to test

Here http://www.4shared.com/zip/Htei56zKba/recoveryphilztouch2.html

To install just download to SD or your PC if is in your PC put the zip in your SD and flash with recovery you need cwm or twrp to flash OK guys let me know

Here a video how it look MOD: CWM - PhilZ Advanced Edition: http://youtu.be/xUcFeOp0pK0

If you like this hit thanks

sorry i forget to give credit

credit go to:

for their source thanks guys lol
 
AS far as I can tell this file will NOT work on the T599 variants from MetroPCS and T-Mobile. The meta info assigns the recovery image to partition 21 which is where the cachefs is located on those models. I'm going to try flashing it to partition 19 via Heimdall just to see if it works. What the hell, I'm boot looping already anyway.:smokingsomb:

will advixe...
 
I suspect that none of the CWM based recoveries are going to work at this point for me because I've flashed back to the stock (rooted) T599 rom. Without a matching kernel (boot.img) The whole thing is probably pointless. Any suggestions for a kernel anyone? I'm going to go looking too...:o
 
Hi the zip file is good block 21 in the device is recovery partition so I don't know what you do it so let me know what you do it OK with what you flashing the zip ?
 
OK, Ive been wrestling with my year old Galaxy Exhibit, T599N, that I bought from MetroPCS almost from the start. I've bricked it many times:mad: And somehow it's been resurrected every time:confused:

Recently I discovered a tool on xda called EFS Professional. I like it because it p4rovides me access to a fair portion of both the Samsung tools AND the Qualcomm NV tools. It also dumps the contents of the PIT file several different ways. The most legible output produced follows:

Device Partition List:
----------------------
mbr,gpt /dev/block/mmcblk0p1
mastertoc /dev/block/mmcblk0p2
steboot1 /dev/block/mmcblk0p3
steboot2 /dev/block/mmcblk0p4
dnt /dev/block/mmcblk0p5
reserved /dev/block/mmcblk0p6
cspsafs /dev/block/mmcblk0p7
cspsafs2 /dev/block/mmcblk0p8
efs /dev/block/mmcblk0p9
modemfs /dev/block/mmcblk0p10
modemfs2 /dev/block/mmcblk0p11
fota /dev/block/mmcblk0p12
ipl modem /dev/block/mmcblk0p13
modem /dev/block/mmcblk0p14
loke4 /dev/block/mmcblk0p15
2ndloke4 /dev/block/mmcblk0p16
param /dev/block/mmcblk0p17
kernel /dev/block/mmcblk0p18
kernel2 /dev/block/mmcblk0p19
system /dev/block/mmcblk0p20
cachefs /dev/block/mmcblk0p21
hidden /dev/block/mmcblk0p22
datafs /dev/block/mmcblk0p23


Note that what I was saying is verified here, partition #19 holds the recovery image, and #18 the boot image. NOT 21 and 20 as I have seen in the discussions here. Those are the partition assignments from the I8190 S III Mini. That is the major reason why firmware from that model doesn't work with the T599. Apparently the memory assignments in the build properties are more liberal with the mini as well.

I've gotten around the weird partition differences by using the Heimdall tool. Mostly because I've never gotten Odin to work well for me. The only thing that gives me much trouble is a tar file containing an actual directory copy of a partition contents, as opposed to a partition image file (.img, .ext4. etc...) I'm beginning to wean myself off of Windows 7 in favor of Ubuntu 14, but that's a bit more hassle than I'm prepared for on a daily basis right now...

Anyway that's my two cents worth. I'd like to see this dichotomy explained/vanquished as much as anybody.

cheers
 
riches2rags said:
OK, Ive been wrestling with my year old Galaxy Exhibit, T599N, that I bought from MetroPCS almost from the start. I've bricked it many times:mad: And somehow it's been resurrected every time:confused:

Recently I discovered a tool on xda called EFS Professional. I like it because it p4rovides me access to a fair portion of both the Samsung tools AND the Qualcomm NV tools. It also dumps the contents of the PIT file several different ways. The most legible output produced follows:

Device Partition List:
----------------------
mbr,gpt /dev/block/mmcblk0p1
mastertoc /dev/block/mmcblk0p2
steboot1 /dev/block/mmcblk0p3
steboot2 /dev/block/mmcblk0p4
dnt /dev/block/mmcblk0p5
reserved /dev/block/mmcblk0p6
cspsafs /dev/block/mmcblk0p7
cspsafs2 /dev/block/mmcblk0p8
efs /dev/block/mmcblk0p9
modemfs /dev/block/mmcblk0p10
modemfs2 /dev/block/mmcblk0p11
fota /dev/block/mmcblk0p12
ipl modem /dev/block/mmcblk0p13
modem /dev/block/mmcblk0p14
loke4 /dev/block/mmcblk0p15
2ndloke4 /dev/block/mmcblk0p16
param /dev/block/mmcblk0p17
kernel /dev/block/mmcblk0p18
kernel2 /dev/block/mmcblk0p19
system /dev/block/mmcblk0p20
cachefs /dev/block/mmcblk0p21
hidden /dev/block/mmcblk0p22
datafs /dev/block/mmcblk0p23


Note that what I was saying is verified here, partition #19 holds the recovery image, and #18 the boot image. NOT 21 and 20 as I have seen in the discussions here. Those are the partition assignments from the I8190 S III Mini. That is the major reason why firmware from that model doesn't work with the T599. Apparently the memory assignments in the build properties are more liberal with the mini as well.

I've gotten around the weird partition differences by using the Heimdall tool. Mostly because I've never gotten Odin to work well for me. The only thing that gives me much trouble is a tar file containing an actual directory copy of a partition contents, as opposed to a partition image file (.img, .ext4. etc...) I'm beginning to wean myself off of Windows 7 in favor of Ubuntu 14, but that's a bit more hassle than I'm prepared for on a daily basis right now...

Anyway that's my two cents worth. I'd like to see this dichotomy explained/vanquished as much as anybody.

cheers
Click to expand...

I still don't know what your do it are you sure you have exhibit phone
 
I have it someone else on my other HDD, so give me a moment to look for it and I'll post it if I can locate it. But in the meantime, this should help you:
 
You must log in or register to reply here.
Back
Top Bottom