yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] djluis48:
Hm...i can get into recovery using the hardware mode, so i guess im not hardware locked?

How did you make it to Download Mode?
[Vibrant Android Development] Duntkno:
been playing with cyna- for a week now. Have used two diff nightlies. noticed im stuck on E data alot. Occasionally goes to 3g, or h, but rare. Is that a known bug or just my own problem?
[Vibrant Android Development] Jackdog89:
Make sure you have ODIN setup to run BEFORE you plug your phone into the USB. It should go into download mode without any problems. I just did it less than an hour ago without any problems.
[Vibrant Android Development] iynfynity:
Try removing the battery then hold the buttons and plug in the USB. After that put the battery.
[Vibrant Android Development] TBDakotaM:
removed the battery, held volume buttons down while plugging in, and then replaced battery.
[Vibrant Android Development] djluis48:
How do i setup Odin to run? I just have it open, do i need to do something else?
[Vibrant Android Development] numberoneoppa:
Wrong

Sent from my Vibrant using the XDA for Android app.
[Vibrant Android Development] bobbbb:
Wish if u dnt know how to use odin leave this thread... u need to place the correct files into odin for it to work
[Vibrant Android Development] liridonb:
Try aio tools 2.5 you can put any of rom you like.no need for combination key.
[Vibrant Android Development] djluis48:
Eh, i want to learn? Thanks?
[Vibrant Android Development] inrelief:
This thread isn't the proper place to learn to use odin.

There are threads already dedicated to this discussion.

This thread is for discussing CM7 nightly vibrant builds ,which have quite literally nothing to do with Odin.

Quickly googling also gives you youtube video walkthroughs in case you're having difficulty, for instance googling "vibrant odin" returned this gem of a link:

http://www.youtube.com/watch?v=AnY7P14JSWQ

Long story short, the search button (and search engines) are your friend.
[Vibrant Android Development] DEFINITIONOFREAL:
Can I use sgs kernel flasher to flash a kernel to go back to froyo, or do we have to odin
[Vibrant Android Development] zyrinx:
Don't you love when people that have no clue what they are talking about give out blatantly wrong information?
[Vibrant Android Development] djluis48:
SGS Kernel Flasher isn't compatible with CM7, you need to Odin back to stock if you want Froyo again.
[Vibrant Android Development] DEFINITIONOFREAL:
thanks for the info
[Vibrant Android Development] zyrinx:
No. You have to Odin back.
[Vibrant Android Development] djluis48:
The problem isn't i don't know how to use Odin, its that my phone won't go into Download mode.

Im no discussing CM7 Nightly directly, but i think that this problem started after i flashed CM7, so im asking here if anyone have this problem.

Thanks, but i have seen most of that stuff. Nothing worked.

Thanks for the advice...?
[Vibrant Android Development] atinm:
CM7 does not touch bootloaders. So if you could get into download mode before by using 3 buttons, you should still be able to now. Otherwise, you need a JIG.
[Vibrant Android Development] droidfan77:
I flashed to Nightly 9 this morning and I'm now having the same wifi problem that others have been reporting. Wifi will stay on fr only about 10-20 seconds and then it shuts off for a couple of seconds and then turns on again in a permanent loop.
[Vibrant Android Development] apollo15rover:
Kang Kernel broke modem radio.. so guess for the time being no custom kernel seems to be working on Build 9
[Vibrant Android Development] movieaddict:
In my opinion its really, really haRD to brick a vibrant!

turn off ur phone

turn on odin and put the pit file and tar file in the proper places on odin and click re-partition.

now plug ur usb cable into ur phone and into ur pc.

Now hold down the 2 volume buttons first and then the power button and let go of the power button when u see vibrant logo and it shoudl godirectly into download mode.

And if that doesnt work pull out battery and try that method.
[Vibrant Android Development] djluis48:
I see, well, i guess thats my only option then. Thanks.

