Database Users

Dead pc, looking for M-SYS DiskOnChip G3 flasher

I have Typhoon MyGuide 5500xl pocket pc. Which became a brick during the normal (through CF) flashing. It doesn't react into any button combination and any rom putted into CF.
Decided to flash by connecting with jtag. Made wiggler cable, connected. Processor was identified:
jtag> detect
IR length: 5
Chain length: 1
Device Id: 01101001001001100100000000010011
Manufacturer: Intel
Part: PXA250
Stepping: PXA255A0
Filename: /usr/local/share/jtag/intel/pxa250/pxa250c0
But flash not:
jtag> detectflash
jedec_detect: mid 4, did ea00
Flash not found!
Because my flash is M-SYS DiskOnChip G3 and it is not yet supported by jtag .
What can I do more?
Is it dificult to program jtag to support this flash?
[according http://www.m-sys.com/NR/rdonlyres/8B28C9C6-275D-44F4-9D15-4F6E54EAD0F7/0/Boot_Software_Dev_Kit_6x_Rev11.pdf|Boot_Software_Dev_Kit_6.x_Rev1.1.pdf]
Or maybe you know or have another flasher which supports this flash?
Thanks for any help

Possible this you will help -but I have not found this program VTI-Host.
http://www.m-sys.com/NR/rdonlyres/2FCFAE9F-7604-4C5E-B3CF-ED4B8926EED0/0/Programming_DOC_With_VTIHost.pdf|Programming_DOC_With_VTIHost.pdf
I also search for this program for OMAP .

The problem is that I have dead Typhoon MyGuide 5500 xl pocket pc, which is based on Asus A620.
There is a JTAG DoC (Disk On Chip) support. http://www.handhelds.org/moin/moin.cgi/MyPal620JTAG
Flashing of dead pocket PC should be easy. BUT.
I can connect to it using jtag 0.5.1 using WIGGLER or DLC5 cables. Now I have only DLC5. I can successfully detect flash but when I am trying to flash it (referencing to the link above ) then problems starts. Looks like system works randomly, or something interferes signal. My DLC5 cable is as short as possible, max 12cm. There are some checkings of signals to start flashing:
if ((c1 & DOC_TOGGLE_BIT) == (c2 & DOC_TOGGLE_BIT)) {printf("Probe DoCM+ failed !\n"); return 0;}
if ((c2 & DOC_TOGGLE_BIT) == (c3 & DOC_TOGGLE_BIT)) {printf("Probe DoCM+ failed !\n"); return 0;}
if ((c1 & DOC_TOGGLE_BIT) != (c3 & DOC_TOGGLE_BIT)) {printf("Probe DoCM+ failed !\n"); return 0;}
So most of the time I cannot pass these checking. Then I start to move connected pocket and suddenly it passes them. Then flashing starts. But again it loops and reaches max iteration count, because of not getting some signal:
while (((DoC_reg_read(DoC_Mplus_FlashControl) & CDSN_CTRL_FR_B_MASK) != CDSN_CTRL_FR_B_MASK) &&
(it++ < max_iter));
So again I am stuck. I was testing on Windows (cygwin) platform. Found a fellow who tried it on Linux and had exactly the same results. Means no difference.
What could you suggest me more?
Thank you.

Hi there,
any progress with mDOC G3 implementation?
I just put a link to this thread in here:
http://forum.xda-developers.com/showthread.php?t=353072
We're trying to solve the same issue for the HTC universal hardware .
At least after some experiments on the platform we decided, it would be most useful to modify an existing JTAG software tool to support mDOC G3 devices.
If there are any news, that are worth to mention, please join our discussion if you like!
By the way:
Code:
if ((c1 & DOC_TOGGLE_BIT) == (c2 & DOC_TOGGLE_BIT)) {printf("Probe DoCM+ failed !\n"); return 0;}
if ((c2 & DOC_TOGGLE_BIT) == (c3 & DOC_TOGGLE_BIT)) {printf("Probe DoCM+ failed !\n"); return 0;}
if ((c1 & DOC_TOGGLE_BIT) != (c3 & DOC_TOGGLE_BIT)) {printf("Probe DoCM+ failed !\n"); return 0;}
This routine is not useable on G3 because of different register definitions. There seems to be no toggle bit like on mDOC M+...
That's why it fails. We have to use another syntax for mDOC G3 (at least other defines!!!).
Best regards,
scholbert

Get 300 Error, goldcard doesn't help?

After trying to upgrade firmware on Herald got brick(?)
When i try to upgrade it by Rom Update Utility - always get 300 error.
I've tried to make Goldcard (tried 3 different sd-cards) with QMAT and typhoonnbfdecode perl script, goldcard always creates succesfully, but
f*** Searching for SD card and moment later tri-color then...
Before that everything was o.k...
When i turn it on there is green display...
Any ideas guys? any suggestions??? what mistakes could i made?

mtty says
SDInit---
SDInit OK
Unlimited time!
GetDeviceCID: Error - InitDecoder
g_cKeyCardSecurityLevel = 0
....
Cmd>getdevinfo
GetDeviceCID: Error - InitDecoder

Now what?

So, now I cant get anything working in my P4350 except the bootloader mode.
The way I got here:
Installed many roms, trying to find the best for me. After some time, even the most stable rom was not stable, all of them crashed, freezed, rebooted after about 1 day usage. (With and without SD card, and no apps installed).
So I decided to remove hardspl and do the whole thing again. I downloaded Aserg-Remove-Hard-Spl pack, and run it. After the second step the phone was not completly blank, I saw the console staying at the "praying ..." text (without backlight), and the phone didnt responded for any buttons or touch. So here came the third step, the RUU, but it gave me error 260, that it cant find my device. (How would this, since the activesync was not connected?)
So i couldnt do anything, I soft reseted the phone, but it wont turned on, or it did but the screen left blank. - like no rom were installed. I tried to press the camera, and the RGB screen came up, saying IPL 4.14.0001 and SPL 4.70 Yang.
Tried to hard reset, but when I pressed send, it said fail.
Tried to update at this position with RUU, but its need activesync so it gave me the same error. Tried to install 3 different roms from 2 differenct SD Cards (that worked before), and It checks the Card, the the RGB screen comes up (like no rom would be on the SD card).
Created a GoldCard, and installed the official ROM. The "Checking SD Card" text stays here for 5 secs, then the RGB screen comes up.. wtf?
Same with heradiag.nbh
Now tried again the Hard reset, it said succesfull, but when it tries to boot I just get a green to black gardient image, something like this: http://www.cylekx.net/help/tutorial_assets/images/byte ramp and green gradient.jpg (but rotated), and nothing else happens.
Any ideas to get the device back to life?
Maybe there are some hardware malfunction inside the phone?
Thanks, and sorry if I posted this to a wrong thread. (was not sure where it should go)
Just got a WhiteScreen crash at the "Checking SD Contents" screen.. It cant be software problem i guess.
Cmd>getdevinfo
GetDeviceCID: Error - InitDecoder
HTCSHTCE
Cmd>ls
clean up the image temp buffer at 0x8C100000 Length 0x03A00000
BOOTLOAD_PAGE_TABLE_BASE_C_VIRTUAL= 0x8C080000
Clear image temp buffer done .
MTTYDownloadImage
start download
==CreateFile err==nb0 Sync bytes error(0) 6B != 42
Error : DownloadImage return error (code = 0xFFFFFFFF)

While your phone is in Bootloader mode, install the original ROM with the RUU. All Heralds (P4350) and Atlas'(Wing P4351) can be flashed while on the bootloader screen. Just disregard the step on the RUU that says to make sure your phone is connected to ActiveSync. Also if you have downloaded the whole RUU for the Original ROM, you have to edit the .EXE file to remove the .SPL file that is inside. You can use 7-Zip to get inside of the .EXE file. If not, then just install the ROM as you normally would. You will not need a SD card to install this. Let us know what happens. EVERYONE: if I have forgotten to mention something, please add.

baronmxc said:
While your phone is in Bootloader mode, install the original ROM with the RUU. All Heralds (P4350) and Atlas'(Wing P4351) can be flashed while on the bootloader screen. Just disregard the step on the RUU that says to make sure your phone is connected to ActiveSync. Also if you have downloaded the whole RUU for the Original ROM, you have to edit the .EXE file to remove the .SPL file that is inside. You can use 7-Zip to get inside of the .EXE file. If not, then just install the ROM as you normally would. You will not need a SD card to install this. Let us know what happens. EVERYONE: if I have forgotten to mention something, please add.
Click to expand...
Click to collapse
Hah, i was so unlucky A chip on the motherboard burnt, so if u plugged in the USB it crashed immadiatelly, no wonder why the PC couldnt recognise it..
But still have a problem. Tried to flash the original shipped rom, and another costum rom but both said INVALID MODEL ID.
So what now?
thanks
Cmd>getdevinfo
GetDeviceCID: Error - InitDecoder
HTCSHTCE
Cmd>ls
clean up the image temp buffer at 0x8C100000 Length 0x03A00000
BOOTLOAD_PAGE_TABLE_BASE_C_VIRTUAL= 0x8C080000
Clear image temp buffer done .
MTTYDownloadImage
start download
==CreateFile err==nb0 Sync bytes error(0) 6B != 42
Error : DownloadImage return error (code = 0xFFFFFFFF)
Cmd>set 32
+ SD Controller init
- SD Controller init
+StorageInit
SDInit+++
PL_SDSetSlotNumber() - MPUIO_SDIF_SEL1=0, MPUIO_SD_IF_SEL=0
SDInit - SD ver2.00
SDCmd1 Command response time-out. MMC_STAT = 80
SDCmd1 Command response time-out. MMC_STAT = 80
SDCmd1 Command response time-out. MMC_STAT = 80
SDCmd55 Card status error in response. MMC_STAT = 4000
SD Ver2.00: Low Capacity
SD clock to 24MHz
***** user area size = 0x79A00000 Bytes
SDInit---
SDInit OK
Unlimited time!
GetDeviceCID: Error - InitDecoder
g_cKeyCardSecurityLevel = 0
HTCE
More Info:
Now i can connect with MTTY and write commands in the bootloader. With this SPL version most commands i found doesnt work, but I got some information about my phones status: the GoldCard's security level is 0, thats correct. The problem is with the CID: GetDeviceCID: Error - InitDecode
I think the problem is this, since it cant get the CID, cant verify the rom matches .
I can write things with mtty into ram or storage, is it possible to write the whole rom directly to the devices boot dir?

CheeseDave said:
Hah, i was so unlucky A chip on the motherboard burnt, so if u plugged in the USB it crashed immadiatelly, no wonder why the PC couldnt recognise it..
But still have a problem. Tried to flash the original shipped rom, and another costum rom but both said INVALID MODEL ID.
So what now?
thanks
More Info:
Now i can connect with MTTY and write commands in the bootloader. With this SPL version most commands i found doesnt work, but I got some information about my phones status: the GoldCard's security level is 0, thats correct. The problem is with the CID: GetDeviceCID: Error - InitDecode
I think the problem is this, since it cant get the CID, cant verify the rom matches .
I can write things with mtty into ram or storage, is it possible to write the whole rom directly to the devices boot dir?
Click to expand...
Click to collapse
a INVALID MODEL ID error occurs when you use the wrong RUU/ROM for a phone. Heralds must use the Herald RUU and Wings must use the Wing RUU.
Herald RUU (P4350) <- English version is the 3rd link.
T-Mobile Wing [Atlas](P4351) RUU <- Phone Number and IMEI Required
T-Mobile Wing [Atlas](P4351) RUU<- Phone Number and IMEI NOT Required however I believe that this is an older Windows 6.0 Build
If you want to keep your phone hard spl'd, you need to modify the EXE of the RUU and erase the SPL.nbh file.
As far as writing the ROM directly, that is out of my expertise. Someone else will have to answer that.

baronmxc said:
a INVALID MODEL ID error occurs when you use the wrong RUU/ROM for a phone. Heralds must use the Herald RUU and Wings must use the Wing RUU.
Herald RUU (P4350) <- English version is the 3rd link.
T-Mobile Wing [Atlas](P4351) RUU <- Phone Number and IMEI Required
T-Mobile Wing [Atlas](P4351) RUU<- Phone Number and IMEI NOT Required however I believe that this is an older Windows 6.0 Build
If you want to keep your phone hard spl'd, you need to modify the EXE of the RUU and erase the SPL.nbh file.
As far as writing the ROM directly, that is out of my expertise. Someone else will have to answer that.
Click to expand...
Click to collapse
Thanks for your help, but as i said my device ID is messed up with the USPL process... "GetDeviceCID: Error - InitDecoder" None of the RUUs works.
Waiting for the directly-writing method, or i'll have to replace the storage at the mainboard... (wont be cheap).

[q] tool version dosent match !!! Hd2

hi all
tried to find answer myself but couldnt find anything related my problem is ive flashed the new xboxmod + yuki wp7 rom (7004) done every thing to letter it gets two updates from zune to (7392) then i tried to send cab files and it fails with this massage " installed version of zunewmdu <4.8.2345.0> dosent match tool version <4.8.2134.0>
now zune tries to update to mango beta 7403 and fails with error code 80180005
any help would be great plus im not a developer i just eat what the chefs here provide so i not sure what u need to know from me plus if this has been solved elsewhere sorry and pls point me to it
many thanks in advance

cmully said:
hi all
tried to find answer myself but couldnt find anything related my problem is ive flashed the new xboxmod + yuki wp7 rom (7004) done every thing to letter it gets two updates from zune to (7392) then i tried to send cab files and it fails with this massage " installed version of zunewmdu <4.8.2345.0> dosent match tool version <4.8.2134.0>
now zune tries to update to mango beta 7403 and fails with error code 80180005
any help would be great plus im not a developer i just eat what the chefs here provide so i not sure what u need to know from me plus if this has been solved elsewhere sorry and pls point me to it
many thanks in advance
Click to expand...
Click to collapse
in the cab sender, there should be 3 folders, one of them says if needed, install this tool. try installing that (there is 1 32bit and 1 64bit so just install the one for your system). also make sure the cab sender app stays in the same folder as those 3 folders. so in the WP7 Cab sender folder (or whatever the main folder is called)you have:
FOLDER: if needed install this tool
FOLDER: logs
FOLDER: tools
and the WP7 Update Cab Sender.bat file

thanks gonna TRY NOW ill report back

hi
just tried again and it returned a new message (as below) am i missing something.
and y does it want to update me to 7403 isnt it supossed to update to 7220 first as zune already updated me to 7392 ????
thanks again
Error:
Update device 7938612c - b493e145 - 90cfab34 - dc9e259e Complete with error code
: 80180011, error message: IU (Image Update) installation failed on phone: None
of the packages in the update are applicable.
■
╚══════» Done
Press any key to continue . . .

thought id cracked it tried to install mango rtm cabs and this come back if this is any help
think i might start again if so do i need to task 29 or can i just re flash the rom
Name: HTC HD2
KITLName: QSD8XXX07185665
Manufacturer: HTC
ModelId: 1
Model: HD2
MobileOperator: 000-00
Version: 07.00.07392.03-00.00.00000.00-00.00.00000.00
Error:
Update device 7938612c - b493e145 - 90cfab34 - dc9e259e Complete with error code
: 80180005, error message: IU (Image Update) installation failed: The update pac
kage isn't a valid CAB file.
■
╚══════» Done
Press any key to continue . . .

[Q] Dell Venue Pro; Update failed, recover not successfull

Hello there,
my "new" Venue Pro arrived yesterday and i just started to test it.
It had a very old firmware, not even mango ... so i startet updates by zune.
After the third update (for wlan problems, i think it was the "latest" wp7 update) i get an error .... so i restartet the phone an tried again, no success.
I read a lot, not even the microsot update tool could help. So i startet the recover in zune over settings, updates.
The update startet and now i always get an error by 61%. I read a lot again, i even tried to backup it from another comuter (copied image %appdata%\Microsoft\Microsoft Phone Update) but the same problem.
So, my "new" phone doesent start any more ... it just loads to the bootloader ...
I tried to get any offiziel firmware to flash the device to "standard" but i seams hat MS dont want this.
I knew a little bit about flashing WM6 devices (HSPL & custom fw) but with WP7 devices i dont really understand what to do in this situation.
I hope you can help me! Can i download the dell firmeware someware to recover the phone? maybe someone have a "personal recover firmware" for me?
Thx

If your device can load into download mode (that you called "bootloader") it can be restored to 7004 T-mobile branded version and later update to 7720 via Zune. This is only one available firmware on the public.
Look at this thread: http://forum.xda-developers.com/showthread.php?t=1411300

THX!
I will try ... downloading ...

So, i downloaded VenuePro_flash_GLEOS2A_US_TMO_SIGNED_SWV0105_LP0030_RV001_RETAIL.ffu and thought, everthing is getting fine.
But i had no idea how i can install this!
I´m reading hours and hours, tried to use UpdateWP.exe (crash on 2 computers, where NO MS Support tools are installed), Windows_Phone_7_Backupv1.9, MangoB2-ZuneClient, Zune 4.7 .... no success.
Could sombody please tell me, how i can install this on Windows 7 x64? I dont know what to do ...

I get this message when i try to updatewp it;
Unhandled Exception: System.TypeInitializationException: The type initializer fo
r 'wm7update.Program' threw an exception. ---> System.IO.FileLoadException: Coul
d not load file or assembly 'Microsoft.WindowsMobile.DeviceUpdate, Version=7.0.0
.0, Culture=neutral, PublicKeyToken=ddd0da4d3e678217' or one of its dependencies
. The located assembly's manifest definition does not match the assembly referen
ce. (Exception from HRESULT: 0x80131040)
File name: 'Microsoft.WindowsMobile.DeviceUpdate, Version=7.0.0.0, Culture=neutr
al, PublicKeyToken=ddd0da4d3e678217'
at wm7update.Program..cctor()
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\M
icrosoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure lo
gging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fus
ion!EnableLog].
--- End of inner exception stack trace ---
at wm7update.Program.Main(String[] args)
See also here: http://forums.create.msdn.com/forums/p/85864/516966.aspx
As i said before, there is no (more) Microsoft Update Software on my computer and on the second there never was it.
Mybe i could handle it with the "MangoB2 Updater" .... but i cant download this anywhere.
I really have no luck :-(

Do not panic yet. You have different versionsof zune or updatewp /missing files
Deinstall everything related to zune.DONT TOUCH EVERYTHING RELATED TO MS SUPPORT TOOLS, IF ITS INSTALLED IT DOESNT INFLUE ON PROCESS!!!
Install Net framework 3.5, 4;
Install Zune(take it from zune.net);
Install wp7 updatetool from zip attached here here http://forum.xda-developers.com/showthread.php?t=1306415 with proper x64 file.
Follow those steps after connecting device in download mode:
Extract command prompt to C:\program files\zune\
go to directory to “C:\program files\zune\ and run Command prompt. Type in : “UpdateWp /list” and your phone should show up there.
If your phone is listed (it should be) and your download is done and extracted, copy the VenuePro_flash_GLEOS2A_US_TMO_SIGNED_SWV0105_LP003 0_RV001_RETAIL.ffu file over to the” C:\program files\zune\” directory.
Type in: “updatewp /ffu VenuePro_flash_GLEOS2A_US_TMO_SIGNED_SWV0105_LP003 0_RV001_RETAIL.ffu” enter, update should start.

YES IT WORKS!
Great, now i can start my dell venue pro again and even updating is functional.
But why can´t i change the display language? I tought i´m able to change the display language in this roms? In all WP7 phones (in germany) i could change the language at the first start (and after a reset).
*argh!*
On this site i found language packs, but that is a little bit ... argh?!
http://forum.xda-developers.com/showthread.php?t=1306415

so it´s over ... i send the phone back ...
Thank u very much 4 helping.