yashsingh1/xdaforums huggingface dataset:
[HTC One S] driz:
Moonshine requires being in the OS with debugging enabled; unless you know what it does in the background and i can manually do it... that being said; when i flashed the RUU, i did not lose s-off or supercid, i only lost my custom recovery. To clarify, i am running the RUU once i fastboot oem rebootRUU

I went in and formatted all; now aligning partitions... can you expand on this, to me this is what i do when building oracle boxes prior to partitioning, i've never had to do this on an android before... I have search to find the partition tables and not seen anything reliable enough to play with my partitioning. I can only adb shell from recovery since i can't full boot, so im a little limited.

The phone did work; the only reason i changed the hboot was moonshine puts that .4444 hboot which was messing with my CM since it checks now. I am running hboot 2.15. Let me know if you have any other suggestions, im to the point where without doing something to the storage, i can't think of anything else. I was under the impression that the RUU would reset my partitions...

I see you live in charlotte, much nicer than fayetteville :)
[HTC One S] nicknc:
Yeah, Charlotte is much nicer than Fayettenam. Go guard like I did and you can live here too. :) If you are AA, I guarantee you've jumped out of the plane I crew chief several times :)

Well, before we go any further, my phone is .4444 hboot, and outside of the "normal" bootloops and data drops that are affecting everyone, I have had no problems using CM10.2. So that's curious that it was blocking you and not me....

Did you flash the RUU through fastboot, then, or did you run the exe? I ran the exe, and I could have sworn it put a stock hboot and S-ON'd my phone after it finished.

Well, I can't seem to find the option to align the sd-card partitions on TWRP-- I know it's on 4EXT (which isn't compatible with this phone), so sorry about that. If you formatted the SD-card, then I guess that's all you can do.

So where we are at is it seems like you can boot stock RUU, which means your internal storage (not internal sd-card) is working. So we are trying to fix your internal sd-card, which appears to cause android to spaz out and reboot when it accesses it. Does that sound right?

Did you format your SD-Card after flashing the RUU or before? If it was after, then try doing the RUU again, this time running the exe (if you didn't do it that way before).

I'd like to see if we can at least get you back to the Moonshine-supplied hboot and then go from there. You might want to S-ON your phone again once you get the stock RUU running so you can make sure you have completely retraced your steps from how you received your phone.

Don't give up yet-- I think you'll fix it-- this phone is just godawful finicky.
[HTC One S] driz:
once AA always AA man, ill stay until i retire :)

For the RUU; i did a fastboot oem rebootRUU, then i ran the exe. I did not format the sd-card after running the ruu, ill reload twrp, and format sd and see what happens. Thanks for sticking with me through this :) Ill report back in a few
[HTC One S] nicknc:
My little brother just went Army aviation, but hopefully I can swing him over to the "smart" side in a few years ;)

You got me for another 40 minutes or so, then I got to head on for the night. Just keep trying to put your phone back to as stock as it can be to start over. That's the only thing that shook mine loose in the end.
[HTC One S] driz:
Just tried formatted sdcard and booting; same issue, bootlooping again. I'll try to return to stock and see what happens. I might just wait for the 15th and get the nexus 5 :(
[HTC One S] nicknc:
Nexus 4 has plenty of problems with CM10.2, and you'll deal with the same with the GN5. This phone flies once it's running.

Just get back to 100% stock and then we'll see how it looks.
[HTC One S] mannequin:
not sure what are you trying to do here people. CM is "done", for this device especially.
[HTC One S] el_smurfo:
Done? You don't think we'll get 4.4? I'm not a fan of the way the top two in CM Inc are behaving, but there are enough 8960 devices around to make it worth their while to keep it supported. Your comment is a slap in the face to all the hard work Ethan has done for us prior to this point.
[HTC One S] Aktivehate:
Indeed, Ethan has done some great work for all the 8960 based devices over the last months, look at the data drops, the wake issue, nearly everything is fixed or nearly fixed. Also there are still new features build into CM for our devices like the brightness for the hardware keys and vibration strength. So no, i rather would say the One S is more than alive, even better supported than HTC does....
[HTC One S] kant1988:
I have hboot 2.16, using Maximus 10 with 4.2.2. S-on.

Can I flash CM10.2 on hboot 2.16 ?

Any help or tip ?
[HTC One S] nicknc:
http://xdaforums.com/search.php?searchid=223817165
[HTC One S] yz250il:
I cant play MP3 files with Poweramp , with Apollo i have no problem.

I'm on the 09/28 build.

is that known issue?

