yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Android Development] timberwolf60:
Phil, I can't attached the log file in xda premium and tapatalk. So I uploaded to mediafire. Just the log for boot and recovery. http://www.mediafire.com/view/7w193o0k75bvfx8/recovery.log

When I used chenglu cwm to flash this recovery and my sd card was dismounted on the first boot up after completed the backup. But 2nd reboot was ok.

*********

This afternoon I done a custom backup on efs. Here is the log.txt: http://db.tt/NvKRTvBf

Send via i9505 using XDA premium,

ROM: cf auto rooted ME2. CWM

superSU 1.30

---------- Post added at 10:55 PM ---------- Previous post was at 10:40 PM ----------

I used 5.04.7 and BACKUP to ny 64gb exFAT without problem. Now going to test this soon.

Send via i9505 using XDA premium,

ROM: cf auto rooted ME2. CWM

superSU 1.30

---------- Post added at 11:10 PM ---------- Previous post was at 10:55 PM ----------

Used sgs4 flasher to flash the latest: the log file is what you want: http://db.tt/Xq93VqVM

Phil 1st reboot after the latest backup on boot and recovery, my sd card wad dismounted. Reboot on the 2nd time solved.

Send via i9505 using XDA premium,

ROM: cf auto rooted ME2. CWM

superSU 1.30
[Galaxy S 4 i9505 Android Development] Phil3759:
Thank you a lot

I see well what's happening

It stops at the last step, when trying to backup .android_secure

Since it cannot mount /external_sd/.android_secure because your exfat card is not recognized, it throws an error and stops

This reveals a bug where people without an external sdcard inserted will fail to complete backup

I will fix it

Also, I will make a repack to enable your exfat hopefully
[Galaxy S 4 i9505 Android Development] Phil3759:
by sdcard you mean external exfat sd?
[Galaxy S 4 i9505 Android Development] cbeckstein:
same here --- happened already at least twice (once after I switched from /data/media to /data/media/0 in the recovery and again after switching back and upon an other reboot from Philz):

first time after a reboot of Philz v5.04.8, the external 64GB exFAT Sd card is dismounted and reported as being damaged ---

Androids offer to format denied, reboot and everything is fine again...
[Galaxy S 4 i9505 Android Development] timberwolf60:
It happen on external sd card.

Send via i9505 using XDA premium,

ROM: cf auto rooted ME2. CWM

superSU 1.30
[Galaxy S 4 i9505 Android Development] Phil3759:
Ok, wait for next update

It will fix issue with some big exfat cards and also the bug when backup errors on devices with a second storage, but not inserted/recognized

This device is really special and unusual. It is taking a while to implement all
[Galaxy S 4 i9505 Android Development] Marchintosh:
is there the app SuperSu integrated?
[Galaxy S 4 i9505 Android Development] joshua.justice:
Will this CWM work on the T-Mobile variant?
[Galaxy S 4 i9505 Android Development] Phil3759:
superuser from Koush is integrated

I am building this upong tmo/can tree, as no tree for i9505 exists in cm-10.1

Despite they are same hardware and same fstab table, i9505 seems much more tricky. We had to, thanks to Chenglu, mod the graphics.c and most importantly the ext4 formatting support

It seems, tmo/can versions do not need that.

You can try it and see if it works:

- graphics could be broken

- formatting cache could corrupt it like it happened here on start

I plan to support these other 2 US variants, but later, once done with this one. Hopefully, I am compiling the good one now
[Galaxy S 4 i9505 Android Development] daniello8:
Will this recovery support NTFS and/or FAT32 formatted ExtSD for backup&restore?
[Galaxy S 4 i9505 Android Development] Phil3759:
Can you attach the updater-script file from that zip?
[Galaxy S 4 i9505 Android Development] Obagleyfreer:
In the latest versions of this recovery I'm getting error 7 when flashing PAC ROM. If I change back to earlier PhilZ recovery It flashes the same ROM .ZIP fine......any ideas?
[Galaxy S 4 i9505 Android Development] hawkerpaul:
Certainly Phil:

ui_print("mounting system");

run_program("/sbin/busybox", "mount", "/system");

ui_print("copying modules");

ui_print("");

