yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] ludachez:
Recovery fix?

Can you boot into stock recovery? from what i have read the issue with a lot of people is using ROM manager to install ROMS or get into recovery. Go into rom manager, flash recovery (even if it says you have the latest one) and EXIT. Power down your phone. Now when you restart try to get to stock recovery, but holding down the buttons like you would for download mode, if you get to stock recovery, hit "Reinstall Packages" and it SHOULD take you to CWM. Finally bit the bullet and it worked for me. I do not have a hardware locked phone, and also have the larger NAND chip. Dont know if that makes a difference.
[Vibrant Android Development] enuro12:
Alright bricked it two more times.

I realized i didn't reinstall ClockWork to the boot thing... (first icon clockwork) after that last flash and possibly not the first time either.

Last time i cleared all the cache & formatted user data.

I also did the install manually in ClockWork

Fully Stock Rom no changes at all.

The last brick was done Fully Stock. This time i updated clock work to 2.5.0.7. Same problem.

Hope this helps someone with the issue.
[Vibrant Android Development] enuro12:
Mine wont go into recovery. I tried Vol/Soft Home & pwr btn combination i could find.

I can get into download which i'm using odin and going back to stock and starting fresh.
[Vibrant Android Development] enuro12:
After loading the stock Rom i had to use a different driver. That installed ADB interface.

I can ADB in using this method now. But doing a adb reboot recovery just brings me back to the vibrant screen.

Download works fine.
[Vibrant Android Development] Shrivel:
No, I use an external cable with a mic when I'm in the car and it works just like it always has.
[Vibrant Android Development] enuro12:
Sorry for so many posts... I know i'm a noob...

Discovered something very interesting (to me at least)

Here is what i did...

1. Open Odin

2. Plug in the USB

3. Press the power button

4. Phone Booted to the Vibrant Screen (Odin detected COM4, normally its COM3)

5. Clicked Start in Odin thinking i'd already loaded the PID & PDA but i didn't. (so select nothing in ODIN)

6. The phone booted.

