yashsingh1/xdaforums huggingface dataset:
[Vibrant General] rfosta:
My machine is a Linux machine, but I do have access to a windows machine. I thought that flashing cm7 would install the GB bootloaders? Is the video a pretty accurate one or should I not go off that? Cause I don't have root yet either.
[Vibrant General] yosup:
CM7 (or any CWR flashable .zip file) does not have BL files. Only Odin / Heimdall flashable files may or may not contain BL files.

Though GB BL's are most likely optional, I did run into issues using Froyo BL's and an old version of ICZen - ie. where I couldn't get into recovery. mr_psycho has since corrected that issue in his kernels. The "tale of the tape" is probably buried in this thread somewhere.

Plus, since you're building your ICS knowledge base, GB BL's are important to know. Even if you don't flash them, you'll want to be aware.

GB BL also gives you the convenient 2-button Recovery / Download mode access. I personally use adyscorpius' Rainbow In My Eye custom GB BL - ie. every time the phone boots, it's obvious I have GB BL's when I see that splash screen.

EDIT:

Hey, man. Woodrube deserves the "thanks" for his informitive input, so make sure to hit those "Thanks" buttons on his posts. ( Tryin' to hook you up, Woodman. Hehe ). Tip: If you hit your daily 8 Thanks limit, you can always jump on Tapatalk (if you bought that app) and bypass the hard limit.
[Vibrant General] rfosta:
Do I need to root before I load the GB bootloaders and do I load them while im on eclair?
[Vibrant General] kaiser_bun:
I've only been going back and forth from ICZen/Slim and Froyo builds since ICZen was in the 1.5 iterations and only recently Slim (3.6 and 3.7), but the battery is definitely decent on both ICS builds. You can easily get a day (18 hours of off charger time) with moderate useage, but streaming and constant browsing can really chomp away at it. Nothing unexpected though with the screen on the whole time, but don't expect Froyo type battery life.

The GPS depends on what you set your expectations at. For me it's still nothing I'm ok with as far as a daily driver. Even with the hardware fix and yagf2 and euphoria scripts I was only able to get a decent lock in terms of speed right after a boot/reboot (17-25s lock time). If I went back to it an hour later the lock would sometimes take about 50 seconds to 3 minutes, and like I said for me that wasn't something I feel like messing with all the time. The locks were super accurate though; 17ft according to GPS Status.

---------- Post added at 11:18 PM ---------- Previous post was at 11:15 PM ----------

I never went from Eclair, I always Odin back to Froyo, but I don't think it would matter for the bootloaders which you were on. Hopefully someone can verify this.

And you don't need root if you're flashing the bootloaders via Odin.
[Vibrant General] yosup:
Refer to adyscorpius' FAQ in the 2nd post (but thoroughly read the 1st & 2nd posts):

http://xdaforums.com/showthread.php?t=1117990

As kaiser_bun (great name, btw) mentioned, BL's are flashed via Odin or Heimdall so root is not an issue.

( man, Woody ... your thread came back to life today. Lol. Luvit! )
[Vibrant General] rfosta:
What's the percentage that the flash will be successful? Cause I want to go through with it just to be safe and as well get some experience.
[Vibrant General] yosup:
Not aware of any % ... but it's a quick flash. Should either work or else get an error message in Odin I suppose. Personally, I've never gotten an error. Took 7 seconds on my old XP machine to flash via Odin. I've never looked back since.

NOTE:

Use Woodrube's suggestion (if you read through this thread) to UN-CHECKMARK Auto-Reboot (in Odin). That way you can manually reboot once you see Odin's "PASS" message appear.

Reading the GB BL discussion in this thread and adyscorpius' first two posts (in his GB BL thread) will alleviate your anxiety. Believe me ... I've been there and can relate.
[Vibrant General] rfosta:
So I'll read on all this week so I really have an understanding of what's going on. Ill report back if I have any other questions. If not I'll. Flash GB bootloaders and let you know how it goes. If there are any. Other threads you think I should read then links world be appreciated. Also you said the update 1 doesn't matter at all?
[Vibrant General] yosup:
This thread covers a very large range of topics. Really is a great read. Woodrube also links to many pertinent threads as well. Check out his sig for his other guides (ie. Battery guides, etc) as well.

Aside from this thread, I'd read adyscorpius' BL thread (first two posts) and the link I posted above re. MTD (if you wanted to learn more about file systems & partitions). If you're going the ICZen route, read Br1cK'd's first few posts and also find mr_psycho's subZero kernel thread (also in RW's Vibrant / Dev section).

GB BL

You can always flash them later (after you're read up). I'd just recommend backing up your sdcard contents before flashing ICS - ie. just in case you run into issues using Froyo BL's.

At this stage of ICS development, running Froyo BL's is probably not an issue. The main issue "back then" (ie. esp. when Passion just rolled out) were people getting "Rainbows" and not being able to read the recovery mode menu, etc. That's most likely old news by now.

I can only speak from my own experience that I ran into issues with Froyo BL's a long while back ... but, in the same vein, the kernel dev (mr_psycho) addressed those issues in his kernels ever since.

As for flashing rom's (without GB BL's) ... you can always resort to restocking via Odin to JFD and going the "Clean Install" route if you run into issues.

2.1 UPDATE 1

I never stayed on Eclair long enough to get this update, so I'm not really sure what was included. Fact remains you're on 2.1 (Eclair), so you should be fine upgrading to CM7 / Gingerbread and then to ICS using Woodrube's instructions.
[Vibrant General] rfosta:
Thanks so much and I've gone back and thanked all of you guys. I hope I can be on ICS by the middle of next week.

EDIT: So you can go to ICS from Eclair bootloaders?
[Vibrant General] yosup:
Cool. Check back in and let us know how everything went. Cheers. :D
[Vibrant General] Woody:
Seriously. Like a thunder.

Really if you just follow Ady's instructions it takes 5-10 secs to flash bootloaders and you are done with it. I understand the fear believe me but really don't sweat it too much. I have all the Froyo and GB bl's in Ady's thread so PM me if you want them.
[Vibrant General] yosup:
AFAIK, there's no difference between Eclair & Froyo bootloaders. Yes, you can stay on those bootloaders if you wish (but GB BL's are always recommended). If you run into rainbows (probably rare these days), you can either then flash the GB BL's (via Odin) or Odin back to stock JFD and flash the GB BL's then, etc.

+1 ... I have some saved screencaptures of when I flashed GB BL's.

Just follow adyscorpius' instructions:

And this is what you'll be seeing ... took me 7 seconds.
[Vibrant General] kaiser_bun:
As yosup said, you can, but most flashing guides I've seen have recommended GB.

If you did flash the GB bootloaders they'd still load a Froyo ROM anyway as far as I know, so it wouldn't be that big of a deal to do.

Good luck with the ICS. It's amazing what the devs have been able to put together for the Vibrant considering its age, and I'm hoping that some kinks are ironed out as the projects evolve. Just have to keep flashing every now and then :D
[Vibrant General] yosup:
Yup ... GB BL's are backwards compatible, so it makes it even more compelling. :D
[Vibrant General] rfosta:
Odin to JFD

Say I do go to a ICS rim and I want to return to eclair or froyo how would I do that? I here people say Odin to JFD, but I have no clue what that means.
[Vibrant General] Woody:
Means going back to stock 2.1 Eclair. Nothing more, nothing less. It is bc you'll have to repartition the system from MTD back to the RFS. Then you can move on to a Eclair (not sure why) or Froyo build. See a few posts back where Yosup and I explain RFS/MTD.

Sidenote: You can always move laterally, i.e. Froyo to Froyo or ICS to ICS but cannot move forward or back from Froyo to GB/ICS or GB/ICS to Froyo because of the above.
[Vibrant General] rfosta:
The part I don't get is say im on ICS and want to return to eclair or froyo. What files would I need. I here a lot about a PIT file, but is that the only thing I need? Do I need more like the actual stock ROM?

I get the whole idea of changing the file system back and using Odin. What I don't get is what exact files are required to do all of this
[Vibrant General] Woody:
If you download the AIO Toolbox like I mentioned before, it has the neccessary drivers, Odin 1.8 (I think that is the version) and the Pit/Tar files you need to go back to stock JFD.

All in one nice neat package. There are other features it has too, but I only use the Odin part of it, as the rest you can do in recovery, but we'l get to that when we get to it.

Edit:: I suggest you get on YouTube and search Odin for Vibrant and see in real life how it works and also to give you some more confidence. It really isn't that hard, but I understand your fear and the PITA finding the right files.
[Vibrant General] kaiser_bun:
s15274n has a good guide here on getting back to stock using Odin: http://xdaforums.com/showthread.php?p=13132341#post13132341

All you need is the PIT (unzip it and get the actual .pit file) and the tar (a tar is a compressed file; like a zip). In Odin the PIT goes in the PIT spot, and the tar goes in the PDA spot. And I always put those two files in the same directory I have the Odin excutable in, but I don't know (and doubt) if you have to.

If you're running Windows 7 64-bit, you'll want to find and install the Windows drivers for the Vibrant before you start messing with Odin (hint: there's a link about the drivers in that Odin guide I mentioned). Odin can lock up in a few places during the load if things aren't quite right (some people say even the USB port can be a problem), but having the drivers and running the Odin executable as an Administrator (not necessary really, but what the hell) has always treated me right.

PS I see a lot of people ask about how to get to download mode, and for me it's always just holding the volume up button while the phone is powered down and then plugging in the USB cable that's connected to the computer. However, you're mileage may vary.
[Vibrant General] yosup:
I'll let adyscorpius do the talking ...
[Vibrant General] rfosta:
So I flashed the GB bootloaders and I was just wondering if I should go through the same wiping as I did before I installed CM7 or I can just install ics over CM7 without wiping?
[Vibrant General] Woody:
Follow the directions as is. I would say that at the very least that you can flash ICS after CM7 with only wiping /cache and /dalvik. There is some speculation that wiping /data

OR

formatting /data are causing the EU bug (don't forget that wiping and formatting are not the same).

When I flash an ICS ROM, I Odin to 2.1 every time. It goes a little something like this.

2.1, re-flash GB bl (since Odin-ing put Froyo bl's on), install update.zip version of CWR, Flash CM7 boot up and then wipe and flash ICS with all the wipes I have in the places in the OP.

Just as a fyi, the only time I don't go all the way back to 2.1 is with an incremental build. I know it is a long way to go every time I flash an ICS ROM, but at this point it is routine to me now.
[Vibrant General] rfosta:
So I wipe data, cache, dalvik, and system then went and installed ICS passion. I also went back to stock before I started the process too. I also installed GB bootloaders too.
[Vibrant General] Woody:
So it worked out? If so, glad I could help.
[Vibrant General] rfosta:
Yes. Everything went well and I thank you for all your help. Now just trying to find the right from and kernel.

Also when going back to stock and flash a ICS rom does it matter if I flash cm7 or cm9
[Vibrant General] Woody:
I generally flash CM7 bc it is already on my SD card. CM9 is an ICS variant so i always feel that the intermediate step of CM7 is a "last chance " type thing and I know that all is well up to point.

Much like when you have GB bl's and you see the sequence of bootloader, kernel ans ROM splashes in that order. If one is missing then something is about to go haywire. Flashing CM7 before any ICS first repartitions it correctly but also is a way for you to turn back if you want.
[Vibrant General] rfosta:
One last thing. ICS passion came with cwm, but for some reason rom manager doesn't know I have it. So would I break something if I flash it through the app.
[Vibrant General] Woody:
Not sure about that. I don't and have never used Rom Manager and not sure that anyone really uses it. Most of the custom kernels (not ROMs) have some form of CWR that is readily accessible through the Extended Power Menu.
[Vibrant General] rfosta:
Thanks. Btw which kernel and rom are you currently running?
[Vibrant General] Woody:
ICZen current version and Subzero #80 or #128. Going back and forth but am about to test something for someone else here pretty soon once my schedule slows down this week.

Hit that Thanks button a couple of times for kicks. And if you need anything else, just ask. I have some obligations this week, so I will only be able to post at night, but there are plenty of competent users out there that can help. Yosup, Lapdog, Adamanda, Xenoism,...all can help and all have run ICS from the ROM's infancy.
[Vibrant General] rfosta:
Also when you switch ROMS you don't wipe data/factory reset?

---------- Post added at 05:50 AM ---------- Previous post was at 05:47 AM ----------

Also is it formatting the data directory that cause the EU bug or is it the wipe data/factory reset that causes it? Also what happens if I dont do it? Cause the Threads say to do it.
[Vibrant General] yosup:
I, personally, always do a full wipe (inc. wipe data / factory reset) between roms. As long as you have your data backed up in Titanium Backup, you should be fine. As Woodrube mentioned, it's not always necessary - ie. if only an incremental update. Then again, many people avoid doing it as well. If you don't and you experience lots of FC issues, then you'll probably have to go back and do a full wipe.

The EU & wiping /data topic is just a theory (although one that was originally suggested by a very well-respected Vibrant kernel dev, mr_psycho).

EU in general has happened to people who always wipe /data (ie. me) as well as to those who rarely wipe /data (ie. Alex9090). The only solid assumption about EU is that it can happen on any ICS rom. The rest of the EU conversation is still open for discussion.

Wipe Data / Factory Reset wipes the /data, /cache, and /datadata directories (amongst others).
[Vibrant General] rfosta:
Thanks. So it can really happen to anyone wiping data or not? Also what kernel and rom are you running?
[Vibrant General] yosup:
Unfortunately, yes. :mad: It doesn't seem to discriminate, however Woodrube & The Gang (over in the EU threads) have been trying to identify some of the triggers which "may" include connecting to PC via MTP and "possibly" something happening when wiping /data on ICS roms. I wish I could say with more conviction, but it's still a crap shoot.

Note, however the vast majority of ICS users have not experienced it. Yet, enough have to make it worthy of consideration. Read thru the EU threads, see what things you may need to do (to prepare for it if, God forbid, it ever happens to you), and then proceed in a heightened state of awareness (and proactively back up your sdcard contents to another device or cloud account).

It's "easier" for me to say this stuff since I've already experienced EU and currently don't have access to my internal sdcard contents. Plus managing EU happening on an external sdcard should be (in theory) much less traumatic. However, for those who've yet to go thru it and wish to keep their internal sdcards intact ... I can understand the level of anxiety whether to proceed.

Imo, the benefits of ICS outweigh the risks - ie. with the caveat to religiously back up your data. I can't go without the ICS specific launchers (ie. Apex, Nova) and ICS specific apps (like Notification Toggle). Plus, the sheer speed, hardware acceleration, and continued development of ICS roms makes it tough for me to downgrade at this point. Then again ... I've already been bitten, so the "sting" has already been taken out of the EU bite. :D

ICZen #1.8.4 (4.0.4, AOKP #40, Linaro -O3) + subZero #144-VC.

I highly recommend ICZen rom (Team Deficient Development) and subZero kernel (mr_psycho) - ie. top-notch support (very responsive to troubleshooting issues), tight enthusiast community (great group of folks over in RootzWiki), and always cutting-edge (frequent updates).

There are also plenty of other ICS roms to try: AOKP official builds, CM9, MIUI, SlimICS, etc.
[Vibrant General] Maelstrom08:
Hey everyone, this is my first post here so I'm sorry if i break any rules in asking questions on this thread. If i do, please point me to the right forum or thread.

I have a rooted samsung vibrant with android 2.2/ baseband version UVKA6 (I rooted the phone a year ago and never flashed any roms). My questions are the following:

- What are the implications of the encryption error caused by ICS roms? I understand you lose access to the data in the internal SD, but does it just restrict access or erase the files (difference being the space available, i guess). Also, if i get the encryption error, can i go back to stock froyo? and what happens to the internal SD, would i still not have access to it?

Please don't feel like I just want easy/quick info, I've read many threads on these fora and haven't found answers to my questions. I just want to make sure i got it right before i give it a go.

Thanks in advance.
[Vibrant General] yosup:
These are the main two EU discussion threads relating to our Vibrants & EU.

[Guide] SD Partition for Encryption Unsuccessful (ICS Bug) · Merio90 · Samsung Vibrant » Q&A

http://xdaforums.com/showthread.php?t=1580902

[Guide] Encryption Unsuccessful - Reset Android [ICS Issue] · cgugino · Samsung Captivate » Development

http://xdaforums.com/showthread.php?t=1447303

You answered your own question - ie. losing access to the internal sdcard is the major implication. Until the internal sdcard access is restored, your external sdcard becomes your main / sole sdcard for rom/system and personal data partitions.

You "can" flash Eugene's Froyo without an external sdcard, but useability is limited (w/out ext sd). If you want to restore full functionality, you'll need to use an external sdcard - ie. repartitioned & using the vold.fstab emmc/sdcard swap described in the two threads referenced above.

The vast majority of EU victims still do NOT have access. It's rare, but a few people had their internal sdcard access miraculously (& mysteriously) restored. No valid methodology has surfaced to scientifically recreate (& validate) their success stories, so (for now) it's sheer luck if it ever happens. Since those few have had their internal data restored, you can make the assumption that the internal sd data itself does not get erased.

If you're asking for absolute answers, you'll never find them until EU gets solved. It's very much a WIP, so you need to keep that in mind when this topic is discussed.

Once you get EU (like I have), you can flash whatever you want and use your phone just as before. The sole exception is you won't / can't use your internal sdcard (until someone figures out how to restore access).

Whenever you flash a new ICS rom, you just need to do the vold.fstab emmc/sdcard swap each time. The methodology may be slightly different for non-ICS roms, but the principle remains the same. That's essentially the main difference in a nutshell.
[Vibrant General] Maelstrom08:
Alright, I will make sure i give those discussion threads a read. Thanks a lot for taking the time to answer my questions in such a detailed manner. I think I might wait until the EU bug is solved to flash an ICS rom, this vibrant is the only phone I own atm. Thanks.
[Vibrant General] explorer-10:
if coming from stock 2.1/2.2 and flashing a completely new custom rom/kernel combo based on ICS, what would be recommended the best to flash for a FFC-based rom[best 2] and a non FFC-based rom[best 2]?
[Vibrant General] Woody:
At present there is no solution for the EU bug. Nor any solid leads. There are plenty of valid theories but nonetheless they are still only theories at this point. We have been actively working on this since the beginning if the year.

ICS is great. And I run it when I'm not testing for someone else, but it will depend on your comfort factor and are you willing to gamble on the bug or not. There are plenty of very well tweaked 2.2 ROMs that you can flash with everything working as well.

Good luck and read and ask questions.

You can flash them the same since the ffc is an add-on mod.

If you are asking which ROM has ffc support, you'll have to read the OPs and find that out.
[Vibrant General] explorer-10:
since there are a lot of professional modders here, i also wanted to know what are the best 2 roms each from both ffc-supported roms/kernels and non ffc-supported roms/kernels

so for example, something like:

ffc-supported roms:

1) romX/kernelX

2) romY/kernelY

non ffc-supported roms

1) romX/kernelX

2) romY/kernelY
[Sony Ericsson XPERIA X10 Mini] meghanath reddy:
can i know the clear information about multy booting in the form any video are with the help of anyu screen shots:):(:):(:):(:):)
[Desire Q&A, Help & Troubleshooting] Salfalot:
Hey,

