unlock mdaII radio 1.17 - MDA II, XDA II, 2060 ROM Development

Hi
I have problem with unlock my pocket qtek 2020.
Radio 1.17
d 1.72.00WE
How can I do it ?
Greetings from Warsaw )

Where did you find that upgrade with 1.17 radio version? Where i can download?
Thank You

I buy new phone with new software and I can`t unlocking my mda
Greetings from Warsaw

can you post a copy to the forum?
to make a copy of your radio rom, do the following:
( you will lose all data on your device, and your sd-card, so make a backup first )
- make sure there is no sd-card in your device.
- boot your device into bootloader mode
( by holding down the big action button together with the power button,
and hard-resetting with the pen at the same time )
now the display should say 'serial' and the bootloader version.
- insert a blank sd-card
- put your device in it's cradle
- start 'mtty' ( see this page )
- select 'usb' in the mtty program.
- type the followint command into the mtty window
Code:
d2s 60000000 00300000
( this will write your radio rom to the sd-card )
- when it says it is done, remove the sd-card.
- hard-reset, and reinitialize your device.
- put it in the cradle again.
- insert the sd-card, answer 'no' to the do-you want to format question.
- use 'psdread' to copy the sdcard image to a file ( you type this command on a windows or dos command prompt )
Code:
psdread -3 0 0x300200 sdradio.img
see here for information on psdread.

correction: I meant 'psdread'.
now put this howto up on the wiki

Related

Backup Original ROM before trash my Himalaya

First of all .. my thanks goes to all the people to this forum!
You're really GREAT !!
In any case sorry for my poor english :wink:
I've few questions ...
I've read many many pages but I can't understand the right procedure to follow for dumping my Himalaya original ROMs because in some pages the "d2s" command is followed by some numbers and in other, by other numbers ... confusion bring me !
After that, otherwise, I've tried to follow the XDA II procedure and the storing procedure to SD seems to be ok .. but when I try to save the rom dump from my SD to PC using ntwr (otherwise was unreadable in Win), I've got a read error but, in any case, I obtain only one file on my PC of about 400 MB and I suppose that something is wrong because all of you speaks of about 50 MB ... so ... What's the right procedure with the right command? How can I be sure that my dump is correct? The dump it's only one file or one for separate ROM Radio and Extended?
When I solve this issue I can try to upgrade my Himalaya to WM2005.
Thank you for your help.
Please help me, I'd like don't lose my guarantee.
This post was submitted also to buzz forum
Now this is the situation ...
Qtek 2020 - 1.66.04ITA
-= Preparing the device =-
01 ) I,m gone to Bootloader (Power + Directions + Reset)
02 ) I see on the device "Serial v1.06"
03 ) I stop MSSync service Ctrl+Alt+Canc and stop wcescomm.exe
04 ) Put device on cradle
05 ) Now I see on the device "USB v1.06" instead of "Serial v1.06"
06 ) Put the 512 MB SD into the device
07 ) Start Mtty 1.42
08 ) Leave as is all the parameters
09 ) I've "USB" port (and not ".WCEUSBSH001") and I press USB
10 ) Ok seems to be connected to the device
-= Dumping the ROM on SD =-
11 ) Into mtty command line I write (and not copy and paste and without "sd a" at the end)
d2s 80000000 02000000
12 ) Device tell me % of work while in mtty I found
SD:Waiting for card insert.........
CMD3 for SD, it's OK, ready to get RCA from response.
SD : Detected one card
SD : ready for transfer OK
pc->drive.total_lba=EEC00
pc->drive.num_heads=0
pc->drive.sec_p_track=0
pc->drive.num_cylinders=0
pc->drive.block_size=200
pc->drive.features=0
pc->drive.RCA=B368
pc->drive.drv_type=40000000
pc->drive.securedAreaSize=0
pc->drive.securityDrv=0
pc->drive.busWidth=1
pc->drive.erasedSize=0
Total card size=1DD80000
SDCARDD2S+,cStoragePlatformTyp e=FF
****************************** ****************************** ****************************** ****************************** ********
Store image to SD/MMC card successful.
USB>
13 ) Then I write
d2s 60000000 00300000 sd a
14 ) Device tell me % of work while in mtty I found
SD:Waiting for card insert.........
CMD3 for SD, it's OK, ready to get RCA from response.
SD : Detected one card
SD : ready for transfer OK
pc->drive.total_lba=EEC00
pc->drive.num_heads=0
pc->drive.sec_p_track=0
pc->drive.num_cylinders=0
pc->drive.block_size=200
pc->drive.features=0
pc->drive.RCA=B368
pc->drive.drv_type=40000000
pc->drive.securedAreaSize=0
pc->drive.securityDrv=0
pc->drive.busWidth=1
pc->drive.erasedSize=0
Total card size=1DD80000
************
Store image to SD/MMC card successful.
USB>
15 ) Then I write
d2s 70000000 01080000 sd a
16 ) Device tell me % of work while in mtty I found
SD:Waiting for card insert.........
CMD3 for SD, it's OK, ready to get RCA from response.
SD : Detected one card
SD : ready for transfer OK
pc->drive.total_lba=EEC00
pc->drive.num_heads=0
pc->drive.sec_p_track=0
pc->drive.num_cylinders=0
pc->drive.block_size=200
pc->drive.features=0
pc->drive.RCA=B368
pc->drive.drv_type=40000000
pc->drive.securedAreaSize=0
pc->drive.securityDrv=0
pc->drive.busWidth=1
pc->drive.erasedSize=0
Total card size=1DD80000
DOCInfoTableinitHW+
Binary0:dwSize=80000
BINFS0:dwSize=0
FAT0:dwSize=1000000
FAT1:dwSize=EA0000
All:dwSize=1F20000
****************************** ****************************** ******
Store image to SD/MMC card successful.
USB>
-= Saving ROM from SD Card to PC =-
17 ) Put the SD Card into a Card Reader
18 ) Go to Dos command line into ntrw path
19 ) Type "ntrw read ROM.nb1 H:" where H: is the Card reader drive
Now start the problem ... :shock:
I want to know if it's all ok with this process ...
The output of ntrw is:
NTRW 2.0
Removable media
Cylinders: 0:60
TracksperCylinder: 255
SectorsPerTrack: 63
BytePerSectors: 512
bufsize is 65536
500629504 bytes written bytes: 0
ReadFile(): ROM.nb1 -- Parametro non corretto
First signal of some error but someone tell that's ok!
And then I see prompt.
Now I find the file ROM.nb1 that is 477 MB (like the SD size after a FAT format).
It's ok? ... I don't think so .. but let's going on!
I open the file with an HEX Editor and the file seems ok but after a string like HTCE the file contains all 00h.
Can I cut off that part?
How can I ensure myself that's all ok?
Come on guru don't leave me with the bootloader splash screen instead of the MAGNETO one :lol: :lol: :lol:
Thanks to rhmartin's help (on buzzdev.net) I've reach this situation ..
I've got my dumped rom in SD and in a file.
But ...
I acquire more information about my Qtek 2020 (XDA2):
ROM: 1.66.04ITA
Radio: 1.10
ExtROM: 1.66.148
I think that's a WM2003 (not SE), isn't it?
In any case ... I put back my dumped roms in SD and followed the procedure for rom restore:
1 - Bootloader
2 - Put SD into device
3 - Wait for "Press Power Button"
4 - ecc. ecc.
But I never reached number 3, what's wrong?
I've put back the dump as a single file (as ntrw output give to me), it's correct or I must put it back (and so backup first in that way) as 3 separate files?
I've seen that in download area there's no WM2003 dumped rom, so I search by myself and I found RUU172128ITA (1.72 ITA) but I prefer if my backup can be useful for disaster recovery and can be used for my original version backup.
I think that you understand my situation .. I prefer ask before a not funny situation instead fill the forum with hundreds emergency posts.
I hope you think I've reason.
Thank you for the patience and sorry for possible misunderstandings or english syntax errors!
NO ONE CAN HELP ME ... INCREDIBLE!
I'm ready to ask sorry but ...
There's no one in this great forum that can help me ...
IT'S INCREDIBLE !!! :shock: :shock: :shock:
I don't think that no one haven't my problem ...
PLEASE SOMEONE HELP ME
:evil:

Hermes Failed Radio

Hi,
First time : i'm sorry for my bad english,
I try a radio corrupt (not for my hermes-probably for 900). I would like change the corrupt radio. I try radio 1.16 but my hermes wait 30 minutes and my pc write "checking the information ..." and nothing.
In bootloader i can see :
Herm200
IPL.-1.01
and
Herm299
SPL-1.04
After change the first corrupt radio, I have a white screen and nothing .
I would like to put the original radio.
My Hermes is a SFR Wodafone 1605.
Thank you for you help
Sincerly,
YC
See "Problem 5: Device shows NO GSM when booting" on this wiki page:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems
Re
Ok prof ! I'se a good article :
"If you feel brave, and always at your own risk, what you should do to fix your bricked hermes with screwed radio is this:
1) Put your Hermes in bootloader mode
2) Disable USB connections in ActiveSync
3) Open mtty.exe and select USB port, then connect.
4) Hit enter twice, you will see the "USB>" prompt.
5) Type the following commands (do not copy paste!!!):
Code:
set 1e 1
erase a0040000 c80000
erase a0cc0000 c80000
erase a1940000 640000
set 1e 06) Reset your phone and put it back in bootloader mode
But 1 question :
How i can find a topic to make a rom without activsync
Thanks

Mtty command

Any one know command to mtty for atom exec\orsio n725 or RoverPC G5.
Phone connect to pc by rs-232, standart command not work
PS sorry for my english
Sorry, just want to understand further, why you using a serial cable (RS-232) to connect to your PC. is your phone hanged at bootloader mode?
Winterice said:
Any one know command to mtty for atom exec\orsio n725 or RoverPC G5.
Phone connect to pc by rs-232, standart command not work
PS sorry for my english
Click to expand...
Click to collapse
mtty is made for HTC devices. Atom is made by Quanta. I've been looking for the same tool myself. have you tried putty? If I'm not mistaken, you are trying to reformat the DOC? or upgrade the device thru mtty?
I have looked into the things we can upgrade from SDCARD flashing, and DOC.IMG is one of the option. I think this will change the format of DOC. One way to get a copy of this DOC.IMG is to dump the ROM thru SDCard using buzz romdumper64.
Please let me know of your developments.
Phone in bootloader, i am try dump rom. if plug phone with USB mtty doesn't see phone. if use command 'r' phone write message Format DOC.OK
Sorry for my English.
This experiments with the MTTY.
This experiments to copy ROM to the SD card or file.
I'm Running MTTY.
connecting PC and the Rover G5 (Atom Exec/Orsio N725), using a serial cable (RS-232).
Run bootloader mode.
On the PC screen :
-----------------
*******Beginning System Initialization*******
Run Mode = 104 MHz
Turbo Mode = Run Mode
MemClk = 104 MHz
Bus Mode = NORMAL
SDCLK[1] = MemClk (SDRAM Clk)
SDCLK[0] = MemClk/2 (Sync. FLASH Clk)
Mode = RUN
Boot FLASH in Asynchronous mode
******************************************************
OEMInitDebugSerial using STUART888
Microsoft Windows CE Ethernet Bootloader built Jun 13 2006 20:41:44
Copyright © 2006 Microsoft Corporation
Portions copyright © 2006 Intel Corporation
Original MSC0 12801282
New MSC0 12807FF2
New MDREFR = 0x11E018
New SXCNFG 40044004
Flash type L18
main:InitDisplay()
InitLCDCtrl..
ClearFrameBuffer..0xA6000480
+Check LCM ID:
==PreBL_Ver = 0.0.0
==2nd_BL_Ver = 0.0.0
Ethernet Boot Loader Configuration:
0) IP address: 0.0.0.0
1) Subnet mask: 0.0.0.0
2) # bootme's: 0
3) Boot delay: 0 seconds
4) DHCP: Disabled
5) Reset to factory default configuration
6) Launch existing flash resident image at startup
7) Program RAM image into FLASH (Disabled)
8 ) Program SMSC MAC address
9) Boot device order: SMSC -> PCMCIA S0 -> PCMCIA S1
D) Download image now
E) Erase flash image
L) Launch existing flash resident image now
U) Download os image now (USB1.1)
O) Overwrite eboot image now (USB1.1)
H) Jump to DM
I) Sim Lock
------------------
But ...
There are undocumented commands.
If press "R" - a message on the screen
Formating DOC.
OK
So there are undocumented commands
we are interesting other command
It would help us if we get hold of Service Manual.
Winterice said:
Phone in bootloader, i am try dump rom. if plug phone with USB mtty doesn't see phone. if use command 'r' phone write message Format DOC.OK
Click to expand...
Click to collapse
Have you tried buzz grab_it ROM dumper? it worked perfectly well with the Atom. It dumped everything to SD Card. You just have to break it apart and identify the sections.
For the Atom:
diskimg.nb0
eboot.nb0
dm.nb0
flash.img
agent.mot
mot.mot
cpld.img
assetinf.img
extended.img
MDOC.img
what particularly interest me is MDOC.img because I believe we can change DOC format with this.
our device have 192 mb rom, i or Alex_beda try this dumper today
This dumper not working.
Message in the screen "cannot create file!"
Using the miniSD 2 GB Kingmax
May be need to use mini SD less 1 GB?
Or using any other dumper?
alex_beda said:
This dumper not working.
Message in the screen "cannot create file!"
Using the miniSD 2 GB Kingmax
May be need to use mini SD less 1 GB?
Or using any other dumper?
Click to expand...
Click to collapse
you have to modify the name of SDCard. It is named "memory card" in your device. the program looks for "Storage Card". Search this value using registry editor.
"Folder"="\Storage\Card"
jiggs said:
you have to modify the name of SDCard. It is named "memory card" in your device. the program looks for "Storage Card". Search this value using registry editor.
"Folder"="\Storage\Card"
Click to expand...
Click to collapse
Thank you!
I'm downloading dump in the miniSD card.
But...
Problem.
Dump size 128 MB maximum
ROM size in my divice 192 MB.
How downloading full size (192 mb)?
alex_beda said:
Thank you!
I'm downloading dump in the miniSD card.
But...
Problem.
Dump size 128 MB maximum
ROM size in my divice 192 MB.
How downloading full size (192 mb)?
Click to expand...
Click to collapse
Your ROM chip size is 192MB. BUT I think, your ROM system size is only 64mb. Same as ATOM. The rest is only persistent storage, extended partition, and checksum partition.
to verify, you can pdocread the memory layout of your device. don't forget to install the RAPI before pdocread; otherwise, it will not work.
my ELF's mac address may be lost
every times, when my elf restart,
a document named HTCExcpthLog_mmdd_hhmmss.txt will be build in SDcard at \storage card\HtcLog\
mmdd_hhmmss is the restart time.

WM 6.5 Miky rom, HTc 7500 probably destroyed.

Ok guys,
i think i'm in a sort of big trouble. I got SPL1.2, i was installing this Miky ROM and then at 91% Windows Mobile Device Center crashed on my pc. Now what i have is a 7500 booting with strange lines on the screen and then fading to white. I tried to pull out the battery and then to recover but nothing is working. I broke my 7500??? Why God is never here when i need him???
See if you can get into bootloader (tri color screen) if you can flash a factory rom. Have a look here, you should find what you need or a link to the needed resources http://forum.xda-developers.com/showthread.php?t=429013
Cheers
BR
***Why You Try This !!!___carefully step by step !!!!!!!!
cmonex
Senior Member Join Date: Jul 2006
Location: Budapest
Posts: 2,314
--------------------------------------------------------------------------------
here's an experimental program I made to make the process more automatic so users can fix their own wifi without our help.
this is good for both corrupt modelid and corrupt wifi, and fixes both at the same time.
STEP BY STEP:
1. download attachment at the end of the post for mac1.exe (requires .net 2.0 installed on the PC)
2. you will also need to download the other attachment in this post for the mtty program.
3. enter bootloader (tricolour screen) manually by pressing and holding camera button all the way in (yes I mean that, press it in as hard as you can!!), while doing a reset, then keep the camera button held until you see the tricolour screen.
4. disable USB in activesync (wmdc if you have vista - in this case, do not kill wmdc, just disable usb in it!!!)
5. run mtty and select USB option from the dropdown box!
6. then press enter in main window that comes up, see if that gives you Cmd>
7. now you should have Cmd>, if not, re-check if you did the above steps right until you get Cmd>
8. now run the mac1.exe, type in your MAC address you want to use for the Athena, if you have SPL 3.xx reported on the tricolour screen, then use the button for SPL 3.xx, otherwise if you have SPL 1.xx reported, use button for 1.xx.
9. this should have generated a .bin file for you, copy that bin file in the folder of mtty.
10. now, in mtty, type (do not copypaste!) this command: task 32
11. this should return Level = 0
12. now, you must only do one of the two following commands:
- if you have SPL 3.xx, then type (do not copypaste!!) this command: lnb filename.bin 76508000
(there filename is the name of the .bin file you generated - don't forget to put .bin after filename, as the full name is needed).
- OR, if you have SPL 1.xx, then the command is different (do not copypaste!!): lnbs filename.bin 75108000
(there filename is the name of the .bin file you generated - don't forget to put .bin after filename, as the full name is needed).
NOTE, the command starts with a lowercase "L", not "I"!
WARNING: PLEASE DO NOT MIX UP THESE TWO DIFFERENT COMMANDS!!!
if this info helps: most people will have SPL 3.xx, and if you have AP4 (not vanilla) already running then you're definitely 3.xx
13. mtty will popup a window asking "OK", you press OK!
if you get "Fail to synchronize with the host (1)", then make sure you did follow step by step. if still same error, try placing mtty and the bin file under C:\.
14. now the file downloads, if mtty reports it flashed the file, and at the end "code entrypoint unknown", then that's it, now boot back to WM and see if wifi works.
edit: see raskell's mtty tutorial too, #36. post in this thread
if you *really* can't manage to get it working, you can still feel free to PM me.
let me know if this program and step by step description helped any.
Attached Files mac1.zip (6.3 KB, 1585 views)
mtty_0513_Test.zip (553.9 KB, 1883 views)
__________________
Here is direct link__on floor #33 ===>
http://forum.xda-developers.com/showthread.php?t=387454&highlight=mtty&page=4
Good Luck!!!

Error [244] : Invalid model id

Hello
Please help me return the model number,
cause when I try to change my rom I always get the same error Error [244] : Invalid model id.
Now I have
some strange symbols in bootloader.
This appeared after I'd tryed to change mac using mtty, as I have created bin file for SPL 1.xx
Please help me
Hi,
You need to carry out the instructions to the letter in post 33 HERE and it will sort your problem, read it all very careful, its easy to make a mistake if you're not paying attention.
regards
Jay
Thanks Jay.
It works again.
You're welcome, glad it helped
Regards
Jay
here's an experimental program I made to make the process more automatic so users can fix their own wifi without our help.
this is good for both corrupt modelid and corrupt wifi, and fixes both at the same time.
STEP BY STEP:
1. download attachment at the end of the post for mac1.exe (requires .net 2.0 installed on the PC)
2. you will also need to download the other attachment in this post for the mtty program.
3. enter bootloader (tricolour screen) manually by pressing and holding camera button all the way in (yes I mean that, press it in as hard as you can!!), while doing a reset, then keep the camera button held until you see the tricolour screen.
4. disable USB in activesync (wmdc if you have vista - in this case, do not kill wmdc, just disable usb in it!!!)
5. run mtty and select USB option from the dropdown box!
6. then press enter in main window that comes up, see if that gives you Cmd>
7. now you should have Cmd>, if not, re-check if you did the above steps right until you get Cmd>
8. now run the mac1.exe, type in your MAC address you want to use for the Athena, if you have SPL 3.xx reported on the tricolour screen, then use the button for SPL 3.xx, otherwise if you have SPL 1.xx reported, use button for 1.xx.
9. this should have generated a .bin file for you, copy that bin file in the folder of mtty.
10. now, in mtty, type (do not copypaste!) this command: task 32
11. this should return Level = 0
12. now, you must only do one of the two following commands:
- if you have SPL 3.xx, then type (do not copypaste!!) this command: lnb filename.bin 76508000
(there filename is the name of the .bin file you generated - don't forget to put .bin after filename, as the full name is needed).
- OR, if you have SPL 1.xx, then the command is different (do not copypaste!!): lnbs filename.bin 75108000
(there filename is the name of the .bin file you generated - don't forget to put .bin after filename, as the full name is needed).
NOTE, the command starts with a lowercase "L", not "I"!
WARNING: PLEASE DO NOT MIX UP THESE TWO DIFFERENT COMMANDS!!!
if this info helps: most people will have SPL 3.xx, and if you have AP4 (not vanilla) already running then you're definitely 3.xx
13. mtty will popup a window asking "OK", you press OK!
if you get "Fail to synchronize with the host (1)", then make sure you did follow step by step. if still same error, try placing mtty and the bin file under C:\.
14. now the file downloads, if mtty reports it flashed the file, and at the end "code entrypoint unknown", then that's it, now boot back to WM and see if wifi works.
edit: see raskell's mtty tutorial too, #36. post in this thread
if you *really* can't manage to get it working, you can still feel free to PM me.
let me know if this program and step by step description helped any.
Attached Files
File Type: zip mac1.zip (6.3 KB, 2125 views)
File Type: zip mtty_0513_Test.zip (553.9 KB, 2613 views)
Ameo
Pfff i have tried everthing what i could find and nothing works. i managed to get the driver working from usb on windows 7 but it keeps showing the bootloader! with some strange marks. i flashed it with 1.2 Olipro and im afraid it will never work again any suggestions left?
Greetings

Categories

Resources