Another way to instal rom - Touch2 ROM Development

i need some beta testers here to make this stable.
Beta testing phase only for advanced users; don't want to explain how to flash a ship ROM using the original SPL to your device!
This is an easy way to flash unsigned OS images to the HD2. It should not void your warranty like HSPLs do, because it does not change your SPL. I know for a fact, that repair centers are advised to check the SPL version number on the device.
How safe is it?
We disabled SPL and Radio flashing, so it can only flash Splashes and OS images.
(To all hackers out there... don’t enable it! else you will BRICK your device)
Worst case is that you destroy your OS partition, in that case you must flash a ship ROM using the original SPL (Vol down on boot run ruu from PC )
We did our best to make it save, else we would not release it for public testing, but anyway, all on your own risk!
How to use it:
* Download the SSPL_RUU.exe and put it into an empty folder
* Add the RUU_signed.nbh that you want to flash to your device into the same folder
* Connect the device to the PC, device must be running WM, not show the 3 color screen
* Run SSPL_RUU.exe
Thanks for testing!

Chriss33 said:
i need some beta testers here to make this stable.
Beta testing phase only for advanced users; don't want to explain how to flash a ship ROM using the original SPL to your device!
This is an easy way to flash unsigned OS images to the HD2. It should not void your warranty like HSPLs do, because it does not change your SPL. I know for a fact, that repair centers are advised to check the SPL version number on the device.
How safe is it?
We disabled SPL and Radio flashing, so it can only flash Splashes and OS images.
(To all hackers out there... don’t enable it! else you will BRICK your device)
Worst case is that you destroy your OS partition, in that case you must flash a ship ROM using the original SPL (Vol down on boot run ruu from PC )
We did our best to make it save, else we would not release it for public testing, but anyway, all on your own risk!
How to use it:
* Download the SSPL_RUU.exe and put it into an empty folder
* Add the RUU_signed.nbh that you want to flash to your device into the same folder
* Connect the device to the PC, device must be running WM, not show the 3 color screen
* Run SSPL_RUU.exe
Thanks for testing!
Click to expand...
Click to collapse
Ok. I want try but where is the SSPL_RUU.exe ?

O.K count me in ,waiting for SSPL.

here is a file http://www.gsmspain.com/foros/p8836635_Marcas-Htc-Qtek_CLUB-HTC-HD2-ALIAS-LEO-Reviews-Apps.html

Chriss33 said:
...
This is an easy way to flash unsigned OS images to the HD2.
...
Click to expand...
Click to collapse
You are talking about Touch HD2 (aka LEO) and this is a Touch 2 (aka MEGA) area.
I don't speak spanish (too much) but the link you provided is about HD2 also .
Are you saying the procedure and SSPL_RUU.exe for HD 2 is the same for Touch 2 ?

ci6i said:
You are talking about Touch HD2 (aka LEO) and this is a Touch 2 (aka MEGA) area.
I don't speak spanish (too much) but the link you provided is about HD2 also .
Are you saying the procedure and SSPL_RUU.exe for HD 2 is the same for Touch 2 ?
Click to expand...
Click to collapse
da. este aceeasi procedura.

Chriss33 said:
da. este aceeasi procedura.
Click to expand...
Click to collapse
You are completely wrong. Cannot use the SSPL_RUU.exe for HD 2 on Touch2.
If you have an SSPL_RUU.exe expressely done for Touch2 please post here otherwise your words are only a "bla bla bla".....

Chriss33 said:
da. este aceeasi procedura.
Click to expand...
Click to collapse
It's not working. ERROR 202: CONNECTION
Hei, Chriss33, hai sa incercam cu un update pt iphone, am auzit ca ar fi compatibil cel de 3gs cu mega
Let's try an IPHONE ROM, they say the one for 3gs i will work on MEGA

eangel said:
It's not working. ERROR 202: CONNECTION
Hei, Chriss33, hai sa incercam cu un update pt iphone, am auzit ca ar fi compatibil cel de 3gs cu mega
Let's try an IPHONE ROM, they say the one for 3gs i will work on MEGA
Click to expand...
Click to collapse
am incercat. posibil sa reusesc cu sspl si un kit de windows 6.1; diseara incerc caci am mai mult timp.

Related

Problem Solved: Dead devices due to tmob 1.72 + Downgrade

