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 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
Hi,
i flashed a rom 2 weeks ago, everything went well. yesterday i wanted to flash another os but before i could flash it, it seemed to get bricked. It stucks on the "HTC Splash" (not the WM6 Splash). I read a lot of threads and wiki threads but i don't unterstand anything! What i've to do to unbrick my phone? I tried to flash another rom but after 0% of flashing a error appears.... flashing with sd card doesn't work, too it changes to bootloader after the "Loading..." screen
i havent got hardspl or something...
please help!
UPDATE: i got the sd flashing to work... same thing but: now it stucks at the WM splash, not the t-mobile/htc one...
You need to find out what SPL you have (I'm guessing 2.03 but if you have 2.10 olipro then its got Hard SPl on it) and then do a search for "bricked SPL x.xx". You will probably find a HEAP of posts. However, some advice that seems to recover a small minority (sometimes with the "No GSM" error) -
1st thing to do is do a hard reset. Both softkeys and reset with stylus. Hold in all buttons until it asks if you want to reset to factory. Press "R" on the slideout keyboard and the "Space".
Hopefully this will fix. If it doesn't, Put it in bootloader, connect to pc (make sure "Allow USB Connection" Active Sync settings have been unticked) and run the SHIPPED STOCK ROM. This is the rom the Hermes came with originally. This MAY fix it otherwise you're in for some major reading and hair pulling.
If you should fix this then PLEASE, for the love of god, Hard SPL your Hermes before going into the wide world of flashing.....
Good Luck...
thanks i'll try it. hard reset causes kinda... nothing^^
i hope i can fix it otherwise i'll buy a touch pro
...but i think it doesn't work, because i flashed a shipped rom via sd card yesterday and the problem is still there... isn't there any way to put hard spl on my device, yet?
Try re-installing the stock rom again using sd card (if thatys how you did it last time), it could've been a bad flash. I've had those a couple of times myself. Just remember to install Hard SPL if you're successful as it makes it SOOOO much easier to recover from bad flashes.
Last thing to check would be if you have "bad blocks" using MTTY. If the boot sector has been stuffed up this may cause this problem. Do a search through the wiki, its been covered extensively...
Cheers...
okay i think my problem is solved: t-mobile replaced my device
first thing i'll do with my new device: HardSPL^^
anyhow thanks!
Upgrade successful but now stuck
I have a Three (au) Dopod 838 pro, which I upgraded from the original Windows Mobile 5 to the Three Windows Mobile 6.0 ROM. Unfortunately I didn't read up on this site first, I thought it would be straightforward since it was a ROM from the manufacturer and all, so I haven't Hard SSPL.
The upgrade reported as successful and my PC disconnected but the phone won't boot, it sticks at the Dopod screen with some numbers at the bottom. They are:
M 05 R 1.47.30.10
S 04 G 32.80.7020.20H
B 07 D 3.54
I have tried hard resetting, and returning the phone to bootloader and reflashing the same new ROM image, always with the same result.
On the bootloader, it says
HERM100
IPL-1.04
HERM100
SPL-2.03
Is there anything which can be done or is it a trip to the service centre (wherever that is)?
Just checking - Hard reset = both soft keys above the dialler closest to the lcd and reset with stylus. Hold in until it asks if you want to reset to factory. Press r on slideout keyboard then space.
This is a hard reset, not just using the stylus.
Otherwise, you have a LOT of reading material to go through with (maybe) no actual solution.
Cheers...
tried that
Thanks, but yes, I had tried that, a number of times. I think the phone will be going to a service centre today.
When i tried to install any firmware the progress stop at 11% and the Hermes only turn on in bootmode, any idea??
rmorera84 said:
When i tried to install any firmware the progress stop at 11% and the Hermes only turn on in bootmode, any idea??
Click to expand...
Click to collapse
I had that problem and few more with my Hermes.
While it didn't help me, this suggestion by ultramag69 may help you...
Use the sd card method to flash a new rom, instead of a USB cable/Windows computer.
1. Format a 2Gb or less sd card to FAT32, copy the large 50MB-90MB .nbh file onto it and rename to hermimg.nbh
2. Insert the card into your Hermes and reset to bootloader (hold OK & POWER and push RESET for a sec with the stylus)
3. If you haven't stuffed up the other steps, follow the prompts.
Hope this helps!
Just one other thing summoner, make sure you have Hard SPL V7 installed. Otherwise the ONLY rom I'd try flashing like that is the SHIPPED STOCK ROM. Its so the CID will be recognised and won't cause a brick.
rmorera84, unless you've installed Hard SPL V7 then find the SHIPPED STOCK ROM and flash that, anything else may permanently brick your Hermes.
If you have Hard SPL V7 (IPL 1.04, SPL 2.10 oli) then flash what you like...
Cheers...
- Installed latested Orange rom, that I know of - SPV_M3100_ROMUpdate_1007
- installed Hard SPL 7 & applied SIM unlock/super CID
- re-installed TNT TNT.19199_Professional_Hermes
The result is:
IPL-1.01
SPL-1.40.Olipro
I suppose I should upgrading the radio rom now!?
I am told don't try fixing what isn't broken - and it is working. 3G iNet, Phone, WiFi, BT - all good atm.
Or is there a particular update I should still install?
Thanks!
SUMM0NER, you're using an older, not so safe version of Hard SPL. The Hermes is downgraded to SPL 1.40 when you sim/CID unlock your phone. Best idea would be to re-install Hard SPL V7. Its a later version that seems less prone to problems when flashing.
Go back to the Hard SPL thread and get Hard SPL V7. I had the same thing happen to me when I unlocked the Hermes, nearly cost me my handset.
The steps are unlock Hermes, Install Hard SPL then upgrade OS.
Cheers...
Do I need to re-apply the OS rom file?
I just reinstalled Hard SPL7, now shows as IPL-104, SPL-2.10.Olipro.
Thanks!
My hermes only work whit this rom:Schaps_WM6Pro_ESN_3.54b-0808_Full
Because whit any other rom they stuck at 11%.
This is the info or the phone:
IPL-1.01
Spl-1.40.Olipro
Whit the first rom the htc boot but the phone funtion don´t work.
rmorera84, refer to my last post.
SUMM0NER, no. You have loaded the os, the reason you put Hard SPL V7 is if you want to upgrade the radio rom (not a good idea unless you are experiencing problems) or wish to change the os. Just means recovery is easier than if you didn't have it.
Cheers...
Many thanks ultramag69.
rmorera84 what branding is your Hermes (ie: Orange M3100, T-Mobile Vario 2, Vodeaphone V1605 etc...)?
Can I assume your Hermes is working right now?
If it is download and install HardSPL V.7 (attached to the bottom of the first post!)
Ones done verify that it installed correctly by holding the OK & Power button and pushing reset for a sec. The screen should display the coloured bars and say towards the centre: SPL-2.10.Olipro
It´s Cingular 8525, i could install the HardSPL V.7, now what rom i can flash??
You didn't confirm if it is working right now!?
If it is not working, try one of the official WM5 Cingular roms from this list. If that worked apply HardSPL 7 and take it from there.
Ones you downloaded the Cingular rom update you will have to keep unpacking the .exe files until you come to the actual .NBH file (WinRAR works for me).
Then follow ultramag69's instructions on flashing the rom via memory card.
Works, now i have this info:
HERM100
IPL-1.04
HERM100
SPL-2.10.Olipro
I download the official Cingular WM5 rom, but. i don´t know how install this rom by memory card, could you help me??
Excellent!
Try downgrading to the Cingular rom via USB. Just double click the EXE and follow the instructions.
To use the memory card method follow these steps...
0. unpack the .exe file containing the rom with Winrar (right-click exe then choose "Extract to...\")
1. Format a 2Gb or less sd card to FAT32, copy the large 50MB-90MB .nbh file onto it and rename to hermimg.nbh
2. Insert the card into your Hermes and reset to bootloader (hold OK & POWER and push RESET for a sec with the stylus)
3. If you haven't stuffed up the other steps, follow the prompts.
The reason to use the memory card to upgrade a rom, rather than a usb cable, is to cut down on failed upgrades (dodgy Windows/usb port/usb cable/etc..).
All working? Try upgrading to a Hermes rom that didn't work previously.
Any rom you can find in the Hermes section. Go to the WM06 part of the forum, theres a sticky at the top with about 50 older roms and you'll find other roms there too (latest is wm6.5).
Cheers...
i install the official WM5 AT-T version the WM6 AT-T, but, i still whit the no-gsm problem, can i flash i radio? or what i can do??
You may not be able to fix this, if you know what the original SHIPPED STOCK ROM was and can find it, then flash that. It may not work, if it gets stuck at 11% - 17% mark it means the radio ROM is stuffed and the memory area is corrupted. Not fixable.
You could also try, if you know what it is, the original radio rom by itself. Again, if you can't get it to work, you have a PDA but won't work as a phone ever again. Sorry to be the bearer of bad news.
Im to having the same problem, it keeps going back to the 2.1.Olipro boot loader.
I tried the memory card option and it starts to install but then stops.
Does anyone have and sugestions?
Cheers
Help Help
Hi, I got my Hermes 8525 in boot mode what i did is to install this Schaps_WM6Pro_WWE_4.00_Full.exe now my hermes is working but i want to unlock it..what can I do cos everytime i try got in to boot mode again..any help tks.,..
I have flashed my x7500 before using the Athena_WM6_TMUK_2.35.110.4 rom and that worked. Bootloader said spl v1.0 so I tried the authenaunlocker which said it worked and from then the bootloader said spl 1.2 olipro
I then thought I could update to AGB v3.0 , it seemed like it worked but when it rebooted, it shows some mad pixels like a corrupt image and then seems to boot but with a black screen. I can hear it do the ping it does when it asks to calibrate the screen but it is entirely black :-(
I have tried an sd card method of loading a new rom but it always fails after a few seconds with red numbers 68002 and then goes back to the tri color boot loader.
I tried ultravanilla rom renamed to ATHEIMG.nbh in the sd card (formatted to fat32) and that does the same thing with the red numbers.
have I completely bricked it?
I should say that I'm on Windows 7 and I've tried the MAC change fix but the mtty app doesn't give me a usb port to select, just com1 and com2
I tried the windows exectuable for updating the rom but it always fails with error 244 invalid model id.
here's the images I see
[edit] hurray! the mtty thing worked after I found an old laptop that had xp on it to use, as soon as I had that I downloaded activesync , unchecked allow usb connections and fired up mtty, that had an entry for usb and then I just followed the instructions and was able to change the id, after that, I was able to use the windows exe rom update. I'm now back to where I'm started and have donated to cmonex!
hi i have the same problem with my t-mobile ameo.
the tri-screen even shows the same digits as yours.
did you manage to get a fix for it. or is it totally bricked
If you can enter the bootloader (tricolor screen) it should be possible to reactivate your Ameo. I have flashed my Ameo with wrong SPL ROM too (because it was labled as SPL 1.2 but is SPL 3.5).
If you don't have a WinXP system on your hand, try to flash with SD-card. You need a FAT32 MiniSD card (not SDHC!) or FAT32 MicroSD with MiniSD adaptor.
Format the card and copy the ROM file (for the right SPL!) to it, rename the file from RUU_Signed.nbh to ATHEIMG.nbh. Then go to the bootloader and the Ameo should be ready to flash the new ROM.
If you have a WinXP system you can try to enter the bootloader (remove the MiniSD card before) and then connect your USB cable. The bootloader should change from "Serial" to "USB" and should be ready to flash a new rom.
If your Ameo is fractious you can find some good tutorials here.
Purzelkater said:
If you can enter the bootloader (tricolor screen) it should be possible to reactivate your Ameo. I have flashed my Ameo with wrong SPL ROM too (because it was labled as SPL 1.2 but is SPL 3.5).
If you don't have a WinXP system on your hand, try to flash with SD-card. You need a FAT32 MiniSD card (not SDHC!) or FAT32 MicroSD with MiniSD adaptor.
Format the card and copy the ROM file (for the right SPL!) to it, rename the file from RUU_Signed.nbh to ATHEIMG.nbh. Then go to the bootloader and the Ameo should be ready to flash the new ROM.
If you have a WinXP system you can try to enter the bootloader (remove the MiniSD card before) and then connect your USB cable. The bootloader should change from "Serial" to "USB" and should be ready to flash a new rom.
If your Ameo is fractious you can find some good tutorials here.
Click to expand...
Click to collapse
hi I have the same problem this guy had, I have one question what rom should I use ? can you give me a link please
Purzelkater said:
If you can enter the bootloader (tricolor screen) it should be possible to reactivate your Ameo. I have flashed my Ameo with wrong SPL ROM too (because it was labled as SPL 1.2 but is SPL 3.5).
If you don't have a WinXP system on your hand, try to flash with SD-card. You need a FAT32 MiniSD card (not SDHC!) or FAT32 MicroSD with MiniSD adaptor.
Format the card and copy the ROM file (for the right SPL!) to it, rename the file from RUU_Signed.nbh to ATHEIMG.nbh. Then go to the bootloader and the Ameo should be ready to flash the new ROM.
If you have a WinXP system you can try to enter the bootloader (remove the MiniSD card before) and then connect your USB cable. The bootloader should change from "Serial" to "USB" and should be ready to flash a new rom.
If your Ameo is fractious you can find some good tutorials here.
Click to expand...
Click to collapse
it is not working...
keep your cool
the most important thing is to keep your cool, I've been in trouble before and managed to sucsses, first of all if you are able to go into bootloader you're fine, it seems to mi you flashed wrong spl, the AGB v3.00 is for spl 3.5 only and for what I understand you have spl 1.2, also i my experience you should work with win xp, i have my laptop with 2 os xp and 7, just to do rom loading on my 3 advantages, so if you are able to put your athena in bootloader plug it to your pc your athena sould change from serial to usb, if you can manage that you are almost done, now all you have to do is flash a compatible rom spl 1.2, if you still want agb v.3 you need spl 3.5 and the only way to achive that is to flash athena projet 4 rom, only when that is acomplished you would be able to load an spl 3.5 rom. I hope this help, keep us posted.
hi i have a pc on windows xp sp3 with htc 4.5 it does not pick up my phone bit it will try to load the windows 6 advantage rom,but after it reaches 2 percent ,the phone resets.i have done the same thing as above,i tried to flach a michy 3.5 rom over windows 6 on 1.25,i can get into bootloader but everytime i flash my phone resets.my mini drive is formatted,so could the problem be with the onboard sd card? if so in plain english could someone take me thru it step by step on hpw to access and format that,to see if it makes a difference,many thanks,and a nice contribution to anyone who can help me,and please if you start talking about hot keys,please state which ones,as every key is a hotkey many thanks curzie,if anyone ever needs pc or laptop advice pm me thanks
Who reflash device with this trouble ???
Working - or not ???
flash rom problem
hi, I'm in the same situation and sorry for my English, I have a X7500 I unlocked the radio, and then I installed the 3.0 rom agb all went well, but on the first reboot the system does not start, black screen, if I press the volume button turns on but displays the volume and the touch does not work, I can not make it go into bootloader because it turns on and remains on the flag!
Can you help me?
thanks
Solved
Check out my post http://forum.xda-developers.com/showthread.php?t=2172291