package_extract_dir("system", "/system");

ui_print("unmounting system");

ui_print("");

unmount("/system");

ui_print("Flashing Kernel");

ui_print("");

package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");

show_progress(0.100000, 0);

The script stopped at "unmounting system"

I waited for a few minutes at this point.

As soon as I unplugged the USB cable, the script finished correctly.

Cheers
[Galaxy S 4 i9505 Android Development] adrenalin100:
Please help dear dev .I make a custom backup efs on ex sd card .

The ex-sd card (exfat format) dont see file efs backup ,but recovery good work, ok complete .In backup folder old date 1970-01-05 .Please .What's the problem? .

Wipes i make .
[Galaxy S 4 i9505 Android Development] Phil3759:
Can you try this

ui_print("mounting system");
run_program("/sbin/busybox", "mount", "/system");
ui_print("copying modules");
ui_print("");
package_extract_dir("system", "/system");

ui_print("unmounting system");
ui_print("");
run_program("/sbin/busybox", "umount", "/system");

ui_print("Flashing Kernel");
ui_print("");

package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
show_progress(0.100000, 0);
[Galaxy S 4 i9505 Android Development] starbucks2010:
I got the same behavior when flashing the SuperSu zip file. It seems that the USB connection keep the system partition mounted and the script cannot unmount it.

Best regards.
[Galaxy S 4 i9505 Android Development] hawkerpaul:
Same thing mate.

hangs at "unmounting system"

Disconnected USB and it resumed immediately
[Galaxy S 4 i9505 Android Development] Phil3759:
I will look at it

Thank you
[Galaxy S 4 i9505 Android Development] cdzo72:
Damn... When I updated to 6.08.7 the time glitch came back... same on 6.09.2... went back to 6.07.9 where I was before glitch and it was still there. .. guess I have to flash abyss right guys?
[Galaxy S 4 i9505 Android Development] rorogio:
is it possible to install this recovery with odin on a non-rooted 4.3 device? ( the one with knox ticking)

____

yes it is

KNOX WARRANTY VOID: 0X1
[Galaxy S 4 i9505 Android Development] Tanis64:
Flashing any Custom Recovery or Kernel will trigger the KNOX Warranty Void Flag, that's nothing new.

Send from the outback with my GT-I9505
[Galaxy S 4 i9505 Android Development] hawkerpaul:
Just a thought Phil.

To avoid people on this thread possibly installing the wrong recovery onto their device, wouldn't it be better to update the link in the op to

i9505 (jfltexx)

http://goo.im/devs/philz_touch/CWM_Advanced_Edition/jfltexx
[Galaxy S 4 i9505 Android Development] GlossGhost:
It wouldn't let them install it if it's not for jfltexx.

But yeah it would be good.
[Galaxy S 4 i9505 Android Development] Phil3759:
The zip version has assert check, no risks

If they use odin, they are on their own. They could flash a bitmap that way!

Now, if I change the link for this, I would need to do the same for near 100 threads :p

Sorry, users need to be responsible. I already made my best to lower risks. On each thread, the device code is clearly mentioned in bold red
[Galaxy S 4 i9505 Android Development] Phil3759:
6.09.6 (15.01.2014)

This version should be able to flash older update zip packages

No more need to manually swap update-binary. It will do it for you
[Galaxy S 4 i9505 Android Development] Phil3759:
Well, in that situation there is no other fix than editing updater-script, so worst than before

I will try to see if cm team agree to do deeper modifications to fix that

Currently, the swap is to avoid the error 7.
[Galaxy S 4 i9505 Android Development] Milamber:
Will the latest recovery work with CM 11? i.e Kitkat?
[Galaxy S 4 i9505 Android Development] Formhault:
Yes.
[Galaxy S 4 i9505 Android Development] MetaIIica:
yes, you will have no problem with the latest recovery and kitkat

Post send with PAC Rom 4.4 Alpha-1 Black Power Edition
[Galaxy S 4 i9505 Android Development] simonbigwave:
delete
[Galaxy S 4 i9505 Android Development] aeroman:
Same error here with Danvdh 4.4.2 Rom and v6.09.6. ;)

