[MDA II, XDA II, 2060 ROM Development] toenailed:
hi zxvf ..:)

actually you and obelix .. inspire me to study and explore the bootloader since it is also been a theory in WM2005 and i want to bypass the "NOT ALLOW OPERATION" ..

m so sorry didnt have a chance to answer your Question in the other thread .. since i havent been online this past few days because of accidentally killing my device when im doing this so called Exploration of BOOTLOADER..

i also found lots of other commands and was about to copy it when my device give this three SCARY BEEP .. then it was my device is dead .. :cry: currently his under surgical operation and confined in Service Center Hospital for almost a weeek now hehehehe..

anyway so far i know only five methods but only test four of them.. in changing bootloader in HIMALAYA .. and yes ALL of them is VERY DANGEROUS

:arrow: First Method is thru nbf or HimaupgradeUT.exe, actually i still dont understand why sometimes the bootloader is change and sometimes is not .. but got a case when im under 1.03 bootloader my bootloader is change to 1.01 after flashing the LaunchROM upgrade.. but after changing it back to bootloader 1.03 and try it again it didnt change after that... i also try it when im in bootloader 1.06 but it didnt work .. i also try some himupgradeut.exe with different bootloader and found that sometimes it change and sometimes it didnt im sorry i didnt list all of them.. but still the idea is since almost all nk.nbf contains bootloader there is still a possibility (but some nk.nbf the bootloader is empty/blank)

:arrow: Second Method is thru "lnb" command in mtty.exe or romupgrade.exe, lnb is flashing directly to your rom using a raw binary files(.nb), the command is

lnb c:\bootloader.nb 80000000 00040000 0

but you have to make sure that the .nb files you have is actually bootloader .. or you will just fry your device.. but before exiting mtty.exe i always take a glimpse of the bootloader if it flash right using this command

mb 80000000 00040000

but not all bootloader contain the "lnb" and "mb" command even you already have the complete password(pass, pass1, securitypass) pls dont ask about the password i didnt get it all .. :)

:arrow: Third Method is thru BootBlaster this is the method that i havent try .. and im not sure if this will really work in Himalaya .. :)

NOW heres the two method that im sure will work in HIMALAYA bootloader and what im using before i kill my device..:)

:arrow: Fourt Method is thru SD Flashing, yup .. SD Flashing can change your BOOTLOADER .. and i think it is the most flexible since you dont need any other device to do this .. you just need to ask someone who has different bootloader make a backup of his bootloader using this command

d2s 80000000 00040000 <- Bootloader only

or

d2s 80000000 02000000 <- Bootloader + OS ROM (Recommended)

(i think you are very knowledgeable to know how to bypass the NOT ALLOW UPDATE error so i will not post it how .. :wink: )

or extract the bootloader in a nbf and use itsme's psdwrite.exe

NOTE: yeah SD Flashing is also dangerous if you didnt do it right .. thats why flashing your Device with a SD that backup their ROM using the command below is very dangerous

d2s 60000000 00300000 <- even it has GSM Bootloader this is still safe

d2s 70000000 01080000 sd a <- DOC Header +Serial Number + Splash Screen + Extended ROM

d2s 80000000 02000000 sd a <- Bootloader and OS ROM

but i didnt say that you dont do this .. you still need to backup your ROM using the Command above and keep it for future reference just do not share or use someones SD Backup that uses that command .. instead .. if your want to share a SD backup use this command

d2s <- OS rom only(other option d2s 80040000 01fc0000)

d2s 60000000 00300000 sd a <-- Still Safe

d2s 70010000 01070000 sd a <-- Splash Screen and Extended_ROM only just like the content of ms_.nbf

:arrow: Fifth Method is thru itsme's PNEWBOOLOADER.exe - tnx somuch itsme for creating this wonderful tool .. i think in all method above this is the safest method(but still dangerous) since you still have a working OS and can repair your bootloader before totally damaging your device

currently pnewbootloader is compatible to the following device and uses the OS ROM

for wallaby you need to be in any following OS version

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

for himalaya you need also in this any following os version

1.60.00WWE

1.52.00WWE

1.66.00WWE

1.66.01GER

1.72.00WWE

for magician you need also in this any following OS version

0.68.00 WWE

1.00.00 WWE

but as always .. you have to make sure you get the correct bootloader files before doing this or you will kill your device..

then after upgrading .. i use itsme's pmemdump or my bootextract.exe to extract the flashed BOOTLOADER and compare it if flashing is all okih ..

here ye go .. i hope it will help .. :D

anyway tnx for ITSME and buzz_lightyear for all the info and help .. also to shafa and rhmartin for help me proving that it is not really the bootloader that causes the rec/cam button problem .. you the best guys.. :D .. and to xda2jojo and gotan .. hehehehe you know why .. :D