yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Android Development] patrickbartalesi22:
I just went on clokworkmod.com/rommanager and under galaxy s4 i9505 recovery 6.0.3.2 has been released.

---------- Post added at 10:57 PM ---------- Previous post was at 10:42 PM ----------

Flashed rom status 7 errors still appear.

---------- Post added at 11:13 PM ---------- Previous post was at 10:57 PM ----------

Flashed rom and received status 7 error. Installed gapps and booted phone rom boots no errors or bugs. The cwm must be reporting an error when there is no error, very interesting.
[Galaxy S 4 i9505 Android Development] zencooler:
OK. It's alive again! :)
[Galaxy S 4 i9505 Android Development] Schrotty35:
Official cwm is out.
[Galaxy S 4 i9505 Android Development] Phil3759:
These info should go in general section please.

This mod is official cwm + tons of things in addition include exfat
[Galaxy S 4 i9505 Android Development] el_kwas:
Thanks Phil3759 for gr8 recovery :D "Thanks button" hited. And recovery? I'm on Yours now :)
[Galaxy S 4 i9505 Android Development] realslicedbread:
Phil im trying to use your latest (5.06) recovery to flash the cm10.1 official nightlies onto my jfltexx/i9505 phone. Because there are problems with consistently flashing the rom without hiccups, the cm10.1 maintainer invisiblek asked me to get some logs.

if the flash fails, it is usually a Status 7 error, however we can't replicate the exact conditions of when it may occur

I have tried connecting the phone to adb whilst in recovery and forcing the phone to give real-time logs (adb shell cat /proc/kmsg > kmsg.log and adb shell tail -f /tmp/recovery.log > recovery.log)

however whenever the phone is connected to USB/ADB, the flash is quite reliable and never fails.

the only times I have gotten it to status 7 fail is always when the phone is not connected to the computer. However once the fail happens I cant get the logs (adb wont connect) until a reboot, and once I reboot the logs are usually lost.

I have 2 logs i did manage to pull after a failed flash and reboot.

Is there anywhere I can send them for you to look at?
[Galaxy S 4 i9505 Android Development] Phil3759:
These issues were probably related to binary-update and format command in script as I showed it with victorator early cm-10.1 ports

i9505 inernational version needs a special ext4 formatting using new tools. These exist in PhilZ Touch, thanks to Chenglu

Sadly, without a phone and enough advanced users/devs to debug it, I cannot help. It could be a faulty script from ROM dev or early cm-10.1 nightlies still missing it like when we started early cwm ports

Maybe it was fixed in latest cm sources and I need to sync it...

Many possibilities, and I have no time actually to start blindly debugging it without a phone

You'll have to wait for more reports and some advanced users to play with it, have custom ROMs and send me helpful info to look at it

Meanwhile, try to remove any format command from zip script and format using cwm instead before flashing. It would probably fix your issue

After that, report it to ROM dev
[Galaxy S 4 i9505 Android Development] realslicedbread:
OK thanks I'll pass this on.
[Galaxy S 4 i9505 Android Development] Phil3759:
Well, i am reading that the new stock cwm is corrupting /cache when formatting it.

So, seems the issue is still related to that and they did not implement a proper fix

Again, without a device to test, it is only speculation based on users reports
[Galaxy S 4 i9505 Android Development] egendomligt:
Is there any way of making a "custom" backup in dup-format?

I'd like to only backup /data, but in dup-format, to external sd..
[Galaxy S 4 i9505 Android Development] Phil3759:
Currently no and I do not plan to support it

dup format is a big mistake in my opinion. The number of files is so huge that it kills boot process in many cases because of its slowness

It even slows down camera on many phones
[Galaxy S 4 i9505 Android Development] egendomligt:
Interesting. But I like the idea of not storing a lot of duplicate files. Wouldn't it be possible to store all these files in an uncompressed tar or image-file to get around the system being nosy? Would take some work ofc. but I'm just throwing stuff out there now :)

