Stuck in bootloader v1.06 - MDA II, XDA II, 2060 ROM Development

I have only had my XdaII for a month, but last week it locked up and upon a soft reset it took 5 minutes to get past the O2 screen, then there was no responce to any screen taps, i decided to do a full reset, once rebooted still no response to screen taps, so i couldnt calibrate the screen or go any further, i connected the xda to activesync this still worked fine and was responding normally. I then decided to reload the rom from myxda.com, biggest mistake as it crashed halfway through now it just says Serial v1.06 or USB v1.06 if its in the cradle, now before i get bashed for just asking this question the same as a lot of other people have, i have spent the last 4 days go over this site trying anything that relates to getting any image back onto my xda, nothing has worked i have tried any nbf or nb1 image i can find on here with orginal or modified himaupgradeut.exe same response every time error 100: incorrect device type, i have tried any image i get can get onto an SD card, they either dont boot or wont allow upload, so my question is i have seen several people on here ask about bring v1.06 back from the dead but so far noone has had any instructions on how to this when a normal boot isnt possible.

I don't know if this is any help,but I had something similar.
I concluded that the rom on xda2 was newer than one being upgraded? with,so it says it won't work.I sent mine back to o2,but think that rom 172 or something, might be accepted.People say that you leave it 30 mins before it starts to upgrade.

There is a problem with bootloader v1.06 in that it will not allow 'downgrades'. It seems to have appeared on devices around the same time that ROM versions 1.72 appeared. I have read that it will allow installation of version 1.66 but nothing less than that (and that may apply only to T-Mobile). However, you should be able to install a version 1.72 ROM without to much problem.

My help
You can make the unit work again by downloading the rom version:
1. Ensure that the main battery has enough charge to make the unit in bootloading mode.
2. Execute the bootloading mode and connect the unit to the docking station(cradle), you will see the "Serial" in the upper portion of the screen will switch to "USB" this is an indication that there's a connection established between the pocket pc and your pc.
3. Then download the latest Rom version(1.72 is a better choice).

Thanks dcs and Juni
The 1.72 rom did get it going again .... but i still have no response on the screen so im guessing ill have to return it.
Does anyone know where i can get the 1.66WWE rom from as im assuming returning it with 1.72 rom on it may be frowned upon, and a voided warrany.
Thanks agian guys for your help

Does anyone know where i can get the 1.66WWE rom from as im assuming returning it with 1.72 rom on it may be frowned upon, and a voided warrany.[/quote]
talk to this person in here: :lol:
http://forum.xda-developers.com/viewtopic.php?t=12044

Related

Touch Screen

My touch screen suddenly stopped working, anyone had this happen to them? As far as I know I didn't do anything to provoke this i.e drop it or make any software changes. I tried a hard reset and still no luck.. If anyone has any suggestions please let me know.
Thanks
Seeps
if it ujust stopped working and you have done a hard rest (formated teh device and reinstalled ) and its still the same then id say most likely faulty(which you probley already guessd)
if you got it as an account upgrade get in touch with ur network service provider and get them to replace the device if you bought it from a 3rd party try to return it if you can, if you are unable get in touch with HTC all the best
nass
Thanks
Yea I tried hard reset and all that, you're right my guess was that its faulty. So I'll be paying cingular a visit tomorrow. I just finished flashing the cingular splash screens back to the device and original os back to the device with the mtty program, luckily I figured all that out because otherwise I couldn't get past the sceen alignment stage to do a regular rom update.
Seeps
The best way to clear any "funny" status on the hardware is to give it a "Russian Reset": power off the phone and then on again. If that doesn't solve your problem then take it in for repairing.
(Russian Reset is a term I heard many moons ago from a Finnish DEC SW engineer regarding PC hangs that would not clear with Ctrl+Alt+Delete but could only be solved by switching off and on.)
Through the turnstyle
Well since my 8525 is 1 month and two weeks I have to send it into cingular's warranty department. The one thing I am concerned about is that I want to make it appear that it had never been modified again. Unfortunately I am not able to do a regular rom update because I can't get the thing past the setup stage because it requires me to tap the screen and do the screen alignment to continue, and thus it won't let me make an active sync connection to do the rom update. I was able to use mtty to get the OS, EXT ROM and splash screens back to original, and I was able to get it back to bootloader 1.04 (Is this the stock bootloader for the 8525?), but I haven't figured out how to downgrade the radio yet. Any suggestions? I think I have radio version 1.27 right now, if anyone knows what the stock radio version is for the 8525 let me know. I want to get this thing back to normal so when I send it in through warranty they don't tell me I am out of luck..
Thanks
Seeps
Put device in bootloader mode and flash the stock rom (cingular 1.34). You don't need activesync at all.
Thanks
That worked. Now I can rest a little easier sending it back.
Trying to downgrade with mtty
when i run mtty i cant see a usb option how do I get it to see one??? the mtty ver i have 1.6 but i reaaly need a hand cause i have the same issue with the dead screen