OK Guys. Problem Solved : Dead devices due to tmob 1.72 + Downgrade
Problem: New version changes Device ID, as well as ID format.
If you upgrade to tmob 1.72, you cannot downgrade back, as you cannot supply valid NBF files for the new device ID. If you try to play around, you end up with a very dull bootloader screen "Serial V.1.06", and nothing more can be done. SD card images cannot be flashed due to the same reason.
Untill our developers come up with a simple tool, the following 2 solutions can be used to get out of the disaster:
Solution 1:
(tested and 100% working for both dead devices stuck in bootloader and devices working but stuck with the tmob 1.72 version.)
You will need a working device (with old ROM before 1.72), besides your dead one.
1. Prepare your DEAD device in Bootloader mode. Don't connect it yet. (If it is still working but you want to downgrade, press Power+Action+Stylus, if it is already stuck in bootloader, just reset with stylus).
2. Connect your WORKING device, with OLD version via activesync.
3. Start the rom installation of your choice normally, with a version compatible with this WORKING device (Official or Modified NBF files via HymaUpgradeUT). If you don't know what I am talking about, just use your official file downloaded from your WORKING devices' provider).
4. Press NEXT, untill you are presented with the Current version and the one that will be installed. DO NOT click "UPGRADE" yet. (If you got an error so far, you are not using the correct version for your working device.)
5. When you get the dialog with the versions, disconnect the WORKING device from the craddle and connect your DEAD device, in bootloader mode.
6. Click "UPGRADE" and go get yourself a drink.
Et Voila.
Thanks to Victor for inspiring this solution.
Solution 2:
If you don't have another working device, and only have a dead one stuck in BootLoader, you can flash the attached image, through SD card. It will bring back your device to life with the BETA tmob 1.72 CE ROM.
Write the image to the card using "NTRW". Info on SD images and NTRW can be found in this forum.
Unfortunately, i don't have device even with working bootloader And it stuck in TMObile screen
I am sorry I have no solution for screwed Bootloaders, but if your device loads into the tmob screen, there must be something there still working. The only thing I can advise is to try to hard reset and not go into the extended ROM setup files (Soft Reset right after the Hard Reset and welcome procedure), but I guess you don't reach that far ....
What is about for XDA 1?
HI !
I have a Dead XDA. The bootloader is OK. How can I do with it ?
I need some advice for doing it, please !
Best reguard,
Carlo & Victor... You are GREAT!!
Okey.... I will try FIRST!!
please, where is the officiale t mobil rom ? we all have the beta (and thee pb you solve) but not the official one...
thanks
When i posted the T-mobile 172 rom i did not know how much greif it would cause people, sorry to everyone for this
As to the second solution using the SD card is it possible to use this method on a working XDA2.
Basically i have a UK XDA2 and of corse i getthe ID error if i run the upgrade, i dont understand very well how to change the ID part so could i just make the SD card with the rom on it and follow your instructions to recover a dead XDA2
Thanks
John
What should I do when I want to upgrade/downgrade...
I have the T-Mobile 1.72WWE rom installed.
Everything works ok for now, no problems.
But do I need to do when I want to upgrade/downgrade?
I don't have a second device so thats not an option
Please advise.
Thanks
To cairo31male!!
NOP!! Can't HELP!! Maybe the BOOTLOADER got the diffrent version? Mine is 1.03. Can u tell me how to upgrade the bootloader to 1.06?
And you mentioned about OLD version, what do you mean by that?
@hcnsoft:
The 2 solutions described above are for XDA 2's which have been screwed up by installing / uninstalling the latest beta version tmob 1.72. If this is your situation, and you have a working bootloader, both solutions should work for you.
@SEB152030:
The beta we have is 1.72, which caused all these problems. If you have another working device, as described in solution 1, you can revert back to the latest working official ROM (1.66), just follow the steps decribed above and use the official 1.66 upgrade program.
@applecom:
If your XDA 2 is dead, there is no harm in trying. But basically, this SD file will only work on devices that have already been upgraded to 1.72 and then died. If it is dead because of any other reason, I suggest you stick with older stable versions and don't try to mess up with 1.72 for now, until the developers come up with a simple tool to go back and forth between different roms. You can flash SD images that were made from other working devices that have your same model/language. You wouldn't get any errors that way.
@Panja:
Since your device is working, I suggest you wait a couple of days, before trying anything. The developers might come up with a simpler solution. If you absolutely have to downgrade, you can follow the solution 1 described above, but you will need another working device for a few minutes. Use the other working device which has the old ROM installed and start the OLD ROM installation software, then plug in your device with the 1.72 ROM AFTER you get the different versions dialog with the button "UPGRADE".
@Ivan-R: which method are you tying? Solution 1 or 2? FOr the first solution, I guess it should work. For the SD flashing, I beleive you should have Bootloader 1.06. How to get that one, I don't know, but I strongly advise against it, untill all this matter is clear, as each new version of the bootloader implements stricter security, which will make it harder to customize in the future.
OLD version means any version before 1.72
cairo31male said:
@hcnsoft:
@Ivan-R: which method are you tying? Solution 1 or 2? FOr the first solution, I guess it should work. For the SD flashing, I beleive you should have Bootloader 1.06. How to get that one, I don't know, but I strongly advise against it, untill all this matter is clear, as each new version of the bootloader implements stricter security, which will make it harder to customize in the future.
OLD version means any version before 1.72
Click to expand...
Click to collapse
I already try BOTH solution!! Solution 1, i try with ROM 1.03.11, which is thats the basic ROM. Solution 2, the RESULT is Not Allowed UpDate!!
So i guess this is the matter of BOOTLOADER!! Yours is 1.06 and me 1.03. THATS THE PROBLEMO NOW!! Now... How about upgrade the BOOTLOADER??
[email protected]#$!%G FREAK ROM!! :evil:
Mas Ivan,
Sebaiknya anda jangan menggunakan sd image yang di upload karena masih beta untuk menghindari kesalahan pada rom 1.72
thanks cairo for the info, my xda is working with the standard rom, Our only problem is me and the guy that got the rom in the first place would like to use it but we cant
anyway thanks for youe info
John
Solution 1
Solution 1 don't work for me because (I think) 2 version of bootloader 1.03 and 1.06.....
I found a solution : Here
Radio Stack Downgrade
I loaded the 1.72 Beta and would like to keep it, but the Radio Stack is horrible for me. I need to go back to the O2 launch version of the radio stack. I noticed in the O2launch Rom that the contents of the exe file included Radio.nb while the 1.72 exe contained Radio.nbf.
Is it safe for me to try and downgrade only the radio stack and if so should i use the launch version of himalaya upgrade or the 1.72 version of himalaya upgrade to install the launch radio.nb file?
Can anyone give me some advice here? My radio is barely functional. can't find networks where i know there is coverage. Thanks for any advice.
Re: Radio Stack Downgrade
watchdogsdg said:
I loaded the 1.72 Beta and would like to keep it, but the Radio Stack is horrible for me. I need to go back to the O2 launch version of the radio stack. I noticed in the O2launch Rom that the contents of the exe file included Radio.nb while the 1.72 exe contained Radio.nbf.
Is it safe for me to try and downgrade only the radio stack and if so should i use the launch version of himalaya upgrade or the 1.72 version of himalaya upgrade to install the launch radio.nb file?
Can anyone give me some advice here? My radio is barely functional. can't find networks where i know there is coverage. Thanks for any advice.
Click to expand...
Click to collapse
Go go go... Just downgrade it!! 8) Then you will join me in HERE!! Huahahahaha... You are STUCK for the REST OF YOUR LIFE!!
Didn't have any trouble downgrading
I just upgraded to 1.72 last week...hated it...gprs was WAY too slow. Today I downgraded and crossed my fingers back to Xda_II_Upgrade_v16050.exe (filename..not sure where i got it).
IT WORKS!! everything went fine and is fine.
I think my bootloader said it was something like version 1.01 (very hard to read that screen without the backlight) So I'm guessing this downgrade problem may be specific to bootloader versions.
No expert, just letting you know what i did.
This site is amazing. Thanks for everything.
Re: Didn't have any trouble downgrading
mkriemersma said:
So I'm guessing this downgrade problem may be specific to bootloader versions.
No expert, just letting you know what i did.
Click to expand...
Click to collapse
I AGREE WITH YOU!! BOOTLOADER thang'!! I am not EXPERT too, but I REALLY NEED SOME HELP HERE!!
Hi,
Thanks for all help!
I have a dead unit due to 1.72 ROm.
Itried to fool the himalya upgrade program with a soft reset as suggested in another thread, it works It gets trough the device id but stops when erasing rom, any suggestion?
Is there anyone out ther that can disassamble the himalyprogram and
make a small program without error checking?
I also have bootloader 1.06 and tried also "ntrw write ROM.nb1 H:"
It works writing the image but my bootloader don´t loads any rom.
Tried with 2 differnet SD cards, and soft reset, hardreset, and only pushing camera button, without succes, what is the right command?
Any more suggestions?
@nilron:
Press ARROW KEY (any direction on joystick) + POWER Button + SOFT RESET, all together, then wait a little. You should get instructions to press POWER to start flashing.

