Hi all
Rather than hijacking other threads I thought it might be of help to others if I start a new one.
Having spent hours trawling thru the other threads I have now concluded that I need the help of one of the wise sages such as Cmonex or Olipro.
I decided that a thread might benefit others rather than just pm'ing them.
Ages ago i bricked my ameo.
I had upgraded to spl 3.5 and had been playing with one of michy's roms. Whilst the rom worked fine the boot-up splash screen had become corrupted, I also noticed that the camera had stopped working/initialising.
In an attempt to get the camera back I tried various other roms and decided to downgrade to spl1.2 so that I could go back to a stock rom. In a moment of stupidity I accidentally tried to reflash using a spl3.5 rom.
This resulted in a invalid model id message.
In desperation I did the old vol key down and reset pin. Told the ameo to restore.
From that point onwards the unit is no longer recognised by my pc, in the tricolour boot screen it initialises and says loading 0058002 and then displays
IPL-v1.00
SPL-v1.20 Olipro
I have tried the mtty option, using different computers and different leads, have even tried running the program from the root c: to no avail.
The problem is that whilst in boot loader screen on connection to the pc there is no usb option displayed, nor is there a usb option in the mtty drop-down list.
Pdajoy kindly suggested using a mini sd card to flash the unit. I purchased a micro sd with a mini adapter. Formatted the card to fat32, renamed the ndc file booted to the tri colour boot screen and hit reset. All that happens is that is tries to boot the old fecked o/s and gets as far as a blank grey screen and no further.
I really do miss my ameo- the screen on my touch pro is just too small!!!
Any help will be greatly appreciated.
Thanks
Hope is a typo error here, should be
"rename the RUU_signed.nbh to ATHEIMG.nbh"
Did you removed your SIM card before applying?
Sorry my bad for not warning you in advance.
Grey screen, you mean no text at all. Total blank grey?
Am just curious.
hi Pdajoy
I had renamed the files ATHEIMG.nbh, the reference in my post above is a typo. There was no sim in the phone either.
The screen after it tries to load the old corrupt rom is just a grey mass- nothing else, no text or images.
The two pics listed show the ameo booting and then the grey screen.
http://imaginarynumber.co.uk/ameo/IMAG0033.jpg
http://imaginarynumber.co.uk/ameo/IMAG0034.jpg
hi imaginarynumber,
Thanks for the photo.
hey 4.00 on screen, I believe your set is still spl 3.5
If it is my set, I will definitely flash AP4 again.
Best wait a little while for kind sage to drop by with to assist you.
Don't wish to see you bricks yours.
I have the same problem what can we do ?
I found a way to bring back the normal bootloader you just have tu press the reset button then you press the camera button and you will have your bootloader again
IT IS NOT WORKING you get back to the original bootloader but when you want to put back a rom even the official one after 1 percent it gets back to the grey screen PLEASE HELP
Srry athena works again place the mmty tool with mac bin file in the root of c and try again dont forget the task 32 command before the bin command that worked for me
I had the same exact problem (even the screen was the same) and didn't realize that the initial screen that shows up isn't the bootloader. fixed it by waiting for the grey/white screen, holding the volume button down then reset button and camera button + reset which brought me to the actual bootloader. From there I installed the latest AP rom, updated my radio and installed mitchy's 6.1
Big problem: Mac Address? Still getting dark screen and blue stripes!
Hi, I have follow the various steps above, however I cannot boot my Athena after words.
I am lost! I have followed exactly the steps:
1. disable activesync and put mtty into the C:/ root
2. connected athena as usb and booth with 3 colors screen
3. run mtty
4. done the cmk
5. selected port usb and created the .bin file for my SPL (1.2)
6. in mtty run task 32 and went up to: "code entrypoint unknow"
When I boot again my Athena I get the same dark screen with blue stripes:-(
You need to flash a rom
puffo said:
Hi, I have follow the various steps above, however I cannot boot my Athena after words.
I am lost! I have followed exactly the steps:
1. disable activesync and put mtty into the C:/ root
2. connected athena as usb and booth with 3 colors screen
3. run mtty
4. done the cmk
5. selected port usb and created the .bin file for my SPL (1.2)
6. in mtty run task 32 and went up to: "code entrypoint unknow"
When I boot again my Athena I get the same dark screen with blue stripes:-(
Click to expand...
Click to collapse
It looks like you did the wifi fixx correctly but the rom is still corrupted
Go into bootloader to confirm your SPL and then flash an spl appropriate rom
cheers
So, how to proceed now?
Dear Iakeman, all,
how can I confirm now my SPL and than flash the ROM?
I confirm that on my 3 color band screen I have:
IPL-v1.00
SPL-v1.20 Olipro
So, what is next??? If I just reset or restart the Athena in the normal way I will get back the dark screen with blue stripes and nothing will happen....
Do I have a this stage to install a new VM ROM? But I am wondering if I can do that since not sure that in this mode the Athena can communicate to my PC and so being able to upload on it any ROM....
puffo said:
Dear Iakeman, all,
how can I confirm now my SPL and than flash the ROM?
I confirm that on my 3 color band screen I have:
IPL-v1.00
SPL-v1.20 Olipro
So, what is next??? If I just reset or restart the Athena in the normal way I will get back the dark screen with blue stripes and nothing will happen....
Do I have a this stage to install a new VM ROM? But I am wondering if I can do that since not sure that in this mode the Athena can communicate to my PC and so being able to upload on it any ROM....
Click to expand...
Click to collapse
You have confirmed that you have spl1.2 by quoting what you have seen in the tricolor screen.
Get back into that screen , making sure you have removed the sim and sd card and then conect to your computer via the usb cable.
You would have downloaded an spl1.2 rom ( you previously stuffed the radio by trying to flash an spl3.5 rom) and then run the romupdateutility .exe .
then you should be sweet!
having read a reply of cmonex to another post I am starting to think that all hope is lost.
It seems that if windows is unable to recognise the phone it is possibly the case that it is completely f*cked!!!
It would be nice if someone could clarify this...
Which WM to ul now?
Dear Iakeman,
thank you so much for your kind reply. So at this stage I can try to upload to my Athena device, basically, any spl 1.2 rom of WM 6.0, or 6.1 or even the 6.5 beta?). Or I must start with spl1.2 rom WM 6.0 ?
Yes! It works!
Hello, after so much pain, I have follow the Cmonex post 33 to fix my broken firmware and now I have been able to upload properly the VM 6.5.
Many thanks!
imaginarynumber said:
I have tried the mtty option, using different computers and different leads, have even tried running the program from the root c: to no avail.
The problem is that whilst in boot loader screen on connection to the pc there is no usb option displayed, nor is there a usb option in the mtty drop-down list.
Thanks
Click to expand...
Click to collapse
just a thought.
Once you finished doing mtty, did you reenable usb in activesync as per this post
http://forum.xda-developers.com/showthread.php?t=387454&highlight=mtty&page=2
the other thought was is the usb cable and the usb port able to sync with other wm devices? maybe the slot on your athena is faulty?
Hi Lakeman
Thanks for the reply.
It is possible that the usb port is faulty but it seems improbable that this should have failed at exactly the same time as me stuffing up the O/S.
I will try to find the cmonex post to which I am refering later today (the one that suggests that the phone is stuffed).
Tnx
when i type task 32 show this plz help
Cmd>task 32
Level = FF
puffo said:
Hello, after so much pain, I have follow the Cmonex post 33 to fix my broken firmware and now I have been able to upload properly the VM 6.5.
Many thanks!
Click to expand...
Click to collapse
HI PUFFO,
WHICH Cmonex POST 33 R U REFERRING TO?
I M FACING EXACTLY THE SAME PROBLEM THAT U FACED AND AM WAITING FOR THE NEXT STEP.
KINDLY REFER ME TO THE POST SO THAT I CAN START USING MY ATHENA.
THANX
Related
Ok I have searched the forums pretty hard the last couple of days, and I have not found anyone that has the same issue as mine. It's not too big of a deal as everything operates but it is an issue all the same. This is all of course after I have succesfully ran HARD SPL v7 and upgraded to Black 3.0.1. Basically I decided to use POF's SuperCid Unlocker 3a (yes I know if I had HARD SPL 7 then why go through the trouble of Unlocking my CID, let's call it a need to mess with things) and everything went succesful. Then after the fact I read that it is still good even if you have SuperCID to upgrade the SPL to 2.10 and have read some peoples signatures and it appears that they have succesfully done this. Here is my issue;
When I run the CustomRUU it autodetects my SPL no problems, HARD-SPL? is checked, everything seems to go fine until it gets to the boot loader, once it is there, the progress bar pops up, zings to 100% and then reboots, cool? no because it didn't actually upgrade anything everything is still the same. Ok, so I tried the format SD card and rename *.nbh file to HERMIMG.nbh and put only it on the card, when I go to bootloader it does a quick flash to the screen like it recognizes the image but then goes to boot loader and nothing changes (the flash is so quick I can't even read whatever message it may be showing). I have tried pretty much every flashing method I can come across. MTTY wont recognize that I even have a USB port so I have been unable to try that method. So two questions:
I have SuperCID, so should I continue to even bother to get to 2.10?
If so, is there anything else I can try? Or do I need to get MTTY to work and try that as that is really the only thing left?
Thanks for any and all help anyone can provide.
PuckX said:
Ok I have searched the forums pretty hard the last couple of days, and I have not found anyone that has the same issue as mine. It's not too big of a deal as everything operates but it is an issue all the same. This is all of course after I have succesfully ran HARD SPL v7 and upgraded to Black 3.0.1. Basically I decided to use POF's SuperCid Unlocker 3a (yes I know if I had HARD SPL 7 then why go through the trouble of Unlocking my CID, let's call it a need to mess with things) and everything went succesful. Then after the fact I read that it is still good even if you have SuperCID to upgrade the SPL to 2.10 and have read some peoples signatures and it appears that they have succesfully done this. Here is my issue;
When I run the CustomRUU it autodetects my SPL no problems, HARD-SPL? is checked, everything seems to go fine until it gets to the boot loader, once it is there, the progress bar pops up, zings to 100% and then reboots, cool? no because it didn't actually upgrade anything everything is still the same. Ok, so I tried the format SD card and rename *.nbh file to HERMIMG.nbh and put only it on the card, when I go to bootloader it does a quick flash to the screen like it recognizes the image but then goes to boot loader and nothing changes (the flash is so quick I can't even read whatever message it may be showing). I have tried pretty much every flashing method I can come across. MTTY wont recognize that I even have a USB port so I have been unable to try that method. So two questions:
I have SuperCID, so should I continue to even bother to get to 2.10?
If so, is there anything else I can try? Or do I need to get MTTY to work and try that as that is really the only thing left?
Thanks for any and all help anyone can provide.
Click to expand...
Click to collapse
Did you look on the bootloader screen to see if your SPL changed? To my knowledge the only place you can see it is in the bootloader screen (tri-color screen) And flashing Olipro's Hard SPL only takes a couple seconds so it sounds to me like it is working as designed.
Or are you trying to flash a different rom? If so then try deleting everything you have in the directory you are using and re-downloading. You might have over-written the file you want to flash with the HardSPL one. You shouldn't be using the hard spl wrapper to flash a rom in any case, i believe that is mentioned in bold at the top of the Hard SPL thread.
Ok nevermind I was able to get it to work and MTTY was the answer. This is the 2 steps I had to follow:
From the thread: http://forum.xda-developers.com/showthread.php?t=291723
sp3dev said:
Hi. I`ve finally found the way to connect mtty and run rom update utility in Vista. tested on rtm 6000.
First of all, connect your device when it`s in bootloader.
next, open Windows Mobile Device Center and in connection settings uncheck Allou USB Connections.
next, goto contol panel-administrative tools-services and start windows mobile device connectivity and windows mobile device 2003 connectivity
next, goto device manager and find your device and update the driver to the one from AS 4, i attached it, wceusbsh.inf.
then, kill wmdc.exe with any taskmanager
You are Ready. run ruu or connect MTTY. I guess that vista default driver uses another port, not WCEUSBSH001, that`s why we have to use the old driver.
Click to expand...
Click to collapse
Then Do This:
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootloaderMFG
Flashing SPL-1.01 MFG instructions
Put hermes in bootloader mode (side ok + power button + softreset)
Connect Hermes to computer using USB cable.
Open mtty.exe, select "USB" from the dialog box, then hit Ok.
Hit enter twice and you'll see the "USB>" prompt.
Then type these commands: (note the use of 'lnb*s*')
USB>task 32
Level = 0
USB> lnbs SPL-1.01.nbs 50020000
USB> task 8
Device will reboot after this, with bootloader 1.01-MFG on it.
Once I was able to do all this I was succesfully at 1.01 at which point I ran the Custom RUU and upgrade to 2.10 without issue. Once again all right there in the forums, just had to be pieced together to find a solution.
Thank you all for all your dedication to these projects, you make owning a PDA more fun than I am sure was originally intended. I love messing with things.
I have also attached the necessary files from the original posts to perform this for anyone else facing this issue.
PuckX said:
Ok nevermind I was able to get it to work and MTTY was the answer.
Click to expand...
Click to collapse
Cool, glad you got it working
Hi All,
I'm new to the PDA-world and the Hermes. I'm trying to Hard SPL my Hermes, but it fails everytime.
When I run 2.10 - Hard-SPL-V7, it kills activesync and my connection is lost and I get always the message "error 260, Update error".
I have the latest framework edition and tried it on 3 pc's (1 Vista, 2 XP)...
What am I doing wrong?
Hope somebody can help me....
Kind Regards,
Micha
1). dont connect to active sync. open active sync and untick "allow usb connections".
2). put hermes into bootloader and connect to usb.
3). run ruu_wrapper.exe
should update to hard spl....
dont forget to tick "allow usb connections" again or you wnot be able to sync..
error 260 is an open port error.
if you wish to flash new os would advise to use sd card method. its safer than using the computer. just make sure you have greater than 50% battery power. happy flashing
Thnx, will give it a try.
First I have to flash HardSPL before I can flash a new OS, don't I?
yep, sorry, should have said run the ruu_wrapper for hard spl. My bad...
im having the same problem. I also tried the way ultramag recommended but i also received the same ending. After time i try i get the Error 260 Update error. Im running SPL 2.04 and the HTC WM6 rom from the HTC website. Does any one know what the problem is?
ultramag69 said:
2). put hermes into bootloader and connect to usb.
Click to expand...
Click to collapse
NOOOOO, that won't work, you need the SSPL to deploy to the phone, if you're running stock HTC bootloader this won't work at all, otherwise we'd have no need for Hard-SPL
hey olipro, then how would i fix this. Im running the stock rom from the HTC website with no hacks. Im trying to load PDA Corners V9 rom. Any ideas on how to fix? thanks!
Take a peek at the guide i wrote about updating the hardspl. Theres some explanation about why we need to use SSPL and the procedures.
http://www.mrvanx.org/hermes_guide/hardspl
thats the guide i used. it still gives me the error. I even unchecked "allow connections" cause i read somewhere that that would help.
i did this two days ago on my phone, im running windows vista on my home laptop and got any number of errors and problems trying to do it via sync with the phone (even after reading the vista troubleshooter, with the drivers etc)
What i ended up using was the memory card upgrade, dump the file onto the memory card and go into bootloader with the card installed.
worked fine doing that way, maybe less risky as there is no chance of the usb cable coming out.
just make sure you have a good battery charge on the phone.
Help Help Help w bricked 8525
I got into this position trying to upgrade WM5 to WM6 from HTC site.
Process got to 20% and just stayed there.
I reconnected usb cable and got a vendor id error
Then I get the Error [260]: CONNECTION
I have read a lot of posts and have tried the sd method (although i am not 100% clear) and all i get is the screen with four colors, red, green blue and white.
I believe this is the bootloader? I have downloaded RUU_signed.nbh, renamed it to hermimg.nbh, installed on root of my SD card and held OK, soft reset and power button:
My display reads:
HERM100
IPL-1.04
HERM100
SPL-2.03
This is where my journey ends.
All post indicate that the device can be reflashed and have the OS reinstalled. I can't get there from here.
Can anyone please help?
blackdog9692 said:
I have read a lot of posts and have tried the sd method (although i am not 100% clear) and all i get is the screen with four colors, red, green blue and white.
Click to expand...
Click to collapse
How big is your SD card? Flashing only works with cards <2GB. Also, sometimes certain cards just don't work for flashing, and just swapping to a different card fixes the problem.
I assume you searched the wiki, and found the relevant pages on the Hermes (including SD Card Flashing and other things about flashing/upgrading) there?
Still Lost
My SD is 2GB and I have tried many times but i just keep getting the 4 color screen. rt now when i boot from the SD my screen goes white and displays "Loading..." and then returns to bootloader screen. When i attempt to flash the rom via PC to WM5 or WM6 i get the Error 260, i also get a vendor ID error sometimes.
How can i find the key 8525 thread that i am told has the answer to my delima? I keep picking up bits and pieces but am missing some key steps and tips.
blackdog9692 said:
My SD is 2GB and I have tried many times but i just keep getting the 4 color screen. rt now when i boot from the SD my screen goes white and displays "Loading..." and then returns to bootloader screen.
Click to expand...
Click to collapse
That sounds like the SD card is formatted incorrectly. Make sure it's formatted using fat32, nothing else will work.
Still not there from here
Thanks for your help. Before I formatted the SD FAT32, nothing would happen doing the bootloader reset. OK/ON/reset button.
After format and only the hermimg.nbh file renamed as indicated, I then get what looks like the loading process but back to the bootloader screen.
Q1: This is an AT&T 8525, it was perfectly fine before failure from WM5 to WM6 (process froze at 20%), what is the RUU file that I need to put on SD??
Q2: After "Loading ..." I try the WM5 PC upgrade of ROM via USB cable, I get the load process to appear to work but it gets to 1% and the phone reboots and the PC reports error [294]: Invalid vendor ID. If I do this again I will get the Error [260]. Ive repeated the process several times.
Is this the normal course to take or should the "SD Method" (with the WM5 or WM6 RUU.. file) complete the process to a working OS?
Q3: Is my situation hopeless? ATT will take my out of warrantee 8525 and reflash for $129. Reading the threads it seems that like me this can be done by me, this is my desire.
Q4: I still am confused by some basic terms and assumed steps. I dont understand "Hard SPL" or OLI's IPLs/SPLs and when and when to use them.
The newbe guide has been off line. I will look again. Is there a single place to read about "radio PDAs and the 8525 and understand the software build and custom options?
Sy for the long post. But still want to fix if possible or I will be force to mail in for ATT repair.
Thank you all.
blackdog9692 said:
Q4: I still am confused by some basic terms and assumed steps. I dont understand "Hard SPL" or OLI's IPLs/SPLs and when and when to use them.
Click to expand...
Click to collapse
Oh boy, you haven't installed HardSPL? You are walking a bit of a line there mate...
HardSPL is a custom boot loader that makes bricking your phone when flashing much harder to do, and helps large amounts in the recovery process if you phone does brick.
Does the phone boot at this point? If so, do not try flashing the phone again. Go get a copy of HardSPL and install it, then try flashing from the SD.
I still wonder why people didn't read before bricking...
Anyway, you should start reading now and wiki is your friend. Your SPL is 2.03, so look at the bottom of the page (there is only one solution till now, so good luck with that):
Code:
1. Boot OS using KITL+PB
2. Do no disconnect your HERMES till the end of the step 6
3. Download SSPL on HERMES by wifi from ie explorer
4. Launch SSPL then flash Hard-SPL from your computer
5. Put your hermes in bootloader mode
6. Flash any radio in NBH format from your computer
Still researching and working this bricked 8525
Thanks for coming to my aide. I believe that I have Hard SPL'd my device. I downloaded Olipro's Hard SPL v7. extracted the RUU_ file and renamed to hermimg.nbh.
I then put it on an SD card and held the keys and reset. The device displayed a white screen and "Loading..." appeared. Afterward the 8525 returned to the stipped boat loader screen and that is where I am now.
Some of the help i receive and read on wiki threads has me confused with what to do next and how "exactly" to do it.
It does seem that I am not alone and people have fixed their phones and the process to do this is on the forum. I'm just still missing something.
Help me further if u can.
Thank you.
blackdog9692 said:
Thanks for coming to my aide. I believe that I have Hard SPL'd my device. I downloaded Olipro's Hard SPL v7. extracted the RUU_ file and renamed to hermimg.nbh.
Click to expand...
Click to collapse
FYI: bad form to PM someone and post the same thing here. Keep it in the thread so others can be helped as well.
As I replied in the PM, if I'm understanding your post correctly, the phone boots to the tri-colour screen?
What text is showing on the screen? This will tell if HardSPL is on the phone or not.
jdc said:
What text is showing on the screen? This will tell if HardSPL is on the phone or not.
Click to expand...
Click to collapse
We already know that the phone is without HardSPL, according:
My display reads:
HERM100
IPL-1.04
HERM100
SPL-2.03
This is where my journey ends.
Click to expand...
Click to collapse
There is small chance (read my previous post) to unbrick device with SPL2.03 so better try to get this back from where you take it.
And please, change topic, because this brick isn't HardSPL fault at all.
Edit: oh dear, it's even not your topic ...good game, I'm off
I installed an "updated" HTC Home Screen Plugin (obviously not for my phone model #) and now my phone is frozen. It will boot up but the home screen is frozen (i.e., non-responsive to any button presses). I attempted to re-flash the ROM using various ones I found for the NEON but all fail for the same reason.
Specifically, connection to ActiveSync is not possible (I connect via USB cable but ActiveSync doesn't recognize device). So what I do is put the phone in bootloader mode and then connect the USB cable. When I do this, the ROM upgrade program recognizes the phone and gets to the point where it shows the screen "Updating the ROM image on your PDA Phone.." and the phone shows a status bar at 0%. However, after a minute the computer screen says "ERROR [262]: UPDATE ERROR" and the phone is stile stuck at 0%.
My question is if there is any other way I can re-flash my NEON300? I've heard that it may be possible to but the nbh file on a FAT32 formatted card. I tried this by naming the nbh file to "TOUCHIMG.NBH" and "NEONIMG.NBH" but neither are recognized by the bootloader.
Thanks in advance for any assistance.
Try changing usb port or even re-installing activesync.
Alot pf people had the same problem on different devices but the cause should be the same.
for example, http://forum.xda-developers.com/showthread.php?t=298516
Let me know how you go.
Thanks for the advice Seth. I followed the link (install/re-install of ActiveSync didn't help) and I think I found my problem. Do I need to CID unlock the phone to install the ROM's? I ran the type 32 command from mtty and it shows a value of FF for the security lock.
Thanks
wangobyte said:
Thanks for the advice Seth. I followed the link (install/re-install of ActiveSync didn't help) and I think I found my problem. Do I need to CID unlock the phone to install the ROM's? I ran the type 32 command from mtty and it shows a value of FF for the security lock.
Thanks
Click to expand...
Click to collapse
You should have read the WIKI before flashing your device... http://wiki.xda-developers.com/index.php?pagename=Flashing Guide and here http://forum.xda-developers.com/showthread.php?t=355730
Hi All,
I had on my Athena the previous Michy Rom (2.04 with SPL 1.20) and when I saw the new version (4.00 with SPL 3.5):
http://forum.xda-developers.com/showthread.php?t=411371
I decided to install it. Like an idiot, I did not pay attention to the fact the SPL was different... I started the flash process and when I realized my error, it was too late.
The upgrade did not completed (as expected :-()) and now I am stuck with a corrupted bootloader screen, so I can't proceed (the device does not boot so I can't access ActiveSync).
Any way forward? Thanks for any hints!
Anubis
Update - I just tried this:
http://forum.xda-developers.com/showthread.php?t=326953
but without success. I get an Error [260] and the entire process stops.
Anubis1965 said:
Hi All,
I had on my Athena the previous Michy Rom (2.04 with SPL 1.20) and when I saw the new version (4.00 with SPL 3.5):
http://forum.xda-developers.com/showthread.php?t=411371
I decided to install it. Like an idiot, I did not pay attention to the fact the SPL was different... I started the flash process and when I realized my error, it was too late.
The upgrade did not completed (as expected :-()) and now I am stuck with a corrupted bootloader screen, so I can't proceed (the device does not boot so I can't access ActiveSync).
Any way forward? Thanks for any hints!
Anubis
Click to expand...
Click to collapse
look here
http://forum.xda-developers.com/showthread.php?t=405814
lakeman said:
look here
http://forum.xda-developers.com/showthread.php?t=405814
Click to expand...
Click to collapse
I have seen that thread. But the problem is different. I have also tried to reload a vanilla WM6 ROM but I cannot go past the corrupted bootloader part...
Anubis
Anubis1965 said:
I have seen that thread. But the problem is different. I have also tried to reload a vanilla WM6 ROM but I cannot go past the corrupted bootloader part...
Anubis
Click to expand...
Click to collapse
When you are in bootloader(three coloured screen) what do you see?
remove sim and sd card , hold camera button all the way in and press the reset button(on the back close to the battery cover)
If you see in bootloader mode ID showing somenting different than ATHE100 the solution is HERE http://forum.xda-developers.com/showthread.php?t=405814
I had the same problem! whell restart your pc and then connect the device to it. now start flashin an spl 1.20 rom. i did it and it worked! I hope i works for you too.
Cheers, Hirad
lakeman said:
When you are in bootloader(three coloured screen) what do you see?
remove sim and sd card , hold camera button all the way in and press the reset button(on the back close to the battery cover)
Click to expand...
Click to collapse
Thanks - already tried!
When I reset/hard-reset the phone (tried many ways) I see a garbled boot image (with random pixels here and there)... It is definitively not the usual bootloader with the information about the various ROM components and the "USB" text at the bottom.
Anubis
Solution!
I managed to do the same thing - had an old AP ROM with SPL 1.2 already installed then earlier today I tried to upgrade to the new Mitchy R4 SPL 3.5. I thought my Ameo was bricked, but after some pain it is now working again.
Here is what I did:
1) Enter bootloader mode using the very tricky Camera+Volume+Reset method.
2)
Follow exactly the steps in post 33 here:
http://forum.xda-developers.com/showthread.php?t=387454&highlight=mtty&page=4
Note, I'm running Vista so to get the USB option to show in MTTY, I had to first open "Windows Mobile Device Center" in Control Panel then disable the USB.
Also, note you should find your MAC under the battery flap.
3) Now all you need to do is reset, enter the bootloader mode again, and re-try the ROM (PS, make sure you use the correct SPL version!
Hope this helps.
spoonter said:
I managed to do the same thing - had an old AP ROM with SPL 1.2 already installed then earlier today I tried to upgrade to the new Mitchy R4 SPL 3.5. I thought my Ameo was bricked, but after some pain it is now working again.
Here is what I did:
1) Enter bootloader mode using the very tricky Camera+Volume+Reset method.
2)
Follow exactly the steps in post 33 here:
http://forum.xda-developers.com/showthread.php?t=387454&highlight=mtty&page=4
Note, I'm running Vista so to get the USB option to show in MTTY, I had to first open "Windows Mobile Device Center" in Control Panel then disable the USB.
Also, note you should find your MAC under the battery flap.
3) Now all you need to do is reset, enter the bootloader mode again, and re-try the ROM (PS, make sure you use the correct SPL version!
Hope this helps.
Click to expand...
Click to collapse
You are right and this is what sergiopi and I were referring to , specifically this post
http://forum.xda-developers.com/showpost.php?p=2154726&postcount=33
We were refering to the whole thread so you could learn the background.
However you are incorrect in your advice about how to enter bootloader
All you need to do is hold in the camera button and reset
spoonter said:
I managed to do the same thing - had an old AP ROM with SPL 1.2 already installed then earlier today I tried to upgrade to the new Mitchy R4 SPL 3.5. I thought my Ameo was bricked, but after some pain it is now working again.
Here is what I did:
1) Enter bootloader mode using the very tricky Camera+Volume+Reset method.
2)
Follow exactly the steps in post 33 here:
http://forum.xda-developers.com/showthread.php?t=387454&highlight=mtty&page=4
Note, I'm running Vista so to get the USB option to show in MTTY, I had to first open "Windows Mobile Device Center" in Control Panel then disable the USB.
Also, note you should find your MAC under the battery flap.
3) Now all you need to do is reset, enter the bootloader mode again, and re-try the ROM (PS, make sure you use the correct SPL version!
Hope this helps.
Click to expand...
Click to collapse
Thanks - you are giving me some hope! I am on a business trip now and my Athena is at home, but I will try that as soon as I am back
Anubis
Hello, I am in serious trouble! I got a brand new HTC Athena with Windows Mobile 5.0. I succesfully upgrade it to Windows Mobile 6.0.
All was OK.
Than I was interested to move into Windows Mobile 6.1 and possibly 6.5. At first I did the Athena unlock (3 step process) and all went OK: Antenna 1.5.0, SPL 1.2 OLI....
THAN I DID MY ERROR! I try to upgrade my 6.0 ROM with the Micky 6.1 cooked file with SPL 3.5. After a 92 percent upgrade, the ROM crashed and now I always get a nasty black screen with few lines (No 3 color bands!). When I try to upgrade again the same ROM or ROM for SPL 1.2 I get an error (ID mismatching). I guess the only solution is a hard and full reset of the Windows. But doing only a hard reset with the PDA will NOT change my error message and I will keep see this nasty black screen and I cannot load the Windows ActiveSync application-
I am totally lost. Help please. Any tool for a true full restore/recover??? (I did NOT make any backup!).
This thread might hold a solution to your problem.
Hi
If you follow the instructions exactly in post 33, it will solve your problems. just click HERE
Jay
Hello, those links are basically for corrupted wifi antenna files.-
In my case my HTC Athena crashed the Windows 6 ROM while I was attempting to upgrade, after unlocking the phone, the Athena from version 6.0 to version 6.1
Are you sure I can use the post #33 also for my specific trouble?
Thank you in advance!
this is also to repair your bootloader-infos
if you look at your bootloaderscreen, you will see ATHE100, IPL, ATHE100, SPL. if not, you have to repair it
make sure you flashed the right rom, spl 1 or 3.5
How can the bootloader get repaired?
yes use that link, post #33. fixes both wifi and modelid problems and bootloader problems when you got stuck at 92% of the flashing process.
Cannot re flash ROM
Please help! I tried the unlocker and it failed at 92% and since then I have no WM6. Then I tried to flash the Michy WM6.5 and that failed. I was getting model id errors so I did the mtty and mac1 fix which was succesful. However all I can get now is a grey screen on boot-up. I can get to the bootloader screen and it displays ATHE100, IPL-v2.02, ATHE100, SPL-v1.20. Olipro. From what I have read on the forum at this stage I should run a RUU to flash a WM6 ROM but all that I try can't connect because no OS running to connect with Activesync? Is there a way to flash from the bootloader? The other option seems to be putting an image and flasher on a miniSD but I can't find clear instructions for this or which files?
Please ignore - my battery wasn't charged enough. Replaced battery and recovered device.
Still Major Problem! Help me! Have mercy!
Hello Responderman, all,
I have follow the link (thread 33)...., however, after I have typed lnbs filename.bin 75108000 (I have SPL 1.2), I got in mtty the "code entrypoint unknown" message, which should be ok......
However, after I have disconnected the usb cable of the Athena from the PC and try to reboot it, I got again the exact same, nasty, dark screen with blue strips.....:-( It means that my damaged firmware has NOT been fix and in fact I am still NOT able to boot WM successfully!
PLEASE HELP. It is 3 months with this problem and I cannot use my device.:-(
Still Major Problem! Help me! Have mercy!
Hello Responderman, all,
first, how can I get the mac address of my device? It is NOT written anywhere in the Athena parts (checked in the battery bay and so on.....), and so when I run mtty i am in trouble! I have used a mac address got from my company's manager, but not sure it is ok to use it with the Athena!
Anyway,......I have follow the post link (thread 33)...., and followed the various steps.- However, after I have typed lnbs filename.bin 75108000 (I have SPL 1.2), I got in mtty the "code entrypoint unknown" message, which should be ok......
However, after I have disconnected the usb cable of the Athena from the PC and try to reboot it, I got again the exact same, nasty, dark screen with blue strips.....:-( It means that my damaged firmware has NOT been fix and in fact I am still NOT able to boot WM successfully!
PLEASE HELP. It is 3 months with this problem and I cannot use my device.:-(
Solved!
Hi, problem done. I have follow the remarks, fixed my broken firmware and now I use well Athena with VM 6.5! Thanks all for your help!
puffo said:
Hi, problem done. I have follow the remarks, fixed my broken firmware and now I use well Athena with VM 6.5! Thanks all for your help!
Click to expand...
Click to collapse
Can you tell what you've actually done after you've changed ROM with Mtty?
I done the thing with Mtty but just as you described when I reset it now I still get the grey screen. And if I try to update ROM it fails again on 92%
where did you find the upgrade from wm5 to wm6?
the link I found on rapidshare seems not be availabel anymore