yashsingh1/xdaforums huggingface dataset:
[HTC One S] Flashalot:
There been a unofficial firmware update that changed the partition layout
[HTC One S] Phil3759:
This doesn't answer any of my questions!
[HTC One S] g4ret:
this is change in firmware (hboot). now it's no sdcard partition, it replaced to /data/media/0/ and linked like /sdcard

it's all
[HTC One S] Phil3759:
The twrp image uploaded here is not datamedia

I can easily add support for data/media, but someone must provide info about new partition layout, mainly if older vfat partition was merged to /data

I am holding on this until a dev or someone understanding about partition blocks give all needed info I asked
[HTC One S] FlyinGrub:
u0_a132@android:/ $ df

Filesystem Size Used Free Blksize

/dev 391M 128K 391M 4096

/mnt/secure 391M 0K 391M 4096

/mnt/asec 391M 0K 391M 4096

/mnt/asec/com.quoord.tapatalkHD-1 20M 18M 2M 4096

/mnt/obb 391M 0K 391M 4096

/system 1637M 638M 999M 4096

/data 12347M 8077M 4269M 4096

/data/DxDrm/fuse: Permission denied

/cache 251M 4M 247M 4096

/devlog 19M 14M 4M 4096

/firmware_radio 199M 33M 166M 4096

/firmware_q6 199M 5M 193M 4096

/firmware_wcnss 4M 1M 3M 2048

/mnt/shell/emulated 12247M 8077M 4169M 4096

/storage/emulated 391M 0K 391M 4096

/storage/emulated/0 12247M 8077M 4169M 4096

/storage/emulated/0/Android/obb 12247M 8077M 4169M 4096

/storage/emulated/legacy 12247M 8077M 4169M 4096

/storage/emulated/legacy/Android/obb 12247M 8077M 4169M 4096

1|u0_a132@android:/ $

Can this help you ?

envoyé par charette.
[HTC One S] Phil3759:
Also need these two

cat /proc/partitions

mount

Obviously under new firmware / main rom / terminal
[HTC One S] Phil3759:
v5.15.9 - New /data/media hboot only

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

I only changed fstab so that /sdcard is now /data/media

Kernel and ramdisk are unchanged as I see nothing changed and only /sdcard and /data were re-sized while keeping same path

Hopefully, it should be enough

I also updated recovery to last 5.15.9 with the new scroll code and many touch bugs fixed

Please, give a feedback if it is ok on new hboot
[HTC One S] alphaeagle777:
Sadly no go
[HTC One S] tominozh:
Can't mount sd-card.

Hopefully this helps.

https://db.tt/s0chYmOi

Sent from my HTC One S
[HTC One S] Phil3759:
these kind of posts are useless

Provide a log please when mounting /sdcard
[HTC One S] Phil3759:
Sorry, I uploaded wrong recovery.img :o

I re-uploaded /data/media version now:

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

Please upload a log if something wrong