Strange older v6.09.2 works fine with all Versions of Danvdh Rom?!

With v6.09.6 the backup time has lengthened.

Regards

●tapatalked GT-I9505●
[Galaxy S 4 i9505 Android Development] Phil3759:
This is the new format required:

exp:

format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "0", "/system");
[Galaxy S 4 i9505 Android Development] Phil3759:
I could not reproduce it

system partition mounts/unmounts without issues from adb shell while usb connected
[Galaxy S 4 i9505 Android Development] hawkerpaul:
Perhaps it has something to do with booting into recovery via the power menu (as opposed to a power-down) then flashing when connected to usb throughout the process?

I'll test some scripts by powering down first.

EDIT:

Well, that didnt make any difference.

Tested by flashing KT's brand new GE kernel (just released this last hour)

Hung on "unmounting system" and as soon as I disconnected the USB, it proceeded with the remainder of the script. (I'm on 6.09.02 by the way due to the format command issues in updater-scripts)
[Galaxy S 4 i9505 Android Development] jin_kazama™:
thanks a lot
[Galaxy S 4 i9505 Android Development] aeroman:
Hi mate,

you mean its not Recovery related, we need edit the updater Script? :)

(same zip works with v6.9.2, but not with v6.9.6)

Best Regards

●tapatalked GT-I9505●
[Galaxy S 4 i9505 Android Development] sachs:
Error 7 here installing TW 4.4.2 leak FNA5
[Galaxy S 4 i9505 Android Development] franzyroy:
Me, I've got an issue, the 6.09.6, it was impossible to launch it when I was on Echoe KitKat v2.2, I returned on the 6.09.2 which worked fine.
[Galaxy S 4 i9505 Android Development] Phil3759:
Post the zip you are installing and exact steps you do so that I can try to reproduce it
[Galaxy S 4 i9505 Android Development] hawkerpaul:
I was installing KT's latest GE kernel.

http://ktoonsez.jonathanjsimon.com/sgs4/TWGE/KT-SGS4-KK4.4-TWGE-INTL-01.17.2014.zip

Running 4.4.2 GE rom (danvdh)

Usb connected.

Power menu

Reboot, recovery

Install zip from sdcard1

Flash above zip

Gets as far as unmounting system then hangs indefinitely.

Disconnect usb and script proceeds immediately with "flashing kernel" then completes.
[Galaxy S 4 i9505 Android Development] Phil3759:
In fact

I could reproduce it

Will look at it
[Galaxy S 4 i9505 Android Development] franzyroy:
Anyone has got this problem?

Now that I has another rom (ProBAM), I gonna test again the 6.09.6 to see.
[Galaxy S 4 i9505 Android Development] hawkerpaul:
Not seen a changelog for 6.10 yet Phil, but I just flashed KT kernel again with USB connected, and it worked without hanging.

:good:
[Galaxy S 4 i9505 Android Development] Phil3759:
I resync sources to new adbd commits

Are you really sure it is fixed?
[Galaxy S 4 i9505 Android Development] HC4Life:
I'm on last version 6.10.0 and i tried to flash the last Echoe rom v14 and gives me an error Status 7 and operation failed.
[Galaxy S 4 i9505 Android Development] hawkerpaul:
not at a pc to connect to usb to test now sorry mate. I'll give it some more flash tests asap phil.
[Galaxy S 4 i9505 Android Development] hawkerpaul:
You're right Phil.

Flashed twice today, and hung at the "unmounting system" message twice.

Not sure how it worked yesterday.
[Galaxy S 4 i9505 Android Development] adrianyujs:
Mine I9505, but I cannot find it.... I only can find I9500 only... I means recovery..
[Galaxy S 4 i9505 Android Development] thejihell:
+1 : No I9505 file in repository at the moment
[Galaxy S 4 i9505 Android Development] MVKA:
No problems here.

The OP says...

Download links

Last version can be found here:

Quote:

i9505 (jfltexx)

http://goo.im/devs/philz_touch/CWM_Advanced_Edition

And when you click I9505 section (jfltexx) yes that's your phone product name you will find this.

http://goo.im/devs/philz_touch/CWM_Advanced_Edition/jfltexx

