yashsingh1/xdaforums huggingface dataset:
[myTouch 3G, Magic General] alyxvance:
Can you give me the console command to flash it from fastboot? Is that the only way to flash recovery? I have tried flash recovery <recovery_name.ext>, but with no success, i get the :

C:\android-sdk-windows\tools>fastboot flash recovery recovery-RA-Magic32A-6.35-v1.6.2.img

error: cannot load 'recovery-RA-Magic32A-6.35-v1.6.2.img'

EDIT:

Me stupid, forgot to place the recovery in tools folder :)

I'll try now to load some ROM for 6.35 radio, or maybe downgrade the SPL/Radio :)
[Vibrant Android Development] designerfx:
it's been strongly advised by the programmers working on CM6 to not flash to 2.2

7/28 9:25AM

Scepterr:

"Vibrant and Captivate users do not flash the i9000 JP1 & JP2 Froyo release it does not work correctly and you can not revert back." I would suggest to stay away from all that is I9000 for now.

Wesgarner has started work on the Galaxy S and it is going "fine".
[Vibrant Android Development] acjames:
I can co-sign this. You WILL brick your phone. I will wait.....
[Vibrant Android Development] Mr_Tricorder:
Talk about giving someone just enough rope to hang themselves. . .

I want to try this out so badly, but I can't risk screwing up my Vibrant. I'm a huge follower of CyanogenMod, so I'll wait.
[Vibrant Android Development] MS_Guru:
Makes me laugh...

I think they just wanted to be first... Almost there guys. It really is running nicely. And honestly, there's no hope in hell of brickin this phone, I've been trying. Shes a stout little B.. :D
[Vibrant Android Development] Mr_Tricorder:
I doubt they were going for first. CM is more about being the best than being the first.
[Vibrant Android Development] ttabbal:
Cool. If you can get data working, I'll give it a go when I get home so I can run Odin. No winders with me right now. :)

Oh, and verify that we can revert to a prior backup. :)
[Vibrant Android Development] fykick:
No...its true. These methods will brick your phone. I thought it was just something i was doing wrong but after going back from xjm1 and 2 i have bricked two phones....so im gonna delete my post as this is now a somewhat verified fact for me.
[Vibrant Android Development] s15274n:
I warned you guys last night to not flash this. Wait for the real thing. Not like our phones are not already amazing.
[Vibrant Android Development] MS_Guru:
Well I'm not sure what to tell ya, but I'm bookin right along here. And when I say I've tried to brick, I'm not joking. When I first got this thing I tried shoehorning every ROM, Flash, Recovery, I could get my hands on to this phone.

Can someone do me a favor, go into clockworkmod and give me a breakdown of the keys and there associated numbers? I've got clockworkmod on already, but without a home key you get stuck in recovery. A quickie remap, and I'll be done.

IE.. Volume up is 164, I think? Volume down, Power, and each touch key. Theress a key feature in there, but don't wanna flash back just for that.
[Vibrant Android Development] acjames:
I flashed mine before this firmware. But it was an overseas firmware and when i tried to revert back my phone went totally dead.
[Vibrant Android Development] pychobj2001:
i'm pretty sure with this you would have to go back to a stock kernel and then do a nandroid to stock 2.1 you made w/ nandroid...i could be wrong tho..but i don't wanna mess with my kernel unless i have to so i'm going to wait till this is an rom version of the .zip flavor and it's ported for the vibrant. or just wait for CM6, but the only thing i'm worried w/ cm6 about is, are we going to lose allshare/tv out/ 5.1 headphone simulatioin / the music player / dialer / phonebook / things i actually like from the samsung rom... but yeah i will flash this puppy once ported.
[Vibrant Android Development] ttabbal:
Vol Up - 42

Vol Down - 58

Power - 26

Menu - 158

Home - 139

Search - 107

Back - 28
[Vibrant Android Development] MS_Guru:
Well it is pretty well done, just need the key numbers. Hint hint... Go to recovery and click the option for key... something or other. Its really really easy. :)

Thank you ttabbal ... :D
[Vibrant Android Development] All~G1:
sounds like MS_guru is more then the average user.

Good luck in your modding. Hope to hear more great news soon!
[Vibrant Android Development] eweo911:
@ MS_Guru,

