Develop Bugs

Ready to flash from stock for 1st time but few questions.

Hey everybody.
I used to flash all sorts of roms on my old galaxy vibrant but I bought a new t989 a few months ago and I want to go to a custom from the stock tmob bloatware infested ICS. I already rooted via odin and installed clockwork recovery, which comes up just fine with the usual volume and power combo so i'm good there.
My question is should I flash my first rom (probably jedi mind trick 5 or x1,or if anyone knows a daily driver ready jelly bean??)
via clockwork mod like on my vibrant? or do I use twrp which I also have via goo manager? I prefer cwm because I am familiar with how to wipe cache, reset and flash with it but I can't figure out why some mods recommend one or the other.
Also,
I keep seeing some roms that come with a radio zip and was wondering if all roms require this or is it just certain roms?
Thanks in advance for any help. I just don't want to wreck my phone the first time. Remember, I've flashed a million times on my vibrant but never on my t989 so any pointers or heads up would be appreciated.

Get darkside wipe scripts (both wipe cache and super wipe)
Go ahead with the Jedi X1 ROM its very stable and fast as hell
But if you want Jelly Bean I recommend Galaxy SBean v8 or Liquidsmooth rc8 they're the most stable JB ROMs from what I experienced
Remember to always wipe dalvic cache and fix permissions (darkside cache wipe) after flashing a new ROM
After you flash your ROM and Gapps then boot that's when you can flash kernels, mods, and apk's so it would have a lesser chance of a soft brick
Happy Flashing!
Sent from my SGH-T989 using xda app-developers app

arthurgreeeen said:
Get darkside wipe scripts (both wipe cache and super wipe)
Go ahead with the Jedi X1 ROM its very stable and fast as hell
But if you want Jelly Bean I recommend Galaxy SBean v8 or Liquidsmooth rc8 they're the most stable JB ROMs from what I experienced
Remember to always wipe dalvic cache and fix permissions (darkside cache wipe) after flashing a new ROM
After you flash your ROM and Gapps then boot that's when you can flash kernels, mods, and apk's so it would have a lesser chance of a soft brick
Happy Flashing!
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Cool. Thanks for the reply. I went and grabbed super wipe and cache wipe. So essentially, I just put those two on my sd and flash like I do a rom zip from recovery and then flash the rom itself and do a darkside cache wipe after new rom is installed before restarting and booting for the first time? Do I still need to do factory reset/wipe or is that part of the scripts? I have the goo app so I can use twrp instead since it's recommended for almost all roms I will be installing. Any major reason why, besides that it has touch function and backup renaming? Is it safe to install from the goo app on stock rom?
I think I will probably try one of the jellybean roms you suggested. I just didn't want random reboots, and I heard that's an issue with jelly bean roms but I think that might have been specific to aokp ones or something. Occasional FCs aren't too big of a deal though.
One other thing though... how do I fix permissions? I kept reading about that but never did it. Do you mean in recovery or under superuser?

how to properly flash a rom
http://forum.xda-developers.com/showthread.php?t=1926754
just follow that and you should be fine.
you can fix permission in recovery. its under advanced in cwm and twrp.

merrygocow said:
how to properly flash a rom
http://forum.xda-developers.com/showthread.php?t=1926754
just follow that and you should be fine.
you can fix permission in recovery. its under advanced in cwm and twrp.
Click to expand...
Click to collapse
Ok thanks. He seems to recommend not using the darkside scripts. I have a slightly older CWM 5.0.2.6 that I did via odin BTW so do I fall into the 'don't' use darkside category or does he mean anything after 5.0.2.7? I don't mind wiping cache and dalvik manually and doing all the formats if that's the case.
Do I fix permissions after I have booted the rom and waited 10 mins and restarted back into cwm or before I boot it for the first time?

benjmiester said:
Ok thanks. He seems to recommend not using the darkside scripts. I have a slightly older CWM 5.0.2.6 that I did via odin BTW so do I fall into the 'don't' use darkside category or does he mean anything after 5.0.2.7? I don't mind wiping cache and dalvik manually and doing all the formats if that's the case.
Do I fix permissions after I have booted the rom and waited 10 mins and restarted back into cwm or before I boot it for the first time?
Click to expand...
Click to collapse
I usually do it after flashing. And you don't need to do it every single time. Also, there's no need to follow everything down to the letter when you flash, wipe cache/dalvik/factory reset/wipe system/fix permissions/sit for 10 mins/reboot/reboot again/etc. Flashing is like cooking. As long as you don't deviate too much from the recipe, you'll get edible food (or a working ROM). If it doesn't work out, just toss the food out and try again (softbricked phone, reflash). If you try something stupid, you'll set your kitchen on fire when you don't have insurance (comparable to hard bricking your phone).

