yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Android Development] Siwandroid:
I have used the lastest version 5.18.2 and i have this error when "Wipe Data/Factory Reset" push on "Clean to install a new rom"

I have this error

-- Wiping data...

Formatting /data...

Formatting /cache...

Formatting /sd-ext...

Formatting /sdcard.android_secure...

Formatting /storage/sdcard1/.android_secure

/storage/sdcard1: Checking

/storage/sdcard1: Mounted

/storage/sdcard1: Idle-Unmounted

Data wipe complete.

--Wiping system...

Formatting system...

--Wiping preload...

E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p27

Now flash a new ROM!

When i try to wipe Wipe Davik cache i have a error:

E:unknow volumefor path [/sd-ext]

EDIT:

When i try to wipe cache partition error:

Wiping preload...

Formatting /preload

E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p27

Now flash a new ROM!

press any key to continue

-- Wiping cache...

Formatting /cache...

Cache wipe complete.

press any key to continue
[Galaxy S 4 i9505 Android Development] Phil3759:
Ignore them all

They are just logging errors on non existing partitions

I will maybe remove preload since it is not used in S4
[Galaxy S 4 i9505 Android Development] Formhault:
It isn't? So Samsung has finally merged /preload into /sysrem?

Sent from hyperspace
[Galaxy S 4 i9505 Android Development] Phil3759:
No, it is just not used and without appropriate Selinux context :cyclops:

Yes, SE again

And you are warned, do not start a SE tech debate again (kidding mode here :D)
[Galaxy S 4 i9505 Android Development] Formhault:
I thought you meant it is not used by Samsung ROMs or others in general. In which case : either /preload has merged with /system (+1 for that) either we got a bunch of free space lying around unused in /preload. Well, sh*t...

Some day, I will know exactly what this SE really consists of and where it is lurking around. Or I will just get a Nexus :)

Sent from hyperspace
[Galaxy S 4 i9505 Android Development] Solark:
[MENTION=4666971]Phil3759[/MENTION]

Thanks you for your great work

I'm using the lastest 5.18.2 version of your recovery.

When I make a full wipe for install a new rom = Clean to install a new rom, Wipe Cache Partition, format data/media, Davik Cache and i install the new rom

But i have a issue when i format the data/media on recovery

If format data/media (Recovery) = Total space in (System manager > Storage) : 9.09 GB (phone)

If i don't format data/media (Recovery) = Total space in (System manager > Storage) : 9.23 GB (phone)

When, i wipe the data/media (Recovery) he stay always at 9,09 GB from the total space on my storage. Until i do that:

I must to reflash a stock rom. Then i must to go back to stock recovery and wipe data/factory reset + cache partition and here only after that i could get back the 9,23 GB

Is that normal?

i should not format data/media so?
[Galaxy S 4 i9505 Android Development] BillGoss:
I can't comment on the space allocation for /data/media.

But I would suggest that you never wipe or format this. The internal storage will happily be used by different ROMs. Think of it as an internal SD card.

Sent from my GT-I9505
[Galaxy S 4 i9505 Android Development] Phil3759:
Recovery, philz touch, will by fefault wipe /data/media/0

Maybe you need to set it in Advanced menu to /data/media
[Galaxy S 4 i9505 Android Development] Solark:
I just checked i can only in Advanced to set it to /data/media/0

And when i set it:

I set to data/media/0 he show me = storage set to /data/media Reboot to apply settings

I set to data/media he show me = storage set to /data/media/0 Reboot to apply settings