Hope you get it all figured out
[Vibrant Android Development] rmind01:
Man...I'll pass I did the other "stock" "pre release firmware" and I damned the moment I did it. I'm back to stock with 3g and camera working thanks to scepterr but still with euro baseband. No thanks!
[Vibrant Android Development] fykick:
Well If it is just a fluke, Time will tell. As more people are willing to flash a foreign rom for Froyo than just a faster kernel. So we will see if its just an unlucky few who have bricked their phones or when all the people who flashed to this revert back and brick their phones. I know for a fact I have bricked 2 phones, reverting back to US firmware from any firmware after JG5...IE: jm1 and jm2. The first brick I assumed was a fluke...but then when the second one from the same method...I stopped testing my luck. I know before when using JG5 and before, I was having success, but something in JM1 and after are causing bricks. There is no guarantee that this bug is not present in the XP1 and XP2, but after two bricks, Ima hold off til CM6.
[Vibrant Android Development] Minker17:
I hear ya. There is plenty I don't like on the phone, but there are some things I would like to keep.
[Vibrant Android Development] rsfaze:
do a back up with something like Titanium backup. I have ALL of the apks that came with this phone. The day I flash another rom that doesn't I can restore the Samsung apps back.

The only issue I could for see is if flashing 2.2 and the Samsung apps are not updated until they officially release 2.2 which then the apps should all receive some update to make them compatible if they are not already.
[Vibrant Android Development] TGA_Gunnman:
If you have the money to gamble with I don't see a problem with it. But if you can't afford to loose your one and only phone that you depend on is quite another.

Have you tried to revert back from the flash yet, to stock? Do you have data functioning yet?

The CM team are not so vain that they would want to be first. They are just being as thorough as possible. When they have a beta to test they post that with a warning and work with individuals to get the bugs out. But no one is perfect.

I do appreciate your efforts. But please thoroughly test your processes including a back-out process.
[Vibrant Android Development] cparekh:
On the other hand, the CM team has always shown a great ability to take things from other UIs that are nice and bring them into CM. I would think that they would like to bring some of these features from Samsung's UI into CM.
[Vibrant Android Development] Minker17:
DO you guys think any of the apks will require any framework removed for CM?
[Vibrant Android Development] rhcp011235:
First i want to say thanks MS_Guru. We see you have been doing alot.

But, i want to say this. Just wait on the offical release of 2.2 from TMO/ATT.

You do not want to be locked to the EURO baseband/radio. As you can see this has been going on for awhile now. and there is no radio nor baseband.

The phone is great. its fast. it does it all. Just wait.
[Vibrant Android Development] MS_Guru:
If your wondering whats takin so long, I'm tryin to set this thing up in a way that a noob could feel comfortable with. Still goin at it though.

@rhcp0112345 ... This is fun man. I love this kinda stuff. Kind of a thirst for knowledge thing. And its always fun to be first. ;)
[Vibrant Android Development] MS_Guru:
Not only that, I've come across so many cool apps and widgets that I've been integrating into my own builds. But on that, its a work day, and I gotta go make a few bucks. I'll be finishing this up tonight for sure.

Current stats... Rooted, clockmod, smooth and clean. Smooooooth. :D

Sorry to leave you folks hangin.
[Vibrant Android Development] youneek:
What's your linpack score and quadrant score?

Sent from my Vibrant
[Vibrant Android Development] kelmerp:
You're such a tease....post a Quadrant score screenshot as soon as you get a chance. What about App2SD? Full flash support? Inquiring minds want to know!
[Vibrant Android Development] glensta:
Good idea to wait on this - I bricked my phone and had to go back to return to T-mobile. Thank God for their great service. Think I'll wait for an update.zip
[Vibrant Android Development] EugeneKay:
Another word of warning from another Vibrick owner. If you try to downgrade from JP1/JP2 using Odin you will end up with a hard, all-black-screen brick after the reboot. This is not the cell+!+PC soft-brick. This is a total will-not-power-on paperweight.

Flasher beware.
[Vibrant Android Development] NexVision:
All of you guys saying not to do this stop crapping the thread.

Here is what I know.

Can the vibrant be bricked beyond repair? Yes as I have bricked 2 of them.

Does that mean you should never flash your phone? No.

If noone ever bricked then we would never know what not to do.

As it says in her first post user beware. If you read that and still choose to do it thats your own problem. If you don't read it and do it anyways again thats your own problem.

If you want to wait for official release then why are u even reading the thread move on and continue on your day.

