yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] Phil3759:
Sorry and many thanks for your help

Do not worry, that was a partition dump using cat, not a yaffs2 backup. That's why your yaffs2 check fails. It can be restored using either cat, dd or my recovery

Now, please, can you, or someone else, test this last one:

http://d-h.st/ejO

Now, the date folder should contain a yaffs2 dump while the raw one with cat will fail

A log would be very important

That way, I would be sure about the final implementation to enable both yaffs2 dump and raw dump

Not meaning to stress, but if it could be done quickly, will be very nice. It is the last thing holding me to release next important update
[Nexus S Android Development] morrigan91:
Try but no backup img and no error...
[Nexus S Android Development] Phil3759:
I see the issue

Thank you again (out of my daily limit for these :good:)

I will release next update with all fixes I can think at to handle this in a good way

If needed, I will then release a small update for your phone, but hopefully not
[Nexus S Android Development] morrigan91:
OK. thanks.. the last recovery that i installed is fully working or beta test.. ? in the waiting a update is better to come back the last ufficial release ?
[Nexus S Android Development] Phil3759:
No, it is the old one, just repacking

I plan updating in the weekend
[Nexus S Android Development] morrigan91:
ok... thanks again for your work... :)
[Nexus S Android Development] migueldbr:
please dont feel discouraged by the lack of replies, the nexus s section has considerably less people because of galaxy nexus and nexus 4, but many of us who still use this device appreciate your work. It is indeed a unique recovery. i cant help right now because im in the middle of exams but im sure more people will take interest in this thread and help you.
[Nexus S Android Development] Phil3759:
Sure

However, it is hard debugging something when you have no testers and you do not own the device

But, as long as there are testers and people that provide logs and report issues, I will support the device. Fixing bugs for your device, means less bugs for other devices and further developments ;)

So, it is important for me
[Nexus S Android Development] BBuZZ:
I cant help you in this one because i dont know what is EFS...sorry
[Nexus S Android Development] Setting.Out:
Ditto, though I will research it a bit more... :)
[Nexus S Android Development] Phil3759:
For now, it is ok. I think i can fix this. I already got enough logs. Many thanks
[Nexus S Android Development] Phil3759:
v5.04.7

Mirror while devhost is down

http://www.mediafire.com/download/t3yctz3pmc0cbt0/philz_touch_5.04.7-crespo.zip

This will fix the efs backup hopefully

Also:

Let me know about any bugs please + a log

Also drop a message if backup now is ok
[Nexus S Android Development] morrigan91:
I downloaded it in 2 different places and same md5sum, i'll post here, it's important to be sure that the file is not corrupt

v5.04.7 md5: A40BED5B32128527F79E42C9E972264C

I tried only on the NS with damaged efs and I think it's ok, it created date_time.img and yaffs2 file. Many many thanks Phil!
[Nexus S Android Development] Phil3759:
zip has crc-32 check, so no worry normally

Great news :victory:

I am testing some changes for a 5.04.8, but they only concern people with an external storage

So, for you, you can consider it as a final stable

All other feedbacks are welcome of course, even to just confirm efs and other things are working

You should be able to flash modem.bin files and to backup/restore your modem too
[Nexus S Android Development] morrigan91:
Hi,Phil

Great work!!!.. test with another device and i open efs.yaffs2.img with unyaffs without problem...

I try to change UI Interface but at reboot , lose backgruond setting.... what's wrong ?
[Nexus S Android Development] Phil3759:
This is great news I could fix the yaffs2 issue. I am grateful for all your logs and debugging :angel:

Argh, I could reproduce the issue

Will be fixed before next update
[Nexus S Android Development] Phil3759:
Uploaded v5.05.0

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

Please test backup if it is fine and report

Change log:

5.05.0 (26.05.2013)
[Nexus S Android Development] morrigan91:
Normal backup works

Efs backup works

Radio backup works

Misc backup works

Bug:

auto restore settings works random: when I go to recovery sometimes I lose all settings, sometimes only the background. Load settings manually works. (tried on 2 different NS).

Can you fix? Thanks!
[Nexus S Android Development] Phil3759:
Auto restore settings: settings are loaded from /data folder on start

If you wipe your phone/factory reset, settings are wiped obviously

Now, here comes auto restore feature:

If you saved your settings to sdcard, recovery will detect them and prompt to load them

