WM2005: Theory About the Bootloader and Button in MAGNETO

[toenailed]

for others pls make a POLL if your button is working or not in WM2005
http://forum.xda-developers.com/viewtopic.php?t=22737

Been a while since the POLL Shows (http://forum.xda-developers.com/viewtopic.php?t=22737) that there are more people who has experiencing the non-working rec and cam button in Magneto than those has a working button. Up to this moment there are no single explanation why this is happening ..

But it is not the number that are very intriguing in the POLL (http://forum.xda-developers.com/viewtopic.php?t=22737) but its BOOTLOADER version, because we can easily distinguish does people who have a working button than those has not working button

:arrow: If you have a BOOTLOADER 1.01, 1.02 or 1.03

Most Likely ALL your Button will work .. if it doesnt work .. just a little adjustment then it gonna work

:arrow: AND if you have a BOOTLOADER 1.04 and 1.05

The Record button will only work if it is turn off(press power off once) and the buttonlock is off but it will not work if the device is ON or Total OFF (press power off twice)
and Camera button is not working in any type of situation (ON, Suspend(press power off once), total OFF(press power off twice))

:arrow: BUT if you have 1.06 the results are mixed

if you are sure that your original Booloader Installed is 1.06, then same as those who have 1.04 and 1.05 your camera and record will not work if the device is ON

but some have a working button and has Bootloader 1.06 ..
im not saying that a ROM upgrade can upgrade the BOOTLOADER since it needs the bootloader to be Unlock or to be Unprotect before it changes the Bootloader which mostly of the Device Bootloader is Lock and Protected and im not sure if there is a ROM upgrade (.nbf) that can unprotect our Bootloader to Upgrade it although we had already a case in the past thread that bootloader is change due to rom upgrade..
http://forum.xda-developers.com/viewtopic.php?p=54696#54696

Heres My list of ROM version that contains Bootloader 1.06

1.66.00 WWE
1.66.00 ITA
1.66.00 WWE
1.66FRA
1.66.01 GER
1.72.00 WWE
1.72.01 GER
1.75.00 WWE
2.02.t1 WWE
2.20.07 CHS - both Translated and not

PS. I cant find yet a ROM Upgrade(.nbf) than contain 1.04 and 1.05 bootloader but some 1.60 ROM (NOT ALL) contains 1.03 Bootloader.
also 2.06.00WWE doesnt contain a bootloader (or bootloader is blank/empty)

Now we first extract and compare the bootloader of those who have working button and uses 1.06 with those is nonworking button and uses 1.06 bootloader

User with working Button and Bootloader 1.06
buzz_lightyear
anybody

User with non-working Button and Bootloader 1.06
toenailed
xda2jojo
gotan

Suprising we FOUND no SINGLE DIFFERENCES AT ALL .. so it means that it is not the BOOTLOADER ..

BUT WE CANNOT CONFIRMED if no one will try to Downgrade there bootloader for those non-working and upgrade there bootloader for working button. And Downgrading and Upgrading the Bootloader is surely a very Dangerous thing that you will do to your device .. i once explain it in this post
http://forum.xda-developers.com/viewtopic.php?p=124909#124909

But Someone has to do it to end this Bootloader version Theory of non-working button .. and since im the KING of STUPIDITY .. i will do THis SimPLE STUpid ExpERIMENTATion to know if the Bootloader
is the MAIN Cause for a non-working Camera and Record BUTTON of SOME WM2005/WM5.0 user, including me ..


[frutybabes.jpg left]DAY 1 -- DOWNGRADING MY BOOTLOADER FROM
My Original Bootloader Installed
Bootloader 1.06 1.34b
Built Time: 14:32:09
Built Date: Feb 18 2004
and My Rec and Camera button is not working

to

BOOTLOADER VERSION NOW

Bootloader : 1.03 1.32b
Built Time : 14:54:39
Built Date : Dec 10 2003

[toenailed]

DAY TWO - RESULTS of DOWNGRADING FROM 1.06 to 1.03:

Flashing thru EXE from WM2003/SE:

After Flashing thru .nbf the Record is Working but the Camera button is not working ..
after the First Soft Reset the Record button is no longer working

Flashing thru SD Card from WM2003/SE:

After Flashing thru SD Card both the Record and Camera button is not working ..

Flashing thru EXE from WM2005:

After Flashing thru .nbf the Record button and Camera Button is not working ..

Flashing thru SD Card from WM2005:

After Flashing thru SD Card both the Record and Camera button is not working ..

Additional INFORMATION:

STILL if the power button is press once, the Record button is working
but
if the power button is press twice (Total Shutdown), the Record Button is not working

but if the Double TAP FUNCTION OF POWER BUTTON is DeActivated
Record Button is Working if the Device is off but not if on

Camera button is not working both on or off or in any situation

Downgrading from 1.06 to 1.03 Conclusion :

after Downgrading my BOOTLOADER from 1.06 to 1.03 MY RECORD AND CAMERA BUTTON IS STILL NOT WORKING

DONE LOTS OF REGISTRY TWEAKING AND ALMOST ALL POSSIBILITIES INCLUDING DOWNGRADING TO WM2003 and WM2003SE and GO BACK TO WM2005, EMPTYING THE EXTENDED ROM ETC..

AND STILL BUTTON IS NOT WORKING


Sponsor of BOOTLOADER 1.03

rhmartin
and
tumtum

TNX SO MUCH GUYS .. need to compare your both bootloader if i get it right .. TNX :D

Special Thanks to

buzz_lightyear
and
xda2jojo
and
gotan

heheh thnx for building courage to this dangerous experiment

and especially to the GREAT ONE

itsme

for creating such a wonderful dangerous tool .. tnx so much ..

-toe

NEXT STOP .. BOOTLOADER 1.01 .. WATCH OUT ..

[JamesManios]

I would image at this point that its probably not bootloader so much as the hardware revision of the device, and probably older devices work, (which typically have older bootloaders).

The REAL experiment would be for someone with working keys to upgrade their bootloader, (like a 1.01 to upgrade to 1.06)...
(Ya I know,... NOT ME!.... :wink: ) Some other braver soul...

Actually Buzz might have done this? Buzz has 1.06, but did Buzz ever upgrade his bootloader?

[toenailed]

I would image at this point that its probably not bootloader so much as the hardware revision of the device, and probably older devices work, (which typically have older bootloaders).

The REAL experiment would be for someone with working keys to upgrade their bootloader, (like a 1.01 to upgrade to 1.06)...
(Ya I know,... NOT ME!.... :wink: ) Some other braver soul...

Actually Buzz might have done this? Buzz has 1.06, but did Buzz ever upgrade his bootloader?

SOme ROM Upgrade, mostly the OLD ROM WM20003 contains already a bootloader 1.06 like the 1.66 and 1.72 (or even 1.75) .. some older rom contains bootloader 1.03 like the 1.60 .. but this ROM will only upgrade/downgrade your device BOOTLOADER if you have unlock bootloader which is most of the case is LOCKED or Protected..

im not sure if there is a rom update that can unlocks the bootloader and change it .. but in the past there is http://forum.xda-developers.com/viewtopic.php?p=54696#54696 .. but in a case of anybody (http://forum.xda-developers.com/viewtopic.php?p=123023#123023), (tnx my friend for all the info and help .. :wink: ), i believe it was updated and not originally 1.06 since he bought his device December 2003 and the bootloader 1.06 is built in Feb 18, 2004 .. :) .. and yet still he has a working Rec and Camera button .. but it was repaired in March 2004 so it could be also an update from the service center .. :) ..

-toe

[toenailed]

[frutybabes.jpg left]DAY 3 - DOWNGRADING MY Device BOOTLOADER from

Bootloader : 1.03 1.32b
Built Time : 14:54:39
Built Date : Dec 10 2003

and

Bootloader 1.06 1.34b
Built Time: 14:32:09
Built Date: Feb 18 2004


to

Bootloader : 1.01 1.28
Built Time : 22:22:13
Built Date : Sep 15 2003

anyway .. successful .. hehe starting to enjoy playing with BOOTLOADER heheh..

THX JAMES for the Bootloader 1.01 .. :D ..

[JamesManios]

anyway .. successful .. hehe starting to enjoy playing with BOOTLOADER heheh..

THX JAMES for the Bootloader 1.01

No prob,

Does that mean that the 1.01 bootloader worked? As in your hardware keys are now working, or the downgrade was successful?

[toenailed]

hi

i need to confirm yet and do more testing before i post the result of downgrading to bootloader version 1.01

anyway heres my initial FINDINGs

MY RECORD AND CAMERA BUTTON IS STILL NOT WORKING

-toe

[rhmartin]

Ok, this is a dirty job but (as they say) somebody has to do it!

As suggested by James, maybe if somebody can volunteer to upgrade his bootloader, we can finally put to rest the issue of "not working buttons" as either related to the bootloader or any other thing.

So toe, I see you are successful in downgrading, if you may share & give me the steps to do the upgrade i'm willing to take the risk!

I have bootloader 1.03 & working buttons. I'm willing to try an upgrade to 1.06.

Let me know. Good luck in your experimentations..... :wink:

[Pyrofer]

I find it odd that there could be a software difference that would stop hardware buttons working, and yet here we have it. 2002/2003/2003se all work fine, but put 2005 on and they brake.

the recent experiments in downgrading bootloader would suggest that its the actual hardware that is the problem, ie, later models (tend to have later bootloader) are less likely to work.

From this, I think its time somebody looked at how the buttons actualy interface with the hardware, and what the difference is. Because the phone buttons, the cam/note buttons and the contact/calender buttons all work on different methods.

We may have to resort to a hardware hack. It may be as simple as changing a surface mount resistor to alter the value that the buttons trigger the hardware or as complicated as changing the gpio pins, who knows.

Any hardware hackers wanna take a look?

[amdworld]

god i wish this theory of bootloader wud go away ,i bought a secondhand xda2 of ebay last week it has 1.03 and it works fine.

one possible clue is unfortunately is to dismantle the device or remove casing and locate what REVISION the board is.which i will do 2morrow .at the same i will try and identify any obvious differences between the two.

my original device has 1.06 and works fine!!!!!
http://www.xsorbit1.com/users/amdworld/Attachment/ScreenShot1123.jpg

[rictec]

well i still think its a driver issue or hardware gpio version issue
if i m not wrong the rom its made for one single device and that device was probably old so
new ones have new ship version and dont work. bootloader is recent
old ones work
and then aggain some new ones works cos the way chip board are manufactured
an old stock off chips got int production in a more recent version of devices wich made some 1.06 bootloaders also work.
so check the driver compared with 2003 driver and the answer is hidden there........

ok i m an idiot full of ideias
god buzz will solve it
god toenailed will prove it
god xda2jojo will anounce it

[toenailed]

Ok, this is a dirty job but (as they say) somebody has to do it!

As suggested by James, maybe if somebody can volunteer to upgrade his bootloader, we can finally put to rest the issue of "not working buttons" as either related to the bootloader or any other thing.

So toe, I see you are successful in downgrading, if you may share & give me the steps to do the upgrade i'm willing to take the risk!

I have bootloader 1.03 & working buttons. I'm willing to try an upgrade to 1.06.

Let me know. Good luck in your experimentations..... :wink:


hi rhmartin .. pls PM me your YM or ICQ bro .. we need to talk live in Upgrading your BOOLOADER .. my first downgrade to 1.03 .. took 1 minute to finish .. and yeah ive been praying that nothing will happen .. when i downgrade to 1.01 from 1.03 it only took 15seconds .. but when i upgrade to 1.06 it took almost 30seconds.. but when i downgrade again to 1.01 and now from 1.06 it took me also 36seconds .. anyway its more on your PC and PPC condition than the actual upgrading process .

wish you were in pHilippines so we can study and compare our device .. :(

anyway guys before i even try to downgrade my Bootloader id already ask a forumer who has a working button to open his device and i will open my device also and compare it with him .. i just had to confirm first using all bootloader that its not really a bootloader issue .. it will just take us too long since i cant find a forumer near to my place that has working button to compare it we only communicate thru IM ..

ONE MORE THING GUys .. anyone here has also BOOTLOADER 1.01 pls pm me .. id like to check and compare it with the one i got from JAMES .. im having some problems with 1.01 than with 1.03 .. id like to know if this is just me and my device or the problem is incompatiblity somewhere of bootloader itself ...

anyway JAMES have you try using an MMC bigger than 64MB .. i dont have a problem in SD card even in 1gb but if i use MMC it can only read first 64MB and it will hang there .. i already try it in 1.06 but i havent encounter that problem .. i remember in 1.03 that i dont a problem in that either .. anyway tnx again for the 1.01 ..:)

[toenailed]

god i wish this theory of bootloader wud go away ,i bought a secondhand xda2 of ebay last week it has 1.03 and it works fine.

one possible clue is unfortunately is to dismantle the device or remove casing and locate what REVISION the board is.which i will do 2morrow .at the same i will try and identify any obvious differences between the two.

my original device has 1.06 and works fine!!!!!


hi amdworld

can you make a Post in Here .. plsss
http://forum.xda-developers.com/viewtopic.php?t=22737

including your Serial Number and part number .. to see how old your device really is .. plss .. tnx

-toe

[rictec]

i read thats what i do and read here that TSC2200 is responsible for the keys
so there is REV A to F of that chip
not working camera and record must be it

i put some file here for the you guys have a look

[toenailed]

i read thats what i do and read here that TSC2200 is responsible for the keys
so there is REV A to F of that chip
not working camera and record must be it

i put some file here for the you guys have a look

=hi rictec..

actually m with you that the problem is due to driver (or dll) and it can be fix with a patch or a new driver .. since we dont have this problem in old WM version .. maybe we just need to distinguish first wat causes the problem .. :)

anyway tnx for the info .. been doing great help for me .. especially the 1.01 .. :)


