yashsingh1/xdaforums huggingface dataset:
[HTC One S] Phil3759:
If recovery crashes but returns to GUI without a reboot, you can grab a log and attach it here so that I can see what happens

Also, do you have a link of that ElementalX installer or the zip causing a crash?

Finally, if it is only one installer while others work, maybe something related to the installer? Same zip works on stock CWM or TWRP?
[HTC One S] Sneakyghost:
- Recovery crashes and reboots the phone. Think i won't get a log this way right?

- After changing back to TWRP, that refuses to wipe /cache, but restores a NANDROID, does a format of /cache in the process. After, the wipes work ok again.

- There is no stock CWM for the One S, only the self-made one from Darkwing, which has been discontinued and is not entirely bug free itself.

ElementalX can be found here: http://xdaforums.com/showthread.php?t=2083229

Theory as of now: Aroma does cause the malfunctioning mounts. It does instruct recovery what to do and i believe in that process lies the problem. Viper.zip causes a malfunctioning /system mount with latest TWRP. Sole error thrown by aroma and recovery: I/O Error. Now CWM does have an issue with /cache mount, again after running an Aroma based zip.

On a side-note: hes_theone64, who does a lot of work for Venom mainly but also others, keeps saying right since the beginning, that the OneS has a problem with its Cache partition. I would like to add that i believe the One S generally has a problem with all its partitions. This odd malfunctioning of mounts is not quite new.
[HTC One S] qazsxdcfv:
Bloody hell , i get that recovery bootloop on minimal percent of my battery , ( i guess 1% ) ..

But can booted up normal again , after the charge reach 15% ..

Sent from my hTC One S powered ViperS by Team Venom™
[HTC One S] Phil3759:
I can try packing it all around a stock ramdisk. It fixed many issues for one x include data access. It is also how i repack all Samsung recoveries to keep exFAT without any issues.

Please provide a stock recovery.img file from a RECENT firmware
[HTC One S] Sneakyghost:
HTC One S stock 3.16 Recovery

Here you go:

Recovery from RUU HTC_Europe_3.16.401.8
[HTC One S] FlyinGrub:
Just want to say that i can't insatll Viper 2.2 without a bug on TWRP 2.3.3 ...

- Statusbar appear 5min after boot

- phone very laggy

- or can't boot at all !

I remember that i have all the time problem flashing viper on twrp and with cwmr it worked :good:

So i've tried with this and it seems to don't work too, still the problem with statusbar. :confused::mad:

i've noticed that venomtweaks after erase data is very very slow !
[HTC One S] Sneakyghost:
Yeah bro that's because its got nothing to do with recovery. That issue is a Viper Issue and has been discussed like 100 pages or even more, once on every page at least. It is to do with the theme and probably also with file leftovers and might need a RUU too and you gotta search there and learn how to solve it. No point going to look here as its really not a recovery issue and has been discussed over and over and over.
[HTC One S] FlyinGrub:
sorry for that, i didn't follow the viperones thread too many thing to read ^^

i didn't know how do you make to do this :P

Aaa : i've just to change the skin and return to default screen, i've forgotten this ! :silly:
[HTC One S] ryanshew:
Re apply HTC skin, (you can change it after).

I can't believe people still go on about this, just read a few pages in the proper thread for this issue. Someone asks about this on almost every page.

HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | Bulletproof_1.3

---------- Post added at 02:31 AM ---------- Previous post was at 02:30 AM ----------

Ok, well that's not what were talking about...that's just your battery dieing, lol

HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | Bulletproof_1.3
[HTC One S] qazsxdcfv:
Lol , haha ..

But there's recovery on the mistake ,..

So i post it on here ..

Lol .. :D

Sent from my hTC One S powered ViperS by Team Venom™
[HTC One S] joemanbui:
Hey phil great work on the recovery. However, I've been having bootloop issues with my phone and I was wondering if you knew what this error message meant.

I: Checking for extendedcommand & OpenRecoveryScript...

I: Skipping execution of extendedcommand, file not found...

I: Skipping execution of OpenRecoveryScript, file not found...

Partitioning SD Card... please wait...

fail1

I am having trouble booting into my phone. I can mount my sd card via cwm recovery but it won't show up in fastboot. Do you know what the problem is? Thank you.
[HTC One S] rustykwak:
I am fairly sure that you cannot mount sd while in fastboot mode so has nothing to do with the recovery!
[HTC One S] noble8:
Thank you, this recovery is superb. :D
[HTC One S] Phil3759:
One requested to add modem support