qtec 2020 rom 1.72

y saw at www.pocketpartner there is a romupdate 1.72 for the qtec 2020
link:http://www.pocketpc-club.nl/content.php?id=3331.
hein
Thanks!!!
Has anyone tried to upgrade using this ROM? Any problems?
I've posted the last rom french & English one on the following link.
Read what the people says (The roms that I post are original from dangard)
http://forum.xda-developers.com/vie...tart=200&sid=f82d07fe82b956d754c6f2e9845c419f
Kind regards
Problem with the ROM 1.72.03
Hi,
I've install the ROM 1.72.02FRA (ExtROM 1.72.603)
And the MMS composer don't work...
When I launch it, they close immediatly
Can you help me ?
Didier
hein said:
y saw at www.pocketpartner there is a romupdate 1.72 for the qtec 2020
link:http://www.pocketpc-club.nl/content.php?id=3331.
hein
Click to expand...
Click to collapse
I have installed the rom update 1.72.00WWE on a Qtek 2020. It works fine. However I do have a view remarks. I dont see any changes. I thought windows 2003 second edition was installed. The external rom version is 172.125. If I start TomTom3 when the wired GPS is not connected, I get the message "Can not open COM1. Port does not exist". Fortunaly it works well when I connect it. Does anyone know why I do not see any changes in 1.72
Re: Problem with the ROM 1.72.03
Figmentbe said:
Hi,
I've install the ROM 1.72.02FRA (ExtROM 1.72.603)
And the MMS composer don't work...
When I launch it, they close immediatly
Can you help me ?
Didier
Click to expand...
Click to collapse
Hi,
I think that you have make a backup before to install the update & that you have tryed to reinstall your backup after the update.
You have to remain that if you make a backup, you are not able to restore your backup after.
If you do this, you will overwrite some programs (mms,...)
If not give me more details.
Kind regards,
Update from pocetpc-club works fine.
I updated my QTEK with the file as mentioned. It worked fine. Restoring an old backup is not a problem, but doesn't give a full backup, because you restore the old files. So you really have to install everything new.
As far as I can see, there are no problems with the update.
Regards, Luc
Does this ROM update the bootloader?
Hi,
Has any of you who have upgraded to this ROM checked if it also does upgrade your bootloader to 1.06?
Regards,
Mark
Hello,
Mine has upgraded the bootloader to v1.10.
Cheers
BootLoader
Raphael said:
Hello,
Mine has upgraded the bootloader to v1.10.
Cheers
Click to expand...
Click to collapse
Upped and running on i-mate + qtek 1.72 ROMs but still 1.01 here.
Sorry, my mistake , my bootloade is V1.14 with the Dangaard 1.72 ROM.
cheers
@Raphael
Are you sure you'are looking at the right place? Haven't heard yet of booloader newer than 1.06 yet. But that doesn't ofcourse mean that it doesn't exist.
Mark
hmm, it seems that someone is mixing up radio stack and bootloader. have never heard of bootloader newer than 1.06 but radio stack 1.10 1.14 and even 1.17 (in some german replacement devices with 1.72.01GER) is out so far.
greetings from black forrest
peter
Sorry, You're right, had a mix up:V.1.02
No w I start to be ashamed of this mix up.
Cheers
:lol:
Just did a soft reset on mine with ROM 1.72 and I can insure you that
Radio is 1.14
I don't know how to find the "bootloader version" ?
so long
there are two ways of finding bootloader version:
1. you hold power-, 4-way rocker switch and soft-reset and your device goes into bootloader mode (and by the way all of your data is lost, so backup your device before doing that)
2. browse around xda-developers forum and find a tool that is called safebootloader.exe or something like that. this file must be copied to your device. start it and it writes a file where informations about the bootloader is in. open that file with a hex-editor e.g. and you can see the version.
regards
peter