In any case, I was wondering how all the generating of md5-sums affects the performance of the backup process? I guess I could just do a few backups and compare myself..
[Galaxy S 4 i9505 Android Development] andymihail:
Full wipe question

I am currently on I9505XXUAMDM, stock rom, stock recovery, stock kernel, rooted using CF-autoroot.

If I flash PhilZ Touch CWM, will I be able to full wipe (Data, System, cache, dalvik Cache) without problems?

I am considering flashing Omega v5.0 and it seem that before that I must do a full wipe first, then flash stock XXUBMEA....

Thank you in advance.
[Galaxy S 4 i9505 Android Development] Kameeeleon:
Just about to install my first custom ROM from this recovery...

Had a Sensation before this and used many custom ROMs but this phone is different in that it has this "internal SD" card that pictures, downloads, etc. are saved onto automatically. Will a wipe-for-flashing through this delete that too, so will I have to move everything I want to keep off it first? (including the ROM!)

On a tangential note the internal SD - is it a hard partition of the internal memory? If I'm installing a much lighter ROM than TouchWiz should I be looking to repartition so I have more available on the internal SD side? I've tried searching about this but not found anything.
[Galaxy S 4 i9505 Android Development] Phil3759:
Wipe before install a new ROM will not delete sdcard content

For other questions, search for /data/media story
[Galaxy S 4 i9505 Android Development] Phil3759:
Anyone can download this:

http://www.hotfile.com/dl/225799876/c76d4e9/I9505XXUBMEA_I9505OXABMEA_DBT.zip.html

And attach recovery.img from it so that I can see if we can have exfat modules working in cwm ramdisk instead of loading them from current ROM?
[Galaxy S 4 i9505 Android Development] kantjer:
This is the recovery.img from I9505XXUAME2_I9505OXXAMDB_I9505XXUAME2_HOME (already had that one on disk)
[Galaxy S 4 i9505 Android Development] Tassos_i:
Here it is (the one you asked XXUBMEA) :

View attachment recovery.zip
[Galaxy S 4 i9505 Android Development] Phil3759:
Thanks, will repack asap
[Galaxy S 4 i9505 Android Development] kantjer:
Sorry selected the wrong file from disk. I see it's already uploaded.
[Galaxy S 4 i9505 Android Development] Phil3759:
np

Forgot that I need these:

/system/lib/modules/exfat_core.ko
/system/lib/modules/exfat_fs.ko

They must come from the same ROM, XXUBMEA else it will fail

You can grab them from your phone if you have that ROM installed. Else, you can unpack the system.img.ext4 if you know how
[Galaxy S 4 i9505 Android Development] kantjer:
Pulled these from my Omega v5.0 XXUBMEA ROM ;)
[Galaxy S 4 i9505 Android Development] hanspampel:
Maybe im wrong, but the file are in wanams kernel too. If i exctract him i see the files in /libs/modules too. They have the same filesize. So i think thats the same files.;)
[Galaxy S 4 i9505 Android Development] Phil3759:
file size doesn't mean anything. binary compare them
[Galaxy S 4 i9505 Android Development] Phil3759:
5.06.6 (13.06.2013)

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

Note: I migrated to new jfltexx device tree. Let me know if graphics are again broken

Also, exfat 64Gb users, let me know if it works or not for you
[Galaxy S 4 i9505 Android Development] marouane80:
tested right now, there is a touchscreen bug on the GUI

need to be fixed. i'm back to the previous version

good work, thanx
[Galaxy S 4 i9505 Android Development] janjan:
Yes black screen and touchscreen bug on the GUI. Thanks
[Galaxy S 4 i9505 Android Development] Tassos_i:
+1

