Hello!
Where I can download mtty for Trinity?
http://wiki.xda-developers.com/uploads/mtty.exe not working!!!!
Hello, so that its it functions is necessary to neutralize (wcescomm.exe) ActiveSync and then to select port USB in mtty.exe.
I have SPL-1.01 MFG, but......
USB> task 32
Level = 0
Cmd>lnb C:\finalsplash.nb 500e0000
:F=C:\finalsplash.nb
:A=501A0000
:O=00000000
:L=FFFFFFFF
start NB image download
Click to expand...
Click to collapse
On this step, process stoped
BE WARNED THIS ROM ADDRESSES ARE FOR HERMES, NOT FOR TRINITY... flashing the wrong address can brick your device!
you have to use mtty 1.16 for the lnb command to work.
Take it from here:
ftp://xda:[email protected]/Hermes/Cooked_ROMs/SPL-1.01MFG_Pack.zip
pof said:
BE WARNED THIS ROM ADDRESSES ARE FOR HERMES, NOT FOR TRINITY... flashing the wrong address can brick your device!
Click to expand...
Click to collapse
Say me, please ROM adress for Trinity!
Sorry, my English very bad....
lvsw said:
Say me, please ROM adress for Trinity!
Click to expand...
Click to collapse
sorry I don't have a Trinity and I don't know what is the ROM layout on it, you can investigate yourself capturing the output of the RUU while flashing a rom with usb monitor, dumping rom parts with rbmc bootloader command, and dumping mmu and parts of mem from gnuharet... but it's a long process until you manage to get all the addresses correctly. You have to compare what you get from the device with the *.nb file extracted from the NBH to see where each part of the ROM starts. Can't really do this without having a Trinity on my hands
Problem using mtty
I have some ploblems using mtty.... I deselect "connect to USB" in pc activesync, then I connect the pocket pc on the usb cable, then I start mtty and I select USB.... I have a the mtty window in which is written CLIENT then, again, CLIENT, and the pocket pc... CONNECTING TO USB... and this situation remain without any changement.... where I am wrong?
pof said:
you have to use mtty 1.16 for the lnb command to work.
Click to expand...
Click to collapse
Actually, the LNB command must be implemented in the bootloader to work. If you connect to Trinity using any version of MTTY (from 1.10 to 1.46) and type LNB, it will just give an "Command error!!!" message.
yes, but seems to be implemented on the MFG bootloader version that is left on the device after unlocking it with imei-check unlocker, isn't it?
can't get MTTY to connect w/ Trinity
dr-jo said:
Hello, so that its it functions is necessary to neutralize (wcescomm.exe) ActiveSync and then to select port USB in mtty.exe.
Click to expand...
Click to collapse
Not that I think it should matter much but in case it does I'll say first that I'm running a PC w/ Vista and not xp or earlier.
Anyway, I can't get MTTY to connect to my Trinity.
The only port that MTTY can open is my Com3. All other ports, inluding the one titled "USB" can not open.
When I have MTTY open on Com3, there is no response to any command so I suspect although the application is occupying the port, it is not communicating w/ the Trinity.
Can anyone provide some insight here or tell me the correct com port settings (parity, baud, stopbits, etc)?
Thanks,
J
I tried MTTY on my WinXP notebook as well. I get the same situation. I downloaded a freeware terminal emulator application also but wasn't able to establish coms w/ the Trinity either.
Can someone confirm their com settings in MTTY?
The same thing has happened to me on p3400i, the New Gene, followed the guide at XDA to every letter, though I knew my device was a new Gene. Now the mtty program opens with some settings window instead of the USB button. Only port accessible is COM3. Flashed and bricked by Olipro SPL.
Related
I have a qtek9090 and it will not boot up, it says "Serial and v2.06". When I place it in the cradle, it changes to USB. I cannot boot it, I can't upgrade it ( connection error). What an I missing?
Re: Help Please, BlueAngel not booting up, not able to upgra
todixy said:
I have a qtek9090 and it will not boot up, it says "Serial and v2.06". When I place it in the cradle, it changes to USB. I cannot boot it, I can't upgrade it ( connection error). What an I missing?
Click to expand...
Click to collapse
Do you have activesync 4.1 installed?
And beware that windows firewall may cause some problems too.. so turn it off before you start upgrading just to be sure.
one lesson learned from upgrading smartphones is to disable activesync:
task manager> end process wcescomm.exe and all ms office
>>disable anti virus and fire wall which also means disconnecting from the net. then try if flash is succesful
xykosomatik said:
one lesson learned from upgrading smartphones is to disable activesync:
task manager> end process wcescomm.exe and all ms office
>>disable anti virus and fire wall which also means disconnecting from the net. then try if flash is succesful
Click to expand...
Click to collapse
I remember closing those processes when I made my first flash... but look at the wiki from TuMa 1.2 for example:
"Flash the ROM.
* If your device is not recognized, make sure you use a fresh Windows XP SP2 or Windows 2000 SP4 installation with Active Sync 4.1."
But it's also true that it may not apply in this case. Anyway.. just trying to help.
Hello All, many of you just keep asking how to do that and this, you do not use search, so im making this Guide which will help you
Things You Should Know:
Things Which Will not work after Upgrading to WM5, WM 6 or WM 6.1 :
Htc Himalaya Backpack (read below)
STK will Not function
There is no SDHC Drivers for any Version of ROMS for HTC Himalaya Yet
To Have 30.53 MB of storage Go here
Upgrading:
Windows XP :
Requirements :
Windows XP
Microsoft ActiveSync 4.5
Minimum of 256 MB of RAM
and some patience
Start your device in bootloader mode by pressing and holding down:
DPad + PowerButton + ResetButton
After a second release Reset Button, then release the rest of them.
Your screen will show word "Serial" at the top.
You are in bootloader mode now.
Place your device in the cradle/USB Cable, ensuring that the cradle/USB
is plugged directly into a USB port on your PC and not to a hub
and that the power supply is connected to the cradle/USB.
It is also a good idea to disable any screensavers on your desktop PC.
Once your device is cradled, the text on the screen will change to "USB".
Run HimaUpgradeUt_noID.exe and follow the instructions
Sit back and wait for the Congratulations screen to be displayed
on your PC.
Your device will still be displaying 'Upgrading radio stack, please wait' but as long as the PC says it is done, then its all OK.
Detach your device from the cradle/USB.
Now you have to hardreset your device :
Press Reset Button and hold down Camera Button + Record Button.
Hold them pressed until the "Boot Options" menu appears on the screen.
Select the options as follows:
(for selecting use Record Button, change values with Camera Button)
Enable KITL -> NO
Clean Registry Hive -> YES
Format Storage -> YES
When done, press DPad/Action Button and wait until OS starts.
Click to expand...
Click to collapse
Windows Vista 32-Bit :
Requirements :
Any Version of Windows Vista 32-Bit
Windows Mobile Device Center (Latest Version)
and a little computer knowledge
Before starting: Your device needs to be connected to the PC, and in BOOTLOADER mode.
Step 1 of 16: Extract the attached zip file to a memorable location on your machine (e.g. the desktop). This is the Activesync 4.5 RTM USB driver.
Step 2 of 16: Run 'Windows Mobile Device Center', and click 'Connection Settings'.
Step 3 of 16: Uncheck the 'Allow USB Connections' box, and select 'OK'.
Step 4 of 16: Run 'Services' by clicking the Start Orb and typing 'Services', and ensure the 'Windows Mobile-based connectivity' and Windows Mobile 2003-based connectivity' services are started. If they are not, click the service name and press the 'play' button on the top bar.
Step 5 of 16: Load 'Device Manager' by clicking the Start Orb and typing 'Device Manager'. Expand the 'Mobile devices' section and click the 'HTC USB Sync' (or similarly named) item.
Step 6 of 16: Click the 'Action' menu and select 'Update Driver Software'.
Step 7 of 16: Click 'Browse my computer for driver software'.
Step 8 of 16: Click 'Let me pick from a list of device drivers on my computer'.
Step 9 of 16: Click 'Have Disk'.
Step 10 of 16: Click 'Browse', and browse to the location where you extracted the ZIP file in Step 1.
Step 11 of 16: Double click 'wceusbsh.inf'.
Step 12 of 16: Select 'HTC USB Sync' from the list, and click 'Next'.
Step 13 of 16: Wait while your driver is installed.
Step 14 of 16: Run 'Task Manager' by clicking the Start Orb and typing 'taskmgr'. Then find the 'WMDC.EXE' item, and click 'End Process'
Step 15 of 16: Install your update! Everything should now run fine! You just need to bear in mind the final step when you want to start syncing normally again...
Step 16 of 16: In 'Windows Mobile Device Center', re-enable the 'allow USB connections' checkbox you disabled in Step 2.
Click to expand...
Click to collapse
If MODS find this Helpful, Please Sticky This
muckelmaus Wrote :
As I tested some ROMs with my himas. Only the CF-slot will not work, 'till someone will write a working driver for it.
There are no probs to use the backpack battery and the vga-video funktion, so far. Two out of three, thats not bad, I think.
Click to expand...
Click to collapse
Backpack problem
Things Which Will not work after Upgrading to WM5, WM 6 or WM 6.1 :
* Htc Himalaya Backpack
As I tested some ROMs with my himas. Only the CF-slot will not work, 'till someone will write a working driver for it.
There are no probs to use the backpack battery and the vga-video funktion, so far. Two out of three, thats not bad, I think.
thanks for the info, i havent tested it my self thats why i didnt knew, edited the First post with this info
Im a noob
Hi I am a noob and followed this guide but it did nothing...
Basically I have a 02 XDA II - it is locked and I want to upgrade it to windows 6/6.1 - I have been reading through the forum for a couple of hours now covering the wiki for himalays and other things.
I followed the steps on this - but nothing has been upgraded. So I guess this isn't how to upgrade to wm6?
So frustrating cos I can't seem to find the instructions on how to do it.
I believe its a rom i need right?> how do i put it on?
Should I unlock the xda first? (havent worked that out yet) or upgrade to wm6 and then it will be unlocked anyway?
Please please help I have been reading loads and trying to not ask obvious thigns.
i donot know if its SIM locked or not...try givinf xda2unlock a try
second, to upgrade you need a ROM, there are MANY roms in this Himalaya WM6 Forum...many of them have detailed instructions
it wont be any harm if you upgrade first...try giving it a shot and tell me
Ather
I have also performed 'Unlock Wiz/Himalaya' but all I get is 'The phone seems unlocked already' - but it is not unlocked - any advice with this also?
try to upgrade the rom simply, if u get stuck, we all are here
I am struggling through trying to work out how to unlock my sim and then flash WM6 onto my 02 XDA ii which therefore is a himalya - says PH10b in model no.
Anyway Im following one of the guides (http://wiki.xda-developers.com/index...0for newbies) and it says I have to establish whether it is a G3 or G4 or else Ill brick it and probably throw myself out of my window.
So I performed a soft reset and got the following information in red letters when I do it.
R 1.10.00
G 1337. 18
1.60.00WWE
I just don't know if it is a G3 or G4 and can't afford to brick this phone - so please could someone help me so I know which intructions to follow?
I will send best reply a stick of rock from Blackpool (famous for rock - its like sugary concerete).
Sorry to be unclear - it is sim locked - it has horrible 02 logos all over it.
Bastards.
Anyway it is sim locked and wm 2003 i think.
Im not clear about how to install a rom - i did update the drivers putting it in boot and then updating driver from what i downloaded - which I think was to resolve and issue with vista/xp as i am using vista.
Right now im trying to work out G3/G4 because i found what seemed to be a good instrucitonal post
lol, the xda2 doesent has g3 or G4 ... so flash away
So how do i unlock it and then install WM6?
Is there a step by step guide?
It is sim locked and i want to unlock it and install wm6
the Branding has nothing to do with the Simlock, my Himalaya is from O2 too, and all it had was Branding, no simlock.
I'm currently using E-Plus as my Provider, and i did not have to circumvent any simlock before flashing WM6.1 onto the Device.
Also, if it DID have a Simlock, it has probably worn off by now, since the Device is already older than 2 years...
I have managed to unlock the sim now thanks to the wonderful people here but still have no clue how to install wm6?
congrats , just download any ROM and enjoy flashing it
do i just download a wm6 file and put it onto my pda and then execute it? double click it? is it that simple?
Can u spefically tell me how to implement a rom?
i assume i download it but then what?
I am thinking I'll just brick it - then spend months on here asking for help... Id rather just ask beforehand and find out how to do it.
it's exactly like ather said, you downloaded the ROM, now you can flash it to your XDA.
Just do it like it says in the Readme and you should have no Problems whatsoever
Strange
I had an old Qtek 2020 and flashed it successfully to WM6.1 No problems exept...... the phne does not conect to the correct provider. The SIM is for the Belgian BASE provider whereas it connects always to ORANGE. When I put the SIM in my new Diamond or in my very old Nokia phne it connects to BASE as intended. I reflashed to the original Qtek WM 2003 SE and same thing. Reflashed again to WM6.1 ans still it only wants to connect to ORANGE ??? What am I overlooking?
BTW if I donload the list of providers there isno BASE provider. If I download the list on my Diamond it appears whithout any problem.
it could be because of the Network Manager has old settings, try setting it up manually
i've got a qtek 2020i
but something went wrong with an upgrade downloaded from qtek netherlands.
now i can't turn it on it doesn't work anymore
in teh screen i can read
serial
v1.01
or when in the cradle usb
plz help out here i can't fint it with active sync.
inreally need the damn thing. it's like losing my right hand
it came with winmobile 2003 ce
maybe i need a more resent version.
I am not an expert by any means but the fact that it switches to USB when cradled means it should be reflashable with a new ROM, search the o2.ie site for their most recent ROM. Not saying their offering is the most recent but it should get you going again
i searched but i can't find anything.
i don't know were i can find it
and if i do how does it work?
my telephone is using Orange / T mobile
Ok I had the same problem recently and managed to fix it using mtty.exe, and a working flash file.
The procedure goes like this:
Get mtty.exe, ( I found a copy on a file sharing site using google ).
Open Activesync and disable the USB option in connection settings, you'll need the usb port for mtty.
Put the device in the cradle, and check that it says USB , (it may say serial 1.01 at this point, don't worry, this happened on mine).
Run mtty.exe, and select USB, this will open a terminal window allowing you to communicate with the device. If you don't see USB as an option then exit mtty and try plugging the USB cable into another port.
Once you have the terminal window open, type task 28 and press enter, this will format the DiskOnChip.
Once this is complete and there are no errors, exit mtty, and run the upgrade, this should hopeully restore your Alpine.
I have definitely got the blue angel. It is an O2 Xda 11s.
I have downloaded the how to flash your BA pdf by D-Two, and followed the instructions. It gets through to the stage where it's about load the software onto the phone, and then it quits saying that he phone is not the appropriate model.
device information
Operator version: PDAViet.net
ROM version: 6.01.10 VH
ROM date: 07/08/08
Radio version: 1.06.00
ExtROM: diamond (01)
RAM size: 128 MB
Flashing eyes: 32 MB
Storage size: 60.3 MB
At present I have windows mobile 6.1.
And suggestions please?
for upgrading, you use the MAupgradeut_noID.
that program avoids country id errors but it was originally made for the magician, hence MA, whereas the original BA upgrade utility is called BAupgradeut.
that is why you get that error. you have to put the device into bootloader mode before connecting it to the pc and before starting maupgradeut_noid, that way, you avoid the device id check.
make sure to follow the correct upgrade procedure, found here: http://forum.xda-developers.com/showthread.php?t=630416
These are the instructions I used;
Temporarily remove your SD Card (it may work for you with the SD card still in your BA, but you may not be able to enter USB mode when cradled).
Put your device into Bootloader mode by pressing and holding the "Power" & "Record" buttons, and then press the Reset Button. Help me with this step
Connect the phone to the sync cable/cradle. sarcasm ahead Note: Did you see a sign out in front of this point that said: "You can flash using BlueTooth connection?" You know why you didn't see that sign? Because you can NOT FLASH using BlueTooth!
Now you can execute the installer file. (something like "MaUpgradeUt_noID")<--------------- Used This
Here is the screen just before boarding the software.
http://i627.photobucket.com/albums/tt356/Pterodactyl_2012/ba1.png
And here is the error message.
http://i627.photobucket.com/albums/tt356/Pterodactyl_2012/ba2.png
nope, you are not using the proper maupgradeut_noid, because that would show a magician on the left, whereas your pictures clearly show a BA, so download the Chef_Tony RUU from my signature and try that. it has the right maupgradeut_noid, that will avoid errors like that.
Chef_Tony said:
nope, you are not using the proper maupgradeut_noid, because that would show a magician on the left, whereas your pictures clearly show a BA, so download the Chef_Tony RUU from my signature and try that. it has the right maupgradeut_noid, that will avoid errors like that.
Click to expand...
Click to collapse
yep, you were right,,,,,,, BUT same error message;
http://i627.photobucket.com/albums/tt356/Pterodactyl_2012/xda4.png
you are trying to flash using vista/7 have you read d-two's manual about that, with the customized driver and everything?
alternatively try a windows xp pc and follow the tutorial in my signature (the read first link)
and make sure, that you don't copy around the rom too much. download the rom and the ruu directly to the pc you flash from and use it from that folder directly. i use windows 7 on my main pc and can only flash from my netbook which runs windows xp, and due to too much copying, i had similar errors, because after copying the rom to a usb flash drive without problems, still the crc changed.
don't worry, your case is far from hopeless, but you seem to be unlucky and go through every problem there is
Chef_Tony said:
you are trying to flash using vista/7 have you read d-two's manual about that, with the customized driver and everything?
alternatively try a windows xp pc and follow the tutorial in my signature (the read first link)
and make sure, that you don't copy around the rom too much. download the rom and the ruu directly to the pc you flash from and use it from that folder directly. i use windows 7 on my main pc and can only flash from my netbook which runs windows xp, and due to too much copying, i had similar errors, because after copying the rom to a usb flash drive without problems, still the crc changed.
don't worry, your case is far from hopeless, but you seem to be unlucky and go through every problem there is
Click to expand...
Click to collapse
Okay yes, I should have said this. I am using windows seven on a Lenovo N500 4233 32g. The problem is, trying to get hold of an XP machine. Have you tried running this programme in compatibility mode? I will have a look at your instructions and see where I get to.
Thanks for your help,
Is d-two's manual, the HTC service manual in you sig?
no, it is to be found here: http://forum.xda-developers.com/showpost.php?p=5456317&postcount=6
compatibility has nothing to do with it, neither has the xp mode or any virtual machine, because there must be suitable windows 7 drivers present. but i cannot help you with his tutorial, since i use windows xp for flashing and have never successfully used windows 7 for flashing.
the htc service manual in my sig is the official htc manual for hardware repairs, you can learn to disassemble the device there and have a list of spare parts
Hello !
I need help please, my phone don't want to get on Bootloader mannualy and I don't have a Windows PC.
Thanks !
mister-gwada97one said:
Hello !
I need help please, my phone don't want to get on Bootloader mannualy and I don't have a Windows PC.
Thanks !
Click to expand...
Click to collapse
read my sig, flashing from phone... have luck
But I can't get this step:
reset your device and within 3 seconds push together the Vol_Down + Back button (the one on the right above the hangup button) and keep pressed until the boot loader appears (the one with the color stripes)
I have a broken button..
so you have to use mtty, but you need anyway a windows based PC (as I know) to install crude usb drivers...
Ok, Thanks for your help
I use VirtualBox on Arch Linux with Windows XP... I can't flash directly on the cell as ActiveSync doesn't recognize the device, but maybe MTTY, with different drivers, works
I use virtual machine with windows xp,, to use mtty on my windows 7 based pc.
All you need is an virtual machine,,
dravik said:
I use virtual machine with windows xp,, to use mtty on my windows 7 based pc.
All you need is an virtual machine,,
Click to expand...
Click to collapse
yep nice trick, anyway I remember that there is a freeware WM5/6 driver working with unix/linux that put the device (also the internal memory) as disk drive, so you can see both memories as "just" plugged usb drives... I rememeber because I used this trick with my old dopod & FreeBSD
suiller said:
yep nice trick, anyway I remember that there is a freeware WM5/6 driver working with unix/linux that put the device (also the internal memory) as disk drive, so you can see both memories as "just" plugged usb drives... I rememeber because I used this trick with my old dopod & FreeBSD
Click to expand...
Click to collapse
He need to flash his Diamond, not to copy files on it
Mod. edit: not dev related, moved to general