[Q] (911HELP) on T-Mobile Vibrant BLK SCREEN w/keys LIT=(

[Q] (911HELP) on T-Mobile Vibrant BLK SCREEN w/keys LIT=( - Vibrant Q&A, Help & Troubleshooting

Ok, here's the story...
I rooted my T-Moblie Vibrant with the Update.zip file via this link "forum.xda-developers.com/showthread.php?t=723479"
Everything worked fine and I tried to do the VooDoo lag fix and all **** happend via this link
"androidspin.com/2010/09/23/overclock-add-some-voodoo-to-your-samsung-vibrant/"
I also applied the "Dalvik-cache & Data Scripts" and "JAC’s OC Kernel + Voodoo Beta4 Kernel " to my phones SD card. At this time, I flashed "Clockwork Recovery" and enetered it to apply the two .zip files to my phone. I installed both .zip files containing the ""Dalvik-cache & Data Scripts" and "JAC’s OC Kernel + Voodoo Beta4 Kernel " AT THE SAME TIME and I then tried to reboot and apply. At this time "LINDA" the robotic voice operator notified me of all the steps and in the end congratulated me for the successful application of the .zip file.
Once the Vibrant screen came up, it NEVER continued, frozen for an hour, I looked at alternative options and tried ODIN... ODIN3+SPL, s1_odin_20100512.pit, SAMSUNG_USB_Driver_for_Mobile_Phones_x86 (32bit)[I AM AWARE MY COMPUTER IS 32 BIT], T959UVJFD.tar. These were all the files used to flash the Original Rom back to my Vibrant. I used several others and NOTHING WORKED, I MEAN NOTHING... THE FARTHEST I GOT IS THE GALAXY S SCREEN AND IT GOES (BLACK RIGHT AFTER ALONG WITH THE ABILITY FOR THE FOUR KEYS ON THE BOTTOM OF THE SCREEN TO BE LIT IF PRESSED) What's weird is that the charging battery screen pops up and it charges, I'm assuming that the software is properly flashed back. I just bought this phone and I'm so frustrated...
CAN ANYONE PLEASE HELP ME... I feel like chukn' this phone at the wall, but $500 will be gone(((((((( TIA...

CASHawaii07 said:
Ok, here's the story...
I rooted my T-Moblie Vibrant with the Update.zip file via this link "forum.xda-developers.com/showthread.php?t=723479"
Everything worked fine and I tried to do the VooDoo lag fix and all **** happend via this link
"androidspin.com/2010/09/23/overclock-add-some-voodoo-to-your-samsung-vibrant/"
I also applied the "Dalvik-cache & Data Scripts" and "JAC’s OC Kernel + Voodoo Beta4 Kernel " to my phones SD card. At this time, I flashed "Clockwork Recovery" and enetered it to apply the two .zip files to my phone. I installed both .zip files containing the ""Dalvik-cache & Data Scripts" and "JAC’s OC Kernel + Voodoo Beta4 Kernel " AT THE SAME TIME and I then tried to reboot and apply. At this time "LINDA" the robotic voice operator notified me of all the steps and in the end congratulated me for the successful application of the .zip file.
Once the Vibrant screen came up, it NEVER continued, frozen for an hour, I looked at alternative options and tried ODIN... ODIN3+SPL, s1_odin_20100512.pit, SAMSUNG_USB_Driver_for_Mobile_Phones_x86 (32bit)[I AM AWARE MY COMPUTER IS 32 BIT], T959UVJFD.tar. These were all the files used to flash the Original Rom back to my Vibrant. I used several others and NOTHING WORKED, I MEAN NOTHING... THE FARTHEST I GOT IS THE GALAXY S SCREEN AND IT GOES (BLACK RIGHT AFTER ALONG WITH THE ABILITY FOR THE FOUR KEYS ON THE BOTTOM OF THE SCREEN TO BE LIT IF PRESSED) What's weird is that the charging battery screen pops up and it charges, I'm assuming that the software is properly flashed back. I just bought this phone and I'm so frustrated...
CAN ANYONE PLEASE HELP ME... I feel like chukn' this phone at the wall, but $500 will be gone(((((((( TIA...
Click to expand...
Click to collapse
This has been answered time after time in the forums. try doing some research before posting. I had to same issue and found a post that fixed it but I searched so much I can't remember which post it was.
WITH ODIN PREFERABLY THE NEWEST BUILD
Basically what you need to do is flash eugene's froyo that doesn't brick from here
http://forum.xda-developers.com/showthread.php?t=740558
(WITHOUT RE-PARTITION CHECKED).
after the phone reboots it will boot into recovery with an error. don't worry this is normal
Now flash the original tmobile stock firmware (WITH RE-PARTITION CHECKED) from here
http://forum.xda-developers.com/showthread.php?t=734475
This worked perfect for me BUT PAY CLOSE ATTENTION!!! DO NOT CHECK RE-PARTITION WHEN FLASHING THE FROYO ROM AND DO CHECK RE-PARTITION WHEN YOUR FLASH STOCK
BTW you will lose all data so hopefully you were wise and backed up before trying to flash a kernel. If not you will from now on lol.
As I said before this worked perfect for me so if you follow directions well you'll be back to stock in no time but if something goes wrong don't blame me.
IF YOU ARE NOT FAMILIAR WITH ODIN CHECK OUT THE VIBRANT BIBLE AT THE TOP OF THE FORUM. I BELIEVE THERE IS A GUIDE FOR ODIN THERE.

While it is completely legitimate to get frustrated when flashing different ROMs and modifying your phone, you gotta realize that this is all experimental. These ROM's are stable for quite a few people, but they aren't completely error and issue free like one of the more seasoned ROM's on an older phone (CM6 comes to mind).
So don't get upset, just realize that if you're running a bunch of scripts and hacks on your phone that you got from a forum, and now you're having problems - other people on this forum have likely already had - and fixed - whatever you're going through.
If you had checked the either of the Bionix threads (I know for a fact it is in the Bionix Final thread) for step-by-step instructions that the devs have already been nice enough to provide. In reality, they go through a lot of extra work to put together documentation for people to use what they create. They do it because they want more people to enjoy what they enjoy, and that says a hell of a lot about the people we have around here.
Keep your chin up, have fun with this stuff. If you can't afford to replace your phone, I would suggest taking a step back until more work/time has been put into these processes. GL HF

Related

JI6 + oclf + Voodoo = Death [ANSWERED]

I seem to be at a bit of a cross road here, hopefully posting this story can give me some direction, as I see people with similar problems elsewhere, but not on XDA.
After getting the JI6 upgrade on stock, it took out OCLF, when i did it update, none of the setting where available. So when I redid OCLF, i could not up to the new OCLF and could not undo the old one. However voodoo5 was available, and seeing the reports on that voodoo5 was the bees knees. So I ran it (stupidly. It went though the motions, heard the voice prompts saying the steps, and said it was Completed. I knew the first boot up took some- what I would get is
Stuck on Black Vibrant screen, would hear T-Mo boot up sound, but would never progress after 20 - 30 minutes
Reading the Forum, (Use that search button) using the steps specifically in this post: [TUTORIAL][ROM] How to fix your phone and apply the update --- to achieve what i heard that had success stories with using Odin to restore to restore JI6 update after this kind of error. Well here is where I am at:
I can get into recover mode and boot loader
I get Vibrant, Tmobile screen, hear the tmobile tone, and then see the galaxy S screen
I then get an all black screen where the buttons on the bottom (home, back etc) light up, and will turn off when i touch them and then come back on
And that's it. I get nothing, a big blank screen. And I am unsure where to go... any advice would be helpful on how to get a full recovery. No longer worried about my data, just want to get my phone back up and running by any means.

buggzero said:
I seem to be at a bit of a cross road here, hopefully posting this story can give me some direction, as I see people with similar problems elsewhere, but not on XDA.
After getting the JI6 upgrade on stock, it took out OCLF, when i did it update, none of the setting where available. So when I redid OCLF, i could not up to the new OCLF and could not undo the old one. However voodoo5 was available, and seeing the reports on that voodoo5 was the bees knees. So I ran it (stupidly. It went though the motions, heard the voice prompts saying the steps, and said it was Completed. I knew the first boot up took some- what I would get is
Stuck on Black Vibrant screen, would hear T-Mo boot up sound, but would never progress after 20 - 30 minutes
Reading the Forum, (Use that search button) using the steps specifically in this post: [TUTORIAL][ROM] How to fix your phone and apply the update --- to achieve what i heard that had success stories with using Odin to restore to restore JI6 update after this kind of error. Well here is where I am at:
I can get into recover mode and boot loader
I get Vibrant, Tmobile screen, hear the tmobile tone, and then see the galaxy S screen
I then get an all black screen where the buttons on the bottom (home, back etc) light up, and will turn off when i touch them and then come back on
And that's it. I get nothing, a big blank screen. And I am unsure where to go... any advice would be helpful on how to get a full recovery. No longer worried about my data, just want to get my phone back up and running by any means.
Click to expand...
Click to collapse
Did You Flash Something Before Disabling Voodoo? 2 Fixes to Help You Out.
So you forgot to disable the voodoo lagfix before you flashed a new rom and now you're getting an error, similar to the one posted below. Even Odin won't allow you to flash back to stock. Well, pay close attention and with some luck, you'll be good as rain...or something like that.
Fix 1:
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Download the 'True stock 2.1 firmware for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine! BAM!
Fix 2: (use only if you know how to use adb commands)
1. Place the 'disable-lagfix' file in your sdk>tools directory
2. Get into clockwork recovery like you normally would
3. Follow these adb commands to push the 'disable-lagfix' file to you sdcard>voodoo
adb push disable-lagfix /sdcard/voodoo
4. File should now be on your sdcard in your voodoo folder.
5. Reboot phone and with luck, you should hear Linda the robot telling you your file system is being converted back to rfs.
6. Because your system directory has already been wiped, you'll still get a black screen when you reboot, but your file system is back to rfs. Just pull the battery, and reflash whatever rom you want. Then reboot again.

ANNNDD THE TRUUUUTHHH SHALL SET YOU FREEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE
Thank you AMD. Following "Fix 1" Method, worked flawlessly!
Now, just to clarify, this put the phone completely back to stock? It has undone the ext2, voodoo and hoodoo nonsence? I just want to know where I stand, becuase now that I am wiped clean, there is obvious no worry of loosing data now lol. Might as well put a nice custom rom, rather than fiddiling with fixes to the stock right now.
Also, I am not yet familiar with ADB, but will read the sticky Bible thread, do you recomend that method over the 1st one? I did not install clockwork recovery, is that a perferred pre-loader to prevent these kind of issues?

buggzero said:
ANNNDD THE TRUUUUTHHH SHALL SET YOU FREEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE
Thank you AMD. Following "Fix 1" Method, worked flawlessly!
Now, just to clarify, this put the phone completely back to stock? It has undone the ext2, voodoo and hoodoo nonsence? I just want to know where I stand, becuase now that I am wiped clean, there is obvious no worry of loosing data now lol. Might as well put a nice custom rom, rather than fiddiling with fixes to the stock right now.
Also, I am not yet familiar with ADB, but will read the sticky Bible thread, do you recomend that method over the 1st one? I did not install clockwork recovery, is that a perferred pre-loader to prevent these kind of issues?
Click to expand...
Click to collapse
Your welcome and yes, you're completely back to stock and everything is gone. So you should be set. No, both methods work well and do the same. I know adb but still prefer the first method, works all the time is something goes wrong with voodoo or any lagfix.
I wouldn't say it's preferred to prevent those issues because you may still have them either way but its nice to have. You can make a backup with it so if anything goes wrong you have something to fall back on. Just makes things simpler.
Sent from my SGH-T959 using XDA App

Seeing some of your other posts in the bionix fusion rom, which is what I ended up flashing to, it seems that the issue you had mentioned is that even if your moving between voodoo compatible roms, voodoo needs to be removed before.
This can be done within the handset with rom manager, using the voodoodisable.zip?
Cause ya, didn't quite understand that part till it happened. Feel pretty dumb when there is post after post of "PPL DUN FKN READ"
Sent from my SGH-T959 using XDA App

buggzero said:
Seeing some of your other posts in the bionix fusion rom, which is what I ended up flashing to, it seems that the issue you had mentioned is that even if your moving between voodoo compatible roms, voodoo needs to be removed before.
This can be done within the handset with rom manager, using the voodoodisable.zip?
Cause ya, didn't quite understand that part till it happened. Feel pretty dumb when there is post after post of "PPL DUN FKN READ"
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
It's simple to disable voodoo. When you have voodoo installed you should have a voodoo folder in your internal SD card, if you don't them make one. Put a file called disable-lagfix in there with no extensions. A blank file with that name. Reboot and you'll hear the.process going through of removing voodoo. Then you can flash what ever you like without any problems. If you want voodoo back delete the disable-lagfix file or rename it to enable-lagfix. Simple.
Sent from my SGH-T959 using XDA App

thx for ur sharing...
i hv the same problem, it's fixed now...

[Q] (911) help vibrant stuck on black screen w/keys lit

if the 512 flash doesnt work, try flashing to i9000 rom eu, then flash to 512. i had to do that when i bricked my phone flashing a rom and not disablling voodoo

Yea I agree, try froyo that does not brick thru odin
Sent from my SGH-T959 using XDA App

Just had this issue with my phone last night, couldn't get it back even using odin and going back to JFD. I ended up at a T-mobile store today and they are replacing it for free except for shipping. Hopefully you have better luck but you should be able to get it replaced if you can't. I was expecting them to tell me no luck but they went ahead and replaced it. I did fail to mention that I may have caused the software issue though....

Email me [email protected]
Sent from my GT-I9000 using XDA App

Its baaack!!!!!
Just got my phone running! Follow the steps in this thread, you first download eugenes froyo to your phone through odin and then immediately flash stock 2.1 through odin and your phone is fixed. I am so happy right now!
Here is the thread with full instructions:
http://forum.xda-developers.com/showthread.php?t=745547

After rushing in, ODIN is not helping me to recover =(

Hi I'm a new member,
I rooted my fascinate easily enough. Then searching and learning about ROMs and Kernels I decided to do use ODIN CWM Recovery to 'backup' or whatever most forums tell you to before installing a new ROM. Point is my phone is stuck in manual boot mode and I cannot undo it.
I have tried multiple times using ODIN plus the four stock files
Stock-i500-VZW-Kernel.tar.md5
Stock-i500-VZW-pit.pit
Stock-i500-VZW-Recovery.tar.md5
Stock-i500-VZW-System.tar.md5
(I always would try to implement them in order pit/system, pit/kernel, pit/recovery)
Unfortunately after the first one (pit/system) ODIN says the process fails, I go ahead with the other two and they both amount to nothing happening. My phone does not reset or do anything for this matter and I am forced to shut down ODIN and unplug my phone (upon which it dies with no battery).
Then I put back in the battery and Im back to before in manual boot mode with
Reboot system Now
Apply sdcard:update.zip
wipe data/factory rset
wipe cache partition
Btw wiped data and wiped cache and it didn't help me =(.
Please someone help me, I really don't want this new phone to be dead... Thanks in advance
Oh and when I press "apply sdcard:update.zip" I receive
E:Can't mount \dev\block\vold\179:9
(No such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted.
I really don't care at all about keeping the phone rooted or not or whatever. I just want to be able to make calls again!

So it looks like you're stuck in blue recovery ... sounds like something that Odining a stock package should fix.
Here is a nice thread for getting back to stock (it's a sticky in the general section). The packages include system, recovery, kernel, and radio in a single file (I've actually never odin'd four separate files to get back to stock, or even ever flashed a system-only file), though no pit file.
So open up odin with your phone in download mode (with the battery out, otherwise there's a small chance of odin stalling at the end), and use:
- either the DI01 all-in-one, EB01 all-in-one, or this DL09 package in PDA
- the pit file in PIT (the link says DI01/EB01 but it also works with DL09)
- check "re-partition" if it isn't already checked
- run odin and hopefully in five minutes your phone will work again If for some reason it doesn't, that thread has instructions for using heimdall, although I've never had to resort to it.
So try this and see if it works! (For which package to use, I'd suggest trying DL09 first (since you'll need it to get to the official froyo build) and DI01 if that fails. If you're wondering whether DL09+pit actually works, I've used it to get out of a "stuck in blue recovery after odining stuff" situation myself so yes, it works.)

Thank you for the response! It's encouraging to hear any support and I think yours is promising.
So unfortunately I tried D101 and no go. Turns out this was before I realized this was for 2.1 and I'd prefer 2.2 for the upgrades. Although would you suggest 2.1 for the purpose of rooting/ROMing/Kerneling in the future? I ask because I'm slowly gaining confidence that after fixing this I might be willing to try this again...
Odin (1.7 -> I decided at your poster friend's advice to upgrade from 1.3) worked well said 'pass' and everything. Unfortunately when booting my phone it went straight to the boot screen as always.
Meanwhile I'm downloading the EB01 and your suggested DL09 to test those two.
Hopefully one of those will work but if not, I guess I'll try that heimdall technique the poster suggested in the other forum. Hopefully not tho b/c it looks a bit more complicated.
I'll let ya know if one of these others works.

Yes it worked!! Thank you so much! I would buy you a round at the ale house if I could!
After running EB01 it worked (with the pit file going all the way back to factory settings). So I'm not sure what this means - maybe since it was after upgrading to 2.2 that my phone bugged out, it could only be restored to the 2.2 state which is EB01?? Idk, thanks anways.
Oh ya for the future if I try do this again - would you suggest I stay away from ROM Manager for backing up, which I believe is what started this problem in the first place? It seemed like ODIN did a fine job of managing my OS. Any thoughts? Thankss!!

mattjac1 said:
Yes it worked!! Thank you so much! I would buy you a round at the ale house if I could!
After running EB01 it worked (with the pit file going all the way back to factory settings). So I'm not sure what this means - maybe since it was after upgrading to 2.2 that my phone bugged out, it could only be restored to the 2.2 state which is EB01?? Idk, thanks anways.
Oh ya for the future if I try do this again - would you suggest I stay away from ROM Manager for backing up, which I believe is what started this problem in the first place? It seemed like ODIN did a fine job of managing my OS. Any thoughts? Thankss!!
Click to expand...
Click to collapse
Definately stay away from rom manager cwm if you have the voodoo lagfix enabled, but since all the new fascinate roms are edify scripted, flashing through cwm in rom manager would be ok.
Sent from my Froyo'd Evil Fascinate full of PB&J

[Q] Need a bit of help

Problem: Whenever I boot my phone after the galaxy S logo dissapears the screen stays black, while the backlight on the touch sensitive buttons still come on.
So here is my background on what I have done with the phone
- It is on 2.1 Eclair
- Everything was fine. I had it rooted and running Bionix.
- When the problem started was when I was trying to install a matrix boot image, and a theme for Bionix.
- First symptons would it wouldnt get past the Vibrant (text) startup screen.
- In response I Restored to the Clockwork mod Restore which would have brang my phone back to normal.
- It did bring my phone back to normal except for one thing, there was a bug that said my cards were full and couldnt install any apps.
- So I went back into clockwork mod recovery and figured out quickly it didnt recognize my sd ext. But when my phone was on it did.
I understand that this problem is very out of now where and probably isnt very solveable with just a one click program. But I would be very thankful if anyone could give me any kind of information on this. Even if it is just saying "Its a problem with your Kernel". AlthoughI hope to see downloads and full instructions.
Thank for reading this.

CWM recovery is not supposed to be able to see your external sd, you are only supposed to be able to flash files from the internal sd.

Thanks given.
Do you know of any method I can do to fix this

You could Odin back to stock 2.1, but first turn off lag fix if there is one via voodoo app.

You want to ODIN using stock firmware and the 512 pit file. This will repartition your internal SD. You will (should) not lose personal data such as pictures, music, files.... You ended up trying to flash a theme or bootanimation that was not compatiable and when you restored traces of it have been left behind.
ODIN is the best method in these situations. Note that in rare cases it may be neccessary to do a full SD reformat.
The first thing you want to do is back everything up to your computer. All those pictures, music anything you want saved and then and only then try the odin with 512 pit.

If you need the files for odin you can check my sig for the odin exe pit file and tar file, if instead you need instructions on how to use odin i'd check here: http://forum.xda-developers.com/showthread.php?p=13132341#post13132341

shreddintyres said:
If you need the files for odin you can check my sig for the odin exe pit file and tar file, if instead you need instructions on how to use odin i'd check here: http://forum.xda-developers.com/showthread.php?p=13132341#post13132341
Click to expand...
Click to collapse
Thanks for referring, I've also included the files in the guide just in case.

I certainly hope you aren't in a partitioning brick situation. I've seen this now twice and both were running Bionix 1.3.1 w/ Voodoo enabled and both somehow got certain bml partitions in an recognizable format by CWM and the Android OS. So far it hasn't been fixable with conventional flashing and PIT repartitioning. I will be trying a full JTAG re-write on one of the customer's phones tonight. I'll report back to this thread whether a JTAG session in which I fully re-write all addresses in the NAND block was able to fix this.
This marks the 3rd instance of what I'm referring to as partitioning bricking that was involved on a Vibrant that was running Bionix 1.3.1 at the time of the brick. I'm not blaming the ROM or the developer as I have used it with no issues and it's a great piece of work but perhaps the CWM packaged with it is allowing users to do things they don't intend to do causing this issue.

Thank you everyone very much for all the information and I was able to restore my phone back to stock 2.1 Eclair and then I flashed the rom bionix onto it.
I have given thanks to everyone that has posted from here on up ^^
Also if anyone is stuck in this situation also and Is reading this thing saying "what the heck I have no idea what to do". Just message me and I could full througho instructions.
Once again thank everyone and I have solved my problem. I am pretty sure it was the boot logo that made it happen.

[Q] Can't flash to stock

Trying to flash to stock via Odin. Odin completes without errors and reboots the phone. The phone, though, shuts off after the inital splash screen ("Vibrant" at the top "samsung" at the bottom").
Since multiupload/megaupload was taken down, I'm unable to find any Odin-flashable stock roms/any kind of roms. I followed steps 2-4 on [I can't post a link, but it was on rootzwiki] and ended up with this.
Does anyone have any ideas? I've been searching for a solution for the past 3-4 hours.

Go to the Dev section and download tha AIO Toolbox (Stickied at the top). It has the Odin v1.8 (I think), all the drivers and pit/tar files that you need to get back to stock 2.1 and then you can download CWR from my signature, find a ROM.zip that you want to install and put them on your Internal SD card.
Make sure you put the ROM in a folder and also make sure that the CWR that you get from my sig is on your internal and is the only thing on it labeled Update.zip. Once those are done, boot into recovery, scroll down to "Reinstall PAckages" and hit it. Let it cycle through and you might have to do it again. Once it cycles through your recovery will go from Blue (stock) to Green (CWR) from there, you can flash your ROM and profit. [If you are going to an ICS flavor, you may have to be on GB bootloaders and flash CM7 as an intermitant step. I suggest trying Moped_Ryder's ROM and Fishman's Bionix Mod-both 2.2 but quality and everything works.]
The toolbox is a valuable thing and you can do many things with it, but mainly and most importantly, it HAS the files to get you back to TMo 2.1. (I use it all the time and I am not even a TMo customer).

Just flashed via the AIO toolbox, still same behavior.
Can't even get into the recovery screen.

What ROM are you coming from? If 2.3 or higher you have to tick repartition.
Just keep trying. I've seen posts where it takes many times for it to pass and boot up for some reason. Not sure why it does this sometimes.
I'll check on you later. My tablet got another update today, so I'll be troubleshooting over there later on.

I'm coming from ICS Passion v4 (I think, it's been a long whiles since I flashed it)
Just reflashed 7 times to no avail :/
Thank you for taking the time to help, it's really appreciated..

Hah! Unbricked!
Followed this guide: http://forum.xda-developers.com/showthread.php?t=817186
Used eugene's odin image from: http://forum.xda-developers.com/showthread.php?t=833024&page=49

Better Mobile App

welcome