-toe

[rictec]

i did test for a 128MB MMC card i have in my foto camera and it worked ok
i usualy use a 1GB sandisk SD card
if that can say anything...its tested

Ps i never tryed a MMC card befoure only SD

[toenailed]

i did test for a 128MB MMC card i have in my foto camera and it worked ok
i usualy use a 1GB sandisk SD card
if that can say anything...its tested

Ps i never tryed a MMC card befoure only SD

hi rictec ..

oic tnx .. ill try your bootloader if i still have the same problem .. and post later the result ..

tnx again MATE .. :wink:

-toe

[rictec]

at least read this will make it go bether lol

[ccrrazzzy]

I have an old XDAII from Korea that came with 1.52 or something like that and a newer one from China with 1.66 with Chinese on it.
I have 2.20 Translated on both now.

The hardware is different.
I broke the screen on the China one and I took the screen out of the older unit. The connections would not even fit. Different hardware. :shock:

The China one is at www.PPCtechs.com now. When it comes back, I will flash them both with 2005.
If one works and the other does not... It will prove it is a hardware issue.

[ccrrazzzy]

Has any one tried this http://ae.inc.ru/aebplus_t.html It woks great on 2003 2.20 etc. If it works on 2005, even with only the two top buttons, you could have a total of SIX buttons. (two real and 4 virtual) If the Volume slider part works.. THAT WOULD BE GREAT TOO! :D

