So I have my new verizon SG3, and I wanted to root it to have access to the SD card. As I seem to have already filled up my storage.
So I started reading many threads, starting with this one for Jelly bean:
http://forum.xda-developers.com/showthread.php?t=2046439
I had trouble with the custom recovery stage. ODIN kept failing when trying to flash it. So eventually I came with a prerooted stock flash at this link:
http://forum.xda-developers.com/showthread.php?p=33948598
and that seems to have got me to root status.
Now I am not really sure what I need the custom recoveries for, or if this link includes the boot loader or unlocker, or whatever it is, and if I really need it.
I'm looked at various ROMS and haven't really seen anything I think I need.
All I really want to do is have access to my SD card which I thought I had with the root option. But any apps that I say "Move to SD card" they only move to the internal SD card and not external.
How Do I actually use my external card?
Also, I have noticed that every time I turn the screen on, I see the "preparing SD card" message on the notification bar. and sometimes a message saying it has been removed.
What's going on with that?
And finally, my battery has been draining rather quickly. "MEDIA" seems to be using about 70% of the battery.
This is including two instances of Downloads
com.sec.android.providers.downloads
DRM protected content storage
and media storage
I read somewhere that it may be unwise to delete the preinstalled content, so I tried freezing the DRM as another forum stated that was ok as well as media hub, some of the google apps, and the verizon ringtones.
But in that process, I somehow managed to loose my notifications and ringtone selections, and when I try to reinstate them, it shows unknown ringtone, and the only options when I click to change is my GO SMS and Solid Explorer. I did locate the ringtones in the systems folder, but clicking on them only gives me an error.
I'm not sure how to get the standard selection screen back.
I tried flashing the previous stock rom again, but that did not help any.
So the question is, how do I get things back to working again, while still being rooted? Then how do I get true access to my SD card? And what can I safely remove. If a ROM will accomplish all this, which one is best and easiest to install?
I already used up half my data usage for the month installing all my apps, so I'd prefer not to do anything that would make me have to go through all that again. I have ROM toolbar installed, but it doesnt seem to want to let me do a backup. (I may need a recovery if I can get that working this time)
update
Update:
I managed to get the CWM recovery flashed finally.
How do I know if my bootlocker is unlocked if I installed the prerooted jelly bean rom I linked to before?
I also managed to get the ringtone selection to work again. I had the Media service frozen still. But that was what I think was a big battery drainer, so we will see. Im not sure why it would be draining the battery so much, something is going on.
I'm still having issues with the SD card, and installing anymore apps even after I deleted a few of the big ones. I was going to install a battery calibration tool witch is less than 200 kbs and it still is showing insufficient storage. Let the drive doesnt seem full. Maybe this is a partition issue? If so, how do I verify that and change it?
Ez unlocker in the play store will unlock your bootloader if you are rooted.
Volume up the phone before clicking yes. ;]…
One thing I've always stuck to, if it's messed up, go back to the beginning.
Could be md5 of dl or build of rom/packing of .tar, flash, etc.
Flash pure motives rls 13, works great.
Sent from my SCH-I535 using xda app-developers app
jam.i.s0n said:
Ez unlocker in the play store will unlock your bootloader if you are rooted.
Volume up the phone before clicking yes. ;]…
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Nah bud, EZ Unlock v.1.2 will properly get you unlocked, it's available on rootzwiki.
Sent from my SCH-I535 using xda app-developers app
Ok, so I am unable to install any apps now no matter what I uninstall. I'm getting an insufficient storage error now, yet I seem to have plenty of space. This is getting really annoying.
I bought the SD card for apps to save their data to it, yet all apps save to the internal SD CARD, and not the external. I see a few apps i can download to possibly switch this option, but I really shouldnt have to go through all that. Whats the point of having a SD card in the first place if no app uses it.
Regardless, something is messed up. Battery is still draining like crazy which seems to be a common problem, but I have yet to find a fix. I would consider a factory reset, but I need to figure out how to back up first, as I can not afford to go and reinstall all my apps again. Will the back up preserve all my apps and their settings without having to reinstall from the play store? I have less than a GB of data left and I'm only about 6 days in my plan.
I am trying to drain my battery completely now, to see if that may "reset" its calibration or whatever. I'm not sure how that works, but It was suggested in places, so I'm trying.
What are my options for a full data wipe? and what is the best way to get my apps back without using a lot of data to do so? I tried doing a backup with my rom toolbox pro last night but I don't believe it worked. I dont think my phone is connecting to my external SD card. I can see the data on it if I browse, but no app actually saves anything onto it. Also, the phone wont let me delete, rename, paste, or do anything accept maybe open files from the card. I had it reformatted to FAT32 before I loaded anything onto it. So I'm not sure the issue. If Its protected, I'm not sure how to unlock it as micro cards dont have he lock switches like the big ones (which was a whole other issue for me when connecting to my computer)
Any advice? I know I'm not the only one with these issues.
So I am still having insufficient space errors when trying to download apps, though for some reason I did manage to get one random app installed that was in my "All apps" section from my previous phone.
I have tried wiping catch, and dalvik, and battery stats. That did nothing.
I have also tried reflashing the unlocked jelly bean update, with no results.
I think a full wipe may work but once again, since I can't make a back up since I can't install the apps to do so. I'm a bit reluctant to do this because I don't want to have to reinstall everything again and use more of my data connection. I do have a wifi connection, but I'm not sure I want to risk that not working properly.
Is there a way to manually backup my apps and data? what should I make copies of?
This is a strange one for me. Stumped. Been working on it all night, no improvement. New one for me, long-ish description (with detail), but a TL;DR too.
Last night I applied the 1.3 OTA for the K1. Being my K1 was rooted, I followed the process I have always followed by restoring the system images to stock, applying the OTA via recovery, then re-rooting. Process:
Shutdown tablet
Swap married/paired SD card with temp SD containing flashables (OTA, SuperSU)
Boot to bootloader, fastboot (re)flash tablet's current system images (recovery was already stock but flashed again for good measure, boot, system, blob -> staging)
Boot to custom recovery using fastboot boot -recovery image-
Flash OTA from temp SD, wipe caches, apply SuperSU
Shutdown, replace married SD, boot, enjoy life
This time I didn't immediately apply SuperSU, as I thought I'd flash 1.3 and let it go fully stock a bit to ensure no other updates were pending (nVidia seems to like incremental updates, so flashing to 1.1 won't give you an OTA to 1.3 directly, but to 1.2 first, then 1.3). I've also followed this process with the K1 for every update since 1.1 without a hitch, and although there haven't been many OTAs, it has still worked perfectly every time. Because of this and because I've done this a billion times on a million different devices with zero issues ever, I didn't take a backup before the update. Woe is me.
When I rebooted this time after flashing the OTA (no root), it booted up seemingly fine to the "Android is upgrading" modal, so I left the tablet alone for a bit to let it do its thing. When I came back, the tablet was HOT, was at a completely black screen save for the status bar (no wallpaper/launcher besides the clock/wifi icon which showed a connection, that's it). I tried to interact with it and couldn't (totally locked up, also a first), then it rebooted on its own. Subsequent times, during troubleshooting, I noticed that it's totally locked -- NOTHING responds, unless you can get to it before it reboots and hold power to kill it.
First thought was a bad flash. NBD, so went back and reflashed, double-checking everything and carefully following the same process. No dice. I did use a newer TWRP recovery from April of this year initially, which was a recommended version for the K1 specifically, rather than a really buggy but working one from last year. To test I did I try using the older TWRP on one of the next flashes thinking maybe the new one borked the partitions, or at least wasn't writing the partitions/symlinks properly (and the older one was the TWRP I had used for previous updates, with no issues). But, no change..
It took me a long time and many reflashes and cache formatting and digging before I realized if I pulled the married SD out, it booted just fine. Weird, and gets weirder. After leaving the married SD out and booting, and having the tablet working just as expected (except for missing the SD), Android shows a notification saying to reinsert the married SD. Once the married SD is reinserted, things seem OK for a few seconds before the whole system goes unresponsive again, heats up, and begins bootlooping. Before it sh'ts the bed, the message on the status notification asking to reinsert the married SD card doesn't change, but in the Storage settings, it shows it's "checking" the card, followed by a sudden hot death spiral into non-function. If you select the SD from Storage settings to take a look around its contents, the tablet basically locks up instantly. Inserting other SDs works fine (for the most part, still some other weirdness), it's just the married SD that totally kills the device without fail.
Obviously I'd like to avoid wiping and reinstalling the whole thing if it can be avoided, not just because my dumb ass didn't take a backup so I'd lose a ton of app/game data, but also because it's a just huge pain. A lot of the sites that offered "fixes" for these types of problems say to just wipe data, which is not a solution and is the nuclear option (like telling someone to to replace a car due to a flat tire).
Ideas? Is this as simple as recreating some symlinks that somehow disappeared and refuse to come back after all the flashes, and if so, how? I've been looking for hours and haven't found anyone with this particular issue or steps to correct.
[size=+2]TL;DR[/size]: Applied K1 1.3 OTA, married/paired SD card is no longer recognized, causes tablet to hard-lock and enter bootloop when inserted (other SDs do not cause this issue).
Other potentially pertinent bits:
Initial flash was dirty, second and subsequent flashes included a wipe of system first
Installed 1.2 images first, then tried going back to 1.1.1 and taking nVidia's OTAs to get back up to 1.3
1.1.1 does not recognize the married SD but doesn't kill the tablet, while 1.2 and 1.3 kill the tablet when the SD is inserted
When married SD is not inserted, using shell or ES Explorer or otherwise, not seeing a /storage/emulated/0, or /sdcard, or /data/media, or any other familiar storage related directories
When married SD is inserted, it dies too fast to look around much or try to do anything to check/fix the SD itself
/storage is totally empty except for a folder called "self", and inserting a working SD creates a directory under /storage labeled with the SD's serial number (not an emulated/0 directory or anything similar)
Not sure if this is expected behavior since the SD was married -- do those directories/symlinks live on the SD now since it's married, and won't show up in the device filesystem until everything's properly mounted?
Tried following these steps, which although written in the N5 forum, still seemed relevant.. no change
Tried the referenced SD permissions update with the card inserted and not, in case of the directories it touches only being visible/available with the card inserted, no change
Noticed even within TWRP, going to the "mount" menu seemed flaky, labored, and didn't show what I expected, but this could be because there isn't a "proper" or official custom recovery for the K1 yet and things are just buggy
ES File Manager still seems to think an /sdcard directory exists and tries to open to it, and just spins in an open directory.. as expected
Going to /data in ES File Manager shows me an empty directory with a message stating the SD card is missing
Using a working, freshly formatted SD in the tablet and trying to point Titanium to a directory on the SD gives me messages about the directory being unwritable, no matter where I go on the SD
Titanium's app permissions (including r/w storage) are proper, SD is not write protected (freshly formatted on the tablet)
Tried using SDFix, which also gave me an error re: "platform permission file is invalid"
There's probably more I'm missing, but can't remember it all -- I have tried everything, I feel like, and have been at it for 13 hours now (apologies if this is written spotty, fighting to keep my eyes open).
So is it totally hosed, or is this recoverable? Is there a way to fix the tablet to recognize the SD, or fix the SD itself if that's the issue (but I'd wonder how it got corrupted in the first place, since it has only been removed once fully powered down)? Is there at least a way to check the married SD for corruption or issues?
Thoughts?
EDIT: Formatting
You removed the sdcard that was set as internal storage? Well you probably broke it/the data on it because that's not what you should do at all
GtrCraft said:
You removed the sdcard that was set as internal storage? Well you probably broke it/the data on it because that's not what you should do at all
Click to expand...
Click to collapse
And why is that? When the OS is running, sure, you can't. It'd be equivalent to just deleting /data while the OS was running. It seems pretty unlikely that removing and reinserting it while it's powered off, though, would make it suddenly unable to read the SD or forget its pairing. Adopted storage is "married" to the device via a generated encryption key, which is stored on the device's internal storage. It's all handled in software, not like the SD fuses itself to the device Removing the SD (while off) would not (and does not) break this pairing method, unless the internal storage or SD decides to spontaneously erase itself while the device was off.
The process outlined is the recommended process for upgrading rooted devices with adopted storage. I've followed this process on multiple tablets/phones with adopted storage with zero issues, including this one several times, like I mentioned.
If it WERE the case that simply removing it (again, while off) made it forget the SD, I could understand the tablet reading the card and saying "nope not going to accept it, you done f'd up" and spitting out a dialog telling me to format it or whatnot.. lesson learned, if that were the case. However it's completely hard-locking the device (again, NOTHING works, no physical buttons, screen is unresponsive, only holding power to kill it works) when it's just reading the SD, and apparently pinning the CPU when doing so (hence the absurd heat)..? It's not just a matter of the tablet forgetting the SD
grivad said:
When the OS is running, sure. Maybe that is the case, but it seems pretty unlikely that removing and reinserting it while it's powered off would make it spontaneously unable to read the SD or forget its pairing.
This is the recommended process for upgrading rooted devices with adopted storage. I've followed this process on multiple tablets/phones with adopted storage with zero issues, including this one several times, like I mentioned.
If it WERE the case that simply removing it (again, while off) made it forget the SD, I could understand the tablet reading the card and saying "nope not going to accept it, you done f'd up" and spitting out a dialog telling me to format it or whatnot.. lesson learned, if that were the case. However it's completely hard-locking the device (again, NOTHING works, no physical buttons, screen is unresponsive, only holding power to kill it works) when it's just reading the SD, and apparently pinning the CPU when doing so (hence the absurd heat)..? It's not just a matter of the tablet forgetting the SD
Click to expand...
Click to collapse
Still, you better off formatting it
Sent from my XT1562 using XDA Labs
Been running adopted storage in my mxpe since mm was released and have never removed the card to flash.
Sent from my SHIELD Tablet using Tapatalk
lafester said:
Been running adopted storage in my mxpe since mm was released and have never removed the card to flash.
Sent from my SHIELD Tablet using Tapatalk
Click to expand...
Click to collapse
Cool.
Regarding the YOU CAN'T REMOVE IT belief (which is categorically false), if this were a serious issue like people speculate it is, Android would simply not ALLOW you to remove it. Meaning if it was ever detected as being removed or missing, first time, Android would tell you "too bad, now it's unpaired", and would also make it REEEEALLY clear not to remove it at all, ever, during the pairing process, which it does not. Nor would it let you eject adopted storage, which you can, safely. Like I mentioned above, when booting without the SD present, the system runs fine and has a persistent notification asking you to reinsert the paired SD, and begins to check the SD as soon as it's inserted so it can be remounted. If you select the notification before putting the SD back in, it takes you to a panel explaining how the SD has all your apps, so you really should put it back in, or you can choose to "forget" the SD and you're back to square one. If you REALLY weren't supposed to remove the SD EVER, none of this would exist.
Additionally, pretty much every piece of documentation around adoptable storage says it can be removed just fine (but is only readable/usable by the device it was paired to), but the system kinda needs it to, you know, run all the apps you put on the thing, and will persistently remind you to reinsert it, unless you choose to break the adoption. So there's that.
Storage adoption isn't this magical, complicated thing. It mounts certain directories to your SD instead of internal storage (e.g., /storage/emulated), generates a key, then encrypts the card to prevent it from being read outside of the device it was paired with. That's really pretty much all there is to it. None of those things necessitate a or even imply that removal of an adopted SD would lead to sudden disaster. That's like believing if you take your hard drive out of your computer, but then plug it right back in, that it's going to be unbootable and dead. Doesn't work that way.
I appreciate you guys trying to help, but the problem is not simply that I removed the SD so now it's broken.
The thing that should get your attention is that when the SD is inserted, it begins to scan the SD and subsequently HARD-LOCKS. And PEGS THE CPU. Also that I cannot write to a working SD with Titanium. These things are pretty abnormal for Android devices, to say the least. There is something else going on here besides "You took the SD out and you weren't supposed to."
grivad said:
Cool.
Regarding the DON'T REMOVE IT belief, if this were an issue like people speculate it is, Android would simply not ALLOW you to remove it. Meaning if it was ever detected as being removed or missing, first time, Android would tell you "too bad, now it's unpaired", and would also make it REEEEALLY clear not to remove it at all, ever, during the pairing process, which it does not. Nor would it let you eject adopted storage, which you can, safely. Like I mentioned above, when booting without the SD present, the system runs fine and has a persistent notification asking you to reinsert the paired SD, and begins to check the SD as soon as it's inserted so it can be remounted. If you select the notification before putting the SD back in, it takes you to a panel explaining how the SD has all your apps, so you really should put it back in, or you can choose to "forget" the SD and you're back to square one. If you REALLY weren't supposed to remove the SD EVER, none of this would exist.
Additionally, pretty much every piece of documentation around adoptable storage says it can be removed just fine (but is only readable/usable by the device it was paired to), but the system kinda needs it to, you know, run all the apps you put on the thing, and will persistently remind you to reinsert it, unless you choose to break the adoption. So there's that.
Storage adoption isn't this magical, complicated thing. It mounts certain directories to your SD instead of internal storage (e.g., /storage/emulated), generates a key, then encrypts the card to prevent it from being read outside of the device it was paired with. That's really pretty much all there is to it. None of those things necessitate a or even imply that removal of an adopted SD would lead to sudden disaster. That's like believing if you take your hard drive out of your computer, but then plug it right back in, that it's going to be unbootable and dead. Doesn't work that way.
I appreciate you guys trying to help, but the problem is not simply that I removed the SD so now it's broken.
The thing that should get your attention is that when the SD is inserted, it begins to scan the SD and subsequently HARD-LOCKS. And PEGS THE CPU. Both of those things are pretty abnormal for Android devices, to say the least. There is something else going on here besides "You took the SD out and you weren't supposed to."
Click to expand...
Click to collapse
Well you tried with another sd and there is no problem. So the cause of the freezing problem is your sd.
But be my guest and find another solution. I just gave an answer to your question and a solution for the problem. If you don't believe that then you shouldn't ask it in the first place
GtrCraft said:
Well you tried with another sd and there is no problem. So the cause of the freezing problem is your sd.
But be my guest and find another solution. I just gave an answer to your question and a solution for the problem. If you don't believe that then you shouldn't ask it in the first place
Click to expand...
Click to collapse
It's not that I don't believe the solution, I don't believe the premise because it is provably false There is absolutely nothing unsafe about ejecting adopted storage, which is why the OS lets you do it, even while it's running and using the storage. Even less of a risk if the thing is off. The "solution" offered wasn't much of a solution, and in the OP it was stated that I wasn't looking for that answer (already know that's an option, which is why I mentioned in the OP).
I appreciate you trying to help, but simply saying "format it", again, is the nuclear option. Not what I'm looking for. Either information as to what's happening (if anyone else has dealt with this) with a justification as to why it's irrepairable, or things to try based on the information I gave. Spending a lot of time being thorough just to get a "format it" response, to be frank, isn't very helpful It's like telling someone to reinstall their entire OS because they can't figure out how to install a driver, or to raze their house because a painting fell off the wall.
The SD didn't spontaneously corrupt itself in the 5 mins it was out of the device. No gamma bursts or EM storms in my area that I know of, either Because the only thing that changed was installing the OTA, this really seems to be a software problem (albeit a bit bizarre, to me) so it should be fixable via software. The fact it's pegging the CPU when the SD is inserted makes me wonder if it's getting stuck in a loop, maybe due to partition changes (looking for a file or partition it can't find). If that's the case, again, that should be fixable via software, with instruction from someone knowledgeable on how the Android FS and mounts work.
Again thanks for trying to help. I know formatting is an option (the easiest one), but I'm looking for just that -- options.
You did update the firmware with the sd out, nothing to do with lightning or gamma bursts.
Did you try downgrading firmware back to where it was?
lafester said:
You did update the firmware with the sd out, nothing to do with lightning or gamma bursts.
Did you try downgrading firmware back to where it was?
Click to expand...
Click to collapse
True, the SD was out, however this is how I've both read to do it in multiple places, and how I've applied every OTA so far without issue (with the same adopted SD every time). As part of my troubleshooting, I did try flashing the OTA with the adopted SD inserted, though. It didn't make a difference.
I did try downgrading.. When I started the tablet was on 1.2, OTAd to 1.3. Every time I'd reflash I would do so to 1.2. I did try flashing down to 1.1.1 (the "recovery OS image") and OTAing back up, and like I mentioned that allowed me to use the device with the SD inserted, but it wouldn't recognize it as the adopted storage.. just kinda did nothing, as if the card wasn't inserted at all. This happened in 1.2 as well (OTAd from 1.1.1), and once it got up to 1.3 from 1.2 it all started all over again.
I'm creating an image of the SD right now (using dd) to try restoring it to another SD. I've read that doing this preserves the pairing information, so if it's a bad SD, this would hopefully fix it. I also wanted to try flashing directly to 1.3, but the images aren't available yet Only 1.2 and 1.1.1..
Honestly I would divorce the card before update then redo it after this whole method is janky anyway no reason to remap the data links like they do and all it would be required is if app devs were forced to comply with a data space method... The feature of installing to SD card should be available to non married storage.
Old thread, haven't been on in a while, but thought I'd post an update.
The problem ended up being a hardware issue. I contacted nVidia after absolutely nothing I tried resolved the issue (different SDs, different OS versions, different process to set up, etc.). I simply explained the problems I was having and my troubleshooting attempts, asked if it was a known issue or if they had any suggestions, and they immediately responded with RMA info, no questions asked. The replacement turnaround time was very fast (within a week IIRC), and the new K1 has had zero issues.
Hi
Can't remember whether or not this has been asked and answered, but here goes...
Shield tablet
5.1.1
Non-root
For the past 2 months or so I've been plagued with random reboots ( up to 2-3 times a day)
I've tried to
wipe cache 2 times
delete a whole bunch of apps
Change power settings
I have NOT YET tried to do a full wipe, due to the fact that I've got waaaay to many apps that don't sync data with google so it would be a major hassle to fix settings, copy data out and so on.... But am looking at backup solutions that include DATA ( helium)
I haven't been able to ascertain pattern.
Any suggestions on what I can do , or for that mater any way to find out why the hell it restarts.
Thanks in advance!
D
That's strange. So just reboots, no shutdowns?
I can only assume, maybe a rogue app with reboot access.
Just reboots
And It seems totally random.... everywhere from 4 times a day to non... Load dosen't seem to matter . From netflix and web to plain and simple spotify. It's driving me up one wall and down the other... can't figure it out, and really don't want to factory reset
Any form for event viewer or something that I can take a look at?
Worst part is I use it to take work notes and on a few occasions it's died (rebooted) on me in the middle of notetaking... starting to really mess with things ... and yes I know, do a factory reset, and I will if I run out of options. But my fear is that after I reinstall all the apps I'm back to square one, and it all starts all over again.
Maybe hibernating all non stock apps with Greenify could solve the riddle; if it's indeed a software issue. Once the problem ceased, activate one app at a time till the reboot bug reoccurs..
Hi
Sry for the slow reply
Been testing the Greenify for about 2 days and the same is still happening. I've more or less put all non stuck apps into hibernating list.. and run it every so often, as well as activated the hibernate at screen off. And it still happens... wish there was an event log or something that could point me in the right direction.
That's too bad. What if it is malware? I'd say make a factory reset. Stay clear of non stock apps and watch and see. If it still reboots, it must be a hardware issue. You still have warranty, aye?
Nope warranty is out, I think. I mean 2 year but got it back in 2014 at some point.
A damn it, was hoping to id the damn offending app and fix it without having to factory reset....
No one knows of any event / log feature in android ( akin to event viewer in windows)...??
I just read on Amazon that someone had the same issue inconsistent reboots and the culprit was a micro SD card.
Do you have on inside your Shield?
I had this problem like 3 months ago. When tablet was charging the led indicator was blinking on green an orange. The problem was that the cable from battery was connected bad, I just had to connect it with solder. (My tablet is replaced )
Niii4 said:
I just read on Amazon that someone had the same issue inconsistent reboots and the culprit was a micro SD card.
Do you have on inside your Shield?
Click to expand...
Click to collapse
Yeah, I do have an NTFS formated sd card installed...
Do you know of any easy way to check...or even better fix it?
Replace the SD card with another one or don't use one for now. You can still backup via USB or WiFi.
It may be a incompatible issue or a damaged SD card.
Backup via usb? As in copy paste the content of the SD card?
I have a lot of apps on the SD card, and not enough space on local storage to move back to tablet ....
Was hoping for some software based diagnostic or test to check the sdcard
Yes, you can copy n paste. Or save new data on a new SD card etc.
I presume there are Android SD card checker apps. But I think that won't help if it's an incompatible issue. Anyway, unmounting the current SD card won't erase its data. It's the sour apple you've to try.
Just somehow experienced the same.
Android 7.0 - no root no anything.
It's weird. Now it rebooted with 1% and then died. Before it just rebooted around 40%. Anyone found a solution?
Thanks