yashsingh1/xdaforums huggingface dataset:
[One (M7) Android Development] Sib64:
No, this process works because a lot of users have used it.

Are you unlocked ? You can see unlocked when you are bootloder.

Where are your recoverystock file .img ? normally in the platform tools or fastboot folder (look pics)

Can you explain what have you make ?
[One (M7) Android Development] la_muerte:
Thanks for the help!

But I think I know why the RECOVERY won't work.

Because I have BRANDED htc one.

cid: H3G__106

H3G (3 Austria)

fastboot getvar version-main
version-main: 1.28.771.6
finished. total time: -0.000s

so I need to find the right version of STOCK RECOVERY IMAGE

1.28.771.6 - Hutchison 3G UK (United Kingdom)

and flash it first!

Just like the steps to unlock AT&T branded htc one.:confused:
[One (M7) Android Development] Sib64:
Lol.. If it's branded by your carrier, I cannot do nothing for this part.

But you're Unlocked without problem ?
[One (M7) Android Development] la_muerte:
Yes! I can see *** UNLOCKED *** on my bootloader screen, but just cannot get into Recovery Mode.:rolleyes:
[One (M7) Android Development] Sib64:
If I find something about this problem with One Branded, I tell you ;)
[One (M7) Android Development] stesa:
follow this guide and install supeboot zip

http://www.ibtimes.co.uk/articles/4...-install-clockworkmod-recovery-android422.htm

then with hanson all in one flash CWR , done
[One (M7) Android Development] Sib64:
About the install of the recovery, you're UNLOCKED so you can flash a recovery even if you're branded by your carrier.

When you write your command lines which name write you for your recovery ?

Don't forget to write the same name as your recovery name in your your folder: Look screens of the OP ;)

Why giving the link for a another guide to a another website, your post is completly useless.

Please respect all OP who writes guides for helping xda members !!!!!

Thanks
[Galaxy S 4 Q&A, Help & Troubleshooting] berju:
Hello,

i receive my S4 recently and it's a very good phone. Before i've a galaxy note. So like the Note the lens is not protected !

I've an orginal flip samung cover, i love this because is thin but not the top for the lens.

I search for few days a case with lens protection ( like the old phone nokia N86 etc etc ) but i don't find anything.

Have you some idea to protect this lens or a case with shutter cover?

Thanks for help.
[Galaxy S 4 Q&A, Help & Troubleshooting] Beefheart:
Get a cheap screen protector and cut a bit out of it to shape.
[Galaxy S 4 i9505 Android Development] Phil3759:
Main thread + features + install instructions + dev support

http://xdaforums.com/showthread.php?t=2201860

PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM

It is a well proven recovery for many phones

It also adds a full touch interface a completely configurable GUI

Please give your feedback, what works, and any bug you could encounter

Read the features, and check if you are missing something

Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut

Download links

Last version can be found here:

Big thanks to [MENTION=3562083]wanam[/MENTION] and [MENTION=395758]ausdim[/MENTION] for their great support with providing kernels and support in compiling them
[Galaxy S 4 i9505 Android Development] Gondolier:
Nice to see you in SGS4 Forums Phil ;) Keep your awesome work on :D :D

Where's my thanks?
[Galaxy S 4 i9505 Android Development] Schrotty35:
Great to see you here. Download and flashed now.
[Galaxy S 4 i9505 Android Development] Phil3759:
Great

Waiting for first feedback to remove the scary red warning
[Galaxy S 4 i9505 Android Development] victorator:
Awesome PhilZ!

Someone please confirm this works fine!
[Galaxy S 4 i9505 Android Development] Schrotty35:
Not Working by me. Black Screen in recovery. See only the Button on the bottom but the rest is black.

Edit: Ok working. Wait 1 Minute and the Screen is coming but the touch not working correct. The Hardware button also not correct working.
[Galaxy S 4 i9505 Android Development] boterkaaseneieren:
Yes Phil it's in the house!!!!
[Galaxy S 4 i9505 Android Development] Phil3759:
Can you give more details

Touch is completely dead or it behaves bad. In that case, how does it act (a video would be helpful)

What issue with hardware buttons

And is the black screen delay on each start
[Galaxy S 4 i9505 Android Development] Schrotty35:
Black Screen on each start yes. After 10 seconds i see the recovery. With the hardware buttons louder and quieter i can not select ever entry. Only every second i can select. With Touch nothing correct working. In Arome the bottom bottons not working. The Font are very small.