If you enable auto-restore, it won't prompt and will restore them automatically

IMPORTANT: the auto-restore will not take when you boot into recovery. It will take place when you reboot from recovery

This means: after wiping your phone, first reboot into recovery, you loose your settings. On reboot, they will be restored

That's how the main check in cwm is implemented. I just added my settings to it. I can make it work on start up though...

Will add to my todo list

Is this your situation? If not, try to provide a log when you start and loose your settings and have to restore them manually

Boot into recovery, settings lost, restore manually, create the log as explained in previous post
[Nexus S Android Development] morrigan91:
I didn't do any wipe, I lose all settings even doing "reboot recovery", auto restore setted "ask" never prompt me anything, setted "yes" didn't work. I lose the settings random, 30% of times I lose only background, 70% I lose everything. "reboot recovery" or going into recovery from the rom or bootloader seems don't change things. Restore manually works.

xda don't let me attach the file, link: https://dl.dropboxusercontent.com/u/79924589/philz_recovery.log
[Nexus S Android Development] Phil3759:
Thanks for the log

Did previous version work for your?
[Nexus S Android Development] morrigan91:
I'm not sure, but with previous versions I lose only the background.
[Nexus S Android Development] Phil3759:
Wired

Nothing, absolutely nothing changed in that regard

It seems like mount of /data fails on boot for you

Reviewing your previous log for background, I see that the failure you faced had nothing to do with the fact I could reproduce it on my system. What I fixed was related to having sdcards with fstype set to auto, which won't happen on your device

So, it's like, you have various partitions failing to early mount on boot.

Anyone else having same issue?

Maybe the kernel used doesn't work well when mounting

It could also be an issue with your phone having corruption

Can you try formatting /data in recovery please (factory reset), then restore a backup. This should remove potential file system errors

If it fixed your issue, great. Else, I will try to change the fstab

Please let me know how it goes as I am willing to fix it if it is really a recovery issue
[Nexus S Android Development] Phil3759:
Reading previous threads, I remember now you also had partition issues with /efs which at the end was a problem on your side

Sorry, but I looked again in device tree for the kernel version I am using, and I see nothing wrong

So, you are having issues with /efs, /sdcard and now /data

Maybe it is phone saying good bye?

Please, if other users have it working, post a feedback that it is ok. Mainly, that recovery settings, when changed by user, are saved on reboot
[Nexus S Android Development] morrigan91:
Here is the log of the NS with no problems, the one of the previously log.. Same bug of mine :crying:
[Nexus S Android Development] Phil3759:
Well, will wait for others feedback. If many have issues, i will try to change mtd name
[Nexus S Android Development] morrigan91:
I have others feedback, hope it helps :fingers-crossed:

other 3 different devices, same problem on 5 different Nexus S
[Nexus S Android Development] Phil3759:
5.06.0 (01.06.2013)

I added mtd/mmc names to recovery.fstab to allow mount /data using second device name

Hopefully, this will fix the issue reported above by only one user for now

Please give a feedback even if it works, so that I know this device thread is not dead and I keep updating it ;)
[Nexus S Android Development] migueldbr:
I haven´t updated since the first version because what i do with recovery has not give me much problems. although usb mount on recovery does not work but i will try to update later and check it out

also, could you tell me what you want me to test?because this recovery has like a hundred functions lol
[Nexus S Android Development] Phil3759:
Thank you:

PhilZ Settings / GUI Settings / change menu height to something

Reboot recovery

See if it saves your changes or not like one user is reporting here