[rhmartin]

It's final .....

The objective of toenailed Part 4 experimentation is to determine if the bootloader is the main cause of not-working buttons in Magneto.

To confirm, we decided to use my device with a version 1.03 bootloader & working buttons to upgrade to version 1.06 & see if the buttons will still work or not.

The procedure involved:
:arrow: OS downgrade from Magneto to PPC 1.72,
:arrow: upgrade of the bootloader to 1.06 (toenailed version 1.06/not working buttons) and
:arrow: installation of Buzz Mobile V1.6a (or any Magneto version).

And ......

THE UPGRADE WAS SUCCESSFUL.

It's a scary thing to do, a cliff-hanger from start to finish but, with toenailed guiding me what could possibly go wrong!? :wink:

So after the upgrade to toenailed bootloader version 1.06 & BM V1.6a, are my camera & record buttons still working???

YES, THE BUTTONS ARE (STILL) WORKING :!: :!: :!:

Therefore, its not the bootloader that's causing the buttons not to work in Magneto .... it's something else: hardware, driver, etc. But whatever, we have eliminated the bootloader as a probable cause of not working buttons :!:

Thank's toenailed for the version 1.06 bootloader & the patience to bear with me during the upgrade process.

Notes:
Version 1.06 bootloader / WM2k5 1.60a solved the hang problem at power on if the device is in landscape mode.
"Double-tap power off" exhibits a different behavior compared to version 1.03 / WM2k5 1.60a.