Sorry my English is not so good.
[Galaxy S 4 i9505 Android Development] Erkan75:
Same problems like Schrotty. After choosing something by touch, it seems the screen doesn't refresh. If I go up or down, the screen appears.

Also I tried to format /cache ... it says Done, but from that point I get the messages "Can't mount /cache/*" ... the problem all the recent recoverys had.

On the right top I see time ... it shows me 02:14 ... no wonder the recent recoveries couldn't have a correct time in backup for me. Strange why some users have correct time/date ....
[Galaxy S 4 i9505 Android Development] Chenglu:
[MENTION=4666971]Phil3759[/MENTION],you need to modify graphics.c.
[Galaxy S 4 i9505 Android Development] Phil3759:
Ah, thank you

However, without a cm source (I use common jflte) and a device to test (still only an i9100), i have no idea where to start to fix it :confused:
[Galaxy S 4 i9505 Android Development] Chenglu:
I send a PM to you.
[Galaxy S 4 i9505 Android Development] Mr.AFK:
Sir Phil, great to see you here!

One question : it is possible to include an autoroot option in your cwm, like it is in the Note recovery?

On S2 only flash your kernel, got cwm, got root, got everything together. Niw it us a little bit different. That's why i ask for the autoroot option.

Gesendet mit meinem S IV
[Galaxy S 4 i9505 Android Development] victorator:
On N7000 and I9100 the kernel and recovery were one .img.

Kernel contained recovery. Since S3 and up, recovery is a separate partition.

lrwxrwxrwx root root 1970-01-09 01:56 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-09 01:56 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-09 01:56 backup -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-09 01:56 boot -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-09 01:56 cache -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-09 01:56 carrier -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-09 01:56 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-09 01:56 fota -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-09 01:56 fsg -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-09 01:56 hidden -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-09 01:56 m9kefs1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-09 01:56 m9kefs2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-09 01:56 m9kefs3 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-09 01:56 mdm -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-09 01:56 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-09 01:56 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-09 01:56 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-09 01:56 param -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-09 01:56 persdata -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-09 01:56 persist -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-09 01:56 recovery -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-09 01:56 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-09 01:56 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-09 01:56 sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-09 01:56 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-09 01:56 ssd -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-09 01:56 system -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-09 01:56 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-09 01:56 userdata -> /dev/block/mmcblk0p29
[Galaxy S 4 i9505 Android Development] Phil3759:
In new cwm 6.0.3.2, Koush added a function to prompt you to root on recovery restart if you loose root

It will copy su binary to where it should

After that, just install Koush CWM Superuser from market and you are rooted
[Galaxy S 4 i9505 Android Development] Mr.AFK:
Can I use this method initially?

So flash your recovery on stock rom, boot into it, "enable root procedure", boot up und go to play an install superuser app?

That's all?

Gesendet mit meinem S IV
[Galaxy S 4 i9505 Android Development] Sammath:
Hey Phil, nice to see you here. Always used your recovery on my note2.

I also get the black screen, I think it's because I use a different kernel. Faux123.

Maybe this helps a bit :)