-MVKA
[Galaxy S 4 i9505 Android Development] aeroman:
Status error 7 has already been fixed in the latest version?

Regards

●tapatalked GT-I9505●
[Galaxy S 4 i9505 Android Development] cdzo72:
That's not for PhilZ to fix but for the ROM developer to update his update binary and update script... correct me if I'm wrong guys
[Galaxy S 4 i9505 Android Development] Phil3759:
The assert error 7 is fixed

But on some installers, updater-script would still need to be fixed
[Galaxy S 4 i9505 Android Development] franzyroy:
6.10.0 works fine. Perhaps, I've an issue with Echoe KK v2.2.
[Galaxy S 4 i9505 Android Development] kar5ten:
I dont know why but i cant update my recovery. Im on 6.04.5.

Odin or over recovery

So I get the Status 7 if i try to update dandv's Rom.

In Stein gemeißelt mit meinem I9505G
[Galaxy S 4 i9505 Android Development] Formhault:
So... Why can't you flash / update to the latest PhilZ recovery?
[Galaxy S 4 i9505 Android Development] kar5ten:
I tried to install the latest Version. Then i Reboot and then it's always the 6.04.5.

6.0.7/6.09/6.1 nothing changed.

Today i flashed Stock 4.3. Rooted it + installed 6.1. Rebooted and it Shows me the Same. So everytime i try to install New dandv's Rom its Status 7.

In Stein gemeißelt mit meinem I9505G
[Galaxy S 4 i9505 Android Development] Bejda:
The strange thing is that I can't find any i9505 6.04.5 version on the ancient download link:

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

At first I thought you were confusing CWM base version which is 6.0.4.6 at the moment and Philz version number that you can check in recovery under Philz settings>about..not the case?

Try to type the exact number version you want to mention please,as you can see it can leads to some confusion ;)

Plus error 7 is something recent if I can say so I guess at first sight that (unless you're using a version from late August/early September which shouldn't be something like 6.04.* anyway) you're using one of the two latest version.
[Galaxy S 4 i9505 Android Development] kar5ten:
Hm..

Yes that With philz and cwm that was maybe my fail.

But however friday i couldnt update (-about was the Same) maybe i destroyed something , cause sometimes i couldnt Boot into recovery. But now it's working. And help for Status 7 ? Found nothing what helped me here

In Stein gemeißelt mit meinem I9505G
[Galaxy S 4 i9505 Android Development] gzax:
Hello I installed latest version and i got a strange issue. I cant get time to show the correct hour and minutes. Even if i install previus version i have the same thing. Any clues about it?

Thank you.
[Galaxy S 4 i9505 Android Development] poyda69:
Where do i find the GT-I9505 files? I went to the Download link but can only see I9500 and it is not the latest version?????
[Galaxy S 4 i9505 Android Development] Phil3759:
you just triggered the thread title change :crying:
[Galaxy S 4 i9505 Android Development] poyda69:
Is this a :good: or a Bad thing????

If it is a Bad thing "Sorry".

If it is a Good thing :victory:
[Galaxy S 4 i9505 Android Development] CarlM34:
LOL.......:D
[Galaxy S 4 i9505 Android Development] Phil3759:
Update 6.10.3

Merges necessary changes to fix adb push to extra storage path

About /system unmount when usb cable is plugged during package install: I identified the cm-11.0 commit that broke it.

I informed repo maintainers about it. Hope it will get fixed soon, else I revert the offending commit until they fix it
[Galaxy S 4 i9505 Android Development] poyda69:
I ill can't work out where to get the GT-I9505 files?????

Can anyone point me to them?

Thanks in advance. :good::good:
[Galaxy S 4 i9505 Android Development] Lucius1972:
Click the link in the op to get to the download side and search for "jfltexx"
[Galaxy S 4 i9505 Android Development] Phil3759:
Update 6.10.4

This adresses 2 issues:

- random hangs on boot

- fix unmount /system commands during install of some zip files when USB cable is connected