I usually wait till I've restored all my apps before fixing permissions, and then sometimes I don't if everything is working fine. As for recovery, I know you're familiar with CWM, but I'd recommend spending some time using TWRP. It's really great. You don't need the scripts with TWRP, but since TWRP lets you cue up zips, you can set it to do super wipe, ROM, gapps, and cache wipe all in one go. Kinda cool. And if you're itching to try jelly bean, AOKP JB milestone 1 is stable and smooth. There are even a couple custom kernels for it and CM10 (which has also reached a stable version, though I haven't tried it).
Sent from my beastly Galaxy S 2.

Dark side super wipe and cache wipe work perfectly on 5.0.2.6! That's how I got PACman ROM on my phone. I didn't bother with fix permissions. Well, I would say don't worry unless the instructions specify to do so.
Either way, I like CWM because I used it on my Samsung Galaxy Ace. Its just the wipes are broken for this phone so the scripts have to be used and work perfect. Happy flashing!
Sent from my SAMSUNG-SGH-T989 using xda premium

benjmiester said:
Ok thanks. He seems to recommend not using the darkside scripts. I have a slightly older CWM 5.0.2.6 that I did via odin BTW so do I fall into the 'don't' use darkside category or does he mean anything after 5.0.2.7? I don't mind wiping cache and dalvik manually and doing all the formats if that's the case.
Do I fix permissions after I have booted the rom and waited 10 mins and restarted back into cwm or before I boot it for the first time?
Click to expand...
Click to collapse
no it's fine to use the scripts w/ cwm 5. just don't use the scripts on cwm 6. that's what he meant.
i usually fix permission after the first reboot & waiting 10-15 mins.
i second the twrp recommendation...however if you're flashing something old, then cwm is the way to go. i haven't had any problems flashing anything in cwm. the latest twrp however failed me after i tried to flash a gb theme for jugg lol.

merrygocow said:
no it's fine to use the scripts w/ cwm 5. just don't use the scripts on cwm 6. that's what he meant.
i usually fix permission after the first reboot & waiting 10-15 mins.
i second the twrp recommendation...however if you're flashing something old, then cwm is the way to go. i haven't had any problems flashing anything in cwm. the latest twrp however failed me after i tried to flash a gb theme for jugg lol.
Click to expand...
Click to collapse
Ok, just wanted to make sure on that one.
Thanks for all the input everybody. Hopefully I will get a chance to do my flash over the holiday. I plan on going with the Sbean V8. Really all of the roms out look excellent but this one looks good for a JB daily driver. I went ahead and downloaded Jedi X1 too though in case the sbean doesn't work out for whatever reason. I have to tether my phone at home for internet so I thought it might be good to have a backup just in case PDAnet doesn't want to work.
Is twrp ok to install from Goo manager on my stock rom or should I flash a new rom and then use it from then on? I just want to make sure it won't conflict with the stocker or the CWM that I have on it already.

benjmiester said:
Ok, just wanted to make sure on that one.
Thanks for all the input everybody. Hopefully I will get a chance to do my flash over the holiday. I plan on going with the Sbean V8. Really all of the roms out look excellent but this one looks good for a JB daily driver. I went ahead and downloaded Jedi X1 too though in case the sbean doesn't work out for whatever reason. I have to tether my phone at home for internet so I thought it might be good to have a backup just in case PDAnet doesn't want to work.
Is twrp ok to install from Goo manager on my stock rom or should I flash a new rom and then use it from then on? I just want to make sure it won't conflict with the stocker or the CWM that I have on it already.
Click to expand...
Click to collapse
--Update--
I got Sbean v8 installed and working just wonderfully! I used CWM for my install with the darkside superwipe and cache wipe scripts. Everything went fine and i'm very happy with the new rom. Thanks everyone. I hope this thread will help any other first flashers in the future.