Sent from the gt9505 galaxy s4
[Galaxy S 4 i9505 Android Development] om22:
You could simply flash a superuser CWM zip with any recovery and you`re rooted. ;)
[Galaxy S 4 i9505 Android Development] Phil3759:
I am downloading the whole ROM to check a bit more the stock boot.img

Also, I think it is better to move some exfat modules to the ramdisk to avoid mounting /system which always ends up in some issues

Also, need to look at some scripts that could be needed on start

When I am done, I will release another repack

Thabk you [MENTION=3084245]Chenglu[/MENTION] for the support, I appreciate it a lot

Note: this phone is a bit different from i9500, and since I do not own one to test, it could be we need some debugging until it is done
[Galaxy S 4 i9505 Android Development] pandorra:
i did so. also checked the in recovery mounted sd card with treesize. nothing on it...
[Galaxy S 4 i9505 Android Development] cholywell:
Has any one tried this on the Canadian SGH-I337M? It should have the same hardware as the 9505 and no locked boot loader like the US version.
[Galaxy S 4 i9505 Android Development] InevitableDJ:
How can you tell if the bootloader is locked or unlocked? I have the i9505 (UK) from argos
[Galaxy S 4 i9505 Android Development] cholywell:
You flash a recovery. If it bricks its locked. If you flash it successfully it's unlocked.
[Galaxy S 4 i9505 Android Development] Terry.666:
Hi all

A general question please, does this recovery support USB for flash or backup/restore?

Thanks in advance
[Galaxy S 4 i9505 Android Development] InevitableDJ:
It's a good thing then mine is unlocked haha
[Galaxy S 4 i9505 Android Development] jamal2367:
Best recovery !!!

Memories of my s3 :p

Nice design all is working :))
[Galaxy S 4 i9505 Android Development] Fir3blade:
Sorry for the question, but where is the backup stored?
[Galaxy S 4 i9505 Android Development] pandorra:
as long as you're talking about the usb storage, yes you can mount the EXTERNAL sd card

seems to be bit of a problem though i can't tell you if it's the recovery in particular or some kind of interaction with previous flashed recoveries (i've tried a whole bunch of different versions). my first backup with philz latest version was "lost" (likely to be stored anywhere on the internal storage which you can't access (besides adb) unless you root the rom), the second one was stored on the external sd card in the typical clockworkmod folder as it should be...
[Galaxy S 4 i9505 Android Development] Fir3blade:
The backup must be somewhere, because there are 4.4GB missing, but I can't find it.
[Galaxy S 4 i9505 Android Development] hanspampel:
Look at /data/media/0/clockworkmod/backup or /data/media/clockworkmod/
[Galaxy S 4 i9505 Android Development] pandorra:
where do you miss them? internal or external?
[Galaxy S 4 i9505 Android Development] Fir3blade:
Thank you hanspampel it is stored in /data/media/clockworkmod :thumbup:.
[Galaxy S 4 i9505 Android Development] hanspampel:
Yep thats the standard settings. But for Android 4.2.X and multiuser migration is /data/media/0/ recommend. You can set it under "advanced" in his recovery.
[Galaxy S 4 i9505 Android Development] Phil3759:
This question was answered so many times. A bit lost with how to make people get it once for all
[Galaxy S 4 i9505 Android Development] pandorra:
why don't you just write it in the first post? :)
[Galaxy S 4 i9505 Android Development] Fir3blade:
Valid argument ;)
[Galaxy S 4 i9505 Android Development] CTPAHHUK:
PhilZ, do, please, larger font
[Galaxy S 4 i9505 Android Development] Phil3759:
Because people do not read first post. I will just loose my time editing all the threads...
[Galaxy S 4 i9505 Android Development] :
Not if you write in big text and say not to ask the questions over again worked for me lol

Sent from my official GT-I9505 powered with qualcom
[Galaxy S 4 i9505 Android Development] MaKTaiL:
I tried using Philz with CM Updater on Cyanogenmod 10.2 and it didn't work. It fails at signature check. What can I do? It works great if I flash it manually though.
[Galaxy S 4 i9505 Android Development] CarlM34:
Philz S2 included rooted kernel and recovery....This is recovery ONLY.

Root - HERE
[Galaxy S 4 i9505 Android Development] BillGoss:
See http://xdaforums.com/showthread.php?p=45910807

Sent from my GT-I9505
[Galaxy S 4 i9505 Android Development] MaKTaiL:
Thanks! I will try that ;)

EDIT

Just tested, it worked perfectly here. Thank you again!
[Galaxy S 4 i9505 Android Development] BillGoss:
You are welcome. You don't need to write a post to say thank you. Just hit the Thanks button

Sent from my GT-I9505
[Galaxy S 4 i9505 Android Development] Phil3759:
v5.16.2 - cwm 6.0.3.9

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

This is the first stable cwm touch cm-10.2 release for S4

Supports new vold managed volumes, USB OTG hot plug...

This also has a workaround to let Aroma File Manager see external storage and even USB OTG files if you plug the key before running Aroma

It also should fix ors with new voldmanager

Deeply test it and report please
[Galaxy S 4 i9505 Android Development] BillGoss:
5.16.2 bug:

I use ors to backup to the external SD card. The backup failed.

Log: https://db.tt/rGKGbdOg

Settings: https://db.tt/Cxv4wZ4x

ORS command: backup BSCDO 2013-10-01.11.33.06_10.2-20130928-NIGHTLY-jfltexx

Update:

Found the problem...

My settings had: ors_backup_path=/external_sd

But 15.6.2 doesn't recognize that and changed it to /sdcard.

I went into Misc nandroid settings and reselected the ORS destination.

Setting now reads: ors_backup_path=/storage/sdcard1

Sent from my GT-I9505
[Galaxy S 4 i9505 Android Development] Phil3759:
Normally, if you use external_sd as source, ors-mount.sh will handle it

However, in Nandroid Settings, you in fact need to reconfigure destination path
[Galaxy S 4 i9505 Android Development] putti71:
Updated right away. Everything works. But strangely, backup takes 35mn instead of 18mn, which I had before on an older recovery build under the same settings.

Sent from Telegraph
[Galaxy S 4 i9505 Android Development] Tassos_i:
Tested nandroid backup through usbotg on an solid state disk 64GB (independently powered) with normal write speed under Windows of about 25MB/sec.

It works, but it is really slow when compared to my sd-exfat64. Backup times are (for 2.2GB,low compression)

- 8min30 secs, on my sdexfat64 (low ambient temperature )

- 34 minutes, when the solid state was exfat formated (room temperature) ,

- 38 minutes, when the ssd was ntfs formatted.

NB: There's a bug in backup size (it shows 0) as well as in compression ratio (it shows 0).
[Galaxy S 4 i9505 Android Development] SeaFargo:
I can't restore Stock ROM previously backupped

Hello. I have a problem, both with philz_touch_5.15.8-i9505 than Official recovery-clockwork-6.0.3.8-jfltexx, and also previous releases but I've started to backup for 10 days.

The problem is that I can not restore a previously backupped stock rom on my I9505. I am talking about I9505XXUDMHB_I9505ITVDMI2_I9505XXUDMHB Stock ROM.

From a fresh Odin flash of the rom I9505XXUDMHB_I9505ITVDMI2_I9505XXUDMHB, I did:

1. Odin flash philz_touch

2. Boot recovery and whipe data/factory, Cache and Dalvik (I want a clean backup).

3. backup (default tar, no compression)

The procedure goes well. :good:

I did the same with Official recovery-clockwork also. Same thing for all.

After both backups I tryed to bootup the system again to see if it still ok and yes, it was OK. Perfect boot and clean stock rom. :good:

Than i did:

1. restore a CM10.2 from a previous backup, but if I install it from zip it's the same thing. The CM is perfectly able to be backupped and restored by philz_touch and recovery-clockwork.

2. boot CM and everything is ok. ;)

3. boot recovery

4. restore the stock rom previously backupped (the procedure goes well)

5. reboot.

After the S4 logo (not the samsung animated. Just the white very first logo) the phone loop the reboot. :(

I tryed to restore each single backup made by philz_touch and recovery-clockwork, with their own recovery, and the results is always the same. :crying:

A white S4 logo and a loop.

What have I to do to proper backup or to proper restore stock rom? :confused:

Maybe have I to include some other partition more than the defaul settings? Have I to manage a custom backup and/or a custom restore?

And if so, how?

Kind regards and thank you in advance for your kind help. :o
[Galaxy S 4 i9505 Android Development] fREAST:
Couldn't the slow speed be related to the USB port on the phone?

Skickat från min GT-I9505 med Tapatalk 4
[Galaxy S 4 i9505 Android Development] Phil3759:
Latest 5.16.2 preview cannot backup to internal sd

I will fix it
[Galaxy S 4 i9505 Android Development] hawkerpaul:
Not sure if it intentional, but latest build refers to external sd card as /storage/sdcard1, and backups not working to it.

I did however try to attempt to flash a zip from external. The external option is down at the bottom of the list (instead of menu option 2 on previous version) and when I try to install from external, it gives a "checking" then "mounted" message.

Perhaps the latest version does not have external card mounted by default which is why people are not able to backup to external?
[Galaxy S 4 i9505 Android Development] donalgodon:
I couldn't backup to external sd either using ROM Manager (which I typically do)

I could do so manually, however. Hope you can address this.

Flashed back to 5.15.8 and tested again with the previous version, and it works, so it must be something with the new update and ROM Manager's interaction.
[Galaxy S 4 i9505 Android Development] Formhault:
The slow speed of backup creation?!
[Galaxy S 4 i9505 Android Development] Phil3759:
Latest 5.16.2 is not for daily use

It is cm10.2 adding mainly usb otg
[Galaxy S 4 i9505 Android Development] Phil3759:
I moved 5.16.2 to Beta subfolder

All cm-10.2 betas will be pushed there until we get a stable version

The size progress and all path issues are due to the new voldmanager used in AOKP sources

TWRP chose to stay with its own fstab manager because of this

Currently, new fstab manager is very limited compared to even older cwm one, as we miss the device2 field

Technically, it is there, but fs_mgr_read_fstab() function doesn't assign it

Sadly, fs_mgr_read_fstab() function is outside recovery sources and the aim is not to rewrite AOKP

In v5.16.2, I added support to a new extra.fstab file

I am going to enhance the extra.fstab handling to provide the needed device2 entry while using existing code

In opposite to TWRP, I am going to keep new fs_mgr but will just complete what we miss. This will make maintenance much easier until device2 is added

I will release some betas from time to time. As I have much less time, these will not be fully tested, hence their name beta

Feel free to download them, test basic functions, mainly backup/restore parts, report bugs, and provide logs

Once done, I will document extra.fstab file
[Galaxy S 4 i9505 Android Development] nokpos:
i have the i9505 and i try to root it but its not working i done it with reboot or without tick at odin and its not working why ?

my rom is i9505XXUBMGA.

thank you !
[Galaxy S 4 i9505 Android Development] hawkerpaul:
This is not a thread about rooting.

Suggest you look for chainfire's thread
[Galaxy S 4 i9505 Android Development] CarlM34:
This is for recovery not root......search CF Chainfire for S4;)
[Galaxy S 4 i9505 Android Development] nokpos:
sorry my mistake ,

i ve done the root and then i tried to setup the CWM ! and its not working ..
[Galaxy S 4 i9505 Android Development] :
I think I missed the point where 5.11.2 wasn't able to restore mh 8. Damn that makes me mad since it backed up perfectly it can restore but ends. Up in boot loop. I love faulty. Backups on my device I've lost too many already. Well some of them I lost due to trying port. Oh well I'll try to restore later with latest and see if it will work most likely it won't. Else backup speed was good
[Galaxy S 4 i9505 Android Development] Phil3759:
Latest Samsung kernels are becoming more and more secure

With Selinux permissions, things are getting even more wired

If they start to lock things even more, they can break all nandroid backups for stock ROMs as we need to apply special permissions

Maybe CWM should start adding backup of these

Hope this is not what they are targetting. For now, I did not migrate to the new locked ROMs/bootloaders of MHx
[Galaxy S 4 i9505 Android Development] :
doesn't need to worry, i'm going to upgrade to new leak anyway,
[Galaxy S 4 i9505 Android Development] DroidRevenge:
if your problem is the root this is not right thread
[Galaxy S 4 i9505 Android Development] CarlM34:
Assuming you have rooted successfully??? Did you follow the install instructions correctly - http://xdaforums.com/showpost.php?p=39433857&postcount=4
[Galaxy S 4 i9505 Android Development] :
[MENTION=4666971]Phil3759[/MENTION] whats new in 5.16.2

i don't find changelog :confused:
[Galaxy S 4 i9505 Android Development] Phil3759:
I update change logs in first page only on official final builds

Real time change log:

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

Mainly for developers
[Galaxy S 4 i9505 Android Development] Phil3759:
v5.16.4 beta

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

cm-10.2 tree

I fixed a lot of bugs in my mod + in original cwm

I quickly tested a backup / restore + progress

This update now supports custom format to all formats include ext2/3 (was broken in cm-10.2)

Partition sdcard is now fixed under cm-10.2

It is not very suitable for exfat users as write speed will be slow (voldmanager is fuse based)

It is beta, so only for debugging. It should be enough stable though

As I have little time, all debugging is welcome + feedback here

We are trying to make cm-10.1 features work under new cm-10.2 builds.

At some time, it could be I drop voldmanager for exfat devices to keep Samsung faster ko modules
[Galaxy S 4 i9505 Android Development] sgbmad:
Great! Now I can use your recovery to flash the P.A.C. ROM :good:

Thanks!
[Galaxy S 4 i9505 Android Development] donalgodon:
ROM Manager external backup data path is still broken with the latest beta 5.16.4
[Galaxy S 4 i9505 Android Development] Phil3759:
Because ROM Manager needs to update his paths to new vold managed devices in cm-10.2

Post in ROM Manager thread or use last 5.15.x which still uses old paths

By the way, vold is based on fuse, and mounts external sd through fuse instead of kernel modules

I am going to either disable it for external storage or find a workaround to mount using system mount on external storage

Hopefully, after +1 year, cwm now supports exfat. Maybe in 1 more year, fuse speed will be fixed :p
[Galaxy S 4 i9505 Android Development] diddsen:
[MENTION=218262]Phil[/MENTION]

i tested on new sammy 4.3 mi8... but after no sound.

so, not for the new?

thx
[Galaxy S 4 i9505 Android Development] Phil3759:
What happens when you flash with TWRP or CWM?

Maybe it is a ROM issue
[Galaxy S 4 i9505 Android Development] diddsen:
flashed with odin3.0.9 ... i thought safest way?

its stock rom mi8.

problem is, after flash yours, no sound... and must be flash again rom :(

cf root also dont work after (with stock cwm)...no sound.