trouble in paradise... why can't i flash roms?

first off let me start off by saying, yes, i'm a noob. i started out by reading all the posts in every thread i could. i have a x10ht that i bought at the local asian mall, not knowing that there were so many problems unlocking it
this is the second failed attempt at flashing a new rom onto my phone. i must say, i am not impressed. it froze the last time, i'm not sure where, and this time at 47%. kinda annoying when u think about it. i took the precautions and followed instructions, but to no avail
can anyone help? i'll give all the details i can...
bl 1.09
radio 1.14
old rom was 1.35
What state is it in now?
if i plug it in to the pc, it goes into bl 1.09
so, i was able to flash the old softbank rom onto it, but now i'm stuck with a japanese device with a sim lock on it(i think). i can't even set up activesync to try to update again. any ideas guys?
I don't have much xp with the ideosyncracies of the Softbank X01ht, but you should be able to build a sspl RUU featuring the os.nb of your choice. I believe you don't want to try flashing the radio ROM area but an os.nb only flash should restore the english version of your choice.
I'd look for confirmation on the above conjecture however, before trying these steps:
download the ruu of your choice and extract the signed nbh file using winrar or equivalent (the exe is an executable rar file)
use nbhextract or nbhdump to extract all the files
use Olipro's RUU builder to create a sspl RUU with only os.nb (use the 06_os.nb extracted from step 2)
flash this onto your device
This procedure should raise a lot of questions for you to research the answers to. The answers are all here I assure you. In researching, you will learn about the techniques of custom flashing for Hermes and whether they can really be used safely on your device.
Flashing the japanese ROM shouldn't have SIM locked you again. However, if it is you can research your free solution on this thread or you can purchase unlock from here.
Also: please explain what you mean by "Can't set up Activesync"
the only problem is right now i can't even access my device... there appears to be some sort of lock on it, something to do with usim and i have no clue what it says. but i can't do anything with it
Its probably saying the SIM is incorrect. You may well be SIMLocked....
You need to get it to the today screen to do sspl flashing. Try resetting with no SIM installed. the first thing you should see after the WM splash is the phone dialer saying "The SIM is missing" in japanese. Hit the cancel button which on my TyTN is the first labeled button above the green button to return to the today screen (you may have to experiment to find the right button).
i do get that, but after a few seconds, it goes to a screen where you can put in a code and there is writing on the left soft button, but you can't select it, i assume until a suitable length code is input, and it has no ok button, so i can't even get out of it... help!!!
and by can't set up activesync i mean that i can only get into the today screen for a very limited time, and activesync doesn't seem to connect fast enough, so i'm kind of stuck.
This happens when there's no SIM installed?
yes, it does. but i may have found out something. i can connect to my hermes through activesync on my work computer... hmmm... let me see here...
wow, that was an experience
so i think i'm good, i'll update you guys as teh day goes on, but i may have fixed this myself, and i feel so releived.
yes, the same usim message was coming up regardless of the way i started it up, but i had about 20 seconds of pda usage before it would come up. i got activesync working via the work laptop on the usim screen, and was able to copy sspl over, i restarted and quickly ran sspl, which got me into des's bootloader. from there, it was just a matter of running the ruu i wanted to run in the first place, WM6 .2, and voila, we seem to be back in business... but i don't ever want to do that again, so i think i'm going to flash that hard sspl... but first to test the radio's and and other features.... wow. last time the flash ****ed up on me, i had to pay this guy $30 to fix it, and tho he did, he never wanted me to know how so i could do it myself next time. screw him!!!!
thanks to everyone and their hard work on the forums here. without you, i'd be styling with a razr rather than hacking this thing apart like it was an xbox or psp....