CM10.1 Freezing issue and message not sent error.

Hey guys,
First post here,
i was searching around for my problem, and i haven't found an accurate answer so thought to share my problem and hopefully find an answer.
i am from Canada, Edmonton, and i am with Rogers.
First problem,
i run CM 10.1 and Most the NIGHTLY updates they were butter smooth and works great, until Update number CM-10.120130317 till the current update. All the updates i download, my phone freezes LOT! example of how it freezes , i try to unlock my phone, it freezes . I try to write something it freezes . and sometimes when its on sleep it freezes i can't turn the screen on again! so i always downgrade to CM-10.120130316 to have that stable ROM.
I did the wipe date /factory reset from the ROM manager, and wipe cache and dalvik. and yet the problem is not solve.
So my question is, dose anyone facing the same problem? or it's just me?
Second Problem
am having this beyond annoying notification, where it says my message has not been sent! but my message get's sent and all acts normal. But i always get notification and its never gone. I have screen shoot the problem. Is there a way i can fix this? i've have attached in the thread.
if you guys have any questions or want me to provide some information please do ask.
Looking forward to hear the feedback.
Cheers,

for starts, you're running nightlies and you need to remember that. i'm not an advocate of these, but thats just my opinion. you generally cant run a non-perfected piece of software and repeatedly dirty flash layers of updates on top. you will generally begin to experience bugs that can only be fixed with a full wipe and clean install.
that being said, i would either 1) commit to these cm10.1 nightlies and perhaps even just stick with 1 of them thats working well for you or 2), find a stable 4.1 or 4.2 rom and install after a full wipe. backup first.

There's a warning that these builds are unstable and use them at your own risk. I use cm10.1 20130317 build and it is extremely stable. A few quirks but nothing major. I plan on sticking with it since the 3.4 kernel on the newer nightlies isn't optimized yet, which result is lower battery life.
Sent from my SAMSUNG-SGH-I747

xBeerdroiDx said:
for starts, you're running nightlies and you need to remember that. i'm not an advocate of these, but thats just my opinion. you generally cant run a non-perfected piece of software and repeatedly dirty flash layers of updates on top. you will generally begin to experience bugs that can only be fixed with a full wipe and clean install.
that being said, i would either 1) commit to these cm10.1 nightlies and perhaps even just stick with 1 of them thats working well for you or 2), find a stable 4.1 or 4.2 rom and install after a full wipe. backup first.
Click to expand...
Click to collapse
Domoo said:
There's a warning that these builds are unstable and use them at your own risk. I use cm10.1 20130317 build and it is extremely stable. A few quirks but nothing major. I plan on sticking with it since the 3.4 kernel on the newer nightlies isn't optimized yet, which result is lower battery life.
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
Thank you guys for the time to post in my thread. Alright, i will stick with update that runs well in my cellphone..
However for my second problem, do you know how i can fix that problem? i am talking about the message not sent notification.
Thanks in advance!

xBeerdroiDx said:
that being said, i would either 1) commit to these cm10.1 nightlies and perhaps even just stick with 1 of them thats working well for you or 2), find a stable 4.1 or 4.2 rom and install after a full wipe. backup first.
Click to expand...
Click to collapse
MH_91 said:
However for my second problem, do you know how i can fix that problem? i am talking about the message not sent notification.
Click to expand...
Click to collapse
assuming you have a stable backup to rely on, i would wipe data/factory rest, wipe cache, wipe dalvik cache and reflash either your current update or (preferably) the one you were running with no problems before. perhaps flash the one listed by a user above that seems to be running well

xBeerdroiDx said:
assuming you have a stable backup to rely on, i would wipe data/factory rest, wipe cache, wipe dalvik cache and reflash either your current update or (preferably) the one you were running with no problems before. perhaps flash the one listed by a user above that seems to be running well
Click to expand...
Click to collapse
Yes, i am have backed up all my stuff. oddly, i did all that you have mentioned last weekend, and still i got those glitches and the text matter it was gone at the start, but i got it back again.
Noob question, what dose "Flash" exactly means? maybe i know what flash step is, but i didnt know it was called by that term lol..