I do not find the PM with partition details

Anyone can repost the device for /modem partition in recovery? I have for special edition, but not the normal ville
[HTC One S] cicciocant:
I found this:

http://xdaforums.com/showpost.php?p=27208055&postcount=255
[HTC One S] Phil3759:
Still need to know, which is the modem for you: radio?

And I need the fstype: often emmc, but for many HTC phones it is vfat

I did not find the data in stock recovery partition neither in TWRP recovery
[HTC One S] Darknites:
P17 and also P18&19 for wifi too.
[HTC One S] AKToronto:
Is there a terminal command or busy box command we can use to find out? I'm thinking those three partitions are emmc but best to double check
[HTC One S] Phil3759:
cat /proc/partitions can list the partitions list, but, to map them and get fstype for non mountable partitions it is a matter of digging into device source and sometimes ramdisk files

From the ramdisk files, it seems just a vfat partition

Anyone knows if using just tar, we can backup and restore the radio partition? I do not want to mess with your phone as I cannot test this at all. And I see no recovery permitting this for your phone, so, maybe they are not all dumb, mainly twrp as it usually allows it

However, it shouldn't be an issue if a tar operation works
[HTC One S] FlyinGrub:
*deleted*
[HTC One S] touch of jobo:
17 - radio - vfat (fat16) - /firmware_radio

18 - adsp - vfat (fat16) - /firmware_q6

19 - wcnss - vfat (fat12) - /firmware_wcnss

24&25 - modem_st1&2 - not mountable

The fstypes according to the partition table are useless. Looks like they're used as IDs or something. (Except for 33~36. See attached table also. It's a dump of the chain of EMBRs.)
[HTC One S] Sneakyghost:
Well since the later hboots, radio can't be written to anymore unless S-OFF so i doubt its possible to write anything to it, be it Tar or img or whatnot. A recovery that would want to write to those would need to determine Security Status first in order to open the write dialogue or hide it. Or else you will have lots of people coming back complaining about a not working feature in the best case or real issues like maybe bricks in the worst case.
[HTC One S] Phil3759:
Yes, that was my fear as I cannot test it my self without such a device

No recovery added this for HTC devices, even TWRP which I consider an ultimate dev coding and that also support encryption for some devices

So, going to drop it to avoid issues, until I can find some existing source to look at or have a device my self to play with before releasing such experimental things
[HTC One S] Darknites:
Maybe I missing something here but twrp can flash the radio and wifi.
[HTC One S] Sneakyghost:
Sure about that? With S-ON and later hboot? I know it works on old hboots and S-OFF...

mobile post
[HTC One S] Darknites:
Ya I get that but I thought this was about flashing if you S-Off'd.
[HTC One S] Phil3759:
I unpacked last version of TWRP ramdisk and the fstab file has no modem entries at all there, so doubt it can back it up at all, unless it uses another fstab file which I am missing
[HTC One S] Darknites:
Oh you trying to back it up so ya it don't do that, see knew I missed something lol.
[HTC One S] Phil3759:
Well, if you can flash it, backing it up is even easier as it is a read only operation
[HTC One S] Darknites:
This zip here can flash radio and wifi with twrp.
[HTC One S] Phil3759:
Thank you, but, your zip will also install in cwm, it's just a recovery install-able zip, nothing to do with flash/backup from withing recovery nandroid options

Looking at the script, it has this:

run_program("/sbin/busybox", "dd", "if=/tmp/radio.img", "of=/dev/block/mmcblk0p17");
delete("/tmp/radio.img");

So, using dd shell command to flash a raw image

It's easy to add directly in recovery nandroid job but I really need to be sure of the filesystem type and not willing to cause issues on your phone. If this goes formatted the bad way, you are in trouble

I will look at adding a special raw dd support like I do for efs partition and modem for Samsung devices.

Will add to my to do list
[HTC One S] Darknites:
Oh right didn't know it was using dd and no clue on filesystem stuff.
[HTC One S] Phil3759:
New version 5.03.0

Below is full change log

In short:

- potential serious bug for /data/media devices

- Advanced Backup statistics during nandroid tar operations

- Update to cwm 6.0.3.2

- 3 new colors as requested

- Add toggles to change color of header text and battery/clock display color