All I am saying is great work Ms_Guru keep it up and keep plugging away and to the everyone else seriously is your life that boring u feel the need to come in and knock a contributor to the community about how u wont use it. Very simple don't use it don't comment either cause all your doing is taking up space.
[Vibrant Android Development] fykick:
Essentially our contribution would be to save you guys the trouble of having to return your devices by giving a warning about what can happen, and express the actual risk, rather than a simple disclaimer which even fully developed roms display in the tutorial. While there is normally no risks involved in things that have disclaimers, unless you use it totally inproperly. There is risks involved in this that are possible even if you do accomplish everything properly.

All I ask is, have any of you successfully flashed this firmware, and then flashed back to US firmware, or will I have to go buy a device from walmart just to test the method on myself. I'm sure not too many would flash back if its running as smooth as the OP says, but so was the Ext 4 Kernel I had running on it. But that didn't stop me from flashing back and bricking two different phones. And I mean real bricks, not the cell---pc screen. Totally unresponsive phones.
[Vibrant Android Development] aloxotls:
I had the all-black-screen after trying to load the stock kernel back to my phone, the power button did nothing and I had no icons. At first I held the volume up and down and the power button for a couple of seconds and then released, nothing happened, so then I tried the volume down and the power button right after and I was able to get the download screen to come back up. I then used Odin to flash my phone with Guru's ROM.

I am not sure if it was the sequence of the button presses or if I was not patient enough when I hit the up, down and power all together, but either way I was RELIEVED because I thought for sure I had bricked it.
[Vibrant Android Development] fykick:
I had this once too...but that was coming from JG5 to US firmware. I finally got the thing back in download mode, but I was already familiar with this little scare when I encountered the second two real bricks. You may be on to something with the button combination. If this is a fix to the "real" brick...then it would be worth the try. But I currently don't have one to try it with. I may go pick up a phone at walmart just to try this because you all have me curious now.
[Vibrant Android Development] aloxotls:
I got the black screen by putting the stock kernel in the phone slot, instead of PDA, of Odin and I also had the re-partition box and the 512 pit file selected.
[Vibrant Android Development] TGA_Gunnman:
................
[Vibrant Android Development] acspin:
How is it that phones can be bricked beyond repair? I've flashed BIOS, Routers, etc...and understood the inherent risks, but never understood why they existed. Does the flashing process (or bad firmware/roms) destroy hardware components?
[Vibrant Android Development] NexVision:
Generally when the term beyond repair is used. It is meant beyond repair with the equipment and files available to us. Of course Samsung or a Samsung repair facility could easily repair the device.
[Vibrant Android Development] jroid:
so i'm guessing to nandroid back would mean a brick?
[Vibrant Android Development] scepterr:
Hey guys, I tweeted the warning because I know somebody who flashed JP1, then tried to go back to UVJE8 with ODIN, it flashed fine but after first reboot wouldn't power on at all anymore. Hopefully that was a fluke.

Oh and to fix data use the libsec-ril.so from UVJE8
[Vibrant Android Development] setzer715:
Amen Brother! Nice to see you in the Vibrant Forum!;)

Keep up the good work Guru!
[Vibrant Android Development] setzer715:
Once you've flashed an entire firmware with Odin it flashes your bootloader, recovery and radio. Nandroid does NOT back those up so you would essentially flash an incompatible ROM with bootloader/radio/recovery images. Well, not so much recovery as bootloader and radio.
[Vibrant Android Development] maydaysos:
Will we get an update.zip form of froyo or is odin the only way.
[Vibrant Android Development] fykick:
Pretty soon we might have enough bricks to build a house....:eek:
[Vibrant Android Development] fykick:
This is what I've wondered, but until someone remaps the keys for the recovery there is no way of knowing if update.zip's or Nandroid backups brick the device in the same way that Odin does when it flashes back.
[Vibrant Android Development] psychoace:
I don't think the update.zip way can write over all the system files on the phone that are necessary to install a new os.
[Vibrant Android Development] Pneumatic:
I didn't see this posted anywhere...

Here's a video review of 2.2 on the Galaxy (early ROM so things some things aren't working yet).

http://phandroid.com/2010/07/28/hdblog-it-goes-in-depth-with-android-2-2-on-the-samsung-galaxy-s/
[Vibrant Android Development] kopykatkiller:
I would agree to hold off on flashing this unless you:

A. Have not had to return a device yet and are still in your 14 day grace period, and don't mind returning for an exchange.

