Related
Hello,
I recently acquired an i-mate and before doing anything, decided to perform a ROM upgrade. It started with ROM version 1.66.00WWE and Radio version 1.10.00. I followed all the instructions on the clubimate website. The ROM upgrade (Step 1) went well, until I started the English Language customization (step 2). That program froze on my computer and left the i-mate in bootloader mode, even before starting the Extended ROM upgrade for the customizations. When trying to upgrade the main 1.72 ROM again, it gets stuck at the Radio Stack Upgrade (to version 1.14) at 14%, then either exits with no message (Win XP), or gives a Radio Stack Upgrade error message (Win 98 ME). The phone meanwhile says that it is perfuming the radio stack upgrade and to please wait. Waiting for an hour yielded no change. The following is the log file entries of the part for the Radio Stack upgrade:
03:06:42 Connection with USB
03:07:52 Begin Stage 4
03:08:22 Radio Erase retry 1
03:08:59 Radio Erase retry 2
03:09:15 Stage 4 Complete
03:09:15 Begin Stage 5
03:09:15 Write block1
03:09:26 Write block2
03:09:32 Write block3
03:10:08 Radio Update data retry 1
03:10:16 Write block4
03:10:24 Write block5
03:10:32 Write block6
03:10:40 Write block7
03:10:49 Write block8
03:11:25 Radio Update data retry 2
03:12:01 Radio Update data retry 3
I tried many times, but get the same result. I followed all advice on this forum and searched all over for solutions, from getting the device into bootloader mode (power button + action button + reset), making sure that my PC does not have any other USB device connected, that the only programs running are the upgrade utility and ActiveSync 3.7.1, etc.
I also notice it takes approx 1 hour from start of upgrade until the Radio Stack Upgrade, instead of the advertised 30 minutes. Someone mentioned that this Radio Stack Upgrade problem may be caused by a security feature on the Radio Stack ROM preventing the installation of older versions. However, I am installing the newest (ver 1.14), so this should not be a problem. With a hunch, I decided to try the English Language Customization (1.72.800) upgrade again, and the extended ROM upgrade worked, but still no Radio Stack. So now I ave everything upgraded, but a blank Radio Stack.
Now when performing a hard reset, I get the blue screen with "i-mate" written on it. In the bottom right only the version of the ROM "D 1.72.00 WWE" is shown, but it says "No GSM" right above it. It takes approx. 15 minutes to boot (with blue Bluetooth LED flashing), then goes through the screen alignment and intro procedure. After that, it installs customization and boots again. It takes another 15 minutes to boot and the phone functions only as a PDA. Even a soft reset takes 15 minutes (with Bluetooth LED flashing). I tried upgrading again after that, but no use. Going to "Device Information", I see the versions of ROM and Extended ROM, but the Radio and Protocol are blank.
I tried phased upgrading, where I would include the main ROM upgrade file into to the directory where the archive was extracted, then extended ROM, then radio stack. Everytime the radio stack upgrade failed (i.e. stuck at 14%), I would try to upgrade that part only, since all others upgraded successfully.
I am really out of options. Any help would be highly appreciated.
Thanks!
I asked Carrier Devices (clubimate) about this step 2 because on the official download page all I saw was the step 1, no step 2 and no link to download.
The answer I got was there is no english customization 800, only a beta. The customization or step2 would be presented for arabic or telstar etc based on your IMEI # not for english it is contained in the first .exe
So you MUST have got this 800 customization and maybe the main upgrade from on here because it was never on the offical download page. Only the BETA from the FTP which some hacked into on clubimate and posted on here.
Go to the official download page on clubimate (register if you havn't) and dowload the official .exe upgrade (one file) and see if it will run. Don't get it from here.
RUU172126WWE_imate.exe
Hard reset a couple times and that should be it. The upgrade does take a LONG time to do.
If that does not work, you might have to do a warranty repair, I would use the online chat support on clubimate, just watch for when they are online and ask. I don't think you can just flash the radio portion.
I find 1.72 VERY stable and fast. Good luck!
Hmm.. All files were downloaded from the official clubimate website (I had to register in order to download). Talking to customer support, they were aware of the Step 2 customization file on their site (they recommended it, too). I doubt I downloaded hacked ones.
Still a loss on what to do, other than take it to a service center, that is (anybody do that? was it expensive? took too long?).
I tried a suggestion where I extracted the Radio Stack ROM upgrade file from version 1.66 and installing it separately. Still stops at 14%. I also tried a full reflash back to 1.66, but also same result. Took it to an i-mate service center nearby, was surprised that they didn't even know how to put the i-mate into bootloader mode (I had to show them)! All they could do was try reflashing using the same utilities we use (still no luck). They said that anything more elaborate would require sending it to Dubai. So much for "service" center. So, no luck there, either.
Also tried to reflash to the orginal 1.00 ROM with 1.05 Radio: The upgrade utilitiy that came with that version won't go past the small "please wait...." screen. Just sits there.
Really sad. I didn't even use this phone (figured that the best start is to perform a ROM upgrade). I'm not that impressed with how fragile ROM upgrading is (and I am careful with using only official releases). I thought after the Wallaby, things would be more robust. Maybe I shold dump this thing and get an HP h6300 series.
Note that I managed to successfully upgrade to 1.72 at least once. It was only when trying the 1.72.800 customization did things start to go south.
Also, does it matter whether the SIM card is in the phone or not while upgrading? Instructions are not clear, although they did mention that the phone will behave as if it is out of area.
Another question (desperate and a long shot, maybe stupid), Do SIM cards from say T-Mobile have an effect on i-mate phone Radio Stack ROM (i.e. lock it, etc.?)
ANY help would be appreciated!
i-mate and bootloader
I just got to see the problem as I am going through the same search for answer. How to get to the stage of bootloader? Somehow I feel that the device has crashed: While I was trying to install the upgrade RUU172126WWE_imate, my laptop, and for some odd reason, shut itself down, then auto restarted. The i-mate from that point on did not respond and in fact all lights on the device went blackout. I tried soft and hard resets but to no avail. I even removed the battery for several hours and when I re-installed it, all what it gave me was the word i-mate (but no backlight). Any advise on how I can get the device functional again.
Thank you.
Put your device in bootloader (press the Jog button and the Power button at same time and press the reset switch). Place it in the cradle and re-run the upgrade. That should work OK.
Jog
Thanks for the quick reply.
Power and reset button I know, but I am not familiar with the Jog button on the i-mate (Pocket PC PE). Appreicate your help.
Its the multi-directional button in the middle at the bottom. Press it straight down.
for others pls make a POLL if your button is working or not in WM2005
http://forum.xda-developers.com/viewtopic.php?t=22737
Been a while since the POLL Shows that there are more people who has experiencing the non-working rec and cam button in Magneto than those has a working button. Up to this moment there are no single explanation why this is happening ..
But it is not the number that are very intriguing in the POLL but its BOOTLOADER version, because we can easily distinguish does people who have a working button than those has not working button
:arrow: If you have a BOOTLOADER 1.01, 1.02 or 1.03
Most Likely ALL your Button will work .. if it doesnt work .. just a little adjustment then it gonna work
:arrow: AND if you have a BOOTLOADER 1.04 and 1.05
The Record button will only work if it is turn off(press power off once) and the buttonlock is off but it will not work if the device is ON or Total OFF (press power off twice)
and Camera button is not working in any type of situation (ON, Suspend(press power off once), total OFF(press power off twice))
:arrow: BUT if you have 1.06 the results are mixed
if you are sure that your original Booloader Installed is 1.06, then same as those who have 1.04 and 1.05 your camera and record will not work if the device is ON
but some have a working button and has Bootloader 1.06 ..
im not saying that a ROM upgrade can upgrade the BOOTLOADER since it needs the bootloader to be Unlock or to be Unprotect before it changes the Bootloader which mostly of the Device Bootloader is Lock and Protected and im not sure if there is a ROM upgrade (.nbf) that can unprotect our Bootloader to Upgrade it although we had already a case in the past thread that bootloader is change due to rom upgrade..
http://forum.xda-developers.com/viewtopic.php?p=54696#54696
Heres My list of ROM version that contains Bootloader 1.06
1.66.00 WWE
1.66.00 ITA
1.66.00 WWE
1.66FRA
1.66.01 GER
1.72.00 WWE
1.72.01 GER
1.75.00 WWE
2.02.t1 WWE
2.20.07 CHS - both Translated and not
PS. I cant find yet a ROM Upgrade(.nbf) than contain 1.04 and 1.05 bootloader but some 1.60 ROM (NOT ALL) contains 1.03 Bootloader.
also 2.06.00WWE doesnt contain a bootloader (or bootloader is blank/empty)
Now we first extract and compare the bootloader of those who have working button and uses 1.06 with those is nonworking button and uses 1.06 bootloader
User with working Button and Bootloader 1.06
buzz_lightyear
anybody
User with non-working Button and Bootloader 1.06
toenailed
xda2jojo
gotan
Suprising we FOUND no SINGLE DIFFERENCES AT ALL .. so it means that it is not the BOOTLOADER ..
BUT WE CANNOT CONFIRMED if no one will try to Downgrade there bootloader for those non-working and upgrade there bootloader for working button. And Downgrading and Upgrading the Bootloader is surely a very Dangerous thing that you will do to your device .. i once explain it in this post
http://forum.xda-developers.com/viewtopic.php?p=124909#124909
But Someone has to do it to end this Bootloader version Theory of non-working button .. and since im the KING of STUPIDITY .. i will do THis SimPLE STUpid ExpERIMENTATion to know if the Bootloader
is the MAIN Cause for a non-working Camera and Record BUTTON of SOME WM2005/WM5.0 user, including me ..
[frutybabes.jpg left]DAY 1 -- DOWNGRADING MY BOOTLOADER FROM
My Original Bootloader Installed
Bootloader 1.06 1.34b
Built Time: 14:32:09
Built Date: Feb 18 2004
and My Rec and Camera button is not working
to
BOOTLOADER VERSION NOW
Bootloader : 1.03 1.32b
Built Time : 14:54:39
Built Date : Dec 10 2003
SimPLE StUpID EXPERimeNTaTIOn .. BOOTLOADER PLAYING part 2
DAY TWO - RESULTS of DOWNGRADING FROM 1.06 to 1.03:
Flashing thru EXE from WM2003/SE:
After Flashing thru .nbf the Record is Working but the Camera button is not working ..
after the First Soft Reset the Record button is no longer working
Flashing thru SD Card from WM2003/SE:
After Flashing thru SD Card both the Record and Camera button is not working ..
Flashing thru EXE from WM2005:
After Flashing thru .nbf the Record button and Camera Button is not working ..
Flashing thru SD Card from WM2005:
After Flashing thru SD Card both the Record and Camera button is not working ..
Additional INFORMATION:
STILL if the power button is press once, the Record button is working
but
if the power button is press twice (Total Shutdown), the Record Button is not working
but if the Double TAP FUNCTION OF POWER BUTTON is DeActivated
Record Button is Working if the Device is off but not if on
Camera button is not working both on or off or in any situation
Downgrading from 1.06 to 1.03 Conclusion :
after Downgrading my BOOTLOADER from 1.06 to 1.03 MY RECORD AND CAMERA BUTTON IS STILL NOT WORKING
DONE LOTS OF REGISTRY TWEAKING AND ALMOST ALL POSSIBILITIES INCLUDING DOWNGRADING TO WM2003 and WM2003SE and GO BACK TO WM2005, EMPTYING THE EXTENDED ROM ETC..
AND STILL BUTTON IS NOT WORKING
Sponsor of BOOTLOADER 1.03
rhmartin
and
tumtum
TNX SO MUCH GUYS .. need to compare your both bootloader if i get it right .. TNX
Special Thanks to
buzz_lightyear
and
xda2jojo
and
gotan
heheh thnx for building courage to this dangerous experiment
and especially to the GREAT ONE
itsme
for creating such a wonderful dangerous tool .. tnx so much ..
-toe
NEXT STOP .. BOOTLOADER 1.01 .. WATCH OUT ..
I would image at this point that its probably not bootloader so much as the hardware revision of the device, and probably older devices work, (which typically have older bootloaders).
The REAL experiment would be for someone with working keys to upgrade their bootloader, (like a 1.01 to upgrade to 1.06)...
(Ya I know,... NOT ME!.... :wink: ) Some other braver soul...
Actually Buzz might have done this? Buzz has 1.06, but did Buzz ever upgrade his bootloader?
JamesManios said:
I would image at this point that its probably not bootloader so much as the hardware revision of the device, and probably older devices work, (which typically have older bootloaders).
The REAL experiment would be for someone with working keys to upgrade their bootloader, (like a 1.01 to upgrade to 1.06)...
(Ya I know,... NOT ME!.... :wink: ) Some other braver soul...
Actually Buzz might have done this? Buzz has 1.06, but did Buzz ever upgrade his bootloader?
Click to expand...
Click to collapse
SOme ROM Upgrade, mostly the OLD ROM WM20003 contains already a bootloader 1.06 like the 1.66 and 1.72 (or even 1.75) .. some older rom contains bootloader 1.03 like the 1.60 .. but this ROM will only upgrade/downgrade your device BOOTLOADER if you have unlock bootloader which is most of the case is LOCKED or Protected..
im not sure if there is a rom update that can unlocks the bootloader and change it .. but in the past there is http://forum.xda-developers.com/viewtopic.php?p=54696#54696 .. but in a case of anybody, (tnx my friend for all the info and help .. :wink: ), i believe it was updated and not originally 1.06 since he bought his device December 2003 and the bootloader 1.06 is built in Feb 18, 2004 .. .. and yet still he has a working Rec and Camera button .. but it was repaired in March 2004 so it could be also an update from the service center .. ..
-toe
SimPLE StUpID EXPERimeNTaTIOn .. BOOTLOADER PLAYING part 3
[frutybabes.jpg left]DAY 3 - DOWNGRADING MY Device BOOTLOADER from
Bootloader : 1.03 1.32b
Built Time : 14:54:39
Built Date : Dec 10 2003
and
Bootloader 1.06 1.34b
Built Time: 14:32:09
Built Date: Feb 18 2004
to
Bootloader : 1.01 1.28
Built Time : 22:22:13
Built Date : Sep 15 2003
anyway .. successful .. hehe starting to enjoy playing with BOOTLOADER heheh..
THX JAMES for the Bootloader 1.01 .. ..
anyway .. successful .. hehe starting to enjoy playing with BOOTLOADER heheh..
THX JAMES for the Bootloader 1.01
Click to expand...
Click to collapse
No prob,
Does that mean that the 1.01 bootloader worked? As in your hardware keys are now working, or the downgrade was successful?
hi
i need to confirm yet and do more testing before i post the result of downgrading to bootloader version 1.01
anyway heres my initial FINDINGs
MY RECORD AND CAMERA BUTTON IS STILL NOT WORKING
-toe
Upgrade Bootloader 1.03 to 1.06
Ok, this is a dirty job but (as they say) somebody has to do it!
As suggested by James, maybe if somebody can volunteer to upgrade his bootloader, we can finally put to rest the issue of "not working buttons" as either related to the bootloader or any other thing.
So toe, I see you are successful in downgrading, if you may share & give me the steps to do the upgrade i'm willing to take the risk!
I have bootloader 1.03 & working buttons. I'm willing to try an upgrade to 1.06.
Let me know. Good luck in your experimentations..... :wink:
I find it odd that there could be a software difference that would stop hardware buttons working, and yet here we have it. 2002/2003/2003se all work fine, but put 2005 on and they brake.
the recent experiments in downgrading bootloader would suggest that its the actual hardware that is the problem, ie, later models (tend to have later bootloader) are less likely to work.
From this, I think its time somebody looked at how the buttons actualy interface with the hardware, and what the difference is. Because the phone buttons, the cam/note buttons and the contact/calender buttons all work on different methods.
We may have to resort to a hardware hack. It may be as simple as changing a surface mount resistor to alter the value that the buttons trigger the hardware or as complicated as changing the gpio pins, who knows.
Any hardware hackers wanna take a look?
god i wish this theory of bootloader wud go away ,i bought a secondhand xda2 of ebay last week it has 1.03 and it works fine.
one possible clue is unfortunately is to dismantle the device or remove casing and locate what REVISION the board is.which i will do 2morrow .at the same i will try and identify any obvious differences between the two.
my original device has 1.06 and works fine!!!!!
o still think its a driver issue
well i still think its a driver issue or hardware gpio version issue
if i m not wrong the rom its made for one single device and that device was probably old so
new ones have new ship version and dont work. bootloader is recent
old ones work
and then aggain some new ones works cos the way chip board are manufactured
an old stock off chips got int production in a more recent version of devices wich made some 1.06 bootloaders also work.
so check the driver compared with 2003 driver and the answer is hidden there........
ok i m an idiot full of ideias
god buzz will solve it
god toenailed will prove it
god xda2jojo will anounce it
Re: Upgrade Bootloader 1.03 to 1.06
rhmartin said:
Ok, this is a dirty job but (as they say) somebody has to do it!
As suggested by James, maybe if somebody can volunteer to upgrade his bootloader, we can finally put to rest the issue of "not working buttons" as either related to the bootloader or any other thing.
So toe, I see you are successful in downgrading, if you may share & give me the steps to do the upgrade i'm willing to take the risk!
I have bootloader 1.03 & working buttons. I'm willing to try an upgrade to 1.06.
Let me know. Good luck in your experimentations..... :wink:
Click to expand...
Click to collapse
hi rhmartin .. pls PM me your YM or ICQ bro .. we need to talk live in Upgrading your BOOLOADER .. my first downgrade to 1.03 .. took 1 minute to finish .. and yeah ive been praying that nothing will happen .. when i downgrade to 1.01 from 1.03 it only took 15seconds .. but when i upgrade to 1.06 it took almost 30seconds.. but when i downgrade again to 1.01 and now from 1.06 it took me also 36seconds .. anyway its more on your PC and PPC condition than the actual upgrading process .
wish you were in pHilippines so we can study and compare our device ..
anyway guys before i even try to downgrade my Bootloader id already ask a forumer who has a working button to open his device and i will open my device also and compare it with him .. i just had to confirm first using all bootloader that its not really a bootloader issue .. it will just take us too long since i cant find a forumer near to my place that has working button to compare it we only communicate thru IM ..
ONE MORE THING GUys .. anyone here has also BOOTLOADER 1.01 pls pm me .. id like to check and compare it with the one i got from JAMES .. im having some problems with 1.01 than with 1.03 .. id like to know if this is just me and my device or the problem is incompatiblity somewhere of bootloader itself ...
anyway JAMES have you try using an MMC bigger than 64MB .. i dont have a problem in SD card even in 1gb but if i use MMC it can only read first 64MB and it will hang there .. i already try it in 1.06 but i havent encounter that problem .. i remember in 1.03 that i dont a problem in that either .. anyway tnx again for the 1.01 ..
amdworld said:
god i wish this theory of bootloader wud go away ,i bought a secondhand xda2 of ebay last week it has 1.03 and it works fine.
one possible clue is unfortunately is to dismantle the device or remove casing and locate what REVISION the board is.which i will do 2morrow .at the same i will try and identify any obvious differences between the two.
my original device has 1.06 and works fine!!!!!
Click to expand...
Click to collapse
hi amdworld
can you make a Post in Here .. plsss
http://forum.xda-developers.com/viewtopic.php?t=22737
including your Serial Number and part number .. to see how old your device really is .. plss .. tnx
-toe
i m getting more convinced of driver
i read thats what i do and read here that TSC2200 is responsible for the keys
so there is REV A to F of that chip
not working camera and record must be it
i put some file here for the you guys have a look
Re: i m getting more convinced of driver
rictec said:
i read thats what i do and read here that TSC2200 is responsible for the keys
so there is REV A to F of that chip
not working camera and record must be it
i put some file here for the you guys have a look
Click to expand...
Click to collapse
=hi rictec..
actually m with you that the problem is due to driver (or dll) and it can be fix with a patch or a new driver .. since we dont have this problem in old WM version .. maybe we just need to distinguish first wat causes the problem ..
anyway tnx for the info .. been doing great help for me .. especially the 1.01 ..
-toe
i tested a 128 mmc card and its ok
i did test for a 128MB MMC card i have in my foto camera and it worked ok
i usualy use a 1GB sandisk SD card
if that can say anything...its tested
Ps i never tryed a MMC card befoure only SD
Re: i tested a 128 mmc card and its ok
rictec said:
i did test for a 128MB MMC card i have in my foto camera and it worked ok
i usualy use a 1GB sandisk SD card
if that can say anything...its tested
Ps i never tryed a MMC card befoure only SD
Click to expand...
Click to collapse
hi rictec ..
oic tnx .. ill try your bootloader if i still have the same problem .. and post later the result ..
tnx again MATE .. :wink:
-toe
and if you will open your device
at least read this will make it go bether lol
Hardware
I have an old XDAII from Korea that came with 1.52 or something like that and a newer one from China with 1.66 with Chinese on it.
I have 2.20 Translated on both now.
The hardware is different.
I broke the screen on the China one and I took the screen out of the older unit. The connections would not even fit. Different hardware. :shock:
The China one is at www.PPCtechs.com now. When it comes back, I will flash them both with 2005.
If one works and the other does not... It will prove it is a hardware issue.
Volume slider program
Has any one tried this http://ae.inc.ru/aebplus_t.html It woks great on 2003 2.20 etc. If it works on 2005, even with only the two top buttons, you could have a total of SIX buttons. (two real and 4 virtual) If the Volume slider part works.. THAT WOULD BE GREAT TOO!
...Details are best left private, but the unit was one of the first Atoms to be released. it has been upgraded to the Jan rom, and then left alone because its owner was, uh, more chicken than I am. The Mini I used to own will be going to someone else. >_>
I will miss Bigstorage, a small price to pay for (somewhat) limited Wifi and no longer having to fear losing all my data to a power out.
Few questions here:
1. Is it safe to use the Xda-Atom-Exec-ENG-20060721-MOT0822.exe from the FTP yet?
2. Should I use that or the Xda-Atom-ENG-20060426-MOT0822.exe ?
3. Is there a way to disable the message that refuses to run unsigned exes, or is there an exe signer anywhere? I remember it having problems with programs that don't need installation.
Thanks in advance.
...Just got it today.
Apparently it's been through the service centre once, so it's ROM turned out to be the 20060426 one - radio still at RS*49. Still wondering if I should flash for the new radio driver.
I've read through the forums and I think I won't be messing around with the Exec rom for now.
Thanks, all.
i currently using the Atom with Atom Exec ROM version Xda-Atom-Exec-ENG-20060721-MOT0822
and so far until now, no prob at all..
anyone know how to cook WM5 ROM in atom,
cause, i see to other forum, they have the ROM WM5 AKU3.5 into their device,,
why can we (atom) have that to??
Ehehehehehe. Finally took the risk, nearly lost my phone - tho it was easily fixed by flashing over with the same Exec rom again. The ROM I grabbed from the FTP right here on xdadev. <_<
See, a funny thing happened.
I installed the Extrom revealer hack for extra space.
Then I installed SKTools Trial 3.0.75 - and thereafter the Extrom revealer hack stopped working.
So my device asked me this question - "Do you want to format your Storage Card so it's easily readable?"
not wanting to get my 2gig eaten, I removed it, and tried to click NO... only I accidentially touched "Yes".
Whoops.
Everything just stopped working - well, except the phone and basic winDOS mobile 5 apps.
Soft reset - device took ages to boot. Nothing that isn't WM5 native runs.
Hard reset - device went wonky, still booted, but screen got out of alignment. Still usable, but autoconfig not working (detected Sim as jumble of numbers, but phone still works).
Went into device settings -> system info.
Guess what I saw:
CMOS: NULL (WTF)
ExtROM: NULL (WTF)
...correct
...correct
...correct
And upon looking at the Flash Size, I saw 192MB (?!). Fake number?
(No screenshots will be made avaliable. I will NOT do this again.)
Anyways, a reflash put the unit back in full working condition, problem, but I'm still seeing it report that I have 192MB of Flash RAM avaliable. Oy.
Still workink for now, but I hope this won't mess up the system any. -.-
Hi everyone, I need help please. I am trying to flash a WM 6.5 ROM to my NIKI 100 (20 keys) but I cant seem to find a HardSPL that will work on my phone I always end up getting "ERROR[262]" I followed the steps to flash sspl-1.16-NIKE.exe on my phone in order to flash a HardSPL but still the same problem.
I have Official 2.09.405.1 ROM, Radio - 1.65.28.25. If I go into bootloader mode it shows: NIKI 100
SPL-1.22.0000
CPLD-4.
Is there anyone that can tell me wich HardSPL I need?? So far I"ve tried -
flash-HardSPL-Niki, HardSPL-1.15mfg-Nike, HardSPL-1.16.Nike, HardSPL-1.22-Nike-shipped and Flash-uspl-Niki.
Thanks
I hope this help
1. installed the SSPL installatoin, v1.16 (look at this thread http://forum.xda-developers.com/showthread.php?t=355730 for the installation)
you can skip step 7 and above.
2. Still in Bootloader screen, you can install HardSPL 1.22 using the installation files.
Dont worry about the step that device must connected to activesync just check the status and do next to update ROM. As long as your device is in bootloader mode (rainbow color) the update process can continue even you are not connected to activesync
3. Good luck
Has this been solved?
Heya Cyanide..
Has this problem been solved? If not, I reckon you should check this out: http://forum.xda-developers.com/showthread.php?t=377260
I have both the 16 keys and 20 keys versions of the HTC Touch Dual. And the confusing thing is, the 20 key version is not a Nike. It is actually a Neon 200 (or at least mine is). How do you tell?
Remove the back cover of the phone, and remove your battery... The label will reveal whether it is in fact a Nike or a Neon. If it's a Neon, then that explains why your attempts to Hard-SPL haven't worked to date.
Anyways, hit up that link above, and you should be able to Hard-SPL easily. If you need directions, let me know, but it should be fine... let us know how you go
HK 20key version is NIKI100
Hi dr3wster
Just FYI. In HK 20 keys version of the Touch DUAL says NIKI100 inside the battery compartment.
to be honest I'm confused over NIKI, NIKE, NEON now, but will keep reading.
dr3wster said:
Heya Cyanide..
Has this problem been solved? If not, I reckon you should check this out: http://forum.xda-developers.com/showthread.php?t=377260
I have both the 16 keys and 20 keys versions of the HTC Touch Dual. And the confusing thing is, the 20 key version is not a Nike. It is actually a Neon 200 (or at least mine is). How do you tell?
Remove the back cover of the phone, and remove your battery... The label will reveal whether it is in fact a Nike or a Neon. If it's a Neon, then that explains why your attempts to Hard-SPL haven't worked to date.
Anyways, hit up that link above, and you should be able to Hard-SPL easily. If you need directions, let me know, but it should be fine... let us know how you go
Click to expand...
Click to collapse
With wich OS you PC (not your HTC) is working?
The error message sounds to me like you are working with VISTA.
If so, try to do these steps on a XP system, and it should work.
Hi,
I made sure...underneath the battery it says NIKI 100.
I tried alot of hard spl's and nothing works.
MvSt said:
With wich OS you PC (not your HTC) is working?
The error message sounds to me like you are working with VISTA.
If so, try to do these steps on a XP system, and it should work.
Click to expand...
Click to collapse
I am working with XP and not Vista
me too have same problem with niki100
i have also same probelm under battrey writen niki100 i tried alot of things here
but not working .
i need a help to flash my niki100 to english
thanks
clickes2000 said:
i have also same probelm under battrey writen niki100 i tried alot of things here
but not working .
i need a help to flash my niki100 to english
thanks
Click to expand...
Click to collapse
Try it this way.
Greetz,
Hi, I have a T4242 with WM6.1 and WM6.5 wanted to install but none of the procedures found in the internet for the T4242 or T4242 + worked, I tested the procedure for the T3238 with the file k3img.bin updated and only the keys no longer work, the Touch works normally but the keys type Vol Up - Down Vol take no more and the key now is the key Dial Red
By contrast he was much quicker than before.
Would not someone pass me a T4242 with WM6.5 ROM in BIN format, so I can apply the T4242 by IDT program?
If it can be even better in Portuguese.
Or a way to configure the hardware device.
OBS: Translated by google.
Assume you have read the HTY thread in this forum.....http://forum.xda-developers.com/showthread.php?t=607709
Perhaps one if the guys there can help you out.