stuck in boot loader updating to 1.43 on black shadow

I was trying to upgrade to radio v1.43 in the hope that battery life was improved over 1.41 however when it got to 8% it stopped and gave me an error i can't remember After atempting to recover, it got off the three colour screen now the 3100 stalls on the blackshadow version4 screen (bootloader screen?) and goes no further. I tried reflashing but got a 260 and using mtty, only getting 2 com port options, didn't offer any help.
I'm really sorry to have not been able to sort this with reading through the relevant post but I haven't found a solution. What else can I try?
Hi,
Could you pls advise what is your device made, model, SPL version ... etc.
Also did you try to do Hard reset?
I'm using now black MAJIK (and few days ago black shadow) with radio 1.43 with no problem.
its the SPV m3100 When I decided to go Black shadow I read up on mr vanx and made sure I had all the things I needed. If I remember right, when I came to upgrade to Majik the auto detect found the second option down
SPL-1.04/1.10 - 1.09 Bootloader. I've realized since I had a spaz and ran the RUU from the archive this time. From what I've since read thats not too cleaver.
I have tried a hard reset and took the battery out instead of pressing space.
I dont know if this information on the starter screen is of use
M 05
S 04
B 05 D 3lak
I'm not sure, but hard reset doesnt mean you take the batery out.
Please check that link:
http://wiki.xda-developers.com/index.php?pagename=Hermes_For_Beginners#hardreset
I was in your position (hanged on booting) few days ago, and when i did hard reset, it changes every thing to basic normal condition.
i meant when i did a hard reset when it asked me to press space to reboot I took the battery out. I tried again this time pressing space to reboot but I still get stuck on the loading screen. I can't connect by USB to the PC I'm guessing the drivers on the phone haven't loaded and I'm stuck as to what to do.
Does anyone have any ideas?
try look at it http://forum.xda-developers.com/showthread.php?t=286755
ok I've tried everything I can think of to connect the 3100 to the computer so I can reflash it but mtty gives only com 1 and com2 but no USB and neither those two work, active sync wont connect so I disabled it as suggested and running the radio ruu and wrapper wont querry the device. I am now at a loss as to what to do next someone must know what I should do. Please?
what is your SPL?
try this http://wiki.xda-developers.com/index.php?pagename=HTC_Hermes
sl is 1.09 i'd updated it on the previously successful black shadow flash
msn [email protected]
icq 150277111
AIM TazmanFH9
Yahoo bigfathairyboggart
I have tried changing KITL trasport but I am unable to select or chose either option. I have also tried the rversion command in the tri colour screen but nothing happens. I hope I'm missing something nice and simple but I get the feeling I'm not going to be that lucky. Please help
tcSPVm3100 said:
sl is 1.09 i'd updated it on the previously successful black shadow flash
Click to expand...
Click to collapse
I suggest you check again, press and hold the side OK button and the power button...then put the stylus into the hole in the bottom of the unit.
yeah I've done that it's "SPL-1.09"
I had this exact problem yesterday, with the same bootloader too. The phone would not pass the splash and IT refused to upgrade. I ended up downgrading to a shipped wm5 rom (in my case the cingular 1.30.502.1_1.11.00.00) which to my surprise actually worked as no rom radio or spl upgrade moved at al on my phone. Then upgraded back to black majik. I hope this helps.
Thanks. I downloaded the trial of wm5 from the windows website and it asked me to install .NET framework version 1 so I got that but it turns out to be 2.0 not 1.1 It would say it had repaired but it would say this with or without the phone connected.
tcSPVm3100 said:
Thanks. I downloaded the trial of wm5 from the windows website and it asked me to install .NET framework version 1 so I got that but it turns out to be 2.0 not 1.1 It would say it had repaired but it would say this with or without the phone connected.
Click to expand...
Click to collapse
Just download a WM5 ROM from the wiki page!
ok tried this too no luck.
Trying to use the one from orange (linked to through wikki) I get an 294 invalid vendor error however active sync cannot connect yet of course so is this to be expected?
I have however gotten a connection with mtty which is a step forward dunno what to do with it yet though except trying the password 0000000000000000 command but it not disabling the password. This then lead me to read for a further hour how to change it and I've got to be honest; it beat me. I have No idea what the hell its talking about. My head hurt with so much reading.
I get a no gsm pop up v briefly on loader. I so want my phone back
I have since tried CID unlocker just so i get something installed onto this brick but I either get a connection error or it telling me it can't install for some other reason. I can not set the password in mtty to 0000000000000000 so how do I do that and is this the first step to getting things sorted? "just running a rom install" is not happening I can get a USB connection in mtty and that is it. Is the fact i'm running SPL 1.09 a problem? I'm getting precious little help guys If i'm posting in the wrong place or something please let me know. I need thing thing back now. Hours are drifting by with me trying to get some head knowledge but I still need some guidance please
tcSPVm3100 said:
I have since tried CID unlocker just so i get something installed onto this brick but I either get a connection error or it telling me it can't install for some other reason. I can not set the password in mtty to 0000000000000000 so how do I do that and is this the first step to getting things sorted? "just running a rom install" is not happening I can get a USB connection in mtty and that is it. Is the fact i'm running SPL 1.09 a problem? I'm getting precious little help guys If i'm posting in the wrong place or something please let me know. I need thing thing back now. Hours are drifting by with me trying to get some head knowledge but I still need some guidance please
Click to expand...
Click to collapse
can u flashing HARD V7?,i think better u have IPL 1.04 SPL 2.10olipro first ,then try to flashing radio?
and did u try SD card.
In bootloader can anyone here connect with active sync? I can't so updating rom and radio flashes in the usual way isn't possible. Trying the hard spl again it tells me to make sure active sync is connected and as it isn't it throws back a 262 update error. 0% on the hermes and that's currently as far as I can get. I have no means with which to access the memory card.
The reason you get an invalid vendor ID is because your CID doesnt match....download a ROM which is for your device (an orange one?)...then try.
You need to read the wiki alot more before trying anything else since you are not aware of the vendor ID error...nor the fact you MUST use HardSPL.
I linked to the orange ROM from wikki and tried installing it. it was while installing THIS ROM SPV_M3100_ROMUpdate_0407.exe I got invalid vendor error.
Installing a recent DL on HARD spl v7 I get a 240 open file error that's one I haven't had before.
With all other attempts they all say they want an active sync connection.
I can not connect to the phone through active sync
so all attempts by me to flash anything to the phone using an RUU fails.