Do not forget the /data/media/0 toggle in Advanced menu if needed by your ROM (normally, you shouldn't use it, unless you flash with cm updater)
[HTC One S] alphaeagle777:
thanks sorry for the short messege it sees now the file in the sdcard but no usb mount mount

sorry no log at the moment will try to provide one later
[HTC One S] Phil3759:
Ah, forgot to mention: /data/media cannot be mount in USB storage, forget it, no recovery will support it any soon probably
[HTC One S] luxandroid:
Why is that?

Poslano sa mog HTC One S koristeći Tapatalk 4
[HTC One S] Phil3759:
http://teamw.in/DataMedia
[HTC One S] jujusito:
Great work, thanks.

But don't work mount usb storage, thanks.
[HTC One S] luxandroid:
Just 2 post above U didn't read ....

Poslano sa mog HTC One S koristeći Tapatalk 4
[HTC One S] AKToronto:
Curious... Does this mean mounting in recovery would work in Ubuntu? I haven't yet upgraded my firmware but I will once I see some custom kernels. Not sure but it would be a good feature to have on recovery to still be able to mount the portions on a Linux system... Not sure if that is already possible or not... Just a thought.
[HTC One S] Phil3759:
No, not for now
[HTC One S] phoenixita:
Any chance we can get an update that let us flash 4.4 kitkat roms?
[HTC One S] voidzero:
Updating no longer worked for me starting with snapshot M7. I'll see if I can either compile an update, or ask for an update with the ville developer. I have asked for info http://xdaforums.com/showpost.php?p=53405862&postcount=4450here[/URL].
[HTC One S] voidzero:
Sorry for the delay guys, I lost my phone for a while. But I found it back, so I built a recovery, and it seems to work.

Philz version: 6.50.6

CWM: 6.0.5.0

Let me know if you use this, please :cowboy:
[HTC One S] HeXDeMoN:
Can't wait :) as others have said all our recoveries don't work properly and have to use old versions.
[HTC One S] Phil3759:
Sent PM with link to new final v5.00.5

PM were sent to people who gave a feedback about last release

Feel free to request a link by PM, but only if you are going to test and give a prompt feedback over PM

Thanks
[HTC One S] Phil3759:
PhilZ Touch version 5: f feedback through PM seems fine for the most

- Brings mainly a completely revised and more portable touch code

- A true scrolling touch GUI

- A lot of fixes and optimizations

Change log

Download link v5.00.5

http://www.mediafire.com/?9cjuv9ivklh7n
[HTC One S] LibertyMonger:
AWESOME! Looks great man thanks a bunch, trying it now
[HTC One S] alphaeagle777:
Dude thank worked great installing droids AOKP rom
[HTC One S] LibertyMonger:
I just flashed the new ChameleonOS nightly and just a couple small issues at first glance, sometimes have to tap something twice for it to work and back takes back to main menu rather than just prior screen. Other than that it worked great and looks great and love all the features. I think maybe one that is missing is wipe system? But that's no biggy either. Thanks again bud nice work. Glad to see a new recovery!
[HTC One S] RockR172:
Thanks mahn..

Sorry not been able to test and provide feedback about the latest ones, been busy.. :(

Anyway, installing this new version.. :)

Great work here! (Y)
[HTC One S] cicciocant:
How Can I flash it if I come from Stock recovery?
[HTC One S] Phil3759:
Under factory reset you have the option
[HTC One S] rootrider:
Mate, it doesn't check the free space before backing up, does it? Got stuck (as I'm out of enough free space).

Just exiting with error while making a backup image of blabla...
[HTC One S] LibertyMonger:
I meant wipe system alone without losing data for when us crack Flasher's want to just wipe caches and system without data. Thanks

PS... Didn't try to sound critical or picky and wasn't bashing just giving the few things I noticed in case you needed to know Bud
[HTC One S] rootrider:
Yes - the same here.

Let's concentrate on the main things to be done - once they're done, plenty of nice words will follow...
[HTC One S] ryanshew:
Go to mounts and there is an option to format system or any single partition....I remember this from the old cwm.

HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | Bulletproof_1.3
[HTC One S] Phil3759:
CWM never checks detailed space. It just checks you have 150Mb free, for backing up a boot image for example

I could add a more detailed check later, but will never be reliable if you use compression (low setting usually achieves a 30% space spare without being slower)

Yes, in mounts menu you can format any partition you want
[HTC One S] qazsxdcfv:
This is the fa'akin masterpiece !!!!
[HTC One S] Phil3759:
About touch behavior:

Here's an extract from a discussion I had recently. Thought I could post it as this was also much debated when this whole project started for Samsung devices
[HTC One S] qazsxdcfv:
Idk whats this , but i dont have any problems with touch-thing ..

Sent from my hTC One S powered ViperS by Team Venom™
[HTC One S] LibertyMonger:
Yeah ok Bud, I really didn't think of them as "issues" or "bugs" I apologize, I was too quick to give my opinion. Thanks a bunch it's all working fine and will be sticking with it for a while!
[HTC One S] Phil3759:
No need to excuse. It is not perfect, i know. User feedback is important for me
[HTC One S] Sneakyghost:
Hello Phil,

i have been using your work to set up my brother Gnote for a while now. Quite surprised to see you here. Just 5 minutes ago i said on the Viper thread CWM is not maintained on the OneS anymore because Darkwing gave up his port.

Very nice to see some alternative to TWRP here. Thank you, Sir!

[EDIT]

Phil, can i place a request here?

My wife owns one of the very rare One S Special Editions. I had Darkwing looking into a CWM for it already but then he gave up. The thing is, TWRP which is available for it, doesn't mount SD as USB and also can't see some other stuff, so it is very limited to use. I don't think Dees_troy is gonna work on that just because one user asks for it. I am trying my chances with you now. I can provide a RUU, a dump, a stock recovery image and i can already tell you it is mounting SD in \data\media like it is done on the HOX i think. I am not sure where the edits have to be made in order to make it work correctly but after finding out, it should just be minor stuff.