Either its the bootloader or the "NEW" v1.60a that caused those, i'll post later if I can confirm.

Waiting for Experimentation Part 5 :idea: toenailed .......

-rhmartin-

[rictec]

thats a driver problem
so rhmartin you are one of a kind great you did that for all the ones who doent have working butons
Thank you man

and toenailed are so quiet lol
i m still searching for driver related info about xda2 in the linux comunites
they reverse eng the htc drivers and info is there somewhere

[steverae]

Sorry i can't offer any technical advice or anything on this matter :(

I can only say that in wm2003se 2.06 all my buttons work fine, but once i upgrade to wm2005 (any version) the rec/cam buttons stop working....

Now i haven't changed the bootloader or anything (i'm on 1.06) but i have noticed a couple of issues :-

1) When i upgraded from 1.50f to 1.50g then to 1.50h i did not lose any data, the only information i had to reenter into my device with the date and time, now when i was experimenting with 2003se every time i changed the os, i had to reinstall everything.... is this a common thing to do with the static storage, or is it unusual ?

2) since my rec/cam buttons don't work, i can't perform a hard reset (by following instructions to hold down rec/cam/nav pad/ power and press the soft reset button - you need like 4 hands) - is this correct or just particular to my device...

It's a unlocked orange m1000 Comments please !