The current build is stable as largely debugged on other devices before this release :good:
[Nexus S Android Development] migueldbr:
hes right, it does not save settings!
[Nexus S Android Development] morrigan91:
Unfortunately, same problem of the previously releases :(

I don't understand why it fails to restore only some options. A question, why the log says that I have android 4.0.4? All the device data are wrong, now I have 4.2.2.

The reason why I posted 5 differents log is because I'm a moderator in an android italian forum, many users without xda account appreciates your work! I asked them some logs..

Here is my log with 5.06.0
[Nexus S Android Development] Phil3759:
Ok, seems you have a very slow /data mounting device

You can see in log that it first fails to mount /data, then, in the middle of loading settings, it is able to mount it (settings start to load). So, it seems we have to add a retry loop to wait for /data to mount before continuing to load the system

The kernel used is a GB kernel :D

Looks crazy, but I checked and even TWRP 2.5 uses a GB kernel for your device to keep USB mount function in recovery. But, in anycase, it doesn't matter a lot. Recovery runs fine under GB

I will try to fix it on next release by adding a loop to wait for /data to mount before loading settings, or early mount it in ramdisk

We'll see
[Nexus S Android Development] Phil3759:
v5.06.1

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

/data is now awaited to moint at ramdisk level

Hope this fixes the issue

Please, let me know + log

Many thanks
[Nexus S Android Development] morrigan91:
It works correctly! Many many thanks Phil!

Here is the log (only rebooted, no restore settings)
[Nexus S Android Development] Phil3759:
So great, this is good news. Many thanks for all the feedback and fast follow up you gave to debug this

I am always ready to fix things when people give so prompt feedbacks + logs :good:

By the way, for anyone interested, here's the diff from init.rc I did to fix it:

+on fs
+ mount ext4 /dev/block/mmcblk0p2 /data noatime nosuid nodev wait
+
on boot

This will mount /data on boot. The wait option will wait a max of 5 seconds until it is mounted
[Nexus S Android Development] spider623:
can i ask something out of the blue, is there any way to change the sorting system to work by letter(twrp default) and not by Upper first(cmw default)?
[Nexus S Android Development] Phil3759:
Probably,

I will look at it once
[Nexus S Android Development] baseli95:
Hello, I just flashed your recovery and I like the way it looks. I just have an issue of deleting backups in the recovery. I had the same issue with CWM 6.0.5.0. How can I report you the bug? Thanks for your support.
[Nexus S Android Development] Basche:
Just a question, should I download the new releases from here or can I download from the main thread?
[Nexus S Android Development] explorer-10:
Unrelated to the thread, but just wanted to ask how are you able to flash the cm lag fix for RBJ if the fix was only for 4.1 based roms?
[Nexus S Android Development] liborio99:
Hey guyz!

Is there any way to flash this whitout my power button since i have cwm instaled and need it to select?

I aready tried flash tools. But i cant figure out how to install the NS drivers!

Gtz for any reply
[Nexus S Android Development] kriout:
you could install goomanager and from there install the TWRP ... then you would have a touch recovery and you could use that one for installing this recovery.

you could also try to use the soft touch key in CWM... one of them should select too ...
[Nexus S Android Development] ej8989:
He might be able to flash it but if there are improvements it's just placebo.
[Nexus S Android Development] Phil3759:
Released v5.08.5

Change list 5.07.1 ---> 5.08.5

Please Note: Device specific threads will no longer be updated. I monitor them for support and feedback though

To check if you have a new version, subscribe to main thread:

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

Thank you for your understanding
[Nexus S Android Development] ironia.:
It possibile to use aroma 1.90?

Tnx
[Nexus S Android Development] ironia.:
miss to take screenshot....on crespo:

when i tap 'about' nothing appear

when delete a backup is displayed only 'chose backutp to d'

reported cwm 6.0.3.7 but on cwm site the latest is 6.0.3.6
[Nexus S Android Development] Phil3759:
Please give more info as I asked you in main thread

No logs, no step by step to reproduce an issue = no support possible
[Nexus S Android Development] ironia.:
Enter into recovery (i see 6.0.3.7 but the latest CWM is 6.0.3.6?!) :

- tap ' about' nothing appear

- tap ' delete backup' and see the title that 'delete' is truncated to 'd'

many thanks
[Nexus S Android Development] Phil3759:
Anyone else confirms this please?

If you post a screen shot about truncated title, would be great
[Nexus S Android Development] ironia.:
also

in the title

in the word 'setting' the letters 'ng' are missed

thanks a lot
[Nexus S Android Development] Phil3759:
Thank you for the log

Is previous version affected?
[Nexus S Android Development] ironia.:
Sorry but I don't remember
[Nexus S Android Development] morrigan91:
Yes same display iusses on 5.08.5..
[Nexus S Android Development] Phil3759:
Anyone interested in debugging it?

It was never reported on any other phone

If yes, I build a debug version and you provide a log from it
[Nexus S Android Development] morrigan91:
not for me is only a display iusses, expect more feedback
[Nexus S Android Development] Phil3759:
behind a bug, a more serious leak must always be looked for...

That's why I try to spot all bugs

I will release a debug version soon
[Nexus S Android Development] explorer-10:
Does Philz cwm recovery output the same backup files compared to the regular cwm?
[Nexus S Android Development] Serris:
I think yes, I was able to restore philz backup with regular cwm recovery
[Nexus S Android Development] explorer-10:
inversely, it's the same as well?
[Nexus S Android Development] ironia.:
yes

philz use cwm, and philz can backup in cwm (both formats) or twrp
[Nexus S Android Development] explorer-10:
anyone ever made a high-compression backup? when using titanium to restore apps from the highly compressed backup, it gives me an error stating, "could not find any data in this CWM backup."
[Nexus S Android Development] Phil3759:
Because TB team is crappy and never answered any email from me to support compressed backups

Surely, now that official CWM added it, they will support it

Disgusted by them despite being a retail user
[Nexus S Android Development] explorer-10:
so for the time being, just gotta wait until they come with an updated version that supports it huh? well, that sucks...no highly compressed backups for me, at least for now
[Nexus S Android Development] keb00:
Are the links down? :(
[Nexus S Android Development] Basche:
I was able to download the latest version fine. Maybe server overload or something.
[Nexus S Android Development] forb'S:
Have I this right, when I say, "Clean to install a new ROM" do not affects my sdcard? Or isn´t there such a option to erase the ROM but not the sdcard? Is this option only a factory reset
[Nexus S Android Development] doma8108:
it doesnt affect the sdcard.. it's a quick option to factory reset
[Nexus S Android Development] Phil3759:
no, this will also format /system
[Nexus S Android Development] doma8108:
Yes, sorry.. I forgot to mention it.. please don't tell that to the developer :D
[Nexus S Android Development] adm1jtg:
@ Phil3759 any chance for a new build soon for crespo.... all new 4.4 builds require 6043 cwm so i cant use your stuff right now and sorely miss it
[Nexus S Android Development] ethan_hines:
I need a way to delete /data but keep /data/radio on my Nexus S because my efs partition is screwed and the only way to keep my IMEI is to keep /data/radio how can I do this with CWM Advanced Edition PhilZ Touch?
[Nexus S Android Development] kkkhattak:
Please make a new version of your recovery also to Nexus S because your recovery rocks :D
[Nexus S Android Development] xbs:
+1
[Nexus S Android Development] cheeze.keyk:
+1 :good:
[Nexus S Android Development] Phil3759:
update to v6.00.5
[Nexus S Android Development] kkkhattak:
Thanks allot bro was waiting for this update :highfive::good::victory::D
[Nexus S Android Development] Setting.Out:
Will this support kitkat?
[Nexus S Android Development] kkkhattak:
Yep it is supporting kitkat :good::highfive::laugh:
[Nexus S Android Development] forb'S:
Thanks a lot, Phil, I appreciate that and your work.

Especially because in the last times you were up to your ears with work. :good: :good:
[Nexus S Android Development] Phil3759:
Anyone can confirm if the display of menu names is still broken

I remember a feedback of something similar.

Please, if it is the case, try to describe exactly how it looks and post a screen shot

I never saw any such report on other devices. Small bizarre glitches can hide bigger bugs sometimes. So I prefer to follow up such issues
[Nexus S Android Development] bjuderas:
Thanks Phill, these are great news!!!
[Nexus S Android Development] forb'S:
No, i could not register such occurrence ´till now. Maybe anybody?, maybe not!
[Nexus S Android Development] adm1jtg:
So far I have two main issues with the newest version of philz

First the font is at least 2 point sizes larger then in previous version and really doesnt fit on the screen very well at all

Second I cannot get mount usb to work in the newest version... loaded 5.15 and everything is fine with mount usb and font size

I can provide screen shots if that would be helpful

Please understand I an reporting these "issues" not to complain but because i like this recovery better then any other and want to see it working 100% on my kitkat installs.
[Nexus S Android Development] Phil3759:
font, I can look at it. Maybe cm-10.2 did not define it and it defaulted to a bigger one

mount usb storage is more annoying as it is probably the kernel issue

Basically you have no choice. Only older 2.x GB kernel was able to bring mount USB storage. I remember on early releases it took me a lot of time to find a kernel that can enable this. However, you won't be able to flash any kitkat rom with the GB kernel

I had to update kernel and use the one from cm-10.2 to enable kit kat support, so you lost mount usb storage.

I see in TWRP main site that they notify about the issue and propose the 2.x GB kernel optionally

Let me know if any other recovery can flash kitkat and have usb mount storage

I could get the kernel from it, if it even exists

Look here, at the notes about Nexus S

http://xdaforums.com/showthread.php?p=41850102&highlight=mount+usb#post41850102
[Nexus S Android Development] bjuderas:
I just installed it, and it doesn't even enter the recovery mode. Everey time I try to enter into the recovery mode, it stays at the bootloader!
[Nexus S Android Development] adm1jtg:
Yeah official cwm hasn't had Mount USB working for a very long time that was actually my initial reason for switching to yours. As far as another recovery the only ones I know work on kk are yours and the original cwm.

I do know when 4.3 hit the kernel I use redid fstab settings. I use devil kernel and that is still somewhat active. You can find git for it under hellybean. Slim ROM also uses it as their default. Not sure if that helps.

Drop me a line if I can help testing or with more info on devil and such
[Nexus S Android Development] Phil3759:
If you have a selinux enabled +4.3 kernel that supports mount usb storage, link to it
[Nexus S Android Development] adm1jtg:
Try this one its devil which does support both of those and is still being actively updated

https://github.com/Hellybean/android_kernel_samsung_crespo/tree/cm-10.2

If not there is always this one also has both those features but is not being actively continued

https://github.com/bedalus/marmite/tree/marmite9.0
[Nexus S Android Development] bjuderas:
And now I have trouble installing the usb drivers so I can flash a new recocery! Recovery IMG is gone! This is just great!!!
[Nexus S Android Development] Setting.Out:
Nexus root toolkit
[Nexus S Android Development] bjuderas:
Thanks, I'll try that!
[Nexus S Android Development] Phil3759:
v6.00.8 Update

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

It is based on Hellybean kernel to hopefully fix mount usb storage while flash kitkat

Let me know if it is all good or not
[Nexus S Android Development] morrigan91:
Mount usb storage not working for me.

I have another problem, I can't save or load settings and themes. Do you remember that NS has a slow sdcard and there was problems loading settings? Now I think it's the same.
[Nexus S Android Development] Phil3759:
Looking at the log, it is not that simple

1- Mount USB storage: I am abandoning this as it must be fixed by your device developers. It will take me a lot of time, sorry. Ask your kernel devs to look at the issue. It is probably just a matter of having the proper ums lun path for the device/kernel combo. Playing in recovery with echo on the lun path to /sdcard should mount it at one point. After that, it should be easy. But, you need an advanced user/dev owning the device to debug it

2- the settings file bug

seems not related to that issue, it is a bug on my side. I did not take into account non data media devices when saving settings

vold changed many things

Thank you for the report, I will fix it
[Nexus S Android Development] adm1jtg:
Talked with steven676 about #1 and he said the following:

I think the path he's looking for is /sys/devices/platform/s3c-usbgadget/gadget/lun0 (that said, sys/class/android_usb/f_mass_storage/lun should work on any device with an Android kernel). I think that has to be defined in userland?

Is this what you needed?
[Nexus S Android Development] Phil3759:
I will look at it, but probably more complex...

Can you test new v6.01.0 if it fixed issues saving/loading settings and accessing sdcard?
[Nexus S Android Development] morrigan91:
Fixed!
[Nexus S Android Development] adm1jtg:
I do not agree i would say the font issue and all seems fixed but mount sd still doesn't work for me.
[Nexus S Android Development] Phil3759:
mount is not fixed yet

As I said, you need a good kernel or some dev looking at cm sources to enable this

If you know a recovery with this working and a new +4.3 kernel, let me know, else it is too much time spent
[Nexus S Android Development] adm1jtg:
Ok I misunderstood I thought the lun path info i gave you was going to generate a try and that this last build was that try.

Apologies....

BTW for me the text is still a little bit to big to fit on the screen properly but it is purely a cosmetic thing far as i can tell
[Nexus S Android Development] Phil3759:
np

But it seems vold uses its own lun path

Have to look at sources if lun is still defined

Will give it a last try
[Nexus S Android Development] adm1jtg:
I am sure you probably know this already but I only just figured it out, when in recovery I can adb push just fine to sdcard... Meaning sdcard can be seen and used in recovery, it's only when we attempt to mount it to computer via graphical interface that it doesn't work