I have just tried flashing WM6 on to a Friends QTEK 8500, it went wrong Doh!!!.
I had already last Friday put on it the version with non wroking GPRS and this went without issue. I then reflashed my own one with a GRPS working version (went without a problem) and then tried his. I can get it into the boot loader screen but nothing else. I have tried SD card flashing (3 cards) 1x 512MB Card and 2 x 2GB card all formatted as FAT32 with file on the root the phone searches for it but doesnt find it.
Please any advise.
vallancen said:
I have just tried flashing WM6 on to a Friends QTEK 8500, it went wrong Doh!!!.
I had already last Friday put on it the version with non wroking GPRS and this went without issue. I then reflashed my own one with a GRPS working version (went without a problem) and then tried his. I can get it into the boot loader screen but nothing else. I have tried SD card flashing (3 cards) 1x 512MB Card and 2 x 2GB card all formatted as FAT32 with file on the root the phone searches for it but doesnt find it.
Please any advise.
Click to expand...
Click to collapse
First of all, REMEMBER, your phone is NOT bricked until it goes to BOOTLOADER mode.
Have you made SuperCID before flashing? What firmware are you trying to flash via bootloader mode?
Erofich said:
First of all, REMEMBER, your phone is NOT bricked until it goes to BOOTLOADER mode.
Have you made SuperCID before flashing? What firmware are you trying to flash via bootloader mode?
Click to expand...
Click to collapse
When you say booloader mode what does that look like. At the moment if I reboot the phone I get the HTC Mobility windows by Erofich screen.
When you hold down camera and record button and then power on the device I get brifely the white scrren looking for SD card it then goes to the tri-colour screen and does nothing.
I beleive I have CID it as I did the same on this as I did on mine i.e. ran the unlock according to the sticky.
I than put on this
Windows Mobile 6 AKU 0.5.0 (5.2.1711 Build 18165.0.5.0) WWE v5c
Yours i beleive (excellent work by the way)
and it all worked fine bar GPRS I relay needed GPRS so I used
http://forum.xda-developers.com/showthread.php?t=368715
using the clean one which updated fine on my phone but when i tried it on my friends it fell over at about 83% I followed the recovery intructions but this did not work.
When you get into bootloader screen by pressing RECORD and CAMERA buttons, then you MUST flash back to the STOCK ROM first. You can't flash any custom WM6 at this point. Only AFTER you have the stock ROM flashed, you can use SDA_ApplicationUnlock.exe to app unlock the phone, and copy the SoftSPL into the phone. Then run SPL.lnk.
To summarize: The built-in bootloader CANNOT flash WM6 and can ONLY flash a stock ROM. Once you go back to stock, you can then try to flash WM6 again. Anytime a flash fails, you must go back to stock first, then try again.
GnatGoSplat said:
When you get into bootloader screen by pressing RECORD and CAMERA buttons, then you MUST flash back to the STOCK ROM first. You can't flash any custom WM6 at this point. Only AFTER you have the stock ROM flashed, you can use SDA_ApplicationUnlock.exe to app unlock the phone, and copy the SoftSPL into the phone. Then run SPL.lnk.
To summarize: The built-in bootloader CANNOT flash WM6 and can ONLY flash a stock ROM. Once you go back to stock, you can then try to flash WM6 again. Anytime a flash fails, you must go back to stock first, then try again.
Click to expand...
Click to collapse
I am trying RUU_STAR100_3.6.251.0_02.67.30_QtekEUR_Ship I believe this is an original version 5 rom?
GnatGoSplat said:
you can use SDA_ApplicationUnlock.exe to app unlock the phone
Click to expand...
Click to collapse
This method works on Cingular ROM only, not Qtek.
vallancen
Hold CAMERA and RECORD button and press power button. When it goes to Bootloader tricolor mode connect your device to PC and run official Qtek 8500 RUU. Then make a reg (app) unlock:
Download regeditSTG2 which is digitally signed: http://4pda.ru/forum/attach/387522/regeditSTG2.zip
Then install it and change some registry values:
HKEY_LOCAL_MACHINE\Security\Policies\Policies\00001001 = 2
-> change to 1
HKEY_LOCAL_MACHINE\Security\Policies\Policies\00001005 = 16
-> change to 40
HKEY_LOCAL_MACHINE\Security\Policies\Policies\00001017 = 128
-> change to 144
HKEY_LOCAL_MACHINE \Security\Policies\Policies
-> create new key "0000101a": Dword = 1
HKEY_LOCAL_MACHINE \Security\Policies\Policies
-> create new key "0000101b": Dword = 1"
Click to expand...
Click to collapse
copy SoftSPL to the root of your device and run SPL.lnk
Then run WM6 RUU
Erofich said:
This method works on Cingular ROM only, not Qtek.
vallancen
Hold CAMERA and RECORD button and press power button. When it goes to Bootloader tricolor mode connect your device to PC and run official Qtek 8500 RUU. Then make a reg (app) unlock:
copy SoftSPL to the root of your device and run SPL.lnk
Then run WM6 RUU
Click to expand...
Click to collapse
When I plug into PC (XP SP2) and run the Qtek 8500 RUU it just times out and says it cant find device.
vallancen said:
When I plug into PC (XP SP2) and run the Qtek 8500 RUU it just times out and says it cant find device.
Click to expand...
Click to collapse
I have two phones one did work and one did not the one that worked shows version 1.02 on the tri colour screen the one I am having problems with shows 3.06 not sure if this is relevant.
Try removing the battery for about 30-seconds (or just removing the battery cover) and then put it back on. With the phone OFF, hold RECORD and CAMERA and plug in the USB while holding those buttons. It should go to the Bootloader. Run the QTEK RUU immediately after doing that.
If you sit at bootloader very long (more than a minute or so), for some reason it times out and the RUU won't work. It could be that's what's happening.
GnatGoSplat said:
Try removing the battery for about 30-seconds (or just removing the battery cover) and then put it back on. With the phone OFF, hold RECORD and CAMERA and plug in the USB while holding those buttons. It should go to the Bootloader. Run the QTEK RUU immediately after doing that.
If you sit at bootloader very long (more than a minute or so), for some reason it times out and the RUU won't work. It could be that's what's happening.
Click to expand...
Click to collapse
Tried that a couple of times just to make sure I was doing it correctly it goes into the tri colour screen I pressed the reflash option on the PC 1 second later this then sits there for a minute or so and times out "ERROR [260]" the phone did come on and has a USB in the bottom left corner so I presume the connection to the PC is OK.
I have just re-done mine again using the NEO rom (very nice) to make sure I am not going mad and that I did it correctly and this all went without a hitch.
Is there anyway I can get the phone to boot of a SPL on an SD Card I think if I could do this then I could get it back to 5 and start again.
No, it will only boot off the built-in SPL in ROM.
Did you try using the OEM .nbh file, naming it STARIMG.nbh and putting it on the SD card?
GnatGoSplat said:
No, it will only boot off the built-in SPL in ROM.
Did you try using the OEM .nbh file, naming it STARIMG.nbh and putting it on the SD card?
Click to expand...
Click to collapse
Yes tried that made sure formatted FAT32 etc. I know the SD card is ok because if I take my working phone and run the SPL link with the card in my good phone it finds the file and asks me if i want to reflash it. The non working phone with SPL3.06 does not do this.
You are not alone.
The bad news - the person in the post ended up having to exchange the phone.
It could be there's a bug in 3.06 SPL? Seems to be the case because I've flashed bad ROMs many dozens of times on my Cingular 3125 StarTrek and not once did I have any trouble flashing OEM ROM back on it.
Can I write the flash at a lower level with any tools i.e. pdocwrite or seomthing like that?
I don't believe so. Those programs require an Activesync connection (copies files to the phone). You could try the MTTY method, but I don't know if that works on StarTrek. I think it's some kind of terminal access into the bootloader, but what I've said so far is the extent of my knowledge about it.
vallancen said:
I have two phones one did work and one did not the one that worked shows version 1.02 on the tri colour screen the one I am having problems with shows 3.06 not sure if this is relevant.
Click to expand...
Click to collapse
I have a similar problem on a 3125 and the phone reports V4.01. I acquired the phone in this condition, so don't know how that came to be. When I try to update via USB, it tells me I need a newer update tool (to match the 4.01, I assume). What error message are you getting when you try to update via USB?
I have been struggling to flash (again) the great pro V2 rom, but I always used my VMWare based XP windows version on my Vista laptop. Today I could use a genuine XP Laptop and I could make a connection and start the upgrade!
Sounds good? That's what I thought too, until the upgrade stopped at 70% (and I didn't touch anything), because of a connection error. I followed the text on my PC screen and I finally it started flashing again for a few seconds and then my startrek suddenly restarted, but it stops at the first splash screen! I tried to get my device back to bootloader mode (push 2 soft buttons and start), but no bootloader mode, only the 1st splash.
I solved the problem.
Thank you for this thread
I tried flashing a new ROM to my i-mate smartflip and thought I had killed it, but going back to the wm5 OEM as suggested on this thread worked and I still have my phone. Now, am I brave enough to try upgrading it to wm6.1 (or even 6.5) again... Once again, many thanks!
somebody can me give the oem rom because i am same problem too on the secreen 3.06 i cant flashing anytihing rom somebody must me help
Related
Apparently, I'm pretty stupid.
I just got the Cingular 8525; I have spent two hours on this site.
Things I've noticed:
One page says go into bootloader; one page says not to allow usb connections.
I do not know if I am supposed to have my non-Cingular SIM card already in the phone when attempting to do anything.
I have seen connect via USB and use mtty (with what settings do I use when I click on USB from the dropdown menu (if any) and do I connect with mtty via USB in bootloader or when the phone has booted into Windows 5.0 and again what about the non-Cingular SIM card?).
I have flashed my computers BIOS several times but I do not understand how to flash this phone based on the myriad of instructions all over this site (and RFTW did not help which is why I am here with 40000000 questions).
The steps to go from SPL 1.06 to an unlocked SIM/CID phone are?
Things I do understand:
I have SPL 1.06 (I know this from bootloader).
I must downgrade to 1.04 from 1.06 then run the upgrade to 1.06 from the Hermes Upgrade wiki page (I already downloaded all of the Cingular files).
Thanks in advance for any clarification.
I unlocked my 8525 last week, I had bootloader 1.06 so I downgraded to a ROM with boetloader 1.04(you can find it here http://wiki.xda-developers.com/index.php?pagename=Hermes_Upgrades ).. then just follow the instructions in the zip file you downloaded(i used HERM_Unlock_v2a), which are:
1. Enter bootloader mode on your Phone. To do this, simultaneously hold side OK and POWER buttons together and reset with stylus.
[You should see SPL-1.04 on the top of the tri-color screen, if you see SPL-1.06 this unlocker will not work, please wait for the next version]
2. Connect your phone to your computer using the USB lead.
3. Run the MaUpgradeUt_noID.exe program – this will reflash your phone with a patched radio ROM required to unlock.
4. Wait patiently.
5. Once the MaUpgradeUt_noID.exe upgrade completes, it will end up saying "Upgrade Error 114", but the patched radio ROM will be flashed anyway, dont worry about that error!
6. Soft reset with stylus (Device will not be hard reset and no data will be lost)
7. Allow your phone to reboot. Once it has, connect to your PC using Activesync, and copy the HERM_Unlock_v2a.exe program onto your phone. Alternatively, copy it to an SD card and insert into your phone.
8. Run HERM_Unlock_v2a.exe on your phone. Wait about 1 minute.
9. You should see a "SUCCESS!" message from HERM_Unlock_v2a.exe, after that soft reset your phone.
10. Process is (hopefully) complete!
11. If the phone requests unlock code when you put a locked SIM, the code is: 22051978
I assume I want go to 1.04 for Cingular which is 1.30.502.1.
What about my SIM card? Is it supposed to be in phone when I run this file? (it's a t-mobile sim).
I assume the activesync connection via usb is okay? I cannot get it to connect (even though the phone is on and booted into Windows 5.0); is this because I have not inserted the SIM card into the phone? Note: after I unplugged the device, setting allow USB connections on the device in the ActiveSync settings, then plugging it back in, it connected via USB in ActiveSync (4.2). However, I just got a box saying the version of ActiveSync is not compatible with this mobile device. This occured after I started the installer and it showing Verifying the information on your PDA phone.
I received an update error 260 since it thinks the phone is not connected via USB (and I noticed the ActiveSync icon in the system tray is gone).
I went to check the M$ page to see if there is a later download; there is not. Then, the AS icon return (trying to update outlook, install nero mobile) so I decided to run the installer again and now sees my current version 1.34.502.1 and I have the option to upgrade ROM
MilanoRex said:
I unlocked my 8525 last week, I had bootloader 1.06 so I downgraded to a ROM with boetloader 1.04(you can find it here http://wiki.xda-developers.com/index.php?pagename=Hermes_Upgrades ).. then just follow the instructions in the zip file you downloaded(i used HERM_Unlock_v2a), which are:
1. Enter bootloader mode on your Phone. To do this, simultaneously hold side OK and POWER buttons together and reset with stylus.
[You should see SPL-1.04 on the top of the tri-color screen, if you see SPL-1.06 this unlocker will not work, please wait for the next version]
2. Connect your phone to your computer using the USB lead.
3. Run the MaUpgradeUt_noID.exe program – this will reflash your phone with a patched radio ROM required to unlock.
4. Wait patiently.
5. Once the MaUpgradeUt_noID.exe upgrade completes, it will end up saying "Upgrade Error 114", but the patched radio ROM will be flashed anyway, dont worry about that error!
6. Soft reset with stylus (Device will not be hard reset and no data will be lost)
7. Allow your phone to reboot. Once it has, connect to your PC using Activesync, and copy the HERM_Unlock_v2a.exe program onto your phone. Alternatively, copy it to an SD card and insert into your phone.
8. Run HERM_Unlock_v2a.exe on your phone. Wait about 1 minute.
9. You should see a "SUCCESS!" message from HERM_Unlock_v2a.exe, after that soft reset your phone.
10. Process is (hopefully) complete!
11. If the phone requests unlock code when you put a locked SIM, the code is: 22051978
Click to expand...
Click to collapse
crazyut said:
I assume I want go to 1.04 for Cingular which is 1.30.502.1.
Click to expand...
Click to collapse
right
crazyut said:
What about my SIM card? Is it supposed to be in phone when I run this file? (it's a t-mobile sim).
Click to expand...
Click to collapse
doesn't matter
crazyut said:
I assume the activesync connection via usb is okay?
Click to expand...
Click to collapse
It is ok, but generally it causes more problems than it helps. Best is to disable the checkbox that says "enable usb connections" on activesync settings and you'll see the icon on the system tray turn gray with a red "X". Then you need to start the RUU when the device is in bootloader mode (tri-color screen). After you have upgrded the rom (or radio rom) you can reenable activesync again if you want.
crazyut said:
I cannot get it to connect (even though the phone is on and booted into Windows 5.0); is this because I have not inserted the SIM card into the phone?
Click to expand...
Click to collapse
SIM card and activesync have nothing to do.
crazyut said:
I received an update error 260 since it thinks the phone is not connected via USB (and I noticed the ActiveSync icon in the system tray is gone).
Click to expand...
Click to collapse
Icon was gone because RUU checks your current rom version using activesync and then kills it an put device in bootloaer mode. If RUU cannot kill activesync correctly errors happen:
You will avoid the 260 error if you disable usb connections on desktop activesync as I told you, and start the upgrade in bootloader mode... only difference you'll notice is that RUU will not report your current rom version.
Hey. I left the RUU software running (the 25+ minute variety) while I went to buy a case and care charger. I came back and evidently, the phone had rebooted because, it is at the Windows Mobile screen to setup the Windows Mobile device. I assume it is safe to do the 2a software. After that, am I able to update the RUU back to 1.06?
Thanks for your help, Milan and pof!
I rebooted into bootloader to confirm successful downgrade to 1.04 from 1.06 and it was. The RUU software from the upgrade page for Cingular appears to have been successful.
I am now going to attempt the 2a software.
Yes, now follow all the instructions on sim&cid unlocker v2a, and when finished, flash the cingular 1.34 rom again.
pof said:
Yes, now follow all the instructions on sim&cid unlocker v2a, and when finished, flash the cingular 1.34 rom again.
Click to expand...
Click to collapse
It's now on the upgrade screen to Radio 1.16.00.69 but it does not show the previous version. Is this normal? I have not pressed upgrade yet. I have the splitter with the AC and USB cables into the phone (currently in bootloader mode at SPL-1.04).
yes, it is normal... i told you before:
pof said:
RUU checks your current rom version using activesync
[...]
start the upgrade in bootloader mode... only difference you'll notice is that RUU will not report your current rom version.
Click to expand...
Click to collapse
pof said:
yes, it is normal... i told you before:
Click to expand...
Click to collapse
I got the 114 error as promised in the readme. I exited the program using the EXIT button.
The next step:
6. Soft reset with stylus (Device will not be hard reset and no data will be lost)
On the phone display, it still shows Upgrade Radio Stack Please Wait..
The soft reset is the simultaneous OK and Power?
I just took the battery out and reset; it appeared to go okay. I copied the exe file to the phone and was able to run the file as in the readme. I then reset the phone, put in the t-mobile sim and it works.
Thanks much to POF and Milan for their straightforward approach. You can use this thread as a tutorial!
Is there any reason I should add the 1.06 file back to the unlocked 8525?
SPL 1.06 to SPL 1.04 back to SPL 1.06?
Hi:
I followed pof's (with pof's help) tutorial on how to unlock the Cingular 8525. I am currently at SPL 1.04 (downgraded form SPL 1.06) and had run the v2a software to unlock. It works great with T-mobile (I was a Cingular customer but made the switch).
My questions are:
Is there any reason to go back SPL 1.06?
If I do go back to SPL 1.06, it does not affect the unlock status of the SIM or CID?
I still am confused about the Radio and what that does in relation to the CID, SIM, or phone. I assume the Radio is affected the SPL version that you have?
I have tried to peruse through various pages regarding downgrading (the 13 page thread for example) to see if that question is answered.
The radio ROM controls the GSM/GPRS/UMTS hardware in your hermes. You cannot independently upgrade it unless you are running SPL 1.04. There is no reason IMO to go to any other bootloader version.
Sleuth255 said:
The radio ROM controls the GSM/GPRS/UMTS hardware in your hermes. You cannot independently upgrade it unless you are running SPL 1.04. There is no reason IMO to go to any other bootloader version.
Click to expand...
Click to collapse
Oh okay, that clears up yet something else I did not understand
Thanks for the tip on the bootloader version; I will leave it at SPL 1.04.
That being said, I am currently in the middle of the Radio 1.20 thread; I have not finished reading it yet (I can only do so much at work before people wonder what I am doing). Have you upgraded to Radio 1.20? If not, what radio are you running and what do you think of its stability and/or functionality?
Thanks!
I'm running the 1.20 radio. It and the 1.35 TyTN ROM are the best combination I've used so far.
I managed to upgrade my phone to aku 3.3 using pof's method(bootloader 1.01 MFG) . Then, out of no where, I tried to use MTTY to upgrade my radio rom
It started as usual with the status bar moving. Suddenly some error messages came up.
Now, the phone is dead completely. I can''t even enter bootloader mode.
Is there a possible way that I can still save it??
Help!!!!
Have I bricked my device? Help plz
I managed to upgrade my phone to aku 3.3 using pof's method(bootloader 1.01 MFG) . Then, out of no where, I tried to use MTTY to upgrade my radio rom
It started as usual with the status bar moving. Suddenly some error messages came up. Can't remember exactly, but like some address can't find error.
Now, the phone is dead completely. I can''t even enter bootloader mode. Only when I take out the battery and plug in the charger cable the red light comes on. I looked the upgrade problem page, my symptom doesn't match any.
Is there a possible way that I can still save it??
Help!!!!
I had something similiar happen a little while back. What I did was pull the battery out and leave it out for a while, maybe a few minutes. I then put the battery back in and held the two side buttons and hit the reset button to put me into bootloader mode. I then cabled it to my computer and flashed a new OS via mutty. That got my phone back and operational.
@float. Nuh, it didn't work on my brick. Prob i will have to take it back to Tmobile if they kind enough to repair the no warranty phone i bought on ebay.
Sorry to have opened a new thread, I was so desperate.
Plz delelte it.
how exactly did you try to update the radio using mtty?
I download the 1.27 shipped radio rom. P.S. It seemed to be a german version, not sure whether that caused the disaster.
Using NBHextract to get the single GSM.NB file, then in MTTY, typed
USB> task 32
USB> lnb GSM.NB
Before flashing, just had it upgraded to the HTC AKU3.3 OS rom only. The old version radio rom version before flashing was 1.18.
Maybe the order i flash is wrong. I flashed OS first then the radio rom.
just guessing
ok, you loaded the radio rom code where os.nb should go. That may have caused mega bad blocks in flash. Can you even get bootloader mode if you reset using Wiki directions to obtain Tri-color bootloader?
Yes. I have tried many ways wiki suggests. Such as removing the battery leaving it more than half an hour and plugging it to the usb cable without battery. still can't get to the tri-color bootloader mode. Basically, I just can't turn on the phone.
If you connect it to the computer, can it communicate w/the PC? If you hear the windows tones try opening up mtty and see if you can communicate.
i'm stuck in the same place
for me it happened during extrom flash
Try removing the battery for a bit (a few minutes, maybe half an hour). Then, put the battery back in but don't plug the usb cable in. After that, hold the two side buttons as if you're trying to get it to go into the bootloader. Hit the reset button a few times with your stylus and see if that gets you to the bootloader. That's what worked for me.
tried that
tried removing battery and connecting usb
nothing helps
is there a place that fixes tytn in belgium ?
is there a way to flash a new rom via mutty ?
cause i still have the boot loader, but the phone still in the splash screen
when i type info 2 in the mutty command prompt i get this answer
Cmd>info 2
HTCSQTEK_203”µ·êHTCE
i think it's not realy normal
diffda said:
is there a way to flash a new rom via mutty ?
cause i still have the boot loader, but the phone still in the splash screen
when i type info 2 in the mutty command prompt i get this answer
Cmd>info 2
HTCSQTEK_203”µ·êHTCE
i think it's not realy normal
Click to expand...
Click to collapse
well your not supercid... your still locked to qtek
Look here and unlock your phone before doing any flashing!
http://forum.xda-developers.com/showthread.php?t=295751
to late i ve done that tow day's ago , now the only way to make my phone back to life, PB + KITL method i think
god bless KITL
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
Purchased the Raphael in Hong Kong, it does not have SIM lock.
It was HARDSPL by myself, done.
Then I flashed other rom - just OS, and the phone worked well. Yesterday, I saw the screen stayed on TRI colors, I made soft reset for couple time, the device is able to load Windows. Thus, I thought the ROM - OS is not good, so I flashed other ROM (OS) bt micro SD card, and it said the job was done and succeed.
But the phone cannot enter Windows anymore, just stayed on the TRICOLORS screen.
What can I do?
Thanks!!
Did you try a hard reset?
did you used the right hardspl?
because there are olso different for wm 6.5
greetz
n3m3s1s said:
did you used the right hardspl?
because there are olso different for wm 6.5
greetz
Click to expand...
Click to collapse
What? HardSPL is HardSPL. It's device specific, not OS specific. As long as his device has been HardSPL'd he's good to go. shgman, when you're at the tricolor screen, connect the phone to your computer. You can't use activesync so don't try. At the bottom of your screen, does it say USB? If so, try to flash again. Sometimes I get incomplete flashes from my SD card.
silentP said:
What? HardSPL is HardSPL. It's device specific, not OS specific. As long as his device has been HardSPL'd he's good to go. shgman, when you're at the tricolor screen, connect the phone to your computer. You can't use activesync so don't try. At the bottom of your screen, does it say USB? If so, try to flash again. Sometimes I get incomplete flashes from my SD card.
Click to expand...
Click to collapse
SlientP, I agree with you. HardSPL is hardSPL, then OS is OS. Yes, the device is able to Laptop while the USB cable is plugged in, the bottom of screen - white area say USB.
I had downloaded official ROM from HTC Hong Kong, and tried to flash the device back to factory default, the package is including Radio, done again. But......... the screen is still stayed at TRICLOLOR screen.
Thanks, shgman
I appreciate somebody who can help me?
I remember having a corrupted ROM install and had to manual enter into the bootloader. From there I was able to flash from my computer just fine... Wanna try that?
Try flashing stock rom then flash custom rom. It the custom rom fails again then its a bad rom or hardspl is not working right.
Got a problem. I wanted to upgrade to new OzRom today so did normal tasks I did last 40 times.
get new rom and unpack it.
Rename image to LEOIMG.nbh and put it to root of SD card
perform mtty task 29
reboot, phone goes to bootloader then goes to normal grey screen it just says loading and that is it. It gets stuck there.
I had tried flashing via sspl, it sees the phone, screen on phone changes to black htc screen but loading bar sticks at 0%
I have HSPL 2.08 on the phone, I tried to re apply HSPL but it states error with usb connection. Can not upgrade radio from sd card or via sspl as well.
Did try previous rom that worked but it also does not want to load?
Any ideas?
Try flashing back to your original rom. Try that via sd card which should replace hspl back too your stock spl and then start the process from scratch.
mitty task 29 has a serious problem. you are not the only one. if ur hd2 is from tmobile. try T-Mobile_HD2_MR_Software_2.13.531.1. flash it just like the way you do. if doesnt work then copy it to sd card and flash it. . it'll return to its original stage.
pnjboyzz said:
mitty task 29 has a serious problem. you are not the only one. if ur hd2 is from tmobile. try T-Mobile_HD2_MR_Software_2.13.531.1. flash it just like the way you do. if doesnt work then copy it to sd card and flash it. . it'll return to its original stage.
Click to expand...
Click to collapse
It is odd that it did it now as I have not had any problems for last 8 months
Did not work!!
Update is that I managed to do the HSPL3 again over USB which I could not do before but I can not flash any roms.
Have you tried flash to ActiveSync????
Ok got it going again.
I hade my HSPL as 2.08.0000 and cotula signs all over it. Flashed again and it again went to the same one. However apparently .0000 means it is stock (no idea why stock rom did not want load). Flashed it again to HSPL2 and then upgrade to 3 fixed it.
alesscam said:
Have you tried flash to ActiveSync????
Click to expand...
Click to collapse
It would not help as I have done mtty before so no os on it.
no problem with mtty...
after mtty
you can press red botton for sofreset and press volume down for go to Bootloader
from bootloader you will see USB ,
this if your leo is connect to PC