Develop Bugs

bootloader 2.01??(1.40??) and stuck

Hi friends.
I bought O2 Xda/Exec and now it stuck on Splash Screen (O2 bubble?).
bootloader is still alive and baking ROM look fine but didn't work.
first, this unit didn't work any before AKU2 ROM.1.3x is OK. 1.13x s NG.
Does anyone have Universal like me? HW ver 2.01
here is MTTY logs
USB>info 7
HTC Integrated Re-Flash Utility for bootloader Version : 1.40j, UNIVERSAL HW Version : 2.01
Built at: Mar 30 2006 15:58:38
Copyright (c) 1998-2005 High Tech Computer Corporation
Turbo=312, Run=208
Memory Frequency = 208 MHz
SDRAM Frequency = 104 MHz
Board ID is: 5
USB>task 28
DOCInfoTableinitHW+
Binary0 Size: 0x100000
FAT0 Size: 0x4000000
FAT1 Size: 0xA00000
FAT2 Size: 0x2840000
All Size: 0x7340000
FAT0_ADDR=0x100000,FAT1_ADDR=0x4100000,FAT2_ADDR=0x4B00000

g0dspeed said:
Hi friends.
I bought O2 Xda/Exec and now it stuck on Splash Screen (O2 bubble?).
bootloader is still alive and baking ROM look fine but didn't work.
first, this unit didn't work any before AKU2 ROM.1.3x is OK. 1.13x s NG.
Does anyone have Universal like me? HW ver 2.01
here is MTTY logs
Click to expand...
Click to collapse
I have bootloader 2.01 and chs WM5 on my Xda Exec which was bought last month in China.
I tried triple to upgade the ROM using O2 Exec ROM version 1.13.82 WWE found on this site, but failed.
I am using 1.30.108 CHT, 1.14.10, 1.30.224 CHS which works fine.

g0dspeed said:
Hi friends.
I bought O2 Xda/Exec and now it stuck on Splash Screen (O2 bubble?).
bootloader is still alive and baking ROM look fine but didn't work.
first, this unit didn't work any before AKU2 ROM.1.3x is OK. 1.13x s NG.
Does anyone have Universal like me? HW ver 2.01
here is MTTY logs
USB>info 7
HTC Integrated Re-Flash Utility for bootloader Version : 1.40j, UNIVERSAL HW Version : 2.01
Built at: Mar 30 2006 15:58:38
Copyright (c) 1998-2005 High Tech Computer Corporation
Turbo=312, Run=208
Memory Frequency = 208 MHz
SDRAM Frequency = 104 MHz
Board ID is: 5
USB>task 28
DOCInfoTableinitHW+
Binary0 Size: 0x100000
FAT0 Size: 0x4000000
FAT1 Size: 0xA00000
FAT2 Size: 0x2840000
All Size: 0x7340000
FAT0_ADDR=0x100000,FAT1_ADDR=0x4100000,FAT2_ADDR=0x4B00000
Click to expand...
Click to collapse
I had this exact same problem after SUCCESSFULLY upgrading all ROMs. A hard reset (that's the LeftMF_Key+RightMF_Key+Power+Reset, at the bootloader - press the 0 key) fixed this problem for me.

g0dspeed said:
Does anyone have Universal like me? HW ver 2.01
Click to expand...
Click to collapse
I assume you're referring to the 2.01 at the bottom of the Bootloader screen. If so, that indicates that you have a G4 Exec (the most recent model). That is compatible with all the ROMS discussed on this part of the site.
g0dspeed said:
first, this unit didn't work any before AKU2 ROM.1.3x is OK. 1.13x s NG.
Click to expand...
Click to collapse
I'm not sure exactly what you mean by this. I agree that you should try hard-resetting and then select "0" when offered the choice at the white screen. If that doesn't work, let us know in more detail what you did before getting stuck in this position and what worked / didn't work.

Loox n5x0 series rom update

heh, i`ve researched on the loox n5x0 series (htc maria?) rom format. now we can create custom roms.
Loox n5x0 OS_xxxU.nbf header format
total 42 bytes header, the rest is not crypted os rom image (what we usually call nb0 or n_d)
4 bytes - model name (N500, N520 or N560) + 11 bytes empty (filled with 0x00) +9 bytes version (e.g. 1.22.0001) + 1 byte 0x20 (space) +3 bytes language (e.g. ENG, ITA, GER) + 2 bytes empty (0x0) +4 bytes - reversed crc32 checksum (if we have, for example, 1163FCED, then we write ED FC 63 11) + 4 bytes - size of decrypted part (reversed somehow? we have 2100000 and write 00001002) + 4 bytes - rom base flash address (seems it it 80400000, we type 00 00 04 80, don`t play with it)
all this is true for OS_yyyU.nbf ( yyy means rom version), bootloader nbf is coded otherwise, it is usually named BL_xxx_G3.nbf or bl_xxx_G4.nbf. xxx - bl version. I suppose you delete file bl_xxx_G4.nbf or bl_xxx_G3.nbf. new pda`s come with g4 flash, it will be killed with g3 update. and, anyhow, bootloader update is always dangerous and not recommended.
wait a bit - in some days i`ll post a tutorial how to extract os rom image from n500/n520 and probably n560 pda.