I've got a situation. I'd like to try and run a HTC Sense 2.1 version, preferably the one from Coolexe into a different Hboot than the common type. Namely into a Hboot with 210/205Mb for system and 5Mb cache so I can have the rest for Data, this is because I prefer to have everything on the nand of the phone instead of the sd-ext etc! I've posted the coming question in his topic aswell..

Coolexe uses at his own ROM a trick which enables him to use the cache partition, he then symlinks those files (which are in the cache partition) to the /system folder. So when I figured that out, I went and put some files into the cache partition so my system folder is lower than 180MB, this way I could use the Sense Hboot. Everything went fine and the ROM booted, however I couldn't get on my WiFi. I did see my WiFi, but I could not connect..

To check if it wasn't the ROM I put everything back into the /system folder and tried the ROM with the stock Hboot. This time everything just worked. So I think that the symlinking simply just doesn't work..

When I looked at titanium backup, with the symlinking ROM, my system folder sayd that my /system had no room left anymore. So I think because of that it won't get an IP address.

So I read somewhere that Thalamus made a Hboot creater, so I thought my problem is solved now! I'll just create my own Hboot.. However when I tried to make a Hboot similar to the one from Oxygen or CM7r2, just to check if everything worked the way it had to, the md5sum didn't match.. So now I'm wondering if someone has created a good functioning Hboot with that tool, I prefer not to brick my phone :P

So I was wondering if someone had the same problem? And if someone doesn't have this problem could he/she create a custom Hboot of 210mb for me? Or something what comes near that figure..

If someone has an idea about why I don't get an IP address I'm glad aswell!

Thanks in advance
[Desire Q&A, Help & Troubleshooting] kotag82:
i had about dozen done... everything is spot on... HERE IS YOURS

md5:

114213A25C3C2E6148B838F5628E5027

Tried and working

About IP address:

Is it still obtaining IP? try to set IP manually, on my router(wifi N) i can't connect without static IP... previous router worked perfectly but unfortunately it was not WIFI N
[Desire Q&A, Help & Troubleshooting] MatDrOiD:
_thalamus developed an app to create your own hboots:

http://thalamus-hacking.blogspot.com/2011/07/custom-hbootsupdate.html