(i've since shutdown and rebooted without freezes...)
[Vibrant Android Development] krazykidd:
I noticed that too after installing it, but that was probably because I did a SD card wipe on the internal SD card after being tired of the things on there, I had to reinstall a lot of the games.

Also, I'm noticing a problem with the slide down notifications, after a phone call, the notifications slide down refuses to slide down and the only way to resolve it is to reboot the phone.
[Vibrant Android Development] krazykidd:
Have you tried the "boot into recovery" option that's in ROM manager?

I think that we should have people who have problems with this state whether or not they have a hardware locked phone. I have a NAND (hardware) locked phone and I still flashed fine. The processes I took were slightly varied since it failed the first time (without brick). I would have shat bricks if my phone bricked; I have no alternative means of getting it restored, other than that USB trinket guide.

Prior to installation, I (while still on JI6):

1. Removed all lagfixes.

2. Reset to factory settings (via Settings>Privacy>Factory data reset).

3. Reinstalled ROM manager (after plugging in my own personal information into the market again).

4. Flashed ClockworkRecovery to the latest 2.5.0.7 (you NEED an external SD card in the phone to be able to do this).

5. Moved the ASOP update file from the external SD card into the base directory of the internal one. I used Root explorer for this, however you can use other methods (I rooted my phone using ADB so it doesn't matter how you put the file into the internal SD).

During Installation, I (while in ClockworkRecovery):

1. Installed update via ClockworkRecovery

2. Wiped ALL caches.

3. Installed packages (I did NOT rename the zip).

4. Hit reboot

After installation, I (while in JK2):

1. Had a long boot (five minutes I think? It's probably because of initial booting and having to build up all the caches. I sat there wondering if I bricked my phone for a good four minutes).

2. Installed OCLF 2.0.

3. Applied lagfix.

4. Enjoyed Froyo on a Vibrant before the conventional users in my college classes will get a taste of it with an OTA.

I don't know what else to really say to help other people, my phone was giving me problems a few times. You just have to remember to remove the lagfix, and then possibly do a factory data reset (in phone and in recovery). Should get it otherwise after. If not, feel free to post how you're trying to do it and I'll do my best to guide you through the process.

Someone else answered my question about this. They said it was a problem with the kernel and that eugene was aware of this problem. You're not the only one with this issue, as I was using the audio jack in my car (without a mic) also.
[Vibrant Android Development] enuro12:
That's what soft bricks it EVERY Time. %100
[Vibrant Android Development] negativedrew:
Anyone else having issues with multiple notifications being fired for the same event, or vibrations when they're turned off?
[Vibrant Android Development] krazykidd:
Something is definitely up with your phone (or you :P). You say soft bricks, how long are you giving it on the Vibrant screen? Mine took a bit longer than standard wait after I got into recovery and after I booted into JK2 for the first time.

What launcher are you using? What apps are you running? I don't have this problem, and I'm using ADW, with the notifications add-on.
[Vibrant Android Development] mulcahyd:
The rom is solid, been using it as my main usage everyday.
[Vibrant Android Development] Zeno78:
I cant enter Download mode for ODIN.. as my phone is now a SOFT BRICK.... I try and hold the volume up down and power at the battery screen and nothing.. Now my battery won't show green i just have the star looking thing in the middle of a black battery. .I nkow that the battery is fully charged as it was charged all night.. WTF...

all was well untill i went to boot into recovery using ROM manager....
[Vibrant Android Development] DaytonaDU:
What got me around this identical issue was to plug the phone into my PC via USB and hold down the Down Volume button after pushing Power.

It locks up on the Vibrant screen every time I try to boot to the Clockwork Recovery.
[Vibrant Android Development] Zeno78:
bump for help...I need my phone working...

Can't get into download mode for ODIN... phone will only show a Black Battery with a white star in the middle. Holding down vol up/down and power just just cycle the phone.
[Vibrant Android Development] ugokind:
titanium backuo

how do I remove the trial titanium backup now that is in STOCCKED?
[Vibrant Android Development] krazykidd:
Use Root Explorer. Under "/" home directory you start out in, navigate to "/system/app/" Mount R/W button on top of screen. Click it. Then find TitaniumBackup.apk and delete it.

You can do this also with ADB if you know how to mount and navigate through it.

After you delete it, go back into application management and uninstall it if it's still there. Avatar.apk is also removed this way.
[Vibrant Android Development] Zeno78:
OK I can get into D/L Mode... waiting 22mins for T959UVJFD.tar to D/L... is there any way to use ODIN to just get back to recovery?

What about the OCLF?
[Vibrant Android Development] krazykidd:
If there is, I've never used it to get into recovery.

What about the OCLF? All it's there for is to apply/remove lagfixes, and possibly EXT2.
[Vibrant Android Development] joe.kerwin:
Is there an update soon on this? Most of us have been reporting recovery issues and soft bricks and I can't find anywhere where it is addressed, it can't just be coincidence, this ROM is awesome but recovery should work since eugenes jk2 base has it working?
[Vibrant Android Development] diaa08:
I wouldn't use the term most of us. I've been ruining this for a couple days without even a fc... I am not doubting some of you are experiencing issues, but this has been beyond stable and proven free for me. I did freeze wifi calling as it is problem-riddled on every rom, and I only applied old school lag fix (move data to nand), but my phone flies on this.
[Vibrant Android Development] tomm454:
how do i get the battery to last longer?
[Vibrant Android Development] mulcahyd:
Try to remove battery. Next, turn phone sideways, press both volume buttons down, connect usb cable to phone, and connect to pc. Open odin. Finally, reinsert battery. Download Mode should be displayed phone. That same method works for me every single time.
[Vibrant Android Development] jlatnyc:
I want this ROM to work but...

I was able to exit the login loop using ODIN, but cant get into recovery. I tried terminal, manual, CWM... nothing works. Need to apply SD fix. Can the SD fix be integrated onto ROM.

I really like Vanilla android, therefore want this ROM to work. I tried eugene's macnut and didn't like it at all, almost hated it. Other ROM's don't have screenies to checkout.
[Vibrant Android Development] Mike.Tyson:
Unfortunately I couldn't download the rom from fileserve.com, after jumping through the hoops they say I already recieved my "free" download. Is there another mirror? Or can somebody help me out?
[Vibrant Android Development] ugokind:
strange:

I tried to launch clockworks mod.. and it get soft bricked..

after more than 15 times removing battery.. starting.. with or w/o battery, odin or not.. it restarted.. but.. PANIC

pweew

that's only because I want to put a voodoo kernel

*******

I tried twice:

I confirm that the ROM doesn't WORK in clockrecovery!! so How can I do mods??
[Vibrant Android Development] stoober:
Has anyone fixed the sd card or calendar issues??

I tried sdcard fix, but still only being seen as a 2.4gb card by wundiws or ubuntu.
[Vibrant Android Development] Zeno78:
how long does ODIN3 take.. it seems that i've been stuck on cache.rfs for a while now.
[Vibrant Android Development] krazykidd:
The only FC I've seen is with the phone app and the call connect tones. I was running a stock with mild alterations on it (AOSP unlock screen, Power on and off screens changed, lagfix (which was removed prior). I wonder if people are checking if they can get into clockwork recovery (without installing, just normal recovery boot) first, then trying to install the package. Btw, I installed packages via ROM Manager, but had to select it when it booted into recovery.

Oh, also, bump. Anyone else experiencing slide down notification window difficulties?
[Vibrant Android Development] Zeno78:
anyone... i have all the files in the same directory as listed here:

http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/

1.Your Device must be in DOWNLOAD mode to use ODIN.

2.Get your phone into DOWNLOAD mode by turning off your phone and plugging it in. Wait for the green charging screen. Hold Volume Up, Volume down, and Power. Let go of power as soon as the screen goes black. A yellow digging Android should be on the screen. This may take a few tries to get it right. (Alternate Method if you have ADB access : use the command ‘adb reboot download’).

3. Launch ODIN, then disconnect/reconnect your phone via USB. It should then say a COM port right under top-right box. (Issues detecting your device on a COM port? Try connecting your phone before starting ODIN, and don’t do the disconnect\reconnect. It’s a finicky application.)

4.In ODIN, load each file with its corresponding field..PIT,PDA,CSC etc. (In this case we just use the PDA and PIT).

5.Don’t check anything else, the other two boxes should be checked by default (Auto Reboot and Reset Time)

6.Hit “start.” Be patient!

NOTE: COM3 worked fine for me. COM should not matter as long as you are using the correct drivers.

Finally we get some U.S love from Samsung firmwares.

For those looking for the Nandroid method, it is in the post below but only recovers system, data, and cache.Not your kernel/recovery or BASEBAND/RADIO (Modem.bin)

Thx to all helping work on the Vibrant. Especially Youneek, Scepterr, MS_Guru, Wes Garner, rhcp0112345, and anyone else I may have forgotten.
[Vibrant Android Development] JD76:
I can confirm that the new Rom Manager update still causes the phone to go into the Vibrant screen
[Vibrant Android Development] Zeno78:
I now have a phone icon then 2 periods the and yellow triangle with an ! the 2 periods then an pc icon..

what gives.
[Vibrant Android Development] ripsphone:
I had the exact same thing happen to me. Everything was fine. Opened ROM manager tried rebooting into recovery and got boot loop.

I had never messed with Odin before, but nothing motivates you to learn like a couple hundred dollar paper weight. Took me a while to figure it out. But there are lots of good resources on this website.

But my big question is what happened? I got everything reinstalled and the ROM working again, but I am afraid that I'm going to have to go through all that message again when the developer releases and update.

Basically I'm afraid to try rebooting to recovery right now.

Anyone got any ideas why this happens and how to avoid it again?
[Vibrant Android Development] Zeno78:
anyone.. please i'm now screwed... need the phone for work etc...

EDITED:

I got back to the Downloading... screen... trying ODIN again... hopefully it will work this time.

followed this:

ODIN is very finicky, although it usually freezes right before starting the flash, not in the middle of it. I would re-download your tar file, as it may be corrupted or damaged in some way. I would also re-download the pit file as well.

Luckily, these phones are very hard to actually "brick" beyond repair. If you get to a screen that shows "Phone ! PC", your phone is just preventing itself from booting due to a damaged file system caused by a bad flash. Close ODIN, unplug your phone, reload ODIN, reboot your phone into download mode, and try again.

If yopu have issues getting into download mode from that screen, dont give it. It takes a few tries. You can also try hooking up USB while attempting to boot into download mode, as Ive found that helps.

Usual time frame for this flash is about 10-15 minutes.
[Vibrant Android Development] mattb6288:
Gps still won't work but network location works. Please ix with j16 or 12 gps files
[Vibrant Android Development] ima757:
"I thought it was just me having the same problem with the stuck on "Vibrant" screen at boot up on this ROM........"

Had one of those D'OH moments and now finally have this great rom running.

The "D'OH" happened when I looked at the ROM Manager (free version) that I had while running the unoffical 2.2 tmo stock load.

At the bottom of the ROM manager there is an section called MORE RECOVERIES. I clicked on the the "All ClockworkMod Recoveries" and it brought a menu asking if I wanted to install more recovery options I selected "yes". A menu came up from where I could select my phone model and it downloaded what I'm guessing are it's updates. I placed this rom on the top level of my INTERNAL (phone) SD card and thru the rom manger I booted into recovery mode. Well the "green" green recovery menu came up, I selected the ROM and installed it. The ROM installed and booted up fine the 1st time, now the real test the 2nd reboot. I shut the phone down, Waited turned it on again and my phone didnt get stuck at the Vibrant screen!!!

Been running this ROM since last night with no problems and have done multiple re-boots without getting stuck at "vibrant" anymore !!!

Hope this helps someone out there.

"To all the great devs out there. I bow to your programing awsomeness!!
[Vibrant Android Development] Zeno78:
ok its takeing more the 15 minutes.. still on the cache.rfs.... any ideas? I even ran ODIN as admin....

<ID:0/003> Added!!

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> cache.rfs
[Vibrant Android Development] HYE_TECH:
My 2nd Vibrant had wonderful GPS on stock 2.1, it locked onto my location indoors. That never happened with my first one.

I wanted FROYO badly and AOSP was the way to go, stock looks much better than the others. GPS worked indoors still. After a day, it didn't work, or so I thought.

I now notice that if I have just GPS checked, it's hard to locate but if I have "use wireless network" "use GPS" and "sensor aiding" checked, it works flawlessly. Exact location and I'm not talking about the icon with the location ring. It gets my exact position. NO ESTIMATES, EXACT!

I've been using AOSP 1.0 since Monday. It's a pretty damn good ROM. Smooth. I tried 1.1 but flashed back and then that's why the clockwork issue started happening. Besides the recovery issue, I don't see anything wrong with the 1.0 ROM....I love it. Adobe Flash is a little buggy but what do you expect...

The thing I hate besides the recovery issue is the camera app. I deleted and tried to install the camera.apk through ROOT EXPLORER but it doesn't work....any suggestions?

I'm going to have to ODIN to stock (as soon as I can find someone with a PC) so I can try to flash 1.1 again.
[Vibrant Android Development] Zeno78:
STALLED... 30 mins now...
[Vibrant Android Development] thegreatcity:
Yes I was at first, it would get stuck and wouldnt respond to touch. Had to use the back button to get it off the screen.

A reboot fixed it, haven't had any troubles since.
[Vibrant Android Development] ekeefe41:
This fixed my market issue

Thank you
[Vibrant Android Development] diaa08:
Happens at that point sometimes... All I can say is I've just pulled the phone and done again... That being said when that's happened it was tough to get back into download mode and you get the scarry computer exclamation mark screen. But I have always eventually gotten back into dl mode and odined back successfully. Just start calm and be patient. Might want to read a post I made a couple months ago..
[Vibrant Android Development] kevinlouie:
I too was having issues with soft bricking coming out of clockworkmod. I was able to get around it by reflashing clockwork recovery, and rebooting. After that clockwork recovery worked.
[Vibrant Android Development] diaa08:
Post above in response to this.
[Vibrant Android Development] johndoe411:
Zeno78, download ODIN version 1.3 and try it.
[Vibrant Android Development] mikeku:
http://www.mediafire.com/?q3lb5fmf35nwffk
[Vibrant Android Development] Zeno78:
FINALLY... back to stock... what a pain in the ass.
[Vibrant Android Development] krazykidd:
Okay, after tinkering around with Zeno, I figured out that the phone in Clockwork recovery does NOT like to boot into recovery and seems to like to hang in the Vibrant load screen. Not too big of an issue of a loop. I got out of it, here's how.

1. Unplug everything, battery & usb cable.

2. Have odin start and wait.

3. Insert battery.

4. Power up the phone.

5. Turn phone on and plug it in as soon as vibrant screen shows. Odin should pick up the phone at 0:[COM3]. If it doesn't, you didn't plug it in fast enough.

6. Wait about 15 seconds.

7. Unplug battery then phone again.

8. Insert battery into the phone and turn it on.

9. Wait for it, should take less than 2 minutes tops to boot back into 2.2 froyo.

I'm currently running through the possibilities of the clockwork recovery versions to see which one is good. It seems that the biggest issue is the fact that people are trying to wipe their batteries and soft bricking from there.
[Vibrant Android Development] Zeno78:
second'd ... reflashing AOSP now.
[Vibrant Android Development] Zeno78:
Make sure you are using ODIN3 1.3

Make sure your pit ends in 803
[Vibrant Android Development] Stridermatu:
Just my two cents with this ROM,

I had the same problem with a soft brick after trying to use ROM manager to install the SD card fix. I used ODIN to recover and have since been running this ROM for the last two days. I was going to go with Macnut but decided not to. It worked out because this ROM is rock solid. I haven't had the Google talk, Wifi, market or other issues that many others have had. My internal memory was hosed but the sd_card fix took care of that. My 32GB mSD card wasn't reading correctly on my laptop or in Android but I realized that wasn't the ROM, that was 1 part my own dumb assness and 1 part a registry issue with my laptop that causes a 0x80070057 error. My laptop read my card as a full 32GB card and some of the data could be moved but some data caused the error, trying to copy data to or from the card cause the error. Android didn't show anything on the card even though sd card settings showed 29GB for the sd. I reformatted the card before I realized that Android wasn't "reading" the data because I was looking in the old "SD" folder and not the new "external_SD" folder where the data was after the new ROM was in place. DOH! I thought the card was corrupted. I have since transferred 6 GBs of music to it but because of the mentioned error, my movies aren't copying. I'll handle that when I get home tonight.

My point in this, for those with a soft boot, get ODIN if you don't have it already. I can't stress that enough. It brought me back from the dead twice and it's not hard to use or hard to set up. For the SD Card fix, after I flashed the ROM, I flashed the SD card fix before I rebooted the phone from CW recovery. In other words, flash the 2.2 ROM, but before you reboot the second time, flash the sd card fix. It worked for me as I was paranoid about trying to boot back into recovery after the second soft brick. This may be a no brainer for many on this site but I'm still coming to grips with flashing and ROMS and the like as are some others whose comments I've read. I'm not too sure I want to use ROM manager in the future though.

If ODIN looks like it locked up, be patient. If you wait 10 minutes or so and there's still no activity, you may have to restart the ODIN process over again. ODIN can be finicky at times. It will work perfectly one minute but flip you the bird the next. Keep trying and be patient. Check your steps and make sure you follow the instructions to flash very carefully. Sorry for the length but I'm just trying to help where I can based on my own limited experience. It's amazing what this community does for these devices which, in most cases, is far more support than the actual manufacturers provide.
[Vibrant Android Development] miglop:
So how does this "wifi calling" work is it free or something do I just need to be connected to my wireless router or something and im done someone please explain it to me please I wanna flash this rom but I need to know if this is free to use or do you have to do monthly payments or something?
[Vibrant Android Development] samurai_war_lord:
ROM running great except for one thing. I'm having a bunch of apps running in the background that usualy dont! battery draining is being a *****
[Vibrant Android Development] Stridermatu:
From my understanding, wifi calling still uses minutes from your monthly plan.
[Vibrant Android Development] krazykidd:
My understanding of it is that instead of using your phone's actual GSM SIM Card connection, it uses a wifi connection. They're getting lazy and trying to charge you for something else that could be free. Look into if you want, text messages are actually just a hack for phones communicating with their respective towers.
[Vibrant Android Development] player4lifeov:
Tried this and it took me to

--Appling Muti-csc...

Installing Muti-csc

--Install from sdcard...

FInding updates
[Vibrant Android Development] Zeno78:
correct.. your minutes will still be used... but you can make calls when you are inside as long as you are connected to a wifi access point... Great for my house as the cel signal sucks.
[Vibrant Android Development] mulcahyd:
My battery seems to be pretty good, I can easily get 8+ hrs. Lol...
[Vibrant Android Development] Zeno78:
is this kernel compatible?

[KERNEL]Project Core v2 - Team Whiskey Production - 11/06/10
[Vibrant Android Development] ohnoezmahfone:
Also, does USB tethering work for peeps? I get nothing on my computer when I try to use it, with Win 7 x64.