Any progress on this? I have a N560 and am very interested in your tutorial. Thanks.

Any news in the N560 area??
I am eager to update the software of my N560... I would like to try the new Windows mobile 6. It's pretty annoying that this really good device cannot be upgraded somehow..
Well, hope to hear something soon..
PS: By the way, you guys are great doing all this stuff

Is loox 5x0 == htc maria? Any prooves?

it's htc dresden)) i'll post aku 3.5.2 for c550/n560 this week

Man that would be awsome!!!
Nice to hear this one!!!
Waiting for the goodie
Thank you man!!

wm6 upgrade
Rafe533 said:
Any progress on this? I have a N560 and am very interested in your tutorial. Thanks.
Click to expand...
Click to collapse
I would also be very interested in upgrading my N560 to wm6.
I thank you in advance.
Shim

shimrob said:
I would also be very interested in upgrading my N560 to wm6.
I thank you in advance.
Shim
Click to expand...
Click to collapse
No WM6 yet, but
http://4pda.ru/forum/attach/805977/n560.Alex_DFR_.AKU.3.5.2.rar - here is the rom with aku 3.5.2 for n560
For Loox C550
http://4pda.ru/forum/attach/808633/PocketLOOXC550FlashTool.7z - here is the flasher for c550, download it, download aku3.5.2 for n560, overwrite the files from the n560 update and open OS_213u.nbf with winhex and change n560 to c550
If you have german/french/italian/spanish pda but want to use this update, edit the nbf with winhex and change ENG to FRA/GER/ITA/SPA
Be sure to remove the password (fsc secure lock) before flashing

getting my n560 ready to flashing... go-go-go!

Does not work!!!
I have a spanish N560 pda. I wanted to upgrade its rom.
I did everything as indicated:
- open pda and put it in the cradle
- connect cradle to the power and the usb to my WinXP laptop
- in my XP machine activesync (4.5 spanish version) connects and recognizes my pda
- check there is no password protection in the pda (there was none before)
- unpack n560.Alex_DFR_.AKU.3.5.2.rar and open with WinHex OS_213U.nbf; change ENG to SPA; save file
- execute PocketLOOX5xxFlashTool; in the end I get this error:
"The language in this Flash Image update () differs from that on your device (SPANISH)!"
Well, I did again and again and again... same error...
Any suggestions???
PS: I would like to put its new rom in english, if it's possible!
Thank you

Hi sp3dev,
your update is quite intersting but I have two questions before I want to flash:
1. is the ROM affected by flashing your image, if flashing fails, can the N560 hard reset to original state?
2. Is there a tool which can fetch a complete image from N560 (with ROM)?
Can you give us a short info how you cook the image?
Where do you get the HW depended drivers (e.g WLAN, display..)?
Do you have any links? I have looked a long time
to find any info about upgrade the N560 or cooking Loox images.
Thanks

SPAschreiben not so, but ESN. then is OK ONE

I have with these Romes update. All OK ONE

Stucked
Hi sp3dev and everyone,
I did the upgrade and it went fine, the only thing was that the keyboard was English, I thought there were all in the ROM, and I wanted to get back to the first ROM, so and here comes my problem, I executed
pdocwrite nk.nb0 0 0x2300000
The result of this is that it get stucked at the very first screen, Is there any way to get back? How could I upload a ROM to the N560 in this case?
Thanx

Hi,
so how it looks with WM6 ROM. It will be great to have WM6 on my N560