Thanks..
[HTC One S] nickmv:
No, it'll be F'd up due to partitions being redone in Maximus with the firmware.zip they provide.

If you already flashed into Maximus and were ran that firmware update, you need to do the following. This assumes you S-OFF'd and have SuperCID:

1. Go back to bootloader

2. Flash the firmware from the guide here (that's the 2.15 hboot version for CM roms)

3. Factory Reset from bootloader ---> requires hard manual reboot into bootloader afterwards

4. Clear storage from bootloader ----> requires same manual reboot into bootloader

5. Flash recovery

6. Flash CM roms, etc,

7. Good to go.

In my case I had TWRP backuped my old setup, so instead of flashing a rom, I selected Recover.
[HTC One S] kant1988:
But I s-on with hboot 2.16, Maximus Rom , i can't s-off ?
[HTC One S] nicknc:
2.16 changed the partition structure of your internal storage. In other words, the partitioning created with 2.16 is vastly different than it was with 2.15 and below.

CM10.2 is not able to install correctly on this new partitioning. It might be fixed in the future, and it might not.

You

cannot

currently install CM10.2 on hboot 2.16. If you can't S-Off and back down to sub-2.16 hboot using the steps nickmv listed above, then you are stuck.

It has nothing to do with ROMs, Sense vs. AOSP, S-off, or anything else. It is a

partitioning

issue.
[HTC One S] nickmv:
Yep, essentially it repartitioned /data to be the new "sdcard". Basically, sdcard partition is actually a fake emulated partition that resides within /data, in order to keep up to date with how Android works nowadays. In the end it's for the better, in terms of performance and file transfer improvements. Or at least that's what I understand it to be.

But at this time, CM 10.2 doesn't work that way on this device, so unless you can S-OFF and reflash back down to 2.15, you're just out of luck. If that's so, I recommend you re-flash Maximus with Sense removed and run an alternative AOSP-style launcher like Apex.
[HTC One S] Phuturist:
Yes it is. Workaround for me is do a full library scan within Poweramp and reboot the phone. After that it recognises the MP3 files again. This workaround has become a pain in the ass with the current reboot issue though if you get stuck in a reboot cycle.
[HTC One S] nickmv:
I'm on the 9/18 build still. Is there a build since then that's worth flashing? Seems like most feedback I've seen since 9/18 has been somewhat negative, with various things breaking, boot loops, etc.

9/18 seems pretty stable, other than the occasional loss of volume button and power-button-menu function.
[HTC One S] nicknc:
For those who are having data drop / data cycling issues with this ROM, the following thread helped me:

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

Basically, just add the following to your build.prop:

ro.ril.hsdpa.category = 24

ro.ril.hsupa.category = 6

ro.ril.hsxpa = 4

ro.ril.fast.dormancy.rule = 2

For me, the dormancy rule was present and set to 1. The other three lines were not present, so I added them.

Supposedly it helps out with H speed as well, but mine didn't change.

---------- Post added at 04:26 PM ---------- Previous post was at 04:21 PM ----------

Yeah--- I flashed the latest PAC-MAN rom. That took care of the bootloops for me. lol! It's not bad, even with that stupid PIE thing that gets in the way.

There's a discussion on the bubba kernel thread, I think, where a couple of the devs mention that a commit needs to be pushed to CM to fix the bootloops. Don't know if it will.

Supposedly bubba kernel doesn't have bootloops, but they also said it's not working with the latest CM10.2 nightlies, so ymmv.
[HTC One S] nicknc:
Never mind, after going all day (and doing manual reboots intermittently through the day), I got a bootloop on Pacman ROM.

Back on CM now, will continue to test the build.prop edit. So far, I have not had a single data drop, despite transitioning between towers.

It may be necessary to change the fast dormancy value to 0 (not sure if T-Mobile supports it in my area yet), but from what I read, all having it at 2 would do is cause a battery drain.

---------- Post added at 09:58 PM ---------- Previous post was at 09:49 PM ----------

Have you looked at this? http://xdaforums.com/showthread.php?t=2086156

It's for folks that have corrupted the "sd-card" portion of internal storage-- sounds a lot like what you are experiencing.
[HTC One S] el_smurfo:
Fast dormancy 2 works well for me also, but 0 gives no signal at all. Really the first build prop mod I've made that has actually had a definite effect.

BTW, these bootloops suck. Any time I reboot, it's 5 minutes of fighting the thing to shut it down and boot properly. I think Intervigil being hired by Inc may mean his attention is on bigger things like the oppo phone :(
[HTC One S] nicknc:
Thanks for the info on 0 value. And yes the bootloops are just a huge pain in the ass.

I tried reverting back to CM10.1 stable and even got them there, makes no sense to me at all. The data drop is the bigger issue, and it's encouraging to hear it fixed it for you.

If it weren't for the trouble free Bluetooth, accurate GPS, and great performance of this phone, I'd be regretting letting my Sensation go. Build.prop edit ironically fixed an 18 month data drop bug on that phone too. Much worse bug, when it went down, it would have no data for days.
[HTC One S] bluebenno:
10.2 builds work for me

I've been using the bleeding edge 10.2 builds for a while, currently '27. They have all been reasonably stable, I get one boot-loop a week and have no data issues.

..Maybe I'm lucky or the networks here are so crap that I'm not affected!
[HTC One S] djsubtronic:
One bootloop a week is still pretty bad :(
[HTC One S] yasser_de72:
Hi. is there anyway to run this rom with s-on?

my phone briked in with hboot-2.16 and s-on...
[HTC One S] djsubtronic:
Unfortunately you won't be able to run this ROM with 2.16. But you might as well try flashing it anyway and try to regain S-OFF using Facepalm or Moonshine so that you can downgrade to 2.15 again.
[HTC One S] yasser_de72:
i dont have any rom on my phone. my phos was bricked. it is on hboot2.16 and s-on , sdcard not mounted and i have not any access to sd card for downgrade to 2.15 or installing ruu or any rom...

please help me :(
[HTC One S] el_smurfo:
10/1 up...still bootloops like crazy, so it you're stable, don't bother.

---------- Post added at 09:53 AM ---------- Previous post was at 09:43 AM ----------

BTW, take back what I said about fast dormancy 0...it seems every time I boot after bootloops I have no cell reception. This time, it happened with the default setting of 1.
[HTC One S] WCCobra:
Maybe we will get a stable version before the Nexus 5 is release. Keep your fingers crossed.
[HTC One S] nicknc:
I always have up to a minute of no coverage after booting (at least until it recognizes the sim), but maybe you're talking about something different.

Well, I did my commute today with the fast dormancy set to 2-- I had 1 data drop all day. It was exactly the same as before--> data stalled, dropped to 3G, bumped briefly to H and then dropped altogether before restoring over the course of about a minute.

That was with 10/01. I can deal with that-- for now.

I'd be interested to see if only T-Mobile folks are having that issue. Perhaps it has something to do with the ongoing network upgrades, which would explain its sporadic applicability across various devices.
[HTC One S] maluus:
Just to inform. Until todays nightly I was having bootloops after flashing the room. need to wipe dalvik/cache to boot the phone. sometimes I had to do it a few times. but todays nightly flashed and booted without problem and never had neither a data drop nor signal loss. this may indicate that it's related to operator or simcard. if is there a way to test it I may help.
[HTC One S] nicknc:
I got two more data drops and a ton of bootloops this evening. The build.prop edit has helped, but not resolved. I wonder if the skipbrokendatacall switch would work for these data drops.

I think I might move to Sense 5 for awhile.
[HTC One S] :
I thought HTC chose to not supply the One S with the Sense 5 update? Or are you talking about a sense-based custom rom?
[HTC One S] fusk:
what radio is recommended with 10.2 or does it update that auto when flashing new ROM?
[HTC One S] el_smurfo:
If you're running 10.2, you've likely applied an RUU or firmware patch that will bring your radio to nearly the latest. 1.13 for TMOUS works fine for me. BTW, flashing ROM no longer flashes radio...it uses the radio loaded into the firmware partition.
[HTC One S] fusk:
well, then I'm still using the radio from 10.1 as I haven't updated for at least 6 months. updating the kernal for 10.2 is the only additional flashing I've done.

I don't know what tmous is, but maybe you can link me in the right direction?

edit. I'm running 1.11.50........8L
[HTC One S] maluus:
I'm using 1.15 eu. No data drop or signal loss as I stated above post. Never edited build.prop either.

edit: another thing to add; since 20/09 there was a hardly perceptable but disturbing glitches on the ui during page transitions in the app drawer or scrolling the pages etc. so I was using 20/09. but on this nightly it seemed to be disappeared.

Enviado desde mi One S usando Tapatalk 4
[HTC One S] nicknc:
Yeah-- that's what I meant. I forgot it involves going to hboot 2.16 and losing sd-card mount in recovery.

Pardon me if I'm a little hesitant to sever the only link I have to a bootlooping unstable phone right now. :rolleyes:

I guess I'll see if I can back down to CM10.1-- hate to do it, but it's clear fixing these two glaring issues is not a priority at CM right now, what with all the more important commits, like adding 20.7 MP resolution to the camera and removing text from menus on the cities screen....
[HTC One S] el_smurfo:
I have to sadly agree. All the CM inc drama mostly just made me feel a bit sad about the way the two principles were behaving, but its obvious that the priority for Inc will be paying platforms and difficult devices like ours will likely be shuffled to the side while buggy bloat like Voice+ and CM account are added. I think what has been done to get 4.3 on this device is awesome, but the week of bootloops on this and similar devices has me worried.
[HTC One S] nicknc:
Well, I'm stuck with 10.2, damn it. Can't restore my data into 10.1 (just causes never ending booting-- not bootloops). Can't figure out why. It takes me a good while to set up my phone again, and I don't have time for it. Further, I can't get Bubba's 3.0 kernel to work with 10.1.3, but his 3.4 kernel will.

I actually use Voice+ and love it-- the GVoice app is horribly unreliable and not very intuitive.

So, I guess bootloops and data drops are here to stay for me-- wonderful.

Going to switch my fast dormancy to 0 and add "ro.ril.radio.svn=19". It was suggested in the maximus forum that that helped resolve data drops for some.
[HTC One S] el_smurfo:
Are you soff? Son need to flash boot.img to restore nandroid
[HTC One S] nicknc:
Of course I'm S-Off-- I like to use my phone :)

CM10.1 will boot just fine-- until I do a restore, that is. I tried all different combinations. Bubba 3.0 kernel will not progress past htc white screen (just bootloops there) Bubba 3.4 kernel will boot in, but has bootloops and screen tearing. Both of these I just confirmed on a clean flash of 10.1 with no data restore.

I can only get CM10.1 to boot with stock kernel, and no data restore. Oh well. I restored my nandroid for 10.2 and made the build.prop edits. Will see if it makes a difference and let you know.

You said fast dormancy 0 and 2 both resolved data drops for you, right?
[HTC One S] el_smurfo:
Can you clean flash 10.1 then restore?

Build prop seems to give better stability, but I don't really have permanent data drops....
[HTC One S] nicknc:
Yeah that's what I did. Clean flash then restore. It won't boot-- just sits on CM loading screen until, I assume, the government (sort-of) shutdown ends....

Either way, I'm back on CM10.2. It's gotta be some setting in that backup that isn't translating correctly to CM10.1. No big deal.

I don't have permanent data drops either-- just that stalling out thing that restores itself over a minute or so.
[HTC One S] djsubtronic:
Not on the latest nightlies but I seem to have cured the bootloops by disabling services. Have tried reproducing numerous times in ways described here as well as ways that I got a 100% bootloop previously, and it seems stable as a rock. I'm using the 5th Sept nightly, I don't think there have really been any changes that I'd care about since then.
[HTC One S] mannequin:
that's because Play Services boot loops are different to the issues that came after 09/05. these heavy reboots, boot loops, getting stuck on boot animation etc are more likely kernel related.
[HTC One S] djsubtronic:
I never seemed to have them up to 24th Sept, and people were reporting heavy bootloops then too. I wonder if it's hardware related.
[HTC One S] nicknc:
Mine are completely sporadic.

What's more likely is that folks that flash more nightlies get higher probability of bootlooping.
[HTC One S] phoenixita:
Those bootloops are kernel related and reverting the kernel to 3.4.60 fixes it. but it brings lockscreen delay...!
[HTC One S] fusk:
Then I'm still using the radio from 10.1 as I haven't updated for at least 6 months. I'm running 1.11.50........8L

How do i update ?
[HTC One S] bunga bunga matze:
You have two Options:

1. Save and clean:

You have to relock bootloader, than flash the latest ruu!

After that boot the device and make OTA update,

Then go to htc and unlock the bootloader again, install recovery and after that your rom, voilà....

2. quick and dirty:

Second method is to search the latest OTA, i have seen it as flash-able file in the internet...

I dont know the installation procedure, because I took the first one (tooks me 30-40min)

Good luck
[HTC One S] pirlano:
OTA blocks s-off exploit

I suggest to s-off without updating with latest OTA and update the firmware only (that can be found in Development section)
[HTC One S] el_smurfo:
Oct 2

Couple kernel commits in today's nightly build. Anyone try? Took me so long to get it to boot yesterday, I don't have time to try this morning...
[HTC One S] Michael1101:
I'm downloading right now. By the way, yesterdays nightly booted fine for me. And no bootloops. OK it was only one day...

Edit:works fine on my phone.

Edit2: I can't remember if the stuttering in the music playback when I turn on the screen was there in the latest nightlies or was it fixed by ethan with the screen on delay fix? Long story short, no stuttering in music playback in 10/2 nightly.
[HTC One S] nicknc:
yesterday's nightly booted fine for me as well-- until this morning where it abruptly rebooted while I was listening to xbox music. It never came back up (just hangs on the CM loading screen w/o bootlooping).

Maybe we should complain about

booting

, not bootloops, if this is the fix for bootloops (they're technically gone, I guess).

Will try today's nightly and report back.
[HTC One S] el_smurfo:
Reboot-a-thon for me. Still trying to get past optimizing apps. Took about 5 minutes of on/off/on/off yesterday to get it up.

EDIT: Got it running. Changes to button function seem to make the button settings menu FC settings. I have noticed that long press home from lockscreen now has the option to lock device...convenient way to extend the life of your power button.
[HTC One S] Lone Shepherd:
Seen this mentioned a couple places. I saw the CM, Inc announcement and thought it seemed pretty well-received in the community. What drama and behavior are you referring to?
[HTC One S] Phuturist:
Just flashed 20131002 and for the first time since about a month it booted without issues. Also a second reboot didn't result in bootloops. Never experienced random reboots fortunately.

The issue with poweramp that has been mentioned a couple off times remains however. But workaround (scan library and reboot) is good for now.
[HTC One S] justaway2:
I'm still having problem booting the 10/02 build. It rebooted once at the spinning logo boot animation and also at the optimizing apps screen.
[HTC One S] el_smurfo:
I get my best results holding power button until it's completely off, then powering up from there.
[HTC One S] justaway2:
I normally do that as well, but sometimes that still fails.

It eventually booted successfully, but took about 4 tries. I think that's about average for me.
[HTC One S] nicknc:
I went back to 09/03, which wiped all my shortcuts off the desktop (hooray) and then updated to 10/02. Bootloops, of course. Data seems to be holding up still with fast dormancy set to 0 and the extra build.prop value I mentioned in a previous post.

I expect to get a few data drops, but hopefully nothing like before the build.prop edits.
[HTC One S] cannondale0815:
In order to get traction on some of the issues, I'd think the official CM forums are the best place.
[HTC One S] Dave77459:
Downloaded the 1002-NIGHTLY and installed using Flash Image GUI + recovery. This time I didn't wipe cache or Dalvik in either place. I got one reboot during the spinning circle, and held VOL DOWN right away until I got to the bootloader. I asked to go to Recovery, because I wanted to wipe cache and Dalvik. Instead, after a long wait at the HTC white screen, it went to the spinning circle, then upgraded apps. I ignored it for five minutes and found it was operating normally.

Seems a little easier. Maybe it was the ignoring it?
[HTC One S] el_smurfo:
CM Forums are a ghost town...sometimes a week between activity there in the Ville Nightly forum. Intervigil may be stuck on the N1 for a bit, but at least he seems to log on here nearly every day...
[HTC One S] cannondale0815:
Thanks. So this thread here is the best way to let the CM guys know about issues with their nightly builds then?
[HTC One S] Brushstroke:
Either here or their Google+ page.
[HTC One S] el_smurfo:
I find their G+ community a disaster of theme screenshots, Inc ranting and generally dumb questions...but at least it's prettier than XDA ;)
[HTC One S] fusk:
Save everything and clean seems like such a hassle.

Quick and dirty i don't know how to do.
[HTC One S] Brushstroke:
Latest nightly couldn't detect my SIM card. Anyone else experiencing this?
[HTC One S] nicknc:
Read back-- another guy had a problem like this. Did you reseat it? Try reflashing? On latest radio?

---------- Post added at 10:50 PM ---------- Previous post was at 10:45 PM ----------

Hey, smurfo-- could you try disabling KSM and purging of assets?

I disabled both on a whim (Sensation used to have reboots due to memory issues), and haven't had a bootloop since doing so (and I've tried :) ).

I was getting bootloops on 10/02 before that.

Also, after adding that ro.ril.radio.svn=19 portion to build.prop, I haven't gotten a data drop. Will update on that if I do-- otherwise, that might be the fix.

Lock screen lag is back on my phone with 10/02, but I don't care about that. Also, got a goofy call situation, where I couldn't answer it via my car's bluetooth, but again, that is small potatoes.