Buzzdev.org

Streamed by Mark Verver in Barcelona, España. More at qik.com

farmville on Nexus One – Flash 10.1 Demo on Android

I haven’t been on here a while and I apologize for that. This summer has been a busy one for me – first in summer school for AP Macroeconomics for 6 weeks and then I went back to India for 4 weeks. I’m back now and of course, school starts in 2 days. But I have been doing some WinMo stuff over the past 2 months. However, I haven’t been working on my OnDemand customization. Instead, something bigger has caught my attention.

Ever since Da_G over at XDA-Developers created a thread about the Image Update system, I’ve been following and developing some of my own software. For those who don’t know, the Image Update system allows for you to update the IMGFS and XIP partition of your phone via cab files instead of flashing the device and losing all personal data/installed applications. To make this mechanism work, which has been present in Windows Mobile since WM5, all of the DSMs (Device Side Manifests) need to be in the proper MS format. Unfortunately, all of the current kitchen tools that we use for ROMs malform these DSMs or completely remove them from the ROMs. Because of that, I’ve been working on applications that will make Image Update work properly. In June, I was able to create two applications – one that regenerated DSMS from scratch in the exact same way MS’s tools are supposed to work. The other would create the Image Update packages and sign them - they produce the same results as the ones generated my MS’s tools as well. I’ve been working to consolidate them into one app that will also act as a ROM kitchen that adheres to MS’s documentation (for the most part ).

For those who are interested, you can check out Da_G’s thread in the Dev & Hacking section of XDA (I’m too lazy to link to it right now )

The most important role of Bootloader is thru FLASHING both using himaupgradeut.exe(nbf), “l” and “lnb” command in mtty.exe or even with SD Flashing (backup first your ROM in your SD/MMC with mtty.exe).

We use also Bootloader for other stuff like reading/writing the content of ROM and RAM. We use it for Backuping the ROM and some other stuff thats beyond the OS enviroment.

Technically there is no reason for changing your bootloader. Almost all bootloader performs as it with other bootloader.

But like the OS update, some bootloader is is not compatible with newer or even older ROM upgrade utility and need to be change if needed.

“;”

Currently there are Six ways to Change your BOOTLOADER in your GOOD old HIMALAYA but i’ve only tried four methods .. and to be exact none of them is safe ..

First Method is Changing thru nbf(HimaUpgradeUT.exe) - ALL nk.nbf contains a BOOTLOADER but some nbf has an emptied/Blank portion for bootloader and can cause for a brick device. But technically by default our devices is set to skip the bootloader during FLASHING. I really dont know how exactly but some upgrade can really change your bootloader (but only in HIMALAYA and BlueAngel Type I ROM, in Magician, BlueAngel Type 2 ROM and Alpine .. you can modify the nk.nbf to also write the bootloader but this method is the most dangerous of ALL method)..

Second Method is thru BootBlaster - ByteBlaster is design for changing the bootloader of Ipaq. I havent try it so i cannot make sure if this can really change the bootloader of HIMALAYA

Third Method is thru JTAG - technically it should be the safest method cause changing the bootloader is thru communicating to the chip itself so if you made it incorrectly then you can repair it again (unlike in other way that if you made mistakes once you already brick the device) but still it is the most dangerous way since you can totally damage the device. DO this only for the last resort

Fourth Method is thru mtty.exe(or Romupdate.exe) - in mtty.exe there are two commands you can use to change your bootloader

• thru “l” command (not i but small Letter L) – but you need a B000FF .bin files to do this, the command is just typing this in mtty.exe window:

l c:bootloader.bin

• thru “lnb” command – in this command you need now a RAW binary files of Bootloader the extension is sometimes use as .raw, .bin(raw), .nb0 or .nb, bootextract.exe can get a raw binary files of Bootloader in your device. The command is :

lnb c:bootloader.nb 80000000 00040000 0

For other Bootloader Commands and its function. Click Here

Fifth Method is thru SD ROM Flashing - yes SD Flashing cannot only backup your OS ROM, Extended_ROM and Radio ROM, but it can Also backup your BOOTLOADER and as a matter of fact it can backup everything in your device and YES can overwrite it aswell. In Order to backup your bootloader in HIMALAYA you have to make this command in mtty.exe

d2s 80000000 00040000 -> Backup bootloader only

or

d2s 80000000 02000000 -> Backup Bootloader + OS Rom (HIGHLY RECOMMENDED)

for a Detailed Explanation on how this works Click here

Sixth Method is thru itsme’s PNEWBOOTLOADER.exe - this method is definitely the easiest and fastest method. Not to consider the safest method of all (but still DANGEROUS). Currently the pnewbootloader.exe is compatible to the following Device with the FOLLOWING OS ROM version installed.

WALLABY with any of the following OS installed
3.04.00 ENG

3.16.52 ENG

3.17.03 ENG

3.18.04 ENG

3.19.01 GER

4.00.10 ENG

4.00.01 ENG

4.00.05 ENG

4.00.16 ENG

4.01.16 ENG

HIMALAYA with any of the following OS installed
1.60.00WWE

1.52.00WWE

1.66.00WWE

1.66.01GER

1.72.00WWE

MAGICIAN with any of the following OS installed
0.68.00 WWE

1.00.00 WWE

1.03.00 WWE

1.12.00 WWE