Hy everybody.
I read somewhere that I should "format" my Trinity before flashing ...
After having searched this site, I saw something around "mtty" in the bootloader.
Does anybody can confirm those points :
1.- It is worth fomatting before flashing ;
2.- There is no risk of bricking doing that
3.- The prodedure to follow on my Trinity, is to enter booloader mode, connect with the USB cable, connect from the PC using "mtty", and type some command I can't remember nor retrieve :-(
leinad said:
Hy everybody.
I read somewhere that I should "format" my Trinity before flashing ...
After having searched this site, I saw something around "mtty" in the bootloader.
Does anybody can confirm those points :
1.- It is worth fomatting before flashing ;
2.- There is no risk of bricking doing that
3.- The prodedure to follow on my Trinity, is to enter booloader mode, connect with the USB cable, connect from the PC using "mtty", and type some command I can't remember nor retrieve :-(
Click to expand...
Click to collapse
i must say that i've never read that information or ever formated my device before flashing .
Where did you read that?
Windoze9t8 said:
i must say that i've never read that information or ever formated my device before flashing .
Where did you read that?
Click to expand...
Click to collapse
maybe on an italian forum....
not need to use "mtty" before flash new rom, only need (if want, not necessary) an HardSPL!!!
Install Olipro Hard SPL 1.20
Then try the mtty procedure:
1) Download mtty from this forum: http://wiki.xda-developers.com/uploads/mtty.exe
2) go into bootloader: Hold side Camera and POWER buttons together and reset with stylus.
3) Disable USB Connection in ActiveSync and connect trinity
4) Star mtty - Port: USB - Baud: 115200 - Press Enter
5) enter these commands
- task 32 Enter
- task 28 Enter
- task 2A Enter
- info 8 Enter
- task 8 Enter
6) Try to reflash with an original htc rom (if you can, flash a wm5 one...)
Windoze9t8 said:
Where did you read that?
Click to expand...
Click to collapse
I read this information here : In the answer from Eliasweb to moustik_2002, in the second line
"I suggest you to format with mtty and reflash the rom !"
I asked to Eliasweb how to do that, but I did not receive any answer from him.
My question is "Since it seems possible to format, is there any interest to format before flashing or not ?"
leinad said:
I read this information here : In the answer from Eliasweb to moustik_2002, in the second line
"I suggest you to format with mtty and reflash the rom !"
I asked to Eliasweb how to do that, but I did not receive any answer from him.
My question is "Since it seems possible to format, is there any interest to format before flashing or not ?"
Click to expand...
Click to collapse
see what mtty do:
http://forum.xda-developers.com/showthread.php?t=219184
Abu RaGHaD said:
Install Olipro Hard SPL 1.20
Then try the mtty procedure:
1) Download mtty from this forum: http://wiki.xda-developers.com/uploads/mtty.exe
2) go into bootloader: Hold side Camera and POWER buttons together and reset with stylus.
3) Disable USB Connection in ActiveSync and connect trinity
4) Star mtty - Port: USB - Baud: 115200 - Press Enter
5) enter these commands
- task 32 Enter
- task 28 Enter
- task 2A Enter
- info 8 Enter
- task 8 Enter
6) Try to reflash with an original htc rom (if you can, flash a wm5 one...)
Click to expand...
Click to collapse
Thank you Abu RaGHaD
Could you please tell me where does this procedure come from ?
If I understand well :
- task 32 => "Checks the security level. Unpriviledged: "Level=0xFF", SuperCID: "Level=0""
- task 28 => "Format Storage (OS partition)"
- task 2A => "Check NAND flash and mark bad blocks. (Requires Level!=0xFF)"
- info 8 => "Returns information on blocks and partitions"
- task 8 => "Resets the device"
Is it possible to know what do all these action mean exactly ?
Are they more or less "dangerous" for my Trinity ?
Is there any risk to brick the device ?
On the contrary, is this a mean to "recover" some "lost" memory space ?
Best regards
No need to format when your'e using an RUU to Flash the ROM.
Formatting is only necessary when using pdoc-read/write method which was by far gone.
I always do a hard reset before flashing...it works for me,this way seems like I can avoid some issues that later on I read that people come across....but this is just me.
Latest MTTy version
Hello guys ,
i would like to know wich is the latest Mtty version .
The posted one by Ervius (i'm going to test your latest coocked rom ) seems to be v. 0.01. Is it the latest ?.
Regards ... .
i never hard reset or format before flashing and never have problems.. ha up to you, bro, but i think you're just complicating the beauty of flashing your trinity.
racerx_ said:
i never hard reset or format before flashing and never have problems.. ha up to you, bro, but i think you're just complicating the beauty of flashing your trinity.
Click to expand...
Click to collapse
True ... very true ..
racerx_ said:
i never hard reset or format before flashing and never have problems.. ha up to you, bro, but i think you're just complicating the beauty of flashing your trinity.
Click to expand...
Click to collapse
used mtty only once, when bricked my device (before install on it DES hard spl, and during flash cooked rom, my pc turned off at 45% of flash....)
but yes, no need to format.
Related
i wonder if anyone could help me with my problem!
i can't upgrade / Install RADIO ROM (any) in my UNIVERSAL. what happens is that it doesn't starts and when rebooting it says NO GSM where the versions are mentioned in red.
my universal goes in the bootloader mode properly and the update or RADIO ROM Starts; but it stays on 0% and doesn't move ahead. after a while and error comes ERROR 114. Can't update RADIO ROM.
This all happened when i was trying to downgrade my radio rom from 1.14.01 to 1.13.00 this morning and it stopped at 66% with giving this messege.. cannot upgrade radio rom... since then i am unable to re-install radio rom. However i am able to install WIN CE ROM and EXT ROM but not radio ROM.
can you guys help me somehow?
farehmani.
farehmani said:
i wonder if anyone could help me with my problem!
i can't upgrade / Install RADIO ROM (any) in my UNIVERSAL. what happens is that it doesn't starts and when rebooting it says NO GSM where the versions are mentioned in red.
my universal goes in the bootloader mode properly and the update or RADIO ROM Starts; but it stays on 0% and doesn't move ahead. after a while and error comes ERROR 114. Can't update RADIO ROM.
This all happened when i was trying to downgrade my radio rom from 1.14.01 to 1.13.00 this morning and it stopped at 66% with giving this messege.. cannot upgrade radio rom... since then i am unable to re-install radio rom. However i am able to install WIN CE ROM and EXT ROM but not radio ROM.
can you guys help me somehow?
farehmani.
Click to expand...
Click to collapse
Radio rom upgrades are definately more reliable with the original cable. I have read somewhere in these forum that the mode of radio ROM upgrade is different from other ROMs (CE and Ext rom) this is the reason why it takes more time than the CE rom although the later is much larger in size. I suggest you try again if possible on a different PC. For some strange reason I can upgrade my Radio ROM only in my office PC.
d_ranade said:
Radio rom upgrades are definately more reliable with the original cable. I have read somewhere in these forum that the mode of radio ROM upgrade is different from other ROMs (CE and Ext rom) this is the reason why it takes more time than the CE rom although the later is much larger in size. I suggest you try again if possible on a different PC. For some strange reason I can upgrade my Radio ROM only in my office PC.
Click to expand...
Click to collapse
i have tried on 3 different computers but it doesn't work. also with original cable too. it is definately a software problem as no physical damage was made to my device. there must be something that fixes it.
still while upgrading Error 114. (UNABLE TO UPDATE RADIO ROM)
i wish i could find any help with this...
Farehmani
farehmani said:
i have tried on 3 different computers but it doesn't work. also with original cable too. it is definately a software problem as no physical damage was made to my device. there must be something that fixes it.
still while upgrading Error 114. (UNABLE TO UPDATE RADIO ROM)
i wish i could find any help with this...
Farehmani
Click to expand...
Click to collapse
Have you tried putting the unit into Bootloader before you start the upgrade - I find that more reliable?
apd said:
Have you tried putting the unit into Bootloader before you start the upgrade - I find that more reliable?
Click to expand...
Click to collapse
I too find that upgrade in Bootloader is more reliable.
To let you into a little secret.. I ALWAYS flash now in Bootloader mode.. I have only had a couple of "bad flashes" but all of them were direct from a running OS...
I have sent you a pm, that should solve your issue. Please check your pm's...
Take care,
-Jwrightmcps
farehmani said:
i wonder if anyone could help me with my problem!
i can't upgrade / Install RADIO ROM (any) in my UNIVERSAL. what happens is that it doesn't starts and when rebooting it says NO GSM where the versions are mentioned in red.
my universal goes in the bootloader mode properly and the update or RADIO ROM Starts; but it stays on 0% and doesn't move ahead. after a while and error comes ERROR 114. Can't update RADIO ROM.
This all happened when i was trying to downgrade my radio rom from 1.14.01 to 1.13.00 this morning and it stopped at 66% with giving this messege.. cannot upgrade radio rom... since then i am unable to re-install radio rom. However i am able to install WIN CE ROM and EXT ROM but not radio ROM.
can you guys help me somehow?
farehmani.
Click to expand...
Click to collapse
apd said:
Have you tried putting the unit into Bootloader before you start the upgrade - I find that more reliable?
Click to expand...
Click to collapse
yes... i have never tried to flash anything while being in the os. always switch my device to the bootloader first. I have BootLoader 1.01
Please help!!
apd said:
Have you tried putting the unit into Bootloader before you start the upgrade - I find that more reliable?
Click to expand...
Click to collapse
How to put the PPC in Bootloader (Qtek900)?
myname70 said:
How to put the PPC in Bootloader (Qtek900)?
Click to expand...
Click to collapse
Read the wiki - the answers are in there.
apd said:
Read the wiki - the answers are in there.
Click to expand...
Click to collapse
the problem is still there....
i have tried circumvent bootloader password too... and getting error like Win32 Error, Cannot read from the specified device when HEX of password is placed on the memory field of WinDbg.
Tried Another solution for NO GSM but no luck !!
okay here goes; your quoted link had point#5 for no GSM when booting so i followed it as given below.
Pls. see the comments in (( )) for how i conduct these steps and what value is returned.
[[[[--->
Problem 5: Device shows NO GSM when booting (( I'm having this problem ))
1) The radio stack is screwed, you don't get GSM signal and the phone says unknown SIM status
2) Device won't start after trying to unlock it with HTC Universal Unlocker (HTC_Uni_SIM_Unlock_v1)
Here is how to fix it:
1)Disable activesync on your computer by right click on activesync icon -> connection settings -> uncheck "allow USB connections". (( Done! ))
2)Put your Hermes (( Universal )) in bootloader mode
3) Connect device to computer using USB cable. (( Done with Original Cable ))
4) Open mtty.exe and select USB port, then connect.
Hit enter twice, you will see the "USB>" prompt. (( Okay but i usually get the USB> prompt with single hit of Enter ))
Type the following commands (do not copy paste!!!) (( I type them ))
USB> password 0000000000000000 (( Returns: HTCSPass1.CMˆËHTCEUSB> ))
USB> set 1e 1 (( Returns: USB> ))
USB> erase a0040000 c80000 (( Returns: HTCST ÚÈÒHTCEUSB> ))
USB> erase a0cc0000 c80000 ((Returns: HTCST ÚÈÒHTCEUSB> ))
USB> erase a1940000 640000 (( Returns: HTCST ÚÈÒHTCEUSB> ))
USB> set 1e 0 ((Returns: USB> ))
(( Then i close the window of MTTY and proceed to step 5 ))
5) Reset your phone and put it back in bootloader mode (( Here i take my Universal off the usb cable, soft reset it with the stylus and without letting it to boot i switch it into the bootloader mode again and get "Serial & v1.01" on the screen's header and footer ))
6) If your bootloader version is different than 1.04 then Flash Bootloader version 1.04 (( I simply ignore this step as this could be for Hermes users only not for UNIVERSAL Users - Pls. correct me if i'm wrong ))
7) Flash the patched radio used to simunlock the Hermes (( I do it with HTC_Uni_Unlock_v1 it has radio version 0.00.00 BUT still it gets stuck at 0% and after sometime gives the same error 114. Cannot Update Radio ROM ))
Your phone should be alive again (( Its Not ))
<---]]]]
i don't think i'm doing anything wrong here... just the step 5 of bootLoader Update to 1.04...
what comes in your mind ???
i'm desperately missing my pda. its begun to hurt now... please help me rescue my baybee....
farehmani
farehmani said:
i don't think i'm doing anything wrong here... just the step 5 of bootLoader Update to 1.04...
what comes in your mind ???
i'm desperately missing my pda. its begun to hurt now... please help me rescue my baybee....
farehmani
Click to expand...
Click to collapse
Don't worry, mate, you're almost there...
Don't worry about the bootloader version, that is just for the Hermes (Universal will be 1.01 or under for G3, 2.1 for G4). If it's under 1.01 it would be worth upgrading to 1.01 which you can find on the ftp.
SpyderTracks said:
Don't worry, mate, you're almost there...
Don't worry about the bootloader version, that is just for the Hermes (Universal will be 1.01 or under for G3, 2.1 for G4). If it's under 1.01 it would be worth upgrading to 1.01 which you can find on the ftp.
Click to expand...
Click to collapse
glad to know about my being almost there... still i wonder whats keeping me away from retaining my device...
i have already got BootLoader 1.01...
what other method should i apply to get it working again?????
I have the same problem, but not in Universal, but apache, jwright help me.
i have the same problem can smeone help
Try this
"Type "task 28 55aa" and hit enter.
This will restore the DOC partition to its original layout and delete all data
including the ROM!
Once finished you must use the "Original OEM ROM" (i.e. JASJAR WWE
1.30.76) that is made for your device and update with it (CE,Extended
and Radio).
Also if your device bootloader version is lower than "v 1.01" you should
update that first (before installing the OEM ROM, but NOT before "Task
28 55aa").
After this is complete you may then use your device again.
Please let me know how things work out for you...
Take care,
-Jwrightmcps"
It solve me...
i am having the same problem with exec it shows me no gsm and when i go to the device information it does not shows the radio ver and my phone imei is 0 can someoe please tell me how do i solve the problem i had read this tread but not understand it can someone please explane me how do i solve the problem
shedragon said:
"Type "task 28 55aa" and hit enter.
This will restore the DOC partition to its original layout and delete all data
including the ROM!
Once finished you must use the "Original OEM ROM" (i.e. JASJAR WWE
1.30.76) that is made for your device and update with it (CE,Extended
and Radio).
Also if your device bootloader version is lower than "v 1.01" you should
update that first (before installing the OEM ROM, but NOT before "Task
28 55aa").
After this is complete you may then use your device again.
Please let me know how things work out for you...
Take care,
-Jwrightmcps"
It solve me...
Click to expand...
Click to collapse
thanx for your suggestion!
i had tried this already... but the problem is beyon this...
i discussed with pof and he said that somehow i screwed up with the qualcomm chip where the radio bootload resides. so it needs replacement.
anyways... thanx budd... i appreciate your support too...
regards...
my hermes having this problem also ((
I m having big troubles with my Universal. I m stuck in the Bootloader screen. When I try I hard reset (pressing 2 softkeys and reset and than 0 he says 'clearing now' for only one second and than switches back to the bootloader screen! I ve tried to upgrade it with MAUpgrade_NOID.exe. He than upgrades I think my OS only but after this a hard reset doesn t help! I keep getting stuck in the bootloader screen! I ve also tried a hard reset without the SIM and SD card but this don t help either......
Now what.......
have you tried set 14 0
I saw something like that. Can you explain how to a bit more specific?
sanderh said:
I saw something like that. Can you explain how to a bit more specific?
Click to expand...
Click to collapse
Hi,
Read this thread and follow the step by step instructions to reset your DOC Table.
http://forum.xda-developers.com/showpost.php?p=1097645&postcount=4
After completing the above please re-flash the Rom you wish to use.
When flashing Roms to your Uni, it is always best practice, to remove the SD Card and enter BootLoader mode before flashing.
Cheers,
Beasty
Try the little tool attached. It's from the wiki.
Here's how to use:
1. disconnect USB cable from your device
2. disable USB connection in ActiveSync
3. reconnect USB cable
4. wait some 30 seconds
5. run the tool
6. If successful, device will boot itself.
Has worked for me every time.
Psi
Had this issue today. Couldn't flash any rom and was stuck on the bootloader screen. Try flashing a shipped rom for your phone. That helped me. After flashing original I was able to flash WM6 rom using ROMUpgradeUt.exe.
Try a diferent cable.
If you get when connecting for a second usb, than changed i to the serial, try a diferent cable - its normal miniusb.
Then go to wiki and download UNI_ExitBootloader.exe.
Maybe will work.
If yes give a masage.
KR.
Lukasz
beast0898 said:
Hi,
Read this thread and follow the step by step instructions to reset your DOC Table.
http://forum.xda-developers.com/showpost.php?p=1097645&postcount=4
After completing the above please re-flash the Rom you wish to use.
When flashing Roms to your Uni, it is always best practice, to remove the SD Card and enter BootLoader mode before flashing.
Cheers,
Beasty
Click to expand...
Click to collapse
Thanks man, that really helped. My qtek9000 got stick at the bootloader's screen and i couldnt perform an upgrade. I followed ur instructions and now it is upgrading. waiting for the results.
thanks again
yeap, everything went fine.
Completely stuck without any UBS communication
Hi everybody,
Since i tried (yesterday) to flash a new UNIVERSAL 2.12 WWE ROM, i 'm stuck in Bootloader. I had this bloody Country ID error and after that, the USB connection between my Universal and my PC went wrong and ... i tried all the solutions given here and there :
1/ an exitboolader.exe tool
2/ the mtty option
3/ tried to kill all the process linked to AS in a way or another
4/ made several Hard Reset - connection - changing cable and so on ...
The main problem is that Windows XP is not able to recognize my Universal anymore SO ... i can't even try the solutions above based on an exiting commication thru USB between my PC and my PPC ...
I only have : "Serial" and "V1.0" on my pocket PC
Any idea to establish an USD relation between the universal and my PC ?
Pls help ... i missed this bloody device ;-/
Hi!
I was using Newplow's WM6 038 ROM with my N560.
Yesterday I tried to write another ROM(WM6 038 with 8MB pagepool) but during update got an error.. It said it just failed.
Now my N560 is stuck on booting screen(people climbing mountain..)
I tried Warm, Cold, Hard reset but with no luck.
Even the power button doesn't work so I had to remove battery. When I insert battery it powers on by itself.
I can enter bootloader screen by pushing power+record button so I tried to copy rom image file to SD card but it doesn't work.
I tried two ROMs(OS_213U.nbf from Original WM5 ROM and Newplow's) and 3 SD Cards(2GB SD, 1GB MicroSD with Adopter, 16GB SDHC)
Is there any recovery tutorial in bootloader mode?
Help me please!
Sorry for my English.
Have you tried flashing a ROM through the computer rather than the memory card? Try going into bootloader and flashing that way rather than the card.
The pagepool ROM is meant for N560s that have been upgraded to 128Mb RAM... have you upgraded the internal RAM to 128Mb? If you have not, then this may have caused your problem.
I had this problem when flashing to 038 normal RAM (from 035). A hard reset reset to the normal start screen, but nothing worked. However, trying a new burn with the Loox flash tool restarted the process and it worked. I found the cure was to make sure you hard reset the N560 before doing a burn. It appears to be that you have to do this to release enough RAM for the burn program to reside and for "working" storage. You may not have done this.
I suggest you try simply re-running the flashtool with SD/SDHC cards removed, battery in place, on the cradle via your PC, even though it appears stuck. The signals coming from the USB link may wake up the bootloader routine in the N560?
Solved the problem! Thanks for your comments!
I asked same question in Newplow's guestbook and the person who made pagepool rom answered. I used MTTY to revive my pda.
What I did is in below post. need translation
http://4pda.ru/forum/index.php?showtopic=55274
Hi all,
I have the same problem. N560 is stick on the himalaya picture. I tried to falsh from WM5 to new rom for Wm6 and after installation the pda stuked. So I did a warm reset and now only the start picture is apperaing. Problem is that battery is down now.
Can someone give more info on the process followed to revive the PDA ? I just cannont read russian (may be Jinsu77 ?)
Many thanks for support in advance
same problem here please please please someone help us
the only thing i can do is the l c:\os_213u.nbf on mtty program and nothing else happend to the machine
sorry for my english
read, and pay attention here:
[email protected]@p://a.mod-site.net/gb/u/newplow-1.html
POST 203.
It was me asking on Newplow's guestbook.
In case you're using Vista, you need some trick to be able to rom update. Read below.
http://www.modaco.com/content/windo...u-on-vista-it-can-be-done-the-ultimate-guide/
And then you need to download MTTY (I used version 1.42, got it by googling) and follow below steps.
(used google translation from 4pda.ru)
------------------------------------------------------------
For rom update without ActiveSync.
1) take this set of extract, copy it to the folder with the firmware.
2) copy the file os_213u.nbf example in C: \
3) You press the button Recorder + food and poke in the hole reset (Recorder button and hold until you eat dolphins)
4) plug the device to a PC, the Task Manager, shooting process - wcescomm.exe
5) Run mtty, choose Port: USB, connect.
6) If mtty caused an error and shut down, simply restart mtty, if not typed commands, then repeat the procedure with paragraph 3.
7) in mtty command, enter: (first letter in kommande - a little l l от слова from the word L L oad)
> l l c:\os_213u.nbf c: \ os_213u.nbf
Since the end of the process will be an inscription about the error, remove the device from the PC.
9) Run rom update, zhmete "next", until you see dolphins.
10), plug the device to a PC and program.
---------------------------------------------------------------
Hope this helps you all
in advance sorry for my english
I am doing all the instructions carefully and the mtty show this
Image Download Finish
OEMFlashWrite(A0000000h,8C200000h,1A0F023Ah)
Download Fails !!!
OEMFlashWrite error(12)
Error : DownloadImage return error (code = 0xFFFFFFFF)
the pda shos the dolphins and the full blue bar
after without change anything i run the PocketLOOX5xxFlashTool that i have in the same folder with the :
EnterBootLoader.exe
OS_213U.nbf (originally rom)
RUUServer.dll
RUU.dll
and the only thing i can see is that the PocketLOOX5xxFlashTool is trying to find the pda without any luck
also the pda is stucked in the same screen with the dolphins and the blue bar
do you see any mistake in this procedure
Helppp!!! please
tuluba said:
Helppp!!! please
Click to expand...
Click to collapse
have you closed EVERY process of activesync before proceding with mtty?
I close the wcescomm.exe and the rapimgr.exe is there anything else?
The pocket LOOX 5xx FlashTool cant connect with the N560 and at the and says that Error"The language in this Flash Image update (ENGLISH) differs from that on your device()!" and i have always english rom exept maybe from the last rom "the killer" with the 128MB rom that i dont know if it is an english or something else because the device never opens to see
After flashing in MTTY(don't care about error messages), you need to unplug your n560 from PC. And then proceed romupdate until you see the dolphin picture. Now you plug n560 to PC and cilck next and wait for a while.. Hope it works!
I change the language of the rom and it works
thank very much all of you
At all they have Probs with flash from SD Card: only use a Card with 512MB! I think a Card greater then can't read by the Bootloader....
hey.
i am compeletly new here. I have the same with my n560. I tried to upgrade to 128mb but after restart I see only climbing. I tried everything here but on dolphins afterr line is blue it is finished. that I am unpluging device. starting looxflastool for 560 and first is trying to connect by active sync and that when no connection made I see dolphins on left screen of flash tool window. than I am pluging again and after couple secs I see that: Error"The language in this Flash Image update (ENGLISH) differs from that on your device. I tried to change rom on every language but not working as well. PLEASE HELP
if that helps than i will add than on top when delfins i see on 560 is two lines. first is typed 2.14.G4 on second directly below is 2.15.
and when mtty 1.42 finishing flashing i see following:
Image Download Finish
OEMFlashWrite(A0000000h,8C200000h,0224002Ah)
Download Fails !!!
OEMFlashWrite error(12)
Error : DownloadImage return error (code = 0xFFFFFFFF)
Need help!!! Please!!!
I bricked my N560. I tried to downgrade from WM6 to WM5 and now I see only delfins and in the first line "2.14.G4" and in the second line "2.15"
What can I do?? How can I flash WM6 or WM5 ROM when there is no connection to the PDA????
ChrisDo said:
Need help!!! Please!!!
I bricked my N560. I tried to downgrade from WM6 to WM5 and now I see only delfins and in the first line "2.14.G4" and in the second line "2.15"
What can I do?? How can I flash WM6 or WM5 ROM when there is no connection to the PDA????
Click to expand...
Click to collapse
You can usually get back to the boot loader if you do a hard reset. I am sure you know how, if not you will find it in the FSC CDROM manual that came with the device. Let us know if this works? I have got stuck at this point too, so I know it works..... hopefully!
Hello,
My HTC 3300 is blocked on Windows start screen.
I have hard reboot my device and un screen with 3 color appear.
When i plug my device with USB cable, my computer play a song to inform my device is well connected.
But when i launch Artemis USPL, a popup appear with the message : "No Device Connected : Would you like to try copying again ?" Yes, No, Cancel.
I'm blocked a this step.
Can you help me ?
Thx
PS: Sorry for my bad english. I'm french guy.
hi guys,
i have the same problem....
I was trying for the first time to upgrade my Artemis!!! I DIDN'T DO THAT!!!!
Please help me!
TNH
USPL only work if you are in WM. It doesn't work at the booloader.
Zecanilis said:
USPL only work if you are in WM. It doesn't work at the booloader.
Click to expand...
Click to collapse
yes... i know
i am reading.... i am looking for a solution.
I read on the POF USPL guide that probably (Unfortunately ) this problem should be caused by same PDAmobiz tool!!!!
i am being funny!!!
yet another bricked artemis owner
Hi…
Newbie as I am I’ll try to explain to you what you should do...I’ve bricked mine artemis()but I think it is more related to hardware issue. You should try this:
1. Download mtty
2. Disable usb in active sync
3. Bring your Artemis to boot loader(pres start record +start phone+ reset)
4. Start mtty, choose usb and you’ll get popup up screen with direct access to your device.
5. Type this in command line of mtty (NOTE-YOU MYST TYPE IT/NO COPY PASTE WORKS)
Password BsaD5SeoA
6. You’ll get %indicator bar on your phone and then you can switch off mtty(do not disconnect your phone!!!)
7. Just start your ROM upgrade (it has to be factory rom if your phone is locked) and you should be ok.
(You need to have downloaded your original factory rom...For me it was O2 UK...do not start until you have it all)
If it fails, or you get some error massages, repeat all from point 2. Or follow on screen instructions...recovery etc...
If it fails,repeat,repeat,repeat....
Hope it will help you and save you from reading s... load of threads!!
P.S.
I’m still trying to bring mine to life….
zikizile said:
Hi…
Newbie as I am I’ll try to explain to you what you should do...I’ve bricked mine artemis()but I think it is more related to hardware issue. You should try this:
1. Download mtty
2. Disable usb in active sync
3. Bring your Artemis to boot loader(pres start record +start phone+ reset)
4. Start mtty, choose usb and you’ll get popup up screen with direct access to your device.
5. Type this in command line of mtty (NOTE-YOU MYST TYPE IT/NO COPY PASTE WORKS)
Password BsaD5SeoA
6. You’ll get %indicator bar on your phone and then you can switch off mtty(do not disconnect your phone!!!)
7. Just start your ROM upgrade (it has to be factory rom if your phone is locked) and you should be ok.
(You need to have downloaded your original factory rom...For me it was O2 UK...do not start until you have it all)
If it fails, or you get some error massages, repeat all from point 2. Or follow on screen instructions...recovery etc...
If it fails,repeat,repeat,repeat....
Hope it will help you and save you from reading s... load of threads!!
P.S.
I’m still trying to bring mine to life….
Click to expand...
Click to collapse
It solved my problem: I've played around with some dll's on my Artemis and it won't boot anymore.
Just one thing: you must type password BsaD5SeoA, cause it's case sensitive.
THANK YOU VERY MUCH!!!
Hi guys,
i fixed my problem!!!!!
i flashed an official ROM (1.12.405) using a SD card (512mb)
now i'm going to work with ARTEMIS_USPL!!!! WOOOOWWWW
owner of a brick called artemis
glad it helped you solve problem...
when I was young I use to poke with programming...
but that was looooong time ago (remember zx spectrum?48 kb ram..haha)now you got it in your pocket(working if you're lucky guy, not like me)
Any way, point is:
never give up!!!!
Yes, I agree with you: NEVER GIVE UP!!!!
I'd like to help you, i'm not expert people on this work...
I just read a lot of good indications on this forum.
Good Luck
Thanks man,
I'm trying to find another motherboard,before I start playing with this one.
Maybe you know where to get one for artemis?(arte 200)Or someone with broken screen not willing to repair it?
cheers,
z
I really need some help!
I was following the the post The DEFINITIVE MTTY Thread!! REVISED 02-11-09 and I made a mistake as follows;
blanktruth said:
Ok, first of all I did not think that it was this dangerous to use MTTY!.
I followed everything and came to these lines
---------------------
Cmd>task 8
Cmd>
---------------------
But after Cmd>task 8 my device restarted immediately before the second line Cmd> appears and I panicked and disconnected my device and pushed the wrong buttons while "Touch Diamond" logo was on the screen.
Now, nothing happens. I can not start from the beginning because I can not start the bootloader by pushing Vol Down and the small red reset button...
Is there anything else left for me to try? Or should I throw my HTC to garbage?
Click to expand...
Click to collapse
Now, I do not know how, but I brought my HTC to bootloader mode and now I can see it via MTTY. But I mistakenly formatted the Internal Storage while I was trying to bring my HTC to bootloader.
Is there any way to upload the DIAMIMG.nbh file to Internal Storage? Or should I follow a different way to save my HTC Diamond?
i have the same probnlem!! with my diam300
my bootloader show not Diam300 64m but only 64M on the first position in 3color mode... plz help
Connect the Diamond and run the customruu.exe from your desktop, this should work.
how to connect if i used mtty... its clear everything what i have on device storage and in bootloader canot start stock or developed rom...
if i want start hard spl its say invalid model it....
blanktruth said:
I really need some help!
I was following the the post The DEFINITIVE MTTY Thread!! REVISED 02-11-09 and I made a mistake as follows;
Now, I do not know how, but I brought my HTC to bootloader mode and now I can see it via MTTY. But I mistakenly formatted the Internal Storage while I was trying to bring my HTC to bootloader.
Is there any way to upload the DIAMIMG.nbh file to Internal Storage? Or should I follow a different way to save my HTC Diamond?
Click to expand...
Click to collapse
The only thing to do now is to flash back a stock ROM or use a custom ROM with the RUU.
Solved!...
Dom1n8tr1x said:
First of, your device is supposed to soft-reset after the "task 8" command and you should have been holding down the "Volume Down" and "Back Buttons" to begin flashing your new ROM. The whole idea of using MTTY is to format your Main Storage and flash a new ROM. Therefor you should have loaded the ROM that you wanted to flash onto your Internal Storage.
Click to expand...
Click to collapse
Thank you for your reply.
Actually I had uploaded the ROM to my internal storage, but during trying to bring my phone to bootloader mode, I formatted the internal storage...
Anyway, what I did now is, first I opened the USB Connection feature from ActiveSync, and then used CustomRUU.exe to Flash the ROM...
Everything is solved now...
Thank you very much all...
ilijan said:
how to connect if i used mtty... its clear everything what i have on device storage and in bootloader canot start stock or developed rom...
if i want start hard spl its say invalid model it....[/QUOT
bootloader is all you need to revive the phone
connect it to usb in bootloader mode and just install an oficial diamond rom from an windows xp pc.
it's easy
Click to expand...
Click to collapse
plz write here step by step guide how you solved
How it was solved...
ilijan said:
plz write here step by step guide how you solved
Click to expand...
Click to collapse
Actually the most crucial part was to bringing phone to boot loader mode. And I think I managed that by pushing the Volume Down and Back (the arrow pointing left) buttons immediately after restarting my phone. And I had to do this after taking out the battery and putting it back after 5 sec.
When I pushed these buttons at the start up the phone tried to install the ROM from my internal storage, but as I explained I had deleted it by mistake. Therefore it could not find the ROM. I disconnected my phone from my PC and the screen started to say something like Retrying USB connection or waiting for USB connection, something like that.
I restarted my PC in Digitally Signed feature disabled by pressing F8 during start-up. Reconnected my phone to PC (the screen of the phone was still blinking as waiting or retrying usb connection). And voila the phone screen changed to boot loader mode...
The rest was easy. I opened the USB connection feature from ActiveSync and used CustomRUU.exe with a ROM to flash my phone...
That is all...
1. plug phone in to computer in bootloader
2. run customruu or stock from rom update on computer
3. wait for rom to flash to device
4.???
5.profit
but my booloader dont show model ID: DIAM300 64M what i had befor
and show me only: 64M
and any flash error with invalid model id, i canot flash, rom, stock rom, or hardspl...
understand me.. im not totaly noob... i used mtty X times... but now have this probles
can somebody help me?
my diamond dont have model id...
before i had in bootloader mode DIAM300 64M model id, but now i havent got... its show only 64M,
every rom flash stopped at 1% cose model id error,
every hard spl falsh finished 100% but after flash when device restart write model id error...
i cant do anithing... can somebody help me?
For everyone facing problems after flashing his/her device, take a look at the link in my sig.
There you can find a guide to restore your diamond.
you dont understand me..
i canto flash any rom any hard spl becous my diamond dont have device ID...
in bootloader dont show DIAM300 64M but only 64M
after all flash say error mobile ID...
i try mtty, hard reseted, soft... and nothing
after start its show me only first stock screan, the red text on the right bottom sight dont start: 1.17.25.14
2.100000
geny d2x
its maybe wrong but i forgot what waz here...
how can change device model ID? form 64M back to my stock DIAM300 64M?
Try another version of Hard-SPL, some people report that 1.40 not fully works.
I suggest you try 1.94 Olinex.
my diamond is death... if somebody know how can heal it... plz write me...
my device ID is missing... so i cant flash any rom, any hard spl, any radio...
try this? http://forum.xda-developers.com/showthread.php?t=409425&highlight=invalid+model+id
im not sure but i dont think one can brick his/her phone after hard spl, thats the reason of hard spl in the first place that u dont brick it. boot loader is always present
Guide
if you are using Windows XP try the following steps:
Connect your device to your PC
In Active Sync > connection settings > check Allow USB connections (which you have un-checked while doing MTTY)
Find a ROM with CustomRUU.exe / diamond wrapper
Now enter into bootloader mode(forget about the device ID)
Go to customRUU.exe and run it
Follow the ROM installation steps
This will help you installing your new ROM.
I had a similar problem and i resolved it by follwoing the above steps.
Guide
if you are using Windows XP try the following steps:
Connect your device to your PCIn Active Sync > connection settings > check
Allow USB connections (which you have un-checked while doing MTTY)
Find a ROM with CustomRUU.exe / diamond wrapper
Now enter into bootloader mode(forget about the device ID)
Go to customRUU.exe and run it
Follow the ROM installation steps
This will help you installing your new ROM.
I had a similar problem and i resolved it by follwoing the above steps.