Smarja said:
Hi,
so how it looks with WM6 ROM. It will be great to have WM6 on my N560
Click to expand...
Click to collapse
Oh, i don`t know. we have xip with all wm6 modules but wm6 doesn`t boot yet. When we fix, and if we do, i`ll inform everyone

I did the upgrade yesterday eve, but i am missing the remote desktop client..
can't seem to find any link.. mtssc or any.. i looked in the windows folder but couldn't find it.
Anyone a hint?

oNNoZeLe said:
I did the upgrade yesterday eve, but i am missing the remote desktop client..
can't seem to find any link.. mtssc or any.. i looked in the windows folder but couldn't find it.
Anyone a hint?
Click to expand...
Click to collapse
It's not there due to a bug. Likewise the transcriber does not work and hangs the system.
I suggest waiting until they fix it and upgrade then, if it is vital for you. I will wait for two reasons: it is probably buggy yet (only two known bugs now though), and I am loath to re-install everything from scratch for the next couple of weeks
Besides, people experiment there with pool size (with some trade-off in RAM) which may yield an even faster machine.
Also if you upgrade, you must not use an old (all-)system backup. Just re-install everything single piece of software you use. Note that some software may lose its registration since you will have a *different* PPC with new (and unofficial) ROM.
... and "if it isn't broken, don't fix it" remember?

AKU 3.5.2
Hi sp3dev,
I thought that in AKU 3.5.2 WPA2 was supported. If I'm right this is supported since AKU 3.5. After upgrade I noticed it wasn't in this release. Is it a mistake? or I'm really wrong.

and "if it isn't broken, don't fix it" remember?
Click to expand...
Click to collapse
True, but i can't rembemer not installing any MS beta ;-)
And if someone posts a wm6 rom here, i won't be the first to try but might be second or third
Maybe my intention was to notify but wrote my text wrong..
i do like the rom..

white screen after upgrade

I tried to upgrade to new wm6 italian roms but after upgrade finishes the p3600 doesn't make auto boot, pressing reset the device start booting and show the first scree but after the screen becomes white and stop going on.
The only rom working is this from lwsw wm6.
All other roms (mun, italians translated) after the upgrade the system doesn't finish first boot and remains white.
I can enter in bootloader pressing on+camera+reset and install italian wm5 gps enabled rom or lwsw wm6 english rom, but no one of the others.
I tried also sspl.trin and hard spl but without success.
What can do to let the upgrade finalize with italian or mun's wm6 roms?
Thanks

no one that happened the same and solved it?

+1 help please

dreambox said:
+1 help please
Click to expand...
Click to collapse
I think you have to use mtty.exe to unlock the device!!!
first have to flash Hardspl, rebbot, then:
disable activesync, enter in bootloader and run mtty from pc, select usb port and flag yes on "local echo"
then press ok, a terminal white window appear
press "enter"
and appears "cmd>" then write:
info 2
then you write task 2a
if there are some memory Bad block, they will be adhusted!!!
reenter in bootloader, reflash with original WM5 italian and try if the old "original" OS works!!
last luigi.ing release of italian rom causes same problem to my device, after theese operations it retunded to work!!!
bye!

same problem here, after last "ing" upgrade... now trying to upgrade with udk.. my PS trin is supercid
UPDATE: Udk seems to work fine! It bringed to life my trin!!

ervius said:
I think you have to use mtty.exe to unlock the device!!!
first have to flash Hardspl, rebbot, then:
disable activesync, enter in bootloader and run mtty from pc, select usb port and flag yes on "local echo"
then press ok, a terminal white window appear
press "enter"
and appears "cmd>" then write:
info 2
then you write task 2a
if there are some memory Bad block, they will be adhusted!!!
reenter in bootloader, reflash with original WM5 italian and try if the old "original" OS works!!
last luigi.ing release of italian rom causes same problem to my device, after theese operations it retunded to work!!!
bye!
Click to expand...
Click to collapse
is there something to do after launching task 2a ? because i still have the white screen problem after
Edit : here is what i have on my screen
Cmd>task 2a
Check block : 75 - Bad
Check block : 76 - Bad
Check block : 915 - Bad
Click to expand...
Click to collapse
what command must i launch ?

there is a way to flash roms with mtty this solves bad dlocks usage, but i don't find how to do it anymore, someone ca give me instructions on how to use mtty for flashing my trinity?
Thanks

Spanish problem
+1 help
Con la versión 2.3 ES me pasa lo mismo.
La única que funciona bien es "LVSW_Trinity_WM6_v2.0.1.1"

+1
"LVSW_Trinity_WM6_v2.0.1.1"

Problem With Flashing
Also to me making all the procedure to the fine ones they give an error to me Cmd>task 2A Check block: 329 - Working Bad
and the only one rom is wm6 the 2.0.1.1

Cmd>info 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Block 0x177(375) is BAD block !!!
Block 0x2D8(728) is BAD block !!!
Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1700
Partition[2], type=0x25, start=0x3000, total=0x19D00
Partition[3], type=0x4, start=0x1CD00, total=0x1DB00
CE Total Length(with sector info) = 0x3A86800
CE CheckSum Length(without sector info) = 0x39A0000

anybody can help us for that?

I'ver read somewhere that flashing roms with mtty solves the problem. But flashing roms with mtty it's not easy because if i remember well, you must decostruct the rom and flash only one file of it.
If someone can tell us how to extract the right file and flash it with mtty we could install every rom.....

The problem comes from Olipro's Hard-SPL in most cases. It ignores bad blocks which can result in the mentioned problems. He fixed it for Hermes...

It seems that I have found a way to revolve the problem, it is not a solution but it seems to work.
The blocks marked "Bad" by mtty such remain bad, but the new rom run on my PDA from 12 hours without problems.
The passages that I have executed are:
- Hard Reset
- Hard-SPL (standard ActiveSync USB connection)
- Boot of PDA in bootloader mode and deactivation of ActiveSync USB connection
- Flash with rom udK 2.3 Full Edition (italian)
- SAME OLD WHITE SCREEN PROBLEM!
- Again Hard Reset
- Again Hard-SPL (standard ActiveSync USB connection)
- Boot of PDA in bootloader mode and deactivation of ActiveSync USB connection
- Flash with rom udK 2.3 Lite Edition (italian)
- Right boot screen whit background ad so on...
It seems that if the rom is small enough to ignore the bad blocks it can work correctly.
In waiting for a definitive solution of the corrupted blocks I hope that my experience can help you.

ZakMcRofl said:
The problem comes from Olipro's Hard-SPL in most cases. It ignores bad blocks which can result in the mentioned problems. He fixed it for Hermes...
Click to expand...
Click to collapse
so if i am flashing my pda with the s-SPL provided witht the rom it should work ?

oufledingue said:
so if i am flashing my pda with the s-SPL provided witht the rom it should work ?
Click to expand...
Click to collapse
i jsut found the anser to your question,don't use the hard spl 1.20!!!!!use the hard spl 1.41.00.11.good luck and tell me if it works now.

unexpected said:
use the hard spl 1.41.00.11.good luck and tell me if it works now.
Click to expand...
Click to collapse
so would you pls tell me where to get that for Trinity?

use this guys then tell me if it works.
flash the trinity with this then flash with the rom you want.
http://www.file-upload.net/download-257820/Trinity-Radio-ROM-1.41.00.11-by-ZakMcRofl.rar.html

unexpected said:
use this guys then tell me if it works.
flash the trinity with this then flash with the rom you want.
http://www.file-upload.net/download-257820/Trinity-Radio-ROM-1.41.00.11-by-ZakMcRofl.rar.html
Click to expand...
Click to collapse
can't find the link to d/l
how about attach to here?

Original "keyboard"

Hello!
I've installed the O2 Rom. The software is great! But I really likes the original input methods of Windows Mobile.
There is any way to use the old block recognizer with this ROM?
Thanks!

Yeh, here by Meschle:
http://forum.xda-developers.com/showpost.php?p=1462112&postcount=2

Anything wrong with the datas of my Hermes?

The device is SoftBank x01ht.I ran the mtty.exe and after cmd>info 8, there are 8 or 9 bad blocks, then I input task 2a and have them repaired. But after infor 8, I get the datas below:
Cmd>info 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1900
Partition[2], type=0x25, start=0x3200, total=0x22E00
Partition[3], type=0x4, start=0x26000, total=0x19000
CE Total Length(with sector info) = 0x4D30000
CE CheckSum Length(without sector info) = 0x4C00000
The total value of Partition[2] and [3] are different from the ones I saw on this forum, and the value of CE Total Length and CE CheckSum are different either. So anything wrong with the datas of my device?
As far as I remember, starting with the ROM TAI's 21109 3G lite ROM, my Hermes kept hardresetting or hunging whatever cooked ROM I flashed (everytime I flashed the official O2 WM6 ROM first and then cooked ROMs, and some of the ROM's I flashed before TAI's rom ran very well on my hermes), then I tried to softreset it if hunging, but resulted in hunging at the flash screen and I have to got it hardreset by hand. But everything goes well I install the official ROM's ( I tried O2 official WM6 ROM and HTC official green WM6 ROM). Anyone know what is happening? Thanks!

pls any words, bros?

seasky3246 said:
The device is SoftBank x01ht.I ran the mtty.exe and after cmd>info 8, there are 8 or 9 bad blocks, then I input task 2a and have them repaired. But after infor 8, I get the datas below:
Cmd>info 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1900
Partition[2], type=0x25, start=0x3200, total=0x22E00
Partition[3], type=0x4, start=0x26000, total=0x19000
CE Total Length(with sector info) = 0x4D30000
CE CheckSum Length(without sector info) = 0x4C00000
The total value of Partition[2] and [3] are different from the ones I saw on this forum, and the value of CE Total Length and CE CheckSum are different either. So anything wrong with the datas of my device?
As far as I remember, starting with the ROM TAI's 21109 3G lite ROM, my Hermes kept hardresetting or hunging whatever cooked ROM I flashed (everytime I flashed the official O2 WM6 ROM first and then cooked ROMs, and some of the ROM's I flashed before TAI's rom ran very well on my hermes), then I tried to softreset it if hunging, but resulted in hunging at the flash screen and I have to got it hardreset by hand. But everything goes well I install the official ROM's ( I tried O2 official WM6 ROM and HTC official green WM6 ROM). Anyone know what is happening? Thanks!
Click to expand...
Click to collapse
My theory is the cooked rom has the structure from XIP something changed and time to time it will be bad and hang up. You have to install only one official rom (don't change different official rom because it has may be not the same structure). For me, i used AT&T official rom and install only one time before flashed the cooked rom. And if i want flash another cooked rom, i don't need first flash official and after cooked rom. I flashed cooked rom many time again until i get hardreset or something wrong.
The data how you saw was not wrong, it changed from xip structure to have more memorie and storages. Many chefs has a different theory to get maximum memorie without any wrong with xip structure but if the structures not clean and you have many problems with hardreset.

TAI_Sw said:
My theory is the cooked rom has the structure from XIP something changed and time to time it will be bad and hang up. You have to install only one official rom (don't change different official rom because it has may be not the same structure). For me, i used AT&T official rom and install only one time before flashed the cooked rom. And if i want flash another cooked rom, i don't need first flash official and after cooked rom. I flashed cooked rom many time again until i get hardreset or something wrong.
The data how you saw was not wrong, it changed from xip structure to have more memorie and storages. Many chefs has a different theory to get maximum memorie without any wrong with xip structure but if the structures not clean and you have many problems with hardreset.
Click to expand...
Click to collapse
Thanks for your words TAI. So is there anything I can do to get things better? I'm using the official AT&T ROM today. I really want to try the cooked ROM, but hanging up and hardreset scared me....

seasky3246 said:
Thanks for your words TAI. So is there anything I can do to get things better? I'm using the official AT&T ROM today. I really want to try the cooked ROM, but hanging up and hardreset scared me....
Click to expand...
Click to collapse
Just be sure to flash oem ATT rom and it will restore the xip structure as tai_SW mentioned and then the new rom will function properly.

joshkoss said:
Just be sure to flash oem ATT rom and it will restore the xip structure as tai_SW mentioned and then the new rom will function properly.
Click to expand...
Click to collapse
Hi josh, I used your color 3G M2D ROM and it's really good before my hermes kept hung up . I'm using the official ATT ROM. So when I flash a new ROM now, it will function preperly? Thanks~

seasky3246 said:
Hi josh, I used your color 3G M2D ROM and it's really good before my hermes kept hung up . I'm using the official ATT ROM. So when I flash a new ROM now, it will function preperly? Thanks~
Click to expand...
Click to collapse
Correct!! Always flash the att OEM rom before flashing a new build rom, for better stability.. it formats the xip structure very well.. and thanks!

seasky3246 said:
Thanks for your words TAI. So is there anything I can do to get things better? I'm using the official AT&T ROM today. I really want to try the cooked ROM, but hanging up and hardreset scared me....
Click to expand...
Click to collapse
You can flash any cooked roms again. Don't scared it so much. But it must be surely that you have also hardSPL installed.

Thanks, josh and TAI. So I'm on it to flash a cooked ROM again. And surely I have the hardSPL installed. Thank you again