Crossbow in hermes

My friend just got the hermes running the crossbow os, would someone tell me how to dump the rom out? Need urgen reply cause he will leave hong kong tomorrow.
First try Buzz's rom dumper. It's available here
There are reports that it won't work which may be related to the Hermes microSD slot. I'd try the miniSD version of Buzz's pgm first.
There are various ways to dump the ROM from a live device, I don't know which one will be the most reliable or will be more helpful to reconstruct the ROM after the dump, so if possible dump the rom in all methods explained here:
1) itsutils pdocread, as explained in the WIKI:
http://wiki.xda-developers.com/index.php?pagename=Hermes_HowtoDumpRom
This is IMHO the most reliable method, first use 'pdocread -l' to list all partitions, then dump ALL them in "raw" files. Feel free to ask if you need help or are unsure in any of the steps.
2) As Sleuth255 suggested, you can also try grab_it! tool from buzz, but I don't know if it will work or not.
3) There is also mamaich's TestWM5.exe, which dumps files and modules to SD card, but I think the dump will not be useful for creating a valid imgfs after, anyway try this method too.
4) It will be also useful if you dump the bootloader on this device: Run gnuharet.exe on the device, then telnet to port 9999 and issue this command: 'pwf splfile 0x30000000 0x40000' in gnuharet.exe
This will dump the running SPL in a file called "splfile" in the folder where you run gnuharet from. It will probably be corrupted by wince usb host buffers, but anyway will be useful too.
Good luck and feel free to ask if you have problems
Suspense is killing me... did we get a dump?
Also please, put the Hermes in bootloader mode (side ok + power button + softreset with stylus) and tell us exactly the IPL and SPL version you see in the tri-color screen. Probably we can investigate how to dump rom parts from bootloader using 'rbmc' command in mtty.
tsuishui said:
My friend just got the hermes running the crossbow os, would someone tell me how to dump the rom out? Need urgen reply cause he will leave hong kong tomorrow.
Click to expand...
Click to collapse
Any progress? Im all tingles here, my wife thinks im crazy...lol cannot wait to get my hands on this one...(and i dont mean my wife)
This should be interesting if he actually gets it
It is as follows
HERM100
IPL-1.00
HERM100 MFG
SPL-1.02
Ok, i will wait a while and I will provide you the commands to dump the ROM from bootloader. Meanwhile download HHD Usb Monitor trial version, and install it.
pof said:
Ok, i will wait a while and I will provide you the commands to dump the ROM from bootloader. Meanwhile download HHD Usb Monitor trial version, and install it.
Click to expand...
Click to collapse
Any idea what the chances are to create a working rom out of this?
I am out of computer right now so i will try to dump the rom later today and my friend tells me that this device is come from microsoft. Also it is the rom from t-mobile.
great news today!
Now I really can't wait for this
http://msmobiles.com/news.php/5846.html
darkjedi said:
Now I really can't wait for this
http://msmobiles.com/news.php/5846.html
Click to expand...
Click to collapse
nice tease...guess i put it up for discussion in our Hermes meeting tomorrow..
Well lookey here! M$ also released a version that runs on the HTC Wizard. The Wizard was their preferred device at MEDC 2006.
I'm really wondering why they called it WM6.0 instead of SE or 5.5...
POF and other more intelligent people than me - if we do get this ROM I am more than happy to act as a guinea pig for this!! I have 2 days off work and a brand new Hermes to mess around with!
LOL I'm sure everyone will want to be a guinea pigs for this
darkjedi said:
I'm really wondering why they called it WM6.0 instead of SE or 5.5...
Click to expand...
Click to collapse
possibly marketing...
Getting the ROM dump is only the first (most important) part. Next the talented folks here at xda developers will need to convert it to a flashable image. The Hermes architecture presents unique challenges here. I'm sure having this dump on the FTP site will add even more incentive to this effort which will also result in our ability to cook our own ROMs....