MH_91 said:
Yes, i am have backed up all my stuff. oddly, i did all that you have mentioned last weekend, and still i got those glitches and the text matter it was gone at the start, but i got it back again.
Noob question, what dose "Flash" exactly means? maybe i know what flash step is, but i didnt know it was called by that term lol..
Click to expand...
Click to collapse
and you tried flashing a different (previous) version of cm10.1 when you did that? there's always a full wipe. that includes formatting /system in recovery.
flash = install.

xBeerdroiDx said:
and you tried flashing a different (previous) version of cm10.1 when you did that? there's always a full wipe. that includes formatting /system in recovery.
flash = install.
Click to expand...
Click to collapse
Interesting.. i have got an idea i will try to do it hopefully by tonight or tomorrow. and i will share the results.
i was thinking to manually download the latest update nightlies instead of my phone update it for me, and then do the wipe thing and then i install it manually, maybe that will fix my problem.
am using G cloud for my backup and it dose his job pretty well. I wanted to use the Titanium backup but it kinda was too complicated for me.
Why they just don't call it "install" instead of Flash then lol?

MH_91 said:
Interesting.. i have got an idea i will try to do it hopefully by tonight or tomorrow. and i will share the results.
i was thinking to manually download the latest update nightlies instead of my phone update it for me, and then do the wipe thing and then i install it manually, maybe that will fix my problem.
am using G cloud for my backup and it dose his job pretty well. I wanted to use the Titanium backup but it kinda was too complicated for me.
Why they just don't call it "install" instead of Flash then lol?
Click to expand...
Click to collapse
avoid using the OTA update feature on your phone. i didnt know you were doing things that way. you'll notice many more bugs and problems that route.
you are on the right path when you say download the actual update (latest release) yourself. make sure you have the gapps to go with it. boot into cwm, wipe data/both cache, flash rom, flash gapps

xBeerdroiDx said:
avoid using the OTA update feature on your phone. i didnt know you were doing things that way. you'll notice many more bugs and problems that route.
you are on the right path when you say download the actual update (latest release) yourself. make sure you have the gapps to go with it. boot into cwm, wipe data/both cache, flash rom, flash gapps
Click to expand...
Click to collapse
Will do mate! Thank you so much for your kind help! i really appreciated it. i will for sure share the results with you very soon.
Have a good one.

Help me pls!!>

i am on android 4.1.2 i have rooted my phone and have installed roms on it b4..but for some reason i can't seem to intall any roms using twrp 2.5.0.0 i made a backup,wipe,then install rom and everything seems like it's sucessful but when the phone boots up it just stays on the bootanikmation of the rom and stays there nothing happens..what am i doing wrong?
btw:i did download a rom from goo manager and it did install but every other rom i try gets stuck.