Vario II needs radio upgrade

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

Upgrading my Jasjam HREM100 Failed with Error [262]

Dear Members,
I tried to upgrade my JasJam with "838Pro_HK_ENG_WM6_Upgrade_20070712"
Which worked with other JasJams (Many of my friends has it working).
On upgrading, it stucked on 11% saying Error [262]
I went through recovery, and it said remove the USB cable, remove the Battry, Return it, start the phone, connect the USB, and its recovered.
After that Its again stucked in 100% and the same senario is happening.
Please tell me is there any possibility to restore my phone working.
Its stuck now, and only the (Three color screen) is on the screen.
Hard reset, soft reset is not functioning, and the phone refused to show anything except the three color screen.
I searched the forum, but found no relative article, I am searching since two days your forum and I know that no other forums can help me in this as I was always getting my help from yours.
Thanks for your time.
HERM100
IPL-1.04
HERM100
SPL-1. 40. 0lopro
If you're using XP then untick "Allow USB Connection" in activesync.
Reset to bootloader on your Hermes, Hold power, OK button above flywheel and reset with stylus.You will get the same screen you have now but it won't be a f*&%ed up version of bootloader. Connect to PC by USB and Install Hard SPL V7, found here - http://forum.xda-developers.com/showthread.php?t=296722
After this, use the sd card method to install the ROM.
1. Format a 2Gb or less sd card FAT32. ?CFopy the .nbh file of the rom you want to it and rename to hermimg.nbh .
2. Insert into phone and reset to bootloader.
3 If you did everything right then follow the prompts...
Cheers...
Again problem!
Dear ultramag69,
Thank you for your fast reply.
I did (untick) that option in the ActiveSync.
And also did reset to the device by holding the Power + Ok (under the flywheel) with Stylus reset.
After that I downloaded "Hard SPL V7" and tried to update.
First of all, in the "Hard SPL V7" there was only the last option active, and there was down a checkbox also active, but when choosing the last option, checkbox bocomes like everything else disabled.
However, I got the erro 286
I felt like the Device disconnected from USB and reconnected again (Windows gave me the sound when you remove some USB device and you re-connect it again) :-|
I don't know what to do with this dead device now !
Thank you very very much for your time and help
Don't quote me on this as I suspect you need Hard SPL V7 but, as yo've tried things out and you're about to quit anyway, Try using the sd card to update the Stock rom, the rom that came on your Hermes, or updated version. It might let you do it if the CID matches.
I don't believe SPL 1.40 allowed you to flash ANY rom but it may let you re-install the stock rom BUT it must be the original carrier software it came with. If you had Telstra rom on it when you got it, it must be a telstra rom you flash. Make sure its for the right country too as some carriers are all over the world.
Cheers...
Hello ultramag69,
Thanks alot for your reply.
Having my i-mate dead, is really interesting.
I am trying to recover it up, Mine came with (HTC) logo when booting, and I did flushed it with Dopod.
But recently, the network stopped, and I asked some experts, they said it need new OS (They ment to re-flush the ROM).
I tried with the same Dopod that was successful before, and its now stucked on 11%.
I even downloaded the Telstra but the same, it stucked on 13%.
This is my entire story, and still I am trying to get it up.
Thanks alot for your helping. nice of you.
And for all who read my post, if they had such experience before, please help.
Hello ultramag69,
Thanks alot for your reply.
Having my i-mate dead, is really interesting.
I am trying to recover it up, Mine came with (HTC) logo when booting, and I did flushed it with Dopod.
But recently, the network stopped, and I asked some experts, they said it need new OS (They ment to re-flush the ROM).
I tried with the same Dopod that was successful before, and its now stucked on 11%.
I even downloaded the Telstra but the same, it stucked on 13%.
This is my entire story, and still I am trying to get it up.
Thanks alot for your helping. nice of you.
And for all who read my post, if they had such experience before, please help.
If you can, try to find the original SHIPPED STOCK ROM. It may be your Hermes won't be recoverable as the flash stopped in the radio rom part. Most people use a cooked rom as this has the radio rom part out.
I personally use the sd card method to flash my roms so there are no sync errors or accidents with my PC. But you need Hard SPL V7 installed to get that to work with any but the shipped rom.
DON'T try flashing anything but the shipped rom or you will loose all chances of recovering your Hermes.
The only other suggestion would be to flash the SHIPPED RADIO ROM, but you need to know what radio it was before you flashed it with the dopod rom.
Unfortunately the radio rom is the Achilles heel of our phone series. Any problems during flashing of that means we pretty much end up with a brick 99% of the time. Most people are stuck and the rest seem to have limited success reflashing the radio. AVERY small percentage get it working with no trouble, but its a REALLY small amount of people.
Good luck, Make sure you flash with the SHIPPED STOCK ROM to improve your chances of success.
Cheers...
Ultramag69, Thanks alot for your consideration.
Flusching using SD card didn't success with SPL V7.
I formatted my MicroSD card, 2GB with Fat32 FS.
After that I copied the file that came with the zip archive (RUU_signed.nbh) and renamed as required: (herming.nbh).
And I put it in my i-mate, and holded the (Power + OK under flyweel) then restarted using the stylus, It showed me the tri-color screen, then it shows (Loading...) with Gray background screen (Which is normally the flusching screen) but it returned to the tri-color screen.
Any suggestions to get this SPL V7 installed successfully ?
I tried with all my (.nbh) files that I have downloaded from all sources, but its the same screen.
I think something is really wrong with me i-mate, should I take it to some Hard-ware service center ? and what can be damaged and need to be replaced in such cases ?
I am very excited in getting it working again.
Thanks alot.
Cheers...
I had bricked my Hermes a couple o' times, because of a rom I cooked half-way ( LOL ). Each time I had to flash back to the stock rom as suggested. Don't lose hope, cuz there's some people who will tell you just to accept it as bricked. You could also take the sucker apart and use jtags to flash. Most types of bricks can be solved when it comes to the Hermes. There's a thread somewhere that polled the different types of bricks, and except for radio bricks, most can be solved. If you unbrick it try 6.5 .... !!! My rom is cooked all the way now
Arwany, did you run the SSPL.exe file in the sd card instructions for Hard SPL found on page 116, post 1160 of the Hard SPL thread? You need a version of Soft SPL (SSPL) to flash using the sd card as the CID must be bypassed. The reason we Hard SPL our Hermes is because its safer. Its worthwhile flashing the SPL using unsafe SSPL (even if you use the pc you have Soft SPL installed) as its a short flash, flashing a rom (especially stock roms with the radio rom inside) is a riskier and longer flash.
Cheers...
I had the same problem.. All you have to do is establish a connection with Actisync, then run the Updater. There will be 3 colors on your Screen, sont worry, just wait 10-15 min and your should be done with the setup.
Want to help
Arwany said:
Ultramag69, Thanks alot for your consideration.
Flusching using SD card........ with the zip archive (RUU_signed.nbh) and renamed as required: (herming.nbh).
And I put it in my i-mate..........
Click to expand...
Click to collapse
Hi,Just to tell You that I've noticed a little spelling mistake.You've written "herming.nbh" But it should be "Hermimg.nbh".
Not the 1st person to make that mistake, and probably won't be the last.....
Hi All,
Yeah, that worked out for me, I could successfully flush my JasJam with that.
Thanks for your reply.
I am still facing problem when trying to flush with other OS, its always stuck on the GSM line.
I am using the SD flush method.
Any suggestions ?
THank s alot for your help!
If you have the no GSM problem the only way to, maybe, fix is to flash the original SHIPPED STOCK ROM, or the original radio rom. Flashing anything else may result in a permanent brick...
If it doesn't succeed then, sorry, its not repairable. Can be used as a PDA but not as a phone ever again.
Cheers...
Thansks Ultramag69, for all the helps, It solved my main problem.
You also Ekonkar, your comments was so helpful.
I will try to do some hardware repairing in some Mobile shop, they may get it up again !
To fix it will cost more than to get a new device... They'll tell you they can't fix it or it needs a new mainboard. Will still cost you for this nugget of info. My advice, buy a Hermes off ebay, either working or not. If its not, make sure its screen related problem cos you have the parts to fix... Unless your screen has gone bung too...
Cheers...
I gave it to the repairing guy, he replaced the GSM item and its up and running now for only 20$.
Prost :-D
Sweet, You should post where and what country so others in the same situation might be able to get their Hermes up & running.

Categories

Resources