- Small GUI changes (fix color highlight of virtual buttons and the bottom menu line color

Download links

Last version can be found here:

It is still repacked on cm-10.1 prebuilt bundled kernel

That's to ensure eventual NEW bugs cannot be put on the new repack

Play a bit with it as it also fixes a bad mount issue for /data/media devices like yours

After that, we see if we go the repack with stock kernel like One X
[HTC One S] jamel_tza:
This is what worked for me. After trying time and time again, doing anything in the recovery was just impossible given the 15 second opportunity to erase the cache. I ended up buying a N4 because of a few problems I encountered while trying to boot up. Eventually I ended up figuring a way around all of it as the all in one root kit wasn't working because of bad drivers. I ended up wiping EVERYTHING (external SD and all), installing TWRP for the mount USB and just started from scratch.

Thank everyone for all your help, I couldn't have done it without you guys.

For anyone looking to download this recovery, do not let my experience deter you. This is a pretty cool recovery, just make sure you have a nandroid (as you should when flashing anything).
[HTC One S] Phil3759:
Does screen shot work with swipe left?
[HTC One S] Phil3759:
HTC One S v5.03.7

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

HTC One S - Special Edition v5.03.7 do not use on normal One S !!!!

This is a highly experimental repack, flash at your own risk

http://d-h.st/users/philz_touch/?fld_id=16793#files
[HTC One S] Evil-Monkey:
What do you mean by normal? lol

echó en Android
[HTC One S] Sneakyghost:
[MENTION=643734]Philz[/MENTION]

SE variant boots, but had severe issues, could only do a quick check but it seems all issues come from paths not being right, e.g. the aroma file manager didn't load, saying E: unable to load package or the SD as usb mount doesn't work. Or anything that needs access to E: fails.

So I can't really get you any details right now but I think it's booting and that is quite something already.

Installed latest TWRP 2.5 to compare (had an old TWRP before) and that can't access E: either, also TWRP didn't load it's theme from sdcard. The issues are similar.

Think the mount points have to be fixed or nothing will work right.

Mobile Post
[HTC One S] Phil3759:
I will look at your excel table to see if mount points are fine

As a start, I used full stock ramdisk and recovery.fstab + all drivers were kept

Good it boots and only mount points to fix
[HTC One S] Sneakyghost:
Yeah thanks mate. One thing though: I'm not sure the problem is the mount points itself as they are identical to the Ville. But I have no other word to describe it. I'm not familiar with how the android partitions are set up. I'm sure something else is wrong as this wrong routing even stays if I flash a Ville RUU to the SE Ville! Maybe there is partitioning information in the chip that needs to be changed with a partitioning tool like we had for the old HD2? Maybe it's coded into some deeper layer that is not overwritten by a RUU, so either that is changed or any system running on top needs to be changed to be equal to the default system.

Or put different: I guess we either find a way to make a Ville out of the SE or we find a way to make any firmware we flash equal to the SE firmware.

Mobile Post
[HTC One S] Phil3759:
Normally it is the kernel and the correct fstab file, just that

I will look at it by tonight or tomorrow hopefully
[HTC One S] Sneakyghost:
OK very nice indeed. I could really use a Recovery with USB mount enabled as TWRP really doesn't offer that and also has other problems due to i suppose lack of interest in looking into this on the side of Teamwin :D
[HTC One S] Phil3759:
USB mount works?

Great

Can I have a log? If you cannot export one to sdcard because of the mount issues, do this after you see some error messages

adb pull /tmp/recovery.log

and attach the log somewhere
[HTC One S] FlyinGrub:
usb mount work with well with the One S (not SE)
[HTC One S] Sneakyghost:
Sorry [MENTION=643734]Philz[/MENTION], misunderstanding here. I was trying to say a recovery which has usb mount would be really great but unfortunately no recovery for the SE can do that yet.

Mobile Post
[HTC One S] Phil3759:
Ville Special Edition

New repack with fixed fstab for recovery

http://d-h.st/JC7

If it fails, can you do this, while booted in main system:

su
mount >/sdcard/mount.txt

and post the /sdcard/mount.txt file

Then:

cat /proc/partitions

and post the output here

Also, if you can attach the boot.img from stock firmware, would be great

That way I can try to guess a bit about partitions
[HTC One S] Sneakyghost:
Ok will do when I can snatch the phone off the missus again. Had it for 6 hours yesterday do redo it from scratch and I doubt she'll let me have it again easily :D

Might be a few days until I get there but thanks a ton for all you do!

Mobile Post
[HTC One S] Phil3759:
Np

This version should do the trick i think
[HTC One S] Sneakyghost:
Villeplus / One S Special Edition Partitions and mounts

Results

- Drive "K" appears in windows with message "needs formatting, unknown file system"

- In recovery, SD cannot be mounted. So no installs possible.

- Mount.txt:

rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
none /dev/timer_group cgroup rw,relatime,timer_slack 0 0
/dev/block/mmcblk0p33 /system ext4 ro,relatime,data=ordered 0 0
/dev/block/mmcblk0p35 /data ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p34 /cache ext4 rw,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/mmcblk0p26 /devlog ext4 rw,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/mmcblk0p17 /firmware_radio vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p18 /firmware_q6 vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p19 /firmware_wcnss vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
htcfs /data/htcfs fuse.htcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0

-CMD Prnt for cat /proc/partitions:

cat /proc/partitions
major minor #blocks name

179 0 61071360 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 130671 mmcblk0p3
179 4 1 mmcblk0p4
179 5 16 mmcblk0p5
179 6 256 mmcblk0p6
179 7 15577 mmcblk0p7
179 8 256 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 256 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 1024 mmcblk0p12
179 13 32 mmcblk0p13
179 14 6144 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 1024 mmcblk0p16
179 17 46080 mmcblk0p17
179 18 10240 mmcblk0p18
179 19 5120 mmcblk0p19
179 20 8190 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 16383 mmcblk0p22
179 23 1022 mmcblk0p23
179 24 4096 mmcblk0p24
179 25 4096 mmcblk0p25
179 26 20480 mmcblk0p26
179 27 4 mmcblk0p27
179 28 256 mmcblk0p28
179 29 16 mmcblk0p29
179 30 1280 mmcblk0p30
179 31 64 mmcblk0p31
179 32 99752 mmcblk0p32
179 33 1703935 mmcblk0p33
179 34 262143 mmcblk0p34
179 35 58589184 mmcblk0p35
179 36 50000 mmcblk0p36
[HTC One S] Phil3759:
Can you give more details?

- except second sdcard, other partitions are ok?

You should have two volumes in mounts and storage:

/sdcard: mapped to internal mmcblk0p36

And external_sd mapped to /dev/block/sda1

If you browse internal or external sd to install, which one works of the 2.

In your logs, i see this: /dev/fuse /storage/sdcard0

This should map to external_sd mount point maybe!
[HTC One S] Sneakyghost:
Philz Touch CWM for Villeplus One S Special Edition TEST

E:error mounting /sdcard

E:error mounting /external_sd

--> When browsing for zip.

--> Same when trying to mount them.

Sorry cannot do more right now.
[HTC One S] Phil3759:
Sorry, but I am abandoning it :(

It is taking me a lot of time and I am really on the busy side. After it failed with a stock ramdisk then with true mtd name mapping, I see no other options without a device in my hands to test

I looked in the scripts it has, and there are tons of them linking the partitions from kernel commands it seems

So, one need to check all the links / mounts and how it is doing them in shell, so that we can translate this in recovery

Sorry

Will be sticking to the One S, not so special :p

However, if you find a working source or image, you can always come back to me
[HTC One S] FlyinGrub:
will you add USB OTG to this recovery ??

And a swype confirmation when doing backup or cleaning cache ?:good:

:fingers-crossed:
[HTC One S] Phil3759:
USB OTG is not in my plans, it will probably need compiling fuse along the kernel. Not sure about it

Swipe to validate could be done once maybe, but not in the near future
[HTC One S] Sneakyghost:
Philz,

not a problem at all. It's only a minor thing to have USB mount on the SE and the phone's lifecycle is already half through anyway and there are no custom ROM's and no devs wanting to port for a virtually non-existent device so, the last thing i want is causing you loads of issues, time-eaters and nervous breakdowns :D

I am totally happy that you tried. At least i know now its not an easy thing. Mdmower tries the same with an edited TWRP he currently does for the normal ville, so maybe he's lucky but i doubt it, his first test showed the exact same **** results as this test of yours. This device is a pain in the backside. I don't get why they had to make it all that different. Its totally the same in every aspect, just a bigger mem chip.
[HTC One S] mdmower:
Phil3759: Did you already try to specify /sdcard as datamedia fstype in recovery.fstab?

/sdcard datamedia /dev/null

This is relevant from teamwin:

While we should be able to get /sdcard to mount, it will likely never work as a USB mass storage device. As for OTG, I remain hopeful but not sure.

CWM and TWRP handle this differently. I believe the above recovery.fstab entry MIGHT be sufficient for CWM(-based) recovery. TWRP has specific build flags to handle this.
[HTC One S] Phil3759:
Ah, no, I didn't try it. I did not even think it was datamedia device as I see some fuse calls and a dedicated mmcblk different from /data
[MENTION=1102297]Sneakyghost[/MENTION]: while in main system, can you access your sdcard with a root explorer from /data/media or /data/media/0?

If not, specifying datamedia in cwm will never work as it just mounts that physical path to /sdcard
[HTC One S] mdmower:
The biggest hint is in the partition sizes posted by Sneakyghost:

FAT 030d4000 = 51200000 Bytes = 48.8 MB
USERDATA DF8000000 = 59995324416 Bytes = 57216 MB

I have device trees up on github: CWM and TWRP. They could need slight amendments if it turns out storage is in /data/media/0 instead of /data/media.
[HTC One S] Phil3759:
yes, I saw that too, but the fuse on /sdcard0 stopped me

Hope Sneakyghost can confirm, while he is in main system, if it is a /data/media device

I am not willing to throw another useless repack if not needed

In my recovery mod, be it /data/media or /data/media/0 is not an issue as it can be set manually in Advanced Menu
[HTC One S] mdmower:
I would say to go ahead an build him a test image. Here is a snippet from a PM he sent me yesterday after testing TWRP based on data/media:

On the off-chance that you cloned by github cwm branch, know that I'm guilty of force pushing a modification without incrementing the commit number (yeah, I know... bad practice; just realized I made a mistake). So, a re-clone would be a good idea.
[HTC One S] Phil3759:
Ah, no, I am using the stock cm-10.1 branch for ville, repacked with a stock ramdisk

Your trick for /data/media is not meaning it is the sdcard.

I have an i9100, not /data/media. I can turn it into /data/media by just adding that same line in recovery.fstab. It is the way I do to debug /data/media devices or devices without a second storage. I just play with that recovery.fstab.

However, obviously, I am just faking things and creating a new /data/media folder. My original sdcard which is on a dedicated partition is not part of the new fake /sdcard

So, what Sneakyghost must confirm is if with your repacked version he can see his real sdcard contents. Or at least, confirm if in main ROM he can browse his sdcard by accessing /data/media

By the way, if it was really a datamedia, it should be /data/media and not /data/media/0 as I do not think he has any 4.2 ROM available
[HTC One S] mdmower:
I put together the recovery commit for ville. I purposely created a separate tree for villeplus so that I could use a stock kernel from the villeplus ruu.
[HTC One S] Phil3759:
Sorry, I never commit the modified device tree as for many devices I use a post compile script to repack from an existing device. It is all automated.

Basically, I compile for maguro, and a shell script will produce the toro and toroplus for example

This is to spare time and space on my limited resources

For the ville_u I repacked completely with stock ramdisk. That's what works the best for many HTC devices
[HTC One S] Sneakyghost:
Villeplus /data/media

Hello,

the booted Android of the Villeplus has the SD contents located on the path /data/media, not on /data/media/0.

mdmower requested me to drop this info here.

Thanks guys.

Here is a recovery.log from the latest CWM based test-build for the villeplus.

- SDcard cannot be mounted in this device per mount option

- there seems no mount as USB option.

- Browse to install zip can access the SD perfectly.
[HTC One S] Phil3759:
You could say it earlier :crying:

But, I could consider it sooner too :p

Ok:

I will build a recovery based on datamedia

However, do not even dream to mount your sdcard from recovery in that case. It is not possible, at least in any simply feasable way

Thank you mdmower
[HTC One S] Sneakyghost:
Yeah fair enough but what I just don't understand is you guys talking about usb mount in a way that makes me think you actually mean usb mass storage. The new JB kernels you also pack in now use MTP natively though. So why not mount it as MTP device? Where's this immense problem I seem not to see? Is it that it's emulated fat on ext4? Or what is the real problem?

I'm always eager to learn. Could you try to get me onboard with this matter so I can actually follow your discussion? That would be very kind and much appreciated.

Mobile Post