BB Connect

Hi all,
Thus far has anyone managed to get any version of BB Connect running on WM6?
I have tried but with no joy
I also need help with this. The WM5 ROM had BB Connect pre-installed, but the WM6 one doesn't. Does anyone have the cab from the WM5 one?
ade0282 said:
Hi all,
Thus far has anyone managed to get any version of BB Connect running on WM6?
I have tried but with no joy
Click to expand...
Click to collapse
Yes. Tonight I took the time to get things sorted. I now have WM6 and BBC 2.1.2.54 running. (Still no luck with BBC4)
Steps that I have done:
- Extracted the WM6 NBH (duttys tool)
- Hex-Edited the windows.nb
Original HEX string is:
4D3EA0E3063083E3452FA0E30510A0E302
New Hex string is:
1D3EA0E3013083E3452FA0E30510A0E301
This resulted in os version 5.1.465 (like the original WM5 for Athena)
- Used the Athena_upgrade package to flash this modified windows.nb to my device.
One word of warning when using this flash method: Be sure to read out the proper handle for the area where the .nb will be stored.
If you want the whole wm6 on your device do the full upgrade with one of the provided WM6-ROMs before flashing the above modified .nb.
- Don't forget to change the AKU to .3.3.1
Thanks to all involved people who provided the tools, wm6 and whatever. You have my greatest respect!
Cheers
c0rnholio said:
Yes. Tonight I took the time to get things sorted. I now have WM6 and BBC 2.1.2.54 running. (Still no luck with BBC4)
Steps that I have done:
- Extracted the WM6 NBH (duttys tool)
- Hex-Edited the windows.nb
Original HEX string is:
4D3EA0E3063083E3452FA0E30510A0E302
New Hex string is:
1D3EA0E3013083E3452FA0E30510A0E301
This resulted in os version 5.1.465 (like the original WM5 for Athena)
- Used the Athena_upgrade package to flash this modified windows.nb to my device.
One word of warning when using this flash method: Be sure to read out the proper handle for the area where the .nb will be stored.
If you want the whole wm6 on your device do the full upgrade with one of the provided WM6-ROMs before flashing the above modified .nb.
- Don't forget to change the AKU to .3.3.1
Thanks to all involved people who provided the tools, wm6 and whatever. You have my greatest respect!
Cheers
Click to expand...
Click to collapse
Hi Cornholio: could you help me with more details on the process to charge into the pda this .nb file? I am not sure if needed to join in a full nbh all the diferent files with .nb after extract the rom or is needed only flash the os.nb
I tried unsucessfully the tools you mention and is not possible to charge the os. I think it is due my device is WM6 before..
beginner said:
Hi Cornholio: could you help me with more details on the process to charge into the pda this .nb file? I am not sure if needed to join in a full nbh all the diferent files with .nb after extract the rom or is needed only flash the os.nb
I tried unsucessfully the tools you mention and is not possible to charge the os. I think it is due my device is WM6 before..
Click to expand...
Click to collapse
Hi, you only need to flash the windows.nb file. It should also work if you already have WM6 on it. What has to be mentioned is that the itsutils in the Athena_Upgrade Package also did not work for me so I was unable to read out the handle and flash it, but I've downloaded the itsutils from here: http://nah6.com/~itsme/itsutilsbin-20070705.zip
and they worked without any problem.
c0rnholio said:
Hi, you only need to flash the windows.nb file. It should also work if you already have WM6 on it. What has to be mentioned is that the itsutils in the Athena_Upgrade Package also did not work for me so I was unable to read out the handle and flash it, but I've downloaded the itsutils from here: http://nah6.com/~itsme/itsutilsbin-20070705.zip
and they worked without any problem.
Click to expand...
Click to collapse
thanks a lot, you are great!!!
do you have some instructions on how to do it, please?
read and re-read and found it. Now working...
beginner said:
thanks a lot, you are great!!!
do you have some instructions on how to do it, please?
read and re-read and found it. Now working...
Click to expand...
Click to collapse
Glad to hear that you figured it out. Sorry for not replying, but I didn't had the time to write a step-by-step guide.
c0rnholio said:
Yes. Tonight I took the time to get things sorted. I now have WM6 and BBC 2.1.2.54 running. (Still no luck with BBC4)
Steps that I have done:
- Extracted the WM6 NBH (duttys tool)
- Hex-Edited the windows.nb
Original HEX string is:
4D3EA0E3063083E3452FA0E30510A0E302
New Hex string is:
1D3EA0E3013083E3452FA0E30510A0E301
This resulted in os version 5.1.465 (like the original WM5 for Athena)
- Used the Athena_upgrade package to flash this modified windows.nb to my device.
One word of warning when using this flash method: Be sure to read out the proper handle for the area where the .nb will be stored.
If you want the whole wm6 on your device do the full upgrade with one of the provided WM6-ROMs before flashing the above modified .nb.
- Don't forget to change the AKU to .3.3.1
Thanks to all involved people who provided the tools, wm6 and whatever. You have my greatest respect!
Cheers
Click to expand...
Click to collapse
i see that BB 4 works with Black, for 5.1.195. I tried some hacking for WM6 of Athena but BB 4 doesn't connect. I think it checks something more that the operative version.
beginner said:
i see that BB 4 works with Black, for 5.1.195. I tried some hacking for WM6 of Athena but BB 4 doesn't connect. I think it checks something more that the operative version.
Click to expand...
Click to collapse
BBC 4.* check the ModelID of the device also... hence wont work on an athena.... you have to wait for a version 4.0 for the Athena sorry...
walshieau said:
BBC 4.* check the ModelID of the device also... hence wont work on an athena.... you have to wait for a version 4.0 for the Athena sorry...
Click to expand...
Click to collapse
do you know where it checks it? i have the idea of replace the header of the rom file, that says what device is it, but non sure if i coul brick the device.