(NB : there's also a little risk as I tried to "install zip" and the recovery asked If I wanted a full wipe ...)
[Galaxy S 4 i9505 Android Development] Phil3759:
Please test the new version:

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

Same 5.06.6, but it is recompiled to fix graphics

Report about 64Gb exfat cards please
[Galaxy S 4 i9505 Android Development] emx_o:
just flashed new recovery. What should I test? I own a 64GB exFAT
[Galaxy S 4 i9505 Android Development] Phil3759:
Try to install zip from external sd. Just browsing, no need to actually install the zip
[Galaxy S 4 i9505 Android Development] emx_o:
I can browse without any problems, but I think that wasn't a problem before, too?! I'll try to flash the latest CM nightly, thats where the problems started usually. After error 7 my external SD was not mountable from recovery
[Galaxy S 4 i9505 Android Development] Phil3759:
Flashing cm nightlies is not a recovery bug, it is probably an issue with binary-update and format command

From what I read, official cwm for i9505 still fails to format /cache like early releases of this recovery

You have to remove format commands from the updater-script and format partition in recovery to avoid that issue

About exfat: this version uses exfat modules in ramdisk. Previously, it was in /system from ROM. Since cm ROM formats /system and doesn't support exfat, you loose exfat access. The issue is that cm will never support exfat.

With this last version, I use the newest exfat modules/kernel combo from Samsung and they are in ramdisk. That is, even without a ROM support, it can load exfat modules

Hope this will work for all exfat sdcards of 64Gb and medium quality

The fact it works for you is a good sign that it is finally done
[Galaxy S 4 i9505 Android Development] emx_o:
that finally makes sense! if I want to use my SD with CM or any AOSP rom I have to format it to fat32?.. uaghhh
[Galaxy S 4 i9505 Android Development] Phil3759:
Yes, they do not recognise exfat

Microsoft licensing issue...
[Galaxy S 4 i9505 Android Development] emx_o:
dont know if it matters, but I did the complete new ROM wipe thingy, installed AOKP without the format lines from external SD afterwards and everyting went well 1st try
[Galaxy S 4 i9505 Android Development] Phil3759:
Great

I will assume this one is a winner, for exfat 64Gb cards

I will wait also for more reports from people that always had issues on previous early with exfat modules in cwm
[Galaxy S 4 i9505 Android Development] I9000bramgmail:
No, you could though, however formatting it ext4 will give you far better performance than fat32 or exfat. Ext4 is a native linux filesystem, exfat modules might be working but it's far from native speed, I have my 64gb micro sd in ext4 now, transfer speed is gone up quite nicely :)

p.s. if you use a ext4 card you can still just use it with a windows PC if connected trough the S4 (;
[Galaxy S 4 i9505 Android Development] Phil3759:
Only through MTP probably

USB mount storage as a real drive won't work
[Galaxy S 4 i9505 Android Development] emx_o:
I would be perfectly fine with MTP :) Didn't know that ext4 is possible too! But how do I format the SD without cardreader? There must be a function in recovery I didn't see, right? :D
[Galaxy S 4 i9505 Android Development] Phil3759:
for now, you cannot format external sd to a specific file system type in cwm

It will keep current file system
[Galaxy S 4 i9505 Android Development] janjan:
The grafic bug is fine with new version. But still unable to browse any zip from external sd. thanks

Edit. I am using 32 gb
[Galaxy S 4 i9505 Android Development] mitky82:
I periodic loose recovery. I dont know how, but i have 3-4 times and without flash anything today i reboot to recovery and i cant go there, just dont have recovery. With buttons, with program, with 3 way reboot... just gone and that was not first time. Need to flash again with s4 flasher to work
[Galaxy S 4 i9505 Android Development] SunSide:
I read about that problem too. Some people have big problems to boot in recovery.When they try the phone just do a normal reboot.No matter how they try.

I don't know if this is especially with PhiZ recovery,i think not.

But it's a strange problem :-/
[Galaxy S 4 i9505 Android Development] Phil3759:
If I remember you also had issues with bigger exFAT cards

Did you test if this version works for you?
[Galaxy S 4 i9505 Android Development] SunSide:
Hmm...i think you remember wrong.I never had such a sd card,not on S3 and not on S4.Only a 32GB card,thats enough for me.

If i would have one then i would have tried :)
[Galaxy S 4 i9505 Android Development] yvliew:
I try flashing this CWM recovery in odin. I says successful. But I still don't have custom recovery. What did I do wrong??

I'm on I9505XXUAMDM
[Galaxy S 4 i9505 Android Development] Mr.AFK:
Look at /system /etc for a file called: install-recovery.sh or something like that.

This caused that the stock 3e recovery every boot overwrite your cwm.

With root, you can delete this file and flash the cwm again.

Gesendet mit meinem S IV
[Galaxy S 4 i9505 Android Development] Tassos_i:
(Sorry for this late report)

5.06.6 "sees" external Sandisk 64GB exfat. However, with my configuration, a nandroid backup took :

12.2 minutes, under 5.06.0

20.3 minutes, under 5.06.6, which is considerably slower

Is this just me ?
[Galaxy S 4 i9505 Android Development] ken2802:
np
[Galaxy S 4 i9505 Android Development] SunSide:
Tried it too,could not boot in the recovery.

Was fighting with adb the evening that it works,so here is another log.
[Galaxy S 4 i9505 Android Development] leeomendes:
so good to see you here! I am happy to help you in anyway you need :)
[Galaxy S 4 i9505 Android Development] Phil3759:
Another repack/compile to fix graphics

http://d-h.st/users/philz_touch/?fld_id=16685#files
[Galaxy S 4 i9505 Android Development] Tassos_i:
HI Phil,

Trying to flash from chenglu's 6.0.2.3-3 your repack gives :

assert failed: write_raw_image("/tmp/recovery.img","/dev/block/platfprm/msm_sdc.1/by-name.recovery")

E:Error in /sdcard/Download/philz_touch_5.03.3-i9505-2.zip

(Status 7)

Installation aborted
[Galaxy S 4 i9505 Android Development] Phil3759:
Could be it needs a different write method to partition (extract_file)

Anyway, I will upload the tar.md5 and look at the zip later
[Galaxy S 4 i9505 Android Development] Phil3759:
done uploading the tar
[Galaxy S 4 i9505 Android Development] Beefheart:
Now works fine when flashed with Odin.
[Galaxy S 4 i9505 Android Development] Phil3759:
Great

Any bugs?

exfat, usb mount, touch, brightness setting?
[Galaxy S 4 i9505 Android Development] leeomendes:
Everytime it start on recovery a message says "E: Can't open /cache/recovery/log" "E: Can't open /cache/recovery/last_log"

@@EDIT

*my mistake*
[Galaxy S 4 i9505 Android Development] Phil3759:
Try to go under mounts and storage and mount /cache if unmounted

Will fix later if that's the issue

Aroma: you have to install the aromafm.zip in dedicated folder
[Galaxy S 4 i9505 Android Development] Beefheart:
Seems to be fine mate. I had a mess around with the GUI settings (increased line size to make touch easier) and turned off vibration and it saved the settings on recovery reboot. It also flashed Adams Kernel with no issue.
[Galaxy S 4 i9505 Android Development] leeomendes:
I can't see any change on brightness mode, at least I can say only one thing: the BEST recovery I ever saw! so friendly, nice-looking and full of functions! THANK YOU!
[Galaxy S 4 i9505 Android Development] Phil3759:
Great news, finally

I will look tomorrow to merge Chenglu fix for time/date or use the fix from stock boot.img

You also have /cache warning?
[Galaxy S 4 i9505 Android Development] Beefheart:
No cache warning for me.
[Galaxy S 4 i9505 Android Development] Phil3759:
Ok

Thank you really

You made my night

Gonna take a rest now

See you tomorrow for some more fixes to any reported bugs
[Galaxy S 4 i9505 Android Development] btemtd:
I have flashed this WOW... Beautiful work Phill... Loooks really nice!!...

Before I flashed it I saw someone say they had a status 7 error, so before I tried to flash it I opened the updater script and I changed the location to /dev/block/mmcblk0p21

instead of:

/dev/block/platform/msm_sdc.1/by-name/recovery

then I Flashed fine with no problem

I am now backing up and it seems to be working , I am 1/4 the way through a backup...