[rhmartin]

thats a driver problem
so rhmartin you are one of a kind great you did that for all the ones who doent have working butons
Thank you man

and toenailed are so quiet lol
i m still searching for driver related info about xda2 in the linux comunites
they reverse eng the htc drivers and info is there somewhere

Hi rictec,

All the credits to toenailed! He designed the tools & made bootloader tweaking 'look' easy. I just provided my device for test.

The intention is to drag away toenailed, jojo & the rest from this hardware button problems so that they could help us out more on some of the Magneto problems. But, unluckily we failed.v :(

Hope you find the driver info soon, I know you are a great man too!

[shafa]

Guys,
I downgraded my boot loader to 1.01 and 1.03 to see if the button problem is rectified, with no luck :(
I think after two Himalayas tested, we can decide that the boot loader is not the problem.

Shafa

[rictec]

for the non working one try replacing the keyboard dll
i dont know but it can work
i cant test it cos mine is working too

[ccrrazzzy]

I have not tried my other XDAII yet cuz it is still not back from the PPC techs but if I remeber correctly, the buttons did not work with 2005.

Old XDA bought in Dec 2003 DOES work.
New one bought this year made in China with Chinese 1.66 on it originally does NOT work.. (If memory is correct.. I only had 2005 for a few days before puting 2.20 back on). I will check again when it comes back.

[kevin666]

we also need to fix the camera quality issue :?

[ketandp]

Hey Guys,
i think I have flashed my ROM for aobut 8 times (including 3 times today itself) to upgrade it to WM5 and stable one.
lastly I tried with the 1.50g and found buttons are not working (with bootloader version 1.0a) now I'm going back to the 2k3SE to see if i can get my older bootloader 1.06 back and then i can proceed with the 1.50g again.
I hv benn facing lot of issues with this like buttons not working; dont see wireless USB modem working(i use it most :( ), didnt see photocontact application in there and lot others.
Can anyone tell me whether these issues been resolved with 1.60 or 1.50i ?
I dont mind flashing my device for another 5-4 times, if i get all these working!!

thanks in advance.
Ketan

[toenailed]

Hey Guys,
i think I have flashed my ROM for aobut 8 times (including 3 times today itself) to upgrade it to WM5 and stable one.
lastly I tried with the 1.50g and found buttons are not working (with bootloader version 1.0a) now I'm going back to the 2k3SE to see if i can get my older bootloader 1.06 back and then i can proceed with the 1.50g again.
I hv benn facing lot of issues with this like buttons not working; dont see wireless USB modem working(i use it most :( ), didnt see photocontact application in there and lot others.
Can anyone tell me whether these issues been resolved with 1.60 or 1.50i ?
I dont mind flashing my device for another 5-4 times, if i get all these working!!

thanks in advance.
Ketan

hi ketan ..

can you extract your bootloader .. just copy the files i attach then send it to me thru pm pls ..

what do you think your old bootloader before you upgrade to WM2005 .. i believe it was changed after you upgrade since 1.50g contains bootloader 1.00a ..

anyway what other OS youve been try before you go to Wm2005 ... can you name it all pls..

PS .. make also your POLL in this thread pls ..
http://forum.xda-developers.com/viewtopic.php?t=22737&start=50

tnx

-toe

[ketandp]

Thanks Toe,
I'll give this a try today and try to extract the bootloader.
u are right, i hav ethe 1.00a right now and that shd be after in upgraded it to 1.50g.
I remember I had 1.06 earlier while i flashed with 2003 and 2003SE.

I tried with 1.60 lastly kept it for a day and then came back to the 1.50g again as it has got more storage memory. I cant live without few programs and my emails also take some space that is not possible wit the 1.60 with low storage memory.

let me know if u still need me to extract the boot loader and pass it onto u.

[richarddb]

just a thought guys. if record button and camera buttons are not working try installing a third party apps like resco audio recorder and w/ camera i have no idea if there's like a third party apps for camera. then instead of having the orig recorder and camera apps map to these buttons, try using the third party apps and map these apps to their corresponding buttons.

[ketandp]

I just tried assigning camera button to my messaging application and that doesnt work.
This is obvious, a button issue not the application. if button cannot be assigned to one application; assigning it to another will give u the same result.

[ketandp]

I saw the screen snap by amdworld here in this blogs (page -1 ). It has got the SPB pocket Plus installed on WM5 i beleive.
I tried the old version I already had with me earlier and that didnt work. after lookin at his screen snap; i tried with the one that is on the SPB site (eval) and I cud install it on WM5 this time. However, most of the functionalities are not working.. importantly, the IE features, that i need most and the battery monitor doesnt work.

[rictec]

we also need to fix the camera quality issue :?

as i have read the camera is probably directx capture now and problably someone could write an aplications to use the directx of the camera
i have some source code examples but its not my language :-)

PS sorry to reply to the wrong post can it be moved into the devel area or something?

thanks

[crusher]

There are 2 different versions of this device (with identical appearance).
One is run by Qtek as 2020, the other is 2060.

The 2060 has a LCD with a bare connector made from the ribbon cable itself, and it fits into a connector that has a lever or something similar.

The 2020 (only this is sold as XDA II) LCD has a 2-pieces snap connector, of which a half is soldered on the end LCD ribbon cable.

There are some other minor hardware differences as well.

And you know what? Generating further complications, despite that only the 2020 is sold as XDA II, BOTH are sold as T-Mobile MDA II.

__

Taking into account the fact that all of these devices will loose camera functionality if you press soft-reset right after hard reset (before customisation starts - you may try this without risk!! it restores if you do a hard reset again and let the customisations install), if I were you, I would give up doing useless experiments with the bootloader and would go for something really specific - like comparing the ExtROM or the like.

[ccrrazzzy]

Before I can assure you of the old hardware and new hardware idea,,, I need to put 2005 back on the newer phone.

I put 2005 on it a few months ago, then put 2.20 back on then broke the screen and sent it to ppctechs.com. Now I have it back and when I try to reload the 2005 for you all to test it, it just hands after insatll.
If I remeber correctly, there was an issue like this of 2003 to 2005 then back to 2003 and NOT be able to go back to 2005 again..
Is there any remody so I can test the buttons again for everyone?

[toenailed]

There are 2 different versions of this device (with identical appearance).
One is run by Qtek as 2020, the other is 2060.

The 2060 has a LCD with a bare connector made from the ribbon cable itself, and it fits into a connector that has a lever or something similar.

The 2020 (only this is sold as XDA II) LCD has a 2-pieces snap connector, of which a half is soldered on the end LCD ribbon cable.

There are some other minor hardware differences as well.

And you know what? Generating further complications, despite that only the 2020 is sold as XDA II, BOTH are sold as T-Mobile MDA II.

QTEK 2060 is PH10A
QTEK 2020 is PH10B .. :wink:

from the start the MODEL ID is never been an issue when it comes to button problem in MAGNETO since it was obvious that some who has working button has also uses PH10B .. ..

it is true that the major difference of two HIMALAYA device is found in LCD but it cannot be distringuish by Model ID .. PH10B has released an Identical LCD hardware that with PH10A .. so we cannot say if it is old or new unless we analyze it ..the best way is thru the Hardware button of WM2k5 ..

i believe the story starts here
http://forum.xda-developers.com/viewtopic.php?p=117629#117629
(thanks Larholm)

since no one ever have try before changing his bootloader, the QUESTION: "HOW TO CHANGE THE BOOTLOADER?" had popup .. and this is wat this experimentation do .. to prove if the BOOTLOADER is really the responsible for Button PROBLEM in MAGNETO


__

Taking into account the fact that all of these devices will loose camera functionality if you press soft-reset right after hard reset (before customisation starts - you may try this without risk!! it restores if you do a hard reset again and let the customisations install), if I were you, I would give up doing useless experiments with the bootloader and would go for something really specific - like comparing the ExtROM or the like.

im so sorry .. what ExtROM ?? in MAGNETO, Exnteded_ROM Folder is use only for additional Memory Storage .. thats why i create this wiki page
http://wiki.xda-developers.com/index.php?pagename=Himalaya_2005_FolderName

so you can rename the Extended_ROM Folder to any other name ...

btw there is no Customization cab release YET for HImalaya MAGNETO (WM2005) .. camera Application is already builtin in the OS .. :)

for further info read this wiki page
http://wiki.xda-developers.com/index.php?pagename=Himalaya_2005


PS ..

GUYS .. who has OTHER Bootloader version and voted it in the POLL .. plsss use this Application to extract the Bootloader then PM it to me or POST it here plss .. tnx so much guys..:D
http://forum.xda-developers.com/download.php?id=5390

-toe

[zxvf]

Ok I'll finally ask this question, I don't know why I didn't ask it earlier, anyways I've been playing around with the bootloader now for some type, me and obelix, have been working at this for some a while.. we've managed to gather enough information to fully manipulate the bootloader. (on my audiovox vx6600 a.k.a XDAIIs/BlueAngel). so here is my question.

I've uploaded so many different versions ROMs (nk.nbf, radio_.nbf, ms_.nbf) to my devices, and NONE have actually changed my bootloader, as I still see on the screen the same thing I've always seen

SERIAL or USA and at the bottom 1.02, the 1.02 has NEVER changed, so how the heck are u guys changing the bootloader.. I finally got my self a serial cable so since I can actually use the "l", and "rrbmc" command's I can send any rom to it directly without the need of any of the programs that the OEM's use. (himaupdate, Baupgrade etc..)

So what am I doing wrong? what program do u guys ACTUALLY use ?

anyways here is the link to the post to the bootloader info, for the ones interested..

thanks

http://forum.xda-developers.com/viewtopic.php?t=21679&highlight=

[jenellej]

I just re-flashed 3 phones (including mine), which all had bootloader 1.06.. however the 2 other phones had their buttons working and mine weren't...

Could upgrading from 2003SE to Buzzmobile be the cause? The 2 other phones I upgraded directly from 2003 (not 2003SE)..

Another note, the registry entries (for the buttons) of the 2 phones with working buttons were very different from mine...

hmmmm :?:

[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

[toenailed]

I just re-flashed 3 phones (including mine), which all had bootloader 1.06.. however the 2 other phones had their buttons working and mine weren't...

Could upgrading from 2003SE to Buzzmobile be the cause? The 2 other phones I upgraded directly from 2003 (not 2003SE)..

Another note, the registry entries (for the buttons) of the 2 phones with working buttons were very different from mine...

hmmmm :?:

hi jenellej

.. the real issue with the button problem is the driver compatiblity with the hardware .. and i believe that HTC(or those who have BSP) can fix it since they know more of our device than the MS(the same issue in WM2003SE BlueAngel CAMERA) .. but i dont think they will waste their time fixing it since they already discontinued the production of HIMALAYA and focuses now in their new devices ..

i've already try using the old driver from WM2003SE and WM2003 but it doesnt work .. so we really need to rely on patching (or other called it cracking).. but still cant figure out how .. especially dont have my device yet .. :cry:

-toe

[zxvf]

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


THANK YOU THANK YOU THANK YOU, you coudn't have done a better job, thanks lots, great HOWTO.. hopefully I can get my phone working again, I'm starting to think that it's really not the bootloader that I screwed up, but instead other parts, cause I try to do a usbmonitor on any update, (even the one made specifically for my device) and I just get errors non stop, even if I modify them with xda2nbftool's tools (thanks itsme), the closest i've gotten to reviving my poor phone (u should be careful too, I learned my lesson, ones I get it working I'll only do it IF i have to hehe) anyways I realized that when it's trying to compare HTCE to check what device it is, the phone replies with something with jibberish, (probably wasn't a good idea starting to flash things at memory address 0x0 to 0xffffffff) :| I should of known better heh. ones again thanks for the info..
anyways, I'm getting tired of working on this been 3days non stop.. i'm going to get some shuteye maybe this is all a dream and my phone will ring waking me up (actually thats the dream it self heh)


CIAO
THANKS AGAIN

[ccrrazzzy]

I hate to be a pest but could ya save me hours of reading?
Q: Is it possible to have 2.20 then upgrade to 2005 then go back to 2.20 and then back to 2005?
I think I remeber mamaich saying you can't but I was wondering if anything has changed.

When I do it, it just sits there and displays the O2 logo.

[Truthiswithin]

Okay, there's probably a completely different answer to this problem, but on my Himalaya NONE of the buttons are working, not even the green and red or the directional key pad, NOT EVEN the power button! This after upgrading to 1.60a

So, I downgraded to 1.50g and the buttons came back to life (all of them, record and photo as well).

Any idea why this would be?

[alpha_geek]

Like everyone else my rec, and cam buttons do not work.

However i have noticed that if i turn my device off, and hit the rec button, it will turn the device back on and start recording. the same is not true for the cam button.

however when i do this, my answer and hang-up buttons stop working, and the can and rec buttons still not work. If i soft reset, everything is back to normal (i.e. my rec and can buttons are not working, but my phone buttons are)

to me this means, that the rec button IS mapped, but for some reason dose not work.

also once i have started recording with the rec button and the device has come on, i cant use the rec button to stop the recording.

is this any help to anyone?

[smogthemog]

Same problem here Alpha !

[Goldry]

I have exactly the same experience with the buttons as alpha and smog.

If anyone thinks it's useful, how can we find the version numbers of the drivers responsible for the buttons?