Database Users

No Radio, Stuck on splash screen

Caused my curiosity, I flashed my Radio ROM with "Phoenx06_Radio_1.41_all_carriers" apache radio ROM. And now my mogul stuck on splash screen with "no radio" in the bottom. Can't boot OS.
i've tried reflash with official SPCS ROM RUU_TITAN_SPRINT_WWE_2.09.651.3_1.32.00_SPCS_NV124_new_Ship, hundreds times, It's always said succsessfull, but still stuck with no radio.
then i used titanunlocker (thanks Olipro..) http://forum.xda-developers.com/attachment.php?attachmentid=52162&d=1190835601 , i put in Bootloader mode, SPL-1.04.0000, but won't flash. Ican't connect to ActiveSync and run haret.exe because i can't boot OS.
Olipro said : "the NBH won't flash because it's not signed with HTCs key so the SPL will reject it".
When i put MTTY:
Cmd>info 0
Cmd>info 1
Cmd>info 2
HTCSSPCS_001æž7HTCE
Cmd>info 3
HTCSA¹WáÃ…8¥}ÆOÇBå%ßoô
Cmd>info 4
HTCSSPCS_001æž7HTCE
Cmd>info 5
Cmd>info 6
HTCST ÚÈÒHTCE
Cmd>info 7
HTC Integrated Re-Flash Utility, Common Base Version : 1.51d
Device Name: Titan, Bootloader Version : 1.04.0000
Built at: Apr 27 2007 22:16:48
Copyright (c) 1998-2006 High Tech Computer Corporation
CPU ID=0x4107B364
Main Board ID=0x3, CPLD ID=0x9
Cmd>info 8
--- 2K bytes sector version ---
DEVICE NAME=samsung_k9k2g08
DEVICE ID=0xAA
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x800
BLOCK PAGE=0x40
Checking block information
BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 2 (0x2) is reversed block
BLOCK 3 (0x3) is reversed block
BLOCK 4 (0x4) is reversed block
BLOCK 5 (0x5) is reversed block
BLOCK 6 (0x6) is reversed block
BLOCK 7 (0x7) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 9 (0x9) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 12 (0xC) is reversed block
BLOCK 13 (0xD) is reversed block
BLOCK 14 (0xE) is reversed block
BLOCK 15 (0xF) is reversed block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x640
Partition[2], type=0x25, start=0xC80, total=0x65C0
Partition[3], type=0x4, start=0x7240, total=0x147C0
CE Total Length(with sector info) = 0x3959200
CE CheckSum Length(without sector info) = 0x3920000
this mean have'nt "device ID" and "bootloader" ??? (info 0 and info 1)
then,
Cmd>checkimage
SPL CRC checksum = 0x671B7AE0
CE CRC checksum = 0x21756FFB
ExtROM CRC checksum = 0x44176D47
no radio checksum, no radio ROM???
it's true if the problem caused no bootloader on my titan???
can we fix bootloader??? or replace it???
pdocwrite???
any suggestion?
@ Mr. Mod, apologize for my double post. Please delete one of it, feel free. Thx.

any body.....???

still stuck no radio in my device........

Let this be a lesson to anyone that wants to flash files for different devices (like apache) to the Titan! Don't do it!! that being said there are still a few things we might be able to try to get you going again, check PM.

ImCoKeMaN said:
Let this be a lesson to anyone that wants to flash files for different devices (like apache) to the Titan! Don't do it!! that being said there are still a few things we might be able to try to get you going again, check PM.
Click to expand...
Click to collapse
thx for ur attention, but i can't go in chatt link...

you havent unlocked, try the unlocker again and carefully follow its directions
your spl is 1.04.0000 should be 1.20-olipro

bricked polaris - black screen after reset

my polaris is bricked.
i can enter tricolor screen , but nothing after that.
tried many tricks but still no solution.
1. pressing reset, screen is totally black
2. i can enter normally into tricolor screen
3. i can flash any rom i like , but everytime black screen after reset.
4. hard reset is working fine.
5. hard spl is installed
6. mtty output :
a.
Cmd>info 8
--- 2K bytes sector version ---
DEVICE NAME=samsung_k9k2g08
DEVICE ID=0xAA
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x800
BLOCK PAGE=0x40
Checking block information
BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 2 (0x2) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 13 (0xD) is reversed block
BLOCK 14 (0xE) is reversed block
BLOCK 16 (0x10) is reversed block
BLOCK 17 (0x11) is reversed block
BLOCK 18 (0x12) is reversed block
BLOCK 19 (0x13) is reversed block
BLOCK 604 (0x25C) is bad block
BLOCK 1150 (0x47E) is bad block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x780
Partition[2], type=0x25, start=0xDC0, total=0xC440
Partition[3], type=0x4, start=0xD200, total=0xE0C0
CE Total Length(with sector info) = 0x6969000
CE CheckSum Length(without sector info) = 0x6900000
b. Cmd>info 9
Storage Start Addr=0x56BA0000, length:0x7090200
c. Cmd>info 0
Platform Model IDOLA10000
Platform HW Board ID:31, PVT1
d. Cmd>info 2
HTCS00000000jR*¥HTCE
e. Cmd>info 3
HTCS;²»ÀA§v³ñ‹+¬úÐx´Wš¿
f. Cmd>boot
InitDisplay: Display_Chip=1
CpldSetSystemLED2 [1],gdwLED2Status=0.
No this System Led2 Behavior [1] polaris locks...
Is there a solution or it's time for Diamond ?