Please confirm asap if these are fixed now
[Galaxy S 4 i9505 Android Development] poyda69:
i go to the Download page this is what i get, i cant see a link for I9505????:confused:
[Galaxy S 4 i9505 Android Development] hnernes:
Please tell me u are joking. He told you to look for "jfltexx" (wich is the name for our phones) and not I9505.
[Galaxy S 4 i9505 Android Development] Phil3759:
Maybe someone answer my request instead of these amazing dev discussions :p
[Galaxy S 4 i9505 Android Development] poyda69:
Sorry :silly: I didn't realize this is what was meant. I feel so :silly::silly:

Thanks for your help.
[Galaxy S 4 i9505 Android Development] hawkerpaul:
I've tried the offending script several times on this version with the USB attached, and it worked perfectly. No more hangs!

Thank you for all your hard work Phil. Very much appreciated.

:good:
[Galaxy S 4 i9505 Android Development] Phil3759:
This is just incredible

I have no clue why the bug at all

It was the performance mode during intsall of zip

Why the hell it was causing trouble I have no idea

Anyway, it was useless and I ditched it.

Will commit to gerrit to see if someone figures it out
[Galaxy S 4 i9505 Android Development] bubba949:
After updating my clock is showing the correct time now also. Thanks for the hard work Phil3759.
[Galaxy S 4 i9505 Android Development] HaTrED_:
What about backup /restore speeds and the error 7?

Sent from my S4, another Galaxy!
[Galaxy S 4 i9505 Android Development] KenHua:
I have just made a comparison of the backup speed for the following three versions:

(Backup size ~1.4 GB; Fast compression yield ~40%; same settings for all; ran in the following sequence)

6.10.4 : 10m52s

6.07.9 : 7m11s

5.18.9 : 2m57s

I'm back to version 5.18.9, which is my benchmark. Thanks Philz for the continued effort.
[Galaxy S 4 i9505 Android Development] Formhault:
Phil... I think you triggered the thread title change in vain :). You might change it to "limax edition" just as well... people wouldn't read anyway.
[Galaxy S 4 i9505 Android Development] phileasx:
Thank you Philz,

I've updated from 6.08.9. so far so good.

I didn't hit into any boot up hang with 6.08.9 either.
[Galaxy S 4 i9505 Android Development] chavdar:
Backup is very slow

I also can confirm, that there are no longer random hang ups on boot. But the backup speed has decreased dramatically.

I made a 5 GB backup (resulting in 3,2 GB with Medium compression) and it took 42 min with 6.10.4

The same Backup was almost twice as fast with 6.08.x ( cant remember the exact version)
[Galaxy S 4 i9505 Android Development] Phil3759:
This is really boring

Nothing changed normally. Need more confirmations
[Galaxy S 4 i9505 Android Development] Formhault:
Hey Phil...

Until this whole 1-hour-long backup thing gets sorted out... what do you think about the implementation of some sort of script in the recovery so that when the backup procedure is done, the phone automatically boots into the ROM and resumes normal operation?

That would be useful for the people that perform backups regularly... "Backup to SDcard", go to sleep, and when they wake up, their phone is up & running... without requiring their input after the completion (manually reboot from recovery), you know...