Something strange there Philz :(

EDIT: Tried both

Conclusion for me, not format /data/media or /data/media/0

It will remain the internal storage after flashing a new rom to Total space: 9,09 GB instead of 9,23 GB
[Galaxy S 4 i9505 Android Development] :
question

sory if already asked, but how to flash this. i get error flashing in odin and also zip flash from my phone. im on 4.2.2 stock rom not rooted. thanks for info
[Galaxy S 4 i9505 Android Development] Phil3759:
I really don't understand what you mean

When it asks you to reboot, follow what it says!

Also, please write exact menu names you're playing with else I cannot follow or help.

Read the faq to understand what each format menu does on data media devices. I can format /data + datamedia without issues
[Galaxy S 4 i9505 Android Development] Solark:
I will try to be more clear, sorry.

I install your recovery 5.18.2

You said it will by default wipe /data/media/0 ok?

But in Advanced menu, i could only push on "Storage set to /data/media/0" (if it's by default why he should set himself to the same "Storage set to /data/media/0" ?) and he should be "Storage set to /data/media"?

>Philz recovery

>>Advanced menu

(But when i'm there, it show me only i could only "Storage set to /data/media/0" (you told me it's by default) normally it should show me "Storage set to /data/media" and not "Storage set to /data/media/0"

If I set in Advanced menu i push on Storage set to /data/media/0

storage set to /data/media

Reboot to apply settings

He should say:

storage set to /data/media/0

Reboot to apply settings

----

After reboot: (i want make the opposite)

If I set in Advanced menu to I push on Storage set to /data/media

storage set to /data/media/0

Reboot to apply settings

He should say:

storage set to /data/media

Reboot to apply settings

It's like they are reversed or wrong named?

I hope you understand what i mean :(

I readed your FAQ also
[Galaxy S 4 i9505 Android Development] franzyroy:
Flash CF - root auto (one that fits your modele) by ODIN (to root your phone)

Install SGS4 Flasher from the playstore (to install: img - tar - tar.MD5)

Install Philz Recovery in .tar.MD5 here with SGS4 Flasher (put it on your internal SD)
[Galaxy S 4 i9505 Android Development] zencooler:
I am on 5.18.2 version and this is really best one till now. So thank you very much for your hard work Phil.

The only issue is date/time but I will do the trick with kernel to correct RTC.

The backup time for exFAT 64GB class 10 SD is: 18:03 min for 5.03GB of data with settings: show progress (x), hide bar ( ) and no compression

One question: how to change the compression level?

I tried change it in backup settings, but it's still "no".

Is it a bug or I'm just stupid? ;)

Regards!
[Galaxy S 4 i9505 Android Development] Phil3759:
In Backup Format, enable tar.gz. Low setting will speed up things
[Galaxy S 4 i9505 Android Development] zukri90:
The latest build 5.18.2 has trouble mounting /cache.

Is this normal or still WIP?
[Galaxy S 4 i9505 Android Development] Phil3759:
Maybe you corrupted cache on older beta. Format cache in recovery
[Galaxy S 4 i9505 Android Development] aresbv2000:
For the love of God....can someone help me?I had installed i9505XXUEMI8 before trying today to install VanirROM.Before installing this rom I made a backup(including preload partition).So...I didn`t like VanirRom so I wanted to restore my backup.But...surprise....after the I9505 bootsplash the screen goes black and reboot to recovery automatically.Why...and how can I restore my old dear ROM?Thanks in advance to who will help me.
[Galaxy S 4 i9505 Android Development] Phil3759:
Did you enable backup of selinux context? If not, you're in trouble

Alwsys look at settings before using a program
[Galaxy S 4 i9505 Android Development] aresbv2000:
no...I did not....but...after a few tries to restore my backup...i managed to get it restored and boot but...with null IMEI and UNKNOWN baseband.Thank God that I was able to restore my efs back and try to restore the whole rom again.But now the old story...reboot after bootsplash and boot in recovery mode!So...the only solution would be to flash again with ODIN?
[Galaxy S 4 i9505 Android Development] Phil3759:
Probably
[Galaxy S 4 i9505 Android Development] aresbv2000:
ok man...thank you very much!And thank you for your hard work!
[Galaxy S 4 i9505 Android Development] Formhault:
[MENTION=4666971]Phil3759[/MENTION]

So, when backing up a TouchWiz ROM, we must enable backup of SELinux content? Otherwise everything goes haywire? The trouble is only when backing up / restoring, right?

But what about that IMEI issue...?! :eek:

And by the way, [MENTION=1648033]aresbv2000[/MENTION]... How did you backup / restore your EFS?

I know a method out there, but perhaps for the S4, there is a different one I am unaware of.
[Galaxy S 4 i9505 Android Development] donalgodon:
I was just going to ask about this. I am very, very hesitant to flash the 4.3 update, because I don't have a Knox bootloader. Does it modify the EFS structure the way updates on the S3 did? :confused:

If so, that's not cool. I need to be able to flash back and forth between CM and Stock.
[Galaxy S 4 i9505 Android Development] Formhault:
Of course, when ROM cookers will build their ROMs on the official 4.3, they will not include bootloaders and modems. An example is Echoe ROM.

But even so, I still am a bit hesitant to flash any of these 4.3 ROMs. Samsung is scaring the cr@p out of me. I'd rather stick to SlimBean or switch to MIUI... :eek:
[Galaxy S 4 i9505 Android Development] donalgodon:
I'm in the same boat, but I ask because the recovery issue is big, and the SE Linux enforcing status is just one more problem to deal with.

All I really want from the update is the camera firmware update (and I'm waiting for the 4.3 sources to drop as they'll improve CM/AOSP) but these issues will continue to cloud the water for all of us.

I don't have Knox bootloader yet, but there's no way to avoid it and use 4.3 stock.

What are the changes (if any) to EFS and SE Linux status regarding the backups and restores?
[Galaxy S 4 i9505 Android Development] Phil3759:
If you backup efs, it will create a tar and img format

If you restore img, it is a raw dump, so all is saved, be it today or when SElinux v5 ever comes :p

Just ensure you have an img raw backup of efs and avoid flashing new locked bootloaders

I need my phone for dev, so skipping Stock 4.3 until they are fixed for this crap

SElinux is part of linux/redhat and implemented by AOKP ROMs too, so not an issue.

SinceCM team did not patch busybox yet, I implemented a temporary workaround to get you backup/restore on 4.3 where stock CWM fails. The patch is from [MENTION=3084245]Chenglu[/MENTION]

You just have to enable it under Misc Nandroid Settings
[Galaxy S 4 i9505 Android Development] Formhault:
Oh... so that's why we can't restore a backup that has no SELinux content in it... because it's enforced, not permissive, as it is with CM etc.?

Do you really think those will help? I mean look, I flashed VirginROM (GE 4.3) and updated the camera firmware... then returned to SlimBean and it's still rubbish!!!

Well, if you want to be 100% stock, yeah, there isn't.

But if you want a custom ROM that's based on MJ3 (official 4.3), you can use it without flashing a new bootloader. At least that's what I understand from the Echoe ROM thread... :eek:

---------- Post added at 10:30 PM ---------- Previous post was at 10:30 PM ----------

Oh, I forgot. Your recovery can backup & restore EFS partition, right? And it is 100% functional on the I9505, right?

*sorry, I just went panic mode*
[Galaxy S 4 i9505 Android Development] donalgodon:
But, it's not part of the old version of your recovery, is it? I mean, I'm still on 15.8 on my S4, and I've had no problems backing up and restoring with CM ROMs but they are in Permissive mode.

Is that going to be an issue for me if I move to stock which is set to Enforcing default?
[Galaxy S 4 i9505 Android Development] Phil3759:
Yes, you need selinux context enabled for stock 4.3 ROMs
[Galaxy S 4 i9505 Android Development] Phil3759:
Update v5.18.5
[Galaxy S 4 i9505 Android Development] aresbv2000:
I have backup since 2 months ago.On an older touchwiz version.I used Philz recovery to make a efs bacup.In the folder .efs-backup is a efs.img file.copy that file to the root of the sd card and install it via dd comand.using a terminal emulator ,grant su permissions with "su" command and write down this without any quotes "dd if=/sdcard/efs.img of=/dev/block/mmcblk0p10 bs=4096" after reboot you should have the imei back.
[Galaxy S 4 i9505 Android Development] Phil3759:
Why dd?

Just restore efs in img format from my recovery
[Galaxy S 4 i9505 Android Development] aresbv2000:
When I restored my efs backup i didn`t had your recovery installed.And that guy asked me how i did restored my backup.That was the way!Of course it`s possible to restore it using your recovery if you have it installed on your phone.If not...he can use dd comand!
[Galaxy S 4 i9505 Android Development] Andr0id7:
Is it ok not to backup the selinux content on current 4.2.2? Backing it up is needed only on 4.3? Thanks.
[Galaxy S 4 i9505 Android Development] Formhault:
Only on 4.3 TW ROMs. It is not necessary on 4.2 or 4.3 AOSP or GE.

Or... Am I wrong?

Sent from hyperspace
[Galaxy S 4 i9505 Android Development] hawkerpaul:
I dont think you can even set the option if your pre 4.3 (or at least on the old boot loader)

I'm still on MGA, and I can press the option and I get feedback, but it does not get set.
[Galaxy S 4 i9505 Android Development] Tamsy:
Well, you can. I'm still on MGA too (with GE 8.0) and have just made two efs-backups: One with selinux enabled and the other one without it.

I did this just to make sure....
[Galaxy S 4 i9505 Android Development] Formhault:
Well... wait a second... What has EFS got to do with SELinux?!
[Galaxy S 4 i9505 Android Development] Tamsy:
Actually I really do not know. I have read Philz note:

[...]If you backup efs, it will create a tar and img format

If you restore img, it is a raw dump, so all is saved, be it today or when SElinux v5 ever comes

Just ensure you have an img raw backup of efs and avoid flashing new locked bootloaders [...]

I just thought to make two efs-backups: One with the setting "Process SE Context" enabled and the other one without having it enabled.

Don't understand this whole SE Linux, Knox etc. thing anyway so I just wanted to make sure to do the efs backups with both options. Better safe than sorry? Doesn't hurt.

Anyway, enabling the option on the old MGA bootloader obviously works (it is getting set here).
[Galaxy S 4 i9505 Android Development] Formhault:
[MENTION=4666971]Phil3759[/MENTION]? How is EFS related to SELinux and do we really need to backup with and without SELinux? What is the best way that is guaranteed to work?

*panic mode activated, once again*
[Galaxy S 4 i9505 Android Development] ionutzvio:
So, when backing up a TouchWiz ROM, we must enable backup of SELinux content? How do i do that? I use your recovery version 5.15.0
[Galaxy S 4 i9505 Android Development] MMarkkk:
:cowboy: http://oi44.tinypic.com/s4qhyg.jpg

4.3 J5
[Galaxy S 4 i9505 Android Development] ionutzvio:
Sry but i don't understand.
[Galaxy S 4 i9505 Android Development] oMaRcO:
How to backup Efs partition IMG with this recovery?

Verstuurd vanaf mijn GT-I9505 met Tapatalk
[Galaxy S 4 i9505 Android Development] Bejda:
Custom backup and choose only efs partition.
[Galaxy S 4 i9505 Android Development] Formhault:
That should do the trick and make an EFS backup that can be restored at ANY time later on, right?

Sent from hyperspace
[Galaxy S 4 i9505 Android Development] Phil3759:
I added in main thread, to the guide section, use of efs backup restore and selinux context. For more info on things like dd/cat/selinux, google or xda search will answer all your needs
[Galaxy S 4 i9505 Android Development] gzax:
Hello there just a question. Cant find /format sdcard option.

Any ideas?
[Galaxy S 4 i9505 Android Development] Phil3759:
You spotted it, bingo :D

It was removed from CWM

Will restore it

But, if you need you can format whole /data, include data_media by format /data and /data/media menu
[Galaxy S 4 i9505 Android Development] gzax:
Thanks for your fast answer.

Yes I tried that but after reboot was like setup again a new installation of a rom. It should be great if we can have it back again.
[Galaxy S 4 i9505 Android Development] Riskytwin:
Hi Phil, thanks for your hard work. I have a doubt. With 5.14.5 philz: date and time are correct in every nandroid backup. If I install 5.18.5 date and time are wrong. Install again 5.14.5 from within philz recovery and automatically date and time are ok. Why?
[Galaxy S 4 i9505 Android Development] Phil3759:
Good news. So, older version doesn't give you any more bad warnings?

It was using a system set time feature that caused issues on early builds

Maybe ROM or teh like. I plan to revert to set time mode and see if it is ok

Give me a break and it will be done once ;)
[Galaxy S 4 i9505 Android Development] Formhault:
I will be so much more scared when formatting /data for a clean ROM install... "Full wipe for clean ROM install" option will still format everything required for a new ROM install, meaning NO sdcard/s wipes, right?

Yeah, that's probably how it's gonna remain, I guess. But still, *panic mode on*.
[Galaxy S 4 i9505 Android Development] Phil3759:
If you read the features list and the FAQ, all this is answered ;)
[Galaxy S 4 i9505 Android Development] Formhault:
I'm just effing scared when it comes to recovery & such since the whole KNOX thing, that's all :p - even though I'm on the old bootloader. Damn you, Crapsung!
[Galaxy S 4 i9505 Android Development] bluflight:
I'm not sure to post in right place.. But i try to do by myself some script to flash with philz recovery, all works good but i not found number of partition of sdcard..

I explain better.. I need to put in my script one string to delete one folder inside /sdcard/my folder, but i need this:

For example to mount system or data:

mount("ext4", "EMMC", "/dev/block/mmcblk0p16", "/system");

mount("ext4", "EMMC", "/dev/block/mmcblk0p29", "/data");

but i'm not good to found mmcblk0p? number to mount sdcard..

Maybe philz or someone of you can help me with this :)

EDIT: sorry for post, i found now by myself.. For who want to know partition of sdcard is mmcblk1p1
[Galaxy S 4 i9505 Android Development] David78130:
Hi all, I have a message to fix root every time I flash .zip when phone reboot. Apps wich need root works fine even when I don't fix root in recovery.. I'm on mj5 rom. Any idea ?

From my Galaxy S4 tuned with CM10.2/Ktoonsez kernel & Philz touch recovery.
[Galaxy S 4 i9505 Android Development] sswagonman:
Are u on echoes rom?
[Galaxy S 4 i9505 Android Development] David78130:
Right !! I was on cm10.2 but my phone came back from warranty with a f...... mh8 rom and off course I can't restore cm.. :(

Ps: signature changed

From my Galaxy S4 tuned with Echoe slim/Ktoonsez kernel & Philz touch recovery.
[Galaxy S 4 i9505 Android Development] franzyroy:
I also have that, even if I return to the version 5.18.2 which didn't make it before.
[Galaxy S 4 i9505 Android Development] David78130:
Gona try

Edit: it worked fine. Thanks again.

From my Galaxy S4 tuned with Echoe slim/Ktoonsez kernel & Philz touch recovery.
[Galaxy S 4 i9505 Android Development] franzyroy:
What rom have you? Echoe v5?
[Galaxy S 4 i9505 Android Development] David78130:
Yes

From my Galaxy S4 tuned with Echoe slim/Ktoonsez kernel & Philz touch recovery.
[Galaxy S 4 i9505 Android Development] franzyroy:
After some tests, I have found that it is with the TW Echoe v5 and recovery of Philz we have this kind of problem. When I was an official TW and recovery of Philz, I had no problem. When I was a TW Echoe and recovery other than Philz, I had no problem either. I wonder why the Recommended Recovery for the Echoe rom should to be this one of Philz, it works fine with another. Not that I do not like one of Philz, it's great, only there is the problem that I have not met with another. The best will be at two devs to find the reason.
[Galaxy S 4 i9505 Android Development] David78130:
Ok, 5.18.2 works fine so I stay on it for the moment..

From my Galaxy S4 tuned with Echoe slim/Ktoonsez kernel & Philz touch recovery.
[Galaxy S 4 i9505 Android Development] franzyroy:
This is what I did, it doesn't prevent this small problem.
[Galaxy S 4 i9505 Android Development] David78130:
I spoke to fast, after a backup message came again.. :( and .hiddenandroiprogress doesn't work.

From my Galaxy S4 tuned with Echoe slim/Ktoonsez kernel & Philz touch recovery.
[Galaxy S 4 i9505 Android Development] angiotell:
In ODIN, I've to put .md5 file in BOOTLOADER or PDA?
[Galaxy S 4 i9505 Android Development] jonneymendoza:
Downloaded and installed the zip philz_touch_5.18.5-i9505.zip and i am having some major issues with it.

The first issue is that when i do a simple dalvik/cach wipe, it will reboot my device whilst doing it so i dont think it is doing a full wipe for me.

Second issue is installing roms. i tried to install Cyanogeon mod 10.2 stable version, Foxhound 2.0 version and omega v12 rom. All do not work. the Omega and foxhound rom simply crashes and reboots as soon as it attempts to do the installation of the rom
[Galaxy S 4 i9505 Android Development] franzyroy:
The recovery isn't a bootloader!

---------- Post added at 12:18 PM ---------- Previous post was at 12:04 PM ----------

Nobody has encountered this problem?

When we've Philz recovery + Echoe v5 (Maybe also the previous, I don't know), we are in the recovery and we select 'Reboot system now', then it ask to fix the root.
[Galaxy S 4 i9505 Android Development] jonneymendoza:
Please, anyone have any suggestions about the issue i am having with this recovery?
[Galaxy S 4 i9505 Android Development] franzyroy:
Return to 5.18.2! ;)
[Galaxy S 4 i9505 Android Development] jonneymendoza:
You serious?
[Galaxy S 4 i9505 Android Development] franzyroy:
Yeah!
[Galaxy S 4 i9505 Android Development] jonneymendoza:
I will try later when i get home. mac's are useless for rooting devices
[Galaxy S 4 i9505 Android Development] hawkerpaul:
I was wondering if someone can help.

I installed echoe v5 and had problems so reverted back to MGA

I've now have no baseband/imei

I have efs backups through PhilZ and OBackup. (in .gz / .tar format) but I'm unsure how to restore.

I seem to remember there being a backup/restore option in Philz but cant see this any more.

Do I need to flash an old PhilZ version to restore a efs.tar?

If so, which version do I need please?

thanks
[Galaxy S 4 i9505 Android Development] Bejda:
The other way around, custom restore>only efs partition?

But I wonder..what problems did you have on Echoe v5 (network stuffs? You flashed JM5 modem to solve it maybe? ) and I'm not sure at first that something is wrong with your efs partition (at least a corrupted IMEI would show numbers starting with 0,not unknown) maybe flash a 4.2.2 modem (MGA then) will help?
[Galaxy S 4 i9505 Android Development] chavdar:
I have the same problem! I tried flashing an older backup of 4.2.2, then flashing with odin again the MJ5 modem, even flashing the MGA modem. Nothing helps...

I am starting to freak out...

Solved, thanks to hawkerpaul:

RESTORING A BACKUP WITH SE Cotent BREAKS THE MODEM (OR AT LEAST MARKS IT AS UNKNOWN AND THUS UNUSABLE) EVEN ODIN CANNOT REPAIR.

Solution is to restore again without SE context

[MENTION=643734]Philz[/MENTION]: Are you familiar with the problem?
[Galaxy S 4 i9505 Android Development] nunosilva10:
same problem here since instalation of 4.3, what can i do? how do i restore the efs folder?
[Galaxy S 4 i9505 Android Development] David78130:
After install mgg+ firmwares your bootloader is locked. You can't downgrade for now.

From my Galaxy S4 tuned with Echoe slim/Ktoonsez kernel & Philz touch recovery.
[Galaxy S 4 i9505 Android Development] chavdar:
Have you flashed through odin or through cwm? If you have an efs backup you can restore it with philz. But this is not the problem that I was referring to.

Sent from the GT-I9505 Galaxy