On a sidenote: my wife and i were already going to sell the SE because of its limited development and her not needing the huge storage (she just loves the white) but then again, it was too nice a device to sell so we still have it and plan on further using it. There are a handful of other SE users here but not really that many. So i guess if i request this, it would probably benefit only very few users. Still, it would be nice. Maybe some Taiwan-folks following XDA would find it and take it over to their fora xD

[EDIT2]

Just booted your recovery on my OneS the first time.

First thing to notice: color is still some 16 bit obviously. TWRP changed kernel a while back and is now running RGB_8888 Pixelformat with 32 bits. Looks nicer. Can that be accomplished on the CWM system too? Would that mean you need to change to a JB kernel in that recovery? If so, it might then produce the same Aroma-incompatibilities we see on the later TWRP versions. Hmmm.
[HTC One S] Phil3759:
The Special edition has an sdcard slot?

If yes, I can look at it to mount sdcard in usb mode. I would need some help in testing though to figure the lun path. You just have to access your phone in adb shell and follow my commands for that

About the graphic switch, this recovery is using a prebuilt kernel. We can try putting a stock kernel/ramdisk. It worked for the One X perfectly without users reporting aroma issues

But if it is nly graphics, I thing we need more editing in device tree. Not much sure and mainly, without a device it will be a real pain. Not sure worth it for me

But, I can look at the usb mount thing. Just maybe start making a search about the lun path for your phone
[HTC One S] psylooooo:
In one word, SPLENDIDE ! Thank you very much :good:
[HTC One S] Evil-Monkey:
I'm currently using cwm 6.0.2.9 and although it does check how much memory is on sdcard it doesn't stop a back up from continuing once you've initiated it.

I'm guessing cwm can't "guess" how big your back will be so it only reads you your memory once you initiate the back up process and it back-up up until if can finish or run out of memory. I think.

echó en Android
[HTC One S] Phil3759:
No. It is easy to add but probably i will improve check on backup start rather than monitoring it permanently. But both can be done
[HTC One S] Sneakyghost:
No it's not gotten an SD-slot. I was referring to the SD-partition mmcblk0p36. It is mounted under /data/media and when running any standard firmware on the device, internal storage will be mounted as SD instead and SD will be found in data/media but not have its own /sdcard mount point attached.

If you pass me the commands to run I'll snatch the phone off the missus when she's not watching and check it out for you. She doesn't like me playing with it though as she always fears I'm gonna break it (done it often enough).

Regarding kernel: don't bother. It'll just lead to aroma problems and will probably not be worth the hassle.

mobile post
[HTC One S] Evil-Monkey:
That would be great if the recovery could recognize space before it intiates a back up. One more step to making an elite recovery.

echó en Android
[HTC One S] Phil3759:
I really did not get the issue

You mean her phone has a dedicated extra sdcard partition not part of /data?

If that's the case, fix is really easy under recovery. Under main system though, it will be your kernel you use

I have one question. Does the phone has /data/media storage too in addition to that extra partition or we just need to disable /data/media and enable sdcard on a dedicated partition?
[HTC One S] qazsxdcfv:
This is awesome .. and how to screen shot ..?

Anyone ?:D

Sent from my hTC One S powered ViperS by Team Venom™
[HTC One S] Phil3759:
Slide left for screen shot
[HTC One S] Darknites:
So anyone put it to the test like can it flash all roms without issue? and anybody tried radios and bootsplash?
[HTC One S] Sneakyghost:
Alternatively, you can use ADB and ffmpeg to do that. Check my TWRP theme thread in themes and apps section for exact instructions. Advantage: you can pull pictures right to your pc.

mobile post

---------- Post added at 01:21 PM ---------- Previous post was at 01:15 PM ----------

I'm really not sure how to explain. The One S SE is nearly 100% identical to the standard edition, only difference is the larger storage capacity and how it's being mounted. When running the correct firmware, I see SD just the way I do with the standard one s, but when trying to run e.g. viper on it or a standard RUU, it shows SD as data/media and the internal storage of 2GB (usually used for apps or ram or so) is then being mounted as SDCARD, rendering the device unstable and hard to use.

Maybe you let me know the commands to run to identify how it's exactly set up?

mobile post
[HTC One S] Phil3759:
Well, probably you have true sdcard partition

Attach a stock recovery.img and the special cwm recovery.img they did on purpose for you to confirm it for sure. It should be just a line to change in recovery.fstab file
[HTC One S] Sneakyghost:
Stock Recovery HTC One S Special Edition

Hello Phil,

i appreciate that you show some interest in the matter. That is very kind of you.

