C:\Repair\JFlash_MM>jflashmm pxa27x32 ebo_a.nb0 N 0 PAR
JFLASH Version 5.01.007
COPYRIGHT (C) 2000 - 2003 Intel Corporation
PLATFORM SELECTION:
Processor= PXA27x
Development System= Mainstone
Data Version= 1.00.001
PXA27x revision ??
Failed to read the Flash ID. Retrying 4 more times...
Failed to read the Flash ID. Retrying 3 more times...
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: F000
Failed to read the Flash ID. Retrying 2 more times...
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: F000
Failed to read the Flash ID. Retrying 1 more times...
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: F000
Failed to read the Flash ID. Retrying 0 more times...
Cannot open input file: Flash_f000_2_32.dat
This program supports flash devices defined by DAT files
contained in the same directory as the executable program.
If the file cannot be opened, there are four possibilities:
1 - The flash device installed is not supported.
2 - The flash device is a licensed product.
3 - The device ID could not be read, resulting in a poorly
constructed filename. The first numeric value in the
filename is the device ID. Verify this value with the
component specification.
4 - The memory bus is not functional. Check all CPLD and FPGA
devices. Make sure that you are using the correct
platform data file.
C:\Repair\JFlash_MM>jflashmm pxa27x32 ebo_a.nb0 N 3F40000 PAR
JFLASH Version 5.01.007
COPYRIGHT (C) 2000 - 2003 Intel Corporation
PLATFORM SELECTION:
Processor= PXA27x
Development System= Mainstone
Data Version= 1.00.001
PXA27x revision ??
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: F000
Failed to read the Flash ID. Retrying 4 more times...
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: F000
Failed to read the Flash ID. Retrying 3 more times...
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: F000
Failed to read the Flash ID. Retrying 2 more times...
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: F000
Failed to read the Flash ID. Retrying 1 more times...
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: F000
Failed to read the Flash ID. Retrying 0 more times...
Cannot open input file: Flash_f000_2_32.dat
This program supports flash devices defined by DAT files
contained in the same directory as the executable program.
If the file cannot be opened, there are four possibilities:
1 - The flash device installed is not supported.
2 - The flash device is a licensed product.
3 - The device ID could not be read, resulting in a poorly
constructed filename. The first numeric value in the
filename is the device ID. Verify this value with the
component specification.
4 - The memory bus is not functional. Check all CPLD and FPGA
devices. Make sure that you are using the correct
platform data file.
Check This
Cannot open input file: Flash_f000_2_32.dat
How do i revive this Phones (((
I am in Gr8 tension
what u do with ur phone?
kingofhearts said:
Check This
Cannot open input file: Flash_f000_2_32.dat
How do i revive this Phones (((
I am in Gr8 tension
Click to expand...
Click to collapse
What were you trying to do?
Actually i was upgrading my phone and unfortunately instead of ATOM life i upgraded to different model and i wrote the Eboot file via memory card now only orange light blinking near the speaker and its not recognised on USB although i did all possible efforts to revive my phone but unsuccessful. I made that J-TAG cable and its working fine 100% but the thing is the loader is missing in JFlash_MM through which we program the flash IC. Although it have another different loaders and dat files but the one which i need is missing. ATOM LIFE and ATOM EXEX both have different loaders.
Looking forward to hope for the favorable reply.
Kind Regards
Haseeb
jtag problem
Dear
I am Adil from Islamabad, I have the same problem with my atom life phone.
I repair my phone with the help of repairing shop located Islamabad(blue Area) if you want help, contact me 0345-6501650
madil said:
Dear
I am Adil from Islamabad, I have the same problem with my atom life phone.
I repair my phone with the help of repairing shop located Islamabad(blue Area) if you want help, contact me 0345-6501650
Click to expand...
Click to collapse
Can you please give me the instructions you got from the repairing shop, via email, [email protected]
Thanks.
help!!! Adil
adil pls help me repair my atom life it has a dead bootloader u said u have revived it through a repair shop in islamabad well than pls give me the instructions of how 2 repairs atom life would be really appreciated
thanx a lot
jtag image
could you post an instruction to the jtag image, because my atom life is dead as well and the jtag method under wiki is not working for me.
please help to get atom life back to life
very appreciated.
MrQ
Related
Hi,
I spent 6-7 hours of reading all kind of suggestions and etc, how to bring a brick to life. the only closest to my situation is http://forum.xda-developers.com/showthread.php?t=295623
I flashed my phone several times and i hadnt much of problems until i tried to put wm6 update.
The last time I tried to downgrade to CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE and the phone freezed to the start screen (that picture with the beer). I restarted it several times but it never went beyond it.
Then I tried to put the previous ROM that worked. I entered bootload mode and started the upgrade wizard. I waited it to finish, but it didnt! When it reached 98% it suddenly got back to 95%(!?) and after few seconds a message for connecition interupted appeared on the computer. The phone stayed on 95% for some time more and nothing happened. Then i clicked on the "how to restore" button of the upgrade wizard. I followed the instructions which stated on step 3 "remove the battery of the phone".
After I did that, my phone died and since then i cant do anything with it. The screen is all black. Of course I tried hard reset, bootloader mode and etc - all failed. It doesnt go into bootloader mode or do hard reset. The computer does not detect any USB connections. The charger doesnt appear to be detected by the phone (LED doesnt light up). There should be 50-60% battery power left. It was working perfectly before flashing.
I think the main problem now is how to enter the Bootloader.
Im not quite familiar with SD flashing, but i think i have the necessary hardware, just please advise is it possible and how I can do it.
Edit: Now I found that my SD card is unreadable too
Please help
Sorry
Greetings,
Sorry for your situation, but do you have G4 or G3 wizard.
If G4 was it CID locked or unlocked.
samy.3660 said:
Greetings,
Sorry for your situation, but do you have G4 or G3 wizard.
If G4 was it CID locked or unlocked.
Click to expand...
Click to collapse
it is g4 cid locked
edit: i now remember that IPL & SPL had different versions like 1.x & 2.x after downgrading. I didnt know that I have to reflash in that case i found it in the forum too late
You should have read more before trying to flash your phone...
That downgrade that you made bricked your phone. That ROM was intended for G3 ONLY. If you have a G4 you should flash only G4-ROMS (or read how to extract ipl & spl from a G3 ROM) ... I am afraid there are no known solutions, because IPL and SPL on a G4 can`t be succesfully upgraded/reflashed (the hardware doesn`t allow that)
(the hardware doesn`t allow that)
Click to expand...
Click to collapse
so how i did broke them in the first place?
anyway i'm trying to cook a SD card image, but the typhoon 5 tool doesnt convert the files to sd image format
Code:
C:\work>typho5.exe -r ipl=nk.nbf -d az.img
read 04741800 for ipl from nk.nbf
no IPL at 4 in IPL image
my idea is to either get a packeded file with all the modules or put them to the SD card one by one at the appropriate offset as it is described in the Wiki (using the winhex disk editor). Is the *.nb format the same as the modules in the SD card image? I mean can i directly paste the contents of the .nb files into the apropriate offset to the empty SD card?
Your only solutions are to get a new board or to get a JTAG device and discover the JTAG pins on the board since it's the only way you can access the flash chip without a bootloader. Problem is until now no one has managed to find the JTAG pins (or bothered).
What you have done was flashing an IPL (Initial Program Loader) that is for G3 DOC chips only (with a 130 nm manufacturing process) ; and since you have a G4 DOC chip (90 nm manufacturing process) the process fails.
This is the IPL:
A small XIP memory (ROM, NOR flash or DiskOnChip boot block) that contains code to
perform minimal system initialization: It must at least initialize the chip-select unit so that
the ROM (if any), RAM, and DiskOnChip can be accessed.
Click to expand...
Click to collapse
3.2. The Boot Process
• Power up and initialization: After system power up, the IPL code that resides on the XIP
block of the DiskOnChip is executed. The IPL code initializes the DiskOnChip controller
and the RAM.
• Copying the SPL code from DiskOnChip to RAM: After initialization, the IPL reads and
loads the SPL code from the DiskOnChip binary partition to RAM. It then jumps to the SPL
start address in RAM and executes the SPL.
Notes: 1. In general, the IPL is limited in size to several KB (the size limitation varies,
depending on the device type), so it is not possible to include both the system
initialization code and the error correction code. The absence of the error correction
code in the IPL is the reason why the boot process is divided into the IPL stage and
SPL stage. The actual loading of the OS image to RAM is done by the SPL code.
Since the SPL runs in the system RAM, there is no limit on code size and it can
include the error correction code.
Click to expand...
Click to collapse
As you can see on step 2 the IPL can't load SPL since they are for different chip versions.
cheers
mestrini said:
Your only solutions are to get a new board or to get a JTAG device and discover the JTAG pins on the board since it's the only way you can access the flash chip without a bootloader. Problem is until now no one has managed to find the JTAG pins (or bothered).
What you have done was flashing an IPL (Initial Program Loader) that is for G3 DOC chips only (with a 130 nm manufacturing process) ; and since you have a G4 DOC chip (90 nm manufacturing process) the process fails.
This is the IPL:
As you can see on step 2 the IPL can't load SPL since they are for different chip versions.
cheers
Click to expand...
Click to collapse
yes, it seems that happened, but after flashing the g3 version, the phone still enters the bootloader. It died completely AFTER i tried to return the g4 version, and may be all happened because it didnt finish the instalation (which interupted for no reason) and stayed with messed up versions.
Anyway seems I need a new mobo, but i'm not sure i could find it here (i'm from Bulgaria) the closest vodafone store is in Romania. The phone is from Germany, a friend of mine bought it there.
FRIENDS help , I think I have the brick of all bricks I followed the wiki step by step including creating and copying the nbh file. I got as far as 70% of image loading and it hung and dropped into recovery mode but could not get passed there. I have tried all forms of reset and do not get passed bootloader screen with Herm100 IPL-1.04 and SPL-2.03. This was a imate jasjam running windows mobile 5.0 to which I tried flashing to the new HTC WWE 6.0 upgrade. I have tried running usb monitor from the link but it just gives me a series of paramters in a notice window and then dops off. I have tried another verison but it is not capturing anything.
I have tried mtty and cant even get the usb> prompt after disabling the usb connect in activesync. Please help as this was a works new unit last month and I have some major explaining to do if I cant get it sorted!
Model: Imate Jasjam
ROM Before Flash: TMO_UK_3.60.110.1_6275_1.50.00.00_108_Test
Radio Before Flash: 1.50
Bootloader Before Flash: Not sure
Flash failed at: 70%
Flashing ROM: Image Vers 3.54.255.3
CID Corrupt: Assume Yes
Radio Corrupt: Assume Yes
No GSM Error: Not got that far
Stuck In Bootloader: Yes
Stuck On Windows Mobile Splash: Not got that far
Can boot into OS: No
Tried mtty command set 14 0: Yes but not getting usb>
Tried wiki problem number 4: Yes dont get passed point 3 as as soon as powers up goes to tri colour screen. Switched from serial to usb with connect of usb cable
mtty info 2 output: cannot run
Current Device Status: unusable
Tried re running install and get error 260 and 294(AFTER 1%)and - Not getting a response from PDA!
I TRIED PB + KITL method .BUT IT FAILED AS I COULD NOT ACTIVATE KITL MODE.I BELIEVE ITS NOT ACTIVATED IN MY PDA.
I SPOKE TO TO IMATE INDIA PEOPLE , THEY REPLIED THAT THE MOTHERBOARD IS TO BE CHANGED , WHICH COSTS 60% OF THE COST OF THE PDA.
CAN ANYONE HELP WITH A BOOTLOADER V2.03 ?
WAKE UP DEVELOPERS .DO SOMETHING.
tHANKS IN ADVANCE.
the output is for :
HTC_Hermes_SIM_CID_Unlock_v3a
And
RUU_Hermes_TMO_UK_3.60.110.1_6275_1.50.00.00_108_Test repectively.
So no HardSPL before you flashed?
You should still be able to get a USB monitor from it.. regardless if the thing has been thrown off the empire state building.
What USB monitor program are you using?
MTTY Set 14 0 I beleive is for a corrupt radio stack, all that does is restore your radio stack to factory form, sounds to me like you have a hybrid brick, which is corrupet or invalid CID coupled along with a corrupt radio stack..
Madcap180 said:
MTTY Set 14 0 I beleive is for a corrupt radio stack, all that does is restore your radio stack to factory form, sounds to me like you have a hybrid brick, which is corrupet or invalid CID coupled along with a corrupt radio stack..
Click to expand...
Click to collapse
set 14 0 tells the device to skip to OS boot rather than go to bootloader (opposite of set 14 1)
what we need to ascertain is exactly what bootloader version this guy is running, and then to find out what CID he has from the bootloader.
until we get these both, I think we'll have to "assume" it's ****ed.
oh and in future, don't PM me twice, it pisses me off. so consider yourself lucky I've bothered to comment.
Cmd>
Cmd>info 2
HTCSCDL__001ÄÊìHTCE
Cmd>info 7
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
CPU ID=0x41129200
Main CPLD version=0x5
Upper CPLD version=0x4
Main Board version=0x6
Cmd>info 6
HTCST ÚÈÒHTCE
Cmd>info 5
Cmd>info 4
HTCSCDL__001ÄÊìHTCE
Cmd>info 3
HTCSH
Cmd>set 14 1
Write Nand Success
HTCST ÚÈÒHTCE
Cmd>rtask 32
Command error !!!
Cmd>rtask 28
Command error !!!
Cmd>rtask 8
Command error !!!
lastly it's not KITL enable.
Hi,
I tried updating my XDA Atom to WM6 using one of the roms from this site. The flash worked up till the last part when it was meant to reboot when something wnet wrong and it crashed.
My Atom is now dead - no reset method works, even the soft reset and camera combo...
i think the bootloader has been corrupted.
So i followed the guides on this site and made the Jtag interface to reflash the bootloader. The cable works fine, the orange LED is flashing - i've installed the software, but every single time i try to flash the bootloader, i get the error below....can anyone help as i want to get my Atom back
PXA27x revision ??
Failed to read the Flash ID. Retrying 4 more times...
Failed to read the Flash ID. Retrying 3 more times...
Failed to read the Flash ID. Retrying 2 more times...
Failed to read the Flash ID. Retrying 1 more times...
Failed to read the Flash ID. Retrying 0 more times...
Cannot open input file: Flash_0_2_32.dat
This program supports flash devices defined by DAT files
contained in the same directory as the executable program.
If the file cannot be opened, there are four possibilities:
1 - The flash device installed is not supported.
2 - The flash device is a licensed product.
3 - The device ID could not be read, resulting in a poorly
constructed filename. The first numeric value in the
filename is the device ID. Verify this value with the
component specification.
4 - The memory bus is not functional. Check all CPLD and FPGA
devices. Make sure that you are using the correct
platform data file.
anyone? i'm hoping there is something atupid that i've missed out which will get it working again...
HI, I'm having the same problem while trying to update my atom, now my atom dead. Can u Try to help me, since u got experinces of setting up the cable.. I don't knoe how to do the cable things ..pls help [email protected]!
manni said:
Hi,
I tried updating my XDA Atom to WM6 using one of the roms from this site. The flash worked up till the last part when it was meant to reboot when something wnet wrong and it crashed.
My Atom is now dead - no reset method works, even the soft reset and camera combo...
i think the bootloader has been corrupted.
So i followed the guides on this site and made the Jtag interface to reflash the bootloader. The cable works fine, the orange LED is flashing - i've installed the software, but every single time i try to flash the bootloader, i get the error below....can anyone help as i want to get my Atom back
PXA27x revision ??
Failed to read the Flash ID. Retrying 4 more times...
Failed to read the Flash ID. Retrying 3 more times...
Failed to read the Flash ID. Retrying 2 more times...
Failed to read the Flash ID. Retrying 1 more times...
Failed to read the Flash ID. Retrying 0 more times...
Cannot open input file: Flash_0_2_32.dat
This program supports flash devices defined by DAT files
contained in the same directory as the executable program.
If the file cannot be opened, there are four possibilities:
1 - The flash device installed is not supported.
2 - The flash device is a licensed product.
3 - The device ID could not be read, resulting in a poorly
constructed filename. The first numeric value in the
filename is the device ID. Verify this value with the
component specification.
4 - The memory bus is not functional. Check all CPLD and FPGA
devices. Make sure that you are using the correct
platform data file.
Click to expand...
Click to collapse
Just try press and hold soft-reset button before run jflashmm.
Cheers,
Benz
manni said:
Hi,
I tried updating my XDA Atom to WM6 using one of the roms from this site. The flash worked up till the last part when it was meant to reboot when something wnet wrong and it crashed.
My Atom is now dead - no reset method works, even the soft reset and camera combo...
i think the bootloader has been corrupted.
So i followed the guides on this site and made the Jtag interface to reflash the bootloader. The cable works fine, the orange LED is flashing - i've installed the software, but every single time i try to flash the bootloader, i get the error below....can anyone help as i want to get my Atom back
PXA27x revision ??
Failed to read the Flash ID. Retrying 4 more times...
Failed to read the Flash ID. Retrying 3 more times...
Failed to read the Flash ID. Retrying 2 more times...
Failed to read the Flash ID. Retrying 1 more times...
Failed to read the Flash ID. Retrying 0 more times...
Cannot open input file: Flash_0_2_32.dat
This program supports flash devices defined by DAT files
contained in the same directory as the executable program.
If the file cannot be opened, there are four possibilities:
1 - The flash device installed is not supported.
2 - The flash device is a licensed product.
3 - The device ID could not be read, resulting in a poorly
constructed filename. The first numeric value in the
filename is the device ID. Verify this value with the
component specification.
4 - The memory bus is not functional. Check all CPLD and FPGA
devices. Make sure that you are using the correct
platform data file.
Click to expand...
Click to collapse
Try to reset button before use JFlashMM. I'am same as problem with you. but i use resistance(R) is 390 ohm.(390*4)because voltage is more it damage to CPU or M-system chip, warn about long of wire connector if more long signal is loss. 1st. reset button Avery time as you flash JflashMM (JTAG). anf finally
my atom is incoming .......Good luck to you.
I have a problem when upgrading ROM: whether upgrade rom by SD or ASync, the progress bar always stucked at 36%. Any ideals?
I have a HTC HERM200, I did a hard reset, the problem is that no radio version and no protocol version displayed device information in parameters and of course impossible to operate my pocket pc as a phone and call using it !
I tried the hard spl 7.
for the 'info 7', this is the result :
HTC Integrated Re-Flash Utility, Common Base Version : 1.51d
Device Name: HERM100, Bootloader Version : 2.10.Olipro
Built at: Apr 22 2007 13:32:26
Copyright (c) 1998-2007 Modified By Olipro - Hard-SPL
CPU ID=0x41129200
Main CPLD version=0x5
Upper CPLD version=0x4
Main Board version=0x6
(in windows, my version of herm is 200, here with the info_7 command it is herm100 !)
when typing 'rtask a', the answer is always command error !!!
how can I install the radio and is there a good version of WM6 compatible with my reference ?? if you can help me this will great for me
thanks !!!
Try reinstalling the shipped rom. You can also try a radio only rom but if neither of these 2 things work, you have a brick on your hands...
Sorry...
reinstalling shipped rom
thanks ultramag69 for your reply,
where can I download a good functional and compatible version for the shipped rom to my herm200 and how to proceed. I tried different version with unsuccess.
I tryed the 'HERM_Radinly_1.56.70.11_CustomRUU' using my sdcard proceeding with renaming the file .nbh to HERMIMG.nbh, the setup stopped at about 10%, and still there for more then 2 hours !!
installing with the usb cable stop always with error#262!
I wish I have a brick on your hands, this means that there is a way to recover the phone operational state !!
"Shipped ROM" means the rom that came on your Hermes. Generally a carrier has its own rom (you should be able to find on the carriers website).
Since you have Hard SPL on your Hermes use the sd card method.
1. format sd card fat32, copy .nbh file onto it & rename to "hermimg.nbh". Put back in Hermes.
2. Reset into bootloader - hold power,, ok button above flywheel and reset with stylus. hold in until tri-colour screen comes up.
3. If you did 1st 2 steps properly then follow the prompts.
This may take a while for the radio to install so give about 20-30 mins. Make sure you do this with a charged battery.
If this doesn't work then I'm sorry, but you have a brick...
You can still install an OS only rom but you won't have phone functionality again...
You can also try a radio only rom.. Above conditions apply...
Good Luck.
Hi,
I have a big problem.
Sorry, but i already search in this forum but no success.
I upgraded a ATH100 with a SPL 3.65 ATH400 Rom
Now, i try to back to ATH100 but i cant. With PC and RomUtility, i get MODEL ID 244 error.
With SDCard i get 00058002 error while Loading...
Anybody can help me.?
Thanks
athena400back to 100
i was in too, now if you cant downgrade yet,sent me an Email ,to [email protected] and sending to me alot of pic from thet and information about your rom.
hi guys,
I had the same issue too....can not flash from SD card with 00058002 loading ...
any solution yet ??
hi guys,
I had the same issue too....can not flash from SD card with 00058002 loading ...
any solution yet ??
I have same problem. Please anybody can help me?
Try out This>>>>>
ERROR [244] : INVALID MODEL ID
from cmonex @xda-dev
This is good for both corrupt modelid and corrupt wifi, and fixes both at the same time.
STEP BY STEP:
1. download attachment at the end of the post for mac1.exe (requires .net 2.0 installed on the PC)
2. you will also need to download the other attachment in this post for the mtty program.
3. enter bootloader (tricolour screen) manually by pressing and holding camera button all the way in (yes I mean that, press it in as hard as you can!!), while doing a reset, then keep the camera button held until you see the tricolour screen.
4. disable USB in activesync (wmdc if you have vista - in this case, do not kill wmdc, just disable usb in it!!!)
5. run mtty and select USB option from the dropdown box!
6. then press enter in main window that comes up, see if that gives you Cmd>
7. now you should have Cmd>, if not, re-check if you did the above steps right until you get Cmd>
8. now run the mac1.exe, type in your MAC address you want to use for the Athena, if you have SPL 3.xx reported on the tricolour screen, then use the button for SPL 3.xx, otherwise if you have SPL 1.xx reported, use button for 1.xx.
9. this should have generated a .bin file for you, copy that bin file in the folder of mtty.
10. now, in mtty, type (do not copypaste!) this command: task 32
11. this should return Level = 0
12. now, you must only do one of the two following commands:
- if you have SPL 3.xx, then type (do not copypaste!!) this command: lnb filename.bin 76508000
(there filename is the name of the .bin file you generated - don't forget to put .bin after filename, as the full name is needed).
- OR, if you have SPL 1.xx, then the command is different (do not copypaste!!): lnbs filename.bin 75108000
(there filename is the name of the .bin file you generated - don't forget to put .bin after filename, as the full name is needed).
NOTE, the command starts with a lowercase "L", not "I"!
WARNING: PLEASE DO NOT MIX UP THESE TWO DIFFERENT COMMANDS!!!
if this info helps: most people will have SPL 3.xx, and if you have AP4 (not vanilla) already running then you're definitely 3.xx
13. mtty will popup a window asking "OK", you press OK!
if you get "Fail to synchronize with the host (1)", then make sure you did follow step by step. if still same error, try placing mtty and the bin file under C:\.
14. now the file downloads, if mtty reports it flashed the file, and at the end "code entrypoint unknown", then that's it, now boot back to WM and see if wifi works.
Download: Mac1.zip mtty_0513_Test.zip
But where atachment ?
For me....WORK...THANKS again CMONEX
but i not do to repair wifi i want to flash my wm........
help me please ,,,
i make hard spl for athe400 in athe100
"ERROR [244] : INVALID MODEL ID
from cmonex @xda-dev
This is good for both corrupt modelid and corrupt wifi, and fixes both at the same time"
as it says it fixes corrupt modelid
It is worth a try
ERROR[244] :Invalid model ID ATHE100
Hi,where do i find the MAC adress for my ATHE100 as i cannot get forward from the bootloader?I am using SPL-v1.20.Olipro.Thanks to any1.
Yes, where is the MAC ADDR
As above, would be grateful if anyone would help us find where the MAC address and thanks for this thread this is the bane of most new owners and newbies. Cheers!!
Mac addr found, but......
Yes found the MAC address - it's under the battery cover, but having gone thru the whole process I got the following 3 errors at the end-
ERROR: no header matched
Transfer CERT error
Flash Programming Error
Thanx buddies!
3 ERROR Messages!!!
Hi Lakeman, could you help decipher these mysterious errors which I had after I have gone through the process twice
ERROR: no header matched
Transfer CERT error
Flash Programming Error
Thank you!
invalid Command
command error
whats wrong???
Cmd>lnb ameo.bin 76508000
lnb ameo.bin 76508000
Command error !!!
here you go >> http://xacsx.de
german ameo-site, roms, repair, and other helpful things
command error
whats wrong???
Cmd>lnb ameo.bin 76508000
lnb ameo.bin 76508000
Command error !!!
if you get notice
-> ERROR [242] : INVALID LANGUAGE
-> ERROR [244] : INVALID MODEL ID
-> ERROR [294] : INVALID VENDER ID
-> ERROR [296] : UPGRADE ONLY
One of these error messages will appear when you use the wrong RUU to do the upgrade. RUU will check if the Model ID and Language ID are compatible with the device. Make sure you use the appropriate RUU tool to upgrade.
stuck in bootloader. Help needed.
I have a HTC Athena x7500.
accidentally upgraded my htc x7500 WITH SSPL-Manual-x7510.zip of HTC X7510
Wend I turn on the device, it goes directly to bootloader and
the screen is:
ATHE 100
IPL - v1.00
ATHE 100
SPL-v3.05.0000 OR my old spl is 1.10.0000
I have tried to change the language of my athena and then he died :spanish > fransh
USB (wend is to connect)
series (wend is unconnectable).
I can not turn the unit off by pressing the button, but must take
the battery.
I have tried with hardspl its not working
I want a solution in the forum xda-develop it says my q must upgrade to the rom of espana oficial
After downloading the rom:Advantage_HTC_SPA_2.21.412.1_1.50.00.00_Ship
I tried to upgrade to this rom May j has a mesage on my athena screen:
found spl v1.10
dowload Spl before v3.05 is not allowed!
I tried to update it with the sd card i have the same mesage
upgrade with athenaUnlucker not work
upgrade with hardspl v7 not work
upgrade with CheetahUnlocker not work
upgrade with athena wraper not work
I have explored ruu_signeg.nbh in spanish rom with notepad jai entered the signer spl 1.10 I know if is sure or not
I believe there is a problem in the image rom saved in my athena rom
what I see on the screen of my athena is the spl 3.05.0000
The real spl is 1.10.0000 there is confusion in my spl
with mtty : task 32 level=ff
is what I can fix this problem with mtty
so if possible please guide me
I board on my pda (cid locked)on the Spanish language HTC_304
sorry for my bad Englis
thank you in advance
My email: [email protected]
http://forum.xda-developers.com/showpost.php?p=5205291&postcount=8
I think there is another thread somewhere about this but you could try the incorrect ID fix in the post above
and try to do the lower SPL