Beginners Guide to Unlocking/Upgrading the ROM

So you want to try some ROM other than the shipped ROM for your Athena!
What Do you need to know?
Backup
You should also know that doing this will usually wipe all the info off your phone(except the microdrive and SD card)
So it is important that you learn to backup any info that you want to keep.
I suggest using pimbackup and I usually back up MyDocuments by syncing with your computer or even copying it to your SD card.
I do this as a routine everytime I fiddle with my ROM so I can return to the previous state.
I also use Sprite Backup as well.
Remove Sim/Sd card
Next , make sure you remove your SD card and simcard before proceeding to apply Olipros unlocker
Unlock
Well you have to unlock your ppc to accept a new ROM.
I haven't done this for a while , but fortunately the process has been made easy by Olipro in this thread
http://forum.xda-developers.com/showthread.php?t=315831
and in german in this thread
http://forum.xda-developers.com/showthread.php?t=378216
Check Bootloader Screen
Throughout this forum you will be referred to your SPL.
This is the Secondary Program Language and on your unadulterated ppc it will be 1.1
Olipro's original unlocker upgraded this to 1.1x but the unlocker above will change it to SPL 1.2
You can see if this has already been done by putting your phone into the Bootloader screen.
This is done by holding the camera button completely in and then pressing the reset button.
You will now see a red/green/blue and white striped screen telling you the device id and SPL version.
If you see SPL 1.2 , you are good to go to load any SPL 1.2 Rom.
Activsync/Windows mobile device centre.
You need this program to apply updates to your ROM
There used to be a problem with earlier versions of these programs not recognising WM6 ROMS.
This problem is easily solved by updating these programs
Upgrading Radio
No there is no FM radio on the Athena, this refers to the operating System radio that operates the phone/wifi/gps etc
This is important to know as AP4 needs at least radio 1.50 (and maybe WM6.1roms)
Upgrading the radio proceeds the same way as a rom upgrade
version1.58 is here http://forum.xda-developers.com/showthread.php?t=409271
version1.57 is here http://forum.xda-developers.com/showthread.php?t=372904
Where to find a ROM
Fortunately Sergiopi has collected and sorted them here
http://forum.xda-developers.com/showthread.php?t=397518
Walk me through the Process
1.backup data
2.remove sim and SD card,apply hard reset and wait till full initialization complete before connecting to pc.
3.establish Activsync connection
4.ensure no background program running, antivirus, firewall and etc. before executing flash command.
5 start the unlocker and follow the instructions.
6.reboot phone and make sure you still have activesync
7.**Update the ROM to an SPL appropriate rom according to what appears on your bootloader screen**
following the above protocol
Great!
Now you should have a new ROM to play with!
And play with it you should !
But I want to try an SPL3.5 ROM!
OK if you got this far You should be able to do this.
**First step is to install AP4**
At the moment there is only 1 foolproof way to do this and this is to use the Athena Updater
But first read the upgrade Guide Please Here http://www.htc-hackers.com/uploads/AP4_How_To_1.8.pdf
It is very detailed and I recommend following it exactly !!
This is the link to the athena Updater
http://forum.xda-developers.com/showthread.php?t=387409
Now I want to go back to SPL 1.2
Ok. this is possible
see here http://forum.xda-developers.com/showthread.php?t=405604
Need to know more or Stuffed the Flash?
Don't worry , nearly everyone here has made a mistake but been able to recover.
Read the wiki and/ or search the forum
If you have any suggestions to change What I have written ,post a reply.
Advanced:SD Card Flashing
Rather than using Activesync/WMDC it is possible to flash using the SD Card
from the athena Wiki (a good source of info)
"Rename the .NBH file to ATHEIMG.nbh and copy it to your miniSD card. Press camera+soft reset to bootloader and wait for reading ATHEIMG.nbh from SD. Remember, the miniSD card must be formatted with a FAT32 filesystem before copying the file ATHEIMG.nbh to your miniSD. After finished, do a soft reset."
this doesn't work with SDHC cards .
reserved 2
Thank you very much,
Because the knowledge in this community is so high, sometimes pleople like me are afraid of writing some type of questions.
This way it will be easy.
"Sticky" please.
fantastic, a thread like this should be made part of the sticky topics!
cheers
Beautiful guide
Yes, is special for a noobs like me and others nice guide thanks.
bump
may help stop a few questions
thanks 1000000 times
now i won't be afraid of upgrading my athena
This really should be made a sticky.
I know when I first visited this forum, it was overwhelming. So many bits of pieces of info everywhere. Very hard for a new person to come in and make sense of it all.
Great guide lakeman.
Unlock Advantage x7501
Hey. I bought an unlock advantage X7501 windows 6.0 professional to HTC company last year. I can not watch videos on internet and you tube. What should I do? Please help me. Thank you
Maencaru said:
Hey. I bought an unlock advantage X7501 windows 6.0 professional to HTC company last year. I can not watch videos on internet and you tube. What should I do? Please help me. Thank you
Click to expand...
Click to collapse
you need to learn a few skills like reading the wiki and then doing a search of the forum.
also this question has nothing to do with the title of this thread.
The problem you talk about is not confined to the X7501 and i refer you to a sticky in this thread http://forum.xda-developers.com/showthread.php?t=387986
At the top of the forum is a new section called question and answers and I suggest you look there as well
I had unlocked my device and upgraded radio version to 1.58. Different Roms tested , last was Michy 5.1.
For variuos reason I had to reinstall the Original HTC Rom and again everything was working succefully.
Now I would like to reinstall Michy Rom 6.1 and once I enter the bootloader the screen is showing:
ATHENE 100 IPL-v1.00 ( standard)
as well as one line below
ATHENE 100-SPL-v1.20 Olipro
In order to avoid to brick my device my question is:
I can flash the Michy Rom straight or I still have to repeat the unlock procedure since the beginning again?
Thanks and regards
chevyc5ls1
chevyc5ls1 said:
Now I would like to reinstall Michy Rom 6.1 and once I enter the bootloader the screen is showing:
ATHENE 100 IPL-v1.00 ( standard)
as well as one line below
ATHENE 100-SPL-v1.20 Olipro
Click to expand...
Click to collapse
You can only flash SPL 1.2 ROMs and last time I looked Michy 6.1 was only SPL3.5.
You would need to upgrade to AP4 first as outlined in my first post
lakeman said:
You can only flash SPL 1.2 ROMs and last time I looked Michy 6.1 was only SPL3.5.
You would need to upgrade to AP4 first as outlined in my first post
Click to expand...
Click to collapse
Indeed for the time being Michy 6.1 is for Spl 3.5.
Thanks a lot for Your support
ciao
chevyc5ls1
lakeman said:
Rather than using Activesync/WMDC it is possible to flash using the SD Card
from the athena Wiki (a good source of info)
"Rename the .NBH file to ATHEIMG.nbh and copy it to your miniSD card. Press camera+soft reset to bootloader and wait for reading ATHEIMG.nbh from SD. Remember, the miniSD card must be formatted with a FAT32 filesystem before copying the file ATHEIMG.nbh to your miniSD. After finished, do a soft reset."
this doesn't work with SDHC cards .
Click to expand...
Click to collapse
Can you do the same thing from the microdrive?
kramerica2 said:
Can you do the same thing from the microdrive?
Click to expand...
Click to collapse
not that I am aware of
update rom and radio
Can someone help me? I have updated my dell axim rom many times but in the case of athena (u1000) i am afraid to do it because it is also a phone. I am not sure whether the radio 1.58 is applicable world wide mobile phone network or is it just in the united states. I live in Malaysia and we have several mobile phone network providers like digi, celcom and maxis.
Also should the radio be updated first or the rom first? Thanks
cphilip said:
Can someone help me? I have updated my dell axim rom many times but in the case of athena (u1000) i am afraid to do it because it is also a phone. I am not sure whether the radio 1.58 is applicable world wide mobile phone network or is it just in the united states. I live in Malaysia and we have several mobile phone network providers like digi, celcom and maxis.
Also should the radio be updated first or the rom first? Thanks
Click to expand...
Click to collapse
Radio 1.58 works everywhere as far as I know and is not carrier specific.
I could not get mms to work.
You need to upgrade to radio 1.5 at least to load AP4 and I think people had troubles if they used an earlier radio with WM6.1 roms.
So I guess it would be best to upgrade the radio first.
Thanks
Thanks lakeman,
Thanks for your clear clarifications about the radio updates and the AP4 Roms.
i am beginning to feel confident again about updating my u1000. I have read so much about michy's rom and a few others. The official rom in my device is stable but might be a bit slow if i were to compare to my axim x51 using the latest L11 rom from Lenny.
The joy of having responsive roms made me reluctant to sell of my dell axim even though I am using my u1000 most of the time now. I wonder if anyone had sold off their previous axim after using u1000 (athena x7500) and regretted.
But if i must use my u1000 which has features that no other ppc has namely the large screen, i would like to have better roms than the official roms.
Thanks to all here who have contributed so much to improve the athena!
lakeman
your instruction seems the most easy to follow (at least for me)
So i am itching to try upgrading my dopod u1000 here in malaysia.
So if i just want to upgrade the radio 1.57/58
I have to
1. do the unlocking using olipro (3 steps)
2. remove sd card and sim
3. connect to pc using activesync
4. install the radio and
5. hard reset (will be done automatically)
CORRECT?
If i want to upgrade to a say michy rom
1. do the unlocking (3 steps)
2. remove sd and sim
3. connect to my notebook (activesync)
4. install radio
5. hard reset
6. connect to notebook (activesync)
7. click on the say michy new rom installer on notebook
8. follow til the end
9. hard reset (automatically will be done)
10. NEW UPGRADED ROM!
Am i correct?
Thanks!!!
(Any recommendations regarding ROMS for a start if a newbie like me wants a the fast u1000 but as plain as possible so that i can choose what to install later?)

Categories

Resources