Just tried that, no luck either. If the battery its in it place, the moment i plug the USB, the phone just boots normally. And if i remove the battery, do the procedure and put the battery back in again, it just boots. I guess the JIG is my only way.
[Vibrant Android Development] Trev420:
i flashed update 9 over update 7, and i cant place, answer, or check voicemail. does update 8 have this problem? or should i just wait for 10?
[Vibrant Android Development] cashyftw:
Go to 8, and wait for 10 (: battery on 8 isn't great though.

Sent from my SGH-T959
[Vibrant Android Development] rel500:
OP this should be on the front page. Lots of ppl don't know how to get back into download mode.

How to get to download mode.

Take out battery

plug usb in

Hold volume buttons

Put battery in

Either download mode or phone to pc... either or u are there. Enjoy froyo again!
[Vibrant Android Development] droidfan77:
Although if you need your wifi to work as well you should go back to Build 6. It looks like that is the last build that wifi worked consistently on.
[Vibrant Android Development] krntehknik303:
Anyone have a problem with the dialpad when trying to get into voicemail? I press the right numbers but the automated system reads it differently. How would I fix or get into my messages?
[Vibrant Android Development] ke.laguardia:
maybe i missed something, but is there a reason that i can drag a notification left and right on the dropdown bar? is that some new feature?
[Vibrant Android Development] inrelief:
::golf clap::
[Vibrant Android Development] jzero88:
Yup seems to have issues hearing on both ends of a phone call, there is nothing. Going back to #8.
[Vibrant Android Development] djluis48:
I don't know why you people still keep this up. Atinm said that its not caused by CM7, and i said "Ok, i see, thanks." Thats it. Move on. Jeez. You people make souch a drama out of anything.

Plus, seems that he added the "Make SURE you can get into Download mode using only buttons (no other method, Download mode from just buttons is essential)." Was added after he asked ME if i was able to enter Download Mode before i flashed CM7, and i told him that idk, never tried before.
[Vibrant Android Development] g1flasher:
X2 Probably 100 or so pages could be erased from this thread for stuff, that is either repeated, been answered or does not belong.
[Vibrant Android Development] MStrawder:
I can give you the method that has worked for me time and again and I even believe it's been mentioned already.

1) Remove battery, SDcard, and SIM.

2) Hold Volume - only (as in the volume down key) and the power key at the same time.

3) Plug in the USB cable (while still holding those two keys down)

4) Insert battery (while still holding those two keys down)

This SHOULD get you in there. Otherwise, yes, you'll need a JIG. I have had instances where it didn't go into download mode instantly. There was a 2-3 second delay, so I kept the buttons pressed during that time and it kicked in.
[Vibrant Android Development] zyrinx:
Wouldn't that imply you have the wrong bootloader flashed? That sounds like you're using the Fascinate's download mode button combination.
[Vibrant Android Development] ajrogers111:
Same here on the no sound issue on #9... I also tested the mic in the video recorder fir the heck of it, and it wasn't recording sound there either... it would play sounds through the rear speaker from previous recordings and music player... flashed back to 8 for now too...
[Vibrant Android Development] MStrawder:
No as since I purchased my Vibrant back in August, that has been the combo. Vol - and power were for Download Mode, both Volume + & - and power were for recovery, Volume + and power for upload mode.
[Vibrant Android Development] lolobabes:
Easy way:

Start with a rooted Eclair/Froyo running Eclair/Froyo Bootloaders (do not ask us how to do this).

Install ROMManager Premium.

Flash ClockworkMod Recovery. Pick Vibrant (MTD) (ignore the warning about not having an official, pick ClockworkMod 2.x).

Make sure you can reboot into ClockworkMod recovery from ROMManager. Reboot and get back into ROMManager Premium.

Choose download ROMs.

Pick the CyanogenMod Nightlies.

Check the Google Apps addon.

Check Backup current ROM!

Check wipe data, cache, dalvik cache.

Let ROMManager finish the installation.

i have been trying to do this but still getting same error

"assert failed: getprop("ro.product.device") == aries"

in the end it says status 7

seems recovery 2x.x not working properly

please help ty
[Vibrant Android Development] Trackstar996:
Yeah you can download it from the cyanogenmod website