B. You have the extra money to buy a new phone and don't mind wasting the money.

C. You hate your phone when it works, but think it is the most beautiful pet rock you've ever seen.

There are too many differences in these phones for me to try again. Think I'll wait for CM6.
[Vibrant Android Development] SiL3nTKiLL:
yeah, flashing this is a bad idea...
[Vibrant Android Development] rhcp011235:
I agree 100%

Just wait on stock. It will be here soon.
[Vibrant Android Development] DAKIDD236:
can you post a short video showing 2.2 running on your vibrant
[Vibrant Android Development] kopykatkiller:
The problem is not flashing these with Odin or running them on the phone. The problem lies with coming back to a non-international rom.
[Vibrant Android Development] designerfx:
props to MS for working on it (ps: I thought your name meant microsoft guru and I was like wtf?), but it's not stable enough and I don't exactly hear other devs giving their blessings on it either.
[Vibrant Android Development] dcchristopher:
Vibrant running Froyo, eh? Eeeexcellent! :D

I don't mind jacking around with new ROMs (coming from a Sprint Hero, G*d knows I was flashing on a weekly basis for about 6 months) but it would be just plain reckless to do it on such a beautiful, functional phone when there's no demonstration (videos, screenshots, etc) of Guru's work. Adding insult to injury, Samsung's official 2.2 release is just around the corner. Furthermore, with root already possible on this phone (and thus WiFi Tether and similar root-needy apps), what's the rush?

Hey, to each his own and far be it from me to tell someone not to flash away, I'm just wondering what the risk/reward proposition here is.

Some people were wondering how on Earth these phones can get bricked ... well, I don't think it's a hardware problem. It's just a software issue. When you brick your phone, you essentially just locked yourself out of the house. It's not that no one can ever get back in or that the house is destroyed. It's just that there's no longer a viable entrance for YOU. I'm sure Samsung has hardware ways of getting back in but since you and I work with ROMs, destroying your bootloader, recovery OS, etc, just screwed us out of a place to install a new ROM. Does that make sense? You press the power button, the phone starts up for a microsecond, notices nothing is there to process and promptly goes night-night. *Shudders* Scary thought! *Coddles Vibrant* There, there.
[Vibrant Android Development] degeneration:
I also did an overseas firmware... my phone is doing great... I think YOU bricked the phone, not the firmware flashing...
[Vibrant Android Development] rhcp011235:
If you look in the general thread there is a I9000 running 2.2 There is no big deal. and its bugged. People just wait. All you are going to do is brick your phones. HARD brick.
[Vibrant Android Development] degeneration:
I'm in no hurry to 2.2, so I am not trying this. But giving your opinion that they will brick their phone is one thing, but since at least 1 person has done this successfully saying "all you are going to do is brick your phones" is a bit false.

Are the chances high? Perhaps, although a lot of people claiming to have bricked their phones, I did the same thing, flashed to an overseas rom the day I got it, still using the exact same phone reverted back to the pre-release... I have messed up this phone many times, but it comes back, sometimes it seems like it isn't going to, but somehow does.

I am probably just lucky, or just too stubborn to give up on fixing it myself, but some people may have been able to fix their phone. When I was rebooting I was getting an all black screen, but I kept pressing key combos until I got phone to pc and then got to download mode and was good to go again.

I don't mean to say that everyone who got a blank screen could just fiddle their way out of it... just that it's possible. A lot of things tend to have exceptions these days.
[Vibrant Android Development] kopykatkiller:
People don't read, it's not the flashing of the i9000 firmware, it's coming back to a standard vibrant rom from these firmwares that is bricking them.
[Vibrant Android Development] degeneration:
I went from overseas back to stock back to over seas (mixed with some stock stuff) back to stock to root to beta clockworkmod back to stock back to root so far...
[Vibrant Android Development] scepterr:
So have I, the issue is with JP1 and possibly JP2 only.
[Vibrant Android Development] degeneration:
OK I will go back since suddenly something just clicked... I was using JG1, no JP1... my bad.
[Vibrant Android Development] PowSniffer0110:
How and where do you get wireless tether. Please do tell
[Vibrant Android Development] MS_Guru:
Okay my friends. Sorry for the delay. Had to get my buddy out of a girly induced rut. Met some ladies bar side and sent him, the two cuties, and my wing man, off to Cache Creek.

