Boot problem - Touch Dual, MDA Touch Plus ROM Development

during flashing with niki-project rom the power went down of entire city
When it came back i couldn't start my niki.
i read some things and tried mtty,
i get this!
Code:
Cmd>boot
No card inserted
OEMGetUpdateMode
OEMTranslateBaseAddress 23 80000000 80000000
IPLMSG:0x8:INFO: Loading image ...
IPLMSG:0x9:INFO: Jumping to image...
OEMLaunchImage 80000000
Jump to Physical Address 10300000
more at http://forum.xda-developers.com/showthread.php?p=2092039#post2092039

Related

Rom backup with d2s

I'm attempting to backup my Himalaya as per
http://en.pdamobiz.com/en/forum/forum_posts.asp?TID=62
According to everything I can find on the web, here and on other PDA sites I should be able to enter:
d2s 80000000 02000000
d2s 60000000 00300000 sd a
d2s 70000000 01080000 sd a
And end up with a complete backup.
d2s works on it's own, however d2s with any argument seems to do nothing but return me to the prompt.
I assume I'm missing something.
Entering the password doesn't make any difference ... with or without the password I still have the same problem.
Any thoughts?
Bump

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:

OS.nb flashing times

Just curious as to how long it should take to flash the OS.nb file through mtty???
its been sitting on the 'start NB image download' for about 30 minutes now...
Code:
USB>
USB>task 32
Level = 0
USB>task 28
Storage format start
Write Nand Success
dwBlockToWrite = 13
Storage start block: 463
Storage Total block: 473
Total Bad Block in CE: 0
NeedToEraseBlockStart: 476
Storage format success
USB>lnb OS.nb
:F=OS.nb
:A=501A0000
:O=00000000
:L=FFFFFFFF
start NB image download
well it should take no where near 30 minutes (a full RUU upgrades takes only 25minutes)
when i upgraded to 2.05 via mtty it was done in under ten minutes (fast).
are you sure the filename is OS.nb because be default when you extract the .nb from the .nbh is will be 06_OS.nb
yes im sure it was named correctly else it wouldnt have picked up the
Code:
USB>lnb OS.nb
:F=OS.nb
:A=501A0000
:O=00000000
:L=FFFFFFFF
start NB image download
should i cancel it and start again??
when you extracted the .nb files from the .nbh did you rename any files?
If you didnt, then again I think OS.nb doesnt exist and that is why it is hanging there after more than 30 minutes.
also, make sure that mtty.exe is in the same directory as the .nb you are trying to flash.
yes i renamed the files from 06_OS.nb to OS.nb and the files are in the same directory... what version and connection speed are you using in mtty??? the version im using is 1.11a...
v1.11a and default settings for the USB connection.
I guess you can restart the process, because immediately after the messages you see on the terminal output should have sees the progress meter kick into full swing.
hahahahaha you were right... was using the mtty from a different folder ... time for some sleep....
there you go,
time for sleep? its only 3:22pm in Melbourne...... should you be at work?
EDIT: I cant talk, reading forums on company time, academia is so good.
yeah at work.. but been up all night playing with all these new tools!!!!

Dead HTC TyTN - Help !!

I have big problem!
I kill my TyTN,
I go to multi port...........
---------------------------------------------
USB>task 32
Level = 0
USB>task 28
Storage format start
Write Nand Success
dwBlockToWrite = 13
Storage start block: 473
Storage Total block: 463
Total Bad Block in CE: 0
NeedToEraseBlockStart: 486
Storage format success
USB>lnb RUU_SIGNED.nbh
:F=RUU_SIGNED.nbh
:A=501A0000
:O=00000000
:L=FFFFFFFF
start NB image downloadSH
Load ADDR: 501A0000 Length: 5544382
***************************************
****************************************
*******************************
****************************************
****************************************
****************************************
****LAST BLOCK, dwBytesCollected=0x10000
Code entry point at 0x556E0000
Write Nand Success
USB>task 28
Storage format start
Write Nand Success
dwBlockToWrite = 17
Can't find OS in flash!!!
Storage format success
USB>task 8
-----------------------------------------------------------
can you halp me? please!
ouch.... you tried to flash the entire nbh. This file contains os, extrom, radio and splash screens. You need to take that apart first with nbhextract to get os.nb then flash that instead. Hopefully you'll be able to....

Stuck in bootloader after trying to flash ROM

Just tryed to update my Nike Rom. Now my Nike is stuck in Bootloader Mode.
It displays:
NIKI100
SPL-1. 16.0000
CPLD-4
On a Red Green Blue & White Screen.
Tried all kinds of things to flash the ROM.
Im a newbie at this. Please can someone Help
Hmm, where's my crystal ball...
how about you tell us everything you did and tried to flash your phone, including version and model numbers. otherwise we really can't be of any help.
with phone on, hold down both call answer/call end buttons, press reset (with stylus in hole buy usb port), remove stylus from hole, keep hold of the above two buttons and you should be in bootloader screen (red, blue, green etc.). insert usb cable which is plugged into windows PC, should show USB on device, establich activesync, then run the flasher prog you are using with the ROM you tried to flash, and it should pick up from there. reflash ROM.
Help Me! Same Problem!!!! Where is the Solution??????
use the tool "MTTY". shut down activsync. connect with MTTY via USB and use the command "boot"
Ok I got some similar problem the pda some one tried to repair before with mtty and then client brought it to me, it enters in bootloader mode three colors and showing
It displays:
NIKI100
SPL-1. 16.0000
CPLD-4
On a Red Green Blue & White Screen.
Tried to flash all kinds of roms, so I tried with mtty sending command boot and this is the anwser,
boot
InitDisplay: Display_Chip=1
Fill RSVD information for block 288 to 309
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
No card inserted
OSSIPreLoad ++
OSSIPreLoad failed, CE is NONE
OEMGetUpdateMode
IPLMSG:0x2:ERROR: Failed to open storage partition.
after this the pda only boots and shows white display, please can any one give me or tell me correct command for mtty to repair this.
thanking and waiting for a prompt reply
bcnboy
some more info about my device read by mtty
info a
HTCS356610011071301šQµAHTCE
Cmd>info 8
--- 2K bytes sector version ---
DEVICE NAME=samsung_k9k2g08
DEVICE ID=0xAA
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x800
BLOCK PAGE=0x40
Checking block information
BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 8 (0x8) is reversed block
OS NOT FOUND !!!
Cmd>info 7
HTC Integrated Re-Flash Utility, Common Base Version : 1.51d
Device Name: Nike, Bootloader Version : 1.16.0000
Built at: Oct 8 2007 18:27:27
Copyright (c) 1998-2007 High Tech Computer Corporation
Board ID=0x4
CPLD ID=0x4
gCurrentPanel=0x4
so any suggestions.
bcnboy

Categories

Resources