Sent from my Vibrant of course!
[Vibrant Android Development] MStrawder:
You can download it from the link in the OP and flash it through recovery. If you're able to though, I recommend you get the paid version to support a good program and simplify the flashing/downloading process.
[Vibrant Android Development] ChristoA1:
Yes, you have to install CWM, download the nightly from download.cyanogenmod.com and GApps if needed, and install through CWM.
[Vibrant Android Development] lolobabes:
thanks guys i just asked that coz am getting same error as i posted above
[Vibrant Android Development] Tha Maxx:
so whatever happend to getting the nightlies pushed to our phone? ( i purchased rom manager. also i have cm7 registered to recieve them) did i miss something or is it not even in rom manager anymore?
[Vibrant Android Development] ChristoA1:
That's interesting... If you open /System/Build.prop and look for the ro.product.device line, what is there?
[Vibrant Android Development] ChristoA1:
Never mind, I missed the part in parenthesis... It may be just because there's a delay between the nightlies going up, and being registered in ROM manager... Notifications work fine for me on the G2/Vision
[Vibrant Android Development] ChristoA1:
If I had to guess, you need to go back to stock ROM first... Your product line is ro.product.device=SGH-T959V whereas it should be ro.product.device=aries.
[Vibrant Android Development] Tha Maxx:
do you have the vibrant? does the new update fix the mic issues?
[Vibrant Android Development] ChristoA1:
Yes, however it's on Build 8; I think the mic issue is on 9?
[Vibrant Android Development] lolobabes:
this is a friends vibrant just trying to help him dont know where to find that am used to my N1 ty
[Vibrant Android Development] lolobabes:
aww not again, are there other variants of vibrant getting confused, this is t mobile vibrant by the way lol
[Vibrant Android Development] Tha Maxx:
i am on the one from 5/16/2011 build-grj22 ( is what it said on the phone)