But as for me, back to my passions. I've been using this as my work phone all day, and the only prob was a mix up in files that reverted me to backwards volume keys all day. (Which really sucks when its something you fixed already.

A little barside display time, proved this OS is a show stopper. Quote: "But I just gut a new Slide"... Ummm... yeah... But this is the Vibrant on Froyo. :cool:

Hehe...

@beckhamsoccerman.... This build comes with a fancy, dressed up app called Mobile AP. Basically its built in, and spit shined. Incorporated into the phones UI settings no doubt. Otherwise, "Android-Wifi-Tether" has always, and will always, be tops on most anyones list.
[Vibrant Android Development] lp894:
what about t-mobile 3g...does it work in this? and, would it be possible to take the build that you have, and MAKE an update.zip?
[Vibrant Android Development] BigWorldJust:
A new update to this is available for the Galaxy S now..
[Vibrant Android Development] Greenarcher707:
@MS_Guru - Hey dude, are you from the Bay area?
[Vibrant Android Development] rsfaze:
nice stuff here MS_Guru

glad to see others are working to make this happen besides just team CM.

Together we can accomplish ANYTHING.
[Vibrant Android Development] jroid:
I want froyo on my vibrant sooo bad.. I'm getting tempted to flash this. Is the new xxJP3 firmware safe to revert from??
[Vibrant Android Development] acjames:
I dont really care what YOU think. When i did the firmware update the phone was fine. Everything was ok except that I couldnt join T-Mobile's network and it could only see AT&T. Which was the only reason why I flashed back to stock. It even completed that completely but did not come back on after the reboot.
[Vibrant Android Development] fykick:
Its not just a bricking problem with jp1, it seems to be any after jg5. I can confirm that jm1 and jm2 also brick phones.

Has anyone tried flashing this actually? Because there are a few who are all for this yet...have you actually flashed it? Cuz you'd realize that you get stuck in recovery on your vibrant anyways unless there is a version someone has or knows how to remap the keys. Which is my next question...

Does someone have the remapped key version. It seems a few of you are acting as if there are vibrant owners who have gotten out of recovery.

Im also curios how the OP got out of recovery if he has yet to remap the keys or post the link. What exactly is there to left to do if you have already carried out the whole process yourself? Just curious what we're waiting on.
[Vibrant Android Development] MS_Guru:
Well thanks to a stupid friend, I think I've figured out whats causing Bricks. Which means firstly, that I'll be able to prevent it. And on another note, I've got a brick to play with. :D Gotta love dumb friends.

My Vibrants running like a champ. Perfect Froyo with every issue fixed. But I won't release anything dangerous. Once I know theres no brick risk, I'll release it.

It appears that the problem comes up when attempting to flash away from certain images. I'll have details in a bit, as well as what to look for when flashing. Meaning, what NOT to flash. Stupid @ss friends can be so helpful sometimes.
[Vibrant Android Development] jroid:
jajaja.. this is great news :) good work man and thanks for all your contributions! looking forward to froyo on my vibrant :D
[Vibrant Android Development] CappyQ:
Nice, that's good news. And I hope you can unbrick your friend's phone!
[Vibrant Android Development] nick_karstedt:
That's Fckin hot. Can you post linpack results? I wanna see this baby blow the nexus one out of the water.
[Vibrant Android Development] Cuda1337:
QFT, can we get some pictures of it running Froyo please?
[Vibrant Android Development] Pneumatic:
http://phandroid.com/2010/07/28/hdblog-it-goes-in-depth-with-android-2-2-on-the-samsung-galaxy-s/
[Vibrant Android Development] kelmerp:
We know there's test builds running on the Galaxy, but what we haven't seen is froyo running error-free on a vibrant...all we have is ms_guru teasing us...
[Vibrant Android Development] junkdruggler:
Its not a tease.. He gave all the info on doing it yourself...
[Vibrant Android Development] kelmerp:
Ok, but not a single person on this forum has tried it and posted something like "The upgrade worked great for me, no problems!" Also, ms_guru's latest post says something about making it idiotproof, which is what most people want to hear (including myself).

Not to mention that other devs are still saying not to do this...
[Vibrant Android Development] scepterr:
MS_Guru , have you been able to ODIN back to UVJE8/JFD after being on JP1/2/3 ?

For anybody with data issues, make sure to use the corresponding libsec-ril.so to your baseband.
[Vibrant Android Development] jroid:
i'd just push that to /system/lib correct?