Phil, Is it possible to make a backup format Zip? So that everything is backedup into a Zip file which is Recovery flashable?

Edit: I might like to add that when I flashed it , it said Failed to find partition size /recovery and same for /boot then said Error opening /external_sd/.android_secure

Then it continued on to start the backup...

EDIT:

Oh wait what does Clone rom to ZIP do .... Does this save all DATA, SYSTEM settings, Personal Data & EVERYTHING else to a > Zip file??
[Galaxy S 4 i9505 Android Development] Beefheart:
Have to say it's a lovely looking recovery. :good:
[Galaxy S 4 i9505 Android Development] Tassos_i:
As with chenglu's, on my I9505 (stock MDM), I notice :

No external SD-exfat 64 support "Can't mount /external_sd/"

No internal SD usb mount support (here, external SD, ok)

+ extreme touch sensitivity
[Galaxy S 4 i9505 Android Development] leeomendes:
you can configure touch sensitivity if i am not wrong...

@@Philz

it says "error mounting /cache"

+ wipe data result in reboot.
[Galaxy S 4 i9505 Android Development] Phil3759:
We have a winner

With usb connected it is slower. Or maybe you have more data. But nothing changed except exfat modules
[Galaxy S 4 i9505 Android Development] Tassos_i:
Usb not connected (off course)

Backups taken sequentially (just before and after flashing new version).

I'll try again and let you know
[Galaxy S 4 i9505 Android Development] I9000bramgmail:
no unfortunately you'll have to format it with a pc i'm afraid.. with a cardreader it's a simple process of just a few minutes
[Galaxy S 4 i9505 Android Development] Tassos_i:
I confirm my previous findings : After 2 new backups under 5.06.6 and 1 new backup under 5.06.0, all of them on my SanDisk 64 exfat, usb not connected, identical data, it comes out that, for nandroid backups, 5.06.0 is twice as fast as 5.06.6.
[Galaxy S 4 i9505 Android Development] Phil3759:
Well, it could be related to exfat modules and exfat card

I propose this: for people having slow exfat cards issue: stick to 5.06.0

For others, I recommend 5.06.6

That's all I can do for now, until we have a new ROM with better exfat modules

In any case, I assume it is a good thing as at least we have a fully working recovery no more relying on exfat modules from ROM (so not working whenever you flash a CM/AOKP rom)
[Galaxy S 4 i9505 Android Development] Tassos_i:
Just to notice that my sd card is really very fast...

Phil, I'm more than ok with 5.6.0 and I want to thank you once again for your continued efforts to improve your unique "recovery universe"!
[Galaxy S 4 i9505 Android Development] Phil3759:
What ROM are you on please?

Can you attach your exfat modules here (/system/lib)
[Galaxy S 4 i9505 Android Development] daibaron:
Hi,

In my previous post in this thread I was explaining that after a full wipe initiated within Android (not recovery) my phone restarted in recovery mode with a bar loading for ever.

1 st I thought that was a part of recovery process then I realize I was stuck in this screen.

I did full wipe in recovery mode and it only take less than 10 sec.

Someone can confirm this is an issue ?

As I said before the recovery from backup went well.
[Galaxy S 4 i9505 Android Development] Tassos_i:
I'm on stock odexed XXUBMEA.

Here are the 2 exfat files you asked plus a 3rd one "system/lib/libexfat_utils.so", in case you need it :

View attachment 2042077
[Galaxy S 4 i9505 Android Development] Cygnust:
Hi guys,

are backup from TWRP compatible with this recovery ?

Many thanks

[edit]

nevermind, found the options in backup/restore :)
[Galaxy S 4 i9505 Android Development] okawunga:
I ve tried new version philz_touch_5.06.6-i9505.zip

and it says cant mount my external sd card

reverted back to philz_touch_5.06.0-i9505.zip and all is fine

I am on ME2 with omega

Kingston 64gb card exfat
[Galaxy S 4 i9505 Android Development] Phil3759:
Well, means these are meant to be in /system...