i dont know what build this constitutes but i would love to fix the issue. mute and unmute is getting old already.. :(
[Vibrant Android Development] ChristoA1:
I'm completely familiar with what you've got; I have the same one... With the T-Mobile Vibrant, the Build.prop should reference "aries". In the CM7 build, ro.product.board=aries and ro.product.device=vibrantmtd. However in the stock ROM, it looks like you should have "aries" on the .device line. Your friend is running Bionix ROM, which may use the different line.
[Vibrant Android Development] lolobabes:
if i try to restore the rooted stock rom eclair then flash this would that worK? oh i think thats what you meant on your first reply ty
[Vibrant Android Development] cojonesx:
0516 is quite an old build now, 8 is 05222011

the mic issues are not fixed on 8, there are additional problems on -9 (as in no sound on calls at all)
[Vibrant Android Development] ChristoA1:
Yup, you should not have any problem once you go stock first. I'll admit I haven't used ODIN and am not too familiar with it, so READ UP ON IT in case going back to stock from Bionix isn't as easy as a NANDroid restore...

Hope this helps!!
[Vibrant Android Development] Tha Maxx:
thanks man i am going back for now then or might go back to miui seeings that its fixed over there.
[Vibrant Android Development] MStrawder:
What is the exact name of the file you're trying to flash? I'm thinking you somehow have the wrong file or possibly the wrong recovery. Which ROM are you currently running also?
[Vibrant Android Development] ChristoA1:
Thanks for this. One of the hardest things for me to keep up with is the dates vs build numbers. Especially considering I'm tracking two different phones, and some dates may have multiple builds! D:
[Vibrant Android Development] lolobabes:
flashed cm_vibrantmtd_full-9.zip

am on teamwhiskey froyo, i think its bionix frost
[Vibrant Android Development] lolobabes:
thanks ill see first for there are other options, i did odin before and i hated it lol

by the way cant i just restore to my stock rooted rom backup? i have done a nandroid backup of it
[Vibrant Android Development] bik245:
Hello, is there way to turn off bln from the rom or do i have to install the app to control it?
[Vibrant Android Development] Paging Dr B:
No. It uses a different file system and a different kernel. You have to ODIN back if you want to go back to the way you had it before.
[Vibrant Android Development] jrafael:
Please use the search function.
[Vibrant Android Development] snce1980:
http://xdaforums.com/showthread.php?p=13983692&highlight=bln#post13983692
[Vibrant Android Development] Relikk356:
I was under the impression that people are intelligent enough that they would understand that I meant nightly revision 9 and not CM version 9. I really didn't put much effort into what I wrote. Thanks for the clarification!

Originally Posted by Relikk356

I went from latest Bionix to CM7 Ver 7 with no problems. I have upgraded to version 9 since. Works great!

1. Download newest version of ROM Manager.

2. Go to Download Rom in ROM Manager

3. Choose CM7, I'm not sure why version 7 would install different then 9 but I can guarantee version 7 installs fine from Bionix.

4. Once ROM is downloaded, I checked all options, BACKUP, Clear Cache, and clear Dalvik's cache.

5. It will install itself. Download google aps rom, install from 3 button method. For some reason you have to get into boot manager the long way for the GAPPS to work.

Only other problem I had is for some reason I can't see the nightly builds as a downloadable ROM. When this happens I just re "Flash Clockwork Mod Recovery" again; choose vibrant and ver 3.x. Now you should be able to see CM7 mod in download section.

version 9 is only the nightly build. it is not the version of the ROM itself.

The rom will be CM7 until a new major build of Android comes (Probabely 2.4)
[Vibrant Android Development] inrelief:
ro.product.board=SGH-T959V

You're running a custom ROM, and failing validation.

As the OP says, odin back to stock.
[Vibrant Android Development] zyrinx:
So... in phone calls I have no incoming sound whatsoever. Any ideas? Bad flash? I just flashed this morning. I Odin'd to stock. Installed a voodoo/CWM kernel and then flashed CM7. And my first phone call of the day... nothing. I tried different outputs i.e. bluetooth, speakerphone etc. I even rebooted, but nothing.
[Vibrant Android Development] Abu-7abash:
If you're on version 9 go back to any previous one. If you're not, then mute/unmute on every call.
[Vibrant Android Development] inrelief:
I believe it's established that in nightly-9, phone calls aren't working.

They are somewhat working in nightly-8, however I don't have working WiFi in nightly-8.

I recall seeing nightly-6 as having both working wifi and somewhat working calling.

I refer to somewhat working as some calls have difficulty hearing you on the outbound, and you must mute/unmute to make it audible.
[Vibrant Android Development] zyrinx:
Well damn. Yeah. I just flashed Ver 9. Guess. I'll Odin back and install Ver 8.
[Vibrant Android Development] cpittman:
Mods please clean the 1700 duplicate posts and make this thread useful again. And to the people asking questions answered in the op or q&a thread, what makes you think you'll get a different answer by asking here? YES YOU MUST ODIN. NO THERE IS NO WAY AROUND IT. YES THEY ARE AWARE OF THE CALL MIC ISSUE. MUTE/UMUTE IS THE ONLY FIX. Seriously doesn't it say in the op this is not for noobs yet 75% of this thread is noobs asking how to fix their screw ups.

Sorry about the rant. Guess I shouldn't be on xda while quiting smoking. To those who are using this thread as much as I am, I think instead of answering the same questions 500 times we should try not to get upset and point them to the correct thread and nothing more. If the mods can't be bothered to mod we might as Well try to keep the thread as clean as we can ourselves without being wanna b mods or jerks. Just my 2 cents.
[Vibrant Android Development] numberoneoppa:
I've read every post in this thread and a good number in the last one and couldn't remember this question being answered. Sorry if I missed it.
[Vibrant Android Development] jrafael:
This is what I did. Beware its my phone and my own experience. Im not responsible if doesnt work you.

1. Download and install neldar sgs kernel flasher from the market.

2. Download all cm7 required files (initial kernel, initial rom, latest nightly, efs backup) and place on root of sdcard (not external microsd).

3. Reboot using 3 combo button to red voodoo recovery and flash vibrant efs backup and reboot once done.

4. Using sgs kernel flasher, locate the cm7 kernel, untick auto reboot, and flash.

5. Pull battery, wait few seconds then put battery back up and use. 3 button combo to go straight into recovery.

6. Format system, data, cache using mount&unmount menu.

7. Flash initial cm7 rom once done while still in recovery do a factory wipe. Reboot.

Then you can flash your latest nightly as normal.

PLEASE USE THIS METHOD AT YOUR OWN RISK.
[Vibrant Android Development] glenelgstudio:
I hope you get a vibe I'll look out. I came back to the Vibrant from the Nexus s and the Galaxy s 4g mainly because the vibe has the 16gb onboard storage and sd card slot which makes a difference. The display is the same and I have not noticed a speed difference. I'm getting 1850 quadrant and with the front facing camera gives this phone a lot more life. I love this rom but because of the ffc I use Bionix or Bionix Frost. If you want me to be a gunny pig I will I'm the master at using odin I can come back from any state. So far.
[Vibrant Android Development] glenelgstudio:
I had the black screen on camera but when you take the pic it comes out ok. Did not fix it just flash again and got it working
[Vibrant Android Development] Andreal:
The thing is I don't have win7, on 2.2.1 I needed to flash wpa supplicant to see adhoc (!) connection, I don't know if gingerbread have something like that
[Vibrant Android Development] Abu-7abash:
How's battery life one this? It's all Im looking for to be honest :D
[Vibrant Android Development] diorDNA:
Ive been getting about 20 hours to a day moderate use without a custom kernel. I've also been using the setcpu Screen Off profile 800 MHz Max and 100 Min.
[Vibrant Android Development] J.a.M:
better than MIUI but worse than the trigger and other froyo roms.
[Vibrant Android Development] german103:
The screen turns off while gaming/watching videos. Any solution for this?
[Vibrant Android Development] atinm:
No, we don't even have tmobile. :)
[Vibrant Android Development] atinm:
Sorry. I read the "will there be ... in the near future" in the following:

as a "when" because "near future" implies an ETA.
[Vibrant Android Development] dligon:
see now that's a dedicated dev
[Vibrant Android Development] atinm:
I only do this because previous Vibrant CM developers abandoned it. I have put in too much work on CM support for SGS and so maintaining Vibrant is only a little more work. A user on xda has offered to send me his broken screen Vibrant which should be good enough for me to test releases on at least and another is sending me a first generation ffc so I can at least make sure it works.
[Vibrant Android Development] apollo15rover:
Hey I just noticed a big series of updates on sourceforge for today.

If I'm running latest (5/4) CM7, do I need to start over with all of those files or can I just flash the 5/6 nightly update?
[Vibrant Android Development] atinm:
Uploaded 20110506 update. Changelog is updated in the OP. Also notice that initial install is much easier now. Updating is the same as before.
[Vibrant Android Development] kevinngu:
i just thought of something, should i be flashing each update? or just the latest update?

below answerd m yquestion. thank you!!!

so for 5/6 we have front facing camera working?
[Vibrant Android Development] atinm:
Just the nightly. The latest nightly is always all you need if you are already running CM7.
[Vibrant Android Development] kevinngu:
does it matter which one or how we flash the new kernel and update?
[Vibrant Android Development] atinm:
If it says initial, and you are already on CM7, don't touch it. Just use the nightly. Initial is for Initial move to CM7 from anything Samsung.
[Vibrant Android Development] kevinngu:
thank you sir!!! i am uber excited!! bout to flash now!
[Vibrant Android Development] Saiboogu:
Don't odin back - just reflash 8, no wipe needed.

I had worthless wifi in 8, went back to 6 with a few minutes effort - no hoops to jump through.
[Vibrant Android Development] zyrinx:
Haha. Well, damn. Didn't realize it would be that simple to jump back, but I suppose I should have. Odin is already through though. So, I'll just do a quick reflash of 8 and be done with it. I suppose I could have retained my settings by just flashing back, but I suppose I'll just have to suck it up and reset everything.\
[Vibrant Android Development] droidfan77:
I installed Build 9 this morning and then went backwards one by one. I loved how fast Build 9 was, but it as way too buggy for me with the calling problems and the wifi issues. After then downgrading to Builds 8, 7 and 6, it seems to me like Build 6 is the most stable and bug free of these builds so far. Also Build 6 has given me the best battery life so far (I didn't give Build 9 a chance to really test the battery life though).

Again I really appreciate all of the hard work the devs are putting in to this ROM. As is it's wonderful and once they get it to an actual release candidate stage I can only imagine how amazing it will be.
[Vibrant Android Development] apollo15rover:
Is GPS Working?

I have a mic issue. .

Tried to install the Captivate version because they have a cool wallpaper on theirs and my phone's bricked; do I have to ODIN now?

Do you guys support Platypus?

NOT asking for an ETA on when you are going to add WiFi calling, but could you just fill in the following give or take an error factor of 1 or 2 days..

___/____/2011 ___:___ (24hr format please)

Whew.. felt good to get those out..
[Vibrant Android Development] inrelief:
..I laughed.
[Vibrant Android Development] cpittman:
lol wish the xda app had a thanks button. I needed that laugh.
[Vibrant Android Development] cpittman:
Oh and you forgot "can I install touch whiz... on this?"
[Vibrant Android Development] gamikzone:
i agree this thread hasnt even been open for a month and already has so much unneeded posts
[Vibrant Android Development] archie53:
Thanks for the last few posts, they made me laugh after a crappy day.

Sent from my CM7 Powered Vibrant
[Vibrant Android Development] ChristoA1:
Yeah, if I could get a definitely answer to this one, that'd be great. Could a dev please answer this now? And PM me once it's answered because honestly, have you seen this thread? I can't be bothered to actually look for the answer once it's posted :/

And if you really want to answer in 12-hour format, I guess that's fine, but it's just a waste of time, and really, you guys should be fixing the no-mic problem with all that extra time.

Thanks.
[Vibrant Android Development] zyrinx:
But you see, if they were to clean the thread they would have to wade through more douchey responses than repeat questions because every time someone posts a question again 5 people post back with completely irrelevant and asinine responses. So, rather than keeping your mouth shut and keeping the thread cleaner, you vent your nonsense and just take up more space. :rolleyes: