Quick tip: flashing the beta version of Bada 2.0 to your Samsung Wave (II)

Now that Samsung seems to be still dedicated to the Bada platform and has even been releasing a continuously worked-on and enhanced firmware, I decided to fully support it and also purchase two current Bada phones (the high-end S8530 and the middle-of-the-road S723) to post on programming both the new and the old Bada versions and to (help) port some genuine iOS projects to Bada.

Of course, the very first thing I wanted to do was flashing the S8530 to the latest (unofficial) beta of 2.0 so that I can test the new features of the new API on a real hardware and not just a simulator.

At first, it was really hard to find relevant information on how beta firmware should be flashed. At the XDA-Devs forum, which, otherwise, does have a lot of interesting info on, for example, flashing Android to the S8500 Wave (but still(?) not the S8530 Wave II), I couldn't find anything of real interest for purely Bada 2.0 flashing for newbies. (The poor English of many of the forum users had made deciphering the info even harder.)

Fortunately, some other sites have turned out to have much more useful guides. The best flashing guide is, in my opinion, HERE, linked from HERE. Using it, I had no problems flashing the current (XPKH2) 2.0 beta released yesterday. Note that you don't need to separately search for each individual file – just drag-and-drop them from inside Explorer / Total Commander, which makes the entire process significantly faster. They're all inside a subdirectory under the one that has MultiLoader_V5.65.exe, the executable file you'll need for flashing. (Earlier RAR files had all the files, along with the USB drivers, in the same directory level, making dragging a bit more complicated if you wanted to deselect these two files before the drag-and-drop operation.)

Note that the tutorial doesn't show how the latest USB drivers (delivered inside a ZIP file in the RAR archive) need to be installed. In my practice, you didn't need to “restore the drivers” as is stated for example HERE. (Nevertheless, if your phone isn't detected and nothing else helps, try activating “'driver recovery” from left-top Kies menu.) Actually, I didn't even need to install Kies at all: just installing the USB drivers was sufficient (on my XP SP3). Note that the latest S8530XPKH2.rar doesn't have the USB drivers. The previous one (S8530XPKH1.rar [HotFile link]) did have. You can safely use that version for S8530XPKH2 too – just unzip the one EXE file from the ZIP and execute it. (Should you need the USB drivers separately, I've made them available HERE.)

Also note that the GUI is completely messed up under Windows XP SP3: the “Full download” and other checkboxes are completely hidden. (Tested on both my under Parallels 6.0 running XP [you, according to the video above, shouldn't flash from a virtual machine, though] in 1680*1050 and on a HP TC1100 with XGA screen resolution. I haven't used non-standard font sizes on either of these machines.) I haven't encountered problems like these under Windows 7 on the same HP TC1100. However, you can check in the checkboxes even “blindly”: after selecting the LSI radio button, press Tab three times on your keyboard, followed by a Space, to check in “Full Download” (and Tab / Space again if you want to enable “Master ROM” - with the current firmware, I didn't need to). I needed to do the (“blind”) flashing under XP as, under Win7, it simply didn't work on my TC1100, not even after 10-12 retries: it always displayed an error after 4-5 minutes, typically during the FFS or, in some cases, later, the CSC flash. I haven't encountered any problem under XP – except for the completely messed-up GUI, of course.

Note that the above-linked XPKH2 is meant for European users and worked for me (I'm also European) out of the box. As the current distribution worked out of the box, I didn't really bother with the intricacies of this problems. If you, on the other hand, use a different (non-European) language, you may have to hack the CSC file before flashing. See for example THIS for more info. (Yes, I know the thread is a bit hard to digest...)

Finally, you may want to disable debugging mode to make the phone faster / less prone to “blue screens” via entering *#33284*# and changing it from Middle to Low. Doing this (to access Security) is also explained in the recommended video – it's just like entering a service code in the dialpad.

Dedicated articles HERE and HERE (with links to distros from the first post.)

Syndicate content