Also, an option in the recovery to verify backups would be nice (unless it's there already :silly:), so you know it's okay to restore - so you don't risk getting a "MD5 mismatch, full wipe, start over, screw you haha" message (if that's still even a thing nowadays... it's been almost a year since I last performed a backup, so... :D).

These are just my thoughts. In the end, it's up to you. I'm good with suggestions, awful with implementations, so please don't throw rocks at me :angel:.
[Galaxy S 4 i9505 Android Development] Dr.No.pt:
When updating CM11 latest nightly in recovery on top of last one ( erase cache and dalvik 1st then update ) and have to reboot it hangs in i9505 forever. Have to power off ( 10 sec ) and then start.
[Galaxy S 4 i9505 Android Development] chavdar:
I am doing a new backup and will post the results later.

Maybe also a couple of other users can post there results

Edit: Here the resutls

Backup time: 51:19 min

Backup size: 3118,61 MB

Compression: 35,01%
[Galaxy S 4 i9505 Android Development] sarbe:
The automatic boot after backup is already there mate.
[Galaxy S 4 i9505 Android Development] BillGoss:
If you run a script from the phone to do the backup (as I do) then you get the result you are looking for.

Here's the code I use:

#

# backup the current system using CWM

#

extc=/cache/recovery/extendedcommand

bud=/storage/sdcard1

echo > $extc

echo backup_rom\( \"$bud/clockworkmod/backup/`date +"%Y-%m-%d.%H.%M.%S"`_`getprop ro.modversion`\"\)\; >> $extc

reboot recovery

Sent from my GT-I9505
[Galaxy S 4 i9505 Android Development] phil.o:
Where? Which option do I have to enable? :confused:

°°° tapatalked °°°
[Galaxy S 4 i9505 Android Development] Phil3759:
Nice one

Browse and discover all settings

Never use a recovery before you did

This turns me mad

Anyway: Custom jobs
[Galaxy S 4 i9505 Android Development] sarbe:
See picture. Custom backup, reboot when done. Sorry for the blurry pic.
[Galaxy S 4 i9505 Android Development] Phil3759:
If you use custom backup, you have the option

In default backup mode, you cannot set it. The reason seems obvious to me

Else, use a script like above by [MENTION=2911853]BillGoss[/MENTION] or ors like with goomanager: backups started with scripts will always auto-reboot
[Galaxy S 4 i9505 Android Development] Formhault:
Silly silly me. Sorry :D

---------- Post added at 01:46 AM ---------- Previous post was at 01:45 AM ----------

That's a script to automate the backup procedure every X period of time? :confused:

And... how do you run it? Type it in Terminal or perhaps use a software to run them... it's probably the second one, haha.
[Galaxy S 4 i9505 Android Development] BillGoss:
You're on your own with scheduling a task. Have a look at Tasker.

Yes, run the script from Terminal. Use su else you won't have permission to write to /cache

Sent from my GT-I9505
[Galaxy S 4 i9505 Android Development] simonbigwave:
jus wanna confirm installed latest 6.10.4 on Samsung test Firmware FNA5. all ok so far and no boot hang up or whatever no problem. did a Backup, not long time took about 35mins. thanks PhilZ.
[Galaxy S 4 i9505 Android Development] störte:
I flashed today the latest philz on my i9505 and then as well a new Rom. I had it now a few times that i was stuck on reboot. I am not sure if this comes from the rom or the new recovery.
[Galaxy S 4 i9505 Android Development] aHcVolle:
Version: 6.10.4

don't know how it was before but:

No compression to fat32 extsdcard (1.4GB): 5:15

Medium compression to fat32 extsdcard (924MB): 15:00

i don't know about the earlier versions as i always use no compression and the 5min seem to be the same as before.

had do 3 reboots to get into recovery, don't know why it didn't want to boot (was haning in galaxy s4 logo)
[Galaxy S 4 i9505 Android Development] Phil3759:
ROM Manager fix

I ended up adding a workaround to fix ROM Manager backup to external storage until Koush fixes his app

Next update will have it
[Galaxy S 4 i9505 Android Development] Phil3759:
Update v6.10.6 - CWM 6.0.4.7
[Galaxy S 4 i9505 Android Development] SoLoR1:
6.10.6 breaks wifi on leaked na5... anyone with same problem? Reverted back to 6.10.4 and wifi is back...
[Galaxy S 4 i9505 Android Development] Bradden1:
Latest version works well for me... 7772mb backup in 28mins - no compression.
[Galaxy S 4 i9505 Android Development] shingers5:
Problem I am having is it won't flash any 4.4.2 ROMs at all. Been using twrp 2.6.3.1 but I always have used this recovery on all my Samsungs. Even using on XZU now but on here it just errors out. I was on stock 4.2.2 before flashing recovery
[Galaxy S 4 i9505 Android Development] shoey63:
You must be on a 4.3 or above kernel base to flash kitkat. (Irrespective of recovery)
[Galaxy S 4 i9505 Android Development] Formhault:
Nevermind. :D
[Galaxy S 4 i9505 Android Development] Phil3759:
Read FAQ

Update to latest version

No, because we have separate recovery partition

What matters is the kernel bundled with recovery image
[Galaxy S 4 i9505 Android Development] simonbigwave:
I jus flashed 6.10.6 on FNA5 also. wifi is fine. even after reboot.. so far so good.