Maybe i will revert to shared moduled after all, until Samsung decides to change their mind and put them in ramdisk
[Galaxy S 4 i9505 Android Development] kieeps:
did some searching but couldnt find anyone with my problem, first i thought it had nothing to do with the recovery since this all happened after installing FolderMount but i'm not sure anymore.

Did a post here to explain: http://xdaforums.com/showthread.php?t=2323599

but now when i check the log i see this:

mount: mounting /dev/block/mmcblk1p1 on /external_sd failed: Invalid argument

Any ideas?

I attached the entire log aswell.

EDIT: the problem appeared about 3-4 versions ago i think and now i'm on the latest release as of today
[Galaxy S 4 i9505 Android Development] Phil3759:
Can you try to go into recovery and using adb shell or Aroma console:

Please do this in 5.06.6

mount -t exfat /external_sd

And report if it does mount your external sd?

Anyone having issues to mount 64Gb exfat on new version while previous one works, please test this
[Galaxy S 4 i9505 Android Development] starkilling:
Just installed 5.06.6 for the i9505. I have one problem with it: it won't restore backups. It just hangs at checking hashsums. I've left it for more than 10 minutes, never gets past that. Any ideas?
[Galaxy S 4 i9505 Android Development] Phil3759:
where is the backup? external or internal sd?

If external, what is your sdcard format/size? (exfat 64Gb?)

md5 check can take a long time when processing many Gb of data anyway, so you must be very patient or disable md5 in settings
[Galaxy S 4 i9505 Android Development] starkilling:
external, 32GB fat32

I'll disable it in settings, thanks a lot for the fast response.
[Galaxy S 4 i9505 Android Development] Phil3759:
np,

Probably the time needed to read through all data on external storage. This is a slow operation and will probably take near same time as the whole restore

If you are sure you have a non corrupted backup, just disable md5 check
[Galaxy S 4 i9505 Android Development] aldreiaan:
Hi, where can i find the nandroid backup I made bacause I want to transfer it to my desktop. My clockworkmod folder is empty. Im using the latest version. Thanks
[Galaxy S 4 i9505 Android Development] hanspampel:
Use the search mate. I was posted soooo many times here.:silly:
[Galaxy S 4 i9505 Android Development] zafu:
Hi,

After (wrongly) using the Cyanogenmod updater my phone now bypasses

philz recovery home screen and proceeds directly to updating the ROM. As

the update fails and the phone is then stuck to the samsung logo I can

no longer access philz recovery to flash another rom.

How can I reboot to recovery without executing the update script?

Thanks,
[Galaxy S 4 i9505 Android Development] joelvn:
First of, great job on the recovery. Everything works fine for me besides one little thing. Sometimes when I restore a backup it takes over 30 minutes to finish. While other times it just takes 2 minutes. Any idea why this is?
[Galaxy S 4 i9505 Android Development] iamnotkurtcobain:
Connected to charger/usb?

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Android Development] *SanSiro*:
Use Root Explorer.

Go to:

/data/media/clockworkmod/backup

:cool:
[Galaxy S 4 i9505 Android Development] Phil3759:
Or set it to /data/media/0 in Advanced menu
[Galaxy S 4 i9505 Android Development] joelvn:
No, not connected to charger nor usb. It just randomly happens that it takes so long.
[Galaxy S 4 i9505 Android Development] leeomendes:
Same here, my backup/restore always take around 37 minutes :S
[Galaxy S 4 i9505 Android Development] *SanSiro*:
Hmm, strange....

Never happend to me so far with this recovery.

What Rom were you restoring?
[Galaxy S 4 i9505 Android Development] Phil3759:
People having slow backups all have 64Gb exfat?

Please post if you have 64Gb exfat to sayif it is:

- slow

- normal

(giving time and size stats shown at end of process is important please to avoid subjective estimations)

Many thanks
[Galaxy S 4 i9505 Android Development] dekker86:
I have 32gb and made a Backup with 3.7gb need estimated 15min.