kay131108 said:
i am on android 4.1.2 i have rooted my phone and have installed roms on it b4..but for some reason i can't seem to intall any roms using twrp 2.5.0.0 i made a backup,wipe,then install rom and everything seems like it's sucessful but when the phone boots up it just stays on the bootanikmation of the rom and stays there nothing happens..what am i doing wrong?
btw:i did download a rom from goo manager and it did install but every other rom i try gets stuck.
Click to expand...
Click to collapse
Hey Kay,
I have a few questions for you that will hopefully lead you in the correct direction in terms of flashing ROMs:
Have you checked the md5sums of the downloaded ROMs? Despite really good technology, it's easy to have a bad download (especially when downloading directly on the phone). It's always best to check the md5sum (pretty much all ROM dev's or download sites provide md5sums). I always check it with ES File Explorer prior to flashing.
You mentioned that you're doing a wipe. What exactly are you wiping? The typical "clean install" means wiping Data, Cache, and Dalvik Cache. I also wipe /System when I want a truly fresh install. Most of the time it's not required, but sometimes I even fully wipe the internal memory. I know that's excessive, but it's nice to have a clean environment.
How long have you left the phone at the boot animation? Not all Roms are created equal and sometimes (especially on DeOdex Roms) the initial boot can take quite some time. I know when I flashed The People's Rom on a friend's phone, I had to wait a good 5 minutes on the first boot. Subsequent reboots were much faster, but waiting for the first one really made me think I had a bad download (even though I had double-checked the md5sum)
What Roms have you tried? I know some ROMs (like The People's Rom) have kernel options. Sometimes (it's rare, but you never know...) choosing a different Kernel in the Aroma installer will help with the install.
That's all I can think of right now, but please let me know if any of the above works.

topherk said:
Hey Kay,
I have a few questions for you that will hopefully lead you in the correct direction in terms of flashing ROMs:
Have you checked the md5sums of the downloaded ROMs? Despite really good technology, it's easy to have a bad download (especially when downloading directly on the phone). It's always best to check the md5sum (pretty much all ROM dev's or download sites provide md5sums). I always check it with ES File Explorer prior to flashing.
You mentioned that you're doing a wipe. What exactly are you wiping? The typical "clean install" means wiping Data, Cache, and Dalvik Cache. I also wipe /System when I want a truly fresh install. Most of the time it's not required, but sometimes I even fully wipe the internal memory. I know that's excessive, but it's nice to have a clean environment.
How long have you left the phone at the boot animation? Not all Roms are created equal and sometimes (especially on DeOdex Roms) the initial boot can take quite some time. I know when I flashed The People's Rom on a friend's phone, I had to wait a good 5 minutes on the first boot. Subsequent reboots were much faster, but waiting for the first one really made me think I had a bad download (even though I had double-checked the md5sum)
What Roms have you tried? I know some ROMs (like The People's Rom) have kernel options. Sometimes (it's rare, but you never know...) choosing a different Kernel in the Aroma installer will help with the install.
That's all I can think of right now, but please let me know if any of the above works.
Click to expand...
Click to collapse
i have not checked the sum's will do that now...
yes i wipe Data, Cache, and Dalvik Cache...
i have left the boot animation on for about 5-15 min....
i have tried people's rom,goodness rom ad sac23...
the only one that worked and installed without issue was the carbon rom i downloded directly from goo manager..all the others don't boot...also sometimes after installing a new rom twrp gives me a message (your device doe not seem to be rooted swipe to install superus or something like that.

My phone has done this before. It wouldn't not boot anything but aosp so I had to Odin back to latest stock and re-root my phone and all has been well
please read this:
https://plus.google.com/app/basic/stream/z12bhtd4nwvmihxsi232wldpfo3mfj3pl04
just for the trolls: anthrax kernels, chad Goodman.

weird issue - not able to install custom ROMs

this is just weird, as i have been installing custom ROM like crazy...
but for some time i was on CM 10.1.2 and didnt install any custom ROM, but i felt like coming back to TW based ROMs, so tried installing DeTmobilized 1.5, but phone stuck at boot screen, i tried to restart by pulling battery out but phone displayed "encryption failed" and kept on showing phone.apk stopped working (something similar). so i decided to ODIN to stock and start fresh, this time i tried installed Dandroid 3.8.1 and it worked, so i thought of giving DeTmobilized one more try, but again it got stuck at samsung letters at the boot.
so i decided to stick with Dandroid for a while, but now i cannot install that too. it gets stuck while booting. but if i ODIN to stock everything works fine on stock firmware, its only the custom ROMs that are not working.
i also tried repartitioning using PIT file along with stock md5 hoping that would solve this issue, but it hasnt.
i need help, i cannot stay on stock ROM.
thank you.

chirantan.f said:
this is just weird, as i have been installing custom ROM like crazy...
but for some time i was on CM 10.1.2 and didnt install any custom ROM, but i felt like coming back to TW based ROMs, so tried installing DeTmobilized 1.5, but phone stuck at boot screen, i tried to restart by pulling battery out but phone displayed "encryption failed" and kept on showing phone.apk stopped working (something similar). so i decided to ODIN to stock and start fresh, this time i tried installed Dandroid 3.8.1 and it worked, so i thought of giving DeTmobilized one more try, but again it got stuck at samsung letters at the boot.
so i decided to stick with Dandroid for a while, but now i cannot install that too. it gets stuck while booting. but if i ODIN to stock everything works fine on stock firmware, its only the custom ROMs that are not working.
i also tried repartitioning using PIT file along with stock md5 hoping that would solve this issue, but it hasnt.
i need help, i cannot stay on stock ROM.
thank you.
Click to expand...
Click to collapse
boot into recovery and wipe cache partition along with davik, that should fix the stuck
also do remember first boot will always take a while
also make sure you're using the latest custom recovery (either twrp or cwm)

i would also like to note here that i tried installing AOSP based ROMs also, and AOKP didnt work, got stuck at nexus like boot animation forever, but when i tried installing CM10.1.2 (which is what i was running when i tried to get back to TW based ROM) it worked perfectly, so for now i am back to CM, but i would really get back to flashing different ROMs and trying them out. just makes me wonder if CM is the reason i am not able to install anything else, just a thought...
has anybody else tried going to any other ROMs from CM 10.1.2?
your help is appreciated!

pcshano said:
boot into recovery and wipe cache partition along with davik, that should fix the stuck
also do remember first boot will always take a while
Click to expand...
Click to collapse
thanks for your reply, but i have tried doing that, i also wipe data and system along with cache and dalvik before installing any new ROM.

pcshano said:
boot into recovery and wipe cache partition along with davik, that should fix the stuck
also do remember first boot will always take a while
also make sure you're using the latest custom recovery (either twrp or cwm)
Click to expand...
Click to collapse
i have latest recovery , TWRP 2.6.0.0 and i have given more than an hour to boot up and still nothing. i have been flashing ROMs like an addict since i got this phone last year, but when CM 10.1 stable was released i stayed on it till today, but now i cannot install any other ROM, i can odin to stock 4.1.1 ROM or install cm 10.1.2 which i did just now, but no other ROM, either TW based on AOSP based is working...which is very weird for me.

Were you able to fix this issue at all? I am facing the same issue, in my case, the phone was encrypted on stock TW. I roooted and put in CM 10.1.2 and now when I try installing Dandroid, the install itself would work but I am struck at the "type password to unlock the screen". If I reflash CM10.1.2, I can login fine. Any pointers?

Random reboots with custom ROMs

Hi All
I've been having such trouble flashing custom ROMs on my Samsung Galaxy Tab Pro 10.1 WiFi SM-T520. I was sucessfully able to flash TWRP 2.8.7 via odin on the device. However, I've tried several ROMs (CM11, 12, 12.1, Unofficial Liquidsmooth) each with their own issues but whichever is able to be flashed always ends up with random startup reboots. I cannot for the life of me figure out why or what is the reason. If I flash back to stock Samsung firmware, everything is fine, works perfectly but no custom firmware.
CM12.1 out right hangs during install in TWRP. The only way I was able to install it is via Cyanogen Recovery which I flashed via odin then attempted to install the rom but even still ends up in random reboots during first bootup and a few times during optimizing apps.
Just a note, I have been doing full wipes (cache, data, system) prior to flashing the ROMs. I don't know what else to do. CM12.1 works really great and smooth but cannot use it because of these random reboots. Can anyone shed some light so I can have a successful flash?
ALSO, I would like to note one suspicion I have and that is my tablet came preloaded with KOT49H.T520UEUAOD1 (T520UEUAOD1_T520XARAOD1_XAR) Samsung Firmware Build. I wonder if perhaps something with this latest build shipped is causing my troubles but am not sure.
Thanks in advanced!

Try booting back to recovery immediatly after new rom flash and perform factory reset and it ahould fix it in most cases.
Sent from my LG-D800 using XDA Free mobile app

I tried the factory reset suggestion but unfortunately did not make a difference.

Are you restoring any backups after flashing? I have been having the same issue, since flashing back to stock. I didn't like stock so I went back to CWM 12.1, which worked flawlessly before. now having random reboots, and the longer I leave it on my system, it's takes longer and longer to wake each time. The only difference between now and the first time I flashed, is, this time I restored a backup! I to, wipe before and after flashing!

Mossey said:
Are you restoring any backups after flashing? I have been having the same issue, since flashing back to stock. I didn't like stock so I went back to CWM 12.1, which worked flawlessly before. now having random reboots, and the longer I leave it on my system, it's takes longer and longer to wake each time. The only difference between now and the first time I flashed, is, this time I restored a backup! I to, wipe before and after flashing!
Click to expand...
Click to collapse
No backup/restores involved for me. Are you still experiencing this issue with CM12.1 or was restoring the backup the problem in your situation?
I am wondering if perhaps the bootloader version that is based off of the latest official stock ROM that was released in April/May 2015 has something to do with my issues. Is there anyone that was on the latest stock Samsung ROM that has been able to successfully flash a custom ROM and use it in a stable way (short of minor CM bugs)?