Related
Hi all, first of all you need to know that I have read the WIKI and have had a look through the forum before asking these questions.
I've just bought a Hermes (I had a Magician before) and would like to get wm6 black edition on it. I've made my phone SuperCID using the tools on this site and that worked nicely. Problem I'm having is that when I start the wm6 upgrade I'm asked what bootloader my phone is running.
Am i correct in saying that the bootloader is the same thing as the IPL ? I'm not sure about that ....
When I turn on my Hermes it comes up with a couple of numbers but only one of them "looks right" : 1.23
Is that my bootloader ? That version doesn't show up in the menu when starting the wm6 upgrade
Regards,
John Gillespie
Be careful, you might need to do some more reading before you start flashing. Put your device in bootloader mode and it will display the IPL / SPL.
Hold the side OK and power button together then soft reset all at the same time to get to the boot loader.
Before you flash make sure you look at installing Hard SPL - should stop the phone getting bricked if anything goes wrong.
mrvanx has written some good guides.
http://www.mrvanx.myzen.co.uk/hermes_guide/
thanks !! i'm running 1.04, now I can upgrade
When I was reading through the black edition wm6 rom thread it made it look as if HardSPL was integrated in the rom. Is that the case or do I need to manually install HardSPL before doing anything ?
That is the case, it pushes the latest version but it's always a good idea to manually install it anyway - just in case.
ok thanks for the tip
other thing I was wondering about was if anyone had bothered testing which radio rom performs best ?
opinion differs but from what I've seen the general consensus is that you should use anything 1.27 or later
Take a look at my guide, it will take you through it all. The radio I use in the guide is 1.38.00.10 I havent updated for the new Imate radio as people are reporting battery drain effects etc.
So far there isnt any known issues with the radio I use in the the guide.
It will take you through upgrading to the latest version of WMXL,LVSW or Black.
thanks for your time
I'm now running wm6 black edition on my Hermes100 Orange France unit and have set my hardware keyboard to french. I've read that it isn't possible to change the virtual keyboard, is this true or has a workaround been found on this issue ?
I've also been looking for msn live but can't find it anywhere :/
I looked through the wiki as suggested on a thread but couldn't find it
anyone know ?
All rite here we go, in advanced i thank u guys for trying to help me out here.
First, i'm a n00bie compared with the most of u guys.
My Device:
Tytn Herm 300
OS: Schaps Purple 3.30c
SPL: Hard-Spl 2.10 oli
Radio: 1.16.00.00 !Hmzz...that's the problem!
My phone functionallity sucks...some how it keep loosing connection while i see the phone indication bar up to 3 bars. So i decided to do something about it.
Beeing a noob i thought it got to do something with the OS. So i upgrade it to Schaps's wonderfull purple WM6 Hermes 3.30c and loaded the Hard SPL 2.10 oil V7. All went great, and my Hermes never looked so cool before.
But now i'm trying to upgrade my radio, which is still version 1.16.00.00, to what ever better version. I tried every radio upgrade possible from this list:
http://wiki.xda-developers.com/index...actedRadioRoms
Every single one starts well. passed the information retrieving from my phone. Confirmed the update, and then there was the installation progress bar....
All versions of the radio roms i downloaden get stuck in here. It doesn't even start..0% and error... And really i dun have any idea why.
So after re-flashing a gazillion times, i decided to ask help to the allmighty XDA community. So pls, if anybody there got a suggestion or the solution...i would be so thankfull and will slaughter a goat to worship you
If you've got schaps Rom and HardSPL on your phone then you obviously don't have problems flashing or with PC/phone comms.
When you try flashing the radio, how long do you wait before deciding it doesn't work? I've found that some of them can take what seems like a really long time and I'm tempted to unplug and start again.
Maybe try again, then go make yourself a cup of tee/coffee or get a beer then come back 10 minutes later. If the upgrade still hasn't worked we'll have to look a bit deeper
RaDeNRFX said:
- I am so sorry posting this twice in the wrong sections, it seems that i'm a really noobie forum user - But i finally found the rite section. So my humble excuses.
All rite here we go, in advanced i thank u guys for trying to help me out here.
First, i'm a n00bie compared with the most of u guys.
My Device:
Tytn Herm 300
OS: Schaps Purple 3.30c
SPL: Hard-Spl 2.10 oli
Radio: 1.16.00.00 !Hmzz...that's the problem!
My phone functionallity sucks...some how it keep loosing connection while i see the phone indication bar up to 3 bars. So i decided to do something about it.
Beeing a noob i thought it got to do something with the OS. So i upgrade it to Schaps's wonderfull purple WM6 Hermes 3.30c and loaded the Hard SPL 2.10 oil V7. All went great, and my Hermes never looked so cool before.
But now i'm trying to upgrade my radio, which is still version 1.16.00.00, to what ever better version. I tried every radio upgrade possible from this list:
http://wiki.xda-developers.com/index...actedRadioRoms
Every single one starts well. passed the information retrieving from my phone. Confirmed the update, and then there was the installation progress bar....
All versions of the radio roms i downloaden get stuck in here. It doesn't even start..0% and error... And really i dun have any idea why.
So after re-flashing a gazillion times, i decided to ask help to the allmighty XDA community. So pls, if anybody there got a suggestion or the solution...i would be so thankfull and will slaughter a goat to worship you
Click to expand...
Click to collapse
ach2 said:
If you've got schaps Rom and HardSPL on your phone then you obviously don't have problems flashing or with PC/phone comms.
When you try flashing the radio, how long do you wait before deciding it doesn't work? I've found that some of them can take what seems like a really long time and I'm tempted to unplug and start again.
Maybe try again, then go make yourself a cup of tee/coffee or get a beer then come back 10 minutes later. If the upgrade still hasn't worked we'll have to look a bit deeper
Click to expand...
Click to collapse
I waited till the Program says connection error...and send me to recovery proces. And i've been making hella tons of coffee after trying to flash that many Radio Roms. Any other suggestions? I'm so desperate
Ok, maybe some more info...
Do you see 'NO GSM' during the phone boot process?
Do you have no radio at all or just intermittent reception?
Are you running Vista?
What is the connection error number?
If you've lost the radio but have hard SPL it may just be a case of re-flashing an original manufacturers ROM (which will include the radio) then start your upgrading again afterwards. Don't forget to back-up data before flashing.
If you do flash a manufacturers shipped rom - check that you still have HardSPL afterwards.
ach2 said:
Ok, maybe some more info...
Do you see 'NO GSM' during the phone boot process?
Do you have no radio at all or just intermittent reception?
Are you running Vista?
What is the connection error number?
If you've lost the radio but have hard SPL it may just be a case of re-flashing an original manufacturers ROM (which will include the radio) then start your upgrading again afterwards. Don't forget to back-up data before flashing.
If you do flash a manufacturers shipped rom - check that you still have HardSPL afterwards.
Click to expand...
Click to collapse
Well the weird part is "No GSM" appeared occasionally...some times it shows it sometimes it's not showing it.
No...i'm a Vista hater. And dun have the original manufacturers ROM. I've got the "T-Mobile Vario II" from The Netherlands..so if anybody got a link for the original version i'd be thankfull.
The Radio it self is intermittent and very inpredictable...for example:
Radio indicator says i got full recieve:...but i can't call or recieve any.
Connection error: 262 (which is, if i'm not mistake a connection error.) Which is bull cuz i'm re-running every other ROM's upload with the same way and succeded/
Radio indicator says no reception and shows an exclamation mark:...and my GF just called me to hurry up and pick her up :/
But the weird part is...it seems that my radio ROM is locked somehow. I can upgrade or downgrade SPL's and OS ROM's but not the Radio ROM.
I've tried to use MTTY by now and followed the manual bellow: (Problem 5)
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems#problem5
But it began with invalid password. Procede as written and it didn't helped.
More suggestions are welcome
My bad...i didn't looked well enough. It is saying No GSM the whole time.
More information:
I've checked the Device information on the Hermes now some information are blank:
Radio: Blank
Protocol version: Blank
IMEI: Blank
All other information field are filled. Been spending hours reading tutorials and manuals...and nothing. HELP!
OK,
This isn't a problem I've had myself, but loads of other people have and there are quite a few threads on how to unbrick from here... you're going to have to do a bit of reading.
This page shows the different combinations of OS/radio/brick type etc and should point you in the right direction for the correct course of action http://wiki.xda-developers.com/index.php?pagename=Hermes_Unbrick
Then read through this thread http://forum.xda-developers.com/showthread.php?t=286755 . It's got really long but read the beginning where POF describes the types of problem and also the solutions. Then it's probably best to jump to somewhere near the end and pick someone who has a similar problem.
It sounds to me as though you need to just flash a radio in nbh format, but please do some more reading before you do this to check my advice - as I said at the beginning, I haven't had this problem so I'm only giving advice from what others have written.
ach2 said:
It sounds to me as though you need to just flash a radio in nbh format, but please do some more reading before you do this to check my advice - as I said at the beginning, I haven't had this problem so I'm only giving advice from what others have written.
Click to expand...
Click to collapse
I am really thankfull of ur post. Unfortunately, i've been doing some reading. Including the link u gave me. The problem is that i can't upload/flash Radio in nhb format.
As i described in the first place, i can't load a nhb format radio in RUUWrapper.exe properly. It can start the proces..but it always end up with a connection error code 260/262 during the installation progres bar (0%).
The solutions some ppl tried in ur link is often not my case. And the similar cases i have tried where i end up with the same grumpfy situation.
have you tried to flash the radio using the SD card method? I too have a cable connection problem but I fear mine may be hardware failure.
Yap...and no luck
UnBrick the Bricked Hermes with "SPL 2.03 - IPL 1.04 - NO GSM - KITL Disabled"
There are many people have this kind of brick but still no solution for it.
I want to ask the mods to make this thread sticky so if anyone find a sulotion for this type of brick would post it Here.
Summary :
IPL: 1.04
SPL: 2.03
CID: NO CID (Request timeout on mtty.exe)
NO GSM
KITL Disabled
I have tested all the possible sulotions available in the wiki but none of the could help me unbrick my hermes.
P.S. : Please just post your sulotions here NOT your comments like "you should superCID your device first", "It's your fault to use telstra wm6",....
Has anyone found a sulotion for this???
You Pm-ed me asking what to do and i pointed you in the correct direction so why have you started this thread?!
Hermes Unbricking Thread
and
Wiki page: How to unbrick your bricked hermes
EVERYTHING you need is there, you just have to read.
Maybe You do not read my Pm!
I have read all the wiki and thread concerning my problem several times!
The simple truth is that some phones are unrecoverable and have to be sent off for repair. Yours is one of these situations and I very much doubt that this will change. More and more of the pioneering technical guys will have updated their Hermes to another phone and the much admired POF has not been seen since he was accused of stealing...
The tacit feeling is that there is enough information and utilities to prevent people bricking their phones (i.e HardSPL and Update from MicroSD card) so if you do find yourself in this unfortunate position and can not recover your phone then you have to bite the bullet, and be better informed the next time.
POF accused of stealing !!!!????
What's that all about?
I dunno if I have a the same problem, but a similar issue, and trust me I am "PC guys, AMD fanboy, A+ tech:"whatever you wanna call i, I am expanding my horizons and I got into the mobile PC world. Trust me I am NOT Google lazy, i have read and read and read and researched and cross-checked and tried literally everything. I am stuck, I know what is wrong with my Hermes, I know where it messes up, and I DO see threads in other sites with 99.9% the same problem I have and I see NO soultion or anyone who knows or Really wants to help, I feel for Koorosh we need help, I have come to terms if have to send it away to repair. That bugs me I got it Literally 3 days ago, and ONLY used the OFFICAL AT&T WM6 Rom to upgrade
on my bootloader all I see is this........
IPL: 1.04
SPL: 2.03
I have too see in my display
IPL: 1.04
SPL: 2.03
when i can flash radio 1% and restart device!
try it
i also had the same problem.i have resolved using rom update through memory card.look for it in wike section.all the best.try it with original rom that came with the phone.
this will not work in this site again no solution for bricked spl2.03 cid locked
biswajitghosh said:
i also had the same problem.i have resolved using rom update through memory card.look for it in wike section.all the best.try it with original rom that came with the phone.
Click to expand...
Click to collapse
Do you know to read micro sd flash not work when device is not superCID!!!
I maybe have the same issue.
From the HTC ROM I flashed my device to Shannix Grass rom, a few days later I flashed to Satin Black rom, so far so good. After that I want to flash back to Shannix Grass and my deviced crashed. While booting he stuck at the HTC screen.
I tried to hard reset, flash another rom (stuck and reset at 1%), flash the bootloader (stuck and reset at 7%). After the failed ROM flashing I get error 270 image is corrupted.
In mtty I tried to format the NAND, and tried the erase command, nothing worked.
How can I diagnose the problem further. Is it possible to see why the ROM update failed or why the OS won't boot? I did some monitoring with USB monitor but I didn't get results where I get some conclusions of.
---
HTC Integrated Re-Flash Utility, Common Base Version : 1.51d
Device Name: HERM100, Bootloader Version : 2.03
Built at: Jun 16 2007 01:57:22
Copyright (c) 1998-2006 High Tech Computer Corporation
(My device is Herm200)
wow , i have the problem too. i almost live in phoneless .
.
SOLVED !!!!!!!! my phone now works
If your device became inoperable like mine, because i had a failed ROM upgrade,and the device failed to power up i have good news for ya.
MY DEVICE info is as below.
Problem:
Phone does not boot up, and looks like a red brick.
IPL: 1.04
SPL: 2.03
(it always gave an error 206 at 1% of any ROM update i tried)
Solution:
I downloaded the official WM6 ROM from the HTC's website below,
http://www.america.htc.com/support/8525/software-downloads.html
Then reset my device to the bootloader screen.
(holding the 'ok' button and the 'power' button and then using my stylus to push the 'reset' button close to the USB port.
i then disconnect the USB cable from my phone, and the display showed 'serial'.
i then ran the downloaded file, and waited till the collecting information from phone window came up, then i connected the usb cable back to the phone.
it connected, and VOALLA!!!... it started the update.
at least its better to have a working phone(without all the custom stuff), than none.
I hope this was not booring( with all the detail and all), but i hope it will help anyone out there who's device wont bootup.
wow , congraution!
i will take the method. but i wonder should i have to get the "connecting time" in the right point, or the computer can't find my phone??
( hope u know what i mean?)
Um.... i cant say for sure
weyun0513 said:
wow , congraution!
i will take the method. but i wonder should i have to get the "connecting time" in the right point, or the computer can't find my phone??
( hope u know what i mean?)
Click to expand...
Click to collapse
Well.. i can't say you should wait 1 or 2 seconds, but just plug it in as soon as you get that screen. i hope it works for you tooo.
what was ur exact situation beforeu can unbrick ur phone???
IPL?
SPL?
KITL??
NO GSM ERROR?
what was the rom that has bricked ur device??
where did it stuck during the brick phase?
is that 1st splash,2nd splash,...??
This method did not work for me!!!!!
Try the Official Cingular ROM
koorosh_bsboys said:
This method did not work for me!!!!!
Click to expand...
Click to collapse
My Hermes "red hot brick" happened when i tried upgrading to aCRCs_PHKv12r8, from a Schaps_WM6Pro_Hermes_4.31_WWE_Full ROM.
My device is a Cingulat 8525.
The upgrade went to the tricolor screen, and after 1% , my phone magically went off. I tried powering on, but it went to the tricolor screen again showing
IPL 1.04
SPL 2.03
and underneath showed "serial".
me too i'm having the same problem....any experts out there that could help us?
Hi guys. Mass apologies for my stupidity, but here goes...
I have now spent over 2 days on this site reading all that I can, but I am at a loss and desperate for your expertise!
I am running a UK Tmobile Vario 2. I was having problems with the phone crashing constantly and not getting any signal at all so I installed WM6 yesterday hoping this would help. Its not crashing as much, but its still not getting any signal.
After reading loads of threads and posts all over the place (I have read enough WIKI to make my eyes bleed), I think I need to update the radio version. This is the information I can gather from my phone:
Bootloader info-
Herm300
IPL-1.04
SPL-2.03
I cant figure out how to enter commands in bootloader to gather any more info I tried the mtty.exe thing with no avail. When I go to "device information" it reads like this:
ROM version: 3.60.110.4
ROM date: 09/05/07
Radio version: SAYS NOTHING!!!!
Protocol version: SAYS NOTHING!!
IMEI: SAYS NOTHING!!
When I do a soft reset I get red letters and numbers appearing and not the "no gsm" message.
This is a 2nd hand phone off of ebay as my original phone was stolen. I have contacted Tmobile, but they refuse to help me as its not the original phone that I bought.
I would be most grateful for any help you can give me!!
Thanks,
April
OK, firstly.....flash hardspl.........instructions here
Next flash ANY radio......try version 1.48.00.10.
with the device booted up and synched with Activesync, download the radio ROM, unzip and run the RUUprogram (the only exe in the zip).
select autodetect, it should highlite SPL v2.10 and tick the "HardSPL?" box.
go through each screen and accept everything......the radio will be flashed.
Hopefully your device will work properly after this.
uh oh...
Thanks so much for your speedy response. Obviously I managed to screw this up.
got to this stage
"select autodetect, it should highlite SPL v2.10 and tick the "HardSPL?" box."
It didnt autodetect, so selected SPL v2.10 and ticked "HardSPL" box manually. Went through all the other bits and when it starts to do its thing it just sits at 0% then i get error message "ERROR 262: UPDATE ERROR. The rom update utility has encountered communication errors during the update process. THe program will guide you step by step to recover from the errors so you can continue with the update."
So I followed the recovery process instructions several times. Nothing has worked. Have tried restarting my computer and doing a hard reset on phone, and stuck with the bootloader screen reading IPL 1.04 and HERM300 SPL-2.10.01Olipro.
Manage to get back to this stage
"select autodetect, it should highlite SPL v2.10 and tick the "HardSPL?" box."
and go through the ticks but always ends up with error message 262.
SORRY!
Sorry to hear about your problems.
Was it the official T-Mobile WM6 ?
If so it was another 1.50 Radio!
I have same now!
http://forum.xda-developers.com/showthread.php?t=357275
I read in another thread try putting phone in fridge for 15mins first without the battery.
Good Luck
fridge vs. floor
Yes, it was the official WM6 from T-Mobile.
Im worried now that my limited experience with flashing, cooking, and now crying will leave me with a proper "brick".
I will try the fridge thing, if I ever get it to loads WM6 again but for the mean time, I will continue to throw it on the floor.
What do you mean by it was another 1.50 radio? I dont know what version I once had, but as suggested by mrvanx, I was trying to upload the 1.48.00.01.
Again apologies for my complete ignorance, but Im sure there are others that share my stupidity and will benefit from me asking goofy questions. If anyone else has any more simpleton advice on how to revive my poor phone, I would be much obliged!
Thanks,
April
The 1.50 radio bit; If it was the official T-Mobile WM6 upgrade, then your radio will have been 1.50 (I am pretty sure)
I dont know what else to do!!??
Ok since trying to update my radio from nothing to 1.48.00.01 and receiving error message 262 during the update, my phone now only goes into bootloader mode reading the following:
HERM300
IPL-1.04
SPL-2.10.0lipro
I have tried the following to bring it back to life (but not in any particular order):
- restarted my pc several times
- made sure my Windows XP SP2 was up to date
- made sure I had .net framework up to date
- hard reset on phone
- soft reset on phone
- leaving battery out overnight
- updating SPL to 2.10.0lipro (again) doesnt get to any percentage, just straight to error 260
- updating radio to 1.48.00.01 (again) - wont autodetect. tried radio button SPL2.10, then just force safe, then just HardSPL. each option dies at 0% then error message 262)
- reinstalling TMobile version WM6 (again) - dies at 11% - error message 262
I saw the post by pof "How to unbrick your bricked hermes" and the solution was to "Flash any radio in NBH format", but I cant figure out how to do that!? (I have tried clicking on the nbh file in the downloaded radio folder, but dont know what program to use to unload all the info. Have also looked at all the links on "Radio sudden death issue knowledge consolidation" and nothing has helped.
Sorry again guys, but can someone please help
If not, does anyone want to buy my brick?
alachlan said:
Sorry again guys, but can someone please help
If not, does anyone want to buy my brick?
Click to expand...
Click to collapse
Dude - there are enough bricks around these parts to build a 500 story repair centre! All we need is MS to merge their NT, CE and ME technologies into CEMENT then we can hold all the bricks together
Error 260 (comms error) is usually caused by using Vista without "fixing" it or Win2K/XP without the .net framework on it
Error 262 is USB port not available - turning hermes off and on (or removing the battery if that fails) at that point and putting it manually into bootloader usually cures that one then continuing with the flash.
Incorrect.
Its more than likely this Vario II was irepairably bricked before the TC bought it, the Radio upgrade is failing on a Tmobile official ROM (which includes a radio) and on a standard CustomRUU upgrade for the radio only.
A "checkimage" command in mtty would probabaly return a failed radio checksum and following on from that the mtty commands to get into the radio bootloader will fail (rtask a......then rversion).
Also there may be a corrupted CID on the device which again isnt good.
Ive seen these types of bricks MANY times.
Sorry dude, looks like your Hermes was a paperweight when you bought it.
Never thought of that - shameful given the amount of radio investigating I've done recently Too busy on 260's with part flashes from people not installing .net (also the amount of hits you should be getting to your vista guide now is scary!)
Still say we should collect up all the bricks and build a repair centre
Mikeapollo said:
.....the amount of hits you should be getting to your vista guide now is scary!....
Click to expand...
Click to collapse
73039 hits according to the site
Pretty much the only fatal brick now is a damaged radio/CID flash. If there was a way for Olipro/Pof/Us to flash a hardspl type package in place of the radio bootloader then it would be solid.
What type of mortar should we use?
mrvanx said:
73039 hits according to the site
Pretty much the only fatal brick now is a damaged radio/CID flash. If there was a way for Olipro/Pof/Us to flash a hardspl type package in place of the radio bootloader then it would be solid.
Click to expand...
Click to collapse
Yup.. Must admit I think that's the one thing that will not happen anytime soon as the interactions between bootloader, radio bootloader and the radio PLA/PIC is a tad complex... It'll be a very difficult thing to test and even finding a suitable vunerability is difficult - certainly beyond my abilities presently. Though the same was said 12 months ago about the No-Wifi issue and Olipro led some excellent progress in that area...
Mind you - the key to fixing CID/radio bricks is to educate the masses not to make them in the first place and not to just blindly execute whatever they stumble across - more of a challenge than rewriting the bootloader by hand on paper tape and almost as frustrating
Oh... as for Mortar... we could have a mass scrape of all that weird dirt stuff that "grows" under the "invisible-until-you-open-it" edges of the screens and around the battery cover and add a drop of water
Wonder if it's the electronic equivelent of belly button fluff?
does that mean its dead?
Thanks for all the entertaining posts guys. Just to clarify things, Im running XP SP2, and the phone did actually work for about 3 months until suddenly one day it gradually started dropping signal, until the signal vanished completely.
Are you guys trying to tell me that my phone is completely dead then? Could I have prevented this by knowing what the hell I was doing or was it a fault of the phone?
With regards to the mortar issue I think a combination of tears and sh*t would do. I think I would build a big wall around the jackasses who release products that arent completely stable but still charge us an arm and a leg for them. (excuse my grumpiness)
Oh and just wanted to say that since my vario has been out of action, I have been relying on the trustiest brick Ive ever owned, my XDA IIs. This thing has been dropped so many times and is held together with super glue, but it does the job and gets on with things, just not very quickly.
Thanks again for all the help.
alachlan said:
Thanks for all the entertaining posts guys. Just to clarify things, Im running XP SP2, and the phone did actually work for about 3 months until suddenly one day it gradually started dropping signal, until the signal vanished completely.
Are you guys trying to tell me that my phone is completely dead then? Could I have prevented this by knowing what the hell I was doing or was it a fault of the phone?
With regards to the mortar issue I think a combination of tears and sh*t would do. I think I would build a big wall around the jackasses who release products that arent completely stable but still charge us an arm and a leg for them. (excuse my grumpiness)
Oh and just wanted to say that since my vario has been out of action, I have been relying on the trustiest brick Ive ever owned, my XDA IIs. This thing has been dropped so many times and is held together with super glue, but it does the job and gets on with things, just not very quickly.
Thanks again for all the help.
Click to expand...
Click to collapse
By the sounds of it you might have a permenant brick but unless i had your device here and actually went through everything myself i cant be sure. take a read through the sticky thread above this one about unbricking......it will take some time to read through but you will see what techniques are used to try and revive the device.
when cid corruped with spl 2.03 and not have gsm no solution can not flash with sd card when you see that level=fff only when level=0 in mtty console can use sd card for flashing rom.
THIS TIME ONLY SOLUTION TO UNBRICK HERMES WITH SPL 2.03 NO CID AND IMEI -
SENT Imei-check to fix this ??
?
uuuummm....
Thanks mbsshop1302gsm for the response, but did I mention that I have limited knowledge on this stuff? So the more basic the instructions are, the better.
Thanks,
April
Ok, after 2 days of fighting, sweating, a pc hdd full with roms,tools,mtty,etc...
...i'm giving up. i am posting a help request for the first time since i am a xda user,
and that's been for almost 2 years now. i rather solve problems by doing research on the xda forums but this time i am out of energy.
i had an raphael before where the hacking process was pretty straightforward
and flashing a cooked rom was really idiotproof.
now i got an cool athena in my hands. i was like yeah, let's flash baby....and
the original OS didn't even last for half of a day. quick enough i realised that
this baby shouldn't be flashed the raphael way - the sd card method...
ok let's get on topic:
what i did:
flashed with the AP4 SPL 3.5 AthenaUpdater (following the howto exactly)
and well. that worked fine. the OS was booting and everything. but to my
surprise it looked like that AP4 update flash thing didn't ship another cooked
rom, but flashed my SPL only. i rather expected a SPL, CID unlock and ROM
install in one single package. i don't know what made me think that, since the
raphael has to be flashed with different stuff too before beeing able to...bla
since i was so happy to find that AP4 update howto i guess i was assuming
that this is the whole deal since it doesn't say anything about seperate CID
unlocking in that .pdf
anyway, i looked for a cooked spl 3.5 compatible rom and there i found it:
[ROM] *Updated Mar/4/2010* AGB V3.00.0 (WM6.5.5 build 23534)
and well, that was basically it. the flash went ok, but after booting only
the rom's splash screen appears and nothing further happens. hard reset
doesn't help.
i tried a few other roms after that, and again. only the rom-specific custom
flash image appears and nothing happens.
tried to flash the AP3 for SPL 3.5 ROM - same thing: flash screen says "operating system is loading", which is an bitmap picture i guess...
downgrade to SPL 1.2 doesn't seem possible since this requires a running
WM, which i don't have.
bootloader works by the way, hard reset works too, but no fix...
after a little reading i get the idea that i should have cid unlocked the device
before flashing with a cooked rom? or did i something else wrong?
any help would be appreciated
oh yeah, and mtty:
the recover from invalid id procedure doesn't fix the issue.
and:
set 14 0
task 8
doesn't fix anything too, just boots the device into the never ending flash screen....
quick questions
what does your boot screen say
and did you remove your sd and simcard before flashing
yeah, the i ofcourse removed the sd card and sim card before everything.
i am at work now but afaik my bootloader screen says:
ATHE100
IPL 2.02
SPL 3.50.Olipro
before the attempt with mtty it said
ATHE400
IPL 2.02
SPL 3.50.Olipro
something like that. is that helpful?
i'm wondering that almost nobody replies. is the athena projcet kinda dead
or am i just asking BS, i don't know. anyway, i'll keep this one posted.
i have a new status of my athena: it boots a ROM for the first time. i have flashed
it with a test rom, called:
Windows Mobile 6.1 Base ROM (Testing)
It can be found on the athena latest ROM links page.
And ofcourse there is a BUT(T)....
BUT..the configuration wizard keeps looping. Means the device boots WM6.1,
asks me to calibrate the screen. after that touchflo (or sense) shows up for a few seconds, a progress bar appears and installs some (invisible) stuff and the device reboots. Normal behaviour you'd say, but the calibration screen comes again, and the progress bar too, and reboots, and again, and again...
maybe somebody could tell me how to stop that process? it seems like the
device doesn't save the first time setup settings. how to fix it?
ultrasonyk said:
i'm wondering that almost nobody replies. is the athena projcet kinda dead
or am i just asking BS, i don't know. anyway, i'll keep this one posted.
i have a new status of my athena: it boots a ROM for the first time. i have flashed
it with a test rom, called:
Windows Mobile 6.1 Base ROM (Testing)
It can be found on the athena latest ROM links page.
And ofcourse there is a BUT(T)....
BUT..the configuration wizard keeps looping. Means the device boots WM6.1,
asks me to calibrate the screen. after that touchflo (or sense) shows up for a few seconds, a progress bar appears and installs some (invisible) stuff and the device reboots. Normal behaviour you'd say, but the calibration screen comes again, and the progress bar too, and reboots, and again, and again...
maybe somebody could tell me how to stop that process? it seems like the
device doesn't save the first time setup settings. how to fix it?
Click to expand...
Click to collapse
Hi mate
I live in a different time zone and my daily email about updates to posts comes late in my day and probably when you sleep.
There are not many people who use this device and it is really a legacy machine.
However your post gives a clue to what happened.
with the bootscreen showing athe400 initially are you sure you have an x7500/x7501 or is it the x7510?
Just make sure before you follow the solution in this thread
http://forum.xda-developers.com/showthread.php?t=387596&highlight=endless+loop
the roms are very different
Check out exactly which hardware you have
this thread is from the x7510 thread and may be worth a read if you have the x7510
Additionally cmonex has the knowlege to fix your issuues if the above doesn,t work
http://forum.xda-developers.com/showthread.php?t=441684
thank god, somebody replied with useful information
well, i must be honest i didn't pay too much attention on the model number.
after reading your post, i checked and i see that i have a X7510 advantage device.
which means as far as i can understand it:
i SHOULD have the modelid ATHE400?
which means, i messed it up by flashing it with mtty to modelID ATHE100?
which means, all the time i was installing X7500 stuff on the wrong device
and bricked it that way?
so the AP4 3.5 SPL solution is not for X7510?
which means, the AP4 3.5 SPL is a hard SPL but for another device?
and after all, what do you suggest? do i need to revert my modelID
to ATHE400 and if yes, how? and after that i should follow the 2nd
thread to install a proper hardSPL and a WM6.5 ROM of my choice?
try contacting cmonex
the author of this thread
http://forum.xda-developers.com/showthread.php?t=441684
wrote the script you used to change the device id and may have a way to reverse this
good luck
lakeman, my friend!
you pointed me to the right direction. i followed the steps for installing
hardspl for x7510 from cmonex, and yeah, the modelid changed back
to athe400 and the device was booting! seems like that hardspl also
corrects the modelid automatically.
i am still curious why the device was working after flashing with AP4 3.5 SPL
in first place, since that one is actually for X7500 devices.
i should 've read some more before going to flash that thing, i must admit.
many thanks to you lakeman, and big ups for that cmonex guy!
now it's time to look for a nice wm6.5 rom for my ATHE400
fantastic
happy to help