i dont know if he can help you, but hit jockyw a pm

have you tried to revert back to original SPL and ROM?
(i know you are great rom cooker, but just in case you forgot something)

Did you try these?
http://forum.xda-developers.com/showpost.php?p=2003948&postcount=2
http://forum.xda-developers.com/showpost.php?p=2350974&postcount=4

I've tried any possible mtty command ...
finally i think that there is a bad block problem (many bad blocks) ....
p.s. A friend gave me a new polaris, so cooking continues ....

sorry about your loss
any advices on what not to do ?
in order not to get in the same situation.

don't let your children play with those problematic & expensive htc pdas ...

swtos said:
I've tried any possible mtty command ...
finally i think that there is a bad block problem (many bad blocks) ....
Click to expand...
Click to collapse
it could be possible to change the ROM memory?

Imate JasJam Bricked real bad

I have unfortunately ended up with IPL-1.01 and SPL 2.03 and will not boot past logo screen, so i can not sync to load Hard-SPL to load a different rom.
Any one please help as I have spent days searching to see if i could load a rom using MTTY or any other tricks to get back to 1.04, 1.09, 2.10. Here are my details.
Cmd> task 32
CID: Wait interpreter timeout
Level = FF
Cmd> info 2
HTCSF kEØ(HTCE
Cmd> info 3
HTCSH
Cmd> info 4
HTCS Lœ3ÆHTCE
Cmd> info 5
Cmd> info 6
HTCST ÚÈÒ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 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Block 0x3F8(1016) is Reversed block
Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1800
Partition[2], type=0x25, start=0x3100, total=0x1E400
Partition[3], type=0x4, start=0x21500, total=0x19300
CE Total Length(with sector info) = 0x43AA800
CE CheckSum Length(without sector info) = 0x42A0000
Cmd> checkimage
IPL CRC checksum = 0xFA9C7DF2
SPL CRC checksum = 0x597976
CE CRC checksum = 0xB573F758
ExtROM CRC checksum = 0x42027B8F
Radio Image CRC checksum = Checksum: Wait interpreter timeout
0x0

If MTTY isn't working, try flashing orginal stock rom which came with your device, then see if device boots up

I need help - my mda vario ii stuck in splash screen
Hi I have the a T-Mobile MDA Vario II i ran unlock program HTC_Hermes_SIM_CID_Unlock_v3a - i must have run it wrong or something cause my phone has colours on the screen red green blue white with the ipl 1.01and spl 1.40 - it used to have ipl 1.4 (ithink) and spl 2.14(i think) before i tried to run the hct_herm.....v3a.
Is my phone trashed or what can i do . when i plug in the usb cable the message at bottom goes from serial to usb but thats it - the active sysnc does not see the phone. help help help any advice welcome ( short of buy a new phone) this is my new phone i only got it a few days ago.
would realllllllly be eternally greatfull for any help.- the reason i run the unlocker was the phone said no gsm and i could not phone and in the posts i read that this would fix it.....PLEASE HELP.......

Create your own thread
Hi there you may get more direct assistance if you create your own thread with specif title for your problem

the posts were wrong, this doesn't fix the "No GSM" problem...
If you have a memory card 2Gb or less, go to the Hard SPL thread, download Hard SPL V7 and then read post 1160 on page 116. You can drop the steps using sspl.exe as you have an old version of Hard SPL on your Hermes. Once you have Hard SPL 2.10 oli and an IPL of 1.04 then use the same method to install a rom. This will NOT fix the no GSM problem, there is no fix for that...
But at least you will have a PDA...

[Q] 1EFATAL HIT 1 also booting from micros... why?

Hello everyone! My hd2 is dead... sigh
i read after threads but nothing worked for now...
- WWE HD2 no brand (bought 2 years ago on eXpansys)
- HSPL2 - HSPL 2.08 (Hard SPL)
- Radio Radio 2_15_50_14 + Leo +2.15.50.14
- 113 magldr
- CWM 5.0.2.6
- XB CM7 MUST SEE. 19
- Sandisk Micro SD 32GB class divided into 2: FAT32 (32K allocation units), 1 GB EXT4, 512 swap the statute did with gparted.
Given that i use my hd2 in a very intensive way with lots of open applications at the same time
(IM +, Meridian for music, oruxmap to follow bike route, facebook, friendcaster pro
camera to take pictures while riding my a bike), so I might have not noticed certain delays
and freeze of the phone, as it has only about half a gb of ram.
When it crashed only IM+, facebook and sygic were running. I was setting a destination on
Sygic when my phone freezed and I had to do a battery pull.
When I restarted, after loading maglder phone got stuck again displaying error:
1Efatal HIT1
This thing had already a couple of times before and after some "recovery AD reset" from magldr,
without using the PC the phone started to work again.
After that I started using CLK 1.4.0.1 and I had a problem of degradation in the rom with the dayly use and
stability problems of data connection, which partially i solved doing a recovery or cwm or flashin the various same rom over.
Although at times it crashed always started it's self without to have fatal errors but losing all programs
in the rom as if it had been just flashed. So i did restorewith CWM to conitnue to use my phone as nothing happened.
Tired of having connection problems a few days ago, I came back to use MAGLDR and 1Efatal HIT1
returned.
To solve it I did : wipe (task29), flashed stock from microsd, all operations that didn't give me errors but the phone is still briked.
Flashing rom to microsd on various stocks gave my only white screen with HTC logo or boot loop.
I can remove or replace HSPL (also version 4), i can install magldr, or clk (sometimes with errors after rebooting ) but can not reach CWM anymore.
It is as if after magldr or clk the phone "fails to write in nand" but it said that he performed the operation successfully.
Last step I tried to do was boot android from microsd with magldr using the right rom obviously. I tryed too different roms and varioud microsd
but i got this error too:
Android LOAD at 11800000
from MicroSD
Load zImage
K: / android / zImage
Load inird.gz
I: / Android / INIRD.GZ
[K] 11808000:2 AE840 12200000:1 B1DFE
Load done!
1EFATAL HIT 1
I don't know what to do. My warranty has expired a 1 month and 8 days ago ... any suggestions?

did you manage to fix this? I have the same problem.

Sounds like you may possibly have bad blocks. I don't know much about this topic though. Their is a thread somewhere around here in Q&A or NAND development, it's called "bad blocks" I think munjeni wrote it.
Maybe that will help some.
1 other idea in case you do have bad blocks is to try clk 1.5 ( I have a guide written in my signature) and change your recovery size to a larger partition.

I tried your method but I have the same issues installing recovery is that when it says restart after installing recovery it doesn't actually restart. In magldr I would get the fatalhit error after and CLK 1.4 I get "cmdline: no_console_suspend=1 wire.search_count=5 clk1.4.0.1"
is there any way to save it?

checking for bad blacks bought back the following, To note I had performed task2a by accident first and then reflashed the 1.66 t-mobile uk winmo software (what came on it) and then performed info 8.
--- 2K bytes sector version ---
DEVICE NAME=hynix_h8BES0UQ0MCP
DEVICE ID=0xBC
DEVICE MAKER ID=0xAD
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x1000
BLOCK PAGE=0x40
Checking block information
BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 2 (0x2) is reversed block
BLOCK 3 (0x3) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 12 (0xC) is reversed block
BLOCK 13 (0xD) is reversed block
BLOCK 14 (0xE) is reversed block
BLOCK 15 (0xF) is reversed block
BLOCK 28 (0x1C) is reversed block
BLOCK 29 (0x1D) is reversed block
BLOCK 30 (0x1E) is reversed block
BLOCK 31 (0x1F) is reversed block
Partition[0], type=0x23, start=0x2, total=0xFE
Partition[1], type=0x0, start=0x0, total=0x0
Partition[2], type=0x0, start=0x0, total=0x0
Partition[3], type=0x0, start=0x0, total=0x0
CE Total Length(with sector info) = 0x80800
CE CheckSum Length(without sector info) = 0x80000
and then I performed task 2a
task 2a
Format ALL start
backup SPL OK
backup MISC configuration OK
SPL start start block=497, total block of CE=3599
Write 0xFF start page=0x7C40, total page=0x383C0
restore SPL OK
restore MISC configuratoin OK
restore MFG configuratoin OK
Format ALL end
what do reversed blocks mean ?

jabran200 said:
checking for bad blacks bought back the following, To note I had performed task2a by accident first and then reflashed the 1.66 t-mobile uk winmo software (what came on it) and then performed info 8.
--- 2K bytes sector version ---
DEVICE NAME=hynix_h8BES0UQ0MCP
DEVICE ID=0xBC
DEVICE MAKER ID=0xAD
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x1000
BLOCK PAGE=0x40
Checking block information
BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 2 (0x2) is reversed block
BLOCK 3 (0x3) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 12 (0xC) is reversed block
BLOCK 13 (0xD) is reversed block
BLOCK 14 (0xE) is reversed block
BLOCK 15 (0xF) is reversed block
BLOCK 28 (0x1C) is reversed block
BLOCK 29 (0x1D) is reversed block
BLOCK 30 (0x1E) is reversed block
BLOCK 31 (0x1F) is reversed block
Partition[0], type=0x23, start=0x2, total=0xFE
Partition[1], type=0x0, start=0x0, total=0x0
Partition[2], type=0x0, start=0x0, total=0x0
Partition[3], type=0x0, start=0x0, total=0x0
CE Total Length(with sector info) = 0x80800
CE CheckSum Length(without sector info) = 0x80000
and then I performed task 2a
task 2a
Format ALL start
backup SPL OK
backup MISC configuration OK
SPL start start block=497, total block of CE=3599
Write 0xFF start page=0x7C40, total page=0x383C0
restore SPL OK
restore MISC configuratoin OK
restore MFG configuratoin OK
Format ALL end
what do reversed blocks mean ?
Click to expand...
Click to collapse
You have no bad blocks, that's great.
To the people that does, run a dmesg, find the location of the bad block and increase the partition of the bad blocks.
for example, my partition table is:
Misc 25
System 160

so then why does it not load windows mobile? I do task 2a, and load 1.66 windows from the sd card straight after but I am stuck on the start screen with the circle and loading recovery ends up with fatal hit.

[Q]1EFATAL HIT 1 and no bad blocks?

I have issues with my phone, It was originally giving my 1EFATAL HIT 1 sometimes while trying to load android from MAGLDR so I decided to flash windows back in and it always gets stuck at the first screen and no numbers in the bottom left hand like there used to be.
This is how I flashed windows, task 29, copy leoimg.nbh to sd card (samsung 8gb) and flashed it via sd which completes etc and then when I turn the phone on it is stuck.
Then I tried to go back to android so task29,flash radio 2.15.50.04, flash magldr113, flash recovery and when trying to load recovery I get 1EFATAL HIT 1.
Then I tried to load android from sd card and when loading it in magldr it says 1EFATAL HIT 1.
no bad blocks
DEVICE NAME=hynix_h8BES0UQ0MCP
DEVICE ID=0xBC
DEVICE MAKER ID=0xAD
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x1000
BLOCK PAGE=0x40
Checking block information
BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 2 (0x2) is reversed block
BLOCK 3 (0x3) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 12 (0xC) is reversed block
BLOCK 13 (0xD) is reversed block
BLOCK 14 (0xE) is reversed block
BLOCK 15 (0xF) is reversed block
BLOCK 28 (0x1C) is reversed block
BLOCK 29 (0x1D) is reversed block
BLOCK 30 (0x1E) is reversed block
BLOCK 31 (0x1F) is reversed block
Partition[0], type=0x23, start=0x2, total=0xFE
Partition[1], type=0x0, start=0x0, total=0x0
Partition[2], type=0x0, start=0x0, total=0x0
Partition[3], type=0x0, start=0x0, total=0x0
CE Total Length(with sector info) = 0x80800
CE CheckSum Length(without sector info) = 0x80000
and task 2a brings the following
Format ALL start
backup SPL OK
backup MISC configuration OK
SPL start start block=497, total block of CE=3599
Write 0xFF start page=0x7C40, total page=0x383C0
restore SPL OK
restore MISC configuratoin OK
restore MFG configuratoin OK
Format ALL end
So what is going on? why do I get 1EFATAL HIT 1.

So I assume reversed blocks are normal after searching google?
I have readall threads about going back to windows mobile, installing android from sd, nand, different recovery, magldr and even ceedsmiths version. I have been flashing windows mobile from sd and through RUU but still the same, I have installed t-mobile 3.14, 1.42 and 1.66 wwe and 3.14 wwe. Only thing I can think of is that the phone is unlocked which may be when the problems occured, it was done via a code I bought.
I get the fatal hit error every time I try to boot android or recovery and windows mobile loads that very first screen only and has no number on the bottom left.

Does anyone know someone in the u.k who can maybe fix it via JTAG or something.

anything? I can't be the first to have such a problem?

Try sticking ur phone in the freezer for 5-10 min and reflash everything. I had the same issue and it worked and it helped another member here http://forum.xda-developers.com/showthread.php?t=1446263
It just means hardware is failing

I tried that in the fridge before for a few hours and it didn't work. So as you suggest I tried in the freezer for 30 minutes flashed via sd in the fridge with a 1gb sd card. completed successfully but stuck on splash screen like before.
really stuck here.

Not sure if this will help, but this is about checking the nand memory for bad blocks
http://forum.xda-developers.com/showthread.php?t=1421029

Like I said in my first post I have already done that and have no bad blocks and you can also see the info8 result in the first thread.