Attached you find the stock HTC One S Special Edition Recovery and the TWRP 2.5.0.0 Recovery for the SE. There is no adjusted CWM for it (Darkwing was about to do it but then lost interest when he gave up his OneS).

Product: Ville (unfortunately it has the same product code as the standard, but the RUU's call it Ville_u)

Partition Listing: Thread by AKToronto

Thanks mate.
[HTC One S] Phil3759:
TWRP version works as you want?

From partition table, it is easy to fix the mount point. However, mount as usb can be another story if nothing was added in kernel source at the start.

I will release an fstab fix for mount point first. After that we try to guess the lun mount point and see if it works with small ramdisk changes. If not, i can try to repack with twrp kernel if it is a custom one or your device kernel
[HTC One S] Sneakyghost:
As i initially stated, TWRP does not offer USB mount for the One S Special Edition, plus some other mount option is missing but i can't recall which one it was right now.

Plus, we had the worst of luck today. My wife lost the SE on her commute to work. Some REALLY nice guy found it and has it at his workplace now. I can go and pick it up late at night and if he doesn't change his mind (he left us with no personal details, so he can just eff off if he wants to) we will have it back by tonight. But first he needs to tell us where he is and a time. So, a bit unfortunate alltogether, but on the other hand, thank god it wasn't some damn thief.
[HTC One S] Phil3759:
Good luck. No hurry though. I will first repack with fstab and see if we can find a lun mount if needed
[HTC One S] Sneakyghost:
Thanks. One S SE is back in business. We were really lucky.
[HTC One S] ipit:
Geez, you're a glass half empty person! I'd describe the chain of events (even up to this point) as the 'best' luck not worst.

How would you have described it, if like 99% of lost phones out there, someone had actually stolen it?
[HTC One S] Sneakyghost:
:D

I'm German. People say for us the glasses are always half empty.

A phone that gets stolen is inexcusable and as such doesn't happen. So that scenario is mere theory, right? :D

mobile post
[HTC One S] ryanshew:
Wow, hearing things like that makes me happy...good to know there are still honest people in this world.

HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | Bulletproof_1.3
[HTC One S] jamel_tza:
So I searched the thread to see if this had been brought up already, I didn't see anyone mention it so my case may be an isolated incident.

After flashing this recovery I soon came to discover that the mount usb option didn't work. Soon after that problem I began having problems with flashing ROMs. CWM would say that the installation was complete but skip from about 7% to 100%. This would happen cheifly when going from CM based ROMs to sense based ROMs. After rebooting I kept getting stuck in bootloops, I tried everything, wiping everything multiple times, trying different ROMs etc.

Eventually the phone began rebooting midway through the installation of Sense based ROMs, then eventually began rebooting on the bootsplash image. My last option is to try and revive the phone from the bootloader but after spending hours on it, I gave up for today. Any help would be much appreciated.
[HTC One S] Evil-Monkey:
Hmm. Back in the earlier stages of CWM(AND EVEN NOW) the recovery had a hicup on me. When I would flash "too many" zips. Aka trying mutiple kernels etc.

The symtom was the same everytime. I would attempt to boot into recovery and it would momentarily but just bootloop. Over and over.. fastboot would work but accessing recovery through fastboot would still bootloop.

The recovery would show an error mounting last recovery log then loop, offers maybe 15 secs for you to take action.

What I do (this happen to me a couple of days ago flashing bricked betas)

If its what I think...

1. Try flashing stock kernel in fastboot.

2. Within the first 15 seconds before it starts to loop, initiate a factory/data reset.

3. If its still looping. Intiate wipes like if you were wiping for a fresh install until it stops showing error. Once I had to wipe everything twice before my recovery didn't loop on me.

Eventually, the recovery will not show an error message and you'll be able to restore a back up or try afresh install.

I'm not sure if this will help your situation but this stops the recovery from continuing to loop on you. Not sure what causes it but I'm sure a higher savvy person can chime in maybe.

echó en Android
[HTC One S] Phil3759:
As you maybe know, recovery uses prebuilt kernel for many HTC devices

That kernel could be old and not well suitable sometimes, maybe on new devices with new board revisions. It is a theory though, but was the case for One X

If you have confirmed issues, and many report it on such devices, upload a the most recent recovery.img for your ville phone and I will repack around its kernel

But again, I won't do until it is confirmed by others
[HTC One S] ryanshew:
I had that happen to me just now. Like 10 mins ago.

I tried fastbooting recovery, then boot.img, a few times over again...I was just about to give up and flash an ruu.

I ended up just doing fastboot erase cache, then fastboot recovery and all of a sudden it started working.

Maybe a cache issue?

HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | Bulletproof_1.3
[HTC One S] Evil-Monkey:
Not sure, but wouldn't doubt it. When I was scrambling around and realized I had a small window to do something. I first reflashed recovery too, but not luck. Tried twrp, still bootlooped. So I cleared cache, then dalvik, and then factory/data with bootloops happening in between. But For sure factory/data reset fixes it for me. But I've also had occasions where cache/dalvik fixes it but more often I have go down the line to factory/data reset and sometimes run it twice before it boot properly.

Fastboot Erase Cache might be the end all fix though since wiping cache through recovery at the time its showing "error" is hit or miss from my experience.

I got so used to just wiping the phone everytime that I haven't even given that a try. But next time it happens I will for sure check fastboot erase since Im now comfortable everytime it happens, its just time consuming lol

echó en Android
[HTC One S] ryanshew:
Let me know if that works next time.

Just for future reference, not sure if related, but I had just finished using aroma/bulletproof zip.

HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | Bulletproof_1.3
[HTC One S] Sneakyghost:
Couldn't it rather be some stuff happening in the recovery when flashing aroma based zips like with the newer TWRP?

I mean that comment saying it jumped from 7% to 100% sounds exactly like it. With viper, 7% stage marks the system write and it is obvious that aroma cannot write to system (note: aroma, not the recovery) or do the write call correctly so it just fails. It also doesn't throw helpful error messages.

People had been so far too say though that aroma is incompatible with the newer (probably jb based) sense kernels.

Now: did you guys have those problems with aroma zips or with normal zips?

[EDIT]

I'm a bit bored today, so i'm going to play with this a little. Will report back if i find anything interesting.
[HTC One S] touch of jobo:
I have seen that happen once or twice too.

..and that was what fixed it for me.
[HTC One S] Sneakyghost:
So you reckon its rather not that nasty aroma bug?
[HTC One S] qazsxdcfv:
Woops .. i can flash Viper with this recovery .. and im not Noticed any problems .. so .,

Bloody hell , .. :confused:

Sent from my hTC One S powered ViperS by Team Venom™
[HTC One S] touch of jobo:
No. When recovery fails to boot, or when it boots but quickly / almost immediately crashes and/or reboots, Aroma is not even involved.

Aroma might be involved in getting into that situation in the first place tho. I don't know. Maybe a failed fastboot flash can leave cache in a bad state, but thats just speculation..

Either way, when I got into the situation where recovery would boot and then crash/bootloop, fastboot erase cache would fix it for me.
[HTC One S] Evil-Monkey:
Maybe, Its definitely something all the zips had in common. But its happened on every single cwm recovery I've had. If you really want to duplicate it, try messing around with a couple kernels within a short period of time. That's what normally causes it for me.

echó en Android
[HTC One S] qazsxdcfv:
So the culprit is the "cache" ..

Your speculation maybe right ..

Sent from my hTC One S powered ViperS by Team Venom™
[HTC One S] Sneakyghost:
Installed Viper 2.1.0 without issues

Installed Viper 2.2.0 OTA without issues.

==> booted each time into full system without errors.

Installed ElementalX and ran into constant bootloops like you guys described.

==> fastboot erased cache before and after ElementalX Flash, cleared cache and dalvik cache additionally. Set aggressive, then safe, then stock values in ElementalX. Nothing. Always crashing the recovery, always bootlooping.

Observation:

- When ElementalX finishes and i wait before pressing the next and reboot buttons, Recovery crashes out of Aroma.

- When i hit those buttons fast and exit Aroma, i can sometimes catch a glimpse of "E: unable to mount / umount blahblah" in recovery before it eventually crashes, but its always too fast so i can fully read it, sometimes it doesn't even show.

I have to apologize because i read the previous page with the initial problem description only fast while at work and underways, so i didn't quite get the issue. I now understand the issue is a recovery crash after flashing a zip. Sorry again.

I can fully reproduce on ElementalX installer, yet not on Viper zips.

[EDIT]

when going back to TWRP to restore my nandroid I faced the "E: unable to mount cache" issue again. I couldn't wipe cache for the life of me. I then decided to try a restore anyway. It worked and it formatted cache. Afterwards, I could then also wipe cache again.

So, when running elemental installer on CWM, it somehow breaks /cache.

Elemental installer runs fine on TWRP, but there, the viper installer has trouble.

I get the impression that we either have to deal with an odd aroma problem (yes! I still believe it) or with an issue with the One S partitions themselves.